Re: Tracking NetBSD-current without burning bridges on release/stable version?

[Michael <macallan%netbsd.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Nov 15, 2010, at 10:10 PM, Thomas Mueller wrote:

> How can one who already has a stable/release version of NetBSD  
> installed track NetBSD-current without destroying the stable/release  
> installation?
>
> Using a separate disk, this would be a trivial question, but my  
> question is if it is possible to do this on a single hard disk.
>
> NetBSD disklabel is one for the entire disk as opposed to the NetBSD  
> slice, and I believe (installboot) bootxx image has to be on  
> partition a?

Different kernel in a different file? With a different root hard-coded  
for convenience?

> Two items of interest in NetBSD 6.0-current are improved ext2fs  
> access, and genfb replacing possibly buggy (as in PR 41214) vesafb.

That's kernel stuff, with the right compat options a -current kernel  
should run most or all of an older userland ( I forgot where the  
threading code changed, I /think/ it was from 4.0 to 5.0, that's where  
backwards compatibility breaks, for threaded binaries only though.  
Then there's the more recent switch to 64bit time_t but that wouldn't  
bite you if you're running amd64 )

Either way, if you just want to check out some kernel driver  
improvements just build a -current kernel with COMPAT_50 or whatever  
matches your userland and run it.

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBTOH3vcpnzkX8Yg2nAQKb1ggAsrNaTgi1DF8yPPV5PM3aZmtNLyVmSC7S
mV9oXQRbnJ843MK69dEkQ9rzSpfxf6CNyEgjyH5NenCv2/j8yyOqRBG03dW+nSbz
viMZfkChIvxHGJr1iKyQdbf1hF3+Y1kCnHkdjVOzPrdQl3yb7/MR8S7ktc8CdmN6
vc5asx/P3uKoy5D92es45EG2/0aCRL2VY4yjuaRNb+IFfNehkEQhZlV5ugpT7Iqa
tMi7RonrhbtnX1Wi/UaHG4fYhKos6imroOjCbeU3Nw3BRZ8VjNgaLTqt8PQT5R1G
PDzNNZgQ7n24Ps8pDMJBaU3JHEQKWBXCb2EjusvY3jKA6rnL8JlMEw==
=ziTl
-----END PGP SIGNATURE-----