beech@ms.uky.edu (Wayne Beech) (03/01/90)
Hello,
I am having a small problem when attempting to make a second boot-able
optical disk. i use builddisk to initialize the disk and it finishes
with no errors. the disk is then bootable and appears to work fine.
next i start the NetManager application and choose local configuration
and change the hostname from autoconfigure to the "box" below and fill
in the name test and click on Save. an alert window comes up that tells
me that the machine will have to reboot for these changes to take place
and gives me the chooses "skip reboot" and "ok". if i click ok the
screen blanks and i get the loading from disk screen and you can hear
a few disk accesses and then nothing, it just hangs. i then go to the
monitor and do a bod and get the following messages:
bad dir ino 7552 at offset 0 : mangled entry
bad dir ino 7552 at offset 1024 : mangled entry
bad dir ino 7552 at offset 2048 : mangled entry
i have a couple of questions regarding this situation:
1.) is using NetManager the correct way to change the hostname of a machine?
2.) can i fix the disk that is giving me these errors? i tried fsck on it
and that didnt seem to help.
any help would be greatly appreciated. thank you.
--
=============================================================================
UUCP : !ukma!beech
BITNET: beech@ukma
DOMAIN: beech@ms.uky.edusmithw@physc1.byu.edu (03/02/90)
can avoid the mangled entry bleep by NOT clicking on the reboot button. Just go and make whatever network file changes you need, and then either reboot from the rom monitor or power off then back on...seems to work that way most of the time...I'd like to know if this happens to you again.