Date: Mon, 16 Jun 2003 17:23:54 -0400 From: Eric Jacobs <eaja@erols.com> To: freebsd-hackers@freebsd.org Subject: Re: floppy.. Was: Drawing graphics on terminal Message-ID: <20030616172354.4850c3b2.eaja@erols.com> In-Reply-To: <20030616153806.A42660@FreeBSD.org> References: <20030616191852.GA52694@ussenterprise.ufp.org> <Pine.BSF.4.21.0306161235420.19977-100000@InterJet.elischer.org> <20030616194359.GA53587@ussenterprise.ufp.org> <20030616194625.GA1845@over-yonder.net> <20030616153806.A42660@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Jun 2003 15:38:06 -0500 Juli Mallett <jmallett@freebsd.org> wrote: > 1) Network install. > The floppy could include only network (and requisite) drivers, > such that mass storage drivers could be pulled over the net at > an early stage in the install. Ideally we would work from the > information we gather about driverless devices to figure out > what drivers may be appropriate, but letting the user select > would be a must, as would possibly trying everything, with a > suitable warning that drivers may be quite large. > > 2) CD-ROM install. > The CD-ROM should be used for booting, or a floppy similar to > that in case 3. should be used. > > 3) Install from other physical medium. > No network drivers. Just storage (and requisite) driers of > every common colour at the very least. Driver floppies could > be available for the more bloated. No reason a user cannot run > sysinstall after the system is installed to set up the network > parameters they want, if they don't need them for the bootstrap > install. This should probably not have netinet, etc., I like these ideas. The one other thing I could imagine being useful would be a consoleless install via Ethernet. That could be managed though by having the network KLD's on the CD-ROM, since there wouldn't be a shortage of space.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030616172354.4850c3b2.eaja>
