Re: Linux JDK 1.3 and hotspot (native threads)

2001-05-03 Thread Peter Mutsaers

>> "Georg-W" == Georg-W Koltermann <[EMAIL PROTECTED]> writes:

Georg-W> I tried the patch and found it makes no difference.  The current SUN
Georg-W> JVM (1.3.0_02) gives the SIG11 as I indicated before.  The latest IBM
Georg-W> JVM (IBM build cx130-20010329) hangs around and eats up CPU time.  It
Georg-W> mostly eats system time (usage is about 8% user, 91% system).  A
Georg-W> normal kill is ineffective, I have to send it a -9 in order to
Georg-W> terminate.  

Running SUn JVM 1.3.0_02 on Solaris 2.6 gives me exactly the same
error once in a while, but only (I think) when using with -server,
i.e. the hotspot server. This might well be a JVM problem, not a
problem of the Linux emulation.

-- 
Peter Mutsaers  |  Dübendorf| UNIX - Live free or die
[EMAIL PROTECTED]  |  Switzerland  | Sent via FreeBSD 4.3-stable

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: egcs unstable

1999-11-13 Thread Peter Mutsaers

>> "MM" == Marcel Moolenaar <[EMAIL PROTECTED]> writes:

MM> After (by accident) compiling world (excluding kernel) with
MM> optimization disabled (ie -O0) and installing the resulting
MM> binaries, xemacs (21.1.7) coredumps with a bus error. I
MM> recompiled and reinstalled xemacs and all was fine. Now, after
MM> building and installing world (excluding kernel again) with
MM> optimization (ie -O), xemacs does exactly the same: core dumps
MM> on bus error. I'll recompile xemacs again and expect it to be
MM> solved, but something is definitely broken: xemacs should not
MM> core dump after recompiling world with only a simple change in
MM> compiler flags.

Are you sure this isn't a problem with xemacs itself? Reading the
xemacs group, I read about crashes all the time on various
platforms. It is getting worse with newer versions (the 19.x versions
were pretty stable). Anyway I stick to good old GNU emacs (I can do
without inline images for the time being) which is rock solid, also
after -current 'make world's.

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED] |  the Netherlands| what I'm doing.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: recent apm changes

1999-08-16 Thread Peter Mutsaers

OK, here I am once more, after yet another reboot :)

Now I'm running an unpatched -current from last week. It behaves
almost the same, except for the delay in 'zzz'.

That is, the system will go in suspend mode (albeit without spinning
down the disks immediately) after a BIOS timeout or power-button
press.

If I use 'zzz', I have to do the known 'sleep 1; zzz' trick. This is
the difference.

Regards,

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED]  |  the Netherlands| what I'm doing. 
---+-+--
Powered by FreeBSD (-current). See http://www.freebsd.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: recent apm changes

1999-08-16 Thread Peter Mutsaers

Followup: I decided to upgrade my P2B BIOS version. I had 1005, went
to 1010. This made a difference!

Now suspend works. However still the disks keep spinning until they
reach their BIOS timeout. In Linux & Windows, there is some hook when
going to suspend mode that spins down the (IDE) disks. This is nice,
since it is well possible that you go to suspend but do not set a disk
spindown timeout.

Weird that 1005 did not, but 1010 does suspend with FreeBSD (& your
patch, I didn't try without it again), while 1005 did work with Linux
& Windows. That's why I didn't think of upgrading before.

I'll report what happens with the original (non patched) kernel
later.


>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes:

MI> Hi,
MI> I got ASUS P2B M/B & ATX case and assembled new box yesterday.  With
MI> my patch, new box successfully transit into suspend state.  There is
MI> no sounds from CPU fun, chassis fun and IDE HDD spin (powered down by 
MI> BIOS setting, Power management setup -> PM Timers -> HDD Power Down: 
MI> 1 Min.).  The power led keeps flashing during suspending.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: recent apm changes

1999-08-16 Thread Peter Mutsaers

>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes:

MI> Hi,
MI> I got ASUS P2B M/B & ATX case and assembled new box yesterday.  With
MI> my patch, new box successfully transit into suspend state.  There is
MI> no sounds from CPU fun, chassis fun and IDE HDD spin (powered down by 
MI> BIOS setting, Power management setup -> PM Timers -> HDD Power Down: 
MI> 1 Min.).  The power led keeps flashing during suspending.

MI> Without the patch, suspending system is never successful (standby
MI> also), message `slept 00:00:00' comes up :-(
MI> The key release event seems prevent suspend, so some sort of delay
MI> mechanism would be necessary such as my patch.

MI> Now I'm wondering why your PC doesn't get quite.  I suspect that
MI> hardware configuration different from yours (I have no SCSI HD on new
MI> box).  Any suggestions?

After a new cvsup I tried your patch again. Same result. Here is my
dmesg output. It is about the same at boot, but the APM debug output
when suspend is tried is completely different.


Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #9: Mon Aug 16 20:56:59 MET DST 1999
plm@muon:/var/arch/fbsd/src/sys/compile/PLM
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x651  Stepping = 1
  
Features=0x183f9ff
real memory  = 268423168 (262132K bytes)
avail memory = 257990656 (251944K bytes)
Pentium Pro MTRR support enabled
Probing for PnP devices:
CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x1f5ceca5 Comp ID: PNPb02f [0x2fb0d041]
Add hook "pcm resume handler"
Add hook "pcm suspend handler"
pcm1 (SB16pnp  sn 0x1f5ceca5) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa
npx0:  on motherboard
npx0: INT 16 interface
apm0:  on motherboard
apm: APM BIOS version 0102
apm: Code16 0xc00f, Data 0xc00fdbd0
apm: Code entry 0x7770, Idling CPU disabled, Management enabled
apm: CS_limit=0x, DS_limit=0x
apm: Engaged control enabled
apm: found APM BIOS v1.2, connected at v1.2
apm: Slow Idling CPU disabled
Add hook "default suspend"
Add hook "default resume"
pcib0:  on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
vga-pci0:  irq 11 at device 0.0 on pci1
isab0:  at device 4.0 on pci0
ata-pci0:  at device 4.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
chip1:  at device 4.2 on pci0
chip2:  at device 4.3 on pci0
ahc0:  irq 9 at device 9.0 on pci0
ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs
ed0:  irq 10 at device 11.0 on pci0
ed0: address 00:40:95:00:57:83, type NE2000 (16 bit) 
isa0:  on motherboard
fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
psm0:  irq 12 on atkbdc0
psm0: model MouseMan+, device ID 0
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio2 at port 0x3e8-0x3ef irq 4 on isa0
sio2: type 16550A
sio3 at port 0x2e8-0x2ef irq 3 on isa0
sio3: type 16550A
ppc0 at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppb0: IEEE1284 device found /NIBBLE/ECP
Probing for PnP devices on ppbus0:
ppbus0:  MLC,PCL,PML
lpt0:  on ppbus 0
lpt0: Interrupt-driven port
ata0: master: setting up UDMA2 mode on PIIX4 chip OK
ad0:  ATA-4 disk at ata0 as master
ad0: 6485MB (13281408 sectors), 13176 cyls, 16 heads, 63 S/T, 512 B/S
ad0: piomode=4, dmamode=2, udmamode=2
ad0: 16 secs/int, 0 depth queue, DMA mode
ata0: slave: setting up UDMA2 mode on PIIX4 chip OK
ad1:  ATA-4 disk at ata0 as slave 
ad1: 9543MB (19545120 sectors), 19390 cyls, 16 heads, 63 S/T, 512 B/S
ad1: piomode=4, dmamode=2, udmamode=2
ad1: 16 secs/int, 0 depth queue, DMA mode
ata1: master: setting up UDMA2 mode on PIIX4 chip OK
ad2:  ATA-3 disk at ata1 as master
ad2: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S
ad2: piomode=4, dmamode=2, udmamode=2
ad2: 16 secs/int, 0 depth queue, DMA mode
Waiting 5 seconds for SCSI devices to settle
sa0 at ahc0 bus 0 target 6 lun 0
sa0:  Removable Sequential Access SCSI-2 device 
sa0: 5.000MB/s transfers (5.000MHz, offset 11)
changing root device to wd2s1a
APM ioctl: cmd = 0x20005005
called apm_event_enable()
cd0 at ahc0 bus 0 target 0 lun 0
cd0:  Removable CD-ROM SCSI-2 device 
cd0: 10.000MB/s transfers (10.000MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present
cd1 at ahc0 bus 0 target 5 lun 0
cd1:  Removable CD-ROM SCSI-2 device 
cd1: 3.300MB/s transfers
cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not 
reportable

up to here at boot time.

this happens when APM SUS

Re: recent apm changes

1999-08-15 Thread Peter Mutsaers

>> "MS" == Mike Smith <[EMAIL PROTECTED]> writes:

>> >> "MS" == Mike Smith <[EMAIL PROTECTED]> writes:
>> 
>> >> Then after 5 seconds the screen blanks, the power light starts
>> >> flashing (indicating suspend mode), but when I hit a key, the
>> >> console says (slept 00:00:02) only, and programs in fact
>> >> continued running (thus it didn't go or remain in suspend mode
>> >> at all).
>> 
MS> I think you'll find that programs didn't, in fact, continue
MS> running; rather they paused and then resumed when you came out
MS> of suspend.
>> 
>> I'm running seti@home, and it really continued while my
>> computer was 'suspended'. Also a little test program continued
>> running.

MS> What you're failing to offer here, and thus why I remain
MS> skeptical, is any evidence that suggests that these programs
MS> were "running" while the system believed itself to be
MS> suspended.

I can see that after one hour of 'suspend' mode, the program has done
for one hour worth of calculations.

Really, I am not insane and know when my programs have run and done
work and when not.

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED]  |  the Netherlands| what I'm doing. 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: recent apm changes

1999-08-14 Thread Peter Mutsaers

>> "MS" == Mike Smith <[EMAIL PROTECTED]> writes:

>> Then after 5 seconds the screen blanks, the power light starts
>> flashing (indicating suspend mode), but when I hit a key, the
>> console says (slept 00:00:02) only, and programs in fact
>> continued running (thus it didn't go or remain in suspend mode
>> at all).

MS> I think you'll find that programs didn't, in fact, continue
MS> running; rather they paused and then resumed when you came out
MS> of suspend.

I'm running seti@home, and it really continued while my computer was
'suspended'. Also a little test program continued running.

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED]  |  the Netherlands| what I'm doing. 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: recent apm changes

1999-08-12 Thread Peter Mutsaers

>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes:

MI> Please try this patch.
MI> If it still fails, it's worth to try increasing APM_SUSPEND_DELAY, 
MI> something like:
MI> #define APM_SUSPEND_DELAY 3

Alas, it doesn't make a difference.

I tried too with APM_SUSPEND_DELAY 5. What I see when I issue 'zzz',
is a delay of 5 seconds, but in between programs keep running (and
thus keep generating interrupts I guess).

Then after 5 seconds the screen blanks, the power light starts
flashing (indicating suspend mode), but when I hit a key, the console
says (slept 00:00:02) only, and programs in fact continued running
(thus it didn't go or remain in suspend mode at all).

Anyway thanks for you efforts so far.

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED]  |  the Netherlands| what I'm doing. 
---+-+--
Powered by FreeBSD (-current). See http://www.freebsd.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: recent apm changes

1999-08-09 Thread Peter Mutsaers

>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes:

plm> In contract, if I suspend in Linux of Windows, the computer shuts up
plm> immediateley and is quiet. Only sometimes there is a (not too loud)
plm> little fan (I think it is the CPU fan) running for a few more minutes.

MI> I've read Linux code (v2.2.9) closely, noticed they put cli
MI> before APM BIOS call and save & restore segment registers.  I
MI> suspect these two (or only cli?) affect the suspending state.
MI> To clarify, could you try attached patches (for
MI> sys/i386/i386/bioscall.s) one by one?

I've tried them all. They don't make a difference alas.

In doing so, to my surprise I found out that when I suspend my computer
in FreeBSD, it isn't suspended at all!

I have an ATX case with an Asus P2B motherboard. When I suspend my
computer, the power led starts flashing (and keeps doing so).

When I suspend my computer in Linux or Windows, as mentioned, the
computer gets quiet (HDD spins down etc). The led flashes.

Now I found out that when I suspend it in FreeBSD (either with
sleep 1; zzz
or with the suspend button or through the BIOS timer), the led starts
flashing, but processes just keep running! I never paid attention to
it, but I got suspicious because I'm running setiathome which accesses
the harddrive occasionally, and even during suspend mode I heard the
typical HDD sound sometimes.


So the problem is not an incomplete suspend, but no suspend at all. It
seems to suspend at first, the led starts flashing, the screen is
blanked, but somehow the computer keeps running.

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED]  |  the Netherlands| what I'm doing. 
---+-+--
Powered by FreeBSD (-current). See http://www.freebsd.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: recent apm changes

1999-08-08 Thread Peter Mutsaers

>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes:

>> PAO has a small sleep in the apm driver, while -current didn't the
>> last time I looked.

MI> OK, I'll work on this.  

MI> To Peter Mutsaers:
MI> Could you try following command to suspend and see any improvements?
MI>  % sleep 3 && apm -z &

I have done this before, and it does bring the computer into suspend
indeed (light flashes). But for my real problem, noise reduction, this
doesn't help of course. The disks keep spinning, and so do all fans
(CPU or whatever). 

In contract, if I suspend in Linux of Windows, the computer shuts up
immediateley and is quiet. Only sometimes there is a (not too loud)
little fan (I think it is the CPU fan) running for a few more minutes.

regards,

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED]  |  the Netherlands| what I'm doing. 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



recent apm changes

1999-08-05 Thread Peter Mutsaers

Hello,

After Linux I gave FreeBSD a try again, when I saw some improvements
to APM had been committed.

I hoped for a real suspend mode, but alas. Now I'm wondering what
makes the difference, and whether I could do it myself.

Let me explain: I run my (desktop) computer in the living room. I
don't want to shut it down all the time, but it must be 100% quiet
when I'm not using it.

In Linux, when suspend mode is activated (either through a short press
on the power button or by the (BIOS) timer ), the disks also spin down
(immediately, not waiting for their timer, which I disabled) and also
the CPU fan and/or the FAN of the box switches off.

In FreeBSD, when I activate suspend mode, I see the light on my
computer blinking, indicating it has gone into suspend mode, but still
there is no reduction in noise whatsoever. The disks keep spinning,
the CPU fan (or whatever) too. I could activate the BIOS spindown
timer on the HDD's, but I'd rather not (since then I also get
spindowns while I'm normally working with the computer) but still the
other fan will always continue to run.

What can I do to change this behaviour? Can anyone explain what Linux
(or Win95 for that matter) are doing to make it 100% quiet in suspend
mode? Then I could give it a try to have FreeBSD do the
same. Currently this prevents me from using FreeBSD alas.

Thanks,

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED]  |  the Netherlands| what I'm doing. 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Suspend mode

1999-06-29 Thread Peter Mutsaers

A while ago (I think when 3.X was still current) when my (ATX) desktop
system would go in suspend mode (using zzz, waiting for the timeout or
by pushing <4s on the power button) the system would become completely
quiet:

- disks spin down
- CPU fan of


Nowadays, some fan keeps running. This is very annoying (forcing me to
halt -p all the time instead of going to suspend mode) since the
system is in the living room and the noise (even though it is not very
loud) is unacceptable.

I vaguely remember changes to APM some months ago, I think the problem
started back then.

Has something changed some months ago that might have caused this? Is
there a way to have a complete & quiet suspend again?

Thanks in advance,

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED]  |  the Netherlands| what I'm doing. 
---+-+--
Powered by FreeBSD (-current). See http://www.freebsd.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files)

1999-05-04 Thread Peter Mutsaers
>> "RW" == Robert Watson  writes:

RW> So will bitkeeper provide a nice interface for migrating code
RW> from an existing and well-established CVS repository to
RW> whatever they use?

I've looked at bitkeeper and wonder what exactly are it's advantages
over CVS. It's model looks very much geared towards the fragmented way
Linux is developed, offering no advantages for more centralized models
such as FreeBSD or most commercial internal environments.

In the Linux environment the 'patch' is everything, and the kernel
looks like a big pile of 'patches' to me. Thus in bitkeeper generating
these patch sets (containing history & log messages) to submit from
one repository to another is important, because people exchange
patches all the time.

The other thing is some graphic tools (written in tcl/tk) but there
are also some of such GUI layers for CVS, though they've never become
very popular because the command line (combined with UNIX pipes &
std. commands, filters) cannot be beaten for this type of work IMO.

I'd suggest to at least wait a (long) while to see how it is
developing. At the moment I see absolutely no advantage for more
centralized development models.

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
p...@xs4all.nl  |  the Netherlands| what I'm doing. 
---+-+--
Running FreeBSD-current UNIX. See http://www.freebsd.org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



Re: suspend mode broken since one week ago

1999-04-25 Thread Peter Mutsaers
>> "WL" == Warner Losh  writes:

WL> In message <87so9r3x44@muon.xs4all.nl> Peter Mutsaers writes:
WL> : Is this a bug that I should report through send-pr, is it already
WL> : known as a bug or is this an intentional change in behaviour?

WL> This is a known bug.  I thought I kludged around it in apm.c in the
WL> timeframe that you mentioned.  Do you have
WL> $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $
WL> or newer?

Today I did a cvsup which upgraded apm.c from 1.79 to 1.80. Now after
a reboot when X starts, the screen gets garbled and crashes after a
while. When I press the suspend button and resume from suspend, the
system reboots.

I don't know if apm.c is causing this (probably the screen
corruption and crash has another cause).

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
p...@xs4all.nl  |  the Netherlands| what I'm doing. 
---+-+--
Running FreeBSD-current UNIX. See http://www.freebsd.org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



suspend mode broken since one week ago

1999-04-23 Thread Peter Mutsaers
I rebuilt my kernel just after the new config stuff (nexus). Since
then (but I'm not 100% sure it is related to this) my desktop computer
doesn't suspend anymore.

Before that, I could suspend it either by:
- pressing the suspend button 
- zzz command (apm -z)
- wait until BIOS-set time for suspend mode passes

Now it won't suspend in any way anymore (which is irritating since my
computer is in the living room; it must be quiet but I don't want it
to reboot all the time).

Is this a bug that I should report through send-pr, is it already
known as a bug or is this an intentional change in behaviour?


-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
p...@xs4all.nl  |  the Netherlands| what I'm doing. 
---+-+--
Running FreeBSD-current UNIX. See http://www.freebsd.org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



LZS (STAC) compression in i4b?

1999-03-25 Thread Peter Mutsaers
Hello,

Does current i4b support LZS/STAC compression? My ISP just enabled it
on their ISDN ports, I'd like to use it.

Or is compression not necessary in the kernel driver, but in the
userspace programs (ppp, pppd). When I grep through ppp sources I do
see STAC mentioned somewhere.


-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
p...@xs4all.nl  |  the Netherlands| what I'm doing. 
---+-+--
Running FreeBSD-current UNIX. See http://www.freebsd.org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



aic (adaptec 152x) still not supported in -current?

1999-01-18 Thread Peter Mutsaers
Hello,

When CAM was integrated someone reported that the aic driver was not
ready yet for CAM, but that "Brian Beattie  is
working on it".

At the moment, looking in LINT, it looks like aic still isn't
supported. Is that true? Does anyone know whether it will be?

Thanks,

-- 
Peter Mutsaers |  Abcoude (Utrecht), | Trust me, I know
p...@xs4all.nl  |  the Netherlands| what I'm doing. 
---+-+-
Running FreeBSD-3.0 UNIX. See http://www.freebsd.org

To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message