> > A little bit tricky to set up, but works fine. > > Why would that be necessary, when mkinitrd can build in iSCSI support > natively? Come to think of it, this may be a case when having the kernel in > an NSS makes perfect sense.
I agree. It's just a little tricky to set up at the moment, as you have to do it by hand and the options to enable iSCSI support aren't immediately obvious. Also, DCSSBKUP and DCSSRSAV don't do so hot with IPLable NSSes -- wouldn't it be nice if SPXTAPE had that CMS Pipe option about now? I guess shipping an EXEC to create the DCSS/NSS wouldn't be so bad, though. Or a SES package to manage creating the DCSS (probably the right way to do it) in VMFPLCD format. I wonder if somebody wrote such an animal, would Dame Tami be willing to help in packaging it to be SES-friendly? > Even without that, having the kernel and initrd > written to DASD or SCSI is enough to then have the root file system (and all > others as desired) on an iSCSI disk. Sounds like an excellent option for a starter system. Would remove a lot of the need for messing around with LVM (or at leaset constrain the LVM stuff to a "server" machine like the SFS servers). Would probably make migrating Linux systems around in clusters a lot easier too. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
