You mean set up a Linux NSS like we do a CMS NSS? When you IPL the CMS NSS it expects 190 to be the boot disk, 19E to be the CMS equivalent of /usr and 191 to contain the configuration files. When it comes up the first thing CMS does is to run the PROFILE EXEC on the 191 disk. The commands to access any other disks and load any needed extensions are in that file. You can place any CP or CMS commands you want to in the PROFILE EXEC and they will be run whenever CMS starts up in that virtual machine.
Stephen Frazier Oklahoma Department of Corrections -----Original Message----- From: [EMAIL PROTECTED] [mailto:owner-linux-390@;VM.MARIST.EDU]On Behalf Of Kris Van Hees Sent: Friday, November 08, 2002 10:00 AM To: Linux on 390 Port 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.
