On 14/06/2013, at 17:48, Alban Hertroys <haram...@gmail.com> wrote: > IMHO it would be helpful to verify what's there first and warn the user about > it if such an operation will overwrite a different type of label than what is > about to get written there. > Perhaps it should even refuse to write (by issuing an error stating that > there is already a label there - and preferably also what type) until the > label that's already there gets explicitly cleared by the user or until the > command gets forced. > Does that make sense?
The problem with this is that then each label tool needs to know about every other label format you want to detect for.. If a label format has a checksum then you could ignore a request to nuke the label if there is no valid checksum (with a flag to force). No idea how many have checksums though.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
