[–]▶ No.995318>>995434 [Watch Thread][Show All Posts]
>A Google developer has proposed /proc/pid/kill as a new procfs-based kill interface for killing a process on Linux.
>With each process running on the system having their own /proc/PID directory, the patch proposal allows writing to /proc/PID/kill with a signal number to kill that process.
>The functionality is similar to the kill command except for the process ID originating from the proc file-system rather than an explicit system call parameter, in order to avoid potential race conditions. Ultimately this new /proc/pid/kill interface could be used to write "a race-free and safe pkill."
https://www.phoronix.com/scan.php?page=news_item&px=Linux-Proc-Pid-Kill-RFC
Thoughts?
▶ No.995323
it's a marginal improvement like extending your lifespan by 1 usec.
▶ No.995324>>995337
At first I thought this was going to be a SJW thing.
▶ No.995337>>995344 >>995350
>>995324
>kill is too offensive and trigger inducing a term, so we propose to change it to holiday
>everyone loves going on holiday and I'm sure these processes will too! [emojis]
▶ No.995344>>995350
▶ No.995350>>995385
>>995337
>>995344
Amusingly enough, the most famous newsgroup about suicide back in the day was alt.suicide.holiday.
▶ No.995360>>995370 >>995435
it's some stupid UNIX shit. everything is an X was never a good idea. everything is an ioctl is fucking AIDS. "everything is a file" is just retarded and not even worth talking about any more than "everything is an HTTP request/response"
▶ No.995370>>995376
>>995360
The worst thing about the proponents of the 'everything is a file' arrangement is that they tell you about it as though it is some revelatory news.
<Everything is a file XDDDDDD I love *nix. I love science! I am enlightened.
>Is the processor a file
<Ugh no. Wut? Why would it be? Umm, I dunno.
▶ No.995376>>995408
>>995370
The everything is a file design philosophy works pretty well, look at plan 9.
▶ No.995385>>995427 >>999790
>>995350
Pretty sure that's where the 41-year old virgin posted his stuff originally[1], starting in 1995. I would read it and become filled with a sense of dread, when it dawned on me that I would one day become the 41-year old virgin. You can't escape your fate, that's just the way it is. Now I better go make myself a fresh pot of coffee and log onto my AIX account. It's going to be another long night and my nerves are shot again.
[1] Web archive sites, in case you never had the privilege of following this epic saga:
http://www.oocities.org/southbeach/lights/5427/virgin1.html
http://losernet.tripod.com/virgin5.html
▶ No.995408>>995412
>>995376
Plan 9 is 'everything is a socket', not 'everything is a file'
▶ No.995412
>>995408
The point is it's seen as a file. /sys and /proc aren't actual files on disk but follow the same idea.
▶ No.995418
This is a perfectly good addition and probably the most innocuous thing Google's done in years.
▶ No.995427>>1001874
>>995385
>it dawned on me that I would one day become the 41-year old virgin.
If you read it when he posted it back in the mid-90s, even if you were a teenager at the time, you'd be middle-aged now. So, was your premonition right?
▶ No.995434>>995436 >>995455 >>1001893
>>995318 (OP)
I can only see this happening as some PID implementing their own kill command which just phones shit on shutdown.
Fucking botnet trash
▶ No.995435>>999789
>>995360
Except when everything is an S-expression amirite
▶ No.995436
>>995434
What's to stop that from happening right now?
Init already kills every process on shutdown.
▶ No.995454
Who's "they"?
Do you mean" Someone is adding a killkill procfs"
▶ No.995455
>>995434
Then you know fuck-all about a Linux system or software development
▶ No.995491
That would make matters worse in my eyes
▶ No.995496
This could be useful when a system is so fucked that there's not enough memory to fork new processes.
▶ No.999597>>999633 >>999666
Linux is going to be unrecognizable in 5 years. The kernel will be entirely System D under a dual license, system administration will drift over time with the whims of the Pajeets at Red Hat, Intel, IBM, Microsoft, and other board members of the Linux Foundation, DRM and anti-circumvention methods working with deeply embedded sneaky technologies will prevent wrongcompute, and of course Linux will continue to become more and more unsuitable for embedded applications.
▶ No.999633>>999666
>>999597
Soon it will be like Windows, and thus they will have achieved their goal.
> systemd fucks up again
> nobody knows why
> solution: reboot server
> notabug :^)
▶ No.999635>>1001920
don't care; doesn't affect me
▶ No.999666>>999669 >>999677 >>999756 >>999937 >>1000003
>>999633
>>999597
>Soon it will be like Windows, and thus they will have achieved their goal.
YEAR OF THE LINUX DESKTOP
These cretins will finally get their with. They just started adding DRM to Wayland.
https://lists.freedesktop.org/archives/wayland-devel/2018-June/038446.html
▶ No.999669
>>999666
>"they"
Ankit K Nautiyal, Intel Pajeet at large. Bless those H1B hires.
▶ No.999672
if jewgle came up with it there must be something wrong with it
▶ No.999674
Seems pretty much interesting. Though it should be namespaced somehow. That's all. If you make it secure, it's okay. Otherwise, GTFO.
▶ No.999677>>999736
>>999666
That freedesktop shit is an unending source of poz. They even managed to affect software that has jack all to do with "desktop" crap. For example, the mc (Midnight Commander) package on OpenBSD uses their fucked-up default ~/.local ~/.cache ~/.conf bullshit hierachy, instead of the simpler traditional single dotfile or dotdir. Hell I'm pretty sure even vifm went that route too. It's all pozzed, gonna have to just write my own software from now on.
▶ No.999736>>999754
>>999677
>~/.conf bullshit hierachy
so you want all your dotfiles for all your various programs to be thrown together into your home directory ~?
▶ No.999754>>999755 >>999785 >>999949 >>999950 >>1001774
>>999736
Yes, that's exactly how it was before all this dekstop environment nonsense, and it worked great. You could type 'ls -a' and see all your stuff at once, or just 'ls' if you didn't want all that clutter. Same thing in file managers, where a key toggles the view. You could also type 'ls -alt' and see immediately which things have been modified recently and what's very old and might as well be deleted (if you no longer use the program that dotfile or dotdir goes with). And you didn't have to traverse a bunch of directories to configure a program. Now mc puts stuff in .local/share/mc/ and also in .local/share/mc/skins/ and before it was just all in one place ~/.mc, nice and simple and easy, and immediately visible.
This freedesktop hierarchy stinks of GUI management tools, that dump shit everywhere and just don't care because they'll present the user a lame ass graphical interface to configure shit with. But I don't want that junk. I'd have installed Win95 instead of Slackware if that was the case. The additional layers of abstraction don't help me. I don't want them, just like I don't want systemd. Things need to be a lot simpler and clear and direct.
▶ No.999755
>>999754
I mean ~/.config/mc and ~/.local/share/mc/skins
▶ No.999756
>>999666
double trips checked
▶ No.999785>>999949
>>999754
Nah, I'll take .conf/ over littering ~/ with an endless stream of dots any day. That .local/ bullshit is retarded though.
▶ No.999789
▶ No.999790
>>995385
>enter building
>get lamp
>quit
moth ?
▶ No.999937
>>999666
HAIL SATAN
HAIL DRM
▶ No.999949
>>999785
>>999754
I don't have any issues with .local personally. I find it satisfactory when I'm compiling software that I only want installed to my homedir (perhaps a locally compiled copy of a system program) or when I'm on a shared box without root privs. Just swap out /usr/local for $HOME/.local when doing a ./configure, throw ~/.local/bin into my path and I'm done.
▶ No.999950>>999993
>>999754
putting all your stuff in a single directory was laughably bad, still is laughably bad, and will forever be laughably bad.
it's the equivalent of computer illiterate grandmas storing everything on their desktop, and it's stupid for the same reasons.
▶ No.999993
>>999950
It's not "all your stuff", it's just config files. And having them all in the same place is more convenient. Also see: /etc
What's laughably bad is spreading shit all over the place, like in that George Carlin skit about "stuff". But I'm nor surprised at all. Modern Linux/desktop shit is designed for GUI and not anymore simple text config file editing. Hell even the logfiles now are binary. Hell I even got pissed off when Firefox changed to use binary files for config stuff. Just give me the plain text nigga!
▶ No.1000003
>>999666
thought it was about direct rendering management and not this shit - they should be working on HDCP stripping instead
▶ No.1001774>>1001794
>>999754
Blaming the XDG Base Directory for that is plain retarded because it's the thing it tired to solve: put all configs in one place. But yeah, try venturing outside your home directory and you'll realize that the rest of the system is like that. Some shit is in /usr/lib, some in /opt, some shit is in /usr/share, the executable is in /usr/bin, the configuration is in /etc, the manual is in /usr/share/man but the documentation is in /usr/share/doc and it goes on and on. And every time someone tries to fix it, it only gets worse because the support for the new standard takes ages.
Here's how retarded QuakeSpasm's installation looks when you try to follow the UNIX® hierarchy (w/o symbolic links):
~/.local/
bin/
quakespasm.sh
lib/quakespasm/
quakespasm-sdl1
quakesmasm-sdl2
share/quake/
id1/
maps/
custom.bps
custom.lit
music/
track02.wav
...
track11.wav
pak0.pak
pak1.pak
rogue/
...
hipnotic/
...
~/.config/
quake/
id1/
autoexec.cfg
config.cfg
quick.sav
s0.sav
s1.sav
...
s18.sav
s19.sav
rogue/
...
hipnotic/
...
Where quakespasm.sh changes the current directory to ../share/quake and executes ../lib/quakespasm/quakespasm-sdl[1|2]. And even then the placement of the ~/.local/share/quake/MOD/maps/ directory is quite questionable because /usr/share/ that $XDG_DATA_HOME mimics is supposedly for read-only files.
▶ No.1001794>>1001949
>>1001774
Nigga this is all retarded. The id1, rogue, and other subdirectories are from id software themselves. You even get those in DOS or Windows. Why would you want to force yourself to follow some FHS and mirror all paths in $HOME? That's stupid! You just create a dotfile for quake, or a dotdir with a couple config files in it and you're done! Only retarded autists want to do exactly things by some made up rules. That's what these freedesktop fucks are. They only know how to make things more complicated.
▶ No.1001874>>1001917
>>995427
>So, was your premonition right?
The crickets say 'yes'.
▶ No.1001893
>>995434
This is what happens when you LARP on /tech/ for too long.
Programs can already choose how to terminate on a kill signal
▶ No.1001917
>>1001874
It's creepypasta, anon. I don't believe virgin boomers exist.
*sips*
▶ No.1001920
>>999635
"First they came for the Communists . . . "
▶ No.1001949>>1002017
>>1001794
having some standards is a good thing for servers that might be used/managed by more than one person. you can do what you want on your neet gaming machine.
▶ No.1002017
>>1001949
Kek. Go make things more complicated for yourself then. I bet you run systemd too.