0 Followers
3 Following
15 Posts
@anselmschueler @myrrhperiwinkle @whitequark > You need to rely on something other than the kernel for this basic property of your process.
Then I have good news for you: procfs is a pseudo-filesystem implemented in your kernel.
> Unless you make your own mount, which I'm not sure whether you can in some way without effective root.
Namespaces, but in case of procfs requiring root is a good idea(see mount options, that give more isolation).
> Even if you make your own mount, it's a hideously complicated sequence compared to just having a syscall for this, especially if you rigorously use O_PATH etc. to avoid TOCTOU. The path is effectively a magic number (a magic string) which is just inelegant.
System call numbers are also magic numbers in that sense. If syscall numbers could be rebound, we would be in exactly same situation regardless of mapping in VFS.
@whitequark I will leave, but leave you with thoughts of procfs in userspace. And maybe some sandboxing.
@whitequark at least you won't get some unexpected ioctl when implementing procfs implementation with fuse.
Also, Linux procfs is not one from Unix, it's one from Plan 9.
@robryk @iurii @whitequark for Plan 9, which Linux took procfs from, it was sensible and probably even worked.
@whitequark or you can fight u-boot for 30 minutes and then install Gentoo
@TechConnectify video for those, who skipped physics in school.
Maybe there is attribute that inverts them? Wait, is it gowin?

No-no-no-no. Watch this.

@TechConnectify

This definetly should work, unless he banned me.

There is no detailed explanation how exactly it works, but I guess No Effort November should be no effort. Interesting video anyway.

Just noticed my main instance is blocked by yours. There probably should be somewhere manual follow accept button.