Subject: Re: netstat problem with ksyms.
To: Pavel Cahyna <firstname.lastname@example.org>
From: Chavdar Ivanov <email@example.com>
Date: 05/28/2006 00:39:43
On 5/27/06, Pavel Cahyna <firstname.lastname@example.org> wrote:
> On Sat, May 27, 2006 at 11:33:46PM +0100, Chavdar Ivanov wrote:
> > >I was successfully booting
> > >NetBSD with GRUB (without chainloading) at least in 1.6. Also, I remem=
> > >that some patches to improve this support were added to pkgsrc quite
> > >recently.
> > >
> > >To use it, you would need:
> > >
> > >- use a command lile kernel --type=3Dnetbsd <path> in grub,
> > >- probably a kernel compiled without MULTIBOOT.
> > I can try that easily.
> You don't have to, it was just a suggestion.
Well, I tried it, and it apparently works. The trouble is the section:
kernel --type=3Dnetbsd /m0 console=3Dpc root=3Dwd0a
in this shape does not seem to pass the root and dump parameters to
the kernel, so they have to be entered by hand (mind you, I had the
splashscreen enabled ... had to reset).
> > >
> > >Chainloading is a better option though.
> > Don't understand why.
> Because the GRUB's support of the native NetBSD boot protocol is limited
> (as I've said, there were some patches to improve this, I don't know the
> current state exactly) and the NetBSD support for the Multiboot protocol
> is also incomplete, as you have seen.
I've had grub with chainloading on this machine (and on two others
previously - the original setup was a few years ago and has been
transfered to two more laptops later, with or without disk change),
but with chainloading; I switched to multiboot around the time it came
about - I believe it to be February this year; the one positive one
can take from this is that one has to be prepared to see strange and
unexpected behaviour when one is running the latest bits of code - but
then, we all know this, don't we?