Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 May 1995 17:16:38 -0400 (EDT)
From:      "House of Debuggin'" <wpaul@skynet.ctr.columbia.edu>
To:        jkh@freefall.cdrom.com (Jordan K. Hubbard)
Cc:        hackers@FreeBSD.ORG
Subject:   Re: Add NIS config to sysinstall, please
Message-ID:  <199505312116.RAA01881@skynet.ctr.columbia.edu>
In-Reply-To: <21573.801951987@freefall.cdrom.com> from "Jordan K. Hubbard" at May 31, 95 01:26:27 pm

next in thread | previous in thread | raw e-mail | index | archive | help
They say this Jordan K. Hubbard person was kidding when he wrote:
> 
> > Maybe it's really cleverly hidden, but I wasn't able to find a NIS client
> > configuration option in the 'Network Services Configuration' menu.
> > I suggest adding an menu for this. The following steps would be involved:
> 
> Um. I thought about this and decided "2.1".  It's just not something I
> have time for at the moment - sorry!

Fair enough, I guess.

How about this then: it would be really, really, really, REALLY helpful
if there were a pause between the time where the emergency holographic shell
comes up and the distribution extraction begins. This might have been
mentioned already. If not, consider that it would make setting up
a bastardized system with an NFS-mounted /usr filesystem a lot simpler.
I'm in the middle of trying to do this now, and I'm having to cheat in
a big way; the machine I'm using is very slow, and I have enough lag time 
before /usr is populated to do the mount manually.

As it is, the extraction (I'm talking about everything after the root.flp
image here) comes up immediately after the shell is spawned, and there's
no way to pause the extraction and resume it once it gets going.

As it happens, this is really the only serious problem I've bumped
into so far. I'm attempting to do a binary-only install on a 386sx/16Mhz
system with an 8-bit 3c503 card, 4Mb of RAM and a 20Mb Seagate ST-225 
XT-class drive -- with bad blocks on it, no less. The kernel reports only 
3.8Mb of RAM in the system. I'm getting quite a few 'Process XX killed 
by vm_pageout -- out of swap' message on the debug screen, but things are 
still moving right along in spite of this. The bad144 scan is taking
an obnoxiously long time to run, but I can deal with that.

Yes, I'm insane. But it never hurts to torture test, right?

> 
> 						Jordna
> 

Wow: you are tired, aren't you. :)

-Bill

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Bill Paul            (212) 854-6020 | System Manager
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Møøse Illuminati: ignore it and be confused, or join it and be confusing!
~~~~~~~~~ FreeBSD 2.1:  "We can kick your operating system's ass!" ~~~~~~~~~~



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505312116.RAA01881>