Subject: Re: port-hp300/17710
To: None <port-hp300-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
List: netbsd-bugs
Date: 03/21/2006 06:45:05
The following reply was made to PR port-hp300/17710; it has been noted by GNATS.

From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
To: gnats-bugs@NetBSD.org
Cc: michael@nosflow.com, tsutsui@ceres.dti.ne.jp
Subject: Re: port-hp300/17710
Date: Tue, 21 Mar 2006 15:44:48 +0900

 > A) does not generate valid default labels.  This prevents sysinst
 > from working correctly (plus it's really annoying when creating 
 > a new label by hand)
  :
 > A) run sysinst and use anything other than "use existing" label,
 >  for example I chose "Standard with X", and this is what it came up with:
 >  We now have your BSD-disklabel partitions as (Size and Offset in MB):
 
 I think this has been fixed in hp300/disksubr.c rev 1.21
 though sysinst has been fixed to generate proper default
 partitions without this fix.
 
 > B) miniroot is unable to label a new disk (one without a label).
  :
 > B) Run miniroot, and edit the label on your new disk.  When done, it says:
 > disklabel: ioctl DIOCWDINFO: No disk label on disk;
 > use "disklabel -I" to install initial label
 > re-edit the label? [y]:
 
 I haven't tried -current miniroot yet, but the boot disk which
 contains miniroot should have a valid disklabel at the moment,
 shouldn't it?
 
 > C) does not properly deal with hp300 bootloader.  See the comments
 > in the basesrc/distrib/hp300/miniroot/install.md
 > 
 > 
 > # because
 > 	# of limitations in disklabel(8), we've had to fudge the number
 > 	# of cylinders up 1 so that disklabel(8) doesn't complain about
 > 	# `c' running past the end of the disk, which can be quite
 > 	# common even with OEM HP drives!
  :
 > C) Try creating a disklabel by hand from the drive's physical info
 >  and writing it to the disk.
 
 Could you please mention your problem more specific?
 
 On hp300, its bootloader is larger than 8KB, so we have to
 prepare space for it in disklabel explicitly. Is it your problem?
 Or are you saying about the "disklabel(8) limitations"?
 (though I'm not sure what is the limitation)
 Or you just claim that the install.md script should be fixed?
 ---
 Izumi Tsutsui