I'm running the binary release version of 1.2. Not having a network boot  
and having run out of disk space so far all I've been able to upgrade
is  the kernel, boot block and core system binaries ( as soon as I can
label this disk I plan to make it bootable and put the full current
release on it, downloading over a modem is kind of painful :-( ).

df seems to show nothing put my main disk in use:

Filesystem  512-blocks     Used    Avail Capacity  Mounted on
/dev/sd0a        29430    27048      910    97%    /
/dev/sd0e       179366   159658    10738    94%    /usr
/dev/sd0f        29754     4620    23646    16%    /var
/dev/sd0g       270032   257308     -778   100%    /local


Any ideas? Did the fix Jason refers to happen after 1.2 was released?

Thanks Tony





On Tue, 8 Apr 1997, Jason Thorpe wrote:

> On Tue, 8 Apr 1997 18:12:55 +0100 (BST) 
>  Tony Povoas <tony@ing.iac.es> wrote:
> 
>  > I'm now getting errors that the disk is read only which is news to me! Any
>  > other ideas? ( I've tried disklabel -W)
> 
> ...which revision are you running?  -current?
> 
> For the record, I'm NOT able to reproduce these problems.  The proper
> way to initialize a disklabel for the first time is to create a label
> (you can do this by running disklabel sd1 > foo, editing foo, then
> running disklabel -W sd1; disklabel -r -R sd1 foo).
> 
>  > dd if=/dev/rsd0c of=/dev/rsd1c count=3
>  > Dec  9 13:55:35 marat /netbsd: sd1: WARNING: no disk label, using old
>  > default partitioning
>  > dd: /dev/rsd1c: Read-only file system
>  > 3+0 records in
>  > 2+0 records out
>  > 1024 bytes transferred in 1 secs (1024 bytes/sec)
>  > 
>  > After that disklabel -r reports no label on the disk :-(
> 
> ...right... it's not letting you write over the label area for some
> reason.  However, I had fixed this, I thought...
> 
> Please make sure you have arch/hp300/dev/sd.c revision:
> 
> 	$NetBSD: sd.c,v 1.29 1997/01/30 09:14:20 thorpej Exp $
> 
> Folks ... when reporting problems, it is _vitally_ important that you
> include all relevant information, including revisions of source
> files for relevant drivers, uname output, etc.  It's almost impossible
> to determine what's actually going on otherwise.
> 
> Jason R. Thorpe                                       thorpej@nas.nasa.gov
> NASA Ames Research Center                               Home: 408.866.1912
> NAS: M/S 258-6                                          Work: 415.604.0935
> Moffett Field, CA 94035                                Pager: 415.428.6939
>