On Sun, 12 Aug 2012 20:50:43 -0600, Brett Glass wrote:
Everyone:
Just ran freebsd-update (fetch, then install) on a system on which
I run a customized kernel, and discovered that it has overwritten
my custom kernel... even though I'd copied the original to
/boot/GENERIC when I first
At 05:24 AM 8/13/2012, Polytropon wrote:
That seems to be the default behaviour, as freebsd-update is
not supposed to be used with a custom kernel. It works with
GENERIC kernels (because it updates them by overwriting).
Actually, freebsd-update is claimed to respect custom kernels. See
the
On Mon, Aug 13, 2012 at 9:35 AM, Brett Glass br...@lariat.net wrote:
Actually, freebsd-update is claimed to respect custom kernels. ...
And it does, in my experience. If the hash of the kernel doesn't
match that of the distribution (or recent update), freebsd-update
leaves it alone.
On Mon, 13 Aug 2012 10:35:12 -0600, Brett Glass wrote:
At 05:24 AM 8/13/2012, Polytropon wrote:
That seems to be the default behaviour, as freebsd-update is
not supposed to be used with a custom kernel. It works with
GENERIC kernels (because it updates them by overwriting).
Actually,
At 11:33 AM 8/13/2012, Michael Sierchio wrote:
And it does, in my experience. If the hash of the kernel doesn't
match that of the distribution (or recent update), freebsd-update
leaves it alone.
That is what I thought it would do, based on the docs. However,
when I recently ran
At 12:59 PM 8/13/2012, Polytropon wrote:
I've never seen a system having a /boot/GENERIC directory
containing the GENERIC kernel.
It does not come that way. The Handbook recommends that one
manuall copy the original kernel from the distribution into
/boot/GENERIC before building a custom
On Mon, Aug 13, 2012 at 1:07 PM, Brett Glass br...@lariat.net wrote:
At 11:33 AM 8/13/2012, Michael Sierchio wrote:
And it does, in my experience. If the hash of the kernel doesn't
match that of the distribution (or recent update), freebsd-update
leaves it alone.
That is what I thought it
Everyone:
Just ran freebsd-update (fetch, then install) on a system on which
I run a customized kernel, and discovered that it has overwritten
my custom kernel... even though I'd copied the original to
/boot/GENERIC when I first installed the system. I was under the
impression that creating
