Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
When selecting whether to boot linux from a USB drive, CDROM, or SATA drive it looks like I have to take 2 (or more) routes:
1. Learn how to create an Initrd image and incorporate it into my GRUB configuration
2. Learn how to boot with ISOLINUX
Before I jump into those guides which seem as big as the LFS guide, can anyone tell me if there is any simple solution?
I've booted my LFS (or should I say GRUB only) on a USB drive and it generates an error when mounting "root=" claiming my USB drive /dev/sdb1 couldn't be found. I get a list of "available" partitions which are all of the /dev/sda* persuasion, and thus, the local computer drive (which I do not want to set as root)
I guess it's not as simple as setting root=/dev/sdb1 or somehow inserting a script to mount /dev/sdb1 before that line is called?
there may be more than one solution such as compiling a kernel with usb BUILTIN instead of modules, but I am wondering if you understood that when you built your usb system....you were likely to have booted from hard drive so sdb for usb was reasonable.
When you change boot order to usb....it should be sda1....try it and see what happens
2) usb devices also need time to settle....does LFS have a boot code like TC which is waitusb=number
---------- Post added 23-08-11 at 20:16 ----------
hi
there may be more than one solution such as compiling a kernel with usb BUILTIN instead of modules, but I am wondering if you understood that when you built your usb system....you were likely to have booted from hard drive so sdb for usb was reasonable.
When you change boot order to usb....it should be sda1....try it and see what happens
2) usb devices also need time to settle....does LFS have a boot code like TC which is waitusb=number
there may be more than one solution such as compiling a kernel with usb BUILTIN instead of modules, but I am wondering if you understood that when you built your usb system....you were likely to have booted from hard drive so sdb for usb was reasonable.
When you change boot order to usb....it should be sda1....try it and see what happens
2) usb devices also need time to settle....does LFS have a boot code like TC which is waitusb=number
---------- Post added 23-08-11 at 20:16 ----------
hi
there may be more than one solution such as compiling a kernel with usb BUILTIN instead of modules, but I am wondering if you understood that when you built your usb system....you were likely to have booted from hard drive so sdb for usb was reasonable.
When you change boot order to usb....it should be sda1....try it and see what happens
2) usb devices also need time to settle....does LFS have a boot code like TC which is waitusb=number
I'll give this a shot soon and post results. Thanks for the suggestions
Following the GRUB instructions I run the grub-mkrescue and get: genisoimage: command not found
So finding that genisoimage is in a package called cdrkit, I try to get cdrkit. I've only found it in RPM format.
BLFS guide (current) recommends using a rpm2targz converter, I ran into some dependency problems and other such things so I took up trying to install RPM on a fresh LFS 6.3 install in order to install the cdrkit for GRUB.
I'm going to start a separate thread for RPM installing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.