LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
Yes, that would be very useful. But it should also take
any includes into account.
It was very annoying to discover that INCLUDE_CONFIG_FILE
gave me only two lines for
Oliver Fromme wrote:
LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
Yes, that would be very useful. But it should also take
any includes into account.
It was very annoying to discover that INCLUDE_CONFIG_FILE
LI Xin wrote:
Oliver Fromme wrote:
LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
Yes, that would be very useful. But it should also take
any includes into account.
It was very annoying to
I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
verify that this is and track down what changed! I don't think it should
ever be
Pete French wrote:
I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
verify that this is and track down what changed! I don't
On Mon, 19 Mar 2007 11:31:54 +
Pete French [EMAIL PROTECTED] wrote:
I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
I think you will want RELENG_6_2_0_RELEASE.
thanks (and to the others who responded)
What happens with RELENG_6_2, IIRC there was only very limited changes
to kernel which should only affect IPv6...
Indeed! Part of the reason I want to do the revert is to make absolutely
sure that it runs
Pete French wrote:
I think you will want RELENG_6_2_0_RELEASE.
thanks (and to the others who responded)
What happens with RELENG_6_2, IIRC there was only very limited changes
to kernel which should only affect IPv6...
Indeed! Part of the reason I want to do the revert is to make
I think this is a very good idea, I've been caught at least once
not being able to recreate a working kernel due to the loss of
the original config file.
Steve
- Original Message -
From: LI Xin [EMAIL PROTECTED]
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
On Mon, Mar 19, 2007 at 01:33:44PM -, Steven Hartland wrote:
I think this is a very good idea, I've been caught at least once
not being able to recreate a working kernel due to the loss of
the original config file.
Steve
- Original Message -
From: LI Xin [EMAIL PROTECTED]
Wojciech A. Koszek wrote:
On Mon, Mar 19, 2007 at 01:33:44PM -, Steven Hartland wrote:
I think this is a very good idea, I've been caught at least once
not being able to recreate a working kernel due to the loss of
the original config file.
Steve
- Original Message -
From:
- Original Message -
From: Wojciech A. Koszek [EMAIL PROTECTED]
I did some work in this area, as several system administrators I've met
also seem to have problem with kernel configuration recovery. In my case
I came with a method of obtaining a configuration of a running kernel
via
On Mon, Mar 19, 2007 at 02:32:48PM -, Steven Hartland wrote:
- Original Message -
From: Wojciech A. Koszek [EMAIL PROTECTED]
I did some work in this area, as several system administrators I've met
also seem to have problem with kernel configuration recovery. In my case
I came
- Original Message -
From: Wojciech A. Koszek [EMAIL PROTECTED]
Yes, it does. You get full configuration file from sysctl(8) or from
config -k kernel, and config(8) is modified in a way, that lets you to
use this file without additional trimming.
Sounds like a very worth while
If memory serves me right, Pete French wrote:
I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
verify that this is and track
On Mar 19, 2007, at 9:24 AM, LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
ew yucky
What I do is keep my kernel configs in subversion. I have a common
component which applies to all systems under my control,
On Mon, Mar 19, 2007 at 10:23:53PM +0800, LI Xin wrote:
Wojciech A. Koszek wrote:
[..]
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
I did some work in this area, as several system administrators I've met
also seem to have
regression that was introduced late in the 6.2 release cycle. I'm
personally pretty skeptical that this could cause a problem, although
I'm admittedly a little biased, plus there weren't a lot of details in
your email as to what the problem is.
Well, you are right - it wont run a stock
18 matches
Mail list logo
