Hi,
I got problems with loop-aes v1.4h and
util-linux-2.11m . I have read and done everything
that stands in the README of loop-aes v1.4h and
created an encrypted fs of /dev/hdb1 with AES-256.
That seem to work just perfect, thanks alot Jari!
The problem is that I did build new mount, umount,
losetup binaries and they do cause me trouble during
bootup of my RedHat 7.2 Linux box. I get this error
during bootup:
Mounting local filesystems: mount: invalid option -- O
<Here comes usage for mount.>
Then the init pukes ugly messages like "no such file:
/var/lock/subsys/syslog, ipchains, ..." and the
like... after timeouts of like 10 minutes system
finally comes up and I then need to start the services
(like syslog) manually. (The path /var/lock/subsys/ is
correct so I am abit confused with the above
error-messages.)
If I switch to the original binaries of mount, umount,
losetup and reboots the system there are no problems.
But then I need to (ofcourse) switch to the loop-aes
versions of mount, umount, losetup to be able to mount
my encrypted partitions and then it works perfect.
When examing the man-pages of the old and the new
mount I see that the "-O" switch isn't there anymore
so I suppose that is the problem. Any idea how to fix
this? (Not fun to switch binaries during every
reboot).
I think this line in /etc/rc.sysinit causes the
problem:
action $"Mounting local filesystems: " mount -a -t
nonfs,smbfs,ncpfs -O no_netdev
Can I change this line in some way to come away from
the "-O" parameter?
Any help with this would be really nice... :)
Regards,
Friedrisch
_______________________________________________________
http://inbox.excite.com
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
