=== Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === Keybuk [n=scott@12.145.6.2] has joined #upstart === juergbi [n=juerg@80-219-18-22.dclient.hispeed.ch] has joined #upstart === sadleder [n=sadleder@p508118ad.dip0.t-ipconnect.de] has joined #upstart === sadleder [n=sadleder@p508118ad.dip0.t-ipconnect.de] has left #upstart [] === wasabi [n=wasabi@ubuntu/member/wasabi] has joined #upstart === tale [n=tale@207.235.54.1] has joined #upstart === wasabi_ [n=jhaltom@ubuntu/member/wasabi] has joined #upstart === mbiebl [n=michael@e180073128.adsl.alicedsl.de] has joined #upstart === liquidat [n=liquidat@4560-02bg04.stw-wh.uni-jena.de] has joined #upstart === cortana [n=sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk] has joined #upstart [11:51] Md: Did you have any problem with switching to upstart? [11:58] mbiebl: actually I have not rebooted yet :-) [11:59] Ah, ok. I've been hacking a bit on native upstart jobs over the weekend. [11:59] The results are pretty promising: http://debs.michaelbiebl.de/upstart/bootchart.png [12:01] Works pretty good so far. [12:02] the next obvious step should be running fsck/mount asyncronously from udev [12:03] mbiebl: 19 seconds from grub to X? [12:03] Amaranth: Yes, including initramfs [12:03] It's a 3 year old laptop. [12:03] _damn_ [12:03] i'm sitting at 35 seconds for my laptop and it's less than a year old :) [12:03] I think I need to do some trimming [12:04] I have to admit, if I switch to gdm instead of entranced, it adds another 8 secs. (gdm is just so slow...) [12:05] heh [12:05] entranced, huh? Hadnt heard of that one. [12:05] % apt-cache search entrance [12:05] e17 login manager [12:05] % [12:05] Ah. [12:05] gdm is a key part of a couple nice gnome features [12:06] Still, I think gdm needs some serious profiling ;-) [12:07] Even kdm is a lot faster. [12:07] either way if with gdm you can get a 27 second boot i should be able to get 13 seconds or something :) [12:08] Which fs do you use for / ? [12:08] Reiser3 can take 3-4 secs just for mounting. [12:08] ext3 [12:08] i'm plain and boring :) [12:08] (depending on the size of the partition) [12:09] but i've got a core duo and the fastest laptop HD in existence so... :) [12:09] I had no idea people still worked on e17 [12:10] My boot time probably decreased by a half when i switched from a 5400 RPM HDD with less than MiB of cache to a 7200 RPM one with a 8 MiB cache. :-) [12:10] wasabi_: they have a pretty complete Debian repo at deb http://edevelop.org/debian/ unstable main [12:10] That stuff usable [12:10] ? [12:11] ion_: yeah, i've got one of those two [12:11] Or is it still just tech demos? [12:11] is yours hitachi? [12:11] Samsung [12:11] wasabi_: I imagine the login manager, window manager, etc is usable but the rest is still at tech demo level [12:11] The older one was an IBM Deahtstar. [12:12] wasabi_: It's definitely usable, but e17 won't become my main desktop though. [12:12] ion_: ah [12:12] Death even. [12:12] ion_: sata? [12:12] Plain PATA. [12:12] oh [12:12] suppose it doesn't make too much of a difference with these laptop drives [12:13] mbiebl: wow, you disabled most everything to get that time :) [12:14] Amaranth: Really? [12:14] well i've got junk for bluetooth and such here [12:15] looks like all you did was essential "this has to run for my system to boot" stuff plus dbus and X [12:15] Well, not quite: I run syslog-ng, acpid, anacron, cron, dbus, hal, NEtworkManager, dhcdbd, console-kit [12:16] Pretty complete I'd say. [12:16] oh, you made upstart scripts for hal, networkmanager, and dhcdbd? [12:16] because otherwise dbus will start those with it's own init system [12:17] That's actually not true anymore in Debian. [12:18] oh? [12:18] I made all the Dbus init scripts regular sysv init scripts the last week. [12:18] cool === Amaranth should start working on making his boot faster [12:18] /etc/dbus-1/event.d/ will soon be gone. [12:18] if i can get it below 20 seconds it's faster than hibernating :) [12:19] Are we suspecting that upstart will in fact replace dbus' init system? [12:19] wasabi_: sure [12:19] including activation, or has nobody brought it up? [12:20] Ah, Service activation is a different topic. [12:20] activation is not something upstart should manage [12:20] Why? [12:20] i know i don't really want upstart managing my rhythmbox ;) [12:20] although i suppose it doesn't matter [12:20] But dhcdbd, network-manager, hal, avahi etc are all native jobs which run as soon dbus is started. [12:20] Hmm. [12:21] I'm not sure how I feel about that either. I think I don't like the idea of DBUs launching UI apps etiher. [12:21] Heh. [12:21] upstart seems a bit heavyweight for something as simple as 'dbus path doesn't exist, $app provides it, launch $app' [12:22] I think a few people have brought up the idea of using upstart for desktop sessions. [12:22] I'd like to think about it someday. :0 [12:22] Basically a non-PID 1 upstart copy.