dir for initrd progs

Elan Ruusamäe glen at pld-linux.org
Fri Mar 20 17:06:07 CET 2009


On Friday 20 March 2009 16:47:01 Jan Rekorajski wrote:
> On Fri, 20 Mar 2009, Elan Ruusamäe wrote:
> > On Sunday 27 April 2008 12:15:29 Elan Ruusamäe wrote:
> > > how about putting programs that were compiled to be put to initrd into
> > > own dir instead of filling up /sbin with them?
> > >
> > > %{_libdir}/initrd
> >
> > i'm still +1 for this.
> >
> > we would use just for binaries nothing %config is placed there.
>
> I thought about it and /{%lib}/initrd may be a better place for this.
> Just one question - does geninitrd require programs from /usr/bin?
> Because if geninitrd does not need /usr then we should not make new
> dependency. And /usr may not be mounted (for any reason) when geninitrd
> is run.
yes, the tools it uses to detect code are not the same progs it put to initrd.

$ grep -c /usr/ /sbin/geninitrd /lib/geninitrd/*
/sbin/geninitrd:18
/lib/geninitrd/functions:0
/lib/geninitrd/mod-dmraid.sh:0
/lib/geninitrd/mod-ide.sh:3
/lib/geninitrd/mod-luks.sh:0
/lib/geninitrd/mod-lvm.sh:0
/lib/geninitrd/mod-multipath.sh:0

> Janek

-- 
glen


More information about the pld-devel-en mailing list