Re: test-includes breaks buildworld when WITHOUT_PF is set in src.conf

2022-02-09 Thread Gary Jennejohn
On Wed, 09 Feb 2022 11:08:44 +0100 Kristof Provost wrote: > On 9 Feb 2022, at 10:57, Gary Jennejohn wrote: > > test-includes uses pf.h when checking usage of pfvar.h. > > > > But, these lines in include/Makefile remove pf.h when WITHOUT_PF is > > set in src.conf: > > > > .if ${MK_PF} != "no" > >

Re: test-includes breaks buildworld when WITHOUT_PF is set in src.conf

2022-02-09 Thread Kristof Provost
On 9 Feb 2022, at 10:57, Gary Jennejohn wrote: > test-includes uses pf.h when checking usage of pfvar.h. > > But, these lines in include/Makefile remove pf.h when WITHOUT_PF is > set in src.conf: > > .if ${MK_PF} != "no" > INCSGROUPS+= PF > .endif > > This breaks buildworld. The error message:

Re: test suite for NIC features...

2020-07-20 Thread Kurt Jaeger
Hi! > Has anyone compiled a script/test suite for testing various NIC > features to make sure they work/function properly? > > That is, being able to run a couple interfaces back to back, and turn > off the features off on one, and make sure things like checksum offload > and the like work

Re: test program for copy_file_range(2)

2019-07-05 Thread Rick Macklem
Alan Somers wrote: >On Fri, Jul 5, 2019 at 9:11 AM Rick Macklem wrote: >> >> Alan Somers wrote: >> >On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote: >> >> >> >> I have a little program for testing the copy_file_range(2) syscall I've >> >> been >> >> working on. (The current version is

Re: test program for copy_file_range(2)

2019-07-05 Thread Alan Somers
On Fri, Jul 5, 2019 at 9:11 AM Rick Macklem wrote: > > Alan Somers wrote: > >On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote: > >> > >> I have a little program for testing the copy_file_range(2) syscall I've > >> been > >> working on. (The current version is attached, in case anyone is > >>

Re: test program for copy_file_range(2)

2019-07-05 Thread Rick Macklem
Alan Somers wrote: >On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote: >> >> I have a little program for testing the copy_file_range(2) syscall I've been >> working on. (The current version is attached, in case anyone is interested.) >> >> It take a few minutes to run on a slow system and uses

Re: test program for copy_file_range(2)

2019-07-05 Thread Alan Somers
On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote: > > I have a little program for testing the copy_file_range(2) syscall I've been > working on. (The current version is attached, in case anyone is interested.) > > It take a few minutes to run on a slow system and uses about 6Gbytes of disk >

Re: test

2013-10-09 Thread Vincent Hoffman
Please use freebsd-test for testing http://lists.freebsd.org/mailman/listinfo/freebsd-test Vince On 08/10/2013 23:00, Joe Nosay wrote: What were you testing? On Tue, Oct 8, 2013 at 5:25 PM, Joe Nosay superbisq...@gmail.com wrote: /div/td/tr/tbody/table/td/tr/tbody/table/divdiv

Re: test

2013-10-08 Thread Joe Nosay
/div/td/tr/tbody/table/td/tr/tbody/table/divdiv class=utdU2e/divdiv class=tx78Ic/divdiv class=aHl/divdiv id=:2il tabindex=-1/divdiv id=:2i7 class=ii gt m1419842a752abb3c adP adOdiv id=:2i6 style=overflow: hidden;testbr__ On Tue, Oct 8, 2013 at 9:29 AM, Alexander

Re: test

2013-10-08 Thread Joe Nosay
What were you testing? On Tue, Oct 8, 2013 at 5:25 PM, Joe Nosay superbisq...@gmail.com wrote: /div/td/tr/tbody/table/td/tr/tbody/table/divdiv class=utdU2e/divdiv class=tx78Ic/divdiv class=aHl/divdiv id=:2il tabindex=-1/divdiv id=:2i7 class=ii gt m1419842a752abb3c adP adOdiv id=:2i6

Re: please (re) test AR9220/AR9280 if_ath in -HEAD

2011-03-10 Thread Adrian Chadd
Hi all again! I've just committed some more fixes to TX power calibration for the AR9220 and AR9280. I -think- I have all of the radio setup correct now for the AR5416, AR9160, AR9220 and AR9280. If you're using any of these, especially if you're using the AR9220/AR9280 (and doubly so oif

Re: please (re) test if_ath in -HEAD

2011-03-09 Thread Adrian Chadd
-grenoble.fr wrote: On Thu 03 March 2011 at 02:31:05PM -0800, Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. I've done a variety of changes to the radio setup

Re: please (re) test if_ath in -HEAD

2011-03-09 Thread Adrian Chadd
mikael.uran...@ujf-grenoble.fr wrote: On Thu 03 March 2011 at 02:31:05PM -0800, Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. I've done

Re: please (re) test if_ath in -HEAD

2011-03-07 Thread Dima Panov
hello! FreeBSD 9.0-900033-CURRENT #0 r219338M: Mon Mar 7 11:31:40 VLAT 2011 All fine with AR9285, WPA2 is used stable 36/48/54Mbps with my AP 07.03.2011, 06:14, Adrian Chadd adrian.ch...@gmail.com: On 7 March 2011 03:21, Ian FREISLICH i...@clue.co.za; wrote:  Adrian Chadd wrote:  I'd like

Re: please (re) test if_ath in -HEAD

2011-03-06 Thread Adrian Chadd
wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. Since running the new code, I get a slew of these: Mar 6 14:41:53 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq

Re: please (re) test if_ath in -HEAD

2011-03-06 Thread Ian FREISLICH
Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. Since running the new code, I get a slew of these: Mar 6 14:41:53 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID

Re: please (re) test if_ath in -HEAD

2011-03-06 Thread Vinícius Zavam
2011/3/6 Ian FREISLICH i...@clue.co.za: Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. Since running the new code, I get a slew of these: Mar  6 14:41:53 mini wpa_supplicant[422]: Trying

Re: please (re) test if_ath in -HEAD

2011-03-06 Thread Ian FREISLICH
Adrian Chadd wrote: I'd like to establish at least a range of subversion revisions so we can start binary searching which one(s) caused instabilities. Is this all the source? Old: $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.300 2011/02/21 19:22:45 adrian Exp $ $FreeBSD:

Re: please (re) test if_ath in -HEAD

2011-03-06 Thread Adrian Chadd
On 7 March 2011 03:21, Ian FREISLICH i...@clue.co.za wrote: Adrian Chadd wrote: I'd like to establish at least a range of subversion revisions so we can start binary searching which one(s) caused instabilities. Is this all the source? Old: $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.300

Re: please (re) test if_ath in -HEAD

2011-03-06 Thread Daren Isaacs
to -HEAD and re-test. I've done a variety of changes to the radio setup and found/fixed a few bugs in the TX path. It's quite possible these have introduced regressions. I'd like to make sure that I haven't broken legacy (11abg

Re: please (re) test if_ath in -HEAD

2011-03-05 Thread Adrian Chadd
it if you'd update to -HEAD and re-test. I've done a variety of changes to the radio setup and found/fixed a few bugs in the TX path. It's quite possible these have introduced regressions. I'd like to make sure that I haven't broken legacy (11abg) support in weird/wonderful ways. I'd also

Re: please (re) test if_ath in -HEAD

2011-03-05 Thread Urankar Mikael
On Thu 03 March 2011 at 02:31:05PM -0800, Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. I've done a variety of changes to the radio setup and found/fixed a few bugs in the TX path. It's

Re: please (re) test if_ath in -HEAD

2011-03-05 Thread Marcelo/Porks
On Thu, Mar 3, 2011 at 19:31, Adrian Chadd adrian.ch...@gmail.com wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. I've done a variety of changes to the radio setup and found/fixed a few bugs in the TX path

Re: please (re) test if_ath in -HEAD

2011-03-05 Thread Urankar Mikael
of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. I've done a variety of changes to the radio setup and found/fixed a few bugs in the TX path. It's quite possible these have introduced regressions. I'd like to make sure that I

Re: please (re) test if_ath in -HEAD

2011-03-05 Thread Adrian Chadd
, Urankar Mikael mikael.uran...@ujf-grenoble.fr wrote: On Thu 03 March 2011 at 02:31:05PM -0800, Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. I've done a variety of changes

please (re) test if_ath in -HEAD

2011-03-03 Thread Adrian Chadd
Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. I've done a variety of changes to the radio setup and found/fixed a few bugs in the TX path. It's quite possible these have introduced regressions. I'd like to make sure

Re: TEST PLEASE: if_tun patch

2003-10-03 Thread Pawel Malachowski
On Tue, Sep 30, 2003 at 03:17:05PM -0700, Brooks Davis wrote: It looks strange to have `ifconfig create' vlan interface on tap, while tap uses different semantics and can disappear after closing it? With ef it is even worse, pseudo-devices are created while ef is starting, so ef module

Re: TEST PLEASE: if_tun patch

2003-09-30 Thread Pawel Malachowski
On Sun, Sep 28, 2003 at 10:04:42PM -0700, Brooks Davis wrote: I'm not convinced this is the right direction to move in. The problem is that users are beginning to expect that pseudo-interfaces be created with network interface cloning, but tun, tap, and vmnet aren't. I'm Same about ef(4)

Re: TEST PLEASE: if_tun patch

2003-09-30 Thread Brooks Davis
On Tue, Sep 30, 2003 at 11:35:34PM +0200, Pawel Malachowski wrote: On Sun, Sep 28, 2003 at 10:04:42PM -0700, Brooks Davis wrote: I'm not convinced this is the right direction to move in. The problem is that users are beginning to expect that pseudo-interfaces be created with network

Re: TEST PLEASE: if_tun patch

2003-09-29 Thread Brooks Davis
On Mon, Sep 29, 2003 at 07:29:08AM +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Brooks Davis writes: | Properly dismantle and remove the interface and destroy the dev_t=20 | at last close of the device. I'm not convinced this is the right direction to move in. The

Re: TEST PLEASE: if_tun patch

2003-09-28 Thread Brooks Davis
On Sat, Sep 27, 2003 at 11:57:19PM +0200, Poul-Henning Kamp wrote: Please test this patch: http://phk.freebsd.dk/patch/if_tun.patch There is a slight change in semantics in that the interface will disappear entirely when the /dev/tun%d device is closed. If no objections this

Re: TEST PLEASE: if_tun patch

2003-09-28 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Brooks Davis writes: | Properly dismantle and remove the interface and destroy the dev_t=20 | at last close of the device. I'm not convinced this is the right direction to move in. The problem is that users are beginning to expect that pseudo-interfaces be

Re: TEST PLEASE: http://phk.freebsd.dk/patch/scsi_cd.patch

2003-09-24 Thread Florian C. Smeets
Poul-Henning Kamp wrote: This patch moves the SCSI cd driver under GEOM. On sparc64 (or with geom_sunlabel in your kernel) try inserting a solaris install CD and then: true /dev/cd0 # make GEOM taste media ls -l /dev/cd* You should now be able to see the boot partitions. It

Re: TEST PLEASE: http://phk.freebsd.dk/patch/scsi_cd.patch

2003-09-24 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Ulrich Spoerlein writes: --OwLcNYc0lM97+oe1 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 23.09.2003 at 10:27:12 +0200, Poul-Henning Kamp wrote: On sparc64 (or with geom_sunlabel in your

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Nate Lawson
On Thu, 23 Jan 2003, Juli Mallett wrote: Thanks to Ruslan's reminder that tunefs now uses libufs and tunefs is one of the crunched programs, I realised that I really needed to make newfs(8) use libufs. To show off that it *can* help us reduce space, a good bit in some cases. Good to see

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Juli Mallett
* De: Nate Lawson [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Re: Test this! Patch to make newfs(8) use libufs. ] On Thu, 23 Jan 2003, Juli Mallett wrote: Thanks to Ruslan's reminder that tunefs now uses libufs and tunefs is one of the crunched programs, I realised that I

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Juli Mallett
* De: Juli Mallett [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Test this! Patch to make newfs(8) use libufs. ] [rambling, and a patch] I thought every bit of code that would possibly write out was protected by Nflag, it isn't. I'll re-instate the wtfs function as a wrapper to

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Juli Mallett
* De: Juli Mallett [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Re: Test this! Patch to make newfs(8) use libufs. ] * De: Juli Mallett [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Test this! Patch to make newfs(8) use libufs. ] [rambling, and a patch] I thought

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Nate Lawson
On Thu, 23 Jan 2003, Juli Mallett wrote: * De: Nate Lawson [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Re: Test this! Patch to make newfs(8) use libufs. ] On Thu, 23 Jan 2003, Juli Mallett wrote: Thanks to Ruslan's reminder that tunefs now uses libufs and tunefs is one

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Juli Mallett
* De: Nate Lawson [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Re: Test this! Patch to make newfs(8) use libufs. ] On Thu, 23 Jan 2003, Juli Mallett wrote: * De: Nate Lawson [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Re: Test this! Patch to make newfs(8) use libufs

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Juli Mallett
* De: Juli Mallett [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Re: Test this! Patch to make newfs(8) use libufs. ] * De: Nate Lawson [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Re: Test this! Patch to make newfs(8) use libufs. ] On Thu, 23 Jan 2003, Juli Mallett

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Juli Mallett
* De: Juli Mallett [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: Re: Test this! Patch to make newfs(8) use libufs. ] I just went to do this, and found that pwrite is failing, saying EBADF. Could this be because of the failed ioctl? I'm not sure why this is happening. Any

Re: Test this! Patch to make newfs(8) use libufs.

2003-01-23 Thread Nate Lawson
On Thu, 23 Jan 2003, Juli Mallett wrote: Here's the URL once more: http://people.freebsd.org/~jmallett/newfs-libufs.diff Two minor issues: one use of if Nflag is left near the beginning of the diff and would prefer the check in bwrite() be if !Nflag instead of returning early. -Nate

Re: test

2001-11-16 Thread Gary Jennejohn
On Friday 16 November 2001 07:09, Brian K. White wrote: testing... Brian K. White -- [EMAIL PROTECTED] -- http://www.aljex.com/bkw/ +[+++[-]-]+..+.+++.-.[+---] ++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani kindly use [EMAIL PROTECTED]

Re: Test tweak for F00F bug..

2001-10-24 Thread Julian Elischer
have you tested the foof bug itself? On Wed, 24 Oct 2001, Giorgos Keramidas wrote: On Tue, Oct 23, 2001 at 10:57:18AM -0700, John Baldwin wrote: Anyone running -current on a true Pentium with the F00F bug that can verify that this simple cleanup patch works?

Re: Test tweak for F00F bug..

2001-10-24 Thread John Baldwin
On 24-Oct-01 Julian Elischer wrote: have you tested the foof bug itself? cjc did. The change has already been committed. On Wed, 24 Oct 2001, Giorgos Keramidas wrote: On Tue, Oct 23, 2001 at 10:57:18AM -0700, John Baldwin wrote: Anyone running -current on a true Pentium with the F00F

Re: Test tweak for F00F bug..

2001-10-23 Thread Kris Kennaway
On Tue, Oct 23, 2001 at 10:57:18AM -0700, John Baldwin wrote: Anyone running -current on a true Pentium with the F00F bug that can verify that this simple cleanup patch works? http://www.freebsd.org/~jhb/patches/f00f.patch I can probably do it over the weekend. Kris PGP signature

Re: Test tweak for F00F bug..

2001-10-23 Thread Giorgos Keramidas
On Tue, Oct 23, 2001 at 10:57:18AM -0700, John Baldwin wrote: Anyone running -current on a true Pentium with the F00F bug that can verify that this simple cleanup patch works? http://www.freebsd.org/~jhb/patches/f00f.patch I can. Running it on p5/133 right now. CPU: Pentium/P54C

Re: test/review: /dev/console logging patch

2000-12-18 Thread John Baldwin
On 18-Dec-00 Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], John Baldwin writes: On 17-Dec-00 Poul-Henning Kamp wrote: This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. Poul-Henning

Re: test/review: /dev/console logging patch

2000-12-17 Thread Doug Barton
Poul-Henning Kamp wrote: This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. This works spectacularly for me on a UP -current with up to date sources. The only nit I have is that it doesn't

Re: test/review: /dev/console logging patch

2000-12-17 Thread Crist J. Clark
On Sun, Dec 17, 2000 at 01:15:41PM -0800, Doug Barton wrote: Poul-Henning Kamp wrote: This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. This works spectacularly for me on a UP

RE: test/review: /dev/console logging patch

2000-12-17 Thread John Baldwin
On 17-Dec-00 Poul-Henning Kamp wrote: This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. Poul-Henning 1. Replace logwakeup() with msgbuftrigger++; There is little point in calling a

Re: test/review: /dev/console logging patch

2000-12-17 Thread John Baldwin
On 17-Dec-00 Doug Barton wrote: Poul-Henning Kamp wrote: This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. This works spectacularly for me on a UP -current with up to date sources. The

Re: test/review: /dev/console logging patch

2000-12-17 Thread Peter Jeremy
On 2000-Dec-17 15:06:40 -0800, John Baldwin [EMAIL PROTECTED] wrote: On 17-Dec-00 Doug Barton wrote: Would there be any harm to changing the dots to something more meaningful, like "Done with additional network setup" on its own line? The '.'s are simple and not too cluttery. Agreed. I

Re: test/review: /dev/console logging patch

2000-12-17 Thread Doug Barton
Peter Jeremy wrote: On 2000-Dec-17 15:06:40 -0800, John Baldwin [EMAIL PROTECTED] wrote: On 17-Dec-00 Doug Barton wrote: Would there be any harm to changing the dots to something more meaningful, like "Done with additional network setup" on its own line? . Agreed. I think the

Re: test/review: /dev/console logging patch

2000-12-17 Thread Poul-Henning Kamp
This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. Dec 17 13:00:26 console.info Master /boot/kernel/kernel: Doing additional network setup: Dec 17 13:00:26 console.info Master

Re: test/review: /dev/console logging patch

2000-12-17 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], John Baldwin writes: On 17-Dec-00 Poul-Henning Kamp wrote: This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. Poul-Henning 1. Replace logwakeup() with

Re: test/review: /dev/console logging patch

2000-12-17 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Peter Jeremy writes: I'm not offering code right now, but how about using a `newline or timeout' approach? If there's a partial line and there's been no console output for some number of seconds, forward the line to log(9). I played with this, and I was not happy

Re: test/review: /dev/console logging patch

2000-12-17 Thread Doug Barton
Poul-Henning Kamp wrote: This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. Dec 17 13:00:26 console.info Master /boot/kernel/kernel: Doing additional network setup: Dec 17 13:00:26

Re: test/review: /dev/console logging patch

2000-12-17 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Doug Barton writes: The '.'s are simple and not too cluttery. Fixing the console to line buffer what it sends to log(9) is a better fix, IMO. I specifically decided not to do this because I want to be able to see stuff like: echo -n "Press return

Re: test from mysql's configure

2000-10-22 Thread Daniel Eischen
On Sun, 22 Oct 2000, Andrey Rouskol wrote: Hi there ! Some days ago I was tring to compile mysql at -current and found that ./configure freezes at 'checking for restartable system calls'. Here is a code witch is executed - if you compile it with '-lc_r -lm -lcrypt' it will It should be

Re: test from mysql's configure

2000-10-22 Thread Andrey Rouskol
On Sun, 22 Oct 2000, Daniel Eischen wrote: On Sun, 22 Oct 2000, Andrey Rouskol wrote: Some days ago I was trying to compile mysql at -current and found that ./configure freezes at 'checking for restartable system calls'. Here is a code witch is executed - if you compile it with '-lc_r

Re: test from mysql's configure

2000-10-22 Thread Daniel Eischen
On Sun, 22 Oct 2000, Andrey Rouskol wrote: Hi there ! Some days ago I was tring to compile mysql at -current and found that ./configure freezes at 'checking for restartable system calls'. Here is a code witch is executed - if you compile it with '-lc_r -lm -lcrypt' it will freeze. Fix

Re: test.

2000-07-27 Thread Robert Drehmel
On Thu, 27 Jul 2000 16:34:58 +0200, "Vincent Bruijnes" wrote: How can i unsubscribe from freebsd-current and subcribe to freebsd-stable, Thanks, Vincent Send a mail to [EMAIL PROTECTED] (not to this list) with unsubscribe freebsd-current subscribe freebsd-stable in the message body.