LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-29-2008, 09:37 AM   #1
-kc-
LQ Newbie
 
Registered: Jun 2007
Distribution: Slackware
Posts: 21

Rep: Reputation: 15
Question Need clarification on encrypted root filesystem


I didn't get any reply from the address in README_CRYPT.TXT, then I'll try here...

The errata for Slackware 12.0 README_CRYPT.TXT (http://alien.slackbook.org/dokuwiki/...e:setup#errata) mention the missing command:
Code:
# mount -o bind /dev /mnt/dev
I had the same problem in Slackware 12.1 and 12.2 (no LVM) but the updated README_CRYPT.TXT doesn't say anything about it.

I can see that the Slackware 12.1 and 12.2 installer mount /sys and /proc, but it doesn't seem to mount /dev, am I missing something?

I've never been able to mount /dev anyway, so I'd suggest to do this instead of just "lilo":
Code:
# exit    #from the "chroot /mnt"
# lilo -C /mnt/etc/lilo.conf
(/boot is a symlink to /mnt/boot, the only thing out of place would be lilo.conf, requiring the -C option)


A couple of notes about README_CRYPT.TXT, "Encrypted root filesystem" section:
Quote:
When the LILO configuration pops up, tell lilo
that your root partition is '/dev/mapper/cryptroot'. Lilo will try to
install and fail, and will tell you so.
The expert lilo.conf setup menu actually asks for two devices: the root partition (root=) and the location to install the LILO boot block (boot=).
For the latter I assume I have to enter the correct location, in my case /dev/hda (the field was already filled correctly).
Quote:
Look up the line that says "boot = /dev/mapper/cryptroot"
which is the device for your root partition and which was the reason for
lilo failing to install.
That line shouldn't need fixing, as long as you answered correctly to liloconfig.
The reason for lilo failing to install in the setup is the line that says: "root = /dev/mapper/cryptroot", since liloconfig does a "lilo -r /mnt" (chroot to /mnt before doing anything else) and you get:
Code:
Fatal: Illegal 'root' specification: /dev/mapper/cryptroot
Thanks to all who worked on encrypted partition support for Slackware, it solved me a lot of problems!
-kc-
 
Old 12-29-2008, 02:00 PM   #2
bapigoo9
Member
 
Registered: Aug 2008
Posts: 107

Rep: Reputation: 16
Would you clarify what your questions are and what you are trying to do? I have Slackware 12.1 and many use Slackware here in LQ. Are you just commenting on Slackware or do you have questions and want help?
 
Old 12-29-2008, 06:04 PM   #3
-kc-
LQ Newbie
 
Registered: Jun 2007
Distribution: Slackware
Posts: 21

Original Poster
Rep: Reputation: 15
Hi, thanks for your reply!
Sorry for not being clear, I can't express myself in English very well.

What I'm trying to do is to install Slackware on an encrypted root partition (without LVM), following the relevant section of README_CRYPT.TXT.

The problem I encounter is that LILO fail because it can't find /dev/mapper/cryptroot inside of the chroot (as mentioned here: http://alien.slackbook.org/dokuwiki/...e:setup#errata)

It was no big deal, I suggested a solution in my previous post, and you can find another one in the old errata from the link above.

My question is: how can the procedure in README_CRYPT.TXT ever succeed if we install LILO inside a "chroot /mnt" and the root partition device is outside /mnt?
I'd like to either find the answer or have README_CRYPT.TXT fixed.

The rest was just a comment, maybe a suggestion to the author to phrase that bit differently to be more precise, but not a cause of problems.
 
Old 01-11-2009, 03:19 PM   #4
bapigoo9
Member
 
Registered: Aug 2008
Posts: 107

Rep: Reputation: 16
Grub works. There is a readme in the iso file for the installtion dvd, if you have that. It is probably in the installation cds as well. What you need to do is to install per those directions, and then to install Grub. Be sure that you create the initrd as described, and then edit your menu.lst file to use that initrd. Without the initrd made for the encrypted system, you will not be able to boot into it. Post if you get stuck. It may take awhile for me to respond...if nobody else does.
 
Old 01-21-2009, 08:14 PM   #5
-kc-
LQ Newbie
 
Registered: Jun 2007
Distribution: Slackware
Posts: 21

Original Poster
Rep: Reputation: 15
Hi, thanks again!
Sorry for wasting your time but I failed to explain myself again...

The practical problem was solved before I started this thread.
You can see how I did it in the top post.
I was quick to fix it for the third time! I had the same problem with Slackware 12.0 and 12.1.

The purpose of this thread was to let the Slackware team know that README_CRYPT.TXT *need to be fixed*, since they ignored my emails
OR
find out how the procedure in README_CRYPT.TXT can ever succeed without the fix and without GRUB.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Encrypted Root Filesystem (dm-crypt/loopAES +ext3fs) - Problem dragoncity99 Slackware 6 08-01-2005 12:14 AM
encrypted filesystem done -now what? randomx Linux - Security 1 04-27-2005 06:13 AM
Encrypted Root Filesystem HOWTO and /dev filesystem tmillard Linux From Scratch 0 10-18-2004 03:58 PM
encrypted virtual filesystem EdoardoC Linux - Security 6 04-19-2004 10:16 AM
8.1 install: encrypted root ext3 filesystem Snailer Slackware 1 10-01-2002 03:48 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:54 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration