Put everything you need to run automatically at startup in /etc/profile or one of the other autoexec files, and you won't have to deal with a mess of init scripts or the horrors of systemd. It's like AUTOEXEC.BAT for *nix, easy and simple. If you want a GUI just put startx in there...
Name:
Anonymous2015-01-26 15:00
Most init systems start some non mutually-dependent services on parallel to speed up the entire boot process, a feature your propose init system lacks.
OpenRC already does this without going "i'm lennart quality software".
Name:
Anonymous2015-01-26 15:11
How should logging/monitoring be handled? If everything is just disjoint programs started from a shell script how can you hook any kind of instrumentation in? How to deal with orphaned processes? How to deal with dependencies, i.e some service A requires networking, logging and service B to be started before hand? Speaking of networking (or other high latency services), do you really wanna stall the entire boot process just because of these? Which brings up: How to deal with asynchronous/parallel startup? In particular with combination of above - parallel + dependencies.
If you consider these 'unnecessary bloat' I would question your use of a computer in the first place - computers are made to automate things and make our lives easier, why would you *not* wanna have fast, asynchronous, event based boot with automatic dependency handling?
When is (s) ever going to be false? All this does is waste the programmer's time when they have to look up the definition for this silly macro when they see this:
Pipe the output to a file if you want. It's not needed most of the time.
Speaking of networking (or other high latency services), do you really wanna stall the entire boot process just because of these? Which brings up: How to deal with asynchronous/parallel startup? In particular with combination of above - parallel + dependencies.
Use &, as mentioned above.
And I'd argue that if you find managing services so complex that you need an entire fucking bloated system to do it, you have too many services.
>>12,14 You don't even have to login. It boots directly to a shell. If you want SSH access then just put a line in that script to run the sshd. To all the "OMG BUT IT'S r00t!!111" whiners: I've been using DOS (and early Windows) for over a decade and that's exactly what it is, with full control full access no-DRM no-"security" bullshit.
>>19 Poettering. He manages to somehow turn technical issues into retarded pseudo-SJW "muh feelings" bullshit. "Accept systemd or you're a *ist bully" seems to be his way of getting his shit into production.
You don't even have to login. It boots directly to a shell. If you want SSH access then just put a line in that script to run the sshd. To all the "OMG BUT IT'S r00t!!111" whiners: I've been using DOS (and early Windows) for over a decade and that's exactly what it is, with full control full access no-DRM no-"security" bullshit.
haha, now you're rambling about some more bullshit that's never going to happen and never going to be fulfilled because you'd rather jerk off to cartoon characters than do anything constructive.
started off with a simple fix that had flaws, turned it into some elaborate set of fixes that's never gonna fuckin happen.
cudder's all talk and no action.
Name:
Anonymous2015-01-27 7:58
haha, now you're rambling about some more bullshit that's never going to happen and never going to be fulfilled because you'd rather jerk off to kids than do anything constructive.
started off with a simple fix that had flaws, turned it into some elaborate facial reconstruction surgeries that's never gonna fuckin happen.
>>25 cudder doesn't jerk off to cartoon characters, where did you pull that from
Name:
Anonymous2015-01-27 12:20
>>8 And where is this program logic supposed to be located? Every program ad hocs implement it themselves? A common library? Aka part of the init system? Aka not just /bin/sh anymore? Hm...
>>25 "never going to happen"? That's what my Linux system has been setup as for the past few years.
>>30 You just figure out what they need and put the line in the right place in the init shellscript. Nothing fancy or complicated about it. Even an idiot would (should) know that you want ssh to run after the network is up.