Using the tool mkbootdisk will take your kernel that your system is running with and make a floppy that will boot to your Linux system that is installed. You need this when some thing trashes your MBR and your boot loader will not you back into your Linux system.
I do not know what TOMSRTBT is. Do you have a URL for it?
On Tue, 2003-01-21 at 08:47, J. Rafael Sánchez wrote:
I've read a couple of messages relating to this topic. Even though it sounds interesting, I'm not sure if I understand it completely. What is the diff between what's discussed here and a 'boot-disk' that is created at installation time or by running the "mkbootdisk -device /dev/fd0 kernel-version"? (i'm entirely sure if this is the exact command). What is the importance of the 'boot-root-floopy' option? I've also read a bit about "TOMSRTBT". What is it relationship to the discussion here? Thanks for your explanations in advance. Rafael. ----- Original Message ----- From: "HJ Hornbeck" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 20, 2003 10:07 PM Subject: Re: (clug-talk) Boot root floppy creation problems. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Roy Souther wrote: > | Does anyone have a boot root floppy image that does not use LILO or > | SysLinux? > > There's always GRUB. More flexible than either but bigger. > > | Does anyone know if the How-To works for 2.4 kernels? > > Not personally. This article implies that it does, though: > > http://www.linuxgazette.com/issue73/mwaikambo.html > > Have you tried making a boot+root combo, using rdev to tell the kernel > that the root is on another floppy? It should be easier to troubleshoot. > See Section 6.3 of your FAQ. > > | Does anyone have an explanation as to why the How-To does not talk about > | how to use initrd? > > An initrd is created by the boot loader before it loads the kernel, I > believe. The kernel itself has no way of loading an initrd; your only > choice is a root image loaded into a ramdisk in this case. > > | The How-To only shows the use of gzip for creating root images. Is there > | anything special that needs to be done to use a bzip2 compressed image? > > The kernel would need the bzip2 decompression routines patched into it. > One or two people have done it, and I've seen it in TOMSRTBT, but it's > not a stock option. > > That reminds me. I think recent kernels have made the gzip routines an > option. Did you compile them in? > > | Would I have better luck if I did this from a 2.2 Linux system? > > My Magic 8-ball says probably. I haven't tried, though, so I'm not sure. > > | I am not expecting anyone to solve this problems for me. With todays > | great tools that come with the newest distributions this may seem like a > | waste of time but I have a curious nature and I need to know how this > | works. Most boot root images use LILO or SysLinux. I would like to find > | a working boot root image that does not use these. > > TOMSRTBT: http://www.toms.net/rb/ > Maybe RIP/Zdisk as well: > http://www.tux.org/pub/people/kent-robotti/looplinux/rip/ > > HJ Hornbeck > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQE+LNWqbYQU8p5saQIRAv2eAKCWBgFxpj1AdKaXfylK7zeZQWLq7gCfcX9Q > hlh+CIXdlPsn+MVhQe9DfsI= > =y7SD > -----END PGP SIGNATURE-----
|
Roy Souther www.SiliconTao.com Changing the way people do business. |
signature.asc
Description: This is a digitally signed message part
