Talk:BSD disklabel

message: I've categorised this as :Category:BSD software, but it seems slightly mendacious - I mean, it's not really software, is it? At the same time, it does seem to me it should be in a sub-category of :Category:BSD rather than in the main BSD category, and this seemed the most suitable. A more clueful edit, however, would be welcome ... --JennyRad 19:30, 2 June 2006 (UTC)
thread_title:  Categorisation 

message: I would vote for a section underlining the fact that the 'disk label' referred to here is NOT what is generally understood as a Disk Label in conventional DOS/Linux terms, i.e a text identification-string for the disk. 
The ambiguity which this double-meaning creates is a dangerous one, as replacing the master boot record (MBR) in entirety would result in at least a nonbootable disk, and possibly destruction of the disk's data, whereas changing the disk's text identifier is a normal and safe operation.  
Label command
--Anteaus (talk) 21:34, 28 January 2008 (UTC)
replies: text: Disklabel is standard BSD UNIX terminology that has been around since at least the 4.3-Tahoe release (1988). What you describe is more usually referred to as a Volume Label. Letdorf (talk) 11:06, 29 January 2008 (UTC)

text: No, a FAT "volume" is not necessarily a hard disk partition (it could be a floppy disk for example). A FAT or NTFS volume label is not the same thing as a partition table! Also, I think the fact that the title of this article is "BSD disklabel" makes it obvious which OS we are talking about here, but I've added some disambiguation to the intro para anyway.  Letdorf (talk) 17:16, 8 February 2008 (UTC)
thread_title:  Dangerously ambiguous term 

message: I know that it's no longer in use, but what was the purpose of partition/label "d" ?
One of the links described it as "obselete whole disk", but how did it then differ from partition/label "c" ?  —Preceding unsigned comment added by Koppe (talk • contribs) 12:57, 8 February 2008 (UTC)
replies: text: Traditionally, d had no special meaning, but in PC BSD ports (eg. FreeBSD/i386, NetBSD/i386 etc), d is used to correspond to the whole physical disk instead of the usual c partition. In these cases, c corresponded to the BIOS MBR partition subdivided into BSD partitions only, excluding other MBR partitions used by other operating systems. Letdorf (talk) 17:10, 8 February 2008 (UTC)
replies: text: FreeBSD has not done this for quite some time now, probably more than a decade; there is no way that it could possibly work (but it's also unnecessary).  It used to be, in ancient *BSD systems, that the kernel did not really understand nested partitioning schemes, so the disk block numbers in the disklabel were absolute (physical) block numbers, rather than relative to the beginning of the slice.  The "d" partition was then needed to be able to access the other parts of the disk (for example, to update the master boot record).  I don't think even FreeBSD 2.2 (1997) still had this.  On modern systems, container boundaries are enforced strictly.  You could dig through old release notes to see when exactly this changed.  121a0012 (talk) 04:46, 7 June 2012 (UTC)
thread_title:  What was the purpose of "d" 

message: Hello fellow Wikipedians,
I have just modified  on BSD disklabel. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20131224093236/http://www.freebsd.org/cgi/man.cgi?query=disklabel&apropos=0&sektion=5&manpath=4.4BSD+Lite2&format=html to http://www.freebsd.org/cgi/man.cgi?query=disklabel&apropos=0&sektion=5&manpath=4.4BSD+Lite2&format=html
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—InternetArchiveBot (Report bug) 12:52, 23 October 2016 (UTC)
thread_title:  External links modified 

message: My very fuzzy recollection is that the original disklabel work was done in an Australian university (perhaps by Robert Elz) but CSRG reimplemented it from scratch for the 4.3-Tahoe release. 121a0012 (talk) 121a0012 (talk) 04:00, 18 August 2022 (UTC)
thread_title:  Original implementation