Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3...

From: Max Matveev (max.matveev_at_sgi.com)
Date: 08/12/04

  • Next message: Ian Mapleson: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..." 
    Date: 12 Aug 2004 20:12:25 +1000

    >>>>> "mapesdhs" == Ian Mapleson <mapesdhs@yahoo.com> writes:

     mapesdhs> Brent Casavant <bcasavan@sgi.com> wrote:
    >> Another one to check is:

     mapesdhs> Yep, tried clearing that. No effect.

    Here is an example of script which we use to do "multiboot"

    #! /bin/sh
    /sbin/nvram OSLoadPartition 'dksc(0,1,11)'
    /sbin/nvram root 'dks0d1s11'

    /sbin/telinit 6

    In this case, all partitions are on the same disk and all are variants
    of 6.5, so we keep one SystemPartition and boot different releases of
    6.5.

    You could consider using 6.5 sash for both and just change to 5.3
    OSLoadPartiton and root - AFAIK there is no requirement to have both
    sash and root on the same disk and as long as both disks are
    connected, it should "just work (tm)".

    >> Oh, and vfs_mountroot is just the name of the kernel routine that
    >> tries to mount the root filesystem.

     mapesdhs> As near as I can make out, consensus in past posts (thanks to Tony
     mapesdhs> for the search suggestions!) is that the kernel has some record
     mapesdhs> built into it of where to boot from and this needs to be
     mapesdhs> changed.

    No, that is (was?) Linux way of doing things, Irix has no information
    about root device in the kernel whatsoever: you can boot from
    different disk, from NFS, from CD, all with the same kernel.

    max

  • Next message: Ian Mapleson: "Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3..."

    Relevant Pages

    • Re: Setting up dual-boot on Indigo2 for 6.5 and 5.3...
      ... /sbin/nvram OSLoadPartition 'dksc' ... all partitions are on the same disk and all are variants ... OSLoadPartiton and root - AFAIK there is no requirement to have both ... mapesdhs> As near as I can make out, consensus in past posts (thanks to Tony ...
      (comp.sys.sgi.misc)
    • SUMMARY: Moving /usr From Under Root "/" To Its Own Partition
      ... One of the reasons for doing this is to end up with a smaller root ... Install the boot block and boot off the new drive. ... " In order for the root partition to be fscked and remounted ... D> temporarily on the existing disk. ...
      (SunManagers)
    • Summary: Restoring root fileset on 4.0d
      ... There is a renamefset command that was suggested, but since the system was running (only the clone backups were failing because the root fileset was mistakenly named "roottmp") I did not want to risk renaming the root filesystem in multiuser mode. ... I used the vdump/vrestore process to copy the original data for root, usr, and var to another disk and then I had a tech onsite move the new disk into the scsi position of the original disk. ... I want to restore the root advfs filesystem on a 4.0d system. ...
      (Tru64-UNIX-Managers)
    • Re: what to do about "cannot dump to dumpdev hd(1/41): space for
      ... smoke out anything that would point to root being there. ... whole disk division and maybe boot but nothing else. ... I've see that before when a client used Microlite Backup ... alter the file system and log its results to /tmp/logfsck. ...
      (comp.unix.sco.misc)
    • Re: Best Practices Survey: Disk Partitioning
      ... minimise root fs; ... => minimise size of actively changed filesystems to speed ... (again to restrict most disk activity to a more limited partition, ...
      (comp.os.linux.security)