NetBSD 1.6.2 installer segfaults

From: cmad (thecmad_at_gmail.com)
Date: 11/30/04


Date: Tue, 30 Nov 2004 21:11:58 +0200

OK so I'm trying to install NetBSD 1.6.2. As I reach the disklabel part,
  when I choose "Custom" (from the list of options: Standard, Standard
with X, Custom, and something else), the installer segfaults (right
after I choose Custom, I haven't tried the others) and it complains
about / being full. The only thing I can do is a hard reboot.

I have no idea what it might be... I doubt it's the HDD, since FreeBSD
installs just fine (on the same place). As for the HDD, one thing I've
noticed is that the geometry BIOS shows me is different (and obviously
wrong) from the one NetBSD (and FreeBSD) show me. What could cause this?

Thanks in advance,
cmad



Relevant Pages

  • cannot install 5-current snapshot.
    ... I booted from the install floppies, and chose "Custom" or "Standard" ... (I encountered the same failure with the snapshot of early May, ...
    (freebsd-current)
  • Re: NetBSD 1.6.2 installer segfaults
    ... > OK so I'm trying to install NetBSD 1.6.2. ... As I reach the disklabel part, ... > with X, Custom, and something else), the installer segfaults (right ...
    (comp.unix.bsd.netbsd.misc)
  • Re: MS Security Update broke Web Servew 2003 Anonymous Connections
    ... credentials were the same in the local SAM. ... The standard IUSR_MachineName is no different from your custom anonymous ... and the Web Sites WORK now. ...
    (microsoft.public.inetserver.iis)
  • Re: Installation of Office 2007 (over Office 97)
    ... Differences between Standard and Professional = Access. ... It will clean the registry after you delete the Office 97 folders from your Windows. ... I will proceed to attempt to install my ... Jocelyn ...
    (microsoft.public.office.misc)
  • RE: Deployment Architecture/Attach SQL MDF
    ... manage SQL Server instance in code. ... Backup and Restore with User Instances ... you can use such code in your custom action program or class. ... Install SQL Server 2005 from the Command Prompt ...
    (microsoft.public.dotnet.languages.vb)