If it's any help, I've been fiddling about with the Installer all =
weekend on a 2.1 GB Fireball. I've tried numerous different partition =
setups (made using a patched HD SC Setup), and they would all cause the =
installer to choke with the error you described _unless_ the NetBSD =
partitions were at the start of the disk (as seen in HD SC Setup, =
anyway). The error you describe would always occur when I attempted to =
make more than 2 dirs. I've had no problems (with the installer, at =
least - I haven't got as far as installing the kernel yet) when the =
NetBSD partitions are at the start of the disk and the number of =
partitions is 8 or less.

Cheers,

/ewen

----------
From:  Ulrich Hausmann[SMTP:ulrich.hausmann@rhein-neckar.netsurf.de]
Sent:  Saturday, September 05, 1998 6:38
To:  Frederick Bruckman
Cc:  port-mac68k@netbsd.org
Subject:  Re: Installation problem

Frederick,

yes, I did that. At a certain point the process stopped with:
| mode =3D 05, inum =3D 1023, fs =3D /
| ialloc: dup alloc

When I first run the installer, I did not notice such, so I presume at
some time, I did something wrong, corrupting the (hopefully originally
correct) installation.

'mount -u /' results:
| mount_ffs: /dev/sd1a on /: No such file or directory=20

Meanwhile, that msg sounds familiar to me :). Anyway, I consider this an
occasion to learn
something. And one consideration comes up to my mind first:

Is the NetBSD filesystem not that robust and solid? While I can accept,
up to a certain point, that MacOS file system isn't that solid, OTOH,
that's widely counterbalanced by the ease of use - at least for me :)).
Now, I'm a bit anxious, whether or not I'm going to suffer similar
experiences with the hd. Shuffling stuff off and on a 4 GB hd isn't that
fun (not even with MacOS!) (?).

Then a practical question, somewhere in the man pages I read there is
way to mount not only ffs but also HFS: Does this mean, I can, without
any add-on, mount a MacOS formatted hd and read in the files there
(copying them then to NetBSD partitions)?=20

I'm sorry, that I'm asking so dumb questions, but until the books I
ordered do not arrive (hoped, in vain, for this weekend) the only
sources are docs and infos gathered somewhere online. And often they
aren't that verbose . . .:)) Without all your help, there would be no
way for me. Thanks!!

Oh, than a final, very curious, may be even foolish, question: I have a
running and well equipped Apple IIGS, with a SCSI adapter in it. Now,
the utilities shipped with that adapter (really, it's in Rom) allow to
format hds not only Prodos (which would be the Apple II standard
format), but also HFS, since GS/OS 6.0.1 has HFS capabilities. Now,
since this formatter does not put any driver partition on the formatted
media (because GS/OS works with a built-in to the OS FST which provides
the driver), would it be an idea to format a media in this way for later
use with NetBSD (or thinkable at all)?

Best regards, Ulrich

----------
>Von: Frederick Bruckman <fb@enteract.com>
>An: Ulrich Hausmann <ulrich.hausmann@rhein-neckar.netsurf.de>
>Cc: Frederick Bruckman <fb@enteract.com>, port-mac68k@netbsd.org
>Betreff: Re: Installation problem
>Datum: Sam, 5. Sep 1998 16:23 Uhr
>

>On Sat, 5 Sep 1998, Ulrich Hausmann wrote:
>
>> I tried and that's what I got using 'mount -u /; cd /dev; .MAKEDEV =
sd1'
>>=20
>> | rm: sd1b (thru rsd1d) Read-only file system
>> | mknod: sd1a Read-only file system
>> | mknod: sd1b (thru rsd1d) file exists
>> | mknod: rsd1e (thru rsd1h) Read-only file system
>> | chgrp: sd1b (thru rsd1d) Read-only file system
>> | chmod: sd1b (thru rsd1d) Read-only file system
>
>That's very odd. Does 'mount -u /' give you an error? That's your
>origninal problem, isn't it, that the root device can't be mounted
>read/write? Have you tried yet, using the installer to make the =
devices?=20
>
>