Subject: Re: New kernel behavior [was] Re: z50 TrackPoint driver for CVS...
To: Andrew Diller <dillera@sudanacid.com>
From: Greg Hughes <gl2hughes@uwaterloo.ca>
List: port-hpcmips
Date: 04/06/2002 07:03:38
Actually, this isn't entirely true anymore.  pbsdboot will let you boot
directly off of a netbsd partition.  I'm currently using:

  1:/netbsd

as my kernel image to pbsdboot, and it reads it right off of the wd0a
bsd partition.  I'm not entirely sure how the numbering works, but I
think it may represent the partition number.

I'll try to find out where I originally saw this to get more details.

- Greg

On Sat, Apr 06, 2002 at 12:48:08AM -0500, Andrew Diller wrote:
> I believe this is due to not copying the new kernel to /netbsd.
> 
> Remember you have to install the kernel in both the wince partition (for 
> the initial boot) and also on your netbsd /, so that when netbsd reboots 
> and boots from /netbsd its using the new kernel, not the one you got from 
> the 1.5 installation procedure.
> 
> I did this once, before I realized what was happening.
> 
> This explains both your symptoms.
> 
> -andy
> 
> --On Friday, April 05, 2002 3:49 PM -0500 billy ball <bball@tux.org> wrote:
> 
> > 4. using:
> >
> > shutdown -r now
> >
> > results in a reboot back to NetBSD, but with a white console (black text
> > on white); is there some way to create a persistent setting for white
> > text  on a black screen?
> > 5. while in the white console, LCD screen blanking does not work
> > 6. using:
> >
> > shutdown -h now
> >
> > from white console results in a reboot back to WinCE