home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!ames!olivea!sgigate!odin!twilight!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Newsgroups: comp.sys.sgi.admin
- Subject: Re: diskless installation woes, help needed
- Message-ID: <up4pohc@zuni.esd.sgi.com>
- Date: 12 Jan 93 06:06:41 GMT
- References: <1993Jan11.195638.10797@Princeton.EDU>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 83
-
- In <1993Jan11.195638.10797@Princeton.EDU> clk@ernie.Princeton.EDU (Christopher Kranz) writes:
- | I am in the process of converting our disk-poor Iris 4D/25s and 4D/35s to
- | diskless machines. I am planning to use the local disk for paging and
- | scratch space. I have run into a couple of problems in the process of
- | installing the diskless share trees and diskless client tress.
- |
- | The exit commands from installing the share tree for the 4D/35s produced the
- | following errors:
- |
- | idev: dependent driver shmiq is EXCLUDED
- | idev: dependent driver shmiq is EXCLUDED
-
- It looks to me like perhaps you used the wrong clinst.dat, and didn't
- get a number of files.
-
- | Does anyone know if this indeed a problem or just a side effect of building a
- | generic kernel for a given diskless class?
-
- It *is* a problem. You won't have a kernel to boot!
-
- | Assuming the above was not a problem, I went ahead and attempted to install a
- | client tree. During the installation I got the following error messages:
- |
- | Installing new versions of selected eoe2.sw subsystems
- | sh: /usr/diskless/client/4D35/client1/bin/rm: not found
-
- Sounds like some other part of the install (from eoe1.sw.unix) failed
- also, or it was using a share tree that was subsequently trashed.
-
- | [Aux Cmd] cd $rbase/usr/lib/fmfonts ; $rbase/bin/rm -f ChBlIc08.pcf.Z
- | ChBlIc11.pcf.Z ChBlIc12.pcf.Z ChBlIc14.pcf.Z ChBlIc15.pcf.Z
- | ChBlIc17.pcf.Z ChBlIc25.pcf.Z ChBlIc33.pcf.Z ChrBlk08.pcf.Z
- | ChrBlk11.pcf.Z ChrBlk12.pcf.Z ChrBlk14.pcf.Z ChrBlk15.pcf.Z
- | ChrBlk17.pcf.Z ChrBlk25.pcf.Z ChrBlk33.pcf.Z ChrtrI08.pcf.Z
- | ChrtrI11.pcf.Z ChrtrI12.pcf.Z ChrtrI14.pcf.Z ChrtrI15.pcf.Z
- | ChrtrI17.pcf.Z ChrtrI25.pcf.Z ChrtrI33.pcf.Z ChrtrR08.pcf.Z
- | ChrtrR11.pcf.Z ChrtrR12.pcf.Z ChrtrR14.pcf.Z ChrtrR15.pcf.Z
- | ChrtrR17.pcf.Z ChrtrR25.pcf.Z ChrtrR33.pcf.Z ChBlIc.ff ChrBlk.ff
- | ChrtrI.ff ChrtrR.ff
-
- This part is just informational.
-
- | I checked for myself and the file /usr/diskless/client/4D35/client1/bin/rm
- | did not exist. I tried to figure out why. After poking around a little I
- | discovered there are two eoe1.sw.cpp and eoe1.sw.lboot subsystems. One set
- | is from the IRIX 4.0.5 CD and is referred to as "eoe1 4.0.5 A" on the CD ROM
- | label. The other set is on the IDO 4.1 CD and is referred to as "eoe1 4.0.5"
- | on the CD ROM label. The eoe1.idb from the IRIX 4.0.5 CD that contains the
- | commands to install rm, as well as other files, got clobbered when the second
- | eoe1 subsystem from the IDO 4.1 disk was installed during the share tree
- | installation.
-
- They should have gotten *replaced*, but not "clobbered", unless you used
- different sets of options during the installation.
-
- | Now for the questions. Was it a mistake to install both of them? How do I
-
- No.
-
- | keep $DISKLESS/$SHARE/usr/lib/inst/eoe1.idb from getting over written by the
- | one on the IDO disk? Which version of eoe1.sw.cpp and eoe1.sw.lboot do I
-
- You shouldn't; it is supposed to do so.
-
- | need to have installed, the ones from the IRIX 4.0.5 A CD or the one from IDO
- | 4.1 CD? Can I safely merge the two eoe1.idb files by hand?
-
- In this case, they should be identical, so it shouldn't matter.
-
- | BTW, for some reason clinst needs to be able to create a symbolic link in /
- | called share that points to $DISKLESS/$SHARE/$CLASS. I had a directory in /
- | called share and could not get things to work until I renamed it to something
- | else. I wish there had been some error message telling me that, I just
- | happened to stumble upon it.
-
- I'll file a bug on that. The share tree is used to reduce disk space
- used on the server if you have multiple clients of the same system type.
- The documentation on setting up diskless should mention this already;
- if it doesn't follow up to this, and I'll file a bug on that also.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-