reverend@xxxxxxxxxxxxx wrote:
> I hoped that it was/it should have been:
>
> dd if=/dev/hda3 bs=64k | /mnt/aespipe -e AES256 -K /mnt/rootkey -gpg -G / | dd of=/dev/hda3 bs=64k conv=notrunc
^^^^
this does not belong here
What version of aespipe did you use?
/mnt/aespipe --version
If it is older than 2.3, then it may have used loop-AES-v2 on-disk format to
encrypt your data.
> maybe dietlibc is not compilable here and is, therefore, killing build-initrd.sh
> and everything.
>
> When I type in (/usr/local/src/dietlibc-0.30) "make", I get enormeus sceens of
> messages which could be all and everything, harmless or serious......
Lots of output from make is normal.
> When I type "install bin-i386/diet /usr/local/bin", only 1 file called
> "diet", 4,9kB, is transported, I don find any other activity and I cannot know
> which files of which size have to be where or are important here.
> I know that should be a wrapper but where are the libs ?
If you follow instructions in dietlibc README, you get a small "diet" binary
that is installed in /usr/local/bin/, 5268 bytes on my box. When that "diet"
program is run, it uses additional files from the place where dietlibc
sources were compiled on, /usr/local/src/dietlibc-0.30/ in your case.
Dietlibc compiled programs are statically linked.
> When I type in
> "make install bin-i386/diet /usr/local/bin",
> ^^^^^
That is not what dietlibc README says.
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
