headers
Hauke Fath | 23 Nov 2005 14:22
Picon

Sysinst defunct on NetBSD/mac68k - still

Hi,

it seems that NetBSD/mac68k 3 will ship without a working sysinst - 
like 2.0 and 2.1 before it (PR 29049).

If we cannot get sysinst fixed in time -- can we at least document 
the manual workaround along the lines of 
http://mail-index.netbsd.org/port-mac68k/2005/05/19/0003.html in a 
prominent place in the 3.0 release notes?

	hauke

--

-- 
/~\  The ASCII Ribbon Campaign                    Hauke Fath
\ /    No HTML/RTF in email	        Institut für Nachrichtentechnik
  X     No Word docs in email	                  TU Darmstadt
/ \  Respect for open standards              Ruf +49-6151-16-3281
Permalink | Reply | 10 comments |
headers
David Laight | 23 Nov 2005 21:24
Picon

Re: Sysinst defunct on NetBSD/mac68k - still

On Wed, Nov 23, 2005 at 02:22:32PM +0100, Hauke Fath wrote:
> Hi,
> 
> it seems that NetBSD/mac68k 3 will ship without a working sysinst - 
> like 2.0 and 2.1 before it (PR 29049).
> 
> If we cannot get sysinst fixed in time -- can we at least document 
> the manual workaround along the lines of 
> http://mail-index.netbsd.org/port-mac68k/2005/05/19/0003.html in a 
> prominent place in the 3.0 release notes?

Someone with a mac68k needs to sit down and sort out what is wrong.
I don't have one.

	David

--

-- 
David Laight: david <at> l8s.co.uk
Permalink | Reply | 2 comments |
headers
Hauke Fath | 23 Nov 2005 21:53
Picon

Re: Sysinst defunct on NetBSD/mac68k - still

At 20:24 Uhr +0000 23.11.2005, David Laight wrote:
>> If we cannot get sysinst fixed in time -- can we at least document
>> the manual workaround along the lines of
>> http://mail-index.netbsd.org/port-mac68k/2005/05/19/0003.html in a
>> prominent place in the 3.0 release notes?
>
>Someone with a mac68k needs to sit down and sort out what is wrong.
>I don't have one.

Fair enough.

I was planning to tackle sysinst, now that Chuck Silvers' fixes provide me
with a working netbsd-2 Quadra 700. But there is a learning curve ahead, so
it's not going to happen for NetBSD 3.

Still, for bor both the newbies and the remaining faithful in port-mac68k,
it would be nice to have a workaround "standard procedure" in the install
docs.

	hauke

--
"It's never straight up and down"     (DEVO)
Permalink | Reply | 2 comments |
headers
William Duke | 23 Nov 2005 23:26
Picon
Favicon

Re: Sysinst defunct on NetBSD/mac68k - still


> From: Hauke Fath <hauke <at> Espresso.Rhein-Neckar.DE>
> Date: Wed, 23 Nov 2005 21:53:29 +0100
> To: David Laight <david <at> l8s.co.uk>
> Cc: Hauke Fath <hf <at> spg.tu-darmstadt.de>, port-mac68k <at> NetBSD.org,
> tech-install <at> NetBSD.org
> Subject: Re: Sysinst defunct on NetBSD/mac68k - still
> 
> At 20:24 Uhr +0000 23.11.2005, David Laight wrote:
>>> If we cannot get sysinst fixed in time -- can we at least document
>>> the manual workaround along the lines of
>>> http://mail-index.netbsd.org/port-mac68k/2005/05/19/0003.html in a
>>> prominent place in the 3.0 release notes?
>> 
>> Someone with a mac68k needs to sit down and sort out what is wrong.
>> I don't have one.
> 
> Fair enough.
> 
> I was planning to tackle sysinst, now that Chuck Silvers' fixes provide me
> with a working netbsd-2 Quadra 700. But there is a learning curve ahead, so
> it's not going to happen for NetBSD 3.
> 
> Still, for bor both the newbies and the remaining faithful in port-mac68k,
> it would be nice to have a workaround "standard procedure" in the install
> docs.
> 
> hauke
> 
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Nestor | 24 Nov 2005 02:35
Picon

Re: Sysinst defunct on NetBSD/mac68k - still

On Nov 23, 2005, at 2:24 PM, David Laight wrote:

> On Wed, Nov 23, 2005 at 02:22:32PM +0100, Hauke Fath wrote:
>> Hi,
>>
>> it seems that NetBSD/mac68k 3 will ship without a working sysinst -
>> like 2.0 and 2.1 before it (PR 29049).
>>
>> If we cannot get sysinst fixed in time -- can we at least document
>> the manual workaround along the lines of
>> http://mail-index.netbsd.org/port-mac68k/2005/05/19/0003.html in a
>> prominent place in the 3.0 release notes?
>
> Someone with a mac68k needs to sit down and sort out what is wrong.
> I don't have one.

Sysinst for mac68k was originally written to 1)Help the "NetBSD/Mac"  
novice partition the disk for NetBSD, and 2)Update the Apple Disk  
Partition Map to accommodate the user's partition selections.  At the  
time only the i386 port had a mechanism in sysinst for assisting the  
user in partitioning the disk.  I attempted to pattern mac68k/sysinst  
after that scheme as close as possible and embedded the Apple Disk  
Map handling inside that code.  Somewhere around the time of NetBSD  
2.0 an effort was made to generalize the disk partitioning in sysinst  
so that it would support many of the other ports.  Unfortunately  
those changes changed a lot of the things that mac68k/sysinst was  
depending on (the sysinst "API") and unfortunately mac68k wasn't  
supported in the updated sysinst partitioning scheme - mainly because  
of the special things that it had to do to handle the Apple Disk  
Partition Map.  Unfortunately I didn't have time to work out the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Volker A. Brandt | 28 Nov 2005 17:33
Picon

(unknown)

Hello all!

I don't know if it is just me, if it is sparc-related or a generic
sysinst problem.

Anyway, here goes:  I wanted to do a complete installation of NetBSD 2.1
(off of a release CD image).  Target is an SS20 with two identical 9 GB
disks like so:

sd0 at scsibus0 target 1 lun 0: <FUJITSU, MAB3091S SUN9.0G, 1705> disk fixed
sd0: 8637 MB, 4926 cyl, 27 head, 133 sec, 512 bytes/sect x 17689267 sectors
sd0: sync (100.00ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing
sd1 at scsibus0 target 3 lun 0: <FUJITSU, MAB3091S SUN9.0G, 1705> disk fixed
sd1: 8637 MB, 4926 cyl, 27 head, 133 sec, 512 bytes/sect x 17689267 sectors
sd1: sync (100.00ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing

Boot is via network from an Ultra5 running Solaris.  The SS20 boots fine
as usual; after all it's called *Net*BSD :-)

So sysinst does it's thing:

 NetBSD uses a BSD disklabel to carve up the NetBSD portion of the disk into
 multiple BSD partitions.  You must now set up your BSD disklabel.

 You can use a simple editor to set the sizes of the NetBSD partitions, or
 keep the existing partition sizes and contents.

 You will then be given the opportunity to change any of the disklabel fields.

 The NetBSD part of your disk is 8633 Megabytes.  A full installation requires
(Continue reading)

Permalink | Reply | 8 comments |
headers
Volker A. Brandt | 28 Nov 2005 21:16
Picon

newfs problems w/sysinst (2.1 release) on Sun SS20

[No, you're not seeing double.  Sorry for re-sending this but I got
 immediately pounced on by people with astute detection capabilities 
 who pointed out that I had stupidly forgotten to add a Subject line...]

Hello all!

I don't know if it is just me, if it is sparc-related or a generic
sysinst problem.

Anyway, here goes:  I wanted to do a complete installation of NetBSD 2.1
(off of a release CD image).  Target is an SS20 with two identical 9 GB
disks like so:

sd0 at scsibus0 target 1 lun 0: <FUJITSU, MAB3091S SUN9.0G, 1705> disk fixed
sd0: 8637 MB, 4926 cyl, 27 head, 133 sec, 512 bytes/sect x 17689267 sectors
sd0: sync (100.00ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing
sd1 at scsibus0 target 3 lun 0: <FUJITSU, MAB3091S SUN9.0G, 1705> disk fixed
sd1: 8637 MB, 4926 cyl, 27 head, 133 sec, 512 bytes/sect x 17689267 sectors
sd1: sync (100.00ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing

Boot is via network from an Ultra5 running Solaris.  The SS20 boots fine
as usual; after all it's called *Net*BSD :-)

So sysinst does it's thing:

 NetBSD uses a BSD disklabel to carve up the NetBSD portion of the disk into
 multiple BSD partitions.  You must now set up your BSD disklabel.

 You can use a simple editor to set the sizes of the NetBSD partitions, or
 keep the existing partition sizes and contents.
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Laight | 28 Nov 2005 23:15
Picon

Re: problems with newfs on sparc during instal:x

On Mon, Nov 28, 2005 at 05:33:20PM +0100, Volker A. Brandt wrote:
> 
> # newfs -O 2 -b  8192 -f 1024 /dev/rsd0f
> newfs: maximum file system size on `/dev/rsd0f' is 1048572 sectors

Hum... that can't easily fail.
The kernel must be returning incorrect values somewhere!

Possibly the size being returned by fstat()

	David

--

-- 
David Laight: david <at> l8s.co.uk
Permalink | Reply | 6 comments |
headers
Volker A. Brandt | 1 Dec 2005 10:29
Picon

Re: problems with newfs on sparc during instal:x

Thanks for your reply, David.

>> # newfs -O 2 -b  8192 -f 1024 /dev/rsd0f
>> newfs: maximum file system size on `/dev/rsd0f' is 1048572 sectors
>
> Hum... that can't easily fail.
> The kernel must be returning incorrect values somewhere!

This only fails when executed from sysinst.  Typed into the
shell, it works fine.

Regards -- Volker
--

-- 
------------------------------------------------------------------------
Volker A. Brandt                  Consulting and Support for Sun Solaris
Brandt & Brandt Computer GmbH              WWW: http://www.bb-c.de/~vab/
Meckenheim, Germany                                   Email: vab <at> bb-c.de
Permalink | Reply | 4 comments |
headers
David Laight | 1 Dec 2005 22:32
Picon

Re: problems with newfs on sparc during instal:x

On Thu, Dec 01, 2005 at 10:29:33AM +0100, Volker A. Brandt wrote:
> Thanks for your reply, David.
> 
> >> # newfs -O 2 -b  8192 -f 1024 /dev/rsd0f
> >> newfs: maximum file system size on `/dev/rsd0f' is 1048572 sectors
> >
> > Hum... that can't easily fail.
> > The kernel must be returning incorrect values somewhere!
> 
> This only fails when executed from sysinst.  Typed into the
> shell, it works fine.

I thought you'd managed to get it to fail whne typed in at the shell.
In any case sysinst execs disklabel to write the label and then newfs,
so it is unlikely that sysinst itself it at fault.

I've changed the error message (on head) so that it includes both sizes.
So at least there will be some extra info!

There was a problem with an uninitialised structure (from which a size
could have been taken) - but that was fixed before netbsd 2.0.

	David

--

-- 
David Laight: david <at> l8s.co.uk
Permalink | Reply | 2 comments |

Gmane