Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 Starfire ethernet controller driver and plus question compaq presario dec et

[Dirk GOUDERS]

o.k., Bill, I'll try to translate it for you:

   $B?9ED$G$9!#(B

My name is Morita.

   
These are Adaptec's replacements for its older DEC 21x4x-based multiport
   
   $B$3$N%I%i%$%P!$OL5$/$J$k$N$G$7$g$$+!)(B-DEC 21x4x-based
   no more supllyed -DEC 21x4x-based

Are these drivers lost? 
(Maybe in the meaning of no more supported.)

  
  Sorry, but I'm just a dumb american: I can't read this.
   
line of adapters. All cards support 10/100 speeds in full or half duplex
.
The multiport cards consist of multiple AIC-6915 chips linkec via a PCI
to PCI bridge. Currently I have only tested the ANA-62022 dual port card
,
however all of them should work equally well. The 64-bit cards will work
in a 32-bit slot on most newer machines.
   
   
   
 $B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!%k$7$?$N$G$9$,!"(B
   NIC$B!'!!(BDEC 21143-based 
 $B$H%S%G%*%+!%I!'(BSiS5598$B$N@_Dj$,$$^$/$$$-$^$;$s!"8=:_(B
   $BF0$+$7$F$k(B
   $BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B

I installed FreeBSD 3.2 on a Compaq PRESARIO 2274 but my DEC
21143-based NIC and SiS5598 video card do not work well (maybe at all).
Can you please tell me, how to get them work?

  
  I can't read this either. :(

I guess, I understood the question, but I cannot answer it.
Can you?

Dirk

  
  -Bill
  
  -- 
  
=
  -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
  Work: [EMAIL PROTECTED] | Center for Telecommunications Researc
h
  Home:  [EMAIL PROTECTED] | Columbia University, New York City
  
=
   "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
  
=
  
  
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with "unsubscribe freebsd-hackers" in the body of the message


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

Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's

On Wed, 21 Jul 1999, Vincent Poy wrote:

 Greetings everyone,
 
   What are the current good motherboards for FreeBSD for the pentium
 II and III?  I know on the Pentium, it was the ASUS board but for the
 PII/PIII, is the Abit the better board?  Also, I was wondering what is the
 fastest Celeron chip that can be overclocked to run at 100Mhz FSB?  Does
 it matter if it's Slot 1 or PPGA based?  Thanks.

My home box based Abit BX6 rev.2.0 Slot1  i use PPGA Celeron-300A with
Socket370-Slot1 bridge overclocked to 450 (100x4.5) with Pelitier
element. This motherboard support PII/PIII.
More overclockers says: Abit better then Asus. I think it right.
All works fine.

Rgdz,
Sergey Osokin aka oZZ,
[EMAIL PROTECTED]
http://www.freebsd.org.ru



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

Re: Will FreeBSD ever see native IPv6 ??

[John Hay]

Are you just teasing or are you serious?

I searched through their site (again), but except for being mentioned
in their TODO for the past few months, I can't find anything that
indicates that they or anyone else is working on it. They may be, but
it isn't visible anywhere where I have looked. It would be nice if
there was some place to follow their progress, because I'm also one
of the people that would like to see IPv6 integrated into FreeBSD.

John
-- 
John Hay -- [EMAIL PROTECTED]

 
 FreeBSD will have native IPV6 within a matter of weeks at this stage.. 
 the code is being readied as we speak.  see www.kame.net . 3 sets of
 developers for FreeBSD IPV6 have merged their efforts and the result of
 this should be available by the end of summer (Northern).  (which isn't
 far away now..) 
 
 On Wed, 21 Jul 1999, David O'Brien wrote:
 
  So is FreeBSD *EVER* going to see native IPv6 ??
  I attended a talk by a group of Intrusion Detection researchers.  They
  were basing their research on FreeBSD because they needed divert
  sockets and found FreeBSD worked perfectly for this in this respect.
  However, once they needed IPv6 and IPsec guess what happened???  They
  moved to Linux and now have such a time investment in their custom kernel
  hacks FreeBSD will never be an option for them again.
  
  NetBSD and OpenBSD get more and more coverage from IPv6/IPsec
  capabilities every day.  FreeBSD has lost considerable ground if we want
  to be a platform of choice for network and security researchers.
  
  Now ever LSOF has IPv6 support for NetBSD and OpenBSD...




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

Re: Anyone know how to dim and SGI flat panel?

[Doug Rabson]

On Thu, 22 Jul 1999, Matthew Dillon wrote:

 
 :
 :I'd bet it's done using DPMS.  See if the XFree86 4.x code can tell you 
 :anything about the monitor's capabilities.
 
 It's up?  Very cool, they actually put the prerelease up 2 days ago!
 47MB download, yummy!  DGA is going to be so cool.
 
 Unfortunately it looks like the DPMS stuff is still a bit primitive.
 Shoot.  I'll check it out, though.  The 3.3.3 I128 driver (that's
 the number 9 card) does not appear to support DPMS at all.
 
 SGI's site has a whitepaper on the flatpanel but it's a bit spare on
 control protocols.  They do say something about an I2C bus but I dunno
 whether that is what DPMS uses or not.

XFree86 has an i2c driver in it for talking to monitors so it sounds as if
it should see it.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




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

Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's

[Vincent Poy]

On Thu, 22 Jul 1999, [KOI8-R] óÅÒÇÅÊ ïÓÏËÉÎ wrote:

 On Wed, 21 Jul 1999, Vincent Poy wrote:
 
  Greetings everyone,
  
  What are the current good motherboards for FreeBSD for the pentium
  II and III?  I know on the Pentium, it was the ASUS board but for the
  PII/PIII, is the Abit the better board?  Also, I was wondering what is the
  fastest Celeron chip that can be overclocked to run at 100Mhz FSB?  Does
  it matter if it's Slot 1 or PPGA based?  Thanks.
 
 My home box based Abit BX6 rev.2.0 Slot1  i use PPGA Celeron-300A with
 Socket370-Slot1 bridge overclocked to 450 (100x4.5) with Pelitier
 element. This motherboard support PII/PIII.
 More overclockers says: Abit better then Asus. I think it right.
 All works fine.

Pretty interesting...  The Pelitier element is pretty expensive I
think...  It seems like I've seen more Abit than ASUS Boards when it's a
FreeBSD box.  We have a 266 running at 400 (100x4) but I don't know which
Pentium II would it be the closest to since this is a cacheless chip.  It
has 384 megs of ram and one thing I can't figure out is that the machine
will sometimes pause for a few seconds when I type a command...


Cheers,
Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED]      __  
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
GaiaNet Corporation - M  C Estate / / / /  | /  | __] ]  
Beverly Hills, California USA 90210   / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]



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

IDE breakage

[Dag-Erling Smorgrav]

I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
on recent versions of -STABLE. Here's an excerpt from messages; kernel
#3 is a recent -STABLE (yesterday's sources), while kernel #2 is
3.2-RELEASE. The config file for both is identical.

Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1992-1999 FreeBSD Inc.
Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 22 10:19:35 xxx /kernel.old: The Regents of the University of California. All 
rights reserved.
Jul 22 10:19:35 xxx /kernel.old: FreeBSD 3.2-STABLE #3: Wed Jul 21 16:21:55 CEST 1999
Jul 22 10:19:35 xxx /kernel.old: [EMAIL PROTECTED]:/usr/src/sys/compile/X
Jul 22 10:19:35 xxx /kernel.old: Timecounter "i8254"  frequency 1193182 Hz
Jul 22 10:19:35 xxx /kernel.old: Timecounter "TSC"  frequency 348205681 Hz
Jul 22 10:19:35 xxx /kernel.old: CPU: Pentium II/Xeon/Celeron (348.21-MHz 686-class 
CPU)
Jul 22 10:19:35 xxx /kernel.old: Origin = "GenuineIntel"  Id = 0x652  Stepping = 2
Jul 22 10:19:35 xxx /kernel.old: 
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
Jul 22 10:19:35 xxx /kernel.old: real memory  = 134217728 (131072K bytes)
Jul 22 10:19:35 xxx /kernel.old: avail memory = 127774720 (124780K bytes)
Jul 22 10:19:35 xxx /kernel.old: Preloaded elf kernel "kernel" at 0xc023c000.
Jul 22 10:19:35 xxx /kernel.old: Probing for devices on PCI bus 0:
Jul 22 10:19:35 xxx /kernel.old: chip0: Intel 82443BX host to PCI bridge rev 0x02 on 
pci0.0.0
Jul 22 10:19:35 xxx /kernel.old: chip1: Intel 82443BX host to AGP bridge rev 0x02 on 
pci0.1.0
Jul 22 10:19:35 xxx /kernel.old: xl0: 3Com 3c905-TX Fast Etherlink XL rev 0x00 int a 
irq 11 on pci0.13.0
Jul 22 10:19:35 xxx /kernel.old: xl0: Ethernet address: 00:60:08:e8:6b:1d
Jul 22 10:19:35 xxx /kernel.old: xl0: autoneg complete, link status good (full-duplex, 
100Mbps)
Jul 22 10:19:35 xxx /kernel.old: chip2: Intel 82371AB PCI to ISA bridge rev 0x02 on 
pci0.20.0
Jul 22 10:19:35 xxx /kernel.old: ide_pci0: Intel PIIX4 Bus-master IDE controller rev 
0x01 on pci0.20.1
Jul 22 10:19:35 xxx /kernel.old: chip3: Intel 82371AB Power management controller 
rev 0x02 on pci0.20.3
Jul 22 10:19:35 xxx /kernel.old: Probing for devices on PCI bus 1:
Jul 22 10:19:35 xxx /kernel.old: vga0: ATI model 4742 graphics accelerator rev 0x5c 
int a irq 11 on pci1.0.0
Jul 22 10:19:35 xxx /kernel.old: Probing for PnP devices:
Jul 22 10:19:35 xxx /kernel.old: Probing for devices on the ISA bus:
Jul 22 10:19:35 xxx /kernel.old: sc0 on isa
Jul 22 10:19:35 xxx /kernel.old: sc0: VGA color 16 virtual consoles, flags=0x0
Jul 22 10:19:35 xxx /kernel.old: atkbdc0 at 0x60-0x6f on motherboard
Jul 22 10:19:35 xxx /kernel.old: atkbd0 irq 1 on isa
Jul 22 10:19:35 xxx /kernel.old: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
Jul 22 10:19:35 xxx /kernel.old: fdc0: FIFO enabled, 8 bytes threshold
Jul 22 10:19:35 xxx /kernel.old: fd0: 1.44MB 3.5in
Jul 22 10:19:35 xxx /kernel.old: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
Jul 22 10:19:35 xxx /kernel.old: wdc0: unit 0 (wd0): Maxtor 90640D4, DMA, 32-bit, 
multi-block-16
Jul 22 10:19:35 xxx /kernel.old: wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 
63 S/T, 512 B/S
Jul 22 10:19:35 xxx /kernel.old: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
Jul 22 10:19:35 xxx /kernel.old: wdc1: unit 0 (atapi): CD-ROM CDU611-Q/2.0c, 
removable, accel, dma, iordis
Jul 22 10:19:35 xxx /kernel.old: acd0: drive speed 1723KB/sec, 256KB cache
Jul 22 10:19:35 xxx /kernel.old: acd0: supported read types: CD-R, CD-RW, CD-DA
Jul 22 10:19:35 xxx /kernel.old: acd0: Audio: play, 16 volume levels
Jul 22 10:19:35 xxx /kernel.old: acd0: Mechanism: ejectable tray
Jul 22 10:19:35 xxx /kernel.old: acd0: Medium: no/blank disc inside, unlocked
Jul 22 10:19:35 xxx /kernel.old: npx0 on motherboard
Jul 22 10:19:35 xxx /kernel.old: npx0: INT 16 interface
Jul 22 10:19:35 xxx /kernel.old: vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa
Jul 22 10:19:35 xxx /kernel.old: IP packet filtering initialized, divert disabled, 
rule-based forwarding disabled, unlimited logging
Jul 22 10:19:35 xxx /kernel.old: DUMMYNET initialized (990504)
Jul 22 10:19:35 xxx /kernel.old: changing root device to wd0s1a
Jul 22 10:19:35 xxx /kernel.old: wd0: DMA failure, DMA status 5active
Jul 22 10:19:35 xxx last message repeated 11 times

Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1992-1999 FreeBSD Inc.
Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 22 10:19:35 xxx /kernel.old: The Regents of the University of California. All 
rights reserved.
Jul 22 10:19:35 xxx /kernel.old: FreeBSD 3.2-RELEASE #2: Mon Jul 12 20:41:42 CEST 1999
Jul 22 10:19:35 xxx /kernel.old: [EMAIL PROTECTED]:/usr/src/sys/compile/X
Jul 22 10:19:35 xxx /kernel.old: Timecounter "i8254"  frequency 1193182 Hz
Jul 22 10:19:35 xxx /kernel.old: Timecounter "TSC"  frequency 348205021 Hz
Jul 22 10:19:35 xxx /kernel.old: CPU: Pentium II/Xeon/Celeron (348.21-MHz 686-class 

Re: IDE breakage

[Dag-Erling Smorgrav]

Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
 I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
 on recent versions of -STABLE. Here's an excerpt from messages; kernel
 #3 is a recent -STABLE (yesterday's sources), while kernel #2 is
 3.2-RELEASE. The config file for both is identical.

A brand new kernel (from the same sources and config, but built in a
clean build directory) produces the following:

Jul 22 11:29:17 irc /kernel: Copyright (c) 1992-1999 FreeBSD Inc.
Jul 22 11:29:17 irc /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 22 11:29:17 irc /kernel: The Regents of the University of California. All rights 
reserved.
Jul 22 11:29:17 irc /kernel: FreeBSD 3.2-STABLE #0: Thu Jul 22 10:54:31 CEST 1999
Jul 22 11:29:17 irc /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/X
Jul 22 11:29:17 irc /kernel: Timecounter "i8254"  frequency 1193182 Hz
Jul 22 11:29:17 irc /kernel: Timecounter "TSC"  frequency 348204679 Hz
Jul 22 11:29:17 irc /kernel: CPU: Pentium II/Xeon/Celeron (348.20-MHz 686-class CPU)
Jul 22 11:29:17 irc /kernel: Origin = "GenuineIntel"  Id = 0x652  Stepping = 2
Jul 22 11:29:17 irc /kernel: 
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
Jul 22 11:29:17 irc /kernel: real memory  = 134217728 (131072K bytes)
Jul 22 11:29:17 irc /kernel: avail memory = 127774720 (124780K bytes)
Jul 22 11:29:17 irc /kernel: Preloaded elf kernel "kernel" at 0xc023c000.
Jul 22 11:29:17 irc /kernel: Probing for devices on PCI bus 0:
Jul 22 11:29:17 irc /kernel: chip0: Intel 82443BX host to PCI bridge rev 0x02 on 
pci0.0.0
Jul 22 11:29:17 irc /kernel: chip1: Intel 82443BX host to AGP bridge rev 0x02 on 
pci0.1.0
Jul 22 11:29:17 irc /kernel: xl0: 3Com 3c905-TX Fast Etherlink XL rev 0x00 int a irq 
11 on pci0.13.0
Jul 22 11:29:17 irc /kernel: xl0: Ethernet address: 00:60:08:e8:6b:1d
Jul 22 11:29:17 irc /kernel: xl0: autoneg complete, link status good (full-duplex, 
100Mbps)
Jul 22 11:29:17 irc /kernel: chip2: Intel 82371AB PCI to ISA bridge rev 0x02 on 
pci0.20.0
Jul 22 11:29:17 irc /kernel: ide_pci0: Intel PIIX4 Bus-master IDE controller rev 
0x01 on pci0.20.1
Jul 22 11:29:17 irc /kernel: chip3: Intel 82371AB Power management controller rev 
0x02 on pci0.20.3
Jul 22 11:29:17 irc /kernel: Probing for devices on PCI bus 1:
Jul 22 11:29:17 irc /kernel: vga0: ATI model 4742 graphics accelerator rev 0x5c int 
a irq 11 on pci1.0.0
Jul 22 11:29:17 irc /kernel: Probing for PnP devices:
Jul 22 11:29:17 irc /kernel: Probing for devices on the ISA bus:
Jul 22 11:29:17 irc /kernel: sc0 on isa
Jul 22 11:29:17 irc /kernel: sc0: VGA color 16 virtual consoles, flags=0x0
Jul 22 11:29:17 irc /kernel: atkbdc0 at 0x60-0x6f on motherboard
Jul 22 11:29:17 irc /kernel: atkbd0 irq 1 on isa
Jul 22 11:29:17 irc /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
Jul 22 11:29:17 irc /kernel: fdc0: FIFO enabled, 8 bytes threshold
Jul 22 11:29:17 irc /kernel: fd0: 1.44MB 3.5in
Jul 22 11:29:17 irc /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
Jul 22 11:29:17 irc /kernel: wdc0: unit 0 (wd0): Maxtor 90640D4, DMA, 32-bit, 
multi-block-16
Jul 22 11:29:17 irc /kernel: wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 
S/T, 512 B/S
Jul 22 11:29:17 irc /kernel: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
Jul 22 11:29:17 irc /kernel: wdc1: unit 0 (atapi): CD-ROM CDU611-Q/2.0c, removable, 
accel, dma, iordis
Jul 22 11:29:17 irc /kernel: acd0: drive speed 1723KB/sec, 256KB cache
Jul 22 11:29:17 irc /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA
Jul 22 11:29:17 irc /kernel: acd0: Audio: play, 16 volume levels
Jul 22 11:29:17 irc /kernel: acd0: Mechanism: ejectable tray
Jul 22 11:29:17 irc /kernel: acd0: Medium: no/blank disc inside, unlocked
Jul 22 11:29:17 irc /kernel: npx0 on motherboard
Jul 22 11:29:17 irc /kernel: npx0: INT 16 interface
Jul 22 11:29:17 irc /kernel: vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa
Jul 22 11:29:17 irc /kernel: IP packet filtering initialized, divert disabled, 
rule-based forwarding disabled, unlimited logging
Jul 22 11:29:17 irc /kernel: DUMMYNET initialized (990504)
Jul 22 11:29:17 irc /kernel: changing root device to wd0s1a
Jul 22 11:29:17 irc /kernel: wd0: DMA failure, DMA status 5active
Jul 22 11:29:17 irc last message repeated 17 times
Jul 22 11:29:17 irc /kernel: wd0: DMA failure, DMA status 7error,active
Jul 22 11:29:17 irc /kernel: 
Jul 22 11:29:17 irc /kernel: 
Jul 22 11:29:17 irc /kernel: Fatal trap 12: page fault while in kernel mode
Jul 22 11:29:17 irc /kernel: fault virtual address = 0x44
Jul 22 11:29:17 irc /kernel: fault code= supervisor read, page not present
Jul 22 11:29:17 irc /kernel: instruction pointer   = 0x8:0xc01813ca
Jul 22 11:29:17 irc /kernel: stack pointer = 0x10:0xc9599b84
Jul 22 11:29:17 irc /kernel: frame pointer = 0x10:0xc9599bf4
Jul 22 11:29:17 irc /kernel: code segment  = base 0x0, limit 0xf, type 0x1b
Jul 22 11:29:17 irc /kernel: = 

Re: PAM LDAP in FreeBSD

[Max Khon]

hi, there!

On Fri, 16 Jul 1999, Oscar Bonilla wrote:

 Following up on my own post:
 
 For LDAP to be seamlessly integrated into the system some of the libraries
 have to be changed. Specifically the ones dealing with /etc/passwd and
 user information. 
 
 I've decided the best way to do this is to do what's done with NIS.
 Basically handle the case where the user is not available in the local
 databases. 
 
 the idea is to have an entry in the /etc/passwd enabling LDAP lookups.
 the Entry would be of the form
 
 ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com
^^^ ^^^ ^^^ ^^
 |  |||   
portbase dnattr LDAP Server
 
 This comes ftom a pam_ldap module I got from Pedro A M Vazquez 
 [EMAIL PROTECTED]
 
 I'll change all of the function in lib/libc/gen/getpwent.c to handle this
 special case.
 
 The only problem is that openldap has to be integrated on the base system
 for this to compile... can I safely copy it to /usr/src/contrib?
 
 How do I submit this after it's done? anyone cares about ldap :)?

aargh. looks horrible to me. better try to implement NSS

/fjoe



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

Re: PAM LDAP in FreeBSD, and userfs too.

[Max Khon]

hi, there!

On Mon, 19 Jul 1999, Dominic Mitchell wrote:

 On Mon, Jul 19, 1999 at 12:29:48PM -0400, David E. Cross wrote:
  I thought now would be a good time to chime in on some of my wild schemes...
  
  The reason I am interested in 'userfs' is to enable me to write a version
  of 'nsd'.

[...]
 
 Lovely.  Sounds like a much better way to do the Solaris/Linux (and
 NetBSD?) /etc/nsswitch.conf stuff.  On Solaris at least, this is
 implemented using masses of weird shared objects...

PAM is also "using masses of weird shared objects" but nevertheless it's
quite usable

/fjoe



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

Re: PAM LDAP in FreeBSD, and userfs too.

[Dominic Mitchell]

On Thu, Jul 22, 1999 at 04:59:59PM +0700, Max Khon wrote:
 On Mon, 19 Jul 1999, Dominic Mitchell wrote:
  Lovely.  Sounds like a much better way to do the Solaris/Linux (and
  NetBSD?) /etc/nsswitch.conf stuff.  On Solaris at least, this is
  implemented using masses of weird shared objects...
 
 PAM is also "using masses of weird shared objects" but nevertheless it's
 quite usable

By statically linked binaries?
-- 
Dom Mitchell -- Palmer  Harvey McLane -- Unix Systems Administrator

In Mountain View did Larry Wall
Sedately launch a quiet plea:
That DOS, the ancient system, shall
On boxes pleasureless to all
Run Perl though lack they C.
-- 
**
This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they   
are addressed. If you have received this email in error please notify 
the system manager.

This footnote also confirms that this email message has been swept by 
MIMEsweeper for the presence of computer viruses.
**


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

NSS project

[Max Khon]

hi, there!

So what is the "official" status of NSS impl.?
Are there any takers?

/fjoe



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

Re: PAM LDAP in FreeBSD

[Max Khon]

hi, there!

On Tue, 20 Jul 1999, Oscar Bonilla wrote:

  It looks like we've got some good concurrent projects happening at the
  moment - markm and co working on PAM, the nsswitch.conf project you're
  talking about, and the stuff I'm working on with modularizing crypt() and
  supporting per-login class password hashes (I've rewritten the library
  since I last posted about it and expect to have my code cleaned up by
  tomorrow night for another snapshot).
  
  The thing to make sure is that we don't tread on each other's toes, and
  basically that we look for the big picture and how all these projects fit
  together.
  
 
 Ok, this is my understanding of the thing:
 
 There are two parts to the problem, first we need a way to tell the
 system where to get its information from (call them databases, tables
 or whatever). This should be done a la solaris, with
 /etc/nsswitch.conf telling if this is to be fetched from "files, ldap,
 nis, dns, etc".
 
 We need to recode all the programs that obtain this info directly from
 files to get it from a library (this would be nsd). And then code the
 library itself to get the info from /etc/nsswitch.conf

You misunderstand the main goal of NSS -- you need not recode anything --
NSS substitutes getxxxbyzzz libc functions

 Second, we need a way to authenticate the user... this is what PAM does.
 What would need to be done is change the pam modules to make them
 nsd aware (i.e. where should I get the passwd from?) or make them
 /etc/auth.conf aware? this is the confusing part... 
 
 where does crypt fit into this? crypt would get what from /etc/login.conf?

go to http://www.padl.com and read about LDAP + NSS and PAM deployment
schemes

/fjoe



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

Re: PAM LDAP in FreeBSD

[Max Khon]

hi, there!

On Mon, 19 Jul 1999, Oscar Bonilla wrote:

 On Mon, Jul 19, 1999 at 04:51:12PM -0600, Wes Peters wrote:
  The implementation details are as unimportant as ever: they have to work
  and be maintainable.  Following prior art remains a good idea; the Solaris
  "name service switch" implementation is a good starting point to consider.
  
 
 I agree. In solaris (and linux by the way) all you do is set
 passwdldap files
 in /etc/nsswitch.conf
 and that's it.
 
 I had started to write the code to mess with libc to "fix" the getpwent stuff,
 but a better solution is to "port" the nsswitch stuff from linux (i don't have
 source from solaris :)

glibc NSS impl. is GPL-poisoned and the author of that impl. (sorry, do
not even remember his name) does not want to distribute it under BSD-style
copyright. better try to port NetBSD impl.

/fjoe



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

Re: IDE breakage

[sthaug]

 I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
 on recent versions of -STABLE. Here's an excerpt from messages; kernel
 #3 is a recent -STABLE (yesterday's sources), while kernel #2 is
 3.2-RELEASE. The config file for both is identical.

I can confirm problems with DMA from IDE disks in -STABLE. The problems
seem to have been introduced in

$Id: ide_pci.c,v 1.28.2.1 1999/07/20 22:58:20 julian Exp $

And the effect for me is that the system stops in singleuser mode, with
a "DMA failure" message. This is on a 440BX/PII-350 system.

Reverting to 1.28 (from 17. January 1999) fixes the problems.

Please back out 1.28.2.1, at least in -STABLE.

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]


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

Re: Will FreeBSD ever see native IPv6 ??

[Jeroen Ruigrok/Asmodai]

* John Hay ([EMAIL PROTECTED]) [990722 11:55]:
 Are you just teasing or are you serious?

Well, according to what was discussed earlier he is serious. But from
prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
stuff is only available for 3.x and below.

 I searched through their site (again), but except for being mentioned
 in their TODO for the past few months, I can't find anything that
 indicates that they or anyone else is working on it. They may be, but
 it isn't visible anywhere where I have looked. It would be nice if
 there was some place to follow their progress, because I'm also one
 of the people that would like to see IPv6 integrated into FreeBSD.

At the moment I am busy merging ipv6 from the 3.x kit into CURRENT, but
I have to see how to spread my time because I am also doing work on OVCS,
the PDP and some other projects. *bwerk* days are much too short...

If anyone else is having some spare time and willing to mess with the
kame 3.x kit cvsup stuff and CURRENT alongside me, please drop a mail.

'gards,

-- 
Jeroen Ruigrok van der Werven  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai
Network/Security SpecialistBSD: Technical excellence at its best
Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...?


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

Re: Will FreeBSD ever see native IPv6 ??

[itojun]

 Are you just teasing or are you serious?
Well, according to what was discussed earlier he is serious. But from
prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
stuff is only available for 3.x and below.

We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE because we can't
base our IPv6 development on top of moving target.
FreeBSD 3.x-STABLE and 4.x are moving target (which moves very quickly)
and are unusable as base version for us - if we need to chase two
moving things (IPv6 and FreeBSD) we are doomed.

There has been NRL/INRIA/KAME integration work going on (basically
to avoid "4 BSDs and 3 IPv6 = 12 choices" nightmare by making one
IPv6 stack).  There are, mainly, some (or too many) management
issues there.  We will be resolving management issues issue very soon,
hopefully by next week.
There's incomplete "unified" codebase there, which is not very
ready for public consumption.  Anyway please hold till the managment
issue is resolved, I believe I can give you a good news.

itojun


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

arpresolve: can't allocate llinfo for 255.255.255.0rt

[Jung, Michael]

I started getting these messages in the daily security output.

 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt

Upon inspection of the routing table I see this

(mikej@hobbs) /usr/home/mikej$netstat -r
Routing tables

Internet:
DestinationGatewayFlags Refs Use Netif
Expire
defaultc5500-rsm-vlan10   UGSc851872  tl0
localhost  localhost  UH  00  lo0
129.2.1/24 link#2 UC  00  de0
199.15/16  link#1 UC  00  tl0
199.15.32  c5500-rsm-vlan10   UGSc00  tl0 =
199.15.320xc70f22 255.255.255.0  UGSc0  185  tl0
c5500-rsm-vlan10   0:e0:34:a1:84:0UHLW50  tl0
1198
calvin 0:80:5f:cb:de:16   UHLW122152  tl0
 67

Can anyone explain how or where the "199.15.320xc70f22" entry could
have come from? I've been unable to remove it and don't have a window to
reload the server for several days.

Thanks--

Michael Jung(502) 315-2457 Voice
Senior Network Specialist   (502) 315-2815 Facsimile
National Processing Company, Inc.   [EMAIL PROTECTED]
1231 Durrett Lane   MJ548
Louisville, KY 40285



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

Re: Anyone know how to dim and SGI flat panel?

[Mike Smith]

 
 :I'd bet it's done using DPMS.  See if the XFree86 4.x code can tell you 
 :anything about the monitor's capabilities.
 
 It's up?  Very cool, they actually put the prerelease up 2 days ago!
 47MB download, yummy!  DGA is going to be so cool.
 
 Unfortunately it looks like the DPMS stuff is still a bit primitive.
 Shoot.  I'll check it out, though.  The 3.3.3 I128 driver (that's
 the number 9 card) does not appear to support DPMS at all.
 
 SGI's site has a whitepaper on the flatpanel but it's a bit spare on
 control protocols.  They do say something about an I2C bus but I dunno
 whether that is what DPMS uses or not.

That is how I believe that DMPS communications are transported to the 
display.  Unfortunately, the DPMS specification is a VESA-proprietary 
document so you will have to either join the XFree86 project or sponsor 
FreeBSD as a VESA member (that would be nice 8).

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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

Re: PAM LDAP in FreeBSD, and userfs too.

[Kris Kennaway]

On Thu, 22 Jul 1999, Dominic Mitchell wrote:

  PAM is also "using masses of weird shared objects" but nevertheless it's
  quite usable
 
 By statically linked binaries?

This is also an issue for a modularized libcrypt(). Peter Wemm suggested
having the library fork and exec a static helper binary module and
communicate via a pipe. So essentially you'd have two files for each
module, one which is a shared library and loaded via dlopen() and one
which is the same code with a small amount of wrapper (main() etc) to make
it into a standalone binary.

Solaris seem to be deprecating static libraries; you cannot have a fully
static libc and they have to resort to keeping (a copy of) libdl (and
presumably the run-time linker) under /etc so it's available on the root
partition.

Kris




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

Re: UDMA broken in -CURRENT/-STABLE?

[Kelly Yancey]

 I updated a system to -CURRENT last night and got a panic with alot of
 messages about UDMA failing (I don't have the exact messages, I can get
 them if need be).  I backed down the wdc0/wdc1 controller flags from
 0xa0ffa0ff to 0x0 and everything is happy.  I figured its -CURRENT, and
that
 is to be expected.

 I updated another system to -STABLE as of earlier today, and I got the
same
 thing... *eeak*.  again backing down from 0xa0ffa0ff to 0x0 works like a
 champ.

 The messages came right after init(8) started, and before any of the
 filesystems were mounted r/w (it happened most during the fsck).

 I hope someone else has seen this (sorry I am so skimpy on the details, I
 will be able to provide more soonish.)

 uname -a:
 FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21
15:17:27 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/PHOENIX  i386

 dmesg:
 [...]
 ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1
 [...]

  I've seen the exact same problem on -stable builds since the 20th (I don't
know how much further back it went than that). I'm not in front of my
computer right now, but the errors were all DMA errors (status ready as I
recall). I have a PIIX4 controller. I played around with it a bit and found
that simply turning of the DMA hint in the flags cleared the problems (my
flags went from f0fff0ff to d0ffd0ff I believe). Actually, once I
accidentilly left the flags with DMA enabled on only 1 drive and only
received DMA errons on that single drive.
  I don't know if this is related, but my atapi CD (Acer 40x) still reports
DMA (apparently not affected by the wdc flags), but won't play audio CDs
from most CD apps (apparently the ones which use the CDIOCPLAYWMF ioctl to
play audio). This has been going on for longer, but I don't know if it was
maybe a precursor to the UDMA bug?

  Kelly
 ~[EMAIL PROTECTED]~
  FreeBSD - The Power To Serve - http://www.freebsd.org/
  Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD



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

FreeBSD: the stealth OS?

[Len Conrad]

Cool with the geeks beecause it's "unknown".

http://www.msnbc.com/news/292376.asp

Len 



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

Filesystem question...

[David E. Cross]

Since I am planning on writing userfs in order to impliment 'nsd' (and
some other ideas I have hatching too :).  I need to know how filesystem
accesses work.  Can they be queued up, and responded to out of order?

For example... I have a request come in (via the filesystem), that request
is going to take awhile, so I thread off a handler.  Now another filesystem
request comes in, will that be delivered to me, or will that block waiting
for the previous request to be honored first?

--
David Cross   | email: [EMAIL PROTECTED] 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself.  | WinNT:Linux::Linux:FreeBSD


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

Re: PAM LDAP in FreeBSD

[Kris Kennaway]

On Wed, 21 Jul 1999, Oscar Bonilla wrote:

 Ok, here goes my understanding of how things should be, please correct me
 if i'm wrong.
 
 There are three parts to the problem: 
 
 1. Where do we get the databases from? I mean, where do we get passwd, group,
hosts, ethers, etc from.
 
This should be handled by a name service switch a la solaris. Basically
we want to be able to tell the system for each individual database where
to get the stuff from. We can add entries for each database in the system.
 
 2. How to authorize the user? I mean, what sort of authentication should we
use to decide if the user should be allowed in. 
 
This should be handled by PAM.

PAM also does other functions; session management, password management,
etc.

 
 3. What password hash should we use when we have the username and the
password hash?
 
This should be handled by the new modularized crypt.
 
 Do we want to be able to tell the system where to get its pam.conf and
 login.conf from? This would mean having a pam.conf and login.conf entry
 in nsswitch.conf.

Hmm. I don't know that this much would be useful.

 Can we make a list of stuff that needs to be done to make this possible?
 Something like a tasklist would be good.
 
 a) design and implement a name service switch.
 b) make libc aware of the name service switch.
 c) ???

I think we should look at what NetBSD is doing and join with their
efforts. There's no sense in reinventing the wheel.

I'm just running my libcrypt through a make world to make sure it's okay -
once it's done I'll post the new source code snapshot for comment and
testing.

Kris

 -Oscar
 
 -- 
 For PGP Public Key: finger [EMAIL PROTECTED]
 

--
  The Feynman Problem-Solving Algorithm:
(1) Write down the problem
(2) Think real hard
(3) Write down the answer
--



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

Re: any docs on how to use bus_dma_tag_create e.a. ?

[Justin T. Gibbs]

/*lowaddr*/BUS_SPACE_MAXADDR_32BIT,
/*highaddr*/BUS_SPACE_MAXADDR,
 
 low and high address of the region that the DMA engine cannot access.

Meaning e.g. the 16Mbyte barrier that ISA DMA has? 
For PCI this would be a 4Gb range(?).

The range could be much larger than 4GB.  Remember this is a range the
device *cannot* access, not a range it can access.  So, the beginning
of the range for an ISA device would be BUS_SPACE_MAXADDR_24BIT and the
hight address would be BUS_SPACE_MAXADDR.  Depending on the platform
or configuration of the machine, the high address could be larger than
a 32bit quantity.

/*maxsize*/MAXBSIZE,
 
 Maximum DMA transfer size.
 
/*nsegments*/AHC_NSEG,
 
 Maximum number of discontinuities in the mapped region.

Eh.. ? 

/*maxsegsz*/AHC_MAXTRANSFER_SIZE,
 
 Maximum size of a segment.  maxsize = nsegments * maxsegsz.

Eh.. ?

Many DMA engines have S/G capability and so can perform a single DMA that
spans multiple segments of "bus space contiguous" data.  By setting these
parameters, the bus_dmamap_load function can determine how best to map
your transfer into bus space and will return to you an array of segments
to program into your DMA hardware.

 You should use the new API if possible.

That is what I'm planning to do. The amount of sample code in the various
drivers is rather limited as most drivers use the old code.

It seems that its mostly confined to the SCSI code, but hopefully that will
change over time.

So I hope you don't mind me asking some more questions,

Not a problem.

--
Justin



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

Re: Filesystem question...

[Tiny Non Cats]

On Thu, Jul 22, 1999 at 10:06:04AM -0400 David E. Cross said:
 Since I am planning on writing userfs in order to impliment 'nsd' (and

This may be completely useless, because I've not been following what you want
to do with 'nsd', but you may find

   http://www.cs.columbia.edu/~ezk/research/security/index.html

interesting. It's a description of 'WrapFS', written by Erik Zadok. It's a 
stackable filesystem template written as a kernel module, and can be extended to 
do all sorts of stuff with relative ease, apparently.

Cian

-- 
What think ye of Christ? Whose son is he? Will you, like Peter, boldly say: 

   "Who?" 



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

Re: PAM LDAP in FreeBSD, and userfs too.

[Dominic Mitchell]

On Thu, Jul 22, 1999 at 11:19:35PM +0930, Kris Kennaway wrote:
 On Thu, 22 Jul 1999, Dominic Mitchell wrote:
 
   PAM is also "using masses of weird shared objects" but nevertheless it's
   quite usable
  
  By statically linked binaries?
 
 This is also an issue for a modularized libcrypt(). Peter Wemm suggested
 having the library fork and exec a static helper binary module and
 communicate via a pipe. So essentially you'd have two files for each
 module, one which is a shared library and loaded via dlopen() and one
 which is the same code with a small amount of wrapper (main() etc) to make
 it into a standalone binary.

This is starting to get icky.  This is also where the earlier idea of a
userspace filesystem would probably fare better, in terms of both
performance and simplicity.

 Solaris seem to be deprecating static libraries; you cannot have a fully
 static libc and they have to resort to keeping (a copy of) libdl (and
 presumably the run-time linker) under /etc so it's available on the root
 partition.

Solaris hasn't supported static linking for some time.  If you have a
look at Casper Dik's FAQ, it goes into more detail.  They do keep stuff
on the root partition:

admin# ls -l /etc/lib
total 644
-rwxr-xr-x   1 bin  bin   155060 Jul  1  1998 ld.so.1*
-rwxr-xr-x   1 bin  bin 4284 Jul  1  1998 libdl.so.1*
-rwxr-xr-x   1 bin  bin25468 Jul 16  1997 nss_files.so.1*
lrwxrwxrwx   1 root root  17 Sep 14  1998 pam_authen.so - 
./pam_authen.so.1*
-rwxr-xr-x   1 root sys14516 Jul 16  1997 pam_authen.so.1*
lrwxrwxrwx   1 root root  16 Sep 14  1998 pam_entry.so - ./pam_entry.so.1*
-rwxr-xr-x   1 root sys11540 Jul 16  1997 pam_entry.so.1*
lrwxrwxrwx   1 root root  17 Sep 14  1998 pam_extern.so - 
./pam_extern.so.1*
-rwxr-xr-x   1 root sys11044 Jul 16  1997 pam_extern.so.1*
lrwxrwxrwx   1 root root  16 Sep 14  1998 pam_pwmgt.so - ./pam_pwmgt.so.1*
-rwxr-xr-x   1 root sys85764 Jul 16  1997 pam_pwmgt.so.1*
lrwxrwxrwx   1 root root  18 Sep 14  1998 pam_session.so - 
./pam_session.so.1*
-rwxr-xr-x   1 root sys 4748 Jul 16  1997 pam_session.so.1*

-- 
Dom Mitchell -- Palmer  Harvey McLane -- Unix Systems Administrator

In Mountain View did Larry Wall
Sedately launch a quiet plea:
That DOS, the ancient system, shall
On boxes pleasureless to all
Run Perl though lack they C.
-- 
**
This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they   
are addressed. If you have received this email in error please notify 
the system manager.

This footnote also confirms that this email message has been swept by 
MIMEsweeper for the presence of computer viruses.
**


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

Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 Starfire ethernet controller driver and plus question compaq presario dec et and * trancelate for english

[aladdin]

heloo all

- Original Message -
From: Bill Paul [EMAIL PROTECTED]
To: morita [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, July 21, 1999 11:00 PM
Subject: Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 "Starfire"
ethernet controller driver and plus question compaq presario dec et


 Of all the gin joints in all the towns in all the world, morita had
to
 walk into mine and say:

  $B?9ED$G$9!#(B
  
   These are Adaptec's replacements for its older DEC 21x4x-based
multiport
 
 japanses 1 .  $B$3$N%I%i%$%P!<$OL5$/$J$k$N$G$7$g$&$+!)(B-DEC
21x4x-based
english  1 .   no more supllyed -DEC 21x4x-based  is it true?
japanses 1=english  1 .


 Sorry, but I'm just a dumb american: I can't read this.

   line of adapters. All cards support 10/100 speeds in full or
half duplex.
   The multiport cards consist of multiple AIC-6915 chips linkec
via a PCI
   to PCI bridge. Currently I have only tested the ANA-62022 dual
port card,
   however all of them should work equally well. The 64-bit cards
will work
   in a 32-bit slot on most newer machines.
  
 
english  2   
$B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!<%k$7(B
$B$?$N$G$9$,!"(B
japanese 2  he install of? FreeBSD3.2 to conpaq PRESARIO$B!!(B2274$B!!(B

english  3NIC$B!'!!(BDEC 21143-based $B$H%S%G%*%+!<%I!'(BSiS5598$B$N@_Dj(B
$B$,$&$^$/$$$-$^$;$s!"8=:_(B
japanese 3  NIC$B!'!!(BDEC 21143-based  video chip is SiS5598 is not
good condition now


  $BF0$+$7$F$k(B
  $BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B
english  4  tell him how install


 I can't read this either. :(

 -Bill

 --

=

 -Bill Paul(212) 854-6020 | System Manager, Master of
Unix-Fu
 Work: [EMAIL PROTECTED] | Center for
Telecommunications Research
 Home:  [EMAIL PROTECTED] | Columbia University, New
York City

=

  "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space
Madness"

=



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




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

Re: arpresolve: can't allocate llinfo for 255.255.255.0rt

[Dominic Mitchell]

On Thu, Jul 22, 1999 at 09:30:28AM -0400, Jung, Michael wrote:
 I started getting these messages in the daily security output.
 
  arpresolve: can't allocate llinfo for 255.255.255.0rt
  arpresolve: can't allocate llinfo for 255.255.255.0rt
  arpresolve: can't allocate llinfo for 255.255.255.0rt
  arpresolve: can't allocate llinfo for 255.255.255.0rt
  arpresolve: can't allocate llinfo for 255.255.255.0rt
  arpresolve: can't allocate llinfo for 255.255.255.0rt
  arpresolve: can't allocate llinfo for 255.255.255.0rt

I get those after a long run of nmap on our /16 network.  At this point,
I just kill nmap and the problem goes away.  I didn't bother looking
into the routing table though.  Maybe it's time to see what the PC
support monkeys have plugged into my network again.  :-)
-- 
Dom Mitchell -- Palmer  Harvey McLane -- Unix Systems Administrator

In Mountain View did Larry Wall
Sedately launch a quiet plea:
That DOS, the ancient system, shall
On boxes pleasureless to all
Run Perl though lack they C.
-- 
**
This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they   
are addressed. If you have received this email in error please notify 
the system manager.

This footnote also confirms that this email message has been swept by 
MIMEsweeper for the presence of computer viruses.
**


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

Re: PAM LDAP in FreeBSD, and userfs too.

[Kris Kennaway]

On Thu, 22 Jul 1999, Dominic Mitchell wrote:

 This is starting to get icky.  This is also where the earlier idea of a
 userspace filesystem would probably fare better, in terms of both
 performance and simplicity.

Maybe I don't get how this userspace filesystem is going to be set out
(for the case of the nss stuff), but I don't see this.

Kris

--
  The Feynman Problem-Solving Algorithm:
(1) Write down the problem
(2) Think real hard
(3) Write down the answer
--



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

Re: Filesystem question...

[Ronald G. Minnich]

One last thing: if you're writing userfs you might want to look at
www.inter-mezzo.org

ron




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

Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU'

[Don Read]

On 22-Jul-99 Jorge Biquez wrote:
 I hope this helps.
 I'm running version 3.1 on ASUS Pentium III double processor. Just a Rocket!
 No problems at all on the installation all the SCSI ports were
 recognized my entire machine cost me 2000 USD...similar
one of a famous
 brabd...at least 6,000
 
 JB

metoo
the ASUS boards
/metoo

PII/350M 128M, 3c905B, dual SCSI (1 on board + 1 Adaptec 2940B), Seagate
ST39173W, Toshiba CD on IDE (had a spare HP DAT-24 tape drive) $3400
compared to a certain BigBlue box at $8000+ monitor

FreeBSD 2.2.8, MySQL 3.22. been running without a hiccup since Feb.

Regards,
---
Don Read [EMAIL PROTECTED]
EDP Manager  [EMAIL PROTECTED]
Calcasieu Lumber Co.   Austin TX
-- But I'm in good company, sendmail has kicked a great many 
 butts in the past


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

Update on Adaptec AIC-6915 starfire driver

[Bill Paul]

I haven't received any feedback yet on the Adaptec "Starfire" driver,
however I made a few updates that people should know about:

- I created a version of the driver for FreeBSD 2.2.x. You can find it
  at http://www.freebsd.org/~wpaul/Adaptec/2.2. Note: while I have
  verified that this code compiles, I have not been able to test it.
  There should not be any problems, but as always, Murphy's Law applies.

- I found a bug today which is that sf_stats_update() required splimp()
  protection. I use the indirect register access method which is done
  in two stages: first you set the indirect address register to the
  register offset that you want to play with, then you access it via
  the indirect data register. However sf_stats_update() was interruptible
  which means that it was possible for the interrupt handler to run
  in between the first and second stages, which caused the stats updater
  to modify incorrect register locations. This bug would manifest itself
  in the form of watchdog timeouts and the 'collisions' counter sometimes
  reporting wildly incorrect values.

  I corrected this problem and updated the driver sources for each
  FreeBSD version (including 2.2.x) and recompiled the KLD module for
  FreeBSD 4.0-current.

- The pre-compiled KLD module for FreeBSD 4.0-current now includes
  BPF support, since I have been told that there stubs that should
  allow BPF-enabled drivers to work even if BPF support isn't compiled
  into the kernel.

- I added a README at http://www.freebsd.org/~wpaul/Adaptec which
  explains how to install the driver on FreeBSD 2.2.x, 3.x and 4.0.

Also, a quick note about the Adaptec cards. I said previously that
the Duralink adapters were Adaptec's replacement for their older
DEC tulip-based cards. Adaptec still sells multiport adapters based
on the 21x4x chip, however I believe they use the 21143 now since
Intel discontinued production of the 21140 and supplies are drying
up. It is possible that Adaptec may stop production on the older cards 
though now that they have their own high performance chipset. The 
Duralink cards may also be preferable in some cases since they are
64-bit PCI devices.

Anyway: I would appreciate it if people could test the driver and
get back to me with some feedback. I hope to merge this into the
-current branch soon.

-Bill

-- 
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home:  [EMAIL PROTECTED] | Columbia University, New York City
=
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=


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

Re: Filesystem question...

[Ronald G. Minnich]

what if you're not root, and you want to add your own file system to your
file system name space? It seems a lot of these systems assume root
access, which seems unrealistic to me.

ron




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

Re: FreeBSD: the stealth OS?

[Matthew Dillon]

:Cool with the geeks beecause it's "unknown".
:
:http://www.msnbc.com/news/292376.asp
:
:Len 

I love the quote by Matthew Fuller at the end:

"There's a lot of things that Linux is 'better' at, and a
lot of things FreeBSD is 'better' at, and a lot of those
things can easily fluctuate on a daily or weekly basis,"
said Fuller, who maintains a Linux vs BSD Web page.
"Thus, any definitive narrow statement that can be made
is usually obsolete before anyone hears it.".

Perfect!

-Matt
Matthew Dillon 
[EMAIL PROTECTED]


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

Re: Filesystem question...

[Kris Kennaway]

On Thu, 22 Jul 1999, Ronald G. Minnich wrote:

 what if you're not root, and you want to add your own file system to your
 file system name space? It seems a lot of these systems assume root
 access, which seems unrealistic to me.

Well, if you're running it as a kernel module then obviously you need root
permissions to load it. If it's running as a userland process, then
there's no reason why you can't run it as a user. mount presumably
wouldn't care as long as you had access rights to the underlying objects
(mountpoint + stacking layer process).

Kris



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

Looking for (commercial?) bandwith on NetBSD/FreeBSD machines

[Julian Assange]

I'm involved in a linguistic analysis project which requires
reasonable quantities of bandwidth. Due to duopolistic price-fixing,
and volume-charing obtaining this bandwith in Australia is a very
expensive proposition indeed (US$0.13/Mb!). I'm trying to find a
co-hosting (or equivalent) solution, preferably on NetBSD or FreeBSD
machines, although this is not essential and I could always provide
the machine. Bandwidth usage would be about 4-10Gb/day incoming during
the next few months. I also have sizeable disk requirements, which
could be forfilled by 2-4x 17GB ATA/IDE -- unfortunately the
equivalent in scsi is a little out of my budget.

Suggestions?


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

Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 Starfire ethernet controller driver and plus question compaq presario dec et

[Warner Losh]

[[ Warning, you'll need something which can display Kanji to be able
   to read what I've written.  I'm using mule and netscape.  I've tried
   to make the non-Japanese parts separate enough that if you only
   understand English and have only english viewing programs, you can
   safely ignore the strange sequences of characters resembling TECO
   progragms and/or line noise.  
]]

In message [EMAIL PROTECTED] Bill Paul writes:
: Sorry, but I'm just a dumb american: I can't read this.

$B?=$7Lu$4$6$$$^$9!#;d$OJF9q?M$G$9!#FI$_$^$;$s!#(B

(which translates, if I've gotten the Japanese correct, as "I'm very
 sorry.  I'm an american.  I cannot read this.")

$B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!%k$7$?$N$G$9$,!"(B
 NIC$B!'!!(BDEC 21143-based 
$B$H%S%G%*%+!%I!'(BSiS5598$B$N@_Dj$,$$^$/$$$-$^$;$s!"8=:_(B
$BF0$+$7$F$k(B
$BJ}$,$$$i$7$?$i65$($F$/$@$5$$!#(B

Using Netscape and 
http://www.dgs.monash.edu.au/cgi-bin/cgiwrap/jwb/wwwjdic?9T
(and my little knowledge of Japanese grammar) I believe that this says 
something along the lines of:

Compaq PRESARIO 2274 with FreeBSD 3.2 installed, but
NIC: DEC 21143-based and Video Card: SiS5598 which won't [attach].
In the current [system], can you please instruct me how [to make it work].

The text in [] is guessed based on context, I didn't look up the
words in hiragana that I didn't already know, or for which the literal 
translation didn't make sense.

Warner


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

Re: Filesystem question...

[Kris Kennaway]

On Thu, 22 Jul 1999, Tiny Non Cats wrote:

 On Thu, Jul 22, 1999 at 10:06:04AM -0400 David E. Cross said:
  Since I am planning on writing userfs in order to impliment 'nsd' (and
 
 This may be completely useless, because I've not been following what you want
 to do with 'nsd', but you may find
 
http://www.cs.columbia.edu/~ezk/research/security/index.html
 
 interesting. It's a description of 'WrapFS', written by Erik Zadok. It's a 
 stackable filesystem template written as a kernel module, and can be extended to 
 do all sorts of stuff with relative ease, apparently.

Cool. It's amazing what pops up on these lists sometimes!

*sigh* If only I had some free time before starting my PhD :-(

Kris



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

Re: Anyone know how to dim and SGI flat panel?

[Matthew Dillon]

:
:XFree86 has an i2c driver in it for talking to monitors so it sounds as if
:it should see it.
:
:--
:Doug RabsonMail:  [EMAIL PROTECTED]
:Nonlinear Systems Ltd. Phone: +44 181 442 9037
:

:...

:
:That is how I believe that DMPS communications are transported to the 
:display.  Unfortunately, the DPMS specification is a VESA-proprietary 
:document so you will have to either join the XFree86 project or sponsor 
:FreeBSD as a VESA member (that would be nice 8).
:
:-- 
:\\  The mind's the standard   \\  Mike Smith


Ahhh.  Interesting.

Ah, the XFree ftp finished. Hmm. the DPMS stuff looks promising but I
don't see an I128 port yet.  Shoot.

-Matt
Matthew Dillon 
[EMAIL PROTECTED]


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

Squid - a bug in src/sys/kern/uipc_socket.c

[Papezik Milon]

Hi,

please don't kill me if it's "well known issue":

I've found that there is a report on Squid site, which
describes a problem with FreeBSD IPC and includes suggested fix.
I verified that this suggested fix is not included in 3.2-RELEASE.

I wonder, if it is really a bug, as I cannot find it in PR database.

Could someone please comment on this report/bug/suggested fix
and if/when the fix could/will be submited?

original URL:
http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2

Thanks in advance,
Milon
--
[EMAIL PROTECTED]


 bug report and suggested fix -
mbuf size

We noticed an odd thing with some of Squid's interprocess communication.
Often, output from the dnsserver processes would NOT be read in one
chunk. With full debugging, it looks like this:

1998/04/02 15:18:48| comm_select: FD 46 ready for reading
1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (100
bytes)
1998/04/02 15:18:48| ipcache_dnsHandleRead: Incomplete reply
other processing occurs...
1998/04/02 15:18:48| comm_select: FD 46 ready for reading
1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (9
bytes)
1998/04/02 15:18:48| ipcache_parsebuffer: parsing:
$name www.karup.com
$h_name www.karup.inter.net
$h_len 4
$ipcount 2
38.15.68.128
38.15.67.128
$ttl 2348
$end

Interestingly, it is very common to get only 100 bytes on the first
read. When two read() calls are required, this adds additional latency
to the overall request. On our caches running Digital Unix, the median
dnsserver response time was measured at 0.01 seconds. On our FreeBSD
cache, however, the median latency was 0.10 seconds.

Here is a simple patch to fix the bug: 

===
RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v
retrieving revision 1.40
retrieving revision 1.41
diff -p -u -r1.40 -r1.41
--- src/sys/kern/uipc_socket.c  1998/05/15 20:11:30 1.40
+++ /home/ncvs/src/sys/kern/uipc_socket.c   1998/07/06 19:27:14
1.41
@@ -31,7 +31,7 @@
  * SUCH DAMAGE.
  *
  * @(#)uipc_socket.c   8.3 (Berkeley) 4/15/94
- * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $
+ * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $
  */
 
 #include sys/param.h
@@ -491,6 +491,7 @@ restart:
mlen = MCLBYTES;
len = min(min(mlen, resid), space);
} else {
+   atomic = 1;
 nopages:
len = min(min(mlen, resid), space);
/*

Another technique which may help, but does not fix the bug, is to
increase the kernel's mbuf size. The default is 128 bytes. The MSIZE
symbol is defined in
/usr/include/machine/param.h. However, to change it we added this line
to our kernel configuration file: 

options MSIZE="256"


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

rtprio and fifo's

[Kevin Day]

I know the evils associated with using rtprio, but I have a real real-time
application that needs to service data very quickly when it is needed from a
piece of hardware.

This daemon reads from a special device. The driver's read handler puts it
to sleep, and wakes it back up when an interrupt comes in.

Other processes communicate with this daemon using fifo's. (They send it
packetized commands, and every once in a while through the loop it checks
the fifo for data).

According to my Stevens book here, fifo and pipe writes are guaranteed to be
atomic, as long as the write is less than PIPE_BUF. (which is 512 bytes
here).

Unless I'm using rtprio, this is true. Apparently I'm somehow stealing
execution away from the child processes during their write() in the middle
of it. Occasionally, when I should be reading 192 bytes in from the fifo,
i'll do one read of 89 bytes, and another of 103. This wasn't hard to code
around, I just kept a buffer, and only processed it when I had a complete
packet.

However, about once every 6-8 hours, the daemon will get stuck in 'sbwait',
and no amount of kicking it will make it wake back up. If I don't use
rtprio, this doesn't happen, but the process becomes too slow to work. 

Has anyone run into this before, or does anyone have any suggestions on how
I might fix this? I may try SYSV style message queues next, if I"m not able
to fix the fifo problem.

Kevin


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

Re: FreeBSD: the stealth OS?

[Matthew D. Fuller]

On Thu, Jul 22, 1999 at 09:51:38AM -0700, a little birdie told me
that Matthew Dillon remarked
 
 I love the quote by Matthew Fuller at the end:
 
 "There's a lot of things that Linux is 'better' at, and a
 lot of things FreeBSD is 'better' at, and a lot of those
 things can easily fluctuate on a daily or weekly basis,"
 said Fuller, who maintains a Linux vs BSD Web page.
 "Thus, any definitive narrow statement that can be made
 is usually obsolete before anyone hears it.".
 
 Perfect!

Thank you, my fans!  Please leave your monetary contributions in the hat
on your way out;



-- 
Matthew Fuller (MF4839) |[EMAIL PROTECTED]
Unix Systems Administrator  |[EMAIL PROTECTED]
Specializing in FreeBSD |http://www.over-yonder.net/
FutureSouth Communications  |ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"


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

Re: IDE breakage

[Julian Elischer]

My fault

I accidentally replaced a PAGE_MASK  with a PAGE_SIZE.
the resulting bug only changes teh behaviour on unaligned pages
which are only possible on the raw device.
(e.g. fsck)

the Cyrix 5530 we used to test has a bug where we cannot do unalligned
transfers by DMA anyhow, so we never hit this bug..

fixed in -current 
will be fixxed in -stable when I reintroduce the patch...

julian


On Thu, 22 Jul 1999 [EMAIL PROTECTED] wrote:

  I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
  on recent versions of -STABLE. Here's an excerpt from messages; kernel
  #3 is a recent -STABLE (yesterday's sources), while kernel #2 is
  3.2-RELEASE. The config file for both is identical.
 
 I can confirm problems with DMA from IDE disks in -STABLE. The problems
 seem to have been introduced in
 
   $Id: ide_pci.c,v 1.28.2.1 1999/07/20 22:58:20 julian Exp $
 
 And the effect for me is that the system stops in singleuser mode, with
 a "DMA failure" message. This is on a 440BX/PII-350 system.
 
 Reverting to 1.28 (from 17. January 1999) fixes the problems.
 
 Please back out 1.28.2.1, at least in -STABLE.
 
 Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-hackers" in the body of the message
 



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

Re: poor ethernet performance?

[Kenton A. Hoover]

You can hijack the MAC address after the CAM table (not ARP cache) times 
out for the switches.  However, you can't just listen to their traffic 
unless you're on a span port (and span ports don't always work correctly).

VLANing has a number of goals, of which you are listing only one.  Another 
is to permit any net to appear on any switch within the switch fabric.  
VLANs are usually used in a form that spans multiple switches, not just 
using VLANs on a single switch.  At an installation I put together in 
India, we used VLANs to allow us to better use IP addresses in a strange 
physical layout.  When we were building out our New Site Architecture at 
Cisco in San Jose, we used VLANs to cut down the number of routing 
components necessary and further to take advantage of Layer 3 
short-cutting in a number of spots around the buildings.

On Wed, 21 Jul 1999 00:33:31 PDT, Sendmail channeled Matthew Dillon saying:
 The switch routes traffic based on its ARP cache.  While you cannot 
 easily monitor another port's traffic, you can take over its MAC address
 and steal its traffic.
 
 Cisco VLANs perform a different function.  Remember that a logical ethern
et
 segment is typically routed by a single network route.  For example,
 a class C or a subnetted class C.  The catalyst allows you to throw
 machines into different VLAN buckets which, in addition to the better
 security, allows you to assign separate subnets to each bucket.  The
 switch itself doesn't care, but this can reduce global ARP traffic
 significantly.   Catalysts can have hundreds of ports stuffed into them.

(ex-of Cisco Systems)


| Kenton A. Hoover  | [EMAIL PROTECTED] |
|  Private Citizen  ||
| San Francisco, California ||
|= http://www.shockwave.org/~shibumi |
|   A non-vegetarian anti-abortionist is a contradiction in terms.   |
| -- Phyllis Schlafly|


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

Re: Will FreeBSD ever see native IPv6 ??

[Julian Elischer]

they ARE doing it,
but they haven't got the merged TCP stack quite right
they are not publically anouncing anything till it works...

On Thu, 22 Jul 1999, John Hay wrote:

 Are you just teasing or are you serious?
 
 I searched through their site (again), but except for being mentioned
 in their TODO for the past few months, I can't find anything that
 indicates that they or anyone else is working on it. They may be, but
 it isn't visible anywhere where I have looked. It would be nice if
 there was some place to follow their progress, because I'm also one
 of the people that would like to see IPv6 integrated into FreeBSD.
 
 John
 -- 
 John Hay -- [EMAIL PROTECTED]
 
  
  FreeBSD will have native IPV6 within a matter of weeks at this stage.. 
  the code is being readied as we speak.  see www.kame.net . 3 sets of
  developers for FreeBSD IPV6 have merged their efforts and the result of
  this should be available by the end of summer (Northern).  (which isn't
  far away now..) 
  
  On Wed, 21 Jul 1999, David O'Brien wrote:
  
   So is FreeBSD *EVER* going to see native IPv6 ??
   I attended a talk by a group of Intrusion Detection researchers.  They
   were basing their research on FreeBSD because they needed divert
   sockets and found FreeBSD worked perfectly for this in this respect.
   However, once they needed IPv6 and IPsec guess what happened???  They
   moved to Linux and now have such a time investment in their custom kernel
   hacks FreeBSD will never be an option for them again.
   
   NetBSD and OpenBSD get more and more coverage from IPv6/IPsec
   capabilities every day.  FreeBSD has lost considerable ground if we want
   to be a platform of choice for network and security researchers.
   
   Now ever LSOF has IPv6 support for NetBSD and OpenBSD...
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-hackers" in the body of the message
 



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

rndcontrol and SMP

[sthaug]

rndcontrol doesn't work very well for SMP systems. I have a system here
with IRQs 16 and 18 for Ethernet and SCSI:

fxp0: Intel EtherExpress Pro 10/100B Ethernet rev 0x05 int a irq 18 on pci0.10.0
ahc0: Adaptec 2940 Ultra2 SCSI adapter rev 0x00 int a irq 16 on pci0.12.0

and I'd like to use these with rndcontrol. However, the ioctl chokes on
IRQ = 16. From i386/i386/mem.c:

/*
 * XXX the data is 16-bit due to a historical botch, so we use
 * magic 16's instead of ICU_LEN and can't support 24 interrupts
 * under SMP.
 */
intr = *(int16_t *)data;
if (cmd != MEM_RETURNIRQ  (intr  0 || intr = 16))
return (EINVAL);

What is needed to make this support a more sensible number of IRQs?


Also, rndcontrol naturally returns an error message, which could have
been better:

rndcontrol: rndcontrol: Invalid argument

rndcontrol uses warn() with argv[0] as the argument - but warn() is
documented to always print the program name. So it gets doubled. Below
is a patch against 3.2-STABLE to make it slightly more intelligent, so
we get an error message like this instead:

rndcontrol: setting irq 16: Invalid argument

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
--
*** rndcontrol.c.orig   Mon Oct 13 13:08:47 1997
--- rndcontrol.cThu Jul 22 22:06:52 1999
***
*** 76,82 
printf("%s: setting irq %d\n", argv[0], irq);
result = ioctl(fd, MEM_SETIRQ, (char *)irq);
if (result == -1) {
!   warn("%s", argv[0]);
return (1);
}
break;
--- 76,82 
printf("%s: setting irq %d\n", argv[0], irq);
result = ioctl(fd, MEM_SETIRQ, (char *)irq);
if (result == -1) {
!   warn("setting irq %d", irq);
return (1);
}
break;
***
*** 86,92 
printf("%s: clearing irq %d\n", argv[0], irq);
result = ioctl(fd, MEM_CLEARIRQ, (char *)irq);
if (result == -1) {
!   warn("%s", argv[0]);
return (1);
}
break;
--- 86,92 
printf("%s: clearing irq %d\n", argv[0], irq);
result = ioctl(fd, MEM_CLEARIRQ, (char *)irq);
if (result == -1) {
!   warn("clearing irq %d", irq);
return (1);
}
break;
***
*** 98,104 
if (verbose) {
result = ioctl(fd, MEM_RETURNIRQ, (char *)irq);
if (result == -1) {
!   warn("%s", argv[0]);
return (1);
}
printf("%s: interrupts in use:", argv[0]);
--- 98,104 
if (verbose) {
result = ioctl(fd, MEM_RETURNIRQ, (char *)irq);
if (result == -1) {
!   warn("");
return (1);
}
printf("%s: interrupts in use:", argv[0]);


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

SURVEY: Sound cards that work under FreeBSD

[John Reynolds~]

Hello all,

I'm working with Nik Clayton to update FAQ 3.15 to give a more comprehensive
list of sound cards known to work with FreeBSD. That's why I'm sending out
this template to this list. Please take the time to fill it out with
information regarding your sound card so that we can compile a better list
for posterity. I will do my best to keep the list current as FreeBSD evolves
(please send to me or cc: me along with the list--it'll be easier to filter
responses than grabbing them out of -hackers-digest :).

Please be as specific about makes, models, chipsets, etc. as you can. The
author of the first mail received regarding a specific sound card will be
listed as the contributor of that information (unless he/she does not want
his/her e-mail address listed :). Please note also that I would like
information about sound cards that do NOT work (as of yet) under FreeBSD if
anyone has experience with them.

Hopefully, this will go well and we will be able to branch out into other pieces
of supported/non-supported hardware in the future. Thank you.

Survey:
---

1) The sound card make and model/chipset. Please be as specific as you can with
   board rev numbers if possible. Please include wether the card is ISA or PCI.


2) FreeBSD version(s) it was tested with. List *all* versions of FreeBSD for
   which you can verify that the sound card does/doesn't work (don't include
   -BETA or -SNAP releases but dates on -STABLE and -CURRENT branches are
   welcome).


3) Appropriate lines from your kernel config file / PNP setup. i.e. what did
   you have to do to get this card working? Did you need patches not committed
   to a particular branch (if so URLs would be welcome)? Do you use OSS drivers
   instead?


4) Sample dmesg output for properly configured device. Show the world what
   boot messages relate to the device after properly configured.


5) Miscellaneous notes. State anything "not obvious" to the casual FreeBSD
   user. Good examples might be, "volume is 0 by default, use mixer(1) to
   adjust at boot time," or "sh MAKEDEV snd1 for the 1st device, not snd0."


6) Is it OK to publish your e-mail address / name as the contributor of this
   information? You may type in an anti-spam version of your e-mail address
   below if you would like that option instead.


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds   CEG, CCE, Next Generation Flows, HLA  |
| Intel Corporation  MS: CH6-210   Phone: 480-554-9092   pgr: 868-6512  |
| [EMAIL PROTECTED]  http://www-aec.ch.intel.com/~jreynold/  |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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

Re: Squid - a bug in src/sys/kern/uipc_socket.c

[Matthew Dillon]

This isn't really a bug since this is a TCP connection.   TCP makes
no guarentees that atomic writes will show up as atomic reads, and
the squid code shouldn't be making that assumption.

On the otherhand, the proposed fix appears to be an excellent performance
optimization.  It is basically only turning 'atomic' on for relatively
small writes, which should be a win for a receiver whether over a
localhost connection or a real network.  I can't imagine that it would
cause a performance loss in any other situation -- it might result in
a slightly smaller-then-full-sized TCP packet occassionally in a stream
but that's about it.

I think committing this would be beneficial.  Would someone w/ commit
privs care to review and then commit this bit?

-Matt
Matthew Dillon 
[EMAIL PROTECTED]

:Hi,
:
:please don't kill me if it's "well known issue":
:
:I've found that there is a report on Squid site, which
:describes a problem with FreeBSD IPC and includes suggested fix.
:I verified that this suggested fix is not included in 3.2-RELEASE.
:
:I wonder, if it is really a bug, as I cannot find it in PR database.
:
:Could someone please comment on this report/bug/suggested fix
:and if/when the fix could/will be submited?
:
:original URL:
:http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2
:
:   Thanks in advance,
:   Milon
:--
:[EMAIL PROTECTED]
:
:
: bug report and suggested fix -
:mbuf size
:
:We noticed an odd thing with some of Squid's interprocess communication.
:Often, output from the dnsserver processes would NOT be read in one
:chunk. With full debugging, it looks like this:
:
:1998/04/02 15:18:48| comm_select: FD 46 ready for reading
:1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (100
:bytes)
:1998/04/02 15:18:48| ipcache_dnsHandleRead: Incomplete reply
:other processing occurs...
:1998/04/02 15:18:48| comm_select: FD 46 ready for reading
:1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (9
:bytes)
:1998/04/02 15:18:48| ipcache_parsebuffer: parsing:
:$name www.karup.com
:$h_name www.karup.inter.net
:$h_len 4
:$ipcount 2
:38.15.68.128
:38.15.67.128
:$ttl 2348
:$end
:
:Interestingly, it is very common to get only 100 bytes on the first
:read. When two read() calls are required, this adds additional latency
:to the overall request. On our caches running Digital Unix, the median
:dnsserver response time was measured at 0.01 seconds. On our FreeBSD
:cache, however, the median latency was 0.10 seconds.
:
:Here is a simple patch to fix the bug: 
:
:===
:RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v
:retrieving revision 1.40
:retrieving revision 1.41
:diff -p -u -r1.40 -r1.41
:--- src/sys/kern/uipc_socket.c  1998/05/15 20:11:30 1.40
:+++ /home/ncvs/src/sys/kern/uipc_socket.c   1998/07/06 19:27:14
:1.41
:@@ -31,7 +31,7 @@
:  * SUCH DAMAGE.
:  *
:  * @(#)uipc_socket.c   8.3 (Berkeley) 4/15/94
:- * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $
:+ * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $
:  */
: 
: #include sys/param.h
:@@ -491,6 +491,7 @@ restart:
:mlen = MCLBYTES;
:len = min(min(mlen, resid), space);
:} else {
:+   atomic = 1;
: nopages:
:len = min(min(mlen, resid), space);



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

Re: Proposal for new syscall to close files

[Matthew Dillon]

:Hi,
:
:   I like this approach. I have a number of often spawned daemon
:processes that could benefit from this. One of the last process
:we debugged where we had unwanted open filedescriptors was in
:programs invoked by the cvs loginfo script.
:
:   For naming convention considerations, I might suggest 'closeall'
:or 'closefdset' or something similar... at least have 'close' in 
:name... :-)

Well, when I weight the benefit of the savings in overhead for a single
syscall verses a close() loop, and when I weigh the seriousness of 
introducing a syscall that would not be portable to other operating 
systems, and if I also take into account the work required to deal with
descriptors after forking a daemon  well, I don't think that adding
a new syscall would be worth the relatively minor benefit nor do I think
the improvement in performance would be noticeable.  The benefit isn't
great enough to warrent a new syscall in my view.

I've written a number of forking daemons, most noteable my web server
and my Diablo news transit system.

I just don't think the reduced overhead would be noticeable over simply
calling close(), and I didn't have any problems keeping track of which
file descriptors to close in Diablo (and there could be 100+ descriptors).
Keep in mind that after a fork these descriptors have a ref count  1,
meaning that the close() syscall is almost free.  If you assume 5uS/close
you are still talking quite a bit less then a millisecond to close a
hundred descriptors.  And that's pretty much the worst case I can think
of.

-Matt



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

Re: Will FreeBSD ever see native IPv6 ??

[Ollivier Robert]

According to John Hay:
 in their TODO for the past few months, I can't find anything that
 indicates that they or anyone else is working on it. They may be, but

I assure you they're working on it. Problem is they also have day jobs and
some part of integration is complicated by export controls (the NRL code is
more advanced IPsec-wise than our japanese friends).
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #72: Mon Jul 12 08:26:43 CEST 1999



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

RE: Squid - a bug in src/sys/kern/uipc_socket.c

[Jaye Mathisen]

Maybe it could be made a sysctl knob...

On Thu, 22 Jul 1999, Jason Young wrote:

 
 It's been committed before, and broke many things (X and CVSup come to
 mind). I have it compiled in locally on a few machines but it's
 definitely not suitable for general distribution until a solution is
 found that doesn't break applications.
 
 Jason Young
 accessUS Chief Network Engineer
 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of
  Matthew Dillon
  Sent: Thursday, July 22, 1999 3:57 PM
  To: Papezik Milon
  Cc: [EMAIL PROTECTED]
  Subject: Re: Squid - a bug in src/sys/kern/uipc_socket.c
 
 
  This isn't really a bug since this is a TCP connection.
TCP makes
  no guarentees that atomic writes will show up as atomic
  reads, and
  the squid code shouldn't be making that assumption.
 
  On the otherhand, the proposed fix appears to be an
  excellent performance
  optimization.  It is basically only turning 'atomic' on
  for relatively
  small writes, which should be a win for a receiver
  whether over a
  localhost connection or a real network.  I can't
  imagine that it would
  cause a performance loss in any other situation -- it
  might result in
  a slightly smaller-then-full-sized TCP packet
  occassionally in a stream
  but that's about it.
 
  I think committing this would be beneficial.  Would
  someone w/ commit
  privs care to review and then commit this bit?
 
  -Matt
  Matthew Dillon
  [EMAIL PROTECTED]
 
  :Hi,
  :
  :please don't kill me if it's "well known issue":
  :
  :I've found that there is a report on Squid site, which
  :describes a problem with FreeBSD IPC and includes suggested fix.
  :I verified that this suggested fix is not included in 3.2-RELEASE.
  :
  :I wonder, if it is really a bug, as I cannot find it in PR
  database.
  :
  :Could someone please comment on this report/bug/suggested fix
  :and if/when the fix could/will be submited?
  :
  :original URL:
  :http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2
  :
  :   Thanks in advance,
  :   Milon
  :--
  :[EMAIL PROTECTED]
  :
  :
  : bug report and suggested fix -
  :mbuf size
  :
  :We noticed an odd thing with some of Squid's interprocess
  communication.
  :Often, output from the dnsserver processes would NOT be read in one
  :chunk. With full debugging, it looks like this:
  :
  :1998/04/02 15:18:48| comm_select: FD 46 ready for reading
  :1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from
  DNS ID 2 (100
  :bytes)
  :1998/04/02 15:18:48| ipcache_dnsHandleRead: Incomplete reply
  :other processing occurs...
  :1998/04/02 15:18:48| comm_select: FD 46 ready for reading
  :1998/04/02 15:18:48| ipcache_dnsHandleRead: Result from DNS ID 2 (9
  :bytes)
  :1998/04/02 15:18:48| ipcache_parsebuffer: parsing:
  :$name www.karup.com
  :$h_name www.karup.inter.net
  :$h_len 4
  :$ipcount 2
  :38.15.68.128
  :38.15.67.128
  :$ttl 2348
  :$end
  :
  :Interestingly, it is very common to get only 100 bytes on the first
  :read. When two read() calls are required, this adds
  additional latency
  :to the overall request. On our caches running Digital
  Unix, the median
  :dnsserver response time was measured at 0.01 seconds. On
  our FreeBSD
  :cache, however, the median latency was 0.10 seconds.
  :
  :Here is a simple patch to fix the bug:
  :
  :===
  :RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v
  :retrieving revision 1.40
  :retrieving revision 1.41
  :diff -p -u -r1.40 -r1.41
  :--- src/sys/kern/uipc_socket.c  1998/05/15 20:11:30 1.40
  :+++ /home/ncvs/src/sys/kern/uipc_socket.c   1998/07/06
  19:27:14
  :1.41
  :@@ -31,7 +31,7 @@
  :  * SUCH DAMAGE.
  :  *
  :  * @(#)uipc_socket.c   8.3 (Berkeley) 4/15/94
  :- * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $
  :+ * $Id: FAQ.sgml,v 1.75 1999/07/06 16:07:36 wessels Exp $
  :  */
  :
  : #include sys/param.h
  :@@ -491,6 +491,7 @@ restart:
  :mlen = MCLBYTES;
  :len = min(min(mlen, resid), space);
  :} else {
  :+   atomic = 1;
  : nopages:
  :len = min(min(mlen, resid), space);
 
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with "unsubscribe freebsd-hackers" in the body of the message
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-hackers" in the body of the message
 



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

Re: RE: Squid - a bug in src/sys/kern/uipc_socket.c

[Matthew Dillon]

:
:It's been committed before, and broke many things (X and CVSup come to
:mind). I have it compiled in locally on a few machines but it's
:definitely not suitable for general distribution until a solution is
:found that doesn't break applications.
:
:Jason Young
:accessUS Chief Network Engineer

Hmm.. it doesn't look like anyone tracked down why it was breaking 
applications after it was backed out the fist time - July last year
looking at the CVS logs.

-Matt


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

Re: RE: Squid - a bug in src/sys/kern/uipc_socket.c

[Matthew Dillon]

::It's been committed before, and broke many things (X and CVSup come to
::mind). I have it compiled in locally on a few machines but it's
::definitely not suitable for general distribution until a solution is
::found that doesn't break applications.
::
::Jason Young
::accessUS Chief Network Engineer
:
:Hmm.. it doesn't look like anyone tracked down why it was breaking 
:applications after it was backed out the fist time - July last year
:looking at the CVS logs.
:
:   -Matt

Looking at the code more closely, a failure can occur if the amount of
data is larger then so-so_snd.sb_hiwat.  

This situation looks like it can occur if the socket buffer fills 
up (the sender is faster then the receiver).

The solution would be to have a slightly more involved patch.   Have
a 'tryatomic' variable which is set based on this particular situation
and then use it to mean 'atomic' in those cases where no error would
occur.

I am going to try to reproduce the failure with the original patch and
will work up a new patch that fixes it if it winds up being what I think
it will be.

-Matt



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

mbuf leakage in NFSv3 writes, possbile?

[David E. Cross]

I have 2 NFS servers.  One is primarily read-only, the other read-write, they
service the same clients (the read-only services more).  They are (were) of
the same build.  I have a problem on the read/write server where it chews
through mbuf clusters (it goes through about 3k in a day).  Especially late
at night the machine is not busy.  And now it is also not busy, yet every
minute or so it goes through a few mbuf clusters.  The rate is about 108
minutes for 300 clusters.  Does it sound reasonable that there is a mbuf leak
in the NFS code somewhere?

--
David Cross   | email: [EMAIL PROTECTED] 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself.  | WinNT:Linux::Linux:FreeBSD


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

Re: mbuf leakage in NFSv3 writes, possbile?

[David E. Cross]

Well, I just -STABLED the server to see if it fixed it, but I was certainly
running out.  the server had only 3000-ish mbuf chains, and it would go through
them all in a day.

--
David Cross   | email: [EMAIL PROTECTED] 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself.  | WinNT:Linux::Linux:FreeBSD


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

Re: InterMezzo: Project for kernel/FS hackers

[Ronald G. Minnich]

I'm working with intermezzo now. It's interesting. 

Note that the VFS is quite simple, and defines a simple kernel-user
channel which maps VFS ops to requests on an IPC channel. The
possibilities are endless ...

A freebsd port would be nice. Maybe you could use v9fs as a starting
point. 

ron




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

Re: IDE breakage

[Wes Peters]

Julian Elischer wrote:
 
 My fault
 
 I accidentally replaced a PAGE_MASK  with a PAGE_SIZE.
 the resulting bug only changes teh behaviour on unaligned pages
 which are only possible on the raw device.
 (e.g. fsck)
 
 the Cyrix 5530 we used to test has a bug where we cannot do unalligned
 transfers by DMA anyhow, so we never hit this bug..
 
 fixed in -current 
 will be fixxed in -stable when I reintroduce the patch...

Bad Programmer!  No doughnuts!

;^)

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
http://softweyr.com/   [EMAIL PROTECTED]


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

New patch fpr uipc_socket.c (was Squid - a bug in src/sys/kern/uipc_socket.c)

[Matthew Dillon]

I believe this will solve the previously reported problems.

With the original patch if I set net.inet.tcp.sendspace=63 and tried 
to run xterm from that machine to my local workstation, I got an X error.
If I set sendspace=31 the xterm process just locked up and did nothing
until I ^C'd it.

machine A   machine B
w/modified kernel   w/unmodified kernel
(sysctl's on this machine)

xterm run on A  -- display is on B

With this patch I can set net.inet.tcp.sendspace to anything (63, 31, 1,
whatever I want) and the xterm will still run.  And yes, the xterm is
amazingly slow when I set net.inet.tcp.sendspace to 1 :-)

This patch is relative to -CURRENT but should also work with -STABLE.

-Matt

Index: uipc_socket.c
===
RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v
retrieving revision 1.60
diff -u -r1.60 uipc_socket.c
--- uipc_socket.c   1999/06/17 23:54:47 1.60
+++ uipc_socket.c   1999/07/22 23:08:38
@@ -413,7 +413,8 @@
register struct mbuf *m;
register long space, len, resid;
int clen = 0, error, s, dontroute, mlen;
-   int atomic = sosendallatonce(so) || top;
+   int atomic = sosendallatonce(so) || top;/* required atomicy */
+   int try_atomic = atomic;/* requested atomicy */
 
if (uio)
resid = uio-uio_resid;
@@ -518,6 +519,7 @@
mlen = MCLBYTES;
len = min(min(mlen, resid), space);
} else {
+   try_atomic = 1; /* try to optimize */
 nopages:
len = min(min(mlen, resid), space);
/*
@@ -541,7 +543,7 @@
top-m_flags |= M_EOR;
break;
}
-   } while (space  0  atomic);
+   } while (space  0  try_atomic);
if (dontroute)
so-so_options |= SO_DONTROUTE;
s = splnet();   /* XXX */


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

Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's

[Doug]

On Wed, 21 Jul 1999, Vincent Poy wrote:

 Greetings everyone,
 
   What are the current good motherboards for FreeBSD for the pentium
 II and III?  I know on the Pentium, it was the ASUS board but for the
 PII/PIII, is the Abit the better board?  Also, I was wondering what is the
 fastest Celeron chip that can be overclocked to run at 100Mhz FSB?  Does
 it matter if it's Slot 1 or PPGA based?  Thanks.

At work we're having good results with an Intel N440BX
motherboard. It's a dual cpu board, running 2 PIII 500's like a champ. It
also has the ability to redirect all console output (like boot/bios
messages, etc.) to a serial console. It comes with a built in Etherexpress
Pro 100+ as well.

I have an Asus P2B at home that I've run my Celeron 300A
overclocked to 450 since the first of the year with no problems (and BIG
fans).

HTH,

Doug
-- 
On account of being a democracy and run by the people, we are the only
nation in the world that has to keep a government four years, no matter
what it does.
-- Will Rogers



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

Re: Filesystem question...

[Kris Kennaway]

On Thu, 22 Jul 1999, Ronald G. Minnich wrote:

 On Fri, 23 Jul 1999, Kris Kennaway wrote:
  Well, if you're running it as a kernel module then obviously you need root
  permissions to load it. If it's running as a userland process, then
  there's no reason why you can't run it as a user. mount presumably
  wouldn't care as long as you had access rights to the underlying objects
  (mountpoint + stacking layer process).
 
 well, you'll have to tell me more. (i have to get my freebsd source tree
 back :-) )
 
 Are you saying that as an ordinary user I can mount something on top of
 /tmp, for example?

If the vfs.usermount sysctl is 1, and you have appropriate access to the
thing you're trying to mount (block device, etc).

 Is the suser() check still in the mount system call? 

From vfs_syscalls.c:

if (usermount == 0  (error = suser(p)))
return (error);

usermount is tuned by the vfs.usermount sysctl and defaults to 0.

Kris



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

Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's

[Vincent Poy]

On Thu, 22 Jul 1999, Doug wrote:

 On Wed, 21 Jul 1999, Vincent Poy wrote:
 
  Greetings everyone,
  
  What are the current good motherboards for FreeBSD for the pentium
  II and III?  I know on the Pentium, it was the ASUS board but for the
  PII/PIII, is the Abit the better board?  Also, I was wondering what is the
  fastest Celeron chip that can be overclocked to run at 100Mhz FSB?  Does
  it matter if it's Slot 1 or PPGA based?  Thanks.
 
   At work we're having good results with an Intel N440BX
 motherboard. It's a dual cpu board, running 2 PIII 500's like a champ. It
 also has the ability to redirect all console output (like boot/bios
 messages, etc.) to a serial console. It comes with a built in Etherexpress
 Pro 100+ as well.

Cool... I thought the Intel motherboards weren't that good
compared to other brands..

   I have an Asus P2B at home that I've run my Celeron 300A
 overclocked to 450 since the first of the year with no problems (and BIG
 fans).

Hmmm, what kinda fans did you use and where can one get those?  Is
the 300A overclocked as fast as a regular PII 450Mhz?


Cheers,
Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED]      __  
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
GaiaNet Corporation - M  C Estate / / / /  | /  | __] ]  
Beverly Hills, California USA 90210   / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]



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

Re: Proposed substitution for ACLs

[Sergey Babkin]

Daniel C. Sobral wrote:
 
 Sergey Babkin wrote:
 
  I want to propose a simple substitution for ACLs. No, here
  is no patch yet but I'm ready and willing to do it. The reason
  why I want to discuss it first is that this is a Political Thing.
  And  if the Core Team decides that it's a Bad Thing, I suppose
  it will never get commited to the system. Because of this I
  would like to see some encouraging signs from the Core Team
  before implementing it.
 
 Do whatever you want: as a fs layer.

Speaking about the fs layers, can you please advise me on the current
state of nullfs ? Is it working now ? I have checked GNATS about this
and did not quite understood whether the results of a lengthly
discussion in there on this subject were ever committed.

On the other hand, I'm not sure whether implementing it as an FS
layer is a good idea. It is certainly possible to do by snooping
at the getattr/setattr calls but IMHO it will mean completely bypassing
the VOP_ACCESS of the underlying filesystem what may be not good.

On the other hand the changes to ufs_assess() seem to be quite small
and cover all the UFS type filesystems, such as FFS and EXT2FS.

Of course yet another option is to create one more fs type with all
the operations in the filesystem switch the same as for FFS except
for ufs_access().

What would be your recommendation ? Thanks!

Here is the proposed patch (made against 3.2). If it will be
considered OK I'll write some man page and LINT kernel entry too.
I'm not sure whether the sysctl sub-node vfs.ufs is really neccessary
but it seems to be logical.

-- cut here -
*** /sys/ufs/ufs/ufs_vnops.c1999/07/15 14:50:53 1.1
--- /sys/ufs/ufs/ufs_vnops.c1999/07/22 18:16:28
***
*** 57,62 
--- 57,63 
  #include sys/dirent.h
  #include sys/lockf.h
  #include sys/poll.h
+ #include sys/sysctl.h
  
  #include vm/vm_zone.h
  #include vm/vm.h
***
*** 104,109 
--- 105,128 
  static int ufsspec_read __P((struct vop_read_args *));
  static int ufsspec_write __P((struct vop_write_args *));
  
+ #ifdef ENABLE_UFS_COMMONID
+ /*
+  * Sysctl variables to control the unified user and
+  * group ID space.
+  * commonid is the lowest ID from which the common UID/GID space starts
+  * MINCOMMONID is the minimal value, if commonid is lower then the
+  * common ID space is disabled
+  */
+ 
+ #define MINCOMMONID   100
+ 
+ SYSCTL_NODE(_vfs, OID_AUTO, ufs, CTLFLAG_RW, 0, "Local Unix-type filesystems");
+ static int commonid=0;
+ SYSCTL_INT(_vfs_ufs, OID_AUTO, commonid, CTLFLAG_RW, commonid, 0,
+   "Lowest ID for the common GID/UID space");
+ 
+ #endif
+ 
  union _qcvt {
int64_t qcvt;
int32_t val[2];
***
*** 339,344 
--- 360,382 
mask |= S_IWUSR;
return ((ip-i_mode  mask) == mask ? 0 : EACCES);
}
+ 
+ #ifdef ENABLE_UFS_COMMONID
+   /* if the common UID/GID is enabled check the groups against the file UID */
+   if (commonid = MINCOMMONID  ip-i_uid = commonid) {
+   for (i = 0, gp = cred-cr_groups; i  cred-cr_ngroups; 
+   i++, gp++)
+   if (ip-i_uid == *gp) {
+   if (mode  VEXEC)
+   mask |= S_IXUSR;
+   if (mode  VREAD)
+   mask |= S_IRUSR;
+   if (mode  VWRITE)
+   mask |= S_IWUSR;
+   return ((ip-i_mode  mask) == mask ? 0 : EACCES);
+   }
+   }
+ #endif
  
/* Otherwise, check the groups. */
for (i = 0, gp = cred-cr_groups; i  cred-cr_ngroups; i++, gp++)
--- cut here 

-SB


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

Re: PAM LDAP in FreeBSD, and userfs too.

[John Polstra]

In article [EMAIL PROTECTED],
Dominic Mitchell  [EMAIL PROTECTED] wrote:
 On Thu, Jul 22, 1999 at 04:59:59PM +0700, Max Khon wrote:
  
  PAM is also "using masses of weird shared objects" but nevertheless it's
  quite usable
 
 By statically linked binaries?

Our PAM implementation works for static binaries too.  See the
sources for the gory details.  Basically it creates a library that
includes all the possible modules, and selects the right one at
runtime.  There's some linker set magic involved.

Concerning "masses of weird shared objects," you'd really better get
used to it.  It was the wave of the future 10 years ago.  It's not
going away.  Dynamic linking provides flexibility and modularity that
you just can't get from static linking.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."-- Nora Ephron


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

usb keyboard setup -or- HELP!

[Jim Bryant]

hi, i'm running 4.0-current on a dual p2-333 box.  i run X, and am
looking for help in setting up a usb keyboard for use with
FreeBSD/Xfree86.

if anyone has this running, i could use the help in setting it up.

also, this keyboard has a ps2 mouse connector.  does the mouse get
recognized as a usb mouse?

jim
-- 
All opinions expressed are mine, if you|  "I will not be pushed, stamped,
think otherwise, then go jump into turbid  |  briefed, debriefed, indexed, or
radioactive waters and yell WAHOO !!!  |  numbered!" - #1, "The Prisoner"
--
Inet: [EMAIL PROTECTED]AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw
voice: KC5VDJ - 6  2 Meters AM/FM/SSB, 70cm FM.   http://www.tfs.net/~jbryant
--
HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+


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

Re: mbuf leakage in NFSv3 writes, possbile?

[Doug]

"David E. Cross" wrote:
 
 Well, I just -STABLED the server to see if it fixed it, but I was certainly
 running out.  the server had only 3000-ish mbuf chains, and it would go through
 them all in a day.

Well, have you tried increasing the number of available mbufs and see if
you reach a point of stability? Assuming you have enough physical ram you
could do 15k mbufs on -Stable without a problem. Check LINT for the
nmbclusters option if you need help with it.

Good luck,

Doug


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

Re: System unique identifier.....

[Mike Smith]

  That's not quite true. It wouldn't be too hard to modify existant files,
  but writing new ones/truncating would take a lot of work. It's still not
  a great idea to try to use a file on the FS for storage of persistent
  data. Wouldn't it be possible to have the kernel itself read in persistent
  data (in some form such as getenv?) to be written to disk? That way, the
  boot loader could pass it easily, and not have to worry about storage.
 
 This may sound like a heresy to you, but... Why don't use the Forth blocks
 for that?

For what?  Saving parametric data?  That was always the plan, but the 
last thing I think anyone wants to do is rewrite the ffs code in Forth.

 They were invented for that purpose. We can create the files
 beforehand (under normal OS operation), then from the bootloader we can
 read and modify them - I suppose writing to a disk block is much easier
 than through the filesystem layer...

Yes, that's what we've always discussed as being the most likely course 
of action.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  msm...@freebsd.org
\\-- Joseph Merrick   \\  msm...@cdrom.com




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

Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's

[Jim Bryant]

In reply:
 On Wed, 21 Jul 1999, Kip Macy wrote:
 
  My employer has gone through numerous motherboards, we have found the ASUS
  P2B (now the P2B-F) to be rock solid for Pentium II usage.
 
 This is probably more appropriate for -hardware or even just -chat..
 but anyway, I'll second that recommendation.  I've found the ASUS P2B
 series to be very solid.  I've also used many ATrend BX boards for
 Winblows95 boxes (simply because they were cheaper than the ASUS
 boards), and haven't had a bit of trouble with them.  YMMV.
 
 
 -- Chris Dillon - cdil...@wolves.k12.mo.us - cdil...@inter-linc.net
FreeBSD: The fastest and most stable server OS on the planet.
For Intel x86 and Alpha architectures (SPARC under development).
( http://www.freebsd.org )
 
One should admire Windows users.  It takes a great deal of
 courage to trust Windows with your data.

don't leave out the tyan thunder2 and thunder100 boards.  the only
problem i even know of with the thunder2 is the sound chip still isn't
recognized, and the id codes pnp returns on the sound chip may differ
from board to board [others claim it works for them, but not here].

i have heard of no problems with the thunder100 board.

jim
-- 
All opinions expressed are mine, if you|  I will not be pushed, stamped,
think otherwise, then go jump into turbid  |  briefed, debriefed, indexed, or
radioactive waters and yell WAHOO !!!  |  numbered! - #1, The Prisoner
--
Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw
voice: KC5VDJ - 6  2 Meters AM/FM/SSB, 70cm FM.   http://www.tfs.net/~jbryant
--
HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+


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

Re: Anyone know how to dim and SGI flat panel?

[Matthew Dillon]

:
:I'd bet it's done using DPMS.  See if the XFree86 4.x code can tell you 
:anything about the monitor's capabilities.

It's up?  Very cool, they actually put the prerelease up 2 days ago!
47MB download, yummy!  DGA is going to be so cool.

Unfortunately it looks like the DPMS stuff is still a bit primitive.
Shoot.  I'll check it out, though.  The 3.3.3 I128 driver (that's
the number 9 card) does not appear to support DPMS at all.

SGI's site has a whitepaper on the flatpanel but it's a bit spare on
control protocols.  They do say something about an I2C bus but I dunno
whether that is what DPMS uses or not.

-Matt
Matthew Dillon 
dil...@backplane.com


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

Re: [FreeBSD-net-jp 1746] [FYI] Adaptec AIC-6915 Starfire ethernet controller driver and plus question compaq presario dec et

[Dirk GOUDERS]

o.k., Bill, I'll try to translate it for you:

   $B?9ED$G$9!#(B

My name is Morita.

   
These are Adaptec's replacements for its older DEC 21x4x-based multiport
   
   $B$3$N%I%i%$%P!$OL5$/$J$k$N$G$7$g$$+!)(B-DEC 21x4x-based
   no more supllyed -DEC 21x4x-based

Are these drivers lost? 
(Maybe in the meaning of no more supported.)

  
  Sorry, but I'm just a dumb american: I can't read this.
   
line of adapters. All cards support 10/100 speeds in full or half duplex
.
The multiport cards consist of multiple AIC-6915 chips linkec via a PCI
to PCI bridge. Currently I have only tested the ANA-62022 dual port card
,
however all of them should work equally well. The 64-bit cards will work
in a 32-bit slot on most newer machines.
   
   
   $B%3%s%Q%C%/!!(BPRESARIO$B!!(B2274$B!!$K(BFreeBSD3.2$B%$%s%9%H!%k$7$?$N$G$9$,!(B
   NIC$B!'!!(BDEC 21143-based 
   $B$H%S%G%*%+!%I!'(bsis5598$...@_dj$,$$^$/$$$-$^$;$s!8=:_(B
   $BF0$+$7$F$k(B
   $BJ}$,$$$i$7$?$i65$($F$/$...@$5$$!#(B

I installed FreeBSD 3.2 on a Compaq PRESARIO 2274 but my DEC
21143-based NIC and SiS5598 video card do not work well (maybe at all).
Can you please tell me, how to get them work?

  
  I can't read this either. :(

I guess, I understood the question, but I cannot answer it.
Can you?

Dirk

  
  -Bill
  
  -- 
  
=
  -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
  Work: wp...@ctr.columbia.edu | Center for Telecommunications Researc
h
  Home:  wp...@skynet.ctr.columbia.edu | Columbia University, New York City
  
=
   It is not I who am crazy; it is I who am mad! - Ren Hoek, Space Madness
  
=
  
  
  To Unsubscribe: send mail to majord...@freebsd.org
  with unsubscribe freebsd-hackers in the body of the message


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

Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's

[Сергей Осокин]

On Wed, 21 Jul 1999, Vincent Poy wrote:

 Greetings everyone,
 
   What are the current good motherboards for FreeBSD for the pentium
 II and III?  I know on the Pentium, it was the ASUS board but for the
 PII/PIII, is the Abit the better board?  Also, I was wondering what is the
 fastest Celeron chip that can be overclocked to run at 100Mhz FSB?  Does
 it matter if it's Slot 1 or PPGA based?  Thanks.

My home box based Abit BX6 rev.2.0 Slot1  i use PPGA Celeron-300A with
Socket370-Slot1 bridge overclocked to 450 (100x4.5) with Pelitier
element. This motherboard support PII/PIII.
More overclockers says: Abit better then Asus. I think it right.
All works fine.

Rgdz,
Sergey Osokin aka oZZ,
o...@etrust.ru
http://www.freebsd.org.ru



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

Re: Will FreeBSD ever see native IPv6 ??

[John Hay]

Are you just teasing or are you serious?

I searched through their site (again), but except for being mentioned
in their TODO for the past few months, I can't find anything that
indicates that they or anyone else is working on it. They may be, but
it isn't visible anywhere where I have looked. It would be nice if
there was some place to follow their progress, because I'm also one
of the people that would like to see IPv6 integrated into FreeBSD.

John
-- 
John Hay -- john@mikom.csir.co.za

 
 FreeBSD will have native IPV6 within a matter of weeks at this stage.. 
 the code is being readied as we speak.  see www.kame.net . 3 sets of
 developers for FreeBSD IPV6 have merged their efforts and the result of
 this should be available by the end of summer (Northern).  (which isn't
 far away now..) 
 
 On Wed, 21 Jul 1999, David O'Brien wrote:
 
  So is FreeBSD *EVER* going to see native IPv6 ??
  I attended a talk by a group of Intrusion Detection researchers.  They
  were basing their research on FreeBSD because they needed divert
  sockets and found FreeBSD worked perfectly for this in this respect.
  However, once they needed IPv6 and IPsec guess what happened???  They
  moved to Linux and now have such a time investment in their custom kernel
  hacks FreeBSD will never be an option for them again.
  
  NetBSD and OpenBSD get more and more coverage from IPv6/IPsec
  capabilities every day.  FreeBSD has lost considerable ground if we want
  to be a platform of choice for network and security researchers.
  
  Now ever LSOF has IPv6 support for NetBSD and OpenBSD...




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

Re: Anyone know how to dim and SGI flat panel?

[Doug Rabson]

On Thu, 22 Jul 1999, Matthew Dillon wrote:

 
 :
 :I'd bet it's done using DPMS.  See if the XFree86 4.x code can tell you 
 :anything about the monitor's capabilities.
 
 It's up?  Very cool, they actually put the prerelease up 2 days ago!
 47MB download, yummy!  DGA is going to be so cool.
 
 Unfortunately it looks like the DPMS stuff is still a bit primitive.
 Shoot.  I'll check it out, though.  The 3.3.3 I128 driver (that's
 the number 9 card) does not appear to support DPMS at all.
 
 SGI's site has a whitepaper on the flatpanel but it's a bit spare on
 control protocols.  They do say something about an I2C bus but I dunno
 whether that is what DPMS uses or not.

XFree86 has an i2c driver in it for talking to monitors so it sounds as if
it should see it.

--
Doug Rabson Mail:  d...@nlsystems.com
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




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

Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's

[Vincent Poy]

On Thu, 22 Jul 1999, [KOI8-R] ?? ?? wrote:

 On Wed, 21 Jul 1999, Vincent Poy wrote:
 
  Greetings everyone,
  
  What are the current good motherboards for FreeBSD for the pentium
  II and III?  I know on the Pentium, it was the ASUS board but for the
  PII/PIII, is the Abit the better board?  Also, I was wondering what is the
  fastest Celeron chip that can be overclocked to run at 100Mhz FSB?  Does
  it matter if it's Slot 1 or PPGA based?  Thanks.
 
 My home box based Abit BX6 rev.2.0 Slot1  i use PPGA Celeron-300A with
 Socket370-Slot1 bridge overclocked to 450 (100x4.5) with Pelitier
 element. This motherboard support PII/PIII.
 More overclockers says: Abit better then Asus. I think it right.
 All works fine.

Pretty interesting...  The Pelitier element is pretty expensive I
think...  It seems like I've seen more Abit than ASUS Boards when it's a
FreeBSD box.  We have a 266 running at 400 (100x4) but I don't know which
Pentium II would it be the closest to since this is a cacheless chip.  It
has 384 megs of ram and one thing I can't figure out is that the machine
will sometimes pause for a few seconds when I type a command...


Cheers,
Vince - vi...@mcestate.com - vi...@gaianet.net      __  
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
GaiaNet Corporation - M  C Estate / / / /  | /  | __] ]  
Beverly Hills, California USA 90210   / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]



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

IDE breakage

[Dag-Erling Smorgrav]

I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
on recent versions of -STABLE. Here's an excerpt from messages; kernel
#3 is a recent -STABLE (yesterday's sources), while kernel #2 is
3.2-RELEASE. The config file for both is identical.

Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1992-1999 FreeBSD Inc.
Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 22 10:19:35 xxx /kernel.old: The Regents of the University of California. 
All rights reserved.
Jul 22 10:19:35 xxx /kernel.old: FreeBSD 3.2-STABLE #3: Wed Jul 21 16:21:55 
CEST 1999
Jul 22 10:19:35 xxx /kernel.old: r...@xxx.x.xx:/usr/src/sys/compile/X
Jul 22 10:19:35 xxx /kernel.old: Timecounter i8254  frequency 1193182 Hz
Jul 22 10:19:35 xxx /kernel.old: Timecounter TSC  frequency 348205681 Hz
Jul 22 10:19:35 xxx /kernel.old: CPU: Pentium II/Xeon/Celeron (348.21-MHz 
686-class CPU)
Jul 22 10:19:35 xxx /kernel.old: Origin = GenuineIntel  Id = 0x652  Stepping 
= 2
Jul 22 10:19:35 xxx /kernel.old: 
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
Jul 22 10:19:35 xxx /kernel.old: real memory  = 134217728 (131072K bytes)
Jul 22 10:19:35 xxx /kernel.old: avail memory = 127774720 (124780K bytes)
Jul 22 10:19:35 xxx /kernel.old: Preloaded elf kernel kernel at 0xc023c000.
Jul 22 10:19:35 xxx /kernel.old: Probing for devices on PCI bus 0:
Jul 22 10:19:35 xxx /kernel.old: chip0: Intel 82443BX host to PCI bridge rev 
0x02 on pci0.0.0
Jul 22 10:19:35 xxx /kernel.old: chip1: Intel 82443BX host to AGP bridge rev 
0x02 on pci0.1.0
Jul 22 10:19:35 xxx /kernel.old: xl0: 3Com 3c905-TX Fast Etherlink XL rev 
0x00 int a irq 11 on pci0.13.0
Jul 22 10:19:35 xxx /kernel.old: xl0: Ethernet address: 00:60:08:e8:6b:1d
Jul 22 10:19:35 xxx /kernel.old: xl0: autoneg complete, link status good 
(full-duplex, 100Mbps)
Jul 22 10:19:35 xxx /kernel.old: chip2: Intel 82371AB PCI to ISA bridge rev 
0x02 on pci0.20.0
Jul 22 10:19:35 xxx /kernel.old: ide_pci0: Intel PIIX4 Bus-master IDE 
controller rev 0x01 on pci0.20.1
Jul 22 10:19:35 xxx /kernel.old: chip3: Intel 82371AB Power management 
controller rev 0x02 on pci0.20.3
Jul 22 10:19:35 xxx /kernel.old: Probing for devices on PCI bus 1:
Jul 22 10:19:35 xxx /kernel.old: vga0: ATI model 4742 graphics accelerator 
rev 0x5c int a irq 11 on pci1.0.0
Jul 22 10:19:35 xxx /kernel.old: Probing for PnP devices:
Jul 22 10:19:35 xxx /kernel.old: Probing for devices on the ISA bus:
Jul 22 10:19:35 xxx /kernel.old: sc0 on isa
Jul 22 10:19:35 xxx /kernel.old: sc0: VGA color 16 virtual consoles, flags=0x0
Jul 22 10:19:35 xxx /kernel.old: atkbdc0 at 0x60-0x6f on motherboard
Jul 22 10:19:35 xxx /kernel.old: atkbd0 irq 1 on isa
Jul 22 10:19:35 xxx /kernel.old: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
Jul 22 10:19:35 xxx /kernel.old: fdc0: FIFO enabled, 8 bytes threshold
Jul 22 10:19:35 xxx /kernel.old: fd0: 1.44MB 3.5in
Jul 22 10:19:35 xxx /kernel.old: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on 
isa
Jul 22 10:19:35 xxx /kernel.old: wdc0: unit 0 (wd0): Maxtor 90640D4, DMA, 
32-bit, multi-block-16
Jul 22 10:19:35 xxx /kernel.old: wd0: 6149MB (12594960 sectors), 13328 cyls, 15 
heads, 63 S/T, 512 B/S
Jul 22 10:19:35 xxx /kernel.old: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on 
isa
Jul 22 10:19:35 xxx /kernel.old: wdc1: unit 0 (atapi): CD-ROM CDU611-Q/2.0c, 
removable, accel, dma, iordis
Jul 22 10:19:35 xxx /kernel.old: acd0: drive speed 1723KB/sec, 256KB cache
Jul 22 10:19:35 xxx /kernel.old: acd0: supported read types: CD-R, CD-RW, CD-DA
Jul 22 10:19:35 xxx /kernel.old: acd0: Audio: play, 16 volume levels
Jul 22 10:19:35 xxx /kernel.old: acd0: Mechanism: ejectable tray
Jul 22 10:19:35 xxx /kernel.old: acd0: Medium: no/blank disc inside, unlocked
Jul 22 10:19:35 xxx /kernel.old: npx0 on motherboard
Jul 22 10:19:35 xxx /kernel.old: npx0: INT 16 interface
Jul 22 10:19:35 xxx /kernel.old: vga0 at 0x3b0-0x3df maddr 0xa msize 131072 
on isa
Jul 22 10:19:35 xxx /kernel.old: IP packet filtering initialized, divert 
disabled, rule-based forwarding disabled, unlimited logging
Jul 22 10:19:35 xxx /kernel.old: DUMMYNET initialized (990504)
Jul 22 10:19:35 xxx /kernel.old: changing root device to wd0s1a
Jul 22 10:19:35 xxx /kernel.old: wd0: DMA failure, DMA status 5active
Jul 22 10:19:35 xxx last message repeated 11 times

Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1992-1999 FreeBSD Inc.
Jul 22 10:19:35 xxx /kernel.old: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 22 10:19:35 xxx /kernel.old: The Regents of the University of California. 
All rights reserved.
Jul 22 10:19:35 xxx /kernel.old: FreeBSD 3.2-RELEASE #2: Mon Jul 12 20:41:42 
CEST 1999
Jul 22 10:19:35 xxx /kernel.old: r...@xxx.x.xx:/usr/src/sys/compile/X
Jul 22 10:19:35 xxx /kernel.old: Timecounter i8254  frequency 1193182 Hz
Jul 22 10:19:35 xxx /kernel.old: Timecounter TSC  frequency 348205021 Hz
Jul 22 10:19:35 xxx /kernel.old: CPU: Pentium II/Xeon/Celeron (348.21-MHz 
686-class CPU)

Re: System unique identifier.....

[Andrzej Bialecki]

On Wed, 21 Jul 1999, Mike Smith wrote:

   That's not quite true. It wouldn't be too hard to modify existant files,
   but writing new ones/truncating would take a lot of work. It's still not
   a great idea to try to use a file on the FS for storage of persistent
   data. Wouldn't it be possible to have the kernel itself read in persistent
   data (in some form such as getenv?) to be written to disk? That way, the
   boot loader could pass it easily, and not have to worry about storage.
  
  This may sound like a heresy to you, but... Why don't use the Forth blocks
  for that?
 
 For what?  Saving parametric data?  That was always the plan, but the 
 last thing I think anyone wants to do is rewrite the ffs code in Forth.

Ugh.. No, of course not. The former, i.e. saving parameters. I'm still
sane, you know... :-)


Andrzej Bialecki

//  ab...@webgiro.com WebGiro AB, Sweden (http://www.webgiro.com)
// ---
// -- FreeBSD: The Power to Serve. http://www.freebsd.org 
// --- Small  Embedded FreeBSD: http://www.freebsd.org/~picobsd/ 



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

Re: IDE breakage

[Dag-Erling Smorgrav]

Dag-Erling Smorgrav d...@yes.no writes:
 I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
 on recent versions of -STABLE. Here's an excerpt from messages; kernel
 #3 is a recent -STABLE (yesterday's sources), while kernel #2 is
 3.2-RELEASE. The config file for both is identical.

A brand new kernel (from the same sources and config, but built in a
clean build directory) produces the following:

Jul 22 11:29:17 irc /kernel: Copyright (c) 1992-1999 FreeBSD Inc.
Jul 22 11:29:17 irc /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 22 11:29:17 irc /kernel: The Regents of the University of California. All 
rights reserved.
Jul 22 11:29:17 irc /kernel: FreeBSD 3.2-STABLE #0: Thu Jul 22 10:54:31 CEST 
1999
Jul 22 11:29:17 irc /kernel: r...@xxx.x.xx:/usr/src/sys/compile/X
Jul 22 11:29:17 irc /kernel: Timecounter i8254  frequency 1193182 Hz
Jul 22 11:29:17 irc /kernel: Timecounter TSC  frequency 348204679 Hz
Jul 22 11:29:17 irc /kernel: CPU: Pentium II/Xeon/Celeron (348.20-MHz 686-class 
CPU)
Jul 22 11:29:17 irc /kernel: Origin = GenuineIntel  Id = 0x652  Stepping = 2
Jul 22 11:29:17 irc /kernel: 
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
Jul 22 11:29:17 irc /kernel: real memory  = 134217728 (131072K bytes)
Jul 22 11:29:17 irc /kernel: avail memory = 127774720 (124780K bytes)
Jul 22 11:29:17 irc /kernel: Preloaded elf kernel kernel at 0xc023c000.
Jul 22 11:29:17 irc /kernel: Probing for devices on PCI bus 0:
Jul 22 11:29:17 irc /kernel: chip0: Intel 82443BX host to PCI bridge rev 0x02 
on pci0.0.0
Jul 22 11:29:17 irc /kernel: chip1: Intel 82443BX host to AGP bridge rev 0x02 
on pci0.1.0
Jul 22 11:29:17 irc /kernel: xl0: 3Com 3c905-TX Fast Etherlink XL rev 0x00 
int a irq 11 on pci0.13.0
Jul 22 11:29:17 irc /kernel: xl0: Ethernet address: 00:60:08:e8:6b:1d
Jul 22 11:29:17 irc /kernel: xl0: autoneg complete, link status good 
(full-duplex, 100Mbps)
Jul 22 11:29:17 irc /kernel: chip2: Intel 82371AB PCI to ISA bridge rev 0x02 
on pci0.20.0
Jul 22 11:29:17 irc /kernel: ide_pci0: Intel PIIX4 Bus-master IDE controller 
rev 0x01 on pci0.20.1
Jul 22 11:29:17 irc /kernel: chip3: Intel 82371AB Power management controller 
rev 0x02 on pci0.20.3
Jul 22 11:29:17 irc /kernel: Probing for devices on PCI bus 1:
Jul 22 11:29:17 irc /kernel: vga0: ATI model 4742 graphics accelerator rev 
0x5c int a irq 11 on pci1.0.0
Jul 22 11:29:17 irc /kernel: Probing for PnP devices:
Jul 22 11:29:17 irc /kernel: Probing for devices on the ISA bus:
Jul 22 11:29:17 irc /kernel: sc0 on isa
Jul 22 11:29:17 irc /kernel: sc0: VGA color 16 virtual consoles, flags=0x0
Jul 22 11:29:17 irc /kernel: atkbdc0 at 0x60-0x6f on motherboard
Jul 22 11:29:17 irc /kernel: atkbd0 irq 1 on isa
Jul 22 11:29:17 irc /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
Jul 22 11:29:17 irc /kernel: fdc0: FIFO enabled, 8 bytes threshold
Jul 22 11:29:17 irc /kernel: fd0: 1.44MB 3.5in
Jul 22 11:29:17 irc /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa
Jul 22 11:29:17 irc /kernel: wdc0: unit 0 (wd0): Maxtor 90640D4, DMA, 32-bit, 
multi-block-16
Jul 22 11:29:17 irc /kernel: wd0: 6149MB (12594960 sectors), 13328 cyls, 15 
heads, 63 S/T, 512 B/S
Jul 22 11:29:17 irc /kernel: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
Jul 22 11:29:17 irc /kernel: wdc1: unit 0 (atapi): CD-ROM CDU611-Q/2.0c, 
removable, accel, dma, iordis
Jul 22 11:29:17 irc /kernel: acd0: drive speed 1723KB/sec, 256KB cache
Jul 22 11:29:17 irc /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA
Jul 22 11:29:17 irc /kernel: acd0: Audio: play, 16 volume levels
Jul 22 11:29:17 irc /kernel: acd0: Mechanism: ejectable tray
Jul 22 11:29:17 irc /kernel: acd0: Medium: no/blank disc inside, unlocked
Jul 22 11:29:17 irc /kernel: npx0 on motherboard
Jul 22 11:29:17 irc /kernel: npx0: INT 16 interface
Jul 22 11:29:17 irc /kernel: vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on 
isa
Jul 22 11:29:17 irc /kernel: IP packet filtering initialized, divert disabled, 
rule-based forwarding disabled, unlimited logging
Jul 22 11:29:17 irc /kernel: DUMMYNET initialized (990504)
Jul 22 11:29:17 irc /kernel: changing root device to wd0s1a
Jul 22 11:29:17 irc /kernel: wd0: DMA failure, DMA status 5active
Jul 22 11:29:17 irc last message repeated 17 times
Jul 22 11:29:17 irc /kernel: wd0: DMA failure, DMA status 7error,active
Jul 22 11:29:17 irc /kernel: 
Jul 22 11:29:17 irc /kernel: 
Jul 22 11:29:17 irc /kernel: Fatal trap 12: page fault while in kernel mode
Jul 22 11:29:17 irc /kernel: fault virtual address = 0x44
Jul 22 11:29:17 irc /kernel: fault code= supervisor read, page not 
present
Jul 22 11:29:17 irc /kernel: instruction pointer   = 0x8:0xc01813ca
Jul 22 11:29:17 irc /kernel: stack pointer = 0x10:0xc9599b84
Jul 22 11:29:17 irc /kernel: frame pointer = 0x10:0xc9599bf4
Jul 22 11:29:17 irc /kernel: code segment  = base 0x0, limit 0xf, 
type 0x1b
Jul 22 11:29:17 irc /kernel: = DPL 0, pres 

Re: PAM LDAP in FreeBSD

[Max Khon]

hi, there!

On Fri, 16 Jul 1999, Oscar Bonilla wrote:

 Following up on my own post:
 
 For LDAP to be seamlessly integrated into the system some of the libraries
 have to be changed. Specifically the ones dealing with /etc/passwd and
 user information. 
 
 I've decided the best way to do this is to do what's done with NIS.
 Basically handle the case where the user is not available in the local
 databases. 
 
 the idea is to have an entry in the /etc/passwd enabling LDAP lookups.
 the Entry would be of the form
 
 ldap:*:389:389:o=My Organization, c=BR:uid:ldap.myorg.com
^^^ ^^^ ^^^ ^^
 |  |||   
portbase dnattr LDAP Server
 
 This comes ftom a pam_ldap module I got from Pedro A M Vazquez 
 vazq...@iqm.unicamp.br
 
 I'll change all of the function in lib/libc/gen/getpwent.c to handle this
 special case.
 
 The only problem is that openldap has to be integrated on the base system
 for this to compile... can I safely copy it to /usr/src/contrib?
 
 How do I submit this after it's done? anyone cares about ldap :)?

aargh. looks horrible to me. better try to implement NSS

/fjoe



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

Re: PAM LDAP in FreeBSD, and userfs too.

[Max Khon]

hi, there!

On Mon, 19 Jul 1999, Dominic Mitchell wrote:

 On Mon, Jul 19, 1999 at 12:29:48PM -0400, David E. Cross wrote:
  I thought now would be a good time to chime in on some of my wild schemes...
  
  The reason I am interested in 'userfs' is to enable me to write a version
  of 'nsd'.

[...]
 
 Lovely.  Sounds like a much better way to do the Solaris/Linux (and
 NetBSD?) /etc/nsswitch.conf stuff.  On Solaris at least, this is
 implemented using masses of weird shared objects...

PAM is also using masses of weird shared objects but nevertheless it's
quite usable

/fjoe



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

Re: IDE breakage

[Jos Backus]

Fwiw, I sometimes (mostly after a warm reboot) see:

mmm dd hh:mm:ss hal /kernel: ata1: unwanted interrupt 1 status = ff

immediately followed by a similar Fatal trap 12: page fault while in kernel
mode. Last time, the current process was swapper. Next time it happens I'll
write down the details.

Power-cycling works around the problem. A kernel built on July 7th does not
exhibit this behavior afaIct.

-- 
Jos Backus  _/ _/_/_/  Reliability means never
   _/ _/   _/   having to say you're sorry.
  _/ _/_/_/ -- D. J. Bernstein
 _/  _/ _/_/
jos.bac...@nl.origin-it.com  _/_/  _/_/_/  use Std::Disclaimer;


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

Re: PAM LDAP in FreeBSD, and userfs too.

[Dominic Mitchell]

On Thu, Jul 22, 1999 at 04:59:59PM +0700, Max Khon wrote:
 On Mon, 19 Jul 1999, Dominic Mitchell wrote:
  Lovely.  Sounds like a much better way to do the Solaris/Linux (and
  NetBSD?) /etc/nsswitch.conf stuff.  On Solaris at least, this is
  implemented using masses of weird shared objects...
 
 PAM is also using masses of weird shared objects but nevertheless it's
 quite usable

By statically linked binaries?
-- 
Dom Mitchell -- Palmer  Harvey McLane -- Unix Systems Administrator

In Mountain View did Larry Wall
Sedately launch a quiet plea:
That DOS, the ancient system, shall
On boxes pleasureless to all
Run Perl though lack they C.
-- 
**
This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they   
are addressed. If you have received this email in error please notify 
the system manager.

This footnote also confirms that this email message has been swept by 
MIMEsweeper for the presence of computer viruses.
**


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

NSS project

[Max Khon]

hi, there!

So what is the official status of NSS impl.?
Are there any takers?

/fjoe



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

Re: PAM LDAP in FreeBSD

[Max Khon]

hi, there!

On Thu, 22 Jul 1999, Daniel C. Sobral wrote:

 I perceive here an unfair biasing toward nss. Someone mentioned
 defining where to get the passwords from based on the login class.
 This is a very interesting option, that doesn't seem to be well
 served by nss.

there is already nss_ldap module for NSS to get all the stuff from LDAP
that's why NSS is better (for me) than other solutions

/fjoe



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

Re: PAM LDAP in FreeBSD

[Max Khon]

hi, there!

On Tue, 20 Jul 1999, Oscar Bonilla wrote:

  It looks like we've got some good concurrent projects happening at the
  moment - markm and co working on PAM, the nsswitch.conf project you're
  talking about, and the stuff I'm working on with modularizing crypt() and
  supporting per-login class password hashes (I've rewritten the library
  since I last posted about it and expect to have my code cleaned up by
  tomorrow night for another snapshot).
  
  The thing to make sure is that we don't tread on each other's toes, and
  basically that we look for the big picture and how all these projects fit
  together.
  
 
 Ok, this is my understanding of the thing:
 
 There are two parts to the problem, first we need a way to tell the
 system where to get its information from (call them databases, tables
 or whatever). This should be done a la solaris, with
 /etc/nsswitch.conf telling if this is to be fetched from files, ldap,
 nis, dns, etc.
 
 We need to recode all the programs that obtain this info directly from
 files to get it from a library (this would be nsd). And then code the
 library itself to get the info from /etc/nsswitch.conf

You misunderstand the main goal of NSS -- you need not recode anything --
NSS substitutes getxxxbyzzz libc functions

 Second, we need a way to authenticate the user... this is what PAM does.
 What would need to be done is change the pam modules to make them
 nsd aware (i.e. where should I get the passwd from?) or make them
 /etc/auth.conf aware? this is the confusing part... 
 
 where does crypt fit into this? crypt would get what from /etc/login.conf?

go to http://www.padl.com and read about LDAP + NSS and PAM deployment
schemes

/fjoe



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

Re: PAM LDAP in FreeBSD

[Max Khon]

hi, there!

On Mon, 19 Jul 1999, Oscar Bonilla wrote:

 On Mon, Jul 19, 1999 at 04:51:12PM -0600, Wes Peters wrote:
  The implementation details are as unimportant as ever: they have to work
  and be maintainable.  Following prior art remains a good idea; the Solaris
  name service switch implementation is a good starting point to consider.
  
 
 I agree. In solaris (and linux by the way) all you do is set
 passwdldap files
 in /etc/nsswitch.conf
 and that's it.
 
 I had started to write the code to mess with libc to fix the getpwent stuff,
 but a better solution is to port the nsswitch stuff from linux (i don't have
 source from solaris :)

glibc NSS impl. is GPL-poisoned and the author of that impl. (sorry, do
not even remember his name) does not want to distribute it under BSD-style
copyright. better try to port NetBSD impl.

/fjoe



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

Re: IDE breakage

[sthaug]

 I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
 on recent versions of -STABLE. Here's an excerpt from messages; kernel
 #3 is a recent -STABLE (yesterday's sources), while kernel #2 is
 3.2-RELEASE. The config file for both is identical.

I can confirm problems with DMA from IDE disks in -STABLE. The problems
seem to have been introduced in

$Id: ide_pci.c,v 1.28.2.1 1999/07/20 22:58:20 julian Exp $

And the effect for me is that the system stops in singleuser mode, with
a DMA failure message. This is on a 440BX/PII-350 system.

Reverting to 1.28 (from 17. January 1999) fixes the problems.

Please back out 1.28.2.1, at least in -STABLE.

Steinar Haug, Nethelp consulting, sth...@nethelp.no


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

RE: 1373 sound chip

[Brian McGroarty]

There's a patch for the 1371 floating around that seems to work for the 1373
as well.

Search the archive of FreeBSD-questions for 1371.

Last I saw, the search page was still confused - you need to put 1371 in
the web search field at the top, but still click the mailing list search
button down below.



 -Original Message-
From: Vince Vielhaber [mailto:v...@michvhf.com]
Sent: Wednesday, July 21, 1999 6:54 PM
To: Brian McGroarty; freebsd-hardware; hackers
Subject: 1373 sound chip

I sent this to multimedia about a week ago and didn't get a response
so I'm trying it here [hackers  hardware] (with minor mods):


I'm setting up a new machine that has onboard sound in the form of an
ES1373 Creative (Ensoniq, probably).  Visual config shows an unknown
device as ES0 and pcm0 doesn't find anything (tried various forms in
the kernel config for that one, the last one was/is:

device  pcm0

Is there any driver for this chip?  Under windows it uses the SoundBlaster
AudioPCI 64V driver.  So far I haven't found any specs on Creative's or
Ensoniq's website.  Can someone shed some light on possibly adapting the
pcm driver to this chip (like how to ID, etc.) ?


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

Re: Will FreeBSD ever see native IPv6 ??

[Jeroen Ruigrok/Asmodai]

* John Hay (j...@mikom.csir.co.za) [990722 11:55]:
 Are you just teasing or are you serious?

Well, according to what was discussed earlier he is serious. But from
prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
stuff is only available for 3.x and below.

 I searched through their site (again), but except for being mentioned
 in their TODO for the past few months, I can't find anything that
 indicates that they or anyone else is working on it. They may be, but
 it isn't visible anywhere where I have looked. It would be nice if
 there was some place to follow their progress, because I'm also one
 of the people that would like to see IPv6 integrated into FreeBSD.

At the moment I am busy merging ipv6 from the 3.x kit into CURRENT, but
I have to see how to spread my time because I am also doing work on OVCS,
the PDP and some other projects. *bwerk* days are much too short...

If anyone else is having some spare time and willing to mess with the
kame 3.x kit cvsup stuff and CURRENT alongside me, please drop a mail.

'gards,

-- 
Jeroen Ruigrok van der Werven  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai
Network/Security SpecialistBSD: Technical excellence at its best
Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...?


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

Re: Will FreeBSD ever see native IPv6 ??

[itojun]

 Are you just teasing or are you serious?
Well, according to what was discussed earlier he is serious. But from
prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6
stuff is only available for 3.x and below.

We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE because we can't
base our IPv6 development on top of moving target.
FreeBSD 3.x-STABLE and 4.x are moving target (which moves very quickly)
and are unusable as base version for us - if we need to chase two
moving things (IPv6 and FreeBSD) we are doomed.

There has been NRL/INRIA/KAME integration work going on (basically
to avoid 4 BSDs and 3 IPv6 = 12 choices nightmare by making one
IPv6 stack).  There are, mainly, some (or too many) management
issues there.  We will be resolving management issues issue very soon,
hopefully by next week.
There's incomplete unified codebase there, which is not very
ready for public consumption.  Anyway please hold till the managment
issue is resolved, I believe I can give you a good news.

itojun


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

arpresolve: can't allocate llinfo for 255.255.255.0rt

[Jung, Michael]

I started getting these messages in the daily security output.

 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt
 arpresolve: can't allocate llinfo for 255.255.255.0rt

Upon inspection of the routing table I see this

(mi...@hobbs) /usr/home/mikej$netstat -r
Routing tables

Internet:
DestinationGatewayFlags Refs Use Netif
Expire
defaultc5500-rsm-vlan10   UGSc851872  tl0
localhost  localhost  UH  00  lo0
129.2.1/24 link#2 UC  00  de0
199.15/16  link#1 UC  00  tl0
199.15.32  c5500-rsm-vlan10   UGSc00  tl0 =
199.15.320xc70f22 255.255.255.0  UGSc0  185  tl0
c5500-rsm-vlan10   0:e0:34:a1:84:0UHLW50  tl0
1198
calvin 0:80:5f:cb:de:16   UHLW122152  tl0
 67

Can anyone explain how or where the 199.15.320xc70f22 entry could
have come from? I've been unable to remove it and don't have a window to
reload the server for several days.

Thanks--

Michael Jung(502) 315-2457 Voice
Senior Network Specialist   (502) 315-2815 Facsimile
National Processing Company, Inc.   mj...@npc.net
1231 Durrett Lane   MJ548
Louisville, KY 40285



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

Re: Anyone know how to dim and SGI flat panel?

[Mike Smith]

 
 :I'd bet it's done using DPMS.  See if the XFree86 4.x code can tell you 
 :anything about the monitor's capabilities.
 
 It's up?  Very cool, they actually put the prerelease up 2 days ago!
 47MB download, yummy!  DGA is going to be so cool.
 
 Unfortunately it looks like the DPMS stuff is still a bit primitive.
 Shoot.  I'll check it out, though.  The 3.3.3 I128 driver (that's
 the number 9 card) does not appear to support DPMS at all.
 
 SGI's site has a whitepaper on the flatpanel but it's a bit spare on
 control protocols.  They do say something about an I2C bus but I dunno
 whether that is what DPMS uses or not.

That is how I believe that DMPS communications are transported to the 
display.  Unfortunately, the DPMS specification is a VESA-proprietary 
document so you will have to either join the XFree86 project or sponsor 
FreeBSD as a VESA member (that would be nice 8).

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  msm...@freebsd.org
\\-- Joseph Merrick   \\  msm...@cdrom.com




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

Re: PAM LDAP in FreeBSD, and userfs too.

[Kris Kennaway]

On Thu, 22 Jul 1999, Dominic Mitchell wrote:

  PAM is also using masses of weird shared objects but nevertheless it's
  quite usable
 
 By statically linked binaries?

This is also an issue for a modularized libcrypt(). Peter Wemm suggested
having the library fork and exec a static helper binary module and
communicate via a pipe. So essentially you'd have two files for each
module, one which is a shared library and loaded via dlopen() and one
which is the same code with a small amount of wrapper (main() etc) to make
it into a standalone binary.

Solaris seem to be deprecating static libraries; you cannot have a fully
static libc and they have to resort to keeping (a copy of) libdl (and
presumably the run-time linker) under /etc so it's available on the root
partition.

Kris




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

Re: UDMA broken in -CURRENT/-STABLE?

[Kelly Yancey]

 I updated a system to -CURRENT last night and got a panic with alot of
 messages about UDMA failing (I don't have the exact messages, I can get
 them if need be).  I backed down the wdc0/wdc1 controller flags from
 0xa0ffa0ff to 0x0 and everything is happy.  I figured its -CURRENT, and
that
 is to be expected.

 I updated another system to -STABLE as of earlier today, and I got the
same
 thing... *eeak*.  again backing down from 0xa0ffa0ff to 0x0 works like a
 champ.

 The messages came right after init(8) started, and before any of the
 filesystems were mounted r/w (it happened most during the fsck).

 I hope someone else has seen this (sorry I am so skimpy on the details, I
 will be able to provide more soonish.)

 uname -a:
 FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21
15:17:27 EDT 1999 r...@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX  i386

 dmesg:
 [...]
 ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1
 [...]

  I've seen the exact same problem on -stable builds since the 20th (I don't
know how much further back it went than that). I'm not in front of my
computer right now, but the errors were all DMA errors (status ready as I
recall). I have a PIIX4 controller. I played around with it a bit and found
that simply turning of the DMA hint in the flags cleared the problems (my
flags went from f0fff0ff to d0ffd0ff I believe). Actually, once I
accidentilly left the flags with DMA enabled on only 1 drive and only
received DMA errons on that single drive.
  I don't know if this is related, but my atapi CD (Acer 40x) still reports
DMA (apparently not affected by the wdc flags), but won't play audio CDs
from most CD apps (apparently the ones which use the CDIOCPLAYWMF ioctl to
play audio). This has been going on for longer, but I don't know if it was
maybe a precursor to the UDMA bug?

  Kelly
 ~kby...@posi.net~
  FreeBSD - The Power To Serve - http://www.freebsd.org/
  Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD



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

FreeBSD: the stealth OS?

[Len Conrad]

Cool with the geeks beecause it's unknown.

http://www.msnbc.com/news/292376.asp

Len 




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

Re: PAM LDAP in FreeBSD

[Kris Kennaway]

On Thu, 22 Jul 1999, Daniel C. Sobral wrote:

 Oscar Bonilla wrote:
  
  There are three parts to the problem:
  
  1. Where do we get the databases from? I mean, where do we get passwd, 
  group,
 hosts, ethers, etc from.
  
 This should be handled by a name service switch a la solaris. Basically
 we want to be able to tell the system for each individual database where
 to get the stuff from. We can add entries for each database in the 
  system.
 
 I perceive here an unfair biasing toward nss. Someone mentioned
 defining where to get the passwords from based on the login class.

Not quite, if you're talking about me - I use login.conf to tell passwd(1)
what hash algorithm to use for new account passwords.

login.conf isn't applicable for where to get passwords from; you need to
already know the user name (and presumably the entire struct passwd) to
know what login class they're in.

What does make sense is to be able to configure where getpwent() and
friends go to get the struct passwd in the first place; whether from
/etc/[s]pwd.db, a LDAP server, etc. This could either be done by teaching
getpwent() how to interface with more and more backends, or by a config
file which (effectively) swaps between entirely different getpwent()
functions (one which talks to spwd.db, one which talks LDAP, etc). This is
the nsswitch.conf route.

Kris

 This is a very interesting option, that doesn't seem to be well
 served by nss.
 
 --
 Daniel C. Sobral  (8-DCS)
 d...@newsguy.com
 d...@freebsd.org



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

Filesystem question...

[David E. Cross]

Since I am planning on writing userfs in order to impliment 'nsd' (and
some other ideas I have hatching too :).  I need to know how filesystem
accesses work.  Can they be queued up, and responded to out of order?

For example... I have a request come in (via the filesystem), that request
is going to take awhile, so I thread off a handler.  Now another filesystem
request comes in, will that be delivered to me, or will that block waiting
for the previous request to be honored first?

--
David Cross   | email: cro...@cs.rpi.edu 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself.  | WinNT:Linux::Linux:FreeBSD


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

Re: PAM LDAP in FreeBSD

[Kris Kennaway]

On Wed, 21 Jul 1999, Oscar Bonilla wrote:

 Ok, here goes my understanding of how things should be, please correct me
 if i'm wrong.
 
 There are three parts to the problem: 
 
 1. Where do we get the databases from? I mean, where do we get passwd, group,
hosts, ethers, etc from.
 
This should be handled by a name service switch a la solaris. Basically
we want to be able to tell the system for each individual database where
to get the stuff from. We can add entries for each database in the system.
 
 2. How to authorize the user? I mean, what sort of authentication should we
use to decide if the user should be allowed in. 
 
This should be handled by PAM.

PAM also does other functions; session management, password management,
etc.

 
 3. What password hash should we use when we have the username and the
password hash?
 
This should be handled by the new modularized crypt.
 
 Do we want to be able to tell the system where to get its pam.conf and
 login.conf from? This would mean having a pam.conf and login.conf entry
 in nsswitch.conf.

Hmm. I don't know that this much would be useful.

 Can we make a list of stuff that needs to be done to make this possible?
 Something like a tasklist would be good.
 
 a) design and implement a name service switch.
 b) make libc aware of the name service switch.
 c) ???

I think we should look at what NetBSD is doing and join with their
efforts. There's no sense in reinventing the wheel.

I'm just running my libcrypt through a make world to make sure it's okay -
once it's done I'll post the new source code snapshot for comment and
testing.

Kris

 -Oscar
 
 -- 
 For PGP Public Key: finger oboni...@fisicc-ufm.edu
 

--
  The Feynman Problem-Solving Algorithm:
(1) Write down the problem
(2) Think real hard
(3) Write down the answer
--



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

Re: any docs on how to use bus_dma_tag_create e.a. ?

[Justin T. Gibbs]

/*lowaddr*/BUS_SPACE_MAXADDR_32BIT,
/*highaddr*/BUS_SPACE_MAXADDR,
 
 low and high address of the region that the DMA engine cannot access.

Meaning e.g. the 16Mbyte barrier that ISA DMA has? 
For PCI this would be a 4Gb range(?).

The range could be much larger than 4GB.  Remember this is a range the
device *cannot* access, not a range it can access.  So, the beginning
of the range for an ISA device would be BUS_SPACE_MAXADDR_24BIT and the
hight address would be BUS_SPACE_MAXADDR.  Depending on the platform
or configuration of the machine, the high address could be larger than
a 32bit quantity.

/*maxsize*/MAXBSIZE,
 
 Maximum DMA transfer size.
 
/*nsegments*/AHC_NSEG,
 
 Maximum number of discontinuities in the mapped region.

Eh.. ? 

/*maxsegsz*/AHC_MAXTRANSFER_SIZE,
 
 Maximum size of a segment.  maxsize = nsegments * maxsegsz.

Eh.. ?

Many DMA engines have S/G capability and so can perform a single DMA that
spans multiple segments of bus space contiguous data.  By setting these
parameters, the bus_dmamap_load function can determine how best to map
your transfer into bus space and will return to you an array of segments
to program into your DMA hardware.

 You should use the new API if possible.

That is what I'm planning to do. The amount of sample code in the various
drivers is rather limited as most drivers use the old code.

It seems that its mostly confined to the SCSI code, but hopefully that will
change over time.

So I hope you don't mind me asking some more questions,

Not a problem.

--
Justin



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

Re: Filesystem question...

[Tiny Non Cats]

On Thu, Jul 22, 1999 at 10:06:04AM -0400 David E. Cross said:
 Since I am planning on writing userfs in order to impliment 'nsd' (and

This may be completely useless, because I've not been following what you want
to do with 'nsd', but you may find

   http://www.cs.columbia.edu/~ezk/research/security/index.html

interesting. It's a description of 'WrapFS', written by Erik Zadok. It's a 
stackable filesystem template written as a kernel module, and can be extended 
to 
do all sorts of stuff with relative ease, apparently.

Cian

-- 
What think ye of Christ? Whose son is he? Will you, like Peter, boldly say: 

   Who? 



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

Re: PAM LDAP in FreeBSD, and userfs too.

[Dominic Mitchell]

On Thu, Jul 22, 1999 at 11:19:35PM +0930, Kris Kennaway wrote:
 On Thu, 22 Jul 1999, Dominic Mitchell wrote:
 
   PAM is also using masses of weird shared objects but nevertheless it's
   quite usable
  
  By statically linked binaries?
 
 This is also an issue for a modularized libcrypt(). Peter Wemm suggested
 having the library fork and exec a static helper binary module and
 communicate via a pipe. So essentially you'd have two files for each
 module, one which is a shared library and loaded via dlopen() and one
 which is the same code with a small amount of wrapper (main() etc) to make
 it into a standalone binary.

This is starting to get icky.  This is also where the earlier idea of a
userspace filesystem would probably fare better, in terms of both
performance and simplicity.

 Solaris seem to be deprecating static libraries; you cannot have a fully
 static libc and they have to resort to keeping (a copy of) libdl (and
 presumably the run-time linker) under /etc so it's available on the root
 partition.

Solaris hasn't supported static linking for some time.  If you have a
look at Casper Dik's FAQ, it goes into more detail.  They do keep stuff
on the root partition:

admin# ls -l /etc/lib
total 644
-rwxr-xr-x   1 bin  bin   155060 Jul  1  1998 ld.so.1*
-rwxr-xr-x   1 bin  bin 4284 Jul  1  1998 libdl.so.1*
-rwxr-xr-x   1 bin  bin25468 Jul 16  1997 nss_files.so.1*
lrwxrwxrwx   1 root root  17 Sep 14  1998 pam_authen.so - 
./pam_authen.so.1*
-rwxr-xr-x   1 root sys14516 Jul 16  1997 pam_authen.so.1*
lrwxrwxrwx   1 root root  16 Sep 14  1998 pam_entry.so - 
./pam_entry.so.1*
-rwxr-xr-x   1 root sys11540 Jul 16  1997 pam_entry.so.1*
lrwxrwxrwx   1 root root  17 Sep 14  1998 pam_extern.so - 
./pam_extern.so.1*
-rwxr-xr-x   1 root sys11044 Jul 16  1997 pam_extern.so.1*
lrwxrwxrwx   1 root root  16 Sep 14  1998 pam_pwmgt.so - 
./pam_pwmgt.so.1*
-rwxr-xr-x   1 root sys85764 Jul 16  1997 pam_pwmgt.so.1*
lrwxrwxrwx   1 root root  18 Sep 14  1998 pam_session.so - 
./pam_session.so.1*
-rwxr-xr-x   1 root sys 4748 Jul 16  1997 pam_session.so.1*

-- 
Dom Mitchell -- Palmer  Harvey McLane -- Unix Systems Administrator

In Mountain View did Larry Wall
Sedately launch a quiet plea:
That DOS, the ancient system, shall
On boxes pleasureless to all
Run Perl though lack they C.
-- 
**
This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they   
are addressed. If you have received this email in error please notify 
the system manager.

This footnote also confirms that this email message has been swept by 
MIMEsweeper for the presence of computer viruses.
**


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

Re: [FreeBSD-users-jp 44304] de0 is availa ble or not? (re:) using nic de0 oｆ peaple much in ja pan

[jir ですうう]

ji です。

 高橋です。
takahashi san


 動かなかった環境
no move envilonment
 ・10baseのバカHUB
 ・接続相手はNE2000互換の10baseなNIC
 ・ifconfigでmediaを指定しても de0: link down: cable problem? がで
す。

good move envilonment
 動いた環境
 ・10/100のデュアルスピードHUB(Autonegotiation有)
 ・接続相手はVIA VT86C100Aチップを使ったNIC
 ・ifconfigでmediaは特に指定せず

question
   10/100のデュアルスピードHUB(Autonegotiation有)
   でなく、１０の場合はどうすればいいのでしょうか？
   kernel　config　とか？
   それとも, それはいじらずですか？
how config Kernel config?


 どうも動いた環境の Autonegotiation有 がくせ者みたいです。
 過去のusers-jpやnet-jpなどのメールを21143で検索してもやはり
 メディアの指定をすると動いた方が多いようです。
 # 21143のdata sheet昔はDECのWeb siteにあったのになくなってる...
 # だれか持ってないかなぁ(ぼそ

 ---
 Daisuke Takahashi / $b$7$+$7$F2K$G$9$+!)




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