Re: preparing netbsd boot straps from gnu/linux

[pierre-philipp braun <pbraun%nethence.com@localhost>]

> Please explain more thoroughly what you are doing.  That makes it seem
> like you are loading the kernel from a FAT32 partition, and I can't tell
> how many partitions of what kind you have and why.

I am trying to setup netbsd from gnu/linux, which means no `installboot`
nor `disklabel` commands (unless I try to cross-compile those).

This is an EXT2 partition, not FAT32.  This is a 1TB drive and I create
a single 25GB NetBSD (a9) partition on it.  I could also use the entire
disk.  And I try to get it used as root filesystem.  Hence `wd0c` or
`wd0e`.  But only the latter works, as is recognized automatically by
netbsd and has the 4.2BSD fstype.

I did not try to do this from FreeBSD yet.

> wd0c is the alias for the entire NetBSD fdisk partition.  wd0d for the
> entire physical disk.  It does not make sense to have a fs on wd0c.  If
> you wanted that, you'd use the a or e slot with the same values, with a
> netbsd fs type code.

yes this is what I do: trying to fsck and mount wd0e.

> I am not following.  please be much clearer about what you are doing and
> where the output is coming from.  I realize that you are posting the
> part that you think is interesting, but the missing expected values are
> critical context for others.

Sorry, that output is coming from a the freshly
netbsd-installed-system-from-a-gnu/linux-environment.  And it fails at
fsck_ext2fs at boot time and when done manually.  I get into single user
mode with that wd0e ext2fs mounted ro as /.  I can eventually switch to
rw.  But fsck_ext2fs is not happy with the gnu/linux `mkfs.ext2
-O^dir_index` filesystem.  This may actually be a bug.

> netbsd 8 GENERIC on amd64 does.

And yes there is no difference in the behaviour when loading netbsd
without the ext2fs kmod.  It mounts it ro but refuses to fsck_ext2fs it.