[DEP-BLOAT] 'mkinitrd' ships 'nash' and requires lot of low-level stuff
enrico.scholz at informatik.tu-chemnitz.de
Mon Aug 21 11:14:26 UTC 2006
arjan at fenrus.demon.nl (Arjan van de Ven) writes:
>> 'nash' and this deps are used for different purposes:
>> * 'nash' is called by 'initscripts' during every boot
> it is ??
$ rpm -qR initscripts | grep nash
$ grep nash /etc/rc.d/rc.sysinit
killall nash-hotplug >/dev/null 2>&1
echo "raidautorun /dev/md0" | nash --quiet
echo "mkdmnod" | /sbin/nash --quiet >/dev/null 2>&1
>> * the low-level stuff is used during kernel upgrade only
> actually they are used at each boot as well, just from the initrd
yes; but a copy is used. Not the file from the current 'mkinitrd'
>> Therefore, they should be packaged separately.
> why? Both are going to be mandatory anyway.... mkinitrd is when you want
> to be able to upgrade kernels, or build your own or ...
* chroot environments do not need this
- a program ('nash' in this case) is used by other packages ('initscripts')
- this program does not require rest of the package (generate-initrd
- the rest of the package adds lot of dependencies (device-mapper,
dmraid, ...) which are not needed for the program
then it is a good packaging style to provide both parts in separate
More information about the devel