|
From: Dick M. <di...@fo...> - 2010-05-15 08:14:41
|
On 05/14/10 18:25, Heiko Zuerker wrote: > Hey, > > would it help to have multiple boot.xxx scripts? > E.g. boot.mountfs, boot.network, boot.last ? > We would consider those user-scripts, just like the boot.local one. If I understand the OP's problem correctly (which I might not) his problem arises because his spool directory is in ram and so its structure does not persist over reboots. This may be a common difficulty for apps in diskless systems. I think the problem might be resolved by having another script which is run after all disks, logical volumes etc are present but before any apps are started. I think this can be done from a script in /etc/init.d/boot.d similar to boot.local but which is run last. It could be called lateboot.local. One issue that might arise is that the network is not running at this point and hostname has been set to a default value. Setting the hostname to a configured value in localnet may be a way around that. Since such changes reside entirely in /etc a solution like this can be implemented by users on an ad-hoc basis and thus not impact the release of 1.4. Dick |