Date: Sat, 11 Feb 2012 13:40:41 +0100 From: Thierry Thomas <thierry@FreeBSD.org> To: stable@FreeBSD.org Subject: Re: Reducing the need to compile a custom kernel Message-ID: <20120211124041.GF32360@graf.pompo.net> In-Reply-To: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--zS7rBR6csb6tI2e1 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Le ven 10 f=E9v 12 =E0 14:56:04 +0100, Alexander Leidinger <Alexander@Leidi= nger.net> =E9crivait=A0: > Hi, Hello, > The question is, is this enough? Or asked differently, why are you > compiling a custom kernel in a production environment (so I rule out > debug options zhich are not enabled in GENERIC)? Are there options > which you add which you can not add as a module (SW_WATCHDOG comes to > my mind)? If yes, which ones and how important are they for you? Not very important, but since you are asking, is there another place to put options to atkbd and sc, like these ones: options ATKBD_DFLT_KEYMAP # specify the built-in keymap makeoptions ATKBD_DFLT_KEYMAP=3Dfr.iso.acc options SC_KERNEL_CONS_ATTR=3D(FG_LIGHTGREEN|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=3D(FG_WHITE|BG_GREEN) options SC_NORM_REV_ATTR=3D(FG_WHITE|BG_BLUE) Regards, --=20 Th. Thomas. --zS7rBR6csb6tI2e1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk82YckACgkQc95pjMcUBaK23QCgyugS83G44AQKM+5eWN9TTw5G VAMAn2c31WkiB8P2HSWyiFQJwD2uMslI =4yER -----END PGP SIGNATURE----- --zS7rBR6csb6tI2e1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120211124041.GF32360>