This is probably covered in NetApp 101 but never having taken the classes (yet) I need something clarified.

Environment: Sun solaris with automounter and different flavors of filers running ATM and LANE.

i mucked up the networking portion of the rc file and the filer was essentially hung trying to export filesystems. it could not resolve the addresses to these hosts because it could not get dns or nis or any name resolution or even a default route for that matter. It hung while complaining for over an hour. so i could not get in through my normal "cd /net/filername/etc" my final recourse was to create boot floppies, boot from them, selecting "boot without rc" bringing up networking with ifconfigs and elconfigs, then going in through "cd /net/filername/etc" and editing the rc file accordingly and rebooting. very slow and tedious.

My basic question is: was this the proper way to fix a screwed up rc?

boot floppy manually config network cd /net/filername/etc edit rc

Or is there a way to edit the rc file from a terminal session? or any other of the /etc files?

what is the quickest way to recover from this type of problem??

can i boot the filer kernel in single user mode without networking?

What is the best way to get around this problem in the future? Can i make the exports fail and just come up to a prompt or do i have to boot floppy everytime?

if i hardcoded my export hosts in the /etc/hosts would the filer come up even without networking and NIS/DNS, etc?

thanks

Roger D. Leonard