19 Jul
2001
19 Jul
'01
2:26 a.m.
On Jul 19, 8:52, Jarkko Teppo wrote:
[ NeXT documentation ]
niload is just a helper for loading text-based configuration files into
the NetInfo DB. nidump does the same in reverse.
I got that far from the man pages, but I need to know which files they
handle and what to turn them into for a single NeXT (in a sea of UNIX
varieties).
That looks useful. Thanks!
Except that it breaks one of the golden UNIX rules; keep the config
information human-readable.
If you install the whole shebang (at least on 3.3) you
get the
documentation
library in (I don't remember)
/NextLibrary/something. It doesn't matter
because the bookshelf-files are in /NextLibrary/BookShelves/. Just double
click on SysAdmin.bshlf.
Thanks, I'll look tonight.
Man-pages on niload and nidump might help too.
Honestly, I never
remember
how to do it so I just improvise and create a
local NI hierarchy and
use DNS for name resolution.
I read them, and realised they didn't tell me enough, mainly because I
don't understand the rest of it. No, NIS is
*never* an option ;-)
Heh :) I'm sometimes ready to put NI into same category but that's
probably just because I have one (or two, if you count white boxes)
NeXT(s). NI would probably kick ass in an installation with something
like 100 machines. I must admit that NetInfo can be quite confusing and I
can screw up a
machine pretty easily with it.
I did that too :-) By following the obvious option in the setup and
telling the machine it should use the network. I didn't realise what I was
telling it to use the network *for* :-)
--
Pete Peter Turnbull
Network Manager
University of York
19 Jul
19 Jul
4:08 a.m.
New subject: NeXT (was (OT) Sgi Indy)
Quoting Pete Turnbull <pete(a)dunnington.u-net.com>om>:
Well, NeXT did a few things against unix traditions, NI didn't
probably work out well but objc, developing environment and the
windowing system certainly did. One really has to try those to see
how badly X11 sucks.
On Jul 19, 8:52, Jarkko Teppo wrote:
Thanks, I'll look tonight.
or:
http://www.channelu.com/NeXT/NeXTStep/3.3/nsa/11_MixedNet.htmld/
NeXT(s). NI
would probably kick ass in an installation with
something
like 100 machines.
Except that it breaks one of the golden UNIX rules; keep the config
information human-readable. I did that too :-) By following the obvious option in
the setup and
telling the machine it should use the network. I didn't realise what I
was
telling it to use the network *for* :-)
If you end up with a corrupted NI db (badly corrupted) you can reset all
the NI information by booting single-user and
cp -r /usr/template/client/etc/hostconfig /etc
cp -r /usr/template/client/etc/netinfo /etc/netinfo
You'll lose all NI information like user accounts and so on. Better than
a reinstall anyway.
I once had to do that when I hooked up a TK50ZGAFSA (the one with almost-scsi
anyway) and it had the same SCSI-ID as my root disk. I should have noticed this
when the tape drive started blinking as the root drive was seeking. Blame it
on the beer. You should have seen the drive corruption though :-)
--
jht
8576
days inactive
8576
days old
1 comments
2 participants
participants (2)
-
jarkko.teppo＠er-grp.com -
pete＠dunnington.u-net.com