I was thinking... a different approach... see what do you think:
1- I copy my fstab and lilo.conf to somewhere... to save my current setup that
is:
/dev/hda is a UDMA100 40G HD and master at IDE interface 1 (win98)
/dev/hdb is a UDMA33 4.2G HD and master at IDE interface 1 (linux)
/dev/hdc is the cd-rom and master at IDE interface 2
2- Do the following: leave /dev/hda where it is (as boot device and windows
drive),
remove /dev/hdb (my linux drive) from the system, install my spare HD (the 600M
one) as /dev/hdc and install my cdrom as /dev/hdd and now I have this:
/dev/hda is a UDMA100 40G HD and master at IDE interface 1 (win98)
/dev/hdc is a 600M HD and master at IDE interface 2 (linux)
/dev/hdd is the cd-rom and slave at IDE interface 2
3- Do a small linux install in /dev/hdc using the same partioning system that I
had in my removed HD (the same partitions and filesystem type -reiserfs-)
4- after the install I copy the new fstab and lilo.conf
5- do a boot floppy, that will say "hey, you can boot windows as default in
/dev/hda or ypu can boot linux in /dev/hdc"
6-shutdown the system... remove spare HD, install my linux HD in its place
7- do a boot using the floppy... now I can (I can? I hope so... :-)) access my
linux drive again...
8- I overwrite the olders fstab and lilo.conf with the newer ones...
9- Happy ending, now I have:
/dev/hda is a UDMA100 40G HD and master at IDE interface 1 (win98)
/dev/hdc is a UDMA33 4.2G HD and master at IDE interface 2 (linux)
/dev/hdd is the cd-rom and slave at IDE interface 2
What do you think? Does it make sense? Or I'm delirious???
TIA
orlando
Rusty Carruth wrote:
>
> "Jose Orlando T. Ribeiro" <[EMAIL PROTECTED]> wrote:
> >
> > I hadn�t expressed myself correctly!!
>
> Ah - ok. No problem!
>
> > What I did: removed the CD-ROM and changed the HD, so it didn't boot up... Now
> > I undestood waht you said... I had to put a small HD in the place of the CD-ROM
> > and don�t make any changes... right?
>
> Short answer - no, you want to put the small hd in place of /dev/hdb, so that lilo
> can still boot there (giving you a bootable linux - see next paragraph).
>
> The whole point of this mess is to
>
> 1 - ensure that you always have a bootable linux partition no matter what.
> 2 - boot that linux partition so you can set up the moved drive to boot again.
>
> In other (longer ;-) words, the idea is to make it so you can boot linux
> somehow, mount '/' from /dev/hdc1 (on e.g. /mnt/hdc1), chroot to there
> (chroot /mnt/hdc1), fix up /etc/lilo.conf, install lilo, fix up /etc/fstab
> (e.g. /mnt/hdc1/etc/fstab) to point to the right device (again, /dev/hdc),
> and then reboot using the newly-re-configured lilo. (Carefully rebooting
> so that you've left the chroot and unmounted everything so you don't have
> to fsck - oh, wait - you're using reiser. Never mind about that ;-)
