Sigh.
Has anyone implemented a pure Upstart system? I’ve spent several days now trying to do so, and with little success.
First, let me say, I really like the idea of Upstart. I dig the concept of an event-based init system. I dig the idea of a faster boot. That, and I’m motivated to try a different init system since I’m just playing around and having fun anyway.
However, every implementation I can find – including the latest Ubuntu flavors – basically break down to a handful of ”pure” Upstart jobs, and then start calling all the old SysVInit scripts. It’s very messy and hard to “reverse engineer”
Don’t get me wrong – I understand the why of this – in the vast number of cases Upstart needs to be able to use those existing scripts somehow. This makes sense, sure. However, in my use case I don’t want any SysVInit scripts. I’m building up from scratch, and I’ll be packaging everything myself, so I can afford to go “pure” Upstart.
Here’s some of the bugaboos I’ve ran into:
Upstart says you need a few things to build Upstart:
- Linux 2.6.4 or later
- GCC 4.1 or later
- GLIBC 2.4 or later
Well, you need libnih as well.
If you go off the Kubuntu start up scripts, you need mountall (which has a very scary man page) and calls for plymouth, which in addition to being something I don’t want to mess with at this point in the process, also calls for mountall as a dependency.
If you’ve just spent several hours mapping out scripts and then are faced with untangling dependencies, it’s discouraging.
I can’t find an easy way to track the boot process just from scripts. Here’s what I mean. Since there isn’t an existing set of basic scripts, I tried to look at those in an stock Kubuntu system. But, since events can be fired from just about anywhere, you have to basically print out every script to make sure you are catching the entire “flow”.
Basically, I’d just like to know if it’s been done so I know it’s possible and might have somewhere to look for a clearer start.
Recent Comments