shogunx wrote: > Thats the only standpoint I need... The 390 is a R&D environment, not > used in production, and we own it outright. SO, theoretically, I could > slap a larger hd in the console of the 390, run linux on it, telnet into > the 390, and mount a partition of the drive in the console as the > DASD via network block device, thereby eliminating the need for an > external SAN to provide DASD? I know, I lose redundancy, etc, but I can't > seem to acquire code to operate the SSA SerialRAID controllers in my > Shark, which I ported linux to. Interresting project to port Linux to your shark ;-). It *should* work as far as I can tell, but be aware that you can run into nasty deadlocks once you don't have a local swap disk: you'll need networking for paging/disk IO, and once linux is hard out of memory networking is suspended until there is memory available => deadlock. Workaround could be to have a ramdisk or z/VM DCSS as swap target, or to go to church once a week ;-).
cheers, Carsten -- Carsten Otte IBM Linux technology center ARCH=s390 ---------------------------------------------------------------------- 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
