[12:27] #define HAVE_SYS_INOTIFY_H 1 is in config.h. I'm out of ideas. maybe you can see a problem in the patch here: http://bugs.uclibc.org/view.php?id=917 ? [12:47] you need the functions in your uclibc as well as the headers [12:55] the kernel headers are in place,too. [01:00] yeah, you still need the stub functions though [01:00] the header declares the existance of the function, but not the function [01:01] you can probably just copy the syscall stuff into a header and inline it [01:01] like the nih/inotify.h thing does [01:02] hmm. I hardly understood what you said. but I'll have a look at nih/inotify.h [01:06] ok looking at it didn't give me any clue. === mbiebl [n=michael@e180068028.adsl.alicedsl.de] has joined #upstart === Starting logfile irclogs/upstart.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #upstart === Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo === Topic (#upstart): set by Md at Sun May 6 19:59:46 2007 === Md [i=md@freenode/staff/md] has joined #upstart === Keybuk [n=scott@quest.netsplit.com] has joined #upstart === juergbi [n=juerg@80-219-19-101.dclient.hispeed.ch] has joined #upstart === |Lupin| [n=seb@zen.loria.fr] has joined #upstart [03:28] <|Lupin|> Hello, everybody [03:30] <|Lupin|> I am joinning the chan because it looks like upstart does not log the bot messages in /var/lob/boot, I am wondering why... === tale [n=tale@207.235.54.1] has joined #upstart [03:47] |Lupin|: we had some last-minute issues with logd [03:47] it turns out that when it isn't running, processes that try to output to stdout die [03:48] ie. the shell running the shutdown scripts [03:51] <|Lupin|> so ? [03:52] <|Lupin|> Actually there is a file called /etc/event.d/logd [03:52] <|Lupin|> it contains a line saying [03:52] <|Lupin|> console output [03:53] <|Lupin|> Does one have to change this line to have hte output redirected to a file rather than to the console ? [03:53] <|Lupin|> More in general, I can't find any documentation about the synta of the files under /etc/event.d [03:55] the console X line does indeed set where the input/output of a job goes; you set jobs to "console logged" to have them use logd, except this is disabled in the code [03:55] the lack of documentation is semi-deliberate, since the syntax isn't stable yet [03:58] <|Lupin|> ok [03:59] <|Lupin|> Keybuk: In fact what I would really like is to be able to have everything appearing on the screen at boot gathered in a file so that I can read it. Is this possible ? [04:23] <|Lupin|> Or perhaps would it be more simple to switch back to sysvinit ? [04:24] there's various interesting ways to do that [04:25] the logd trick is to set the console to a set of sockets that are intercepted by a daemon [04:25] the disadvantage is obviously that without the daemon, the trick doesn't work [04:25] an alternate trick is to use TIOCCONS to capture "console output" [04:25] the disadvantage to that is that you don't know which service is doing the output [04:27] <|Lupin|> Keybuk: oh indeed the daemon is not installed... [04:27] (the other disadvantage to the logd trick is that with ordinary sockets, you don't have a tty, which can adjust the behaviour) [04:27] <|Lupin|> Keybuk: I think I don't mind loosing the name of the service, as a temporary solution. But how can this solution be implemented, concretely, please ? [04:28] there's not an easy answer available right now [04:28] <|Lupin|> Hmm... [04:28] it turns out to be a more difficult problem [04:28] <|Lupin|> If the system remains in text mode, will I be able to rean the console with shift-pagep / shift-page-down ? [04:30] yes [04:31] you're obviously relying on the kernel ring-buffer size there === wasabi_ [n=jhaltom@ubuntu/member/wasabi] has joined #upstart [04:34] <|Lupin|> yes [04:35] <|Lupin|> I am wondering how I can keep the system in text mode.. ? [04:37] <|Lupin|> is it a matter of runlevel ? [04:49] <|Lupin|> I believed so, but runlevels 2, 3, 4 and 5 seem to run gdm... [04:54] remove gdm symlinks from one of the runlevels [04:58] <|Lupin|> is it all I have to do ? okay. === phoenix24 [n=phoenix2@59.176.11.215] has joined #upstart [05:45] <|Lupin|> it worked, thantks [06:21] <|Lupin|> bye every body [06:21] <|Lupin|> thanks a lot for your assistance === |Lupin| [n=seb@zen.loria.fr] has left #upstart [] === jonib1 [n=jonas@ua-83-227-144-18.cust.bredbandsbolaget.se] has joined #upstart === quitte [n=quitte@stgt-d9bebb70.pool.mediaWays.net] has joined #upstart [06:56] hi. is it possible that my problems compiling upstart using uclibc are related to the kernel being 2.6.13? that's the release that inotify was introduced. [06:56] quitte, yes, you need a recent kernel [06:56] :( ok. so it'S impossible to use it on a fritzbox without loosing support for the proprietary modules [06:56] Upstart works best when you have the most event support from the kernel [06:57] since if you're interested in an event-based init daemon, you're kinda inherently interested in the events to base it off [06:57] the kernel's uevent interface didn't reach maturity until about 2.6.17 [06:57] yeah, it's better to have the uevent support for udev which was introduced in .17 IIRC [06:58] ok i see. so i'd best stick with busybox init for now. maybe the vendor will update the kernel version someday, but i doubt it. === cortana [n=sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk] has joined #upstart === Starting logfile irclogs/upstart.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #upstart === Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo === Topic (#upstart): set by Md at Sun May 6 19:59:46 2007 === Md [i=md@freenode/staff/md] has joined #upstart === jonib1 [n=jonas@ua-83-227-144-18.cust.bredbandsbolaget.se] has left #upstart []