Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Jan 1996 21:28:30 -0800
From:      "Jordan K. Hubbard" <jkh@time.cdrom.com>
To:        Jon Loeliger <jdl@jdl.com>
Cc:        obrien@cs.ucdavis.edu (David E. O'Brien), freebsd-hackers@freebsd.org (FreeBSD Hacker's list)
Subject:   Re: X for install 
Message-ID:  <2771.820646910@time.cdrom.com>
In-Reply-To: Your message of "Tue, 02 Jan 1996 23:02:46 CST." <199601030503.XAA02277@chrome.jdl.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
> This sounds to me like the same general goal as the separation of
> the hardware detection process during boot -- part of the detect,
> semi-probe, negotiate, allocate, attach process that we've often
> discussed.  Can the same core be used for both the normal UNIX boot
> process and for the initial system config/install process?  Or am
> I totally in the weeds here?

If coverage was complete enough (e.g. *all* the useful devices were
detected and reportable somehow) then I certainly don't see why not!
I'd kill for a decent "here's where everything is" interface in
sysinstall, and it wouldn't really matter to me where the detection
happened - by the time you've invoked sysinstall, you've pretty much
finished (or certainly should have) all the probing and configuration.

					Jordan



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