[08:45] anyone knows why 'tail -f /var/log/syslog' doesnt work on a live cd ? by "doesn't work" I mean that data appended to the file is not displayed. [08:46] and with any file, not only syslog of course. [09:02] jibel: broken inotify support in overlayfs I think [09:02] kernel bug [09:03] thanks, will report [09:14] I thought that was known ... [09:14] * cjwatson checks [09:14] yes, bug 882147 [09:14] Launchpad bug 882147 in linux "overlayfs does not implement inotify interfaces correctly" [Medium,Triaged] https://launchpad.net/bugs/882147 [09:24] ah thanks for the link. I'll use another method to collect the logs. === shadeslayer_ is now known as shadeslayer [16:42] jibel: the ugly "watch tail -n 60 /var/log/syslog" works pretty well here (adjusting -n depending on screen size obviously) [16:47] stgraber, not in that case. I used it to collect syslog of the automated testing and redirect the output to ttyS0 [16:49] stgraber, I changed it to modifying the configuration of rsyslog to write to ttyS0 with a casper hook and I'm now also redirecting the console. [16:49] ah yeah, won't work too well in your case indeed [16:49] this way we collect boot and shutdown messages. [16:49] cool [16:53] stgraber, now I need to upgrade the grub entry and rsyslog conf after installation in order to keep collecting information after reboot for post-installation tests. [16:53] s/upgrade/update [16:55] https://help.ubuntu.com/11.10/installation-guide/i386/preseed-advanced.html says "... but still have the question asked" [16:55] "d-i preseed/late_command seen false" doesn't seem to be working for me. [16:56] CarlFK: that question is *never* asked [16:56] cjwatson: k - i figured it was something like that. [16:56] 'seen false' doesn't magically create a place where never-asked questions are asked [16:56] it merely inhibits the normal way that preseeding prevents questions from being asked [16:57] I can't imagine any realistic value in asking preseed/late_command [16:58] in other words, all 'seen false' does is restore the state of affairs to if you hadn't preseeded that question at all, except presumably you've given the question some different default [16:58] I was trying to use it to figure out why my late_command was failing [16:59] "set -x; " at the start and then watch syslog [16:59] ... is what I'd do [17:02] d-i preseed/late_command string set -e && chroot /target apt-get install --force-yes --assume-yes squid-deb-proxy-client [17:02] apparently one of the scripts errors [17:03] and the -e bubbles it up - otherwise it is ignorred, and all seems to work ok anyway. [17:03] i guess that should that be reported against squid-deb-proxy-client [17:30] CarlFK: 'set -e' only has any effect at all in the shell you run it in; in the example you just gave it's a no-op, because the shell would exit after the second command anyway [17:32] cjwatson: that will halt the install - so i guess the shell exits with an error code [17:32] remove the -e, and the install doesn't halt [17:32] which is reasonable behavior [17:34] the shell should exit with an error code if its last command exits non-zero *anyway* [17:34] $ sh -c 'true; false'; echo $? [17:34] 1 [17:35] good point. I will swear I needed the -e. easy to test... just takes 20 min [20:19] ev, hi. how do I make ubiquity-frontend run on first boot? (is there something like oem-config-prepare I need to run in the image build chroot?) [20:19] gtk [20:19] kyleN install ubiquity-frontend-gtk in the image and put maybe-ubiquity in the kernel command line [20:20] ev, will do. thx === CarlFK1 is now known as CarlFK