headers
Doug White | 1 Jun 2002 02:01

Re: KLD mmap question

On Thu, 30 May 2002, Tom Tang wrote:

>   Thanks for the reply, I'll check it out.  However
> if you'll notice in my prev mail, I stated that I was
> trying to contigmalloc 4K... Hard to believe that
> the system doesnt have 4K lying around.

Good point.

Contigmallocing a page is pretty silly, since you get a page anyway. Why
not just use normal malloc?

Doug White                    |  FreeBSD: The Power to Serve
dwhite <at> resnet.uoregon.edu     |  www.FreeBSD.org

To Unsubscribe: send mail to majordomo <at> FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Permalink | Reply | 0 comments |
headers
Giorgos Keramidas | 1 Jun 2002 03:17
Picon
Favicon

Adding diffs to commit-mail on the fly

Hi Matt and everyone,

I remember that Matt had mentioned adding diffs of the commits to the
commit-mail, which would make it possible to quickly view what changed
without leaving the MUA and manually searching for the proper CVS
diff/rdiff incantation to view the diff.

The idea was resting at the back of my mind, and tonight I hacked this
Perl script that seems to mostly do what I want, when I pipe a single
message to it's STDIN in mbox format.  Given a script in Perl or awk
or whatever that works like this one, how would you all integrate this
with procmail to let it filter all the commit mail of FreeBSD?

The code of the script is a bit clumsily written, but here it is for
anyone who cares to play with it.  You can see a sample of the output
of this script, in mbox file format, at:

http://www.FreeBSD.org/~keramida/files/freebsd-rdiff.txt

- Giorgos

======================================================================
#!/usr/bin/perl
#
# A filter that copies all the lines from stdin unchanged, until it
# matches the magic FreeBSD commit-mail line that says files and
# revisions follow.  When that line is matched, do our stuff until the
# line that matches /^$/; when all file changes are finished.

# If this is set to non-zero, then trim EOL whitespace from the
(Continue reading)

Permalink | Reply | 9 comments |
headers
Jos Backus | 1 Jun 2002 03:53

Re: Improving GNU make compatibility in BSD make (+ patch)

Fyi: it appears nobody is really interested in having BSD make and GNU make
converge a little, so I am not going waste any more time on this.

--

-- 
Jos Backus                 _/  _/_/_/        Santa Clara, CA
                          _/  _/   _/
                         _/  _/_/_/             
                    _/  _/  _/    _/
jos <at> catnook.com     _/_/   _/_/_/            use Std::Disclaimer;

To Unsubscribe: send mail to majordomo <at> FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Permalink | Reply | 14 comments |
headers
Brandon D. Valentine | 1 Jun 2002 03:53

Re: Adding diffs to commit-mail on the fly

On Sat, 1 Jun 2002, Giorgos Keramidas wrote:

>Given a script in Perl or awk
>or whatever that works like this one, how would you all integrate this
>with procmail to let it filter all the commit mail of FreeBSD?

Assuming your script works, here's the procmail hoodoo:

:0 fw
* ^List-Id: <cvs-all.FreeBSD.ORG>
| /path/to/filter/script

Insert this rule into your .procmailrc anywhere above where you actually
filter cvs-all to a specific folder.

Brandon D. Valentine
--

-- 
http://www.geekpunk.net                         bandix <at> geekpunk.net
++[>++++++<-]>[<++++++>-]<.>++++[>+++++<-]>[<+++++>-]<+.+++++++..++
+.>>+++++[<++++++>-]<++.<<+++++++++++++++.>.+++.------.--------.>+.

To Unsubscribe: send mail to majordomo <at> FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Permalink | Reply | 6 comments |
headers
Julian Elischer | 1 Jun 2002 03:55

Re: Improving GNU make compatibility in BSD make (+ patch)

what would you want to do?

On Fri, 31 May 2002, Jos Backus wrote:

> Fyi: it appears nobody is really interested in having BSD make and GNU make
> converge a little, so I am not going waste any more time on this.
> 
> -- 
> Jos Backus                 _/  _/_/_/        Santa Clara, CA
>                           _/  _/   _/
>                          _/  _/_/_/             
>                     _/  _/  _/    _/
> jos <at> catnook.com     _/_/   _/_/_/            use Std::Disclaimer;
> 
> To Unsubscribe: send mail to majordomo <at> FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 

To Unsubscribe: send mail to majordomo <at> FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Permalink | Reply | 5 comments |
headers
Giorgos Keramidas | 1 Jun 2002 04:07
Picon
Favicon

Re: Adding diffs to commit-mail on the fly

On 2002-05-31 20:53 -0500, Brandon D. Valentine wrote:
> On Sat, 1 Jun 2002, Giorgos Keramidas wrote:
> 
> >Given a script in Perl or awk
> >or whatever that works like this one, how would you all integrate this
> >with procmail to let it filter all the commit mail of FreeBSD?
> 
> Assuming your script works, here's the procmail hoodoo:
> 
> :0 fw
> * ^List-Id: <cvs-all.FreeBSD.ORG>
> | /path/to/filter/script
> 
> Insert this rule into your .procmailrc anywhere above where you actually
> filter cvs-all to a specific folder.

The problem with this is that I would have to hardwire the output
folder name to the script, or pass it as a parameter.  I've found two
answers until now, by reading my manpages [beats head]. One is:

    :0 H
    * ^sender: owner-cvs-all <at> freebsd.org
    | /path/to/filter freebsd-cvs-all

But 'm not sure if this will let procmail lock the folder properly.

My intention was to add something like:

    :0 H
    * ^sender: owner-cvs-all <at> freebsd.org
(Continue reading)

Permalink | Reply | 5 comments |
headers
Brandon D. Valentine | 1 Jun 2002 04:18

Re: Adding diffs to commit-mail on the fly

On Sat, 1 Jun 2002, Giorgos Keramidas wrote:

>On 2002-05-31 20:53 -0500, Brandon D. Valentine wrote:
>> Assuming your script works, here's the procmail hoodoo:
>>
>> :0 fw
>> * ^List-Id: <cvs-all.FreeBSD.ORG>
>> | /path/to/filter/script
>
>The problem with this is that I would have to hardwire the output
>folder name to the script, or pass it as a parameter.  I've found two
>answers until now, by reading my manpages [beats head]. One is:

Nonsense.  With the rule I gave you your script should take the message
on stdin, modify it, and spit it back out on stdout where it will
continue to fall through the procmail rules.  That's what the 'f' option
at the start of the rule is all about.  You end up with two succesive
rules like this:

:0 fw
* ^List-Id: <cvs-all.FreeBSD.ORG>
| /path/to/filter/script

:0:
*^ List-Id: <cvs-all.FreeBSD.ORG>
cvs-all

Make sense?

Brandon D. Valentine
(Continue reading)

Permalink | Reply | 4 comments |
headers
Giorgos Keramidas | 1 Jun 2002 04:27
Picon
Favicon
Gravatar

Re: Adding diffs to commit-mail on the fly

On 2002-05-31 21:18 -0500, Brandon D. Valentine wrote:
>On Sat, 1 Jun 2002, Giorgos Keramidas wrote:
>>On 2002-05-31 20:53 -0500, Brandon D. Valentine wrote:
>>> Assuming your script works, here's the procmail hoodoo:
>>>
>>> :0 fw
>>> * ^List-Id: <cvs-all.FreeBSD.ORG>
>>> | /path/to/filter/script
>>
>>The problem with this is that I would have to hardwire the output
>>folder name to the script, or pass it as a parameter.  I've found two
>>answers until now, by reading my manpages [beats head]. One is:
> 
> Nonsense.  With the rule I gave you your script should take the message
> on stdin, modify it, and spit it back out on stdout where it will
> continue to fall through the procmail rules.  That's what the 'f' option
> at the start of the rule is all about.  You end up with two succesive
> rules like this:
> 
> :0 fw
> * ^List-Id: <cvs-all.FreeBSD.ORG>
> | /path/to/filter/script
> 
> :0:
> *^ List-Id: <cvs-all.FreeBSD.ORG>
> cvs-all
> 
> Make sense?

Indeed.  Brain cells shutting down already.  I shouldn't read procmail
(Continue reading)

Permalink | Reply | 3 comments |
headers
Brandon D. Valentine | 1 Jun 2002 04:32

Re: Adding diffs to commit-mail on the fly

On Sat, 1 Jun 2002, Giorgos Keramidas wrote:

>Indeed.  Brain cells shutting down already.  I shouldn't read procmail
>rules after I get sleepy.  The 'f' flag of procmail seems like, aw mee
>gods, so fine ;-)))

Cool.  If I might make another suggestion, you will likely get faster
performance and in general make people happier if you only run this
script against your own personal mirror of the CVS repo so as not to tie
up anoncvs.freebsd.org.

Brandon D. Valentine
--

-- 
http://www.geekpunk.net                         bandix <at> geekpunk.net
++[>++++++<-]>[<++++++>-]<.>++++[>+++++<-]>[<+++++>-]<+.+++++++..++
+.>>+++++[<++++++>-]<++.<<+++++++++++++++.>.+++.------.--------.>+.

To Unsubscribe: send mail to majordomo <at> FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Permalink | Reply | 2 comments |
headers
Jos Backus | 1 Jun 2002 04:54

Re: Improving GNU make compatibility in BSD make (+ patch)

On Fri, May 31, 2002 at 06:55:54PM -0700, Julian Elischer wrote:
> what would you want to do?
> 
> On Fri, 31 May 2002, Jos Backus wrote:
> 
> > Fyi: it appears nobody is really interested in having BSD make and GNU make
> > converge a little, so I am not going waste any more time on this.

BSD make and GNU make use different symbols for .ALLSRC: GNU make uses $^ and
BSD make uses $>. All my tiny patch to BSD make does is have BSD make treat $^
as $>. This fixes the problem of the mktool Makefile which with this patch is
executed properly by both make's. Perhaps there is a better way to achieve
this but I don't see it. Since BSD make (or OpenBSD make, for that matter)
doesn't currently use $^ I thought it was a pretty safe and useful change.

Thanks for caring!

CC?=gcc
OPT=-O2 -march=i686
#DEBUG=-g -pedantic -Wall -Werror
LDFLAGS=-s
CFLAGS=$(OPT) $(DEBUG)
PROGS=envuidgid setugid tcpaccept tcplisten execlp bsok babysit
BINMODE?=555
prefix=/usr/local
bindir=$(prefix)/bin

.c.o:
	$(CC) $(CFLAGS) -c $<
(Continue reading)

Permalink | Reply | 4 comments |

Gmane