[ale] Quick question about HD and LILO
Zhongbin Yu " <zyu at tc.net>
Zhongbin Yu " <zyu at tc.net>
Thu Jun 10 19:31:02 EDT 1999
$0.02
after making sym links to fool lilo, the other way is to do the following
after mount as Jim said at /mnt/hda5
cd /mnt/hda5 && chroot .
after this, you can issue lilo to redo the bootloader as you will do with
an ordiinary boot-up. It worked for me everytime.
Thanks.
Jerry Yu
----------------------------------------------------------------------------
Systems Engineer | zyu at tc.net
Premiere Technologies | 404-262-8544(O) 1-800-979-1105 (P)
Atlanta, GA 30326 | ae.tc.net/dept/engineering/op/public/developer/zyu
On Thu, 10 Jun 1999, Jim Kinney wrote:
#The drives are labeled as follows:
#Ist primary=/dev/hda
#any partitions are hda1, hda2, etc
#the second drive on the primary is /dev/hdb
#The first drive on the secondary is hdc
#and the second on the secondary is hdd.
#
#You will need a method to boot with a floppy. Toms rootboot disk
#comes to mind. Redhats rescue disk will also work well.
#
#Boot with one of these and do the following:
#
#mount /dev/hdb? /mnt/hdb? /* the ? is the partition number*/
#do this for the / and /etc and /sbin and /boot if they are on seperate
#partitions. They are probably all just in / . I'll assume they are all in
#the / partition (/dev/hda5 for example)
#
#ln -s /mnt/hda5/boot /boot
#ln -s /mnt/hda5/etc/lilo.conf /etc/lilo.conf
#ln -s /mnt/hda5/sbin/lilo /sbin/lilo
#
#This will make links that lilo will follow when run later.
#
#In the file /etc/lilo.conf edit the lines that list your old
#/dev/hdc5 to be /dev/hdb5
#
#/* EXAMPLE*/
#
#boot=/dev/hda
#map=/boot/map
#install=/boot/boot.b
#prompt
#timeout=50
#image=/boot/vmlinuz-2.2.5-15
# label=linux
# root=/dev/hdc1
# initrd=/boot/initrd-2.2.5-15.img
# read-only
#
#/* BECOMES*/
#
#boot=/dev/hda
#map=/boot/map
#install=/boot/boot.b
#prompt
#timeout=50
#image=/boot/vmlinuz-2.2.5-15
# label=linux
# root=/dev/hdb1
# initrd=/boot/initrd-2.2.5-15.img
# read-only
#
#If you use the redhat rescue disk, it has pico for an editor (easy) the
#other uses vi (not so easy)
#
#now run: /sbin/lilo
#
#You should see that the lilo command adds a linux * line (in this case,
#you may have other OS's installed).
#
#IMPORTANT!!! cd /
#
#umount /dev/hdb5
#
#If you don't umount the drive, it may not get written to properly. now 3
#finger salute, pop out the boot floppy and you should get you old LILO
#prompt. If you have more than 1 OS in LILO, the tab key will give you a
#list of keywords to boot with.
#
#
#James Kinney M.S.Physics jkinney at teller.physics.emory.edu
#Educational Technology Specialist 404-727-4734
#Department of Physics Emory University http://teller.physics.emory.edu
#
#On Thu, 10 Jun 1999, Chris Woodruff wrote:
#
#> I moved my second hard drive from the secondary IDE controller and made it
#> the second device on the primary IDE controller. Linux is located on the
#> moved hard drive. I try to boot up Linux and get a kernel boot error. I
#> assumed that would happen. How can I fix this? I just loaded linux a few
#> days ago so if I had to redo the install it wouldn't be a big deal.
#>
#> On another note I went and bought a Diamond Viper V770 and then NVIDIA
#> released the open source drivers for all their chipsets. I would advise
#> anyone who is looking for a new card and wants something special to get your
#> hands on this baby. Besides the nice people at NVIDIA for releasing the
#> drivers, this is a great card. The only drawback is that you cannot go over
#> 16 bit color if you want hardware acceleration. But I can live with it.
#> Just wanted to pass that along.
#>
#> Chris Woodruff
#> cwoodruff at worldwindtech.com
#> Worldwind Technologies, Inc.
#> www.worldwindtech.com
#>
#
More information about the Ale
mailing list