If you put something like cmsfs or hcp on the root disk, you should have enough
to read a config file from the CMS A-disk and use information in there to do
the dynamic configuration of the disks.
Despite what Sun Microsystems did with linking /usr/bin and /usr/sbin into the
root filesystem as /bin and /sbin, a more sensible setup is still to have the
core utilities that are required to boot a system (and to do basic maintenance)
as part of the actual root partition. I've banged my head against that
stupidity in Solaris more than once when a disk that held /usr happened to die.
Especially when you do not have a CDROM to boot the install media from.
Kris
On Fri, Nov 08, 2002 at 11:23:25AM -0500, David Boyes wrote:
> You would need at least one non-root/swap address mounted as /config or
> something for storing the configuration of what goes where, and you'd
> have to move at least a few of the utilities (eg mount, ifconfig, etc)
> from /usr to /sbin (generating statically linked versions) and include
> /sbin in the root filesystem.
>
> Much as I dislike Solaris, their diskless workstation filesystem layout
> is a pretty good model for this. We should use that as a model for
> ideas.
>
> -- db
>
> David Boyes
> Sine Nomine Associates
>
>
> > -----Original Message-----
> > From: Linux on 390 Port [mailto:LINUX-390@;VM.MARIST.EDU]On Behalf Of
> > Kris Van Hees
> > Sent: Friday, November 08, 2002 11:00 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: More NSS Info
> >
> >
> > Would it not be sufficient to create the NSS with just the
> > boot disk and maybe
> > swap configured in on the kernel parameter line, and then
> > using something very
> > early on in the boot process to add the other disks using
> > /proc/dasd/devices?
> > It might take some work to get the NSS and RO boot disk just
> > right for this to
> > work, but it would make it a lot more flexible.
> >
> > Kris
> >
> > On Fri, Nov 08, 2002 at 10:43:15AM -0500, Adam Thornton wrote:
> > > I don't have the faintest idea why IBM claims that you have
> > to have an
> > > identical DASD layout on all machines that share an NSS.
> > >
> > > Admittedly cursory testing seems to show that your NSS will have
> > > whatever parameter line you burned into it, which does
> > specify a range
> > > of devices. But not only can those devices change size (I
> > tested this
> > > with an ext3 and a swap filesystem), if you boot without a listed
> > > device, the only problem you will have that I could find
> > was that you
> > > may trip over it in /etc/fstab.
> > >
> > > But if you have a disk that's not in /etc/fstab, which you
> > detach before
> > > IPL, you can re-link and then access that disk pefectly
> > normally from
> > > Linux (using the console or hcp to perform the link).
> > >
> > > So it's looking to *me* like you should pick a
> > lowest-common-denominator
> > > disk layout (for most of our guests, that'd be / on 150,
> > swap on VDISK
> > > on 151, and /usr on 152), build the NSS with as small a
> > storage size as
> > > you can (24M works for us) and then not worry about it.
> > >
> > > If anyone can tell me why I'm wrong, and that, although I
> > have mounted
> > > differently-sized disks, I'm heading for fatal filesystem corruption
> > > just around the corner, I'd appreciate it.
> > >
> > > Adam
> >
> > --
> > Never underestimate a Mage with:
> > - the Intelligence to cast Magic Missile,
> > - the Constitution to survive the first hit, and
> > - the Dexterity to run fast enough to avoid being hit a second time.
> >
--
Never underestimate a Mage with:
- the Intelligence to cast Magic Missile,
- the Constitution to survive the first hit, and
- the Dexterity to run fast enough to avoid being hit a second time.
