Date: Fri, 27 Oct 2000 15:44:01 -0600 (MDT) From: Fred Clift <fclift@verio.net> To: Robert Nordier <rnordier@nordier.com> Cc: Fred Clift <fclift@verio.net>, Matt Dillon <dillon@earth.backplane.com>, Terry Lambert <tlambert@primenet.com>, "freebsd-stable@FreeBSD.ORG" <freebsd-stable@FreeBSD.ORG>, hackers@FreeBSD.ORG Subject: Re: Really odd "BTX halted" problem booting FreeBSD on VALinux Message-ID: <Pine.BSF.4.21.0010271539300.21278-100000@vespa.orem.iserver.com> In-Reply-To: <200010272111.XAA32064@siri.nordier.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > Why not edit the partition table after boot1 gets installed? > > Because you can never make it valid. By keeping it the same set of > illegal values, at least the system can recognise it. What do you mean it can't be made valid? fdisk -u and a few keystrokes later and I have a valid partition table... Whats wrong with it? Really, if I'm being dense, sorry -- perhaps I just dont under stand yet -- please be patient with me :) > > A final point: > > o Don't use dangerously dedicated mode. I'd love to but the tools for automated installs in non-dedicated mode dont really exist in a supported way. One of the things that was pointed out in the thread is that disklabel doesn't work inside an fdisk slice. I could use expect to manipulate sysinstall? So, for now, I use dangerously dedicated installs with a hacked fake partition table to work around the broken bioses I use. I just might start using program posted in this thread that lets you do labels right in lieu of anything else, or perhaps I'll fix disklabel to work right as was suggeseted elsewhere. Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010271539300.21278-100000>