Unsafe GENERIC? - Re: (unknown)
Alan Barrett a...@cequrux.com writes: On Mon, 15 Mar 2010, Aleksej Saushev wrote: While here, can anyone enlighten us how one boots NetBSD so that it looks for modules in non-default directory? You can't, and the people who want NetBSD to move to modular kernels don't seem to care. Until this problem is fixed, I will try to avoid using modular kernels. Well... Could we arrange it so that we have safe monolithic GENERIC until issues are resolved somehow? It isn't nice to provide highly experimental feature as default one. Until release management is arranged so that drivers are backported faster, users of commodity hardware are forced to use current sometimes. -- HE CE3OH...
Re: Unsafe GENERIC? - Re: (unknown)
On Tue, 16 Mar 2010, Aleksej Saushev wrote: Well... Could we arrange it so that we have safe monolithic GENERIC until issues are resolved somehow? For i386, use MONOLITHIC instad of GENERIC For amd64, the default is still MONOLITHIC, if I remember correctly. - | Paul Goyette | PGP DSS Key fingerprint: | E-mail addresses: | | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net | | Kernel Developer | | pgoyette at netbsd.org | -
Re: Unsafe GENERIC? - Re: (unknown)
Paul Goyette p...@whooppee.com writes: On Tue, 16 Mar 2010, Aleksej Saushev wrote: Well... Could we arrange it so that we have safe monolithic GENERIC until issues are resolved somehow? For i386, use MONOLITHIC instad of GENERIC For amd64, the default is still MONOLITHIC, if I remember correctly. This produces unnecessary confusion and nothing more. Update procedure becomes more machine-dependent. Even on commodity hardware, where some users prefer to stay with i386 because of e.g. WINE and other 32-bit only software. -- HE CE3OH... pgpWIWokP0FMi.pgp Description: PGP signature
