*BSD News Article 71089


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.dacom.co.kr!bofh.dot!usenet.seri.re.kr!bofh.dot!news.cais.net!van-bc!nntp.portal.ca!news.iceonline.com!iceonline!matthewa
From: Matthew Asham (matthewa@iceonline.com)
Subject: Various problems w/ 2.2-960612-SNAP
X-Newsreader: ICE Online's W3 Newsreader v1.00
Sender: Matthew Asham (matthewa@iceonline.com)
Nntp-Posting-Host: ns.iceonline.com
Organization: ICE Online Inc.  http://www.iceonline.com/
Message-ID: <Dt3tE4.49C@iceonline.com>
Originator: root@iceonline.com
Date: Sun, 16 Jun 1996 17:35:56 GMT
Lines: 31

Two weeks ago I installed the May 1 snapshot over my FreeBSD 2.1 system and had absolutely
no problems.  Yesterday I decided to install the latest snapshot (960612) but I have had nothing
but problems getting it to work after the installation.

These are the issues I seem to be running in to:

After the installation has completed, I booteasy gives me the usual "F? BSD" prompt (I have only one
drive in my box).  I press "F1" only to get the Booteasy prompt, I have never gotten the FreeBSD 
bootstrap.  I have started the OS by using the Snap boot disk and specifying the
root partition manually ( wd(0,a)kernel) and the system boots up fine.  Not that I really have to 
much of a problem with this, this is just bloody annoying.  

Even more annoying than this happening with the SNAP is that I reinstalled FreeBSD 2.1.0 earlier this 
morning, only to have the exact same thing happen.  Again, I had to boot off of the installation disks.

I guess it should be noted that the first upgrade I did with the May 1st snap shot was installed over
my existing 2.1 system, aka: Nice Upgrade.  The June 12 SNAP and 2.1.0 reinstalls were complete reinstalls,
complete with re labelling, etc..

The second issue that I have ran into is using sysinstall.  I can NOT add any packages, ports, etc.. using 
sysinstall (either during the normal install from disk, or in multiuser setup).  sysinstall claims a write_pkg
error and a "caught SIGPIPE" (on the debug console).  I am using the FTP style installation media (on a T1).

Ideas?  Comments?  Thank you for your time..

--
Matthew Asham - bwm@iceonline.com
Software Engineer - ICE Online Inc.  http://www.iceonline.com