[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[stephen@marenka.net: 9.3 Replacing the Rescue Floppy Kernel i386]

Well I wrote this about four months ago and I still haven't gotten it
added to the boot-floppy docs. Would Chris or someone else with SGML 
experience please add it? 



----- Forwarded message from Stephen R Marenka <stephen@marenka.net> -----

Envelope-to: marenks@localhost
Delivery-date: Wed, 15 Aug 2001 13:12:19 -0500
X-Envelope-Sender: marenks@marenka.net
From: Stephen R Marenka <stephen@marenka.net>
To: debian-boot@lists.debian.org
Subject: 9.3 Replacing the Rescue Floppy Kernel i386
Mail-Followup-To: debian-boot@lists.debian.org
Resent-Message-ID: <0puOeD.A.sHF.ukre7@murphy>
Resent-From: debian-boot@lists.debian.org
X-Mailing-List: <debian-boot@lists.debian.org> archive/latest/22567
Resent-Sender: debian-boot-request@lists.debian.org
Resent-Date: Wed, 15 Aug 2001 13:11:49 -0500

I had the opportunity to install from a floppy using a custom kernel and
I wanted to update the documentation to reflect my experience. Before I
mess with SGML, I thought I'd run this by the gurus here and see what
ya'll thought.
This one is for i386.
9.3 Replacing the Rescue Floppy Kernel
Comment on kernel list.
Minix file support is not required, but msdos and ext2 are for i386.
<snip until after the kernel list>
Download a set of boot floppies: root, rescue, and driver disks. You need
to know that ide, idepci, and compact use flavored kernels. One
reason to use the compact set, for instance, is that it has only 1
driver disk and your custom kernel will likely have all the drivers you
need built in. The downside is that it requires an extra manual step
unless you built your custom kernel with the same flavor name (see
make-kpkg in the kernel-package). You may also see some error messages
regarding modules.
Mount the rescue disk image, something like the following.
        mount -t auto -o loop rescue.bin /mnt
Assuming you used /mnt as the mount point, copy your custom kernel
to the file linux on /mnt. Next run the script rdev.sh which resides
on /mnt. The rdev.sh script assumes that the kernel is in the current
directory or /mnt/linux. If not, you should supply the path as an
argument to the script.
If you want to be complete about it, you'll also want to gzip the
System.map from your custom kernel and place it on /mnt as sys_map.gz
and gzip the .config and place it on /mnt as config.gz.
Now you can umount your disk image and burn your floppies.

You will probably want to "Install Kernel and Driver Modules" using the 
floppies you just built to get your custom kernel installed on the hard 
drive. This is why having one driver disk is nice.

If you are using a disk set featuring a flavored kernel, you will need 
to switch to VC2 and hit enter to get a prompt.

Type "ls /target/lib/modules" to see where the driver disk put your 
modules. Then "uname -r" to find out where the modules should be. You'll 
then want to do something suitable like the following.
	mv /target/lib/modules/* /target/lib/modules/`uname -r`

Now you may exit out of the shell and return to VC1. If you didn't 
perform the last step properly, then "Configure Device Drivers" won't 
find any modules and thus will be sad.

I'm sure somebody can explain that better with fewer words, but I think 
it's better than what we have. Thoughts?



Stephen R. Marenka     If life's not fun, you're not doing it right!

----- End forwarded message -----

Stephen R. Marenka     If life's not fun, you're not doing it right!

Attachment: pgpEgPEBMzVJQ.pgp
Description: PGP signature

Reply to: