At 22:06 13/08/2011, Steven Hartland wrote:
- Original Message - From: Alexander Best arun...@freebsd.org
i just had the following idea: how about instead of copying the
current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target
Eduardo Morras nec...@retena.com writes:
At 22:06 13/08/2011, Steven Hartland wrote:
i just had the following idea: how about instead of copying the
current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique
Test Rat ttse...@gmail.com writes:
Eduardo Morras nec...@retena.com writes:
At 22:06 13/08/2011, Steven Hartland wrote:
i just had the following idea: how about instead of copying the
current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as
the
results
On Sun Aug 14 11, Test Rat wrote:
Test Rat ttse...@gmail.com writes:
Eduardo Morras nec...@retena.com writes:
At 22:06 13/08/2011, Steven Hartland wrote:
i just had the following idea: how about instead of copying the
current kernel
to /boot/kernel.old and then installing the new one
On Sat, Aug 13, 2011 at 12:51 PM, Alexander Best arun...@freebsd.orgwrote:
hi there,
i just had the following idea: how about instead of copying the current
kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as
the
results of target installkernel, we create
On Sun, Aug 14, 2011 at 10:56 AM, Freddie Cash fjwc...@gmail.com wrote:
On Sat, Aug 13, 2011 at 12:51 PM, Alexander Best arun...@freebsd.orgwrote:
hi there,
i just had the following idea: how about instead of copying the current
kernel
to /boot/kernel.old and then installing the new one
Freddie Cash fjwc...@gmail.com writes:
On Sat, Aug 13, 2011 at 12:51 PM, Alexander Best arun...@freebsd.orgwrote:
hi there,
i just had the following idea: how about instead of copying the current
kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as
the
results
On 8/14/11 3:27 AM, Eduardo Morras wrote:
At 22:06 13/08/2011, Steven Hartland wrote:
- Original Message - From: Alexander Best
arun...@freebsd.org
i just had the following idea: how about instead of copying the
current kernel
to /boot/kernel.old and then installing the new one under
of copying the current
kernel
to /boot/kernel.old and then installing the new one under /boot/kernel
as
the
results of target installkernel, we create a unique directory name for
the
old
kernel?
something like /boot/kernel-r${revision}-${/dev/random}?
that would let people
hi there,
i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique directory name for the old
kernel?
something like /boot/kernel-r${revision
On 13 August 2011 20:51, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique
On Sat Aug 13 11, Chris Rees wrote:
On 13 August 2011 20:51, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current
kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as
the
results
On Aug 13, 2011, at 12:51 PM, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique
On Sat Aug 13 11, Garrett Cooper wrote:
On Aug 13, 2011, at 12:51 PM, Alexander Best arun...@freebsd.org wrote:
hi there,
i just had the following idea: how about instead of copying the current
kernel
to /boot/kernel.old and then installing the new one under /boot/kernel
- Original Message -
From: Alexander Best arun...@freebsd.org
i just had the following idea: how about instead of copying the current kernel
to /boot/kernel.old and then installing the new one under /boot/kernel as the
results of target installkernel, we create a unique directory name
/kernel.old and then installing the new one under /boot/kernel as
the
results of target installkernel, we create a unique directory name for the
old
kernel?
something like /boot/kernel-r${revision}-${/dev/random}?
that would let people not only boot the previous kernel, but all kernels
As Chuck Robey wrote ...
I was thinking about Peter Wemm's recent change to the kernel Makefile,
making a way to install multiple kernels without fragging your last
known good kernel, and it got me to thinking, scragging kernel.old, now
that we have good kld's, isn't the only way to find
I was thinking about Peter Wemm's recent change to the kernel Makefile,
making a way to install multiple kernels without fragging your last
known good kernel, and it got me to thinking, scragging kernel.old, now
that we have good kld's, isn't the only way to find yourself well and
truly screwed
In message pine.bsf.4.10.9905091608060.401-100...@picnic.mat.net, Chuck Robe
y writes:
Something on the order of modules.old is going to need to
be implemented.
Not to mention /boot/kernel.old.config ...
I think you are seeing -current as the norm. You shouldn't. Under
-stable the modules
Something on the order of modules.old is going to need to
be implemented.
Not to mention /boot/kernel.old.config ...
I think you are seeing -current as the norm. You shouldn't. Under
-stable the modules should (tm) continue to work since there are not
made API changes in -stable.
BUT
I wish :-(
It seems that some people think that it is OK to make changes to stable
even though those changes break things which used to work.
IMHO, branches of the kernel SHOULD be like shared libraries.
(It is OK to ADD previously absent features or CORRECT internal errors,
but NOT OK to delete
21 matches
Mail list logo
