Re: bin/49510: gpt(8) fails w/o drvctl and breaks sysinst

[John Nemeth <jnemeth%cue.bc.ca@localhost>]

The following reply was made to PR bin/49510; it has been noted by GNATS.

From: John Nemeth <jnemeth%cue.bc.ca@localhost>
To: gnats-bugs%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost,
        martin%NetBSD.org@localhost
Cc: 
Subject: Re: bin/49510: gpt(8) fails w/o drvctl and breaks sysinst
Date: Mon, 29 Dec 2014 22:10:07 -0800

 On Dec 30,  5:00am, Masao Uebayashi wrote:
 }
 } The following reply was made to PR bin/49510; it has been noted by GNATS.
 } 
 } From: Masao Uebayashi <uebayasi%gmail.com@localhost>
 } To: gnats-bugs%netbsd.org@localhost
 } Cc: 
 } Subject: Re: bin/49510: gpt(8) fails w/o drvctl and breaks sysinst
 } Date: Tue, 30 Dec 2014 13:59:08 +0900
 } 
 }  On Tue, Dec 30, 2014 at 6:03 AM, Christos Zoulas <christos%zoulas.com@localhost> wrote:
 }  > Consider stat'ing /dev/nrst0. Do you really want it to return the
 }  > size?
 }  
 }  I'd expect it to return the physical disk size in bytes.
 
      That's a tape, not a disk.  And, if you say you want the
 capacity, how are you going to determine it?
 
 }  > Or /dev/rcd0a, what's the size? Is it the capacity? Or the
 }  > current amount of data written? What if it's unformatted? Or even
 }  > on regular disks, the size can be iffy... If you return sectors *
 }  > secperunit, are you sure you can write that many bytes (what about
 }  > bad sectors)?
 }  
 }  I'd expect it to return the physical partition size in bytes, no
 }  matter if it's impossible to write that many bytes.
 
      For a disk, I would agree.  A CD though is different.  Do you
 return the full capacity, or the amount currently.  How do you
 handle a CD-RW versus a CD-R?  For the latter, is the result
 different if it's blank?
 
 }-- End of excerpt from Masao Uebayashi