chari@math.utexas.edu (Chris Whatley) (07/26/90)
I have run into a big problem with a new network station (a.k.a diskless NeXT). It seems a network station with 1.2 roms does not operate properly with 1.0 roms. It also seems that NeXT should make this kind of information more readily available so that certain sysadmins do not waste nearly an entire day chasing down possible misconfigurations of software. The solution to this problem is to swap boards between the server and client, giving the server the new roms. Everything after that works great. The symptom of this problem arises after booting up multiuser (which works). If you mount an NFS partition on the diskless client, it mounts fine. If you try to access that directory by using 'cd' in sh or csh, their calls to chdir() return ENOTDIR. When you 'ls' the directory, for each item in the directory, the shell replies with "<fname> does not exist.". Just to clarify things, the root and private partitions mount up fine. They are readable and writable on the client. The exact same software configuration (i.e. using the same client partition, only changing bootparams to reply to a different ethernet address) works for a 1.0 server to a 1.0 client and a 1.2 server to a 1.0 client. Chris "I've got good news. The gum you like is going to come back in style." -- Chris Whatley - Research Systems Administrator UT-Austin Mathematics E-mail: chari@math.utexas.edu (NeXT) Ph: (O):512/471-7711 (H):512/499-0475