Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3...
From: Ian Mapleson (mapesdhs_at_yahoo.com)
Date: 08/12/04
- Next message: Ian Mapleson: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."
- Previous message: noorg: "Re: xfsdump Problems"
- In reply to: Brent Casavant: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."
- Next in thread: Max Matveev: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."
- Reply: Max Matveev: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 12 Aug 2004 02:55:19 -0700
Brent Casavant <bcasavan@sgi.com> wrote:
> Another one to check is:
Yep, tried clearing that. No effect.
> Oh, and vfs_mountroot is just the name of the kernel routine that
> tries to mount the root filesystem.
As near as I can make out, consensus in past posts (thanks to Tony
for the search suggestions!) is that the kernel has some record
built into it of where to boot from and this needs to be changed.
Mark Mitchell said in 1997 on .admin:
***************************
From: Mark Mitchell (mark@k-par.co.uk)
Subject: Re: Dual boot capability
View: Complete Thread (3 articles)
Original Format
Newsgroups: comp.sys.sgi.admin
Date: 1997/02/25
> I have a need to be able to boot an Indigo2 system under either 5.3 or 6.2.
> I have two drives (one with either operating system), and I can mount the
> 5.3 drive under 6.2, but the need is to be able to boot under the OS of
> choice without having to physically swap drives. So far, this capability is
> completely eluding me. Any pointers would be greatly appreciated. Thanks.
Mike,
I've got an IRIX 5.3 disk on ID 1, and a 6.2 disk on ID 2. To boot
IRIX 5, I run the following script:
nvram -v SystemPartition "dksc(0,1,8)"
nvram -v OSLoadPartition "dksc(0,1,0)"
/etc/reboot
or to boot IRIX 6:
nvram -v SystemPartition "dksc(0,2,8)"
nvram -v OSLoadPartition "dksc(0,2,0)"
/etc/reboot
I hope this helps.
By the way - be careful if you're changing the scsi IDs of these disks. E.g. if
you've currently got both disks on ID 1. The scsi ID (or some reference to it from
/dev/root) is compiled into the kernel: if you change the scsi ID of the disk and
try to boot - it'll fail - or it'll load the kernel off the disk at ID 1.
If you do have this situation, (and you don't want to re-install):
- set your 6.2 disk to scsi ID 1
- boot
- change /dev/root and /dev/rroot so that the minor numbers are correct for the
new scsi ID: it'll be the same as the fs partition containing unix:
e.g. for ID 2, partition 0:
ls -l /dev/rdsk/dks0d2s0
brw------- 2 root sys 128, 32 Oct 8 11:49 dks0d2s0
giving a major number of 128 and a minor number of 32.
Create the new devices with:
mknod /dev/root b 128 32
mknod /dev/rroot c 128 32
- run /etc/autoconfig
- Shutdown, set the scsi ID to the new ID and boot.
This last section should probably have "use at your own risk" and "may be a bad
idea" plastered all over it.
Mark.
***************************
What do you reckon? Also, one other poster thought that the swap reference
may have to be changed in the same way; if so, how?
I'll setup a basic 5.3 disk to test this out, make sure I don't wreck
my main complete 5.3 disk.
Thanks for the replies so far!
Ian.
- Next message: Ian Mapleson: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."
- Previous message: noorg: "Re: xfsdump Problems"
- In reply to: Brent Casavant: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."
- Next in thread: Max Matveev: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."
- Reply: Max Matveev: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
