Small linux distribution for system rescue on FAT filesystem
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Small linux distribution for system rescue on FAT filesystem
Here's my dilemma:
I have a laptop with a minimal (~0.5 G FAT partition). The FAT partition contains DOS 7 (from Windows 98) that comes with the laptop as well as hibernate file for saving the system memory on APM suspend. I'm looking for a small Linux distribution (<50 MB) that would fit in the space available on the FAT system. I wouldn't want to go tampering with the partitions, so I need something that can work on a FAT filesystem. The idea is to have a little rescue linux available on the FAT partition in case I ever mess up my primary partition.
Right now I'm using BGRescue which is perfect otherwise, but It's lacking PPP and PPPoE which I really would like to be there.
Any distribution recommendations or other solutions?
--edit--
Oh, yes, I've tried DSL, but is there any way to have it installed on FAT partition? I really wouldn't want to depend on a boot CD.
How about Puppy. It will certainly do it in Fat partition but I cannot be sure of fitting within 50Mb. I would put it in a pendrive or simply use a LiveCD and forget about the 50Mb limitation.
Yes, I know it does, but can it be run from a FAT partition instead of CDROM? It has a "tohd" (or something like that) boot option, that copies it to HD, but making it start is still not possible without the CD.
Puppy works, but doesn't include LILO which is one of the tools I definitely need on my rescue system.
My main distro boots with lilo, so that's why I'd like to have it available on my rescue system too (to be able to re-install it if something goes wrong). I've heard a lot of "not-so-good" comments about Grub, so I don't think I'm going to convert my main system to it.
I can confirm that if you use Lilo as the controlling boot loader then the type of bootloader of any other Linux doesn't really matter.
If you have Grub in a Linux say hda5 and wish it to be booted by Lilo all you need is to do is to tell that Linux's Grub to replicate its boot loader inside its root partition hda5 with a command
Code:
grub-install /dev/hda5
Thereafter in the /etc/lilo.conf of the booting Linux you can fire up the Linux in hda5 by Lilo commands
Code:
other=/dev/hda5
label=Linux_in_hda5
The only difference if hda5 uses Lilo instead of Grub then instead of
Code:
grub-install /dev/hda5
you use
Code:
lilo -b /dev/hda5
So what is the big deal?
I am not here to popularise Grub but my experience is that Grub is far more easier and powerful than Lilo and I have documented 5 findings in Section E of the second last link in my signature. 4 out of the 5 findings are advantages that Lilo cannot match.
I am not here to popularise Grub but my experience is that Grub is far more easier and powerful than Lilo and I have documented 5 findings in Section E of the second last link in my signature. 4 out of the 5 findings are advantages that Lilo cannot match.
The big deal is you're missing the point My rescue system will boot up with loadlin because it gets started from the dos prompt. The reason I want lilo to be there is to fix the booting of my system in case it ever goes wrong. I don't really care about grubs advantages over lilo (or vice versa for that matter), my system just happens to boot up with lilo, so that's what I need.
I'll give you an example: Recently I upgraded my kernel and forgot to run lilo before rebooting the machine. Result: Linux doesn't boot. Now if I had had a rescue system with lilo on my dos partition (like I do now) I could have just booted to dos, boot the rescue system and run lilo with the correct lilo.conf to have it working again.
Of many methods of rescuing an unbootable Linux I investigated I now come down on just two universal tools (1) A LiveCD and (2) a bootable Grub floopy (can turn into a CD).
Anything you can do with your rescue system, which I suspect is a Loadin-based as it is an old Dos-based boot loader used in the past, is now superseded by the LiveCD. A LiveCD can restore any Lilo or Grub based distro.
There is no PC system that I know of that cannot be booted by a Grub floppy, including any MS system, any BSD and of course any Linux even it used Lilo originally.
You can stick with your rescue system disk but things have moved on.
My earlier point is Linux boot loaders are interchangeable mutually supporting each other. Users using one and afraid of the other is mainly due to a lack of experience on both systems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.