From owner-freebsd-stable Sun Aug 16 06:46:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12675 for freebsd-stable-outgoing; Sun, 16 Aug 1998 06:46:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12538 for ; Sun, 16 Aug 1998 06:46:09 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id PAA20865 for ; Sun, 16 Aug 1998 15:45:40 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id PAA15919 for ; Sun, 16 Aug 1998 15:45:40 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id PAA24165 for ; Sun, 16 Aug 1998 15:45:37 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808161345.PAA19691@internal> Subject: Re: Found reason why lpr -r -s doesn't work as expected In-Reply-To: <199808151331.GAA01035@cwsys.cwsent.com> from Cy Schubert - ITSD Open Systems Group at "Aug 15, 98 06:31:54 am" To: cschuber@uumail.gov.bc.ca Date: Sun, 16 Aug 1998 15:45:28 +0200 (CEST) Cc: andre.albsmeier@mchp.siemens.de, imp@village.org, freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > In message <199808141807.UAA13224@internal> Andre Albsmeier writes: > > > : if (strchr(line+1, '/')) > > > : continue; > > > : This disables the removement of files starting with '/'. This was > > > : introduced in version 1.14 according to the CVS log. However, I didn't > > > : find an explanation why this change was made. Is it a security hole? > > > > > > Without this fix, people could remove any file on your system by > > > having remote print access. > > > > OK, and if remote access is disabled would it be safe? Have you got > > any references how this exploit exactly works so I can figure out > > what to do in order to be able to remove both files and without > > making my machine insecure... > > No. By revoking remote access to your lpd, e.g. firewall, you would > still have an exposure that local users could exploit, which in this > case revoking access to local users would solve the problem. I think > you get the picture... OK, thanks for the info. I have now changed printjob.c so that removing files containing '/' still is forbidden except when it starts with '/var/spool/samba/'. It's ugly but works. But, I think this behaviuor should be stated in the manual page of lpr. Now it says: -r Remove the file upon completion of spooling or upon completion of printing (with the -s option). -s Use symbolic links. Usually files are copied to the spool direc- tory. The -s option will use symlink(2) to link data files rather than trying to copy them so large files can be printed. Thanks again, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 07:28:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15838 for freebsd-stable-outgoing; Sun, 16 Aug 1998 07:28:48 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sussie.datadesign.se (ns.datadesign.se [194.23.109.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15827; Sun, 16 Aug 1998 07:28:37 -0700 (PDT) (envelope-from kaj@interbizz.se) Received: from localhost (sussie.datadesign.se [194.23.109.130]) by sussie.datadesign.se (8.8.5/8.8.7) with ESMTP id QAA16228; Sun, 16 Aug 1998 16:24:36 +0200 (MET DST) To: andre.albsmeier@mchp.siemens.de Cc: cschuber@uumail.gov.bc.ca, imp@village.org, freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Cc: kaj@interbizz.se Subject: Re: Found reason why lpr -r -s doesn't work as expected From: Rasmus Kaj In-Reply-To: Your message of "Sun, 16 Aug 1998 15:45:28 +0200 (CEST)" <199808161345.PAA19691@internal> References: <199808161345.PAA19691@internal> X-Mailer: Mew version 1.92.4 on XEmacs 20.4 (Emerald) X-URL: http://www.e.kth.se/~kaj/ X-Phone: +46 (0)8 - 692 35 09 / +46 (0)70 640 49 14 X-Attribution: Kaj X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980816162435K.kaj@interbizz.se> Date: Sun, 16 Aug 1998 16:24:35 +0200 X-Dispatcher: imput version 971024 Lines: 23 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "AA" == Andre Albsmeier writes: >> No. By revoking remote access to your lpd, e.g. firewall, you would >> still have an exposure that local users could exploit, which in this >> case revoking access to local users would solve the problem. I think >> you get the picture... AA> OK, thanks for the info. I have now changed printjob.c so that AA> removing files containing '/' still is forbidden except when it AA> starts with '/var/spool/samba/'. It's ugly but works. A 'serious' way to fix this (IMHO) would be to make lpd su to the user that requested the printout before removing any file at all. But this would probably be very hard to do ... Obvious catch: a remote user might print without even having an account on the host where lpd runns. // Rasmus -- kaj@cityonline.se --------------- Rasmus Kaj - http://www.e.kth.se/~kaj/ \ CityOnLine IB Production AB - http://www.CityOnLine.se/ \------------------- HELP! MY TYPEWRITER IS BROKEN! -- E. E. CUMMINGS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 07:45:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17695 for freebsd-stable-outgoing; Sun, 16 Aug 1998 07:45:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17660 for ; Sun, 16 Aug 1998 07:45:38 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id QAA23168 for ; Sun, 16 Aug 1998 16:45:05 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id QAA18406 for ; Sun, 16 Aug 1998 16:45:04 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id QAA24964 for ; Sun, 16 Aug 1998 16:45:02 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808161444.QAA04591@internal> Subject: Re: Found reason why lpr -r -s doesn't work as expected In-Reply-To: <19980816162435K.kaj@interbizz.se> from Rasmus Kaj at "Aug 16, 98 04:24:35 pm" To: kaj@interbizz.se (Rasmus Kaj) Date: Sun, 16 Aug 1998 16:44:57 +0200 (CEST) Cc: andre.albsmeier@mchp.siemens.de, cschuber@uumail.gov.bc.ca, imp@village.org, freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, kaj@interbizz.se X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>>>> "AA" == Andre Albsmeier writes: > > >> No. By revoking remote access to your lpd, e.g. firewall, you would > >> still have an exposure that local users could exploit, which in this > >> case revoking access to local users would solve the problem. I think > >> you get the picture... > > AA> OK, thanks for the info. I have now changed printjob.c so that > AA> removing files containing '/' still is forbidden except when it > AA> starts with '/var/spool/samba/'. It's ugly but works. > > A 'serious' way to fix this (IMHO) would be to make lpd su to the user > that requested the printout before removing any file at all. But this > would probably be very hard to do ... Obvious catch: a remote user > might print without even having an account on the host where lpd > runns. I thought of similar things but haven't come to a handy solution yet... I don't know a lot about lpr/lpd interaction and how the cf files are created and how remote printing works in detail. But maybe one day I'll have a look at this. It's really annoying, especially because samba prints with 'lpr -r -s'... -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 08:36:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22364 for freebsd-stable-outgoing; Sun, 16 Aug 1998 08:36:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.ukconnect.net (mail.ukconnect.net [195.219.13.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA22356 for ; Sun, 16 Aug 1998 08:36:09 -0700 (PDT) (envelope-from phil@virtek.com) Received: from gsi.ukconnect.net (gsi.ukconnect.net [195.219.13.179]) by mail.virtek.com (NTMail 3.03.0017/1.aa3h) with ESMTP id ya012166 for ; Sun, 16 Aug 1998 15:34:06 +0100 Message-Id: <3.0.3.32.19980816163509.00a2bbe0@mail.virtek.com> X-Sender: phil@mail.virtek.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 16 Aug 1998 16:35:09 +0100 To: freebsd-stable@FreeBSD.ORG From: Phil Allsopp Subject: virtual FTP servers Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am finding it difficult to find information on setting up a number of virtual ftp servers on a single 2.2.5 FreeBSD box. I wondered if anyone out there could point me the right way. Regards Phil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 12:22:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09912 for freebsd-stable-outgoing; Sun, 16 Aug 1998 12:22:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA09811 for ; Sun, 16 Aug 1998 12:21:55 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 17703 invoked by uid 1003); 16 Aug 1998 19:21:11 -0000 Message-ID: <19980816212111.A16740@rucus.ru.ac.za> Date: Sun, 16 Aug 1998 21:21:11 +0200 From: Neil Blakey-Milner To: Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: virtual FTP servers References: <3.0.3.32.19980816163509.00a2bbe0@mail.virtek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3.0.3.32.19980816163509.00a2bbe0@mail.virtek.com>; from Phil Allsopp on Sun, Aug 16, 1998 at 04:35:09PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun 1998-08-16 (16:35), Phil Allsopp wrote: > I am finding it difficult to find information on setting up a number of > virtual ftp servers on a single 2.2.5 FreeBSD box. I wondered if anyone out > there could point me the right way. Try ncftpd. Should be able to find it from: http://www.probe.net/~mgleason/ncftpd/ There seems to be a FreeBSD version. (well, it came with a README.freebsd file mentioning binaries compiled for 2.2.5) Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 12:49:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13275 for freebsd-stable-outgoing; Sun, 16 Aug 1998 12:49:09 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA13243 for ; Sun, 16 Aug 1998 12:48:59 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z88ka-0002T5-00; Sun, 16 Aug 1998 12:46:00 -0700 Date: Sun, 16 Aug 1998 12:45:57 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Neil Blakey-Milner cc: Phil Allsopp , freebsd-stable@FreeBSD.ORG Subject: Re: virtual FTP servers In-Reply-To: <19980816212111.A16740@rucus.ru.ac.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Aug 1998, Neil Blakey-Milner wrote: > On Sun 1998-08-16 (16:35), Phil Allsopp wrote: > > I am finding it difficult to find information on setting up a number of > > virtual ftp servers on a single 2.2.5 FreeBSD box. I wondered if anyone out > > there could point me the right way. > > Try ncftpd. > > Should be able to find it from: http://www.probe.net/~mgleason/ncftpd/ > > There seems to be a FreeBSD version. (well, it came with a README.freebsd > file mentioning binaries compiled for 2.2.5) BTW, the stock FreeBSD ftpd supports virtual servers too. It has a nice internal ls feature. See "man ftpd" wu-ftpd seems the most common way to setup virtual FTP servers. There is alos prof-ftpd too. Consult appropiate manpages for each. Almost any ftpd can be virtualized using an inetd that allows different services per IP (ex. xinetd). > Neil > -- > Neil Blakey-Milner > nbm@rucus.ru.ac.za Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 13:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15701 for freebsd-stable-outgoing; Sun, 16 Aug 1998 13:02:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from coal.sentex.ca (coal.sentex.ca [209.112.4.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15694 for ; Sun, 16 Aug 1998 13:02:11 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by coal.sentex.ca (8.8.8/8.8.7) with SMTP id QAA01636; Sun, 16 Aug 1998 16:01:36 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19980816155908.00cbd830@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 16 Aug 1998 15:59:08 -0400 To: Phil Allsopp , freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: virtual FTP servers In-Reply-To: <3.0.3.32.19980816163509.00a2bbe0@mail.virtek.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:35 PM 8/16/98 +0100, Phil Allsopp wrote: >I am finding it difficult to find information on setting up a number of >virtual ftp servers on a single 2.2.5 FreeBSD box. I wondered if anyone out >there could point me the right way. Try wu-ftpd. There is a port of it as well and I think its free. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 18:32:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20702 for freebsd-stable-outgoing; Sun, 16 Aug 1998 18:32:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20694 for ; Sun, 16 Aug 1998 18:32:14 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA10294; Mon, 17 Aug 1998 11:01:21 +0930 (CST) Message-Id: <199808170131.LAA10294@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: stable@FreeBSD.ORG, doconnor@gsoft.com.au Subject: Re: Adaptec 7895? In-reply-to: Your message of "Fri, 14 Aug 1998 09:41:31 MST." <199808141641.JAA06248@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Aug 1998 11:01:20 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You need to get the CAM patches from ftp://ftp.freebsd.org/pub/FreeBSD/C > > the 7895 chips to work. > Yes, with CAM these chips work flawlessly. Hmm.. OK.. I get the following when I boot up tho -> ahc0 rev 4 int a irq 10 on pci0:14:0 ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time!ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1 rev 4 int b irq 10 on pci0:14:1 ahc1: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time!ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs Which is wrong, since only the first one is used, and it only has a CD-R on it using the ultra connector. I haven't got cdrecord to work yet (I'm trying the patched version) but I haven't tried too hard yet. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 19:30:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26744 for freebsd-stable-outgoing; Sun, 16 Aug 1998 19:30:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26708 for ; Sun, 16 Aug 1998 19:30:03 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id UAA00266; Sun, 16 Aug 1998 20:23:29 -0600 (MDT) Date: Sun, 16 Aug 1998 20:23:29 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808170223.UAA00266@narnia.plutotech.com> To: "Daniel O'Connor" cc: stable@FreeBSD.ORG Subject: Re: Adaptec 7895? Newsgroups: pluto.freebsd.stable In-Reply-To: <199808170131.LAA10294@cain.gsoft.com.au> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808170131.LAA10294@cain.gsoft.com.au> you wrote: >> > You need to get the CAM patches from ftp://ftp.freebsd.org/pub/FreeBSD/C >> > the 7895 chips to work. >> Yes, with CAM these chips work flawlessly. > Hmm.. OK.. I get the following when I boot up tho -> > ahc0 rev 4 int a irq 10 on pci0:14:0 > ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time!ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1 rev 4 int b irq 10 on pci0:14:1 > ahc1: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time!ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs > > Which is wrong, since only the first one is used, and it only has a CD-R on > it using the ultra connector. Is this controller on the MB? If so, and it allows you to select "automatic" termination, set the termination manually. It seems that many of the MB manufacturers ship BIOSes with "automatic termination" as the default, but don't build in the logic on the MB to actually perform auto-term. The aic7xxx driver will believe whatever the BIOS writes to the SEEPROM. Try setting the termination settings manually. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 19:37:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27934 for freebsd-stable-outgoing; Sun, 16 Aug 1998 19:37:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27915 for ; Sun, 16 Aug 1998 19:37:08 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id MAA11004; Mon, 17 Aug 1998 12:06:26 +0930 (CST) Message-Id: <199808170236.MAA11004@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: "Daniel O'Connor" , stable@FreeBSD.ORG Subject: Re: Adaptec 7895? In-reply-to: Your message of "Sun, 16 Aug 1998 20:23:29 CST." <199808170223.UAA00266@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Aug 1998 12:06:26 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "automatic" termination, set the termination manually. It seems that > many of the MB manufacturers ship BIOSes with "automatic termination" > as the default, but don't build in the logic on the MB to actually > perform auto-term. The aic7xxx driver will believe whatever the BIOS > writes to the SEEPROM. Try setting the termination settings manually. Ahh.. right.. OK, thanks :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 20:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00633 for freebsd-stable-outgoing; Sun, 16 Aug 1998 20:01:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00628 for ; Sun, 16 Aug 1998 20:01:02 -0700 (PDT) (envelope-from dmt@bigfoot.com) Received: from SpamWall.lbl.gov (root@localhost [127.0.0.1]) by postal1.lbl.gov (8.9.0/8.9.0) with ESMTP id TAA18571 for ; Sun, 16 Aug 1998 19:55:55 -0700 (PDT) Received: from dante.lbl.gov.lbl.gov (dante.lbl.gov [128.3.13.76]) by SpamWall.lbl.gov (8.9.0/8.9.0) with SMTP id TAA18564 for ; Sun, 16 Aug 1998 19:55:54 -0700 (PDT) Received: from noosphere (user-38ld63g.dialup.mindspring.com) by dante.lbl.gov.lbl.gov (4.1/SMI-4.1) id AA07178; Sun, 16 Aug 98 20:00:26 PDT Message-Id: <3.0.5.32.19980816200116.008175a0@ieng9.ucsd.edu> X-Sender: jdweinst@ieng9.ucsd.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 16 Aug 1998 20:01:16 -0700 To: stable@FreeBSD.ORG From: "Jeff W." Subject: Xwin wont do SVGA In-Reply-To: <199808170131.LAA10294@cain.gsoft.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First of all, I couldn't find my video card in the list, which I guess doesn't matter, but it's a diamond Fire GL 1000 Pro. So, I installed the generic SVGA and the VGA16 driver. The problem is that when I run XF86Setup, even if I tell X to use the SVGA server, and even if I mess with the different monitor types (I've tried all of them), X only runs in a really low resolution. Hardly any of the windows that pop up fit on the screen. So, my question is how do I get it to run in just a plain SVGA mode???? Do I have to install something else??? --Jeff W. "dude things out here are out of ahh... ahh. known reality." "mail me my damn toothpaste. yeah... that's right bitch. and send it priority too." My trippy page (note the address change): http://2cb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 20:02:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00766 for freebsd-stable-outgoing; Sun, 16 Aug 1998 20:02:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00733 for ; Sun, 16 Aug 1998 20:02:02 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA27855; Sun, 16 Aug 1998 20:01:11 -0700 (PDT) (envelope-from jdp) Message-Id: <199808170301.UAA27855@austin.polstra.com> To: "Daniel O'Connor" cc: stable@FreeBSD.ORG Subject: Re: Adaptec 7895? In-reply-to: Your message of "Mon, 17 Aug 1998 11:01:20 +0930." <199808170131.LAA10294@cain.gsoft.com.au> Date: Sun, 16 Aug 1998 20:01:11 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm.. OK.. I get the following when I boot up tho -> > ahc0 rev 4 int a irq 10 on pci0:14:0 > ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time!ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1 rev 4 int b irq 10 on pci0:14:1 > ahc1: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time!ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs > > Which is wrong, since only the first one is used, and it only has a CD-R on it > using the ultra connector. I don't know what's causing those messages. I don't get them on my Tyan S1836DLUAN motherboard. My kernel and my CAM version are about 5 weeks old, though. Also, I'm running -current and not -stable. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 16 21:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13779 for freebsd-stable-outgoing; Sun, 16 Aug 1998 21:46:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mbox.ualr.edu (mbox.ualr.edu [144.167.10.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13770 for ; Sun, 16 Aug 1998 21:46:17 -0700 (PDT) (envelope-from jeroyce@athena.ualr.edu) Received: from athena.ualr.edu by UALR.EDU (PMDF V4.2-11 #15587) id <01J0OU3Y00O00069DW@UALR.EDU>; Sun, 16 Aug 1998 23:45:42 CDT Received: from athena.ualr.edu ([144.167.7.48]) by athena.ualr.edu with ESMTP for stable@FreeBSD.ORG; Sun, 16 Aug 1998 23:45:41 -0500 Date: Sun, 16 Aug 1998 23:44:07 -0500 From: Joe Subject: Re: Xwin wont do SVGA To: "stable@FreeBSD.ORG" Message-id: <35D7B517.42628468@athena.ualr.edu> X-Envelope-to: stable@FreeBSD.ORG MIME-version: 1.0 X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.35 i686) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit References: <3.0.5.32.19980816200116.008175a0@ieng9.ucsd.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeff W. wrote: > First of all, I couldn't find my video card in the list, which I guess > doesn't matter, but it's a diamond Fire GL 1000 Pro. So, I installed the > generic SVGA and the VGA16 driver. The problem is that when I run > XF86Setup, even if I tell X to use the SVGA server, and even if I mess with > the different monitor types (I've tried all of them), X only runs in a > really low resolution. Hardly any of the windows that pop up fit on the > screen. So, my question is how do I get it to run in just a plain SVGA > mode???? Do I have to install something else??? > --Jeff W. > SuSE has their own xserver driver for the Fire GL 1000 Pro. I don't know if it works for FreeBSD, however. Their website is: http://www.suse.de/XSuSE/XSuSE_E.html -- There are no secret messages in this signature file. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 17 11:01:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11630 for freebsd-stable-outgoing; Mon, 17 Aug 1998 11:01:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from stl-system-5.stl-group.com ([206.243.183.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11613 for ; Mon, 17 Aug 1998 11:00:55 -0700 (PDT) (envelope-from j.baggen@stl-group.com) From: j.baggen@stl-group.com Received: from stl-sys-6 (stl-group.xs4all.nl [194.109.83.251]) by stl-system-5.stl-group.com (8.8.7/8.8.7) with SMTP id SAA17172 for ; Mon, 17 Aug 1998 18:01:10 GMT (envelope-from j.baggen@stl-group.com) Message-Id: <3.0.5.32.19980817200014.0098f250@stl-group.net> X-Sender: jbaggen@stl-group.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 17 Aug 1998 20:00:14 +0200 To: freebsd-stable@FreeBSD.ORG Subject: Instalation on wd2c, primairy IDE Controller Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When booting 2.2.6 after installation I got "panic: cannot mount root" messages. The FreeBSD FAQ (http://www.nl.freebsd.org/FAQ/FAQ44.html#44) reported this problem and provided me with a sollution: To fix the problem I should move both my disks to the primairy IDE controller, but after rebooting I still got the message. All other fixes won`t work for me, cause I can`t boot my system with FreeBSD. Are there any other sollutions to boot FreeBSD on 2th Hard Disk that I`m not aware off? _________________________________________________________ J.J.W.H. Baggen Starline Group Europe www.stl-group.com SALES DEPARTEMENT: sales@stl-group.com +31(0)455 650 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 17 12:01:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23527 for freebsd-stable-outgoing; Mon, 17 Aug 1998 12:01:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailhub.ainet.com (mailhub.ainet.com [204.30.40.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23520 for ; Mon, 17 Aug 1998 12:01:48 -0700 (PDT) (envelope-from jmscott@ainet.com) Received: from perl.ainet.com (perl.ainet.com [204.30.40.14]) by mailhub.ainet.com (8.9.1/8.9.1) with SMTP id MAA03147; Mon, 17 Aug 1998 12:01:01 -0700 (PDT) Message-Id: <3.0.5.32.19980817120222.00ab1d20@mail.ainet.com> X-Sender: jmscott@mail.ainet.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 17 Aug 1998 12:02:22 -0700 To: j.baggen@stl-group.com, freebsd-stable@FreeBSD.ORG From: "Joseph M. Scott" Subject: Re: Instalation on wd2c, primairy IDE Controller In-Reply-To: <3.0.5.32.19980817200014.0098f250@stl-group.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got this to work by editing the boot.config file ( and entering it at the boot prompt the first time it comes back up ) to something like : 1:wd(3,a)/kernel you will need to change the 3 to your corresponding drive. Joseph Scott jmscott@ainet.com At 08:00 PM 8/17/98 +0200, j.baggen@stl-group.com wrote: > >When booting 2.2.6 after installation I got "panic: cannot mount root" >messages. The FreeBSD FAQ (http://www.nl.freebsd.org/FAQ/FAQ44.html#44) >reported this problem and provided me with a sollution: To fix the >problem I should move both my disks to the primairy IDE controller, but >after rebooting I still got the message. > >All other fixes won`t work for me, cause I can`t boot my system with >FreeBSD. Are there any other sollutions to boot FreeBSD on 2th Hard >Disk that I`m not aware off? > > > > > >_________________________________________________________ >J.J.W.H. Baggen Starline Group Europe www.stl-group.com >SALES DEPARTEMENT: sales@stl-group.com +31(0)455 650 137 > > >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 Mon Aug 17 12:02:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23797 for freebsd-stable-outgoing; Mon, 17 Aug 1998 12:02:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.fcc.net (241.pearlriver.fcc.net [207.198.253.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23787 for ; Mon, 17 Aug 1998 12:02:49 -0700 (PDT) (envelope-from nathan@fcc.net) Received: from noc.fcc.net (nathan@noc.fcc.net [207.198.253.18]) by mail.fcc.net (8.9.1/8.9.1) with ESMTP id PAA09295 for ; Mon, 17 Aug 1998 15:01:40 -0400 (EDT) Received: (from nathan@localhost) by noc.fcc.net (8.9.1/8.9.1) id PAA17768 for freebsd-stable@FreeBSD.org; Mon, 17 Aug 1998 15:02:55 -0400 (EDT) Message-ID: <19980817150255.A17575@fcc.net> Date: Mon, 17 Aug 1998 15:02:55 -0400 From: Nathan Dorfman To: freebsd-stable@FreeBSD.ORG Subject: NFS problems in -stable? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In 2.2.7-R as well as 2.2.7-S built an hour or so ago, I'm having problems with nfs. The FreeBSD machine is running mountd, and exporting /usr/home; two Solaris machines are mounting this home directory. The server randomly stops responding when I try to do things such as gunzip, tar xf, and install. This seems to happen whether or not the operation spans remote/local mountpoints. As I've been told that only NFSv3 is broken, I'm running mountd -2 and have -o vers=2 on the Solaris client. The problem seems to come up mostly from the 2.5.1 machine. I haven't run into it on 2.6, but that machine hardly gets used. Does anyone know if this is some pilot error, broken solaris, or broken FreeBSD? -- Nathan Dorfman | E-mail: nathan@fcc.net Frontline Communications | Front desk: 914-623-8553: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 17 12:50:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02704 for freebsd-stable-outgoing; Mon, 17 Aug 1998 12:50:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA02625 for ; Mon, 17 Aug 1998 12:50:12 -0700 (PDT) (envelope-from vev@paprika.michvhf.com) Received: (qmail 3792 invoked by uid 1000); 17 Aug 1998 19:49:50 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.5.32.19980817200014.0098f250@stl-group.net> Date: Mon, 17 Aug 1998 15:49:50 -0400 (EDT) From: Vince Vielhaber To: j.baggen@stl-group.com Subject: RE: Instalation on wd2c, primairy IDE Controller Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Aug-98 j.baggen@stl-group.com wrote: > > When booting 2.2.6 after installation I got "panic: cannot mount root" > messages. The FreeBSD FAQ (http://www.nl.freebsd.org/FAQ/FAQ44.html#44) > reported this problem and provided me with a sollution: To fix the > problem I should move both my disks to the primairy IDE controller, but > after rebooting I still got the message. > > All other fixes won`t work for me, cause I can`t boot my system with > FreeBSD. Are there any other sollutions to boot FreeBSD on 2th Hard > Disk that I`m not aware off? > When you get the boot prompt, type 1:wd(2,a)kernel and if it boots for you add that line to /boot.config. That's for the first partition on the master disk of the secondary controller. I think 0:wd(1,a)kernel would boot the slave on the primary. With those two examples you should be able to figure out what you need if your config is different. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 17 15:46:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10850 for freebsd-stable-outgoing; Mon, 17 Aug 1998 15:46:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10840 for ; Mon, 17 Aug 1998 15:46:33 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id PAA00902 for ; Mon, 17 Aug 1998 15:45:55 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 17 Aug 1998 15:45:49 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: Increasing IP_FW_MAX_PORTS seems to fail Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In order to pass H.323 conferencing, we need to increase the number of ports explicitly called out in our ipfw configuration. Currently running -STABLE with a last CVSup of 980815. After editing /usr/src/sys/netinet/ip_fw.h to reflect the increased number of ports (16 attempted from original 10) and examining the .depend files the following were 'make; make install'-ed: /usr/src/sbin/ipfw /usr/src/lkm/ipfw (full kernel build and install) Upon reboot, ipfw does not function, with the error message: ip_fw_ctl: len=104, want 116 (somewhat confusing since ip_fw.h says: * Warning: setsockopt() will fail if sizeof(struct ip_fw) > MLEN (108) ) As a "last resort" I have also tried 'make -DNOCLEAN buildworld; make -DNOCLEAN installworld' followed by a full kernel rebuild -- with the same results. I have not yet tried a *full* make world, hoping that this can be changed without it. What am I missing? TIA, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 17 17:51:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02608 for freebsd-stable-outgoing; Mon, 17 Aug 1998 17:51:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA02598 for ; Mon, 17 Aug 1998 17:51:29 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id BAA24079; Tue, 18 Aug 1998 01:04:58 +0200 From: Luigi Rizzo Message-Id: <199808172304.BAA24079@labinfo.iet.unipi.it> Subject: Re: Increasing IP_FW_MAX_PORTS seems to fail To: Jeff@Wagsky.com (Jeff Kletsky) Date: Tue, 18 Aug 1998 01:04:58 +0200 (MET DST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: from "Jeff Kletsky" at Aug 17, 98 03:45:30 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In order to pass H.323 conferencing, we need to increase the number of > ports explicitly called out in our ipfw configuration. Currently running > -STABLE with a last CVSup of 980815. > > After editing /usr/src/sys/netinet/ip_fw.h to reflect the increased number > of ports (16 attempted from original 10) and examining the .depend files > the following were 'make; make install'-ed: not the way to go... just duplicate rules instead: ipfw add accept udp from X p1,p2,..,p9 to ... ipfw add accept udp from X p10,p11,..,p16 to ... > Upon reboot, ipfw does not function, with the error message: > > ip_fw_ctl: len=104, want 116 > > (somewhat confusing since ip_fw.h says: > * Warning: setsockopt() will fail if sizeof(struct ip_fw) > MLEN (108) are you using dummynet by chance ? This would add a field to the mbuf header and reduce the usable slace (MLEN) to 104 ... and the number of usable ports per rule with dummynet is even lower since i need more room in the firewall structs for other fields. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 17 18:03:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04204 for freebsd-stable-outgoing; Mon, 17 Aug 1998 18:03:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from nash.pr.mcs.net (nash.pr.mcs.net [204.95.47.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04193 for ; Mon, 17 Aug 1998 18:03:45 -0700 (PDT) (envelope-from alex@nash.pr.mcs.net) Received: (from alex@localhost) by nash.pr.mcs.net (8.8.8/8.8.7) id UAA29594; Mon, 17 Aug 1998 20:02:33 -0500 (CDT) (envelope-from alex) Message-ID: <19980817200233.R169@pr.mcs.net> Date: Mon, 17 Aug 1998 20:02:33 -0500 From: Alex Nash To: Jeff Kletsky , freebsd-stable@FreeBSD.ORG Subject: Re: Increasing IP_FW_MAX_PORTS seems to fail References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeff Kletsky on Mon, Aug 17, 1998 at 03:45:49PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 17, 1998 at 03:45:49PM -0700, Jeff Kletsky wrote: > After editing /usr/src/sys/netinet/ip_fw.h to reflect the increased number > of ports (16 attempted from original 10) and examining the .depend files > the following were 'make; make install'-ed: > > /usr/src/sbin/ipfw > /usr/src/lkm/ipfw > (full kernel build and install) > > Upon reboot, ipfw does not function, with the error message: > > ip_fw_ctl: len=104, want 116 > > (somewhat confusing since ip_fw.h says: > * Warning: setsockopt() will fail if sizeof(struct ip_fw) > MLEN (108) [...] > What am I missing? The ipfw binary you built includes /usr/include/netinet/ip_fw.h, I suspect your changes haven't made it there. You should probably heed the warning about setsockopt() failing for sizeof(struct ip_fw) > 108 bytes -- this restriction is removed in -current but not in -stable. Consider using multiple rules instead. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 17 19:08:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12368 for freebsd-stable-outgoing; Mon, 17 Aug 1998 19:08:16 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ariel.macarthur.uws.EDU.AU (ariel.macarthur.uws.EDU.AU [137.154.72.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12362 for ; Mon, 17 Aug 1998 19:08:12 -0700 (PDT) (envelope-from D.Lorschy@uws.edu.au) Received: from damien ([137.154.71.11]) by ariel.macarthur.uws.EDU.AU (8.8.8/8.8.8) with SMTP id MAA10620 for ; Tue, 18 Aug 1998 12:07:49 +1100 Message-ID: <000b01bdca4c$a6272370$0b479a89@damien.macarthur.uws.edu.au> Reply-To: "Damien Lorschy" From: "Damien Lorschy" To: Date: Tue, 18 Aug 1998 12:05:13 +1000 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 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 8dea4690 unsubscribe freebsd-stable D.Lorschy@uws.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 03:36:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01569 for freebsd-stable-outgoing; Tue, 18 Aug 1998 03:36:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01561 for ; Tue, 18 Aug 1998 03:36:47 -0700 (PDT) (envelope-from voland@plab.ku.dk) Received: from eagle.plab.ku.dk (eagle.plab.ku.dk [130.225.105.63]) by plab.ku.dk (8.8.8/8.8.5) with SMTP id MAA28563 for ; Tue, 18 Aug 1998 12:36:06 +0200 (CEST) Message-Id: <199808181036.MAA28563@plab.ku.dk> From: "Vadim Belman" To: "freebsd-stable@FreeBSD.ORG" Date: Tue, 18 Aug 1998 12:37:02 +0100 Reply-To: "Vadim Belman" X-Mailer: PMMail 1.96a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Subject: Intel EtherExpress Pro 10/100B network collisions Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, after having heard so many positive opinions about the network card in , we decided to give it a try on our new FreeBSD 2.2.7 machine (previously we used 3COM 905 TP for all of ours FreeBSD boxes). Surprisingly, we found that Intel board produces a _huge_ number of network collisions, almost for every output packet. The strange thing is that we anyhow had a terrific transfer rate - absolutely the same as with 3COMs (~920 Kb/s on a 10 mbps connection). It is definitely a problem with the card, for we have also tried 3COM on the same machine, with predictable zero number of collisions. There is quite likely that this is not a problem with a particular Intel card, for we have also tried another one --- with the same bad results. We have 3COM switches installed in our location. Did anyone experience the same or similar problem with cards in question? We'd appreciate any help; we think the results we obtained are kind of strange. Thank you in advance, Vadim. ---- /Voland FIDO: 2:464/15@fidonet, Vadim Belman e-mail: voland@plab.ku.dk WWW: http://www.plab.ku.dk/voland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 03:45:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02210 for freebsd-stable-outgoing; Tue, 18 Aug 1998 03:45:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02198 for ; Tue, 18 Aug 1998 03:45:10 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id MAA10981; Tue, 18 Aug 1998 12:44:33 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <35D95B0F.137593BC@partitur.se> Date: Tue, 18 Aug 1998 12:44:31 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5b1 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: sv,en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: MAKEDEV: arith: syntax error: "" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! What's this? sh -v MAKEDEV ... # Control bit for SCSI scsictl=$((1 << 29)) MAKEDEV: arith: syntax error: "" uname -a reveals: FreeBSD trumpet.partitur.se 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Mon Jul 27 16:37:05 CEST 1998 girgen@trumpet.partitur.se:/usr/src/sys/compile/TRUMPET i386 I see on most of our machines. The MAKEDEV script is fresh and doesn't diff from the just now cvsupped src tree. /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 04:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07447 for freebsd-stable-outgoing; Tue, 18 Aug 1998 04:28:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA07438 for ; Tue, 18 Aug 1998 04:28:10 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id HLTMAJHJ; Tue, 18 Aug 98 11:27:34 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19980818132451.00922100@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 18 Aug 1998 13:24:51 +0200 To: Palle Girgensohn From: Marius Bendiksen Subject: Re: MAKEDEV: arith: syntax error: "" Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <35D95B0F.137593BC@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >MAKEDEV: arith: syntax error: "" I also see this, with FreeBSD cvsupped yesterday from the .no mirror. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 05:11:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11720 for freebsd-stable-outgoing; Tue, 18 Aug 1998 05:11:40 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tetragr.zaporizhzhe.ua (news.tetragr.zaporizhzhe.ua [194.44.20.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11709 for ; Tue, 18 Aug 1998 05:11:25 -0700 (PDT) (envelope-from oleg@www.reis.zp.ua) Received: from www.tetragr.zaporizhzhe.ua (oleg@www.tetragr.zaporizhzhe.ua [194.44.20.6]) by tetragr.zaporizhzhe.ua (8.8.8/Relcom-2A/nov1) with ESMTP id PAA01382 ;Tue, 18 Aug 1998 15:07:44 +0300 (EEST) Received: (from oleg@localhost) by www.reis.zp.ua (8.8.8/Relcom-2A/nov0.7) id PAA04914 ;Tue, 18 Aug 1998 15:07:43 +0300 (EEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.5.32.19980818132451.00922100@mail.scancall.no> Date: Tue, 18 Aug 1998 15:07:43 +0300 (EEST) Organization: ReIS Ltd. From: "Oleg V. Naumann" To: Marius Bendiksen Subject: Re: MAKEDEV: arith: syntax error: "" Cc: freebsd-stable@FreeBSD.ORG, Palle Girgensohn Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Aug-98 Marius Bendiksen wrote: >>MAKEDEV: arith: syntax error: "" > > I also see this, with FreeBSD cvsupped yesterday from the .no mirror. What's about sh ./MAKEDEV all ? > > --- > Marius Bendiksen, IT-Trainee, ScanCall AS > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Oleg V. Naumann tetragr.zaporizhzhe.ua/reis.zp.ua postmaster To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 06:14:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17718 for freebsd-stable-outgoing; Tue, 18 Aug 1998 06:14:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17713 for ; Tue, 18 Aug 1998 06:14:02 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id PAA12108; Tue, 18 Aug 1998 15:13:24 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <35D97DF2.62D6595D@partitur.se> Date: Tue, 18 Aug 1998 15:13:22 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5b1 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: sv,en MIME-Version: 1.0 To: Marius Bendiksen CC: freebsd-stable@FreeBSD.ORG Subject: Re: MAKEDEV: arith: syntax error: "" References: <3.0.5.32.19980818132451.00922100@mail.scancall.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marius Bendiksen wrote: > > >MAKEDEV: arith: syntax error: "" > > I also see this, with FreeBSD cvsupped yesterday from the .no mirror. > > --- > Marius Bendiksen, IT-Trainee, ScanCall AS I've seen it for the entire summer, to be honest. And I also use the .no mirror. Just grabbed it from another mirror, just in case, but it's the same thing. /palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 08:46:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07434 for freebsd-stable-outgoing; Tue, 18 Aug 1998 08:46:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07426 for ; Tue, 18 Aug 1998 08:46:23 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from skejdbrimir.ifi.uio.no (skejdbrimir.ifi.uio.no [129.240.65.2]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id RAA12157; Tue, 18 Aug 1998 17:45:45 +0200 (MET DST) Received: from localhost (dag-erli@localhost) by skejdbrimir.ifi.uio.no ; Tue, 18 Aug 1998 15:45:44 GMT Mime-Version: 1.0 To: "Vadim Belman" Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Intel EtherExpress Pro 10/100B network collisions References: <199808181036.MAA28563@plab.ku.dk> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 18 Aug 1998 15:45:42 +0000 In-Reply-To: "Vadim Belman"'s message of "Tue, 18 Aug 1998 12:37:02 +0100" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA07430 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Vadim Belman" writes: > (~920 Kb/s on a 10 mbps connection). *groan* "920 Kelvin-bits per second on a 10 millibit per second connection". When will people learn to use units and SI prefixes properly? DES (just my daily rant) -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 09:10:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10094 for freebsd-stable-outgoing; Tue, 18 Aug 1998 09:10:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from jane.lfn.org (www.neworleansonline.com [209.16.92.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA09582 for ; Tue, 18 Aug 1998 09:06:52 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 14127 invoked by uid 100); 18 Aug 1998 16:05:47 -0000 Date: Tue, 18 Aug 1998 11:05:47 -0500 (CDT) From: Craig Johnston To: freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: panic in -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a stable kernel, cvsupped a couple of days ago. The system is a K6-133 on an ASUS HX mobo, with an NCR53c810 and an IBM DCAS-32160 drive. It seems that /usr/bin/install is the only program that causes this to happen. It causes a panic pretty regularly. (preventing me from doing a 'make installworld' and bringing the binaries up to date.) Otherwise, the machine has long uptimes serving out ethertalk for a bunch of macs. Here's the error I got yesterday: Data buffered space not in kernel context sd0: oops not queued panic: biodone: buffer not busy I can provide more info, but I was hoping this was something that has been seen before. I have enabled all the debugging I could find, and will no doubt have more to report presently. I have 'FAILSAFE' defined in the kernel config file. I'll probably poke around in the kernel later today, and look at /usr/bin/install to see if I can figure out why it might be exercising this. Any ideas before I do? thanks, -Craig PS -- please advise if I should have targetted different lists. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 09:17:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11127 for freebsd-stable-outgoing; Tue, 18 Aug 1998 09:17:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10077 for ; Tue, 18 Aug 1998 09:10:32 -0700 (PDT) (envelope-from ekagarc@kkeka.ericsson.se) Received: from kkdus8.kkeka.ericsson.se (kkdus8.kkeka.ericsson.se [130.100.159.107]) by penguin.wise.edt.ericsson.se (8.9.0/8.9.0/glacier-1.11) with ESMTP id SAA26350 for ; Tue, 18 Aug 1998 18:09:28 +0200 (MET DST) Received: from kkeka.ericsson.se (kkdus7.kkeka.ericsson.se [130.100.158.73]) by kkdus8.kkeka.ericsson.se (8.8.8/8.8.8) with ESMTP id SAA03905 for ; Tue, 18 Aug 1998 18:09:26 +0200 (MET DST) Message-ID: <35D9A735.F7A44416@kkeka.ericsson.se> Date: Tue, 18 Aug 1998 18:09:26 +0200 From: Felipe Garcia Organization: Ericsson Conentents AB Energy Systems Devision X-Mailer: Mozilla 4.05 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: 3COM ethernet cards 3c905b-tx Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something I found in solaris x86 release notes that may be of interess when thinking about 100Mb NICs -------------------------------------------------------------------------------------- 100-Mbps Ethernet Performance Problem on Some Intel Motherboard Chipsets Some PCI motherboards contain DMA chipsets that are unable to support 100-Mbps Fast Ethernet. Because of this problem, the Solaris operating environment does not support 100-Mbps PCI network operation on systems containing the slow chipsets. This problem affects PCI cards only. Other buses are not affected. The following chipsets are known to exhibit this problem:  82430LX (Mercury)  82450GX (Orion) (A and B steppings only) The following chipsets do not exhibit this problem:  82430NX (Neptune)  82430FX (Triton)  82430HX (Triton II)  82440FX (Natoma)  82450GX (Orion) (C0 stepping and later) Some slow PCI motherboard chipsets do not support long data burst DMA transfers and are unable to transfer data from PCI cards to system memory sufficiently fast to sustain 100-Mbps throughput. When systems with these chipsets are connected to a 100-Mbps network, data can arrive at a PCI Ethernet card faster than DMA can transfer it from the card to system memory. When this happens, the card?s FIFO begins to fill. If this condition persists long enough, the card?s FIFO will over ow, causing loss of incoming network data. When incoming data is lost, higher-level protocols such as TCP or NFS TM will time out and retransmit the lost data. These protocols ensure that all data is transferred, but performance is lowered. If only a few packets are lost, the performance impact may be small or moderate, but if many packets are lost, a very substantial and severe performance loss can arise. In some cases, a drop in network FTP performance of two orders of magnitude has been seen when using such chipsets, rendering the network unusable. This case occurs when using 100-Mbps cards containing relatively small FIFOs. The cards are designed to be able to hold only a couple of packets, and they depend on the DMA mechanism to transfer data out of the FIFO in a timely way. In other cases, cards with larger FIFOs are not as severely impacted by the problem, and under normal conditions perform as well on machines with slow chipsets as they do on speedy ones. However, under sustained 100-Mbps operation, this cannot continue indefinitely. Because of this problem, the Solaris environment does not support 100-Mbps PCI network operation on systems containing the slow chipsets. In particular, the PCI cards supported by the dnet, iprb, and elx drivers will not provide good performance on machines with the problem chipsets. If 100-Mbps operation is required on such a machine, it is best to use a non-PCI Ethernet controller. It is also possible that the PCI cards supported by the ieef driver, which have larger FIFOs, may function adequately. You must decide whether the performance on a particular machine is adequate for the intended purpose. -- =--------=/////////////////\\\\\\\\\\\\\\\\\\\\=--------= ((___)) | Felipe Garcia | ((___)) [ x x ] | ekagarc@kkeka.ericsson.se | [ x x ] \ / =\\\\\\\\\\\\\\\\\////////////////////= \ / (' ') | | (' ') (U) | Live UNIX or DIE | (U) =--------=-------------------------------------=--------= Definition of Win 95 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 09:38:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13878 for freebsd-stable-outgoing; Tue, 18 Aug 1998 09:38:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13871 for ; Tue, 18 Aug 1998 09:38:15 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id LAA07347; Tue, 18 Aug 1998 11:37:37 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 18 Aug 1998 11:37:36 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us Reply-To: Chris Dillon To: Vadim Belman cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Intel EtherExpress Pro 10/100B network collisions In-Reply-To: <199808181036.MAA28563@plab.ku.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Aug 1998, Vadim Belman wrote: > Hello, > > after having heard so many positive opinions about the > network card in , we decided to give it a try on > our new FreeBSD 2.2.7 machine (previously we used > 3COM 905 TP for all of ours FreeBSD boxes). > > Surprisingly, we found that Intel board produces a _huge_ > number of network collisions, almost for every output > packet. > > The strange thing is that we anyhow had a terrific > transfer rate - absolutely the same as with 3COMs > (~920 Kb/s on a 10 mbps connection). > > It is definitely a problem with the card, for we have also > tried 3COM on the same machine, with predictable zero number > of collisions. There is quite likely that this is not a problem > with a particular Intel card, for we have also tried another one > --- with the same bad results. > > We have 3COM switches installed in our location. > > Did anyone experience the same or similar problem with > cards in question? > > We'd appreciate any help; we think the results we obtained > are kind of strange. I set up a small network for someone using a P5-200 with a EtherExpress Pro 100/B running a 2.2.5-STABLE copy of FreeBSD (just before 2.2.6 came out, actually) and Samba for SMB filesharing. The hub I used was a small 16-port 10BaseT Netgear job (I hear good things about NetGear.. don't know if they're true or not). My situation is still to this day worse than what you are experiencing. Luckily the load is rather low so the person doesn't care or even notice, but I still want to eventually resolve this. The three clients are running Win95 OSR2.1 with 3COM 3c509s (EtherLink III). Upon transferring any data between the server and the Win95 boxen, there is an interesting collision phenomena. According to netstat, the amount of collisions vs. data flow seem to follow an almost half-duty-cycle sawtooth waveform pattern (you electronics nuts will know what I'm talking about). Actual data transfer rates start out high, and collisions begin to inch up until the collision rate is so high that absolutely no data passes, and then the collision rate suddenly drops to zero and data starts going full-speed again. The cycles continue and each cycle lasts approximately 4 or 5 seconds. The cabling appears to be fine and the same situation occurs even if I remove all nodes from the network except the ones under test, and I have tested each client with the same results. If you ever figure out what is going on or if anyone else could shed light on this I'd also be grateful. :-) P.S. I always figured it was just because FreeBSD was too damn fast for those poor Windows clients and they couldn't choke the data down fast enough. ;-> -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 10:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18898 for freebsd-stable-outgoing; Tue, 18 Aug 1998 10:11:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18890 for ; Tue, 18 Aug 1998 10:11:13 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z8pHE-0000dq-00; Tue, 18 Aug 1998 10:10:32 -0700 Date: Tue, 18 Aug 1998 10:10:30 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Vadim Belman cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Intel EtherExpress Pro 10/100B network collisions In-Reply-To: <199808181036.MAA28563@plab.ku.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Aug 1998, Vadim Belman wrote: ... > Surprisingly, we found that Intel board produces a _huge_ > number of network collisions, almost for every output > packet. ... > We have 3COM switches installed in our location. > > Did anyone experience the same or similar problem with > cards in question? Yes, this will hapen if the card isn't configured with the same duplex mode as the switch port it is plugged in. You might just need to do a "ifconfig fxp0 mediaopt full-duplex" Also, some 3COM switches have some propietary flow options that are only supported by 3COM cards. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 10:27:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21637 for freebsd-stable-outgoing; Tue, 18 Aug 1998 10:27:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wraith.psc.edu (wraith.psc.edu [128.182.61.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21626 for ; Tue, 18 Aug 1998 10:27:09 -0700 (PDT) (envelope-from akadams@wraith.psc.edu) Received: from localhost (localhost [[UNIX: localhost]]) by wraith.psc.edu (8.8.8/8.8.8) with SMTP id NAA17881; Tue, 18 Aug 1998 13:26:22 -0400 (EDT) Message-Id: <199808181726.NAA17881@wraith.psc.edu> X-Authentication-Warning: wraith.psc.edu: localhost [[UNIX: localhost]] didn't use HELO protocol X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-stable@FreeBSD.ORG cc: akadams@wraith.psc.edu Subject: poll()... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Aug 1998 13:26:22 -0400 From: "Andrew K. Adams" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does any version of FreeBSD have poll() or another similar function that can be used in place of select()? Thanks, Andrew -- Andrew K. Adams National Laboratory of Applied Network Research: National Center for Network Engineering Pittsburgh Supercomputing Center Office: 218-C Mellon Institute Carnegie Mellon University Phone: (412) 268-5142 4000 Fifth Ave. Fax: (412) 268-8200 Pittsburgh, PA 15213 WWW: http://www.psc.edu/~akadams/ D3 FA 7D 61 FD ED BD D9 0C DE 94 DB 0F 25 D0 2E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 12:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09889 for freebsd-stable-outgoing; Tue, 18 Aug 1998 12:17:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09882 for ; Tue, 18 Aug 1998 12:17:57 -0700 (PDT) (envelope-from djflow@erols.com) Received: from portbus1.tc.cc.va.us (portbus1.tc.cc.va.us [164.106.211.24]) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id PAA26813; Tue, 18 Aug 1998 15:11:22 -0400 (EDT) Message-Id: <199808181911.PAA26813@portwwwbus.tc.cc.va.us> X-Sender: djflow@portwwwbus.tc.cc.va.us X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 18 Aug 1998 15:17:51 -0400 To: freebsd-stable@FreeBSD.ORG From: Derek Flowers Subject: Re: Intel EtherExpress Pro 10/100B network collisions Cc: Tom , Vadim Belman In-Reply-To: References: <199808181036.MAA28563@plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:10 AM 8/18/98 -0700, you wrote: > >On Tue, 18 Aug 1998, Vadim Belman wrote: > >... >> Surprisingly, we found that Intel board produces a _huge_ >> number of network collisions, almost for every output >> packet. >... >> We have 3COM switches installed in our location. >> >> Did anyone experience the same or similar problem with >> cards in question? This may or may not apply here but is worth looking at: High Rate of Collisions on 100-MB Networks http://support.microsoft.com/support/kb/articles/q169/7/89.asp I know it is for Windows, but if the hardware is configured the same way, the same problem could occur. -Derek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 12:44:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14810 for freebsd-stable-outgoing; Tue, 18 Aug 1998 12:44:49 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from caffeine.internal.enteract.com (caffeine.internal.enteract.com [207.229.129.24]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA14803 for ; Tue, 18 Aug 1998 12:44:44 -0700 (PDT) (envelope-from kdulzo@caffeine.internal.enteract.com) Received: (qmail 11947 invoked by uid 100); 18 Aug 1998 19:44:08 -0000 Message-ID: <19980818144408.A11916@caffeine.internal.enteract.com> Date: Tue, 18 Aug 1998 14:44:08 -0500 From: "Kevin M. Dulzo" To: freebsd-stable@FreeBSD.ORG Subject: Re: MAKEDEV: arith: syntax error: "" Reply-To: kdulzo@enteract.com References: <3.0.5.32.19980818132451.00922100@mail.scancall.no> <35D97DF2.62D6595D@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <35D97DF2.62D6595D@partitur.se>; from Palle Girgensohn on Tue, Aug 18, 1998 at 03:13:22PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had these problems on 2.2.7 from the day it was released. I'll bet you all have CFLAGS in make.conf set to -O2 or -O3... The fix, drop the optimization to -O, at least for sh. I don't know why, noone had an answer to this for me either. make world worked -O2 before, and -O3 broke on groff; now -O3 compiles, but sh is broken :) -- .-._.-. To see a thing uncolored by one's own personal preferences and desires is to see it in its own pristine simplicity. ._.-._. +==-- | Kevin M. Dulzo Check us out! | | Network Operations http://www.enteract.com | | Enteract, L.L.C. mailto: info@enteract.com| | kdulzo@enteract.com (773)248-8511 | --==+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 12:48:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15785 for freebsd-stable-outgoing; Tue, 18 Aug 1998 12:48:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15757 for ; Tue, 18 Aug 1998 12:48:47 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id TAA16941; Tue, 18 Aug 1998 19:46:47 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA22345; Tue, 18 Aug 1998 21:46:46 +0200 (MET DST) Message-ID: <19980818214641.04355@follo.net> Date: Tue, 18 Aug 1998 21:46:41 +0200 From: Eivind Eklund To: "Andrew K. Adams" , freebsd-stable@FreeBSD.ORG Subject: Re: poll()... References: <199808181726.NAA17881@wraith.psc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199808181726.NAA17881@wraith.psc.edu>; from Andrew K. Adams on Tue, Aug 18, 1998 at 01:26:22PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 18, 1998 at 01:26:22PM -0400, Andrew K. Adams wrote: > > Does any version of FreeBSD have poll() or another similar function that > can be used in place of select()? Yes - -current does. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 16:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25174 for freebsd-stable-outgoing; Tue, 18 Aug 1998 16:17:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25166; Tue, 18 Aug 1998 16:17:51 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA08091; Wed, 19 Aug 1998 09:17:08 +1000 Date: Wed, 19 Aug 1998 09:17:08 +1000 From: Bruce Evans Message-Id: <199808182317.JAA08091@godzilla.zeta.org.au> To: caj@lfn.org, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: panic in -stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'll probably poke around in the kernel later today, and look at >/usr/bin/install to see if I can figure out why it might be exercising >this. /usr/bin/install exercises mmap() a lot. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 16:53:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01365 for freebsd-stable-outgoing; Tue, 18 Aug 1998 16:53:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d4.dialup.hilink.com.au [203.2.144.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01347 for ; Tue, 18 Aug 1998 16:53:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00856; Tue, 18 Aug 1998 16:51:46 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808181651.QAA00856@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: kdulzo@enteract.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: MAKEDEV: arith: syntax error: "" In-reply-to: Your message of "Tue, 18 Aug 1998 14:44:08 EST." <19980818144408.A11916@caffeine.internal.enteract.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Aug 1998 16:51:44 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I had these problems on 2.2.7 from the day it was released. > I'll bet you all have CFLAGS in make.conf set to -O2 or -O3... > The fix, drop the optimization to -O, at least for sh. I don't > know why, noone had an answer to this for me either. make world worked > -O2 before, and -O3 broke on groff; now -O3 compiles, but sh is broken :) Optimiser settings above -O have been known to be broken for literally years. Don't use them. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 17:20:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07136 for freebsd-stable-outgoing; Tue, 18 Aug 1998 17:20:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07124 for ; Tue, 18 Aug 1998 17:20:02 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id TAA08748; Tue, 18 Aug 1998 19:19:18 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 18 Aug 1998 19:19:18 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Tom cc: Vadim Belman , "freebsd-stable@FreeBSD.ORG" Subject: Re: Intel EtherExpress Pro 10/100B network collisions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Aug 1998, Tom wrote: > > On Tue, 18 Aug 1998, Vadim Belman wrote: > > ... > > Surprisingly, we found that Intel board produces a _huge_ > > number of network collisions, almost for every output > > packet. > ... > > We have 3COM switches installed in our location. > > > > Did anyone experience the same or similar problem with > > cards in question? > > Yes, this will hapen if the card isn't configured with the same duplex > mode as the switch port it is plugged in. You might just need to do a > "ifconfig fxp0 mediaopt full-duplex" > > Also, some 3COM switches have some propietary flow options that are only > supported by 3COM cards. You may have just solved the same problem (well, actually worse than the above) that I have been having. I don't have the card connected to a switch (or any switches on the network at all for that matter) but I will force the card to do half-duplex and see what happens. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 17:20:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07255 for freebsd-stable-outgoing; Tue, 18 Aug 1998 17:20:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07250 for ; Tue, 18 Aug 1998 17:20:43 -0700 (PDT) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.1/8.9.0) id TAA00653; Tue, 18 Aug 1998 19:20:01 -0500 (CDT) To: Tom Cc: Vadim Belman , "freebsd-stable@FreeBSD.ORG" Subject: Re: Intel EtherExpress Pro 10/100B network collisions References: From: stephen farrell Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 18 Aug 1998 19:20:01 -0500 In-Reply-To: Tom's message of "Tue, 18 Aug 1998 10:10:30 -0700 (PDT)" Message-ID: <87af51bz66.fsf@couatl.uchicago.edu> Lines: 29 X-Mailer: Gnus v5.6.22/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom writes: > On Tue, 18 Aug 1998, Vadim Belman wrote: > > ... > > Surprisingly, we found that Intel board produces a _huge_ > > number of network collisions, almost for every output > > packet. > ... > > We have 3COM switches installed in our location. > > > > Did anyone experience the same or similar problem with > > cards in question? > > Yes, this will hapen if the card isn't configured with the same duplex > mode as the switch port it is plugged in. You might just need to do a > "ifconfig fxp0 mediaopt full-duplex" Note that full-duplex can also SLOW your network down. I don't understand this, and am too looking for answers. However, I switched a 100+ to full-duplex and went from 10Mbps -> 10bps transfer rates to a sparc/sol2.5 box on 10baseT LAN (though connections off the LAN were normal). Clearly some care needs to be taken in how to configure this card. -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 17:22:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07553 for freebsd-stable-outgoing; Tue, 18 Aug 1998 17:22:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07451; Tue, 18 Aug 1998 17:22:05 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199808190022.RAA07451@hub.freebsd.org> Subject: Re: your mail In-Reply-To: <199808150736.AAA15377@tantivy.stanford.edu> from Bob Vaughan at "Aug 15, 98 00:36:45 am" To: techie@tantivy.stanford.edu (Bob Vaughan) Date: Tue, 18 Aug 1998 17:22:03 -0700 (PDT) Cc: billf@chc-chimes.com, timsarver@netdirect.net, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Vaughan wrote: > more to the point, why isn't majordomo@freebsd.org configured to catch > administrative crap?? it isn't hard.. > because it catches too much. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 17:37:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10634 for freebsd-stable-outgoing; Tue, 18 Aug 1998 17:37:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA10607 for ; Tue, 18 Aug 1998 17:37:02 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z8wEd-000146-00; Tue, 18 Aug 1998 17:36:19 -0700 Date: Tue, 18 Aug 1998 17:36:16 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: stephen farrell cc: Vadim Belman , "freebsd-stable@FreeBSD.ORG" Subject: Re: Intel EtherExpress Pro 10/100B network collisions In-Reply-To: <87af51bz66.fsf@couatl.uchicago.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Aug 1998, stephen farrell wrote: > Tom writes: > > > On Tue, 18 Aug 1998, Vadim Belman wrote: > > > > ... > > > Surprisingly, we found that Intel board produces a _huge_ > > > number of network collisions, almost for every output > > > packet. > > ... > > > We have 3COM switches installed in our location. > > > > > > Did anyone experience the same or similar problem with > > > cards in question? > > > > Yes, this will hapen if the card isn't configured with the same duplex > > mode as the switch port it is plugged in. You might just need to do a > > "ifconfig fxp0 mediaopt full-duplex" > > Note that full-duplex can also SLOW your network down. I don't Yes, this setting must match the setting on your port on your switch. If you don't have a switch, it MUST be set to half-duplex. > understand this, and am too looking for answers. However, I switched > a 100+ to full-duplex and went from 10Mbps -> 10bps transfer rates to > a sparc/sol2.5 box on 10baseT LAN (though connections off the LAN were > normal). Clearly some care needs to be taken in how to configure this > card. You probably have your card connected to a hub. This means that you MUST use half-duplex. > -- > > Steve Farrell Tom Systems Support Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 17:51:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13958 for freebsd-stable-outgoing; Tue, 18 Aug 1998 17:51:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13942 for ; Tue, 18 Aug 1998 17:51:25 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id UAA22734; Tue, 18 Aug 1998 20:50:28 -0400 (EDT) (envelope-from gjp@gjp.erols.com) To: stephen farrell cc: Tom , Vadim Belman , "freebsd-stable@FreeBSD.ORG" From: "Gary Palmer" Subject: Re: Intel EtherExpress Pro 10/100B network collisions In-reply-to: Your message of "18 Aug 1998 19:20:01 CDT." <87af51bz66.fsf@couatl.uchicago.edu> Date: Tue, 18 Aug 1998 20:50:27 -0400 Message-ID: <22730.903487827@gjp.erols.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG stephen farrell wrote in message ID <87af51bz66.fsf@couatl.uchicago.edu>: > Note that full-duplex can also SLOW your network down. I don't > understand this, and am too looking for answers. However, I switched > a 100+ to full-duplex and went from 10Mbps -> 10bps transfer rates to > a sparc/sol2.5 box on 10baseT LAN (though connections off the LAN were > normal). Clearly some care needs to be taken in how to configure this > card. This normally only happens on poor (read: cheap, low quality) switches. In tests here, full duplex operation doesn't decrease performance. We use Catalyst and `Extreme' 100bTX switches. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 18:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22658 for freebsd-stable-outgoing; Tue, 18 Aug 1998 18:46:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22648 for ; Tue, 18 Aug 1998 18:46:47 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id SAA02887; Tue, 18 Aug 1998 18:45:02 -0700 (MST) From: "Chad R. Larson" Message-Id: <199808190145.SAA02887@freebie.dcfinc.com> Subject: Re: MAKEDEV: arith: syntax error: "" To: mike@smith.net.au (Mike Smith) Date: Tue, 18 Aug 1998 18:45:02 -0700 (MST) Cc: kdulzo@enteract.com, freebsd-stable@FreeBSD.ORG In-Reply-To: <199808181651.QAA00856@dingo.cdrom.com> from Mike Smith at "Aug 18, 98 04:51:44 pm" Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The fix, drop the optimization to -O, at least for sh. I don't > > know why, noone had an answer to this for me either. make world worked > > -O2 before, and -O3 broke on groff; now -O3 compiles, but sh is broken :) > > Optimiser settings above -O have been known to be broken for literally > years. Don't use them. How about someone fixes the compiler, then? -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 18:54:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23993 for freebsd-stable-outgoing; Tue, 18 Aug 1998 18:54:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23972 for ; Tue, 18 Aug 1998 18:54:26 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA18742; Tue, 18 Aug 1998 18:50:57 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: chad@dcfinc.com cc: mike@smith.net.au (Mike Smith), kdulzo@enteract.com, freebsd-stable@FreeBSD.ORG Subject: Re: MAKEDEV: arith: syntax error: "" In-reply-to: Your message of "Tue, 18 Aug 1998 18:45:02 PDT." <199808190145.SAA02887@freebie.dcfinc.com> Date: Tue, 18 Aug 1998 18:50:56 -0700 Message-ID: <18738.903491456@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How about someone fixes the compiler, then? Sounds good to me - I didn't see your diffs attached though. Perhaps your mailer dropped them? Please re-send. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 19:34:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29316 for freebsd-stable-outgoing; Tue, 18 Aug 1998 19:34:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com ([203.8.14.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29306 for ; Tue, 18 Aug 1998 19:34:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.hilink.com.au [127.0.0.1] (may be forged)) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA01909; Tue, 18 Aug 1998 19:31:22 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808181931.TAA01909@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: chad@dcfinc.com cc: mike@smith.net.au (Mike Smith), kdulzo@enteract.com, freebsd-stable@FreeBSD.ORG Subject: Re: MAKEDEV: arith: syntax error: "" In-reply-to: Your message of "Tue, 18 Aug 1998 18:45:02 MST." <199808190145.SAA02887@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Aug 1998 19:31:22 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The fix, drop the optimization to -O, at least for sh. I don't > > > know why, noone had an answer to this for me either. make world worked > > > -O2 before, and -O3 broke on groff; now -O3 compiles, but sh is broken :) > > > > Optimiser settings above -O have been known to be broken for literally > > years. Don't use them. > > How about someone fixes the compiler, then? Go for it. See 'egcs' and 'gcc-2.8' for some examples of how easy it might be. Seriously; we don't maintain gcc. Feel free to pester the maintainers about this. Meanwhile, simply be advised that optimiser levels above -O are known to cause problems, and don't yield any significant performance benefits. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 19:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02238 for freebsd-stable-outgoing; Tue, 18 Aug 1998 19:48:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02147 for ; Tue, 18 Aug 1998 19:48:00 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt2-160.HiWAAY.net [208.147.148.160]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id VAA24081; Tue, 18 Aug 1998 21:47:21 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id VAA06742; Tue, 18 Aug 1998 21:47:19 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199808190247.VAA06742@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Vadim Belman" cc: "freebsd-stable@FreeBSD.ORG" From: David Kelly Subject: Re: Intel EtherExpress Pro 10/100B network collisions In-reply-to: Message from "Vadim Belman" of "Tue, 18 Aug 1998 12:37:02 BST." <199808181036.MAA28563@plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Aug 1998 21:47:19 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Vadim Belman" writes: > > Surprisingly, we found that Intel board produces a _huge_ > number of network collisions, almost for every output > packet. > > The strange thing is that we anyhow had a terrific > transfer rate - absolutely the same as with 3COMs > (~920 Kb/s on a 10 mbps connection). > > It is definitely a problem with the card, for we have also > tried 3COM on the same machine, with predictable zero number > of collisions. There is quite likely that this is not a problem > with a particular Intel card, for we have also tried another one > --- with the same bad results. I bet the vx0 driver lies about collisions. I forget what 10/100 3Com PCI card I have in my FreeBSD box at work but it *never* reports collisions on the 10baseT network its connected to. OTOH the collision LED lights solid on my little office hub when the SGI O2 and FreeBSD box start pushing files back and forth. Bob Metcalf, inventor of ethernet, has stated publicly something to the effect that his greatest regret about ethernet was naming a particular event, "collision". The truth is until your collision rate gets above 100% into the 200% range, you don't have a problem. There was a very nice article in SGI's Pipeline in recent months covering ethernet "collisions" and documenting the math behind a collision's effect on thruput. I can't find the article online tonight. Must be holding my tongue wrong or something. Seems like 100% collision rate results in an 8% hit on network thruput. This is because a "collision" occurs early, something like within the first 80 bytes of a packet frame. So the collision doesn't consume much bandwidth. The Thing To Worry About are "late collisions". Late collisions are due to broken network stacks, hardware, or networks which have been extended beyond the lengths permitted in the ethernet spec. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 20:38:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09410 for freebsd-stable-outgoing; Tue, 18 Aug 1998 20:38:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rachel (mail.glenatl.glenayre.com [157.230.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA09402 for ; Tue, 18 Aug 1998 20:38:49 -0700 (PDT) (envelope-from jhicks@glenatl.glenayre.com) Received: from jhicks.glenatl.glenayre.com by rachel (SMI-8.6/SMI-SVR4) id XAA05223; Tue, 18 Aug 1998 23:31:25 -0400 Received: from jhicks.glenatl.glenayre.com (localhost.glenatl.glenayre.com [127.0.0.1]) by jhicks.glenatl.glenayre.com (8.8.8/8.8.5) with ESMTP id XAA02689 for ; Tue, 18 Aug 1998 23:31:22 -0400 (EDT) Message-Id: <199808190331.XAA02689@jhicks.glenatl.glenayre.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: MAKEDEV: arith: syntax error: "" In-reply-to: Your message of "Tue, 18 Aug 1998 19:31:22 -0000." <199808181931.TAA01909@dingo.cdrom.com> Date: Tue, 18 Aug 1998 23:31:22 -0400 From: Jerry Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Meanwhile, simply be advised that optimiser levels above -O > are known to cause problems, and don't yield any significant performance > benefits. I've seen this come up many times... Does it make sense to whack the options parsed from argv to force -O as long as we're using 2.7.x? Cheers, Jerry Hicks jhicks@glenatl.glenayre.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 21:19:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15171 for freebsd-stable-outgoing; Tue, 18 Aug 1998 21:19:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15166 for ; Tue, 18 Aug 1998 21:19:09 -0700 (PDT) (envelope-from dmt@bigfoot.com) Received: from SpamWall.lbl.gov (root@localhost [127.0.0.1]) by postal1.lbl.gov (8.9.0/8.9.0) with ESMTP id VAA07056 for ; Tue, 18 Aug 1998 21:13:55 -0700 (PDT) Received: from dante.lbl.gov.lbl.gov (dante.lbl.gov [128.3.13.76]) by SpamWall.lbl.gov (8.9.0/8.9.0) with SMTP id VAA07051 for ; Tue, 18 Aug 1998 21:13:54 -0700 (PDT) Received: from noosphere (user-38ld66f.dialup.mindspring.com) by dante.lbl.gov.lbl.gov (4.1/SMI-4.1) id AA21554; Tue, 18 Aug 98 21:18:28 PDT Message-Id: <3.0.5.32.19980818211920.007a9790@ieng9.ucsd.edu> X-Sender: jdweinst@ieng9.ucsd.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 18 Aug 1998 21:19:20 -0700 To: stable@FreeBSD.ORG From: "Jeff W." Subject: problem with X and XSuse driver Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG alright, I donwloaded the binary for FreeBSD for the Diamond Fire GL 1000 Pro, and when I unzipped it, it was just the original filename, but without the .gz extension. Sooo, what the heck do I do with that? I couldn't find any help on the web page. Also, I downloaded the modified xf86config file, but I'm hesitant to unzip it, because the last time I did that and tried typing "xf86config", it yelled at me saying something about ELF binaries (which I presume relates to Linux), and wouldn't run. Can someone help me? I tried to find a FAQ on the suse web page, but that too wasn't there. --Jeff W. "dude things out here are out of ahh... ahh. known reality." "mail me my damn toothpaste. yeah... that's right bitch. and send it priority too." My trippy page (note the address change): http://2cb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 21:29:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16623 for freebsd-stable-outgoing; Tue, 18 Aug 1998 21:29:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rachel (mail.glenatl.glenayre.com [157.230.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA16611 for ; Tue, 18 Aug 1998 21:29:04 -0700 (PDT) (envelope-from jhicks@glenatl.glenayre.com) Received: from jhicks.glenatl.glenayre.com by rachel (SMI-8.6/SMI-SVR4) id AAA05517; Wed, 19 Aug 1998 00:21:39 -0400 Received: from jhicks.glenatl.glenayre.com (localhost.glenatl.glenayre.com [127.0.0.1]) by jhicks.glenatl.glenayre.com (8.8.8/8.8.5) with ESMTP id AAA02840; Wed, 19 Aug 1998 00:21:36 -0400 (EDT) Message-Id: <199808190421.AAA02840@jhicks.glenatl.glenayre.com> To: "Jeff W." cc: freebsd-stable@FreeBSD.ORG Subject: Re: problem with X and XSuse driver In-reply-to: Your message of "Tue, 18 Aug 1998 21:19:20 PDT." <3.0.5.32.19980818211920.007a9790@ieng9.ucsd.edu> Date: Wed, 19 Aug 1998 00:21:36 -0400 From: Jerry Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I do believe that is the X server itself (the executable). You'll need the rest of X installed to use it. The last time I inquired, Suse told me that the configuration utilities for Linux would run on FreeBSD under emulation so you'll need to be configured for Linux emulation. Good Luck (you'll need it :-) Jerry Hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 21:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17215 for freebsd-stable-outgoing; Tue, 18 Aug 1998 21:32:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17209 for ; Tue, 18 Aug 1998 21:32:10 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from obie.softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with SMTP id WAA05841; Tue, 18 Aug 1998 22:33:03 -0600 (MDT) (envelope-from wes@softweyr.com) Date: Tue, 18 Aug 1998 22:33:03 -0600 (MDT) Message-Id: <199808190433.WAA05841@obie.softweyr.com> Subject: Re: Intel EtherExpress Pro 10/100B network collisions From: Wes Peters To: stephen@farrell.org Cc: freebsd-stable@FreeBSD.ORG Reply-To: Wes Peters In-Reply-To: <87af51bz66.fsf@couatl.uchicago.edu> References: <87af51bz66.fsf@couatl.uchicago.edu> X-Priority: 3 (Normal) X-Mailer: BeatWare Mail-It 1.6 X-BeOS-Platform: Intel or clone Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id VAA17211 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My hidden microphone recorded stephen farrell (stephen@farrell.org) saying: % Note that full-duplex can also SLOW your network down. I don't % understand this, and am too looking for answers. However, I switched % a 100+ to full-duplex and went from 10Mbps -> 10bps transfer rates to % a sparc/sol2.5 box on 10baseT LAN (though connections off the LAN were % normal). Clearly some care needs to be taken in how to configure this % card. Full-duplex doesn't slow your network down, bogus configurations do. Did you set the SPARC system to full duplex also? Does it even support full duplex? If not, that is where your problem lies. Full duplex is only of use if EVERY item in your network supports it. Typically, this means replacing any hubs you may have with switches, in additional to replacing any network interfaces that don't support it. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 21:36:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17825 for freebsd-stable-outgoing; Tue, 18 Aug 1998 21:36:23 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17814; Tue, 18 Aug 1998 21:36:16 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from obie.softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with SMTP id WAA05848; Tue, 18 Aug 1998 22:37:15 -0600 (MDT) (envelope-from wes@softweyr.com) Date: Tue, 18 Aug 1998 22:37:15 -0600 (MDT) Message-Id: <199808190437.WAA05848@obie.softweyr.com> Subject: Re: Intel EtherExpress Pro 10/100B network collisions From: Wes Peters To: stephen@farrell.org, gpalmer@FreeBSD.ORG Cc: tom@uniserve.com, voland@plab.ku.dk, freebsd-stable@FreeBSD.ORG Reply-To: Wes Peters In-Reply-To: <22730.903487827@gjp.erols.com> References: <22730.903487827@gjp.erols.com> X-Priority: 3 (Normal) X-Mailer: BeatWare Mail-It 1.6 X-BeOS-Platform: Intel or clone Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id VAA17820 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My hidden microphone recorded Gary Palmer (gpalmer@FreeBSD.ORG) saying: % stephen farrell wrote in message ID % <87af51bz66.fsf@couatl.uchicago.edu>: % > Note that full-duplex can also SLOW your network down. I don't % > understand this, and am too looking for answers. However, I switched % > a 100+ to full-duplex and went from 10Mbps -> 10bps transfer rates to % > a sparc/sol2.5 box on 10baseT LAN (though connections off the LAN were % > normal). Clearly some care needs to be taken in how to configure this % > card. % % This normally only happens on poor (read: cheap, low quality) % switches. In tests here, full duplex operation doesn't decrease % performance. We use Catalyst and `Extreme' 100bTX switches. Hasn't happened in my testing either. We use Xylan OmniSwitch and OmniStack, with 100Base-TX connections to desktop machines and ATM 622 Mbps connections to the backbone *and* the Sun Ultra servers. My FreeBSD machine with onboard Intel Pro 100+ moves pretty quickly on this network, even if it is only a 200 MMX. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 22:05:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20363 for freebsd-stable-outgoing; Tue, 18 Aug 1998 22:05:30 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20352 for ; Tue, 18 Aug 1998 22:05:27 -0700 (PDT) (envelope-from dmt@bigfoot.com) Received: from SpamWall.lbl.gov (root@localhost [127.0.0.1]) by postal1.lbl.gov (8.9.0/8.9.0) with ESMTP id WAA09409 for ; Tue, 18 Aug 1998 22:00:13 -0700 (PDT) Received: from dante.lbl.gov.lbl.gov (dante.lbl.gov [128.3.13.76]) by SpamWall.lbl.gov (8.9.0/8.9.0) with SMTP id WAA09404 for ; Tue, 18 Aug 1998 22:00:12 -0700 (PDT) Received: from by dante.lbl.gov.lbl.gov (4.1/SMI-4.1) id AB24443; Tue, 18 Aug 98 22:04:43 PDT Message-Id: <3.0.5.32.19980818220128.00820b30@ieng9.ucsd.edu> X-Sender: jdweinst@ieng9.ucsd.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 18 Aug 1998 22:01:28 -0700 To: stable@FreeBSD.ORG From: "Jeff W." Subject: Re: problem with X and XSuse driver - fixed In-Reply-To: <3.0.5.32.19980818211920.007a9790@ieng9.ucsd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG problem fixed =) --Jeff W. "dude things out here are out of ahh... ahh. known reality." "mail me my damn toothpaste. yeah... that's right bitch. and send it priority too." My trippy page (note the address change): http://2cb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 22:05:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20383 for freebsd-stable-outgoing; Tue, 18 Aug 1998 22:05:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20359 for ; Tue, 18 Aug 1998 22:05:29 -0700 (PDT) (envelope-from dmt@bigfoot.com) Received: from SpamWall.lbl.gov (root@localhost [127.0.0.1]) by postal1.lbl.gov (8.9.0/8.9.0) with ESMTP id WAA09418 for ; Tue, 18 Aug 1998 22:00:15 -0700 (PDT) Received: from dante.lbl.gov.lbl.gov (dante.lbl.gov [128.3.13.76]) by SpamWall.lbl.gov (8.9.0/8.9.0) with SMTP id WAA09413 for ; Tue, 18 Aug 1998 22:00:14 -0700 (PDT) Received: from by dante.lbl.gov.lbl.gov (4.1/SMI-4.1) id AB24443; Tue, 18 Aug 98 22:04:49 PDT Message-Id: <3.0.5.32.19980818220458.007aa100@ieng9.ucsd.edu> X-Sender: jdweinst@ieng9.ucsd.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 18 Aug 1998 22:04:58 -0700 To: stable@FreeBSD.ORG From: "Jeff W." Subject: mouse is retarded in X, but fine in XF86Setup Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well it's probably me that's retarded, but oh well. In XF86Setup my mouse works without any problems, so I click the APPLY button, set up the rest of my stuff, and run X. But, in X, the mouse is very jumpy, and seems to only move around the sides of the screen. What the heck is it's problem? It's a Microsoft PS2 Intellimouse, one of those nifty mice with a wheel on it. The link in /dev/mouse points to /dev/sysmouse, I don't know if that makes a difference, that's also the port that i chose to install the mouse on in XF86Setup. --Jeff W. "dude things out here are out of ahh... ahh. known reality." "mail me my damn toothpaste. yeah... that's right bitch. and send it priority too." My trippy page (note the address change): http://2cb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 22:05:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20418 for freebsd-stable-outgoing; Tue, 18 Aug 1998 22:05:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20407 for ; Tue, 18 Aug 1998 22:05:36 -0700 (PDT) (envelope-from dmt@bigfoot.com) Received: from SpamWall.lbl.gov (root@localhost [127.0.0.1]) by postal1.lbl.gov (8.9.0/8.9.0) with ESMTP id WAA09427 for ; Tue, 18 Aug 1998 22:00:17 -0700 (PDT) Received: from dante.lbl.gov.lbl.gov (dante.lbl.gov [128.3.13.76]) by SpamWall.lbl.gov (8.9.0/8.9.0) with SMTP id WAA09422 for ; Tue, 18 Aug 1998 22:00:17 -0700 (PDT) Received: from by dante.lbl.gov.lbl.gov (4.1/SMI-4.1) id AB24443; Tue, 18 Aug 98 22:04:51 PDT Message-Id: <3.0.5.32.19980818220530.0081f850@ieng9.ucsd.edu> X-Sender: jdweinst@ieng9.ucsd.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 18 Aug 1998 22:05:30 -0700 To: stable@FreeBSD.ORG From: "Jeff W." Subject: thank you! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wanted to say thanks, you guys reply reallllly quickly and have been a big help so far =) --Jeff W. "dude things out here are out of ahh... ahh. known reality." "mail me my damn toothpaste. yeah... that's right bitch. and send it priority too." My trippy page (note the address change): http://2cb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 18 22:40:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24040 for freebsd-stable-outgoing; Tue, 18 Aug 1998 22:40:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA24035 for ; Tue, 18 Aug 1998 22:40:17 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z90y0-0006KU-00; Tue, 18 Aug 1998 22:39:28 -0700 Date: Tue, 18 Aug 1998 22:39:24 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Wes Peters cc: stephen@farrell.org, freebsd-stable@FreeBSD.ORG Subject: Re: Intel EtherExpress Pro 10/100B network collisions In-Reply-To: <199808190433.WAA05841@obie.softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Aug 1998, Wes Peters wrote: > support full duplex? If not, that is where your problem lies. Full > duplex is only of use if EVERY item in your network supports it. No. Full duplex is of benefit to any device to connected to full-duplex ports. Switches will happily transfer data between half and full duplex ports. In fact the early Catalyst 1900 switches only support half-duplex on the 10BT ports, and full-duplex only on the 100BT ports. But that is ok for small workgroups where the server would get a full-duplex 100BT port. However, the original poster didn't even mention if he/she was using a switch! I suspect not. > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://www.softweyr.com/~softweyr wes@softweyr.com Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 01:44:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11011 for freebsd-stable-outgoing; Wed, 19 Aug 1998 01:44:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA11006 for ; Wed, 19 Aug 1998 01:44:57 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA01512; Wed, 19 Aug 1998 17:44:15 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id RAA03131; Wed, 19 Aug 1998 17:53:36 +0900 (JST) Message-Id: <199808190853.RAA03131@zodiac.mech.utsunomiya-u.ac.jp> To: "Jeff W." Cc: stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: mouse is retarded in X, but fine in XF86Setup In-Reply-To: Your message of "Tue, 18 Aug 1998 22:04:58 MST." <3.0.5.32.19980818220458.007aa100@ieng9.ucsd.edu> References: <3.0.5.32.19980818220458.007aa100@ieng9.ucsd.edu> Date: Wed, 19 Aug 1998 17:53:35 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >well it's probably me that's retarded, but oh well. In XF86Setup my mouse >works without any problems, so I click the APPLY button, set up the rest of >my stuff, and run X. But, in X, the mouse is very jumpy, and seems to only >move around the sides of the screen. What the heck is it's problem? It's >a Microsoft PS2 Intellimouse, one of those nifty mice with a wheel on it. >The link in /dev/mouse points to /dev/sysmouse, I don't know if that makes >a difference, that's also the port that i chose to install the mouse on in >XF86Setup. > --Jeff W. IF you are running FreeBSD 2.2.6 or later and XFree86 3.3.2 or later, and you have `moused' running, you MUST tell the X server that /dev/sysmouse is your mouse port (if /dev/mouse is linked to /dev/sysmouse, it's OK), and specify "SysMouse" or "Auto" as protocol. IF you are NOT running `moused', the mouse port for your PS/2 IntelliMouse should be /dev/psm0 and the protocol MUST be "PS/2". See /usr/X11R6/lib/X11/doc/README.mouse. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 05:11:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00907 for freebsd-stable-outgoing; Wed, 19 Aug 1998 05:11:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from service.mfx.net (service.mfx.net [208.144.35.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA00902 for ; Wed, 19 Aug 1998 05:10:58 -0700 (PDT) (envelope-from clibby@mfx.net) Received: from pcchris.mps.mfx.net [208.144.35.68] by service.mfx.net with smtp (Exim 1.70 #3) id 0z9747-0002Tp-00 (BSDi); Wed, 19 Aug 1998 08:10:11 -0400 Message-ID: <00e301bdcb6a$1f123220$4a020180@pcchris.mps.mfx.net> From: "Christopher A. Libby" To: Subject: Re: Intel EtherExpress Pro 10/100B network collisions Date: Wed, 19 Aug 1998 07:41:40 -0400 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 4.72.2110.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 06:47:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13130 for freebsd-stable-outgoing; Wed, 19 Aug 1998 06:47:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13122 for ; Wed, 19 Aug 1998 06:47:29 -0700 (PDT) (envelope-from voland@plab.ku.dk) Received: from eagle.plab.ku.dk (eagle.plab.ku.dk [130.225.105.63]) by plab.ku.dk (8.8.8/8.8.5) with SMTP id PAA16819 for ; Wed, 19 Aug 1998 15:46:52 +0200 (CEST) Message-Id: <199808191346.PAA16819@plab.ku.dk> From: "Vadim Belman" To: "freebsd-stable@FreeBSD.ORG" Date: Wed, 19 Aug 1998 15:47:51 +0100 Reply-To: "Vadim Belman" X-Mailer: PMMail 1.96a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Subject: Solved: Intel EtherExpress Pro 10/100B network collisions Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to thank everybody who gave us advices about the subject. We solved the problem. ---- /Voland FIDO: 2:464/15@fidonet, Vadim Belman e-mail: voland@plab.ku.dk WWW: http://www.plab.ku.dk/voland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 06:54:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14326 for freebsd-stable-outgoing; Wed, 19 Aug 1998 06:54:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from is2.net.ohio-state.edu (is2.net.ohio-state.edu [128.146.48.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA14311 for ; Wed, 19 Aug 1998 06:54:40 -0700 (PDT) (envelope-from maf@dev1.net.ohio-state.edu) Received: (qmail 1168 invoked from network); 19 Aug 1998 13:54:00 -0000 Received: from dev1.net.ohio-state.edu (128.146.222.3) by is2.net.ohio-state.edu with SMTP; 19 Aug 1998 13:54:00 -0000 Received: (qmail 20408 invoked by uid 4454); 19 Aug 1998 13:53:59 -0000 Message-ID: <19980819095359.A20393@net.ohio-state.edu> Date: Wed, 19 Aug 1998 09:53:59 -0400 From: Mark Fullmer To: freebsd@magnet.geophysik.tu-freiberg.de Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Answering myself, was: URGENT! ASUS P2B/LS supported ? References: <19980728120553.A22817@net.ohio-state.edu> <199807291334.PAA06279@magnet.geophysik.tu-freiberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <199807291334.PAA06279@magnet.geophysik.tu-freiberg.de>; from Holm Tiffe on Wed, Jul 29, 1998 at 03:34:59PM +0200 X-Mutt-References: <199807291334.PAA06279@magnet.geophysik.tu-freiberg.de> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 29, 1998 at 03:34:59PM +0200, Holm Tiffe wrote: > > On Tue, Jul 28, 1998 at 01:08:58PM +0200, Holm Tiffe wrote: > [..] > > > > This is -stable around the 2.2.7 branch, not current. The pci code > > has changed quite a bit in -current. > > > > chip2 rev 2 on pci0:4:0 > > chip3 rev 1 on pci0:4:1 > > chip4 rev 1 int d irq 12 on pci0:4:2 > > chip5 rev 2 on pci0:4:3 > > ahc0 rev 0 int a irq 12 on pci0:6:0 > > pci_map_mem failed: bad memory type=0xfffff004 > > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs > > fxp0 rev 5 int a irq 10 on pci0:7:0 > avail memory = 259104768 (253032K bytes) > Probing for devices on PCI bus 0: > chip0: rev 0x02 on pci0.0.0 > chip1: rev 0x02 on pci0.1.0 > chip2: rev 0x02 on pci0.4.0 > chip3: rev 0x01 int d irq 255 on pci0.4.2 > chip4: rev 0x02 on pci0.4.3 > ahc0: rev 0x00 int a irq 15 on pci0.6.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs > fxp0: rev 0x05 int a irq 10 on pci0.7.0 > fxp0: Ethernet address 00:e0:18:90:2b:8f > > This is from my dmesg output. You are sure, that you have used the cam-drivers? > [yeah, I know, a stupid question] (I've never tryed to use the old drivers) > Have we the same revision of the host to pci bridge ? It's a -stable problem, not -current. I do have the CAM patches applied, but that shouldn't matter. -- mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 08:11:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26752 for freebsd-stable-outgoing; Wed, 19 Aug 1998 08:11:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from lincc.lincc.lib.or.us ([198.245.131.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26746 for ; Wed, 19 Aug 1998 08:11:03 -0700 (PDT) (envelope-from george@lincc.lib.or.us) Received: from localhost (george@localhost) by lincc.lincc.lib.or.us (8.8.5/8.8.5) with SMTP id IAA01403; Wed, 19 Aug 1998 08:09:53 -0700 (PDT) Date: Wed, 19 Aug 1998 08:09:52 -0700 (PDT) From: George Yobst To: Vadim Belman cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Solved: Intel EtherExpress Pro 10/100B network collisions In-Reply-To: <199808191346.PAA16819@plab.ku.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Aug 1998, Vadim Belman wrote: * I want to thank everybody who gave us advices about the *subject. We solved the problem. How? What actually did it? --------------------------------------------------------------------- George Yobst, Automation Specialist email: george@lincc.lib.or.us LINCC phone: 503-794-3890 16239 SE McLoughlin Blvd, Suite 208 fax: 503-655-8555 Oak Grove, OR 97267-4654 webmaster: [www.]lincc.lib.or.us "...it is impossible for anyone to begin to learn what he thinks he already knows." - Epictetus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 08:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04851 for freebsd-stable-outgoing; Wed, 19 Aug 1998 08:53:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04846 for ; Wed, 19 Aug 1998 08:53:13 -0700 (PDT) (envelope-from voland@plab.ku.dk) Received: from eagle.plab.ku.dk (eagle.plab.ku.dk [130.225.105.63]) by plab.ku.dk (8.8.8/8.8.5) with SMTP id RAA18297; Wed, 19 Aug 1998 17:52:29 +0200 (CEST) Message-Id: <199808191552.RAA18297@plab.ku.dk> From: "Vadim Belman" To: "George Yobst" Cc: "freebsd-stable@FreeBSD.ORG" Date: Wed, 19 Aug 1998 17:53:28 +0100 Reply-To: "Vadim Belman" X-Mailer: PMMail 1.96a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Subject: Re: Solved: Intel EtherExpress Pro 10/100B network collisions Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Aug 1998 08:09:52 -0700 (PDT), George Yobst wrote: >* I want to thank everybody who gave us advices about the >*subject. We solved the problem. >How? What actually did it? We have a 3COM 1000 series switch. And, as Michael Pearlman told, it doesn't auto-negotiate. So, collisions cease when we forced both the switch and the card to use full-duplex. ---- /Voland FIDO: 2:464/15@fidonet, Vadim Belman e-mail: voland@plab.ku.dk WWW: http://www.plab.ku.dk/voland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 10:04:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16282 for freebsd-stable-outgoing; Wed, 19 Aug 1998 10:04:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from B1FF.nas.nasa.gov (b1ff.nas.nasa.gov [129.99.34.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16277 for ; Wed, 19 Aug 1998 10:04:36 -0700 (PDT) (envelope-from rone@B1FF.nas.nasa.gov) Received: (from rone@localhost) by B1FF.nas.nasa.gov (8.8.8/8.8.8) id KAA18486 for stable@freebsd.org; Wed, 19 Aug 1998 10:03:14 -0700 (PDT) (envelope-from rone) From: Ron Echeverri Message-Id: <199808191703.KAA18486@B1FF.nas.nasa.gov> Subject: Re: MAKEDEV: arith: syntax error: "" In-Reply-To: <199808190331.XAA02689@jhicks.glenatl.glenayre.com> from Jerry Hicks at "Aug 18, 98 11:31:22 pm" To: stable@FreeBSD.ORG Date: Wed, 19 Aug 1998 10:03:14 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jerry Hicks writes: > Meanwhile, simply be advised that optimiser levels above -O > are known to cause problems, and don't yield any significant performance > benefits. I've seen this come up many times... Does it make sense to whack the options parsed from argv to force -O as long as we're using 2.7.x? Or, at the very least, have it spit out a "WARNING: optimization levels above -O are known to be broken. Proceed at your own risk." message. rone -- Ron Echeverri Numerical Aerodynamic Simulation Facility DSS/Usenet Administrator NASA Ames Research Center Internet Sysop Mountain View, CA x42771 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 10:13:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18477 for freebsd-stable-outgoing; Wed, 19 Aug 1998 10:13:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from drax-i.leverage.com (ns.leverage.com [206.79.139.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18472; Wed, 19 Aug 1998 10:13:53 -0700 (PDT) (envelope-from tlod@leverage.com) Received: (from smapman@localhost) by drax-i.leverage.com (8.6.12/8.6.12) id KAA27156; Wed, 19 Aug 1998 10:23:32 -0700 Received: from proton.leverage.com(172.16.0.33) by drax-i.leverage.com via smap (V1.3) id sma027154; Wed Aug 19 10:23:24 1998 Received: from localhost (tlod@localhost) by leverage.com (8.8.7/8.8.7) with SMTP id KAA13659; Wed, 19 Aug 1998 10:13:03 -0700 (PDT) Date: Wed, 19 Aug 1998 10:13:03 -0700 (PDT) From: Thede Loder To: freebsd-stable@FreeBSD.ORG cc: freebsd-bugs@FreeBSD.ORG Subject: proc disappeared, w, uptime, who malfunctioning Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1056796358-903546783=:7133" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-1056796358-903546783=:7133 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm running FreeBSD 2.2.7-RELEASE with a custom (but not very custom) recompiled kernel, on a 233 Pentium II (Dell XPS). The machine has been up for about 13 days. This morning odd things are happening. /proc empty when I ls -R it. Just an empty directory. w, who, uptime all spit a page full of gibberish at me before reporting anything, causing the xterm to become screwy. Other than this unusual behavior, thing seem to work ok. various xsysstats are working, as is "top". The gibberish is included as an attachment, for those who are curious. Apparently the garbage is being written to stderr, while the output of w, who, and uptime goes to stdout and appears ok. Has anyone else had their /proc disappear? Thede -- tlod@leverage.com ---559023410-1056796358-903546783=:7133 Content-Type: TEXT/PLAIN; name=wout Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: dzogL2Rldi8vcuNVC/XejAOp3Gn8X9rM9NfZJ+9z3fHuLuPe8V3od/Vs7An5 KNi/7zogTm8gc3VjaCBmaWxlIG9yIGRpcmVjdG9yeQ0KdzogL2Rldi8v+PH+ /uf1wAR49xgJC/i0DCH4mg609fYLmPFRBnzt6v8NCup4+SjYv+86IE5vIHN1 Y2ggZmlsZSBvciBkaXJlY3RvcnkNCnc6IC9kZXYvL/jns/Oz5q7v+eR67Fjh xOg13j3mrN1a5l7f0+jE4RXshuEE7ijYv+86IE5vIHN1Y2ggZmlsZSBvciBk aXJlY3RvcnkNCnc6IC9kZXYvL4HfDPA33S/yBNu9887bP/Uw33L03eT08Pjs GOyI9NXm5fnh4ijYv+86IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkNCnc6 IC9kZXYvL9v71d+V+9Pd//s/35T7g+GM/MTk1gHm6ZUJDu+dEqL09hnV+CjY v+86IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkNCnc6IC9kZXYvLwQdL/o6 IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkNCnc6IC9kZXYvL5n4O8wq/qPR lgXd3pcNc/CGFWUDXx0pFRAkRyPPKNgswyyqMijYv+86IE5vIHN1Y2ggZmls ZSBvciBkaXJlY3RvcnkNCnc6IC9kZXYvL7IsbTKyKV4tiiYiJQMipRnnG1EN lRW4AYkQ7PjCDPryugk+7yjYv+86IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3Rv cnkNCnc6IC9kZXYvL3AG4+wNCgRB7OUHNvENChB7+nAXVQWWHLMQXB6BGxMc DiOeGWEoKNi/7zogTm8gc3VjaCBmaWxlIG9yIGRpcmVjdG9yeQ0KdzogL2Rl di8vCxjuKiUWFigdE18gqw+PFvoNCs4NCh4FB//W/l71gfrx7jH4teso2L/v OiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5DQp3OiAvZGV2Ly9p+B3ro/po 7GL+o+9fAr3zYAZu+LANClL+5AzWA5QLLAdrBNUHKNi/7zogTm8gc3VjaCBm aWxlIG9yIGRpcmVjdG9yeQ0KdzogL2Rldi8vau4e5yLuPOGJ7N7e6elm4Ejm CeTe5Rzr++hL9EPwEv5s+yMHKNi/7zogTm8gc3VjaCBmaWxlIG9yIGRpcmVj dG9yeQ0KdzogL2Rldi8vEQeZDRcRihFyGcEUEx1aFosYfhI+DdUJtwFrOiBO byBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5DQogOTo1NEFNICB1cCAxMyBkYXlz LCAxNzozNCwgMTAgdXNlcnMsIGxvYWQgYXZlcmFnZXM6IDAuMDgsIDAuMTUs IDAuMTYNClVTRVIgICAgIFRUWSBGUk9NICAgICAgICAgICAgICBMT0dJTkAg IElETEUgV0hBVA0KdGxvZCAgICAgcDIgIDowLjAgICAgICAgICAgICAgV2Vk MDlQTSAgICAgLSAgKHcpDQp0bG9kICAgICBwNSAgOjAuMCAgICAgICAgICAg ICAwNkF1Zzk4IDE2OjA5ICAodGVsbmV0KQ0KdGxvZCAgICAgcDYgIDowLjAg ICAgICAgICAgICAgMDZBdWc5OCA3ZGF5cyAgKHNzaCkNCnRsb2QgICAgIHA3 ICA6MC4wICAgICAgICAgICAgIE1vbjAyUE0gMWRheSAgICh0Y3NoKQ0KdGxv ZCAgICAgcDggIDowLjAgICAgICAgICAgICAgVHVlMDRQTSAxNTo1MSAgKHNz aCkNCnRsb2QgICAgIHA5ICA6MC4wICAgICAgICAgICAgIFdlZDAxUE0gNGRh eXMgIChybG9naW4pDQp0bG9kICAgICBwYSAgOjAuMCAgICAgICAgICAgICAw NkF1Zzk4IDE1OjE4ICAodGVsbmV0KQ0KdGxvZCAgICAgcGIgIDowLjAgICAg ICAgICAgICAgV2VkMDFQTSAxNjo1OSAgKHJsb2dpbikNCnRsb2QgICAgIHBj ICA6MC4wICAgICAgICAgICAgICA1OjU2UE0gMTU6NDIgICh0Y3NoKQ0KdGxv ZCAgICAgcGQgIDowLjAgICAgICAgICAgICAgVHVlMTJQTSAxOTo0NCAgKHZp KQ0K ---559023410-1056796358-903546783=:7133-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 13:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19890 for freebsd-stable-outgoing; Wed, 19 Aug 1998 13:09:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.fcc.net (241.pearlriver.fcc.net [207.198.253.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19879; Wed, 19 Aug 1998 13:09:49 -0700 (PDT) (envelope-from nathan@fcc.net) Received: from noc.fcc.net (noc.fcc.net [207.198.253.18]) by mail.fcc.net (8.9.1/8.9.1) with ESMTP id QAA00720; Wed, 19 Aug 1998 16:08:27 -0400 (EDT) Received: (from nathan@localhost) by noc.fcc.net (8.8.8+Sun/8.8.8) id QAA06496; Wed, 19 Aug 1998 16:09:43 -0400 (EDT) Message-ID: <19980819160023.B5565@fcc.net> Date: Wed, 19 Aug 1998 16:00:23 -0400 From: Nathan Dorfman To: Thede Loder Subject: Re: proc disappeared, w, uptime, who malfunctioning References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Thede Loder on Wed, Aug 19, 1998 at 10:13:03AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 19, 1998 at 10:13:03AM -0700, Thede Loder wrote: > > I'm running FreeBSD 2.2.7-RELEASE with a custom (but not very custom) > recompiled kernel, on a 233 Pentium II (Dell XPS). The machine has > been up for about 13 days. > > This morning odd things are happening. > > /proc empty when I ls -R it. Just an empty directory. Is it mounted? Type /sbin/mount, you should see a line like: procfs on /proc (local) If not, then that's the problem. mount -t procfs procfs /proc, and everything should be well again. > Thede > -- > tlod@leverage.com -- Nathan Dorfman | Frontline Communications Corporation nathan@fcc.net | Pearl River, NY - 914-623-8559 -- linux/exit.h: -+---------------------------------------- #define exit(X); (X == 0 ? raise(SIGSEGV); : system("yes > /proc/self/mem");) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 13:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00995 for freebsd-stable-outgoing; Wed, 19 Aug 1998 13:59:33 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.fcc.net (241.pearlriver.fcc.net [207.198.253.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00977 for ; Wed, 19 Aug 1998 13:59:22 -0700 (PDT) (envelope-from nathan@fcc.net) Received: from noc.fcc.net (noc.fcc.net [207.198.253.18]) by mail.fcc.net (8.9.1/8.9.1) with ESMTP id QAA00818; Wed, 19 Aug 1998 16:58:11 -0400 (EDT) Received: (from nathan@localhost) by noc.fcc.net (8.8.8+Sun/8.8.8) id QAA08077; Wed, 19 Aug 1998 16:59:25 -0400 (EDT) Message-ID: <19980819165925.A7948@fcc.net> Date: Wed, 19 Aug 1998 16:59:25 -0400 From: Nathan Dorfman To: Thede Loder Cc: freebsd-stable@FreeBSD.ORG Subject: Re: proc disappeared, w, uptime, who malfunctioning References: <19980819160023.B5565@fcc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Thede Loder on Wed, Aug 19, 1998 at 01:52:39PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 19, 1998 at 01:52:39PM -0700, Thede Loder wrote: > > Nathan - > > I've mounted /proc. It was missing as you suggested. I feel pretty > dumb about that - I must have removed it from my fstab when we were > doing some swapping of machines here a while ago. Heh :-) > Though /proc is mounted, I've not yet rebooted. w, who, and uptime > all still produce garbage. I'll reboot and if I'm still having the > problem, I'll drop you a line... w, who, and uptime read /dev/kmem, not /proc (AFAIK). The symptoms you describe come up frequently from people who are running a newer kernel than the said utilities, or vice versa. Have you upgraded your kernel without first upgrading your world? > Thede -- Nathan Dorfman | Frontline Communications Corporation nathan@fcc.net | Pearl River, NY - 914-623-8559 -- linux/exit.h: -+---------------------------------------- #define exit(X); (X == 0 ? raise(SIGSEGV); : system("yes > /proc/self/mem");) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 14:09:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02797 for freebsd-stable-outgoing; Wed, 19 Aug 1998 14:09:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from drax-i.leverage.com (ns.leverage.com [206.79.139.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA02783 for ; Wed, 19 Aug 1998 14:09:06 -0700 (PDT) (envelope-from tlod@leverage.com) Received: (from smapman@localhost) by drax-i.leverage.com (8.6.12/8.6.12) id OAA27899; Wed, 19 Aug 1998 14:18:57 -0700 Received: from proton.leverage.com(172.16.0.33) by drax-i.leverage.com via smap (V1.3) id sma027897; Wed Aug 19 14:18:53 1998 Received: from localhost (tlod@localhost) by leverage.com (8.8.7/8.8.7) with SMTP id OAA14653; Wed, 19 Aug 1998 14:08:26 -0700 (PDT) Date: Wed, 19 Aug 1998 14:08:26 -0700 (PDT) From: Thede Loder To: Nathan Dorfman cc: freebsd-stable@FreeBSD.ORG Subject: Re: proc disappeared, w, uptime, who malfunctioning In-Reply-To: <19980819165925.A7948@fcc.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Though /proc is mounted, I've not yet rebooted. w, who, and uptime > > all still produce garbage. I'll reboot and if I'm still having the > > problem, I'll drop you a line... > > w, who, and uptime read /dev/kmem, not /proc (AFAIK). The symptoms you > describe come up frequently from people who are running a newer kernel > than the said utilities, or vice versa. Have you upgraded your kernel > without first upgrading your world? The system is back up and the utilities are now all functioning properly. When I upgraded (2.2.6 -> 2.2.7), I did a "make world" for a 2.2.7-RELEASE /usr/src while running the 2.2.6 kernel. Once all the binaries had been rebuilt, I built the kernel. Should I do another make world, this time with the 2.2.7 kernel active? Thede To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 14:16:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04321 for freebsd-stable-outgoing; Wed, 19 Aug 1998 14:16:55 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.fcc.net (241.pearlriver.fcc.net [207.198.253.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04309 for ; Wed, 19 Aug 1998 14:16:52 -0700 (PDT) (envelope-from nathan@fcc.net) Received: from noc.fcc.net (noc.fcc.net [207.198.253.18]) by mail.fcc.net (8.9.1/8.9.1) with ESMTP id RAA00841; Wed, 19 Aug 1998 17:15:38 -0400 (EDT) Received: (from nathan@localhost) by noc.fcc.net (8.8.8+Sun/8.8.8) id RAA08620; Wed, 19 Aug 1998 17:16:53 -0400 (EDT) Message-ID: <19980819171652.A8468@fcc.net> Date: Wed, 19 Aug 1998 17:16:52 -0400 From: Nathan Dorfman To: Thede Loder Cc: freebsd-stable@FreeBSD.ORG Subject: Re: proc disappeared, w, uptime, who malfunctioning References: <19980819165925.A7948@fcc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Thede Loder on Wed, Aug 19, 1998 at 02:08:26PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 19, 1998 at 02:08:26PM -0700, Thede Loder wrote: > The system is back up and the utilities are now all functioning properly. Great :) > When I upgraded (2.2.6 -> 2.2.7), > I did a "make world" for a 2.2.7-RELEASE /usr/src while running the 2.2.6 > kernel. Once all the binaries had been rebuilt, I built the kernel. > Should I do another make world, this time with the 2.2.7 kernel active? When you update your source tree, you need to make world, then build your new kernel with the newly build world in place. You don't need to rebuild world after you build the kernel. Making world twice would not be fun. The general procedure is # cvsup /usr/share/examples/cvsup/standard-supfile # cd /usr/src && make world # cd /usr/src/sys/i386/conf && /usr/sbin/config MYKERNEL # cd /usr/src/sys/compile/MYKERNEL && make depend kernel install On -current, this occasionally requires considerably more effort :-) > Thede -- Nathan Dorfman | Frontline Communications Corporation nathan@fcc.net | Pearl River, NY - 914-623-8559 -- linux/exit.h: -+---------------------------------------- #define exit(X); (X == 0 ? raise(SIGSEGV); : system("yes > /proc/self/mem");) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 19:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24583 for freebsd-stable-outgoing; Wed, 19 Aug 1998 19:20:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from seraph.uunet.ca (uunet.ca [142.77.1.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24577 for ; Wed, 19 Aug 1998 19:20:50 -0700 (PDT) (envelope-from erics@now.com) Received: from now by seraph.uunet.ca with UUCP id <185037-3213>; Wed, 19 Aug 1998 22:19:59 -0400 Received: from business.now.com (really [205.150.6.1]) by vishnu.now.com via rsmtp (Smail-3.2 1996-Jul-4 #2 built 1997-Apr-17) with bsmtp id for ; Wed, 19 Aug 1998 22:01:44 -0400 (EDT) Received: by business.now.com (Smail3.1.29.1 #12) id m0z9K0A-00002sC; Wed, 19 Aug 98 21:58 EDT Message-Id: From: erics@now.com (Eric Siegerman) Subject: Re: Found reason why lpr -r -s doesn't work as expected To: andre.albsmeier@mchp.siemens.de (Andre Albsmeier) Date: Wed, 19 Aug 1998 21:58:58 -0400 Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <199808161345.PAA19691@internal> from "Andre Albsmeier" at Aug 16, 98 09:45:28 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andre Albsmeier wrote: > I have now changed printjob.c so that removing > files containing '/' still is forbidden except when it starts with > '/var/spool/samba/'. It's ugly but works. But, I think this behaviuor > should be stated in the manual page of lpr. Now it says: > > -r Remove the file upon completion of spooling or upon completion of > printing (with the -s option). > > -s Use symbolic links. Usually files are copied to the spool direc- > tory. The -s option will use symlink(2) to link data files > rather than trying to copy them so large files can be printed. Why not instead make "lpr -r" (without -s) act like mv(1): try to rename the file into /var/spool/output, and only copy-and-unlink if the rename fails? If you have /var/spool/samba and /var/spool/output on the same filesystem, you'd avoid the extra file copy, without introducing either new security holes or the ugly special case. (One could conceivably go a step further by having "lpr" (with neither -r nor -s) try to hard-link the file into the spool directory. Bad idea; it would change the original file's st_ctime behind the user's back, when they thought they were only reading the file.) Rasmus Kaj wrote: > A 'serious' way to fix this (IMHO) would be to make lpd su to the user > that requested the printout before removing any file at all. But this > would probably be very hard to do ... Obvious catch: a remote user > might print without even having an account on the host where lpd > runns. Well, any file that wasn't created by lpr. Otherwise it'd keep lpd from removing files from /var/spool/output. Besides which, as you were probably thinking, this would require adding -- and security-auditing -- machinery to pass the userid from lpr to lpd. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont. erics@now.com | | / The Rock & Roll Baby Theorem: Syllables(x+"baby") = Syllables("baby"+x) = Syllables(x) + 2 SemanticContent(x+"baby") = SemanticContent("baby"+x) = SemanticContent(x) - Anonymous To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 19 21:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14422 for freebsd-stable-outgoing; Wed, 19 Aug 1998 21:45:58 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14409 for ; Wed, 19 Aug 1998 21:45:47 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id GAA00211 for ; Thu, 20 Aug 1998 06:44:58 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id GAA15809 for ; Thu, 20 Aug 1998 06:44:57 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id GAA27433 for ; Thu, 20 Aug 1998 06:44:54 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808200444.GAA13907@internal> Subject: Re: Found reason why lpr -r -s doesn't work as expected In-Reply-To: from Eric Siegerman at "Aug 19, 98 09:58:58 pm" To: erics@now.com (Eric Siegerman) Date: Thu, 20 Aug 1998 06:44:51 +0200 (CEST) Cc: andre.albsmeier@mchp.siemens.de, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Andre Albsmeier wrote: > > I have now changed printjob.c so that removing > > files containing '/' still is forbidden except when it starts with > > '/var/spool/samba/'. It's ugly but works. But, I think this behaviuor > > should be stated in the manual page of lpr. Now it says: > > > > -r Remove the file upon completion of spooling or upon completion of > > printing (with the -s option). > > > > -s Use symbolic links. Usually files are copied to the spool direc- > > tory. The -s option will use symlink(2) to link data files > > rather than trying to copy them so large files can be printed. > > Why not instead make "lpr -r" (without -s) act like mv(1): try > to rename the file into /var/spool/output, and only > copy-and-unlink if the rename fails? If you have > /var/spool/samba and /var/spool/output on the same filesystem, > you'd avoid the extra file copy, without introducing either new > security holes or the ugly special case. Yes, I have thought of this as well. Anyone who wants to implement this :-) Would it have a chance to go into the src trees? If it is undesired to use -r, maybe we could make a new option... -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 20 02:11:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21453 for freebsd-stable-outgoing; Thu, 20 Aug 1998 02:11:46 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from unix.sim.com.pl (www1.sim.com.pl [195.117.85.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21389 for ; Thu, 20 Aug 1998 02:11:02 -0700 (PDT) (envelope-from pawel@unix.sim.com.pl) Received: from unix.sim.com.pl (pawel.sim.com.pl [192.168.1.11]) by unix.sim.com.pl (8.8.8/8.8.8) with ESMTP id LAA15207 for ; Thu, 20 Aug 1998 11:10:25 GMT (envelope-from pawel@unix.sim.com.pl) Message-ID: <35DBE721.7D159586@unix.sim.com.pl> Date: Thu, 20 Aug 1998 11:06:41 +0200 From: Gawel X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: buildworld problem Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, After "make buildworld" from 2.2.6-Release to 2.2.7-Stable (18 Aug) I have received: ... rm -f freebsd.cf (cd /usr/src/usr.sbin/sendmail/cf/cf && m4 ../m4/cf.m4 freebsd.mc) > freebsd.cf m4: eval: major botch *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Any ideas? Gawel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 20 10:44:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19994 for freebsd-stable-outgoing; Thu, 20 Aug 1998 10:44:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA19897 for ; Thu, 20 Aug 1998 10:44:06 -0700 (PDT) (envelope-from kris@atipa.com) Received: (qmail 25307 invoked by uid 1012); 20 Aug 1998 16:39:52 -0000 Date: Thu, 20 Aug 1998 10:39:52 -0600 (MDT) From: Kris Efland To: freebsd-stable@FreeBSD.ORG cc: freebsd-hardware@FreeBSD.ORG Subject: Intel EEPro Not Detecting on N440BX Server Board Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Whom it May Concern, I am trying to install FreeBSD via FTP, on a system with the Intel N440BX Server Board, however the on-board EtherExpress is not detecting and the only options to install, are a null modem cable, parallel port, or PPP Dial-Up. Any advice would be greatly appreciated. Regards, Kris Efland Atipa Computers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 20 16:45:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20903 for freebsd-stable-outgoing; Thu, 20 Aug 1998 16:45:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from homer.supersex.com (homer.supersex.com [209.5.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20898 for ; Thu, 20 Aug 1998 16:45:28 -0700 (PDT) (envelope-from leo@homer.supersex.com) Received: (from leo@localhost) by homer.supersex.com (8.8.8/8.8.5) id TAA11139; Thu, 20 Aug 1998 19:45:49 -0400 (EDT) Message-ID: <19980820194548.56450@supersex.com> Date: Thu, 20 Aug 1998 19:45:48 -0400 From: Leo Papandreou To: stable@FreeBSD.ORG Subject: Re: Intel EEPro Not Detecting on N440BX Server Board References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Kris Efland on Thu, Aug 20, 1998 at 10:39:52AM -0600 X-Organization: Once neatly stacked a pile of paper. X-Wife: Forgotten but not gone. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 20, 1998 at 10:39:52AM -0600, Kris Efland wrote: > To Whom it May Concern, > I am trying to install FreeBSD via FTP, on a system with the Intel N440BX > Server Board, however the on-board EtherExpress is not detecting I assume you mean you cannot spot its signature on the screen as its being probed during a boot, correct? If not, what evidence, in the way of an error message, are you getting that indicates the FTP failed due to undetected ethernet? > and the > only options to install, are a null modem cable, parallel port, or PPP > Dial-Up. Any advice would be greatly appreciated. > I didnt have this problem. The board works flawlessly with FreeBSD. As a first step, check the bios to make sure the on-board ethernet is actually enabled. > Regards, > Kris Efland > Atipa Computers > > > 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 Aug 20 17:51:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00291 for freebsd-stable-outgoing; Thu, 20 Aug 1998 17:51:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from srv1.thuntek.net (srv1.thuntek.net [206.206.98.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00283 for ; Thu, 20 Aug 1998 17:51:42 -0700 (PDT) (envelope-from freaker@thuntek.net) Received: from shell1.thuntek.net (freaker@shell1.thuntek.net [206.206.98.21]) by srv1.thuntek.net (8.8.7/8.6.12TNT1.0) with ESMTP id SAA25855 for ; Thu, 20 Aug 1998 18:51:02 -0600 (MDT) Received: from localhost by shell1.thuntek.net (8.8.7/client-1.3) id TAA13832; Thu, 20 Aug 1998 19:03:22 -0600 (MDT) Date: Thu, 20 Aug 1998 19:03:22 -0600 (MDT) From: Jason Vennes To: stable@FreeBSD.ORG Subject: Talk / Hostnames... Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-796134775-903661402=:13733" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-796134775-903661402=:13733 Content-Type: TEXT/PLAIN; charset=US-ASCII Dear People, I have on a problem on my 2.2.7-Stable box, My true domain is: freaksys.thuntek.net but when Even I go to write and/or talk to a user on my box.. locally, it says.... % talk sysop [sysop's side says:] Message from Talk_Daemon@FreaKSyS.net talk: connection requested by root@localhost.thuntek.net talk: respond with: talk root@localhost.thuntek.net -- So any ideas? Also I attached the "netstat" and "netstat -A" output ... freaksys.netstat is 'netstat' and freaksys.netstat2 is "netstat -A" thanks! - ************************** Jason Vennes FreaKSyS Shell Systems www.FreaKSyS.net SysOp / SysAdmin ************************** --0-796134775-903661402=:13733 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="freaksys.netstat" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Um91dGluZyB0YWJsZXMNCg0KSW50ZXJuZXQ6DQpEZXN0aW5hdGlvbiAgICAg ICAgR2F0ZXdheSAgICAgICAgICAgIEZsYWdzICAgICBSZWZzICAgICBVc2Ug ICAgIE5ldGlmIEV4cGlyZQ0KZGVmYXVsdCAgICAgICAgICAgIGRkaWFsMi50 aHVudGVrICAgICBVR1NjICAgICAgIDIwICAgICAgIDczICAgICAgdHVuMA0K bG9jYWxob3N0LnRodW50ZWsgIGxvY2FsaG9zdC50aHVudGVrICBVSCAgICAg ICAgICA3ICAgICAgNzIwICAgICAgIGxvMA0KZGRpYWwyLnRodW50ZWsgICAg IGZyZWFrc3lzLnRodW50ZWsgICBVSCAgICAgICAgIDE5ICAgICAgICAwICAg ICAgdHVuMA0KZnJlYWtzeXMudGh1bnRlayAgIGxvY2FsaG9zdC50aHVudGVr ICBVSCAgICAgICAgICAwICAgICAgODg2ICAgICAgIGxvMA0K --0-796134775-903661402=:13733 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="freaksys.netstat2" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: QWN0aXZlIEludGVybmV0IGNvbm5lY3Rpb25zDQpQQ0IgICAgICBQcm90byBS ZWN2LVEgU2VuZC1RICBMb2NhbCBBZGRyZXNzICAgICAgRm9yZWlnbiBBZGRy ZXNzICAgIChzdGF0ZSkNCmYwODFkMTAwIHRjcCAgICAgICAgMCAgICAgIDAg IGxvY2FsaG9zdC50aHVudGUuMSAqLiogICAgICAgICAgICAgICAgTElTVEVO DQpmMDk3ZWQwMCB0Y3AgICAgICAgIDAgICAgICAwICBmcmVha3N5cy50aHVu dGVrLjEgY3ljbG9uZS5saWdoLjY2NjcgIEVTVEFCTElTSEVEDQpmMDgyOWMw MCB0Y3AgICAgICAgIDAgICAgICAwICBmcmVha3N5cy50aHUuMTMxNSAgc2hl bGwxLnRodW50ZWsuMzkwIEVTVEFCTElTSEVEDQpmMDlmN2IwMCB0Y3AgICAg ICAgIDAgICAgICAwICBmcmVha3N5cy50aHVudGVrLjEgaXJjLnBhc3Nwb3J0 LjY2NjcgIEVTVEFCTElTSEVEDQpmMGExOGMwMCB0Y3AgICAgICAgIDAgICAg ICAwICBmcmVha3N5cy50aHUudGVsbmUgc3RpbGV0dG8uYWNhZGlhbi40IEVT VEFCTElTSEVEDQpmMDkxM2QwMCB0Y3AgICAgICAgIDAgICAgICAwICBmcmVh a3N5cy50aHVudGVrLjEgYXNzaW1pbGF0aW9uLjY2NjYgIEVTVEFCTElTSEVE DQpmMDcyYzEwMCB0Y3AgICAgICAgIDAgICAgICAwICBmcmVha3N5cy50aHUu dGVsbmUgMTcwLTMtNjYuaXB0LmFvbC4yIEVTVEFCTElTSEVEDQpmMGExMjIw MCB0Y3AgICAgICAgIDAgICAgICAwICBmcmVha3N5cy50aHVudGVrLjEgcmVw ZW50LmV4b2R1LjY2NjcgIEVTVEFCTElTSEVEDQpmMDgwZGEwMCB0Y3AgICAg ICAgIDAgICAgICAwICBmcmVha3N5cy50aHVudGVrLjEgZG5zMS5ud3MuMjI0 NSAgICAgIEVTVEFCTElTSEVEDQpmMDg0ODgwMCB0Y3AgICAgICAgIDAgICAg ICAwICBmcmVha3N5cy50aHVudGVrLjEgaXJjMS5jLWNvbS42NjY3ICAgIEVT VEFCTElTSEVEDQpmMDk4YjEwMCB1ZHAgICAgICAgIDAgICAgICAwICBsb2Nh bGhvc3QudGh1bnRlLjEgKi4qICAgICAgICAgICAgICAgDQpmMDc3NjM4MCB1 ZHAgICAgICAgIDAgICAgICAwICBsb2NhbGhvc3QudGguMTAyMiAgbG9jYWxo b3N0LnRodW50ZS4zDQpmMDc2ZmE4MCB1ZHAgICAgICAgIDAgICAgICAwICBs b2NhbGhvc3QudGguTlNXUyAgKi4qICAgICAgICAgICAgICAgDQpBY3RpdmUg VU5JWCBkb21haW4gc29ja2V0cw0KQWRkcmVzcyAgVHlwZSAgIFJlY3YtUSBT ZW5kLVEgICAgSW5vZGUgICAgIENvbm4gICAgIFJlZnMgIE5leHRyZWYgQWRk cg0KZjA3N2IyMDAgZGdyYW0gICAgICAgMCAgICAgIDAgICAgICAgIDAgZjA1 MzVmMTQgICAgICAgIDAgZjA1MzVkOTQNCmYwNzdiNjAwIGRncmFtICAgICAg IDAgICAgICAwICAgICAgICAwIGYwNTM1ZjE0ICAgICAgICAwIGYwNTM1YzE0 DQpmMDc2OWQwMCBkZ3JhbSAgICAgICAwICAgICAgMCAgICAgICAgMCBmMDUz NWYxNCAgICAgICAgMCBmMDUzNWE5NA0KZjA3Njg3MDAgZGdyYW0gICAgICAg MCAgICAgIDAgICAgICAgIDAgZjA1MzVmMTQgICAgICAgIDAgZjA1MzViMTQN CmYwNzIyMTAwIGRncmFtICAgICAgIDAgICAgICAwICAgICAgICAwIGYwNTM1 ZjE0ICAgICAgICAwICAgICAgICAwDQpmMDcxYTQwMCBkZ3JhbSAgICAgICAw ICAgICAgMCBmMDcxYmEwMCAgICAgICAgMCBmMDUzNWM5NCAgICAgICAgMCAv dmFyL3J1bi9sb2cNCg== --0-796134775-903661402=:13733-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 20 20:57:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27009 for freebsd-stable-outgoing; Thu, 20 Aug 1998 20:57:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26997 for ; Thu, 20 Aug 1998 20:57:33 -0700 (PDT) (envelope-from dmt@bigfoot.com) Received: from SpamWall.lbl.gov (root@localhost [127.0.0.1]) by postal1.lbl.gov (8.9.0/8.9.0) with ESMTP id UAA28510 for ; Thu, 20 Aug 1998 20:52:14 -0700 (PDT) Received: from dante.lbl.gov.lbl.gov (dante.lbl.gov [128.3.13.76]) by SpamWall.lbl.gov (8.9.0/8.9.0) with SMTP id UAA28505 for ; Thu, 20 Aug 1998 20:52:13 -0700 (PDT) Received: from by dante.lbl.gov.lbl.gov (4.1/SMI-4.1) id AB02320; Thu, 20 Aug 98 20:56:51 PDT Message-Id: <3.0.5.32.19980820205637.00830ba0@ieng9.ucsd.edu> X-Sender: jdweinst@ieng9.ucsd.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 20 Aug 1998 20:56:37 -0700 To: stable@FreeBSD.ORG From: "Jeff W." Subject: FreeBSD takes 8 years to boot up Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, not literally, but a damn long time. I know I have to reconfigure the kernel to only probe for the devices known to exist, but after doing that, it still takes a long time. I notice the lag right after it detects my hard drive, and then another lag after detecting the CDROM. Is there a way around this, or should I just get used to getting up for a drink while FreeBSD loads? --Jeff W. "dude things out here are out of ahh... ahh. known reality." "mail me my damn toothpaste. yeah... that's right bitch. and send it priority too." My trippy page (note the address change): http://2cb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 20 21:46:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02950 for freebsd-stable-outgoing; Thu, 20 Aug 1998 21:46:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02938 for ; Thu, 20 Aug 1998 21:46:26 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id OAA19138; Fri, 21 Aug 1998 14:15:33 +0930 (CST) Message-Id: <199808210445.OAA19138@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jeff W." cc: stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-reply-to: Your message of "Thu, 20 Aug 1998 20:56:37 MST." <3.0.5.32.19980820205637.00830ba0@ieng9.ucsd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 14:15:33 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, not literally, but a damn long time. I know I have to reconfigure > the kernel to only probe for the devices known to exist, but after doing > that, it still takes a long time. I notice the lag right after it detects > my hard drive, and then another lag after detecting the CDROM. Is there a > way around this, or should I just get used to getting up for a drink while > FreeBSD loads? The reason for the delay is it waits a while to detect other IDE devices you might have and waits a while before giving up. If you're only using one controller, then disable the other one in the config screen. If however you have, say, a HD on chain 1, and a CDROM on chain 2, then you need to explicitly disable 'disk wd?' entries. So, if you had a HD as master on chain 1 and a CDROM as master on chain to, change the lines in your kernel config file which read 'disk wd1 at wdc0 drive 1' to 'disk wd1 at wcd0 disable drive 1' do the same for the wd3 line. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 20 22:39:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09902 for freebsd-stable-outgoing; Thu, 20 Aug 1998 22:39:50 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09879 for ; Thu, 20 Aug 1998 22:39:40 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id AAA15006; Fri, 21 Aug 1998 00:38:59 -0500 (CDT) Message-ID: <19980821003859.31729@futuresouth.com> Date: Fri, 21 Aug 1998 00:38:59 -0500 From: "Matthew D. Fuller" To: "Jeff W." Cc: stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up References: <3.0.5.32.19980820205637.00830ba0@ieng9.ucsd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <3.0.5.32.19980820205637.00830ba0@ieng9.ucsd.edu>; from Jeff W. on Thu, Aug 20, 1998 at 08:56:37PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 20, 1998 at 08:56:37PM -0700, Jeff W. woke me up to tell me: > Well, not literally, but a damn long time. I know I have to reconfigure > the kernel to only probe for the devices known to exist, but after doing > that, it still takes a long time. I notice the lag right after it detects > my hard drive, and then another lag after detecting the CDROM. Is there a > way around this, or should I just get used to getting up for a drink while > FreeBSD loads? Lemme guess... A single drive as master on the primary IDE controller, and CDROM as master on the secondary? It's probing for the slaves on the respective controllers. You can take out the secondary drives in the kernel config if you need it to boot faster. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 06:38:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05009 for freebsd-stable-outgoing; Fri, 21 Aug 1998 06:38:41 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05004 for ; Fri, 21 Aug 1998 06:38:38 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id GAA07568; Fri, 21 Aug 1998 06:37:52 -0700 (PDT) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdEV7563; Fri Aug 21 06:37:14 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.1/8.6.10) id GAA08894; Fri, 21 Aug 1998 06:37:01 -0700 (PDT) Message-Id: <199808211337.GAA08894@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdWf8886; Fri Aug 21 06:36:51 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: "Daniel O'Connor" cc: "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-reply-to: Your message of "Fri, 21 Aug 1998 14:15:33 +0930." <199808210445.OAA19138@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 06:36:44 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Well, not literally, but a damn long time. I know I have to reconfigure > > the kernel to only probe for the devices known to exist, but after doing > > that, it still takes a long time. I notice the lag right after it detects > > my hard drive, and then another lag after detecting the CDROM. Is there a > > way around this, or should I just get used to getting up for a drink while > > FreeBSD loads? > > The reason for the delay is it waits a while to detect other IDE devices you > might have and waits a while before giving up. If you're only using one > controller, then disable the other one in the config screen. If however you > have, say, a HD on chain 1, and a CDROM on chain 2, then you need to > explicitly disable 'disk wd?' entries. > > So, if you had a HD as master on chain 1 and a CDROM as master on chain to, > change the lines in your kernel config file which read > 'disk wd1 at wdc0 drive 1' > to > 'disk wd1 at wcd0 disable drive 1' > do the same for the wd3 line. I've taken this one step further by also disabling any unused drive addresses in the BIOS. Many BIOS's spend as much time searching the universe for devices as FreeBSD does. It also may be a good idea to remove other unused devices from the kernel as well. The disadvantage to this is that every time you change your configuration you will need to rebuild the kernel. Hopefully that won't be that often. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 08:17:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19341 for freebsd-stable-outgoing; Fri, 21 Aug 1998 08:17:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19333 for ; Fri, 21 Aug 1998 08:16:58 -0700 (PDT) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id LAA01628 for ; Fri, 21 Aug 1998 11:17:24 -0400 (EDT) (envelope-from witr@rwwa.com) Message-Id: <199808211517.LAA01628@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-stable@FreeBSD.ORG Subject: New NFS probs with 2.2.6 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 11:17:24 -0400 From: Robert Withrow Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've used essentially the same NFS/AMD setup since 2.2.beginning, and today, after rebooting my machine (to get the stinking bios version number....grrr) NFS to a NAC or Auspex (I forget which) developed a problem where it will work for a while and then it will hang. It may be that the sysadmin types upgraded the software on the server box. Am I having a problem that can be fixed by using NFS v2 for my outbound mounts? Is there a way to set this as an option to sysctl? Otherwise, is there an amd *option* (specified on the command line) that will force this? I ask that because all my maps come from NIS (even the master map) and I don't have the ability to change them (and it would be wrong to change them just to support an interop problem with one system, e.g. FreeBSD). --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 08:57:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24472 for freebsd-stable-outgoing; Fri, 21 Aug 1998 08:57:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24464 for ; Fri, 21 Aug 1998 08:57:41 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id RAA04575; Fri, 21 Aug 1998 17:56:29 +0200 (MET DST) Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Fri, 21 Aug 1998 17:56:28 +0200 (MET DST) Mime-Version: 1.0 To: Cy Schubert - ITSD Open Systems Group Cc: "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up References: <199808211337.GAA08894@cwsys.cwsent.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 21 Aug 1998 17:56:28 +0200 In-Reply-To: Cy Schubert - ITSD Open Systems Group's message of "Fri, 21 Aug 1998 06:36:44 -0700" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA24466 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group writes: > It also may be a good idea to remove other unused devices from the > kernel as well. The disadvantage to this is that every time you change > your configuration you will need to rebuild the kernel. Hopefully that > won't be that often. Recompiling the kernel on anything above P150 is a matter of a couple of minutes at most if you use the '-n' option to config (but remember to always make depend!) The advantages are quicker booting and a smaller memory footprint. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 09:03:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25616 for freebsd-stable-outgoing; Fri, 21 Aug 1998 09:03:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25608 for ; Fri, 21 Aug 1998 09:03:56 -0700 (PDT) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id JAA11465; Fri, 21 Aug 1998 09:03:00 -0700 (PDT) Message-Id: <199808211603.JAA11465@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdJ11454; Fri Aug 21 09:02:58 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-reply-to: Your message of "21 Aug 1998 17:56:28 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 09:02:57 -0700 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Cy Schubert - ITSD Open Systems Group writes: > > It also may be a good idea to remove other unused devices from the=20 > > kernel as well. The disadvantage to this is that every time you change=20 > > your configuration you will need to rebuild the kernel. Hopefully that=20 > > won't be that often. > > Recompiling the kernel on anything above P150 is a matter of a couple > of minutes at most if you use the '-n' option to config (but remember > to always make depend!) The advantages are quicker booting and a > smaller memory footprint. On my 486/DX33 it took approximately 90 minutes, on my P120 it takes about 6 minutes and on the P333's here at work it takes about 2 minutes. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 09:57:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02051 for freebsd-stable-outgoing; Fri, 21 Aug 1998 09:57:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02030; Fri, 21 Aug 1998 09:57:49 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id JAA00333; Fri, 21 Aug 1998 09:57:07 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 21 Aug 1998 09:57:00 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: FYI: page faults caused by "speculative read" Cc: freebsd-questions@FreeBSD.ORG, support@tomshardware.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While I have not had this problem with several other Pentium systems, in building 2.2.7-RELEASE from CD-ROM I recently encountered a system that would not run sysinstall without page faults. This was apparently caused by enabling "Speculative Read" in the BIOS. Abit AB-TX5 (Intel 430TX) AMD K6-233 at "normal" voltages and clock 64 MB SDRAM (10 ns) I do not know the hardware cause of this problem; the vendor I use has been very reliable and supplies better-than-average components. I have enabled speculative read on other AB-TX5-based systems (albeit all Intel Pentiums) without incident, and find the M/B to be very reliable, even at 83 MHz bus speeds. In the hopes someone else may be spared gray hairs, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 10:52:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08189 for freebsd-stable-outgoing; Fri, 21 Aug 1998 10:52:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08171 for ; Fri, 21 Aug 1998 10:51:59 -0700 (PDT) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id NAA02542 for ; Fri, 21 Aug 1998 13:52:31 -0400 (EDT) (envelope-from witr@rwwa.com) Message-Id: <199808211752.NAA02542@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@FreeBSD.ORG Subject: Xfree86 server doesn't recover after sleep Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 13:52:31 -0400 From: Robert Withrow Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my laptop with 2.2.7, XFree86 3.3.2, on a Trident Cyber 9397 chipset, if I sleep the compter (with zzz), or if I just close the lid, the server never seems to recover to display the screen. If I kill the server (I use XDM) and re-start it, everything works OK. Is there any workaround/fix for this. I didn't see anything on the XFree86 site, and I don't know if this is a FreeBSD or X issue. --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 11:42:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14274 for freebsd-stable-outgoing; Fri, 21 Aug 1998 11:42:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14231; Fri, 21 Aug 1998 11:41:59 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by yip.org (8.8.8/8.8.8) with SMTP id OAA25407; Fri, 21 Aug 1998 14:41:33 -0400 (EDT) (envelope-from melange@yip.org) Date: Fri, 21 Aug 1998 14:41:31 -0400 (EDT) From: Bob K To: Jeff Kletsky cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, support@tomshardware.com Subject: Re: FYI: page faults caused by "speculative read" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Aug 1998, Jeff Kletsky wrote: > While I have not had this problem with several other Pentium systems, in > building 2.2.7-RELEASE from CD-ROM I recently encountered a system that > would not run sysinstall without page faults. This was apparently caused > by enabling "Speculative Read" in the BIOS. > > Abit AB-TX5 (Intel 430TX) > AMD K6-233 at "normal" voltages and clock > 64 MB SDRAM (10 ns) > > I do not know the hardware cause of this problem; the vendor I use has been > very reliable and supplies better-than-average components. I have enabled > speculative read on other AB-TX5-based systems (albeit all Intel Pentiums) > without incident, and find the M/B to be very reliable, even at 83 MHz bus > speeds. > > In the hopes someone else may be spared gray hairs, I think in the manual for my AOpen AP5T rev.3.1 (tx chipset), it mentions that one can't use speculative read with two DIMMs - only if you have one. I can't remember if the option is even available in the BIOS if you do have two, though. Might that have had something to do with why it was causing that? melange@yip.org - "Slightly tacky but completely entertaining" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 17:09:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18570 for freebsd-stable-outgoing; Fri, 21 Aug 1998 17:09:14 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d3.dialup.hilink.com.au [203.2.144.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18541 for ; Fri, 21 Aug 1998 17:09:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA10911; Fri, 21 Aug 1998 17:06:26 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211706.RAA10911@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-reply-to: Your message of "21 Aug 1998 17:56:28 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 21 Aug 1998 17:06:25 +0000 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA18558 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Cy Schubert - ITSD Open Systems Group writes: > > It also may be a good idea to remove other unused devices from the > > kernel as well. The disadvantage to this is that every time you change > > your configuration you will need to rebuild the kernel. Hopefully that > > won't be that often. > > Recompiling the kernel on anything above P150 is a matter of a couple > of minutes at most if you use the '-n' option to config (but remember > to always make depend!) The advantages are quicker booting and a > smaller memory footprint. You can also just 'disable' them in userconfig. This prevents them being probed, but leaves them there for when you need them. The userconfig changes are saved back into the kernel by 'dset' out of / etc/rc, so you only need to do this once. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 17:21:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21368 for freebsd-stable-outgoing; Fri, 21 Aug 1998 17:21:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d3.dialup.hilink.com.au [203.2.144.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21345 for ; Fri, 21 Aug 1998 17:21:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA10978; Fri, 21 Aug 1998 17:17:44 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211717.RAA10978@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Withrow cc: stable@FreeBSD.ORG Subject: Re: Xfree86 server doesn't recover after sleep In-reply-to: Your message of "Fri, 21 Aug 1998 13:52:31 -0400." <199808211752.NAA02542@spooky.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 17:17:43 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On my laptop with 2.2.7, XFree86 3.3.2, on a Trident Cyber 9397 > chipset, if I sleep the compter (with zzz), or if I just close > the lid, the server never seems to recover to display the screen. > > If I kill the server (I use XDM) and re-start it, everything works OK. > > Is there any workaround/fix for this. I didn't see anything on the > XFree86 site, and I don't know if this is a FreeBSD or X issue. If you try swapping to a text console, then back, does the screen recover? If you swap to a text console before 'zzz'ing, can you swap back to X and have it work? Ultimately, it's a BIOS issue (the BIOS is expected to restore the display hardware state). It may be feasible to work around it by having syscons install an apm hook so that it returns to the console before allowing the shutdown. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 19:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06630 for freebsd-stable-outgoing; Fri, 21 Aug 1998 19:06:43 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06625 for ; Fri, 21 Aug 1998 19:06:41 -0700 (PDT) (envelope-from ian@gamespot.com) Received: from localhost (ian@localhost) by mail.gamespot.com (8.9.0/8.9.0) with SMTP id TAA25607 for ; Fri, 21 Aug 1998 19:05:13 -0700 (PDT) Date: Fri, 21 Aug 1998 19:05:13 -0700 (PDT) From: Ian Kallen To: freebsd-stable@FreeBSD.ORG Subject: kernel compile hitting aicasm_scan.c & puking Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded from something 2.2.2ish to 2.2.7 and my kernel compile is bombing out with something like: cc -O -I. -c aicasm_scan.c ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': ../../dev/aic7xxx/aicasm_scan.l:68: `T_DOWNLOAD' undeclared (first use this function) ../../dev/aic7xxx/aicasm_scan.l:68: (Each undeclared identifier is reported only once ../../dev/aic7xxx/aicasm_scan.l:68: for each function it appears in.) *** Error code 1 I just supped /sys from stable and I'm making world, I'll check on it in a few hours, meantime: anybody else seen this problem recently? Wassup? thanks, -Ian -- Ian Kallen ICQ: 17073910 For a while I didn't have a car...I had a helicopter...no place to park it, so I just tied it to a lamp post and left it running... [slow glance upward] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 19:32:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10265 for freebsd-stable-outgoing; Fri, 21 Aug 1998 19:32:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d3.dialup.hilink.com.au [203.2.144.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10249 for ; Fri, 21 Aug 1998 19:32:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA11864; Fri, 21 Aug 1998 19:28:56 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211928.TAA11864@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Withrow cc: freebsd-stable@FreeBSD.ORG Subject: Re: New NFS probs with 2.2.6 In-reply-to: Your message of "Fri, 21 Aug 1998 11:17:24 -0400." <199808211517.LAA01628@spooky.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 19:28:55 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've used essentially the same NFS/AMD setup since 2.2.beginning, > and today, after rebooting my machine (to get the stinking bios > version number....grrr) NFS to a NAC or Auspex (I forget which) > developed a problem where it will work for a while and then it > will hang. It may be that the sysadmin types upgraded the software > on the server box. When you say "hang", in what state are the "hung" processes? (Use 'ps -axl' to see this) > Am I having a problem that can be fixed by using NFS v2 for my > outbound mounts? Possibly. Try duplicating a mount manually in v2 mode and see if it still fails. > Is there a way to set this as an option to sysctl? The mount type is determined by the mount request, which isn't sent by the kernel. You should be able to rebuild amd and tweak it to always request a v2 mount. The correct solution, of course, is to work out what's going wrong where and fix it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 19:39:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11820 for freebsd-stable-outgoing; Fri, 21 Aug 1998 19:39:22 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d3.dialup.hilink.com.au [203.2.144.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11807 for ; Fri, 21 Aug 1998 19:39:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA11928; Fri, 21 Aug 1998 19:37:00 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211937.TAA11928@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ian Kallen cc: freebsd-stable@FreeBSD.ORG Subject: Re: kernel compile hitting aicasm_scan.c & puking In-reply-to: Your message of "Fri, 21 Aug 1998 19:05:13 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 19:36:58 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I just upgraded from something 2.2.2ish to 2.2.7 and my kernel compile is > bombing out with something like: > > cc -O -I. -c aicasm_scan.c > ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': > ../../dev/aic7xxx/aicasm_scan.l:68: `T_DOWNLOAD' undeclared (first use > this function) > ../../dev/aic7xxx/aicasm_scan.l:68: (Each undeclared identifier is > reported only once > ../../dev/aic7xxx/aicasm_scan.l:68: for each function it appears in.) > *** Error code 1 > > I just supped /sys from stable and I'm making world, I'll check on > it in a few hours, meantime: anybody else seen this problem recently? > Wassup? You haven't finished your world build. One thing at a time. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 22:02:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25299 for freebsd-stable-outgoing; Fri, 21 Aug 1998 22:02:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25245 for ; Fri, 21 Aug 1998 22:01:56 -0700 (PDT) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id NAA12848; Sat, 22 Aug 1998 13:00:58 +0800 (GMT) Date: Sat, 22 Aug 1998 13:00:58 +0800 (GMT) From: Michael Robinson Message-Id: <199808220500.NAA12848@public.bta.net.cn> To: stable@FreeBSD.ORG, witr@rwwa.com Subject: Re: Xfree86 server doesn't recover after sleep Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Withrow writes: >On my laptop with 2.2.7, XFree86 3.3.2, on a Trident Cyber 9397 >chipset, if I sleep the compter (with zzz), or if I just close >the lid, the server never seems to recover to display the screen. > >If I kill the server (I use XDM) and re-start it, everything works OK. > >Is there any workaround/fix for this. I didn't see anything on the >XFree86 site, and I don't know if this is a FreeBSD or X issue. I have a similar problem with my Toshiba TECRA. What works for me is to switch to another virtual console (Ctl-Alt-F[1-3]) and back, which seems to do whatever is necessary to wake up the X server. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 22:25:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27664 for freebsd-stable-outgoing; Fri, 21 Aug 1998 22:25:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bart.zip.com.au (bart.zip.com.au [203.62.151.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27636; Fri, 21 Aug 1998 22:24:50 -0700 (PDT) (envelope-from bart@bart.zip.com.au) Received: (from bart@localhost) by rocklands.burra.zip.com.au (8.8.8/8.8.8) id NAA03470; Sat, 22 Aug 1998 13:10:12 +1000 (EST) (envelope-from bart) Date: Sat, 22 Aug 1998 13:10:12 +1000 (EST) Message-Id: <199808220310.NAA03470@rocklands.burra.zip.com.au> From: Bart Lindsey To: Jeff@Wagsky.com CC: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, support@tomshardware.com In-reply-to: (message from Jeff Kletsky on Fri, 21 Aug 1998 09:57:00 -0700) Subject: Re: FYI: page faults caused by "speculative read" References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had some trouble with page faults myself. I have an IBM P200 L CPU and a Triton VX MB. The page faults appear to have gone away since reducing the bus speed from 75MHz to 66MHz (and jacking up the CPU core freq multiplier accordingly). I believe the SDRAM I'm using is unreliable at bus speeds higher than 66MHz. Try giving this a go. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 22:25:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27696 for freebsd-stable-outgoing; Fri, 21 Aug 1998 22:25:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bart.zip.com.au (bart.zip.com.au [203.62.151.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27656; Fri, 21 Aug 1998 22:24:57 -0700 (PDT) (envelope-from bart@bart.zip.com.au) Received: (from bart@localhost) by rocklands.burra.zip.com.au (8.8.8/8.8.8) id MAA03427; Sat, 22 Aug 1998 12:50:08 +1000 (EST) (envelope-from bart) Date: Sat, 22 Aug 1998 12:50:08 +1000 (EST) Message-Id: <199808220250.MAA03427@rocklands.burra.zip.com.au> From: Bart Lindsey To: Jeff@Wagsky.com CC: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, support@tomshardware.com In-reply-to: (message from Jeff Kletsky on Fri, 21 Aug 1998 09:57:00 -0700) Subject: Re: FYI: page faults caused by "speculative read" References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had some trouble with page faults myself. I have an IBM P200 L CPU and a Triton VX MB. The page faults appear to have gone away since reducing the bus speed from 75MHz to 66MHz (and jacking up the CPU core freq multiplier accordingly). I believe the SDRAM I'm using is unreliable at bus speeds higher than 66MHz. Try giving this a go. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 23:10:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02210 for freebsd-stable-outgoing; Fri, 21 Aug 1998 23:10:51 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02199 for ; Fri, 21 Aug 1998 23:10:47 -0700 (PDT) (envelope-from ian@gamespot.com) Received: from localhost (ian@localhost) by mail.gamespot.com (8.9.0/8.9.0) with SMTP id XAA02025; Fri, 21 Aug 1998 23:09:09 -0700 (PDT) Date: Fri, 21 Aug 1998 23:09:09 -0700 (PDT) From: Ian Kallen To: Mike Smith cc: freebsd-stable@FreeBSD.ORG Subject: Re: kernel compile hitting aicasm_scan.c & puking In-Reply-To: <199808211937.TAA11928@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, now I'm done with make world and guess what, it's still bombing out. It looks like this was a problem for a while in April, is this a recurrent bug or did a kludge something here? Thanks, -Ian On Fri, 21 Aug 1998, Mike Smith wrote: :> I just upgraded from something 2.2.2ish to 2.2.7 and my kernel compile is :> bombing out with something like: :> :> cc -O -I. -c aicasm_scan.c :> ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': :> ../../dev/aic7xxx/aicasm_scan.l:68: `T_DOWNLOAD' undeclared (first use :> this function) :> ../../dev/aic7xxx/aicasm_scan.l:68: (Each undeclared identifier is :> reported only once :> ../../dev/aic7xxx/aicasm_scan.l:68: for each function it appears in.) :> *** Error code 1 :> :> I just supped /sys from stable and I'm making world, I'll check on :> it in a few hours, meantime: anybody else seen this problem recently? :> Wassup? : :You haven't finished your world build. One thing at a time. : :-- :\\ Sometimes you're ahead, \\ Mike Smith :\\ sometimes you're behind. \\ mike@smith.net.au :\\ The race is long, and in the \\ msmith@freebsd.org :\\ end it's only with yourself. \\ msmith@cdrom.com : : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-stable" in the body of the message : -- Ian Kallen ICQ: 17073910 Homer: All right, time for a family meeting. Lisa: [snidely] Why can't we have a meeting when you're watching TV? Homer: Now look,, You know and I know this family needs help, professional help. So I've made an appointment with Dr Marvin Monroe. Bart: The fat guy on TV? Lisa: You're sending us to a doctor who advertises on Pro-Wrestling? Homer: Boxing, Lisa, Boxing -- there's a world of difference. -- ``There's no disgrace like Home'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 21 23:16:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03056 for freebsd-stable-outgoing; Fri, 21 Aug 1998 23:16:00 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03049 for ; Fri, 21 Aug 1998 23:15:58 -0700 (PDT) (envelope-from ian@gamespot.com) Received: from localhost (ian@localhost) by mail.gamespot.com (8.9.0/8.9.0) with SMTP id XAA02088; Fri, 21 Aug 1998 23:14:25 -0700 (PDT) Date: Fri, 21 Aug 1998 23:14:25 -0700 (PDT) From: Ian Kallen To: Mike Smith cc: freebsd-stable@FreeBSD.ORG Subject: Re: kernel compile hitting aicasm_scan.c & puking In-Reply-To: <199808211937.TAA11928@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eh, fikken aye, doing a make clean in /sys/dev/aic7xxx/ and then going back to my kernel compile fixed it. -Ian On Fri, 21 Aug 1998, Mike Smith wrote: :> I just upgraded from something 2.2.2ish to 2.2.7 and my kernel compile is :> bombing out with something like: :> :> cc -O -I. -c aicasm_scan.c :> ../../dev/aic7xxx/aicasm_scan.l: In function `yylex': :> ../../dev/aic7xxx/aicasm_scan.l:68: `T_DOWNLOAD' undeclared (first use :> this function) :> ../../dev/aic7xxx/aicasm_scan.l:68: (Each undeclared identifier is :> reported only once :> ../../dev/aic7xxx/aicasm_scan.l:68: for each function it appears in.) :> *** Error code 1 :> :> I just supped /sys from stable and I'm making world, I'll check on :> it in a few hours, meantime: anybody else seen this problem recently? :> Wassup? : :You haven't finished your world build. One thing at a time. : :-- :\\ Sometimes you're ahead, \\ Mike Smith :\\ sometimes you're behind. \\ mike@smith.net.au :\\ The race is long, and in the \\ msmith@freebsd.org :\\ end it's only with yourself. \\ msmith@cdrom.com : : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-stable" in the body of the message : -- Ian Kallen ICQ: 17073910 Marge: Bart, I feel so bad for going so many years without... mmm... mmm... What's that word where you encourage something to grow? Bart+Homer: [stare blankly and hum ``I dunno''] Lisa: [brightly] Nurturing. Marge: ... nurturing your brilliant brain. -- ``Bart the Genius'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 05:54:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27052 for freebsd-stable-outgoing; Sat, 22 Aug 1998 05:54:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27047 for ; Sat, 22 Aug 1998 05:54:50 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from skejdbrimir.ifi.uio.no (skejdbrimir.ifi.uio.no [129.240.65.2]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id OAA20966; Sat, 22 Aug 1998 14:53:51 +0200 (MET DST) Received: from localhost (dag-erli@localhost) by skejdbrimir.ifi.uio.no ; Sat, 22 Aug 1998 12:53:49 GMT Mime-Version: 1.0 To: Mike Smith Cc: Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up References: <199808211706.RAA10911@dingo.cdrom.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 22 Aug 1998 12:53:43 +0000 In-Reply-To: Mike Smith's message of "Fri, 21 Aug 1998 17:06:25 +0000" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA27048 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > You can also just 'disable' them in userconfig. This prevents them > being probed, but leaves them there for when you need them. They still take up memory and make the kernel slower to load and link (one consequence of which is that modload is very slow, especially on boxes with little memory) DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 06:26:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00452 for freebsd-stable-outgoing; Sat, 22 Aug 1998 06:26:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dc.dialup.hilink.com.au [203.2.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00433 for ; Sat, 22 Aug 1998 06:26:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id GAA17475; Sat, 22 Aug 1998 06:23:44 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808220623.GAA17475@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: Mike Smith , Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-reply-to: Your message of "22 Aug 1998 12:53:43 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 22 Aug 1998 06:23:43 +0000 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA00444 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > > You can also just 'disable' them in userconfig. This prevents them > > being probed, but leaves them there for when you need them. > > They still take up memory and make the kernel slower to load and link > (one consequence of which is that modload is very slow, especially on > boxes with little memory) You should qualify "slower" here. I would suggest "marginally" as a good candidate. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 06:38:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01910 for freebsd-stable-outgoing; Sat, 22 Aug 1998 06:38:03 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01841 for ; Sat, 22 Aug 1998 06:38:00 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from skejdbrimir.ifi.uio.no (skejdbrimir.ifi.uio.no [129.240.65.2]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id PAA23019; Sat, 22 Aug 1998 15:37:05 +0200 (MET DST) Received: from localhost (dag-erli@localhost) by skejdbrimir.ifi.uio.no ; Sat, 22 Aug 1998 13:37:03 GMT Mime-Version: 1.0 To: Mike Smith Cc: Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up References: <199808220623.GAA17475@dingo.cdrom.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 22 Aug 1998 13:37:00 +0000 In-Reply-To: Mike Smith's message of "Sat, 22 Aug 1998 06:23:43 +0000" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA01901 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > > You can also just 'disable' them in userconfig. This prevents them > > > being probed, but leaves them there for when you need them. > > They still take up memory and make the kernel slower to load and link > > (one consequence of which is that modload is very slow, especially on > > boxes with little memory) > You should qualify "slower" here. I would suggest "marginally" as > a good candidate. Not at all. Try loading lkms on a box with a kernel about half the size of your RAM. Been there, done that. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 06:53:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03679 for freebsd-stable-outgoing; Sat, 22 Aug 1998 06:53:20 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dc.dialup.hilink.com.au [203.2.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03672 for ; Sat, 22 Aug 1998 06:53:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id GAA17660; Sat, 22 Aug 1998 06:50:37 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808220650.GAA17660@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: Mike Smith , Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-reply-to: Your message of "22 Aug 1998 13:37:00 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 22 Aug 1998 06:50:36 +0000 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA03673 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > > > > You can also just 'disable' them in userconfig. This prevents them > > > > being probed, but leaves them there for when you need them. > > > They still take up memory and make the kernel slower to load and link > > > (one consequence of which is that modload is very slow, especially on > > > boxes with little memory) > > You should qualify "slower" here. I would suggest "marginally" as > > a good candidate. > > Not at all. Try loading lkms on a box with a kernel about half the > size of your RAM. Been there, done that. FreeBSD doesn't run in 2M anymore. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 07:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06915 for freebsd-stable-outgoing; Sat, 22 Aug 1998 07:34:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA06909 for ; Sat, 22 Aug 1998 07:34:34 -0700 (PDT) (envelope-from vev@paprika.michvhf.com) Received: (qmail 15532 invoked by uid 1000); 22 Aug 1998 14:34:31 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199808220650.GAA17660@dingo.cdrom.com> Date: Sat, 22 Aug 1998 10:34:31 -0400 (EDT) From: Vince Vielhaber To: stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Aug-98 Mike Smith wrote: >> Mike Smith writes: >> > > > You can also just 'disable' them in userconfig. This prevents them >> > > > being probed, but leaves them there for when you need them. >> > > They still take up memory and make the kernel slower to load and link >> > > (one consequence of which is that modload is very slow, especially on >> > > boxes with little memory) >> > You should qualify "slower" here. I would suggest "marginally" as >> > a good candidate. >> >> Not at all. Try loading lkms on a box with a kernel about half the >> size of your RAM. Been there, done that. > > FreeBSD doesn't run in 2M anymore. Yep, learned that when I tried to put picobsd on my 2MB laptop. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 08:02:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09629 for freebsd-stable-outgoing; Sat, 22 Aug 1998 08:02:42 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phoenix.welearn.com.au (suebla.lnk.telstra.net [139.130.44.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09622 for ; Sat, 22 Aug 1998 08:02:39 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.8.5/8.8.5) id BAA29481; Sun, 23 Aug 1998 01:01:36 +1000 (EST) Message-ID: <19980823010133.43922@welearn.com.au> Date: Sun, 23 Aug 1998 01:01:33 +1000 From: Sue Blake To: Mike Smith Cc: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= , Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up References: <199808220650.GAA17660@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199808220650.GAA17660@dingo.cdrom.com>; from Mike Smith on Sat, Aug 22, 1998 at 06:50:36AM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 22, 1998 at 06:50:36AM +0000, Mike Smith wrote: > > Mike Smith writes: > > > > > You can also just 'disable' them in userconfig. This prevents them > > > > > being probed, but leaves them there for when you need them. > > > > They still take up memory and make the kernel slower to load and link > > > > (one consequence of which is that modload is very slow, especially on > > > > boxes with little memory) > > > You should qualify "slower" here. I would suggest "marginally" as > > > a good candidate. > > > > Not at all. Try loading lkms on a box with a kernel about half the > > size of your RAM. Been there, done that. > > FreeBSD doesn't run in 2M anymore. So do you mean that on my overworked 386 with 8 megs RAM and not much swap I might as well use GENERIC and save the hassle of building special anorexic kernels? If the difference is marginal, that changes everything. -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 12:59:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01325 for freebsd-stable-outgoing; Sat, 22 Aug 1998 12:59:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA01319 for ; Sat, 22 Aug 1998 12:58:58 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 208 invoked by uid 1000); 22 Aug 1998 20:04:25 -0000 Message-ID: <19980822220425.A180@paert.tse-online.de> Date: Sat, 22 Aug 1998 22:04:25 +0200 From: Andreas Braukmann To: freebsd-stable@FreeBSD.ORG Subject: Natd/LibAlias/IPDivert [other] problem ... Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Organization: TSE TeleService GmbH Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, at a client's site I'm running 'natd' quite fine on an 'older' 2.2.5-based system. Currently I'm trying out a similar configuration on an 2.2-stable (from 98/08/19, kernel and userland) with no success so far. It seems, that 'natd' (or the underlying libalias) gets something really wrong? This happens (simplified): diverting ipfw-rule: divert natd log ip from 192.168.100.0/24 to any 'de0' is configured (as long as the system exists) to a valid ip-address. # natd -v -interface de0 > In [ICMP] 192.168.100.2 -> 194.97.69.190 aliased to 192.168.100.2 -> 194.97.69.190 All 'diverted' packets are translated to their very own real 'source address'. Any hints? TIA, Andreas -- /// TSE TeleService GmbH | Gsf: Arne Reuter | /// Hovestrasse 14 | Andreas Braukmann | We do it with /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP /// ------------------------------------------------------------------- /// PGP-Key: http://www.tse-online.de/~ab/public-key /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 15:00:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10036 for freebsd-stable-outgoing; Sat, 22 Aug 1998 15:00:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (user-38lcoi5.dialup.mindspring.com [209.86.98.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10031 for ; Sat, 22 Aug 1998 15:00:16 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost.mindspring.com [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id SAA24029; Sat, 22 Aug 1998 18:02:57 -0400 (EDT) (envelope-from dex@wankers.net) Date: Sat, 22 Aug 1998 18:02:56 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: Cy Schubert - ITSD Open Systems Group cc: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-Reply-To: <199808211603.JAA11465@passer.osg.gov.bc.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Aug 1998, Cy Schubert wrote: > > Cy Schubert - ITSD Open Systems Group writes: > > > It also may be a good idea to remove other unused devices from the=20 > > > kernel as well. The disadvantage to this is that every time you change=20 > > > your configuration you will need to rebuild the kernel. Hopefully that=20 > > > won't be that often. > > > > Recompiling the kernel on anything above P150 is a matter of a couple > > of minutes at most if you use the '-n' option to config (but remember > > to always make depend!) The advantages are quicker booting and a > > smaller memory footprint. > > On my 486/DX33 it took approximately 90 minutes, on my P120 it takes > about 6 minutes and on the P333's here at work it takes about 2 minutes. > it takes about 2 minutes on an AMD K6-233, as well, FYI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 17:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22239 for freebsd-stable-outgoing; Sat, 22 Aug 1998 17:12:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d6.dialup.hilink.com.au [203.2.144.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22232 for ; Sat, 22 Aug 1998 17:12:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA20160; Sat, 22 Aug 1998 17:09:05 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808221709.RAA20160@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Sue Blake cc: Mike Smith , =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= , Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Jeff W." , stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-reply-to: Your message of "Sun, 23 Aug 1998 01:01:33 +1000." <19980823010133.43922@welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Aug 1998 17:09:04 +0000 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So do you mean that on my overworked 386 with 8 megs RAM and not much > swap I might as well use GENERIC and save the hassle of building special > anorexic kernels? If the difference is marginal, that changes everything. Do the comparisons yourself and make up your own mind. Apart from maxusers being too small, GENERIC tries very hard to be one-size-fits-all. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 22 17:24:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24490 for freebsd-stable-outgoing; Sat, 22 Aug 1998 17:24:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from SchematiX.net (schematix.net [24.234.31.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24482 for ; Sat, 22 Aug 1998 17:24:49 -0700 (PDT) (envelope-from scott@SchematiX.net) Received: from localhost (scott@localhost) by SchematiX.net (8.8.8/8.8.8) with SMTP id RAA00360; Sat, 22 Aug 1998 17:21:56 -0700 (PDT) (envelope-from scott@SchematiX.net) Date: Sat, 22 Aug 1998 17:21:56 -0700 (PDT) From: Scott To: Dexnation Holodream cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: FreeBSD takes 8 years to boot up In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Aug 1998, Dexnation Holodream wrote: > On Fri, 21 Aug 1998, Cy Schubert wrote: > > > > Cy Schubert - ITSD Open Systems Group writes: > > > > It also may be a good idea to remove other unused devices from the=20 > > > > kernel as well. The disadvantage to this is that every time you change=20 > > > > your configuration you will need to rebuild the kernel. Hopefully that=20 > > > > won't be that often. > > > > > > Recompiling the kernel on anything above P150 is a matter of a couple > > > of minutes at most if you use the '-n' option to config (but remember > > > to always make depend!) The advantages are quicker booting and a > > > smaller memory footprint. > > > > On my 486/DX33 it took approximately 90 minutes, on my P120 it takes > > about 6 minutes and on the P333's here at work it takes about 2 minutes. > > > it takes about 2 minutes on an AMD K6-233, as well, FYI Thats rather quick. I built a K6-2/300 machine with 64MB PC100 SDRAM and a rather fast IDE hard disk and it took over 5 minutes. Possibly something wrong with the system? My PII233 does it in 4 > > > 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