I checked, one by one, *all* the scripts in /scripts (not only the ones in /scripts/casper-bottom, just to be sure).
Nothing uses any functionality not already present in the initramfs or options not supported by busybox.
What needs commands from /root/ already uses chroot.
To confirm this I also compared two casper.log files from two boots: the first one with the default PATH setting, the latter with all /root/* dirs removed from the PATH (in /scripts/casper). I didn't find any difference or new error.
So PATH= /usr/bin:/usr/sbin:/bin:/sbin is safe and sane.
Tollef, Colin: are you here? What is your opinion?
PS. In the process I discovered an error in casper-bottom/23networking (independent from the PATH issue). At line 30 there is a call to udevtrigger:
udevtrigger -Bpci -Iclass="0x02*"
I don't know what it is supposed to do, but it doesn't work. As also man udevtrigger says, udevtrigger doesn't support any -B or -I options! So it fails.
So we all more or less agree :-)
I checked, one by one, *all* the scripts in /scripts (not only the ones in /scripts/ casper- bottom, just to be sure).
Nothing uses any functionality not already present in the initramfs or options not supported by busybox.
What needs commands from /root/ already uses chroot.
To confirm this I also compared two casper.log files from two boots: the first one with the default PATH setting, the latter with all /root/* dirs removed from the PATH (in /scripts/casper). I didn't find any difference or new error.
So PATH= /usr/bin: /usr/sbin: /bin:/sbin is safe and sane.
Tollef, Colin: are you here? What is your opinion?
PS. In the process I discovered an error in casper- bottom/ 23networking (independent from the PATH issue). At line 30 there is a call to udevtrigger:
udevtrigger -Bpci -Iclass="0x02*"
I don't know what it is supposed to do, but it doesn't work. As also man udevtrigger says, udevtrigger doesn't support any -B or -I options! So it fails.