cees@htsa (cees keyer) (12/01/88)
********** WARNING ************ Hello dear reader, I've stumbeled on a promblem when you want to boot the diskless node's. I have created the diskless_list file in /sys/net with vi but now way the diskless node's couldn't be booted. Then I created the diskless_list file with the apollo (dm) editor and there was no problem. If anyone could explain me what the difference is in files created by the apollo editor or by vi. BTW we are running sr9.7.01 or something like that. Thanx in advance, Cees Keyer ____________________________________________________ | DISCLAIMER: All the opinions expressed are my own | | | | Cees Keyer, Algemene Hogeschool Amsterdam. | | Deparment of electrical engineering | |---------------------------------------------------| | The answer is ' 42 ' | | The hitchikers guide to the galaxy | |---------------------------------------------------| |uucp: {backbones}!mcvax!htsa!tamtam!cees or | | {backbones}!mcvax!htsa!cees | |___________________________________________________|
dbfunk@ICAEN.UIOWA.EDU (David B. Funk) (12/10/88)
WRT posting <18@tamtam.htsa.UUCP> from Cees Keyer about a problem with
creating a diskless boot list using vi instead of the dm for an editor:
Intrinsicly, there should be no reason why you can't use vi to edit
your diskless_list file. Regardless of whether you use vi or the DM
to do the editing, you should be able to end up with a text file that
netman could use.
I can think of two possible problems that could arise when you use
vi that wouldn't with the DM, though:
The DM uses the initial default ACL for protections when creating the
file, vi uses your umask. If you had your umask set so that the file was
not readable by the world, then netman (which runs as user.server.none)
couldn't read it and boot the diskless nodes. When you use vi be sure to
check the protections when you're done.
The DM is quite strict about not putting stray control characters into
a file that it is editing. You have to use special escape sequences to put
things like tab & ff into a file, and you can't even put in most other
control characters. Vi will happily let you put in just about any control
character that you want to hit, even if accidently. So you may have put in
some control character that caused netman to not like the rest of the file
contents. (This is pure speculation, I havn't tried it to check it out.)
When you use vi be sure that no stray control characters slip in where not
invited.
I notice that you say that you are running "sr9.7.01 or something like that."
If you are running sr9.7.0.1 on DN3000 or DN4000 series machines, be
aware that there is a bug in that rev. of the OS on those machines that
can break SIO output. Please note that this only applies to DN3k & DN4k
machines and sr9.7.0.1. If you have any questions as to what you have,
use /com/bldt to check it out. If you see output that looks like:
AEGIS7-DOMAIN/IX kernel, revision 9.7.0.1 , Wednesday, January 6, 1988 9:05:14
or
AEGIS8-DOMAIN/IX kernel, revision 9.7.0.1 , Wednesday, January 6, 1988 9:13:08
and your SIO output locks up after outputing a few thousand characters,
you need an OS patch kit. The correct revision to use is sr9.7.0.3.
Call your Apollo service rep for the patch kit.
Dave Funk
University of Iowa