Date: Sun, 15 Sep 2002 14:05:40 -0700 (PDT) From: "Andrew P. Lentvorski" <bsder@mail.allcaps.org> To: Mike Tancsa <mike@sentex.net> Cc: Valentin Nechayev <netch@iv.nn.kiev.ua>, Dmitry Suhodoev <raven@bingo.chel.ru>, <stable@FreeBSD.ORG> Subject: Re: creating ad2s1a Message-ID: <20020915135238.V93261-100000@mail.allcaps.org> In-Reply-To: <5.1.0.14.0.20020915120003.05e01890@192.168.0.12>
next in thread | previous in thread | raw e-mail | index | archive | help
All these workarounds kind of point to an interesting problem: Why doesn't FreeBSD have a consistent disk label/partitioner/editor as a standalone command? I bump into strange problems quite often when I am setting up RAID partitioning schemes. I wind up having to utter several magic incantations that I never remember between setups. Things like using dd to zero out the initial label, fdisk to set the slice, disklabel to set the partition, oh did I remember to set the slice bootable, oops, I forgot to write the boot code, oh, bummer, now I have to newfs it, oh, blast, I forgot to set softupdates, etc. That's an awful lot of magic to expect people to work out. A single tool which moves a blank device with possibly random data up to a state where newfs actually works would be Useful Thing(tm). -a 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?20020915135238.V93261-100000>