Hi,
I don't see your problem. If you do have encrypted root or other filesystems which are mounted during the boot process, then they are usually mounted in a verly early phase. A local bootscript is usually the last startup script in the boot phase. This requires for example, that all potential volumes are already mounted. If you do not want your dm-crypt volumes to be mounted during the bootphase, then just tell your crypto-device-config (depends on distribution) not to do. Could you please be a bit more verbose? - What is your _exact_ problem? - Which distribution do you use? - What do you want to achieve? Regards Ralf On 06/05/2015 11:29 PM, Angel Dimitrov wrote: Hello, |
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt