Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!olivea!hal.com!decwrl!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: question about 386BSD to FreeBSD upgrade Date: 28 Oct 1993 18:17:31 GMT Organization: Montana State University, Bozeman MT Lines: 30 Message-ID: <2ap2br$bih@pdq.coe.montana.edu> References: <1993Oct27.231725.13173@mcshub.dcss.mcmaster.ca> <2an2u0$4ak@pdq.coe.montana.edu> <2anvp4$43c@germany.eu.net> NNTP-Posting-Host: bsd.coe.montana.edu In article <2anvp4$43c@germany.eu.net>, Bernard Steiner <bs@Germany.EU.net> wrote: > >In article <2an2u0$4ak@pdq.coe.montana.edu>, nate@bsd.coe.montana.edu (Nate Williams) writes: >|> There will be a set of upgrade patches to go from EPSILON to the 1.0 >|> release whenever the 1.0 release is done. (EPSILON isn't *that* old :-) > >Will there be a proper script to install things from scratch ? > >I'm talking about the install script happily discarding the old disklabel >information instead of offering it as the default configuration, especially >for stuff like interleave and seek time, and the badsect flag; and I'm talking >about the "bad144 wd0 0" that is run shortly afterwards, which isn't very >helpful at all since there is a bad block in the lower 8 Meg on my wd0d... This is totally different from the installation disks. This is a set of scripts to *upgrade* (ie: NOT re-install). For installation problems, you need to speak to someone else. As always, send email to freebsd-questions@freefall.cdrom.com Nate -- nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone, nate@cs.montana.edu | so let's not compete with each other, let's work #: (406) 994-4836 | compete with folks who try to tie us down to home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me