[15:00] <mbiebl> Keybuk: hi
[15:00] <Keybuk> hey
[15:00] <mbiebl> tested your ubuntu-boot ppa
[15:00] <mbiebl> noticed two issues:
[15:00] <mbiebl> With FSCKFIX=no, it fails to boot
[15:01] <mbiebl> and I get a warning during boot from mountall, that it couldn't write the pid file
[15:01] <mbiebl> as the fs was ro
[15:02] <Keybuk> err, as in you *set* FSCKFIX=no?
[15:02] <mbiebl> mountall also mounts stuff which is later attempted again by the apparmor sysv init script
[15:03] <mbiebl> Yes, I had set FSCKFIX=no
[15:06] <mbiebl> With FSCKFIX=yes it boots fine
[15:07] <mbiebl> I'm getting a warning though: init: mountall main process (927) terminated with status 1
[15:08] <Keybuk> oh, that's not good ;)
[15:10] <ion> mbiebl: Do you have multiple partitions in fstab, btw? Are they on the same disk?
[15:10] <ion> mbiebl: Oh, actually, do you have multiple pass=2 partitions in fstab?
[15:11] <mbiebl> interestingly I can't always reproduce this warning message
[15:12] <mbiebl> The: "mountall: Unable to write pid file: Read-only file system" is reproducible
[15:12] <mbiebl> The other one not
[15:12] <ion> keybuk: Does mountall handle the pass=1 / partition first and pass=2 ones later in parallel? I haven’t really looked at that part of the code.
[15:12] <mbiebl> ion: I tested inside virtualbox installation with a / and swap partition
[15:13] <Keybuk> no
[15:13] <ion> Ok, no need to test my patches then. I probably should install virtualbox myself and test different partition configurations.
[15:13] <Keybuk> pass= is fairly nonsensical for mountall
[15:13] <ion> Ok
[15:14] <mbiebl> Keybuk: another issue I observed is, that the upgrade of at hangs
[15:15] <mbiebl> The "start at" command in postinst does not complete
[15:15] <mbiebl> so the upgrade process is stuck at this stage
[15:15] <mbiebl> I manually had to kill the start command so the upgrade process could finish
[15:17] <mbiebl> I also remember problems with services that use restart in postinst instead of start/stop (like rsyslog), when the initial upgrade to the upstart job is made
[15:18] <Keybuk> I thought I'd fixed all those issues
[15:18] <Keybuk> it'll complain but not fail the postinst
[15:19] <mbiebl> lemme check again. I set a snapshot in virtualbox, so I can easily test an upgrade again.
[16:55] <mbiebl> Keybuk: looking at the bootchart of the default alpha5 install now
[16:56] <mbiebl> What is this weird couchdb doing. It spawns xulrunner and takes over 5 secs
[16:59] <mbiebl> Keybuk: I think FSCKFIX=no is the default
[16:59] <Keybuk> it is
[17:00] <sadmac2> mbiebl: couchdb wat?
[17:00] <mbiebl> sadmac2: no idea what this is doing
[17:01] <mbiebl> and why this is in a default install
[17:01] <sadmac2> mbiebl: I'd love to know
[17:02] <Md> couchdb is a key-value data storage
[17:02] <Md> I fear that somebody tought it would be a great backend for some desktop application...
[17:02] <mbiebl> Md: why does it need to run xulrunner for that?
[17:02] <Keybuk> I know
[17:02] <Keybuk> I saw that today
[17:03] <Keybuk> BIG SIGH
[17:03] <sadmac2> Md: is it just key-value? last I read up on it I thought it was a bit shinier.
[17:04] <mbiebl> Keybuk: damn, I'm hitting the superblock mount time in the future issue in my virtualbox install
[17:04] <mbiebl> I guess this is also where the new mountall fails
[17:04] <sadmac2> mbiebl: your drive has negative write latency?
[17:05] <Keybuk> hahaha
[17:06] <mbiebl> could this be a ext4 or util-linux bug?
[17:06] <Keybuk> did the new mountall fail properly to a shell
[17:06] <Keybuk> ?
[17:06] <Keybuk> it's a bug in the ext3 and ext4 filesystem code in the kernel
[17:06] <Md> no clue about both issues, since it is written in erlang I stand clear from it
[17:08] <mbiebl> Keybuk: when is it triggered?
[17:08] <mbiebl> I don't seem to encounter it on every boot
[17:09] <sadmac2> Md: something particular against erlang, or just not a λ guy?
[17:10]  * sadmac2 still has haskell on his list of languages to find something to do with.
[17:10] <Keybuk> mbiebl: east of UTC, hardware clock in local time, system powered off without clean unmount
[17:11] <mbiebl> It's the clean unmount that bothers me, because I did a regular shutdown/reboot
[17:11] <Md> sadmac2: I had ejabberd explode puke erlang core dumps on me too many times...
[17:12] <sadmac2> Md: shame. That's supposed to be one of the better jabber servers.
[17:12] <Md> and indeed it is. you figure :-)
[17:12] <Md> (I jave not tried the java ones, but I hate java with a passion)
[17:13] <sadmac2> Md: you're a good man
[17:14] <ion> CouchDB seems awesome and Erlang is awesome. :-P
[17:15] <sadmac2> I'm very drawn to λ programming. I need something to do in ocaml/haskell/erlang
[17:15] <sadmac2> something that isn't such a wacky idea that I'm afraid of dooming it further by writing it in a language people are hostile to by policy
[18:12] <Keybuk> mbiebl: hah, that FSCKFIX is never going to work, is it?
[18:41] <mbiebl> Keybuk: what do you mean, setting it to yes?
[18:41] <Keybuk> no, I mean that if you do FSCKFIX=no it'll still act as if it's yes
[18:43] <mbiebl> dunno if this is the case with the new mountall command
[18:43] <mbiebl> With the old initscripts, it made a difference
[18:44] <Keybuk> huh? :)
[18:44] <Keybuk> I mean the code in /etc/init/mountall.conf
[18:44] <Keybuk> [ -n "$MOUNTALL" ] && fsck_fix="--fsck-fix"
[18:44] <Keybuk> err
[18:44] <Keybuk> [ -n "$FSCKFIX" ] && fsck_fix="--fsck-fix"
[18:44] <Keybuk> is wrong ;)
[18:44] <Keybuk> I just changed it
[18:45] <Keybuk> [ "$FSCKFIX" = "yes" ] && fsck_fix="--fsck-fix"
[18:45] <Keybuk> ;)
[18:45] <mbiebl> ok
[21:25] <sadmac2> Keybuk: I tried to test an upstart build the other day. It didn't grab the dbus name (because I didn't run it as root and left out the upstart.xml file), but moreover I couldn't look at it at all with d-feet. System logs said something about not having permissions to call the introspection methods. Will putting the permissions file in place and running as root miraculously fix this?
[21:40] <mbiebl> Keybuk: found a few other issues: at vs atd
[21:40] <mbiebl> after the upgrade, there is /etc/init.d/atd and /etc/rcS.d/S89atd because the upstart job is called "at"
[21:42] <mbiebl> Directly after the upgrade, this is the list of initctl list: http://paste.debian.net/46172/
[21:44] <mbiebl> As you can see, a few services are not listed as running, like rsyslog, udev or avahi-daemon
[21:44] <mbiebl> interestingly dbus is marked as start/running without a pid
[21:57] <mbiebl> There is also still a symlink /etc/rcS.d/S37udev-finish after the upgrade
[22:01] <mbiebl> on shutdown, I also get the following messages
[22:02] <mbiebl> init: rc main process (2383) stopped by STOP signal
[22:02] <mbiebl> init: rc main process (2383) continued by CONT signal
[22:02] <mbiebl> init: rc main process (2383) stopped by STOP signal
[22:02] <mbiebl> init: rc main process (2383) continued by CONT signal
[22:02] <mbiebl> ...