--ZGiS0Q5IWpPtfppv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Apr 30, 2013 at 04:41:03PM -0600, Brett Glass wrote:
> At 03:15 PM 4/30/2013, Glen Barber wrote:
>=20
> >Let's start from the beginning. What is the name of your custom kernel?
>=20
> The file name of the compiled kernel? The file name of the configuration =
file?
> Or the identification string within the kernel?
>=20
Yes. (All of them.)
> The file name is, of course, /boot/kernel/kernel. It's built without
> modules, so
> it's the only file in the directory /boot/kernel.
>=20
> The configuration file is at /sys/amd64/conf/GATEWAY.
>=20
> The identification string within the kernel is GATEWAY.
>=20
> I am not sure what you're driving at here, though, so please explain.
>=20
What I was getting at is seeing if you had a custom kernel called
GENERIC, despite the vast amounts of documentation noting that GENERIC
should _not_ be modified to customize the kernel.
So, since I know you're not new to FreeBSD, if you feel there is a bug
somewhere, please file a PR. I disagree that there is a problem,
however, since users building a custom kernel should _not_ use
freebsd-update(8) for kernel upgrades.
Glen
--ZGiS0Q5IWpPtfppv
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iQEcBAEBCAAGBQJRgEpSAAoJEFJPDDeguUajWz4H/jLPw4+qwDGL0olN1EDgr1U0
Y20jp4hiTul5pUaFff57sa71MhgPPpa3yiT/D3PaSf33eLyi+jkK9xcD1k1ShqZZ
VneTPq382qFZTsPVi7eBGFxRr3Q6cvO8MfqPg/bbvQ7Yw1Dojul2z/rHLeVxW6SM
9aWPnht6ubVe/qVEEON30ggvkQk+sh6py42+eBszRWU2ozI7A9PsnmWkcgt2OjB7
5QIU8815dXrQBoI4cSlx9jMgSYGh5tkmpDWn89fMNzLyps0m9/FWT3hwnRzcQakZ
ARt39VOClQ+HHq1/0kS1Sa4oUVSu8tQivUtR0dqsFWaAI8YjxzrMzjQJ0NCtn40=
=hirH
-----END PGP SIGNATURE-----
--ZGiS0Q5IWpPtfppv--