freebsd-stable Digest, Vol 71, Issue 5
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. MFC of Realtek if_re support? (Barry Bouwsma)
2. Re: perl5.8 with 4.10 stable? (Warren Pollans)
3. Re: perl5.8 with 4.10 stable? (Matthew Seaman)
4. Re: perl5.8 with 4.10 stable? (Warren Pollans)
5. Re: real player & SMB shares (Tony Montana)
6. Re: TEST PLEASE: Synaptics Touchpad on 4-stable
(Norikatsu Shigemura)
7. Re: TEST PLEASE: Synaptics Touchpad on 4-stable
(Norikatsu Shigemura)
8. Looking for ntp/PPS setup guide (Gregory Bond)
9. Re: Looking for ntp/PPS setup guide (Kevin Oberman)
10. Panic in ufs_dirhash.c 5.2.1-RELEASE-p9 help? (Paul Tatarsky)
11. Re: Looking for ntp/PPS setup guide (Harlan Stenn)
12. Re: NEW TAR (Tim Kientzle)
13. Re: permissions (Malcolm Kay)
14. Re: nullfs in 4.10 (Brian Buchanan)
15. clarification regarding netgraph and ipfw (Glenn Dawson)
16. Re: clarification regarding netgraph and ipfw (Glenn Dawson)
17. RE: clarification regarding netgraph and ipfw
(Alexander Vasenin aka BlackSir)
----------------------------------------------------------------------
Message: 1
Date: Thu, 29 Jul 2004 14:28:06 +0200 (CEST)
From: Barry Bouwsma
<freebsd...@remove-NOSPAM-to-reply.NOSPAM.dyndns.dk>
Subject: MFC of Realtek if_re support?
To: FreeBSD Stable <freebsd...@freebsd.org>
Message-ID: <200407291228...@Mail.NOSPAM.DynDNS.dK>
Yeah, yeah, and all that.
Is there any plan to either MFC the if_re Realtek driver with
support for GigEthernet into 4.x, or less likely, unrevert the
reversion of if_rl which had early support for some chipsets,
reverted right before a release when it apparently broke other
support, and bring that up-to-date?
I've tried out the un-reverted if_rl with my newly-purchased
card just for fun, where it's clear that more additions are
needed to the code from that point of time to make it coexist
with my card. Also, it's not the way of -current.
Then I tried hacking the if_re from -current to shoehorn it
into compiling with my -stable, and after a disturbing number
of hacks whose correctness I cannot vouch for (I'm no hacker
or programmer and have no idea what I'm doing), finally got
something that compiled, woo.
After adding rgephy to miibus, I'm able to kldload the if_re
kernel module and it actually recognizes my card:
re0: <RealTek 8169S Single-chip Gigabit Ethernet> port 0x6200-0x62ff mem 0xe1002000-0xe10020ff irq 9 at device 10.0 on pci0
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S media interface> on miibus0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
bpf: re0 attached
After a few days of additional hacking, I'm able to `ifconfig'
it to actually do something, too. I'd almost say it works, but
I don't really have the network to test it.
There seem to be a number of minor issues, like I can't force
100Mbit full-duplex, while autoselect works fine to give me
full-duplex 100Mbit, but I see the same thing under the NetBSD-
current import of the driver. (I don't have FreeBSD-current
ability at the moment.)
My hacks are uglier than sin, and I'd prefer that someone
who actually knows what they are doing make a patch for -stable,
but I'll grudgingly share my hideous hacks privately with any
interested parties.
I haven't tried this card other than connected to a fast switch,
and under any OS but my 4.x (and a brief foray into NetBSD-current)
yet, and I thought it would be best to pass this to some expert
who might know more than I do.
And by the way, I'm curious whether anyone can say anything about
this chip, like whether the comments about other Realtek chipsets
apply, or what. (For the price I paid, I don't expect stellar
performance, but I'm curious how it stacks up against the others.)
thanks
barry bouwsma
------------------------------
Message: 2
Date: Thu, 29 Jul 2004 10:01:33 -0400
From: Warren Pollans <war...@meyer-pollans.net>
Subject: Re: perl5.8 with 4.10 stable?
To: freebsd...@freebsd.org
Message-ID: <20040729100...@localhost.localdomain>
Content-Type: text/plain; charset=US-ASCII
Thanks, do I also need to deinstall the old version?
On Thu, 29 Jul 2004 01:50:38 +0400 (MSD)
Dmitry Morozovsky <ma...@rinet.ru> wrote:
> 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 ***
> ------------------------------------------------------------------------
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
------------------------------
Message: 3
Date: Thu, 29 Jul 2004 15:54:49 +0100
From: Matthew Seaman <m.se...@infracaninophile.co.uk>
Subject: Re: perl5.8 with 4.10 stable?
To: Warren Pollans <war...@meyer-pollans.net>
Cc: freebsd...@freebsd.org
Message-ID:
<20040729145...@happy-idiot-talk.infracaninophile.co.uk>
Content-Type: text/plain; charset="us-ascii"
[perl 5.003.05 as bundled with 4.x systems]
On Thu, Jul 29, 2004 at 10:01:33AM -0400, Warren Pollans wrote:
> Thanks, do I also need to deinstall the old version?
Not unless you're a neatness freak. Having the old version around is
pretty harmless usually. Leave it lying about on the disk, or delete
it -- makes little difference. Nb. don't delete /usr/bin/perl as
that's now a symlink to the ports version of perl you will have
installed.
Cheers,
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
-------------- 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-stable/attachments/20040729/82beb782/attachment-0001.bin
------------------------------
Message: 4
Date: Thu, 29 Jul 2004 11:24:00 -0400
From: Warren Pollans <war...@meyer-pollans.net>
Subject: Re: perl5.8 with 4.10 stable?
To: freebsd...@freebsd.org
Message-ID: <20040729112...@localhost.localdomain>
Content-Type: text/plain; charset=US-ASCII
thank you - that's what I needed to know - I am a bit of a neatness freak but I'll try to exercise some restraint :-)
On Thu, 29 Jul 2004 15:54:49 +0100
Matthew Seaman <m.se...@infracaninophile.co.uk> wrote:
> [perl 5.003.05 as bundled with 4.x systems]
>
> On Thu, Jul 29, 2004 at 10:01:33AM -0400, Warren Pollans wrote:
> > Thanks, do I also need to deinstall the old version?
>
> Not unless you're a neatness freak. Having the old version around is
> pretty harmless usually. Leave it lying about on the disk, or delete
> it -- makes little difference. Nb. don't delete /usr/bin/perl as
> that's now a symlink to the ports version of perl you will have
> installed.
>
> Cheers,
>
> --
> Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
> Savill Way
> PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
> Tel: +44 1628 476614 Bucks., SL7 1TH UK
>
------------------------------
Message: 5
Date: Thu, 29 Jul 2004 08:45:04 -0700 (PDT)
From: Tony Montana <tonymon...@yahoo.com>
Subject: Re: real player & SMB shares
To: freebsd...@freebsd.org
Message-ID: <2004072915450...@web20221.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Ok, further info on the situation:
I am running 4.10 and trying to access a windows 2000
pro machine which i successfully did under 4.9 with
the same exact configurations and commands as follows.
In fstab i have:
//<User>@192.x.x.x/O$ /mnt/share/O$ smbfs
rw,noauto,nodev,nosuid -N, -I=192.168.1.100 0 0
//<User>@192.x.x.x/J$ /mnt/share/J$ smbfs
rw,noauto,nodev,nosuid -N, -I=192.168.1.100 0 0
in /etx/nsmb.conf:
[SHAREHOST:SHAREUSER]
addr=192.x.x.x
password=<password>
the command i issue is
mount_smbfs -I 192.x.x.x //S-HOST@S-USER/O
/mnt/share/O
I commented out the ip and the hostnames obviously.
Other than the real player not accessing the files it
works fine. Mp3 files on the shares work fine as do
documents. I run the mount command as su as i did in
4.9. I use to get that even tho "su" would mount the
drives, "user" would get a link to the mounts on the
desktop(strange i thought) I no longer get that which
is good but now real player cant get those .rm.
It seems to me that its a real player problem but i
didnt have to make any changes to it in 4.9 i dont
know what they would have to be in 4.10
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
------------------------------
Message: 6
Date: Fri, 30 Jul 2004 01:33:33 +0900 (JST)
From: Norikatsu Shigemura <no...@FreeBSD.org>
Subject: Re: TEST PLEASE: Synaptics Touchpad on 4-stable
To: Frederic Hardy <f.h...@hexanet.fr>
Cc: freebsd...@FreeBSD.org
Message-ID: <200407291633....@sakura.ninth-nine.com>
Content-Type: text/plain; charset="us-ascii"
On Thu, 29 Jul 2004 09:29:48 +0200
Frederic Hardy <f.h...@hexanet.fr> wrote:
> 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
> :-(
Oops, please add attached patch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: synaptics-extra-patches.shar
Type: application/octet-stream
Size: 1990 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040730/5ed562f6/synaptics-extra-patches-0001.obj
------------------------------
Message: 7
Date: Fri, 30 Jul 2004 01:34:31 +0900 (JST)
From: Norikatsu Shigemura <no...@FreeBSD.org>
Subject: Re: TEST PLEASE: Synaptics Touchpad on 4-stable
To: "Daniel O'Connor" <doco...@gsoft.com.au>
Cc: freebsd...@FreeBSD.org
Message-ID: <200407291634....@sakura.ninth-nine.com>
Content-Type: text/plain; charset=US-ASCII
On Thu, 29 Jul 2004 10:18:25 +0930
"Daniel O'Connor" <doco...@gsoft.com.au> 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..)
Sorry, I have no idea. Anyone, please support it:-).
------------------------------
Message: 8
Date: Fri, 30 Jul 2004 09:38:32 +1000
From: Gregory Bond <g...@itga.com.au>
Subject: Looking for ntp/PPS setup guide
To: freebsd...@freebsd.org
Message-ID: <2004072923...@lightning.itga.com.au>
Content-Type: text/plain; charset=us-ascii
We've got a GPS receiver to make an NTP server, and it has PPS output. Is
there a guide to how to set up PPS on recent (4.10-ish) FreeBSD boxes? Or I
can put it on a 5.x box if that is better. I've had a look in all the obvious
places but the only references I can find are to old (load a line discipline or
patch a kernel) solutions.
------------------------------
Message: 9
Date: Thu, 29 Jul 2004 17:02:05 -0700
From: "Kevin Oberman" <obe...@es.net>
Subject: Re: Looking for ntp/PPS setup guide
To: Gregory Bond <g...@itga.com.au>
Cc: freebsd...@freebsd.org
Message-ID: <200407300002...@ptavv.es.net>
> From: Gregory Bond <g...@itga.com.au>
> Date: Fri, 30 Jul 2004 09:38:32 +1000
> Sender: owner-free...@freebsd.org
>
>
> We've got a GPS receiver to make an NTP server, and it has PPS output.
> Is there a guide to how to set up PPS on recent (4.10-ish) FreeBSD
> boxes? Or I can put it on a 5.x box if that is better. I've had a
> look in all the obvious places but the only references I can find are
> to old (load a line discipline or patch a kernel) solutions.
I'd suggest the documentation at www.ntp.org, but it has a few errors
and lacks a bit of FreeBSD specific bits.
First off, you will need to rebuild ntpd with the appropriate reference
clocks, pps and whatever type of GPS you have. The software is in
/usr/src/contrib/ntp/ntpd. You can look at the list of clock drivers and
pick the one you need. If you look at the driver source, you will see
that REFCLOCK and a driver specific variable need to be defined.
Go to /usr/src/usr.sbin/ntp/ntpd and rebuild ntpd with the clock driver:
make clean
make -DREFCLOCK -DCLOCK_yourclock
make install
You need to rebuild you kernel with "options PPS_SYNC". You can run PPS
without this and the man page even says it's more accurate that way, but
my experience is that it is much more accurate with the kernel option.
I use CDMA clocks and they my time is stable within 10 microseconds.
I did find that nptd 4.2 seemed to converge better than 4.1, so I built
the ntp port instead of the standard one. I then just installed the ntpd
from the port over the one in /usr/sbin. 4.2 is now the standard NTP in
version 5 and I suspect it will be MFCed to STABLE soon.
Read the manual pages for pps and your GPS clock driver for how to set
up ntp.conf for that clock. You will need to set up kernel PPS there.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: obe...@es.net Phone: +1 510 486-8634
------------------------------
Message: 10
Date: Thu, 29 Jul 2004 17:31:50 -0700
From: Paul Tatarsky <pa...@soe.ucsc.edu>
Subject: Panic in ufs_dirhash.c 5.2.1-RELEASE-p9 help?
To: freebsd...@freebsd.org
Cc: pa...@services.cse.ucsc.edu
Message-ID: <200407300031....@services.cse.ucsc.edu>
I'm not sure if this is the right place to post this. I
hope 5.2.1-RELEASE is considered part of this list. If
not, I apologize. I don't know much about debuging kernel
crashes in FreeBSD so here goes trying to provide enough
information about the problem:
I am running 5.2.1-RELEASE-p9.
FreeBSD hgdownload 5.2.1-RELEASE-p9 FreeBSD 5.2.1-RELEASE-p9 #1: Thu Jul 29 08:29:56 PDT 2004 root@hgdownload:/usr/src/sys/i386/compile/HGDOWNLOAD i386
On a Dell 2650 with a PERC3/QC. Both data area and boot/swap drive is on
the PERC3/QC drives. Separate logical drives.
Recently, under heavy load (rsync download server for genome data) system
has repeatably crashed with the following gdb -k output every time:
(NOTE, the nullfs module is because we do a few loopback mounts)
panic: mtx_lock() of spin mutex (null) @ ../../../ufs/ufs/ufs_dirhash.c:282
panic messages:
---
panic: mtx_lock() of spin mutex (null) @ ../../../ufs/ufs/ufs_dirhash.c:282
Stack backtrace:
Uptime: 7h24m50s
Dumping 2047 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 1024 1040 1056 1072 1088 1104 1120 1136 1152 1168 1184 1200 1216 1232 1248 1264 1280 1296 1312 1328 1344 1360 1376 1392 1408 1424 1440 1456 1472 1488 1504 1520 1536 1552 1568 1584 1600 1616 1632 1648 1664 1680 1696 1712 1728 1744 1760 1776 1792 1808 1824 1840 1856 1872 1888 1904 1920 1936 1952 1968 1984 2000 2016 2032
---
Reading symbols from /usr/src/sys/i386/compile/HGDOWNLOAD/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done.
Loaded symbols for /usr/src/sys/i386/compile/HGDOWNLOAD/modules/usr/src/sys/modules/acpi/acpi.ko.debug
Reading symbols from /usr/src/sys/i386/compile/HGDOWNLOAD/modules/usr/src/sys/modules/nullfs/nullfs.ko.debug...done.
Loaded symbols for /usr/src/sys/i386/compile/HGDOWNLOAD/modules/usr/src/sys/modules/nullfs/nullfs.ko.debug
#0 doadump () at ../../../kern/kern_shutdown.c:240
240 dumping++;
(kgdb) where
#0 doadump () at ../../../kern/kern_shutdown.c:240
#1 0xc04c8158 in boot (howto=260) at ../../../kern/kern_shutdown.c:372
#2 0xc04c84e7 in panic () at ../../../kern/kern_shutdown.c:550
#3 0xc04be773 in _mtx_lock_flags (m=0x0, opts=0,
file=0xc0674938 "../../../ufs/ufs/ufs_dirhash.c", line=282)
at ../../../kern/kern_mutex.c:215
#4 0xc05d9eab in ufsdirhash_free (ip=0xc8c85578)
at ../../../ufs/ufs/ufs_dirhash.c:282
#5 0xc05dbf44 in ufs_reclaim (ap=0x0) at ../../../ufs/ufs/ufs_inode.c:182
#6 0xc05e3eb8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2793
#7 0xc0521c08 in vclean (vp=0xc8c9f514, flags=8, td=0xc8248640)
at vnode_if.h:981
#8 0xc0522171 in vgonel (vp=0xc8c9f514, td=0x0)
at ../../../kern/vfs_subr.c:2788
#9 0xc051e15a in vtryrecycle (vp=0xc8c9f514) at ../../../kern/vfs_subr.c:898
#10 0xc051e3e9 in getnewvnode (tag=0xc066da2c "ufs", mp=0x0, vops=0x0, vpp=0x0)
at ../../../kern/vfs_subr.c:960
#11 0xc05d4be5 in ffs_vget (mp=0xc8235c00, ino=187006288, flags=2,
vpp=0xee5aea4c) at ../../../ufs/ffs/ffs_vfsops.c:1268
#12 0xc05dcd12 in ufs_lookup (ap=0xee5aeb10)
at ../../../ufs/ufs/ufs_lookup.c:603
#13 0xc05e3eb8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2793
#14 0xc0514ca1 in vfs_cache_lookup (ap=0x0) at vnode_if.h:82
#15 0xc05e3eb8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2793
#16 0xc0519ed2 in lookup (ndp=0xee5aec28) at vnode_if.h:52
#17 0xc05198be in namei (ndp=0xee5aec28) at ../../../kern/vfs_lookup.c:183
#18 0xc0527262 in lstat (td=0xc8248640, uap=0xee5aed14)
at ../../../kern/vfs_syscalls.c:2030
#19 0xc06339e0 in syscall (frame=
{tf_fs = 134742063, tf_es = 134742063, tf_ds = -1078001617, tf_edi = 134563840, tf_esi = 134563912, tf_ebp = -1077940936, tf_isp = -296030860, tf_ebx = 672370976, tf_edx = 134524928, tf_ecx = 0, tf_eax = 190, tf_trapno = 12, tf_err = 2, tf_eip = 671863887, tf_cs = 31, tf_eflags = 582, tf_esp = -1077941092, tf_ss = 47}) at ../../../i386/i386/trap.c:1010
#20 0xc062483d in Xint0x80_syscall () at {standard input}:136
---Can't read userspace from dump, or kernel process---
Kernel Config is as follows, note we are running it uniprocessor
to try to rule out SMP problems. We have also turned off logical
processors (hyperthreading).
machine i386
cpu I686_CPU
ident HGDOWNLOAD
options SCHED_4BSD #4BSD scheduler
options INET #InterNETworking
options INET6 #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES #Enable FFS soft updates support
options UFS_ACL #Support for access control lists
options UFS_DIRHASH #Improve performance on big directories
options MD_ROOT #MD is a potential root device
options NFSCLIENT #Network Filesystem Client
options NFSSERVER #Network Filesystem Server
options NFS_ROOT #NFS usable as /, requires NFSCLIENT
options MSDOSFS #MSDOS Filesystem
options CD9660 #ISO 9660 Filesystem
options PROCFS #Process filesystem (requires PSEUDOFS)
options PSEUDOFS #Pseudo-filesystem framework
options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI
options KTRACE #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions
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.
options PFIL_HOOKS # pfil(9) framework
makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols
options DDB
options DDB_TRACE
options DDB_UNATTENDED
ptions INVARIANTS #Enable calls of extra sanity checking
options INVARIANT_SUPPORT #Extra sanity checks of internal structur
# To make an SMP kernel, the next two are needed
#options SMP # Symmetric MultiProcessor Kernel
#device apic # I/O APIC
device isa
device pci
device scbus # SCSI bus (required for SCSI)
device ch # SCSI media changers
device da # Direct Access (disks)
device sa # Sequential Access (tape etc)
device cd # CD
device pass # Passthrough device (direct SCSI access)
device ses # SCSI Environmental Services (and SAF-TE)
device amr # AMI MegaRAID
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse
device vga # VGA video card driver
device splash # Splash screen and screen saver support
# syscons is the default console driver, resembling an SCO console
device sc
device agp # support several AGP chipsets
# Floating point support - do not disable.
device npx
# Add suspend/resume support for the i8254.
device pmtimer
# Serial (COM) ports
device sio # 8250, 16[45]50 based serial ports
# Parallel port
device ppc
device ppbus # Parallel port bus (required)
device lpt # Printer
device ppi # Parallel port interface device
# 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 bfe # Broadcom BCM440x 10/100 ethernet
device bge # Broadcom BCM570xx Gigabit Ethernet
device random # Entropy device
device loop # Network loopback
device ether # Ethernet support
device ppp # Kernel PPP
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
device md # Memory "disks"
device gif # IPv6 and IPv4 tunneling
device faith # IPv6-to-IPv4 relaying (translation)
Dmesg output follows:
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.2.1-RELEASE-p9 #1: Thu Jul 29 08:29:56 PDT 2004
root@hgdownload:/usr/src/sys/i386/compile/HGDOWNLOAD
Preloaded elf kernel "/boot/kernel/kernel" at 0xc07a8000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc07a821c.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2784.39-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf29 Stepping = 9
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
real memory = 2147352576 (2047 MB)
avail memory = 2084798464 (1988 MB)
Pentium Pro MTRR support enabled
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <DELL PE2650 > on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
pcibios: BIOS version 2.10
Using $PIR table, 9 entries at 0xc00fc410
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_cpu0: <CPU> on acpi0
acpi_cpu1: <CPU> on acpi0
device_probe_and_attach: acpi_cpu1 attach returned 6
acpi_cpu1: <CPU> on acpi0
device_probe_and_attach: acpi_cpu1 attach returned 6
acpi_cpu1: <CPU> on acpi0
device_probe_and_attach: acpi_cpu1 attach returned 6
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib0: slot 4 INTA is routed to irq 11
pcib0: slot 4 INTB is routed to irq 10
pcib0: slot 4 INTC is routed to irq 7
pcib0: slot 15 INTA is routed to irq 5
pci0: <unknown> at device 4.0 (no driver attached)
pci0: <unknown> at device 4.1 (no driver attached)
pci0: <unknown> at device 4.2 (no driver attached)
pci0: <display, VGA> at device 14.0 (no driver attached)
pci0: <mass storage, ATA> at device 15.1 (no driver attached)
pci0: <serial bus, USB> at device 15.2 (no driver attached)
isab0: <PCI-ISA bridge> at device 15.3 on pci0
isa0: <ISA bus> on isab0
pcib1: <ACPI Host-PCI bridge> on acpi0
pci6: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 8.0 on pci6
pci7: <ACPI PCI bus> on pcib2
pcib2: slot 6 INTA is routed to irq 7
pcib2: slot 6 INTB is routed to irq 11
pci7: <mass storage, SCSI> at device 6.0 (no driver attached)
pci7: <mass storage, SCSI> at device 6.1 (no driver attached)
pcib3: <ACPI Host-PCI bridge> on acpi0
pci5: <ACPI PCI bus> on pcib3
pcib3: slot 6 INTA is routed to irq 11
pcib3: slot 8 INTA is routed to irq 10
bge0: <Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002> mem 0xeff10000-0xeff
1ffff irq 11 at device 6.0 on pci5
bge0: Ethernet address: 00:0d:56:ba:cd:45
miibus0: <MII bus> on bge0
brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX
-FDX, auto
bge1: <Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002> mem 0xeff00000-0xeff
0ffff irq 10 at device 8.0 on pci5
bge1: Ethernet address: 00:0d:56:ba:cd:46
miibus1: <MII bus> on bge1
brgphy1: <BCM5703 10/100/1000baseTX PHY> on miibus1
brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX
-FDX, auto
pcib4: <ACPI Host-PCI bridge> on acpi0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI Host-PCI bridge> on acpi0
pci1: <ACPI PCI bus> on pcib5
pcib6: <PCI-PCI bridge> at device 8.0 on pci1
pci2: <PCI bus> on pcib6
pcib5: slot 8 INTB is routed to irq 11
pcib6: slot 1 INTA is routed to irq 11
pcib5: slot 8 INTC is routed to irq 10
pcib6: slot 2 INTA is routed to irq 10
pcib7: <PCI-PCI bridge> at device 0.0 on pci2
pci3: <PCI bus> on pcib7
pcib5: slot 8 INTA is routed to irq 7
pcib6: slot 0 INTA is routed to irq 7
pcib7: slot 0 INTA is routed to irq 7
amr0: <LSILogic MegaRAID> mem 0xf0000000-0xf7ffffff irq 7 at device 0.0 on pci3
amr0: <LSILogic PERC 3/QC> Firmware 196T, BIOS 3.33, 128MB RAM
pci2: <mass storage, SCSI> at device 1.0 (no driver attached)
pci2: <mass storage, SCSI> at device 2.0 (no driver attached)
fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port 0x3f7,0x3f0-0
x3f5 irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
acpi_cpu1: <CPU> on acpi0
device_probe_and_attach: acpi_cpu1 attach returned 6
acpi_cpu1: <CPU> on acpi0
device_probe_and_attach: acpi_cpu1 attach returned 6
acpi_cpu1: <CPU> on acpi0
device_probe_and_attach: acpi_cpu1 attach returned 6
pmtimer0 on isa0
orm0: <Option ROMs> at iomem 0xec000-0xeffff,0xca800-0xcbfff,0xc8000-0xc8fff,0xc
0000-0xc7fff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 2784393264 Hz quality 800
Timecounters tick every 10.000 msec
amrd0: <LSILogic MegaRAID logical drive> on amr0
amrd0: 34680MB (71024640 sectors) RAID 1 (optimal)
GEOM: create disk amrd0 dp=0xc81fa40c
amrd1: <LSILogic MegaRAID logical drive> on amr0
amrd1: 1818700MB (3724697600 sectors) RAID 5 (optimal)
GEOM: create disk amrd1 dp=0xc81fa30c
Mounting root from ufs:/dev/amrd0s1a
WARNING: / was not properly dismounted
bge0: gigabit link up
Does anyone have suggestions on what I can do to debug this further?
The unit did have some hardware problems, but we've swapped out all
the components involved and updated firmware of critical components.
At least we think we have to proper levels.
Any help anyone could provide would be greatly appreciated.
--------------------------------------------------------------------
Paul Tatarsky pa...@cse.ucsc.edu
UC Santa Cruz http://www.cse.ucsc.edu/~paul
CBSE Cluster Project Sysadmin SOE Network Security Advisor
--------------------------------------------------------------------
------------------------------
Message: 11
Date: Thu, 29 Jul 2004 22:08:00 -0400
From: Harlan Stenn <Harlan...@pfcs.com>
Subject: Re: Looking for ntp/PPS setup guide
To: Gregory Bond <g...@itga.com.au>
Cc: freebsd...@freebsd.org
Message-ID: <16365.10...@dog.pfcs.com>
Content-Type: text/plain; charset=US-ASCII
There should be a start at twiki.ntp.org .
If there isn't, it has been a hot topic lately.
H
------------------------------
Message: 12
Date: Thu, 29 Jul 2004 20:01:47 -0700
From: Tim Kientzle <kien...@freebsd.org>
Subject: Re: NEW TAR
Cc: sta...@freebsd.org
Message-ID: <4109BA1B...@freebsd.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Barry Bouwsma wrote:
>
> 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 ...
Done. Thanks for the input. Let me know if you
find anything else.
Tim Kientzle
------------------------------
Message: 13
Date: Fri, 30 Jul 2004 15:03:55 +0930
From: Malcolm Kay <malco...@internode.on.net>
Subject: Re: permissions
To: "Amiel Ong" <amie...@votek.com.ph>, <freebsd...@freebsd.org>
Message-ID: <200407301503.55...@internode.on.net>
Content-Type: text/plain; charset="iso-8859-1"
On Saturday 24 July 2004 17:00, Amiel Ong wrote:
> How can I make a directory permission so that
> the user can write but cannot delete a file inside the directory?
>
I suspect you mean "create" rather than "write".
Some of the responses to your query seem to be unnecessarily complicated.
I think you are looking for the same permissions as normally apply to
the /tmp directory which can be achieved with:
$ chmod ugo+xrwt my-special-directory
If you want any user to be able to "write" to an "existing" file in the
directory then in general I believe the permissions on that particular
file must permit write for that user:
$ chmod o+rw particular-file
Ability to write an existing file does relate the ability to delete it.
The latter depends on the permissions of the directory containing the
file, as indeed does the ability to create a file.
Malcolm
------------------------------
Message: 14
Date: Thu, 29 Jul 2004 23:25:27 -0700 (PDT)
From: Brian Buchanan <b...@holo.org>
Subject: Re: nullfs in 4.10
To: t...@freebsd.org
Cc: sta...@freebsd.org
Message-ID: <2004072923132...@thought.holo.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Tim,
I've been experimenting with your nullfs patch for 4-STABLE. I've found
that I can easily reproduce a bug involving one nullfs mounted inside
another nullfs. It appears that the null_lock for the vnode representing
the root directory of the interior nullfs does not get released. Any
subsequent process attempting to traverse into that part of the filesystem
gets stuck waiting in "nullnode".
What I'm doing is:
mount_nullfs -o ro /usr/jail/template /usr/jail/jail1
mount_nullfs -o ro /usr/ports /usr/jail/jail1/usr/ports
head /usr/jail/jail1/usr/ports/Makefile
head /usr/jail/jail1/usr/ports/Makefile
(hangs)
/usr/jail/template contains a fresh FreeBSD distribution.
/usr/ports is NFS-mounted from a remote host.
If instead of the "head ..." stuff, I do a "find /usr/jail/jail1/usr/ports
-type f", the system promptly panics with "draining against myself".
This appears to be due to attempting a LK_DRAIN operation against the root
dir vnode lock that the process still holds.
Unfortunately, due to my inexperience with filesystem locking in FreeBSD,
I haven't been able to determine why the lock isn't being released. I
just thought I'd provide some feedback in case you're still working on
this.
- B
--
Brian Buchanan, CISSP b...@holo.org
--------------------------------------------------------------------------
FreeBSD - The Power to Serve http://www.freebsd.org
------------------------------
Message: 15
Date: Thu, 29 Jul 2004 23:59:44 -0700
From: Glenn Dawson <gl...@antimatter.net>
Subject: clarification regarding netgraph and ipfw
To: sta...@freebsd.org
Message-ID: <6.1.0.6.2.200407...@cobalt.antimatter.net>
Content-Type: text/plain; charset="us-ascii"; format=flowed
Greetings,
I have a firewall running -STABLE. I'm using ipfw2 for filtering and
ng_netgraph (via ng_tee) to export netflow data.
According to the man page for ng_ether, the lower hook gets raw ethernet
frames as they come off the wire. Reading the man page for ipfw it seems
to say that if I turn on net.link.ether.ipfw in sysctl that it will also
get things as they come off the wire.
So my question is, which one gets them first?
The reason I ask is that if I have an ipfw rule to block traffic from an
IP, will it get counted by ng_netgraph? Or will ipfw drop the packet
before it even gets to ng_ether?
If the packets go through ng_ether first and then through ipfw, does anyone
know if it's possible to reverse that behavior? I'm doing billing based on
traffic and don't want the netflow data to include packets that were
dropped by ipfw.
Thanks in advance for any insight.
-Glenn
------------------------------
Message: 16
Date: Fri, 30 Jul 2004 00:10:48 -0700
From: Glenn Dawson <gl...@antimatter.net>
Subject: Re: clarification regarding netgraph and ipfw
To: sta...@freebsd.org
Message-ID: <6.1.0.6.2.200407...@cobalt.antimatter.net>
Content-Type: text/plain; charset="us-ascii"; format=flowed
oops
s/ng_netgraph/ng_netflow/g
-Glenn
At 11:59 PM 7/29/2004, Glenn Dawson wrote:
>Greetings,
>
>I have a firewall running -STABLE. I'm using ipfw2 for filtering and
>ng_netgraph (via ng_tee) to export netflow data.
>
>According to the man page for ng_ether, the lower hook gets raw ethernet
>frames as they come off the wire. Reading the man page for ipfw it seems
>to say that if I turn on net.link.ether.ipfw in sysctl that it will also
>get things as they come off the wire.
>
>So my question is, which one gets them first?
>
>The reason I ask is that if I have an ipfw rule to block traffic from an
>IP, will it get counted by ng_netgraph? Or will ipfw drop the packet
>before it even gets to ng_ether?
>
>If the packets go through ng_ether first and then through ipfw, does
>anyone know if it's possible to reverse that behavior? I'm doing billing
>based on traffic and don't want the netflow data to include packets that
>were dropped by ipfw.
>
>Thanks in advance for any insight.
>
>-Glenn
>
>_______________________________________________
>freebsd...@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
------------------------------
Message: 17
Date: Fri, 30 Jul 2004 11:47:13 +0400
From: "Alexander Vasenin aka BlackSir" <blac...@number.ru>
Subject: RE: clarification regarding netgraph and ipfw
To: "Glenn Dawson" <gl...@antimatter.net>, <sta...@freebsd.org>
Message-ID: <NKEJKOHEKMBIMCCEHE...@number.ru>
Content-Type: text/plain; charset="us-ascii"
Maybe this is rather crucial solution, but ng_netflow can deal with raw IP (and not only ethernet), so, you can set 'divert' or 'tee' rule for passing traffic from arbitrary place in ipfw to ng_ksocket, which connected to ng_netflow (which export NetFlow through another ng_ksocket). I use tee (with 'tee' patch, described in PR/60377).
Alexander Vasenin aka BlackSir
> -----Original Message-----
> From: owner-free...@freebsd.org
> [mailto:owner-free...@freebsd.org]On Behalf Of Glenn Dawson
> Sent: Friday, July 30, 2004 11:00 AM
> To: sta...@freebsd.org
> Subject: clarification regarding netgraph and ipfw
>
>
>
> Greetings,
>
> I have a firewall running -STABLE. I'm using ipfw2 for filtering and
> ng_netgraph (via ng_tee) to export netflow data.
>
> According to the man page for ng_ether, the lower hook gets raw ethernet
> frames as they come off the wire. Reading the man page for ipfw it seems
> to say that if I turn on net.link.ether.ipfw in sysctl that it will also
> get things as they come off the wire.
>
> So my question is, which one gets them first?
>
> The reason I ask is that if I have an ipfw rule to block traffic from an
> IP, will it get counted by ng_netgraph? Or will ipfw drop the packet
> before it even gets to ng_ether?
>
> If the packets go through ng_ether first and then through ipfw, does anyone
> know if it's possible to reverse that behavior? I'm doing billing based on
> traffic and don't want the netflow data to include packets that were
> dropped by ipfw.
>
> Thanks in advance for any insight.
>
> -Glenn
>
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
>
------------------------------
_______________________________________________
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 5
*********************************************