Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-hackers Digest, Vol 71, Issue 5

2 views

Skip to first unread message

freebsd-hac...@freebsd.org

unread,

Jul 30, 2004, 8:07:59 AM7/30/04

Send freebsd-hackers mailing list submissions to
freebsd...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
or, via email, send a message with subject or body 'help' to
freebsd-hac...@freebsd.org

You can reach the person managing the list at
freebsd-ha...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-hackers digest..."

Today's Topics:

1. Kernel Configuration script [was Re: Next (William Kirkland)
2. Kernel Configuration script [was Re: "Next Generation" kernel
configuration?] (William Kirkland)
3. Re: Kernel Configuration script [was Re: Next (Brooks Davis)
4. Re: License of dev/arl (M. Warner Losh)
5. Re: Ready or not? (Pawel Malachowski)
6. Re: Ready or not? (M. Warner Losh)
7. Re: How to clean out old files after 'make world'?
(Ruslan Ermilov)
8. Re: How to clean out old files after 'make world'? (Max Laier)
9. Re: How to clean out old files after 'make world'?
(Colin Percival)
10. Re: Kernel Configuration script [was Re: "Next Generation"
kernel configuration?] (Conrad J. Sabatier)

----------------------------------------------------------------------

Message: 1
Date: Thu, 29 Jul 2004 08:25:53 -0700 (PDT)
From: William Kirkland <bi...@wek4.com>
Subject: Kernel Configuration script [was Re: Next
To: "Generationkernelconfiguration?]"@wek4.com,
freebsd...@freebsd.org
Message-ID: <200407291525....@wek4.com>
Content-Type: text/plain; charset=US-ASCII

On Tue, Jul 20, 2004 at 07:39:31PM -0500, Conrad J. Sabatier wrote:
> Just musing on an idea here:
>
> I've been thinking for a while now about trying to write a tool to make
> kernel configuration easier, sort of a "make config" (as in ports) for
> the kernel, similar to what's available on some of the Linux distros.

Ok, I have attached some scripts I wrote, to make my life simpler.
Though I do have some concerns that one should write their own, or use
the existing structure and tools. I am willing to show what I use and
share ideas.

If you choose to use this, please give credit where it is due. As I
have never previously published this, nor anything else. I find the GNU
GPL (http://www.gnu.org/copyleft/gpl.html) acceptable. Use at your own
risk.

My scripts parces the boot information from /var/log/messages, then
builds a kernel configuration file from that and a configuration file.
I have, just now, written a brief overview of what is done and am
willing to provide more information if you ask. I suppose I could even
clean it up a bit and write proper documentation.

The profile is a bit overly complex, though I use it for a number of
other scripts as well. Sufice it to say, it searches (based upon the
PATH environmental variable, replacing "/bin:" and "/sbin:" with
"/etc:" for an appropriate configuration file (one that has the script
name, minus an optional .sh and appending a .cfg, as a sufix). Once
the file is found, appropriate variables are set.

The performance can be enhanced by setting the "grep" variable, so
that only the relevent boot entries are parced, or copying the message
file somewhere else, then setting the "boot" variable to point to that
file.

Options and and device entries are included if a reference is found
for them in the /var/log/messages file. The exclude and include
configuration variables, modify this behavior, in that the script does
not find references for everything in the boot record, and also finds
references to things I do not use.

You should probably uncomment line 34, and verify the results, prior to
using. For that matter, there are a number of other things you should
understand prior to use (review it before you use it!).

#! /bin/sh
#- -r-xr-xr-x 1 root wheel 1285 May 9 20:20 /wek/bin/kernel.sh
. /wek/bin/_profile

if [ ! -f "${_kernel_dst}" ]; then
grep -E "${_kernel_grep:-.*}" ${_kernel_boot:-/var/log/messages} >${tmp}
awk -v K=${_kernel} -v B=${tmp} -v P=${_kernel_prefix} \
-v I="${_kernel_include}" -v X="${_kernel_exclude}" '
BEGIN { while( getline <B ) {
if ( $0 ~ P && $5 == "kernel:" && $6 ~ "[0-9]:$" ) {
sub( "[0-9]:$", "", $6 ); D[$6]++
} }
z=split( I, Z ); for( i=1; i<=z; i++ ) { d=Z[i]; D[d]++ }
z=split( X, Z ); for( i=1; i<=z; i++ ) { d=Z[i]; D[d]=0 }
}
/^[ # ]*ident[ ]/ { printf( "ident %s\n", K ); next }
/^[ # ]*device[ ]/ {
sub( "^[ # ]*", "" )
sub( "[ ]*$", "" )
if ( D[$2] == 0 ) { printf( "#- %s\n", $0 )
} else { printf( "%s #=%d\n", $0, D[$2] ) }
next }
/^[ # ]*(options|cpu)[ ]/ {
if ( D[$2] != "" ) {
sub( "^[ # ]*", "" )
sub( "[ ]*$", "" )
if ( D[$2] == 0 ) { printf( "#- %s\n", $0 )
} else { printf( "%s #=%d\n", $0, D[$2] ) }
next } }
/./ { print }' <${_kernel_src:-/dev/null} >${_kernel_dst}
if [ -f "${_kernel_add}" ]; then
cat ${_kernel_add} >>${_kernel_dst}
fi
rm -f ${tmp} 2>/dev/null
#- exit
fi

( uname -a; date; set -o xtrace
printenv | grep "^_${P}" | sort
cd /usr/src && make -i depend \
&& make buildkernel KERNCONF=${_kernel} \
&& make installkernel KERNCONF=${_kernel}
) 2>&1 | tee ${_kernel_log}

#- -r--r--r-- 1 operator wheel 126 Apr 23 15:50 /wek/etc/kernel.add
#- options FAST_IPSEC # new IPsec
options IPSEC
options IPSEC_ESP
options IPFIREWALL
options IPDIVERT
options DUMMYNET

#- -r--r--r-- 1 operator wheel 372 May 9 13:59 /wek/etc/kernel.cfg
wek-*
boot=/tmp/boot
boot=/var/log/messages
src=/usr/src/sys/$( uname -m )/conf/GENERIC
dst=/usr/src/sys/$( uname -m )/conf/${_kernel}
include="atadisk atapicd atapifd atapist random loop ether pty md bpf miibus gif sis"
exclude="INET6 MD_ROOT NFS_ROOT I486_CPU I586_CPU SMP plip"
add=${home}/etc/${P}.add
log=${home}/log/${_kernel}

#! /bin/sh
#- -rw-r--r-- 1 root wheel 742 May 11 14:39 /wek/bin/_profile

P=$( basename ${0%.*} )
export home=/wek
export tmp=/tmp/$$
export log=/tmp/${P}-$( date "+%y%m%d" )

for T in $( echo ${PATH}:${home}/etc \
| sed 's|/[s]*bin:|/etc |g' | tr ":" " " ); do
if [ -z "${cfg}" -a -r ${T}/${P}.cfg ]; then
cfg=${T}/${P}.cfg
fi
done
awk -F = -v P=${P} -v M="${1:-$( date '+wek-%y%m%d' )}" '
/^[^ ]/ { ok=0; if ( M ~ $1 ) { print "export _" P "=" M; ok=1; next } }
/^[ ]+[A-Z0-9a-z_]*[ ]*=/ { if ( ok ) {
gsub( "^[ ]*", "export _" P "_" ); print
} }' ${cfg:-/dev/null} >${tmp}
. ${tmp} && rm ${tmp}
export PATH=${home}/bin:${PATH}

------------------------------

Message: 2
Date: Thu, 29 Jul 2004 08:28:05 -0700 (PDT)
From: William Kirkland <bi...@wek4.com>
Subject: Kernel Configuration script [was Re: "Next Generation" kernel
configuration?]
To: freebsd...@freebsd.org
Message-ID: <200407291528....@wek4.com>
Content-Type: text/plain; charset=US-ASCII

You should probably uncomment line 34, and verify the results, prior to
using. For that matter, there are a number of other things you should
understand prior to use (review it before you use it!).

#! /bin/sh
#- -r-xr-xr-x 1 root wheel 1285 May 9 20:20 /wek/bin/kernel.sh
. /wek/bin/_profile

#- -r--r--r-- 1 operator wheel 126 Apr 23 15:50 /wek/etc/kernel.add
#- options FAST_IPSEC # new IPsec
options IPSEC
options IPSEC_ESP
options IPFIREWALL
options IPDIVERT
options DUMMYNET

#! /bin/sh
#- -rw-r--r-- 1 root wheel 742 May 11 14:39 /wek/bin/_profile

P=$( basename ${0%.*} )
export home=/wek
export tmp=/tmp/$$
export log=/tmp/${P}-$( date "+%y%m%d" )

------------------------------

Message: 3
Date: Thu, 29 Jul 2004 08:58:11 -0700
From: Brooks Davis <bro...@one-eyed-alien.net>
Subject: Re: Kernel Configuration script [was Re: Next
To: William Kirkland <bi...@wek4.com>
Cc: freebsd...@freebsd.org
Message-ID: <2004072915...@Odin.AC.HMC.Edu>
Content-Type: text/plain; charset="us-ascii"

On Thu, Jul 29, 2004 at 08:25:53AM -0700, William Kirkland wrote:
> On Tue, Jul 20, 2004 at 07:39:31PM -0500, Conrad J. Sabatier wrote:
> > Just musing on an idea here:
> >
> > I've been thinking for a while now about trying to write a tool to make
> > kernel configuration easier, sort of a "make config" (as in ports) for
> > the kernel, similar to what's available on some of the Linux distros.
>
> Ok, I have attached some scripts I wrote, to make my life simpler.
> Though I do have some concerns that one should write their own, or use
> the existing structure and tools. I am willing to show what I use and
> share ideas.
>
> If you choose to use this, please give credit where it is due. As I
> have never previously published this, nor anything else. I find the GNU
> GPL (http://www.gnu.org/copyleft/gpl.html) acceptable. Use at your own
> risk.

Anyone wishing to produce something to be included in the project,
should STOP READING HERE to avoid GPL comtamination.

-- Brooks

--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20040729/5a07201b/attachment-0001.bin

------------------------------

Message: 4
Date: Thu, 29 Jul 2004 10:02:34 -0600 (MDT)
From: "M. Warner Losh" <i...@bsdimp.com>
Subject: Re: License of dev/arl
To: jo...@britannica.bec.de
Cc: hac...@freebsd.org
Message-ID: <20040729.10023...@bsdimp.com>
Content-Type: Text/Plain; charset=us-ascii

In message: <2004072910...@britannica.bec.de>
Joerg Sonnenberger <jo...@britannica.bec.de> writes:
: what's the license under which arl(4) is distributed? The source doesn't
: contain any copyright or license header. I would appreciate it, if someone
: could fix that.

I'll make sure that one gets affixed.

Warner

------------------------------

Message: 5
Date: Thu, 29 Jul 2004 22:19:09 +0200
From: Pawel Malachowski <pawmal-...@freebsd.lublin.pl>
Subject: Re: Ready or not?
To: Max Laier <m...@love2party.net>
Cc: freebsd...@freebsd.org
Message-ID: <20040729201...@shellma.zin.lublin.pl>
Content-Type: text/plain; charset=iso-8859-2

On Wed, Jul 28, 2004 at 03:02:38PM +0200, Max Laier wrote:

Hello,

> as PF+ALTQ gateway in production environment. For ALTQ there is the problem
> of "will your driver be supported?".

Could You please explain a bit, why ALTQ model is placed so close
to network adapter driver (that they have to be modified) instead
of placing it in upper layers (and leaving NIC drivers untouched)?

TIA,
--
Paweł Małachowski

------------------------------

Message: 6
Date: Thu, 29 Jul 2004 23:55:08 -0600 (MDT)
From: "M. Warner Losh" <i...@bsdimp.com>
Subject: Re: Ready or not?
To: freebsd...@freebsd.org, pawmal-...@freebsd.lublin.pl
Cc: m...@love2party.net
Message-ID: <20040729.23550...@bsdimp.com>
Content-Type: Text/Plain; charset=us-ascii

In message: <20040729201...@shellma.zin.lublin.pl>
Pawel Malachowski <pawmal-...@freebsd.lublin.pl> writes:
: On Wed, Jul 28, 2004 at 03:02:38PM +0200, Max Laier wrote:
:
: Hello,
:
: > as PF+ALTQ gateway in production environment. For ALTQ there is the problem
: > of "will your driver be supported?".
:
: Could You please explain a bit, why ALTQ model is placed so close
: to network adapter driver (that they have to be modified) instead
: of placing it in upper layers (and leaving NIC drivers untouched)?

The short answer is because there is buffering (queueing) in the NIC
layer, and that limits the ability of of ALTQ to do its job. In order
to do QoS type things, this queueing makes it harder without the help
of the NIC driver. It is more complicated than this (I don't
understand all the details), but that is the jist of a larger
presentation of ALTQ that I had the pleasure of viewing at
AsiaBSDcon.

Warner

------------------------------

Message: 7
Date: Fri, 30 Jul 2004 09:56:38 +0300
From: Ruslan Ermilov <r...@freebsd.org>
Subject: Re: How to clean out old files after 'make world'?
To: "Stas D.Myasnikov" <my...@tut.by>
Cc: freebsd...@freebsd.org
Message-ID: <20040730065...@ip.net.ua>
Content-Type: text/plain; charset="us-ascii"

On Tue, Jul 20, 2004 at 10:23:25PM +0300, Stas D.Myasnikov wrote:
> Hello!
>
> While doing 'make world' I used make.conf with couple on 'NO_*=yes',
> e.g. NO_KERBEROS=yes (I don't need Kerberos on my home computer). But
> after rebuilding world and install I saw the old binaries, configs,
> etc. of Kerberos and other parts of base that I didn't build. I had
> thought that install script removes all unneeded files, but it don't.
> How can I clean out this old binaries, configs, etc?.. Is there any
> automatic way to do this?
>
I routinely use find(1) and some secret knowledge about files that
do not change their timestamps between installworlds to clean up
stale files. Fortunately there are not too much files that install
with -C, less in 5.x than in 4.x.

Also, Warner Losh worked on a project that would allow to remove
files obsoleted between releases. I don't know what the current
status of this project is, or if it's still alive. ;)

Cheers,
--
Ruslan Ermilov
r...@FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20040730/f459b4e0/attachment-0001.bin

------------------------------

Message: 8
Date: Fri, 30 Jul 2004 11:17:25 +0200
From: Max Laier <m...@love2party.net>
Subject: Re: How to clean out old files after 'make world'?
To: freebsd...@freebsd.org
Cc: Warner Losh <i...@freebsd.org>
Message-ID: <20040730111...@love2party.net>
Content-Type: text/plain; charset="iso-8859-1"

On Friday 30 July 2004 08:56, Ruslan Ermilov wrote:
> On Tue, Jul 20, 2004 at 10:23:25PM +0300, Stas D.Myasnikov wrote:
> > Hello!
> >
> > While doing 'make world' I used make.conf with couple on 'NO_*=yes',
> > e.g. NO_KERBEROS=yes (I don't need Kerberos on my home computer). But
> > after rebuilding world and install I saw the old binaries, configs,
> > etc. of Kerberos and other parts of base that I didn't build. I had
> > thought that install script removes all unneeded files, but it don't.
> > How can I clean out this old binaries, configs, etc?.. Is there any
> > automatic way to do this?
>
> I routinely use find(1) and some secret knowledge about files that
> do not change their timestamps between installworlds to clean up
> stale files. Fortunately there are not too much files that install
> with -C, less in 5.x than in 4.x.
>
> Also, Warner Losh worked on a project that would allow to remove
> files obsoleted between releases. I don't know what the current
> status of this project is, or if it's still alive. ;)

I am wondering, would it be possible to (automatically) create pkg-plist info
for the NO_* targets in make.conf? We could put that into the ports-tree
somewhere and if you'd like to remove something completely you can install
the dummy port & pkg-plist and use pkg_delete to clean up.

It seems to me that it might be possible to add some kind of Makefile hint
variables (i.e. define a variable in Makefiles/targets that depend on NO_*)
that'd help to generate filelists for the NO_* targets. If this is the case
it should be possible to place pkg descriptions into /var/db/pkg during the
installworld pass. This would also make it easy to get rid of things after a
CDROM install.

What do you think?

--
/"\ Best regards, | mla...@freebsd.org
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | mlaier@EFnet
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: signature
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20040730/42797d1a/attachment-0001.bin

------------------------------

Message: 9
Date: Fri, 30 Jul 2004 02:36:36 -0700
From: Colin Percival <colin.p...@wadham.ox.ac.uk>
Subject: Re: How to clean out old files after 'make world'?
To: Max Laier <m...@love2party.net>
Cc: freebsd...@freebsd.org
Message-ID: <6.1.0.6.1.200407...@popserver.sfu.ca>
Content-Type: text/plain; charset=us-ascii

At 02:17 30/07/2004, Max Laier wrote:
>I am wondering, would it be possible to (automatically) create pkg-plist info
>for the NO_* targets in make.conf? We could put that into the ports-tree
>somewhere and if you'd like to remove something completely you can install
>the dummy port & pkg-plist and use pkg_delete to clean up.
>
>It seems to me that it might be possible to add some kind of Makefile hint
>variables (i.e. define a variable in Makefiles/targets that depend on NO_*)
>that'd help to generate filelists for the NO_* targets. If this is the case
>it should be possible to place pkg descriptions into /var/db/pkg during the
>installworld pass. This would also make it easy to get rid of things after a
>CDROM install.

In March, I posted to freebsd-current (subject: Nuking parts of the world)
offering a patch which makes it possible to remove some subsystems:

http://docs.freebsd.org/cgi/mid.cgi?6.0.1.1.1.20040316023919.039fa5f0

Colin Percival

------------------------------

Message: 10
Date: Fri, 30 Jul 2004 06:55:28 -0500 (CDT)
From: "Conrad J. Sabatier" <con...@cox.net>
Subject: Re: Kernel Configuration script [was Re: "Next Generation"
kernel configuration?]
To: William Kirkland <bi...@wek4.com>
Cc: freebsd...@freebsd.org
Message-ID: <XFMail.2004073...@cox.net>
Content-Type: text/plain; charset=us-ascii

On 29-Jul-2004 William Kirkland wrote:
> On Tue, Jul 20, 2004 at 07:39:31PM -0500, Conrad J. Sabatier wrote:
>> Just musing on an idea here:
>>
>> I've been thinking for a while now about trying to write a tool to
>> make kernel configuration easier, sort of a "make config" (as in
>> ports) for the kernel, similar to what's available on some of the
>> Linux distros.
>
> Ok, I have attached some scripts I wrote, to make my life simpler.
> Though I do have some concerns that one should write their own, or
> use the existing structure and tools. I am willing to show what I
> use and share ideas.
>
> If you choose to use this, please give credit where it is due. As I
> have never previously published this, nor anything else. I find the
> GNU GPL (http://www.gnu.org/copyleft/gpl.html) acceptable. Use at
> your own risk.

Well, at this point, I'm not at all sure I even want to try to proceed
with working on something like this. I and several others are of the
opinion that, in their current state, the files used to describe all of
the available kernel options are simply not useable by an automated
system, at least not for the sort of thing I had envisioned. And I
don't expect that any sort of radical revision of the existing layout
would be greeted too warmly by most of the developers. :-)

But thanks, I'll take a look at your work.

Conrad

--
Conrad J. Sabatier <con...@cox.net> -- "In Unix veritas"

------------------------------

_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hacke...@freebsd.org"

End of freebsd-hackers Digest, Vol 71, Issue 5
**********************************************

0 new messages