From owner-freebsd-stable Sun Jan 13 4:53:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cyberland.fi (mail.cyberland.fi [62.142.63.103]) by hub.freebsd.org (Postfix) with SMTP id C3E4837B405 for ; Sun, 13 Jan 2002 04:53:10 -0800 (PST) Received: (qmail 56240 invoked from network); 13 Jan 2002 13:06:20 -0000 Received: from unknown (HELO ryssa) (62.142.63.76) by 0 with SMTP; 13 Jan 2002 13:06:20 -0000 Subject: Re: mount_null problems From: Edvard Fagerholm To: Tod McQuillin Cc: freebsd-stable@freebsd.org In-Reply-To: <20020113104154.G78412-100000@glass.pun-pun.prv> References: <20020113104154.G78412-100000@glass.pun-pun.prv> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.99.0 (Preview Release) Date: 13 Jan 2002 10:52:49 -0200 Message-Id: <1010926373.4008.0.camel@ryssa.cyberland.fi> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yeah, I never looked at the man page for known bugs. After seeing so many people advertise it on -questions and in several other places I thought it would have been stable. Well, I was wrong, now I know better. I already got one suggestion as a solution to this problem which is to locally export the filesystem with NFS and mount it from the localhost i.e. "loopback" NFS. This seems stable and I haven't been able to crash anything using it. And it really doesn't hurt in any way either as I'm already running portmapper etc. on the host. Another suggestion was automounter. I've never really used it in practice and it seems to be a solution to limit the amount of mounts needed, as I don't need to permanently mount each directory, only when they are actually needed. Anyways, thanks for the replies. - Edvard On Sun, 2002-01-13 at 03:45, Tod McQuillin wrote: > On 12 Jan 2002, Edvard Fagerholm wrote: > > > Any ideas, why this doesn't work or why it's stupid or impossible to do > > I would love to use mount_null too because it seems like a good solution > for a number of problems. > > However, did you read the BUGS section of the man page? > > BUGS > THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T > WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. > USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. > > This code also needs an owner in order to be less dangerous - > serious hackers can apply by sending mail to > and announcing their intent to take it over. > > I crashed FreeBSD quite a few times trying to use nullfs. Now I know > better. > -- > Tod McQuillin > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 13 5:52:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id C1A4337B416 for ; Sun, 13 Jan 2002 05:52:52 -0800 (PST) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 3.33 #1) id 16Pl41-00087C-00; Sun, 13 Jan 2002 13:52:45 +0000 To: roelof@nisser.com, stephen@math.missouri.edu Subject: Re: Portupgrade Utility Cc: beholder@unios.dhs.org, nunotex@pt-quorum.com, stable@FreeBSD.ORG In-Reply-To: <3C40B786.5020105@nisser.com> Message-Id: From: Pete French Date: Sun, 13 Jan 2002 13:52:45 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Ruby is a true blooded OO language in the spirit of Smalltalk. Perl > is not. Ruby invites to OO design, perl less so since it's been So would a rewrite in Objective-C be more viable since a) this is also an OO language in the spirit of smalltalk b) it is already part of the base system I also wrote a set of small foundation-kit type objects too which I would be happy to donate to this. -pcf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 13 6:24: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 2155037B400 for ; Sun, 13 Jan 2002 06:23:56 -0800 (PST) Received: from isc.org (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.6/8.11.2) with ESMTP id g0DENGs00755; Mon, 14 Jan 2002 01:23:17 +1100 (EST) (envelope-from marka@isc.org) Message-Id: <200201131423.g0DENGs00755@drugs.dv.isc.org> To: Kris Kennaway Cc: Mark_Andrews@isc.org, alexus , freebsd-stable@freebsd.org From: Mark.Andrews@isc.org Subject: Re: Fw: Cron /usr/local/bin/cvsup -g -h cvsup.FreeBSD.org /usr/share/examples/cvsup/stable-supfile >/dev/null;cd /usr/src;make buildworld >/dev/null;make buildkernel >/dev/null In-reply-to: Your message of "Sat, 12 Jan 2002 22:03:11 -0800." <20020112220311.A923@xor.obsecurity.org> Date: Mon, 14 Jan 2002 01:23:16 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Sun, Jan 13, 2002 at 02:36:37PM +1100, Mark.Andrews@isc.org wrote: > > > > Yeah, but they're not problems the end user needs to worry about, in > > > that they're perfectly normal when compiling FreeBSD. > >=20 > > So you have performed the call analysis to verify that there > > is not a bounds write violation? > >=20 > > The program is buggy. If someone submitted a patch for BIND > > which generated this error I would not accept it as it is. > > I'd either send it back to them to correct or fix the calling > > sequence myself. > > I think you're missing my point. Yes, they're probably pieces of code > which should be fixed by the developers, but they're not abnormal > messages from the FreeBSD build process (since they're there all the > time) which the end user needs to take action over. > > Kris > Except not all of them are there all the time. There are changes to the code base and these changes can generate new warnings that happen to be over looked because of all the other warnings that are being ignored. The problem is to be able to tell which warning falls into which category. It it the same old warning or is it a new one that really should be addressed. Mark -- Mark Andrews, Internet Software Consortium 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@isc.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 13 7:26:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (pcp419987pcs.martnz01.ga.comcast.net [68.47.18.240]) by hub.freebsd.org (Postfix) with ESMTP id 12EA137B41A for ; Sun, 13 Jan 2002 07:26:29 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id g0DFQRC01620 for ; Sun, 13 Jan 2002 10:26:28 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C41A723.141910E8@vortex.wa4phy.net> Date: Sun, 13 Jan 2002 10:26:27 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-PRERELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: CLOSE_WAIT Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Have there been any changes made in the code that cause sockets to not close promptly after successful connection? I'm seeing the close_wait state for 15-20 minutes after closing a connection. OR, do I have something not turned on that used to be? 4.5-Pre of 23 Dec. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 13 7:36:49 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rebecca.tiscali.nl (rebecca.tiscali.nl [195.241.76.181]) by hub.freebsd.org (Postfix) with ESMTP id B84BD37B416 for ; Sun, 13 Jan 2002 07:36:46 -0800 (PST) Received: from monkey-online.net (unknown [195.241.113.9]) by rebecca.tiscali.nl (Postfix) with ESMTP id E00428A2F7C for ; Sun, 13 Jan 2002 16:36:31 +0100 (MET) Message-ID: <3C41A86E.9070909@monkey-online.net> Date: Sun, 13 Jan 2002 16:31:58 +0100 From: Eric Veraart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Filtering out problem with IPFilter Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I'm running a FreeBSD 4.4p2-RELEASE gateway here with IPFilter. I noticed that packets comming in from the network can be filtered and blocked, but once they are through I can't filter them with out rules. For example; I make a rule to pass in all traffic from xl0 to any Then I say all traffic out on ep0 is allowed, but on xl1 only a small range of addresses can go out. What I notice is that all computers on xl0 can go to an address behind xl1. The gateway itself can't go out on xl1. It almost seems as if gateway_enable="YES" in rc.conf lets packets bypass the out filter. I'm not using NAT. This is not a big problem, because I can manage everything through IN rules, it's still strange. Greetings, Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 13 8:12:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 0E3FF37B417 for ; Sun, 13 Jan 2002 08:12:36 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA04471; Sun, 13 Jan 2002 08:11:14 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda04459; Sun Jan 13 08:11:12 2002 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.6/8.9.1) id g0DGB7w07156; Sun, 13 Jan 2002 08:11:07 -0800 (PST) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdsd7154; Sun Jan 13 08:10:21 2002 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.6/8.9.1) id g0DGALu34418; Sun, 13 Jan 2002 08:10:21 -0800 (PST) Message-Id: <200201131610.g0DGALu34418@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpde34414; Sun Jan 13 08:10:02 2002 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Sam Drinkard Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CLOSE_WAIT In-reply-to: Your message of "Sun, 13 Jan 2002 10:26:27 EST." <3C41A723.141910E8@vortex.wa4phy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Jan 2002 08:10:02 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3C41A723.141910E8@vortex.wa4phy.net>, Sam Drinkard writes: > Have there been any changes made in the code that cause sockets to not > close promptly after successful connection? I'm seeing the close_wait > state for 15-20 minutes after closing a connection. OR, do I have > something not turned on that used to be? 4.5-Pre of 23 Dec. Let me guess, HTTP, right? Try shutting down your browser, the CLOSE_WAIT's will disappear. If you're running a web server you'll see the corresponding FIN_WAIT_2's will also disappear on the server machine when you shut down your browser. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 13 8:32:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (pcp419987pcs.martnz01.ga.comcast.net [68.47.18.240]) by hub.freebsd.org (Postfix) with ESMTP id 3C11337B404 for ; Sun, 13 Jan 2002 08:32:29 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id g0DGW1C01765; Sun, 13 Jan 2002 11:32:01 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C41B681.D00271B4@vortex.wa4phy.net> Date: Sun, 13 Jan 2002 11:32:01 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-PRERELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@freebsd.org Subject: Re: CLOSE_WAIT References: <200201131610.g0DGALu34418@cwsys.cwsent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yep.. at first, I thought it was doing it with ftp and smtp, but see they disappear rather quickly.. Dunno why I didn't think of the browser... Yep.. problem solved! Thanks.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 13 10:51:45 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pkl.net (spoon.pkl.net [212.111.57.14]) by hub.freebsd.org (Postfix) with ESMTP id C0F4A37B405 for ; Sun, 13 Jan 2002 10:51:29 -0800 (PST) Received: (from cez@localhost) by pkl.net (8.9.3/8.9.3) id SAA16540 for freebsd-stable@FreeBSD.ORG; Sun, 13 Jan 2002 18:51:28 GMT Date: Sun, 13 Jan 2002 18:48:13 +0000 From: Ceri Storey To: freebsd-stable@FreeBSD.ORG Subject: sysctl(2) related panic? Message-ID: <20020113184813.GD84064@mandelbrot.house> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.25i Status: RO Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, i'm running FreeBSD-stable on one of my machines here, and just a moment ago, it paniced, after me running a sysctl -a. The backtrace seems to indicated it paniced in the sysctl code, with a NULL oid. Here's the dmesg / gdb session, if you need anything else, just ask. -- Ceri Storey http://pkl.net/~cez/ vi(1)! postfix(7)! pie(5)! --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-PRERELEASE #6: Thu Dec 20 15:21:06 GMT 2001 cez@mandelbrot.house:/usr/obj/usr/src/sys/HILBERT Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (451.02-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 67043328 (65472K bytes) avail memory = 62103552 (60648K bytes) Preloaded elf kernel "kernel" at 0xc0322000. K6-family MTRR support enabled (2 registers) md0: Malloc disk Using $PIR table, 5 entries at 0xc00f7a50 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci0: at 2.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 rl0: port 0xdc00-0xdcff mem 0xdfffef00-0xdfffefff irq 9 at device 8.0 on pci0 rl0: Ethernet address: 00:c0:df:04:df:eb miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem 0xdfffee00-0xdfffeeff irq 12 at device 9.0 on pci0 dc0: Ethernet address: 00:a0:cc:65:5c:76 miibus1: on dc0 ukphy0: on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at 10.0 irq 11 atapci0: port 0xffa0-0xffaf irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 orm0:
Unrelated, but possibly = related:
I have a problem that all my Dell = 1550's crash when=20 they have 2GB of ram, but are stable with 1GB of ram, the exact same = kernel=20 works fine on a STL2 with 2GB of ram.
--Phil
------=_NextPart_000_0005_01C2BCA6.3190EE50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 11: 5:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from shikima.mine.nu (pc1-card4-0-cust77.cdf.cable.ntl.com [62.252.49.77]) by hub.freebsd.org (Postfix) with ESMTP id E4F8D37B400 for ; Tue, 15 Jan 2002 11:05:47 -0800 (PST) Received: from rasputin by shikima.mine.nu with local (Exim 3.33 #1) id 16QYx0-00005i-00 for stable@freebsd.org; Tue, 15 Jan 2002 19:08:50 +0000 Date: Tue, 15 Jan 2002 19:08:50 +0000 From: Rasputin To: stable@freebsd.org Subject: what's vnlru? Message-ID: <20020115190850.A338@shikima.mine.nu> Reply-To: Rasputin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Any ideas? rasputin@shikima rasputin]$ps ax|head PID TT STAT TIME COMMAND 0 ?? DLs 0:00.00 (swapper) 1 ?? ILs 0:00.01 /sbin/init -- 2 ?? DL 0:00.00 (pagedaemon) 3 ?? DL 0:00.00 (vmdaemon) 4 ?? DL 0:00.00 (bufdaemon) 5 ?? DL 0:00.00 (vnlru) 6 ?? DL 0:00.06 (syncer) 26 ?? ILs 0:00.28 mfs -o async /dev/ad0s4b /tmp (mount_mfs) 28 ?? Is 0:00.00 adjkerntz -i rasputin@shikima rasputin]$uname -a FreeBSD shikima.mine.nu 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #5: \ Tuesday January 8 12:03:05 GMT 2002 \ rasputin@shikima.mine.nu:/usr/obj/usr/src/sys/SHIKIMA i386 Looks like some kind of system process, doesn't seem to exist in the filesystem, manpages and mailing list archives see mot draw a blank.. I'm a bit worried. Answers on a postcard please... -- Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 11: 9:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 8114537B402 for ; Tue, 15 Jan 2002 11:09:50 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g0FJ9mL15207; Tue, 15 Jan 2002 20:09:48 +0100 (CET) (envelope-from wkb) Date: Tue, 15 Jan 2002 20:09:48 +0100 From: Wilko Bulte To: Rasputin Cc: stable@FreeBSD.ORG Subject: Re: what's vnlru? Message-ID: <20020115200948.A15193@freebie.xs4all.nl> References: <20020115190850.A338@shikima.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020115190850.A338@shikima.mine.nu>; from rasputin@submonkey.net on Tue, Jan 15, 2002 at 07:08:50PM +0000 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 15, 2002 at 07:08:50PM +0000, Rasputin wrote: > > Any ideas? No, but if it makes you feel better the Alpha has it too ;) ds10#ps ax PID TT STAT TIME COMMAND 0 ?? DLs 0:00.00 (swapper) 1 ?? SLs 0:00.13 (init) 2 ?? DL 0:00.00 (pagedaemon) 3 ?? DL 0:00.00 (vmdaemon) 4 ?? DL 0:00.02 (bufdaemon) 5 ?? DL 0:00.01 (vnlru) ds10#uname -a FreeBSD ds10.wbnet 4.5-RC FreeBSD 4.5-RC #4: Fri Jan 11 20:57:51 CET 2002 root@:/usr/obj/usr/src/sys/GENERIC alpha > > rasputin@shikima rasputin]$ps ax|head > PID TT STAT TIME COMMAND > 0 ?? DLs 0:00.00 (swapper) > 1 ?? ILs 0:00.01 /sbin/init -- > 2 ?? DL 0:00.00 (pagedaemon) > 3 ?? DL 0:00.00 (vmdaemon) > 4 ?? DL 0:00.00 (bufdaemon) > 5 ?? DL 0:00.00 (vnlru) > 6 ?? DL 0:00.06 (syncer) > 26 ?? ILs 0:00.28 mfs -o async /dev/ad0s4b /tmp (mount_mfs) > 28 ?? Is 0:00.00 adjkerntz -i > rasputin@shikima rasputin]$uname -a > FreeBSD shikima.mine.nu 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #5: \ > Tuesday January 8 12:03:05 GMT 2002 \ > rasputin@shikima.mine.nu:/usr/obj/usr/src/sys/SHIKIMA i386 > > Looks like some kind of system process, doesn't seem to exist > in the filesystem, manpages and mailing list archives see mot draw a blank.. > > I'm a bit worried. > > Answers on a postcard please... > > -- > Rasputin :: Jack of All Trades - Master of Nuns :: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---end of quoted text--- -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 11:18: 4 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 46C0237B417 for ; Tue, 15 Jan 2002 11:17:55 -0800 (PST) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id UAA06973; Tue, 15 Jan 2002 20:17:53 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Tue, 15 Jan 2002 20:17:52 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= To: Rasputin Cc: Subject: Re: what's vnlru? In-Reply-To: <20020115190850.A338@shikima.mine.nu> Message-ID: <20020115201637.T6012-100000@ramstind.gtf.ol.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 15 Jan 2002 19:08-0000, Rasputin wrote: > rasputin@shikima rasputin]$ps ax|head > PID TT STAT TIME COMMAND > 0 ?? DLs 0:00.00 (swapper) > 1 ?? ILs 0:00.01 /sbin/init -- > 2 ?? DL 0:00.00 (pagedaemon) > 3 ?? DL 0:00.00 (vmdaemon) > 4 ?? DL 0:00.00 (bufdaemon) > 5 ?? DL 0:00.00 (vnlru) > 6 ?? DL 0:00.06 (syncer) > 26 ?? ILs 0:00.28 mfs -o async /dev/ad0s4b /tmp (mount_mfs) > 28 ?? Is 0:00.00 adjkerntz -i > rasputin@shikima rasputin]$uname -a > FreeBSD shikima.mine.nu 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #5: \ > Tuesday January 8 12:03:05 GMT 2002 \ > rasputin@shikima.mine.nu:/usr/obj/usr/src/sys/SHIKIMA i386 It could be a vnode lru clock hand, like pagedaemon. -- ---------------------------------------------------------------------- Trond Endrestøl | trond@ramstind.gtf.ol.no Patron of The Art of Computer Programming| FreeBSD 3.5-S & Pine 4.33 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 11:18:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from shumai.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id A36A737B41A for ; Tue, 15 Jan 2002 11:18:24 -0800 (PST) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.6/8.11.6) with ESMTP id g0FJIKk82090; Tue, 15 Jan 2002 14:18:20 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Tue, 15 Jan 2002 14:18:20 -0500 (EST) From: Joe Clarke To: Wilko Bulte Cc: Rasputin , Subject: Re: what's vnlru? In-Reply-To: <20020115200948.A15193@freebie.xs4all.nl> Message-ID: <20020115141714.A80449-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 15 Jan 2002, Wilko Bulte wrote: > On Tue, Jan 15, 2002 at 07:08:50PM +0000, Rasputin wrote: > > > > Any ideas? > > No, but if it makes you feel better the Alpha has it too ;) This was added after Matt's recent stability commits. I believe it attemtps to recycle vnodes safely. Joe > > ds10#ps ax > PID TT STAT TIME COMMAND > 0 ?? DLs 0:00.00 (swapper) > 1 ?? SLs 0:00.13 (init) > 2 ?? DL 0:00.00 (pagedaemon) > 3 ?? DL 0:00.00 (vmdaemon) > 4 ?? DL 0:00.02 (bufdaemon) > 5 ?? DL 0:00.01 (vnlru) > > ds10#uname -a > FreeBSD ds10.wbnet 4.5-RC FreeBSD 4.5-RC #4: Fri Jan 11 20:57:51 CET 2002 > root@:/usr/obj/usr/src/sys/GENERIC alpha > > > > > rasputin@shikima rasputin]$ps ax|head > > PID TT STAT TIME COMMAND > > 0 ?? DLs 0:00.00 (swapper) > > 1 ?? ILs 0:00.01 /sbin/init -- > > 2 ?? DL 0:00.00 (pagedaemon) > > 3 ?? DL 0:00.00 (vmdaemon) > > 4 ?? DL 0:00.00 (bufdaemon) > > 5 ?? DL 0:00.00 (vnlru) > > 6 ?? DL 0:00.06 (syncer) > > 26 ?? ILs 0:00.28 mfs -o async /dev/ad0s4b /tmp (mount_mfs) > > 28 ?? Is 0:00.00 adjkerntz -i > > rasputin@shikima rasputin]$uname -a > > FreeBSD shikima.mine.nu 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #5: \ > > Tuesday January 8 12:03:05 GMT 2002 \ > > rasputin@shikima.mine.nu:/usr/obj/usr/src/sys/SHIKIMA i386 > > > > Looks like some kind of system process, doesn't seem to exist > > in the filesystem, manpages and mailing list archives see mot draw a blank.. > > > > I'm a bit worried. > > > > Answers on a postcard please... > > > > -- > > Rasputin :: Jack of All Trades - Master of Nuns :: > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > ---end of quoted text--- > > -- > | / o / /_ _ email: wilko@FreeBSD.org > |/|/ / / /( (_) Bulte Arnhem, the Netherlands > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 11:33: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 3B1D537B417 for ; Tue, 15 Jan 2002 11:32:55 -0800 (PST) Received: from colt.ncptiddische.net (ppp-30.wobline.de [212.68.69.30]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id g0FJWpw18350; Tue, 15 Jan 2002 20:32:51 +0100 Received: from tisys.org (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id g0FJYFX85894; Tue, 15 Jan 2002 20:34:16 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id g0FJXKC97921; Tue, 15 Jan 2002 20:33:20 +0100 (CET) (envelope-from nils) Date: Tue, 15 Jan 2002 20:32:44 +0100 From: Nils Holland To: Brady Montz Cc: freebsd-stable@FreeBSD.ORG Subject: Re: VIA crahes - solved (it seems)! Message-ID: <20020115203244.A97794@tisys.org> Mail-Followup-To: Brady Montz , freebsd-stable@FreeBSD.ORG References: <20020113224800.A82744@tisys.org> <3C42F7E1.3040508@magpage.com> <200201152200.g0FM0lT28843@mail.hydrologue.com> <20020115183113.A96245@tisys.org> <200201152314.g0FNEvn29022@mail.hydrologue.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200201152314.g0FNEvn29022@mail.hydrologue.com>; from bradym@mail.hydrologue.com on Tue, Jan 15, 2002 at 03:14:57PM -0800 X-Operating-System: FreeBSD jodie.ncptiddische.net 4.5-RC FreeBSD 4.5-RC X-Machine-Uptime: 8:17PM up 10:35, 2 users, load averages: 0.13, 0.03, 0.01 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 15, 2002 at 03:14:57PM -0800, Brady Montz stood up and spoke: > > One final note, I stress tested it on windows and linux specifically > looking for this problem, with no luck (or good luck, depending on > your point of view, it didn't crash though). And this machine ran > linux without a single crash for years before switching to > BSD. Crashes and all, I've grown fond of BSD and would rather not > switch back. A hardware glitch that is only tickled by one OS is > perfectly feasible. Yes, things are strange at time. As I said, my machine would crash as of last weeks sources, but with this Saturday's sources the problems are gone. The strange think is that according to my knowledge, no parts that could have had to do with the crash I was experiencing were modified in the new sources. So, sometimes it's better not to ask how a problem was solved - after all, a problem solving itself is probably the best thing that can happen to us ;-) > I've tested the RAM with the various ram testing software out there > (memtest86 being my favorite). What can I use to test the CPU or > motherboard? There may be software for that purpose, but from what I have heard such test software often misses problems that get triggered during real-world operations. There will also be hardware test equipment or testing mainboards and CPUs, but getting such stuff is probably not an option. So, what can be done? The best approach is probably swapping. Simply try the CPU in a different motherboard, exchange the RAM, exchange any expansion cards. Using such shuffeling, you should eventually be able to pin the problem down to a certain component, which is then the fualty one that needs replacing. Of course, this approach is sometimes a little hard. I remember when I first bought an Athlon Socket A System which had problems. I couldn't do much component swapping as the only other machines I had were K6-2 /Socket 7 based. Of course I could not swap boards and CPUs between the Socket A and Socket 7 systems ;-) Now that I'm at it, you may also want to set your BIOS settings to some conservative settings. I have seen a machine that behaves a little strange in terms of RAM timing settings. Specifically, if I set the DRAM Timing on that machine to normal, it won't boot at all and hangs during the POST. If I set it to "Turbo" it will boot, but crash under stress. The other tree settings "Medium", "Fast" and "SDRAM 8/10 ns" work totally fine, and the machine will not crash even if I let it repeatedly compile stuff overnight. Bottom line: If a system produces reproducible crashes, I'd first check the BIOS settings, set them to more "unoptimized" values and see what happens. If the problem persists, component swapping is probably the best method to track the problem down, though this may not always be easy due to the lack of exchange components at hand. Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 11:37: 7 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 68BFB37B400 for ; Tue, 15 Jan 2002 11:37:03 -0800 (PST) Received: from colt.ncptiddische.net (ppp-30.wobline.de [212.68.69.30]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id g0FJZjw18694; Tue, 15 Jan 2002 20:35:45 +0100 Received: from tisys.org (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id g0FJbAX85930; Tue, 15 Jan 2002 20:37:10 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id g0FJaGc97936; Tue, 15 Jan 2002 20:36:16 +0100 (CET) (envelope-from nils) Date: Tue, 15 Jan 2002 20:36:16 +0100 From: Nils Holland To: Wilko Bulte Cc: Rasputin , stable@FreeBSD.ORG Subject: Re: what's vnlru? Message-ID: <20020115203616.B97794@tisys.org> References: <20020115190850.A338@shikima.mine.nu> <20020115200948.A15193@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020115200948.A15193@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Tue, Jan 15, 2002 at 08:09:48PM +0100 X-Operating-System: FreeBSD jodie.ncptiddische.net 4.5-RC FreeBSD 4.5-RC X-Machine-Uptime: 8:17PM up 10:35, 2 users, load averages: 0.13, 0.03, 0.01 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 15, 2002 at 08:09:48PM +0100, Wilko Bulte stood up and spoke: > On Tue, Jan 15, 2002 at 07:08:50PM +0000, Rasputin wrote: > > > > Any ideas? > > No, but if it makes you feel better the Alpha has it too ;) If it helps, I guess vnlru started to appear at around christmas. I CVSupped, made world & kernel and noticed it. Though I don't know what it is, it seems to work fine ;-) Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 11:48:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [209.98.56.21]) by hub.freebsd.org (Postfix) with ESMTP id 449F637B416 for ; Tue, 15 Jan 2002 11:48:37 -0800 (PST) Received: from twinstar (twinstar.grasslake.net [192.168.30.2]) by accord.grasslake.net (8.11.6/8.11.6) with SMTP id g0FJcKm17794 for ; Tue, 15 Jan 2002 13:38:24 -0600 (CST) (envelope-from swb@grasslake.net) Message-ID: <009d01c19dfd$a434b950$021ea8c0@twinstar> From: "Shawn Barnhart" To: Subject: Group executable bit quit working? Date: Tue, 15 Jan 2002 13:48:40 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just upgraded three systems to 4.5 RC-6 this weekend and I seem to have lost the ability execute shell scripts or perl scripts that are group executable only. The scripts run otherwise if I make them executable by the owner, but having them g+x doesn't seem to be enough anymore. I have another system running 4.4 that also exhibits this behavior, so its confusing me. The scripts in question the 4.5-RC system have been running for years with permissions of 654. I'm wondering if some security or permissions change has occured in 4.5 that would affect this (seems odd, basic execution mode). Or am I dreaming, and being a member of a group *and* having a file group executable isn't enough to run it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 11:52: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id D611D37B402 for ; Tue, 15 Jan 2002 11:52:06 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id 568FB2D23; Tue, 15 Jan 2002 12:52:06 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id CDDA0108; Tue, 15 Jan 2002 12:52:05 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id LAA02454; Tue, 15 Jan 2002 11:52:05 -0800 (PST) Message-Id: <200201151952.LAA02454@mina.soco.agilent.com> To: Brady Montz Cc: freebsd-stable@FreeBSD.ORG Subject: Re: VIA crahes - solved (it seems)! Reply-To: Darryl Okahata In-Reply-To: Your message of "Tue, 15 Jan 2002 15:14:57 PST." <200201152314.g0FNEvn29022@mail.hydrologue.com> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Tue, 15 Jan 2002 11:52:04 -0800 From: Darryl Okahata Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Brady Montz wrote: > I've tested the RAM with the various ram testing software out there > (memtest86 being my favorite). What can I use to test the CPU or > motherboard? Note that software test programs like memtest86 will only catch gross memory errors. To catch the really nasty, intermittent ones, you need a specialized hardware RAM tester, which is probably not an option here. Also, I've looked over your postings for the past month, and I can't tell if you've tried the obvious: do you have a known good power supply? Some motherboards need really clean power, and AMD chips are power hogs. Borderline power supplies can easily cause the symptoms you're seeing. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 13:45:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.acns.ab.ca (h24-64-56-135.cg.shawcable.net [24.64.56.135]) by hub.freebsd.org (Postfix) with ESMTP id 3AD9737B417 for ; Tue, 15 Jan 2002 13:45:39 -0800 (PST) Received: from colnta.acns.ab.ca (colnta.acns.ab.ca [192.168.1.2]) by mail.acns.ab.ca (8.11.6/8.11.3) with ESMTP id g0FLjbI78022; Tue, 15 Jan 2002 14:45:37 -0700 (MST) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.11.6/8.11.3) id g0FLjbm12286; Tue, 15 Jan 2002 14:45:37 -0700 (MST) (envelope-from davidc) Date: Tue, 15 Jan 2002 14:45:37 -0700 From: Chad David To: Rasputin Cc: stable@FreeBSD.ORG Subject: Re: what's vnlru? Message-ID: <20020115144537.A12216@colnta.acns.ab.ca> Mail-Followup-To: Rasputin , stable@FreeBSD.ORG References: <20020115190850.A338@shikima.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020115190850.A338@shikima.mine.nu>; from rasputin@submonkey.net on Tue, Jan 15, 2002 at 07:08:50PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 15, 2002 at 07:08:50PM +0000, Rasputin wrote: > > Any ideas? > > I noticed it during shutdown a while back, and found this. revision 1.332 date: 2001/12/18 20:48:53; author: dillon; state: Exp; lines: +74 -8 This is a forward port of Peter's vlrureclaim() fix, with some minor mods by me to make it more efficient. The original code had serious balancing problems and could also deadlock easily. This code relegates the vnode reclamation to its own kproc and relaxes the vnode reclamation requirements to better maintain kern.maxvnodes. This code still doesn't balance as well as it could, but it does a much better job then the original code. Approved by: re@freebsd.org Obtained from: ps, peter, dillon MFS Assuming: Assuming no problems crop up in Yahoo testing MFC after: 7 days -- Chad David davidc@acns.ab.ca www.FreeBSD.org davidc@freebsd.org ACNS Inc. Calgary, Alberta Canada Fourthly, The constant breeders, beside the gain of eight shillings sterling per annum by the sale of their children, will be rid of the charge of maintaining them after the first year. - Johnathan Swift To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 13:57:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from web21208.mail.yahoo.com (web21208.mail.yahoo.com [216.136.175.166]) by hub.freebsd.org (Postfix) with SMTP id C08BB37B41A for ; Tue, 15 Jan 2002 13:57:50 -0800 (PST) Message-ID: <20020115215750.53211.qmail@web21208.mail.yahoo.com> Received: from [217.81.27.252] by web21208.mail.yahoo.com via HTTP; Tue, 15 Jan 2002 22:57:50 CET Date: Tue, 15 Jan 2002 22:57:50 +0100 (CET) From: =?iso-8859-1?q?Heinz=20Becker?= Subject: subscribe To: freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Ihre E-Mail noch individueller? - http://domains.yahoo.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 13:59:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (pcp419987pcs.martnz01.ga.comcast.net [68.47.18.240]) by hub.freebsd.org (Postfix) with ESMTP id E08C137B417 for ; Tue, 15 Jan 2002 13:59:44 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id g0FLxhC08875 for ; Tue, 15 Jan 2002 16:59:43 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C44A64F.67DCC61@vortex.wa4phy.net> Date: Tue, 15 Jan 2002 16:59:43 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-PRERELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Static files Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Most likely inappropriate subject line, but are there parts of the current -stable tree that are now NOT being worked on? Like the "base" FreeBSD system as a whole, no ports (or the port tree itself) but just a bare OS? Even though I've been following -stable, I gather things are still being debugged .. Which leads me to the real question, how often should one update from sources? I'm sure there are many a variable in that, but if something is working fine, why upgrade unless you happen to need the latest fix for a multi-frama-snickafoo-filter or whatever? Replys can be sent direct to keep the noise level down.. Thanks.. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 14: 2:39 2002 Delivered-To: freebsd-stable@freebsd.org Received: from web21203.mail.yahoo.com (web21203.mail.yahoo.com [216.136.130.22]) by hub.freebsd.org (Postfix) with SMTP id 0C74537B417 for ; Tue, 15 Jan 2002 14:02:38 -0800 (PST) Message-ID: <20020115220237.48644.qmail@web21203.mail.yahoo.com> Received: from [217.81.27.252] by web21203.mail.yahoo.com via HTTP; Tue, 15 Jan 2002 23:02:37 CET Date: Tue, 15 Jan 2002 23:02:37 +0100 (CET) From: =?iso-8859-1?q?Heinz=20Becker?= To: freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Ihre E-Mail noch individueller? - http://domains.yahoo.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 15:18:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from 141.com (mail1.141.com [65.168.139.2]) by hub.freebsd.org (Postfix) with ESMTP id 5259537B416 for ; Tue, 15 Jan 2002 15:17:46 -0800 (PST) Received: from 141.com [138.88.111.213] by 141.com with ESMTP (SMTPD32-7.05) id A8A9A2600FA; Tue, 15 Jan 2002 16:18:01 -0700 To: stable@FreeBSD.org Subject: Re:what's vnlru? Date: Tue, 15 Jan 2002 18:17:45 -0500 From: Andrew Lankford Message-Id: <200201151618468.SM01176@141.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My assumption is that it has something to do with ipfw. > >Any ideas? > >$ps ax|head > PID TT STAT TIME COMMAND > 0 ?? DLs 0:00.00 (swapper) > 1 ?? ILs 0:00.01 /sbin/init -- > 2 ?? DL 0:00.00 (pagedaemon) > 3 ?? DL 0:00.00 (vmdaemon) > 4 ?? DL 0:00.00 (bufdaemon) > 5 ?? DL 0:00.00 (vnlru) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 17: 1:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E2E4737B405 for ; Tue, 15 Jan 2002 17:01:08 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g0G117r64693; Tue, 15 Jan 2002 17:01:07 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Jan 2002 17:01:07 -0800 (PST) From: Matthew Dillon Message-Id: <200201160101.g0G117r64693@apollo.backplane.com> To: Andrew Lankford Cc: stable@FreeBSD.ORG Subject: Re:what's vnlru? References: <200201151618468.SM01176@141.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG vnlru is responsible for flushing and freeing vnodes when you hit the kern.maxvnodes limit. The history of this is: 4.4 and earlier vnodes were only freed if they had no cached pages. This could lead to a vnode blowout on machines with large amounts of ram accessing lots of small files. (the kern.maxvnodes limit was essentially ignored) 4.4-stable I introduced code to flush/reuse vnodes on the fly, but this lead to possible locking deadlocks. 4.5-* Peter introduced a separate kernel thread to deal with vnode flushing issues, 'vnlru', in order to fix the possible locking deadlocks. The on-the-fly code was changed to only be called from the kernel thread. This kernel thread will generally not be very active, even on a heavily loaded system. You have to have a lot of ram and be accessing tens of thousands of tiny files to activate the thread. -Matt Matthew Dillon :My assumption is that it has something to do with ipfw. : :> :>Any ideas? :> :>$ps ax|head :> PID TT STAT TIME COMMAND :> 0 ?? DLs 0:00.00 (swapper) :> 1 ?? ILs 0:00.01 /sbin/init -- :> 2 ?? DL 0:00.00 (pagedaemon) :> 3 ?? DL 0:00.00 (vmdaemon) :> 4 ?? DL 0:00.00 (bufdaemon) :> 5 ?? DL 0:00.00 (vnlru) : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 18:11:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 847D337B400 for ; Tue, 15 Jan 2002 18:11:19 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g0G2Au202938; Tue, 15 Jan 2002 18:10:56 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g0G2At248672; Tue, 15 Jan 2002 18:10:55 -0800 (PST) (envelope-from jdp) Date: Tue, 15 Jan 2002 18:10:55 -0800 (PST) Message-Id: <200201160210.g0G2At248672@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: swb@grasslake.net Subject: Re: Group executable bit quit working? In-Reply-To: <009d01c19dfd$a434b950$021ea8c0@twinstar> References: <009d01c19dfd$a434b950$021ea8c0@twinstar> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <009d01c19dfd$a434b950$021ea8c0@twinstar>, Shawn Barnhart wrote: > Just upgraded three systems to 4.5 RC-6 this weekend and I seem to have lost > the ability execute shell scripts or perl scripts that are group executable > only. > > The scripts run otherwise if I make them executable by the owner, but having > them g+x doesn't seem to be enough anymore. I have another system running > 4.4 that also exhibits this behavior, so its confusing me. > > The scripts in question the 4.5-RC system have been running for years with > permissions of 654. It works for me. However, I have an idea about why you might think it's broken. Let's say the file's modes are 654 (rw-r-xr--) and you are a member of the file's group. If you are also the owner of the file, you will not be able to execute it. But if you are _not_ the owner, you will be able to execute it. It's counter-intuitive, but the rule is that if you own the file, the owner permissions are used and the group permissions are ignored. I believe this is the traditional behavior, as I remember seeing it on other Unix systems at least 10 years ago. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 20:19:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from zoon.lafn.org (zoon.lafn.org [206.117.18.9]) by hub.freebsd.org (Postfix) with ESMTP id 377A237B404 for ; Tue, 15 Jan 2002 20:19:20 -0800 (PST) Received: from [10.0.1.90] (66-81-34-215-modem.o1.com [66.81.34.215]) by zoon.lafn.org (8.11.3/8.11.3) with ESMTP id g0G4JEl82890; Tue, 15 Jan 2002 20:19:14 -0800 (PST) (envelope-from bc979@lafn.org) Mime-Version: 1.0 X-Sender: bc979@mail.lafn.org Message-Id: In-Reply-To: <20020115133933.GA44311@maths.tcd.ie> References: <200201140227.NAA07734@lightning.itga.com.au> <20020115133933.GA44311@maths.tcd.ie> Date: Tue, 15 Jan 2002 20:16:14 -0800 To: David Malone From: Doug Hardie Subject: Re: mbuf usage Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 13:39 +0000 1/15/02, David Malone wrote: >On Sun, Jan 13, 2002 at 07:06:18PM -0800, Doug Hardie wrote: >> Is there any tool that shows the process or port to which mbufs are >> associated? One of my systems is showing 10K mbufs in use but there >> are only 2 tcp connections established and a couple of udp active >> processes. Trafshow shows nothing unusual. Very light load on the >> server but someting is eating mbufs. > >Some of Ian's libkvm tools might be useful: > > http://www.maths.tcd.ie/~iedowse/projects.html > >David. Thanks for the tip. I tried them and they give a very accurate picture of tcp/ip usage of mbufs. Unfortunately, it shows the same results as netstat - around 100 mbufs in use. However, netstat -m shows almot 10K in use. One of the tools shows the contents of the mbufs and many are completely nulls and others are obviously left over buffers as they have log file contents from weeks ago. What besides tcp/ip uses mbufs? Can mbufs become orphaned? -- -- Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 21:20:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ntplx.net (mail5.ntplx.net [204.213.176.70]) by hub.freebsd.org (Postfix) with ESMTP id 016B537B404 for ; Tue, 15 Jan 2002 21:20:26 -0800 (PST) Received: from ntplx.net (dhcp-209-54-75-231.ct.dsl.ntplx.com [209.54.75.231]) by mail.ntplx.net (8.11.6/8.11.4/NETPLEX) with ESMTP id g0G5K9B27722; Wed, 16 Jan 2002 00:20:10 -0500 (EST) Message-ID: <3C450E9F.2E06C52@ntplx.net> Date: Wed, 16 Jan 2002 00:24:47 -0500 From: Ted Sikora X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.5 i686) X-Accept-Language: en-US, en MIME-Version: 1.0 To: John Polstra , "freebsd-stable@FreeBSD.ORG" Subject: Re: Port cvsup problem... References: <20020115190027.A5224@infocom.kh.ua> <200201151725.g0FHPoA47993@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Polstra wrote: > > In article <20020115190027.A5224@infocom.kh.ua>, > Aleksey Ovcharenko wrote: > > Than trying to update doc's tree via cvs I got: > > I started having a problem with cvsup on stable several days ago. It core dumps and fails with a FileStatus.m3 line 586 ASSERT error. I removed it reinstalled it via ports .. SNAP_16_1f same thng no matter what I do Tried your static bin's and building static versions building the 1e version too ... HELP! -- Ted Sikora tsikora@unixos2.org http://unixos2.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 21:29:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pom.INS.cwru.edu (pom.INS.CWRU.Edu [129.22.8.234]) by hub.freebsd.org (Postfix) with ESMTP id 5E3BA37B402 for ; Tue, 15 Jan 2002 21:29:47 -0800 (PST) Received: from po.cwru.edu (adsl-64-108-88-128.dsl.clevoh.ameritech.net [64.108.88.128]) by pom.INS.cwru.edu with ESMTP (8.8.8+cwru/CWRU-1.0-smtprelay) id AAA10470; Wed, 16 Jan 2002 00:29:46 -0500 (EST) (from sjh13@po.cwru.edu for ) Message-ID: <3C450FC9.2050601@po.cwru.edu> Date: Wed, 16 Jan 2002 00:29:45 -0500 From: Steven Huwig User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.7) Gecko/20020107 X-Accept-Language: en-us MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Changes to man page in 4.5-R? References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I was reading the QA guidelines at http://www.freebsd.org/releases/4.5R/qa.html, and I was wondering what the following statement (second bullet from bottom) means: * Once the man page change goes in (which I think it should) we'll want some basic testing of the man command. What is the "man page change?" And is it in? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 15 23:29:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mao.stokely.org (mao.stokely.org [65.84.64.228]) by hub.freebsd.org (Postfix) with ESMTP id 6B01937B419 for ; Tue, 15 Jan 2002 23:29:27 -0800 (PST) Received: by mao.stokely.org (Postfix, from userid 2074) id C8F8D4B65D; Tue, 15 Jan 2002 23:29:26 -0800 (PST) Date: Tue, 15 Jan 2002 23:29:26 -0800 From: Murray Stokely To: Steven Huwig Cc: stable@FreeBSD.ORG Subject: Re: Changes to man page in 4.5-R? Message-ID: <20020116072926.GV6073@windriver.com> References: <3C450FC9.2050601@po.cwru.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C450FC9.2050601@po.cwru.edu> User-Agent: Mutt/1.3.25i X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 16, 2002 at 12:29:45AM -0500, Steven Huwig wrote: > I was reading the QA guidelines at > http://www.freebsd.org/releases/4.5R/qa.html, and I was wondering what > the following statement (second bullet from bottom) means: > > * Once the man page change goes in (which I think it should) we'll want > some basic testing of the man command. > > What is the "man page change?" And is it in? This change was just committed to -CURRENT within the last 24 hours. I posted a message to -qa about this earlier today. It will most likely be approved for MFC shortly. Ruslan's commit message does a good job of describing the change : - Murray ru 2002/01/15 06:11:05 PST Modified files: gnu/usr.bin/man/man Makefile man.c etc/mtree BSD.local.dist BSD.usr.dist BSD.x11-4.dist BSD.x11.dist Log: Do not install man(1) setuid ``man''. The catpaging and setuidness features of man(1) combined make it vulnerable to a number of security attacks. Specifically, it was possible to overwrite system catpages with arbitrarily contents by either setting up a symlink to a directory holding system catpages, or by writing custom -mdoc or -man groff(1) macro packages and setting up GROFF_TMAC_PATH in environment to point to them. (See PR below for details). This means man(1) can no longer create system catpages on a regular user's behalf. (It is still able to if the user has write permissions to the directory holding catpages, e.g., user's own manpages, or if the running user is ``root''.) To create and install catpages during ``make world'', please set MANBUILDCAT=YES in /etc/make.conf. To rebuild catpages on a weekly basis, please set weekly_catman_enable="YES" in /etc/periodic.conf. PR: bin/32791 Revision Changes Path 1.85 +3 -7 src/etc/mtree/BSD.local.dist 1.251 +4 -6 src/etc/mtree/BSD.usr.dist 1.19 +2 -4 src/etc/mtree/BSD.x11-4.dist 1.16 +2 -4 src/etc/mtree/BSD.x11.dist 1.33 +1 -4 src/gnu/usr.bin/man/man/Makefile 1.51 +2 -62 src/gnu/usr.bin/man/man/man.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 0: 0:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from onion.ish.org (onion.ish.org [210.145.219.202]) by hub.freebsd.org (Postfix) with ESMTP id B97A237B41A for ; Wed, 16 Jan 2002 00:00:53 -0800 (PST) Received: from localhost (ishizuka@localhost [127.0.0.1]) by onion.ish.org (8.11.6/8.11.6/2001-11-30) with ESMTP id g0G80qN91631 for ; Wed, 16 Jan 2002 17:00:52 +0900 (JST) (envelope-from ishizuka@ish.org) Date: Wed, 16 Jan 2002 17:00:52 +0900 (JST) Message-Id: <20020116.170052.74668685.ishizuka@ish.org> To: freebsd-stable@FreeBSD.ORG Subject: 4.5-RC1 cannot boot up with fxp NIC on Asus P3B-F slot #4 From: Masachika ISHIZUKA X-PGP-Fingerprint20: 276D 697A C2CB 1580 C683 8F18 DA98 1A4A 50D2 C4CB X-PGP-Fingerprint16: C6 DE 46 24 D7 9F 22 EB 79 E2 90 AB 1B 9A 35 2E X-PGP-Public-Key: http://www.ish.org/pgp-public-key.txt X-URL: http://www.ish.org/ X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, this is ishizuka@ish.org. Is there anyone who have Asus P3B-F mother board and fxp NIC ? I cannot bootup GENERIC kernel of 4.5-RC1 similar to described in kern/30715 that was for 4.4-RELEASE. -- ishizuka@ish.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 0:24:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from onion.ish.org (onion.ish.org [210.145.219.202]) by hub.freebsd.org (Postfix) with ESMTP id C573637B419 for ; Wed, 16 Jan 2002 00:24:09 -0800 (PST) Received: from localhost (ishizuka@localhost [127.0.0.1]) by onion.ish.org (8.11.6/8.11.6/2001-11-30) with ESMTP id g0G8O8N93009 for ; Wed, 16 Jan 2002 17:24:08 +0900 (JST) (envelope-from ishizuka@ish.org) Date: Wed, 16 Jan 2002 17:24:08 +0900 (JST) Message-Id: <20020116.172408.41714577.ishizuka@ish.org> To: freebsd-stable@FreeBSD.ORG Subject: bind 8.2.4-REL in 4.5-RC1 is safe enough ? From: Masachika ISHIZUKA X-PGP-Fingerprint20: 276D 697A C2CB 1580 C683 8F18 DA98 1A4A 50D2 C4CB X-PGP-Fingerprint16: C6 DE 46 24 D7 9F 22 EB 79 E2 90 AB 1B 9A 35 2E X-PGP-Public-Key: http://www.ish.org/pgp-public-key.txt X-URL: http://www.ish.org/ X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, this is ishizuka@ish.org. Bind in 4.5-RC1 is 8.2.4-REL. Is there any reason that is not 8.2.5-REL, 8.3.0, nor 9.2.0. The recommended versions in http://www.isc.org/ are 8.3.0 for bind8 or 9.2.0 for bind9. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 1: 0:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mile.nevermind.kiev.ua (freebsddiary.org.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id 8281237B404; Wed, 16 Jan 2002 01:00:41 -0800 (PST) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.11.6/8.11.4) id g0G94ag04030; Wed, 16 Jan 2002 11:04:36 +0200 (EET) (envelope-from never) Date: Wed, 16 Jan 2002 11:04:19 +0200 From: Nevermind To: Murray Stokely Cc: Steven Huwig , stable@FreeBSD.ORG Subject: Re: Changes to man page in 4.5-R? Message-ID: <20020116090419.GB3705@nevermind.kiev.ua> References: <3C450FC9.2050601@po.cwru.edu> <20020116072926.GV6073@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20020116072926.GV6073@windriver.com> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Murray Stokely! On Tue, Jan 15, 2002 at 11:29:26PM -0800, you wrote: > This change was just committed to -CURRENT within the last 24 hours. > I posted a message to -qa about this earlier today. It will most > likely be approved for MFC shortly. Ruslan's commit message does a > good job of describing the change : > > - Murray > > ru 2002/01/15 06:11:05 PST > > Modified files: > gnu/usr.bin/man/man Makefile man.c > etc/mtree BSD.local.dist BSD.usr.dist > BSD.x11-4.dist BSD.x11.dist > Log: > Do not install man(1) setuid ``man''. [skip] > To create and install catpages during ``make world'', please > set MANBUILDCAT=YES in /etc/make.conf. To rebuild catpages > on a weekly basis, please set weekly_catman_enable="YES" in > /etc/periodic.conf. I suppose we should not forget this to be added to UPDATING ? -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 1:14: 4 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 6D3F237B416 for ; Wed, 16 Jan 2002 01:13:45 -0800 (PST) Received: from max ([12.254.136.195]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020116091345.IPTU5944.rwcrmhc51.attbi.com@max> for ; Wed, 16 Jan 2002 09:13:45 +0000 Message-ID: <080801c19e6e$4712f360$0900a8c0@max> From: "John Nielsen" To: Subject: typo in man ed (4) Date: Wed, 16 Jan 2002 02:15:01 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is something that's bitten me on the two occasions I've needed to use it, so I'm hoping it can get fixed. In the CAVEATS section of the ed (4) manpage, it says this: 16bit Compex cards identify themselves as being 8bit. While these cards will work in 8bit mode, much higher performance can be achieved by speci- fying "flags 0x04" (force 16bit mode) in your kernel config file. In addi- tion, you should also specify "iosize 16384" to take advantage of the extra 8k of shared memory that 16bit mode provides. If you put the word "iosize" in a kernel config file it produces a syntax error. It should be "iosiz" (without the 'e'). I'm not familiar with the procedure(s) for fixing typos like this, but if one of you could enlighten me and/or just take care of it I'd be appreciative. Thanks, JN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 1:20:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 03FFA37B400 for ; Wed, 16 Jan 2002 01:20:43 -0800 (PST) Received: (from uucp@localhost) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) id g0G9KV419709; Wed, 16 Jan 2002 10:20:31 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.11.6/8.11.3) id g0G9AUK16612; Wed, 16 Jan 2002 10:10:30 +0100 (CET) (envelope-from andreas) Date: Wed, 16 Jan 2002 10:10:30 +0100 From: Andreas Klemm To: apsfilter-help@apsfilter.org Cc: Garance A Drosihn , desmo@bandwidth.org, freebsd-stable@freebsd.org Subject: 4.4R: if: doesn't get started when getting remote print job (Re: apsfilter doesn't work on server) Message-ID: <20020116091030.GA16535@titan.klemm.gtn.com> References: <20020115062456.GA13349@christian.chrullrich.de> <20020115151846.GA14953@christian.chrullrich.de> <20020115213522.GA15920@christian.chrullrich.de> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20020115213522.GA15920@christian.chrullrich.de> User-Agent: Mutt/1.3.23.1i X-Operating-System: FreeBSD 4.5-RC X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 15, 2002 at 10:35:22PM +0100, Christian Ullrich wrote: > * Christian Ullrich wrote on Tuesday, 2002-01-15: >=20 > > * Michael Lo=DFin wrote on Tuesday, 2002-01-15: > >=20 > > > On 15-Jan-02 Christian Ullrich wrote: > >=20 > > > Which spooler do you use on those? > >=20 > > BSD lpd on the Server, LPRng on the client. > >=20 > > > Please try to use LPRng on server *and* client machines, since > > > the old BSD-style lpd has some problems with remote printing. > >=20 > > I'll try that ASAP. >=20 > Warning: The following is _very_ detailed. It took me three hours > to do it all and write it down. If there is _any_ information=20 > missing, please do not hesitate to ask. >=20 > Just as a reminder: The server is FreeBSD 4.4-RELEASE, the client > is SuSE Linux 7.3, using LPRng 3.7.4. The printer in question,=20 > connected to the server by parallel cable, is an HP LaserJet 1200, > which is PostScript Level2 capable, although it also supports PCL. > The problem in question is that, while printing on the server=20 > works just fine, printing from the client seems to bypass apsfilter. > The symptoms are: > - Text is printed with "staircase effect". > - PostScript is printed flawlessly. > - Anything else is not printed at all. >=20 > The following is an account of my adventures tonight. Steps 1 to > 18 took place on the server, 19, 20 and 21 on the client. >=20 > 1. I updated selected parts of the installed ports, nothing to do > with printing or graphics or such things (but I thought I should > include it here). >=20 > 2. I moved /etc/printcap and /etc/apsfilter out of the way. >=20 > 3. I moved all files in /usr/bin and /usr/sbin with names starting=20 > with "lp" out of the way, provided they looked like parts of > BSD lpd: /usr/bin/{lp,lpq,lpr,lprm} and /usr/sbin/{lpc,lpd} >=20 > 4. I rebuilt LPRng-3.7.6 from the ports collection and installed it > as it was built, without messing with the build directory. >=20 > 5. I verified the settings in /usr/local/etc/rc.d/lprng.sh and found > them to be in good order. >=20 > 6. I built apsfilter-7.2.1, with the following options enabled: > - A4 - A4 papersize > - GS_NO_X11 - Postscript for non-PS printer, no X11 > - GS_PDF_CRYPT - print encrypted PDF files using gs > - PSUTILS - for pseudo duplex printing + paper handling > - A2PS - ASCII files in different styles/orientation > - DVIPS - TeX DVI files > - HTML2PS - HTML documents > - TROFF - Troff documents > - BZIP2 - print bunzip2 compressed documents > On the first attempt to "make install" apsfilter, I was told that > the file /usr/local/etc/apsfilter existed. It was a symbolic link > to /etc/apsfilter, which I had renamed in step 2. I removed the=20 > link and installed again. This time it worked fine. If you had updated the ports collection you would have used apsfilter 7.2.1, which includes a fix for that by using ln -sf ... > 7. I started the SETUP script and accepted the ownership of > root.daemon for the spool directory /var/spool/lpd . >=20 > 8. I configured a printer as follows: > - Printer Driver Selection [PS] > - Interface Setup [parallel], via /dev/lpt0 > - Paper Format [a4] > - Printing Quality [medium] > - Color Mode [gray] > - Print Resolution in "dots per inch" [600x600] > - Default Printing Method [ascii] >=20 > 9. I printed a test page. Preparation took no time at all, printing, > however, lasted 4:33. It is a complex page, after all, and the=20 > HP 1200 seems to be slightly underpowered. > =20 > 10. I installed that configuration under the name "ascii" and finished > the SETUP script for the time being. > =20 > This is the generated printcap (comments stripped): > =20 > ascii|PS;r=3D600x600;q=3Dmedium;c=3Dgray;p=3Da4;m=3Dascii:\ > :lp=3D/dev/lpt0:\ > :if=3D/etc/apsfilter/basedir/bin/apsfilter:\ > :sd=3D/var/spool/lpd/ascii:\ > :lf=3D/var/spool/lpd/ascii/log:\ > :af=3D/var/spool/lpd/ascii/acct:\ > :mx#0:\ > :sh: Why you named it ASCII ? > 11. I started LPRng and found this line in syslog: >=20 > Jan 15 20:41:02 ser1 checkpc[73259]: ascii: Checkwrite: fcntl F_SETFL= =20 > of '/dev/lpt0' failed - Operation not supported by device > =09 > Similar output was generated by calling "checkpc -f". But sending > data to the printer was never the problem, so I'm currently not > much concerned about it. Ask FreeBSD port maintainer, LPRng people. > 12. I tried to print a simple text file ("lpr -Pascii /etc/printcap"), > but lpq said this: > =09 > Status: cannot open '/dev/lpt0' - 'Permission denied', attempt 2,=20 > sleeping 20 at 20:48:37.238 >=20 > I removed the job ("lprm 337") > =09 > 13. I checked the permissions on /dev/lpt0: root.daemon 660. >=20 > 14. Trying to find out what user LPRng's lpd runs as, I read a lot > of documentation in the build directory, only to find that it > apparently setuid()'s itself to daemon.daemon, which ought to=20 > work. > =09 > 15. In order to test if this made it work, I changed the permissions > on /dev/lpt0 to root.daemon 666, killed and restarted lpd, and > tried again to print the text file. It worked, and the output=20 > looked fine. The F_SETFL error message appeared again. > =09 > 16. A cursory glance at the source code showed that LPRng perhaps > does not -- as written in the LPRng-HOWTO -- set both uid and > gid to daemon, but only the UID. In my case, it would then > run as daemon.wheel, which can't possibly work. > A less cursory glance at the output of "lpd -D4" showed that > lpd does at least look up the correct GID of 1 for the > daemon group. >=20 > 17. I tested this idea: > - chown chris.chris /dev/lpt0; chmod 660 /dev/lpt0 > (myself, to make sure that neither user nor group match) > - "permission denied" > - chown chris.daemon /dev/lpt0 > (may be the correct group) > - "permission denied" > - chown daemon.chris /dev/lpt0 > (may be the correct user) > - worked. > So lpd sets the documented uid, but another gid. > =09 > Unfortunately, ps apparently can't find out the effective gid > of a process, so I had to settle for the real one, which is > 0 (wheel). But that didn't tell me anything, of course. > =09 > - chown chris.wheel /dev/lpt0 > (the suspected gid of 0) > - worked. > Obviously, lpd succeeds only in changing the uid, but fails > at the gid (if it tries at all, that is). > =09 > I set the ownership to daemon.wheel to make at least that work. > =09 > 18. I checked the LPRng changelog. Lo and behold, it mentions that > very bug as fixed in 3.7.6. Unfortunately, that is the version > I installed. Let's blame it on a wrong fix. About time the LPRng > port gets updated, the current release is 3.8.4. Please tell the port maintainer. > 19. Now for the client. Using SuSE's YaST configuration tool, > I configured a simple network printer: > =09 > ascii|remote printer on ser1:\ > :sd=3D/var/spool/lpd/ascii:\ > :rm=3Dser1:\ > :rp=3Dascii:\ > :bk:sh:mx#0: > =09 > 20. "lpq -Pascii" on the client showed that the printer status was > accessible. > =09 > 21. "lpr -Pascii /etc/printcap" from the client produced the usual > staircased text. Even an "ASCII only" apsfilter configuration > on the server didn't work, and still doesn't. Because the printer > stopped blinking, I'm sure that it got the text file directly, > without apsfilter in between. >=20 > I'm out of ideas. What about you out there? As workaround install apsfilter on the client, to compute print data on the client, so that the correct data stream enters the server. You should try to contact Garance A Drosihn to ask, since he did a lot on the FreeBSD spooling system. Theoretically I think the input filter should be executed even when getting print data via network. He can tell you, if there is a bug in 4.4-RELEASE. Well now you installed LPRng on FreeBSD which normally is not necessary, since FreeBSD's lpd is not so "stock" and limited as all the other un-fixed versions around. For example printing to a remote printer and using an input filter is fixed in FreeBSD since a long time. So theoretically you can stay with FreeBSD lpd, since its not so bloated like LPRng. Not that its really bad, but I don't like it .... Then additionally send this report to the LPRng port maintainer so that an update gets releases. I hope both can help you. BTW: I already put both on Cc: ... Concerning lpd I'd remove the LPRng port if Garant has replied to you and I'm sure, that he will be helpful to you. But then you should re-install lpd from /usr/src, that shouldn't be a problem with FreeBSD ... Additionally you could then try to update to 4.5-RC, since then you can both work on the latest and greatest -STABLE version of FreeBSD, so that there every bug is shaken out ... And I remember people have merged something from -current into the printing subsystem, maybe this already helped. And please use apsfilter 7.2.1. Andreas /// --=20 Andreas Klemm Apsfilter Homepage http://www.apsfilter.org Support over mailing-lists (only!) http://www.apsfilter.org/support Mailing-list archive http://www.apsfilter.org/Lists-Arc= hives Songs from our band >> 64Bits << http://www.64bits.de Inofficial band pages with add-on stuff http://www.apsfilter.org/64bits.ht= ml --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE8RUOGd3o+lGxvbLoRAue6AJ4542/XLgKhKTZbv50MbYxlTS52BQCfZaMU 7D2TzTqMnPSSsxDE0m+Z4/c= =Drrh -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 1:21:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from keyser.soze.com (keyser.soze.com [194.165.93.196]) by hub.freebsd.org (Postfix) with ESMTP id 1C0A737B400; Wed, 16 Jan 2002 01:21:01 -0800 (PST) Received: from erg.verweg.com ([132.229.90.89]) by keyser.soze.com (8.9.1/8.9.1) with ESMTP id KAA26042; Wed, 16 Jan 2002 10:15:27 +0100 (CET) Received: (from ruben@localhost) by erg.verweg.com (8.9.3+3.2W/8.9.3) id KAA11551; Wed, 16 Jan 2002 10:20:59 +0100 (CET) Date: Wed, 16 Jan 2002 10:20:57 +0100 From: Ruben van Staveren To: freebsd-stable@FreeBSD.ORG Cc: freebsd-smp@FreeBSD.ORG Subject: Audio can hang machine. SMP related Message-ID: <20020116092057.GA11305@erg.verweg.com> References: <20020104101054.A26506@mikea.ath.cx> <20020104160606.F46320-100000@galatea.internal.lustygrapes.net> <20020107185514.GA7545@erg.verweg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020107185514.GA7545@erg.verweg.com> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jan 07, 2002 at 07:55:14PM +0100, Ruben van Staveren wrote: > These hangs seem very similar to what I am experiencing and wrote earlier > about in message id's <20011115205310.A13588@erg.verweg.com> and > <20011226235825.A9317@erg.verweg.com> > > I've recompiled almost everything on my system that possibly could interact > with kernel internals. I set my bios to MPS 1.4 specification (I still wonder > what it does, has something to do with interrupt assignment ?) but still > these lockups while running a SMP kernel. Uniprocessor is just fine. > > For the moment I have unloaded my audio device drivers from loader.conf > (FYI, it is an AudioPCI ES1370 card (SB 128 PCI)) System is running just fine ever since, putting back in the audio support makes it unstable again. Is there an open PR for this ? Kind regards, Ruben -- ,-_ .----------------------------------------------------------------. /() ) | Ruben van Staveren http://ruben.is.verweg.com/ |_o (__ ( |Men are from Mars. Women are from Venus. Computers are from hell| #> =/ () `----------------------------------------------------------------' 4 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 1:40:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id A20C037B400 for ; Wed, 16 Jan 2002 01:40:20 -0800 (PST) Received: (from uucp@localhost) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) id g0G9eCm25021; Wed, 16 Jan 2002 10:40:12 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.11.6/8.11.3) id g0G9WvE18127; Wed, 16 Jan 2002 10:32:57 +0100 (CET) (envelope-from andreas) Date: Wed, 16 Jan 2002 10:32:57 +0100 From: Andreas Klemm To: apsfilter-help@apsfilter.org Cc: Garance A Drosihn , desmo@bandwidth.org, freebsd-stable@freebsd.org Subject: Re: 4.4R: if: doesn't get started when getting remote print job (Re: apsfilter doesn't work on server) Message-ID: <20020116093257.GA18106@titan.klemm.gtn.com> References: <20020115062456.GA13349@christian.chrullrich.de> <20020115151846.GA14953@christian.chrullrich.de> <20020115213522.GA15920@christian.chrullrich.de> <20020116091030.GA16535@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20020116091030.GA16535@titan.klemm.gtn.com> User-Agent: Mutt/1.3.23.1i X-Operating-System: FreeBSD 4.5-RC X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Another idea ... additionally. use set -x in apsfilter shellscript and see in the printers logfile, if apsfilter gets called an how, to make sure what happens or not ... Andreas /// --=20 Andreas Klemm Apsfilter Homepage http://www.apsfilter.org Support over mailing-lists (only!) http://www.apsfilter.org/support Mailing-list archive http://www.apsfilter.org/Lists-Arc= hives Songs from our band >> 64Bits << http://www.64bits.de Inofficial band pages with add-on stuff http://www.apsfilter.org/64bits.ht= ml --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE8RUjId3o+lGxvbLoRArvdAKCfE1VUd/ZSPt57ZwgQUQPsuBlB6gCfSAJz 5FzYk1iNJmJPyerObQCBBB8= =hqOF -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 1:40:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id AF61D37B417 for ; Wed, 16 Jan 2002 01:40:20 -0800 (PST) Received: (from uucp@localhost) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) id g0G9eDx25026; Wed, 16 Jan 2002 10:40:13 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.11.6/8.11.3) id g0G9Xpb18142; Wed, 16 Jan 2002 10:33:51 +0100 (CET) (envelope-from andreas) Date: Wed, 16 Jan 2002 10:33:50 +0100 From: Andreas Klemm To: apsfilter-help@apsfilter.org Cc: Garance A Drosihn , desmo@bandwidth.org, freebsd-stable@freebsd.org Subject: Re: 4.4R: if: doesn't get started when getting remote print job (Re: apsfilter doesn't work on server) Message-ID: <20020116093350.GB18106@titan.klemm.gtn.com> References: <20020115062456.GA13349@christian.chrullrich.de> <20020115151846.GA14953@christian.chrullrich.de> <20020115213522.GA15920@christian.chrullrich.de> <20020116091030.GA16535@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20020116091030.GA16535@titan.klemm.gtn.com> User-Agent: Mutt/1.3.23.1i X-Operating-System: FreeBSD 4.5-RC X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Yylu36WmvOXNoKYn" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Yylu36WmvOXNoKYn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable And please summarize in your mail the exact FreeBSD version. uname -a could additionally help FreeBSD titan.klemm.gtn.com 4.5-RC FreeBSD 4.5-RC #0... ^^^^^^ Andreas /// --=20 Andreas Klemm Apsfilter Homepage http://www.apsfilter.org Support over mailing-lists (only!) http://www.apsfilter.org/support Mailing-list archive http://www.apsfilter.org/Lists-Arc= hives Songs from our band >> 64Bits << http://www.64bits.de Inofficial band pages with add-on stuff http://www.apsfilter.org/64bits.ht= ml --Yylu36WmvOXNoKYn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE8RUj+d3o+lGxvbLoRAmC6AKClTTkJV2vgYbJ/BuJzb7DamGdNbQCeKDmG 5Askl8FxGvzGQr/PKTCV0PA= =J6YE -----END PGP SIGNATURE----- --Yylu36WmvOXNoKYn-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 2:46:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from shikima.mine.nu (pc1-card4-0-cust77.cdf.cable.ntl.com [62.252.49.77]) by hub.freebsd.org (Postfix) with ESMTP id 8410037B416 for ; Wed, 16 Jan 2002 02:46:15 -0800 (PST) Received: from rasputin by shikima.mine.nu with local (Exim 3.33 #1) id 16Qncu-0000lf-00; Wed, 16 Jan 2002 10:49:04 +0000 Date: Wed, 16 Jan 2002 10:49:04 +0000 From: Rasputin To: Matthew Dillon Cc: stable@freebsd.org Subject: Re: what's vnlru? Message-ID: <20020116104904.A2800@shikima.mine.nu> Reply-To: Rasputin References: <200201151618468.SM01176@141.com> <200201160101.g0G117r64693@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200201160101.g0G117r64693@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Jan 15, 2002 at 05:01:07PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matthew Dillon [020116 01:10]: > vnlru is responsible for flushing and freeing vnodes when you > hit the kern.maxvnodes limit. The history of this is: > > 4.4 and earlier vnodes were only freed if they had no cached pages. > This could lead to a vnode blowout on machines with > large amounts of ram accessing lots of small files. > (the kern.maxvnodes limit was essentially ignored) > > 4.4-stable I introduced code to flush/reuse vnodes on the fly, > but this lead to possible locking deadlocks. > > 4.5-* Peter introduced a separate kernel thread to deal with > vnode flushing issues, 'vnlru', in order to fix the > possible locking deadlocks. The on-the-fly code > was changed to only be called from the kernel thread. > > This kernel thread will generally not be very active, even on a heavily > loaded system. You have to have a lot of ram and be accessing tens of > thousands of tiny files to activate the thread. Thansk for the overview - it's not a performance issue, I just checked another fairly recent (4.5 pre) BSD box and didn't see it, so thought I'd better check it out. [ Is this the sort of thing that should go into UPDATING? ] Thanks to all ! -- Learned men are the cisterns of knowledge, not the fountainheads. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 3: 8:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id DA6E637B404; Wed, 16 Jan 2002 03:07:55 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g0GB70872616; Wed, 16 Jan 2002 13:07:00 +0200 (EET) (envelope-from ru) Date: Wed, 16 Jan 2002 13:07:00 +0200 From: Ruslan Ermilov To: Nevermind Cc: Murray Stokely , Steven Huwig , stable@FreeBSD.ORG, Warner Losh Subject: Re: Changes to man page in 4.5-R? Message-ID: <20020116130700.E40637@sunbay.com> References: <3C450FC9.2050601@po.cwru.edu> <20020116072926.GV6073@windriver.com> <20020116090419.GB3705@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020116090419.GB3705@nevermind.kiev.ua> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 16, 2002 at 11:04:19AM +0200, Nevermind wrote: > Hello, Murray Stokely! > > On Tue, Jan 15, 2002 at 11:29:26PM -0800, you wrote: > > > This change was just committed to -CURRENT within the last 24 hours. > > I posted a message to -qa about this earlier today. It will most > > likely be approved for MFC shortly. Ruslan's commit message does a > > good job of describing the change : > > > > - Murray > > > > ru 2002/01/15 06:11:05 PST > > > > Modified files: > > gnu/usr.bin/man/man Makefile man.c > > etc/mtree BSD.local.dist BSD.usr.dist > > BSD.x11-4.dist BSD.x11.dist > > Log: > > Do not install man(1) setuid ``man''. > [skip] > > To create and install catpages during ``make world'', please > > set MANBUILDCAT=YES in /etc/make.conf. To rebuild catpages > > on a weekly basis, please set weekly_catman_enable="YES" in > > /etc/periodic.conf. > I suppose we should not forget this to be added to UPDATING ? > Ah, thanks for reminding. I was going to ask Warner to add this last paragraph (or equivalent) to UPDATING. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 3:12:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mout03.kundenserver.de (mout03.kundenserver.de [195.20.224.218]) by hub.freebsd.org (Postfix) with ESMTP id 529AB37B417 for ; Wed, 16 Jan 2002 03:11:29 -0800 (PST) Received: from [195.20.224.204] (helo=mrvdom00.kundenserver.de) by mout03.kundenserver.de with esmtp (Exim 2.12 #2) id 16QnyN-0007kU-00; Wed, 16 Jan 2002 12:11:15 +0100 Received: from [217.230.78.245] (helo=ser1.chrullrich.de) by mrvdom00.kundenserver.de with esmtp (Exim 2.12 #2) id 16QnyK-0000E2-00; Wed, 16 Jan 2002 12:11:13 +0100 Received: from christian.chrullrich.de (christian.chrullrich.de [192.168.0.2]) by ser1.chrullrich.de (Postfix) with ESMTP id 5DB5316F; Wed, 16 Jan 2002 12:11:12 +0100 (CET) Received: by christian.chrullrich.de (Postfix on SuSE Linux 7.3 (i386), from userid 1000) id 25B1645; Wed, 16 Jan 2002 12:11:06 +0100 (CET) Date: Wed, 16 Jan 2002 12:04:48 +0100 From: Christian Ullrich To: apsfilter-help@apsfilter.org Subject: Re: 4.4R: if: doesn't get started when getting remote print job (Re: apsfilter doesn't work on server) Message-ID: <20020116110448.GA19558@christian.chrullrich.de> References: <20020115062456.GA13349@christian.chrullrich.de> <20020115151846.GA14953@christian.chrullrich.de> <20020115213522.GA15920@christian.chrullrich.de> <20020116091030.GA16535@titan.klemm.gtn.com> <20020116093257.GA18106@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020116093257.GA18106@titan.klemm.gtn.com> User-Agent: Mutt/1.3.25i X-Current-Uptime: 7 d, 12:51:40 h Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Andreas Klemm schrieb am Mittwoch, 2002-01-16: > Another idea ... additionally. > use set -x in apsfilter shellscript and see in the printers logfile, > if apsfilter gets called an how, to make sure what happens or not ... I did that. As I'm currently some 30 km away from the printer, I can't see what it produced, but now I know at least that apsfilter was indeed called. In the directory /var/spool/lpd/ascii, two files have been created: "lpq" and "lpq.0". The first one contains only: 4=filenames=lpq.0,prstatus=0x3c4485ce,queue_status_file=0x3c455d0d, (including that comma at the end of the previous line). The second is about 6 KiB and starts thus: Printer: ascii@ser1 'PS;r=600x600;q=medium;c=gray;p=a4;m=ascii' Queue: no printable jobs in queue Status: IF filter 'apsfilter' filter msg - 'J(STDIN)' at 11:59:23.292 Status: IF filter 'apsfilter' filter msg - 'Pchris' at 11:59:23.292 Status: IF filter 'apsfilter' filter msg - 'Qascii' at 11:59:23.292 Status: IF filter 'apsfilter' filter msg - 'N(STDIN)' at 11:59:23.292 Status: IF filter 'apsfilter' filter msg - 'ldfA671christian.chrullrich.de' at 11:59:23.292 Status: IF filter 'apsfilter' filter msg - 'UdfA671christian.chrullrich.de' at 11:59:23.292 Status: IF filter 'apsfilter' filter msg - '' ']'' at 11:59:23.292 Status: IF filter 'apsfilter' filter msg - '+ '[' '(STDIN)' = stdin -o '(STDIN) ' = '(stdin)' -o '(STDIN)' = '(STDIN)' ']'' at 11:59:23.293 Status: IF filter 'apsfilter' filter msg - '+ unset JOB' at 11:59:23.293 Status: IF filter 'apsfilter' filter msg - '+ '[' christian ']'' at 11:59:23.29 4 More data on request. As I said before, I don't really know what's lying in the printer's output tray right now, but I'm quite sure that it's still staircased text. What I printed, BTW, was "fortune -l | lpr -Pascii". The remote queue on the client (christian) is also called "ascii". Thanks for your reply no. 2. -- Christian Ullrich Registrierter Linux-User #125183 "Deliver." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 3:12:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mout01.kundenserver.de (mout01.kundenserver.de [195.20.224.132]) by hub.freebsd.org (Postfix) with ESMTP id 2132337B43D for ; Wed, 16 Jan 2002 03:11:42 -0800 (PST) Received: from [195.20.224.209] (helo=mrvdom02.kundenserver.de) by mout01.kundenserver.de with esmtp (Exim 2.12 #2) id 16Qnyj-0002lD-00; Wed, 16 Jan 2002 12:11:37 +0100 Received: from [217.230.78.245] (helo=ser1.chrullrich.de) by mrvdom02.kundenserver.de with esmtp (Exim 2.12 #2) id 16Qnyg-0006sz-00; Wed, 16 Jan 2002 12:11:34 +0100 Received: from christian.chrullrich.de (christian.chrullrich.de [192.168.0.2]) by ser1.chrullrich.de (Postfix) with ESMTP id 3FAF2175; Wed, 16 Jan 2002 12:11:32 +0100 (CET) Received: by christian.chrullrich.de (Postfix on SuSE Linux 7.3 (i386), from userid 1000) id 3E56245; Wed, 16 Jan 2002 12:11:31 +0100 (CET) Date: Wed, 16 Jan 2002 12:11:31 +0100 From: Christian Ullrich To: apsfilter-help@apsfilter.org Cc: Garance A Drosihn , desmo@bandwidth.org, freebsd-stable@freebsd.org Subject: Re: 4.4R: if: doesn't get started when getting remote print job (Re: apsfilter doesn't work on server) Message-ID: <20020116111131.GA19728@christian.chrullrich.de> References: <20020115062456.GA13349@christian.chrullrich.de> <20020115151846.GA14953@christian.chrullrich.de> <20020115213522.GA15920@christian.chrullrich.de> <20020116091030.GA16535@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020116091030.GA16535@titan.klemm.gtn.com> User-Agent: Mutt/1.3.25i X-Current-Uptime: 7 d, 12:51:40 h Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Andreas Klemm wrote on Wednesday, 2002-01-16: > On Tue, Jan 15, 2002 at 10:35:22PM +0100, Christian Ullrich wrote: > > Warning: The following is _very_ detailed. It took me three hours > > to do it all and write it down. If there is _any_ information > > missing, please do not hesitate to ask. [...] > > 6. I built apsfilter-7.2.1, with the following options enabled: > > - A4 - A4 papersize > > - GS_NO_X11 - Postscript for non-PS printer, no X11 > > - GS_PDF_CRYPT - print encrypted PDF files using gs > > - PSUTILS - for pseudo duplex printing + paper handling > > - A2PS - ASCII files in different styles/orientation > > - DVIPS - TeX DVI files > > - HTML2PS - HTML documents > > - TROFF - Troff documents > > - BZIP2 - print bunzip2 compressed documents > > On the first attempt to "make install" apsfilter, I was told that > > the file /usr/local/etc/apsfilter existed. It was a symbolic link > > to /etc/apsfilter, which I had renamed in step 2. I removed the > > link and installed again. This time it worked fine. > > If you had updated the ports collection you would have used > apsfilter 7.2.1, which includes a fix for that by using > ln -sf ... I did update the ports collection, via cvsup. And I built and installed apsfilter 7.2.1. I just noticed that I forgot to "pkg_delete" version 7.1.1 before installing the new version, but as /usr/local/share/apsfilter/bin/apsfilter is: # $ApsCVS: src/apsfilter/bin/apsfilter.in,v 1.212.2.7 2002/01/09 21:06:30 andrea s Exp $ ############################################################################## # # apsfilter 7.2.1 # --------- I don't think that I'm still running the old version. > > 10. I installed that configuration under the name "ascii" and finished > > the SETUP script for the time being. > > > > This is the generated printcap (comments stripped): > > > > ascii|PS;r=600x600;q=medium;c=gray;p=a4;m=ascii:\ > > :lp=/dev/lpt0:\ > > :if=/etc/apsfilter/basedir/bin/apsfilter:\ > > :sd=/var/spool/lpd/ascii:\ > > :lf=/var/spool/lpd/ascii/log:\ > > :af=/var/spool/lpd/ascii/acct:\ > > :mx#0:\ > > :sh: > > Why you named it ASCII ? I wanted to save "lp" for a future configuration with automatic file type recognition, so that there would no random bits of old configurations lying around. > > 11. I started LPRng and found this line in syslog: > > > > Jan 15 20:41:02 ser1 checkpc[73259]: ascii: Checkwrite: fcntl F_SETFL > > of '/dev/lpt0' failed - Operation not supported by device > > > > Similar output was generated by calling "checkpc -f". But sending > > data to the printer was never the problem, so I'm currently not > > much concerned about it. > > Ask FreeBSD port maintainer, LPRng people. Of course. There is a lot of possibly unnecessary information in my mail, but I gave as much detail as possible. > > 19. Now for the client. Using SuSE's YaST configuration tool, > > I configured a simple network printer: > > > > ascii|remote printer on ser1:\ > > :sd=/var/spool/lpd/ascii:\ > > :rm=ser1:\ > > :rp=ascii:\ > > :bk:sh:mx#0: > > > > 20. "lpq -Pascii" on the client showed that the printer status was > > accessible. > > > > 21. "lpr -Pascii /etc/printcap" from the client produced the usual > > staircased text. Even an "ASCII only" apsfilter configuration > > on the server didn't work, and still doesn't. Because the printer > > stopped blinking, I'm sure that it got the text file directly, > > without apsfilter in between. > > > > I'm out of ideas. What about you out there? > > As workaround install apsfilter on the client, to compute print > data on the client, so that the correct data stream enters the > server. Well, that's just what I wanted to avoid in the first place. If I had considered that the optimal solution, I would not have started messing with it. I will do it that way again for the time being, though. > is a bug in 4.4-RELEASE. Well now you installed LPRng on FreeBSD > which normally is not necessary, since FreeBSD's lpd is not so > "stock" and limited as all the other un-fixed versions around. Well, when it didn't work with BSD lpd, I grasped for any straw. > Concerning lpd I'd remove the LPRng port if Garant has replied > to you and I'm sure, that he will be helpful to you. But then > you should re-install lpd from /usr/src, that shouldn't be a problem > with FreeBSD ... No, that shouldn't be too hard. > Additionally you could then try to update to 4.5-RC, since then you > can both work on the latest and greatest -STABLE version of FreeBSD, > so that there every bug is shaken out ... > > And I remember people have merged something from -current into the > printing subsystem, maybe this already helped. > > And please use apsfilter 7.2.1. I did. I really did. Thanks for your answer no. 1. -- Christian Ullrich Registrierter Linux-User #125183 "Deliver." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 3:12:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mout02.kundenserver.de (mout02.kundenserver.de [195.20.224.133]) by hub.freebsd.org (Postfix) with ESMTP id 5ED9937B427 for ; Wed, 16 Jan 2002 03:11:51 -0800 (PST) Received: from [172.19.20.61] (helo=mrvdomng0.kundenserver.de) by mout02.kundenserver.de with esmtp (Exim 2.12 #2) id 16Qnyv-00009z-00; Wed, 16 Jan 2002 12:11:49 +0100 Received: from [217.230.78.245] (helo=ser1.chrullrich.de) by mrvdomng0.kundenserver.de with esmtp (Exim 3.22 #2) id 16Qnyu-0004G7-00; Wed, 16 Jan 2002 12:11:48 +0100 Received: from christian.chrullrich.de (christian.chrullrich.de [192.168.0.2]) by ser1.chrullrich.de (Postfix) with ESMTP id B0FD216F; Wed, 16 Jan 2002 12:11:46 +0100 (CET) Received: by christian.chrullrich.de (Postfix on SuSE Linux 7.3 (i386), from userid 1000) id B3A8E45; Wed, 16 Jan 2002 12:11:45 +0100 (CET) Date: Wed, 16 Jan 2002 12:11:45 +0100 From: Christian Ullrich To: apsfilter-help@apsfilter.org Cc: Garance A Drosihn , desmo@bandwidth.org, freebsd-stable@freebsd.org Subject: Re: 4.4R: if: doesn't get started when getting remote print job (Re: apsfilter doesn't work on server) Message-ID: <20020116111145.GB19728@christian.chrullrich.de> References: <20020115062456.GA13349@christian.chrullrich.de> <20020115151846.GA14953@christian.chrullrich.de> <20020115213522.GA15920@christian.chrullrich.de> <20020116091030.GA16535@titan.klemm.gtn.com> <20020116093350.GB18106@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020116093350.GB18106@titan.klemm.gtn.com> User-Agent: Mutt/1.3.25i X-Current-Uptime: 7 d, 12:51:40 h Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Andreas Klemm schrieb am Mittwoch, 2002-01-16: > And please summarize in your mail the exact FreeBSD version. FreeBSD ser1.chrullrich.de 4.4-RELEASE FreeBSD 4.4-RELEASE #2: Mon Oct 22 18:13:05 CEST 2001 Thanks for your answer no. 3. -- Christian Ullrich Registrierter Linux-User #125183 "Deliver." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 4:24: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sbk-gw.sibnet.ru (sbk-gw.sibnet.ru [217.70.96.146]) by hub.freebsd.org (Postfix) with ESMTP id 92A9D37B400 for ; Wed, 16 Jan 2002 04:23:56 -0800 (PST) Received: from localhost (stranger@localhost) by sbk-gw.sibnet.ru (8.11.6/8.11.6) with ESMTP id g0GCNhu06014; Wed, 16 Jan 2002 18:23:44 +0600 (NOVT) (envelope-from stranger@sberbank.sibnet.ru) Date: Wed, 16 Jan 2002 18:23:43 +0600 (NOVT) From: "Maxim M. Kazachek" X-X-Sender: stranger@sbk-gw.sibnet.ru To: Brady Montz Cc: freebsd-stable@FreeBSD.ORG Subject: Re: VIA crahes - solved (it seems)! In-Reply-To: <200201152200.g0FM0lT28843@mail.hydrologue.com> Message-ID: <20020116182138.R5997-100000@sbk-gw.sibnet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've got a problems on VIA based Lucky Star 5MVP3 motherboard with AMD K6-2 233 overclocked to 350 by bus. When I've switched back to 233 the problem went away. WinME/Win2K worked fine on 350MHz Sincerely, Maxim M. Kazachek mailto:stranger@sberbank.sibnet.ru mailto:stranger@fpm.ami.nstu.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 4:27:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtp015.mail.yahoo.com (smtp015.mail.yahoo.com [216.136.173.59]) by hub.freebsd.org (Postfix) with SMTP id 8EA2537B400 for ; Wed, 16 Jan 2002 04:27:14 -0800 (PST) Received: from unknown (HELO mlevy) (12.27.148.78) by smtp.mail.vip.sc5.yahoo.com with SMTP; 16 Jan 2002 12:27:14 -0000 Message-ID: <00e001c19e89$89a14400$fd6e34c6@mlevy> From: "Barazani" To: References: <20020116.172408.41714577.ishizuka@ish.org> Subject: Smbfs not creating nsmb* /dev entry and looks for conf file in /etc ? Date: Wed, 16 Jan 2002 07:30:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All , I have a box which i cvsup'd the stable-source to [root@freebsd:root]->uname -a FreeBSD freebsd 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #0: Thu Dec 20 17:16:53 EST 2001 root@freebsd:/usr/src/sys/compile/NEW i386 [root@freebsd:root]-> any way i tried to compile smbfs to the kernel and mount some win shares and ran into some problems . 1.mount_smbfs looks for the nsmb.conf in /etc/ and not /usr/local/etc 2./dev/nsmb0 is not created by default ( had to go to /usr/src/contrib/smbfs and run make configure ;make makedev ) is this the procedure or is something broken ? thanks barazani "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 5:39:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mongrel.pacific.net.au (mongrel.pacific.net.au [61.8.0.107]) by hub.freebsd.org (Postfix) with ESMTP id D43AC37B402 for ; Wed, 16 Jan 2002 05:39:51 -0800 (PST) Received: from dungeon.home (ppp181.dyn248.pacific.net.au [203.143.248.181]) by mongrel.pacific.net.au (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA17628; Thu, 17 Jan 2002 00:32:45 +1100 X-Authentication-Warning: mongrel.pacific.net.au: Host ppp181.dyn248.pacific.net.au [203.143.248.181] claimed to be dungeon.home Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.11.3/8.11.1) with ESMTP id g0GDiKb16672; Wed, 16 Jan 2002 23:44:20 +1000 (EST) (envelope-from mckay) Message-Id: <200201161344.g0GDiKb16672@dungeon.home> To: Darryl Okahata Cc: stable@freebsd.org, mckay@thehub.com.au, Brady Montz Subject: Re: VIA crahes - solved (it seems)! References: <200201152314.g0FNEvn29022@mail.hydrologue.com> <200201151952.LAA02454@mina.soco.agilent.com> In-Reply-To: <200201151952.LAA02454@mina.soco.agilent.com> from Darryl Okahata at "Tue, 15 Jan 2002 19:52:04 +0000" Date: Wed, 16 Jan 2002 23:44:20 +1000 From: Stephen McKay Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 15th January 2002, Darryl Okahata wrote: > Also, I've looked over your postings for the past month, and I >can't tell if you've tried the obvious: do you have a known good power >supply? Some motherboards need really clean power, and AMD chips are >power hogs. Borderline power supplies can easily cause the symptoms >you're seeing. I can attest that borderline power supplies can cause a lot of mysterious trouble, and that the "borderline" has moved in recent times. My Athlon 1.2GHz started acting just slightly weird when I added a better video card (Geforce2 GTS actually). I got sick of that card and added a more powerful all-singing all-dancing ASUS video card (Geforce2 GTS Pro with lots of ram, TV in, TV out, all that jazz). When I did this, very weird things happened, including complete boot failures. Replacing the power supply (that had "300W" written on it) with an Enermax 430W seemed over the top to the sales droid, but fixed 100% of my problems. Well worth the expense, though I would have tried a less powerful version if the store had had, say, the 350W version. If weird things are happening and your RAM checks out (in another machine) then you could be the victim of a substandard power supply. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 5:40:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from corpmail.mondus.com (gateway.mondus.com [193.132.141.145]) by hub.freebsd.org (Postfix) with ESMTP id BF14337B41A for ; Wed, 16 Jan 2002 05:40:07 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: PCI Wavelan cards under 4.4 Date: Wed, 16 Jan 2002 13:36:08 -0000 Message-ID: <851336E23970B348A23A1A46DB20D64F0F99E9@ukmail02.internal.mondus.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PCI Wavelan cards under 4.4 Thread-Index: AcGeksFt4FvHblQ8SEST5crEIdZ9uw== From: "Richard Shaw" To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm attempting to get a 3com wavelan 3crwe777a PCI card working under = 4.4 Release. I've trawled for posts on this and have found plenty = mentioning how easy it was to get the ISA version working, but have had = no solid confirmations that the PCI one will work. There have been = mumblings of incompatibilities with some motherboards, talk of support = coming soon but nothing definite. Has anyone set one up, or managed to = get one working ? Many thanks, Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 5:42:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from corpmail.mondus.com (gateway.mondus.com [193.132.141.145]) by hub.freebsd.org (Postfix) with ESMTP id 97F0937B425 for ; Wed, 16 Jan 2002 05:42:50 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: PCI Wavelan cards under 4.4 Date: Wed, 16 Jan 2002 13:42:49 -0000 Message-ID: <851336E23970B348A23A1A46DB20D64F0F99EA@ukmail02.internal.mondus.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PCI Wavelan cards under 4.4 Thread-Index: AcGek7A+S0S/O2+AREKimWZWKVFIqQ== From: "Richard Shaw" To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm attempting to get a 3com wavelan 3crwe777a PCI card working under = 4.4 Release. I've trawled for posts on this and have found plenty = mentioning how easy it was to get the ISA version working, but have had = no solid confirmations that the PCI one will work. There have been = mumblings of incompatibilities with some motherboards, talk of support = coming soon but nothing definite. Has anyone set one up, or managed to = get one working ? Many thanks, Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 5:53:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mailrelay.netcologne.de (mailrelay.netcologne.de [194.8.194.96]) by hub.freebsd.org (Postfix) with ESMTP id 1553837B41C for ; Wed, 16 Jan 2002 05:53:34 -0800 (PST) Received: from localhost (xdsl-213-168-108-45.netcologne.de [213.168.108.45]) by mailrelay.netcologne.de (8.11.6/8.11.6) with ESMTP id g0GDrTY11829 for ; Wed, 16 Jan 2002 14:53:29 +0100 (MET) Received: (qmail 462 invoked by uid 1001); 16 Jan 2002 13:53:18 -0000 Date: Wed, 16 Jan 2002 14:53:18 +0100 From: Thomas Seck To: stable@FreeBSD.ORG Subject: Re: what's vnlru? Message-ID: <20020116135318.GA427@laurel.seck.home> Mail-Followup-To: stable@FreeBSD.ORG References: <200201151618468.SM01176@141.com> <200201160101.g0G117r64693@apollo.backplane.com> <20020116104904.A2800@shikima.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020116104904.A2800@shikima.mine.nu> User-Agent: Mutt/1.3.24i Organization: private site in Germany X-PGP-KeyID: DF46EE05 X-PGP-Fingerprint: A38F AE66 6B11 6EB9 5D1A B67D 2444 2FE1 DF46 EE05 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG # Rasputin (rasputin@submonkey.net): [vnlru] > Thansk for the overview - it's not a performance issue, I just checked > another fairly recent (4.5 pre) BSD box and didn't see it, > so thought I'd better check it out. > > [ Is this the sort of thing that should go into UPDATING? ] I'd vote for a short description in the release notes (I did not overlook them for a few months, so I do not know whether Bruce Mah picked it up already). --Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 6:33:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [128.29.154.90]) by hub.freebsd.org (Postfix) with ESMTP id 0EF9537B404 for ; Wed, 16 Jan 2002 06:33:30 -0800 (PST) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g0GEXRc08359; Wed, 16 Jan 2002 09:33:27 -0500 (EST) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g0GEXOi14237; Wed, 16 Jan 2002 09:33:24 -0500 (EST) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub1.mitre.org with SMTP id 8864794; Wed, 16 Jan 2002 09:33:24 -0500 Message-ID: <3C458F36.659269C5@mitre.org> Date: Wed, 16 Jan 2002 09:33:26 -0500 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Shaw Cc: Freebsd-stable@freebsd.org Subject: Re: PCI Wavelan cards under 4.4 References: <851336E23970B348A23A1A46DB20D64F0F99E9@ukmail02.internal.mondus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Richard Shaw wrote: > > Hi, > > I'm attempting to get a 3com wavelan 3crwe777a PCI card working under 4.4 Release. I've trawled for posts on this and have found plenty mentioning how easy it was to get the ISA version working, but have had no solid confirmations that the PCI one will work. There have been mumblings of incompatibilities with some motherboards, talk of support coming soon but nothing definite. Has anyone set one up, or managed to get one working ? I was under the impression the PCI versions won't work until FreeBSD 5 because the PCI version effectivly requires newcard. The "PCI" card here is really just a PCCARD controller on an PCI card that you plug an off-the-shelf Wavelan/Orinoco card into. OTOH, the ISA version works fine (although the controllers use a slightly unusual memory address IIRC). -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 7: 1:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tensor.xs4all.nl (tensor.xs4all.nl [213.84.53.200]) by hub.freebsd.org (Postfix) with ESMTP id 9D22437B404 for ; Wed, 16 Jan 2002 07:01:48 -0800 (PST) Received: from kilgore.xs4all.nl (kilgore.xs4all.nl [192.168.1.3]) by tensor.xs4all.nl (Postfix) with ESMTP id F3BA154C9; Wed, 16 Jan 2002 16:01:46 +0100 (CET) Date: Wed, 16 Jan 2002 16:01:18 +0100 From: Dimitry Andric X-Mailer: The Bat! (v1.54 Beta/29) Business Reply-To: Dimitry Andric X-Priority: 3 (Normal) Message-ID: <1258994333.20020116160118@xs4all.nl> To: Barazani Cc: freebsd-stable@freebsd.org Subject: Re: Smbfs not creating nsmb* /dev entry and looks for conf file in /etc ? In-Reply-To: <00e001c19e89$89a14400$fd6e34c6@mlevy> References: <20020116.172408.41714577.ishizuka@ish.org> <00e001c19e89$89a14400$fd6e34c6@mlevy> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/16/2002 at 13:30:08 Barazani wrote: B> 1.mount_smbfs looks for the nsmb.conf in /etc/ and not /usr/local/etc B> 2./dev/nsmb0 is not created by default ( had to go to /usr/src/contrib/smbfs Both of these problems were reported and fixed some time ago. Please cvsup and rebuild, that should fix it. See the following PRs: http://www.freebsd.org/cgi/query-pr.cgi?pr=33065 http://www.freebsd.org/cgi/query-pr.cgi?pr=33068 Cheers, - -- Dimitry Andric PGP Key: http://www.xs4all.nl/~dim/dim.asc Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3 Lbh ner abj va ivbyngvba bs gur QZPN -----BEGIN PGP SIGNATURE----- Version: PGP 6.5i Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBPEWHt7BeowouIJajEQJVFgCdE44Zev6u6+Xph53F4vtr/G3/VTgAoPoi T2gKZIHIMUx+RCt++CJuT0F6 =CFvZ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 7:14:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tl.kom.tuwien.ac.at (tl.kom.tuwien.ac.at [128.130.34.35]) by hub.freebsd.org (Postfix) with ESMTP id E760C37B400 for ; Wed, 16 Jan 2002 07:14:37 -0800 (PST) Received: (from tilman@localhost) by tl.kom.tuwien.ac.at (8.11.6/8.11.6) id g0GFIBV39814; Wed, 16 Jan 2002 16:18:11 +0100 (CET) (envelope-from tilman@arved.de) X-Authentication-Warning: tl.kom.tuwien.ac.at: tilman set sender to tilman@arved.de using -f Subject: Re: PCI Wavelan cards under 4.4 From: Tilman Linneweh To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-VDeBpE7LmVWQ2Z2XdYTL" X-Mailer: Evolution/1.0.1 Date: 16 Jan 2002 16:18:11 +0100 Message-Id: <1011194291.18831.326.camel@tl.kom.tuwien.ac.at> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-VDeBpE7LmVWQ2Z2XdYTL Content-Type: text/plain Content-Transfer-Encoding: quoted-printable * Jason Andresen wrote:=20 >I was under the impression the PCI versions won't work until FreeBSD 5 >because the PCI version effectivly requires newcard. The "PCI" card >here is really just a PCCARD controller on an PCI card that you >plug an off-the-shelf Wavelan/Orinoco card into. I don't know what "newcard" ist. But I have got a PCI-PCMCIA Adaptor with an Avaya Wireless Card running under 4.4PRELEASE (*hmm i should update this machine soon*) Regards arved --=-VDeBpE7LmVWQ2Z2XdYTL Content-Type: application/pgp-signature; name=signature.asc Content-Description: Dies ist ein digital signierter Nachrichtenteil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQA8RZmzEH3do0kMxDoRAoSiAJ9uyUAdqrLjieslNmwrSKhk9ukmzACfbNLI Qtr06/e3M2k36eTQJ5boAO0= =OqK3 -----END PGP SIGNATURE----- --=-VDeBpE7LmVWQ2Z2XdYTL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 7:18: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from spitfire.velocet.net (spitfire.velocet.net [216.138.223.227]) by hub.freebsd.org (Postfix) with ESMTP id 34B4237B405 for ; Wed, 16 Jan 2002 07:17:57 -0800 (PST) Received: from nomad.tor.lets.net (H74.C220.tor.velocet.net [216.138.220.74]) by spitfire.velocet.net (Postfix) with SMTP id BAD5A44AAE1 for ; Wed, 16 Jan 2002 15:17:51 +0000 (GMT) Received: (qmail 636 invoked by uid 1001); 16 Jan 2002 15:12:13 -0000 Date: Wed, 16 Jan 2002 10:12:12 -0500 From: Steve Shorter To: freebsd-stable@freebsd.org Subject: "server not responding" / "is alive again" NFS tunables Message-ID: <20020116101212.A610@nomad.lets.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy! I have a dedicated NFS server with 16 nfsd's running, connected to SCSI raid/softupdates and good network connectivity/switching. Under moderate or even sometimes light load the clients(7 of them) log messages nfs server 192.168.10.2:/mnt: not responding nfs server 192.168.10.2:/mnt: is alive again several times per minute. They always have the same timestamp. Performance is not noticably impaired, but I am wondering if this situation will eventually become a performance barrier as the system ramps up to full production, if the above log messages mean that packets must be delayed or retransmitted. I have experimented with both udp/tcp mounts with various rw sizes ranging from 8192 - 32768. tcp with rw=32768 was the worst case wrt above, and am currently using udp mounts with default rw. Running 8 or 16 nfsd gives no noticable difference wrt the above either. I can find no issues on the server side, and was wondering if there is a timeout threshold on the client side that is triggering the messages/condition and whether adjusting the compile time tunables in sys/nfs/nfs.h can aleviate the problem(if it even is a problem). The server is 4.5-PRE, the clients are 4.4-RELEASE. I know that there have been a log of NFS changes in 4.5, but testing 4.5 on the clients is problematic. Do any of those changes affect the above? So which variable(s) in nfs.h affect the client side and contribute to the server timeout situation. Or are there any other suggestions? Here are the variables in nfs.h(4.5-RC) for your amusement. Thanks /* * Tunable constants for nfs */ #define NFS_MAXIOVEC 34 #define NFS_TICKINTVL 5 /* Desired time for a tick (msec) */ #define NFS_HZ (hz / nfs_ticks) /* Ticks/sec */ #define NFS_TIMEO (1 * NFS_HZ) /* Default timeout = 1 second */ #define NFS_MINTIMEO (1 * NFS_HZ) /* Min timeout to use */ #define NFS_MAXTIMEO (60 * NFS_HZ) /* Max timeout to backoff to */ #define NFS_MINIDEMTIMEO (5 * NFS_HZ) /* Min timeout for non-idempotent ops*/ #define NFS_MAXREXMIT 100 /* Stop counting after this many */ #define NFS_MAXWINDOW 1024 /* Max number of outstanding requests */ #define NFS_RETRANS 10 /* Num of retrans for soft mounts */ #define NFS_MAXGRPS 16 /* Max. size of groups list */ #ifndef NFS_MINATTRTIMO #define NFS_MINATTRTIMO 3 /* VREG attrib cache timeout in sec */ #endif #ifndef NFS_MAXATTRTIMO #define NFS_MAXATTRTIMO 60 #endif #ifndef NFS_MINDIRATTRTIMO #define NFS_MINDIRATTRTIMO 30 /* VDIR attrib cache timeout in sec */ #endif #ifndef NFS_MAXDIRATTRTIMO #define NFS_MAXDIRATTRTIMO 60 #endif #define NFS_WSIZE 8192 /* Def. write data size <= 8192 */ #define NFS_RSIZE 8192 /* Def. read data size <= 8192 */ #define NFS_READDIRSIZE 8192 /* Def. readdir size */ #define NFS_DEFRAHEAD 1 /* Def. read ahead # blocks */ #define NFS_MAXRAHEAD 4 /* Max. read ahead # blocks */ #define NFS_MAXUIDHASH 64 /* Max. # of hashed uid entries/mp */ #define NFS_MAXASYNCDAEMON 20 /* Max. number async_daemons runnable */ #define NFS_MAXGATHERDELAY 100 /* Max. write gather delay (msec) */ #ifndef NFS_GATHERDELAY #define NFS_GATHERDELAY 10 /* Default write gather delay (msec) */ #endif #define NFS_DIRBLKSIZ 4096 /* Must be a multiple of DIRBLKSIZ */ #ifdef _KERNEL #define DIRBLKSIZ 512 /* XXX we used to use ufs's DIRBLKSIZ */ #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 8:39:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by hub.freebsd.org (Postfix) with ESMTP id 4EF5E37B402 for ; Wed, 16 Jan 2002 08:39:37 -0800 (PST) Received: from [24.49.144.68] (helo=bloodberry) by hobbiton.shire.net with asmtp (Exim 3.22 #6) id 16Qt0g-000F5I-00 for freebsd-stable@freebsd.org; Wed, 16 Jan 2002 09:33:58 -0700 Date: Wed, 16 Jan 2002 11:39:25 -0500 Mime-Version: 1.0 (Apple Message framework v475) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: thread issues fixed in 4.5? From: Seiko Leigh To: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <99D5EFF6-0A9F-11D6-9F41-000502EDE760@leigh.org> X-Mailer: Apple Mail (2.475) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I have been searching the archives for answers on this and have not found anything. I am running 4.2 currently and amplanning on moving to 4.5 FreeBSD. I also use the Roxen webserver (www.roxen.com) and it has a problem with "locking up" when it is compiled to use threads. This happens only when CGIs are being used, and not always, just on some CGI invocations (regardless of the actual CGI). Also, the Apache 2 documentation says that on FreeBSD it uses the old forking method rather than the new Apache threaded model because FreeBSD has some thread problems. It kind of sounds like the source for Apache and Roxen 's problems are related based on the descriptions. I asked about whether a new Roxen release fixed this problem and here was an asnwer " >Any hints or solutions to this problem??? I had hoped that this was >finally solved in 2.2 but it seems to not be. Non of my other thread >aware software seems to have any sorts of problems on FBSD, only >pike/roxen. The main problem is that almost no other thread-using program fork/exec's other programs. Most of the time they're self-contained. Roxen's sort of unique in that regard, and it ends up stressing a part of the threads code that doesn't get used very often. It doesn't make it any easier that the only way to reliably reproduce the bug is to do a "make verify" on a full Pike build; a build takes quite a long time. " Is the Apache 2 problem with FreeBSD threads fixed in the -stable (or to be 4.5) releases? I am trying to plan my new version strategies for a lot of different software pieces I use. thanks Chad chad@shire.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 8:47:38 2002 Delivered-To: freebsd-stable@freebsd.org Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by hub.freebsd.org (Postfix) with ESMTP id 3413D37B405 for ; Wed, 16 Jan 2002 08:47:34 -0800 (PST) Received: from [24.49.144.68] (helo=bloodberry) by hobbiton.shire.net with asmtp (Exim 3.22 #6) id 16Qt8N-000F6j-00 for freebsd-stable@freebsd.org; Wed, 16 Jan 2002 09:41:55 -0700 Date: Wed, 16 Jan 2002 11:47:30 -0500 Mime-Version: 1.0 (Apple Message framework v475) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: thread issues fixed in 4.5? From: Chad Leigh -- Shire.Net LLC To: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.475) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I have been searching the archives for answers on this and have not found anything. I am running 4.2 currently and amplanning on moving to 4.5 FreeBSD. I also use the Roxen webserver (www.roxen.com) and it has a problem with "locking up" when it is compiled to use threads. This happens only when CGIs are being used, and not always, just on some CGI invocations (regardless of the actual CGI). Also, the Apache 2 documentation says that on FreeBSD it uses the old forking method rather than the new Apache threaded model because FreeBSD has some thread problems. It kind of sounds like the source for Apache and Roxen 's problems are related based on the descriptions. I asked about whether a new Roxen release fixed this problem and here was an asnwer " >Any hints or solutions to this problem??? I had hoped that this was >finally solved in 2.2 but it seems to not be. Non of my other thread >aware software seems to have any sorts of problems on FBSD, only >pike/roxen. The main problem is that almost no other thread-using program fork/exec's other programs. Most of the time they're self-contained. Roxen's sort of unique in that regard, and it ends up stressing a part of the threads code that doesn't get used very often. It doesn't make it any easier that the only way to reliably reproduce the bug is to do a "make verify" on a full Pike build; a build takes quite a long time. " Is the Apache 2 problem with FreeBSD threads fixed in the -stable (or to be 4.5) releases? I am trying to plan my new version strategies for a lot of different software pieces I use. thanks Chad chad@shire.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 8:51:43 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 4707437B402 for ; Wed, 16 Jan 2002 08:51:40 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g0GGpd207059 for ; Wed, 16 Jan 2002 08:51:39 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g0GGpdK49758; Wed, 16 Jan 2002 08:51:39 -0800 (PST) (envelope-from jdp) Date: Wed, 16 Jan 2002 08:51:39 -0800 (PST) Message-Id: <200201161651.g0GGpdK49758@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Subject: Re: Port cvsup problem... (Solved) In-Reply-To: <20020115190027.A5224@infocom.kh.ua> References: <20020115190027.A5224@infocom.kh.ua> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020115190027.A5224@infocom.kh.ua>, Aleksey Ovcharenko wrote: > Than trying to update doc's tree via cvs I got: > > -------------------------------------------------------------- > >>> Running /usr/local/bin/cvsup > -------------------------------------------------------------- > Parsing supfile "/root/cvsup/doc-supfile" > Connecting to cvsup.uk.FreeBSD.org > Connected to cvsup.uk.FreeBSD.org > Server software version: SNAP_16_1e > Negotiating file attribute support > Exchanging collection information > Establishing multiplexed-mode data connection > ChannelMux.Accept failed: Connection closed > *** Error code 1 Aleksey sent me a bunch more information about this, and I know what the problem is. If you install ezm3 without first removing pm3, you end up with left-over Modula-3 shared libraries from the pm3 port. These get used instead of the proper static libraries which come with ezm3. There are some incompatibilities between the libraries, and these cause the problems people are seeing. If you are seeing problems with cvsup-16.1f, run "ldd /usr/local/bin/cvsup". It should not list any Modula-3 libraries. You can recognize them because they are all under "/usr/local/lib/m3". The solution is: pkg_delete all pm3-* ports, the ezm3 port, and the cvsup port. Then "rm -rf /usr/local/lib/m3" if it is present. Then rebuild and install the cvsup port. I will see if I can fix the ezm3 port so that it ignores left-over Modula-3 shared libraries. No guarantees, though. To be safe you have to pkg_delete all other Modula-3 ports before installing it. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 8:57:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id D9F9637B400 for ; Wed, 16 Jan 2002 08:57:16 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id 57D4F2DE4; Wed, 16 Jan 2002 09:57:16 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id 81ABFD9; Wed, 16 Jan 2002 09:57:15 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id IAA10812; Wed, 16 Jan 2002 08:57:14 -0800 (PST) Message-Id: <200201161657.IAA10812@mina.soco.agilent.com> To: Stephen McKay Cc: stable@freebsd.org, Brady Montz Subject: Re: VIA crahes - solved (it seems)! Reply-To: Darryl Okahata In-Reply-To: Your message of "Wed, 16 Jan 2002 23:44:20 +1000." <200201161344.g0GDiKb16672@dungeon.home> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Wed, 16 Jan 2002 08:57:14 -0800 From: Darryl Okahata Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Stephen McKay wrote: > I can attest that borderline power supplies can cause a lot of mysterious > trouble, and that the "borderline" has moved in recent times. That's definitely true. Not only has the power requirements of CPUs skyrocketed, but some video cards are now starting to suck up obscene amounts of power, too (as you've found out). Before, you could just use a power supply's overall/total wattage rating. Today, you often have to look at the amount of current the 3.3V line can supply, as it's quite possible that, while a power supply's total wattage may be more than adequate, the power supply may not be able to supply sufficient current on the 3.3V line for a given CPU/speed. In the case of Athlons, getting an AMD-approved power supply for a particular speed CPU should be enough, but may not always be. PCI cards can also suck power from the 3.3V line, which could (in theory, as I don't know of any such PCI cards, offhand) make an AMD-approved power supply inadequate. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 9:25: 8 2002 Delivered-To: freebsd-stable@freebsd.org Received: from patrocles.silby.com (d153.as1.nwbl0.wi.voyager.net [169.207.130.219]) by hub.freebsd.org (Postfix) with ESMTP id 5BF6137B416 for ; Wed, 16 Jan 2002 09:25:01 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g0GBSSn91515 for ; Wed, 16 Jan 2002 11:28:28 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Wed, 16 Jan 2002 11:28:28 +0000 (GMT) From: Mike Silbersack To: freebsd-stable@freebsd.org Subject: Need help from samba/linux users Message-ID: <20020116112211.W91477-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This may sound like quite a silly request, but it's serious. I'm trying to figure out what's going wrong with samba 2.2.2 on freebsd, and I need some debug from samba 2.2.2 on a linux box for comparison. If you happen to have a linux box available to you, please do the following: - Install samba 2.2.2 - rm /var/log/log.smbd (I don't want old log files) - Set the following options in smb.conf: max log size = 0 - Just to ensure that the log doesn't get truncated debuglevel = 10 - So we have all the information available - Start up samba, establish a few connections, run some copies to / from the machine. - Send me a copy of your log.smbd (gzip'd, please!) I do not need the host-specific logfile. Your help is appreciated. Thanks, Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 9:40:43 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id A0D0C37B404 for ; Wed, 16 Jan 2002 09:40:40 -0800 (PST) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id 546065D32; Wed, 16 Jan 2002 09:40:40 -0800 (PST) To: "Maxim M. Kazachek" Cc: Brady Montz , freebsd-stable@FreeBSD.ORG Subject: Re: VIA crahes - solved (it seems)! In-reply-to: Your message of "Wed, 16 Jan 2002 18:23:43 +0600." <20020116182138.R5997-100000@sbk-gw.sibnet.ru> Date: Wed, 16 Jan 2002 09:40:40 -0800 From: "Kevin Oberman" Message-Id: <20020116174040.546065D32@ptavv.es.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Wed, 16 Jan 2002 18:23:43 +0600 (NOVT) > From: "Maxim M. Kazachek" > Sender: owner-freebsd-stable@FreeBSD.ORG > > I've got a problems on VIA based Lucky Star 5MVP3 motherboard with > AMD K6-2 233 overclocked to 350 by bus. When I've switched back to 233 the > problem went away. WinME/Win2K worked fine on 350MHz You are very brave to over-clock a K6, although the 233 MHz models were not too bad. But, in general, it's been widely reported (and I have personal confirmation) that over-clocking K^ chips is very risky. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 9:46:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 8986637B400 for ; Wed, 16 Jan 2002 09:46:46 -0800 (PST) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id 520EE5D13; Wed, 16 Jan 2002 09:46:46 -0800 (PST) To: Sam Drinkard Cc: freebsd-stable@freebsd.org Subject: Re: Static files In-reply-to: Your message of "Tue, 15 Jan 2002 16:59:43 EST." <3C44A64F.67DCC61@vortex.wa4phy.net> Date: Wed, 16 Jan 2002 09:46:46 -0800 From: "Kevin Oberman" Message-Id: <20020116174646.520EE5D13@ptavv.es.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Tue, 15 Jan 2002 16:59:43 -0500 > From: Sam Drinkard > Sender: owner-freebsd-stable@FreeBSD.ORG > > Most likely inappropriate subject line, but are there parts of the > current -stable tree that are now NOT being worked on? Like the "base" > FreeBSD system as a whole, no ports (or the port tree itself) but just a > bare OS? Even though I've been following -stable, I gather things are > still being debugged .. Which leads me to the real question, how often > should one update from sources? I'm sure there are many a variable in > that, but if something is working fine, why upgrade unless you happen to > need the latest fix for a multi-frama-snickafoo-filter or whatever? Almost every significant portion of FreeBSD has someone working on it and changes are continual. You can subscribe to the cvs-all list and watch for changes you consider significant. I try to update my base system about once a week. Others do this more often and many cvsup daily. Others do it only occasionally for a specific modification. A lot depends on the time it takes to do the update. For my laptop it builds in about 3 hours, but only takes 15 minutes to install, so I could really do it every day, if I wanted to. Many newer systems with fast disks and multiple processors can significantly reduce these times. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 9:58: 2 2002 Delivered-To: freebsd-stable@freebsd.org Received: from jupiter.linuxengine.net (jupiter2.linuxengine.net [209.61.188.254]) by hub.freebsd.org (Postfix) with ESMTP id 16D0B37B417 for ; Wed, 16 Jan 2002 09:57:58 -0800 (PST) Received: from jupiterweb.commercevault.com (jupiterweb.commercevault.com [209.61.179.16] (may be forged)) by jupiter.linuxengine.net (8.11.6/8.11.0) with ESMTP id g0GHvbx01420; Wed, 16 Jan 2002 11:57:37 -0600 Date: Wed, 16 Jan 2002 11:57:33 -0600 (CST) From: John Utz X-X-Sender: To: Kevin Oberman Cc: "Maxim M. Kazachek" , Brady Montz , Subject: Re: VIA crahes - solved (it seems)! In-Reply-To: <20020116174040.546065D32@ptavv.es.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG the K6's come precooked from the factory :-) but i run my k6-II/200 at 233 or so without i'll effects. it's a pretty old piece of silicon and i think the earlier chips had more 'intel-ish' thermal safety margins. i think AMD got braver about pushing the silicon as they got more experience with the manufacturing process, so they end up *selling* the slicon rated at a more aggressive clock speed. but now i am inspired to try to bump mine to 250 and see what happens. :-) it's my home gateway box and it never runs windows. usually i know that i have been too ambitious when gcc barfs abruptly during a kernel compile... On Wed, 16 Jan 2002, Kevin Oberman wrote: > > Date: Wed, 16 Jan 2002 18:23:43 +0600 (NOVT) > > From: "Maxim M. Kazachek" > > Sender: owner-freebsd-stable@FreeBSD.ORG > > > > I've got a problems on VIA based Lucky Star 5MVP3 motherboard with > > AMD K6-2 233 overclocked to 350 by bus. When I've switched back to 233 the > > problem went away. WinME/Win2K worked fine on 350MHz > > You are very brave to over-clock a K6, although the 233 MHz models > were not too bad. But, in general, it's been widely reported (and I > have personal confirmation) that over-clocking K^ chips is very risky. > > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- John L. Utz III john@utzweb.net Idiocy is the Impulse Function in the Convolution of Life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 10:37:59 2002 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id 1940437B402 for ; Wed, 16 Jan 2002 10:37:48 -0800 (PST) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id D8D19319AF7; Wed, 16 Jan 2002 12:37:45 -0600 (CST) Date: Wed, 16 Jan 2002 12:37:45 -0600 From: "David W. Chapman Jr." To: Mike Silbersack Cc: freebsd-stable@freebsd.org Subject: Re: Need help from samba/linux users Message-ID: <20020116183745.GC34802@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: Mike Silbersack , freebsd-stable@freebsd.org References: <20020116112211.W91477-100000@patrocles.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020116112211.W91477-100000@patrocles.silby.com> User-Agent: Mutt/1.3.25i X-Operating-System: FreeBSD 4.5-RC i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 16, 2002 at 11:28:28AM +0000, Mike Silbersack wrote: > This may sound like quite a silly request, but it's serious. I'm trying > to figure out what's going wrong with samba 2.2.2 on freebsd, and I need > some debug from samba 2.2.2 on a linux box for comparison. If you happen > to have a linux box available to you, please do the following: > What's strange about this problem, is I cannot reproduce it that often on my FreeBSD system, but others can reproduce it very easily. -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 10:49:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from patrocles.silby.com (d153.as1.nwbl0.wi.voyager.net [169.207.130.219]) by hub.freebsd.org (Postfix) with ESMTP id 4435D37B41A for ; Wed, 16 Jan 2002 10:49:08 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g0GCqX592079; Wed, 16 Jan 2002 12:52:33 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Wed, 16 Jan 2002 12:52:33 +0000 (GMT) From: Mike Silbersack To: "David W. Chapman Jr." Cc: freebsd-stable@freebsd.org Subject: Re: Need help from samba/linux users In-Reply-To: <20020116183745.GC34802@leviathan.inethouston.net> Message-ID: <20020116125114.V91984-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 16 Jan 2002, David W. Chapman Jr. wrote: > On Wed, Jan 16, 2002 at 11:28:28AM +0000, Mike Silbersack wrote: > > This may sound like quite a silly request, but it's serious. I'm trying > > to figure out what's going wrong with samba 2.2.2 on freebsd, and I need > > some debug from samba 2.2.2 on a linux box for comparison. If you happen > > to have a linux box available to you, please do the following: > > > What's strange about this problem, is I cannot reproduce it that > often on my FreeBSD system, but others can reproduce it very easily. > > -- > David W. Chapman Jr. That's another important point. I can reproduce the problem repeatedly, but I just have one testcase. If you can repeat the samba 2.2.2 hanging problem on your setup repeatedly, please contact David and I. Perhaps we can figure out the common thread which is causing problems. Thanks, Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 10:50:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.home.nl (mail4.home.nl [213.51.129.228]) by hub.freebsd.org (Postfix) with ESMTP id 57B3937B417 for ; Wed, 16 Jan 2002 10:50:41 -0800 (PST) Received: from ws2 ([217.120.114.216]) by mail4.home.nl (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20020116185115.LYS5515.mail4.home.nl@ws2> for ; Wed, 16 Jan 2002 19:51:15 +0100 From: "Bas v.d. Wiel" To: Subject: VPN how?? Date: Wed, 16 Jan 2002 19:50:33 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Google has already brought me a lot of articles on setting up a vpn gateway. They are mostly step by step instructions for a particular situation. I'd rather understand the big picture instead of mindlessly copying shell scripts from websites. Does anyone know of a good source (book, online or other)to find detailed information from which I could learn how to set up a vpn using FreeBSD gateways? TIA Bas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 11: 5:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.nec.com (dns4.nec.com [131.241.15.4]) by hub.freebsd.org (Postfix) with ESMTP id DE83A37B404 for ; Wed, 16 Jan 2002 11:05:16 -0800 (PST) Received: from netkeeper2.sj.nec.com (netkeeper2.sj.nec.com [131.241.31.10]) by mail4.nec.com (/) with ESMTP id g0GJ5BM07553 for ; Wed, 16 Jan 2002 11:05:11 -0800 (PST) Received: from ccrl.sj.nec.com (localhost [127.0.0.1]) by netkeeper2.sj.nec.com (8.9.1a/8.9.1) with ESMTP id LAA08906 for ; Wed, 16 Jan 2002 11:05:08 -0800 (PST) Received: from localhost (hirosige [131.241.79.26]) by ccrl.sj.nec.com (8.9.3/8.9.2) with ESMTP id LAA12612 for ; Wed, 16 Jan 2002 11:05:09 -0800 (PST) Date: Wed, 16 Jan 2002 11:05:09 -0800 (PST) Message-Id: <20020116.110509.05717273.hino@ccrl.sj.nec.com> To: stable@freebsd.org Subject: 4.5-RC1: Why sshd require opie for SSH version 2? From: Koji Hino Organization: C&C Research Laboratories (CCRL), NEC USA, Inc. X-Mailer: Mew version 2.2rc1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, # I am not on the list currently, so please CC me if you need more info. I'm just testing 4.5-RC1. I installed to clear disk, and configure it minimum: ifconfig/DNS-resolver staff, activate NIS, set NIS-domainname, and add +::.. to passwd files. It seems to work well on Dell Precision 220 (http://docs.us.dell.com/docs/systems/ws220/en/ug/specs.htm), except that kernel probe message don't show fancy printing about system chipset: Intel 820. It may be so minor :-). After doing some tests, I found that connecting to this 4.5-RC1 box from other machine by OpenSSH (without RSA/DSA key, nor rhost*auth, assuming to use plain password to login), requires opie to login, though /etc/opiekeys, and /etc/skeykeys are both size 0. If I start openssh with flag '-1', which means to use OpenSSH version 1 protocol, it works fine: require plain password. I checked 4.4-RELEASE machine, and found that it works fine without '-1' flag, and even with '-2', it works. Is this an intended behavior? Some info: Client side: OS: SunOS 5.5.1 with almost latest Sun's recommended patches SSH client: openssh-3.0.1p1 SSH client config: only comments in /etc/ssh/ssh_config, no ~/.ssh/*config SSH client compile time config option: env CFLAGS=-O ./configure --prefix=/usr/Local --sysconfdir=/etc/ssh --localstatedir=/var --disable-suid-ssh --with-zlib=/usr/Local/lib --with-ssl-dir=/usr/Local/ssl --without-pam --without-rsh --with-xauth=/usr/Local/X11R6/bin/xauth --with-prngd-socket=/var/run/egd-pool --with-ipv4-default --without-bsd-auth Verbose messages from ssh: 1) ssh to 4.5-RC1 OpenSSH_3.0.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Seeding random number generator debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 1414 geteuid 1414 anon 1 debug1: Connecting to tanner [131.241.79.205] port 22. debug1: temporarily_use_uid: 1414/20 (e=1414) debug1: restore_uid debug1: temporarily_use_uid: 1414/20 (e=1414) debug1: restore_uid debug1: Connection established. debug1: identity file /home/kensett/hino/.ssh/identity type 0 debug1: identity file /home/kensett/hino/.ssh/id_rsa type -1 debug1: identity file /home/kensett/hino/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_2.9 FreeBSD localisations 20011202 debug1: match: OpenSSH_2.9 FreeBSD localisations 20011202 pat ^OpenSSH Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.0.1p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: dh_gen_key: priv key bits set: 118/256 debug1: bits set: 980/2049 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'tanner' is known and matches the DSA host key. debug1: Found key in /home/kensett/hino/.ssh/known_hosts:3 debug1: bits set: 1082/2049 debug1: ssh_dss_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password,keyboard-interactive debug1: next auth method to try is publickey debug1: try privkey: /home/kensett/hino/.ssh/id_rsa debug1: try privkey: /home/kensett/hino/.ssh/id_dsa debug1: next auth method to try is keyboard-interactive otp-md5 170 al4268 ext S/Key Password: debug1: packet_send2: adding 32 (len 17 padlen 15 extra_pad 64) debug1: authentications that can continue: publickey,password,keyboard-interactive otp-md5 453 al8647 ext S/Key Password: 2) ssh -v -1 to 4.5-RC1 OpenSSH_3.0.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Seeding random number generator debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 1414 geteuid 1414 anon 1 debug1: Connecting to tanner [131.241.79.205] port 22. debug1: temporarily_use_uid: 1414/20 (e=1414) debug1: restore_uid debug1: temporarily_use_uid: 1414/20 (e=1414) debug1: restore_uid debug1: Connection established. debug1: identity file /home/kensett/hino/.ssh/identity type 0 debug1: Remote protocol version 1.99, remote software version OpenSSH_2.9 FreeBSD localisations 20011202 debug1: match: OpenSSH_2.9 FreeBSD localisations 20011202 pat ^OpenSSH debug1: Local version string SSH-1.5-OpenSSH_3.0.1p1 debug1: Waiting for server public key. debug1: Received server public key (768 bits) and host key (1024 bits). debug1: Host 'tanner' is known and matches the RSA1 host key. debug1: Found key in /home/kensett/hino/.ssh/known_hosts:4 debug1: Encryption type: 3des debug1: Sent encrypted session key. debug1: Installing crc compensation attack detector. debug1: Received encrypted confirmation. debug1: Trying RSA authentication with key '/home/kensett/hino/.ssh/identity' debug1: Server refused our key. debug1: Doing challenge response authentication. debug1: No challenge. debug1: Doing password authentication. hino@tanner's password: 2) ssh -v to 4.4-RELEASE OpenSSH_3.0.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Seeding random number generator debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 1414 geteuid 1414 anon 1 debug1: Connecting to free1 [131.241.79.106] port 22. debug1: temporarily_use_uid: 1414/20 (e=1414) debug1: restore_uid debug1: temporarily_use_uid: 1414/20 (e=1414) debug1: restore_uid debug1: Connection established. debug1: identity file /home/kensett/hino/.ssh/identity type 0 debug1: identity file /home/kensett/hino/.ssh/id_rsa type -1 debug1: identity file /home/kensett/hino/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_2.3.0 FreeBSD localisations 20010713 debug1: match: OpenSSH_2.3.0 FreeBSD localisations 20010713 pat ^OpenSSH_2\.3\.0 Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.0.1p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client 3des-cbc hmac-md5 none debug1: kex: client->server 3des-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: dh_gen_key: priv key bits set: 204/384 debug1: bits set: 1074/2049 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'free1' is known and matches the DSA host key. debug1: Found key in /home/kensett/hino/.ssh/known_hosts:5 debug1: bits set: 1059/2049 debug1: ssh_dss_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password debug1: next auth method to try is publickey debug1: try privkey: /home/kensett/hino/.ssh/id_rsa debug1: try privkey: /home/kensett/hino/.ssh/id_dsa debug1: next auth method to try is password hino@free1's password: Best regards, ==================================================================== Koji HINO(HINO is my family name) C&C Research Laboratories, NEC USA, Inc. E-mail: hino@ccrl.sj.nec.com ---------- DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of NEC USA, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 11:13: 8 2002 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id B6A8F37B41A for ; Wed, 16 Jan 2002 11:13:03 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id g0GJD1g20808; Wed, 16 Jan 2002 11:13:01 -0800 Date: Wed, 16 Jan 2002 11:13:01 -0800 From: Brooks Davis To: Richard Shaw Cc: Freebsd-stable@FreeBSD.ORG Subject: Re: PCI Wavelan cards under 4.4 Message-ID: <20020116111301.A14632@Odin.AC.HMC.Edu> References: <851336E23970B348A23A1A46DB20D64F0F99E9@ukmail02.internal.mondus.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <851336E23970B348A23A1A46DB20D64F0F99E9@ukmail02.internal.mondus.com>; from Richard.Shaw@mondus.com on Wed, Jan 16, 2002 at 01:36:08PM -0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 16, 2002 at 01:36:08PM -0000, Richard Shaw wrote: >=20 >=20 > Hi, >=20 > I'm attempting to get a 3com wavelan 3crwe777a PCI card working under > 4.4 Release. I've trawled for posts on this and have found plenty > mentioning how easy it was to get the ISA version working, but have > had no solid confirmations that the PCI one will work. There have been > mumblings of incompatibilities with some motherboards, talk of support > coming soon but nothing definite. Has anyone set one up, or managed to > get one working ? There are two kinds of PCI cards that seem to work and at least one other that haven't been made to work. Assuming the picture on 3Com's webpage is acturate, you may be in luck. There is a large chip which appears to say PLX on it and there are two supported cards with those on them. What you need to try is adding the vendor and device ids to the pci_ids array in src/sys/i386/isa/if_wi.c and building a new kernel. If works, your in luck. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RdC9XY6L6fI4GtQRAhhNAJ46ciN0Jk+29lHbAxGYZ98DSqMh7gCg0ncI HSUJXKRIYFllZXk8sdznXEo= =g4q2 -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 11:22:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id AC6B237B433 for ; Wed, 16 Jan 2002 11:22:09 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id g0GJFiJ20989; Wed, 16 Jan 2002 11:15:44 -0800 Date: Wed, 16 Jan 2002 11:15:44 -0800 From: Brooks Davis To: Jason Andresen Cc: Richard Shaw , Freebsd-stable@FreeBSD.ORG Subject: Re: PCI Wavelan cards under 4.4 Message-ID: <20020116111544.B14632@Odin.AC.HMC.Edu> References: <851336E23970B348A23A1A46DB20D64F0F99E9@ukmail02.internal.mondus.com> <3C458F36.659269C5@mitre.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="yNb1oOkm5a9FJOVX" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3C458F36.659269C5@mitre.org>; from jandrese@mitre.org on Wed, Jan 16, 2002 at 09:33:26AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --yNb1oOkm5a9FJOVX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 16, 2002 at 09:33:26AM -0500, Jason Andresen wrote: > Richard Shaw wrote: > >=20 > > Hi, > >=20 > > I'm attempting to get a 3com wavelan 3crwe777a PCI card working > > under 4.4 Release. I've trawled for posts on this and have > > found plenty mentioning how easy it was to get the ISA version > > working, but have had no solid confirmations that the PCI one will > > work. There have been mumblings of incompatibilities with some > > motherboards, talk of support coming soon but nothing definite. Has > > anyone set one up, or managed to get one working ? > > I was under the impression the PCI versions won't work until FreeBSD 5 > because the PCI version effectivly requires newcard. The "PCI" card > here is really just a PCCARD controller on an PCI card that you=20 > plug an off-the-shelf Wavelan/Orinoco card into. =20 The change to PCCard prior to 4.4 were specificaly to correct this problem. The PCI card in this case appears to NOT be a generic CardBus bridge like the Lucent adaptors though both are know to work. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --yNb1oOkm5a9FJOVX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RdFgXY6L6fI4GtQRAv1LAJ4mBedCfNsCEoshiQZrhNKfokbObQCfSQ7Y Q11dZuvWpHVHC09ix6DhfiA= =j2r9 -----END PGP SIGNATURE----- --yNb1oOkm5a9FJOVX-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 11:58:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtprelay8.dc2.adelphia.net (smtprelay8.dc2.adelphia.net [64.8.50.40]) by hub.freebsd.org (Postfix) with ESMTP id 1CE6437B417; Wed, 16 Jan 2002 11:58:39 -0800 (PST) Received: from BradMorgan ([24.53.83.156]) by smtprelay8.dc2.adelphia.net (Netscape Messaging Server 4.15) with SMTP id GQ1RHP00.MV2; Wed, 16 Jan 2002 14:58:37 -0500 From: "Brad Morgan" To: "John Baldwin" , , Subject: RE: New cdboot ISO available Date: Wed, 16 Jan 2002 12:58:37 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Please test this ISO and provide feedback to the -stable or -qa lists thanks. I tried the minicdboot on my 4 machines with the following results: Dell Dimension XPS p133c (133 MHz P-I) did not boot. 4.4-Release Disk 1 did boot. Dell Dimension XPS D333 (333 MHz P-II) booted to sysinstall screen. Dell Dimension XPS R350 (350 MHz P-II) booted to sysinstall screen. Dell Dimension 4100 (933 MHz P-III) booted but hung probing for devices. This machine has hung at this point since 4.2. I've reported it numerous times. Sure would be nice to get this fixed as this machine is my main machine. I have FreeBSD installed on this machine by using a set of 5.0-current floppies to get past the above hang. It then installs and runs FreeBSD without any (known) problems. I'd be happy to provide whatever assistance is necessary. Regards, Brad Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 12:16:57 2002 Delivered-To: freebsd-stable@freebsd.org Received: from usagi.cts.com (usagi.cts.com [209.68.192.66]) by hub.freebsd.org (Postfix) with ESMTP id 2BBC137B417 for ; Wed, 16 Jan 2002 12:16:49 -0800 (PST) Received: from golf.cts.com (golf.cts.com [205.163.23.102]) by usagi.cts.com (8.9.3/8.9.3) with ESMTP id MAA29887; Wed, 16 Jan 2002 12:16:47 -0800 (PST) Received: from ctsd2 (ctsd2.cts.com [205.163.23.182]) by golf.cts.com (8.11.6/8.11.6) with ESMTP id g0GKGlS41566; Wed, 16 Jan 2002 12:16:47 -0800 (PST) (envelope-from morgan.davis@hosting.com) Reply-To: From: "Morgan Davis" To: Cc: "'Richard Shaw'" Subject: RE: PCI Wavelan cards under 4.4 Date: Wed, 16 Jan 2002 12:16:52 -0800 Organization: Hosting.com Message-ID: <001b01c19eca$bcac85d0$b617a3cd@ctsd2> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <851336E23970B348A23A1A46DB20D64F0F99E9@ukmail02.internal.mondus.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have one of these working with 4.5-PRERELEASE: http://www.addtron.com/products/awa100.htm I bought it only because it said it was compatible with Linux, and was thrilled to see that it worked with FreeBSD. I'm getting about 5+ Mbps over it. The only problem, which I reported here a couple weeks ago, is that I regularly get kernel messages on the console about "oversized packets". Other than annoying, it doesn't seem to be a problem. Does anyone know if those messages indicate a real error situation that can be fixed on my end, is this just debug output, or what? By the way, the Addtron AWA-100 PCI card looked identical to one sold by 3Com under the USRobotics brand, but was less expensive at Fry's: $79 for the Addtron vs. $140 for the USRobotics. The $79 package also included the Addtron pccard, which, amazingly, sells separately for $110. --Morgan > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd- > stable@FreeBSD.ORG] On Behalf Of Richard Shaw > Sent: Wednesday, January 16, 2002 5:36 AM > To: Freebsd-stable@FreeBSD.ORG > Subject: PCI Wavelan cards under 4.4 > > > > Hi, > > I'm attempting to get a 3com wavelan 3crwe777a PCI card working under 4.4 > Release. I've trawled for posts on this and have found plenty mentioning > how easy it was to get the ISA version working, but have had no solid > confirmations that the PCI one will work. There have been mumblings of > incompatibilities with some motherboards, talk of support coming soon but > nothing definite. Has anyone set one up, or managed to get one working ? > > Many thanks, > > Richard > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 12:28:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from relay2.agava.net.ru (ofc.agava.net [217.106.235.141]) by hub.freebsd.org (Postfix) with ESMTP id A390C37B419 for ; Wed, 16 Jan 2002 12:28:25 -0800 (PST) Received: from hellbell.domain (hellbell.domain [192.168.1.12]) by relay2.agava.net.ru (Postfix) with ESMTP id 0729166B72 for ; Wed, 16 Jan 2002 23:28:24 +0300 (MSK) Received: from localhost (localhost [127.0.0.1]) by hellbell.domain (Postfix) with ESMTP id F08C7CD11 for ; Wed, 16 Jan 2002 23:28:23 +0300 (MSK) Date: Wed, 16 Jan 2002 23:28:23 +0300 (MSK) From: Alexey Zakirov X-X-Sender: To: Subject: vinum behavior after disk errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hail! I have a question about vinum behavior after some disk errors. One of my servers sometimes have a glitch with the disk (or probably controller). It's looks like this: Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): phase change 2-7 10@13d44d68 resid=3. Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): READ(10). CDB: 28 0 0 96 c1 6a 0 0 4 0 Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): ILLEGAL REQUEST asc:24,0 Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): Invalid field in CDB field replaceable unit: 1 sks:ce,5 So vinum immediatly marks the plex as faulty: Jan 16 18:29:15 glance /kernel: vinum: vinum0.p0.s0 is crashed by force Jan 16 18:29:15 glance /kernel: vinum: vinum0.p0 is faulty Jan 16 18:29:15 glance /kernel: vinum: vinum0 is down Jan 16 18:29:15 glance /kernel: fatal:vinum0.p0.s0 read error, block 4048549 for 2048 bytes Jan 16 18:29:15 glance /kernel: vinum0.p0.s0: user buffer block 4048284 for 2048 bytes After reboot OS can't start because it can't check a vinum volume. One must manually do "vinum start vinum0.p0" to get system up. Is there any way to do something like 'fsck_y_enable="YES"' does? Or should I patch /etc/rc to do "vinum start " after "vinum start" ? *** WBR, Alexey Zakirov (frank@agava.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 12:43:13 2002 Delivered-To: freebsd-stable@freebsd.org Received: from jupiter.linuxengine.net (jupiter2.linuxengine.net [209.61.188.254]) by hub.freebsd.org (Postfix) with ESMTP id 8915E37B419 for ; Wed, 16 Jan 2002 12:43:01 -0800 (PST) Received: from jupiterweb.commercevault.com (jupiterweb.commercevault.com [209.61.179.16] (may be forged)) by jupiter.linuxengine.net (8.11.6/8.11.0) with ESMTP id g0GKgpx06721; Wed, 16 Jan 2002 14:42:51 -0600 Date: Wed, 16 Jan 2002 14:42:51 -0600 (CST) From: John Utz X-X-Sender: To: Cc: , "'Richard Shaw'" Subject: RE: PCI Wavelan cards under 4.4 In-Reply-To: <001b01c19eca$bcac85d0$b617a3cd@ctsd2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG wow! cool. so, if i stuck this in my gateway box, would i then be able to route all the wireless traffic in my house? that would be *mass* cheaper than buying one of those combo wire/wireless switches.... On Wed, 16 Jan 2002, Morgan Davis wrote: > I have one of these working with 4.5-PRERELEASE: > > http://www.addtron.com/products/awa100.htm > > I bought it only because it said it was compatible with Linux, and was > thrilled to see that it worked with FreeBSD. I'm getting about 5+ Mbps > over it. > > The only problem, which I reported here a couple weeks ago, is that I > regularly get kernel messages on the console about "oversized packets". > Other than annoying, it doesn't seem to be a problem. Does anyone know > if those messages indicate a real error situation that can be fixed on > my end, is this just debug output, or what? > > By the way, the Addtron AWA-100 PCI card looked identical to one sold by > 3Com under the USRobotics brand, but was less expensive at Fry's: $79 > for the Addtron vs. $140 for the USRobotics. The $79 package also > included the Addtron pccard, which, amazingly, sells separately for > $110. > > --Morgan > > > > > -----Original Message----- > > From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd- > > stable@FreeBSD.ORG] On Behalf Of Richard Shaw > > Sent: Wednesday, January 16, 2002 5:36 AM > > To: Freebsd-stable@FreeBSD.ORG > > Subject: PCI Wavelan cards under 4.4 > > > > > > > > Hi, > > > > I'm attempting to get a 3com wavelan 3crwe777a PCI card working under > 4.4 > > Release. I've trawled for posts on this and have found plenty > mentioning > > how easy it was to get the ISA version working, but have had no solid > > confirmations that the PCI one will work. There have been mumblings of > > incompatibilities with some motherboards, talk of support coming soon > but > > nothing definite. Has anyone set one up, or managed to get one working > ? > > > > Many thanks, > > > > Richard > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- John L. Utz III john@utzweb.net Idiocy is the Impulse Function in the Convolution of Life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 12:54:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.snickers.org (mail.snickers.org [216.126.90.4]) by hub.freebsd.org (Postfix) with ESMTP id 95C9A37B404 for ; Wed, 16 Jan 2002 12:54:41 -0800 (PST) Received: by mail.snickers.org (Postfix, from userid 66) id 6BC094C; Wed, 16 Jan 2002 15:57:47 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by asherah.dyndns.org (Postfix) with ESMTP id 7647D5EF0E; Wed, 16 Jan 2002 15:54:38 -0500 (EST) Received: by asherah.dyndns.org (Postfix, from userid 701954) id BC3045EF0C; Wed, 16 Jan 2002 15:54:36 -0500 (EST) Date: Wed, 16 Jan 2002 15:54:36 -0500 From: Josh Tiefenbach To: Koji Hino Cc: stable@freebsd.org Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? Message-ID: <20020116155436.A28166@zipperup.org> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020116.110509.05717273.hino@ccrl.sj.nec.com>; from hino@ccrl.sj.nec.com on Wed, Jan 16, 2002 at 11:05:09AM -0800 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > After doing some tests, I found that connecting to this 4.5-RC1 box > from other machine by OpenSSH (without RSA/DSA key, nor rhost*auth, > assuming to use plain password to login), requires opie to login, > though /etc/opiekeys, and /etc/skeykeys are both size 0. If I start > openssh with flag '-1', which means to use OpenSSH version 1 protocol, > it works fine: require plain password. I checked 4.4-RELEASE machine, > and found that it works fine without '-1' flag, and even with '-2', it > works. For what its worth, I (well, a friend) is seeing the same behavior. Client: OpenSSH_3.0.2p1, SSH protocols 1.5/2.0, OpenSSL 0x0090601f (on Sun IIRC) Server: FreeBSD khmer.jrt 4.4-STABLE FreeBSD 4.4-STABLE #4: Thu Dec 6 09:08:36 EST 2001 OpenSSH_2.9 FreeBSD localisations 20011202, SSH protocols 1.5/2.0, OpenSSL 0x0090601f Perhaps its an OpenSSH v3 thing? If I have some time tonite, I'll go compile up v3 someplace and check it out. josh -- 'Stay fuzzy. Save the world. Choices.' - Daxter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 12:56:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from marvin.nildram.co.uk (marvin.nildram.co.uk [195.112.4.71]) by hub.freebsd.org (Postfix) with SMTP id 715E137B419 for ; Wed, 16 Jan 2002 12:56:04 -0800 (PST) Received: (qmail 27146 invoked from network); 16 Jan 2002 20:56:02 -0000 Received: from muttley.gotadsl.co.uk (HELO VicNBob) (213.208.123.26) by marvin.nildram.co.uk with SMTP; 16 Jan 2002 20:56:02 -0000 From: Matthew Whelan To: stable@FreeBSD.ORG, "John Nielsen" Cc: freebsd-doc@FreeBSD.ORG Date: Wed, 16 Jan 2002 20:55:53 -0000 X-Priority: 3 (Normal) In-Reply-To: <080801c19e6e$4712f360$0900a8c0@max> Message-Id: Subject: Re: typo in man ed (4) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------DI8Hk+OxDPTC0PXfZp0SoI" X-Mailer: Opera 6.0 build 1010 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ------------DI8Hk+OxDPTC0PXfZp0SoI Content-Type: text/plain; charset="iso-8859-1" CC'ed to docs@ who should be interested 16/01/2002 09:15:01, "John Nielsen" wrote: >This is something that's bitten me on the two occasions I've needed to use >it, so I'm hoping it can get fixed. > >In the CAVEATS section of the ed (4) manpage, it says this: > > 16bit Compex cards identify themselves as being 8bit. While these >cards > will work in 8bit mode, much higher performance can be achieved by >speci- > fying "flags 0x04" (force 16bit mode) in your kernel config file. In >addi- > tion, you should also specify "iosize 16384" to take advantage of the >extra > 8k of shared memory that 16bit mode provides. > >If you put the word "iosize" in a kernel config file it produces a syntax >error. It should be "iosiz" (without the 'e'). > >I'm not familiar with the procedure(s) for fixing typos like this, but if >one of you could enlighten me and/or just take care of it I'd be >appreciative. Thanks, > >JN Source for ed(4) is /usr/src/share/man/man4/ed.4, the attached patch should fix the problem. Normal procedure for getting this addressed would be to fire a mail at docs@ (as it is a documentation problem) and/or file a PR (using send-pr or http://www.freebsd.org/send-pr.html) Yours, Matthew ------------DI8Hk+OxDPTC0PXfZp0SoI Content-Disposition: attachment; filename="ed.4.patch" Content-Type: application/octet-stream; name="ed.4.patch" Content-Transfer-Encoding: Base64 KioqIGVkLjQJV2VkIEphbiAxNiAyMDoyOToyOSAyMDAyCi0tLSBlZC40Lm5l dwlXZWQgSmFuIDE2IDIwOjMwOjA3IDIwMDIKKioqKioqKioqKioqKioqCioq KiAxNzUsMTgxICoqKioKICAuRW0gImZsYWdzIDB4MDQiCiAgKGZvcmNlIDE2 Yml0IG1vZGUpIGluIHlvdXIga2VybmVsIGNvbmZpZyBmaWxlLgogIEluIGFk ZGl0aW9uLCB5b3Ugc2hvdWxkIGFsc28gc3BlY2lmeQohIC5FbSAiaW9zaXpl IDE2Mzg0IgogIHRvIHRha2UgYWR2YW50YWdlIG9mIHRoZSBleHRyYSA4ayBv ZiBzaGFyZWQgbWVtb3J5IHRoYXQgMTZiaXQgbW9kZSBwcm92aWRlcy4KICAu U2ggQlVHUwogIFRoZQotLS0gMTc1LDE4MSAtLS0tCiAgLkVtICJmbGFncyAw eDA0IgogIChmb3JjZSAxNmJpdCBtb2RlKSBpbiB5b3VyIGtlcm5lbCBjb25m aWcgZmlsZS4KICBJbiBhZGRpdGlvbiwgeW91IHNob3VsZCBhbHNvIHNwZWNp ZnkKISAuRW0gImlvc2l6IDE2Mzg0IgogIHRvIHRha2UgYWR2YW50YWdlIG9m IHRoZSBleHRyYSA4ayBvZiBzaGFyZWQgbWVtb3J5IHRoYXQgMTZiaXQgbW9k ZSBwcm92aWRlcy4KICAuU2ggQlVHUwogIFRoZQo= ------------DI8Hk+OxDPTC0PXfZp0SoI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 13:10:34 2002 Delivered-To: freebsd-stable@freebsd.org Received: from usagi.cts.com (usagi.cts.com [209.68.192.66]) by hub.freebsd.org (Postfix) with ESMTP id A310A37B41A for ; Wed, 16 Jan 2002 13:09:28 -0800 (PST) Received: from golf.cts.com (golf.cts.com [205.163.23.102]) by usagi.cts.com (8.9.3/8.9.3) with ESMTP id NAA46463; Wed, 16 Jan 2002 13:09:26 -0800 (PST) Received: from ctsd2 (ctsd2.cts.com [205.163.23.182]) by golf.cts.com (8.11.6/8.11.6) with ESMTP id g0GL9PS41750; Wed, 16 Jan 2002 13:09:25 -0800 (PST) (envelope-from morgan.davis@hosting.com) Reply-To: From: "Morgan Davis" To: "'John Utz'" Cc: , "'Richard Shaw'" Subject: RE: PCI Wavelan cards under 4.4 Date: Wed, 16 Jan 2002 13:09:31 -0800 Organization: Hosting.com Message-ID: <002001c19ed2$1769b950$b617a3cd@ctsd2> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm not using the AWA-100 quite that way as I have a D-Link WAP 1000 Wireless Access Point that connects to my private LAN switch. D-Link WAP 1000 http://www.dlink.com/products/wireless/dwl1000ap/ I got the D-Link after reading a good PC Magazine review comparing it to others (including more expensive Cisco stuff). The price is great and the wired link speed is 100mbps (unlike many others that top out at 10mbps -- kind of silly with theoretical 11mbps wireless speed). The home network is served by a FreeBSD router/nat/firewall/fileserver machine. The Addtron AWA-100 pci/pccard is in another FreeBSD "client" machine acting as an audio component upstairs in my stereo rack. Its sole job is to playback MP3s which it pulls over wireless NFS access to the server downstairs. Putting the AWA-100 in that little box (see link below) saved me from having to run wiring between floors of the house. Shuttle SV24 Mini Barebones System http://www.anandtech.com/showdoc.html?i=1572&p=1 It only has PCI slot, which the AWA-100 occupies. I would love to know if there is any kind of a wlan adapter that can plug into a 10/100 port (or even USB if it works with FreeBSD), so I can free up the PCI slot for a sound card with digital outputs. If anyone knows, please enlighten me! Thanks. --Morgan > -----Original Message----- > From: John Utz [mailto:john@utzweb.net] > Sent: Wednesday, January 16, 2002 12:43 PM > To: mdavis@cts.com > Cc: freebsd-stable@FreeBSD.ORG; 'Richard Shaw' > Subject: RE: PCI Wavelan cards under 4.4 > > wow! cool. > > so, if i stuck this in my gateway box, would i then be able to route all > the wireless traffic in my house? > > that would be *mass* cheaper than buying one of those combo wire/wireless > switches.... > > On Wed, 16 Jan 2002, Morgan Davis wrote: > > > I have one of these working with 4.5-PRERELEASE: > > > > http://www.addtron.com/products/awa100.htm > > > > I bought it only because it said it was compatible with Linux, and was > > thrilled to see that it worked with FreeBSD. I'm getting about 5+ Mbps > > over it. > > > > The only problem, which I reported here a couple weeks ago, is that I > > regularly get kernel messages on the console about "oversized packets". > > Other than annoying, it doesn't seem to be a problem. Does anyone know > > if those messages indicate a real error situation that can be fixed on > > my end, is this just debug output, or what? > > > > By the way, the Addtron AWA-100 PCI card looked identical to one sold by > > 3Com under the USRobotics brand, but was less expensive at Fry's: $79 > > for the Addtron vs. $140 for the USRobotics. The $79 package also > > included the Addtron pccard, which, amazingly, sells separately for > > $110. > > > > --Morgan > > > > > > > > > -----Original Message----- > > > From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd- > > > stable@FreeBSD.ORG] On Behalf Of Richard Shaw > > > Sent: Wednesday, January 16, 2002 5:36 AM > > > To: Freebsd-stable@FreeBSD.ORG > > > Subject: PCI Wavelan cards under 4.4 > > > > > > > > > > > > Hi, > > > > > > I'm attempting to get a 3com wavelan 3crwe777a PCI card working under > > 4.4 > > > Release. I've trawled for posts on this and have found plenty > > mentioning > > > how easy it was to get the ISA version working, but have had no solid > > > confirmations that the PCI one will work. There have been mumblings of > > > incompatibilities with some motherboards, talk of support coming soon > > but > > > nothing definite. Has anyone set one up, or managed to get one working > > ? > > > > > > Many thanks, > > > > > > Richard > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > > John L. Utz III > john@utzweb.net > > Idiocy is the Impulse Function in the Convolution of Life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 13:29:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id DB6C537B416 for ; Wed, 16 Jan 2002 13:29:06 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id g0GLSrF36620; Wed, 16 Jan 2002 16:28:53 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020116091030.GA16535@titan.klemm.gtn.com> References: <20020115062456.GA13349@christian.chrullrich.de> <20020115151846.GA14953@christian.chrullrich.de> <20020115213522.GA15920@christian.chrullrich.de> <20020116091030.GA16535@titan.klemm.gtn.com> Date: Wed, 16 Jan 2002 16:28:51 -0500 To: Andreas Klemm , apsfilter-help@apsfilter.org From: Garance A Drosihn Subject: Re: 4.4R: if: doesn't get started when getting remote print job (Re: apsfilter doesn't work on server) Cc: desmo@bandwidth.org, freebsd-stable@freebsd.org, Christian Ullrich Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:10 AM +0100 1/16/02, Andreas Klemm wrote: >On Tue, Jan 15, 2002, Christian Ullrich wrote: > > I'm out of ideas. What about you out there? > >You should try to contact Garance A Drosihn >to ask, since he did a lot on the FreeBSD spooling system. I'll exchange some messages directly with Christian and see if we can't figure out what was happening with the bsd-ish lpr. I don't have the experience with lprNG to say what is happening there. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 13:35:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by hub.freebsd.org (Postfix) with ESMTP id 3706B37B416 for ; Wed, 16 Jan 2002 13:35:13 -0800 (PST) Received: (from jschlesn@localhost) by emmi.physik.TU-Berlin.DE (8.11.6/8.11.6) id g0GLYq375192; Wed, 16 Jan 2002 22:34:52 +0100 (CET) (envelope-from jschlesn) Date: Wed, 16 Jan 2002 22:34:52 +0100 From: Jan Schlesner To: Steve Shorter Cc: freebsd-stable@freebsd.org Subject: Re: "server not responding" / "is alive again" NFS tunables Message-ID: <20020116223452.A74841@physik.TU-Berlin.DE> References: <20020116101212.A610@nomad.lets.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020116101212.A610@nomad.lets.net>; from steve@nomad.tor.lets.net on Wed, Jan 16, 2002 at 10:12:12AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, some weeks ago, the same problem was posted in this newsgroup. Here is the anwser from Ian Dowse: -- These are a side-effect of the operation of the NFS dynamic retransmit timeout code. The NFS client measures the request response time for various types of operations and it sets a timeout based on the mean and deviation of observed times. The time taken by the server to perform some operations can vary wildly though, so occasionally when a large number of operations complete with very little delay, the response time estimate and hence the timeout become very small. Then when one request is unusually slow to complete (such as when the disk on the server is busy), the client thinks that the server isn't responding and prints those warnings. A fraction of a second later the request completes and the client prints a an 'is alive again' message. On non-soft mounts these messages are completely harmless because the client will just wait for the server to eventually reply. On soft mounts, the effect can cause problems because applications occasionally see an EINTR error. The dynamic retransmit timeout code can be disabled with the `-d' flag to mount_nfs; this is often recommended for fast networks that see very little packet loss. -- On Wed, Jan 16, 2002 at 10:12:12AM -0500, Steve Shorter wrote: > > I have a dedicated NFS server with 16 nfsd's running, connected > to SCSI raid/softupdates and good network connectivity/switching. Under > moderate or even sometimes light load the clients(7 of them) log messages > > nfs server 192.168.10.2:/mnt: not responding > nfs server 192.168.10.2:/mnt: is alive again > > several times per minute. They always have the same timestamp. Performance > is not noticably impaired, but I am wondering if this situation will eventually > become a performance barrier as the system ramps up to full production, if > the above log messages mean that packets must be delayed or retransmitted. -- [ gpg key: http://wwwnlds.physik.tu-berlin.de/~schlesner/jschlesn.gpg ] [ key fingerprint: 4236 3497 C4CF 4F3A 274F B6E2 C4F6 B639 1DF4 CF0A ] -- It's better to reign in hell, than to serve in heaven... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 13:37:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id A87BF37B416 for ; Wed, 16 Jan 2002 13:37:39 -0800 (PST) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id AE4025D13; Wed, 16 Jan 2002 13:37:39 -0800 (PST) To: mdavis@cts.com Cc: freebsd-stable@freebsd.org, "'Richard Shaw'" Subject: Re: PCI Wavelan cards under 4.4 In-reply-to: Your message of "Wed, 16 Jan 2002 12:16:52 PST." <001b01c19eca$bcac85d0$b617a3cd@ctsd2> Date: Wed, 16 Jan 2002 13:37:39 -0800 From: "Kevin Oberman" Message-Id: <20020116213739.AE4025D13@ptavv.es.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: "Morgan Davis" > Date: Wed, 16 Jan 2002 12:16:52 -0800 > Sender: owner-freebsd-stable@FreeBSD.ORG > > I have one of these working with 4.5-PRERELEASE: > > http://www.addtron.com/products/awa100.htm > > I bought it only because it said it was compatible with Linux, and was > thrilled to see that it worked with FreeBSD. I'm getting about 5+ Mbps > over it. > > The only problem, which I reported here a couple weeks ago, is that I > regularly get kernel messages on the console about "oversized packets". > Other than annoying, it doesn't seem to be a problem. Does anyone know > if those messages indicate a real error situation that can be fixed on > my end, is this just debug output, or what? Oversized packets are usually from on of two sources: 1. Duplex mis-match. (This should also produce CRC and framing errors). Auto-negotiation of duplex often fails. We always lock our ports down if they are permanently connected to a device. Speed detection is quite reliable. 2. 802.1q VLAN trunking. The VLAN header expands the packet by 2 octets which exceeds the old 802.3 limit on frame size for full 1500 byte packets. Lowering the MTU by 2 on the sending systems might fix this, but the header is normally removed by the last switch to process the frame. This might indicate a mis-configured switch. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 15: 5:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from hardy.mskcc.org (hardy.mskcc.org [140.163.115.228]) by hub.freebsd.org (Postfix) with ESMTP id A77C737B417 for ; Wed, 16 Jan 2002 15:05:27 -0800 (PST) Received: (from heath@localhost) by hardy.mskcc.org (8.9.3/8.9.3) id SAA11706; Wed, 16 Jan 2002 18:05:08 -0500 Date: Wed, 16 Jan 2002 18:05:08 -0500 From: Simon Heath To: Josh Tiefenbach Cc: Koji Hino , stable@FreeBSD.ORG Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? Message-ID: <20020116180508.A11693@hardy.mskcc.org> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020116155436.A28166@zipperup.org>; from josh@zipperup.org on Wed, Jan 16, 2002 at 03:54:36PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > After doing some tests, I found that connecting to this 4.5-RC1 box > > from other machine by OpenSSH (without RSA/DSA key, nor rhost*auth, > > assuming to use plain password to login), requires opie to login, > > though /etc/opiekeys, and /etc/skeykeys are both size 0. If I start > > openssh with flag '-1', which means to use OpenSSH version 1 protocol, > > it works fine: require plain password. I checked 4.4-RELEASE machine, > > and found that it works fine without '-1' flag, and even with '-2', it > > works. > > For what its worth, I (well, a friend) is seeing the same behavior. > > Client: OpenSSH_3.0.2p1, SSH protocols 1.5/2.0, OpenSSL 0x0090601f (on Sun IIRC) > Server: > FreeBSD khmer.jrt 4.4-STABLE FreeBSD 4.4-STABLE #4: Thu Dec 6 09:08:36 EST 2001 > OpenSSH_2.9 FreeBSD localisations 20011202, SSH protocols 1.5/2.0, > OpenSSL 0x0090601f > > Perhaps its an OpenSSH v3 thing? If I have some time tonite, I'll go compile > up v3 someplace and check it out. > As no one has mentioned this yet, editing /etc/ssh/sshd_config to uncomment the line: ChallengeResponseAuthentication no does the trick (i.e., stops the opie requests). I noticed this about a month ago, but I'm not sure when it started. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 15:30:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.snickers.org (mail.snickers.org [216.126.90.4]) by hub.freebsd.org (Postfix) with ESMTP id 3E5B237B6B5 for ; Wed, 16 Jan 2002 15:19:58 -0800 (PST) Received: by mail.snickers.org (Postfix, from userid 66) id 5216851; Wed, 16 Jan 2002 18:22:50 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by asherah.dyndns.org (Postfix) with ESMTP id AC8FC5EF0E; Wed, 16 Jan 2002 18:19:45 -0500 (EST) Received: by asherah.dyndns.org (Postfix, from userid 701954) id 00AC85EF0C; Wed, 16 Jan 2002 18:19:43 -0500 (EST) Date: Wed, 16 Jan 2002 18:19:43 -0500 From: Josh Tiefenbach To: Simon Heath Cc: Koji Hino , stable@FreeBSD.ORG Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? Message-ID: <20020116181943.B30361@zipperup.org> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> <20020116180508.A11693@hardy.mskcc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020116180508.A11693@hardy.mskcc.org>; from heath@hardy.mskcc.org on Wed, Jan 16, 2002 at 06:05:08PM -0500 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > As no one has mentioned this yet, editing /etc/ssh/sshd_config to uncomment > the line: > > ChallengeResponseAuthentication no > > does the trick (i.e., stops the opie requests). Hrmm. I dont see a config var by that name, but there is an SkeyAuthentication knob which I set to no. We'll see how that works. josh -- 'Stay fuzzy. Save the world. Choices.' - Daxter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 16: 3:39 2002 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.bogen.org (adsl-216-103-84-120.dsl.snfc21.pacbell.net [216.103.84.120]) by hub.freebsd.org (Postfix) with ESMTP id 7CFD937B400 for ; Wed, 16 Jan 2002 16:03:34 -0800 (PST) Received: from bogen.org (localhost [127.0.0.1]) by merlin.bogen.org (8.11.5/8.11.2) with ESMTP id g0H03Q203309; Wed, 16 Jan 2002 16:03:26 -0800 (PST) (envelope-from db@bogen.org) Message-ID: <3C4614CE.8050001@bogen.org> Date: Wed, 16 Jan 2002 16:03:26 -0800 From: David Bogen User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.7) Gecko/20020107 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Tiefenbach Cc: Simon Heath , Koji Hino , stable@FreeBSD.ORG Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> <20020116180508.A11693@hardy.mskcc.org> <20020116181943.B30361@zipperup.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Try inserting: PreferredAuthentications publickey,password into /etc/ssh/ssh_config. Josh Tiefenbach wrote: >>As no one has mentioned this yet, editing /etc/ssh/sshd_config to uncomment >>the line: >> >>ChallengeResponseAuthentication no >> >>does the trick (i.e., stops the opie requests). >> > > Hrmm. I dont see a config var by that name, but there is an SkeyAuthentication > knob which I set to no. We'll see how that works. > > josh > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 16:29:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (snafu.adept.org [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id 5490337B41C for ; Wed, 16 Jan 2002 16:29:41 -0800 (PST) Received: by snafu.adept.org (Postfix, from userid 1000) id 420A49EE33; Wed, 16 Jan 2002 16:29:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id 3A88E9B031; Wed, 16 Jan 2002 16:29:33 -0800 (PST) Date: Wed, 16 Jan 2002 16:29:33 -0800 (PST) From: Mike Hoskins To: "Bas v.d. Wiel" Cc: Subject: Re: VPN how?? In-Reply-To: Message-ID: <20020116162854.M4307-100000@snafu.adept.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 16 Jan 2002, Bas v.d. Wiel wrote: > scripts from websites. Does anyone know of a good source (book, online or > other)to find detailed information from which I could learn how to set up a > vpn using FreeBSD gateways? Here's something, found on bsdtoday.com's front page: http://www.onlamp.com/pub/a/bsd/2001/12/10/ipsec.html Later, -Mike -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." --Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 17:35:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from notes.sfinc.com (notes.sfinc.com [207.66.145.18]) by hub.freebsd.org (Postfix) with SMTP id 7A3CB37B402; Wed, 16 Jan 2002 17:34:24 -0800 (PST) Received: from yourdomain.net by notes.sfinc.com (Lotus SMTP MTA v1.05 (274.9 11-27-1996)) with SMTP id 88256B44.0007796F; Fri, 16 Jan 1970 17:22:19 -0700 From: ashley_franks2@yahoo.com To: peggy w <> Subject: WORK HOME ON YOUR COMPUTER Date: Wed, 16 Jan 2002 17:28:55 -0800 X-Sender: ashley_franks2@yahoo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 X-MSMail-Priority: Normal Message-Id: <20020117013424.7A3CB37B402@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG WORK HOME ON YOUR COMPUTER AND EARN MONEY. In less than 90 days you can earn more than $45.000 simply by sending e-mails. Do you think this is possible? Keep on reading and you will get information about how this is possible. There are no limits. Thanks for your interest. Due to the wide interest this letter has received on the Internet, one of the most respectable news agencies in the United States made a detailed story about this program in order to find out if it really worked, i.e. if you really could gain money this way. They also wanted to find out if it was legal. Their result was that no laws prohibit programs like this or people to participate in it. In fact, this is a simple and legal way to earn money from your own home. Furthermore, the news show established that the participants were unusually many and that their lives took a swift turn for the better. Every participant received a high amount of money in a short time and hence, the word got around fast. As soon as you get our point you will have learned something new. HERE IT COMES You should print this out and keep it available. This way to earn money will surely catch your interest. You start by small investment and the result will be enormous. If you want to earn more than $45.000 in less than 90 days, read through this letter . think about it . and read it again. This is a legal way to earn money. You do not have to sell any product nor work hard, and best of all, you even do not have to leave your home. If you believe that one day you will make it, follow these instructions and your dreams will come true. This Multi-Level-Marketing Program works 100%. E-mail is today's future sales tool. Take advantage of this advertising technology right now and participate. Today, Multi-Level Marketing (MLM) is accepted in the world of business. As an example we can tell you that it is taught in Harvard University. Stanford Research and Wall Street Journal have verified that 50-65% of all merchandise and service industry takes place with MLM. This is a million dollar industry and 20% (700.000 individuals) of the world's 3.500.000 millionaires got their success through MLM. Statistics show us that each day 100 individuals are added to this group. You may think that this is a cliché you have heard before, but Donald Trump (one of the world's richest man) said in a David Letterman- show last summer that if he lost everything and had to start over he would definitely start by founding an Internet MLM business. The audience on the show yelled and protested and Mr. Trump responded by saying, "This is the reason why you are sitting down there and I am sitting up here!". MLM has two sources of income. First, you have income through your own sale and second, you receive income by introducing new participants. Non-stop incoming is the secret of the rich, which means that you invest with a small amount of money and get great returns. MLM means getting money with the help of others and their work. This program is now working in 50 countries around the world. I had almost let this information pass me but luckily I decided to give it a chance and study it carefully. My name is Petra Pieren, I am a housewife and the mother of two children. My husband and me have for a long time search for an easy way to earn money. We had financial difficulties and for a while we were living in poverty. We asked ourselves how on earth we could make this work in the future? Despite our fear of having not enough money to live, we were too proud to accept help from the social workers. We believed that one day our luck would turn. Somebody emailed me this program twice and I ignored it, because I assumed that these extraordinary high amounts of money meant that it had to be illegal. Finally in March this year I received the email again and decided to give it a chance and read it carefully. I saw that this was my chance to turn things around for my family and me. I thank God that my name was on one of the lists and I decided to take part. When money started coming in I thought that it was too good to be true. I began by investing without putting my self in debt. We read the whole thing through once more, recalculated our investments, and found out that we would always get the money invested returned. But we were sceptical, like you maybe, that this was legal so we contacted U.S. Post Office (tel. 001-800-725-2161/24) and they verified that what we were taking part in was totally legal. We decided to take part because we realised that this is a legal program and CERTAINLY NOT A CHAIN LETTER. I started by buying an internet-connection, which cost me 25 SFR, and sent a few thousands of e-mails. The advantage of e-mail is that there is no need to buy expensive paper, it only takes some of your time! I am honest when I tell you, and hopefully it doesn't frighten you, that I promised myself that no matter what I would never drag anyone by the tail/participate in anything that would make fool out of other people. Within a week orders for Report #1 started coming. The goal is to receive 20 orders of Report #1 within two weeks. If this doesn't succeed all you have to do is send more people emails about this program until you reach your goal. This was my first step to earn $45.000 within 90 days. Next goal is to receive 100 orders of Report #2 within 2 weeks. If that doesn't happen to you simply send more emails like you did with Report #1. Once these 100 orders are achieved the rest is easy. All you have to do is sit back and relax because the $45.000 profit is secured. Give yourself enough time to read about this program. Consider the fact, that if you don't take part the program will not work for you. The program works but you need to follow the instructions carefully. Take good care to place your name at the right place on the list, because otherwise you could loose considerable money. In order for this program to work as it should and bring you the whole $45.000, you need to receive 20 orders of Report #1 and at least 100 for Report #2. If you decide not to take part in this program I will be sorry for your half, because this is an extraordinary chance to gain financial independence with minimum risk and cost. Yours sincerely, Petra Pieran A PERSONAL REMARK FROM THE FOUNDER OF THE PROGRAM You should now have realised that amateurs did not make this program Let me begin by telling you a bit about myself. I had a successful business for 10 years but in 1997 things started going for the worst. I continued working in the same way that brought me success before but it just didn't work anymore. I discovered that the problem had its origin in the economy system itself but not me. The so-called stabilised economy that has been dominant since 1945 is history because of inflation and recession. I don't need to tell you how unemployment rates went up because you lived it yourselves, along with bankruptcies in every part of the world. Middleclass evaporated and those who knew what they were doing advanced in society. Those who did nothing became poor. As the saying goes: "The richer will get richer and the poorer poorer." Be sure that conventional way to earn money will not bring you success because of the inflation. You have already received information that will change your life and bring you success without high risks or costs. You can earn more money in the next months than you have ever dreamed of. I would like to underline that neither me, nor the person who gathered this information for you, will share your profit. I have already earned over $4 million by sending 1,6 million e-mails. Now I run many offices that make sure that this program, along with others alike, is working both in U.S.A and Europe. Follow the program carefully; do not change any aspect of it because it works perfectly like it is. You can send this program to everybody you know and one of them will than send 100.000 e-mails with your name in it. You get more clients by sending more e-mail. Now I have given you an idea, information, material and a chance to gain financial independence and it's your turn. Think carefully. Take a while and think before you delete this text. Grab a pencil and calculate possible outcomes of your participation in the program. Assume that few orders come in and you will see that no matter what, you will still be gaining much money. You will always get your investment returned. All your doubts will disappear when the first orders start pouring in. It works! Jody Jacobs, Richmond, VA INSTRUCTIONS ON HOW THIS EXTRAORDINARY PROGRAM WORKS AND BRINGS YOU MILLIONS This method of earning money always works 100%. I am sure that you can find a use for $45.000 in the next few months. Before you denounce this please read this carefully through because we are telling you about a perfectly legal way to earn money. This is what you should do: 1. Order all six Reports, which are on the list because you can not sell a report if you don't own it. a. Send $5 dollar bill for each Report, or the same amount in your local currency (always bill not change), the number and title of the Report and your name along with your address (in case of problems with the mail) to the person on the list on that Report. b. You need to order all six Reports when you order. You need to have a downloaded file of all six Reports when you start sending it from your own computer. c. In a few days, you will receive a file of all six Reports through e-mail and you can then download them on your hard disk, where they will wait to be sent to thousands of people who will order from you. 2. NOTICE: Do not change names or their order on the lists. If you change something in the program you will loose high amount of money. Once you have understood how the program works you will understand why it doesn't work if you change it. Consider the fact that this program has undergone tests in order to make it fail to work if you change it. a. Take the list that contains the Reports. b. Once you have ordered all the Reports, you should take the text the goes with the list and change the name and address in Report #6 and put instead in the name from Report #5. Presumably the person who owns the name in Report #6 has closed his/her circle and is now enjoying $45.000. c. Move name and address in Report #4 to Report #5. d. Move name and address in Report #3 to Report #4. e. Move name and address in Report #2 to Report #3. f. Move name and address in Report #1 to Report #2. g. Put your own name and address in Report #1. 3. Gather a list of all the names and download it without changes on your hard disc. Make no alterations on the instructions. Minimum cost is spent on starting (we can all spare $30). Obviously you own a computer and an e-mail account. In order to succeed your marketing on the net you need to own all 6 Reports. They contain invaluable marketing information about how to send e-mails in large quantities. Furthermore, you will be informed about Internet marketing clubs such as the Internet Marketing Resources (IMR) which one of its kind. It works as information centres for people in marketing from all over the world and gives them an opportunity to exchange ideas and secrets about the advantages of Internet marketing. In addition, members of the club get a free copy of a special marketing tool which is called "do it your self" marketing. You will be given free e-mail software and through that up to 1.000.000 e-mail addresses every week. These club gives you access to hundreds of free web-sides and advertise your own webside. You will be able to send much e-mail to AOL and CompuServe and introduce your product with newsgroups. METHOD 1: E-MAIL ADVERTISMENT Let's take an example. You start small to see how you do. You and your friends send 2000 programs each through e-mail and get 0,3% ratings. If your lists are good you will have a much better rating. Furthermore, some will send more than 2000 e-mails, even 100.000 or more. O, 3% rating would mean 6 orders on Report #1. Each of those six individuals will then e-mail 2000 programs, in all 12.000 programs, and 0,3% of their recipients, i.e. 36 persons, will order Report #2. Those 36 individuals will then continue and send 2000 programs each or 72.000 programs. That would lead to at least 216 orders of Report #3. Those 216 individuals send each 2000 programs, in all 432.000 e-mails. That would lead to 1.296 individuals ordering Report #4 and each of those individuals would send 2.592.000 programs, which means that orderings coming in for Report #5 should be about 7.776. Which means that 7.776 individuals would send you $5. What would happen if 1994 individuals out of 2000 would decide not to take part and delete the program? Think about what would happen if all of the 2000 people would send 100.000 e-mails instead of 2000. Believe me, many will do that because the costs is close to zero. Obviously, you now have an Internet link and e-mail. Report #2 and Report 5# show you how to send e-mails in large quantities and free software to send as much as 1.000.000 e-mails without costs. METHOD TWO: HOW TO ADVERTISE ON THE INTERNET FOR FREE. 1. To advertise on the Internet is very practical. One can find hundreds of free space for advertisement. Lets take an example: You would like to start slow to see how it goes. Your aim is to get 6 people on level 1 and these 6 individuals will then only get another 6. Level 1. Your 6 with $5 ($5 multiplied by 6).........$30 Level 2. Your 6 with their 6 ($5 multiplied by 36)......$180 Level 3. Your 6 with their 36 ($5 multiplied by 216)....$1.080 Level 4. Your 6 with their 216 ($5 multiplied by 1296).....$6.480 Level 5. Your 6 with their 1296 ($5 multiplied by 7776)...$38.880 Level 6. Your 6 with their 7776 ($5 multiplied by 46656)..$233.280 Total Sum ...............$279.930 For every $5 you receive you simply send the Report requested in e-mail. You should always respond to an order on the same day it arrives. As soon as you respond the client can start working in your favour. REPORTS AVAILABLE Order all the six Reports according their number and title. NOTICE: You should always send a $5 bill, never coins or cheques. Send the order with ordinary mail; fold a paper around the bill before putting it in the envelope and on the paper you should write the following: a. Number and title of the Report. b. Your e-mail address. c. Name and address. Report #1: The insider's guide to advertising for free on the Internet Flosi JakobssonPo Box: 4345,124 Reykjavik, Iceland Report #2: The insider's guide to sending bulk e-mail on the Internet Maria HaraldsdottirPo Box: 5426,125 Reykavik, Iceland Report #3: The secrets to MLM ,Multi-Level Marketing" on the Internet AEvar B. JakobssonPo Box: 9087129 Reykjavik, Iceland Report #4: How to become a millionaire utilizing the power of MLM and the Internet Aslaug SkeggjadottirPo Box: 4095,124 Reykjavik Iceland Report #5: 1 million e-mail dispatching ability, FREE! Hallbera BjarnadottirFludasel 95,109 Reykjavik, Iceland Report #6: The address list generator, FREE never ending fresh addresses Elvar JakobssonRübenkamp 82, 22307 Hamburg, (Germany) To remember!  Consider the program your job. Follow the instructions carefully.  ORDER ALL SIX REPORTS IMMEDIATELY, so they will be available to you, when orders start coming in.  Always respond to order on the same day.  Be patient when you use this program because if you follow instructions the result will be in your favour.  By all means, believe in you. P.S. AT THIS MOMENT 175.000 INDIVIDUALS ARE USING THIS PROGRAM! The goal is to get 20 orders for Report #1 and 100 orders for Report #2. After that, you can relax and the money will start coming in. IMPORTANT Each time you move a name off the list, your name will be put in another Report. You can follow up on your results by checking the numbers of ordered Reports. If you want to earn more money you can simply start a new round of e-mails, because there are no limits. Before you decide if you want to participate answer one question: THE QUESTION IS: DO YOU WANT TO CHANGE YOUR LIFE? If the answer is yes, then check this out. 1. You will be selling a product which has no production cost. 2. You will be selling a product which has no transportation cost. 3. You will be selling a product which has no advertisement cost. 4. You will use the power of the Internet and MLM to distribute your product around the world. 5. The only investment you make is $30 and your time. 6. All income is pure profit. TESTIMONY Here are few examples of people who have become rich working this program. Mitchell Wolf. Chicago, IL. He earned $147.200 in $5 bills in 45 days. Pam Hedland, Halmstad, Sweden earned in the first 2 weeks $36.470 in $5 bills and the money kept coming in. Mohammed, Cairo, Egypt. In 4 weeks he earned $41.000 Order these Reports today and become financially independent. It is your turn! The results are marvellous This is a one time mailing. To be removed from our database, reply with "REMOVE" in the subject line. To ensure that the "unsubscribe process" has been completed successfully please allow 2 weeks. We do apologize for any interim emails that are received while we are updating our records. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 17:36: 7 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.nec.com (dns4.nec.com [131.241.15.4]) by hub.freebsd.org (Postfix) with ESMTP id D669E37B42A for ; Wed, 16 Jan 2002 17:35:34 -0800 (PST) Received: from netkeeper2.sj.nec.com (netkeeper2.sj.nec.com [131.241.31.10]) by mail4.nec.com (/) with ESMTP id g0H1ZRe20846 for ; Wed, 16 Jan 2002 17:35:27 -0800 (PST) Received: from ccrl.sj.nec.com (localhost [127.0.0.1]) by netkeeper2.sj.nec.com (8.9.1a/8.9.1) with ESMTP id RAA17738 for ; Wed, 16 Jan 2002 17:35:26 -0800 (PST) Received: from localhost (hirosige [131.241.79.26]) by ccrl.sj.nec.com (8.9.3/8.9.2) with ESMTP id RAA16174 for ; Wed, 16 Jan 2002 17:35:26 -0800 (PST) Date: Wed, 16 Jan 2002 17:35:25 -0800 (PST) Message-Id: <20020116.173525.68550113.hino@ccrl.sj.nec.com> To: stable@FreeBSD.ORG Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? From: Koji Hino In-Reply-To: <3C4614CE.8050001@bogen.org> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> <20020116180508.A11693@hardy.mskcc.org> <20020116181943.B30361@zipperup.org> <3C4614CE.8050001@bogen.org> Organization: C&C Research Laboratories (CCRL), NEC USA, Inc. X-Mailer: Mew version 2.2rc1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks to everyone who answered to my question. OK, there are some workaround to overcome this problem. Then, how 4.5-R should be? Disable opie as default sshd configuration? Or.... I looked into source (not deeply), and found: * opiechallenge() [/usr/src/contrib/opie/libopie/challenge.c] returns value: 0, -1, 1. If there are no related user, it seems (I'm not checked by debugger. only my understanding..) to return 1. * old version, skeychallenge(), only return 0 (OK), or -1 (BAD). * get_challenge() [/usr/src/crypto/openssh/auth-chall.c] only check return value of opiechallenge() if it is -1. So, I think get_challenge() should handle '1' case. Best regards, ==================================================================== Koji HINO(HINO is my family name) C&C Research Laboratories, NEC USA, Inc. E-mail: hino@ccrl.sj.nec.com ---------- DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of NEC USA, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 17:42:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 788F237B416 for ; Wed, 16 Jan 2002 17:42:18 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 8B31F782D0; Thu, 17 Jan 2002 12:12:15 +1030 (CST) Date: Thu, 17 Jan 2002 12:12:15 +1030 From: Greg Lehey To: Alexey Zakirov Cc: freebsd-stable@freebsd.org Subject: Re: vinum behavior after disk errors Message-ID: <20020117121215.E95888@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] Log output was truncated. On Wednesday, 16 January 2002 at 23:28:23 +0300, Alexey Zakirov wrote: > Hail! > > I have a question about vinum behavior after some disk errors. > One of my servers sometimes have a glitch with the disk (or probably > controller). It's looks like this: > > Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): phase change 2-7 10@13d44d68 resid=3. > Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): READ(10). CDB: 28 0 0 96 c1 6a 0 0 4 0 > Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): ILLEGAL REQUEST asc:24,0 Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): Invalid field in CDB > field replaceable unit: 1 sks:ce,5 > > So vinum immediatly marks the plex as faulty: > > Jan 16 18:29:15 glance /kernel: vinum: vinum0.p0.s0 is crashed by force > Jan 16 18:29:15 glance /kernel: vinum: vinum0.p0 is faulty > Jan 16 18:29:15 glance /kernel: vinum: vinum0 is down > Jan 16 18:29:15 glance /kernel: fatal:vinum0.p0.s0 read error, block 4048549 for 2048 bytes > Jan 16 18:29:15 glance /kernel: vinum0.p0.s0: user buffer block 4048284 for 2048 bytes > > After reboot OS can't start because it can't check a vinum volume. > One must manually do "vinum start vinum0.p0" to get system up. > > Is there any way to do something like 'fsck_y_enable="YES"' does? > Or should I patch /etc/rc to do "vinum start " after "vinum > start" ? Hmm, that's an interesting idea. The trouble I see at the moment is that there are so many possible Vinum configurations that it would be difficult to check them all. I'm also rather surprised that you could change this simply with a 'vinum start'. This suggests that you already had a functional volume, in which case you shouldn't have had any trouble with the fsck. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 17:52: 8 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.nec.com (dns4.nec.com [131.241.15.4]) by hub.freebsd.org (Postfix) with ESMTP id 1871337B402 for ; Wed, 16 Jan 2002 17:52:06 -0800 (PST) Received: from netkeeper2.sj.nec.com (netkeeper2.sj.nec.com [131.241.31.10]) by mail4.nec.com (/) with ESMTP id g0H1pxe21249 for ; Wed, 16 Jan 2002 17:51:59 -0800 (PST) Received: from ccrl.sj.nec.com (localhost [127.0.0.1]) by netkeeper2.sj.nec.com (8.9.1a/8.9.1) with ESMTP id RAA19114 for ; Wed, 16 Jan 2002 17:51:58 -0800 (PST) Received: from localhost (hirosige [131.241.79.26]) by ccrl.sj.nec.com (8.9.3/8.9.2) with ESMTP id RAA16277 for ; Wed, 16 Jan 2002 17:51:59 -0800 (PST) Date: Wed, 16 Jan 2002 17:51:58 -0800 (PST) Message-Id: <20020116.175158.125114578.hino@ccrl.sj.nec.com> To: stable@FreeBSD.ORG Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? From: Koji Hino In-Reply-To: <20020116.173525.68550113.hino@ccrl.sj.nec.com> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> <20020116180508.A11693@hardy.mskcc.org> <20020116181943.B30361@zipperup.org> <3C4614CE.8050001@bogen.org> <20020116.173525.68550113.hino@ccrl.sj.nec.com> Organization: C&C Research Laboratories (CCRL), NEC USA, Inc. X-Mailer: Mew version 2.2rc1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: Koji Hino Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? Date: Wed, 16 Jan 2002 17:35:25 -0800 (PST) ID: <20020116.173525.68550113.hino@ccrl.sj.nec.com> > So, I think get_challenge() should handle '1' case. One lost comment: Yes, from system security view, it may be desired to make indistinguishable if requested account name is valid or not. If get_challenge() handle '1' case like '-1' case, cracker can know that specific username is valid (valid on opie) or not (not valid on opie, nor passwd, etc). Koji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 18: 3:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.nec.com (dns4.nec.com [131.241.15.4]) by hub.freebsd.org (Postfix) with ESMTP id 98A8537B402 for ; Wed, 16 Jan 2002 18:03:45 -0800 (PST) Received: from netkeeper2.sj.nec.com (netkeeper2.sj.nec.com [131.241.31.10]) by mail4.nec.com (/) with ESMTP id g0H23de21538 for ; Wed, 16 Jan 2002 18:03:39 -0800 (PST) Received: from ccrl.sj.nec.com (localhost [127.0.0.1]) by netkeeper2.sj.nec.com (8.9.1a/8.9.1) with ESMTP id SAA20216 for ; Wed, 16 Jan 2002 18:03:38 -0800 (PST) Received: from localhost (hirosige [131.241.79.26]) by ccrl.sj.nec.com (8.9.3/8.9.2) with ESMTP id SAA16399 for ; Wed, 16 Jan 2002 18:03:38 -0800 (PST) Date: Wed, 16 Jan 2002 18:03:37 -0800 (PST) Message-Id: <20020116.180337.46622827.hino@ccrl.sj.nec.com> To: stable@FreeBSD.ORG Subject: 4.5-RC1: S/Key -> Opie From: Koji Hino Organization: C&C Research Laboratories (CCRL), NEC USA, Inc. X-Mailer: Mew version 2.2rc1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG One more issue about sshd/opie on 4.5-RC1. If I added entry to /etc/skeykeys, ftpd and telnetd happily accept S/Key. sshd also accept it if SSH version 1 protocol is used. But, sshd do not understand S/Key with SSH version 2 protocol. sshd only use opie if SSH version 2 protocol is used. Anyway, upgrading users who utilize S/Key to login thru SSH should be notified by RELNOTES. Best regards, ==================================================================== Koji HINO(HINO is my family name) C&C Research Laboratories, NEC USA, Inc. E-mail: hino@ccrl.sj.nec.com ---------- DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of NEC USA, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 18:43: 7 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ntplx.net (mail5.ntplx.net [204.213.176.70]) by hub.freebsd.org (Postfix) with ESMTP id 09E7537B405 for ; Wed, 16 Jan 2002 18:43:01 -0800 (PST) Received: from ntplx.net (dhcp-209-54-75-202.ct.dsl.ntplx.com [209.54.75.202]) by mail.ntplx.net (8.11.6/8.11.4/NETPLEX) with ESMTP id g0H2gvj17010; Wed, 16 Jan 2002 21:42:57 -0500 (EST) Message-ID: <3C4639F0.C6409544@ntplx.net> Date: Wed, 16 Jan 2002 21:41:52 -0500 From: Ted Sikora Organization: UnixOS2.org X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: John Polstra , "freebsd-stable@FreeBSD.ORG" Subject: Re: Port cvsup problem... (Solved) References: <20020115190027.A5224@infocom.kh.ua> <200201161651.g0GGpdK49758@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Polstra wrote: > > In article <20020115190027.A5224@infocom.kh.ua>, > Aleksey Ovcharenko wrote: > > Than trying to update doc's tree via cvs I got: > > Aleksey sent me a bunch more information about this, and I know what > the problem is. If you install ezm3 without first removing pm3, you > end up with left-over Modula-3 shared libraries from the pm3 port. > These get used instead of the proper static libraries which come > with ezm3. There are some incompatibilities between the libraries, > and these cause the problems people are seeing. > > If you are seeing problems with cvsup-16.1f, run "ldd > /usr/local/bin/cvsup". It should not list any Modula-3 libraries. > You can recognize them because they are all under "/usr/local/lib/m3". > > The solution is: pkg_delete all pm3-* ports, the ezm3 port, and the > cvsup port. Then "rm -rf /usr/local/lib/m3" if it is present. Then > rebuild and install the cvsup port. > > I will see if I can fix the ezm3 port so that it ignores left-over > Modula-3 shared libraries. No guarantees, though. To be safe you > have to pkg_delete all other Modula-3 ports before installing it. Followed your advice and it worked perfectly after deleting all the files in /usr/sup/src-* ... thanks. TreeList failed: Error in "/usr/sup/src-all/checkouts.cvs:RELENG_4": x x 21324: File is not sorted properly. Delete it and try again. x file "/usr/ports/net/cvsup/work/cvsup-snap-16.1f/suplib/src/FileStatus.m3", line 586 use option @M3stackdump to get a stack trace Abort trap - core dumped -- Ted Sikora tsikora@ntplx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 19:51:45 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id DE61D37B400 for ; Wed, 16 Jan 2002 19:51:41 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g0H3pel23546; Wed, 16 Jan 2002 20:51:40 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g0H3pcx91077; Wed, 16 Jan 2002 20:51:39 -0700 (MST) (envelope-from imp@village.org) Date: Wed, 16 Jan 2002 20:51:16 -0700 (MST) Message-Id: <20020116.205116.56511571.imp@village.org> To: Richard.Shaw@mondus.com Cc: Freebsd-stable@FreeBSD.ORG Subject: Re: PCI Wavelan cards under 4.4 From: "M. Warner Losh" In-Reply-To: <851336E23970B348A23A1A46DB20D64F0F99EA@ukmail02.internal.mondus.com> References: <851336E23970B348A23A1A46DB20D64F0F99EA@ukmail02.internal.mondus.com> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <851336E23970B348A23A1A46DB20D64F0F99EA@ukmail02.internal.mondus.com> "Richard Shaw" writes: : I'm attempting to get a 3com wavelan 3crwe777a PCI card working under : 4.4 Release. I've trawled for posts on this and have found plenty : mentioning how easy it was to get the ISA version working, but have : had no solid confirmations that the PCI one will work. There have : been mumblings of incompatibilities with some motherboards, talk of : support coming soon but nothing definite. Has anyone set one up, or : managed to get one working ? I've *NEVER* had a report of 3com wavelan cards working with the wi driver, although they have a PRISM II chipset. PCI has nothing to do with that. :-) Also, for PCI to work, (the BIOS *MUST* route an interrupt or the routing BIOS must be able to do it) and you can't, on some motherboards, put the card behind a bridge, since the PCI interrupt bridge swizzle isn't implemented on -stable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 19:52:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2128937B404 for ; Wed, 16 Jan 2002 19:52:22 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g0H3qKl23580; Wed, 16 Jan 2002 20:52:21 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g0H3qJx91103; Wed, 16 Jan 2002 20:52:19 -0700 (MST) (envelope-from imp@village.org) Date: Wed, 16 Jan 2002 20:51:57 -0700 (MST) Message-Id: <20020116.205157.32432381.imp@village.org> To: jandrese@mitre.org Cc: Richard.Shaw@mondus.com, Freebsd-stable@FreeBSD.ORG Subject: Re: PCI Wavelan cards under 4.4 From: "M. Warner Losh" In-Reply-To: <3C458F36.659269C5@mitre.org> References: <851336E23970B348A23A1A46DB20D64F0F99E9@ukmail02.internal.mondus.com> <3C458F36.659269C5@mitre.org> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <3C458F36.659269C5@mitre.org> Jason Andresen writes: : I was under the impression the PCI versions won't work until FreeBSD 5 : because the PCI version effectivly requires newcard. The "PCI" card : here is really just a PCCARD controller on an PCI card that you : plug an off-the-shelf Wavelan/Orinoco card into. That was the original plan, but starting with 4.4 you can use PCI add-in cards with 16-bit cards on FreeBSD. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 20:31:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 7E7BC37B402 for ; Wed, 16 Jan 2002 20:31:46 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id PAA05730 for ; Thu, 17 Jan 2002 15:31:44 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01KD6L4J1PG0VFF3ZT@cim.alcatel.com.au> for freebsd-stable@freebsd.org; Thu, 17 Jan 2002 15:31:58 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g0H4Vge53073 for freebsd-stable@freebsd.org; Thu, 17 Jan 2002 15:31:42 +1100 Content-return: prohibited Date: Thu, 17 Jan 2002 15:31:41 +1100 From: Peter Jeremy Subject: NTP packet routing problem To: freebsd-stable@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org Message-id: <20020117153141.P72285@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm having a problem with NTP packets being routed via the wrong interface. Specifically, given the following network, with NTP peering between host1 and host2, host2 will send NTP packets to host1 via the ethernet rather than via PPP following a temporary link outage. Other TCP traffic seems to be routed normally. +------+ +------+ +------+ | | ppp | | fxp0 | | |host1 |-------|host2 |-------| net2 | | | | | | | +------+ +------+ +------+ "ppp" is a dial-on-demand link that is initiated by host1 using ppp(8) (the PPP link addresses are static). "enet" are the ethernet links to the LANs (net1 and net2). "host2.ppp" refers to the IP address of the PPP interface on host2 etc. Both hosts are running 4.4-STABLE from mid-December (just before the 4.5 freeze). host2 is running ipfw rules to block "invalid" packets. The hosts were happily exchanging PPP packets until the PPP link dropped out. ntpd on host2 then started reporting "permission denied" on every attempt to send a packet to host1 - even after the PPP link was restored. Looking at the ipfw logs, I find: Jan 17 12:07:47 host2 /kernel: ipfw: 12000 Deny UDP host2-ppp:123 host1-ppp:123 out via fxp0 Those addresses are correct, but the packet should be going via tun0 not fxp0. The routing table on host2 looks like: tcsbrpc# netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.123.1 UGSc 1 2756 fxp0 localhost localhost UH 1 520 lo0 host2-ppp host1-ppp UH 7 10208 tun0 net2 link#1 UC 6 0 fxp0 router x:x:xx:x:xx:xx UHLW 1 0 fxp0 75 host3 x:x:x:x:x:xx UHLW 2 3397 fxp0 4 host4 x:x:x:x:x:xx UHLW 0 8525 fxp0 1094 host5 x:x:x:x:x:xx UHLW 2 747 fxp0 1084 host6 x:x:x:x:x:xx UHLW 4 11467 fxp0 1161 host2-fxp0 x:x:xx:xx:xx:xx UHLW 1 2 lo0 I've tried playing with the routing tables with no effect. Restarting ntpd has restored the expected behaviour - but presumably only until the next link outage. Has anyone else seen this behaviour? Can anyone offer any suggestions? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 20:44:45 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.snickers.org (mail.snickers.org [216.126.90.4]) by hub.freebsd.org (Postfix) with ESMTP id 7CE2F37B417 for ; Wed, 16 Jan 2002 20:44:42 -0800 (PST) Received: by mail.snickers.org (Postfix, from userid 66) id 626B254; Wed, 16 Jan 2002 23:47:57 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by asherah.dyndns.org (Postfix) with ESMTP id EB1485EF0E; Wed, 16 Jan 2002 23:42:03 -0500 (EST) Received: by asherah.dyndns.org (Postfix, from userid 701954) id 42EA45EF0C; Wed, 16 Jan 2002 23:42:02 -0500 (EST) Date: Wed, 16 Jan 2002 23:42:02 -0500 From: Josh Tiefenbach To: David Bogen Cc: Simon Heath , Koji Hino , stable@FreeBSD.ORG Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? Message-ID: <20020116234202.B33314@zipperup.org> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> <20020116180508.A11693@hardy.mskcc.org> <20020116181943.B30361@zipperup.org> <3C4614CE.8050001@bogen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C4614CE.8050001@bogen.org>; from db@bogen.org on Wed, Jan 16, 2002 at 04:03:26PM -0800 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Picking random message to reply to] Toggling the SkeyAuthentication knob on the server side seems to have quelled the opie requests. josh -- 'Stay fuzzy. Save the world. Choices.' - Daxter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 21: 3:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 51C3D37B404 for ; Wed, 16 Jan 2002 21:03:22 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020117050321.DPTM10199.rwcrmhc53.attbi.com@bmah.dyndns.org>; Thu, 17 Jan 2002 05:03:21 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id g0H53KZ15935; Wed, 16 Jan 2002 21:03:20 -0800 (PST) (envelope-from bmah) Message-Id: <200201170503.g0H53KZ15935@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Thomas Seck Cc: stable@FreeBSD.ORG Subject: Re: what's vnlru? In-reply-to: <20020116135318.GA427@laurel.seck.home> References: <200201151618468.SM01176@141.com> <200201160101.g0G117r64693@apollo.backplane.com> <20020116104904.A2800@shikima.mine.nu> <20020116135318.GA427@laurel.seck.home> Comments: In-reply-to Thomas Seck message dated "Wed, 16 Jan 2002 14:53:18 +0100." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Jan 2002 21:03:20 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If memory serves me right, Thomas Seck wrote: > # Rasputin (rasputin@submonkey.net): > > [vnlru] > > > Thansk for the overview - it's not a performance issue, I just checked > > another fairly recent (4.5 pre) BSD box and didn't see it, > > so thought I'd better check it out. > > > > [ Is this the sort of thing that should go into UPDATING? ] No. UPDATING is for issues that could pose particular obstacles to people upgrading, not for documenting general changes. > I'd vote for a short description in the release notes (I did not > overlook them for a few months, so I do not know whether Bruce Mah > picked it up already). I'm working on it, thanks in part to dillon's recent post here. (It's weird seeing people mention me in random threads!) Cheers, Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 21:35:30 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 9DD1037B402 for ; Wed, 16 Jan 2002 21:35:25 -0800 (PST) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA57569; Thu, 17 Jan 2002 16:35:19 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (localhost [127.0.0.1]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA03202; Thu, 17 Jan 2002 16:35:19 +1100 (EST) Message-Id: <200201170535.QAA03202@lightning.itga.com.au> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 From: Gregory Bond To: Peter Jeremy Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NTP packet routing problem In-reply-to: Your message of Thu, 17 Jan 2002 15:31:41 +1100. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Jan 2002 16:35:18 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've seen similar problems with PPP links over ssh - the link comes up, but on the PPP host the route to the remote end is via the ether interface. This is true for all pkts, not just ntp (which doesn't run over this particular link). You can fix it by deleting a static route on the ppp host, and it all starts working again. I _think_ this is caused by ppp not removing routes it adds before the tunX interface goes down, and then the kernel re-binds the route via a seemingly viable non-down interface (i.e. the default route), and won't re-bind it when the tunX interface comes up. But it happens rarely so I've not nailed down the exact circumstances. Yours sounds like the same problem, but the kill-&-restart ntp works because killing it releases the last usecount on the bogus route, so it gets dropped and then recreated properly when you restart ntp. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 21:48:24 2002 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 97E3837B405 for ; Wed, 16 Jan 2002 21:48:18 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id QAA15352; Thu, 17 Jan 2002 16:48:14 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01KD6NSHFZHS5IJ8QC@cim.alcatel.com.au>; Thu, 17 Jan 2002 16:48:33 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g0H5mBV53402; Thu, 17 Jan 2002 16:48:11 +1100 Content-return: prohibited Date: Thu, 17 Jan 2002 16:48:11 +1100 From: Peter Jeremy Subject: Re: NTP packet routing problem In-reply-to: <200201170535.QAA03202@lightning.itga.com.au>; from gnb@itga.com.au on Thu, Jan 17, 2002 at 04:35:18PM +1100 To: Gregory Bond Cc: freebsd-stable@FreeBSD.ORG Mail-Followup-To: Gregory Bond , freebsd-stable@FreeBSD.ORG Message-id: <20020117164811.T72285@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200201170535.QAA03202@lightning.itga.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-Jan-17 16:35:18 +1100, Gregory Bond wrote: >I've seen similar problems with PPP links over ssh - the link comes >up, but on the PPP host the route to the remote end is via the ether >interface. This is true for all pkts, not just ntp (which doesn't >run over this particular link). You can fix it by deleting a static >route on the ppp host, and it all starts working again. Except I can get other IP traffic through the PPP link - it's just NTP. Also, creating/deleting static routes didn't have any effect. >I _think_ this is caused by ppp not removing routes it adds before >the tunX interface goes down, and then the kernel re-binds the route >via a seemingly viable non-down interface (i.e. the default route), >and won't re-bind it when the tunX interface comes up. But it >happens rarely so I've not nailed down the exact circumstances. With everything working correctly, I can't see any cloned routes. When the link drops next time, I'll have a closer look at the routing table innards. I will also try and reproduce the problem on a system that I have physical access to. Maybe some ntpd debugging or tracing might suggest something. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 16 23:33:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.innovativeinternet.net (ns3.innovativeinternet.net [208.244.165.3]) by hub.freebsd.org (Postfix) with ESMTP id 9A5C637B405 for ; Wed, 16 Jan 2002 23:33:11 -0800 (PST) Received: from pcpsj.pfcs.com (harlan.xecu.net [216.127.150.112]) by mail.innovativeinternet.net (Postfix) with ESMTP id CC9A428C6; Thu, 17 Jan 2002 02:33:02 -0500 (EST) Received: from brown.pfcs.com (brown.pfcs.com [192.52.69.44]) by pcpsj.pfcs.com (Postfix) with ESMTP id 1524AD367; Thu, 17 Jan 2002 01:06:58 -0500 (EST) Received: from localhost.pfcs.com [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 17 Jan 2002 01:06:58 -0500 (EST) To: Peter Jeremy Cc: Gregory Bond , freebsd-stable@FreeBSD.ORG, Harlan.Stenn@pfcs.com Subject: Re: NTP packet routing problem In-Reply-To: Peter Jeremy's (peter.jeremy@alcatel.com.au) message dated Thu, 17 Jan 2002 16:48:11. <20020117164811.T72285@gsmx07.alcatel.com.au> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd2.2.8) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Thu, 17 Jan 2002 01:06:57 -0500 Message-ID: <13699.1011247617@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It might also be the NTP associations - ntpd makes it associations based on the IP of the local machine, and if your PPP link goes down/up and you get a new IP then ntpd will continue to attempt to communicate using its old IP address (association). In this case one of the better answers is to use linkup and linkdown scripts that uses ntpdc(?) to tear down the old association (during linkdown) and brings up a new association during the linkup script. I have no idea if you can avoid this problem by having ntpd bind to a (permanent) local address and then use NAT for the periodic connections. OBTW, if you are using PPP connections for NTP it's probably a good idea to use both the "burst" and "tinker huffpuff 7200" (more or less) things in your ntp.conf file. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 5:29: 5 2002 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.kharkov.ukrpack.net (ns.kharkov.ukrpack.net [212.1.112.1]) by hub.freebsd.org (Postfix) with SMTP id A2CB337B400 for ; Thu, 17 Jan 2002 05:28:54 -0800 (PST) Received: (qmail 24653 invoked by uid 518); 17 Jan 2002 13:28:42 -0000 From: "Aleksey Ovcharenko" Date: Thu, 17 Jan 2002 15:28:42 +0200 To: John Polstra Cc: freebsd-stable@freebsd.org Subject: Re: Port cvsup problem... Message-ID: <20020117152842.A23203@infocom.kh.ua> References: <20020116085924.A10236@infocom.kh.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jdp@polstra.com on Wed, Jan 16, 2002 at 07:38:56AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 16, 2002 at 07:38:56AM -0800, John Polstra wrote: > Aleksey, > > Thanks for the detailed information. I think I know what the > problem is. > > >> Did you build the cvsup port yourself, or did you install a package > >> from an FTP site? > >> > > Build from port ports/net/cvsup-without-gui ... > > > >> If you built the port yourself, did it use the ezm3 Modula-3 compiler? > >> You can find out if ezm3 is installed by looking at the output from > >> "pkg_info". > >> > ># pkg_info | grep ezm3 > > ezm3-1.0 Easier, more portable Modula-3 distribution for building CV > > Good ... > > >> What is the output from "ldd /usr/local/bin/cvsup"? > >> > ># ldd /usr/local/bin/cvsup > > /usr/local/bin/cvsup: > > libset.so.7 => /usr/local/lib/m3/FreeBSD4/libset.so.7 (0x280cc000) > > libm3tcp.so.7 => /usr/local/lib/m3/FreeBSD4/libm3tcp.so.7 (0x280d6000) > > libTempFiles.so.7 => /usr/local/lib/m3/FreeBSD4/libTempFiles.so.7 > > (0x280de000) > > libm3.so.7 => /usr/local/lib/m3/FreeBSD4/libm3.so.7 (0x280e1000) > > libm3core.so.7 => /usr/local/lib/m3/FreeBSD4/libm3core.so.7 (0x2817e000) > > libutil.so.3 => /usr/lib/libutil.so.3 (0x281d5000) > > libmd.so.2 => /usr/lib/libmd.so.2 (0x281de000) > > libm.so.2 => /usr/lib/libm.so.2 (0x281e7000) > > libc.so.4 => /usr/lib/libc.so.4 (0x28203000) > > Aha, this is wrong! All of the Modula-3 libraries (from "libset" to > "libm3core") should be linked statically. The ezm3 port doesn't even > create shared versions of the Modula-3 libraries. I bet these shared > libraries were left over from a previous Modula-3 port such as pm3. > > I recommend that you pkg_delete ezm3-1.0 and cvsup-16.1f, and then "rm > -rf /usr/local/lib/m3". Then rebuild the cvsup port and see if the > problem is solved. Please let me know what happens. > > Maybe I can fix the ezm3 port so that it ignores shared Modula-3 > libraries even if they are present. > > I bet this is why some other people are having problems, too. > Yep, this was the problem. Now cvsup works fine. Thanks a lot! -- Sincerely Yours, Aleksey Ovcharenko postmaster@ic.kharkov.ua Postmaster JV "Infocom" nic-hdl: OAA1-RIPE Kharkov Dep. UA uanic-hdl: AO13-UANIC Phone: +380 (572) 275 851 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 6:32:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from atos.sr.se (atos.sr.se [192.121.194.132]) by hub.freebsd.org (Postfix) with ESMTP id 90EA337B402 for ; Thu, 17 Jan 2002 06:32:31 -0800 (PST) Received: from honken.sr.se (honken.sr.se [134.25.128.27]) by atos.sr.se (8.11.6/8.11.6) with ESMTP id g0HEWMo68865 for ; Thu, 17 Jan 2002 15:32:23 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id PAA12716 for ; Thu, 17 Jan 2002 15:32:22 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: (from root@localhost) by pluto.sr.se (8.11.6/8.11.1) id g0HEWMW41342 for freebsd-stable@freebsd.org; Thu, 17 Jan 2002 15:32:22 +0100 (CET) (envelope-from gunnar) Received: (from gunnar@localhost) by pluto.sr.se (8.11.6/8.11.1av) id g0HEWJq41334 for freebsd-stable@freebsd.org; Thu, 17 Jan 2002 15:32:19 +0100 (CET) (envelope-from gunnar) Date: Thu, 17 Jan 2002 15:32:19 +0100 From: Gunnar Flygt To: FreeBSD Stable Subject: Using ISO8859 and perl Message-ID: <20020117153219.A41263@sr.se> Reply-To: Gunnar Flygt Mail-Followup-To: Gunnar Flygt , FreeBSD Stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG When I start pkg_version I get the following startinfo: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = (unset), LC_CTYPE = "sv_SE.ISO8859-1", LANG = "sv_SE.ISO8859-1" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). How can I make perl aware of local language settings. Maybe not a "stable" question, but since it's the only list I'm connected to :) But of course the system is -STABLE -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 8:35: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id E56D437B400 for ; Thu, 17 Jan 2002 08:34:51 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020117163451.PER5944.rwcrmhc51.attbi.com@bmah.dyndns.org>; Thu, 17 Jan 2002 16:34:51 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id g0HGYpD22958; Thu, 17 Jan 2002 08:34:51 -0800 (PST) (envelope-from bmah) Message-Id: <200201171634.g0HGYpD22958@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Josh Tiefenbach Cc: Koji Hino , stable@FreeBSD.ORG Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? In-reply-to: <20020116155436.A28166@zipperup.org> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> Comments: In-reply-to Josh Tiefenbach message dated "Wed, 16 Jan 2002 15:54:36 -0500." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Jan 2002 08:34:51 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If memory serves me right, Josh Tiefenbach wrote: > > After doing some tests, I found that connecting to this 4.5-RC1 box > > from other machine by OpenSSH (without RSA/DSA key, nor rhost*auth, > > assuming to use plain password to login), requires opie to login, > > though /etc/opiekeys, and /etc/skeykeys are both size 0. If I start > > openssh with flag '-1', which means to use OpenSSH version 1 protocol, > > it works fine: require plain password. I checked 4.4-RELEASE machine, > > and found that it works fine without '-1' flag, and even with '-2', it > > works. [snip] > Perhaps its an OpenSSH v3 thing? If I have some time tonite, I'll go compile > up v3 someplace and check it out. Did you get a chance to do this? I'm unable to reproduce this problem between two RELENG_4 machines running the base system OpenSSH (both machines built within the last three days). Usually I use a DSA keypair to authenticate, but I temporarily blew away ~/.ssh/authorized_keys2 on the server side and ~/ .ssh/id_dsa on the client side. Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 8:35:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id B38D837B41C for ; Thu, 17 Jan 2002 08:35:50 -0800 (PST) Received: from d1o913.telia.com (d1o913.telia.com [195.252.44.241]) by maile.telia.com (8.11.6/8.11.6) with ESMTP id g0HGZmS11171 for ; Thu, 17 Jan 2002 17:35:49 +0100 (CET) Received: from falcon.midgard.homeip.net (h185n2fls20o913.telia.com [212.181.163.185]) by d1o913.telia.com (8.8.8/8.8.8) with SMTP id RAA19970 for ; Thu, 17 Jan 2002 17:35:48 +0100 (CET) Received: (qmail 95876 invoked by uid 1001); 17 Jan 2002 16:35:46 -0000 Date: Thu, 17 Jan 2002 17:35:46 +0100 From: Erik Trulsson To: Gunnar Flygt Cc: FreeBSD Stable Subject: Re: Using ISO8859 and perl Message-ID: <20020117163546.GA95852@student.uu.se> Mail-Followup-To: Gunnar Flygt , FreeBSD Stable References: <20020117153219.A41263@sr.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020117153219.A41263@sr.se> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jan 17, 2002 at 03:32:19PM +0100, Gunnar Flygt wrote: > When I start pkg_version I get the following startinfo: > perl: warning: Setting locale failed. > perl: warning: Please check that your locale settings: > LC_ALL = (unset), > LC_CTYPE = "sv_SE.ISO8859-1", > LANG = "sv_SE.ISO8859-1" > are supported and installed on your system. > perl: warning: Falling back to the standard locale ("C"). > > How can I make perl aware of local language settings. Maybe not a > "stable" question, but since it's the only list I'm connected to :) > > But of course the system is -STABLE Assuming you have recent enough system (so that the sv_SE.ISO8859-1 locale actually exists) you shouldn't have to do anything. I just tried running pkg_version with LC_ALL, LC_CTYPE and LANG set as above and I didn't get any warnings at all. I am running 4.5-RC from Jan 10. Since that locale name was added fairly recently I suggest to update your system to the latest -STABLE if you haven't already done so within the last week or so. (In case your system doesn't have that locale installed.) -- Erik Trulsson ertr1013@student.uu.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 9: 5:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by hub.freebsd.org (Postfix) with ESMTP id 022AB37B41A for ; Thu, 17 Jan 2002 09:05:15 -0800 (PST) Received: (from wayne@localhost) by manor.msen.com (8.9.3/8.9.3) id MAA68551 for freebsd-stable@FreeBSD.ORG; Thu, 17 Jan 2002 12:05:11 -0500 (EST) (envelope-from wayne) Date: Thu, 17 Jan 2002 12:05:11 -0500 From: "Michael R. Wayne" To: freebsd-stable@FreeBSD.ORG Subject: Re: Force keyboard detection flag? Message-ID: <20020117120511.W73347@staff.msen.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from doconnor@gsoft.com.au on Tue, Jan 15, 2002 at 06:21:30PM +1030 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I started to look through the kernel code for keyboard detection with plans toward having a sysctl that forces the keyboard at run time, rather than kernel compile. But I got sidetracked. Related problems come up so often that I am convinced that such a fix is required. Me finding time to implement is a problem. /\/\ \/\/ On Tue, Jan 15, 2002 at 06:21:30PM +1030, Daniel O'Connor wrote: > I was wondering if there is a flag to force the kernel to detect a PS/2 > keyboard even if it doesn't detect one. > > The usual answer is 'set atkbdc flags to 0x0' but you can't do that if you are > installing for the first time - when you boot -c the config prompt is printed > in an infinite loop :( > > The newer keyboards I have (Mitsubishi Diamond Touch) do not get detected by > FreeBSD so every time I need to install from a base CD I have to dig up my > detectable keyboard and hot swap it after the detection phase. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 9:18:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tesla.foo.is (tesla.reverse-bias.org [217.151.166.96]) by hub.freebsd.org (Postfix) with ESMTP id 895D237B404 for ; Thu, 17 Jan 2002 09:18:25 -0800 (PST) Received: from germanium (germanium.reverse-bias.org [192.168.1.1]) by tesla.foo.is (Postfix) with SMTP id DD46A274C; Thu, 17 Jan 2002 17:18:18 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" From: Baldur Gislason To: "Michael R. Wayne" Subject: Re: Force keyboard detection flag? Date: Thu, 17 Jan 2002 17:21:14 +0000 X-Mailer: KMail [version 1.2] References: <20020117120511.W73347@staff.msen.com> In-Reply-To: <20020117120511.W73347@staff.msen.com> Cc: freebsd-stable@freebsd.org MIME-Version: 1.0 Message-Id: <0201171721140C.03869@germanium> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Have you never compiled your own kernel? Here's a paste from LINT: # `flags' for atkbd: # 0x01 Force detection of keyboard, else we always assume a keyboard # 0x02 Don't reset keyboard, useful for some newer ThinkPads # 0x04 Old-style (XT) keyboard support, useful for older ThinkPads And GENERIC has: device atkbd0 at atkbdc? irq 1 flags 0x1 Remove the 0x1 flag and recompile, also a look at the boot(8) manpage: -P probe the keyboard. If no keyboard is found, the -D and -h options are automatically set. Remove the -P from /boot.config Baldur On Thursday 17 January 2002 17:05, you wrote: > I started to look through the kernel code for keyboard detection > with plans toward having a sysctl that forces the keyboard at run > time, rather than kernel compile. But I got sidetracked. > > Related problems come up so often that I am convinced that such a > fix is required. Me finding time to implement is a problem. > > /\/\ \/\/ > > On Tue, Jan 15, 2002 at 06:21:30PM +1030, Daniel O'Connor wrote: > > I was wondering if there is a flag to force the kernel to detect a PS/2 > > keyboard even if it doesn't detect one. > > > > The usual answer is 'set atkbdc flags to 0x0' but you can't do that if > > you are installing for the first time - when you boot -c the config > > prompt is printed in an infinite loop :( > > > > The newer keyboards I have (Mitsubishi Diamond Touch) do not get detected > > by FreeBSD so every time I need to install from a base CD I have to dig > > up my detectable keyboard and hot swap it after the detection phase. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 9:28: 3 2002 Delivered-To: freebsd-stable@freebsd.org Received: from spider.nic-se.se (spider.nic-se.se [212.247.3.67]) by hub.freebsd.org (Postfix) with ESMTP id 870DD37B405 for ; Thu, 17 Jan 2002 09:28:00 -0800 (PST) Received: from localhost (dufberg@localhost) by spider.nic-se.se (8.11.1/8.11.1) with ESMTP id g0HHRrt17377; Thu, 17 Jan 2002 18:27:53 +0100 (CET) X-Authentication-Warning: spider.nic-se.se: dufberg owned process doing -bs Date: Thu, 17 Jan 2002 18:27:53 +0100 (CET) From: Mats Dufberg To: Gunnar Flygt Cc: FreeBSD Stable Subject: Re: Using ISO8859 and perl In-Reply-To: <20020117153219.A41263@sr.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Jan 17, 2002, 15:32 (+0100) Gunnar Flygt wrote: > When I start pkg_version I get the following startinfo: > perl: warning: Setting locale failed. > perl: warning: Please check that your locale settings: > LC_ALL = (unset), > LC_CTYPE = "sv_SE.ISO8859-1", > LANG = "sv_SE.ISO8859-1" > are supported and installed on your system. > perl: warning: Falling back to the standard locale ("C"). I think you have misspelled the data. I have LANG=sv_SE.ISO_8859-1 Mats ---------------------------------------------------------------------- Mats Dufberg ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 10: 2: 2 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ledzep.dyndns.org (12-237-138-17.client.attbi.com [12.237.138.17]) by hub.freebsd.org (Postfix) with ESMTP id C730C37B416; Thu, 17 Jan 2002 10:01:56 -0800 (PST) Received: from attbi.com (localhost [127.0.0.1]) by ledzep.dyndns.org (8.11.6/8.11.6) with ESMTP id g0HI1tV10742; Thu, 17 Jan 2002 12:01:56 -0600 Message-ID: <3C471191.1090406@attbi.com> Date: Thu, 17 Jan 2002 12:01:53 -0600 From: Jordan Breeding User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Questions about upcoming FreeBSD 4.5... Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * I am not subscribed to this list, please cc: me in any replies * I have a few questions about FreeBSD, I have been using Linux and Unix now for quite some time but am considering switching my home system to FreeBSD. One question I have is this, in linux even though there is a text console by default (using vga) you can use a frame buffer console for just about any video card out right now so that I am able to use my brand new ATI Radeon 7500 to have a console which is at 1280x1024 at 8bit depth with a refresh of 85 Hz, is this possible in FreeBSD or are only certain cards able to be used in frame buffer mode for virtual consoles? Also I only have a USB keyboard currently and when I boot up from FreeBSD 4.2 or 4.3 bootable CDs they do not detect my keyboard once the kernel has booted and I can not navigate the install menu at all, FreeBSD 4.4 seems to not boot at all on my system because it always hangs at the "detecting hardware" message, then today I downloaded the FreeBSD 4.5-RC1-cdboot iso and it at least booted again, and booted quite speadily using the new cdboot process but then once I am to the menu to begin installing it still will not work with my USB keyboard. Will there ever be support for USB keyboards during the installation process? If there will not be and I can borrow a PS2 keyboard for a while is there at least support for USB keyboards on virtual consoles and X Windows? Thank you for any information. Jordan Breeding To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 10:43: 5 2002 Delivered-To: freebsd-stable@freebsd.org Received: from columbus.cris.net (columbus.cris.net [212.110.128.65]) by hub.freebsd.org (Postfix) with ESMTP id C710C37B419 for ; Thu, 17 Jan 2002 10:43:00 -0800 (PST) Received: from phantom.cris.net (phantom.cris.net [212.110.130.74]) by columbus.cris.net (8.9.3/8.9.3) with ESMTP id UAA50694; Thu, 17 Jan 2002 20:42:55 +0200 (EET) Received: (from ml@localhost) by phantom.cris.net (8.11.1/8.11.1) id g0HIiuo40575; Thu, 17 Jan 2002 20:44:56 +0200 (EET) (envelope-from ml) Date: Thu, 17 Jan 2002 20:44:55 +0200 From: Alexey Zelkin To: Gunnar Flygt Cc: FreeBSD Stable Subject: Re: Using ISO8859 and perl Message-ID: <20020117204455.A40506@phantom.cris.net> References: <20020117153219.A41263@sr.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020117153219.A41263@sr.se>; from flygt@sr.se on Thu, Jan 17, 2002 at 03:32:19PM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, On Thu, Jan 17, 2002 at 03:32:19PM +0100, Gunnar Flygt wrote: > When I start pkg_version I get the following startinfo: > perl: warning: Setting locale failed. > perl: warning: Please check that your locale settings: > LC_ALL = (unset), > LC_CTYPE = "sv_SE.ISO8859-1", > LANG = "sv_SE.ISO8859-1" > are supported and installed on your system. > perl: warning: Falling back to the standard locale ("C"). > > How can I make perl aware of local language settings. Maybe not a > "stable" question, but since it's the only list I'm connected to :) Please check existence of directory: /usr/share/locale/sv_SE.ISO8859-1 If this directory is missing then just upgrade to -STABLE (support for ISO8859-1 names was commited week ago) Or just switch your environment to use sv_SE.ISO_8859-1. > But of course the system is -STABLE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 11:53:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id B105C37B41D for ; Thu, 17 Jan 2002 11:53:02 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id GAA16173; Fri, 18 Jan 2002 06:53:00 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01KD7HAT4HSG5IJFVW@cim.alcatel.com.au>; Fri, 18 Jan 2002 06:53:18 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g0HJquP28448; Fri, 18 Jan 2002 06:52:56 +1100 Content-return: prohibited Date: Fri, 18 Jan 2002 06:52:56 +1100 From: Peter Jeremy Subject: Re: NTP packet routing problem In-reply-to: <13699.1011247617@brown.pfcs.com>; from Harlan.Stenn@pfcs.com on Thu, Jan 17, 2002 at 01:06:57AM -0500 To: Harlan Stenn Cc: Gregory Bond , freebsd-stable@FreeBSD.ORG Mail-Followup-To: Harlan Stenn , Gregory Bond , freebsd-stable@FreeBSD.ORG Message-id: <20020118065256.U72285@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <"20020117164811.T72285"@gsmx07.alcatel.com.au> <13699.1011247617@brown.pfcs.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-Jan-17 01:06:57 -0500, Harlan Stenn wrote: >It might also be the NTP associations - ntpd makes it associations based on >the IP of the local machine, and if your PPP link goes down/up and you get a >new IP then ntpd will continue to attempt to communicate using its old >IP address (association). I'm using static IP addresses so that's not it. >OBTW, if you are using PPP connections for NTP it's probably a good idea to >use both the "burst" and "tinker huffpuff 7200" (more or less) things in >your ntp.conf file. Thanks for that. I've enabled "burst", but I missed the "huffpuff". Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 12:10: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by hub.freebsd.org (Postfix) with ESMTP id 9663537B400 for ; Thu, 17 Jan 2002 12:09:57 -0800 (PST) Received: from cs.nott.ac.uk ([62.255.164.232]) by mta03-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020117200956.QVED8780.mta03-svc.ntlworld.com@cs.nott.ac.uk>; Thu, 17 Jan 2002 20:09:56 +0000 Message-ID: <3C473100.8050001@cs.nott.ac.uk> Date: Thu, 17 Jan 2002 20:16:00 +0000 From: Guy Coleman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Gunnar Flygt Cc: FreeBSD Stable Subject: Re: Using ISO8859 and perl References: <20020117153219.A41263@sr.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Gunnar Flygt wrote: > When I start pkg_version I get the following startinfo: > perl: warning: Setting locale failed. > perl: warning: Please check that your locale settings: > LC_ALL = (unset), > LC_CTYPE = "sv_SE.ISO8859-1", > LANG = "sv_SE.ISO8859-1" > are supported and installed on your system. > perl: warning: Falling back to the standard locale ("C"). > I'm also seeing this with both en_GB.ISO8859-15 and en_GB.ISO_8859-15 whenever I run perl. /usr/share/locale/en_GB.ISO8859-15 does exist, and I re-built my world/kernel today. Have I missed something? -Guy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 12:52:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from proverbs.outreachnetworks.com (proverbs.outreachnetworks.com [65.196.249.4]) by hub.freebsd.org (Postfix) with SMTP id 2A9FE37B402 for ; Thu, 17 Jan 2002 12:52:26 -0800 (PST) Received: (qmail 69636 invoked from network); 17 Jan 2002 20:52:24 -0000 Received: from unknown (HELO phoncella.outreachnetworks.com) (65.196.249.11) by proverbs.outreachnetworks.com with SMTP; 17 Jan 2002 20:52:24 -0000 Received: (from elh@localhost) by phoncella.outreachnetworks.com (8.11.6/8.11.6) id g0HKqOL03484 for freebsd-stable@freebsd.org; Thu, 17 Jan 2002 15:52:24 -0500 X-Authentication-Warning: phoncella.outreachnetworks.com: elh set sender to elh@outreachnetworks.com using -f Date: Thu, 17 Jan 2002 15:52:24 -0500 From: "Eric L. Howard" To: freebsd-stable@freebsd.org Subject: random crashes on 4.4-S - ASUS CUSL2-M mobo Message-ID: <20020117155224.B2190@outreachnetworks.com> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Favorite-Scripture: Romans 8:18 Theocratic-Rule-Advocate: http://www.crossmovement.com Registered-Secret-Agent: Agent Double-Naught Seven Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm experiencing totally random crashes on a rackmount box. It's a PIII 750 on an ASUS CUSL2-M - onboard 3c920. The crashes are complete random and usually follow processes that die w/ SIGSEGV (a couple of SIGABRT thrown in for good measure have been found also). Syslog gives me info such as... (lines are wrapped) Jan 16 01:03:28 www /kernel: pid 692 (httpd), uid 65534: exited on signal 11 Jan 17 15:09:35 www /kernel: pid 290 (cpp0), uid 0: exited on signal 11 (core dumped) Jan 17 15:36:53 www /kernel: pid 310 (grep), uid 0: exited on signal 11 (core dumped) Jan 17 15:36:57 www /kernel: pid 252 (bash), uid 0: exited on signal 11 (core dumped) Jan 17 15:37:03 www /kernel: pid 313 (grep), uid 0: exited on signal 11 (core dumped) Dec 29 13:43:54 www /kernel: pid 1703 (cvsup), uid 0: exited on signal 6 (core dumped) I've swapped memory at least twice - each time yielding no success. Not sure about how to get anywhere debugging core files - pointers appreciated. Any and all ideas will be appreciated and checked. Thanx. 4.4-STABLE FreeBSD 4.4-STABLE #0: Fri Nov 23 23:41:12 EST 2001 ~elh -- Eric L. Howard e l h @ o u t r e a c h n e t w o r k s . c o m ------------------------------------------------------------------------ www.OutreachNetworks.com 313.297.9900 ------------------------------------------------------------------------ Advocate of the Theocratic Rule To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 13:12:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mikea.ath.cx (okc-65-30-192-11.mmcable.com [65.30.192.11]) by hub.freebsd.org (Postfix) with ESMTP id 3EF5437B419 for ; Thu, 17 Jan 2002 13:12:17 -0800 (PST) Received: (from mikea@localhost) by mikea.ath.cx (8.11.6/8.11.1) id g0HLCGw90591 for freebsd-stable@FreeBSD.ORG; Thu, 17 Jan 2002 15:12:16 -0600 (CST) (envelope-from mikea) Date: Thu, 17 Jan 2002 15:12:16 -0600 From: mikea To: freebsd-stable@FreeBSD.ORG Subject: Re: random crashes on 4.4-S - ASUS CUSL2-M mobo Message-ID: <20020117151216.A90572@mikea.ath.cx> References: <20020117155224.B2190@outreachnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020117155224.B2190@outreachnetworks.com>; from elh@outreachnetworks.com on Thu, Jan 17, 2002 at 03:52:24PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jan 17, 2002 at 03:52:24PM -0500, Eric L. Howard wrote: > I'm experiencing totally random crashes on a rackmount box. It's a PIII 750 > on an ASUS CUSL2-M - onboard 3c920. > > The crashes are complete random and usually follow processes that die w/ > SIGSEGV (a couple of SIGABRT thrown in for good measure have been found > also). > > Syslog gives me info such as... (lines are wrapped) > > Jan 16 01:03:28 www /kernel: pid 692 (httpd), uid 65534: exited on signal 11 > Jan 17 15:09:35 www /kernel: pid 290 (cpp0), uid 0: exited on signal 11 (core dumped) > Jan 17 15:36:53 www /kernel: pid 310 (grep), uid 0: exited on signal 11 (core dumped) > Jan 17 15:36:57 www /kernel: pid 252 (bash), uid 0: exited on signal 11 (core dumped) > Jan 17 15:37:03 www /kernel: pid 313 (grep), uid 0: exited on signal 11 (core dumped) > Dec 29 13:43:54 www /kernel: pid 1703 (cvsup), uid 0: exited on signal 6 (core dumped) > > I've swapped memory at least twice - each time yielding no success. Not > sure about how to get anywhere debugging core files - pointers appreciated. > > Any and all ideas will be appreciated and checked. Thanx. > > 4.4-STABLE FreeBSD 4.4-STABLE #0: Fri Nov 23 23:41:12 EST 2001 Temperature? Can you run a temperature/fan-rpm/whatnot monitor, such as healthd? Totally random w.r.t. system load, or just totally random w.r.t. clock time? Or something else? -- Mike Andrews mikea@mikea.ath.cx Tired old sysadmin since 1964 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 14:29:41 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.nec.com (dns4.nec.com [131.241.15.4]) by hub.freebsd.org (Postfix) with ESMTP id F2E9737B405; Thu, 17 Jan 2002 14:29:36 -0800 (PST) Received: from netkeeper2.sj.nec.com (netkeeper2.sj.nec.com [131.241.31.10]) by mail4.nec.com (/) with ESMTP id g0HMTUe18868; Thu, 17 Jan 2002 14:29:30 -0800 (PST) Received: from ccrl.sj.nec.com (localhost [127.0.0.1]) by netkeeper2.sj.nec.com (8.9.1a/8.9.1) with ESMTP id OAA15778; Thu, 17 Jan 2002 14:29:27 -0800 (PST) Received: from localhost (hirosige [131.241.79.26]) by ccrl.sj.nec.com (8.9.3/8.9.2) with ESMTP id OAA23127; Thu, 17 Jan 2002 14:29:28 -0800 (PST) Date: Thu, 17 Jan 2002 14:29:26 -0800 (PST) Message-Id: <20020117.142926.45265184.hino@ccrl.sj.nec.com> To: green@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? From: Koji Hino In-Reply-To: <20020116.173525.68550113.hino@ccrl.sj.nec.com> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> <20020116180508.A11693@hardy.mskcc.org> <20020116181943.B30361@zipperup.org> <3C4614CE.8050001@bogen.org> <20020116.173525.68550113.hino@ccrl.sj.nec.com> Organization: C&C Research Laboratories (CCRL), NEC USA, Inc. X-Mailer: Mew version 2.2rc1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I send this message to green@freebsd.org, because Brian committed skeychallenge() -> opiechallenge() staff... Brian, could you check this? I change crypto/openssh/auth-chall.c as follows, and test it. --- auth-chall.c.dist Thu Sep 27 18:33:33 2001 +++ auth-chall.c Thu Jan 17 13:28:07 2002 @@ -77,7 +77,7 @@ { static char challenge[1024]; struct opie opie; - if (opiechallenge(&opie, authctxt->user, challenge) == -1) + if (opiechallenge(&opie, authctxt->user, challenge)) return NULL; strlcat(challenge, "\nS/Key Password: ", sizeof challenge); return challenge; It works as expected, ie: * FreeBSD 4.5-RC1 box is in default config. * Client is OpenSSH_3.0.1p1, in default config. (1) If /etc/opiekeys @ FreeBSD box is size=0, opiechallenge return 1, and sshd fall back to plain password. OK. (2) If /etc/opiekeys @ FreeBSD box lists no requested user, same as (1). OK. (3) If there are no /etc/opiekeys @ FreeBSD box, /etc/opiekeys is created automatically, and behave as (1). OK. (4) If requested user is listed on /etc/opiekeys @ FreeBSD box, sshd requests opie password, and happy with correct pass phrase. OK. Koji From: Koji Hino Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? Date: Wed, 16 Jan 2002 17:35:25 -0800 (PST) ID: <20020116.173525.68550113.hino@ccrl.sj.nec.com> :> Thanks to everyone who answered to my question. :> :> OK, there are some workaround to overcome this problem. Then, how :> 4.5-R should be? Disable opie as default sshd configuration? :> :> Or.... :> :> I looked into source (not deeply), and found: :> * opiechallenge() [/usr/src/contrib/opie/libopie/challenge.c] returns :> value: 0, -1, 1. If there are no related user, it seems (I'm not :> checked by debugger. only my understanding..) to return 1. :> * old version, skeychallenge(), only return 0 (OK), or -1 (BAD). :> * get_challenge() [/usr/src/crypto/openssh/auth-chall.c] only check :> return value of opiechallenge() if it is -1. :> :> So, I think get_challenge() should handle '1' case. :> :> Best regards, :> :> ==================================================================== :> Koji HINO(HINO is my family name) :> C&C Research Laboratories, NEC USA, Inc. :> E-mail: hino@ccrl.sj.nec.com :> ---------- :> DISCLAIMER: this message is the author's personal opinion and does not :> constitute the support, opinion, or policy of NEC USA, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 15:37:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by hub.freebsd.org (Postfix) with ESMTP id 888E737B416 for ; Thu, 17 Jan 2002 15:37:17 -0800 (PST) Received: from cs.nott.ac.uk ([62.255.167.225]) by mta03-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020117233715.WRFO8780.mta03-svc.ntlworld.com@cs.nott.ac.uk>; Thu, 17 Jan 2002 23:37:15 +0000 Message-ID: <3C476199.6090405@cs.nott.ac.uk> Date: Thu, 17 Jan 2002 23:43:21 +0000 From: Guy Coleman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Guy Coleman Cc: FreeBSD Stable Subject: Re: Using ISO8859 and perl References: <20020117153219.A41263@sr.se> <3C473100.8050001@cs.nott.ac.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Guy Coleman wrote: > I'm also seeing this with both en_GB.ISO8859-15 and en_GB.ISO_8859-15 > whenever I run perl. I'd missed out a colon in login.conf. Solved! -Guy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 17:42:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 5D15A37B421 for ; Thu, 17 Jan 2002 17:42:17 -0800 (PST) Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.33 #1 (Red Hack)) id 16RO2p-0001P5-00 for ; Fri, 18 Jan 2002 14:42:15 +1300 Date: Fri, 18 Jan 2002 14:42:14 +1300 (New Zealand Daylight Time) From: Juha Saarinen To: freebsd-stable@freebsd.org Subject: Spontaneous reboot mystery Message-ID: X-X-Sender: juha@vimfuego.saarinen.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a remote server that has started rebooting itself for no apparent reason. It looks like a controlled shutdown: # last juha ttyp0 saarinen.org Thu Jan 17 15:15 still logged in reboot ~ Thu Jan 17 15:03 juha ttyp0 saarinen.org Thu Jan 17 13:14 - crash (01:48) reboot ~ Thu Jan 17 13:01 juha ttyp1 saarinen.org Wed Jan 16 15:12 - 15:12 (00:00) juha ttyp0 saarinen.org Wed Jan 16 08:05 - crash (1+04:56) reboot ~ Wed Jan 16 05:58 juha ttyp1 saarinen.org Mon Jan 14 14:36 - 15:09 (1+00:33) juha ttyp0 saarinen.org Mon Jan 14 10:40 - crash (1+19:17) reboot ~ Sun Jan 13 17:34 reboot ~ Sat Jan 12 02:58 reboot ~ Thu Jan 10 21:13 reboot ~ Wed Jan 9 17:42 reboot ~ Tue Jan 8 11:22 reboot ~ Tue Jan 8 10:59 reboot ~ Tue Jan 8 09:36 reboot ~ Mon Jan 7 21:00 reboot ~ Mon Jan 7 20:10 reboot ~ Mon Jan 7 16:23 juha ttyp0 saarinen.org Mon Jan 7 11:30 - 11:39 (00:08) reboot ~ Mon Jan 7 11:29 juha ttyp0 saarinen.org Mon Jan 7 07:57 - crash (03:32) reboot ~ Sun Jan 6 17:51 reboot ~ Sun Jan 6 16:19 reboot ~ Sun Jan 6 15:54 reboot ~ Sun Jan 6 15:23 reboot ~ Sun Jan 6 00:22 reboot ~ Sat Jan 5 14:39 reboot ~ Sat Jan 5 07:58 juha ttyp0 saarinen.org Fri Jan 4 17:25 - 17:28 (00:03) reboot ~ Fri Jan 4 05:18 reboot ~ Thu Jan 3 20:59 reboot ~ Thu Jan 3 18:37 juha ttyp0 saarinen.org Thu Jan 3 16:16 - crash (02:20) reboot ~ Thu Jan 3 16:16 reboot ~ Wed Jan 2 09:44 reboot ~ Wed Jan 2 03:58 ... but I can't find anything that could cause it to reboot at irregular intervals. # uname -a FreeBSD www.searchnow.co.nz 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Dec 4 15:18:45 NZDT 2000 root@www.searchnow.co.nz:/usr/obj/usr/src/sys/SEARCHNOW i386 Could it be some kind of remote 'sploit? -- Juha Take off every sig! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 17:49:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.oskarmobil.cz (smtp1.oskarmobil.cz [217.77.161.133]) by hub.freebsd.org (Postfix) with ESMTP id C43A537B402 for ; Thu, 17 Jan 2002 17:49:27 -0800 (PST) Received: from wh01ex01.ceskymobil.cz (wh01ex01.oskarmobil.cz [172.20.116.17]) by smtp1.oskarmobil.cz (8.11.2/8.11.1) with ESMTP id g0I1ivg22406 for ; Fri, 18 Jan 2002 02:44:57 +0100 (CET) (envelope-from Milon.Papezik@oskarmobil.cz) Received: by wh01ex01.oskarmobil.cz with Internet Mail Service (5.5.2653.19) id ; Fri, 18 Jan 2002 02:46:29 +0100 Message-ID: From: Milon Papezik To: "'freebsd-stable@FreeBSD.org'" Subject: problem with 4.4-RELEASE to 4.5-RC upgrade Date: Fri, 18 Jan 2002 02:46:28 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-2" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I would like to report that I had a problem with upgrade via CVSUP from 4.4-RELEASE to 4.5-RC (freshly cvsuped about 2 hours before sending this message). The problem is with .../sys/modules/libiconv/Makefile where perl gets called with arguments starting with @/... Those files are not found and I hat to chage the @/kern/... into ${.CURDIR}/../../kern/... Could this be fixed before 4.5 ? Thanks in advance, Milon -- milon.papezik@oskarmobil.cz ### Speaking for myself. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 18:38: 3 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vms3.rit.edu (vms3.isc.rit.edu [129.21.3.10]) by hub.freebsd.org (Postfix) with ESMTP id 5DDB237B404 for ; Thu, 17 Jan 2002 18:37:57 -0800 (PST) Received: from sonic.rit.edu ([129.21.10.135]) by ritvax.isc.rit.edu (PMDF V5.2-32 #40294) with ESMTPA id <01KD6XW3QWLYDGJU57@ritvax.isc.rit.edu> for freebsd-stable@freebsd.org; Thu, 17 Jan 2002 21:37:50 EST Date: Thu, 17 Jan 2002 21:37:36 -0500 From: Matt Penna Subject: FreeBSD Memory Requirements Legacy and Present X-Sender: mdp1261@vmspop.isc.rit.edu To: freebsd-stable@freebsd.org Message-id: <5.1.0.14.2.20020117210634.01d8eec0@vmspop.isc.rit.edu> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear folks, I noticed some time ago that the memory requirements in the FreeBSD FAQ, as well as in the files detailing hardware requirements, are no longer accurate. I am working on a PR in hopes of getting this fixed for the benefit of new users, but haven't had much luck in finding the information I need. My apologies if this is a bit off-topic for -stable, but I didn't have much luck on -doc or -questions. I was encouraged to try posting here by more than one person on those lists. Basically, what I'm trying to do is determine the exact minimum memory requirements for FreeBSD's various releases. I'm most interested in what's required to run the installer all the way through in each case, but I am also interested in the amount required to run a usable system. The "5MB for install and 4MB to run" documented in various places is no longer correct, and it seems references to greater amounts such as 12MB and 8MB are based on hearsay or are located in documents that are not trustworthy. Is there anyone here who can tell me when the memory requirements changed, and to exactly what amounts? Is there a reliable way I can determine these numbers on my own? (I use the word "reliable" because, in ignorance, I attempted to run through the installer for 4.3-Release on a system with only 8MB and succeeded without any difficulty whatsoever, though that was apparently impossible. :) Any information would be greatly appreciated. Polite suggestions of other people to bother with this are welcome, as well. :) Please CC me on any replies, as I am not subscribed to -stable. Thanks! Matt -- Matt Penna mdp1261@rit.edu ICQ: 399825 S0ba on AOLIM "The trouble with computers, of course, is that they're very sophisticated idiots." -Dr. Who To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19: 5:45 2002 Delivered-To: freebsd-stable@freebsd.org Received: from zoon.lafn.org (zoon.lafn.org [206.117.18.9]) by hub.freebsd.org (Postfix) with ESMTP id 0027E37B404 for ; Thu, 17 Jan 2002 19:05:43 -0800 (PST) Received: from [10.0.1.90] (66-81-74-13-modem.o1.com [66.81.74.13]) by zoon.lafn.org (8.11.3/8.11.3) with ESMTP id g0I35Z924897; Thu, 17 Jan 2002 19:05:36 -0800 (PST) (envelope-from bc979@lafn.org) Mime-Version: 1.0 X-Sender: bc979@mail.lafn.org Message-Id: In-Reply-To: References: Date: Thu, 17 Jan 2002 19:00:40 -0800 To: Juha Saarinen From: Doug Hardie Subject: Re: Spontaneous reboot mystery Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 14:42 +1300 1/18/02, Juha Saarinen wrote: >I have a remote server that has started rebooting itself for no apparent >reason. It looks like a controlled shutdown: I used to have a server that did that about every 3 days. Take a close look at /var/messages before each reboot. Sometimes a message will make it to the file before the crash and give you an indication what the cause is. Mine were always running out of mbufs. Turning off delayed acks solved it. -- -- Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:14:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 76E6B37B416 for ; Thu, 17 Jan 2002 19:14:52 -0800 (PST) Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.33 #1 (Red Hack)) id 16RPUP-0001Wa-00; Fri, 18 Jan 2002 16:14:49 +1300 Date: Fri, 18 Jan 2002 16:14:49 +1300 (New Zealand Daylight Time) From: Juha Saarinen To: Doug Hardie Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Spontaneous reboot mystery In-Reply-To: Message-ID: X-X-Sender: juha@vimfuego.saarinen.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 17 Jan 2002, Doug Hardie wrote: > I used to have a server that did that about every 3 days. Take a close > look at /var/messages before each reboot. Sometimes a message will > make it to the file before the crash and give you an indication what > the cause is. Mine were always running out of mbufs. Turning off > delayed acks solved it. Nothing in the logs that's helpful. How do I check for mbuf usage? -- Juha Take off every sig! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:20:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rockstar.stealthgeeks.net (h-66-134-120-173.LSANCA54.covad.net [66.134.120.173]) by hub.freebsd.org (Postfix) with SMTP id 48BC037B402 for ; Thu, 17 Jan 2002 19:20:06 -0800 (PST) Received: (qmail 6246 invoked by uid 1001); 18 Jan 2002 03:20:00 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Jan 2002 03:20:00 -0000 Date: Thu, 17 Jan 2002 19:20:00 -0800 (PST) From: Patrick Greenwell To: Juha Saarinen Cc: Doug Hardie , "freebsd-stable@FreeBSD.ORG" Subject: Re: Spontaneous reboot mystery In-Reply-To: Message-ID: <20020117191952.Q6241-100000@rockstar.stealthgeeks.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 18 Jan 2002, Juha Saarinen wrote: > On Thu, 17 Jan 2002, Doug Hardie wrote: > > > I used to have a server that did that about every 3 days. Take a close > > look at /var/messages before each reboot. Sometimes a message will > > make it to the file before the crash and give you an indication what > > the cause is. Mine were always running out of mbufs. Turning off > > delayed acks solved it. > > Nothing in the logs that's helpful. How do I check for mbuf usage? netstat -m /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Patrick Greenwell Stealthgeeks,LLC. Operations Consulting http://www.stealthgeeks.net \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:24:38 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 656D737B416 for ; Thu, 17 Jan 2002 19:24:33 -0800 (PST) Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.33 #1 (Red Hack)) id 16RPdl-0001Wv-00; Fri, 18 Jan 2002 16:24:29 +1300 Date: Fri, 18 Jan 2002 16:24:29 +1300 (New Zealand Daylight Time) From: Juha Saarinen To: Patrick Greenwell Cc: Doug Hardie , "freebsd-stable@FreeBSD.ORG" Subject: Re: Spontaneous reboot mystery In-Reply-To: <20020117191952.Q6241-100000@rockstar.stealthgeeks.net> Message-ID: X-X-Sender: juha@vimfuego.saarinen.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 17 Jan 2002, Patrick Greenwell wrote: > netstat -m Thanks # netstat -m 232/720/6144 mbufs in use (current/peak/max): 189 mbufs allocated to data 43 mbufs allocated to packet headers 173/340/1536 mbuf clusters in use (current/peak/max) 860 Kbytes allocated to network (18% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Looks OK, doesn't it? The peak value is considerably below the max one. -- Juha Take off every sig! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:34:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-131.dsl.lsan03.pacbell.net [63.207.60.131]) by hub.freebsd.org (Postfix) with ESMTP id AA9AC37B476 for ; Thu, 17 Jan 2002 19:34:04 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0F55B66E1C; Thu, 17 Jan 2002 19:34:04 -0800 (PST) Date: Thu, 17 Jan 2002 19:34:03 -0800 From: Kris Kennaway To: Juha Saarinen Cc: freebsd-stable@freebsd.org Subject: Re: Spontaneous reboot mystery Message-ID: <20020117193403.A25576@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from juha@saarinen.org on Fri, Jan 18, 2002 at 02:42:14PM +1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 18, 2002 at 02:42:14PM +1300, Juha Saarinen wrote: > I have a remote server that has started rebooting itself for no apparent > reason. It looks like a controlled shutdown: Could be a Linux binary which has lost its ELF branding and is being treated as a FreeBSD binary. One of the common Linux syscalls has the same syscall number as reboot() under FreeBSD. Kris --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8R5erWry0BWjoQKURAgVwAKDaDAxCqMJ12MaqsiyQPkNCCDVeMwCgnfBg h0ncVrYNFK0JmvTp82ot1rs= =LTmp -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:38:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id B32D337B402 for ; Thu, 17 Jan 2002 19:38:16 -0800 (PST) Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.33 #1 (Red Hack)) id 16RPr2-0001XP-00; Fri, 18 Jan 2002 16:38:13 +1300 Date: Fri, 18 Jan 2002 16:38:13 +1300 (New Zealand Daylight Time) From: Juha Saarinen To: Kris Kennaway Cc: "freebsd-stable@freebsd.org" Subject: Re: Spontaneous reboot mystery In-Reply-To: <20020117193403.A25576@xor.obsecurity.org> Message-ID: X-X-Sender: juha@vimfuego.saarinen.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 17 Jan 2002, Kris Kennaway wrote: > Could be a Linux binary which has lost its ELF branding and is being > treated as a FreeBSD binary. One of the common Linux syscalls has the > same syscall number as reboot() under FreeBSD. That's a possibility. The box is running several Linux binaries under emulation. brandelf -t Linux on them, I suppose? -- Juha Take off every sig! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:40:38 2002 Delivered-To: freebsd-stable@freebsd.org Received: from zoon.lafn.org (zoon.lafn.org [206.117.18.9]) by hub.freebsd.org (Postfix) with ESMTP id 4EEF237B400 for ; Thu, 17 Jan 2002 19:40:36 -0800 (PST) Received: from [10.0.1.90] (66-81-78-227-modem.o1.com [66.81.78.227]) by zoon.lafn.org (8.11.3/8.11.3) with ESMTP id g0I3eU927869; Thu, 17 Jan 2002 19:40:30 -0800 (PST) (envelope-from bc979@lafn.org) Mime-Version: 1.0 X-Sender: bc979@mail.lafn.org Message-Id: In-Reply-To: References: Date: Thu, 17 Jan 2002 19:35:42 -0800 To: Juha Saarinen From: Doug Hardie Subject: Re: Spontaneous reboot mystery Cc: Patrick Greenwell , "freebsd-stable@FreeBSD.ORG" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 16:24 +1300 1/18/02, Juha Saarinen wrote: >On Thu, 17 Jan 2002, Patrick Greenwell wrote: > >> netstat -m > >Thanks > ># netstat -m >232/720/6144 mbufs in use (current/peak/max): > 189 mbufs allocated to data > 43 mbufs allocated to packet headers >173/340/1536 mbuf clusters in use (current/peak/max) >860 Kbytes allocated to network (18% of mb_map in use) >0 requests for memory denied >0 requests for memory delayed >0 calls to protocol drain routines > >Looks OK, doesn't it? The peak value is considerably below the max one. You may need to monitor it just prior to the reboot. Mine looked fine until about 10 minutes prior to the reboot. Then it went nuts. Another possibility is to setup the machine for serial console and hook it to another machine that captures the console information. There should be an indication there as to the cause. Frequently those messages just don't have enough time to make it to /var/messages. -- -- Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:44:30 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rockstar.stealthgeeks.net (h-66-134-120-173.LSANCA54.covad.net [66.134.120.173]) by hub.freebsd.org (Postfix) with SMTP id 765AF37B417 for ; Thu, 17 Jan 2002 19:44:28 -0800 (PST) Received: (qmail 6529 invoked by uid 1001); 18 Jan 2002 03:44:27 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Jan 2002 03:44:27 -0000 Date: Thu, 17 Jan 2002 19:44:27 -0800 (PST) From: Patrick Greenwell To: Juha Saarinen Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Spontaneous reboot mystery In-Reply-To: Message-ID: <20020117194311.O6512-100000@rockstar.stealthgeeks.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 18 Jan 2002, Juha Saarinen wrote: > # netstat -m > 232/720/6144 mbufs in use (current/peak/max): > 189 mbufs allocated to data > 43 mbufs allocated to packet headers > 173/340/1536 mbuf clusters in use (current/peak/max) > 860 Kbytes allocated to network (18% of mb_map in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > > Looks OK, doesn't it? The peak value is considerably below the max one. Looks fine. /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Patrick Greenwell Stealthgeeks,LLC. Operations Consulting http://www.stealthgeeks.net \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:45:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 1408037B400 for ; Thu, 17 Jan 2002 19:45:55 -0800 (PST) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.33 #1 (Red Hack)) id 16RPyQ-0001Xk-00; Fri, 18 Jan 2002 16:45:50 +1300 Date: Fri, 18 Jan 2002 16:45:50 +1300 (NZDT) From: Juha Saarinen To: Doug Hardie Cc: Patrick Greenwell , "freebsd-stable@FreeBSD.ORG" Subject: Re: Spontaneous reboot mystery In-Reply-To: Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 17 Jan 2002, Doug Hardie wrote: > You may need to monitor it just prior to the reboot. Mine looked > fine until about 10 minutes prior to the reboot. Then it went nuts. > Another possibility is to setup the machine for serial console and > hook it to another machine that captures the console information. > There should be an indication there as to the cause. Frequently > those messages just don't have enough time to make it to > /var/messages. OK, thanks, I'll try that. -- Regards, Juha C program run. C program crash. C programmer quit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 19:47: 2 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail7.nc.rr.com (fe7.southeast.rr.com [24.93.67.54]) by hub.freebsd.org (Postfix) with ESMTP id 1CD6937B416 for ; Thu, 17 Jan 2002 19:46:59 -0800 (PST) Received: from i8k.babbleon.org ([66.57.85.154]) by mail7.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Thu, 17 Jan 2002 21:56:27 -0500 Received: by i8k.babbleon.org (Postfix, from userid 111) id F13233E99; Thu, 17 Jan 2002 21:55:52 -0500 (EST) Content-Type: text/plain; charset="iso-8859-1" From: Brian T.Schellenberger To: Matt Penna , freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Memory Requirements Legacy and Present Date: Thu, 17 Jan 2002 21:55:52 -0500 X-Mailer: KMail [version 1.3] References: <5.1.0.14.2.20020117210634.01d8eec0@vmspop.isc.rit.edu> In-Reply-To: <5.1.0.14.2.20020117210634.01d8eec0@vmspop.isc.rit.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020118025552.F13233E99@i8k.babbleon.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday 17 January 2002 09:37 pm, Matt Penna wrote: > Dear folks, > > I noticed some time ago that the memory requirements in the FreeBSD FAQ, as > well as in the files detailing hardware requirements, are no longer > accurate. I am working on a PR in hopes of getting this fixed for the > benefit of new users, but haven't had much luck in finding the information > I need. My apologies if this is a bit off-topic for -stable, but I didn't > have much luck on -doc or -questions. I was encouraged to try posting here > by more than one person on those lists. > > Basically, what I'm trying to do is determine the exact minimum memory > requirements for FreeBSD's various releases. I'm most interested in what's > required to run the installer all the way through in each case, but I am > also interested in the amount required to run a usable system. The "5MB for > install and 4MB to run" documented in various places is no longer correct, > and it seems references to greater amounts such as 12MB and 8MB are based > on hearsay or are located in documents that are not trustworthy. > > Is there anyone here who can tell me when the memory requirements changed, > and to exactly what amounts? Is there a reliable way I can determine these > numbers on my own? (I use the word "reliable" because, in ignorance, I > attempted to run through the installer for 4.3-Release on a system with > only 8MB and succeeded without any difficulty whatsoever, though that was > apparently impossible. :) Seems to me that if you've done it that's more reliable information than any documentation you'd find. > > Any information would be greatly appreciated. Polite suggestions of other > people to bother with this are welcome, as well. :) > > Please CC me on any replies, as I am not subscribed to -stable. Thanks! > > Matt -- Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) Brian, the man from Babble-On . . . . bts@babbleon.org (personal) http://www.babbleon.org -------> Free Dmitry Sklyarov! (let him go home) <----------- http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 20: 8:45 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pendragon.tacni.net (radius.tacni.net [64.247.218.2]) by hub.freebsd.org (Postfix) with SMTP id F275337B400 for ; Thu, 17 Jan 2002 20:08:42 -0800 (PST) Received: (qmail 84475 invoked by alias); 18 Jan 2002 04:08:37 -0000 Received: from unknown (HELO there) (216.201.213.69) by tacni.net with SMTP; 18 Jan 2002 04:08:37 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Erich Zigler To: freebsd-stable@freebsd.org Subject: OpenSSH Woes Date: Thu, 17 Jan 2002 22:08:41 -0600 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020118040843.F275337B400@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I recently upgraded one of my machines to OpenSSH 3.0.2p1. For some reason now I am not able to login without a password using 3.0.2p1 to my 2.9-FREEBSD machines. This is pretty important considering I automate a lot of things between machines using shell scripts and scp. If anyone could provide any assistance I would greatly appreciate it. Thank you. -- Hardware, n.: The parts of a computer system that can be kicked. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 20:15:39 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pendragon.tacni.net (radius.tacni.net [64.247.218.2]) by hub.freebsd.org (Postfix) with SMTP id 1114137B405 for ; Thu, 17 Jan 2002 20:15:38 -0800 (PST) Received: (qmail 84811 invoked by alias); 18 Jan 2002 04:15:37 -0000 Received: from unknown (HELO there) (216.201.213.69) by tacni.net with SMTP; 18 Jan 2002 04:15:37 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Erich Zigler To: stable@freebsd.org Subject: Re: OpenSSH Woes Date: Thu, 17 Jan 2002 22:15:43 -0600 X-Mailer: KMail [version 1.3.2] References: <20020118040843.F275337B400@hub.freebsd.org> In-Reply-To: <20020118040843.F275337B400@hub.freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020118041538.1114137B405@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday 17 January 2002 10:08 pm, you wrote: > I recently upgraded one of my machines to OpenSSH 3.0.2p1. For some > reason now I am not able to login without a password using 3.0.2p1 to my > 2.9-FREEBSD machines. > This is pretty important considering I automate a lot of things between > machines using shell scripts and scp. > If anyone could provide any assistance I would greatly appreciate it. Slight update: Specifying SSH1 enables me to login, SSH2 makes me use a password. Evidently this would be great, but I can't figure out how to make scp use ssh1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 20:18:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 290FB37B400 for ; Thu, 17 Jan 2002 20:18:25 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.6/8.11.6) id g0I4INn31549; Thu, 17 Jan 2002 23:18:23 -0500 (EST) (envelope-from mike@sentex.net) Received: from house.sentex.net (fcage [192.168.0.2]) by cage.simianscience.com (8.11.6/8.11.6av) with ESMTP id g0I4IH331540; Thu, 17 Jan 2002 23:18:21 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20020117231728.02063e50@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 17 Jan 2002 23:18:16 -0500 To: Erich Zigler From: Mike Tancsa Subject: Re: OpenSSH Woes Cc: stable@freebsd.org In-Reply-To: <20020118041538.1114137B405@hub.freebsd.org> References: <20020118040843.F275337B400@hub.freebsd.org> <20020118040843.F275337B400@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG see /etc/ssh/ssh_config Change the Protocol to 1,2 ---Mike At 10:15 PM 1/17/2002 -0600, Erich Zigler wrote: >Slight update: Specifying SSH1 enables me to login, SSH2 makes me use a >password. Evidently this would be great, but I can't figure out how to make >scp use ssh1. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 20:36:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pendragon.tacni.net (radius.tacni.net [64.247.218.2]) by hub.freebsd.org (Postfix) with SMTP id 374B737B404 for ; Thu, 17 Jan 2002 20:36:56 -0800 (PST) Received: (qmail 85732 invoked by alias); 18 Jan 2002 04:36:51 -0000 Received: from unknown (HELO there) (216.201.213.69) by tacni.net with SMTP; 18 Jan 2002 04:36:51 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Erich Zigler To: Mike Tancsa Subject: Re: OpenSSH Woes Date: Thu, 17 Jan 2002 22:36:57 -0600 X-Mailer: KMail [version 1.3.2] Cc: stable@freebsd.org References: <20020118040843.F275337B400@hub.freebsd.org> <5.1.0.14.0.20020117231728.02063e50@192.168.0.12> In-Reply-To: <5.1.0.14.0.20020117231728.02063e50@192.168.0.12> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020118043656.374B737B404@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday 17 January 2002 10:18 pm, Mike Tancsa wrote: > see > /etc/ssh/ssh_config > Change the Protocol to 1,2 That fixed it! Thank you very much! -- Why is the symbol for anarchy always written the same way? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 20:52:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from proverbs.outreachnetworks.com (proverbs.outreachnetworks.com [65.196.249.4]) by hub.freebsd.org (Postfix) with SMTP id B196A37B416 for ; Thu, 17 Jan 2002 20:52:10 -0800 (PST) Received: (qmail 78187 invoked from network); 18 Jan 2002 04:52:09 -0000 Received: from unknown (HELO phoncella.outreachnetworks.com) (64.108.59.165) by proverbs.outreachnetworks.com with SMTP; 18 Jan 2002 04:52:09 -0000 Received: (from elh@localhost) by phoncella.outreachnetworks.com (8.11.6/8.11.6) id g0I4q9H03160 for freebsd-stable@FreeBSD.ORG; Thu, 17 Jan 2002 23:52:09 -0500 X-Authentication-Warning: phoncella.outreachnetworks.com: elh set sender to elh@outreachnetworks.com using -f Date: Thu, 17 Jan 2002 23:52:09 -0500 From: "Eric L. Howard" To: freebsd-stable@FreeBSD.ORG Subject: Re: random crashes on 4.4-S - ASUS CUSL2-M mobo Message-ID: <20020117235209.D2293@outreachnetworks.com> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <20020117155224.B2190@outreachnetworks.com> <20020117151216.A90572@mikea.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020117151216.A90572@mikea.ath.cx>; from mikea@mikea.ath.cx on Thu, Jan 17, 2002 at 03:12:16PM -0600 Favorite-Scripture: Romans 8:18 Theocratic-Rule-Advocate: http://www.crossmovement.com Registered-Secret-Agent: Agent Double-Naught Seven Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At a certain time, now past, mikea spake thusly: > On Thu, Jan 17, 2002 at 03:52:24PM -0500, Eric L. Howard wrote: > > I'm experiencing totally random crashes on a rackmount box. It's a PIII 750 > > on an ASUS CUSL2-M - onboard 3c920. > > > > The crashes are complete random and usually follow processes that die w/ > > SIGSEGV (a couple of SIGABRT thrown in for good measure have been found > > also). > > > > Syslog gives me info such as... (lines are wrapped) > > > > Jan 16 01:03:28 www /kernel: pid 692 (httpd), uid 65534: exited on signal 11 > > Jan 17 15:09:35 www /kernel: pid 290 (cpp0), uid 0: exited on signal 11 (core dumped) > > --------8<--snip-------- > > I've swapped memory at least twice - each time yielding no success. Not > > sure about how to get anywhere debugging core files - pointers appreciated. > > > > Any and all ideas will be appreciated and checked. Thanx. > > > > 4.4-STABLE FreeBSD 4.4-STABLE #0: Fri Nov 23 23:41:12 EST 2001 > > Temperature? Can you run a temperature/fan-rpm/whatnot monitor, > such as healthd? Yes...if only I could compile... [root@www etc]# cd /usr/ports/sysutils/healthd/ [root@www healthd]# make all >> healthd-0.6.5.tar.gz doesn't seem to exist in /usr/ports/distfiles/. >> Attempting to fetch from http://healthd.thehousleys.net/. Receiving healthd-0.6.5.tar.gz (64789 bytes): 100% --------8<--snip-------- updating cache ./config.cache creating ./config.status creating Makefile creating config.h *** Signal 11 Stop in /usr/ports/sysutils/healthd. *** Error code 1 Stop in /usr/ports/sysutils/healthd. *** Error code 1 Stop in /usr/ports/sysutils/healthd. [root@www healthd]# ls Makefile pkg-comment pkg-plist work distinfo pkg-descr touch.core > Totally random w.r.t. system load, or just totally random w.r.t. > clock time? Or something else? Completely random period...there was zero load on the machine when I tried to compile the above - the room and cabinet the server sits in are temp controlled...and the box soon died after the above attempt. I've moved everything off the server so I've got a little playing room/time. I did catch this just before the box died earlier: vm_page_remove: page not found in hash ~elh -- Eric L. Howard e l h @ o u t r e a c h n e t w o r k s . c o m ------------------------------------------------------------------------ www.OutreachNetworks.com 313.297.9900 ------------------------------------------------------------------------ Advocate of the Theocratic Rule To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 21: 9:53 2002 Delivered-To: freebsd-stable@freebsd.org Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by hub.freebsd.org (Postfix) with ESMTP id 5FC5437B400 for ; Thu, 17 Jan 2002 21:09:46 -0800 (PST) Received: from www.kuzbass.ru (kost [213.184.65.82]) by www.svzserv.kemerovo.su (8.11.6/8.11.6) with ESMTP id g0I59cm63289; Fri, 18 Jan 2002 12:09:38 +0700 (KRAT) (envelope-from eugen@www.kuzbass.ru) Message-ID: <3C47AE08.24F97802@www.kuzbass.ru> Date: Fri, 18 Jan 2002 12:09:28 +0700 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.79 [en] (Win95; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: Matt Penna Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Memory Requirements Legacy and Present References: <5.1.0.14.2.20020117210634.01d8eec0@vmspop.isc.rit.edu> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt Penna wrote: > Is there anyone here who can tell me when the memory requirements changed, > and to exactly what amounts? Is there a reliable way I can determine these > numbers on my own? (I use the word "reliable" because, in ignorance, I > attempted to run through the installer for 4.3-Release on a system with > only 8MB and succeeded without any difficulty whatsoever, though that was > apparently impossible. :) 4.2 was the last release that can be installed from FTP using NIC with 8Mb RAM/no swap. It's still possible to install 4.4-RELEASE from FTP using NIC with 8Mb RAM but the first step in sysinstall must be allocation of some swap space and activating it with key 'W' in Label Editor screen. Otherwise, sysinstall will run out of memory while configuring ethernet interface. 4.5-RC1 can be booted to multiuser with 4Mb RAM and custom stripped-down kernel if one have at least 512Kb of swap. I guess it won't be very useful. It will run smoothly as router/NAT/traffic shaper/small network monitoring system with 8Mb RAM and some swap space. The amount of swap depends of number and size of running applications. I currently run 486SX-25/8MB RAM with one of 4.4-SNAPs. It acts as ethernet/modem gateway, runs sshd and net-snmp and is capable of serving several simultanious shell sessions under screen(1). Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 22:28:13 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sapphire.tenebras.com (dsl092-188-241.sfo2.dsl.speakeasy.net [66.92.188.241]) by hub.freebsd.org (Postfix) with ESMTP id 09A2637B400 for ; Thu, 17 Jan 2002 22:27:59 -0800 (PST) Received: from tenebras.com (laptop [66.92.188.18]) by sapphire.tenebras.com (8.11.6/8.11.6) with ESMTP id g0I6RVo00960; Thu, 17 Jan 2002 22:27:31 -0800 (PST) (envelope-from kudzu@tenebras.com) Message-ID: <3C47C04D.27F6A894@tenebras.com> Date: Thu, 17 Jan 2002 22:27:26 -0800 From: Michael Sierchio Reply-To: kudzu@tenebras.com X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Eugene Grosbein Cc: Matt Penna , freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Memory Requirements Legacy and Present References: <5.1.0.14.2.20020117210634.01d8eec0@vmspop.isc.rit.edu> <3C47AE08.24F97802@www.kuzbass.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Eugene Grosbein wrote: > 4.2 was the last release that can be installed from FTP using NIC > with 8Mb RAM/no swap. It's still possible to install 4.4-RELEASE > from FTP using NIC with 8Mb RAM but the first step in sysinstall must > be allocation of some swap space and activating it with key 'W' > in Label Editor screen. Otherwise, sysinstall will run out of memory while > configuring ethernet interface. > Sheesh. 64MB of PC133 RAM is USD 22.00. 1GB of PC133w/ECC is $325. Cheaper than these is the brick you can use to bash your head for being too cheap to buy memory. ;-) That said, it would of course be useful to have an accurate "minimum" stated -- even if it is not precise, just guaranteed to work in all circumstances. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 22:58:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id CD25037B405 for ; Thu, 17 Jan 2002 22:58:51 -0800 (PST) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id RAA69658; Fri, 18 Jan 2002 17:58:50 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (localhost [127.0.0.1]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id RAA07910; Fri, 18 Jan 2002 17:58:50 +1100 (EST) Message-Id: <200201180658.RAA07910@lightning.itga.com.au> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 From: Gregory Bond To: kudzu@tenebras.com Cc: Eugene Grosbein , Matt Penna , freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Memory Requirements Legacy and Present In-reply-to: Your message of Thu, 17 Jan 2002 22:27:26 -0800. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Jan 2002 17:58:49 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Sheesh. 64MB of PC133 RAM is USD 22.00. Which won't work in a 486 or Pentium-class machine that uses 36-pin SIMs. Try buying RAM for them now, yet they make perfectly acceptable FreeBSD machines for many uses (e.g. poersonal firewalls) and should certainly be supported for the installer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 23:22:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id E556F37B400 for ; Thu, 17 Jan 2002 23:22:25 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g0I7M7N91140; Fri, 18 Jan 2002 08:22:07 +0100 (CET) (envelope-from wkb) Date: Fri, 18 Jan 2002 08:22:07 +0100 From: Wilko Bulte To: Michael Sierchio Cc: Eugene Grosbein , Matt Penna , freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Memory Requirements Legacy and Present Message-ID: <20020118082207.D91029@freebie.xs4all.nl> References: <5.1.0.14.2.20020117210634.01d8eec0@vmspop.isc.rit.edu> <3C47AE08.24F97802@www.kuzbass.ru> <3C47C04D.27F6A894@tenebras.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C47C04D.27F6A894@tenebras.com>; from kudzu@tenebras.com on Thu, Jan 17, 2002 at 10:27:26PM -0800 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jan 17, 2002 at 10:27:26PM -0800, Michael Sierchio wrote: > Eugene Grosbein wrote: > > > 4.2 was the last release that can be installed from FTP using NIC > > with 8Mb RAM/no swap. It's still possible to install 4.4-RELEASE > > from FTP using NIC with 8Mb RAM but the first step in sysinstall must > > be allocation of some swap space and activating it with key 'W' > > in Label Editor screen. Otherwise, sysinstall will run out of memory while > > configuring ethernet interface. > > > > Sheesh. 64MB of PC133 RAM is USD 22.00. 1GB of PC133w/ECC is $325. Cheaper > than these is the brick you can use to bash your head for being too cheap > to buy memory. ;-) All good and well but not all machines can use DIMMs. Like my firewall, an older P90. That old hardware is frequently used in roles like these. For x86 I suggest to consider 16MB to be the minimum, for Alpha 32MB. ( On x86 12MB appears to work, on Alpha 16MB If you consider slow as molasses reasonable that is..) W/ -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 17 23:44:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 0EBB637B400 for ; Thu, 17 Jan 2002 23:44:06 -0800 (PST) Received: from there (kajsa.energyhq.org [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id 04E3223EC2 for ; Fri, 18 Jan 2002 08:44:04 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Miguel Mendez Organization: Energy HQ To: freebsd-stable@FreeBSD.org Subject: Kernel panic on 4.5-RC Date: Fri, 18 Jan 2002 08:43:44 +0100 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020118074405.04E3223EC2@energyhq.homeip.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, Last night my router/nfs server panic'ed with the following message: energyhq# gdb -k /var/crash/kernel.0 /var/crash/vmcore.0 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x00333000 initial pcb at physical address 0x002a4020 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x3a fault code = supervisor write, page not present instruction pointer = 0x8:0xc0204632 stack pointer = 0x10:0xc6a2bd80 frame pointer = 0x10:0xc6a2be20 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 24079 (local) interrupt mask = net bio cam trap number = 12 panic: page fault syncing disks... done Uptime: 3d7h15m4s dumping to dev #ad/0x20001, offset 131072 dump ata0: resetting devices .. done 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xc0138642 in dumpsys () (kgdb) ---------------------------------------------------------- This machine had been working perfectly well until now, with a typical uptime of 1 month (I usually upgrade word every month). Any clue what could have caused this? Cheers, -- Miguel Mendez - flynn@energyhq.homeip.net EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 0:38:41 2002 Delivered-To: freebsd-stable@freebsd.org Received: from camelot.spsl.nsc.ru (camelot.spsl.nsc.ru [194.226.174.80]) by hub.freebsd.org (Postfix) with ESMTP id 707CC37B400 for ; Fri, 18 Jan 2002 00:38:06 -0800 (PST) Received: (from root@localhost) by camelot.spsl.nsc.ru (8.11.6/8.11.6) id g0I8bwj15139 for stable@freebsd.org.AVP; Fri, 18 Jan 2002 14:37:58 +0600 (NOVT) (envelope-from fjoe@iclub.nsu.ru) Received: from iclub.nsu.ru (root@iclub.nsu.ru [193.124.222.66]) by camelot.spsl.nsc.ru (8.11.6/8.11.6) with ESMTP id g0I8buX15131; Fri, 18 Jan 2002 14:37:56 +0600 (NOVT) (envelope-from fjoe@iclub.nsu.ru) Received: (from fjoe@localhost) by iclub.nsu.ru (8.11.6/8.11.6) id g0I8bo643751; Fri, 18 Jan 2002 14:37:50 +0600 (NS) (envelope-from fjoe) Date: Fri, 18 Jan 2002 14:37:50 +0600 From: Max Khon To: "Bruce A. Mah" Cc: Josh Tiefenbach , Koji Hino , stable@freebsd.org Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2? Message-ID: <20020118143750.E43443@iclub.nsu.ru> References: <20020116.110509.05717273.hino@ccrl.sj.nec.com> <20020116155436.A28166@zipperup.org> <200201171634.g0HGYpD22958@bmah.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200201171634.g0HGYpD22958@bmah.dyndns.org>; from bmah@freebsd.org on Thu, Jan 17, 2002 at 08:34:51AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, there! On Thu, Jan 17, 2002 at 08:34:51AM -0800, Bruce A. Mah wrote: > > Perhaps its an OpenSSH v3 thing? If I have some time tonite, I'll go compile > > up v3 someplace and check it out. > > Did you get a chance to do this? > > I'm unable to reproduce this problem between two RELENG_4 machines > running the base system OpenSSH (both machines built within the last > three days). Usually I use a DSA keypair to authenticate, but I > temporarily blew away ~/.ssh/authorized_keys2 on the server side and ~/ > .ssh/id_dsa on the client side. you need to install OpenSSH 3.0.2 from ports. Problem is not reproducible if you use OpenSSH 2.9 on both sides /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 0:39:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-131.dsl.lsan03.pacbell.net [63.207.60.131]) by hub.freebsd.org (Postfix) with ESMTP id A7FD037B400 for ; Fri, 18 Jan 2002 00:39:26 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DC25D66B3A; Fri, 18 Jan 2002 00:39:25 -0800 (PST) Date: Fri, 18 Jan 2002 00:39:24 -0800 From: Kris Kennaway To: Juha Saarinen Cc: Kris Kennaway , "freebsd-stable@freebsd.org" Subject: Re: Spontaneous reboot mystery Message-ID: <20020118003923.A28113@xor.obsecurity.org> References: <20020117193403.A25576@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from juha@saarinen.org on Fri, Jan 18, 2002 at 04:38:13PM +1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 18, 2002 at 04:38:13PM +1300, Juha Saarinen wrote: > On Thu, 17 Jan 2002, Kris Kennaway wrote: >=20 > > Could be a Linux binary which has lost its ELF branding and is being > > treated as a FreeBSD binary. One of the common Linux syscalls has the > > same syscall number as reboot() under FreeBSD. >=20 > That's a possibility. The box is running several Linux binaries under > emulation. >=20 > brandelf -t Linux on them, I suppose? Yep! Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8R986Wry0BWjoQKURAiJaAJ0XGyn/3AjCNnwklUJYoa29ZtwJHACg+R/6 xuRYbUQvvMQpz+XalI1iazo= =TCux -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 0:41:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-131.dsl.lsan03.pacbell.net [63.207.60.131]) by hub.freebsd.org (Postfix) with ESMTP id 6A4BB37B405 for ; Fri, 18 Jan 2002 00:41:09 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6D35366E18; Fri, 18 Jan 2002 00:41:02 -0800 (PST) Date: Fri, 18 Jan 2002 00:41:01 -0800 From: Kris Kennaway To: Miguel Mendez Cc: freebsd-stable@FreeBSD.org Subject: Re: Kernel panic on 4.5-RC Message-ID: <20020118004101.B28113@xor.obsecurity.org> References: <20020118074405.04E3223EC2@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="vGgW1X5XWziG23Ko" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020118074405.04E3223EC2@energyhq.homeip.net>; from flynn@energyhq.homeip.net on Fri, Jan 18, 2002 at 08:43:44AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --vGgW1X5XWziG23Ko Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 18, 2002 at 08:43:44AM +0100, Miguel Mendez wrote: > This machine had been working perfectly well until now, with a typical up= time=20 > of 1 month (I usually upgrade word every month). Any clue what could have= =20 > caused this? The usual causes are: 1) CPU fan not working 2) Bad RAM 3) CPU fan not working 4) Bad RAM 5) CPU fan not working 6) Bad RAM :-) Kris --vGgW1X5XWziG23Ko Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8R9+dWry0BWjoQKURAqthAKCa1pWY4JDbKfJGk2vSg1e9g6ceLgCg3dN9 sPuBF1jrKVJx9jhqOid/AhA= =2Zzx -----END PGP SIGNATURE----- --vGgW1X5XWziG23Ko-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 1:24:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vivaldi.pn.sinp.msu.ru (pn-gw.sinp.msu.ru [213.131.0.178]) by hub.freebsd.org (Postfix) with ESMTP id 818A037B416 for ; Fri, 18 Jan 2002 01:24:46 -0800 (PST) Received: from handel.pn.sinp.msu.ru (handel.pn.sinp.msu.ru [213.131.11.24]) (authenticated) by vivaldi.pn.sinp.msu.ru (8.11.6/8.11.6) with ESMTP id g0I9Q8t37967 for ; Fri, 18 Jan 2002 12:26:08 +0300 (MSK) (envelope-from svysh@pn.sinp.msu.ru) Message-Id: <5.1.0.14.2.20020118121711.00a72870@vivaldi.pn.sinp.msu.ru> X-Sender: svysh@vivaldi.pn.sinp.msu.ru X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 18 Jan 2002 12:25:45 +0300 To: freebsd-stable@freebsd.org From: Sergei Vyshenski Subject: newsyslog stops logging of apache Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 4.5-PRERELEASE with fresh port collection, apache-1.3.22_7. As soon as newsyslog turns over file /var/log/httpd-access.log, logging to this file stops despite otherwise normal operation. No such effect with a file /var/log/httpd-error.log. All this started a month ago with my weekly tracing of the stable branch. Updating of apache port did not help. Thank you in advance for any comment, Sergei To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 1:39:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sbtx.tmn.ru (sbtx.tmn.ru [212.76.160.49]) by hub.freebsd.org (Postfix) with ESMTP id 4E49437B41C for ; Fri, 18 Jan 2002 01:39:20 -0800 (PST) Received: from sv.tech.sibitex.tmn.ru (sv.tech.sibitex.tmn.ru [212.76.160.59]) by sbtx.tmn.ru (8.11.6/8.11.6) with ESMTP id g0I9dGL52797; Fri, 18 Jan 2002 14:39:17 +0500 (YEKT) (envelope-from serg@sbtx.tmn.ru) Received: (from serg@localhost) by sv.tech.sibitex.tmn.ru (8.11.6/8.11.6) id g0I9dGC11513; Fri, 18 Jan 2002 14:39:16 +0500 (YEKT) (envelope-from serg) Date: Fri, 18 Jan 2002 14:39:15 +0500 From: "Sergey N. Voronkov" To: Sergei Vyshenski Cc: freebsd-stable@FreeBSD.ORG Subject: Re: newsyslog stops logging of apache Message-ID: <20020118143915.A11440@sv.tech.sibitex.tmn.ru> References: <5.1.0.14.2.20020118121711.00a72870@vivaldi.pn.sinp.msu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.2.20020118121711.00a72870@vivaldi.pn.sinp.msu.ru>; from svysh@pn.sinp.msu.ru on Fri, Jan 18, 2002 at 12:25:45PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jan 18, 2002 at 12:25:45PM +0300, Sergei Vyshenski wrote: > 4.5-PRERELEASE with fresh port collection, apache-1.3.22_7. > > As soon as newsyslog turns over file /var/log/httpd-access.log, > logging to this file stops despite otherwise normal operation. > No such effect with a file /var/log/httpd-error.log. > Do you send SIGHUP/SIGUSR1 to running apache? serg@sv ~>tail -2 /etc/newsyslog.conf /var/log/httpd-error.log 644 5 100 * Z /var/run/httpd.pid 30 /var/log/httpd-access.log 644 7 250 * Z /var/run/httpd.pid 30 Best Regards, Serg N. Voronkov, Sibitex JSC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 1:53:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mta07-svc.ntlworld.com (mta07-svc.ntlworld.com [62.253.162.47]) by hub.freebsd.org (Postfix) with ESMTP id 94F6537B41D for ; Fri, 18 Jan 2002 01:53:45 -0800 (PST) Received: from localhost ([62.252.180.23]) by mta07-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020118095343.PGNX6966.mta07-svc.ntlworld.com@localhost> for ; Fri, 18 Jan 2002 09:53:43 +0000 Received: from ac by localhost with local (Exim 3.33 #1 (Debian)) id 16RViV-0001Fk-00 for ; Fri, 18 Jan 2002 09:53:47 +0000 Date: Fri, 18 Jan 2002 09:53:47 +0000 From: Anthony Campbell To: stable@freebsd.org Subject: Bug in kernel documentation? Message-ID: <20020118095346.GA4808@debian.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.24i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The documentation for the kernel, and the Handbook, say that if you don't have ethernet you can omit the pseudo-device for ether. If you do this, however, you can't include usb. If you try to do so you get the following error message: linking kernel usb_ethersubr.o: In function `usbintr': usb_ethersubr.o(text+0x31): undefined reference to ether_input' *** Error code 1 Incidentally, if you don't compile in usb but try to insert it later as a module, a similar message appears. Anthony -- Anthony Campbell - running Linux GNU/Debian (Windows-free zone) For an electronic book (The Assassins of Alamut), skeptical essays, and over 150 book reviews, go to: http://www.acampbell.org.uk/ Our planet is a lonely speck in the great enveloping cosmic dark. In our obscurity, in all this vastness, there is no hint that help will come from elsewhere to save us from ourselves. [Carl Sagan] -- Anthony Campbell - running Linux GNU/Debian (Windows-free zone) For an electronic book (The Assassins of Alamut), skeptical essays, and over 150 book reviews, go to: http://www.acampbell.org.uk/ Our planet is a lonely speck in the great enveloping cosmic dark. In our obscurity, in all this vastness, there is no hint that help will come from elsewhere to save us from ourselves. [Carl Sagan] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 2:19:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from etek.chalmers.se (quarl0.etek.chalmers.se [129.16.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 8E2D837B419 for ; Fri, 18 Jan 2002 02:19:36 -0800 (PST) Received: from downy.etek.chalmers.se (_7-268@downy.etek.chalmers.se [129.16.32.207]) by etek.chalmers.se (8.10.0/8.8.8) with ESMTP id g0IAJYO31415; Fri, 18 Jan 2002 11:19:34 +0100 (MET) Received: from localhost (b@localhost) by downy.etek.chalmers.se (8.10.0/8.10.0) with ESMTP id g0IAJYZ24987; Fri, 18 Jan 2002 11:19:34 +0100 (MET) Date: Fri, 18 Jan 2002 11:19:34 +0100 (MET) From: Magnus B{ckstr|m To: Erich Zigler Cc: stable@freebsd.org Subject: Re: OpenSSH Woes In-Reply-To: <20020118043656.374B737B404@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 17 Jan 2002, Erich Zigler wrote: > > On Thursday 17 January 2002 10:18 pm, Mike Tancsa wrote: > > > see > > /etc/ssh/ssh_config > > Change the Protocol to 1,2 > > That fixed it! Thank you very much! > The problem actually is that versions 1 and 2 use different key sets. V.1 used one type of key in ~/.ssh/identity etc. An alternate (and possibly better) fix is to make another set of keys that work with version 2: ssh-keygen -t rsa # ... or "-t dsa" Then copy the generated ~/.ssh/id_rsa.pub to ~/.ssh/authorized_keys2 on the target system. Magnus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 2:25:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id A084537B417 for ; Fri, 18 Jan 2002 02:25:25 -0800 (PST) Received: from there (kajsa.energyhq.org [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id 214C323EC2; Fri, 18 Jan 2002 11:25:08 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Miguel Mendez Organization: Energy HQ To: Anthony Campbell , stable@freebsd.org Subject: Re: Bug in kernel documentation? Date: Fri, 18 Jan 2002 11:24:48 +0100 X-Mailer: KMail [version 1.3.2] References: <20020118095346.GA4808@debian.local> In-Reply-To: <20020118095346.GA4808@debian.local> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020118102509.214C323EC2@energyhq.homeip.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday 18 January 2002 10:53, Anthony Campbell wrote: > linking kernel > usb_ethersubr.o: In function `usbintr': > usb_ethersubr.o(text+0x31): undefined reference to ether_input' > *** Error code 1 > > Incidentally, if you don't compile in usb but try to insert it later as > a module, a similar message appears. Well, my guess is that usb depends on the ethernet code for the usb ethernet devices it supports, but yes, maybe the docs should be corrected regarding that. Cheers, Miguel Mendez - running FreeBSD (Linux GNU/Debian & Windows-free zone ;-) -- Miguel Mendez - flynn@energyhq.homeip.net EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 2:26:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mao.stokely.org (mao.stokely.org [65.84.64.228]) by hub.freebsd.org (Postfix) with ESMTP id 6062237B416; Fri, 18 Jan 2002 02:26:02 -0800 (PST) Received: by mao.stokely.org (Postfix, from userid 2074) id AAD344B661; Fri, 18 Jan 2002 02:25:56 -0800 (PST) Date: Fri, 18 Jan 2002 02:25:56 -0800 From: Murray Stokely To: freebsd-qa@FreeBSD.org Cc: freebsd-stable@FreeBSD.org Subject: FreeBSD 4.5-RC2 / x86 Now Available. Message-ID: <20020118102556.GJ18587@freebsdmall.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AjmyJqqohANyBN/e" Content-Disposition: inline User-Agent: Mutt/1.3.25i X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --AjmyJqqohANyBN/e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Our second 4.5 release candidate is now available : ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.5-RC2 ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/4.5-RC2-install.iso (available at some sites, still transferring to others) RC1 is still available from ftp://releng4.freebsd.org. There will be no cdboot images for this RC, as it is clear that this functionality needs some more work and will not be ready in time for 4.5. Please watch freebsd-alpha for an announcement about the status of RC2 for the Alpha platform. This release candidate fixes a number of issues that were reported with RC1. Loadable kernel modules are now available on the MFSROOT floppy, and these are automatically loaded by sysinstall. This functionality could use a great deal of testing. There is a little extra room left over for another kernel module or two, so if there is a device that you would like to use for installation that is currently not included on the boot kernel, please speak up. Installing Linux compatibility during installation should now work, and could also use a fair amount of testing with common Linux applications such as Netscape and Acrobat reader. The Gnome / Sawfish and fvwm2 ports are still unavailable in the package set. This will be fixed with RC3 to follow in the coming days. There was also a build failure for 'unzip', but otherwise the package set is complete. This ISO image does not include HFS support (mkisofs -h) for long file names and extended attributes on the Macintosh platform. This gives us an extra 30MB to use for packages : -rw-r--r-- 1 root wheel 683661312 Jan 17 22:48 4.5-RC2-HFS.iso -rw-r--r-- 1 root wheel 652187648 Jan 17 22:52 4.5-RC2-install.iso The FreeBSD 4.4 CDs did not include HFS support either, but previous releases may have. If anyone requires this functionality, please speak up. Thanks, The FreeBSD 4.5 Release Engineering Team. --AjmyJqqohANyBN/e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE8R/g0tNcQog5FH30RAvhYAKCjQD7U2NtnE5/CkwoLbSGDpGOw5wCgwXeK 7qWOj0tSt0ymBc4rEiqXxyk= =1HMd -----END PGP SIGNATURE----- --AjmyJqqohANyBN/e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 2:26:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by hub.freebsd.org (Postfix) with ESMTP id 09F6237B41F for ; Fri, 18 Jan 2002 02:26:28 -0800 (PST) Received: from dim.lostboys.nl (dim.lostboys.nl [212.123.234.49]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id g0IAQAAI022631; Fri, 18 Jan 2002 11:26:10 +0100 (CET) Date: Fri, 18 Jan 2002 11:25:56 +0100 From: Dimitry Andric X-Mailer: The Bat! (v1.54 Beta/29) Business Reply-To: Dimitry Andric X-Priority: 3 (Normal) Message-ID: <3277032336.20020118112556@xs4all.nl> To: Miguel Mendez Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel panic on 4.5-RC In-Reply-To: <20020118074405.04E3223EC2@energyhq.homeip.net> References: <20020118074405.04E3223EC2@energyhq.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/18/2002 at 08:43:44 Miguel Mendez wrote: MM> Last night my router/nfs server panic'ed with the following message: Are you by any chance using the xl(4) driver? Please post a dmesg. Cheers, - -- Dimitry Andric PGP Key: http://www.xs4all.nl/~dim/dim.asc Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3 -----BEGIN PGP SIGNATURE----- Version: PGP 6.5i Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBPEfqK7BeowouIJajEQKhwwCgq3Dzen4P/nIPRer/eAJa4Rs3+ZoAniJx /ZWrHomqnHWNbIK1fug9I38T =6ALQ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 2:48:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-131.dsl.lsan03.pacbell.net [63.207.60.131]) by hub.freebsd.org (Postfix) with ESMTP id B380637B41C for ; Fri, 18 Jan 2002 02:48:13 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AA5F966BBF; Fri, 18 Jan 2002 02:48:10 -0800 (PST) Date: Fri, 18 Jan 2002 02:48:10 -0800 From: Kris Kennaway To: Anthony Campbell Cc: stable@FreeBSD.ORG Subject: Re: Bug in kernel documentation? Message-ID: <20020118024809.A82050@xor.obsecurity.org> References: <20020118095346.GA4808@debian.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020118095346.GA4808@debian.local>; from ac@acampbell.org.uk on Fri, Jan 18, 2002 at 09:53:47AM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 18, 2002 at 09:53:47AM +0000, Anthony Campbell wrote: > The documentation for the kernel, and the Handbook, say that if you > don't have ethernet you can omit the pseudo-device for ether. If you do > this, however, you can't include usb. If you try to do so you get the > following error message: >=20 > linking kernel > usb_ethersubr.o: In function `usbintr': > usb_ethersubr.o(text+0x31): undefined reference to ether_input' > *** Error code 1 Is this because you've included a USB ethernet device? # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet Can you please post your config file? Kris --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8R/1pWry0BWjoQKURAu8JAJ4vvxzI1WdU/XdedtFQJAIoties0ACghSFn K/r7T8ymFhc34liE1ElnT9o= =nytg -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 3:49:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 9C87F37B404 for ; Fri, 18 Jan 2002 03:48:56 -0800 (PST) Received: from localhost ([62.252.176.200]) by mta01-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020118114854.JLYQ9422.mta01-svc.ntlworld.com@localhost>; Fri, 18 Jan 2002 11:48:54 +0000 Received: from ac by localhost with local (Exim 3.33 #1 (Debian)) id 16RXVx-0001YW-00; Fri, 18 Jan 2002 11:48:57 +0000 Date: Fri, 18 Jan 2002 11:48:56 +0000 From: Anthony Campbell To: Kris Kennaway Cc: stable@freebsd.org Subject: Re: Bug in kernel documentation? Message-ID: <20020118114856.GA5901@debian.local> References: <20020118095346.GA4808@debian.local> <20020118024809.A82050@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020118024809.A82050@xor.obsecurity.org> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18 Jan 2002, Kris Kennaway wrote: > On Fri, Jan 18, 2002 at 09:53:47AM +0000, Anthony Campbell wrote: > > The documentation for the kernel, and the Handbook, say that if you > > don't have ethernet you can omit the pseudo-device for ether. If you do > > this, however, you can't include usb. If you try to do so you get the > > following error message: > > > > linking kernel > > usb_ethersubr.o: In function `usbintr': > > usb_ethersubr.o(text+0x31): undefined reference to ether_input' > > *** Error code 1 > > Is this because you've included a USB ethernet device? > no > # USB Ethernet, requires mii > device aue # ADMtek USB ethernet > device cue # CATC USB ethernet > device kue # Kawasaki LSI USB ethernet > > Can you please post your config file? > > Kris # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.34 2001/08/12 13:13:46 joerg Exp $ machine i386 cpu I686_CPU ident TOSHIBA maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support #options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem #options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev options EXT2FS # needed for linux # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) #pseudo-device md # Memory "disks" pseudo-device gif # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! #pseudo-device bpf #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet Anthony -- Anthony Campbell - running Linux GNU/Debian (Windows-free zone) For an electronic book (The Assassins of Alamut), skeptical essays, and over 150 book reviews, go to: http://www.acampbell.org.uk/ Our planet is a lonely speck in the great enveloping cosmic dark. In our obscurity, in all this vastness, there is no hint that help will come from elsewhere to save us from ourselves. [Carl Sagan] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 5:43:59 2002 Delivered-To: freebsd-stable@freebsd.org Received: from zeus.nordnet.ru (zeus.nordnet.ru [213.150.64.3]) by hub.freebsd.org (Postfix) with ESMTP id 9BE2437B405 for ; Fri, 18 Jan 2002 05:43:50 -0800 (PST) Received: from tarn.noc.ctk.ru (CrasotinPA.noc.ctk.ru [213.150.66.11]) by zeus.nordnet.ru (8.11.1/8.11.1) with ESMTP id g0IDhwF83330 for ; Fri, 18 Jan 2002 16:43:59 +0300 (MSK) Date: Fri, 18 Jan 2002 16:43:47 +0300 From: Pavel A Crasotin X-Mailer: The Bat! (v1.53d) Reply-To: Pavel A Crasotin Organization: OJSC SeverTransCom X-Priority: 3 (Normal) Message-ID: <84720546210.20020118164347@ctk.ru> To: freebsd-stable@FreeBSD.ORG Subject: tcpdump hangs network interface MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I'm running 4.5-PRERELEASE. When I stop tcpdump it hangs network interface. hermes# tcpdump host x.x.x.x tcpdump: listening on pcn0 11:24:40.644664 y.y.y.y > x.x.x.x: icmp: echo request 11:24:40.651675 x.x.x.x > y.y.y.y: icmp: echo reply (DF) 11:24:41.660268 y.y.y.y > x.x.x.x: icmp: echo request 11:24:41.666985 x.x.x.x > y.y.y.y: icmp: echo reply (DF) ^C 187 packets received by filter 0 packets dropped by kernel hermes# After that network interface hangs and can be started only by ifconfig pcn0 down ifconfig pcn0 up Im using FreeBSD 4.5-PRERELEASE (HERMES) #1: Sat Jan 12 00:15:50 MSK 2002 on IBM xSeries 340. Ethernet card - AMD PCnet/PCI 10/100BaseTX Does anyone knows what's wrong? With respect, Pavel A Crasotin ____________________________________ OJSC SeverTransCom 40/13 Sobinova, Yaroslavl, 150000, Russia Tel/Fax: +7 (0852) 47-71-70, 47-69-49 +7 (0852) 72-17-28, 72-17-38 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 6:22:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.viamidia.com (access-bridge.icablenet.com.br [200.215.9.227]) by hub.freebsd.org (Postfix) with ESMTP id 26CD137BAD0 for ; Fri, 18 Jan 2002 06:18:49 -0800 (PST) Received: (from root@localhost) by mail.viamidia.com (8.10.1/pre1.0-MySQL/8.10.1) id g0IEIkP12418 for freebsd-stable@freebsd.org; Fri, 18 Jan 2002 12:18:46 -0200 (EDT) Received: (from root@localhost) by mail.viamidia.com (8.10.1/pre1.0-MySQL/8.10.1) id g0IE7Zt12298 for freebsd-stable@freebsd.org; Fri, 18 Jan 2002 12:07:35 -0200 (EDT) Received: from freebsd.viamidia.com (freebsd.viamidia.com [10.0.0.254]) by mail.viamidia.com (8.10.1/pre1.0-MySQL/8.10.1av) with ESMTP id g0IE7XU12290 for ; Fri, 18 Jan 2002 12:07:34 -0200 (EDT) Message-ID: X-Mailer: XFMail 1.5.1 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 18 Jan 2002 12:07:32 -0200 (BRST) From: Helio Luchtenberg Junior To: freebsd-stable@freebsd.org Subject: FWD: RE: tcpdump hangs network interface X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm facing the same problem with 4.3-RELEASE and 4.3-STABLE. My interface card is the same: pcn0 It looks like a problema with the driver for this NIC ? Helio. On 18-Jan-2002 Pavel A Crasotin wrote: > Hi > > I'm running 4.5-PRERELEASE. > When I stop tcpdump it hangs network interface. > > hermes# tcpdump host x.x.x.x > tcpdump: listening on pcn0 > 11:24:40.644664 y.y.y.y > x.x.x.x: icmp: echo request > 11:24:40.651675 x.x.x.x > y.y.y.y: icmp: echo reply (DF) > 11:24:41.660268 y.y.y.y > x.x.x.x: icmp: echo request > 11:24:41.666985 x.x.x.x > y.y.y.y: icmp: echo reply (DF) > ^C > 187 packets received by filter > 0 packets dropped by kernel > hermes# > > > After that network interface hangs and can be started only by > ifconfig pcn0 down > ifconfig pcn0 up > > Im using FreeBSD 4.5-PRERELEASE (HERMES) #1: Sat Jan 12 00:15:50 MSK 2002 > on IBM xSeries 340. Ethernet card - AMD PCnet/PCI 10/100BaseTX > > Does anyone knows what's wrong? > > With respect, > Pavel A Crasotin > ____________________________________ > OJSC SeverTransCom > 40/13 Sobinova, Yaroslavl, 150000, Russia > Tel/Fax: +7 (0852) 47-71-70, 47-69-49 > +7 (0852) 72-17-28, 72-17-38 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- __o ---_ \<,_ email: hlj@viamidia.com ---- (_)/ (_) o _ _ _ _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ Helio Luchtenberg Junior Consultoria em Informatica ---------------------------------- E-Mail: Helio Luchtenberg Junior Date: 18-Jan-2002 Time: 12:04:22 This message was sent by XFMail ---------------------------------- --------------End of forwarded message------------------------- -- __o ---_ \<,_ email: hlj@viamidia.com ---- (_)/ (_) o _ _ _ _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ Helio Luchtenberg Junior Consultoria em Informatica ---------------------------------- E-Mail: Helio Luchtenberg Junior Date: 18-Jan-2002 Time: 12:06:28 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 6:35:15 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sage-american.com (sage-american.com [216.122.141.44]) by hub.freebsd.org (Postfix) with ESMTP id 6A61B37B419 for ; Fri, 18 Jan 2002 06:35:06 -0800 (PST) Received: from SAGEONE (adsl-64-219-20-175.dsl.crchtx.swbell.net [64.219.20.175]) by sage-american.com (8.9.3/8.9.3) with SMTP id IAA28963; Fri, 18 Jan 2002 08:34:37 -0600 (CST) Message-Id: <3.0.5.32.20020118083435.017908f8@mail.sage-american.com> X-Sender: jacks@mail.sage-american.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 18 Jan 2002 08:34:35 -0600 To: "Sergey N. Voronkov" , Sergei Vyshenski From: jacks@sage-american.com Subject: Re: newsyslog stops logging of apache Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <20020118143915.A11440@sv.tech.sibitex.tmn.ru> References: <5.1.0.14.2.20020118121711.00a72870@vivaldi.pn.sinp.msu.ru> <5.1.0.14.2.20020118121711.00a72870@vivaldi.pn.sinp.msu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm running the following line to rotate using 4.4-stable: /var/log/httpd-access.log 644 1 100 * B /var/run/httpd.pid I alsdo thought I might need signal 30, but found this worked with the default. You'll probably just need to restart httpd to get the logs to begin again... At 02:39 PM 1.18.2002 +0500, Sergey N. Voronkov wrote: >On Fri, Jan 18, 2002 at 12:25:45PM +0300, Sergei Vyshenski wrote: >> 4.5-PRERELEASE with fresh port collection, apache-1.3.22_7. >> >> As soon as newsyslog turns over file /var/log/httpd-access.log, >> logging to this file stops despite otherwise normal operation. >> No such effect with a file /var/log/httpd-error.log. >> > >Do you send SIGHUP/SIGUSR1 to running apache? > >serg@sv ~>tail -2 /etc/newsyslog.conf >/var/log/httpd-error.log 644 5 100 * Z /var/run/httpd.pid 30 >/var/log/httpd-access.log 644 7 250 * Z /var/run/httpd.pid 30 > >Best Regards, > >Serg N. Voronkov, >Sibitex JSC. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > Best regards, Jack L. Stone, Server Admin =================================================== Sage-American http://www.sage-american.com jacks@sage-american.com "My center is giving way, my right is in retreat; ....situation excellent! ....I shall attack!" =================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 6:39:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mikea.ath.cx (okc-65-30-192-11.mmcable.com [65.30.192.11]) by hub.freebsd.org (Postfix) with ESMTP id 3B8BC37B41D for ; Fri, 18 Jan 2002 06:39:13 -0800 (PST) Received: (from mikea@localhost) by mikea.ath.cx (8.11.6/8.11.1) id g0IEdCf92459 for freebsd-stable@FreeBSD.ORG; Fri, 18 Jan 2002 08:39:12 -0600 (CST) (envelope-from mikea) Date: Fri, 18 Jan 2002 08:39:11 -0600 From: mikea To: freebsd-stable@FreeBSD.ORG Subject: Re: random crashes on 4.4-S - ASUS CUSL2-M mobo Message-ID: <20020118083911.B92349@mikea.ath.cx> References: <20020117155224.B2190@outreachnetworks.com> <20020117151216.A90572@mikea.ath.cx> <20020117235209.D2293@outreachnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020117235209.D2293@outreachnetworks.com>; from elh@outreachnetworks.com on Thu, Jan 17, 2002 at 11:52:09PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jan 17, 2002 at 11:52:09PM -0500, Eric L. Howard wrote: > Mike Andrews wrote: > > Temperature? Can you run a temperature/fan-rpm/whatnot monitor, > > such as healthd? > > Yes...if only I could compile... > > [root@www etc]# cd /usr/ports/sysutils/healthd/ > [root@www healthd]# make all > >> healthd-0.6.5.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > >> Attempting to fetch from http://healthd.thehousleys.net/. > Receiving healthd-0.6.5.tar.gz (64789 bytes): 100% > --------8<--snip-------- > updating cache ./config.cache > creating ./config.status > creating Makefile > creating config.h > *** Signal 11 > > Stop in /usr/ports/sysutils/healthd. > *** Error code 1 > > Stop in /usr/ports/sysutils/healthd. > *** Error code 1 > > Stop in /usr/ports/sysutils/healthd. > [root@www healthd]# ls > Makefile pkg-comment pkg-plist work > distinfo pkg-descr touch.core That's really bad. > > Totally random w.r.t. system load, or just totally random w.r.t. > > clock time? Or something else? > > Completely random period...there was zero load on the machine when I tried > to compile the above - the room and cabinet the server sits in are temp > controlled...and the box soon died after the above attempt. > > I've moved everything off the server so I've got a little playing room/time. > > I did catch this just before the box died earlier: > > vm_page_remove: page not found in hash It's about one chance in 10^googolplex of _not_ being a hardware problem. Do you have a different mobo that you can slide under the CPU(s), RAM, cards, etc.? Can you put the box out on a table and to a fingertip temperature check of things during operations? Have you tried dis- and re-connecting/inserting _EVERYTHING_, on the premise that it might be an intermittent connection triggered by vibration? Can you swap in a new power supply? Got any cooling spray? If yes (a can of compressed air for cleaning things will work), try cooling down specific components, one at a time. Do the same thing with a heat gun or hair dryer. Tap the board gently to try to isolate bad solder joints. At this point, it's grab-at-straws time. And, of course, the serial console idea is a good one. Keep us posted. -- Mike Andrews mikea@mikea.ath.cx Tired old sysadmin since 1964 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 6:44:13 2002 Delivered-To: freebsd-stable@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id E6FB237B417 for ; Fri, 18 Jan 2002 06:44:05 -0800 (PST) Received: from there (kajsa.energyhq.org [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id 230C53FC39; Fri, 18 Jan 2002 15:44:04 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Miguel Mendez Organization: Energy HQ To: Dimitry Andric Subject: Re: Kernel panic on 4.5-RC Date: Fri, 18 Jan 2002 15:43:44 +0100 X-Mailer: KMail [version 1.3.2] Cc: freebsd-stable@FreeBSD.ORG References: <20020118074405.04E3223EC2@energyhq.homeip.net> <3277032336.20020118112556@xs4all.nl> In-Reply-To: <3277032336.20020118112556@xs4all.nl> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020118144404.230C53FC39@energyhq.homeip.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday 18 January 2002 11:25, Dimitry Andric wrote: > On 1/18/2002 at 08:43:44 Miguel Mendez wrote: > > MM> Last night my router/nfs server panic'ed with the following message: > > Are you by any chance using the xl(4) driver? Please post a dmesg. Yes I am, but as soon as I've opened the box I've found the obvious problem, the CPU's fan had died and stopped spinning, I wonder how the machine did to reboot and be up for another 8 hours. Anyway, if you want the dmesg here it goes, but my bet is the damaged fan which I've replaced already. -- Miguel Mendez - flynn@energyhq.homeip.net EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! -------------------------------- Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-RC #0: Thu Jan 10 18:41:02 CET 2002 root@energyhq.homeip.net:/storage2/obj/storage2/src/sys/ENERGYHQ Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (381.16-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 67108864 (65536K bytes) avail memory = 62173184 (60716K bytes) Preloaded elf kernel "kernel" at 0xc0314000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031409c. K6-family MTRR support enabled (2 registers) md0: Malloc disk Using $PIR table, 6 entries at 0xc00fdc70 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci0: at 2.0 irq 5 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 10.0 irq 11 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xf000-0xf07f mem 0xd5801000-0xd580107f irq 10 at device 11.0 on pci0 xl0: Ethernet address: 00:10:4b:5a:08:9c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ed0: port 0xf400-0xf41f irq 12 at device 12.0 on pci0 ed0: address 00:20:18:39:5c:53, type NE2000 (16 bit) atapci0: port 0xf800-0xf80f at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 orm0:
subscribe = freebsd-stable
------=_NextPart_000_0007_01C1A0CB.D6801CD0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 19:10:49 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AC16537B402 for ; Fri, 18 Jan 2002 19:10:45 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g0J3Ail34064 for ; Fri, 18 Jan 2002 20:10:44 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g0J3Ahx04138 for ; Fri, 18 Jan 2002 20:10:43 -0700 (MST) (envelope-from imp@village.org) Date: Fri, 18 Jan 2002 12:05:16 -0700 (MST) Message-Id: <20020118.120516.62411486.imp@village.org> To: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Memory Requirements Legacy and Present From: "M. Warner Losh" In-Reply-To: <3C47AE08.24F97802@www.kuzbass.ru> References: <5.1.0.14.2.20020117210634.01d8eec0@vmspop.isc.rit.edu> <3C47AE08.24F97802@www.kuzbass.ru> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <3C47AE08.24F97802@www.kuzbass.ru> Eugene Grosbein writes: : 4.5-RC1 can be booted to multiuser with 4Mb RAM and custom stripped-down : kernel if one have at least 512Kb of swap. I guess it won't be very useful. : It will run smoothly as router/NAT/traffic shaper/small network monitoring : system with 8Mb RAM and some swap space. The amount of swap depends of : number and size of running applications. I currently run 486SX-25/8MB RAM : with one of 4.4-SNAPs. It acts as ethernet/modem gateway, runs sshd : and net-snmp and is capable of serving several simultanious shell sessions : under screen(1). I have booted a 4.4-stable kernel (very highly stripped down) on my 4M test box. I was able to get it configured to do my routing stuff. I did have to turn off ttys, cron, etc. But once I did that, it seemed reasonable enough. However, adding some more memory did help improve the response time (I have 100M of swap on that box). I didn't install it with sysinstall. :-) I also have a 128MB P-133 that I use as my wireless gateway, booted off of a 32M CF card. The only reason that i thas 128M rather than the 8MB it came with was that I wanted the CF card to be mounted read only (to save wear and tear on the card and to help proevent accidents). Mounting memory file systems in 8M isn't really possible. Oh, 128M was the smallest stick I could buy at Office MAX when I sent there. It was a whole $25.00, and I didn't want to special order the 64M version for $20.00. Machines with 30-pin simms, and those with weird or non-existant memory expansion (think laptops) are much harder to upgrade, no matter how cheap the latest technology is. The 30-pin simms are cheap enough, but most 486 machines that take them are limited to banks of 4, which limits the number of configurations that are possible. I have also booted FreeBSD's standard /etc/rc scripts off of an 8MB flash card. The minimal bootable w/o error messages size image that I've been able to make is on the order of 6.5MB. I also, as an experiment in the 4.2 time frame, booted a 3.95MB image that used a heavily hacked /etc/rc* set of files, but I've lost the hacks I made to get it that small. Both of these tests were done on machines with 32MB or more of RAM (since I needed a MFS for /dev and for /var). Laptops that I have to install for test purposes I generally take apart, put the 2.5" IDE disk into an adapter and plug it into either a desktop or into another laptop depending on the hardware at hand... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 19:16:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8E1DD37B402 for ; Fri, 18 Jan 2002 19:16:15 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g0J3GEl34192; Fri, 18 Jan 2002 20:16:14 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g0J3GCx04236; Fri, 18 Jan 2002 20:16:13 -0700 (MST) (envelope-from imp@village.org) Date: Fri, 18 Jan 2002 20:16:00 -0700 (MST) Message-Id: <20020118.201600.44942631.imp@village.org> To: drosih@rpi.edu Cc: stable@freebsd.org Subject: Re: Stable build broken, missing update to pccbbdevid.h From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: Garance A Drosihn writes: : seems to need Revision 1.5 of src/sys/dev/pccbb/pccbbdevid.h : which has *not* been MFC-ed. : : Apologies if my guess is wrong... So, you are right :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 19:18:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 9B28D37B400 for ; Fri, 18 Jan 2002 19:18:22 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id g0J3IKc36104; Fri, 18 Jan 2002 22:18:20 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020118.201600.44942631.imp@village.org> References: <20020118.201600.44942631.imp@village.org> Date: Fri, 18 Jan 2002 22:18:18 -0500 To: "M. Warner Losh" From: Garance A Drosihn Subject: Re: Stable build broken, missing update to pccbbdevid.h Cc: stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 8:16 PM -0700 1/18/02, M. Warner Losh wrote: >In message: > Garance A Drosihn writes: >: seems to need Revision 1.5 of src/sys/dev/pccbb/pccbbdevid.h >: which has *not* been MFC-ed. >: >: Apologies if my guess is wrong... > >So, you are right :-( I've already committed the fix, after getting the go-ahead from re@ It seems to be OK now. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 19:20:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (pcp419987pcs.martnz01.ga.comcast.net [68.47.18.240]) by hub.freebsd.org (Postfix) with ESMTP id 28F5C37B405 for ; Fri, 18 Jan 2002 19:20:16 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id g0J3KFc01658 for ; Fri, 18 Jan 2002 22:20:15 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C48E5EF.87F873F9@vortex.wa4phy.net> Date: Fri, 18 Jan 2002 22:20:15 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-RC i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Java Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just discovered I need to install java on this machine, but looking at the ports, I see all kinds of flavors of java. Is the Linux-jdk 13/14 fairly stable? Stated in the docs of the software I'm attempting to bring up, says that it needs Java v1.2 or higher. The software is GDS, a GrADS-DODS Server. Can anybody help me out here? Thanks.. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 19:21: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2957B37B416 for ; Fri, 18 Jan 2002 19:20:52 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g0J3Kol34305; Fri, 18 Jan 2002 20:20:51 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g0J3Kmx04366; Fri, 18 Jan 2002 20:20:48 -0700 (MST) (envelope-from imp@village.org) Date: Fri, 18 Jan 2002 20:20:35 -0700 (MST) Message-Id: <20020118.202035.122942008.imp@village.org> To: drosih@rpi.edu Cc: stable@freebsd.org Subject: Re: Stable build broken, missing update to pccbbdevid.h From: "M. Warner Losh" In-Reply-To: References: <20020118.201600.44942631.imp@village.org> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: Garance A Drosihn writes: : I've already committed the fix, after getting the go-ahead from re@ : : It seems to be OK now. OK. Thanks. I was just going to look into that. Sorry for the screw up. I even had it in my tree here, which is why I didn't see it earlier. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 19:41:41 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 3AFB937B416 for ; Fri, 18 Jan 2002 19:41:39 -0800 (PST) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.33 #1 (Red Hack)) id 16RmNl-0002nt-00; Sat, 19 Jan 2002 16:41:29 +1300 Date: Sat, 19 Jan 2002 16:41:29 +1300 (NZDT) From: Juha Saarinen To: Sam Drinkard Cc: "freebsd-stable@freebsd.org" Subject: Re: Java In-Reply-To: <3C48E5EF.87F873F9@vortex.wa4phy.net> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 18 Jan 2002, Sam Drinkard wrote: > I just discovered I need to install java on this machine, but looking at > the ports, I see all kinds of flavors of java. Is the Linux-jdk 13/14 > fairly stable? Stated in the docs of the software I'm attempting to > bring up, says that it needs Java v1.2 or higher. The software is GDS, > a GrADS-DODS Server. Can anybody help me out here? Works fine for us, with Resin plus a few other bits and pieces. -- Regards, Juha C program run. C program crash. C programmer quit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 19:52:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id 4FB0E37B405 for ; Fri, 18 Jan 2002 19:52:07 -0800 (PST) Received: (from eugen@localhost) by D00015.dialonly.kemerovo.su (8.11.6/8.11.6) id g0J3a8000559; Sat, 19 Jan 2002 10:36:08 +0700 (KRAT) (envelope-from eugen) Date: Sat, 19 Jan 2002 10:36:08 +0700 From: Eugene Grosbein To: Matt Penna Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD Memory Requirements Legacy and Present Message-ID: <20020119103608.A488@grosbein.pp.ru> References: <5.1.0.14.2.20020117210634.01d8eec0@vmspop.isc.rit.edu> <3C47AE08.24F97802@www.kuzbass.ru> <5.1.0.14.2.20020118130619.01d954f0@vmspop.isc.rit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.2.20020118130619.01d954f0@vmspop.isc.rit.edu>; from mdp1261@ritvax.rit.edu on Fri, Jan 18, 2002 at 01:51:57PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jan 18, 2002 at 01:51:57PM -0500, Matt Penna wrote: > The allocation of swap space during the install is a great bit of > information I didn't have previously, so I'll be sure to mention that in my > revisions. You mention that an install will succeed with 8MB and some swap > - will it work with less physical memory as long as swap is allocated? If > you don't know the answer, no problem; It definitly will not work with 4Mb and I don't know where dead line lies. > I can simply try it out when I have > easy access to a low-memory machine. (I just moved to a new house and a lot > of my hardware is not here yet.) Well, if you have good hardware running FreeBSD you can easily make experiments emulating memory-stressed situations. Just grab kernel configuration for install floppy, add options MAXMEM=5*1024 The boot floppy will use only 5Mb of RAM then. Rebuild install floppies then and try to boot and see if it will be possible to activate swap before die :-) Apparently, it won't work if you can't proceed to swap activation. At the other hand, it will be nesessary to try complete installation with real old hardware when you'll find 'dead threshold'. Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 22: 0:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0B9CF37B404 for ; Fri, 18 Jan 2002 22:00:46 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g0J60em46015; Fri, 18 Jan 2002 22:00:40 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Jan 2002 22:00:40 -0800 (PST) From: Matthew Dillon Message-Id: <200201190600.g0J60em46015@apollo.backplane.com> To: Steve Shorter Cc: freebsd-stable@FreeBSD.ORG Subject: Re: "server not responding" / "is alive again" NFS tunables References: <20020116101212.A610@nomad.lets.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It's probably the NFS retry code being a little too finicky again. It should be fairly harmless, but you can try mounting the clients with the 'dumbtimer' mount option to get rid of the dynamic retransmit estimator. If you are interested in helping me fix the dynamic retransmit estimator, send me an email sometime after we release 4.5 and I'll give you some simple patch sets to try. (We don't have time to fix it prior to the release and I'm busy with release stuff right now). I would also be interested in a tcpdump of the NFS traffic on the client side that catches it in the act (one should see a retransmitted nfs request in the dump at the same time the kernel logs the responding/alive-again warning). -Matt Matthew Dillon :Howdy! : : I have a dedicated NFS server with 16 nfsd's running, connected :to SCSI raid/softupdates and good network connectivity/switching. Under :moderate or even sometimes light load the clients(7 of them) log messages : : nfs server 192.168.10.2:/mnt: not responding : nfs server 192.168.10.2:/mnt: is alive again : : several times per minute. They always have the same timestamp. Performance :is not noticably impaired, but I am wondering if this situation will eventually :become a performance barrier as the system ramps up to full production, if :the above log messages mean that packets must be delayed or retransmitted. : : I have experimented with both udp/tcp mounts with various rw sizes :ranging from 8192 - 32768. tcp with rw=32768 was the worst case wrt above, and :am currently using udp mounts with default rw. Running 8 or 16 nfsd gives no :noticable difference wrt the above either. : : I can find no issues on the server side, and was wondering if :there is a timeout threshold on the client side that is triggering the :messages/condition and whether adjusting the compile time tunables in :sys/nfs/nfs.h can aleviate the problem(if it even is a problem). : : The server is 4.5-PRE, the clients are 4.4-RELEASE. I know :that there have been a log of NFS changes in 4.5, but testing 4.5 on :the clients is problematic. Do any of those changes affect the above? : : So which variable(s) in nfs.h affect the client side and contribute :to the server timeout situation. Or are there any other suggestions? : : Here are the variables in nfs.h(4.5-RC) for your amusement. Thanks : :/* : * Tunable constants for nfs : */ : :#define NFS_MAXIOVEC 34 :#define NFS_TICKINTVL 5 /* Desired time for a tick (msec) */ :#define NFS_HZ (hz / nfs_ticks) /* Ticks/sec */ :#define NFS_TIMEO (1 * NFS_HZ) /* Default timeout = 1 second */ :#define NFS_MINTIMEO (1 * NFS_HZ) /* Min timeout to use */ :#define NFS_MAXTIMEO (60 * NFS_HZ) /* Max timeout to backoff to */ :#define NFS_MINIDEMTIMEO (5 * NFS_HZ) /* Min timeout for non-idempotent ops*/ :#define NFS_MAXREXMIT 100 /* Stop counting after this many */ :#define NFS_MAXWINDOW 1024 /* Max number of outstanding requests */ :#define NFS_RETRANS 10 /* Num of retrans for soft mounts */ :#define NFS_MAXGRPS 16 /* Max. size of groups list */ :#ifndef NFS_MINATTRTIMO :#define NFS_MINATTRTIMO 3 /* VREG attrib cache timeout in sec */ :#endif :#ifndef NFS_MAXATTRTIMO :#define NFS_MAXATTRTIMO 60 :#endif :#ifndef NFS_MINDIRATTRTIMO :#define NFS_MINDIRATTRTIMO 30 /* VDIR attrib cache timeout in sec */ :#endif :#ifndef NFS_MAXDIRATTRTIMO :#define NFS_MAXDIRATTRTIMO 60 :#endif :#define NFS_WSIZE 8192 /* Def. write data size <= 8192 */ :#define NFS_RSIZE 8192 /* Def. read data size <= 8192 */ :#define NFS_READDIRSIZE 8192 /* Def. readdir size */ :#define NFS_DEFRAHEAD 1 /* Def. read ahead # blocks */ :#define NFS_MAXRAHEAD 4 /* Max. read ahead # blocks */ :#define NFS_MAXUIDHASH 64 /* Max. # of hashed uid entries/mp */ :#define NFS_MAXASYNCDAEMON 20 /* Max. number async_daemons runnable */ :#define NFS_MAXGATHERDELAY 100 /* Max. write gather delay (msec) */ :#ifndef NFS_GATHERDELAY :#define NFS_GATHERDELAY 10 /* Default write gather delay (msec) */ :#endif :#define NFS_DIRBLKSIZ 4096 /* Must be a multiple of DIRBLKSIZ */ :#ifdef _KERNEL :#define DIRBLKSIZ 512 /* XXX we used to use ufs's DIRBLKSIZ */ :#endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 22:13:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mao.stokely.org (mao.stokely.org [65.84.64.228]) by hub.freebsd.org (Postfix) with ESMTP id 3142737B416; Fri, 18 Jan 2002 22:13:11 -0800 (PST) Received: by mao.stokely.org (Postfix, from userid 2074) id E16B34B65D; Fri, 18 Jan 2002 22:13:05 -0800 (PST) Date: Fri, 18 Jan 2002 22:13:05 -0800 From: Murray Stokely To: Robert Watson Cc: Nevermind , freebsd-stable@freebsd.org, qa@freebsd.org Subject: Re: we should note "maxusers 0" in UPDATING Message-ID: <20020119061305.GF18200@freebsdmall.com> References: <20020118151109.GA35506@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Lez9QO3Seu3ycz0M" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Lez9QO3Seu3ycz0M Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 18, 2002 at 11:15:51AM -0500, Robert Watson wrote: > And it should even appear in the handbook, which last I checked it still > didn't. I added this to the Handbook in config/chapter.sgml r1.31 on 12/31/01. It is indeed there as someone posted the URL for the content on the web site. It is not in the kernel configuration chapter, but in the "Configuration and Tuning" chapter. Obviously, we need to add a pointer from the Kernel Configuration chapter, or move the content entirely. - Murray ---------------------------- revision 1.31 date: 2001/12/31 21:10:13; author: murray; state: Exp; lines: +27 -14 * Update the Config chapter regarding vfs.vmiodirenable, MAXUSERS, and Soft Updates. * Also fix various typos and markup errors. PR: docs/33017 Submitted by: Ceri ---------------------------- config/chapter.sgml : As of FreeBSD 4.5, setting to 0 in your kernel configuration file will choose a reasonable default value based on the amount of RAM present in your system. --Lez9QO3Seu3ycz0M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE8SQ5xtNcQog5FH30RAmFoAJ9r+xaGMX8X3klzZdxDXrPqIYDIuQCfRkmv D/2Txi+Z9rR30P3/7JkAPwk= =6jmG -----END PGP SIGNATURE----- --Lez9QO3Seu3ycz0M-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 18 23: 1:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id C068737B416 for ; Fri, 18 Jan 2002 23:01:42 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id g0J71ec110804; Sat, 19 Jan 2002 02:01:41 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sat, 19 Jan 2002 02:01:39 -0500 To: stable@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Possible bug in 4.5-RC1 vs VMware (linux emulation?) Cc: Marcel Moolenaar , Dag-Erling Smorgrav Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Jan 11/2002 (a week ago), Garance A Drosihn wrote: >I upgraded to 4.5-RC1 as it was on Wednesday (Jan 9th) at about 7pm. >I then upgraded most (but not quite all) of my ports. On Thursday >I needed to run VMware2 to debug some obscure problem I am seeing >elsewhere (something not related to freebsd at all). > >The possible-bug part is that I get an error message when starting >up vmware, saying "VMware was unable to read from /dev/acd0c. This >can be caused by a Linux kernel bug...". It is saying "Linux kernel" >because this is the Linux version of VMware2, which I am running via >Linux emulation on freebsd. So, it thinks the host OS is linux. In >any case, I wasn't getting this error until after those upgrades. > >All my ports are updated except for: > cvsup gdk-pixbuf glib gtk lcms mozilla and stunnel >so I don't *think* any of those would be the problem. For what it's worth, today I did another buildworld, and I seemed to still have the error (but I only did one test). I then upgraded all of my ports, and the error with the CD-ROM vs Vmware has gone away. So, whatever the problem was, I think it has been fixed now. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 19 5:27:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 25C7137B41D; Sat, 19 Jan 2002 05:27:29 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.6/8.11.6) id g0JDCAn92483; Sat, 19 Jan 2002 13:12:10 GMT (envelope-from nik) Date: Sat, 19 Jan 2002 13:12:10 +0000 From: Nik Clayton To: Robert Watson Cc: "David W. Chapman Jr." , Lawrence Sica , Nevermind , freebsd-stable@freebsd.org, qa@freebsd.org, re@freebsd.org Subject: Re: we should note "maxusers 0" in UPDATING Message-ID: <20020119131210.M62672@clan.nothing-going-on.org> References: <20020118163839.GB67507@leviathan.inethouston.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="v541l457l4DThMFo" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@freebsd.org on Fri, Jan 18, 2002 at 12:03:31PM -0500 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --v541l457l4DThMFo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 18, 2002 at 12:03:31PM -0500, Robert Watson wrote: > o Doesn't account for maxusers 0 auto-tuning; probably should specify the > scaling factor, which is currently: [...] > o GENERIC now includes UFS_DIRHAS by default, and that should probably be > listed in the descriptions here, if not also elsewhere: >=20 > options UFS_DIRHASH #Improve performance on big direc= tories >=20 > o pseudo-device gif is now self-cloning, so the constant number of > instances there is no longer needed. Here's the line now in GENERIC on > -STABLE: >=20 > pseudo-device gif # IPv6 and IPv4 tunneling Fixed. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --v541l457l4DThMFo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxJcKkACgkQk6gHZCw343U2aACePILhKR88VNEa1ZRxVvC/L0zz xSUAmgMWQnLc0hTa4kAfQG78zIvxnhCB =z3wA -----END PGP SIGNATURE----- --v541l457l4DThMFo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 19 5:34:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mailrelay.netcologne.de (mailrelay.netcologne.de [194.8.194.96]) by hub.freebsd.org (Postfix) with ESMTP id D11C037B419 for ; Sat, 19 Jan 2002 05:34:07 -0800 (PST) Received: from localhost (xdsl-213-168-108-225.netcologne.de [213.168.108.225]) by mailrelay.netcologne.de (8.11.6/8.11.6) with ESMTP id g0JDY4Y27594 for ; Sat, 19 Jan 2002 14:34:04 +0100 (MET) Received: (qmail 718 invoked by uid 1001); 19 Jan 2002 13:29:02 -0000 Date: Sat, 19 Jan 2002 14:29:02 +0100 From: Thomas Seck To: stable@FreeBSD.ORG Subject: Re: what's vnlru? Message-ID: <20020119132902.GB676@laurel.seck.home> Mail-Followup-To: stable@FreeBSD.ORG References: <200201151618468.SM01176@141.com> <200201160101.g0G117r64693@apollo.backplane.com> <20020116104904.A2800@shikima.mine.nu> <20020116135318.GA427@laurel.seck.home> <200201190102.g0J12MF37253@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200201190102.g0J12MF37253@apollo.backplane.com> User-Agent: Mutt/1.3.24i Organization: private site in Germany X-PGP-KeyID: DF46EE05 X-PGP-Fingerprint: A38F AE66 6B11 6EB9 5D1A B67D 2444 2FE1 DF46 EE05 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG # Matthew Dillon (dillon@apollo.backplane.com): [Relnotes description] > How about this (see at end). Unfortunately, I have no idea how to make > the doc tree build, typing 'make' in /usr/src/release/doc in -stable > doesn't work. You need to set DOC_PREFIX=/path/to/docprojfiles (usually /usr/doc) in your environment or /etc/make.conf. > Index: common/new.sgml > =================================================================== > RCS file: /home/ncvs/src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml,v > retrieving revision 1.22.2.176 > diff -u -r1.22.2.176 new.sgml > --- common/new.sgml 14 Jan 2002 16:00:20 -0000 1.22.2.176 > +++ common/new.sgml 19 Jan 2002 00:42:35 -0000 > @@ -149,6 +149,12 @@ > the timing of samples, in order to avoid synchronization with > processes that run periodically. > > + The kernel now enforces the kern.maxvnodes limit with > + a new kernel process called vnlru. The > + code typically only needs to do work on large-memory systems > + which access lots of tiny files and prevents us from overflowing > + the kernel malloc hoppers for vnodes or inodes. > + > If a debugging kernel with modules is being built > (i.e. using makeoptions DEBUG=-g), the modules > will now be built with debugging support as well, for Hmm, this sounds like one can turn it on or off (which is not the case, right?) and people then tend to ask how to do it. How about rewording the second sentence into something like "This code prevents the system from overflowing the kernel malloc hoppers for vnodes or inodes when a large number of small files are accessed on large memory systems"? (Please apply grammar fixes as needed, apologies for my german high-school english). --Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 19 5:43:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 7A09237B405 for ; Sat, 19 Jan 2002 05:43:38 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020119134338.YPGJ10199.rwcrmhc53.attbi.com@bmah.dyndns.org>; Sat, 19 Jan 2002 13:43:38 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id g0JDhbN72777; Sat, 19 Jan 2002 05:43:37 -0800 (PST) (envelope-from bmah) Message-Id: <200201191343.g0JDhbN72777@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Thomas Seck Cc: stable@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: what's vnlru? In-reply-to: <20020119132902.GB676@laurel.seck.home> References: <200201151618468.SM01176@141.com> <200201160101.g0G117r64693@apollo.backplane.com> <20020116104904.A2800@shikima.mine.nu> <20020116135318.GA427@laurel.seck.home> <200201190102.g0J12MF37253@apollo.backplane.com> <20020119132902.GB676@laurel.seck.home> Comments: In-reply-to Thomas Seck message dated "Sat, 19 Jan 2002 14:29:02 +0100." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Jan 2002 05:43:37 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If memory serves me right, Thomas Seck wrote: [snip] > > + The kernel now enforces the kern.maxvnodes limit with > > + a new kernel process called vnlru. The > > + code typically only needs to do work on large-memory systems > > + which access lots of tiny files and prevents us from overflowing > > + the kernel malloc hoppers for vnodes or inodes. [snip] > Hmm, this sounds like one can turn it on or off (which is not the > case, right?) and people then tend to ask how to do it. How about > rewording the second sentence into something like "This code prevents > the system from overflowing the kernel malloc hoppers for vnodes or > inodes when a large number of small files are accessed on large memory > systems"? (Please apply grammar fixes as needed, apologies for my german > high-school english). So...here's what I already committed a day or two ago to the release notes for both CURRENT and 4-STABLE... The kern.maxvnodes limit now properly limits the number of vnodes in use. Previously only vnodes with no cached pages could be freed; this could allow the number of vnodes to grow without limit on large-memory machines accessing many small files. A vnlru kernel thread helps to flush and reuse vnodes. Matt...if you'd like me to replace this with what you wrote or make changes, just give me a yell. Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 19 5:50:20 2002 Delivered-To: freebsd-stable@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B048C37B417; Sat, 19 Jan 2002 05:50:15 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g0JDo8D38591; Sat, 19 Jan 2002 08:50:08 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 19 Jan 2002 08:50:08 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Nik Clayton Cc: "David W. Chapman Jr." , Lawrence Sica , Nevermind , freebsd-stable@freebsd.org, qa@freebsd.org, re@freebsd.org Subject: Re: we should note "maxusers 0" in UPDATING In-Reply-To: <20020119131210.M62672@clan.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 19 Jan 2002, Nik Clayton wrote: > Fixed. Thanks! Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 19 6:40:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from fem.uniag.sk (fem.uniag.sk [193.87.97.7]) by hub.freebsd.org (Postfix) with ESMTP id 3C27E37B419 for ; Sat, 19 Jan 2002 06:40:34 -0800 (PST) Received: from localhost (lk01@localhost) by fem.uniag.sk (8.10.2+Sun/8.10.2) with ESMTP id g0JEdZR22629 for ; Sat, 19 Jan 2002 15:39:35 +0100 (MET) Date: Sat, 19 Jan 2002 15:39:35 +0100 (MET) From: Ladislav Kostal To: freebsd-stable@freebsd.org Subject: server recommendation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, We plan to buy new server in few weeks. It should be something with at least 4 PIII Xeon, 4GB RAM, RAID, 1GB NIC and some fast U160 SCSI disks. I am looking at intel SPKA4/SRKA4. But I found some mentions on lists about problems with 4GB ram and some problems with ServerWorks chipset. What servers are you using? What would you recommend? Thanks in advance Ladislav Kostal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 19 7:19:45 2002 Delivered-To: freebsd-stable@freebsd.org Received: from fem.uniag.sk (fem.uniag.sk [193.87.97.7]) by hub.freebsd.org (Postfix) with ESMTP id BBC6637B404 for ; Sat, 19 Jan 2002 07:19:42 -0800 (PST) Received: from localhost (lk01@localhost) by fem.uniag.sk (8.10.2+Sun/8.10.2) with ESMTP id g0JFIiE24216 for ; Sat, 19 Jan 2002 16:18:45 +0100 (MET) Date: Sat, 19 Jan 2002 16:18:44 +0100 (MET) From: Ladislav Kostal To: freebsd-stable@freebsd.org Subject: ide problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, We have som problems with IDE in RELENG4. When I disable IDE controller in BIOS, remove it from kernel - system can not boot. It stops just after lpt detection and before IDE stuff. Also in computer with just one IDE CDROM installation diskette stops after lpt. Disabling in BIOS and in visual kernel config doesn't help. Why? Thanks in advance Ladislav Kostal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 19 7:44:15 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by hub.freebsd.org (Postfix) with ESMTP id 3078437B416 for ; Sat, 19 Jan 2002 07:43:49 -0800 (PST) Received: from lungfish.ntlworld.com ([62.253.152.236]) by mta05-svc.ntlworld.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020119154340.PYAQ7206.mta05-svc.ntlworld.com@lungfish.ntlworld.com> for ; Sat, 19 Jan 2002 15:43:40 +0000 Received: from tuatara.goatsucker.org (tuatara.goatsucker.org [192.168.1.6]) by lungfish.ntlworld.com (8.11.3/8.11.3) with ESMTP id g0JFhcn10735 for ; Sat, 19 Jan 2002 15:43:38 GMT (envelope-from scott@tuatara.goatsucker.org) Received: (from scott@localhost) by tuatara.goatsucker.org (8.11.6/8.11.6) id g0JFfso00720 for freebsd-stable@freebsd.org; Sat, 19 Jan 2002 15:41:54 GMT (envelope-from scott) Date: Sat, 19 Jan 2002 15:41:54 +0000 From: Scott Mitchell To: freebsd-stable@freebsd.org Subject: 4.5-RC kernel panic on boot with Advansys SCSI card Message-ID: <20020119154154.A422@localhost> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.5-RC i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, My 4.5-RC kernel (from sources cvsupped at around 2300 GMT on Jan 17th) started crashing during boot after I plugged in an IWill 2936UW-E SCSI adapter. I've attached the kernel config, dmesg and gdb stack trace. Booting with a GENERIC kernel built from the same sources works just fine, so I'll hazard a guess that this is somehow connected with module loading, especially since the crash happens in a kldload syscall. Note that adw0 is probed once during the intial boot, then pops up again right before the crash, after the system has gone multiuser. The IWill card doesn't quite work on FreeBSD -- I'd actually plugged it in so I could start doing something about that. It's probed as an Advansys 3550 by Win2K and works fine on that OS, dual-booted on the same hardware. The only thing attached to it is a Yamaha CDRW drive. Any thoughts? I appreciate that people will be busy with getting 4.5 out the door; I'll hang onto the crash dump and see if I can figure out anything myself in the meantime. Cheers, Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott.mitchell@mail.com | 0xAA775B8B | -- Anon --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=TUATARA # # TUATARA -- Custom kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.37 2001/12/19 18:34:45 iedowse Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident TUATARA maxusers 0 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories #options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem #options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required #options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev options DDB # Drop to kernel debugger on panic # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers #device aac # Adaptec FSA RAID, Dell PERC2/PERC3 #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family #device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device txp # 3Com 3cR990 (``Typhoon'') #device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! #device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device pcn # AMD Am79C97x PCI 10/100 NICs #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device wx # Intel Gigabit Ethernet Card (``Wiseman'') #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # 'device ed' requires 'device miibus' #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex #device ep #device fe0 at isa? port 0x300 # Xircom Ethernet #device xe # PRISM I IEEE 802.11b wireless NIC. #device awi # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attachment needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. #device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # # SMB bus # # System Management Bus support is provided by the 'smbus' device. # Access to the SMBus device is via the 'smb' device (/dev/smb*), # which is a child of the 'smbus' device. # # Supported devices: # smb standard io through /dev/smb* # # Supported SMB interfaces: # iicsmb I2C to SMB bridge with any iicbus interface # bktr brooktree848 I2C hardware interface # intpm Intel PIIX4 (82371AB, 82443MX) Power Management Unit # alpm Acer Aladdin-IV/V/Pro2 Power Management Unit # ichsmb Intel ICH SMBus controller chips (82801AA, 82801AB, 82801BA) # device smbus # Bus support, required for smb below. device intpm device alpm device ichsmb device smb # # I2C Bus # # Philips i2c bus support is provided by the `iicbus' device. # # Supported devices: # ic i2c network interface # iic i2c standard io # iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. # # Supported interfaces: # pcf Philips PCF8584 ISA-bus controller # bktr brooktree848 I2C software interface # # Other: # iicbb generic I2C bit-banging code (needed by lpbb, bktr) # device iicbus # Bus support, required for ic/iic/iicsmb below. device iicbb device ic device iic device iicsmb # smb over i2c bridge device pcf0 at isa? port 0x320 irq 5 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP #pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) #pseudo-device md # Memory "disks" #pseudo-device gif # IPv6 and IPv4 tunneling #pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support #device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface #device usb # USB Bus (required) #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse #device uscanner # Scanners #device urio # Diamond Rio MP3 Player # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Content-Transfer-Encoding: quoted-printable Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-RC #0: Fri Jan 18 00:04:28 GMT 2002 scott@tuatara:/local/0/-STABLE/obj/usr/src/sys/TUATARA Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) XP 1800+ (1535.22-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x662 Stepping =3D 2 Features=3D0x383f9ff AMD Features=3D0xc0480000<,AMIE,DSP,3DNow!> real memory =3D 536805376 (524224K bytes) avail memory =3D 518348800 (506200K bytes) Preloaded elf kernel "kernel" at 0xc0373000. Preloaded elf module "snd_emu10k1.ko" at 0xc037309c. Preloaded elf module "snd_pcm.ko" at 0xc0373140. Preloaded elf module "if_xl.ko" at 0xc03731e0. Preloaded elf module "miibus.ko" at 0xc0373280. Pentium Pro MTRR support enabled Using $PIR table, 10 entries at 0xc00fde00 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 5.0 irq 5 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd400-0xd40f at device 7.1 on= pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 9 pci0: at 7.3 irq 9 ichsmb0: at device 7.4 on pci0 device_probe_and_attach: ichsmb0 attach returned 6 xl0: <3Com 3c900B-COMBO Etherlink XL> port 0xe000-0xe07f mem 0xd9000000-0xd= 900007f irq 10 at device 9.0 on pci0 xl0: Ethernet address: 00:10:4b:1a:03:98 xl0: selecting 10baseT transceiver, half duplex pcm0: port 0xe400-0xe41f irq 11 at device 13.0 on pci0 adw0: port 0xec00-0xec3f mem 0xd9002000-= 0xd90020ff irq 11 at device 15.0 on pci0 adw0: SCSI ID 7, adw0: Firmware load failed! device_probe_and_attach: adw0 attach returned 6 orm0: