Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
I'm currently in a situation where need to travel, can't take my laptop, but can access information if it's on an external USB drive.
Given this, I'd like to have full Slackware installation on this removable drive, encrypted with LUKS using LVM.
Problem is, I have no experience doing a Slackware installation on a removable drive that'll work *reasonably well* with all hardware. Specifically, I don't know how to make the boot manager recognize the drive to boot from every time. If I'm on a different machine, the name of the drive will vary (sda1, sdb1, something else entirely).
Please advise. Would be much obliged for specific details on how to configure the boot manager, be it LILO or GRUB, or something else.
I don't have much experience with this, but the following two things come to mind:
1. Make a non-encrypted boot partition on the external drive with it's own boot loader { Grub, Lilo};
this would be the simplest way as the host machine would only need it's Bios boot-sequence altered to pass control
to the external drive.
2. Assuming your host systems are all linux and you have admin acces to them, you could specify an entry into their
boot loader , looking for the external (fully encrypted) drive by it's udev id, I think. But , as said above, since I have very limited
experience with this, that is no more than a assumption. Someone with more experience might help you with that.
My best bet would be the first option , if that is possible in your circumstances,
ie having a non-encrypted boot partition and point the host Bios to it.
Hi,
1. Make a non-encrypted boot partition on the external drive with it's own boot loader { Grub, Lilo};
this would be the simplest way as the host machine would only need it's Bios boot-sequence altered to pass control
to the external drive.
Exactly, I'm planning on installing the boot loader to the MBR of the USB HD, and changing the boot sequence of the computer to boot from USB first
The problem would be that I don't know how to tell {LILO/Grub/etc} where to look for the drive. Assuming that the target PC has 2 SATA drives, the my root would be in sdc, no SATA or SCSI, and it would be in sda ...
After that bit of detail, it *should* all work like a normal installation (I think :P).
If you use grub, you can boot without a menu and type in commands interactively. Awkward, but you ought to be able to specify the proper drive by typing root ( and using the tab key to identify drives on that particular machine, or using find (at the grub prompt) to find your kernel and initrd files. Then you type kernel (hdX,X) your file, initrd (etc.etc), splashimage (if you have one and want to bother) and finally type boot.
Or you could have a really big menu with every possible drive spec you are likely to encounter and pick one that works. If there's only a few options, e.g. sda1, sdb1, hda1, that might be easiest.
Hope that helps
Last edited by mostlyharmless; 06-24-2008 at 02:38 PM.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
I don't know if GRUB can work with the rather new identifiers in /dev/disk/*. If it can handle /dev/disk/by-UUID then it should always find your disk and boot partition.
I don't know if GRUB can work with the rather new identifiers in /dev/disk/*. If it can handle /dev/disk/by-UUID then it should always find your disk and boot partition.
Hrm, looks like GRUB can use UUID to select the disk, I'll report back later on my experience.
I don't know if GRUB can work with the rather new identifiers in /dev/disk/*. If it can handle /dev/disk/by-UUID then it should always find your disk and boot partition.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.