SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all,
I was reading the post about encrypting a file system and since i had just recently killed my poor pipe smoking penguin i decided to try it. following the instructions on http://slackware.osuosl.org/slackwar...ADME_CRYPT.TXT i found my self booting into nothing but this "L 99 99 99 99 99 99 99 99... for about 50 more" i'm not quite sure where i went wrong, the only thing i can think of is that i have a bad disc and lilo is the part that got corrupted. any ideas? I was encrypting the whole root fs.
Well it still doesn't work, using the new install method with the extra bit at the end i am still getting the error on boot "L 99 99 99 99 99 99..." I am starting to think that this is a corrupted Lilo. just incase however this is what i did.
1. boot huge.s (i've had problems with the smp)
2. cfdisk
3. make a 100mb linux partition /dev/hda1
4. make a 59.5gb Linux partition /dev/hda2
5. make a 400mb Swap parition /dev/hda3
6. write the partition table
7. cryptsetup -s 256 -y luksFormat /dev/hda2
8. cryptsetup luksDump /dev/hda2 (this is mainly to confirm the info)
9. cryptsetup luksOpen /dev/hda2 cryptroot
10. setup
11. Set my root to /dev/mapper/cryptroot ext3
12. set my /boot to /dev/hda1 ext3
13. install slackware
14. make my lilo.conf file
15. install to the root of /dev/mapper/cryptroot
14. mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
mount -o bind /dev /mnt/dev
chroot /mnt
15. mkinitrd -c -k 2.6.21.5 -m ext3 -f ext3 -r cryptroot -C /dev/hda2 -L
16. edit the lilo.conf file
17. point the boot to /dev/hda1
18. add the initrd = initrd.gz to the linux part
19. run 'lilo'
20. reboot
Your mistake is probably that you do not have any OS installed in the MBR of your computer.
The README_CRYPT.TXT is not complete in it's coverage of installation instructions for LILO. MOre information is found on the 'errata' page - you can find its URL on the bottom of the README_CRYPT.TXT.
lilo:
No chainloading going on,
so lilo will be installed to the MBR:
boot = /dev/hda (NOT /dev/hda1)
root = /dev/mapper/cryptroot
finish install.
# echo "cryptroot /dev/hda2" > /mnt/etc/crypttab
(edit: You don't need this. By the time /etc/crypttab is available,
the root partition is already being decrypted.
If other partitions need decrypting, the passphrase (or path to a key-file)
can be placed in /etc/crypttab. Keeps you from entering multiple passwords.
Unless you think this compromises security.)
# mount -o bind /proc /mnt/proc
# mount -o bind /sys /mnt/sys
# mount -o bind /dev /mnt/dev
error here, so: # cp -a /dev/mapper /mnt/dev
# chroot /mnt
Glad its working. But one of those commands wasn't necessary.
You won't need an /etc/crypttab if only the root partition is encrypted.
Doesn't do any harm though.
I stuck a note in post #6.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.