| GNU\colossus | hi there. I just asked what's the reasoning behind changing /etc/event.d to /etc/init in 10.04, and they told me it's an "upstream change". | 14:31 |
|---|---|---|
| GNU\colossus | so I thought I'd just relay my question here: what's the reasoning behind the change? | 14:32 |
| GNU\colossus | what's so bad about /etc/event.d/, now that all distros using Upstart actually adopted that path? is /etc/init/ at least going to be mandatory? | 14:32 |
| ion | event.d is simply a confusing name, since the files aren’t events. | 15:02 |
| GNU\colossus | ion: and that's the official reason to break all the guides and docs out there describing how to interface with upstart's init-scripts from 200X to march 2010? I mean, it's not like there aren't many, many rather confusing things in a GNU/Linux or UNIX systems because of history, right? why not just stick to accepted de-facto standards? | 17:14 |
| ion | The job syntax itself has changed as well. | 17:15 |
| ion | And will change further in the future. | 17:23 |
| ion | The current directory name will most likely stay, though. | 17:23 |
| GNU\colossus | ion: why not include a version identifier in the scripts themselves then? | 17:32 |
| ion | It’s planned for future versions to have automatic backwards compability for ≥ 0.6 job definitions. | 17:40 |
| ion | http://www.youtube.com/watch?v=qMtFarv7FuA | 23:00 |
| Keybuk | ion: ? | 23:04 |
| ion | Offtopic, just some old beatboxing of mine. | 23:05 |
| Keybuk | ahh | 23:05 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!