Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!emory!stiatl!srchtec.searchtech.com!mra From: mra@srchtec.uucp (Michael Almond) Newsgroups: comp.unix.ultrix Subject: Re: Ultrix diskless client weirdness Message-ID: <1991Feb18.035712.15248@srchtec.uucp> Date: 18 Feb 91 03:57:12 GMT References: <3501@dali> Organization: search technology, inc. Lines: 35 In article <3501@dali> osyjm@caesar.cs.montana.edu (Jaye Mathisen) writes: > > >I have a VS2000 booted diskless off of a DS5000/200. I've had to go through >and change IP addresses on these machines, and now the VS won't boot. Okay, I've gone through this same problem. If you look in /etc/dms on the DS5000 you see that it is actually a shell script and this is how I found out how it adds a client and thus how to avoid re-installing a client. There are some commands you can use to examine the 'node' database that mop uses. They are: getnode - display one or more entries from the nodes database addnode - add or change an entry in the nodes database remnode - remove one or more entries from the nodes database You con't modify an entry in the database, but you can remove it and then add it back in the node database, leaving the client directory and other dms files uneffected. Try 'getnode ', where is whatever you call it when working with dms. This should show you the old ethernet address for your VS2000. Now 'remnode ' and then 'addnode '. It's been a while since I've done this, but I just looked over the /etc/dms script again to recall the steps. -- Michael R. Almond (Georgia Tech Alumnus) mra@srchtec.uucp (registered) search technology, inc. mra@searchtech.com 4725 peachtree corners cir., suite 200 emory!stiatl!srchtec!mra norcross, georgia 30092 (404) 441-1457 (office)