Ashley, Yes, this has been gotten to work. Every Linux/390 installation process I know of works this way. It's accomplished by using an initrd (ramdisk) for a root file system so that the init scripts can be executed to do the actual network setup commands. The parameter to the kernel just tells it what device numbers to look for, it doesn't tell it anything about the IP address, netmask, routing, etc. You'll need a running Linux/390 system (preferably) to create the initrd, but it is very much possible. Mark Post -----Original Message----- From: Ashley Chaloner [mailto:csuwf@dcs.warwick.ac.uk] Sent: Thursday, November 28, 2002 6:32 AM To: LINUX-390@VM.MARIST.EDU Subject: Root NFS for s390 with CTCs Hello there, I'm trying to get a 'diskless' VM by IPling a kernel from the reader and using a parmfile (in the reader, after the kernel) to determine the hostname and CTC info (IP address, netmask and the partner's IP address). I am also using V-DISK as swap. I have already compiled the CTC stuff into the kernel, and am passing the kernel a parameter like "ctc=ctc0,0x2000,0x2001", but this has no effect because I need the CTC to be activated in the kernel initialisation functions (before the root_nfs stuff) so that a NFS connection can be made. (I know the parmfile trick works because I can boot from the reader but still using DASD and after the DASD is mounted, the CTC connection starts fine using info from /proc/cmdline .) So my question is: Has anyone else tried this and got it to work, or has anyone got any useful comments/suggestions ? Thanks in advance, Ashley Chaloner. _______________________________________________ Redhat-s390-list mailing list Redhat-s390-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-s390-list
