Linux, not even once!

try this code:

rm rf /*

>>61320225
grate*

>>61320225

> Be OP
> Use kill -9 despite all the nasty stuff that can happen then.
> OP fucks up his system because of this (duh)
> Goes shitposting on /g/

Good one OP! OMG I really hate linux now.

>>61320295
I used kill first, you fucking moron.

>>61320225
>he dosent know about -9

>>61320311
Stop damage controlling, freetards. That's not the issue, I have already explained I tried regular kill first.

>>61320225
>logged in as root
something tells me gparted isn't your only problem faggot

>>61320310

That doesn't change a damn thing about kill -9 you incompetent cockmongler.

>>61320331
>running gparted as anything but root
Excuse me, but are you retarded?

>>61320352

6/10, made me smile.

But seriously, I hope you're trolling m8

>>61320351
So let me get this straight: your dogshit toy OS comes with a feature made specifically for cases in which an application is not responding anymore and can't be terminated cleanly, named SIGKILL, but I'm wrong for using it?

Alright, thanks for playing, I'll just start ignoring you from now on, kid...

>>61320225
Use pkill.

Also how experienced are you on Linux?

>>61320371
Stay ignorant newfriend.

>>61320370
I hope you faggots are trolling. I have been sysadmining for 27 years, since Novell fucking Netware, and I've never had to deal with a cruder OS than Linux. What kind of OS is so shit it doesn't even have control over its own processes, being unable to terminate them? That is literally indefensible, and you guys are a special kind of stupid for even trying to defend it.

>>61320395
You're nervous and it's showing.

>>61320371
Summer needs to end already.

>>61320371
Yes, you understood what kill -9 does but you clearly didn't think about its implications.

File: 2.png (55KB, 326x371px) Image search: [Google]

55KB, 326x371px

>>61320225
Is this the daily "I'M TOO RETARDED TO USE LINUX" thread?

>>61320371
Lol that's right use kill -9, on gparted no less.
Frustration leads to stupid decisions, but you don't have to listen to anyone if you don't mind fucking everything up.

>>61320432
I'll say it again because Loonix shills are obviously too dumb to understand the first time: kill -9 is not what caused this. It was happening before. kill -9 was a last resort (that obviously didn't change anything).

>>61320413
It's not summer where I live.

>>61320473
Nice, keep repeating the "kill -9" red herring.

Freetards are so pathetic.

>>61320483
It would help if you didn't do the same thing until two posts ago.
Instead we are pathetic.
I agree, its pathetic to try to defended an operating system against a raging retard, one who cares to insult rather than learn.
Shit thread, go to hell.

>>61320553
Anyone can see from that post that you're literally on the verge of tears. Stay mad, freecuck.

File: hm.jpg (44KB, 282x341px) Image search: [Google]

44KB, 282x341px

Can someone explain to a newfag what is wrong with OP way of terminating process..?

try: ps -ef | grep gparted
then: kill -9 PID PPID

>>61320577
Nothing. It's a desperate red herring in a frustrated attempt to distract readers of the thread from the real issue here, namely that Loonix can't do something as simple as terminating a dead process.

>>61320404
It's 'more crude', not 'cruder'.

What systems were you running in 1990? Genuinely interested.

>>61320586
Naah, he's too retarded. I planned to give him a for loop that would list all gparted PIDs and kill them but after reading his replies he can fuck off.

Try sending SIGCHLD to the defunct process' parent.

>OP doesn't know how to kill a zombie process
>blames it on Loonix and not his own incompetency
nothing new here

File: hmmmmm.gif (469KB, 512x807px) Image search: [Google]

469KB, 512x807px

>>61320621
OP, I'm not asking you.

>>61320225
read the error. kill gpartedbin you pleb

>>61320626
https://en.wiktionary.org/wiki/cruder
Also Netware.

>>61320664
tssss... so he just tries to kill wrong process..?
I thought there's something more to this...

>>61320664
>another Loonix user confirms he's retarded
Can't tell if you're really that dumb or actively trying to make Linux users look bad.

File: I understand.png (10KB, 416x279px) Image search: [Google]

10KB, 416x279px

>windows
>program hangs
>click the X
>nothing
>open task manager
>wait for it to open
>scroll through list to find bad program
>click end task
>nothing
>tell the computer to turn off
>"waiting for programs to close..."
>unplug computer
>turn it back on
>needs to check filesystem
>wait an hour for it to finish
>boot up
>bluescreen
Windows masterrace

>>61320672
It's far more crude to say 'cruder' than 'more crude'

What versions of Netware on what hardware? What was the network infrastructure like etc?

>>61320730
Regular PCs on token ring.

Works on my machine

File: damn son.png (277KB, 787x221px) Image search: [Google]

277KB, 787x221px

>>61320773
You have got to be trolling.

>>61320404
>I have been sysadmining for 27 years

been a sysadmin for 27 years but you still don't know what a defunct process is nor how to kill one nor how to fucking google it

you are literally everything that is wrong with self-described power users

File: Green.Lantern.The.Animated.Series.S01E04.Into.the.Abyss.720p.WEB-DL.x264.AAC.mp4_snapshot_00.42_[2017.05.05_05.37.23].png (685KB, 1280x720px) Image search: [Google]

685KB, 1280x720px

>>61320729
> Windows
> Program hangs
> Click X
> Nothing happens
> Click X again, Windows registers program as hung
> "The program is not responding. Do you want to wait or terminate?"
> Click terminate
> "Please wait while Windows collects diagnostics information"
> Program is killed
> "Do you want to try debugging?"

alternatively

> Program hangs
> Open task manager
> Right click "Go to Details"/"Go to Process"
> Right click "End task"/"End Process"
> Click "End Process" in confirmation box

And thus the program goes away, without having to restart, without having to unplug and without bluescreens.
OP is a retard, but you are twice the retard for doing something even my grandma would consider fucking stupid.

>>61320225
>kill -9
Read the fucking manual

>only one gpartedbin process is permitted

muh freedumb cucks BTFO

>>61320818
t. never used windows

>>61320241
rm: cannot remove 'rf': No such file or directory

jk i'm not that stupid

has op figured out he needs to find and kill the ppid yet or has he had enough of trying to troll trolls?

>>61320225
You killed gpartedbin but not gparted you fucking retard

>>61320225
I Don't Know Unix And Am Retarded: The Thread

The Z means it's a zombie process. That happens when a process is forked from a parent process, is then killed, but the parent hasn't waited for its return value. The Zombie process is but an empty shell that stores the return value.
Kill the parent (PPID is the third column in ps -ef) and the zombie process shall be adopted by init and reaped.
(Yes, this is all proper Unix terminology. The hackers of old were metal as fuck.)

>>61320404
>I have been sysadmining for 27 years
That's a lie. Knowing what a zombie process is is basic stuff.

>I've never had to deal with a cruder OS than Linux
Another lie. You've never seen a proper UNIX. Linux is extremely user friendly and polished compared to systems like AIX or HP-UX.

The rest is pretty much a confirmation that you are a retard that doesn't know anything.

>>61321264
>b-but muh unix shit
I'm sorry if I've never been in academia. My area of work has always been the real world.

>>61321292
So what is this work in the "real world" that you've been doing?

>>61320875
haha :DDD

>>61321308
I've built three Gibsons from scratch.

>>61320577
a process can't catch or ignore SIGKILL (9), thus the process will be stripped of it's resources effectively killed. in turn this does not give the program any chance to recover / exit in a clean fashion, potentially resulting in an unstable/unsafe state.

File: 1499264336782.png (40KB, 400x400px) Image search: [Google]

40KB, 400x400px

>>61320225
>kill -9

>>61320225
have you tried turning it off and back on again?

>>61320729
winkey + r
TASKKILL /F /IM process.exe
never fails

File: 1496044144852.gif (2MB, 295x254px) Image search: [Google]

2MB, 295x254px

>>61320225
>kill -9
Why didn't you just rip the fucking power plug out of the wall while you were at it.

>>61321942
>being this retarded
ripping out the power plug could lead to file system damage kill -9 just affects one process

>>61321958
>ripping out the power plug could lead to file system damage
did you just step out of a time portal from 1993?

>>61321973
>I don't know how hard drives work!

>>61321995
What's a "hard drive"? Pic related is where my filesystem resides.

File: SSD.jpg (33KB, 575x352px) Image search: [Google]

33KB, 575x352px

>>61322011
>forgot to attach file...

>>61321973
You fucking moron

If you rip out the power cord in the middle of a write what do you think is going to happen?

>>61321958
>thinks kill -9 gparted is a good idea
>afraid of file system corruption

>>61321973
Welcome to year 2017 where writeback cache is used all the time you fucking moron.

>>61321995
>harddrive
wow you really did just step straight out of the 90s

>>61322026
i'm still using hdds ok?
and an incomplete write can cause you trouble if it's unfortunately located

especially when doing some raid stuff

>falling for the linux meme
kek

>>61322448
This, Linux is literally the feminine penis of /g/.

>>61322703
>would much rather use windows, dealing with crashed left and right, unable to make adjustments to the core system

A great kernel won't really care some shit process died.
Linux shills on suicide watch.

>>61322774
When was the last time you "adjusted" your loonix "core system", kiddo?

>>61322822
are you referring to the last time I installed a kernel module or programmed one?

>>61322882
Because you can't install kernel modules or program ones for Windows, I forgot!

>>61322882
>>61322904
kek he gotchu

>>61322904
>>61322917
he got me on that one, but can he have different kernels to chose from at the same time?

File: boot_manager.jpg (29KB, 600x544px) Image search: [Google]

29KB, 600x544px

>>61322965
Ahem...

>>61323048
that's basically multiboot and you need to install your software etc on both versions if you want to use it, it's not as simple as just switching out the kernel, leaving the whole directory tree untouched and not requiring a separate partition

>>61320241
-rf retard.

>>61320225
You should've used cfdisk.

>>61320463
hourly*

File: unimpressed.jpg (47KB, 620x430px) Image search: [Google]

47KB, 620x430px

>>61323176
>no support for GPT

>>61320577
OP is a dujmb newfag

>>61320225
$man kill
Read it you fool

>>61320225
Where do technology illiterate mactoddler morons get the false impression that they or their fruity toddler toys are welcome much less belong on a technology board?

>can't figure out simple process/session management

Retards shouldn't be using Linux.

>>61323334
I thought OP was the autistic 'mactoddler' poster taking a break tbqh.

>>61320371
>kernel has powerful feature
>retard abuses it without knowing what the fuck it does
>SIGKILLs fucking gparted
>can't deal with simple process management
>doesn't even know what a zombie process is
>thinks the process is "not responding"

pls go

>>61320225
>logged in as root
>fucking with the command line when you don't know how to use it
Haha. Saged.

>>61320330
just kill the job retard
or go back to windows and have fun with your spyware

>>61320818
He obviously overexaggerated the process because OP did the same. If you are too dumb to kill processes on linux you should just end yourself.

>>61320331
>not being 24/7 root on your own machine

What's the problem? Can't handle the heat? Lol.

>>61320225
this happens to me on windows all the fucking time

File: screencast-2017-07-11_12.32.35.webm (2MB, 1920x1080px) Image search: [Google]

2MB, 1920x1080px

>>61320225

>>61321646
Feh! Go hack a Gibson an then we'll talk.

>>61320225
try

kill -9 1

it will fix all your problems

>>61323176
You mean gdisk, which is basically fdisk for GPT.

>>61320225
>Install Windows
Enjoy your MicroSpy(tm) technology. Hope you don't have any pirated media, anon.

File: 1374577328217.png (224KB, 554x439px) Image search: [Google]

224KB, 554x439px

>>61320225
>Fucking SIGKILLing a program without a good reason
>Doesn't allow it to clean up lock files and other shit it might have
>Complains about shit not working
It's entirely your fault, OP.

>>61320241
It's better to rtfm instead.

>>61320626
>It's 'more crude', not 'cruder'.
Both "cruder" and "more crude" are correct. If you're going to be a grammar nazi, at least do it properly.

>>61320404
>I have been sysadmining for 27 years
I can't believe you worked as a sys admin for that long without ever seeing a zombie process...

do you at least know how to use google?

>>61320225
ITT:
>what is a zombie process stuck on I/O that was killed in a critical section?
Can you please leave now?

>>61326714
OP here. I spent my 27 years sucking dicks, so I'm not updated on modern technology like the googles.

File: 1498090022434.gif (384KB, 421x437px) Image search: [Google]

384KB, 421x437px

app

>>61320241
windows user detected.
Try

rm -rf / --no-preserve-root

File: q4pXd54.png (162KB, 568x602px) Image search: [Google]

162KB, 568x602px

>>61320225
I know this is bait, but seriously, I can't take anymore of this.
>>>/v/, either actually LEARN informatics or fuck off.
I'm sick, physically and emotionally sick, of your incessant shitposting.
If you don't understand a topic, don't comment on it.
Linux is the furthest away from being obsolete compared to the proprietary and bricked shitfest that is Macintosh software and hardware, or the banal and bloated botware of Micropenis.
If you want play your shitty AAA games (in which they don't even bother anymore), rather than actually contribute to intelligent technology related discussion? That's great.
But newsflash!
We have a containment board for that rubbish:
>>>/v/
>Go home!
>Picture very much related, it is you trying to browse and understand TRUE /g/threads.

>>61320225
it looks like you were fucking around with something you shouldn't have been fucking around with, Linux is not going to hold your hand and go "nu-uh." before you go fucking around with shit, READ SOME DAMN DOCUMENTATION. Your problem is operator error, not a Linux problem.

>>61320621
unironically accurate

>>61320331
>not using su
I bet you use sudo like a mouthbreathing faggot.

>>61320818
neither of these works 100% of the time

>>61326854
>Picture very much related, it is you trying to browse and understand TRUE /g/threads.
Most people are here just to shitpost desu

>>61327009
>MMXVII
>not using doas
Is it self-loathing?