uselessdguy

7 ms·

31.
by uselessdguy 12y ago
Most people don't make a distinction, but I feel that is important to note these. Strictly speaking, init(8)'s sole responsibility is to reap children, set the session and process group IDs, and optionally exec the actual process
32.
by uselessdguy 12y ago
Actually, you do get (limited) dependency management through insserv, which was standardized by LSB and its set of initscript headers. Most dpkg and RPM-based distros used them. Automatic respawning is a job for a process supervisor, not a
33.
by uselessdguy 12y ago
systemd's purpose is to deprecate fstab(5) entirely through GPT partition discovery. These things can already be accomplished through a device node manager, such as (e)udev. We just no longer handle maintaining it, because it doesn&#x2
34.
by uselessdguy 12y ago
Sorry about that. We've been under attack since shortly after we got covered on Phoronix. Started off with IRC bot spam, but looks like they got the wiki, as well. We're working on undoing it. Good thing ikiwiki is versioned. It&#
35.
by uselessdguy 12y ago
It's a little bit of both, coupled with the fact that I simply wanted a challenge, being a bored sap and all. This is probably the first remotely noteworthy thing I've done. The end goal is to drive systemd into a direction that f
36.
by uselessdguy 12y ago
Figured I'd make a throwaway to answer questions. I'm the person who goes by The Initfinder General. Feel free to ask and be elucidated about uselessd and my general outlook on systemd/the state of Linux/Unix, if you so