[02:17] <lupine_85> hello people :)
[01:30] !christel:*! Morning all. The Ubuntu Marketing Team are conducting a survey at the moment and have kindly asked if we could encourage users to participate, although the survey is Ubuntu-centric they intend to release the report under creative commons and hope that it will be useful for the FOSS community as a whole. For those wishing to participate, head over to http://surveys.geekosophical.net/ and have a good day!
[02:14] <Ingmar^> on edgy, using upstart, the modules for cpu frequency scaling don't get loaded correctly, i'm on an intel pentium M 1.6 gHz, I can load them manually, but i'd like to have that done on boot, how do i do that ?
[02:15] <Ingmar^> highlight me of someone feels like helping, and thanks :-)
[02:16] <cortana> does it get loaded with sysvinit?
[02:16] <_ion> That isn't really related to upstart.
[08:43] <johnnybuoy> why don't you guys team up with einit? it look as though your goals are somewhat common.
[08:50] <Md> oops
[08:51] <johnnybuoy> LOL
[08:51] <johnnybuoy> not bad, ehh
[08:52] <johnnybuoy> what is uptart different in than einit? why is it better?
[08:54] <LarstiQ> johnnybuoy: the original announcement I saw had a load of comparisons
[08:55] <LarstiQ> not sure if einit was in there
[09:04] <_ion> From the einit feature list:
[09:04] <_ion> - Configuration file in XML
[09:04] <_ion> ARGH
[09:05] <_ion> http://einit.sourceforge.net/documentation/users/x203.html
[09:05] <_ion> I already hate it. :-)
[09:06] <asdx> is upstart distro specific or will be able to run in other distros too?
[09:06] <_ion> It's not distro-specific.
[09:07] <asdx> nice
[09:16] <johnnybuoy> so no need to configure through xml, that's minr
[09:17] <johnnybuoy> but why make 5 replacements to init
[09:17] <johnnybuoy> it's such a waste
[09:18] <LarstiQ> right, everyone flock to upstart! :)
[09:18] <_ion> Right. :-)
[09:18] <johnnybuoy> :D
[09:18] <LarstiQ> johnnybuoy: fwiw, the model was different enough to other solutions to warrant a new project
[09:19] <LarstiQ> but that should all be explained in the docs
[09:19] <_ion> Actually there are lot more than 5 replacement for init. Keybuk inspected many of them before concluding that none of them are adequate.
[09:19] <johnnybuoy> will it do parallel starting? modes?
[09:19] <johnnybuoy> LOL
[09:20] <_ion> His discoveries are documented. Perhaps i'll dig up the URL if nobody else does. :-)
[09:21] <johnnybuoy> thx :)
[09:21] <johnnybuoy> you maybe even put it in the topic to not get annoying questions like these ;)
[09:22] <johnnybuoy> right, LarstiQ , right
[09:22] <LarstiQ> a guy can hope :)
[09:22] <johnnybuoy> wll, i can try,but...
[09:22] <asdx> what features for example upstart has that initng/einit lacks?
[09:23] <LarstiQ> johnnybuoy: http://www.netsplit.com/blog/articles/2006/08/26/upstart-in-universe
[09:23] <_ion> "Existing implementations" in http://people.ubuntu.com/~scott/upstart/spec.txt and in https://wiki.ubuntu.com/ReplacementInitDiscussion
[09:23] <LarstiQ>  /win 53
[09:23] <_ion> initng is covered in them.
[09:23] <johnnybuoy> thx!
[09:24] <_ion> At least the latter is linked from upstart.ubuntu.com, which is in the topic.
[09:25] <LarstiQ> my paste is as well
[09:26] <_ion> Chronologically the text file is the oldest, and the blog entry is the newest.
[09:30] <asdx> johnnybuoy: are you running upstart?
[09:30] <johnnybuoy> yep
[09:30] <johnnybuoy> on ubuntu edgy
[09:30] <johnnybuoy> quite stable right now...
[09:30] <asdx> cool
[09:31] <johnnybuoy> asdx, are you using einit?
[09:32] <asdx> no
[09:32] <asdx> normal sysvinit
[09:32] <asdx> i don't know which to choose yet ;P
[09:32] <asdx> but i will try them all :P
[09:33] <asdx> upstart doesn't need /etc/fstab?
[09:33] <_ion> What does an init daemon have to do with fstab?
[09:34] <asdx> http://people.ubuntu.com/~scott/upstart/spec.txt
[09:34] <asdx> there says something about fstab
[09:35] <_ion> Upstart _jobs_ handle mounting filesystems, upstart itself doesn't. Just like scripts started by sysvinit handle mounting, not sysvinit itself.
[09:36] <johnnybuoy> cio all!
[09:36] <johnnybuoy> ciao all!
[09:36] <asdx> i see
[09:37] <asdx> _ion: so if the kernel detects file systems upstart jobs mounts them?
[09:39] <_ion> With upstart, it's going to be something like this: HAL finds a hard disk and triggers an upstart event for each partition. An upstart job responsible for mounting starts on such event and, if the partition is listed with 'auto' in fstab, it mounts it. As soon as each 'auto' partition in fstab is mounted, the job triggers a 'writable-filesystem' event. Other jobs may start on that event.
[09:40] <_ion> Actually, for the 'writable-filesystem' event to be triggered, most likely only FHS mountpoints are going to be considered.
[09:41] <asdx> i see
[09:41] <asdx> thanks for explain
[10:55] <Ingmar^> on edgy, using upstart, the modules for cpu frequency scaling don't get loaded correctly, i'm on an intel pentium M 1.6 gHz, I can load them manually, but i'd like to have that done on boot, how do i do that ?
[11:50] <theCore> Ingmar^, I don't it's related to upstart
[11:50] <theCore> check https://launchpad.net/bugs/36014
[11:51] <Ingmar^> theCore: don't think it's related to upstart ?
[11:51] <theCore> Ingmar^, upstart just launch programs
[11:52] <Ingmar^> in the bug the modules are loaded, but mine aren't, on boot
[11:52] <Ingmar^> and if i load them, it just works
[11:52] <Ingmar^> right, that's true
[11:54] <Ingmar^> thanks for the reply btw
[11:55] <theCore> Ingmar^, np