3 ms·
At the time they made the switch, there was not much documentation or support for upstart. All documentation on the internet was (is?) for init scripts and runl
by memset 13y ago
At the time they made the switch, there was not much documentation or support for upstart. All documentation on the internet was (is?) for init scripts and runlevels.
For example, I wanted to take some old hardware and set it up as a server. Easy - just change init to runlevel 3 (no display) and boom, there you are, headless linux.
If I wanted to do that in ubuntu, I still wouldn't know how, to be honest. I guess I'd have to reinstall it with ubuntu server? Do we even have single-user mode any more?
(I learned sysadmin from "the armadillo book" [1]. I feel like most of the concepts are identical, but the tools are so different now. all I want to do is run a new script on boot. why do i want upstart??)
[1] http://shop.oreilly.com/product/9780596003432.do http://shop.oreilly.com/product/9780596003432.do
- icebraining 13y agoIn my case, the "Upstart Intro, Cookbook and Best Practises" document has told me all I needed to know. For example, here's the info on Runlevels, including how to set Single-User mode either temporarily or permanently: http://upstart.ubuntu.com/cookbook/#runlevels http://upstart.ubuntu.com/cookbook/#runlevels all I want to do is run a new script on boot. why do i want upstart?? Frankly, if all you wanted was that, you could just stick the script in the kernel init= parameter, no need for Upstart or SysV ;) Both of them are daemon management applications, and frankly I don't think it makes much sense to optimize for the "running script on boot" versus sanely managing daemon startup. That said, at least on Ubuntu the SysV infrastructure is still called (as an Upstart job), so you should still be able to stick something in /etc/rc.local. Alternatively, you can just write an Upstart configuration file: post-start script #your script here end script