freebsd-stable Digest, Vol 71, Issue 4
freebsd-sta...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. test message - please ignore (Solomon Kounin)
2. Anyone maintaining / care about 4.x anymore ? (Marc G. Fournier)
3. Rumors of 4.x death greatly exagerated (was: Re: Anyone
maintaining / care about 4.x anymore ?) (Robert Watson)
4. Re: ZERO LENGTH DIRECTORY & fsck (Robert Watson)
5. Re: ZERO LENGTH DIRECTORY & fsck (Marc G. Fournier)
6. Re: Rumors of 4.x death greatly exagerated (was: Re:
Anyonemaintaining / care about 4.x anymore ?) (Marc G. Fournier)
7. TEST PLEASE: Synaptics Touchpad on 4-stable (Norikatsu Shigemura)
8. panic: page fault ... in ffs_write / generic_bcopy ...
(Marc G. Fournier)
9. perl5.8 with 4.10 stable? (Warren Pollans)
10. xfce4-panel-4.0.6 (Warren Pollans)
11. Re: perl5.8 with 4.10 stable? (Korey Verlsteffen)
12. Re: perl5.8 with 4.10 stable? (Dmitry Morozovsky)
13. strange top TIME values (Arno J. Klaassen)
14. Re: TEST PLEASE: Synaptics Touchpad on 4-stable (Daniel O'Connor)
15. FreeBSD 4.10 Stable on VMWare 4.5.1 - network problem
(Solomon Kounin)
16. Re: FreeBSD 4.10 Stable on VMWare 4.5.1 - network problem
(Ivan Voras)
17. Re: TEST PLEASE: Synaptics Touchpad on 4-stable (Frederic Hardy)
18. Real Player cant access SMB shared files... (Tony Montana)
19. Re: NEW TAR (Barry Bouwsma)
----------------------------------------------------------------------
Message: 1
Date: Wed, 28 Jul 2004 15:09:04 +0200
From: "Solomon Kounin" <se...@technion.ac.il>
Subject: test message - please ignore
To: <freebsd...@freebsd.org>
Message-ID: <200407281209...@techunix.technion.ac.il>
Content-Type: text/plain; charset="us-ascii"
_____
Solomon Kounin - Biomedical Engineering Dept., Technion
E-mail: se...@technion.ac.il Phone: 054-5556995 (+972-54-5556995)
------------------------------
Message: 2
Date: Wed, 28 Jul 2004 11:24:42 -0300 (ADT)
From: "Marc G. Fournier" <scr...@hub.org>
Subject: Anyone maintaining / care about 4.x anymore ?
To: freebsd...@freebsd.org
Message-ID: <200407281...@ganymede.hub.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Since I'm under the impression that 4.10 is/was meant to be 'end of line',
is anyone looking at / dealing with bug reports for 4.x anymore?
I had a crash yesterday that had a nice clean core dump ... I did submit a
problem report for it, but just curious as to whether its worth submitting
for the 4.x line anymore ?
This isn't a "nobody has looked at it yet" email, since I know everyone is
busy ... this is just a 'is it worth adding to GNaTs for 4.x related bugs
anymore' email ... I'm not sure where -STABLE is sitting in ppls minds
right now :(
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scr...@hub.org Yahoo!: yscrappy ICQ: 7615664
------------------------------
Message: 3
Date: Wed, 28 Jul 2004 10:36:02 -0400 (EDT)
From: Robert Watson <rwa...@FreeBSD.rog>
Subject: Rumors of 4.x death greatly exagerated (was: Re: Anyone
maintaining / care about 4.x anymore ?)
To: "Marc G. Fournier" <scr...@hub.org>
Cc: freebsd...@freebsd.org
Message-ID:
<Pine.NEB.3.96L.104072...@fledge.watson.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 28 Jul 2004, Marc G. Fournier wrote:
> Since I'm under the impression that 4.10 is/was meant to be 'end of
> line', is anyone looking at / dealing with bug reports for 4.x anymore?
Rumors of 4.x's death are greatly exagerated. We plan to continue
supporting 4.x well into the future with security fixes, stability fixes,
and at least one additional release (which would imply additional
features, wot?). The reality is that even if we did "end of life" 4.x, it
would remain in use for years to come, and we're hardly going to ignore
that :-). If you look at the FreeBSD Release Engineering web page, you'll
see that 4.11 is on the impending release list, but doesn't yet have a
schedule assigned. Right now we're largely focussing on getting 5.3 ready
to go out the door.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
rob...@fledge.watson.org Principal Research Scientist, McAfee Research
------------------------------
Message: 4
Date: Wed, 28 Jul 2004 10:39:46 -0400 (EDT)
From: Robert Watson <rwa...@freebsd.org>
Subject: Re: ZERO LENGTH DIRECTORY & fsck
To: "Marc G. Fournier" <scr...@hub.org>
Cc: freebsd...@freebsd.org
Message-ID:
<Pine.NEB.3.96L.104072...@fledge.watson.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 27 Jul 2004, Marc G. Fournier wrote:
> Is there anything that can be done to 'fix' this? Under 4.x, using
> unionfs (and don't respond if your only answer is "its broken"), if it
> crashes, fsck finds a whack of the above ...
It's broken. :-) But in all honesty, this has been discussed extensively,
and it's carefully documented in the man page. So if you run into bugs,
it should not be a surprise.
> Now, I think I understand the *why* for the error ... union creates a
> 'mirror' of the file system, especially where a du/find is concerned,
> and teh ZLDs are 'end nodes' that have no files under them ... but is
> there a better way that fsck can handle those? Its almost as if it
> doesn't know what to do with them, so has to remove them all ...
Are you using union mounting of UFS or unionfs? Theory tells us that
unionfs is a stacked file system layer, and shouldn't directly manipulate
the on-disk layout of UFS, instead, issuing vnode operations that allow
UFS to maintain its consistency guarantees. Theory tells us that union
mounting UFS relies on UFS doing the magic, which means it has more
opportunity to currupt on disk storage.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
rob...@fledge.watson.org Principal Research Scientist, McAfee Research
------------------------------
Message: 5
Date: Wed, 28 Jul 2004 12:25:34 -0300 (ADT)
From: "Marc G. Fournier" <scr...@hub.org>
Subject: Re: ZERO LENGTH DIRECTORY & fsck
To: Robert Watson <rwa...@freebsd.org>
Cc: freebsd...@freebsd.org
Message-ID: <200407281...@ganymede.hub.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Wed, 28 Jul 2004, Robert Watson wrote:
>
> On Tue, 27 Jul 2004, Marc G. Fournier wrote:
>
>> Is there anything that can be done to 'fix' this? Under 4.x, using
>> unionfs (and don't respond if your only answer is "its broken"), if it
>> crashes, fsck finds a whack of the above ...
>
> It's broken. :-) But in all honesty, this has been discussed extensively,
> and it's carefully documented in the man page. So if you run into bugs,
> it should not be a surprise.
It doesn't surprise me, never has ... I've been most appreciatative of the
work/time that ppl like David Schultz and Tor Egge (among others) have put
in to help debug, and fix issues I've been able to provide core files for
... over the past year, unionfs (at least for me) has gone from something
that I can watch a server lock up daily running out of vnodes, to
something that goes for >3 months before a crash/reboot ... its not
perfect, but its 100x better then it was last year ...
>> Now, I think I understand the *why* for the error ... union creates a
>> 'mirror' of the file system, especially where a du/find is concerned,
>> and teh ZLDs are 'end nodes' that have no files under them ... but is
>> there a better way that fsck can handle those? Its almost as if it
>> doesn't know what to do with them, so has to remove them all ...
>
> Are you using union mounting of UFS or unionfs? Theory tells us that
> unionfs is a stacked file system layer, and shouldn't directly manipulate
> the on-disk layout of UFS, instead, issuing vnode operations that allow
> UFS to maintain its consistency guarantees. Theory tells us that union
> mounting UFS relies on UFS doing the magic, which means it has more
> opportunity to currupt on disk storage.
unionfs ... basically, I run:
/sbin/mount_union -b <template>/usr <jailroot>/usr
and then run the jail with <jailroot> ...
the ZLD stuff is what fsck pumps out, generally after I've had a good
uptime run on a server before it crashes ... for instance, yesterday one
of my servers just shy of 52 days uptime crashed, and it took ~7hrs to
fsck the file system, most of it was watching the ZLD messages scrolling
up the screen ...
Today, I had one with only ~26days uptime crash, and the fsck took <20
minutes, with just a few ZLDs ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scr...@hub.org Yahoo!: yscrappy ICQ: 7615664
------------------------------
Message: 6
Date: Wed, 28 Jul 2004 12:27:17 -0300 (ADT)
From: "Marc G. Fournier" <scr...@hub.org>
Subject: Re: Rumors of 4.x death greatly exagerated (was: Re:
Anyonemaintaining / care about 4.x anymore ?)
To: Robert Watson <rwa...@FreeBSD.rog>
Cc: freebsd...@freebsd.org
Message-ID: <200407281...@ganymede.hub.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Wed, 28 Jul 2004, Robert Watson wrote:
>
> On Wed, 28 Jul 2004, Marc G. Fournier wrote:
>
>> Since I'm under the impression that 4.10 is/was meant to be 'end of
>> line', is anyone looking at / dealing with bug reports for 4.x anymore?
>
> Rumors of 4.x's death are greatly exagerated. We plan to continue
> supporting 4.x well into the future with security fixes, stability fixes,
> and at least one additional release (which would imply additional
> features, wot?). The reality is that even if we did "end of life" 4.x, it
> would remain in use for years to come, and we're hardly going to ignore
> that :-). If you look at the FreeBSD Release Engineering web page, you'll
> see that 4.11 is on the impending release list, but doesn't yet have a
> schedule assigned. Right now we're largely focussing on getting 5.3 ready
> to go out the door.
Nope, that's perfect ... thank you for the answer ... personally, I'm
looking forward to 5.x moving into STABLE mode, and starting to shift my
servers over to it :)
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scr...@hub.org Yahoo!: yscrappy ICQ: 7615664
------------------------------
Message: 7
Date: Thu, 29 Jul 2004 02:32:08 +0900
From: Norikatsu Shigemura <no...@FreeBSD.org>
Subject: TEST PLEASE: Synaptics Touchpad on 4-stable
To: freebsd...@FreeBSD.org
Message-ID: <20040729023208...@FreeBSD.org>
Content-Type: text/plain; charset="us-ascii"
I wrote synaptic touchpad driver for 4-stable, based on
Arne Schwabe's driver. I don't have synaptic touchpad
on 4-stable. I just did compile test. I don't know
whether or not good :-). So please test.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: synaptic-stable.diff
Type: application/octet-stream
Size: 11428 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040729/c0d010da/synaptic-stable-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: synaptics.shar
Type: application/octet-stream
Size: 2661 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040729/c0d010da/synaptics-0001.obj
------------------------------
Message: 8
Date: Wed, 28 Jul 2004 14:52:27 -0300 (ADT)
From: "Marc G. Fournier" <scr...@hub.org>
Subject: panic: page fault ... in ffs_write / generic_bcopy ...
To: freebsd...@freebsd.org
Message-ID: <200407281...@ganymede.hub.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
I have two *nice* core files right now, or at least look nice to me ... I
put one in through GNaTs yesterday, but after a short period of uptime,
its panic'd a second time, so figured I'd post the trace here as well ...
in case someone glances at it and has an idea?
(kgdb) where
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
#1 0x801522eb in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316
#2 0x8015275d in panic (fmt=0x80275399 "%s") at /usr/src/sys/kern/kern_shutdown.c:595
#3 0x8023fa41 in trap_fatal (frame=0xb892e750, eva=0) at /usr/src/sys/i386/i386/trap.c:974
#4 0x8023f6ad in trap_pfault (frame=0xb892e750, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:867
#5 0x8023f20b in trap (frame={tf_fs = -1774387176, tf_es = -2042626032, tf_ds = -2042626032, tf_edi = -1509507072, tf_esi = 0,
tf_ebp = -1198331972, tf_isp = -1198332036, tf_ebx = 8192, tf_edx = -1509507072, tf_ecx = 2048, tf_eax = -1509507072,
tf_trapno = 12, tf_err = 0, tf_eip = -2145131498, tf_cs = 8, tf_eflags = 66054, tf_esp = -1198331732, tf_ss = -1198331760})
at /usr/src/sys/i386/i386/trap.c:466
#6 0x8023e416 in generic_bcopy ()
#7 0x801f5b65 in ffs_write (ap=0xb892e854) at /usr/src/sys/ufs/ufs/ufs_readwrite.c:547
#8 0x80191451 in union_write (ap=0xb892e898) at vnode_if.h:363
#9 0x8020cca8 in vnode_pager_generic_putpages (vp=0xca66d740, m=0xb892e970, bytecount=8192, flags=12, rtvals=0xb892e93c)
at vnode_if.h:363
#10 0x801912c2 in union_putpages (ap=0xb892e900) at /usr/src/sys/miscfs/union/union_vnops.c:1047
#11 0x8020caca in vnode_pager_putpages (object=0xc4c81958, m=0xb892e970, count=2, sync=12, rtvals=0xb892e93c) at vnode_if.h:1147
#12 0x80209a0f in vm_pageout_flush (mc=0xb892e970, count=2, flags=12) at /usr/src/sys/vm/vm_pager.h:147
#13 0x8020697b in vm_object_page_collect_flush (object=0xc4c81958, p=0x828b23b0, curgeneration=47865, pagerflags=12)
at /usr/src/sys/vm/vm_object.c:806
#14 0x80206559 in vm_object_page_clean (object=0xc4c81958, start=0, end=0, flags=4) at /usr/src/sys/vm/vm_object.c:605
#15 0x80182b08 in vfs_msync (mp=0x8fd6c600, flags=2) at /usr/src/sys/kern/vfs_subr.c:2731
#16 0x80183c80 in sync (p=0x802c5440, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:582
#17 0x80152086 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:235
#18 0x8015275d in panic (fmt=0x80275399 "%s") at /usr/src/sys/kern/kern_shutdown.c:595
#19 0x8023fa41 in trap_fatal (frame=0xb892ebc4, eva=0) at /usr/src/sys/i386/i386/trap.c:974
#20 0x8023f6ad in trap_pfault (frame=0xb892ebc4, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:867
#21 0x8023f20b in trap (frame={tf_fs = -1851260904, tf_es = -2146303984, tf_ds = -1989672944, tf_edi = -1464680448, tf_esi = 0,
tf_ebp = -1198330832, tf_isp = -1198330896, tf_ebx = 8192, tf_edx = -1464680448, tf_ecx = 2048, tf_eax = -1464680448,
tf_trapno = 12, tf_err = 0, tf_eip = -2145131498, tf_cs = 8, tf_eflags = 66054, tf_esp = -1198330592, tf_ss = -1198330620})
at /usr/src/sys/i386/i386/trap.c:466
#22 0x8023e416 in generic_bcopy ()
#23 0x801f5b65 in ffs_write (ap=0xb892ecc8) at /usr/src/sys/ufs/ufs/ufs_readwrite.c:547
#24 0x80191451 in union_write (ap=0xb892ed0c) at vnode_if.h:363
#25 0x8020cca8 in vnode_pager_generic_putpages (vp=0xc83f83c0, m=0xb892ede4, bytecount=8192, flags=12, rtvals=0xb892edb0)
at vnode_if.h:363
#26 0x801912c2 in union_putpages (ap=0xb892ed74) at /usr/src/sys/miscfs/union/union_vnops.c:1047
#27 0x8020caca in vnode_pager_putpages (object=0xc7076170, m=0xb892ede4, count=2, sync=12, rtvals=0xb892edb0) at vnode_if.h:1147
#28 0x80209a0f in vm_pageout_flush (mc=0xb892ede4, count=2, flags=12) at /usr/src/sys/vm/vm_pager.h:147
#29 0x8020697b in vm_object_page_collect_flush (object=0xc7076170, p=0x835e4830, curgeneration=25361, pagerflags=12)
at /usr/src/sys/vm/vm_object.c:806
#30 0x80206559 in vm_object_page_clean (object=0xc7076170, start=0, end=0, flags=4) at /usr/src/sys/vm/vm_object.c:605
#31 0x80182b08 in vfs_msync (mp=0x8fd6c600, flags=2) at /usr/src/sys/kern/vfs_subr.c:2731
#32 0x80182ed6 in sync_fsync (ap=0xb892ef7c) at /usr/src/sys/kern/vfs_subr.c:2992
#33 0x801811bf in sched_sync () at vnode_if.h:558
(kgdb) up 7
#7 0x801f5b65 in ffs_write (ap=0xb892e854) at /usr/src/sys/ufs/ufs/ufs_readwrite.c:547
547 error =
(kgdb) list
542
543 size = BLKSIZE(fs, ip, lbn) - bp->b_resid;
544 if (size < xfersize)
545 xfersize = size;
546
547 error =
548 uiomove((char *)bp->b_data + blkoffset, (int)xfersize, uio);
549 if ((ioflag & (IO_VMIO|IO_DIRECT)) &&
550 (LIST_FIRST(&bp->b_dep) == NULL)) {
551 bp->b_flags |= B_RELBUF;
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scr...@hub.org Yahoo!: yscrappy ICQ: 7615664
------------------------------
Message: 9
Date: Wed, 28 Jul 2004 14:52:01 -0400
From: Warren Pollans <war...@meyer-pollans.net>
Subject: perl5.8 with 4.10 stable?
To: freebsd...@freebsd.org
Message-ID: <20040728145...@localhost.localdomain>
Content-Type: text/plain; charset=US-ASCII
Hello,
I'd like to upgrade perl on my recently installed 4.10 box - the current perl version is 5.005_03. Do I download the source and build/install it - and then re-install the perl modules? Or is there a cvsup/portupgrade way of doing this? I have cvsup'd (ports-all tag=.) and portupgrade'd (arR) - but I still have the old perl. :-( Sorry, I'm new to freebsd. I have also cvsup'd (src-all) and rebuilt the kernel.
Any suggestions and/or redirection appreciated. The box appears to work fine - I'd just like to have a newer perl
Thanks,
Warren
------------------------------
Message: 10
Date: Wed, 28 Jul 2004 16:48:02 -0400
From: Warren Pollans <war...@meyer-pollans.net>
Subject: xfce4-panel-4.0.6
To: freebsd...@freebsd.org
Message-ID: <20040728164...@localhost.localdomain>
Content-Type: text/plain; charset=US-ASCII
Hello,
I just upgraded xfce (4.10) and get the following when I try access xfce4-panel properties (the panel is also missing from the settings window): 'Multi-Channel Manager Error: No such plugin "xfce"'. I deinstalled and reinstalled xfce4-panel after getting this error - there were no errors reported - xfce4-panel seemed to build without any problems.
How can I fix this?
Thanks,
Warren
------------------------------
Message: 11
Date: Wed, 28 Jul 2004 17:13:28 -0400
From: "Korey Verlsteffen" <ko...@webstream.net>
Subject: Re: perl5.8 with 4.10 stable?
To: <freebsd...@freebsd.org>
Message-ID: <00ff01c474e7$bbb86db0$0a01a8c0@kv>
Content-Type: text/plain; charset="iso-8859-1"
>I'd like to upgrade perl on my recently installed 4.10 box - the current perl
version is 5.005_03. Do I download the >source and build/install it - and then
re-install the perl modules? Or is there a cvsup/portupgrade way of doing
>this? I have cvsup'd (ports-all tag=.) and portupgrade'd (arR) - but I still
have the old perl. :-( Sorry, I'm new >to freebsd. I have also cvsup'd
(src-all) and rebuilt the kernel.
>Any suggestions and/or redirection appreciated. The box appears to work fine -
I'd just like to have a newer perl
Type the following:
cd /usr/ports/lang/perl5.8
make install clean
use.perl port
------------------------------
Message: 12
Date: Thu, 29 Jul 2004 01:50:38 +0400 (MSD)
From: Dmitry Morozovsky <ma...@rinet.ru>
Subject: Re: perl5.8 with 4.10 stable?
To: Korey Verlsteffen <ko...@webstream.net>
Cc: freebsd...@freebsd.org
Message-ID: <2004072901...@woozle.rinet.ru>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 28 Jul 2004, Korey Verlsteffen wrote:
KV> >I'd like to upgrade perl on my recently installed 4.10 box - the current perl
KV> version is 5.005_03. Do I download the >source and build/install it - and then
KV> re-install the perl modules? Or is there a cvsup/portupgrade way of doing
KV> >this? I have cvsup'd (ports-all tag=.) and portupgrade'd (arR) - but I still
KV> have the old perl. :-( Sorry, I'm new >to freebsd. I have also cvsup'd
KV> (src-all) and rebuilt the kernel.
KV>
KV> >Any suggestions and/or redirection appreciated. The box appears to work fine -
KV> I'd just like to have a newer perl
KV>
KV>
KV> Type the following:
KV>
KV> cd /usr/ports/lang/perl5.8
KV>
KV> make install clean
KV>
KV> use.perl port
... and then
portupgrade -f 'p5-*'
since most perl modules don't like new system-wide perl or even note it...
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***
------------------------------------------------------------------------
------------------------------
Message: 13
Date: 29 Jul 2004 01:36:39 +0200
From: "Arno J. Klaassen" <ar...@heho.snv.jussieu.fr>
Subject: strange top TIME values
To: freebsd...@freebsd.org
Message-ID: <wpsmbby...@heho.snv.jussieu.fr>
Content-Type: text/plain; charset=us-ascii
Hello,
I see the following on a dual PPro -stable; same sources
(and config, apart form ethernet driver) on UP Athlon and
SMP PIII work OK :
######
last pid: 259; load averages: 1.70, 1.63, 1.07 up 0+00:19:05 14:18:32
38 processes: 4 running, 34 sleeping
CPU states: 9.6% user, 0.0% nice, 15.6% system, 25.6% interrupt, 49.3% idle
Mem: 52M Active, 86M Inact, 39M Wired, 7068K Cache, 29M Buf, 572K Free
Swap: 246M Total, 12K Used, 246M Free
PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
246 root 64 0 17976K 17548K RUN 1 96:14 57.13% 57.13% rsync
222 root 45 0 17740K 17300K RUN 1 225:05 34.52% 34.52% rsync
213 arno 31 0 5292K 1732K CPU1 1 0:43 10.11% 10.11% sshd
119 root 10 0 212K 28K nfsidl 0 164:34 1.32% 1.32% nfsiod
223 root 2 0 17720K 17292K select 0 2:04 0.73% 0.73% rsync
120 root 10 0 212K 28K nfsidl 0 0:10 0.20% 0.20% nfsiod
253 arno 28 0 1908K 996K CPU0 0 0:10 0.00% 0.00% top
######
box is up just 19 minutes, but top shows 96, 225, 164 minutes for
various processes.
This is just a backup-server and works OK;
top -I -s1 shows seconds just going up as expected and then suddenly
the minutes jump high.
No problem other whatsoever, I vaguely remember -current has the same
"problem" for some.
FYI, Arno
------------------------------
Message: 14
Date: Thu, 29 Jul 2004 10:18:25 +0930
From: "Daniel O'Connor" <doco...@gsoft.com.au>
Subject: Re: TEST PLEASE: Synaptics Touchpad on 4-stable
To: freebsd...@freebsd.org
Cc: Norikatsu Shigemura <no...@freebsd.org>
Message-ID: <200407291018....@gsoft.com.au>
Content-Type: Text/Plain; charset="iso-8859-1"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 29 Jul 2004 03:02, Norikatsu Shigemura wrote:
> I wrote synaptic touchpad driver for 4-stable, based on
> Arne Schwabe's driver. I don't have synaptic touchpad
> on 4-stable. I just did compile test. I don't know
> whether or not good :-). So please test.
I don't suppose you'd want to add support to moused instead of XFree86? :)
(Then XFree86 gets it for free..)
- --
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFBCElZ5ZPcIHs/zowRAsZTAJ4sFbYY94qwiy7JdLYzjg/HwW+TFQCdGZzS
H9v1sndKJSs4dTbA+URlJyg=
=xRRe
-----END PGP SIGNATURE-----
------------------------------
Message: 15
Date: Thu, 29 Jul 2004 03:48:59 +0200
From: "Solomon Kounin" <se...@technion.ac.il>
Subject: FreeBSD 4.10 Stable on VMWare 4.5.1 - network problem
To: <freebsd...@freebsd.org>
Message-ID: <200407290049...@techunix.technion.ac.il>
Content-Type: text/plain; charset="US-ASCII"
Hello
I've recently installed FreeBSD 4.10 - STABLE on VMWare 4.5.1 and some
strange errors/warnings are showing up from time to time in the log file:
Jul 28 14:43:25 vmware /kernel: lnc0: Missed packet -- no receive buffer
Jul 28 16:02:48 vmware /kernel: lnc0: Missed packet -- no receive buffer
Jul 28 17:47:51 vmware /kernel: lnc0: Missed packet -- no receive buffer
Jul 28 17:54:08 vmware /kernel: lnc0: Missed packet -- no receive buffer
Jul 28 18:52:00 vmware /kernel: lnc0: Missed packet -- no receive buffer
Any ideas?
Thanks in advance.
Here is my kernel configuration file:
machine i386
cpu I686_CPU
ident VMWARE
maxusers 512
#makeoptions DEBUG=-g #Build kernel with gdb(1) debug
symbols
#options MATH_EMULATE #Support for x87 emulation
options INET #InterNETworking
#options INET6 #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT #FFS usable as root device [keep
this!]
options SOFTUPDATES #Enable FFS soft updates support
options UFS_DIRHASH #Improve performance on big
directories
#options MFS #Memory Filesystem
#options MD_ROOT #MD is a potential root device
#options NFS #Network Filesystem
#options NFS_ROOT #NFS usable as root device, NFS
required
#options MSDOSFS #MSDOS Filesystem
options CD9660 #ISO 9660 Filesystem
#options CD9660_ROOT #CD-ROM usable as root, CD9660
required
options PROCFS #Process filesystem
options COMPAT_43 #Compatible with BSD 4.3 [KEEP
THIS!]
options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI
#options UCONSOLE #Allow users to grab the console
#options USERCONFIG #boot -c editor
#options VISUAL_USERCONFIG #visual boot -c editor
#options KTRACE #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B #Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM #Rate limit bad replies
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
#options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
#options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~215k to driver.
# To make an SMP kernel, the next two are needed
#options SMP # Symmetric MultiProcessor Kernel
#options APIC_IO # Symmetric (APIC) I/O
device isa
device pci
device agp # support several AGP chipsets
# ATA and ATAPI devices
device ata0 at isa? port IO_WD1 irq 14
device ata1 at isa? port IO_WD2 irq 15
device ata
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
#device atapifd # ATAPI floppy drives
#device atapist # ATAPI tape drives
options ATA_STATIC_ID #Static device numbering
# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc0 at isa? port IO_KBD
device atkbd0 at atkbdc? irq 1 flags 0x1
device psm0 at atkbdc? irq 12
device vga0 at isa?
# splash screen/screen saver
pseudo-device splash
# syscons is the default console driver, resembling an SCO console
device sc0 at isa? flags 0x100
# Floating point support - do not disable.
device npx0 at nexus? port IO_NPX irq 13
# Power management support (see LINT for more options)
#device apm0 at nexus? disable flags 0x20 # Advanced Power
Management
# PCI Ethernet NICs.
#device de # DEC/Intel DC21x4x (``Tulip'')
#device em # Intel PRO/1000 adapter Gigabit Ethernet
Card (``Wiseman'')
#device txp # 3Com 3cR990 (``Typhoon'')
#device vx # 3Com 3c590, 3c595 (``Vortex'')
# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device miibus # MII bus support
#device dc # DEC/Intel 21143 and various workalikes
#device fxp # Intel EtherExpress PRO/100B (82557, 82558)
#device pcn # AMD Am79C97x PCI 10/100 NICs
#device rl # RealTek 8129/8139
#device sf # Adaptec AIC-6915 (``Starfire'')
#device sis # Silicon Integrated Systems SiS 900/SiS
7016
#device ste # Sundance ST201 (D-Link DFE-550TX)
#device tl # Texas Instruments ThunderLAN
#device tx # SMC EtherPower II (83c170 ``EPIC'')
#device vr # VIA Rhine, Rhine II
#device wb # Winbond W89C840F
#device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')
#device bge # Broadcom BCM570x (``Tigon III'')
# ISA Ethernet NICs.
# 'device ed' requires 'device miibus'
#device ed0 at isa? disable port 0x280 irq 10 iomem 0xd8000
#device ex
#device ep
#device fe0 at isa? disable port 0x300
# Xircom Ethernet
#device xe
# PRISM I IEEE 802.11b wireless NIC.
#device awi
# WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really
# exists only as a PCMCIA device, so there is no ISA attachment needed
# and resources will always be dynamically assigned by the pccard code.
#device wi
# Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will
# work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP
# mode (the factory default). If you set the switches on your ISA
# card for a manually chosen I/O address and IRQ, you must specify
# those parameters here.
#device an
# The probe order of these is presently determined by i386/isa/isa_compat.c.
#device ie0 at isa? disable port 0x300 irq 10 iomem 0xd0000
#device le0 at isa? disable port 0x300 irq 5 iomem 0xd0000
#device lnc0 at isa? disable port 0x280 irq 10 drq 0
device lnc # (VMWare NIC) Probe for lnc on PCI
#device cs0 at isa? disable port 0x300
#device sn0 at isa? disable port 0x300 irq 10
# Pseudo devices - the number indicates how many units to allocate.
pseudo-device loop # Network loopback
pseudo-device ether # Ethernet support
#pseudo-device sl 1 # Kernel SLIP
#pseudo-device ppp 1 # Kernel PPP
#pseudo-device tun # Packet tunnel.
pseudo-device pty # Pseudo-ttys (telnet etc)
#pseudo-device md # Memory "disks"
#pseudo-device gif # IPv6 and IPv4 tunneling
#pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation)
# The `bpf' pseudo-device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
pseudo-device bpf #Berkeley packet filter
# Firewall support
options IPFILTER
options IPFILTER_LOG
options RANDOM_IP_ID
________________________________
Solomon Kounin - Biomedical Engineering Dept., Technion
E-mail: se...@technion.ac.il Phone: 054-5556995 (+972-54-5556995)
------------------------------
Message: 16
Date: Thu, 29 Jul 2004 02:57:00 +0200
From: Ivan Voras <ivo...@fer.hr>
Subject: Re: FreeBSD 4.10 Stable on VMWare 4.5.1 - network problem
To: se...@technion.ac.il, sta...@freebsd.org
Message-ID: <41084B5C...@fer.hr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Solomon Kounin wrote:
> Hello
>
> I've recently installed FreeBSD 4.10 - STABLE on VMWare 4.5.1 and some
> strange errors/warnings are showing up from time to time in the log file:
>
> Jul 28 14:43:25 vmware /kernel: lnc0: Missed packet -- no receive buffer
> Jul 28 16:02:48 vmware /kernel: lnc0: Missed packet -- no receive buffer
> Jul 28 17:47:51 vmware /kernel: lnc0: Missed packet -- no receive buffer
> Jul 28 17:54:08 vmware /kernel: lnc0: Missed packet -- no receive buffer
> Jul 28 18:52:00 vmware /kernel: lnc0: Missed packet -- no receive buffer
I notice the same errors on FreeBSD 5-current under "heavy" traffic. It
seems that vmware is emulating a 10mbit NIC, and the messages pop up
when the traffic gets heavy. It seems that they are only warning
messages, as everything works fine. (ignore them)
--
What part of "Ph'nglui mglw'nath Cthulhu R'lyeh wgah'nagl fhtagn" don't
you understand?
------------------------------
Message: 17
Date: Thu, 29 Jul 2004 09:29:48 +0200
From: Frederic Hardy <f.h...@hexanet.fr>
Subject: Re: TEST PLEASE: Synaptics Touchpad on 4-stable
To: Norikatsu Shigemura <no...@FreeBSD.org>
Cc: freebsd...@FreeBSD.org
Message-ID: <4108A76C...@hexanet.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
synaptics.c:55: sys/mouse.h: No such file or directory
In file included from synaptics.c:80:
synaptics.h:25: sys/mouse.h: No such file or directory
gmake: *** [synaptics.o] Erreur 1
*** Error code 2
:-(
Best regards,
Fred
Norikatsu Shigemura wrote:
> I wrote synaptic touchpad driver for 4-stable, based on
> Arne Schwabe's driver. I don't have synaptic touchpad
> on 4-stable. I just did compile test. I don't know
> whether or not good :-). So please test.
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>freebsd...@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
>
>
------------------------------
Message: 18
Date: Thu, 29 Jul 2004 03:35:39 -0700 (PDT)
From: Tony Montana <tonymon...@yahoo.com>
Subject: Real Player cant access SMB shared files...
To: freebsd...@freebsd.org
Message-ID: <2004072910353...@web20226.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
I set up a few smb shares with mount points in /
After loading the shares succesfully, real player
returns an error messsage to the tune of "cannot find
address, address may have moved. check the path" while
trying to play a .rm file on the mout point.
The real player works fine for files on the local
computer so as far as i know the player is working
fine other than that.
I had this working fine under 4.9, not sure what has
happened. Any ideas? tia
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
------------------------------
Message: 19
Date: Thu, 29 Jul 2004 13:59:20 +0200 (CEST)
From: Barry Bouwsma
<freebsd...@remove-NOSPAM-to-reply.NOSPAM.dyndns.dk>
Subject: Re: NEW TAR
To: Tim Kientzle <kien...@freebsd.org>
Cc: sta...@freebsd.org
Message-ID: <200407291159...@Mail.NOSPAM.DynDNS.dK>
[introduced to freebsd-stable@ , don't bother replying directly to me]
On Sat, 17 Jul 2004 10:37:28 -0700, Tim Kientzle proclaimed:
> By default, /usr/bin/tar is now a symlink pointing
> to /usr/bin/bsdtar.
[in -current]
[...]
> * Portability: gtar is portable to many different Unix and non-Unix
> systems. bsdtar supports standard file formats that are widely
> supported by other implementations. There are efforts to port
> bsdtar to other platforms.
Would it be possible to include patches similar to (or based
upon) the following diffs, in order to get `bsdtar' to compile
cleanly under my (older) 4.x -- based on checking out HEAD of
libarchive and bsdtar from the CVS repository? (I haven't looked
for source otherwise, sorry; this is to make an future MFC more
compatible with older 4.x)
--- bsdtar_platform.h-ORIG Sun Jul 25 10:51:11 2004
+++ bsdtar_platform.h Sun Jul 25 11:48:16 2004
@@ -43,8 +43,10 @@
#define HAVE_CHFLAGS 1
#define ARCHIVE_STAT_MTIME_NANOS(st) (st)->st_mtimespec.tv_nsec
+#if __FreeBSD_version >= 450002 /* nl_langinfo introduced */
/* nl_langinfo supports D_MD_ORDER (FreeBSD extension) */
#define HAVE_NL_LANGINFO_D_MD_ORDER 1
+#endif
#if __FreeBSD__ > 4
#define HAVE_GETOPT_LONG 1
--- write.c-ORIG Sun Jul 25 10:51:11 2004
+++ write.c Sun Jul 25 11:56:30 2004
@@ -52,6 +52,13 @@
#include "bsdtar.h"
+/* #if __FreeBSD_version < ??? XXX not present in my 4.x ... */
+#ifndef _ID_T_DECLARED
+typedef __int64_t id_t;
+#define _ID_T_DECLARED
+#endif /* XXXX HACK how to do this right? what about other OSen?? */
+
+
/* Fixed size of uname/gname caches. */
#define name_cache_size 101
As you see, I'm not sure how to best handle id_t above.
My source may be outdated, being some ten days old.
thanks,
barry bouwsma
------------------------------
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
End of freebsd-stable Digest, Vol 71, Issue 4
*********************************************