ad 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?
> &g
On 8/14/11 3:27 AM, Eduardo Morras wrote:
At 22:06 13/08/2011, Steven Hartland wrote:
- Original Message - From: "Alexander Best"
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
Freddie Cash writes:
> On Sat, Aug 13, 2011 at 12:51 PM, Alexander Best 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/k
On Sun, Aug 14, 2011 at 10:56 AM, Freddie Cash wrote:
> On Sat, Aug 13, 2011 at 12:51 PM, Alexander Best wrote:
>
>> hi there,
>>
>> i just had the following idea: how about instead of copying the current
>> kernel
>> to /boot/kernel.old and then installi
On Sat, Aug 13, 2011 at 12:51 PM, Alexander Best 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 installkerne
On Sun Aug 14 11, Test Rat wrote:
> Test Rat writes:
>
> > Eduardo Morras writes:
> >
> >> At 22:06 13/08/2011, Steven Hartland wrote:
> >>>> i just had the following idea: how about instead of copying the
> >>>> current kernel
> &
Test Rat writes:
> Eduardo Morras 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
Eduardo Morras 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 t
At 22:06 13/08/2011, Steven Hartland wrote:
- Original Message - From: "Alexander Best"
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 install
On Aug 13, 2011, at 1:15 PM, Alexander Best wrote:
> On Sat Aug 13 11, Garrett Cooper wrote:
>> On Aug 13, 2011, at 12:51 PM, Alexander Best wrote:
>>
>>> hi there,
>>>
>>> i just had the following idea: how about instead of copying the current
&
- Original Message -
From: "Alexander Best"
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 f
On Sat Aug 13 11, Garrett Cooper wrote:
> On Aug 13, 2011, at 12:51 PM, Alexander Best 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 ne
On Aug 13, 2011, at 12:51 PM, Alexander Best 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 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/
On 13 August 2011 20:51, Alexander Best 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 dir
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
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&
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
> >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 -stab
In message , 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 should (tm) continue to work since there are not
made A
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
t
21 matches
Mail list logo
