Jochen Hayek wrote:
Ludwig Nussel writes:
LN> Jochen Hayek wrote:
>> I prepare my /etc/crypttab and my /etc/fstab for quite a few different external encrypted disks. >> And I don't attach them all at the same time, esp. not at boot time.
>> /etc/init.d/boot.crypto shouldn't bother attempting to mount disks, >> that are not currently attached. >> [...]
LN> Most current boot.crypto from factory already skips devices that don't exist.
I had installed (upgraded) SUSE Linux 10.3 from CD-ROMs, then I upgraded certain parts from SUSE Factory, and ...
$ rpm --query -f /etc/init.d/boot.crypto aaa_base-10.1-41
In aaa_base-10.3-29.i586.rpm (currently on SUSE Factory) :
$ rpm2cpio aaa_base-10.3-29.i586.rpm | cpio -tv | fgrep crypt 630 blocks -rw-r--r-- 1 root root 1232 Apr 27 17:31 ./var/adm/fillup-templates/sysconfig.boot.crypto
1st: I find it a little risky to upgrade esp. aaa_base.
2nd: I cannot find boot.crypto in that package, so I cannot verify, what you're saying, and I would at least like to have a look at the new code in boot.crypto.
boot.crypto is now in the util-linux-crypto package as it entirely depends on cryptsetup. You also need to upgrade the kernel, the 10.2 one does not support the on disk format you need via dm-crypt. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE Labs V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org