* maximilian attems <m...@stro.at> [20090622 13:54]: > On Mon, Jun 22, 2009 at 10:47:28AM +0200, Michael Prokop wrote:
> > When using MODULES=netboot there are udev rules included in the > > initrd like /etc/udev/rules.d/70-persistent-net.rules and > > /etc/udev/rules.d/70-persistent-cd.rules - which usually doesn't > > make any sense. > > I'm aware that this is deriving from udev's extra/initramfs.hook > > though I'd like to discuss what's the best way to get rid of > > persistent files in the initrd. > > Something like a "delete persistent infos" feature for initrd > > generation would be nice. Building generic initrds works if the > > currently running system doesn't have udev running but on a live > > system building a generic initrd isn't 100% reliable. > > What about providing a file /etc/initramfs-tools/conf.d/blacklist > > which provides a list of files that should not be included in the > > initrd (not enabled by default but just when using BLACKLIST=y in > > /etc/initramfs-tools/initramfs.conf)? > this should be best fixed in the udev hook script itself. Hm. This would have the disadvantage that every package that wants to be part of the "delete persistent infos" feature would have to add according checks in its file(s) instead of providing a central place via initramfs-tools. > but doesn't sound easy as i can see cases of netboot method, > where you clearly want persistent device naming. That's why I was thinking about adding support for BLACKLIST=y through /etc/initramfs-tools/initramfs.conf. As long as one doesn't explicitly enable BLACKLIST=y the behaviour is exactly as it was before. On the other hand everone suffering from the persistent files problem can get easily rid of it. regards, -mika-
signature.asc
Description: Digital signature
