Date: Fri, 1 Sep 1995 19:18:23 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: hackers@freefall.FreeBSD.org Subject: Re: fdisk in 2.1.0-<mumble>-SNAP is broken Message-ID: <199509011718.TAA01574@uriah.heep.sax.de> In-Reply-To: <9509011110.AA06700@kanga.x.org> from "Kaleb S. KEITHLEY" at Sep 1, 95 07:10:32 am
next in thread | previous in thread | raw e-mail | index | archive | help
As Kaleb S. KEITHLEY wrote: > > > > fdisk -u -a /dev/r[sw]d0 > > > > (Don't use the `d' parititon.) > > Er, okay, that works. Don't know why that didn't occur to me, guess I'm > too set in my ways from 1.x and they way that it worked. So that raises > the next question, which is why was this changed from the way it worked > in 1.x, i.e. why did the 1.x fdisk know to use the raw device by default > but the 2.x fdisk does not? It doesn't follow the rule of least surprise. It's been changed since we've got a better solution than the mystic `d' partition now to access the entire drive; it's the slice code. Only the `c' partition remains magic now, it's the synonym for the entire slice. fdisk hasn't been updated yet. I'm about to commit my minor change to fdisk as recently posted here, fdisk will remain icky, but at least it will have better defaults than. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509011718.TAA01574>