Bugzilla – Bug 119854
Bootsplash: suboptimal location of /lib/bootsplash/control for diskless clients
Last modified: 2006-03-27 10:07:18 UTC
Hi!! The location of the control pipe for the bootsplash (in /lib/bootsplash) is rather suboptimal for diskless client concepts, because normally /lib would be exported RO via NFS. For some reason on SuSE NFS servers it is allowed on clients to write to that file (odd - then should RO exported devices files on NFS be writeable too - but they aren't ...) - but if I mount the same filesystem structure from a debian NFS server (or some other linux) I get permission denied for that file. So it would be great to have that pipe somewhere in the filesystem which should be writeable because of FSHS like /dev or /var ... Ciao, Dirk
Formerly it was in /var, I had to move it out because it has to work if /var is not yet mounted. So only /dev remains. I have to check with the FHS guys if /dev is ok with them...
OK got the problem! /dev would definitely better :-) and should be available just from the beginning of the boot procedure ... Thanks!! Dirk
Actually the named pipe won't be there if /dev/ is tmpfs and populated by udev...
Yes, but other processes devices have that problem too. There are still modules which do not generate the hint for udev to produce a certain dev entry. I would agree on /tmp too for that pipe. But I think /lib, /usr, /opt or such directories are not meant for such files which should be writeable on the local system ...
Still located in /lib/bootsplash (SuSE 10.1b6) :-((
Yeah, I don't like dev because of udev. How about /etc?
Nah. Will use /dev.
Hi! /etc is much more convenient, but probably not the optimal place, /dev would be fine with me :-)
It's now in /dev (and will hopefilly stay there).