May be include in GENERIC option INCLUDE_CONFIG_FILE?
Alex Keda
managers who have inherited a server "by inheritance" is often the
question arises - where to find the configuration file in which to
compile your kernel? (Of course, a file by that time there =))
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Doug Barton
> For those who have recently engaged in FreeBSD, and inexperienced
> managers who have inherited a server "by inheritance" is often the
> question arises - where to find the configuration file in which to
> compile your kernel? (Of course, a file by that time there =))
I actually thought that was already done, but I see now that it's not.
I would like to see this as well, any objections?
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Wojciech A. Koszek
> Alex Keda wrote:
> > For those who have recently engaged in FreeBSD, and inexperienced
> > managers who have inherited a server "by inheritance" is often the
> > question arises - where to find the configuration file in which to
> > compile your kernel? (Of course, a file by that time there =))
>
> I actually thought that was already done, but I see now that it's not.
> I would like to see this as well, any objections?
>
>
Alex, Doug,
In the past, I got two kinds of responses to this question:
1) "OK" from most of the people
>From the kernel via config(8) you can get a ready-to-use configuration file,
but without comments.
2) "We don't like new INCLUDE_CONFIG_FILE, since it doesn't support comments,
and comments are crucial"
We'd have to add "-C" to config(8) execution in build scripts, the
same preserving the old way of keeping comments, but without getting
ready-to-use configuration file.
My vote is for (1)
Thanks,
--
Wojciech A. Koszek
wko...@FreeBSD.org
http://FreeBSD.czest.pl/~wkoszek/
Alex Kozlov
> Alex Keda wrote:
> > For those who have recently engaged in FreeBSD, and inexperienced
> > managers who have inherited a server "by inheritance" is often the
> > question arises - where to find the configuration file in which to
> > compile your kernel? (Of course, a file by that time there =))
> I actually thought that was already done, but I see now that it's not.
> I would like to see this as well, any objections?
--
Adios
Robert Watson
On Sat, 12 Dec 2009, Doug Barton wrote:
> Alex Keda wrote:
>> For those who have recently engaged in FreeBSD, and inexperienced managers
>> who have inherited a server "by inheritance" is often the question arises -
>> where to find the configuration file in which to compile your kernel? (Of
>> course, a file by that time there =))
>
> I actually thought that was already done, but I see now that it's not. I
> would like to see this as well, any objections?
I'd say go for it. It's not perfect, but given modern memory sizes for
systems using GENERIC, I'd say the administrative benefit is well worth it.
People doing embeddded will cut it as well as lots of other stuff in GENERIC
anyway.
Robert N M Watson
Computer Laboratory
University of Cambridge
Doug Barton
>
> On Sat, 12 Dec 2009, Doug Barton wrote:
>
>> Alex Keda wrote:
>>> For those who have recently engaged in FreeBSD, and inexperienced
>>> managers who have inherited a server "by inheritance" is often the
>>> question arises - where to find the configuration file in which to
>>> compile your kernel? (Of course, a file by that time there =))
>>
>> I actually thought that was already done, but I see now that it's not.
>> I would like to see this as well, any objections?
>
> I'd say go for it.
Ok, here is the proposed patch. I'll commit it tomorrow unless someone
objects.
Dag-Erling Smørgrav
> Ok, here is the proposed patch. [...]
I'd put it in DEFAULTS instead...
DES
--
Dag-Erling Smørgrav - d...@des.no
Wojciech A. Koszek
> Robert Watson wrote:
> >
> > On Sat, 12 Dec 2009, Doug Barton wrote:
> >
> >> Alex Keda wrote:
> >>> For those who have recently engaged in FreeBSD, and inexperienced
> >>> managers who have inherited a server "by inheritance" is often the
> >>> question arises - where to find the configuration file in which to
> >>> compile your kernel? (Of course, a file by that time there =))
> >>
> >> I actually thought that was already done, but I see now that it's not.
> >> I would like to see this as well, any objections?
> >
> > I'd say go for it.
>
> Ok, here is the proposed patch. I'll commit it tomorrow unless someone
> objects.
It looks fine for the first glance. I would also reconsider putting it in
DEFAULTS, as des@ pointed out.
--
Wojciech A. Koszek
wko...@FreeBSD.org
http://FreeBSD.czest.pl/~wkoszek/
Doug Barton
> It looks fine for the first glance. I would also reconsider putting it in
> DEFAULTS, as des@ pointed out.
Ok, no objections on my part. I thought putting it in the file itself
would make it easier for those who wanted to remove it, but I'm also
in agreement with those that believe that there is no real need to
remove it except for extreme cases, and they (generally) already know
what they are doing. :)
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
_______________________________________________
Dag-Erling Smørgrav
> Wojciech A. Koszek wrote:
> > It looks fine for the first glance. I would also reconsider putting it in
> > DEFAULTS, as des@ pointed out.
> Ok, no objections on my part. I thought putting it in the file itself
> would make it easier for those who wanted to remove it, but I'm also
> in agreement with those that believe that there is no real need to
> remove it except for extreme cases, and they (generally) already know
> what they are doing. :)
One could argue that making it hard to disable is a feature... Anyway,
adding
nooption INCLUDE_CONFIG_FILE
to your kernel config will disable it without having to mess with
DEFAULTS.
I wish we had a global DEFAULTS, though, so you didn't have to add
INCLUDE_CONFIG_FILE to N different files.
DES
--
Dag-Erling Smørgrav - d...@des.no
M. Warner Losh
Robert Watson <rwa...@FreeBSD.org> writes:
:
:
: > Alex Keda wrote:
: >> For those who have recently engaged in FreeBSD, and inexperienced
: >> managers who have inherited a server "by inheritance" is often the
: >> question arises - where to find the configuration file in which to
: >> compile your kernel? (Of course, a file by that time there =))
: >
: > I actually thought that was already done, but I see now that it's
: > not. I would like to see this as well, any objections?
:
: I'd say go for it. It's not perfect, but given modern memory sizes
: for systems using GENERIC, I'd say the administrative benefit is well
: worth it. People doing embeddded will cut it as well as lots of other
: stuff in GENERIC anyway.
I didn't see this discussion until now, since it was burried in
-current.
I'd say go ahead and add it to GENERIC (and I'll be happy do do that
now that I've backed it out of DEFAULTS).
But it does not belong in DEFAULTS. That file is not for this sort of
thing. That file is only for those options required to build a
bootable kernel, or for those options that went from being NO_FOO to
FOO and/or from being standard to being optional (like device mem).
There's also a desire to eliminate this file entirely when something
better comes along.
I'm planning on including standard files so that we can easily add
things in one place instead of many that will be better than DEFAULTS
in the next month or so. I've worked through several prototypes, none
of which have been suitable to share with the wider world, but each
one better than the one before... I'll post to arch@ when I have a
proposal.
Warner