[09:58] <AlexExtreme> hmm, in ubuntu, does usplash get started by the initramfs or is it started by the init scripts?
[09:59] <_ion> It's started ASAP from initramfs.
[09:59] <AlexExtreme> thought so
[10:03] <AlexExtreme> btw _ion, did you get anywhere with your event based mounting ideas?
[10:04] <_ion> I haven't yet got around to implementing any of that.
[10:04] <AlexExtreme> k
[09:04] <mbiebl> Keybuk: hi
[09:44] <Keybuk> hey
[09:55] <mbiebl> I noticed when I symlink an upstart job file into /etc/event.d, upstart does not recognize when the file is changed.
[09:55] <Keybuk> right
[09:55] <mbiebl> Is that a limitation of inotify?
[09:55] <Keybuk> or a feature
[09:56] <Keybuk> more a filesystem limitation
[09:56] <Keybuk> since when changing a file, one would have to search the entire disk for symlinks to it, in order to update their directory entries
[09:57] <mbiebl> why that?
[09:57] <Keybuk> because the alternative would be every time you make a symlink, storing a back link somewhere in the linked-to file's inode
[09:58] <Keybuk> and that simply doesn't work with relative symlinks ;)
[09:58] <Keybuk> since they can be on filesystems that can be mounted anywhere
[09:58] <Keybuk> thus refer to different paths
[09:58] <Keybuk> (not to mention that it wouldn't work with cross-filesystem symlinks)
[09:59] <mbiebl> Hm, maybe I don't get it. If /etc/event.d/foo is a symlink to /lib/upstart/foo, why would you have to store a back link?
[09:59] <Md> the solution would be to use inotify on each symlink in the directory. may or may not be worth the effort (see the debian-devel thread about udev and the same problem)
[10:01] <Keybuk> because upstart watches /etc/event.d for changes
[10:01] <Keybuk> and changing /lib/upstart/foo doesn't change that directory
[10:01] <Keybuk> it changes the /lib/upstart directory
[10:01] <Keybuk> and there's nothing there telling the filesystem that there's a symlink in the /etc/event.d directory and you might want to touch that too
[10:01] <Keybuk> personally I think it's a feature, since it means you can have a set of files that are explicitly *not* watched
[10:02] <mbiebl> I guess, you're right