Am Dienstag, den 22.02.2005, 19:10 +0100 schrieb Wesley W. Terpstra: > On Tue, Feb 22, 2005 at 05:48:50PM +0100, [EMAIL PROTECTED] wrote: > > There is also a second problem thru the early initializing of the crypt > > device for the swap space. /etc/init.d/cryptdisk (package> cryptsetup) > > find a running crypt device and don't call mkswap and the system runs > > without swapspace. > > I don't understand what you mean here, could you clarify?
The crypt device initialized by the initrd will not processes by /etc/init.d/cryptdisk. This often is OK. But in combination of crypted swap devices with random pass phrases, the device have to processes by cryptdisk to create a new swap signatur and add it as swap space. Best solution IMHO: Don't let the initrd initialize crypted swap devices and also all devices with pass phrases from /dev/random and /dev/urandom. Greetings Carsten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
