Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have an old pc which can boot only old USB (small) pens. So unable to boot a modern large live distro.
I found a viable solution to boot a large live distro using the PLP bootloader. I boot into PLP with the small USB pen. Since the bootloader stays in ram, I replace the small pen with the large pen containing the large distro. Then I ask PLP to boot with USB (which now contains the large size pen) and the live distro works.
I would like to do something similar with Syslinux, possibly keeping both the small and large USB pens plugged.
Now I need a way to tell in the syslinux.cfg that the kernel to start is not on same device where syslinux is and the system started. So not sda but sdb.
I try to do this with:
Besides I would like to find documentation about root, boot and similar switches, any ideas.
Can you please describe your PC spec and USB storage spec ( number of MB? format FAT16 or 32? or this is an USB adapter with a card on it?).
I personally have a PC which DONT boot from USB via BIOS setups; so it is probably older than your (97 purchasing date, and BIOS dated 2001).
I experienced that SD-HC cards, or any USB adapters cannot boot on any PC.
If you have a 256MB USB stick or SD card, this is already enough to boot a modern distro: look at www.distrowatch.com for having a distro for old computers (or see my blog).
Changing boot order does not work. As I told, one of the two sticks is unable to boot the system. The strategy is booting with stick A, which is compatible with my BIOS, and then pass control to stick B. To do this both stick are plugged and stick A is plugged in the port that gets enumerated first. Of course, to pass control from A to B I need to manage config syntax of syslinux.
Again my question is always the same:
Do you know how can I specify the linux kernel path including a drive in syslinux config file?
Please do not propose hardware or BIOS tricks, do not suggest light or faster distro, I do not need these. Please, just enlighten me about syslinux config syntax.
This is what I am asking from the very first post and sorry if the content was misleading for you.
Well, this now gets more complex than fixing the original deal.
I think you now want to put in a chain statement to pass the loader off to the sdb and not try to load directly to it.
The reason I think this is that I don't know what the state is when plop and grub meet and your original statement about not being able to boot to this other flash drive. If the other drive were in fact a known working flash install then I think you now need to chain to it.
Typical example of a chain statement.
You have to know what is what on boot. Your grub may have find command.
I might suggest that you repost this and ask about chainloading from a grub to another disk.