From owner-freebsd-current Mon Dec 10 23:51:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 00FE437B405 for ; Mon, 10 Dec 2001 23:51:14 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id IAA27652 for freebsd-current@FreeBSD.org; Tue, 11 Dec 2001 08:51:12 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id fBB7dhK95573 for freebsd-current@FreeBSD.org; Tue, 11 Dec 2001 08:39:43 +0100 (MET) (envelope-from j) Date: Tue, 11 Dec 2001 08:39:43 +0100 From: Joerg Wunsch To: freebsd-current@FreeBSD.org Subject: Re: cvs commit: src/sys/kern subr_diskmbr.c Message-ID: <20011211083943.Q97235@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , freebsd-current@FreeBSD.org References: <200112101150.aa33241@salmon.maths.tcd.ie> <20011210222003.4391539F0@overcee.netplex.com.au> <20011209102129.F97235@uriah.heep.sax.de> <20011210004350.6703C3810@overcee.netplex.com.au> <200112092200.fB9M0J660085@uriah.heep.sax.de> <20011210005928.9538A3810@overcee.netplex.com.au> <20011210091103.M97235@uriah.heep.sax.de> <20011211111629.O63585@monorchid.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211111629.O63585@monorchid.lemis.com>; from grog@FreeBSD.org on Tue, Dec 11, 2001 at 11:16:29AM +1030 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As Peter Wemm wrote: > Yes, that is much safer, however there are certain bioses that have > interesting quirks that the MBR has to work around. The problem > when overlapping mbr and boot1 into the same block is that we no > longer have the space to do that. boot1.s has got *3* bytes free. Too bad. Peter, do you care to update the section about DD mode (and its dangers) in the FAQ after all this discussion? I could probably do it, too (the original entry is mine), but i had to quote your arguments only anyway. > Also (and I think this is more likely to be the problem you ran > into) many newer PC's are looking at the partition tables for a > suspend-to-disk partition or a FAT filesystem with a suspend-to-disk > dump file. Seems i really love my Toshiba (Libretto) that simply hibernates to the last nnn MB of the physical disk. ;-) (I have reserved a FreeBSD partition as a placeholder for the hibernation data.) > However, there is light at the end of the tunnel. EFI GPT is pretty > clean. Good to hear. While this sounds like dedicated disks will be gone then :), at least the format looks rationale enough. > It supports up to something like 16384 partitions ... It would be interesting to see how Windoze will arrange for 16K "drive" letters. :-)) The day vinum is up and ready to also cover the root FS, i won't need /any/ partition at all anymore. ;-) As Greg Lehey wrote: > > ...73 of those silly messages are just beyond any form of usefulness. > Hadn't we agreed to do this? I'm certainly in favour of the > bootverbose approach. I can't remember any agreement so far. But thinking a bit more about it, it sounds like the best solution to me, too. The only other useful option would be to restrict the message to once per drive, but that'll cost an additional per-drive flag, which is probably too much effort just for that message. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message