From owner-freebsd-stable Sun Jan 7 2:58: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 9853937B402 for ; Sun, 7 Jan 2001 02:57:44 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id F3FE12CE74; Sun, 7 Jan 2001 12:57:33 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id f07AvNG13011; Sun, 7 Jan 2001 12:57:23 +0200 (EET) (envelope-from vallo) Date: Sun, 7 Jan 2001 12:57:23 +0200 From: Vallo Kallaste To: Greg Lehey Cc: Josef Karthauser , Thomas Seck , freebsd-stable@FreeBSD.ORG Subject: Re: Vinum safe to use for raid 0? Message-ID: <20010107125723.A12982@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20010102230107.A559@basildon.homerun> <20010103102943.A770@tao.org.uk> <20010103214829.X4336@wantadilla.lemis.com> <20010103172844.D13221@myhakas.matti.ee> <20010104094938.B4336@wantadilla.lemis.com> <20010106224329.A10969@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010106224329.A10969@myhakas.matti.ee>; from vallo@myhakas.matti.ee on Sat, Jan 06, 2001 at 10:43:29PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 06, 2001 at 10:43:29PM +0200, Vallo Kallaste wrote: [snip] Additional info, checkparity returns: vinum -> checkparity raidvol.p0 Parity incorrect at offset 0x1f729c4 vinum -> -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 5:18:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.sacoriver.net (dilbert.mix-net.net [216.64.56.4]) by hub.freebsd.org (Postfix) with ESMTP id 1A04E37B400 for ; Sun, 7 Jan 2001 05:18:32 -0800 (PST) Received: from loqtis (dsl-216.sacoriver.net [64.31.104.217]) by dilbert.sacoriver.net (8.9.3/8.9.0) with SMTP id IAA11367 for ; Sun, 7 Jan 2001 08:18:30 -0500 (EST) Message-ID: <001001c078ac$67228f00$0100a8c0@loqtis> From: "B" To: Subject: /var drive space problem Date: Sun, 7 Jan 2001 08:19:00 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C07882.7D43F0A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C07882.7D43F0A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, This probably isnt the place to be posting this question BUT...ive = always gottin good advise from this mailing list so here goes = nothing............ i have a recently upgraded FreeBSD 4.2 from 4.1...and my problem is that = im runing out of space on the /var partition (i recieve alot of system = mail in that partition which i have to delete daily to keep it at 99%) = ..im not sure what i can delete to make room...although if i go to=20 /var/tmp theres a dir thats called "temproot" ..i think it was = from when i CVS the new 4.2 src..and installed....can i delete this = dir??? this is the dir structure under /var account/ crash/ games/ msgs/ rwho/ = yp/ at/ cron/ log/ preserve/ spool/ backups/ db/ mail/ run/ tmp/ if anyone has any suggestions.... they would be greatly appreciated..... thanx in advance Brent=20 ------=_NextPart_000_000D_01C07882.7D43F0A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
This probably isnt the place to be = posting this=20 question  BUT...ive always gottin good advise from this mailing = list so=20 here goes nothing............
i have a recently upgraded FreeBSD 4.2 = from=20 4.1...and my problem is that im runing out of space on the /var = partition (i=20 recieve alot of system mail  in that partition which i have to = delete daily=20 to keep it at 99%) ..im not sure what i can delete to make = room...although if i=20 go to
/var/tmp       theres=20 a dir thats called "temproot" ..i think it was from when i CVS the new = 4.2=20 src..and installed....can i delete this dir???  this is the dir = structure=20 under /var
 
account/       =20 crash/         =20 games/         =20 msgs/          =20 rwho/          =20 yp/
at/          &nb= sp; =20 cron/          =20 log/           =20 preserve/      =20 spool/
backups/       =20 db/           &nbs= p;=20 mail/          =20 run/           =20 tmp/
 
if anyone has any suggestions.... they = would be=20 greatly appreciated.....
 
thanx in advance
Brent
------=_NextPart_000_000D_01C07882.7D43F0A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 5:41:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id 8CCB737B400 for ; Sun, 7 Jan 2001 05:41:36 -0800 (PST) Received: (qmail 19438 invoked by uid 1078); 7 Jan 2001 13:41:46 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jan 2001 13:41:46 -0000 Date: Sun, 7 Jan 2001 05:41:46 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: B Cc: Subject: Re: /var drive space problem In-Reply-To: <001001c078ac$67228f00$0100a8c0@loqtis> 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, 7 Jan 2001, B wrote: > i have a recently upgraded FreeBSD 4.2 from 4.1...and my problem is that im runing out of space on the /var partition (i recieve alot of system mail in that partition which i have to delete daily to keep it at 99%) ..im not sure what i can delete to make room...although if i go to > /var/tmp theres a dir thats called "temproot" ..i think it was from when i CVS the new 4.2 src..and installed....can i delete this dir??? this is the dir structure under /var > > account/ crash/ games/ msgs/ rwho/ yp/ > at/ cron/ log/ preserve/ spool/ > backups/ db/ mail/ run/ tmp/ > > if anyone has any suggestions.... they would be greatly appreciated..... Do this: cd /var du -s * This should give you an idea of which directories are consuming the space and let you prune accordingly. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 5:42:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from front002.cluster1.charter.net (outbound.charter.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id A806A37B404 for ; Sun, 7 Jan 2001 05:42:20 -0800 (PST) Received: from [24.217.145.132] (HELO dave) by front002.cluster1.charter.net (CommuniGate Pro SMTP 3.3.2) with SMTP id 35037308; Sun, 07 Jan 2001 08:42:20 -0500 From: Dave Uhring To: "B" , Subject: Re: /var drive space problem Date: Sun, 7 Jan 2001 07:42:19 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" References: <001001c078ac$67228f00$0100a8c0@loqtis> In-Reply-To: <001001c078ac$67228f00$0100a8c0@loqtis> MIME-Version: 1.0 Message-Id: <01010707421900.00345@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday 07 January 2001 07:19, B wrote: > > Hello, > This probably isnt the place to be posting this question BUT...ive > always gottin good advise from this mailing list so here goes > nothing............ i have a recently upgraded FreeBSD 4.2 from > 4.1...and my problem is that im runing out of space on the /var > partition (i recieve alot of system mail in that partition which i > have to delete daily to keep it at 99%) ...im not sure what i can > delete to make room...although if i go to /var/tmp theres a dir > thats called "temproot" ..i think it was from when i CVS the new 4.2 > src..and installed....can i delete this dir??? this is the dir > structure under /var > > account/ crash/ games/ msgs/ rwho/ > yp/ at/ cron/ log/ > preserve/ spool/ backups/ db/ mail/ > run/ tmp/ > > if anyone has any suggestions.... they would be greatly > appreciated..... > > thanx in advance > Brent # mv /var/mail /usr/mail # ln -s /usr/mail /var/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 6: 1:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.sacoriver.net (dilbert.mix-net.net [216.64.56.4]) by hub.freebsd.org (Postfix) with ESMTP id 0328237B400 for ; Sun, 7 Jan 2001 06:01:02 -0800 (PST) Received: from loqtis (dsl-156.sacoriver.net [64.31.104.157]) by dilbert.sacoriver.net (8.9.3/8.9.0) with SMTP id JAA16349 for ; Sun, 7 Jan 2001 09:01:00 -0500 (EST) Message-ID: <004801c078b2$572331d0$0100a8c0@loqtis> From: "B" To: Subject: /var drive space problem Date: Sun, 7 Jan 2001 09:01:31 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0045_01C07888.6DBBBF40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0045_01C07888.6DBBBF40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I wanna thank you peoples for your speedy replies.....I have 1 = thing to say YOU GUYS ARE AWESOME!!!!!!!!!!!!! Thanx Brent ------=_NextPart_000_0045_01C07888.6DBBBF40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    I wanna thank = you peoples=20 for your speedy replies.....I have  1 thing to say
 
 
YOU GUYS ARE = AWESOME!!!!!!!!!!!!!
 
Thanx
Brent
------=_NextPart_000_0045_01C07888.6DBBBF40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 6:57:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id C90D737B7B6 for ; Sun, 7 Jan 2001 06:46:31 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA07662; Sun, 7 Jan 2001 06:46:23 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda07660; Sun Jan 7 06:46:17 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.1/8.9.1) id f07EkCM00582; Sun, 7 Jan 2001 06:46:12 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpduLa580; Sun Jan 7 06:45:34 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f07EjWe54252; Sun, 7 Jan 2001 06:45:32 -0800 (PST) Message-Id: <200101071445.f07EjWe54252@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdG54245; Sun Jan 7 06:45:03 2001 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.2-RELEASE X-Sender: cy To: Gordon Tetlow Cc: B , freebsd-stable@FreeBSD.ORG Subject: Re: /var drive space problem In-reply-to: Your message of "Sun, 07 Jan 2001 05:41:46 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Jan 2001 06:45:01 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Go rdon Tetlow writes: > On Sun, 7 Jan 2001, B wrote: > > > i have a recently upgraded FreeBSD 4.2 from 4.1...and my problem is that im > runing out of space on the /var partition (i recieve alot of system mail in > that partition which i have to delete daily to keep it at 99%) ..im not sure > what i can delete to make room...although if i go to > > /var/tmp theres a dir thats called "temproot" ..i think it was from w > hen i CVS the new 4.2 src..and installed....can i delete this dir??? this is > the dir structure under /var > > > > account/ crash/ games/ msgs/ rwho/ > yp/ > > at/ cron/ log/ preserve/ spool/ > > backups/ db/ mail/ run/ tmp/ > > > > if anyone has any suggestions.... they would be greatly appreciated..... > > Do this: > cd /var > du -s * > > This should give you an idea of which directories are consuming the space > and let you prune accordingly. My favourite approach, assuming you've installed the xdu port, is, du -k . | xdu This saves me from recursing through what I think might be the offending directory tree, reducing a 1-5 minute job, depending on how far down the tree the problem is, down to mere seconds. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 9:45:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id CFD0437B6A0 for ; Sun, 7 Jan 2001 09:41:24 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.20 #1) id 14FJoo-000BLE-00; Sun, 07 Jan 2001 17:41:22 +0000 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.1/8.11.1) id f07HfMK06373; Sun, 7 Jan 2001 17:41:22 GMT (envelope-from ben) Date: Sun, 7 Jan 2001 17:41:22 +0000 From: Ben Smithurst To: B Cc: freebsd-stable@freebsd.org Subject: Re: /var drive space problem Message-ID: <20010107174121.A85794@strontium.scientia.demon.co.uk> References: <001001c078ac$67228f00$0100a8c0@loqtis> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001001c078ac$67228f00$0100a8c0@loqtis> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG B wrote: > /var/tmp theres a dir thats called "temproot" ..i think it was from > when i CVS the new 4.2 src..and installed....can i delete this dir??? > this is the dir structure under /var That's from mergemaster, and yes, you can delete it. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 10:13:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dtcnj.com (dtcnj.com [198.93.66.41]) by hub.freebsd.org (Postfix) with ESMTP id 4582437B402 for ; Sun, 7 Jan 2001 10:13:42 -0800 (PST) Received: from localhost (jovens@localhost) by dtcnj.com (8.11.1/8.11.1) with ESMTP id f07IDV864966; Sun, 7 Jan 2001 13:13:31 -0500 (EST) Date: Sun, 7 Jan 2001 13:13:30 -0500 (EST) From: Justin Ovens To: stable@freebsd.org Cc: evilicey@lostworld.net Subject: CVSUP from 4.1.1-RELEASE to 4.2-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 I CVSup'ed a machine about 2 days again and now it seems when you telnet to it somtimes it will reboot itself, can anyone give me any pointers? I don't see anything in the logs that would help. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Justin Ovens (evilicey@lostworld.net) System/Network Administrator http://www.lostworld.net -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 11:21:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id BFF0537B400 for ; Sun, 7 Jan 2001 11:21:05 -0800 (PST) Received: from grolsch.ai (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 925954D for ; Sun, 7 Jan 2001 15:21:02 -0400 (AST) Date: Sun, 07 Jan 2001 15:21:02 -0400 From: "Jeroen C. van Gelderen" To: freebsd-stable@FreeBSD.ORG Subject: Intel PRO/100+ driver or hardware? Message-ID: <128310000.978895262@grolsch.ai> X-Mailer: Mulberry/2.0.6b2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope this isn't too off-topic for this list but I'm experiencing a rather strange problem. I've been searching the various mailing lists and websites for information but to no avail. I've included all information that I know to extract. I may miss some because I've tried a lot of different things in the past 24 hours :-( I'm keeping the machines around in the exact same configuration so I can extract more data if needed... I have two identical machines (Asus/Athlon with Intel PRO/100+ NICs). For the record, one machine is running a recent 4-STABLE and one is running and older 4.0-STABLE. I've tried a recent 4-STABLE kernel on both though, so I don't think this difference is significant. I noticed my problem when I tried to upgrade the 4.0-STABLE box with an NFS installworld. It would consistently hang after a short while. Further investigation showed that *every* TCP connection to or from this box stalls after transferring somewhere between 1MB and 20MB of data. (Tested with NFS, scp, etc). As the machine is handling small transactions most of the time I hadn't noticed this, until now :-( I tried to reproduce the problem on the 4.2-STABLE box wihtout sucess, until I finally realized that the problematic box is connected to a hub(10) and the 4.2-STABLE box to a switch (10/100). Either box has it's TCP connections stalled when connected to the hub and not when connected to the switch. I'd normally expect the hub to be dud, except that only machines with Intel PRO/100+ NICs seem to have a problem with it. None of the other machines that are connected to the hub are be affected. Moreover, a tcpdump on both sides of a stalled TCP connection seems to indicate that no packets get lost. I do an scp on hayek (problematic machine) to fetch a file from keynes. It looks like hayek simply stops responding to incoming packets and the TCP connection stalls until keynes gives up and sends RST. I've stuck both tcpdumps for hayek# scp me@keynes.ai:./bla.tgz /dev/null at http://vangelderen.org/~gelderen/tcpdump-hayek (problematic machine) http://vangelderen.org/~gelderen/tcpdump-keynes (has the file) If someone with a clue could have a look over them? I'm sure some netstat information could be useful but I don't know which bits to include. My tentative conclusion is that the Intel NICs don't work with my hub, even though they should. As my hub seems to work with other cards, I'm suspecting an Intel PRO/100+ specific problem. I can't determine whether it is a hardware or a software problem though :-( Anybody care to point out the obvious bits I've missed? TIA, Jeroen ====8<====8<====8<====8<====8<====8<====8<====8<==== FreeBSD hayek.ai 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Jun 9 18:49:08 AST 2000 gelderen@hayek.ai:/usr/src/sys/compile/ISSUER i386 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #0: Fri Jun 9 18:49:08 AST 2000 gelderen@hayek.ai:/usr/src/sys/compile/ISSUER Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (650.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ff AMD Features=0xc0400000 real memory = 268419072 (262128K bytes) avail memory = 258453504 (252396K bytes) Preloaded elf kernel "kernel" at 0xc0277000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 12 pci0: at 4.3 irq 12 pci0: at 10.0 irq 10 fxp0: port 0xa000-0xa03f mem 0xe1800000-0xe18fffff,0xe2000000-0xe2000fff irq 11 at device 12.0 on pci0 fxp0: Ethernet address 00:d0:b7:74:87:2b pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.8 ad0: 19470MB [39560/16/63] at ata0-master using UDMA66 ad2: 19470MB [39560/16/63] at ata1-master using UDMA33 Mounting root from ufs:/dev/ad0s1a vinum: loaded vinum: reading configuration from /dev/ad2s1h vinum: updating configuration from /dev/ad2s1f vinum: updating configuration from /dev/ad2s1g vinum: updating configuration from /dev/ad2s1e vinum: updating configuration from /dev/ad0s1h vinum: updating configuration from /dev/ad0s1g vinum: updating configuration from /dev/ad0s1f vinum: updating configuration from /dev/ad0s1e ====8<====8<====8<====8<====8<====8<====8<====8<==== fxp0: flags=8843 mtu 1500 inet 209.88.68.42 netmask 0xffffff00 broadcast 209.88.68.255 ether 00:d0:b7:74:87:2b media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 ====8<====8<====8<====8<====8<====8<====8<====8<==== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 12: 6: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id EB68537B402 for ; Sun, 7 Jan 2001 12:05:45 -0800 (PST) Received: from mail.de.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id VAA28628; Sun, 7 Jan 2001 21:05:44 +0100 (MET) (envelope-from Helge.Oldach@de.origin-it.com) Received: from smtprelay-de1.origin-it.com(172.16.188.53) by gw-nl1.origin-it.com via mwrap (4.0a) id xma028626; Sun, 7 Jan 01 21:05:44 +0100 Received: from mailhub.de.origin-it.com (mailhub.de.origin-it.com [172.16.189.20]) by mail.de.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id VAA10972; Sun, 7 Jan 2001 21:05:43 +0100 (MET) Received: from galaxy.de.cp.philips.com (galaxy.de.cp.philips.com [130.143.166.29]) by mailhub.de.origin-it.com (8.11.1/8.11.1/hmo23oct00) with ESMTP id f07K5eY97794; Sun, 7 Jan 2001 21:05:41 +0100 (CET) (envelope-from Helge.Oldach@de.origin-it.com) Received: (from hmo@localhost) by galaxy.de.cp.philips.com (8.9.3/8.9.3/hmo14aug98) id VAA06959; Sun, 7 Jan 2001 21:05:40 +0100 (MET) Message-Id: <200101072005.VAA06959@galaxy.de.cp.philips.com> Subject: Re: /var drive space problem In-Reply-To: <001001c078ac$67228f00$0100a8c0@loqtis> from B at "Jan 7, 2001 8:19: 0 am" To: brentb@loa.com (B) Date: Sun, 7 Jan 2001 21:05:39 +0100 (MET) Cc: freebsd-stable@freebsd.org From: Helge Oldach X-Address: Atos Origin, Billstrasse 80, D-20539 Hamburg, Germany X-Phone: +49 40 7886 464, Fax: +49 40 7886 235, Mobile: +49 172 4515513 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 B: >/var/tmp theres a dir thats called "temproot" ..i think it was from when i CVS the new 4.2 src..and installed....can i delete this dir??? Definitely. This is created by mergemaster and should have gone anyway if you'd answered his questions correctly. Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 13:40:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.com (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 4D99137B402 for ; Sun, 7 Jan 2001 13:40:36 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.com (Postfix) with ESMTP id A335E177E9F for ; Sun, 7 Jan 2001 15:45:32 -0600 (CST) Message-ID: <002901c078f3$26910c40$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Subject: IPFW Date: Sun, 7 Jan 2001 15:45:28 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know if this is for -questions or -stable so let me know if its the wrong place, but what level does ipfw log to and can I change the facility to make it log to say local4 or so. I want to log all ipfw deny's into its own log file separate from /var/log/security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 13:58:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from epsilon.lucida.ca (epsilon.lucida.ca [216.95.146.6]) by hub.freebsd.org (Postfix) with SMTP id 0ECB337B400 for ; Sun, 7 Jan 2001 13:58:33 -0800 (PST) Received: (qmail 18549 invoked by uid 1000); 7 Jan 2001 21:58:31 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jan 2001 21:58:31 -0000 Date: Sun, 7 Jan 2001 16:58:30 -0500 (EST) From: Matt Heckaman X-X-Sender: To: B Cc: Subject: Re: /var drive space problem In-Reply-To: <001001c078ac$67228f00$0100a8c0@loqtis> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 7 Jan 2001, B wrote: ... : if anyone has any suggestions.... they would be greatly appreciated..... *sigh* My advice is for the default partition size of /var to be upped to a more reasonable number. Too many people fall into this trap without realizing just what goes into /var. (I know I did the first time I installed FreeBSD, was used to Linux's monolithic / partition.) This a the world of 20+ GB hard drives for under 200$ Canadian. There really is no reason for the default /var to be at 20 Mb (last I checked). I know that just me alone on a workstation can easily end up with more mail than that. We aren't talking server configs where "the admin should know better" - we're talking every-day desktop usage. I set my /var at 150 Mb, which always has worked fine for me long as I clear out logfiles here and there.. This isn't a flame, just wondering why this is still the same :) Matt * Matt Heckaman - mailto:matt@lucida.ca http://www.lucida.ca/pgp * * GPG fingerprint - 53CA 8320 C8F6 32ED 9DDF 036E 3171 C093 4AD3 1364 * -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://www.lucida.ca/pgp iD8DBQE6WOaHMXHAk0rTE2QRAuieAKCNr/lUbesKUaFdLslK8F5+9avAfgCfYZ3K 1pLkIw5LAOj/sRNbmqeM1u0= =stWv -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 14:13:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zogbe.tasam.com (hc6526bd1.dhcp.vt.edu [198.82.107.209]) by hub.freebsd.org (Postfix) with ESMTP id 9199237B69D for ; Sun, 7 Jan 2001 14:13:17 -0800 (PST) Received: from battleship (hc6526bd1.dhcp.vt.edu [198.82.107.209]) by zogbe.tasam.com (8.11.1/8.11.1) with SMTP id f07MDEX04199; Sun, 7 Jan 2001 17:13:15 -0500 (EST) Message-ID: <002701c078f7$086b9f60$0b2d2d0a@fireduck.com> From: "Joe Gleason" To: "Matt Heckaman" , "B" Cc: References: Subject: Re: /var drive space problem Date: Sun, 7 Jan 2001 17:13:14 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree that /var should be bigger. How about something like this: In sysinstall if the user selects "auto defaults for all" do: VarSize=FreePartitionSpace * 0.10 If VarSize < 20M then VarSize = 20M If VarSize > 1024M then VarSize = 1024M I think a percent with a max and min is a good solution that will work well on systems with alot of mail/log traffic as well as on 170mb drives people find in their basement. Joe Gleason ----- Original Message ----- From: "Matt Heckaman" To: "B" Cc: Sent: Sunday, January 07, 2001 4:58 PM Subject: Re: /var drive space problem > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sun, 7 Jan 2001, B wrote: > ... > : if anyone has any suggestions.... they would be greatly appreciated..... > > *sigh* My advice is for the default partition size of /var to be upped to > a more reasonable number. Too many people fall into this trap without > realizing just what goes into /var. (I know I did the first time I > installed FreeBSD, was used to Linux's monolithic / partition.) > > This a the world of 20+ GB hard drives for under 200$ Canadian. There > really is no reason for the default /var to be at 20 Mb (last I checked). > > I know that just me alone on a workstation can easily end up with more > mail than that. We aren't talking server configs where "the admin should > know better" - we're talking every-day desktop usage. I set my /var at 150 > Mb, which always has worked fine for me long as I clear out logfiles here > and there.. > > This isn't a flame, just wondering why this is still the same :) > > Matt > > * Matt Heckaman - mailto:matt@lucida.ca http://www.lucida.ca/pgp * > * GPG fingerprint - 53CA 8320 C8F6 32ED 9DDF 036E 3171 C093 4AD3 1364 * > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.4 (FreeBSD) > Comment: http://www.lucida.ca/pgp > > iD8DBQE6WOaHMXHAk0rTE2QRAuieAKCNr/lUbesKUaFdLslK8F5+9avAfgCfYZ3K > 1pLkIw5LAOj/sRNbmqeM1u0= > =stWv > -----END PGP SIGNATURE----- > > > > > 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 Sun Jan 7 15: 6:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from backup.safepages.com (unknown [216.127.146.2]) by hub.freebsd.org (Postfix) with ESMTP id 9EDB337B400 for ; Sun, 7 Jan 2001 15:06:19 -0800 (PST) Received: from kursk.dyndns.org (1Cust200.tnt1.florence.al.da.uu.net [63.29.244.200]) by backup.safepages.com (Postfix) with ESMTP id 03E6D70BCF for ; Sun, 7 Jan 2001 23:01:21 +0000 (GMT) Received: (from kursk@localhost) by kursk.dyndns.org (8.9.3/8.9.3) id HAA00333; Sat, 6 Jan 2001 07:25:15 -0600 (CST) (envelope-from kursk) Date: Sat, 6 Jan 2001 07:25:15 -0600 (CST) Message-Id: <200101061325.HAA00333@kursk.dyndns.org> To: stable@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: http://www.freebsd.org/handbook/makeworld.html X-Mailer: Lynx, Version 2.8.3rel.1 From: roholm@vei.net Subject: http://www.freebsd.org/handbook/makeworld.html Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 15:30:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from backup.safepages.com (unknown [216.127.146.2]) by hub.freebsd.org (Postfix) with ESMTP id EA53837B400 for ; Sun, 7 Jan 2001 15:30:36 -0800 (PST) Received: from kursk.dyndns.org (1Cust200.tnt1.florence.al.da.uu.net [63.29.244.200]) by backup.safepages.com (Postfix) with ESMTP id 8CAE670DCE for ; Sun, 7 Jan 2001 23:24:31 +0000 (GMT) Received: (from kursk@localhost) by kursk.dyndns.org (8.9.3/8.9.3) id RAA01678; Sun, 7 Jan 2001 17:00:59 -0600 (CST) (envelope-from kursk) Date: Sun, 7 Jan 2001 17:00:59 -0600 (CST) Message-Id: <200101072300.RAA01678@kursk.dyndns.org> To: stable@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: file://localhost/usr/share/doc/handbook/makeworld.html X-Mailer: Lynx, Version 2.8.3rel.1 From: roholm@vei.net Subject: subscribe Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 15:42:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id DEFD537B698 for ; Sun, 7 Jan 2001 15:40:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f07NemZ74202; Sun, 7 Jan 2001 17:40:48 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101072340.f07NemZ74202@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Jeroen C. van Gelderen" Cc: freebsd-stable@FreeBSD.ORG, dkelly@grumpy.dyndns.org Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: Message from "Jeroen C. van Gelderen" of "Sun, 07 Jan 2001 15:21:02 -0400." <128310000.978895262@grolsch.ai> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Jan 2001 17:40:48 -0600 From: David Kelly Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeroen C. van Gelderen" writes: > My tentative conclusion is that the Intel NICs don't work with my hub, even > though they should. As my hub seems to work with other cards, I'm > suspecting an Intel PRO/100+ specific problem. I can't determine whether it > is a hardware or a software problem though :-( > > Anybody care to point out the obvious bits I've missed? I've seen "impossible" network problems like this traced to a bad ethernet cable. One system ran fine for a year until I had to sit in front of it for 5 mintues. Problem was its "CAT 5" cable was connected 1:1, and not with the wires properly paired. -- David Kelly N4HHE, dkelly@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 Sun Jan 7 15:57: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.com (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 2718937B400 for ; Sun, 7 Jan 2001 15:56:49 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.com (Postfix) with ESMTP id 65BFF177E9F; Sun, 7 Jan 2001 18:01:46 -0600 (CST) Message-ID: <00c901c07906$2df88400$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Jeroen C. van Gelderen" , "David Kelly" Cc: , References: <200101072340.f07NemZ74202@grumpy.dyndns.org> Subject: Re: Intel PRO/100+ driver or hardware? Date: Sun, 7 Jan 2001 18:01:41 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had a problem like this also with the cabling, where it worked fine with a 10mbps card but the 100mbps card would detect 100, but only really work at 10mbps(due to bad wiring/bad cabling). Are the rest of your cards that do work 10mbps? > > Anybody care to point out the obvious bits I've missed? > > I've seen "impossible" network problems like this traced to a bad > ethernet cable. One system ran fine for a year until I had to sit in > front of it for 5 mintues. Problem was its "CAT 5" cable was connected > 1:1, and not with the wires properly paired. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 17:46:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zeus.foote.com.au (zeus.foote.com.au [203.32.153.21]) by hub.freebsd.org (Postfix) with ESMTP id 0F8D837B400 for ; Sun, 7 Jan 2001 17:46:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zeus.foote.com.au (8.11.1/8.11.1) with ESMTP id f081kEv72723; Mon, 8 Jan 2001 12:16:14 +1030 (CST) (envelope-from chris@zeus.foote.com.au) Date: Mon, 8 Jan 2001 12:16:14 +1030 (CST) From: Chris Foote X-X-Sender: To: "Jeroen C. van Gelderen" Cc: Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: <128310000.978895262@grolsch.ai> 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, 7 Jan 2001, Jeroen C. van Gelderen wrote: > I noticed my problem when I tried to upgrade the 4.0-STABLE box with an NFS > installworld. It would consistently hang after a short while. Further > investigation showed that *every* TCP connection to or from this box stalls > after transferring somewhere between 1MB and 20MB of data. (Tested with > NFS, scp, etc). As the machine is handling small transactions most of the > time I hadn't noticed this, until now :-( > > > > My tentative conclusion is that the Intel NICs don't work with my hub, even > though they should. As my hub seems to work with other cards, I'm > suspecting an Intel PRO/100+ specific problem. I can't determine whether it > is a hardware or a software problem though :-( These symptoms sound like they're caused by duplex mismatch problems. Try forcing half or full-duplex options and test again - i.e. use media and mediaopt flags in your /etc/rc.conf. Available values for these are in `man fxp`. Chris Foote SE Net Technical Manager 222 Grote Street SE Network Access Adelaide SA 5000 e-mail chris@senet.com.au Australia phone : (08) 8221 5221 PGP Public Key available from fax: (08) 8221 5220 http://www.senet.com.au/PGP support: (08) 8221 5792 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 18: 1:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id B276437B69B for ; Sun, 7 Jan 2001 18:00:05 -0800 (PST) Received: from grolsch.ai (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 11D3F63; Sun, 7 Jan 2001 22:00:03 -0400 (AST) Date: Sun, 07 Jan 2001 22:00:02 -0400 From: "Jeroen C. van Gelderen" To: "David W. Chapman Jr." , David Kelly Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? Message-ID: <271170000.978919202@grolsch.ai> In-Reply-To: <00c901c07906$2df88400$931576d8@inethouston.net> X-Mailer: Mulberry/2.0.6b2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Sunday, January 07, 2001 18:01:41 -0600 "David W. Chapman Jr." wrote: > I've had a problem like this also with the cabling, where it worked fine > with a 10mbps card but the 100mbps card would detect 100, but only really > work at 10mbps(due to bad wiring/bad cabling). Are the rest of your cards > that do work 10mbps? > >> > Anybody care to point out the obvious bits I've missed? >> >> I've seen "impossible" network problems like this traced to a bad >> ethernet cable. One system ran fine for a year until I had to sit in >> front of it for 5 mintues. Problem was its "CAT 5" cable was connected >> 1:1, and not with the wires properly paired. Ta for the suggestion, but I'm pretty sure the cables are okay. I've tried multiple sets and all of the cables work fine at 100Mbps FX when plugged into the switch but they don't work when plugged into a 10Mb hub :-( Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 7 18:15:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id E992F37B402 for ; Sun, 7 Jan 2001 18:14:35 -0800 (PST) Received: from grolsch.ai (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 1D9EC57; Sun, 7 Jan 2001 22:14:34 -0400 (AST) Date: Sun, 07 Jan 2001 22:14:34 -0400 From: "Jeroen C. van Gelderen" To: "David W. Chapman Jr." , David Kelly Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? Message-ID: <295980000.978920074@grolsch.ai> In-Reply-To: <00c901c07906$2df88400$931576d8@inethouston.net> X-Mailer: Mulberry/2.0.6b2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Sunday, January 07, 2001 18:01:41 -0600 "David W. Chapman Jr." wrote: > I've had a problem like this also with the cabling, where it worked fine > with a 10mbps card but the 100mbps card would detect 100, but only really > work at 10mbps(due to bad wiring/bad cabling). Are the rest of your cards > that do work 10mbps? It seems that the cards detect 10Mbps by themselves. To be sure I forced them to 10Mbps half duplex mode and the problem persisted. (The machines I'm talking to are at 10Mbps half duplex as well.) Additionally I tried different cables, without results. All cables work fine at 100FX connected to the switch but not at 10 when connected to the hub. The other cards connected to the hub are a mixture of 10 and 100 cards (3Com 905B, LinkSys LNE100TX, 3Com 509). All of these work fine. I'm still a bit puzzled. I would expect a duplex mismatch to cause packet loss and as shown in the tcpdump(1)s, no such loss seems to occur. Can a duplex mismatch or a bad cable indeed result in the dumps I included? Any tcpdump wizards out there? Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 0:17:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sigtrap.com (ip212-226-143-10.adsl.kpnqwest.fi [212.226.143.10]) by hub.freebsd.org (Postfix) with SMTP id 4067937B400 for ; Mon, 8 Jan 2001 00:16:58 -0800 (PST) Received: (qmail 11652 invoked from network); 8 Jan 2001 08:15:44 -0000 Received: from ip212-226-143-11.adsl.kpnqwest.fi (HELO sigtrap.com) (desti@212.226.143.11) by ip212-226-143-9.adsl.kpnqwest.fi with SMTP; 8 Jan 2001 08:15:44 -0000 Message-ID: <3A599400.A5A0CAE1@sigtrap.com> Date: Mon, 08 Jan 2001 10:18:40 +0000 From: Edvard Fagerholm X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Jeroen C. van Gelderen" Cc: freebsd-stable@freebsd.org Subject: Re: Intel PRO/100+ driver or hardware? References: <295980000.978920074@grolsch.ai> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The other cards connected to the hub are a mixture of 10 and 100 cards > (3Com 905B, LinkSys LNE100TX, 3Com 509). All of these work fine. Funny, as I've got a quite similar problem. During high network throughput (about 50mbit/s) one of my boxes just dies. This is why it always crashes when doing backups and I had to put the backup computer to 10mbit half-duplex mode to get it work... This box has 3 intel eepro NICs. I've tried switching NICs, cables and the switch (a HP procurve), but it doesn't help. The only thing that solves my problems is using some NICs other than the eepros... I really haven't tested, but I think I should check the amount of interrupts occuring on this box to check if it always fails at similar levels, afaik the BP6 ain't the most stable mobo out there. Edvard Fagerholm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 3:33:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from internethelp.ru (wh.internethelp.ru [212.113.112.145]) by hub.freebsd.org (Postfix) with ESMTP id D1AF637B400 for ; Mon, 8 Jan 2001 03:32:59 -0800 (PST) Received: from ibmka ([192.168.0.6]) by internethelp.ru (8.9.3/8.9.3) with SMTP id OAA59571; Mon, 8 Jan 2001 14:32:28 +0300 (MSK) Message-ID: <016901c07966$4c94a910$0600a8c0@ibmka.internethelp.ru> From: "Nickolay A. Kritsky" To: "David W. Chapman Jr." Subject: Re: IPFW Date: Mon, 8 Jan 2001 14:29:41 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: David W. Chapman Jr. To: freebsd-stable@FreeBSD.ORG Date: 8 января 2001 г. 0:41 Subject: IPFW >I don't know if this is for -questions or -stable so let me know if its the >wrong place, but what level does ipfw log to and can I change the facility >to make it log to say local4 or so. I want to log all ipfw deny's into its >own log file separate from /var/log/security > try this: 1) add following to your /etc/syslog.conf: !ipfw *.* /var/log/ipfw.log 2)#touch /var/log/ipfw.log NKritsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 3:58:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lamia.lf.net (lamia.LF.net [212.9.160.192]) by hub.freebsd.org (Postfix) with ESMTP id 5C6A637B402 for ; Mon, 8 Jan 2001 03:58:18 -0800 (PST) Received: by lamia.lf.net (Smail3.2.0.111/lamia.lf.net) via LF.net GmbH Internet Services for hub.freebsd.org id m14FawL-001Sq2C; Mon, 8 Jan 2001 12:58:17 +0100 (CET) To: freebsd-stable@freebsd.org Subject: Re: IPFW References: <016901c07966$4c94a910$0600a8c0@ibmka.internethelp.ru> Organization: LF.net GmbH X-URL: http://www.LF.net/ X-Face: iq-"D}ZS'It[NXourO#`D+JoJC>bZPU\xvX4Um\sR}_zUI?R: lt{Y/s1g[=5L/BHY@]NxB(D?&:tCwX@Vp:YJURe}$MDZ1&/v<`C+^AVc"s/&m`Mu#s| From: Norbert Koch Date: 08 Jan 2001 12:58:17 +0100 In-Reply-To: <016901c07966$4c94a910$0600a8c0@ibmka.internethelp.ru> Message-ID: Lines: 16 User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.2 (Persephone) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Nickolay A. Kritsky" writes: Hi! > 1) add following to your /etc/syslog.conf: > > !ipfw > *.* /var/log/ipfw.log > > 2)#touch /var/log/ipfw.log and don't forget to kill -HUP `cat /var/run/syslog.pid` norbert. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 4: 6:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apotheosis.org.za (apotheosis.org.za [137.158.128.27]) by hub.freebsd.org (Postfix) with ESMTP id 6143637B400 for ; Mon, 8 Jan 2001 04:05:41 -0800 (PST) Date: Mon, 8 Jan 2001 14:05:21 +0200 From: Matthew West To: stable@freebsd.org Subject: page faults on FreeBSD 4.2-STABLE Message-ID: <20010108140521.A23828@apotheosis.org.za> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I have a 4.2-STABLE machine which had been running fine until a recent cvsup and make world. The previous version was from around early December. FreeBSD 4.2-STABLE #0: Sun Jan 7 23:03:17 SAST 2001 The machine catches a trap 12 now and then, but I seem to be able to raise the chances significantly by running gimp-1.2 (installed from ports) - very strange. I'm running a vinum mirror volume with softupdates _disabled_ on the vinum volume. Here's the output from a crash dump: (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.0 (kgdb) core-file /var/crash/vmcore.0 SMP 2 cpus IdlePTD 3031040 initial pcb at 265940 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01f2cbb stack pointer = 0x10:0xe53dfef8 frame pointer = 0x10:0xe53dff04 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 499 (gimp) interrupt mask = net tty bio cam <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 32 done Uptime: 4m43s dumping to dev #da/0x20029, offset 128 dump 1023 1022 1021 1020 1019 1018 1017 1016 1015 1014 1013 1012 1011 1010 1009 1008 1007 1006 1005 1004 1003 1002 1001 1000 999 998 997 996 995 994 993 [ ... ] 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at ../../kern/kern_shutdown.c:469 469 if (dumping++) { (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:469 #1 0xc0145c0b in boot (howto=256) at ../../kern/kern_shutdown.c:309 #2 0xc0145fbc in poweroff_wait (junk=0xc024300f, howto=-449438752) at ../../kern/kern_shutdown.c:556 #3 0xc021a20f in trap_fatal (frame=0xe53dfeb8, eva=0) at ../../i386/i386/trap.c:951 #4 0xc0219ea5 in trap_pfault (frame=0xe53dfeb8, usermode=0, eva=0) at ../../i386/i386/trap.c:844 #5 0xc0219a3f in trap (frame={tf_fs = 24, tf_es = -449445872, tf_ds = -1012662256, tf_edi = 0, tf_esi = 0, tf_ebp = -448921852, tf_isp = -448921884, tf_ebx = -1014879872, tf_edx = 0, tf_ecx = 16777217, tf_eax = 411, tf_trapno = 12, tf_err = 0, tf_eip = -1071698757, tf_cs = 8, tf_eflags = 66054, tf_esp = 138129408, tf_ss = -449438752}) at ../../i386/i386/trap.c:443 #6 0xc01f2cbb in zalloci (z=0xc3822980) at ../../vm/vm_zone.h:87 #7 0xc0154733 in pipe (p=0xe5361be0, uap=0xe53dff80) at ../../vm/vm_zone.h:117 #8 0xc021a4d9 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077937480, tf_esi = 137187616, tf_ebp = -1077938004, tf_isp = -448921644, tf_ebx = 138129408, tf_edx = 136032223, tf_ecx = 137487536, tf_eax = 42, tf_trapno = 22, tf_err = 2, tf_eip = 675698356, tf_cs = 31, tf_eflags = 647, tf_esp = -1077938064, tf_ss = 47}) at ../../i386/i386/trap.c:1150 #9 0xc020899b in Xint0x80_syscall () cannot read proc at 0 Any ideas? I've included /var/run/dmesg.boot and my kernel configuration file as attachments. -- mwest@uct.ac.za --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Sun Jan 7 23:03:17 SAST 2001 mwest@casper2.cs.uct.ac.za:/usr/src/sys/compile/CASPER2 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (547.18-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387fbff real memory = 1073676288 (1048512K bytes) avail memory = 1042120704 (1017696K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02c5000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pcib3: at device 15.0 on pci1 pci2: on pcib3 ahc0: port 0x2000-0x20ff mem 0xf4100000-0xf4100fff irq 19 at device 12.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x2400-0x24ff mem 0xf4101000-0xf4101fff irq 19 at device 12.1 on pci0 aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: port 0x2800-0x283f mem 0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 21 at device 14.0 on pci0 fxp0: Ethernet address 00:90:27:e0:6c:d7 isab0: at device 18.0 on pci0 isa0: on isab0 pci0: at 18.1 pci0: at 18.2 irq 21 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x1040-0x104f at device 18.3 on pci0 pci0: at 20.0 pcib1: on motherboard pci3: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! pass3 at ahc0 bus 0 target 6 lun 0 pass3: Fixed Processor SCSI-2 device pass3: 3.300MB/s transfers Mounting root from ufs:/dev/da5s1a da5 at ahc1 bus 0 target 0 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 20.000MB/s transfers (20.000MHz, offset 15) da5: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) WARNING: / was not properly dismounted vinum: loaded vinum: reading configuration from /dev/da1e vinum: updating configuration from /dev/da2s1e vinum: updating configuration from /dev/da0e --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=CASPER2 machine i386 cpu I686_CPU ident CASPER2 maxusers 512 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options NFS #Network Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options QUOTA #enable disk quotas options TCP_RESTRICT_RST #restrict emission of TCP RST #options DDB # ipfirewall options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus0 # SCSI bus (required) device scbus1 # SCSI bus (required) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) device da0 at scbus0 target 0 device da1 at scbus0 target 1 device da2 at scbus0 target 2 device da3 at scbus0 target 3 device da4 at scbus0 target 4 device da5 at scbus1 target 0 # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # PCI Ethernet NICs. device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter --HcAYCG3uE/tztfnV-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 4:57:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 079B737B400 for ; Mon, 8 Jan 2001 04:57:08 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Jan 2001 12:56:51 +0000 (GMT) To: Matthew West Cc: stable@freebsd.org, iedowse@maths.tcd.ie Subject: Re: page faults on FreeBSD 4.2-STABLE In-Reply-To: Your message of "Mon, 08 Jan 2001 14:05:21 +0200." <20010108140521.A23828@apotheosis.org.za> Date: Mon, 08 Jan 2001 12:56:51 +0000 From: Ian Dowse Message-ID: <200101081256.aa88963@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010108140521.A23828@apotheosis.org.za>, Matthew West writes: >#6 0xc01f2cbb in zalloci (z=0xc3822980) at ../../vm/vm_zone.h:87 >#7 0xc0154733 in pipe (p=0xe5361be0, uap=0xe53dff80) at ../../vm/vm_zone.h:11 >7 >#8 0xc021a4d9 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = -1077937480, tf_esi = 137187616, tf_ebp = -1077938004, > tf_isp = -448921644, tf_ebx = 138129408, tf_edx = 136032223, > tf_ecx = 137487536, tf_eax = 42, tf_trapno = 22, tf_err = 2, > tf_eip = 675698356, tf_cs = 31, tf_eflags = 647, tf_esp = -1077938064, > tf_ss = 47}) at ../../i386/i386/trap.c:1150 >#9 0xc020899b in Xint0x80_syscall () I've seen a similar trace on a machine here, but I haven't had a chance to analyse it properly yet. The source is from Dec 18: FreeBSD 4.2-STABLE #0: Mon Dec 18 19:35:28 GMT 2000 Just looking at it now, pipe_zone->zitems is NULL but zfreecnt != 0, so there is a clearly a bug somewhere... Ian #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469 #1 0xc015fc63 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:309 #2 0xc016002d in panic (fmt=0xc02b256f "page fault") at /usr/src/sys/kern/kern_shutdown.c:556 #3 0xc0271328 in trap_fatal (frame=0xe1fd9eb4, eva=0) at /usr/src/sys/i386/i386/trap.c:951 #4 0xc0270f99 in trap_pfault (frame=0xe1fd9eb4, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:844 #5 0xc0270aef in trap (frame={tf_fs = 24, tf_es = -533725168, tf_ds = 16, tf_edi = 0, tf_esi = 0, tf_ebp = -503472384, tf_isp = -503472416, tf_ebx = -1027344512, tf_edx = 0, tf_ecx = 50331649, tf_eax = 287, tf_trapno = 12, tf_err = 0, tf_eip = -1071425373, tf_cs = 8, tf_eflags = 66054, tf_esp = 0, tf_ss = -504081952}) at /usr/src/sys/i386/i386/trap.c:443 #6 0xc02358a3 in zalloci (z=0xc2c3f780) at /usr/src/sys/vm/vm_zone.h:87 #7 0xc016ec0f in pipe (p=0xe1f451e0, uap=0xe1fd9f80) at /usr/src/sys/vm/vm_zone.h:117 #8 0xc0271659 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 134549600, tf_ebp = -1077936952, tf_isp = -503472172, tf_ebx = 134578240, tf_edx = 5, tf_ecx = -1077938316, tf_eax = 42, tf_trapno = 12, tf_err = 2, tf_eip = 671667916, tf_cs = 31, tf_eflags = 647, tf_esp = -1077938404, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1150 #9 0xc025c9bb in Xint0x80_syscall () cannot read proc at 0 (kgdb) p *pipe_zone $4 = {zlock = {lock_data = 50331649}, zitems = 0x0, zfreecnt = 287, zfreemin = 25, znalloc = 115851, zkva = 412, zpagecount = 0, zpagemax = 128, zmax = 0, ztotal = 306, zsize = 160, zalloc = 4, zflags = 0, zallocflag = 2, zobj = 0x0, zname = 0xc02943a0 "PIPE", znext = 0xc2bd7380} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 5:56:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.newst.irs.ru (newst.irs.ru [212.164.94.1]) by hub.freebsd.org (Postfix) with ESMTP id EB87437B6AB for ; Mon, 8 Jan 2001 05:54:47 -0800 (PST) Received: from lark.nsk.bsgdesign.com (lark.nsk.bsgdesign.com [192.168.3.21]) by mail.newst.irs.ru (8.11.1/8.11.0) with ESMTP id f08DseX68036 for ; Mon, 8 Jan 2001 19:54:40 +0600 (NOVT) (envelope-from fjoe@newst.net) Date: Mon, 8 Jan 2001 19:54:19 +0600 (NOVT) From: Max Khon X-Sender: fjoe@localhost To: freebsd-stable@freebsd.org Subject: make buildkernel breakage on -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 hi, there! --- sys/modules/sk/Makefile.orig Mon Jan 8 19:46:47 2001 +++ sys/modules/sk/Makefile Mon Jan 8 19:46:31 2001 @@ -4,5 +4,6 @@ KMOD = if_sk SRCS = if_sk.c opt_bdg.h device_if.h bus_if.h pci_if.h SRCS += miibus_if.h +KMODDEPS = miibus .include /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 6:35:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.retec.net (apollo.retec.net [207.99.22.10]) by hub.freebsd.org (Postfix) with ESMTP id 4D99D37B6B8 for ; Mon, 8 Jan 2001 06:30:34 -0800 (PST) Received: from newken (dhcp113.retec.net [207.99.22.113]) by apollo.retec.net (8.9.3/8.9.0) with SMTP id JAA17562; Mon, 8 Jan 2001 09:24:36 -0500 (EST) Message-ID: <014101c0797f$84682880$711663cf@icarz.com> From: "Ken Menzel" To: "Joe Gleason" , "Matt Heckaman" , "B" Cc: References: <002701c078f7$086b9f60$0b2d2d0a@fireduck.com> Subject: Re: /var drive space problem Date: Mon, 8 Jan 2001 09:30:11 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I Agree, with Joe, but I also want to add I think the root file systems is also too small. The same type of formula could work. As for me I'll continue to set my favorite values for modern drives: 250M root, 2*mem swap, 250M /var, the rest /usr. 20M is way too small for modern drives, but we can't hard code this as many people stll are using old hardware to do jobs (such as nat boxs and ipfw etc). Ken > I agree that /var should be bigger. How about something like this: > > In sysinstall if the user selects "auto defaults for all" do: > VarSize=FreePartitionSpace * 0.10 > If VarSize < 20M then VarSize = 20M > If VarSize > 1024M then VarSize = 1024M > > I think a percent with a max and min is a good solution that will work well > on systems with alot of mail/log traffic as well as on 170mb drives people > find in their basement. > > Joe Gleason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 6:45:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tsolab.org (w132.z064220255.trn-nj.dsl.cnc.net [64.220.255.132]) by hub.freebsd.org (Postfix) with ESMTP id 816D137B404 for ; Mon, 8 Jan 2001 06:45:03 -0800 (PST) Received: from tsolab.org ([206.173.250.169]) by tsolab.org (8.8.8/8.8.8) with ESMTP id JAA29255; Mon, 8 Jan 2001 09:44:01 -0500 (EST) (envelope-from dan@tsolab.org) Message-ID: <3A59D273.CB58B4D0@tsolab.org> Date: Mon, 08 Jan 2001 09:45:07 -0500 From: Daniel Tso Reply-To: dan@tsolab.org X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Ken Menzel Cc: Joe Gleason , Matt Heckaman , B , freebsd-stable@FreeBSD.ORG Subject: Re: /var drive space problem References: <002701c078f7$086b9f60$0b2d2d0a@fireduck.com> <014101c0797f$84682880$711663cf@icarz.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I Agree, with Joe, but I also want to add I think the root file > systems is also too small. The same type of formula could work. As > for me I'll continue to set my favorite values for modern drives: 250M > root, 2*mem swap, 250M /var, the rest /usr. > 20M is way too small for modern drives, but we can't hard code this > as many people stll are using old hardware to do jobs (such as nat > boxs and ipfw etc). Why would you want a 250M root ? I always keep root small, usually the default 32M or 40M. It limits the possible damage and makes it much easier to restore. /tmp does not belong in root, but has its own partition, which can be 200M if you have it. The root partition should be as static as possible, IMHO. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 6:57:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 8372C37B402 for ; Mon, 8 Jan 2001 06:56:52 -0800 (PST) Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id PAA07538; Mon, 8 Jan 2001 15:53:20 +0100 Received: from bsf.alcatel.fr (mail.dit.sxb.bsf.alcatel.fr [155.132.205.115]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id PAA18366; Mon, 8 Jan 2001 15:52:19 +0100 (MET) Received: from mail (mail-bsf-alcatel-fr.dit.sxb.bsf.alcatel.fr [155.132.205.91]) by bsf.alcatel.fr (8.8.8+Sun/8.9.3) with ESMTP id PAA06842; Mon, 8 Jan 2001 15:55:36 +0100 (MET) Received: from barr (barr [172.25.60.80]) by mail (8.8.8+Sun/) with ESMTP id PAA06838; Mon, 8 Jan 2001 15:55:36 +0100 (MET) Received: from sxb.bsf.alcatel.fr by barr (8.9.3+Sun/ABS1.5) id PAA27670; Mon, 8 Jan 2001 15:56:43 +0100 (MET) Message-ID: <3A59D52B.2F4277EC@sxb.bsf.alcatel.fr> Date: Mon, 08 Jan 2001 15:56:43 +0100 From: Sebastien ROCHE X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: dan@tsolab.org Cc: Ken Menzel , Joe Gleason , Matt Heckaman , B , freebsd-stable@freebsd.org Subject: Re: /var drive space problem References: <002701c078f7$086b9f60$0b2d2d0a@fireduck.com> <014101c0797f$84682880$711663cf@icarz.com> <3A59D273.CB58B4D0@tsolab.org> Content-Type: multipart/alternative; boundary="------------8AE054E49F4D8D37B2E6FBA9" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------8AE054E49F4D8D37B2E6FBA9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, About this particular problem (size of /): My / partition is 32 Mb large. I had no problem until yesterday, when the make installkernel didn't work due to insufficient space. I think it's /modules which is bigger than it was (and the installation process makes a copy of it). Anyway it was difficult to have it work. I lost /stand and I put /lkm on /usr and I had to delete some binaries in /bin or /sbin that I don't use. Do you have an idea of what else I could put on /usr ? (not /bin /sbin /modules /boot /kernel /etc, hmmm there's not much more I think). Thanks for help, Sebastien Daniel Tso wrote: > > I Agree, with Joe, but I also want to add I think the root file > > systems is also too small. The same type of formula could work. As > > for me I'll continue to set my favorite values for modern drives: 250M > > root, 2*mem swap, 250M /var, the rest /usr. > > 20M is way too small for modern drives, but we can't hard code this > > as many people stll are using old hardware to do jobs (such as nat > > boxs and ipfw etc). > > Why would you want a 250M root ? I always keep root small, usually the > default 32M or 40M. It limits the possible damage and makes it much > easier to restore. > > /tmp does not belong in root, but has its own partition, which can be > 200M if you have it. > > The root partition should be as static as possible, IMHO. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message --------------8AE054E49F4D8D37B2E6FBA9 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all,

About this particular problem (size of /):

My / partition is 32 Mb large. I had no problem until yesterday, when the make installkernel didn't work due to insufficient space.
I think it's /modules which is bigger than it was (and the installation process makes a copy of it). Anyway it was difficult to have it work. I lost /stand and I put /lkm on /usr and I had to delete some binaries in /bin or /sbin that I don't use.

Do you have an idea of what else I could put on /usr ?  (not /bin /sbin /modules /boot /kernel /etc, hmmm there's not much more I think).

Thanks for help,

Sebastien
 
 

Daniel Tso wrote:

> I Agree, with Joe,  but I also want to add I think the root file
> systems is also too small.  The same type of formula could work.  As
> for me I'll continue to set my favorite values for modern drives: 250M
> root,  2*mem swap, 250M /var,  the rest /usr.
> 20M is way too small for modern drives,  but we can't hard code this
> as many people stll are using old hardware to do jobs (such as nat
> boxs and ipfw etc).

Why would you want a 250M root ? I always keep root small, usually the
default 32M or 40M. It limits the possible damage and makes it much
easier to restore.

/tmp does not belong in root, but has its own partition, which can be
200M if you have it.

The root partition should be as static as possible, IMHO.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

--------------8AE054E49F4D8D37B2E6FBA9-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 7:19:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.tue.le (p3EE3268C.dip.t-dialin.net [62.227.38.140]) by hub.freebsd.org (Postfix) with ESMTP id 5509A37B402 for ; Mon, 8 Jan 2001 07:19:19 -0800 (PST) Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by mail.tue.le (8.8.8/8.8.8) with ESMTP id QAA25864 for ; Mon, 8 Jan 2001 16:18:55 +0100 (CET) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.11.1/8.11.1) id f08FItr05939 for freebsd-stable@freebsd.org; Mon, 8 Jan 2001 16:18:55 +0100 (CET) (envelope-from thz) Date: Mon, 8 Jan 2001 16:18:55 +0100 From: Thomas Zenker To: freebsd-stable@freebsd.org Subject: SIGSEGV can be blocked!? Message-ID: <20010108161854.A3547@mezcal.tue.le> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG debugging a program I discovered a strange behaviour today: Blocking SIGSEGV with sigprocmask does really BLOCK it. I think, this is a bug. I discovered this because I wanted to provoke a core dump by a write to (int *)0, but the process got hung, ps -ax showed it constantly running. A SIGQUIT got it to dump core and gdb showed exactly my write to NULL. Probably the process gets occupied by repeatedly retrying the write to null?? this is on 4.2-STABLE from 21 of december any opinions? -- Thomas Zenker c/o Lennartz electronic GmbH Bismarckstrasse 136, D-72072 Tuebingen, Germany Phone: +49-(0)7071-93550 Email: thz@lennartz-electronic.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 7:19:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 5635E37B400 for ; Mon, 8 Jan 2001 07:19:34 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f08FLDi31948; Mon, 8 Jan 2001 09:21:13 -0600 (CST) (envelope-from jlemon) Date: Mon, 8 Jan 2001 09:21:13 -0600 (CST) From: Jonathan Lemon Message-Id: <200101081521.f08FLDi31948@prism.flugsvamp.com> To: jeroen@vangelderen.org, stable@freebsd.org Subject: Re: Intel PRO/100+ driver or hardware? X-Newsgroups: local.mail.freebsd-stable In-Reply-To: Organization: Cc: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Moreover, a tcpdump on both sides of a stalled TCP connection seems to >indicate that no packets get lost. I do an scp on hayek (problematic >machine) to fetch a file from keynes. It looks like hayek simply stops >responding to incoming packets and the TCP connection stalls until keynes >gives up and sends RST. > >I've stuck both tcpdumps for > hayek# scp me@keynes.ai:./bla.tgz /dev/null >at > http://vangelderen.org/~gelderen/tcpdump-hayek (problematic machine) > http://vangelderen.org/~gelderen/tcpdump-keynes (has the file) > >If someone with a clue could have a look over them? I'm sure some netstat >information could be useful but I don't know which bits to include. It looks like 'hayek' is refusing to accept one of the segments that 'keynes' is transmitting. The segment arrives at the machine, but 'hayek' never sends an ACK. I'd look at 'netstat -s' and see whether any of the 'bad checksum' counters are set, if so, then something is corrupting the packets. Does this happen even if you connect the machines back to back (with a crossover cable?) -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 7:25: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.retec.net (apollo.retec.net [207.99.22.10]) by hub.freebsd.org (Postfix) with ESMTP id 3276137B400 for ; Mon, 8 Jan 2001 07:24:38 -0800 (PST) Received: from newken (dhcp113.retec.net [207.99.22.113]) by apollo.retec.net (8.9.3/8.9.0) with SMTP id KAA18623; Mon, 8 Jan 2001 10:18:25 -0500 (EST) Message-ID: <039901c07987$06b142c0$711663cf@icarz.com> From: "Ken Menzel" To: "Sebastien ROCHE" , Cc: "Joe Gleason" , "Matt Heckaman" , "B" , References: <002701c078f7$086b9f60$0b2d2d0a@fireduck.com> <014101c0797f$84682880$711663cf@icarz.com> <3A59D273.CB58B4D0@tsolab.org> <3A59D52B.2F4277EC@sxb.bsf.alcatel.fr> Subject: Re: /var drive space problem Date: Mon, 8 Jan 2001 10:24:00 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0396_01C0795D.1D981740" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0396_01C0795D.1D981740 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Sebastion, /modules should not be that big, but try "du -hx /", my servers = have 34 Meg in the root filesystem. Make sure you don't have multiple = copies of the kernel, this is why when I build my roots I make them = 250M it's overkill, but hey I got 72G of space, and 35Gig per tape on = the backup I don't want to run out of space just because I build a = couple of kernels to play with! =20 Anyway the du command will show you where the space is used, be careful = not to delete anything needed to boot! However you can probably clean = up modules.old and old kernels and any junk in /root (root users home = directory). Ken ----------------------------------------------------- Ken Menzel ICQ# 9325188 www.icarz.com kenm@icarz.com ----- Original Message -----=20 From: Sebastien ROCHE=20 To: dan@tsolab.org=20 Cc: Ken Menzel ; Joe Gleason ; Matt Heckaman ; B ; = freebsd-stable@freebsd.org=20 Sent: Monday, January 08, 2001 9:56 AM Subject: Re: /var drive space problem Hi all,=20 About this particular problem (size of /):=20 My / partition is 32 Mb large. I had no problem until yesterday, when = the make installkernel didn't work due to insufficient space.=20 I think it's /modules which is bigger than it was (and the = installation process makes a copy of it). Anyway it was difficult to = have it work. I lost /stand and I put /lkm on /usr and I had to delete = some binaries in /bin or /sbin that I don't use.=20 Do you have an idea of what else I could put on /usr ? (not /bin = /sbin /modules /boot /kernel /etc, hmmm there's not much more I think).=20 Thanks for help,=20 Sebastien=20 =20 =20 Daniel Tso wrote:=20 > I Agree, with Joe, but I also want to add I think the root file=20 > systems is also too small. The same type of formula could work. = As=20 > for me I'll continue to set my favorite values for modern drives: = 250M=20 > root, 2*mem swap, 250M /var, the rest /usr.=20 > 20M is way too small for modern drives, but we can't hard code = this=20 > as many people stll are using old hardware to do jobs (such as nat = > boxs and ipfw etc).=20 Why would you want a 250M root ? I always keep root small, usually = the=20 default 32M or 40M. It limits the possible damage and makes it much=20 easier to restore.=20 /tmp does not belong in root, but has its own partition, which can = be=20 200M if you have it.=20 The root partition should be as static as possible, IMHO.=20 To Unsubscribe: send mail to majordomo@FreeBSD.org=20 with "unsubscribe freebsd-stable" in the body of the message ------=_NextPart_000_0396_01C0795D.1D981740 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Sebastion,
  /modules should not be that = big,  but=20 try "du -hx /",   my servers have 34 Meg in the root = filesystem. =20 Make sure you don't have multiple copies of the kernel,  this is = why when I=20 build my roots I make them 250M it's overkill, but hey I got 72G of = space, =20 and 35Gig per tape on the backup I don't want to run out of space just = because I=20 build a couple of kernels to play with! 
 
Anyway the du command will show you = where the space=20 is used, be careful not to delete anything needed to boot!  However = you can=20 probably clean up modules.old and old kernels and any junk in /root = (root users=20 home directory).
 
Ken
-----------------------------------------------------
Ken = Menzel =20 ICQ# 9325188
www.icarz.com  = kenm@icarz.com
----- Original Message -----
From:=20 Sebastien ROCHE
Sent: Monday, January 08, 2001 = 9:56=20 AM
Subject: Re: /var drive space=20 problem

Hi all,=20

About this particular problem (size of /):=20

My / partition is 32 Mb large. I had no problem until yesterday, = when the=20 make installkernel didn't work due to insufficient = space.
I=20 think it's /modules which is bigger than it was (and the installation = process=20 makes a copy of it). Anyway it was difficult to have it work. I lost = /stand=20 and I put /lkm on /usr and I had to delete some binaries in /bin or = /sbin that=20 I don't use.=20

Do you have an idea of what else I could put on /usr ?  (not = /bin=20 /sbin /modules /boot /kernel /etc, hmmm there's not much more I = think).=20

Thanks for help,=20

Sebastien
 
 =20

Daniel Tso wrote:=20

> I Agree, with Joe,  but I also = want to add=20 I think the root file
> systems is also too small.  The = same=20 type of formula could work.  As
> for me I'll continue = to set my=20 favorite values for modern drives: 250M
> root,  2*mem = swap,=20 250M /var,  the rest /usr.
> 20M is way too small for = modern=20 drives,  but we can't hard code this
> as many people = stll are=20 using old hardware to do jobs (such as nat
> boxs and ipfw = etc).=20

Why would you want a 250M root ? I always keep root small, = usually the=20
default 32M or 40M. It limits the possible damage and makes it = much=20
easier to restore.=20

/tmp does not belong in root, but has its own partition, which = can be=20
200M if you have it.=20

The root partition should be as static as possible, IMHO.=20

To Unsubscribe: send mail to majordomo@FreeBSD.org
with = "unsubscribe=20 freebsd-stable" in the body of the=20 message

------=_NextPart_000_0396_01C0795D.1D981740-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 7:54:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4FCE637B402 for ; Mon, 8 Jan 2001 07:54:02 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Jan 2001 15:53:58 +0000 (GMT) Date: Mon, 8 Jan 2001 15:53:57 +0000 From: David Malone To: Thomas Zenker Cc: freebsd-stable@freebsd.org Subject: Re: SIGSEGV can be blocked!? Message-ID: <20010108155357.A68700@walton.maths.tcd.ie> References: <20010108161854.A3547@mezcal.tue.le> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010108161854.A3547@mezcal.tue.le>; from thz@Lennartz-electronic.de on Mon, Jan 08, 2001 at 04:18:55PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 08, 2001 at 04:18:55PM +0100, Thomas Zenker wrote: > Blocking SIGSEGV with sigprocmask does really BLOCK it. > I think, this is a bug. I discovered this because I wanted to > provoke a core dump by a write to (int *)0, but the process got hung, > ps -ax showed it constantly running. A SIGQUIT got it to dump core and > gdb showed exactly my write to NULL. Probably the process gets > occupied by repeatedly retrying the write to null?? I think some programs catch signals for SIGSEGV and SIGBUS to do memory management things, so this is expected. If you want your program to core dump then call abort(). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 8:18:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from digital.csudsu.com (digital.csudsu.com [209.249.57.102]) by hub.freebsd.org (Postfix) with ESMTP id E159B37B6A4 for ; Mon, 8 Jan 2001 08:17:39 -0800 (PST) Received: by digital.csudsu.com (Postfix, from userid 1000) id A0A6622E01; Mon, 8 Jan 2001 08:17:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by digital.csudsu.com (Postfix) with ESMTP id 919571F001; Mon, 8 Jan 2001 08:17:44 -0800 (PST) Date: Mon, 8 Jan 2001 08:17:44 -0800 (PST) From: Stefan Molnar To: "Jeroen C. van Gelderen" Cc: Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: <128310000.978895262@grolsch.ai> 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 have noticed that the eepro does not like some hubs/switches. I have a netgear 8 port 10mb switch, and the eepro just goes to a crawl with the same things you see. I have tried over a dozen eepro cards (had this switch for almost 2 years), and countless ethernet cables. I bought a 4 port hub, connected the xover to the swtitch and the eepro on the hub, and bamf, those problems went away. The tulip cards that most of the eepros replaced worked very happly. Stefaq On Sun, 7 Jan 2001, Jeroen C. van Gelderen wrote: > > I hope this isn't too off-topic for this list but I'm experiencing a rather > strange problem. I've been searching the various mailing lists and websites > for information but to no avail. I've included all information that I know > to extract. I may miss some because I've tried a lot of different things in > the past 24 hours :-( I'm keeping the machines around in the exact same > configuration so I can extract more data if needed... > > I have two identical machines (Asus/Athlon with Intel PRO/100+ NICs). For > the record, one machine is running a recent 4-STABLE and one is running and > older 4.0-STABLE. I've tried a recent 4-STABLE kernel on both though, so I > don't think this difference is significant. > > I noticed my problem when I tried to upgrade the 4.0-STABLE box with an NFS > installworld. It would consistently hang after a short while. Further > investigation showed that *every* TCP connection to or from this box stalls > after transferring somewhere between 1MB and 20MB of data. (Tested with > NFS, scp, etc). As the machine is handling small transactions most of the > time I hadn't noticed this, until now :-( > > I tried to reproduce the problem on the 4.2-STABLE box wihtout sucess, > until I finally realized that the problematic box is connected to a hub(10) > and the 4.2-STABLE box to a switch (10/100). Either box has it's TCP > connections stalled when connected to the hub and not when connected to the > switch. > > I'd normally expect the hub to be dud, except that only machines with Intel > PRO/100+ NICs seem to have a problem with it. None of the other machines > that are connected to the hub are be affected. > > Moreover, a tcpdump on both sides of a stalled TCP connection seems to > indicate that no packets get lost. I do an scp on hayek (problematic > machine) to fetch a file from keynes. It looks like hayek simply stops > responding to incoming packets and the TCP connection stalls until keynes > gives up and sends RST. > > I've stuck both tcpdumps for > hayek# scp me@keynes.ai:./bla.tgz /dev/null > at > http://vangelderen.org/~gelderen/tcpdump-hayek (problematic machine) > http://vangelderen.org/~gelderen/tcpdump-keynes (has the file) > > If someone with a clue could have a look over them? I'm sure some netstat > information could be useful but I don't know which bits to include. > > My tentative conclusion is that the Intel NICs don't work with my hub, even > though they should. As my hub seems to work with other cards, I'm > suspecting an Intel PRO/100+ specific problem. I can't determine whether it > is a hardware or a software problem though :-( > > Anybody care to point out the obvious bits I've missed? > > TIA, > Jeroen > > ====8<====8<====8<====8<====8<====8<====8<====8<==== > > FreeBSD hayek.ai 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Jun 9 18:49:08 AST > 2000 gelderen@hayek.ai:/usr/src/sys/compile/ISSUER i386 > > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-STABLE #0: Fri Jun 9 18:49:08 AST 2000 > gelderen@hayek.ai:/usr/src/sys/compile/ISSUER > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD Athlon(tm) Processor (650.03-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 > > Features=0x183f9ff ,PAT,PSE36,MMX,FXSR> > AMD Features=0xc0400000 > real memory = 268419072 (262128K bytes) > avail memory = 258453504 (252396K bytes) > Preloaded elf kernel "kernel" at 0xc0277000. > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > pcib2: at device 1.0 on > pci0 > pci1: on pcib2 > isab0: at device 4.0 on pci0 > isa0: on isab0 > atapci0: port 0xd800-0xd80f at device 4.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 4.2 irq 12 > pci0: at 4.3 irq 12 > pci0: at 10.0 irq 10 > fxp0: port 0xa000-0xa03f mem > 0xe1800000-0xe18fffff,0xe2000000-0xe2000fff irq 11 at device 12.0 on pci0 > fxp0: Ethernet address 00:d0:b7:74:87:2b > pcib1: on motherboard > pci2: on pcib1 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > IP Filter: initialized. Default = pass all, Logging = enabled > IP Filter: v3.3.8 > ad0: 19470MB [39560/16/63] at ata0-master using UDMA66 > ad2: 19470MB [39560/16/63] at ata1-master using UDMA33 > Mounting root from ufs:/dev/ad0s1a > vinum: loaded > vinum: reading configuration from /dev/ad2s1h > vinum: updating configuration from /dev/ad2s1f > vinum: updating configuration from /dev/ad2s1g > vinum: updating configuration from /dev/ad2s1e > vinum: updating configuration from /dev/ad0s1h > vinum: updating configuration from /dev/ad0s1g > vinum: updating configuration from /dev/ad0s1f > vinum: updating configuration from /dev/ad0s1e > > ====8<====8<====8<====8<====8<====8<====8<====8<==== > > fxp0: flags=8843 mtu 1500 > inet 209.88.68.42 netmask 0xffffff00 broadcast 209.88.68.255 > ether 00:d0:b7:74:87:2b > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP > 10baseT/UTP > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > ====8<====8<====8<====8<====8<====8<====8<====8<==== > > > > 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 Jan 8 9:21: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hq1.tyfon.net (hq1.tyfon.net [217.27.162.35]) by hub.freebsd.org (Postfix) with ESMTP id A843C37B699 for ; Mon, 8 Jan 2001 09:20:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id A9C671C7DD for ; Mon, 8 Jan 2001 18:19:55 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id B376B1C5C9 for ; Mon, 8 Jan 2001 18:19:52 +0100 (CET) Date: Mon, 8 Jan 2001 18:19:52 +0100 (CET) From: Dan Larsson To: FreeBSD Stable List Subject: ssh issues after make world Message-ID: Organization: Tyfon Svenska AB X-NCC-NIC: DL1999-RIPE X-NCC-RegID: se.tyfon MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by hq1.tyfon.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before the make world I didn't have the below problem: % ssh remote-machine dsa_verify failed for server_host_key % It seems as the problem only appears with machines running non OpenSSH daemons, but that's just a guess. Anyone having these issues too? Regards +------ Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 GPG and PGP keys | finger dl@hq1.tyfon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 9:31: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from new.buzzit.com (unknown [206.80.217.164]) by hub.freebsd.org (Postfix) with ESMTP id 7B31C37B402 for ; Mon, 8 Jan 2001 09:30:40 -0800 (PST) Received: from localhost (gwood@localhost) by new.buzzit.com (8.9.3/8.9.3) with ESMTP id KAA46318; Mon, 8 Jan 2001 10:29:43 -0700 (MST) (envelope-from gwood@georgewood.net) Date: Mon, 8 Jan 2001 10:29:43 -0700 (MST) From: George Wood X-Sender: gwood@new.buzzit.com To: "Jeroen C. van Gelderen" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: <128310000.978895262@grolsch.ai> 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 had similar symptoms (with a cheap realtek 10/100 nic card) when one of the cards was not autonegotiating a full duplex connection with the switch. Small transfers and telnet sessions would generally work ok (although they were much slower than they should have been) unless there was a sudden burst (i.e. "find /" in a telnet session), at which point the connection would lock or stall. Sometimes the connection would come back, sometimes not. My solution on that box was to set the ifconfig "media" to 100baseTX and "mediaopt" to full-duplex. ("ifconfig -a" had previously indicated that autoselect was NOT picking 100mbps + full-duplex. Your ifconfig looks like it is picking 10mbps half-duplex, and you said you were plugged into a switch, so the situation looks a lot like mine.) The apparent explanation for the behavior was that for small or slow transfers, the switch (or nic) buffers would compensate for the inevitable collisions resulting from a mix of full- and half- duplex, but at some point the collision rate exceeds available buffers. Switch (and/or nic) quality may reveal itself here: a good 10/100 switch would have sufficient buffers to allow lots of large packets to move from a 100mbps fdx segment to a 10mbps half-duplex segment, but in my case performance was terrible on the segment with the realtek card until I forced it to 100 fdx. On Sun, 7 Jan 2001, Jeroen C. van Gelderen wrote: > Date: Sun, 07 Jan 2001 15:21:02 -0400 > From: Jeroen C. van Gelderen > To: freebsd-stable@FreeBSD.ORG > Subject: Intel PRO/100+ driver or hardware? > > > I hope this isn't too off-topic for this list but I'm experiencing a rather > strange problem. I've been searching the various mailing lists and websites > for information but to no avail. I've included all information that I know > to extract. I may miss some because I've tried a lot of different things in > the past 24 hours :-( I'm keeping the machines around in the exact same > configuration so I can extract more data if needed... > > I have two identical machines (Asus/Athlon with Intel PRO/100+ NICs). For > the record, one machine is running a recent 4-STABLE and one is running and > older 4.0-STABLE. I've tried a recent 4-STABLE kernel on both though, so I > don't think this difference is significant. > > I noticed my problem when I tried to upgrade the 4.0-STABLE box with an NFS > installworld. It would consistently hang after a short while. Further > investigation showed that *every* TCP connection to or from this box stalls > after transferring somewhere between 1MB and 20MB of data. (Tested with > NFS, scp, etc). As the machine is handling small transactions most of the > time I hadn't noticed this, until now :-( > > I tried to reproduce the problem on the 4.2-STABLE box wihtout sucess, > until I finally realized that the problematic box is connected to a hub(10) > and the 4.2-STABLE box to a switch (10/100). Either box has it's TCP > connections stalled when connected to the hub and not when connected to the > switch. > > I'd normally expect the hub to be dud, except that only machines with Intel > PRO/100+ NICs seem to have a problem with it. None of the other machines > that are connected to the hub are be affected. > > Moreover, a tcpdump on both sides of a stalled TCP connection seems to > indicate that no packets get lost. I do an scp on hayek (problematic > machine) to fetch a file from keynes. It looks like hayek simply stops > responding to incoming packets and the TCP connection stalls until keynes > gives up and sends RST. > > I've stuck both tcpdumps for > hayek# scp me@keynes.ai:./bla.tgz /dev/null > at > http://vangelderen.org/~gelderen/tcpdump-hayek (problematic machine) > http://vangelderen.org/~gelderen/tcpdump-keynes (has the file) > > If someone with a clue could have a look over them? I'm sure some netstat > information could be useful but I don't know which bits to include. > > My tentative conclusion is that the Intel NICs don't work with my hub, even > though they should. As my hub seems to work with other cards, I'm > suspecting an Intel PRO/100+ specific problem. I can't determine whether it > is a hardware or a software problem though :-( > > Anybody care to point out the obvious bits I've missed? > > TIA, > Jeroen > > ====8<====8<====8<====8<====8<====8<====8<====8<==== > > FreeBSD hayek.ai 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Jun 9 18:49:08 AST > 2000 gelderen@hayek.ai:/usr/src/sys/compile/ISSUER i386 > > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-STABLE #0: Fri Jun 9 18:49:08 AST 2000 > gelderen@hayek.ai:/usr/src/sys/compile/ISSUER > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD Athlon(tm) Processor (650.03-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 > > Features=0x183f9ff ,PAT,PSE36,MMX,FXSR> > AMD Features=0xc0400000 > real memory = 268419072 (262128K bytes) > avail memory = 258453504 (252396K bytes) > Preloaded elf kernel "kernel" at 0xc0277000. > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > pcib2: at device 1.0 on > pci0 > pci1: on pcib2 > isab0: at device 4.0 on pci0 > isa0: on isab0 > atapci0: port 0xd800-0xd80f at device 4.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 4.2 irq 12 > pci0: at 4.3 irq 12 > pci0: at 10.0 irq 10 > fxp0: port 0xa000-0xa03f mem > 0xe1800000-0xe18fffff,0xe2000000-0xe2000fff irq 11 at device 12.0 on pci0 > fxp0: Ethernet address 00:d0:b7:74:87:2b > pcib1: on motherboard > pci2: on pcib1 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > IP Filter: initialized. Default = pass all, Logging = enabled > IP Filter: v3.3.8 > ad0: 19470MB [39560/16/63] at ata0-master using UDMA66 > ad2: 19470MB [39560/16/63] at ata1-master using UDMA33 > Mounting root from ufs:/dev/ad0s1a > vinum: loaded > vinum: reading configuration from /dev/ad2s1h > vinum: updating configuration from /dev/ad2s1f > vinum: updating configuration from /dev/ad2s1g > vinum: updating configuration from /dev/ad2s1e > vinum: updating configuration from /dev/ad0s1h > vinum: updating configuration from /dev/ad0s1g > vinum: updating configuration from /dev/ad0s1f > vinum: updating configuration from /dev/ad0s1e > > ====8<====8<====8<====8<====8<====8<====8<====8<==== > > fxp0: flags=8843 mtu 1500 > inet 209.88.68.42 netmask 0xffffff00 broadcast 209.88.68.255 > ether 00:d0:b7:74:87:2b > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP > 10baseT/UTP > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > ====8<====8<====8<====8<====8<====8<====8<====8<==== > > > > 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 Jan 8 13:18:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 1C58E37B7B6 for ; Mon, 8 Jan 2001 13:17:34 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 3FC02177E9F for ; Mon, 8 Jan 2001 15:19:02 -0600 (CST) Message-ID: <008201c079b8$9d0b9820$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Subject: ISC-DHCP 2.0pl5 Date: Mon, 8 Jan 2001 15:18:58 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This version has been updated in the ports, I haven't seen whether it has been integrated into the source tree, the last I checked the source tree only had pl3. This should be one of the very last version. If it is not in -stable now what is the likelihood of it being merged into it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 14: 5:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id EE39837B82F for ; Mon, 8 Jan 2001 13:36:49 -0800 (PST) Received: (qmail 29308 invoked from network); 8 Jan 2001 21:36:44 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 8 Jan 2001 21:36:44 -0000 Message-ID: <3A5A32C5.99D17398@gactr.uga.edu> Date: Mon, 08 Jan 2001 16:36:05 -0500 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: 4.2-stable buildworld over nfs problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok... buildworld builds just fine when /usr/src is on the local disk. however, if i move that same src over to my NFS server (in this case, an Origin 2000 with IRIX 6.5.4). i have the following entry in my /etc/fstab fs2.servers.nat:/export/maint/freebsd/4.2-STABLE/src /usr/src nfs rw,nfsv3 2 2 with that, buildworld consistently fails (on all my machines) during /usr/src/gnu/usr.bin/groff what could be going on here? (this is using the latest cvs) -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 14: 5: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from saturn.home.ben.com (c1058885-a.bvrtn1.or.home.com [24.12.186.106]) by hub.freebsd.org (Postfix) with ESMTP id A3E3237B7F2 for ; Mon, 8 Jan 2001 13:32:46 -0800 (PST) Received: (from bjj@localhost) by saturn.home.ben.com (8.11.1/8.9.3) id f08LWhL18526; Mon, 8 Jan 2001 13:32:43 -0800 (PST) From: Ben Jackson Message-Id: <200101082132.f08LWhL18526@saturn.home.ben.com> Subject: Re: SIGSEGV can be blocked!? In-Reply-To: <20010108161854.A3547@mezcal.tue.le> from Thomas Zenker at "Jan 8, 2001 04:18:55 pm" To: Thomas Zenker Date: Mon, 8 Jan 2001 13:32:43 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (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 > Blocking SIGSEGV with sigprocmask does really BLOCK it. > I think, this is a bug. I discovered this because I wanted to > provoke a core dump by a write to (int *)0, but the process got hung, The instruction that caused the SEGV is going to restart after any handler runs because the handler may have mapped the page that caused the fault. On other operating systems you can block SEGV for purposes of asynchronous signals (ie `kill -SEGV') but not for synchronous signals. To quote from the Solaris sigprocmask manpage: Signals that are generated synchronously should not be masked. If such a signal is blocked and delivered, the receiving process is killed. and indeed a test program shows that you still get SEGV in that case. You can still shoot yourself in the foot with a SEGV handler that doesn't eliminate the fault. --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 14:23:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 3862F37B401 for ; Mon, 8 Jan 2001 14:23:30 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Jan 2001 22:23:18 +0000 (GMT) Date: Mon, 8 Jan 2001 22:23:16 +0000 From: David Malone To: Ian Dowse Cc: Matthew West , stable@freebsd.org Subject: Re: page faults on FreeBSD 4.2-STABLE Message-ID: <20010108222316.A10341@walton.maths.tcd.ie> References: <20010108140521.A23828@apotheosis.org.za> <200101081256.aa88963@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101081256.aa88963@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Mon, Jan 08, 2001 at 12:56:51PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 08, 2001 at 12:56:51PM +0000, Ian Dowse wrote: > I've seen a similar trace on a machine here, but I haven't had a chance > to analyse it properly yet. The source is from Dec 18: Ian and I tracked this down today, I've just committed a patch to -current. I'll merge it in a couple of days. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 14:25:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from atlantis.homeip.net (d110240.upc-d.chello.nl [213.46.110.240]) by hub.freebsd.org (Postfix) with SMTP id F179E37B402 for ; Mon, 8 Jan 2001 14:24:46 -0800 (PST) Received: (qmail 94139 invoked from network); 8 Jan 2001 22:24:49 -0000 Received: from unknown (HELO moses.ourhome.nl) (192.168.1.2) by 192.168.1.1 with SMTP; 8 Jan 2001 22:24:49 -0000 Date: Mon, 8 Jan 2001 23:27:08 +0100 From: Willem van Engen To: freebsd-stable@freebsd.org Subject: makeworld fails at kerberos5 X-Mailer: Sylpheed version 0.4.4 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010108222446.F179E37B402@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> /usr/src/kerberos5/usr.bin/k5init cc -O -pipe -I/usr/src/kerberos5/usr.bin/k5init/../../../crypto/heimdal/include -I/usr/src/kerberos5/usr.bin/k5init/../../../crypto/heimdal/lib/roken -I/usr/s rc/kerberos5/usr.bin/k5init/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerbero s5/usr.bin/k5init/../../../crypto/heimdal/lib/asn1 -I/usr/src/kerberos5/usr.bin /k5init/../../../crypto/heimdal/kuser -I/usr/obj/usr/src/kerberos5/usr.bin/k5in it/../../lib/libasn1 -I/usr/obj/usr/src/kerberos5/usr.bin/k5init -Wall -I/usr/s rc/kerberos5/usr.bin/k5init/../../include -I/usr/src/kerberos5/usr.bin/k5init/.. /../include -DHAVE_CONFIG_H -DINET6 -I/usr/obj/usr/src/i386/usr/include -c /us r/src/kerberos5/usr.bin/k5init/../../../crypto/heimdal/kuser/kinit.c cc -O -pipe -I/usr/src/kerberos5/usr.bin/k5init/../../../crypto/heimdal/include -I/usr/src/kerberos5/usr.bin/k5init/../../../crypto/heimdal/lib/roken -I/usr/s rc/kerberos5/usr.bin/k5init/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerbero s5/usr.bin/k5init/../../../crypto/heimdal/lib/asn1 -I/usr/src/kerberos5/usr.bin /k5init/../../../crypto/heimdal/kuser -I/usr/obj/usr/src/kerberos5/usr.bin/k5in it/../../lib/libasn1 -I/usr/obj/usr/src/kerberos5/usr.bin/k5init -Wall -I/usr/s rc/kerberos5/usr.bin/k5init/../../include -I/usr/src/kerberos5/usr.bin/k5init/.. /../include -DHAVE_CONFIG_H -DINET6 -I/usr/obj/usr/src/i386/usr/include -c /us r/src/kerberos5/usr.bin/k5init/../../../crypto/heimdal/kuser/kinit_options.c cc -O -pipe -I/usr/src/kerberos5/usr.bin/k5init/../../../crypto/heimdal/include -I/usr/src/kerberos5/usr.bin/k5init/../../../crypto/heimdal/lib/roken -I/usr/s rc/kerberos5/usr.bin/k5init/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerbero s5/usr.bin/k5init/../../../crypto/heimdal/lib/asn1 -I/usr/src/kerberos5/usr.bin /k5init/../../../crypto/heimdal/kuser -I/usr/obj/usr/src/kerberos5/usr.bin/k5in it/../../lib/libasn1 -I/usr/obj/usr/src/kerberos5/usr.bin/k5init -Wall -I/usr/s rc/kerberos5/usr.bin/k5init/../../include -I/usr/src/kerberos5/usr.bin/k5init/.. /../include -DHAVE_CONFIG_H -DINET6 -I/usr/obj/usr/src/i386/usr/include -o k5 init kinit.o kinit_options.o -L/usr/obj/usr/src/kerberos5/usr.bin/k5init/../../ lib/libkrb5 -lkrb5 -L/usr/obj/usr/src/kerberos5/usr.bin/k5init/../../lib/librok en -lroken -L/usr/src/kerberos5/usr.bin/k5init/../../lib/libkafs5 -lkafs5 -lkrb -lkafs -L/usr/obj/usr/src/kerberos5/usr.bin/k5init/../../lib/libasn1 -lasn1 -lc rypto -lmd -lcrypt -lcom_err /usr/obj/usr/src/i386/usr/libexec/elf/ld: cannot find -lkafs5 *** Error code 1 Stop in /usr/src/kerberos5/usr.bin/k5init. I have MAKE_KERBEROS4=NO and MAKE_KERBEROS5=NO defined in my make.conf, but also if I remove those lines, the problem remains. It's quite logical that the kafs5 library cannot be found, since Makefile in /usr/src/kerberos5/lib contains the following: .if defined(MAKE_KERBEROS4) && \ (${MAKE_KERBEROS4} == "YES" || ${MAKE_KERBEROS4} == "yes") SUBDIR+=libkafs5 .endif When I decend into the /usr/src/kerberos5/lib/libkafs5 directory and do a make by hand, I get the following errors: Warning: Object directory not changed from original /usr/src/kerberos5/lib/libkafs5 cc -O -pipe -I/usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/kafs -I/usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/asn1 -I/usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/roken -I/usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/include -I/usr/src/kerberos5/lib/libkafs5/../../lib/libkrb5 -I/usr/src/kerberos5/lib/libkafs5/../../lib/libasn1 -Wall -I/usr/src/kerberos5/lib/libkafs5/../../include -I/usr/src/kerberos5/lib/libkafs5/../../include -DHAVE_CONFIG_H -DINET6 -c /usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/kafs/afssys.c -o afssys.o In file included from /usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/kafs/afssys.c:34: /usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/kafs/kafs_locl.h:89: roken.h: No such file or directory In file included from /usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/kafs/kafs_locl.h:92, from /usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/kafs/afssys.c:34: /usr/src/kerberos5/lib/libkafs5/../../../crypto/heimdal/lib/krb5/krb5.h:42: asn1_err.h: No such file or directory and more "No such file or directory" messages and many resulting "cannot find symbol foo" errors. Does anyone have an idea how to get my world made? - Willem van Engen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 14:33:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id 1599537B400 for ; Mon, 8 Jan 2001 14:33:35 -0800 (PST) Received: from mail.de.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id XAA26628; Mon, 8 Jan 2001 23:33:28 +0100 (MET) (envelope-from Helge.Oldach@de.origin-it.com) Received: from smtprelay-de1.origin-it.com(172.16.188.53) by gw-nl1.origin-it.com via mwrap (4.0a) id xma026626; Mon, 8 Jan 01 23:33:29 +0100 Received: from mailhub.de.origin-it.com (mailhub.de.origin-it.com [172.16.189.20]) by mail.de.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id XAA15182; Mon, 8 Jan 2001 23:33:28 +0100 (MET) Received: from galaxy.de.cp.philips.com (galaxy.de.cp.philips.com [130.143.166.29]) by mailhub.de.origin-it.com (8.11.1/8.11.1/hmo23oct00) with ESMTP id f08MXRY23064; Mon, 8 Jan 2001 23:33:27 +0100 (CET) (envelope-from Helge.Oldach@de.origin-it.com) Received: (from hmo@localhost) by galaxy.de.cp.philips.com (8.9.3/8.9.3/hmo14aug98) id XAA09900; Mon, 8 Jan 2001 23:33:24 +0100 (MET) Message-Id: <200101082233.XAA09900@galaxy.de.cp.philips.com> Subject: Re: /var drive space problem In-Reply-To: <3A59D52B.2F4277EC@sxb.bsf.alcatel.fr> from Sebastien ROCHE at "Jan 8, 2001 3:56:43 pm" To: roche1@sxb.bsf.alcatel.fr (Sebastien ROCHE) Date: Mon, 8 Jan 2001 23:33:24 +0100 (MET) Cc: dan@tsolab.org, kenm@icarz.com, clash@fireduck.com, matt@ARPA.MAIL.NET, brentb@loa.com, freebsd-stable@freebsd.org From: Helge Oldach X-Address: Atos Origin, Billstrasse 80, D-20539 Hamburg, Germany X-Phone: +49 40 7886 464, Fax: +49 40 7886 235, Mobile: +49 172 4515513 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 Sebastien ROCHE: >My / partition is 32 Mb large. I had no problem until yesterday, when the >make installkernel didn't work due to insufficient space. >I think it's /modules which is bigger than it was (and the installation >process makes a copy of it). Anyway it was difficult to have it work. I >lost /stand and I put /lkm on /usr and I had to delete some binaries in >/bin or /sbin that I don't use. Actually you can safely remove /modules and /modules.old after a successful "make buildkernel" (!) while you are in single-user just before "make installkernel". Then even a 32 MB root should suffice. If you want to be on the very safe side you can try removing /modules.old first. Often that suffices. A populated /lkm is pointless on an ELF system anyhow. Also /stand gets outdated quickly :-) and thus can be removed. Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 15:57:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 34BA637B401 for ; Mon, 8 Jan 2001 15:57:15 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id QAA01425; Mon, 8 Jan 2001 16:56:55 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200101082356.QAA01425@freeway.dcfinc.com> Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: from Chris Foote at "Jan 8, 1 12:16:14 pm" To: chris@zeus.foote.com.au (Chris Foote) Date: Mon, 8 Jan 2001 16:56:55 -0700 (MST) Cc: jeroen@vangelderen.org, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition 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 As I recall, Chris Foote wrote: > These symptoms sound like they're caused by duplex mismatch problems. > > Try forcing half or full-duplex options and test again - i.e. use > media and mediaopt flags in your /etc/rc.conf. Available values for > these are in `man fxp`. If you've selected "autoselect" for the media, is there then a way to determine what was negotiated? That is: +--------------- | chad> grep fxp /var/run/dmesg.boot | fxp0 rev 2 int a irq 10 on pci0:10:0 | fxp0: Ethernet address 00:a0:c9:49:ec:ca | | chad> ifconfig fxp0 | fxp0: flags=8843 mtu 1500 | inet 192.168.1.129 netmask 0xffffff00 broadcast 192.168.1.255 | ether 00:a0:c9:49:ec:ca | media: autoselect | supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP +--------------- How can I tell if this interface is running 100/full or 10/half? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 16: 0:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F0AC37B402 for ; Mon, 8 Jan 2001 15:59:53 -0800 (PST) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA09477; Mon, 8 Jan 2001 17:59:36 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-104.max1.wa.cyberlynk.net(207.227.118.104) by peak.mountin.net via smap (V1.3) id sma009385; Mon Jan 8 17:58:57 2001 Message-Id: <4.3.2.20010108174340.020ee910@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Mon, 08 Jan 2001 17:53:12 -0600 To: Stefan Molnar , "Jeroen C. van Gelderen" From: "Jeffrey J. Mountin" Subject: Re: Intel PRO/100+ driver or hardware? Cc: In-Reply-To: References: <128310000.978895262@grolsch.ai> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:17 AM 1/8/01 -0800, Stefan Molnar wrote: >I have noticed that the eepro does not like some hubs/switches. >I have a netgear 8 port 10mb switch, and the eepro just goes to >a crawl with the same things you see. I have tried over a dozen >eepro cards (had this switch for almost 2 years), and countless >ethernet cables. I bought a 4 port hub, connected the xover to the >swtitch and the eepro on the hub, and bamf, those problems went >away. The tulip cards that most of the eepros replaced worked >very happly. Almost every 8255x card works just fine with a Netgear FS105 here in all modes. Say "almost" since I don't have an old 82556 card around. One of systems has a newer version on an Asus A7V running -stable, so doubt the problem is with FBSD or the card. Good cables and nailing down the modes fix most problems. Most likely a hardware or disposition, as we seem to say "doesn't like" when problems like this crop up, issue here. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 16: 2:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 2608A37B400 for ; Mon, 8 Jan 2001 16:02:00 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA01467; Mon, 8 Jan 2001 17:00:31 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200101090000.RAA01467@freeway.dcfinc.com> Subject: Re: IPFW In-Reply-To: from Norbert Koch at "Jan 8, 1 12:58:17 pm" To: nk@LF.net (Norbert Koch) Date: Mon, 8 Jan 2001 17:00:31 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition 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 As I recall, Norbert Koch wrote: > and don't forget to > > kill -HUP `cat /var/run/syslog.pid` And to make an entry in /etc/newsyslog.conf -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 16:24:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 9C77B37B401 for ; Mon, 8 Jan 2001 16:24:13 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f090O5K31687; Mon, 8 Jan 2001 16:24:05 -0800 (PST) (envelope-from dillon) Date: Mon, 8 Jan 2001 16:24:05 -0800 (PST) From: Matt Dillon Message-Id: <200101090024.f090O5K31687@earth.backplane.com> To: "Jeffrey J. Mountin" Cc: Stefan Molnar , "Jeroen C. van Gelderen" , Subject: Re: Intel PRO/100+ driver or hardware? References: <128310000.978895262@grolsch.ai> <4.3.2.20010108174340.020ee910@207.227.119.2> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>I have noticed that the eepro does not like some hubs/switches. :>I have a netgear 8 port 10mb switch, and the eepro just goes to :>a crawl with the same things you see. I have tried over a dozen :>eepro cards (had this switch for almost 2 years), and countless :>ethernet cables. I bought a 4 port hub, connected the xover to the :>swtitch and the eepro on the hub, and bamf, those problems went :>away. The tulip cards that most of the eepros replaced worked :>very happly. : :Almost every 8255x card works just fine with a Netgear FS105 here in all :modes. Say "almost" since I don't have an old 82556 card around. One of :systems has a newer version on an Asus A7V running -stable, so doubt the :problem is with FBSD or the card. Good cables and nailing down the modes :fix most problems. Most likely a hardware or disposition, as we seem to :say "doesn't like" when problems like this crop up, issue here. : :Jeff Mountin - jeff@mountin.net :Systems/Network Administrator :FreeBSD - the power to serve I've had incredibly good luck with the netgear FS516 (16 port unmanaged switch), more then I probably deserve. I haven't had a single problem using them to distribute our office LAN. However, I get mixed results with the smaller netgear switches (e.g. 5 and 8-port babies), and would not recommend them. Here's a an interesting review in PC Mag of various managed and unmanaged switches. It doesn't say a lot about the unmanaged switches, but it is interesting nonetheless. http://www.zdnet.com/pcmag/stories/reviews/0,6755,2331808,00.html In anycase, as a general rule nobody should even be contemplating using a hub in these modern times. If you are cheap, then get a cheap switch. If you are loaded,then get a loaded switch :-) -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 16:45: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 1A7A937B402 for ; Mon, 8 Jan 2001 16:44:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f090gqR62354; Mon, 8 Jan 2001 18:42:52 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101090042.f090gqR62354@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: chad@DCFinc.com Cc: freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: Intel PRO/100+ driver or hardware? In-reply-to: Message from "Chad R. Larson" of "Mon, 08 Jan 2001 16:56:55 MST." <200101082356.QAA01425@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Jan 2001 18:42:52 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chad R. Larson" writes: > If you've selected "autoselect" for the media, is there then a way > to determine what was negotiated? That is: [...] > How can I tell if this interface is running 100/full or 10/half? This one is running 10baseT: % ifconfig fxp0 fxp0: flags=8843 mtu 1500 [...] media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP % -- David Kelly N4HHE, dkelly@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 Mon Jan 8 16:45:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 2C65837B404 for ; Mon, 8 Jan 2001 16:45:00 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id f090ix214155 for ; Mon, 8 Jan 2001 16:44:59 -0800 (PST) Received: from pau-amma.whistle.com( 207.76.205.64) by whistle.com via smap (V2.0) id xma014150; Mon, 8 Jan 2001 16:44:31 -0800 Received: (from dhw@localhost) by pau-amma.whistle.com (8.11.1/8.11.1) id f090iVi92824 for freebsd-stable@FreeBSD.ORG; Mon, 8 Jan 2001 16:44:31 -0800 (PST) Date: Mon, 8 Jan 2001 16:44:31 -0800 (PST) From: David Wolfskill Message-Id: <200101090044.f090iVi92824@pau-amma.whistle.com> Subject: Re: Intel PRO/100+ driver or hardware? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <200101090024.f090O5K31687@earth.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 8 Jan 2001 16:24:05 -0800 (PST) >From: Matt Dillon > I've had incredibly good luck with the netgear FS516 (16 port unmanaged > switch), more then I probably deserve. I haven't had a single problem > using them to distribute our office LAN. However, I get mixed results > with the smaller netgear switches (e.g. 5 and 8-port babies), and would > not recommend them. For whatever it might be worth, we swapped out just about all of the 4-, 5-, & 8-port mini-hubs from engineers' desks and replaced them with the 5- & 8-port NetGear 10/100 switches (FS105 & FS108). I then replaced the odd assortment of hubs & switches with 24-port NetGear switches. The sole problem was in communicating with an old Black Box device that converts between 10base-T & fiber. I circumvented that by interposing one of the dumb 5-port mini-hubs between the Black Box device & the switch. :-{ I liked the results enough to deploy an FS108 at home.... :-) Of course, YMMV. Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 I need help: http://www.whistle.com/employment/employ-engg.html#K030391 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 16:47:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id 785A037B400 for ; Mon, 8 Jan 2001 16:47:07 -0800 (PST) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.9.3/8.9.3) with ESMTP id OAA18593; Mon, 8 Jan 2001 14:46:44 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Mon, 8 Jan 2001 14:46:43 -1000 (HST) From: Vincent Poy To: David Kelly Cc: , Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: <200101090042.f090gqR62354@grumpy.dyndns.org> 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 Mon, 8 Jan 2001, David Kelly wrote: > "Chad R. Larson" writes: > > If you've selected "autoselect" for the media, is there then a way > > to determine what was negotiated? That is: > [...] > > How can I tell if this interface is running 100/full or 10/half? > > This one is running 10baseT: > > % ifconfig fxp0 > fxp0: flags=8843 mtu 1500 > [...] > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP > % And this one is running Full 100. root@oahu [9:45pm][/home/vince] >> ifconfig fxp0 fxp0: flags=8843 mtu 1500 [other data taken out] media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 19:10:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 6963437B400 for ; Mon, 8 Jan 2001 19:09:55 -0800 (PST) Received: (qmail 74684 invoked from network); 9 Jan 2001 03:09:43 -0000 Received: from unknown (HELO prydn.tacni.net) (207.55.167.213) by 216.178.136.168 with SMTP; 9 Jan 2001 03:09:43 -0000 Received: (qmail 358 invoked by uid 1001); 9 Jan 2001 03:09:40 -0000 Date: Mon, 8 Jan 2001 21:09:39 -0600 From: Erich Zigler To: freebsd-stable@freebsd.org Subject: ps and top problems Message-ID: <20010108210939.A317@superhero.org> Mail-Followup-To: Erich Zigler , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I rebuilt my world and kernel recently and when I did ps and top I would get these errors... ps: proc size mismatch (36176 total, 1056 chunks) kvm_open: proc size mismatch (72352 total, 1056 chunks) top: Out of memory. Following advice I rm -rf'ed /usr/src and cvsupped down the latest 4-STABLE source tree. Rebuilt... make buildworld make installworld make buildkernel KERNEL= make installkernel KERNEL= cp /usr/src/etc/MAKEDEV /dev sh /dev/MAKEDEV all cd /usr/src/release/sysinstall make && make install && make clean reboot And I still get the same errors as above. What am I missing? -- Erich Zigler What are you doing wrong with our bug-free product? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 21:32: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id E3E1437B400 for ; Mon, 8 Jan 2001 21:31:46 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 8 Jan 2001 21:30:01 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.0/8.11.0) id f095Vfa82962; Mon, 8 Jan 2001 21:31:41 -0800 (PST) (envelope-from cjc) Date: Mon, 8 Jan 2001 21:31:41 -0800 From: "Crist J. Clark" To: Erich Zigler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ps and top problems Message-ID: <20010108213141.I95729@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <20010108210939.A317@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010108210939.A317@superhero.org>; from erichz@superhero.org on Mon, Jan 08, 2001 at 09:09:39PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 08, 2001 at 09:09:39PM -0600, Erich Zigler wrote: > I rebuilt my world and kernel recently and when I did ps and top I would get > these errors... > > ps: proc size mismatch (36176 total, 1056 chunks) > > kvm_open: proc size mismatch (72352 total, 1056 chunks) > top: Out of memory. > > Following advice I rm -rf'ed /usr/src and cvsupped down the latest 4-STABLE > source tree. Rebuilt... > > make buildworld > make installworld > make buildkernel KERNEL= > make installkernel KERNEL= Is this what you really typed? You didn't build a kernel. Userland and the kernel are out of sync. If you are building GENERIC, make buildkernel make installkernel If you are building your own, you should be putting in its name. Setting "KERNEL=" (setting the KERNEL variable to null) is not the same as not defining it at all. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 21:48: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hellraiser.cannoncreek.com (unknown [202.78.79.4]) by hub.freebsd.org (Postfix) with SMTP id 966EF37B400 for ; Mon, 8 Jan 2001 21:47:46 -0800 (PST) Received: (qmail 3634 invoked from network); 9 Jan 2001 05:53:13 -0000 Received: from nomad.cannoncreek.com (HELO nomad) (192.168.0.69) by hellraiser.cannoncreek.com with SMTP; 9 Jan 2001 05:53:13 -0000 Message-ID: <004b01c07a02$37671680$4500a8c0@nomad> From: "Mars Attack" To: "Erich Zigler" Cc: References: <20010108210939.A317@superhero.org> Subject: Re: ps and top problems Date: Tue, 9 Jan 2001 14:05:47 +0800 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I rebuilt my world and kernel recently and when I did ps and top I would get > these errors... > > ps: proc size mismatch (36176 total, 1056 chunks) > > kvm_open: proc size mismatch (72352 total, 1056 chunks) > top: Out of memory. > > Following advice I rm -rf'ed /usr/src and cvsupped down the latest 4-STABLE > source tree. Rebuilt... > > make buildworld > make installworld > make buildkernel KERNEL= > make installkernel KERNEL= you need to [build/install]kernel before installworld. it would help if you'd re-read /usr/src/UPDATING > cp /usr/src/etc/MAKEDEV /dev > sh /dev/MAKEDEV all > cd /usr/src/release/sysinstall > make && make install && make clean > reboot > > And I still get the same errors as above. What am I missing? > > -- > Erich Zigler > > What are you doing wrong with our bug-free product? > > > 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 Jan 8 23:11:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 2F2E137B401 for ; Mon, 8 Jan 2001 23:11:28 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id XAA17642; Mon, 8 Jan 2001 23:12:39 -0800 Date: Mon, 8 Jan 2001 23:12:39 -0800 From: Kris Kennaway To: Dan Larsson Cc: FreeBSD Stable List Subject: Re: ssh issues after make world Message-ID: <20010108231239.E17341@citusc.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="O5XBE6gyVG5Rl6Rj" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from dl@tyfon.net on Mon, Jan 08, 2001 at 06:19:52PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --O5XBE6gyVG5Rl6Rj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 08, 2001 at 06:19:52PM +0100, Dan Larsson wrote: > Before the make world I didn't have the below problem: >=20 > % ssh remote-machine > dsa_verify failed for server_host_key > % >=20 > It seems as the problem only appears with machines running > non OpenSSH daemons, but that's just a guess. >=20 > Anyone having these issues too? That's a pretty minimal bug report. What was your old FreeBSD version prior to make world, and what does ssh -v tell you, etc. Allow us to debug your problem. Kris --O5XBE6gyVG5Rl6Rj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6WrnnWry0BWjoQKURAgsxAJ9EmA42EibyEbcTjYq4Rqz37gMhRQCfeGA1 mGGg08PjFBR72BShDNNv4eU= =qTlp -----END PGP SIGNATURE----- --O5XBE6gyVG5Rl6Rj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 8 23:17:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 5D57637B400 for ; Mon, 8 Jan 2001 23:17:06 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id XAA17298; Mon, 8 Jan 2001 23:10:15 -0800 (PST) Message-Id: <200101090710.XAA17298@implode.root.com> To: Matt Dillon Cc: "Jeffrey J. Mountin" , Stefan Molnar , "Jeroen C. van Gelderen" , freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? In-reply-to: Your message of "Mon, 08 Jan 2001 16:24:05 PST." <200101090024.f090O5K31687@earth.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 08 Jan 2001 23:10:15 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've had incredibly good luck with the netgear FS516 (16 port unmanaged > switch), more then I probably deserve. I haven't had a single problem > using them to distribute our office LAN. However, I get mixed results > with the smaller netgear switches (e.g. 5 and 8-port babies), and would > not recommend them. Yeah, we've been using both the 8 and 16 port Netgear switches in the TeraSolutions offices for about a year and haven't had any problems with them. They autonegotiate correctly with the Intel NICs and have been very reliable. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 0:19:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.tue.le (p3EE325B1.dip.t-dialin.net [62.227.37.177]) by hub.freebsd.org (Postfix) with ESMTP id 598FF37B400 for ; Tue, 9 Jan 2001 00:19:05 -0800 (PST) Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by mail.tue.le (8.8.8/8.8.8) with ESMTP id JAA27431 for ; Tue, 9 Jan 2001 09:00:33 +0100 (CET) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.11.1/8.11.1) id f0980WW00827 for freebsd-stable@freebsd.org; Tue, 9 Jan 2001 09:00:32 +0100 (CET) (envelope-from thz) Date: Tue, 9 Jan 2001 09:00:32 +0100 From: Thomas Zenker To: freebsd-stable@freebsd.org Subject: Re: SIGSEGV can be blocked!? Message-ID: <20010109090032.A795@mezcal.tue.le> References: <20010108161854.A3547@mezcal.tue.le> <200101082132.f08LWhL18526@saturn.home.ben.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200101082132.f08LWhL18526@saturn.home.ben.com>; from ben@ben.com on Mon, Jan 08, 2001 at 01:32:43PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 08, 2001 at 01:32:43PM -0800, Ben Jackson wrote: > > Blocking SIGSEGV with sigprocmask does really BLOCK it. > > I think, this is a bug. I discovered this because I wanted to > > provoke a core dump by a write to (int *)0, but the process got hung, > > The instruction that caused the SEGV is going to restart after any handler > runs because the handler may have mapped the page that caused the fault. > > On other operating systems you can block SEGV for purposes of asynchronous > signals (ie `kill -SEGV') but not for synchronous signals. To quote from > the Solaris sigprocmask manpage: > > Signals that are generated synchronously should not be > masked. If such a signal is blocked and delivered, the > receiving process is killed. > > and indeed a test program shows that you still get SEGV in that case. > You can still shoot yourself in the foot with a SEGV handler that doesn't > eliminate the fault. there is no handler for SEGV - it is simply blocked, if QUIT have been blocked the machine would lockup. -- Thomas Zenker c/o Lennartz electronic GmbH Bismarckstrasse 136, D-72072 Tuebingen, Germany Phone: +49-(0)7071-93550 Email: thz@lennartz-electronic.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 0:20:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hq1.tyfon.net (hq1.tyfon.net [217.27.162.35]) by hub.freebsd.org (Postfix) with ESMTP id 6F16537B401; Tue, 9 Jan 2001 00:20:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id 577711C7D3; Tue, 9 Jan 2001 09:20:23 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id 56DD81C5C9; Tue, 9 Jan 2001 09:20:20 +0100 (CET) Date: Tue, 9 Jan 2001 09:20:20 +0100 (CET) From: Dan Larsson To: Kris Kennaway Cc: FreeBSD Stable List Subject: Re: ssh issues after make world In-Reply-To: <20010108231239.E17341@citusc.usc.edu> Message-ID: Organization: Tyfon Svenska AB X-NCC-NIC: DL1999-RIPE X-NCC-RegID: se.tyfon MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by hq1.tyfon.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 8 Jan 2001, Kris Kennaway wrote: | That's a pretty minimal bug report. What was your old FreeBSD version | prior to make world, and what does ssh -v tell you, etc. Allow us to | debug your problem. Sorry about that, here's a bit more info: % ssh -v remote-host SSH Version OpenSSH_2.2.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). debug: Reading configuration data /etc/ssh/ssh_config debug: Applying options for * debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to remote-host [10.0.22.1] port 22. debug: Allocated local port 1004. debug: Connection established. debug: Remote protocol version 1.99, remote software version 2.0.13 (non-commercial) datafellows: 2.0.13 (non-commercial) Enabling compatibility mode for protocol 2.0 debug: Local version string SSH-2.0-OpenSSH_2.2.0 debug: send KEXINIT debug: done debug: wait KEXINIT debug: got kexinit: diffie-hellman-group1-sha1 debug: got kexinit: ssh-dss debug: got kexinit: 3des-cbc,blowfish-cbc,none debug: got kexinit: 3des-cbc,blowfish-cbc,none debug: got kexinit: hmac-md5,md5-8,none debug: got kexinit: hmac-md5,md5-8,none debug: got kexinit: none,zlib debug: got kexinit: none,zlib debug: got kexinit: debug: got kexinit: debug: first kex follow: 0 debug: reserved: 0 debug: done debug: kex: server->client 3des-cbc hmac-md5 none debug: kex: client->server 3des-cbc hmac-md5 none debug: Sending SSH2_MSG_KEXDH_INIT. debug: bits set: 533/1024 debug: Wait SSH2_MSG_KEXDH_REPLY. debug: Got SSH2_MSG_KEXDH_REPLY. The authenticity of host 'remote-host' can't be established. DSA key fingerprint is 83:aa:b2:14:cb:f1:d3:f1:a0:99:77:de:01:71:f1:6a. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'remote-host' (DSA) to the list of known hosts. debug: bits set: 523/1024 debug: len 40 datafellows 15 debug: dsa_verify: signature incorrect dsa_verify failed for server_host_key debug: Calling cleanup 0x805b634(0x0) % Using a system cvsup:ed and make world:ed 2001/01/04. The problem only appears when using ssh2, ssh1 seems to work just fine. | Regards +------ Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 GPG and PGP keys | finger dl@hq1.tyfon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 0:55:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C924237B401 for ; Tue, 9 Jan 2001 00:55:02 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f098swl19012; Tue, 9 Jan 2001 00:54:58 -0800 (PST) Date: Tue, 9 Jan 2001 00:54:58 -0800 From: Alfred Perlstein To: Thomas Zenker Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SIGSEGV can be blocked!? Message-ID: <20010109005458.N15744@fw.wintelcom.net> References: <20010108161854.A3547@mezcal.tue.le> <200101082132.f08LWhL18526@saturn.home.ben.com> <20010109090032.A795@mezcal.tue.le> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010109090032.A795@mezcal.tue.le>; from thz@lennartz-electronic.de on Tue, Jan 09, 2001 at 09:00:32AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Thomas Zenker [010109 00:19] wrote: > On Mon, Jan 08, 2001 at 01:32:43PM -0800, Ben Jackson wrote: > > > Blocking SIGSEGV with sigprocmask does really BLOCK it. > > > I think, this is a bug. I discovered this because I wanted to > > > provoke a core dump by a write to (int *)0, but the process got hung, > > > > The instruction that caused the SEGV is going to restart after any handler > > runs because the handler may have mapped the page that caused the fault. > > > > On other operating systems you can block SEGV for purposes of asynchronous > > signals (ie `kill -SEGV') but not for synchronous signals. To quote from > > the Solaris sigprocmask manpage: > > > > Signals that are generated synchronously should not be > > masked. If such a signal is blocked and delivered, the > > receiving process is killed. > > > > and indeed a test program shows that you still get SEGV in that case. > > You can still shoot yourself in the foot with a SEGV handler that doesn't > > eliminate the fault. > > there is no handler for SEGV - it is simply blocked, if QUIT have been > blocked the machine would lockup. Sorry, what? The machine should never lockup because of signal handling. Can you clarify? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 3:15:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netcabo.pt (mail.netcabo.pt [212.113.161.135]) by hub.freebsd.org (Postfix) with ESMTP id 406C937B404 for ; Tue, 9 Jan 2001 03:15:00 -0800 (PST) Received: from OpsyDopsy ([213.22.0.84]) by netcabo.pt with Microsoft SMTPSVC(5.5.1877.537.53); Tue, 9 Jan 2001 11:12:12 +0000 Date: Tue, 09 Jan 2001 11:16:19 -0000 To: stable@freebsd.org From: Joгo Fernandes Subject: Dhis mail relaying is OFF, please resend me any messages you may have sent to me. Reply-To: OpsyDopsy@netcabo.pt X-Mailer: Opera 5.00 build 828 X-Priority: 3 (Normal) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <054db1212110911TVCABO05@netcabo.pt> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My old mail: root@opsydopsy.net.dhis.org My new mail: OpsyDopsy@netcabo.pt Please resend me all the mail you sent me. Thanks in advance. Joao Fernandes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 4:39:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.tue.le (p3E9E12EB.dip.t-dialin.net [62.158.18.235]) by hub.freebsd.org (Postfix) with ESMTP id 6AB2A37B400 for ; Tue, 9 Jan 2001 04:39:18 -0800 (PST) Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by mail.tue.le (8.8.8/8.8.8) with ESMTP id NAA27965 for ; Tue, 9 Jan 2001 13:38:30 +0100 (CET) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.11.1/8.11.1) id f09CcU503189 for freebsd-stable@freebsd.org; Tue, 9 Jan 2001 13:38:30 +0100 (CET) (envelope-from thz) Date: Tue, 9 Jan 2001 13:38:30 +0100 From: Thomas Zenker To: freebsd-stable@freebsd.org Subject: Re: SIGSEGV can be blocked!? Message-ID: <20010109133830.A3166@mezcal.tue.le> References: <20010108161854.A3547@mezcal.tue.le> <200101082132.f08LWhL18526@saturn.home.ben.com> <20010109090032.A795@mezcal.tue.le> <20010109005458.N15744@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010109005458.N15744@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Jan 09, 2001 at 12:54:58AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 12:54:58AM -0800, Alfred Perlstein wrote: > * Thomas Zenker [010109 00:19] wrote: > > On Mon, Jan 08, 2001 at 01:32:43PM -0800, Ben Jackson wrote: > > > > Blocking SIGSEGV with sigprocmask does really BLOCK it. > > > > I think, this is a bug. I discovered this because I wanted to > > > > provoke a core dump by a write to (int *)0, but the process got hung, > > > > > > The instruction that caused the SEGV is going to restart after any handler > > > runs because the handler may have mapped the page that caused the fault. > > > > > > On other operating systems you can block SEGV for purposes of asynchronous > > > signals (ie `kill -SEGV') but not for synchronous signals. To quote from > > > the Solaris sigprocmask manpage: > > > > > > Signals that are generated synchronously should not be > > > masked. If such a signal is blocked and delivered, the > > > receiving process is killed. > > > > > > and indeed a test program shows that you still get SEGV in that case. > > > You can still shoot yourself in the foot with a SEGV handler that doesn't > > > eliminate the fault. > > > > there is no handler for SEGV - it is simply blocked, if QUIT have been > > blocked the machine would lockup. > > Sorry, what? The machine should never lockup because of signal handling. > Yeah, normally it doesn't lockup, but it gives a full load on the machine. in my particular case it did lockup the machine, because it was running with the fifo scheduler at realtime prio. Anyway, obviously i have to unblock SEGV. the program was running before on other OSs like HPUX and Solaris. At least on HPUX i know, that SEGV was not possible to block. -- Thomas Zenker c/o Lennartz electronic GmbH Bismarckstrasse 136, D-72072 Tuebingen, Germany Phone: +49-(0)7071-93550 Email: thz@lennartz-electronic.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 5:13:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 5B7D137B400; Tue, 9 Jan 2001 05:13:27 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f09DC8O73342; Tue, 9 Jan 2001 09:12:08 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 9 Jan 2001 09:12:08 -0400 (AST) From: The Hermit Hacker To: , Will Andrews Cc: , Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... In-Reply-To: <20010108172445.P649@puck.firepipe.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 from what I can tell right now, the problem is in either 4.2-STABLE *or* the XF-4.0.2 port ... I just wiped out everything, so that I'm startign with a clean slate (rm -rf /usr/X11R6 /usr/local) and can't get XFree-4.0.2 to install now without pthread errors ... On Mon, 8 Jan 2001, Will Andrews wrote: > [.. other posts considered ..] > On Mon, Jan 08, 2001 at 11:43:52AM -0400, The Hermit Hacker wrote: > > if I do a 'setenv LDFLAGS -pthread', the error changes to: > [..] > > Just to note, KDE2 was totally broken when built with -pthread with > QT22-thread-GL. However, I nuked the GL dependency a few nights ago, > and installed the threaded QT version. I believe KDE2 should compile > without threads now, but I'm not sure. Kevin will have to answer for > that one. :-) > > -- > wca > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 5:19:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6ACFB37B400 for ; Tue, 9 Jan 2001 05:19:12 -0800 (PST) Received: from inspiral.net (tigris-isdn-163.uninet.ee [194.204.61.163]) by ns.uninet.ee (Postfix) with ESMTP id 8E75325812 for ; Tue, 9 Jan 2001 15:19:06 +0200 (EET) Message-ID: <3A5B0F9D.E986E033@inspiral.net> Date: Tue, 09 Jan 2001 15:18:21 +0200 From: Lauri Laupmaa Organization: Inspiral.Net X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en,et MIME-Version: 1.0 To: stable@freebsd.org Subject: Compaq dual processor & broken MP table Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms2BC3C195F97F11531600C823" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms2BC3C195F97F11531600C823 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi On compaq ML350 dual processor kernel says: APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 Is it some major problem or just annoying message ? TIA L. --------------ms2BC3C195F97F11531600C823 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIKKwYJKoZIhvcNAQcCoIIKHDCCChgCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B7cwggSBMIID6qADAgECAhBRff1uOxqNtD+DymrDYl03MA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAxMDEwNzAwMDAw MFoXDTAxMDMwODIzNTk1OVowggEFMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMSYwJAYDVQQLEx1EaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZTEWMBQGA1UEAxQNTGF1cmkgTGF1cG1hYTEhMB8GCSqGSIb3DQEJARYSbWF1cmlA aW5zcGlyYWwubmV0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCtwtrfGV1XM4dhgowq QK9fsL+Ip5UthKacaoNORgLX6nxAOXUeLPePFHrUjCVtYRbfrAjCPmE5Zy9Qnpfm4fgf/sK2 5IQ+QoHdY/g6BZ+7dc9Wf3ZszKrw/NT/Wu8Mmvg7Ek34F460CHxgCVxRYPMYt+gK7Ly8ubGE /zXHfMzNYQIDAQABo4IBJjCCASIwCQYDVR0TBAIwADBEBgNVHSAEPTA7MDkGC2CGSAGG+EUB BwEIMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwEQYJYIZI AYb4QgEBBAQDAgeAMIGGBgpghkgBhvhFAQYDBHgWdmQ0NjUyYmQ2M2YyMDQ3MDI5Mjk4NzYz YzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5ZGE3NWJjNGJjOTcwMTc0N2RhNWQzZjQxNDFiZWFk YjJiZDJlODkyMTZhZDZiZjFkNzExNDk5Y2EyYjk0NWZkZjNlYTQ1MGQwMwYDVR0fBCwwKjAo oCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQF AAOBgQBcAPAx7vFJmoiGWujs15eHChQjeK/95q6UT+wXqfJ1sa0DUZdipBYq4MANkN2Bcauh J0L22WU64bMsD8K4yPEEf7XEXfOlsn0XEWwWI819pbEnUrDnc4z/D4wbnQwf85v2mHtfw+kD EUR+A4zomDnKek1ZHdjt7WBbLStYoTnVvzCCAy4wggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v 7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwg SW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1 dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5NTlaMIHMMRcwFQYDVQQKEw5W ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1 YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB iQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBou5XZMUFweoFLuUgTVi3H COGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5UiE+HSr8Z2vkV6A+HthzjzMaa jn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejARBglghkgBhvhCAQEEBAMCAQYw RwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNpZ24u Y29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQDAgEGMA0GCSqG SIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bxndPKZDjcG5gMB4ZbhRVqD7lJ haSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJ PJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYICPDCCAjgCAQEwgeEwgcwxFzAV BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr MUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkg UmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2 aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEFF9/W47Go20P4PKasNi XTcwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ BTEPFw0wMTAxMDkxMzE4MjJaMCMGCSqGSIb3DQEJBDEWBBRm7L6XiVeVIOfYP+SH6ffNnp1B LTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMC BzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgKSVG+0N bcdt/x31Z79hasg/kTiUoLBGM4/F79QX/GPU4UhB0O3T6W/r7oJ8JAHdEQf3wcKFzumf+C90 RQo9+qik9uhvxYK+0FJuIST34wjBvvCmfU3s6zamYauAxbrCqkzZg92amlDjoOKYzbYHKxDw LW+7O4CFRzd9US4P10xs --------------ms2BC3C195F97F11531600C823-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 5:37:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3A95537B69B for ; Tue, 9 Jan 2001 05:35:21 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f09DYqE25693; Tue, 9 Jan 2001 05:34:52 -0800 (PST) Date: Tue, 9 Jan 2001 05:34:52 -0800 From: Alfred Perlstein To: Lauri Laupmaa Cc: stable@FreeBSD.ORG Subject: Re: Compaq dual processor & broken MP table Message-ID: <20010109053452.Q15744@fw.wintelcom.net> References: <3A5B0F9D.E986E033@inspiral.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5B0F9D.E986E033@inspiral.net>; from mauri@inspiral.net on Tue, Jan 09, 2001 at 03:18:21PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Lauri Laupmaa [010109 05:19] wrote: > Hi > > On compaq ML350 dual processor kernel says: > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 > intpin 2 > APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > > Is it some major problem or just annoying message ? I don't know, does the machine work? If so it's a diagnostic message, if not it explains a reason why it's probably not working. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 6:10:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from duckling.worldonline.nl (duckling.worldonline.nl [195.241.45.86]) by hub.freebsd.org (Postfix) with ESMTP id 61C8537B400 for ; Tue, 9 Jan 2001 06:10:32 -0800 (PST) Received: (from maikel@localhost) by duckling.worldonline.nl (8.11.1/8.11.1) id f09E8uF31597 for stable@freebsd.org; Tue, 9 Jan 2001 15:08:56 +0100 (CET) (envelope-from maikel) Date: Tue, 9 Jan 2001 15:08:51 +0100 From: Maikel Verheijen To: stable@freebsd.org Subject: Problems with XFree86-4... Message-ID: <20010109150851.E30549@duckling.worldonline.nl> Mail-Followup-To: Maikel Verheijen , stable@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="/e2eDi0V/xtL+Mc8" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --/e2eDi0V/xtL+Mc8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all! Recently, I upgraded my machine at the office freom XFree-3 to XFree-4. It was working quite nicely, and I figured: what the heck, lets try it at home too :) My videocard is in the list of supported cards, (NVidia riva TNT) so I gave it a shot. To avoid getting all kinds of troubles with libraries, and to make sure everything is back to the most recent versions, I decided to deinstalll all packages, and to reinstall them after I finished updating my XFree. As you all may have guessed, it didn't succeed as planned. I did a binary install of XFree86-4 (downloaded the package, and installed it with pkg_add), and tried to configure it, using xf86cfg. My X then dumps core with a signal 11. I hope someone can help me with this... :) I will attach my XFree86 log file. TIA, Maikel Verheijen. --/e2eDi0V/xtL+Mc8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: 24ZfRT20kAFh2Zm+1EOdTN7R/7sBUQrZ iQA/AwUBOlsbcqmWNQ7RrPkAEQKSEACdE96zhzTVH0Qr8tWeoJRS4+RpwI8AoI5S n8TiMOSSuVnsVE3MFtFQltP6 =XVLP -----END PGP SIGNATURE----- --/e2eDi0V/xtL+Mc8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 6:19:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from duckling.worldonline.nl (duckling.worldonline.nl [195.241.45.86]) by hub.freebsd.org (Postfix) with ESMTP id A48EE37B400 for ; Tue, 9 Jan 2001 06:18:46 -0800 (PST) Received: (from maikel@localhost) by duckling.worldonline.nl (8.11.1/8.11.1) id f09EHC131774 for stable@freebsd.org; Tue, 9 Jan 2001 15:17:12 +0100 (CET) (envelope-from maikel) Date: Tue, 9 Jan 2001 15:17:12 +0100 From: Maikel Verheijen To: stable@freebsd.org Subject: Re: Problems with XFree86-4... Message-ID: <20010109151712.G30549@duckling.worldonline.nl> Mail-Followup-To: Maikel Verheijen , stable@freebsd.org References: <20010109150851.E30549@duckling.worldonline.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="RMedoP2+Pr6Rq0N2" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010109150851.E30549@duckling.worldonline.nl>; from maikel@worldonline.nl on Tue, Jan 09, 2001 at 03:08:51PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --RMedoP2+Pr6Rq0N2 Content-Type: multipart/mixed; boundary="xkXJwpr35CY/Lc3I" Content-Disposition: inline --xkXJwpr35CY/Lc3I Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! And now WITH the attachment... Tia, Maikel. --xkXJwpr35CY/Lc3I Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="XFree86.8.log" Content-Transfer-Encoding: quoted-printable XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: FreeBSD 4.2-STABLE i386 [ELF]=20 Module Loader present (=3D=3D) Log file: "/var/log/XFree86.8.log", Time: Tue Jan 9 15:09:13 2001 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages =3D 0x03, oldVal1 =3D 0x80000060, mode1Res1 =3D 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0597 card 0000,0000 rev 22 class 06,00,00 hdr = 00 (II) PCI: 00:01:0: chip 1106,8598 card 0000,0000 rev 00 class 06,04,00 hdr = 01 (II) PCI: 00:07:0: chip 1106,0596 card 1106,0000 rev 09 class 06,01,00 hdr = 80 (II) PCI: 00:07:1: chip 1106,0571 card 0000,0000 rev 06 class 01,01,8a hdr = 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 02 class 0c,03,00 hdr = 00 (II) PCI: 00:07:3: chip 1106,3050 card 0000,0000 rev 00 class 06,00,00 hdr = 00 (II) PCI: 00:10:0: chip 1319,0801 card 1319,1319 rev b1 class 04,01,00 hdr = 80 (II) PCI: 00:10:1: chip 1319,0802 card 1319,1319 rev b1 class 09,04,10 hdr = 80 (II) PCI: 00:12:0: chip 10b7,9055 card 10b7,9055 rev 30 class 02,00,00 hdr = 00 (II) PCI: 00:14:0: chip 158b,0001 card 158b,0001 rev 01 class 07,80,00 hdr = 00 (II) PCI: 01:00:0: chip 10de,0020 card 10b4,273e rev 04 class 03,00,00 hdr = 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Host-to-PCI bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus 0 I/O range: [0] -1 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0x0000c000 - 0x0000c0ff (0x100) IX[B] [1] -1 0x0000c400 - 0x0000c4ff (0x100) IX[B] [2] -1 0x0000c800 - 0x0000c8ff (0x100) IX[B] [3] -1 0x0000cc00 - 0x0000ccff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0xe4000000 - 0xe5ffffff (0x2000000) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xe6000000 - 0xe6ffffff (0x1000000) MX[B] (II) Bus -1: bridge is at (0:7:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (II) Bus -1: bridge is at (0:0:0), (-1,-1,0), BCTRL: 0x00 (VGA_EN is cleare= d) (II) Bus -1 I/O range: [0] -1 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] (--) PCI:*(1:0:0) NVidia Riva TNT rev 4, Mem @ 0xe4000000/24, 0xe6000000/24 List of video drivers: atimisc r128 radeon mga glint nv tga s3virge sis rendition neomagic i740 tdfx cirrus tseng trident chips apm fbdev i128 ati i810 ark cyrix siliconmotion vesa vga (II) LoadModule: "atimisc" (II) Loading /usr/X11R6/lib/modules/drivers/atimisc_drv.o (II) Module ati: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 6.2.3 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "r128" (II) Loading /usr/X11R6/lib/modules/drivers/r128_drv.o (II) Module r128: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 4.0.1 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "radeon" (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o (II) Module radeon: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 4.0.1 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "mga" (II) Loading /usr/X11R6/lib/modules/drivers/mga_drv.o (II) Module mga: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "glint" (II) Loading /usr/X11R6/lib/modules/drivers/glint_drv.o (II) Module glint: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "nv" (II) Loading /usr/X11R6/lib/modules/drivers/nv_drv.o (II) Module nv: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "tga" (II) Loading /usr/X11R6/lib/modules/drivers/tga_drv.o (II) Module tga: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "s3virge" (II) Loading /usr/X11R6/lib/modules/drivers/s3virge_drv.o (II) Module s3virge: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.5.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "sis" (II) Loading /usr/X11R6/lib/modules/drivers/sis_drv.o (II) Module sis: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 0.6.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "rendition" (II) Loading /usr/X11R6/lib/modules/drivers/rendition_drv.o (II) Module rendition: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 4.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "neomagic" (II) Loading /usr/X11R6/lib/modules/drivers/neomagic_drv.o (II) Module neomagic: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "i740" (II) Loading /usr/X11R6/lib/modules/drivers/i740_drv.o (II) Module i740: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "tdfx" (II) Loading /usr/X11R6/lib/modules/drivers/tdfx_drv.o (II) Module tdfx: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "cirrus" (II) Loading /usr/X11R6/lib/modules/drivers/cirrus_drv.o (II) Module cirrus: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "tseng" (II) Loading /usr/X11R6/lib/modules/drivers/tseng_drv.o (II) Module tseng: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "trident" (II) Loading /usr/X11R6/lib/modules/drivers/trident_drv.o (II) Module trident: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "chips" (II) Loading /usr/X11R6/lib/modules/drivers/chips_drv.o (II) Module chips: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "apm" (II) Loading /usr/X11R6/lib/modules/drivers/apm_drv.o (II) Module apm: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "fbdev" (II) Loading /usr/X11R6/lib/modules/drivers/fbdev_drv.o (II) Module fbdev: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "i128" (II) Loading /usr/X11R6/lib/modules/drivers/i128_drv.o (II) Module i128: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "ati" (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o (II) Module ati: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 6.2.3 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "i810" (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "ark" (II) Loading /usr/X11R6/lib/modules/drivers/ark_drv.o (II) Module ark: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 0.5.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "cyrix" (II) Loading /usr/X11R6/lib/modules/drivers/cyrix_drv.o (II) Module cyrix: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "siliconmotion" (II) Loading /usr/X11R6/lib/modules/drivers/siliconmotion_drv.o (II) Module siliconmotion: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.2.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "vesa" (II) Loading /usr/X11R6/lib/modules/drivers/vesa_drv.o (II) Module vesa: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "vga" (II) Loading /usr/X11R6/lib/modules/drivers/vga_drv.o (II) Module vga: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 4.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) Addressable bus resource ranges are [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0x00000000 - 0x000001ff (0x200) IX[B]E (II) Active PCI resource ranges: [0] -1 0xe8000000 - 0xefffffff (0x8000000) MX[B]E [1] -1 0xe7000000 - 0xe7ffffff (0x1000000) MX[B]E [2] -1 0xe8010000 - 0xe801ffff (0x10000) MX[B]E [3] -1 0xe0000000 - 0xe3ffffff (0x4000000) MX[B]E [4] -1 0xe6000000 - 0xe6ffffff (0x1000000) MX[B](B) [5] -1 0xe4000000 - 0xe4ffffff (0x1000000) MX[B](B) [6] -1 0x0000e400 - 0x0000e4ff (0x100) IX[B]E [7] -1 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [8] -1 0x0000dc00 - 0x0000dcff (0x100) IX[B]E [9] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [10] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [11] -1 0x0000d000 - 0x0000d0ff (0x100) IX[B]E (II) PCI Memory resource overlap reduced 0xe8000000 from 0xefffffff to 0xe8= 00ffff (II) Active PCI resource ranges after removing overlaps: [0] -1 0xe8000000 - 0xe800ffff (0x10000) MX[B]E [1] -1 0xe7000000 - 0xe7ffffff (0x1000000) MX[B]E [2] -1 0xe8010000 - 0xe801ffff (0x10000) MX[B]E [3] -1 0xe0000000 - 0xe3ffffff (0x4000000) MX[B]E [4] -1 0xe6000000 - 0xe6ffffff (0x1000000) MX[B](B) [5] -1 0xe4000000 - 0xe4ffffff (0x1000000) MX[B](B) [6] -1 0x0000e400 - 0x0000e4ff (0x100) IX[B]E [7] -1 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [8] -1 0x0000dc00 - 0x0000dcff (0x100) IX[B]E [9] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [10] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [11] -1 0x0000d000 - 0x0000d0ff (0x100) IX[B]E (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0x00000000 - 0x000001ff (0x200) IX[B]E (II) All system resource ranges: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0xe8000000 - 0xe800ffff (0x10000) MX[B]E [6] -1 0xe7000000 - 0xe7ffffff (0x1000000) MX[B]E [7] -1 0xe8010000 - 0xe801ffff (0x10000) MX[B]E [8] -1 0xe0000000 - 0xe3ffffff (0x4000000) MX[B]E [9] -1 0xe6000000 - 0xe6ffffff (0x1000000) MX[B](B) [10] -1 0xe4000000 - 0xe4ffffff (0x1000000) MX[B](B) [11] -1 0x00000000 - 0x000001ff (0x200) IX[B]E [12] -1 0x0000e400 - 0x0000e4ff (0x100) IX[B]E [13] -1 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [14] -1 0x0000dc00 - 0x0000dcff (0x100) IX[B]E [15] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [16] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [17] -1 0x0000d000 - 0x0000d0ff (0x100) IX[B]E (II) Primary Device is: PCI 01:00:0 (II) NV: driver for NVIDIA chipsets: RIVA128, RIVATNT, RIVATNT2, RIVATNT2 (Ultra), RIVATNT2 (Vanta), RIVATNT2 M64, RIVATNT2 (Integrated), GeForce 256, GeForce DDR, Quadro, GeForce2 GTS, GeForce2 GTS (rev 1), GeForce2 ultra, Quadro 2 Pro, GeForce2 MX, GeForce2 MX DDR, Quadro 2 MXR, GeForce 2 Go S3VProbe begin (II) Loading sub module "cirrus_laguna" (II) LoadModule: "cirrus_laguna" (II) Loading /usr/X11R6/lib/modules/drivers/cirrus_laguna.o (II) Module cirrus_laguna: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 ABI class: XFree86 Video Driver, version 0.3 (II) Loading sub module "cirrus_alpine" (II) LoadModule: "cirrus_alpine" (II) Loading /usr/X11R6/lib/modules/drivers/cirrus_alpine.o (II) Module cirrus_alpine: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 ABI class: XFree86 Video Driver, version 0.3 (II) ATI: Shared non-ATI VGA in PCI/AGP slot 1:0:0 detected. CYRIX: Device Sections found: 1 (II) VESA: driver for VESA chipsets: vesa (II) VGA: Generic VGA driver (version 4.0) for chipsets: generic (++) Using config file: "/root/XF86Config.new" Markers: (--) probed, (**) from config file, (=3D=3D) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (=3D=3D) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fon= ts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/u= sr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (--) Chipset RIVATNT found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0xe8000000 - 0xe800ffff (0x10000) MX[B]E [6] -1 0xe7000000 - 0xe7ffffff (0x1000000) MX[B]E [7] -1 0xe8010000 - 0xe801ffff (0x10000) MX[B]E [8] -1 0xe0000000 - 0xe3ffffff (0x4000000) MX[B]E [9] -1 0xe6000000 - 0xe6ffffff (0x1000000) MX[B](B) [10] -1 0xe4000000 - 0xe4ffffff (0x1000000) MX[B](B) [11] -1 0x00000000 - 0x000001ff (0x200) IX[B]E [12] -1 0x0000e400 - 0x0000e4ff (0x100) IX[B]E [13] -1 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [14] -1 0x0000dc00 - 0x0000dcff (0x100) IX[B]E [15] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [16] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [17] -1 0x0000d000 - 0x0000d0ff (0x100) IX[B]E (II) resource ranges after probing: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0xe8000000 - 0xe800ffff (0x10000) MX[B]E [6] -1 0xe7000000 - 0xe7ffffff (0x1000000) MX[B]E [7] -1 0xe8010000 - 0xe801ffff (0x10000) MX[B]E [8] -1 0xe0000000 - 0xe3ffffff (0x4000000) MX[B]E [9] -1 0xe6000000 - 0xe6ffffff (0x1000000) MX[B](B) [10] -1 0xe4000000 - 0xe4ffffff (0x1000000) MX[B](B) [11] 0 0x000a0000 - 0x000affff (0x10000) MS[B] [12] 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [13] 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [14] -1 0x00000000 - 0x000001ff (0x200) IX[B]E [15] -1 0x0000e400 - 0x0000e4ff (0x100) IX[B]E [16] -1 0x0000e000 - 0x0000e0ff (0x100) IX[B]E [17] -1 0x0000dc00 - 0x0000dcff (0x100) IX[B]E [18] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [19] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [20] -1 0x0000d000 - 0x0000d0ff (0x100) IX[B]E [21] 0 0x000003b0 - 0x000003bb (0xc) IS[B] [22] 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 ABI class: XFree86 Video Driver, version 0.3 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/libint10.a (II) Module int10: vendor=3D"The XFree86 Project" compiled for 4.0.2, module version =3D 1.0.0 ABI class: XFree86 Video Driver, version 0.3 (II) NV(0): initializing int10 (=3D=3D) NV(0): Write-combining range (0xa0000,0x20000) was already clear (=3D=3D) NV(0): Write-combining range (0xf0000,0x10000) (II) xf86ReadBIOS(0, 0, Buf, 600)-> d0 e7 00 f0... (II) xf86ReadBIOS(c0000, 0, Buf, 10000)-> 55 aa 40 eb... (II) xf86ReadBIOS(d0000, 0, Buf, 10000)-> ff ff ff ff... (II) xf86ReadBIOS(e0000, 0, Buf, 10000)-> ff ff ff ff... Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/cirr= us_alpine.o is unresolved! Symbol vgaHWSetStdFuncs from module /usr/X11R6/lib/modules/drivers/cirrus_a= lpine.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/sili= conmotion_drv.o is unresolved! Symbol vgaHWSetStdFuncs from module /usr/X11R6/lib/modules/drivers/siliconm= otion_drv.o is unresolved! Symbol vgaHWSetStdFuncs from module /usr/X11R6/lib/modules/drivers/siliconm= otion_drv.o is unresolved! Symbol vgaHWCopyReg from module /usr/X11R6/lib/modules/drivers/siliconmotio= n_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/sili= conmotion_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/sili= conmotion_drv.o is unresolved! Symbol fbdevHWDPMSSet from module /usr/X11R6/lib/modules/drivers/fbdev_drv.= o is unresolved! Symbol fbdevHWGetType from module /usr/X11R6/lib/modules/drivers/fbdev_drv.= o is unresolved! Symbol fbdevHWGetType from module /usr/X11R6/lib/modules/drivers/fbdev_drv.= o is unresolved! Symbol fbdevHWLinearOffset from module /usr/X11R6/lib/modules/drivers/fbdev= _drv.o is unresolved! Symbol fbdevHWGetLineLength from module /usr/X11R6/lib/modules/drivers/fbde= v_drv.o is unresolved! Symbol fbdevHWGetType from module /usr/X11R6/lib/modules/drivers/fbdev_drv.= o is unresolved! Symbol fbdevHWGetLineLength from module /usr/X11R6/lib/modules/drivers/fbde= v_drv.o is unresolved! Symbol fbdevHWSetVideoModes from module /usr/X11R6/lib/modules/drivers/fbde= v_drv.o is unresolved! Symbol XAAInitDualFramebufferOverlay from module /usr/X11R6/lib/modules/dri= vers/chips_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/chip= s_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/chip= s_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/chip= s_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/chip= s_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/tdfx= _drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/neom= agic_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/neom= agic_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/neom= agic_drv.o is unresolved! Symbol vgaHWSetStdFuncs from module /usr/X11R6/lib/modules/drivers/neomagic= _drv.o is unresolved! Symbol drmSiSAgpInit from module /usr/X11R6/lib/modules/drivers/sis_drv.o i= s unresolved! Symbol XAAGCIndex from module /usr/X11R6/lib/modules/drivers/tga_drv.o is u= nresolved! Symbol XAAGCIndex from module /usr/X11R6/lib/modules/drivers/tga_drv.o is u= nresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/tga_drv.= o is unresolved! Symbol RamDacFreeRec from module /usr/X11R6/lib/modules/drivers/tga_drv.o i= s unresolved! Symbol RamDacHandleColormaps from module /usr/X11R6/lib/modules/drivers/tga= _drv.o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/tga_drv.= o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/tga_drv.= o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/tga_drv.= o is unresolved! Symbol BTramdacProbe from module /usr/X11R6/lib/modules/drivers/tga_drv.o i= s unresolved! Symbol RamDacDestroyInfoRec from module /usr/X11R6/lib/modules/drivers/tga_= drv.o is unresolved! Symbol RamDacInit from module /usr/X11R6/lib/modules/drivers/tga_drv.o is u= nresolved! Symbol RamDacCreateInfoRec from module /usr/X11R6/lib/modules/drivers/tga_d= rv.o is unresolved! Symbol TIramdacCalculateMNPForClock from module /usr/X11R6/lib/modules/driv= ers/glint_drv.o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/glint_dr= v.o is unresolved! Symbol XAAMoveDWORDS_FixedBase from module /usr/X11R6/lib/modules/drivers/g= lint_drv.o is unresolved! Symbol XAAMoveDWORDS_FixedBase from module /usr/X11R6/lib/modules/drivers/g= lint_drv.o is unresolved! Symbol TIramdacCalculateMNPForClock from module /usr/X11R6/lib/modules/driv= ers/glint_drv.o is unresolved! Symbol IBMramdac640CalculateMNPCForClock from module /usr/X11R6/lib/modules= /drivers/glint_drv.o is unresolved! Symbol IBMramdac526CalculateMNPCForClock from module /usr/X11R6/lib/modules= /drivers/glint_drv.o is unresolved! Symbol IBMramdac526CalculateMNPCForClock from module /usr/X11R6/lib/modules= /drivers/glint_drv.o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/glint_dr= v.o is unresolved! Symbol IBMramdac526CalculateMNPCForClock from module /usr/X11R6/lib/modules= /drivers/glint_drv.o is unresolved! Symbol IBMramdac526CalculateMNPCForClock from module /usr/X11R6/lib/modules= /drivers/glint_drv.o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/glint_dr= v.o is unresolved! Symbol RamDacFreeRec from module /usr/X11R6/lib/modules/drivers/glint_drv.o= is unresolved! Symbol RamDacHandleColormaps from module /usr/X11R6/lib/modules/drivers/gli= nt_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/glin= t_drv.o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/glint_dr= v.o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/glint_dr= v.o is unresolved! Symbol RamDacGetHWIndex from module /usr/X11R6/lib/modules/drivers/glint_dr= v.o is unresolved! Symbol RamDacDestroyInfoRec from module /usr/X11R6/lib/modules/drivers/glin= t_drv.o is unresolved! Symbol RamDacInit from module /usr/X11R6/lib/modules/drivers/glint_drv.o is= unresolved! Symbol RamDacCreateInfoRec from module /usr/X11R6/lib/modules/drivers/glint= _drv.o is unresolved! Symbol RamDacCreateInfoRec from module /usr/X11R6/lib/modules/drivers/glint= _drv.o is unresolved! Symbol IBMramdacProbe from module /usr/X11R6/lib/modules/drivers/glint_drv.= o is unresolved! Symbol RamDacDestroyInfoRec from module /usr/X11R6/lib/modules/drivers/glin= t_drv.o is unresolved! Symbol RamDacInit from module /usr/X11R6/lib/modules/drivers/glint_drv.o is= unresolved! Symbol RamDacCreateInfoRec from module /usr/X11R6/lib/modules/drivers/glint= _drv.o is unresolved! Symbol TIramdacProbe from module /usr/X11R6/lib/modules/drivers/glint_drv.o= is unresolved! Symbol RamDacDestroyInfoRec from module /usr/X11R6/lib/modules/drivers/glin= t_drv.o is unresolved! Symbol RamDacInit from module /usr/X11R6/lib/modules/drivers/glint_drv.o is= unresolved! Symbol TIramdacLoadPalette from module /usr/X11R6/lib/modules/drivers/glint= _drv.o is unresolved! Symbol RamDacCreateInfoRec from module /usr/X11R6/lib/modules/drivers/glint= _drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/rade= on_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/atim= isc_drv.o is unresolved! Symbol drmR128ResetCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmR128StartCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmR128ResetCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmR128StartCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmR128WaitForIdleCCE from module /usr/X11R6/lib/modules/drivers/r12= 8_drv.o is unresolved! Symbol drmR128ResetCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmR128StartCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/r128= _drv.o is unresolved! Symbol drmR128StartCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StartCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmAgpVendorId from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmAgpDeviceId from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmMap from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unre= solved! Symbol drmMap from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unre= solved! Symbol drmMap from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unre= solved! Symbol drmMap from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unre= solved! Symbol drmR128InitCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StartCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.= o is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128StopCCE from module /usr/X11R6/lib/modules/drivers/r128_drv.o= is unresolved! Symbol drmR128CleanupCCE from module /usr/X11R6/lib/modules/drivers/r128_dr= v.o is unresolved! Symbol drmUnmap from module /usr/X11R6/lib/modules/drivers/r128_drv.o is un= resolved! Symbol drmUnmap from module /usr/X11R6/lib/modules/drivers/r128_drv.o is un= resolved! Symbol drmUnmap from module /usr/X11R6/lib/modules/drivers/r128_drv.o is un= resolved! Symbol drmUnmap from module /usr/X11R6/lib/modules/drivers/r128_drv.o is un= resolved! Symbol drmAgpUnbind from module /usr/X11R6/lib/modules/drivers/r128_drv.o i= s unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/mga_= drv.o is unresolved! Symbol XAA_888_plus_PICT_a8_to_8888 from module /usr/X11R6/lib/modules/driv= ers/mga_drv.o is unresolved! Symbol drmMap from module /usr/X11R6/lib/modules/drivers/mga_drv.o is unres= olved! Symbol drmUnmap from module /usr/X11R6/lib/modules/drivers/mga_drv.o is unr= esolved! Symbol DRIGetDrawableStamp from module /usr/X11R6/lib/modules/drivers/mga_d= rv.o is unresolved! Symbol DRIGetDrawableInfo from module /usr/X11R6/lib/modules/drivers/mga_dr= v.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/nv_d= rv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/nv_d= rv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/nv_d= rv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/s3vi= rge_drv.o is unresolved! Symbol vgaHWCopyReg from module /usr/X11R6/lib/modules/drivers/s3virge_drv.= o is unresolved! Symbol vgaHWSetStdFuncs from module /usr/X11R6/lib/modules/drivers/s3virge_= drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/s3vi= rge_drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/s3vi= rge_drv.o is unresolved! Symbol XAACopyROP_PM from module /usr/X11R6/lib/modules/drivers/s3virge_drv= .o is unresolved! Symbol XAACopyROP_PM from module /usr/X11R6/lib/modules/drivers/s3virge_drv= .o is unresolved! Symbol XAACopyROP_PM from module /usr/X11R6/lib/modules/drivers/s3virge_drv= .o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/trid= ent_drv.o is unresolved! Symbol XAAPixmapOps from module /usr/X11R6/lib/modules/drivers/apm_drv.o is= unresolved! Symbol XAAPixmapOps from module /usr/X11R6/lib/modules/drivers/apm_drv.o is= unresolved! Symbol XAAPixmapOps from module /usr/X11R6/lib/modules/drivers/apm_drv.o is= unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/i128= _drv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/vesa= _drv.o is unresolved! Symbol shadowAlloc from module /usr/X11R6/lib/modules/drivers/vesa_drv.o is= unresolved! Symbol shadowUpdatePlanar4 from module /usr/X11R6/lib/modules/drivers/vesa_= drv.o is unresolved! Symbol shadowUpdatePlanar4x8 from module /usr/X11R6/lib/modules/drivers/ves= a_drv.o is unresolved! Symbol shadowUpdatePacked from module /usr/X11R6/lib/modules/drivers/vesa_d= rv.o is unresolved! Symbol shadowUpdatePacked from module /usr/X11R6/lib/modules/drivers/vesa_d= rv.o is unresolved! Symbol xf86SetDDCproperties from module /usr/X11R6/lib/modules/drivers/cirr= us_laguna.o is unresolved! Symbol xf86InterpretEDID from module /usr/X11R6/lib/modules/libvbe.a is unr= esolved! Fatal server error: Caught signal 11. Server aborting When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.8.log". Please report problems to xfree86@xfree86.org. --xkXJwpr35CY/Lc3I-- --RMedoP2+Pr6Rq0N2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: XCjKuTyd0MyYBlk+7bZq3T+sTaQUlovr iQA/AwUBOlsdZ6mWNQ7RrPkAEQIDMACgmRft05qkxqPu845feQJzrTMPhgcAoLEn n6UAQb1vaeE8J53SeOYDGMbp =XFZr -----END PGP SIGNATURE----- --RMedoP2+Pr6Rq0N2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 7:11:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 2D12E37B400; Tue, 9 Jan 2001 07:11:13 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 4228218BD; Tue, 9 Jan 2001 10:11:12 -0500 (EST) Date: Tue, 9 Jan 2001 10:11:12 -0500 From: Will Andrews To: The Hermit Hacker Cc: freebsd-ports@FreeBSD.ORG, kevlo@FreeBSD.ORG, jmz@FreeBSD.org Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... Message-ID: <20010109101112.F867@puck.firepipe.net> Reply-To: Will Andrews , FreeBSD Ports References: <20010108172445.P649@puck.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Tue, Jan 09, 2001 at 09:12:08AM -0400 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 09:12:08AM -0400, The Hermit Hacker wrote: > from what I can tell right now, the problem is in either 4.2-STABLE *or* > the XF-4.0.2 port ... I just wiped out everything, so that I'm startign > with a clean slate (rm -rf /usr/X11R6 /usr/local) and can't get > XFree-4.0.2 to install now without pthread errors ... The problem with QT/KDE is a result of the fact that X402 now builds GL with threads. If X402 is not building anymore, that's a new problem and should be taken up with Jean-Marc. -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 7:24:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 0BE7537B400; Tue, 9 Jan 2001 07:24:09 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f09FMk774779; Tue, 9 Jan 2001 11:22:46 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 9 Jan 2001 11:22:45 -0400 (AST) From: The Hermit Hacker To: Will Andrews , FreeBSD Ports Cc: , , Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... In-Reply-To: <20010109101112.F867@puck.firepipe.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 On Tue, 9 Jan 2001, Will Andrews wrote: > On Tue, Jan 09, 2001 at 09:12:08AM -0400, The Hermit Hacker wrote: > > from what I can tell right now, the problem is in either 4.2-STABLE *or* > > the XF-4.0.2 port ... I just wiped out everything, so that I'm startign > > with a clean slate (rm -rf /usr/X11R6 /usr/local) and can't get > > XFree-4.0.2 to install now without pthread errors ... > > The problem with QT/KDE is a result of the fact that X402 now builds GL > with threads. If X402 is not building anymore, that's a new problem and > should be taken up with Jean-Marc. Here's what my suspicion is right now ... recently, I reported a problem where KDE (from CVS) wouldn't compile due to mcopidl SegFault'ng ... someone answered back that there is a problem with -pthread in -current *AND* -stable ... I'm wondering if this is the same thing creeping in? Or "something completely different"? Jean-Marc? I'm running the latest -STABLE on this machine ... as of yesterday, and am just about to update it again based on changes since, just in case I'm right and its been fixed ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8: 7:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ms39.hinet.net (ms39.hinet.net [168.95.4.39]) by hub.freebsd.org (Postfix) with ESMTP id 9654537B402; Tue, 9 Jan 2001 08:07:01 -0800 (PST) Received: from freebsd.esnsi.com (freebsd.esnsi.com [210.241.235.251]) by ms39.hinet.net (8.8.8/8.8.8) with SMTP id AAA01807; Wed, 10 Jan 2001 00:06:43 +0800 (CST) Message-Id: <200101091606.AAA01807@ms39.hinet.net> Date: Wed, 10 Jan 2001 00:10:36 +0000 From: Kevin Lo To: The Hermit Hacker Cc: Will Andrews , FreeBSD Ports , freebsd-stable@FreeBSD.ORG, jmz@FreeBSD.ORG Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... (fwd) In-Reply-To: References: X-Mailer: Sylpheed version 0.4.4 (GTK+ 1.2.8; FreeBSD 4.2-20001202-STABLE; i386) 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 Hermit Hacker wrote: > On Tue, 9 Jan 2001, Will Andrews wrote: > > > On Tue, Jan 09, 2001 at 09:12:08AM -0400, The Hermit Hacker wrote: > > > from what I can tell right now, the problem is in either 4.2-STABLE *or* > > > the XF-4.0.2 port ... I just wiped out everything, so that I'm startign > > > with a clean slate (rm -rf /usr/X11R6 /usr/local) and can't get > > > XFree-4.0.2 to install now without pthread errors ... > > > > The problem with QT/KDE is a result of the fact that X402 now builds GL > > with threads. If X402 is not building anymore, that's a new problem and > > should be taken up with Jean-Marc. > > Here's what my suspicion is right now ... recently, I reported a problem > where KDE (from CVS) wouldn't compile due to mcopidl SegFault'ng ... > someone answered back that there is a problem with -pthread in -current > *AND* -stable ... I'm wondering if this is the same thing creeping in? Or > "something completely different"? I just reinstalled qt22 and kde2 ports about three days ago. I have no problems with -pthread issue on -STABLE. BTW, I use XFree3.6.6. > Jean-Marc? > > I'm running the latest -STABLE on this machine ... as of yesterday, and am > just about to update it again based on changes since, just in case I'm > right and its been fixed ... - Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8:11:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from panda.FreeBSDsystems.COM (unknown [24.69.168.19]) by hub.freebsd.org (Postfix) with ESMTP id 2F2F037B402; Tue, 9 Jan 2001 08:11:19 -0800 (PST) Received: (from lnb@localhost) by panda.FreeBSDsystems.COM (8.11.1/8.11.1) id f09GBFD79805; Tue, 9 Jan 2001 11:11:15 -0500 (EST) (envelope-from lnb) Date: Tue, 9 Jan 2001 11:11:15 -0500 From: Lanny Baron To: The Hermit Hacker Cc: Will Andrews , FreeBSD Ports , freebsd-stable@FreeBSD.ORG, kevlo@FreeBSD.ORG, jmz@FreeBSD.ORG Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... Message-ID: <20010109111115.D70171@panda.FreeBSDsystems.COM> References: <20010109101112.F867@puck.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Tue, Jan 09, 2001 at 11:22:45AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am wondering if you just want to use kde2. I have installed them both (kde11 and kde2) from /usr/ports/x11/kd*. However there is a certain order you must do. For the life of me I can't remember. I do know you need to install kde11 (i think you start at libs then base)but my problem was with Kmail and the way (or lack of) it handles gnupg. So I took a different route. /stand/sysinstall and went to options to change to RELEASE from STABLE then to Xconfig and did the kde. Next i went into packages and into KDE and selected kde2 and it places an x on the dependencies. Hope that provides a solution for you. Lanny On Tue, Jan 09, 2001 at 11:22:45AM -0400, The Hermit Hacker wrote: > On Tue, 9 Jan 2001, Will Andrews wrote: > > > On Tue, Jan 09, 2001 at 09:12:08AM -0400, The Hermit Hacker wrote: > > > from what I can tell right now, the problem is in either 4.2-STABLE *or* > > > the XF-4.0.2 port ... I just wiped out everything, so that I'm startign > > > with a clean slate (rm -rf /usr/X11R6 /usr/local) and can't get > > > XFree-4.0.2 to install now without pthread errors ... > > > > The problem with QT/KDE is a result of the fact that X402 now builds GL > > with threads. If X402 is not building anymore, that's a new problem and > > should be taken up with Jean-Marc. > > Here's what my suspicion is right now ... recently, I reported a problem > where KDE (from CVS) wouldn't compile due to mcopidl SegFault'ng ... > someone answered back that there is a problem with -pthread in -current > *AND* -stable ... I'm wondering if this is the same thing creeping in? Or > "something completely different"? > > Jean-Marc? > > I'm running the latest -STABLE on this machine ... as of yesterday, and am > just about to update it again based on changes since, just in case I'm > right and its been fixed ... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- ------------------------------------- Lanny Baron Proud to be 100% FreeBSD FreeBSD Systems, Inc; Freedom Technologies Corp. http://www.FreeBSDsystems.COM 1.877.963.1900 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8:21:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 3676B37B6AE; Tue, 9 Jan 2001 08:21:23 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f09GJvo75579; Tue, 9 Jan 2001 12:19:57 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 9 Jan 2001 12:19:57 -0400 (AST) From: The Hermit Hacker To: Lanny Baron Cc: Will Andrews , FreeBSD Ports , , , Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... In-Reply-To: <20010109111115.D70171@panda.FreeBSDsystems.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 right now, I just want to get a make install of XFree86-4.0.2 to work :( On Tue, 9 Jan 2001, Lanny Baron wrote: > Hi, > I am wondering if you just want to use kde2. I have installed them both (kde11 and kde2) from /usr/ports/x11/kd*. However there is a certain order you must do. For the life of me I can't remember. I do know you need to install kde11 (i think you start at libs then base)but my problem was with Kmail and the way (or lack of) it handles gnupg. > > So I took a different route. /stand/sysinstall and went to options to change to RELEASE from STABLE then to Xconfig and did the kde. Next i went into packages and into KDE and selected kde2 and it places an x on the dependencies. > > Hope that provides a solution for you. > > Lanny > > > > On Tue, Jan 09, 2001 at 11:22:45AM -0400, The Hermit Hacker wrote: > > On Tue, 9 Jan 2001, Will Andrews wrote: > > > > > On Tue, Jan 09, 2001 at 09:12:08AM -0400, The Hermit Hacker wrote: > > > > from what I can tell right now, the problem is in either 4.2-STABLE *or* > > > > the XF-4.0.2 port ... I just wiped out everything, so that I'm startign > > > > with a clean slate (rm -rf /usr/X11R6 /usr/local) and can't get > > > > XFree-4.0.2 to install now without pthread errors ... > > > > > > The problem with QT/KDE is a result of the fact that X402 now builds GL > > > with threads. If X402 is not building anymore, that's a new problem and > > > should be taken up with Jean-Marc. > > > > Here's what my suspicion is right now ... recently, I reported a problem > > where KDE (from CVS) wouldn't compile due to mcopidl SegFault'ng ... > > someone answered back that there is a problem with -pthread in -current > > *AND* -stable ... I'm wondering if this is the same thing creeping in? Or > > "something completely different"? > > > > Jean-Marc? > > > > I'm running the latest -STABLE on this machine ... as of yesterday, and am > > just about to update it again based on changes since, just in case I'm > > right and its been fixed ... > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > ------------------------------------- > Lanny Baron > Proud to be 100% FreeBSD > FreeBSD Systems, Inc; Freedom Technologies Corp. > http://www.FreeBSDsystems.COM > 1.877.963.1900 > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8:22:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id DB9DE37B6B4; Tue, 9 Jan 2001 08:21:52 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f09GKQU75635; Tue, 9 Jan 2001 12:20:26 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 9 Jan 2001 12:20:26 -0400 (AST) From: The Hermit Hacker To: Kevin Lo Cc: Will Andrews , FreeBSD Ports , , Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... (fwd) In-Reply-To: <200101091606.AAA01807@ms39.hinet.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 On Wed, 10 Jan 2001, Kevin Lo wrote: > The Hermit Hacker wrote: > > > On Tue, 9 Jan 2001, Will Andrews wrote: > > > > > On Tue, Jan 09, 2001 at 09:12:08AM -0400, The Hermit Hacker wrote: > > > > from what I can tell right now, the problem is in either 4.2-STABLE *or* > > > > the XF-4.0.2 port ... I just wiped out everything, so that I'm startign > > > > with a clean slate (rm -rf /usr/X11R6 /usr/local) and can't get > > > > XFree-4.0.2 to install now without pthread errors ... > > > > > > The problem with QT/KDE is a result of the fact that X402 now builds GL > > > with threads. If X402 is not building anymore, that's a new problem and > > > should be taken up with Jean-Marc. > > > > Here's what my suspicion is right now ... recently, I reported a problem > > where KDE (from CVS) wouldn't compile due to mcopidl SegFault'ng ... > > someone answered back that there is a problem with -pthread in -current > > *AND* -stable ... I'm wondering if this is the same thing creeping in? Or > > "something completely different"? > > I just reinstalled qt22 and kde2 ports about three days ago. > I have no problems with -pthread issue on -STABLE. > BTW, I use XFree3.6.6. Ya, but XFree3.6.6 didn't use -pthread(s), did it? > > > Jean-Marc? > > > > I'm running the latest -STABLE on this machine ... as of yesterday, and am > > just about to update it again based on changes since, just in case I'm > > right and its been fixed ... > > - Kevin > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8:38:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [208.184.13.195]) by hub.freebsd.org (Postfix) with ESMTP id 8B53A37B6BA for ; Tue, 9 Jan 2001 08:38:24 -0800 (PST) Received: from onceler.kciLink.com (onceler.kciLink.com [208.184.13.196]) by yertle.kciLink.com (Postfix) with ESMTP id 85F392E443 for ; Tue, 9 Jan 2001 11:38:23 -0500 (EST) Received: (from khera@localhost) by onceler.kciLink.com (8.11.1/8.11.1) id f09GcNe60888; Tue, 9 Jan 2001 11:38:23 -0500 (EST) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14939.15999.339574.284445@onceler.kciLink.com> Date: Tue, 9 Jan 2001 11:38:23 -0500 To: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: <200101082356.QAA01425@freeway.dcfinc.com> References: <200101082356.QAA01425@freeway.dcfinc.com> X-Mailer: VM 6.88 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "CRL" == Chad R Larson writes: CRL> | chad> ifconfig fxp0 CRL> | fxp0: flags=8843 mtu 1500 CRL> | inet 192.168.1.129 netmask 0xffffff00 broadcast 192.168.1.255 CRL> | ether 00:a0:c9:49:ec:ca CRL> | media: autoselect CRL> | supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP CRL> +--------------- CRL> How can I tell if this interface is running 100/full or 10/half? It isn't connected. Note the "media" line as compared to the output of mine: [onceler]% ifconfig fxp0 fxp0: flags=8843 mtu 1500 inet 208.184.13.196 netmask 0xffffff00 broadcast 208.184.13.255 ether 00:e0:18:ac:14:21 media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP Is the link light on the card on or off? There should also be a 10/100 light that is on for 100baseT (full or half). -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8:49: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hub.lovett.com (hub.lovett.com [216.60.121.161]) by hub.freebsd.org (Postfix) with ESMTP id B1A2C37B698; Tue, 9 Jan 2001 08:48:39 -0800 (PST) Received: from ade by hub.lovett.com with local (Exim 3.20 #1) id 14G1wm-000EB8-00; Tue, 09 Jan 2001 10:48:32 -0600 Date: Tue, 9 Jan 2001 10:48:32 -0600 From: Ade Lovett To: The Hermit Hacker Cc: FreeBSD Ports , freebsd-stable@FreeBSD.ORG Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... Message-ID: <20010109104832.J49646@FreeBSD.org> References: <20010109111115.D70171@panda.FreeBSDsystems.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Tue, Jan 09, 2001 at 12:19:57PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 12:19:57PM -0400, The Hermit Hacker wrote: > > right now, I just want to get a make install of XFree86-4.0.2 to work :( Personally, I'd stick with the individual ports, rather than x11/XFree86-4, which not only has pthread issues, but is also not prefix safe (installs a whole bunch of crud in /etc/X11), and installation will lead to numerous weird errors later on as packages/ports try to register their dependencies on imake-4.0.1, XFree86-libraries-4.0.1_2 etc.. (after all, that's what bento is using to build the packages). Adding a suitable BROKEN tag to x11/XFree86-4 might help speed up resolution, or at least back out the changes that caused this whole mess. -aDe -- Ade Lovett, Austin, TX. ade@FreeBSD.org FreeBSD: The Power to Serve 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 Jan 9 8:51:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 7A99637B6C4 for ; Tue, 9 Jan 2001 08:51:29 -0800 (PST) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.20 #1) id 14FzmL-000FJM-00 for freebsd-stable@freebsd.org; Tue, 09 Jan 2001 14:29:37 +0000 To: freebsd-stable@freebsd.org Subject: upgrading mutiple machines... Message-Id: From: Pete French Date: Tue, 09 Jan 2001 14:29:37 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am new to the stable tracking process, but it looks faily simple as far as I can make out (though I cant find a target for make that just rebuilds what I;ve chnaged - do I have to 'make buildworld' *every* time? surely not?) anyway, I have one master machine with all the surce & gubbins on it, plus several slave machines with just a user install on them. I want to keep these in sync by NFS mounting /usr/src and then doing a 'make installworld' on each after building on the master. This works for installing the kernel O.K., but when I use the installworld target I get failures on the NFS machines - they complain about missing files. The same tree works quite happly on the mail machine. So I am worndering several things... 1) Is this actually a sensible thing to do anyway ? I have a worry that I am upgrading NFS whilst it is runnign and it may break horribly. I got the idea from the online documentation though, but I think that just applied to the kernel. 2) Is the fact that I have a smaller distribution on th slave machines going to be recognised, or will an 'installworld' just clobber everything and install compilers, include files, etc... if I use 'installmost' then that implies it will not upgrade libraries though - so what happens when a shared library changes ? 3) Do I neeed to set maproot=root on the NFS ? I currently have it set as 'nobody' as I assumed an 'installworld' would only need read access. It works fr the ketenl after all. Any helpful hintsor pointers to the correct documentation would be much appreciated. Also the solution to not having to wait 5 hours after only changing one file ! :-) cheers, -pete french. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8:55:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id DFBC337B6C0; Tue, 9 Jan 2001 08:55:08 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f09Grok75997; Tue, 9 Jan 2001 12:53:50 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 9 Jan 2001 12:53:49 -0400 (AST) From: The Hermit Hacker To: Ade Lovett Cc: FreeBSD Ports , , Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... In-Reply-To: <20010109104832.J49646@FreeBSD.org> 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, 9 Jan 2001, Ade Lovett wrote: > On Tue, Jan 09, 2001 at 12:19:57PM -0400, The Hermit Hacker wrote: > > > > right now, I just want to get a make install of XFree86-4.0.2 to work :( > > Personally, I'd stick with the individual ports, rather than x11/XFree86-4, > which not only has pthread issues, but is also not prefix safe > (installs a whole bunch of crud in /etc/X11), and installation will lead > to numerous weird errors later on as packages/ports try to register > their dependencies on imake-4.0.1, XFree86-libraries-4.0.1_2 etc.. > (after all, that's what bento is using to build the packages). > > Adding a suitable BROKEN tag to x11/XFree86-4 might help speed up > resolution, or at least back out the changes that caused this whole mess. Can someone out there confirm that I'm not the only one hitting this problem? I'm running under the potentially mistaken assumption here that Jean-Marc has/is testing his changes before committing them, and that the problem is on my side ... but if others are also experiencing it, then it should definitely be marked as BROKEN ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8:59:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhub1.rjf.com (mailhub1.rjf.com [170.12.128.128]) by hub.freebsd.org (Postfix) with ESMTP id EECFB37B6C2; Tue, 9 Jan 2001 08:59:12 -0800 (PST) Received: from exmta5.rjf.com by mailhub1.rjf.com with ESMTP; Tue, 9 Jan 2001 11:56:13 -0500 Received: by exmta5.rjf.com with Internet Mail Service (5.5.2650.21) id ; Tue, 9 Jan 2001 11:59:11 -0500 Message-Id: <6D5097D4B56AD31190D50008C7B1579BC97DD3@exlan5.rjf.com> From: Ian Cartwright To: 'The Hermit Hacker' , Ade Lovett Cc: FreeBSD Ports , jmz@freebsd.org, freebsd-stable@FreeBSD.org Subject: RE: kdesupport2 fails to compile on 4.2-STABLE ... Date: Tue, 9 Jan 2001 11:59:09 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: The Hermit Hacker [mailto:scrappy@hub.org] > Sent: Tuesday, January 09, 2001 11:54 AM > To: Ade Lovett > Cc: FreeBSD Ports; jmz@freebsd.org; freebsd-stable@FreeBSD.org > Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... > > > On Tue, 9 Jan 2001, Ade Lovett wrote: > > > On Tue, Jan 09, 2001 at 12:19:57PM -0400, The Hermit Hacker wrote: > > > > > > right now, I just want to get a make install of > XFree86-4.0.2 to work :( > > > > Personally, I'd stick with the individual ports, rather > than x11/XFree86-4, > > which not only has pthread issues, but is also not prefix safe > > (installs a whole bunch of crud in /etc/X11), and > installation will lead > > to numerous weird errors later on as packages/ports try to register > > their dependencies on imake-4.0.1, XFree86-libraries-4.0.1_2 etc.. > > (after all, that's what bento is using to build the packages). > > > > Adding a suitable BROKEN tag to x11/XFree86-4 might help speed up > > resolution, or at least back out the changes that caused > this whole mess. > > Can someone out there confirm that I'm not the only one hitting this > problem? I'm running under the potentially mistaken > assumption here that > Jean-Marc has/is testing his changes before committing them, > and that the > problem is on my side ... but if others are also experiencing > it, then it > should definitely be marked as BROKEN ... > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > I am also having a problem with pthreads when compiling the XFree86-4 port. The port makes ok but make install failes when trying to link some of the libraries. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 8:59:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id EBB2E37B6C6 for ; Tue, 9 Jan 2001 08:59:37 -0800 (PST) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 14G27S-000Iuu-00; Tue, 09 Jan 2001 08:59:34 -0800 Date: Tue, 9 Jan 2001 08:59:32 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Pete French Cc: freebsd-stable@freebsd.org Subject: Re: upgrading mutiple machines... 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, 9 Jan 2001, Pete French wrote: ... > keep these in sync by NFS mounting /usr/src and then doing a > 'make installworld' on each after building on the master. ... You have to export and mount /usr/obj too. You should be able to make both exports (/usr/src & /usr/obj) read-only, although in the past installworld used to require write access. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 9: 4:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 9F35B37B6C2; Tue, 9 Jan 2001 09:04:12 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f09H2qh76179; Tue, 9 Jan 2001 13:02:52 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 9 Jan 2001 13:02:52 -0400 (AST) From: The Hermit Hacker To: Ian Cartwright Cc: Ade Lovett , FreeBSD Ports , , Subject: RE: kdesupport2 fails to compile on 4.2-STABLE ... In-Reply-To: <6D5097D4B56AD31190D50008C7B1579BC97DD3@exlan5.rjf.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, 9 Jan 2001, Ian Cartwright wrote: > > -----Original Message----- > > From: The Hermit Hacker [mailto:scrappy@hub.org] > > Sent: Tuesday, January 09, 2001 11:54 AM > > To: Ade Lovett > > Cc: FreeBSD Ports; jmz@freebsd.org; freebsd-stable@FreeBSD.org > > Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... > > > > > > On Tue, 9 Jan 2001, Ade Lovett wrote: > > > > > On Tue, Jan 09, 2001 at 12:19:57PM -0400, The Hermit Hacker wrote: > > > > > > > > right now, I just want to get a make install of > > XFree86-4.0.2 to work :( > > > > > > Personally, I'd stick with the individual ports, rather > > than x11/XFree86-4, > > > which not only has pthread issues, but is also not prefix safe > > > (installs a whole bunch of crud in /etc/X11), and > > installation will lead > > > to numerous weird errors later on as packages/ports try to register > > > their dependencies on imake-4.0.1, XFree86-libraries-4.0.1_2 etc.. > > > (after all, that's what bento is using to build the packages). > > > > > > Adding a suitable BROKEN tag to x11/XFree86-4 might help speed up > > > resolution, or at least back out the changes that caused > > this whole mess. > > > > Can someone out there confirm that I'm not the only one hitting this > > problem? I'm running under the potentially mistaken > > assumption here that > > Jean-Marc has/is testing his changes before committing them, > > and that the > > problem is on my side ... but if others are also experiencing > > it, then it > > should definitely be marked as BROKEN ... > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > I am also having a problem with pthreads when compiling the XFree86-4 port. > The port makes ok but make install failes when trying to link some of the > libraries. Okay, this is definitely what I'm hitting right now ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 9:27: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id D4C1137B6CA for ; Tue, 9 Jan 2001 09:26:50 -0800 (PST) Received: (from pfrench@localhost) by dilbert.fcg.co.uk (8.11.1/8.11.1) id f09HQmg01436; Tue, 9 Jan 2001 17:26:49 GMT (envelope-from pfrench) Date: Tue, 9 Jan 2001 17:26:49 GMT From: Pete French Message-Id: <200101091726.f09HQmg01436@dilbert.fcg.co.uk> To: tom@uniserve.com Subject: Re: upgrading mutiple machines... Cc: freebsd-stable@freebsd.org In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You have to export and mount /usr/obj too. You should be able to make > both exports (/usr/src & /usr/obj) read-only, although in the past > installworld used to require write access. I have both /usr/src and /usr/obj mounted read-[only and now it works fine. I ended up doing a 'make buildworld' on the master again and that fixed the problem (unsure why, but it work now so I;m not complaining!) cheers, -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 9:27:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id C0E6737B6C9; Tue, 9 Jan 2001 09:27:21 -0800 (PST) Received: (from root@localhost) by dsl.MexComUSA.net (8.11.1/8.11.1) id f09HMe318511; Tue, 9 Jan 2001 09:22:40 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from 63.205.16.202 ( [63.205.16.202]) as user eculp@EnContacto.Net by Mail.MexComUSA.net with HTTP; Tue, 9 Jan 2001 09:22:38 -0800 Message-ID: <979060958.3a5b48dee4894@Mail.MexComUSA.net> Date: Tue, 9 Jan 2001 09:22:38 -0800 From: Edwin Culp To: The Hermit Hacker Cc: Ade Lovett , FreeBSD Ports , jmz@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.6-cvs Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting The Hermit Hacker : > On Tue, 9 Jan 2001, Ade Lovett wrote: > > > On Tue, Jan 09, 2001 at 12:19:57PM -0400, The Hermit Hacker wrote: > > > > > > right now, I just want to get a make install of XFree86-4.0.2 to work > :( > > > > Personally, I'd stick with the individual ports, rather than > x11/XFree86-4, > > which not only has pthread issues, but is also not prefix safe > > (installs a whole bunch of crud in /etc/X11), and installation will lead > > to numerous weird errors later on as packages/ports try to register > > their dependencies on imake-4.0.1, XFree86-libraries-4.0.1_2 etc.. > > (after all, that's what bento is using to build the packages). > > > > Adding a suitable BROKEN tag to x11/XFree86-4 might help speed up > > resolution, or at least back out the changes that caused this whole mess. > > Can someone out there confirm that I'm not the only one hitting this > problem? I'm running under the potentially mistaken assumption here that > Jean-Marc has/is testing his changes before committing them, and that the > problem is on my side ... but if others are also experiencing it, then it > should definitely be marked as BROKEN ... > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-ports" in the body of the message > I went through the same problems with kde2 after installing XFree86-4.02 but on Current about 10 days ago and ended up installing some of the precompiled packages and compiling others, in desperation. Luckily, it all seems to work. I've been waiting to see if it is fixed to reinstall "correctly:-)" Saludos, ed -- EnContacto.Net - InternetSalon.Org - CafeMania.Net -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 9:44:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by hub.freebsd.org (Postfix) with ESMTP id EFDB537B6D0 for ; Tue, 9 Jan 2001 09:43:54 -0800 (PST) Received: from [216.64.45.172] (helo=akane) by hobbiton.shire.net with esmtp (Exim 2.04 #5) id 14G2oM-0005NU-00 for freebsd-stable@freebsd.org; Tue, 9 Jan 2001 10:43:54 -0700 Date: Tue, 09 Jan 2001 12:22:18 -0500 From: "Chad Leigh, Pengar Enterprises, Inc. & Shire.Net LLC" Reply-To: chad@pengar.com To: freebsd-stable@freebsd.org Subject: 4.2-RELEASE ld-elf problem Message-ID: <7100000.979060938@akane> X-Mailer: Mulberry/2.0.6b2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I just upgraded by doing an upgrade install from 4.0-RELEASE to 4.2-RELEASE. Now, the dirname and basename programs don't work correctly. I get /usr/libexec/ld-elf.so.1: basename: Undefined symbol "basename" (and the dirname equivalent) whenever they are used (like installing ports or compiling apps). It appears I have a missing library or ldconfig is screwed up or something. But I don't know where to start. Any hints appreciated. thanks Chad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 9:58:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from digital.csudsu.com (digital.csudsu.com [209.249.57.102]) by hub.freebsd.org (Postfix) with ESMTP id 5548437B6DB; Tue, 9 Jan 2001 09:58:25 -0800 (PST) Received: by digital.csudsu.com (Postfix, from userid 1000) id D6AA422E01; Tue, 9 Jan 2001 09:58:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by digital.csudsu.com (Postfix) with ESMTP id C6B0F1F001; Tue, 9 Jan 2001 09:58:30 -0800 (PST) Date: Tue, 9 Jan 2001 09:58:30 -0800 (PST) From: Stefan Molnar To: The Hermit Hacker Cc: Ian Cartwright , Ade Lovett , FreeBSD Ports , , Subject: RE: kdesupport2 fails to compile on 4.2-STABLE ... 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 I built and installed kdebase2 with the standard make install on XFree4, buillt the day before. And no isues. The dates were Jan 4 and Jan 5 on a -STABLE built on the Dec 30th On Tue, 9 Jan 2001, The Hermit Hacker wrote: > On Tue, 9 Jan 2001, Ian Cartwright wrote: > > > > -----Original Message----- > > > From: The Hermit Hacker [mailto:scrappy@hub.org] > > > Sent: Tuesday, January 09, 2001 11:54 AM > > > To: Ade Lovett > > > Cc: FreeBSD Ports; jmz@freebsd.org; freebsd-stable@FreeBSD.org > > > Subject: Re: kdesupport2 fails to compile on 4.2-STABLE ... > > > > > > > > > On Tue, 9 Jan 2001, Ade Lovett wrote: > > > > > > > On Tue, Jan 09, 2001 at 12:19:57PM -0400, The Hermit Hacker wrote: > > > > > > > > > > right now, I just want to get a make install of > > > XFree86-4.0.2 to work :( > > > > > > > > Personally, I'd stick with the individual ports, rather > > > than x11/XFree86-4, > > > > which not only has pthread issues, but is also not prefix safe > > > > (installs a whole bunch of crud in /etc/X11), and > > > installation will lead > > > > to numerous weird errors later on as packages/ports try to register > > > > their dependencies on imake-4.0.1, XFree86-libraries-4.0.1_2 etc.. > > > > (after all, that's what bento is using to build the packages). > > > > > > > > Adding a suitable BROKEN tag to x11/XFree86-4 might help speed up > > > > resolution, or at least back out the changes that caused > > > this whole mess. > > > > > > Can someone out there confirm that I'm not the only one hitting this > > > problem? I'm running under the potentially mistaken > > > assumption here that > > > Jean-Marc has/is testing his changes before committing them, > > > and that the > > > problem is on my side ... but if others are also experiencing > > > it, then it > > > should definitely be marked as BROKEN ... > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > I am also having a problem with pthreads when compiling the XFree86-4 port. > > The port makes ok but make install failes when trying to link some of the > > libraries. > > Okay, this is definitely what I'm hitting right now ... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 10: 7: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 7F02237B6DE for ; Tue, 9 Jan 2001 10:06:48 -0800 (PST) Received: from grolsch.ai (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id DCB9A49; Tue, 9 Jan 2001 14:06:43 -0400 (AST) Date: Tue, 09 Jan 2001 14:06:42 -0400 From: "Jeroen C. van Gelderen" To: Jonathan Lemon , stable@freebsd.org Subject: Re: Intel PRO/100+ driver or hardware? (Update) Message-ID: <89010000.979063602@grolsch.ai> In-Reply-To: <200101081521.f08FLDi31948@prism.flugsvamp.com> X-Mailer: Mulberry/2.0.6b2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Monday, January 08, 2001 09:21:13 -0600 Jonathan Lemon wrote: [...] > It looks like 'hayek' is refusing to accept one of the segments that > 'keynes' is transmitting. The segment arrives at the machine, but > 'hayek' never sends an ACK. > > I'd look at 'netstat -s' and see whether any of the 'bad checksum' > counters are set, if so, then something is corrupting the packets. Just the flag I needed :-) As soon as the connection stalls, the bad-checksum counter goes trough the roof. And *every* re-transmitted packet seems to have a bad checksum as well. The hub is not busy at the moment I tried and none of the other TCP connections to and from this box are affected when this occurs. It seems that packets with certain content get mangled so that retransmits will never solve the problem. For the record, the fxp0 has mostly been fixed at 10baseT/UTP but I've tested all possible permutations of the media(opt) settings. I've tried 6 cables so far, all good quality. No difference. I've also tried a different, known-good hub (Netgear DS108) which exhibits the same problem. I am now quite positive that the rest of my networking hardware is okay and the problem must be with the Intel card or with the Asus K7V mobo with PCI riser card. Replacing the Intel card with a spare doesn't help. Replacing the Intel card with a 3Com 905B does however solve the problem. An SMC card doesn't have any trouble either. I don't see a single bad checksum after transferring 1 GB of data. My conclusion is that the Intel cards I have are broken. They refuse to work reliably in an otherwise healthy low-end network. I may have a bad batch or maybe these cards are broken by design. The question now becomes: what cards do people recommend? 3Com 905B seems a logical choice. I've also never had any trouble with the cheap SMC cards I have lying around. > Does this happen even if you connect the machines back to back (with > a crossover cable?) I don't have a cross-over cable unfortunately, and I won't be able to buy one where I am :-( I seem to recall however that Intel cards don't like being connected back2back? Thanks, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 10:14:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3E4FB37B401 for ; Tue, 9 Jan 2001 10:14:19 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA28251 for ; Tue, 9 Jan 2001 10:14:18 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f09IEHo77081 for stable@freebsd.org; Tue, 9 Jan 2001 10:14:17 -0800 (PST) (envelope-from obrien) Date: Tue, 9 Jan 2001 10:14:17 -0800 From: "David O'Brien" To: stable@freebsd.org Subject: ** HEADS UP ** C++ threading believed to be fixed Message-ID: <20010109101417.A77048@dragon.nuxi.com> Reply-To: stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have committed changes to the way we build the C/C++ compiler support code (libgcc). This should fix the various problems people have been seeing since just before 4.2-RELEASE with Mozilla, MySQL, and other threaded applications. If you still have problems, please send me bug reports. Enjoy! -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 10:16:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 3BC8D37B401 for ; Tue, 9 Jan 2001 10:16:04 -0800 (PST) Received: from grolsch.ai (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id A40D949; Tue, 9 Jan 2001 14:16:03 -0400 (AST) Date: Tue, 09 Jan 2001 14:16:03 -0400 From: "Jeroen C. van Gelderen" To: "Jeffrey J. Mountin" , Stefan Molnar Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? Message-ID: <107550000.979064163@grolsch.ai> In-Reply-To: <4.3.2.20010108174340.020ee910@207.227.119.2> X-Mailer: Mulberry/2.0.6b2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Monday, January 08, 2001 17:53:12 -0600 "Jeffrey J. Mountin" wrote: > At 08:17 AM 1/8/01 -0800, Stefan Molnar wrote: > >> I have noticed that the eepro does not like some hubs/switches. >> I have a netgear 8 port 10mb switch, and the eepro just goes to >> a crawl with the same things you see. I have tried over a dozen >> eepro cards (had this switch for almost 2 years), and countless >> ethernet cables. I bought a 4 port hub, connected the xover to the >> swtitch and the eepro on the hub, and bamf, those problems went >> away. The tulip cards that most of the eepros replaced worked >> very happly. > > Almost every 8255x card works just fine with a Netgear FS105 here in all > modes. Say "almost" since I don't have an old 82556 card around. One of > systems has a newer version on an Asus A7V running -stable, so doubt the > problem is with FBSD or the card. Good cables and nailing down the modes > fix most problems. Most likely a hardware or disposition, as we seem to > say "doesn't like" when problems like this crop up, issue here. I just replied to Jonathan Lemon's mail describing why I think it doesn't look like bad cabling, wrong duplex/speed settings or bad hubs. I'm fairly convinced that my fxp cards are to blame. Either a bad batch of cards or a rather marginal design that doesn't like hubs (or cheap switches)... Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 10:16:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhub1.rjf.com (mailhub1.rjf.com [170.12.128.128]) by hub.freebsd.org (Postfix) with ESMTP id 6304837B6A1 for ; Tue, 9 Jan 2001 10:16:14 -0800 (PST) Received: from [170.12.9.16] by mailhub1.rjf.com with ESMTP for stable@freebsd.org; Tue, 9 Jan 2001 13:13:12 -0500 Received: by GOLDFISH3 with Internet Mail Service (5.5.2650.21) id ; Tue, 9 Jan 2001 13:14:49 -0500 Message-Id: <6D5097D4B56AD31190D50008C7B1579BC97DD6@exlan5.rjf.com> From: Ian Cartwright To: "'stable@freebsd.org'" Subject: RE: ** HEADS UP ** C++ threading believed to be fixed Date: Tue, 9 Jan 2001 13:16:09 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does this mean a buildworld needs to be done to fix these problems? Cheers Ian -----Original Message----- From: David O'Brien [mailto:TrimYourCc@NUXI.com] Sent: Tuesday, January 09, 2001 1:14 PM To: stable@freebsd.org Subject: ** HEADS UP ** C++ threading believed to be fixed I have committed changes to the way we build the C/C++ compiler support code (libgcc). This should fix the various problems people have been seeing since just before 4.2-RELEASE with Mozilla, MySQL, and other threaded applications. If you still have problems, please send me bug reports. Enjoy! -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 10:31:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9B34E37B699 for ; Tue, 9 Jan 2001 10:31:02 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA28405; Tue, 9 Jan 2001 10:31:01 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f09IV0q77347; Tue, 9 Jan 2001 10:31:00 -0800 (PST) (envelope-from obrien) Date: Tue, 9 Jan 2001 10:31:00 -0800 From: "David O'Brien" To: Ian Cartwright Cc: "'stable@freebsd.org'" Subject: Re: ** HEADS UP ** C++ threading believed to be fixed Message-ID: <20010109103100.A77327@dragon.nuxi.com> Reply-To: stable@freebsd.org References: <6D5097D4B56AD31190D50008C7B1579BC97DD6@exlan5.rjf.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <6D5097D4B56AD31190D50008C7B1579BC97DD6@exlan5.rjf.com>; from ICartwright@IT.RJF.com on Tue, Jan 09, 2001 at 01:16:09PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 01:16:09PM -0500, Ian Cartwright wrote: > Does this mean a buildworld needs to be done to fix these problems? Yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 10:32:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhub1.rjf.com (mailhub1.rjf.com [170.12.128.128]) by hub.freebsd.org (Postfix) with ESMTP id A0B2B37B400 for ; Tue, 9 Jan 2001 10:32:26 -0800 (PST) Received: from exmta2.rjf.com by mailhub1.rjf.com with ESMTP; Tue, 9 Jan 2001 13:29:27 -0500 Received: by exmta.rjf.com with Internet Mail Service (5.5.2650.21) id ; Tue, 9 Jan 2001 13:32:25 -0500 Message-Id: <6D5097D4B56AD31190D50008C7B1579BC97DD7@exlan5.rjf.com> From: Ian Cartwright To: "'Jeroen C. van Gelderen'" , "Jeffrey J. Mountin" , Stefan Molnar Cc: freebsd-stable@FreeBSD.ORG Subject: RE: Intel PRO/100+ driver or hardware? Date: Tue, 9 Jan 2001 13:32:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A few weeks back I mentioned a similar problem I was having with a Compaq Dexkpro EN. It has a built in 82559 chip. Under FreeBSD it would hang every so often with a device timeout. Under Win2k it works great. I tried everything I could think of (swapping cables, hubs, etc.) with no success for FreeBSD. I tried the mailing lists but no one saw my post I guess. ;-/ I hope this helps to corroborate your story... Ian -----Original Message----- From: Jeroen C. van Gelderen [mailto:jeroen@vangelderen.org] Sent: Tuesday, January 09, 2001 1:16 PM To: Jeffrey J. Mountin; Stefan Molnar Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? --On Monday, January 08, 2001 17:53:12 -0600 "Jeffrey J. Mountin" wrote: > At 08:17 AM 1/8/01 -0800, Stefan Molnar wrote: > >> I have noticed that the eepro does not like some hubs/switches. >> I have a netgear 8 port 10mb switch, and the eepro just goes to >> a crawl with the same things you see. I have tried over a dozen >> eepro cards (had this switch for almost 2 years), and countless >> ethernet cables. I bought a 4 port hub, connected the xover to the >> swtitch and the eepro on the hub, and bamf, those problems went >> away. The tulip cards that most of the eepros replaced worked >> very happly. > > Almost every 8255x card works just fine with a Netgear FS105 here in all > modes. Say "almost" since I don't have an old 82556 card around. One of > systems has a newer version on an Asus A7V running -stable, so doubt the > problem is with FBSD or the card. Good cables and nailing down the modes > fix most problems. Most likely a hardware or disposition, as we seem to > say "doesn't like" when problems like this crop up, issue here. I just replied to Jonathan Lemon's mail describing why I think it doesn't look like bad cabling, wrong duplex/speed settings or bad hubs. I'm fairly convinced that my fxp cards are to blame. Either a bad batch of cards or a rather marginal design that doesn't like hubs (or cheap switches)... Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 10:58:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apocalypse.cdsnet.net (apocalypse.cdsnet.net [63.163.68.5]) by hub.freebsd.org (Postfix) with ESMTP id BAA4037B401 for ; Tue, 9 Jan 2001 10:58:14 -0800 (PST) Received: (from mrcpu@localhost) by apocalypse.cdsnet.net (8.11.1/8.11.1) id f09J1JM13727 for stable@freebsd.org; Tue, 9 Jan 2001 11:01:19 -0800 (PST) (envelope-from mrcpu) Date: Tue, 9 Jan 2001 11:01:18 -0800 From: Jaye Mathisen To: stable@freebsd.org Subject: Repeated panic in 4.2-stable Message-ID: <20010109110118.H32287@apocalypse.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG L440 GX+ motherboard, 2 P3 550's, 1GB ECC RAM. I'm getting the followin crash after anywhere from 2-8 hours of operation pretty consistently. Fans have been checked, airflow is good. The machine is driving a 14 drive vinum array (930GB), and news service. It seems to be load related with news, as just farting around with the vinum array (rebuilding and such) doesn't cause any problems, but inn kills it. here's a backtrace from a debugging kernel. (I have the vmcore and kernel file if anybody wants me to poke around a bit more: #0 dumpsys () at ../../kern/kern_shutdown.c:469 #1 0xc0135713 in boot (howto=260) at ../../kern/kern_shutdown.c:309 #2 0xc0135ac4 in poweroff_wait (junk=0xc02712ef, howto=0) at ../../kern/kern_shutdown.c:556 #3 0xc02403cf in trap_fatal (frame=0xff806c60, eva=16) at ../../i386/i386/trap.c:951 #4 0xc0240065 in trap_pfault (frame=0xff806c60, usermode=0, eva=16) at ../../i386/i386/trap.c:844 #5 0xc023fbd3 in trap (frame={tf_fs = 851992, tf_es = -1071054832, tf_ds = 16, tf_edi = 1, tf_esi = 4096, tf_ebp = -8360712, tf_isp = -8360820, tf_ebx = 0, tf_edx = 32, tf_ecx = 77824, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071589508, tf_cs = 8, tf_eflags = 66118, tf_esp = -458452928, tf_ss = 0}) at ../../i386/i386/trap.c:443 #6 0xc020d77c in vnode_pager_generic_putpages (vp=0xe4ac9040, m=0xff806d98, bytecount=4096, flags=0, rtvals=0xff806d68) at machine/globals.h:114 #7 0xc01f8a46 in ffs_putpages (ap=0xff806d2c) at ../../ufs/ufs/ufs_readwrite.c:695 #8 0xc020d60a in vnode_pager_putpages (object=0xe4c019c0, m=0xff806d98, count=1, sync=0, rtvals=0xff806d68) at vnode_if.h:1126 #9 0xc020a62f in vm_pageout_flush (mc=0xff806d98, count=1, flags=0) at ../../vm/vm_pager.h:145 #10 0xc0207cbf in vm_object_page_clean (object=0xe4c019c0, start=0, end=0, flags=4) at ../../vm/vm_object.c:655 #11 0xc0162579 in vfs_msync (mp=0xc5b56200, flags=2) at ../../kern/vfs_subr.c:2522 #12 0xc0163724 in sync (p=0xc02ad480, uap=0x0) at ../../kern/vfs_syscalls.c:544 #13 0xc01354ee in boot (howto=256) at ../../kern/kern_shutdown.c:233 #14 0xc0135ac4 in poweroff_wait (junk=0xc02712ae, howto=19) at ../../kern/kern_shutdown.c:556 #15 0xc02403cf in trap_fatal (frame=0xff806fac, eva=0) at ../../i386/i386/trap.c:951 #16 0xc023fd1f in trap (frame={tf_fs = 24, tf_es = -1071513584, tf_ds = -1071513584, tf_edi = -1, tf_esi = 0, tf_ebp = -8359948, tf_isp = -8359976, tf_ebx = 0, tf_edx = 554, tf_ecx = -8359940, tf_eax = -1431655488, tf_trapno = 19, tf_err = 0, tf_eip = -1071363110, tf_cs = 8, tf_eflags = 2051, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:613 #17 0xc0244bda in vm_page_zero_idle () at ../../i386/i386/vm_machdep.c:565 I'm thinking maybe RAM problems, but wouldn't have guess it to be in the vm_page stuff, would've guessed more something with NMI's or some such. But it's not an area I have any real knowledge in. Any tips appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 11: 5:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id C044537B699 for ; Tue, 9 Jan 2001 11:04:55 -0800 (PST) Received: (from dkelly@localhost) by grumpy.dyndns.org (8.11.1/8.11.1) id f09J4di48504; Tue, 9 Jan 2001 13:04:39 -0600 (CST) (envelope-from dkelly) Date: Tue, 9 Jan 2001 13:04:39 -0600 From: David Kelly To: "Jeroen C. van Gelderen" Cc: Jonathan Lemon , stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? (Update) Message-ID: <20010109130439.A48418@grumpy.dyndns.org> References: <200101081521.f08FLDi31948@prism.flugsvamp.com> <89010000.979063602@grolsch.ai> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <89010000.979063602@grolsch.ai>; from jeroen@vangelderen.org on Tue, Jan 09, 2001 at 02:06:42PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 02:06:42PM -0400, Jeroen C. van Gelderen wrote: > --On Monday, January 08, 2001 09:21:13 -0600 Jonathan Lemon > wrote: > [...] > > It looks like 'hayek' is refusing to accept one of the segments that > > 'keynes' is transmitting. The segment arrives at the machine, but > > 'hayek' never sends an ACK. > > > > I'd look at 'netstat -s' and see whether any of the 'bad checksum' > > counters are set, if so, then something is corrupting the packets. > > Just the flag I needed :-) As soon as the connection stalls, the > bad-checksum counter goes trough the roof. And *every* re-transmitted > packet seems to have a bad checksum as well. > > The hub is not busy at the moment I tried and none of the other TCP > connections to and from this box are affected when this occurs. It seems > that packets with certain content get mangled so that retransmits will > never solve the problem. OK, that seems to be part of the key. You have hit on a data pattern which will not make it thru some part of the link. Not an unheard of situation. Often an impedance mismatch where the pattern resonates and "rings" an extra bit out of place. Hard to say if the problem is the hub or the Intel card. But seemingly the combination. Changing either to a different model and/or brand solves the problem? Any chance you can capture and/or share the problem data? -- David Kelly N4HHE, dkelly@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 Jan 9 11:43:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bitbucket.extern.uniface.nl (bitbucket.extern.uniface.nl [193.78.88.139]) by hub.freebsd.org (Postfix) with ESMTP id 6040B37B402 for ; Tue, 9 Jan 2001 11:43:23 -0800 (PST) Received: from bh2.nl.compuware.com (unknown [172.16.17.82]) by bitbucket.extern.uniface.nl (Postfix) with ESMTP id 5E9B0828E for ; Tue, 9 Jan 2001 20:43:21 +0100 (CET) Received: from c1111.nl.compuware.com ([172.16.16.36]) by bh2.nl.compuware.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id CTC95GWC; Tue, 9 Jan 2001 20:43:21 +0100 Received: from nl.compuware.com (bertd@localhost [127.0.0.1]) by c1111.nl.compuware.com (8.9.3/8.9.3) with ESMTP id UAA27163 for ; Tue, 9 Jan 2001 20:43:21 +0100 (CET) Message-ID: <3A5B69D8.C46CE2D1@nl.compuware.com> Date: Tue, 09 Jan 2001 20:43:20 +0100 From: Bert Driehuis Organization: Compuware Europe (but I only speak for myself) X-Mailer: Mozilla 4.74 [en] (X11; U; BSD/OS 4.1 i386) X-Accept-Language: en, fr MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: Intel PRO/100+ driver or hardware? (Update) References: <89010000.979063602@grolsch.ai> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeroen C. van Gelderen" wrote: > My conclusion is that the Intel cards I have are broken. They refuse to > work reliably in an otherwise healthy low-end network. I may have a bad > batch or maybe these cards are broken by design. It is possible your motherboard vendor screwed up: http://developer.intel.com/design/support/faq/82559.htm Apparently, some motherboard vendors let boards go out with wrong wiring or capacitors (see the bottom of the page), and the symptoms match yours (which, I must stress, may very well be a coincidence). It is no doubt an oversight that this info is on the web site, seeing that the "errata" for the 8255x seem to be available under NDA only... And those errata make the difference between a reliable and an unreliable drivern (actually, I think the developers did have access to the errata; I see a workaround for at least one known issue with the 82559 in the if_fxp.c source). Incidentally, the 3Com 3C905TX is actually worse in this respect than the Intel 100Pro. Cheers, -- Bert -- Bert Driehuis, MIS -- bert_driehuis@nl.compuware.com -- +31-20-3116119 Dihydrogen Monoxide kills! Join the campaign at http://www.dhmo.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 11:45:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id C699F37B404 for ; Tue, 9 Jan 2001 11:44:52 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f09JkJP06692; Tue, 9 Jan 2001 13:46:19 -0600 (CST) (envelope-from jlemon) Date: Tue, 9 Jan 2001 13:46:18 -0600 From: Jonathan Lemon To: "Jeroen C. van Gelderen" Cc: Jonathan Lemon , stable@freebsd.org Subject: Re: Intel PRO/100+ driver or hardware? (Update) Message-ID: <20010109134618.L29115@prism.flugsvamp.com> References: <200101081521.f08FLDi31948@prism.flugsvamp.com> <89010000.979063602@grolsch.ai> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <89010000.979063602@grolsch.ai> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 02:06:42PM -0400, Jeroen C. van Gelderen wrote: > --On Monday, January 08, 2001 09:21:13 -0600 Jonathan Lemon > wrote: > [...] > > It looks like 'hayek' is refusing to accept one of the segments that > > 'keynes' is transmitting. The segment arrives at the machine, but > > 'hayek' never sends an ACK. > > > > I'd look at 'netstat -s' and see whether any of the 'bad checksum' > > counters are set, if so, then something is corrupting the packets. > > Just the flag I needed :-) As soon as the connection stalls, the > bad-checksum counter goes trough the roof. And *every* re-transmitted > packet seems to have a bad checksum as well. > > The hub is not busy at the moment I tried and none of the other TCP > connections to and from this box are affected when this occurs. It seems > that packets with certain content get mangled so that retransmits will > never solve the problem. I did have a similar problem with an early netgear FS509 switch; it would consistently refuse to transmit certain data patterns. Netgear support confirmed that there was memory problem with certain revisions and sent me a new switch; it's worked fine thereafter. > My conclusion is that the Intel cards I have are broken. They refuse to > work reliably in an otherwise healthy low-end network. I may have a bad > batch or maybe these cards are broken by design. That's possible. The other possibility is that the driver may be at fault; it may need further updating for the 82559 chip variants. > > Does this happen even if you connect the machines back to back (with > > a crossover cable?) > > I don't have a cross-over cable unfortunately, and I won't be able to buy > one where I am :-( I seem to recall however that Intel cards don't like > being connected back2back? Not that I know of; any cards should work with a crossover cable. By doing this, you can at least isolate whether the problem is with the switch/hub, or with the cards themselves. I use a mixture of Intel, 3com and various gigabit cards with no problems. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 11:47:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 5C23137B401 for ; Tue, 9 Jan 2001 11:47:08 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f09JkiU50586; Tue, 9 Jan 2001 11:46:44 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Jan 2001 11:46:44 -0800 (PST) From: Matt Dillon Message-Id: <200101091946.f09JkiU50586@earth.backplane.com> To: Jaye Mathisen Cc: stable@FreeBSD.ORG Subject: Re: Repeated panic in 4.2-stable References: <20010109110118.H32287@apocalypse.cdsnet.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :L440 GX+ motherboard, 2 P3 550's, 1GB ECC RAM. : :I'm getting the followin crash after anywhere from 2-8 hours of :operation pretty consistently. Fans have been checked, airflow is :good. : :The machine is driving a 14 drive vinum array (930GB), and :news service. : :It seems to be load related with news, as just farting around :with the vinum array (rebuilding and such) doesn't cause any :problems, but inn kills it. : :here's a backtrace from a debugging kernel. (I have the :vmcore and kernel file if anybody wants me to poke around :a bit more: If you could make the vmcore availabel to me (give me the path in private email), along with the debug kernel image if you have it, /var/run/dmesg.boot, and kernel configuration, I will take a look at it. Hold old is the source base you built the kernel from? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 11:47:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id DC50437B400 for ; Tue, 9 Jan 2001 11:47:16 -0800 (PST) Received: from grolsch.ai (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id DF57249; Tue, 9 Jan 2001 15:47:15 -0400 (AST) Date: Tue, 09 Jan 2001 15:47:15 -0400 From: "Jeroen C. van Gelderen" To: David Kelly Cc: Jonathan Lemon , stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? (Update) Message-ID: <179010000.979069635@grolsch.ai> In-Reply-To: <20010109130439.A48418@grumpy.dyndns.org> X-Mailer: Mulberry/2.0.6b2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Tuesday, January 09, 2001 13:04:39 -0600 David Kelly wrote: > On Tue, Jan 09, 2001 at 02:06:42PM -0400, Jeroen C. van Gelderen wrote: >> --On Monday, January 08, 2001 09:21:13 -0600 Jonathan Lemon >> wrote: >> [...] >> > It looks like 'hayek' is refusing to accept one of the segments that >> > 'keynes' is transmitting. The segment arrives at the machine, but >> > 'hayek' never sends an ACK. >> > >> > I'd look at 'netstat -s' and see whether any of the 'bad checksum' >> > counters are set, if so, then something is corrupting the packets. >> >> Just the flag I needed :-) As soon as the connection stalls, the >> bad-checksum counter goes trough the roof. And *every* re-transmitted >> packet seems to have a bad checksum as well. >> >> The hub is not busy at the moment I tried and none of the other TCP >> connections to and from this box are affected when this occurs. It seems >> that packets with certain content get mangled so that retransmits will >> never solve the problem. > > OK, that seems to be part of the key. You have hit on a data pattern > which will not make it thru some part of the link. Not an unheard of > situation. Often an impedance mismatch where the pattern resonates > and "rings" an extra bit out of place. Ah, so it may not just be my vivid imagination ;-) > Hard to say if the problem is the hub or the Intel card. But seemingly > the combination. Changing either to a different model and/or brand > solves the problem? I tried 2 hubs, one claims to be a cheap 8816TPC, the other NetGear DS108. Both give problems. Replacing the Intel card with a 3Com or SMC solves the problem. Of course I've tried multiple cables as well. Maybe this is relevant. The DS108 actually is a dual speed hub. IIRC it has a 10 Mbit bus and a 100 Mbit bus, connected with a little switch. The machine I'm testing against has a 10Mbit card. I tried forcing to Intel to 10Mbit and tried to transfer the file. It stalls after a couple of megabytes. I then forced the Intel card to 100Mbit mode and tried the transfer again (so it would have to go trough the switching device in the hub); That got me a little further (22 MB) but this transfer too stalled eventually. > Any chance you can capture and/or share the problem data? More than willing to, but I'm not sure how to do it most effectively. You just want the tcpdump data? Do I need to give any special arguments to tcpdump? Thanks + Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 12:11:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id CFBA537B404 for ; Tue, 9 Jan 2001 12:11:33 -0800 (PST) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Jan 2001 20:11:32 +0000 (GMT) To: Matt Dillon Cc: Jaye Mathisen , stable@FreeBSD.ORG, iedowse@maths.tcd.ie Subject: Re: Repeated panic in 4.2-stable In-Reply-To: Your message of "Tue, 09 Jan 2001 11:46:44 PST." <200101091946.f09JkiU50586@earth.backplane.com> Date: Tue, 09 Jan 2001 20:11:32 +0000 From: Ian Dowse Message-ID: <200101092011.aa63743@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101091946.f09JkiU50586@earth.backplane.com>, Matt Dillon writes: >:here's a backtrace from a debugging kernel. (I have the >:vmcore and kernel file if anybody wants me to poke around >:a bit more: > > If you could make the vmcore availabel to me (give me the > path in private email), along with the debug kernel image > if you have it, /var/run/dmesg.boot, and kernel configuration, > I will take a look at it. I had suggested to Jaye that he use a filesystem with 16k/4k blocks/frags, since the ffs code was writing off the end of the superblock fs_csp[] array with 8k/1k blocks (I'm working on getting this fixed). Since then I noticed an old message from one of the mailing lists (I can't seem to find it right now) mentioning that people have seen significant problems running big filesystems with less than 8 frags per block. I think a 16k/2k filesystem will still avoid the superblock corruption, so this would be worth a try instead. However, we should obviously try to find what is causing the problems with non-standard frags per block... Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 13: 8:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bellona.asdf.com (bellona.asdf.com [205.138.138.158]) by hub.freebsd.org (Postfix) with ESMTP id 8397037B69D for ; Tue, 9 Jan 2001 13:07:57 -0800 (PST) Received: from localhost (xlogan@localhost) by bellona.asdf.com (8.9.3/8.9.3) with ESMTP id QAA77920 for ; Tue, 9 Jan 2001 16:07:56 -0500 (EST) (envelope-from xlogan@novagate.net) X-Authentication-Warning: bellona.asdf.com: xlogan owned process doing -bs Date: Tue, 9 Jan 2001 16:07:56 -0500 (EST) From: -=X=- To: freebsd-stable@FreeBSD.ORG Subject: Re: /var drive space problem In-Reply-To: <3A59D273.CB58B4D0@tsolab.org> 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 Mon, 8 Jan 2001, Daniel Tso wrote: > Why would you want a 250M root ? I always keep root small, usually the > default 32M or 40M. It limits the possible damage and makes it much > easier to restore. One thing we found is that if you have a lot of users on a box and your /etc/master.passwd file is > 10 megs, you end up with a /etc/passwd file of ~9 megs, an /etc/pwd.db file of ~ 9 megs and an /etc/spwd.db file of ~ 10 megs. Added up, that is just about 40 megs. Then if you go to add another user in and you do a pwd_mkdb, it makes copies of the password files in /etc/, and you end up filling up the root partition and pwd_mkdb dies out with an error. We eventually went from a 50 meg partition to a 256 meg partition for /. -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 13:14:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id B470C37B69B for ; Tue, 9 Jan 2001 13:14:12 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA19567; Tue, 9 Jan 2001 13:07:31 -0800 (PST) Message-Id: <200101092107.NAA19567@implode.root.com> To: Bert Driehuis Cc: stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? (Update) In-reply-to: Your message of "Tue, 09 Jan 2001 20:43:20 +0100." <3A5B69D8.C46CE2D1@nl.compuware.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 09 Jan 2001 13:07:31 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It is no doubt an oversight that this info is on the web site, seeing >that the "errata" for the 8255x seem to be available under NDA only... >And those errata make the difference between a reliable and an >unreliable drivern (actually, I think the developers did have access to >the errata; I see a workaround for at least one known issue with the >82559 in the if_fxp.c source). > >Incidentally, the 3Com 3C905TX is actually worse in this respect than >the Intel 100Pro. I did have access to an early copy of the errata, but it was a mistake that I got it without an NDA. Fortunately the 82557/8/9 had relatively few problems to begin with and the driver is very solid as a result. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 13:14:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id E360D37B69E for ; Tue, 9 Jan 2001 13:14:40 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f09LETI51662; Tue, 9 Jan 2001 13:14:29 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Jan 2001 13:14:29 -0800 (PST) From: Matt Dillon Message-Id: <200101092114.f09LETI51662@earth.backplane.com> To: Ian Dowse Cc: Jaye Mathisen , stable@FreeBSD.ORG, iedowse@maths.tcd.ie Subject: Re: Repeated panic in 4.2-stable References: <200101092011.aa63743@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's worth trying out the latest -stable first, to see if the problem goes away. Jaye's kernel was from the 19th of December and the traceback was from an msync()/block-allocation sequence, so it could be related to bugs we've fixed since the 19th. On the otherhand, his kernel faulted in the kernel rather then paniced so it could be something more insideous related to the frag size or the large filesystem (internal overflows or something like that), as you posit. It is also possible that the blocksize is only the indirect effect, and that the real problem is that the larger per-cylinder bitmaps are creating more opportunities for Kirk's background bitmap write code (which is independant of softupdates) to interfere with the clustering code. I have a patch for that below (not well tested and Kirk hasn't gotten back to me on it yet so I don't know how real the problem is. It looks real, though). -Matt Index: vfs_cluster.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_cluster.c,v retrieving revision 1.92.2.3 diff -u -r1.92.2.3 vfs_cluster.c --- vfs_cluster.c 2000/12/30 01:51:07 1.92.2.3 +++ vfs_cluster.c 2001/01/06 19:40:52 @@ -392,15 +392,22 @@ tbp = getblk(vp, lbn + i, size, 0, 0); - if ((tbp->b_flags & B_CACHE) || - (tbp->b_flags & B_VMIO) == 0) { + /* + * If the buffer is already fully valid or locked + * (which could also mean that a background write is + * in progress), or the buffer is not backed by VMIO, + * stop. + */ + if ((tbp->b_flags & (B_CACHE|B_LOCKED)) || + (tbp->b_flags & B_VMIO) == 0) { bqrelse(tbp); break; } - for (j = 0;j < tbp->b_npages; j++) + for (j = 0;j < tbp->b_npages; j++) { if (tbp->b_pages[j]->valid) break; + } if (j != tbp->b_npages) { bqrelse(tbp); @@ -701,8 +708,13 @@ while (len > 0) { s = splbio(); + /* + * If the buffer is not delayed-write (i.e. dirty), or it + * is delayed-write but either locked or inval, it cannot + * partake in the clustered write. + */ if (((tbp = gbincore(vp, start_lbn)) == NULL) || - ((tbp->b_flags & (B_INVAL | B_DELWRI)) != B_DELWRI) || + ((tbp->b_flags & (B_LOCKED | B_INVAL | B_DELWRI)) != B_DELWRI) || BUF_LOCK(tbp, LK_EXCLUSIVE | LK_NOWAIT)) { ++start_lbn; --len; @@ -774,12 +786,16 @@ /* * If it IS in core, but has different - * characteristics, don't cluster with it. + * characteristics, or is locked (which + * means it could be undergoing a background + * I/O or be in a weird state), then don't + * cluster with it. */ if ((tbp->b_flags & (B_VMIO | B_CLUSTEROK | B_INVAL | B_DELWRI | B_NEEDCOMMIT)) != (B_DELWRI | B_CLUSTEROK | (bp->b_flags & (B_VMIO | B_NEEDCOMMIT))) || + (tbp->b_flags & B_LOCKED) || tbp->b_wcred != bp->b_wcred || BUF_LOCK(tbp, LK_EXCLUSIVE | LK_NOWAIT)) { splx(s); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 13:52:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id 7F28037B69B for ; Tue, 9 Jan 2001 13:51:45 -0800 (PST) Received: (qmail 25990 invoked from network); 9 Jan 2001 21:51:43 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 9 Jan 2001 21:51:43 -0000 Message-ID: <3A5B87EE.8ACA0D05@gactr.uga.edu> Date: Tue, 09 Jan 2001 16:51:42 -0500 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: buildworld over nfs failing consistently Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok. i really need some help here. i've got several (identical) dell poweredge servers that i've been trying to update for a few weeks now -- all to no avail. i put together a fresh new install on one this morning, cvsup'ed the source and successfully built and installed world. marvelous. now for the other six machines... the fresh box is the NFS server with /etc/exports like so: /usr -alldirs -maproot=root:staff (this is a private network so i'm not too concerned about who's connecting -- only me) the six other servers have this in their /etc/fstab: castro.servers.nat:/usr/src /usr/src nfs rw 0 0 castro.servers.nat:/usr/obj /usr/obj nfs rw 0 0 an installworld on *any* of these machines goes along just fine until getting to: ===> gnu/usr.bin/perl/library/B cd /usr/obj/usr/src/gnu/usr.bin/perl/library/B/ext/B ; make -B install INSTALLP RIVLIB=/usr/libdata/perl/5.00503 INSTALLARCHLIB=/usr/libdata/perl/5.00503/mach where it plods along a bit more until: [...snip...] vm/vnode_pager.h -> vm/vnode_pager.ph *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 17:12:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lcremeans.homeip.net (dsl254-119-131-nyc1.dsl-isp.net [216.254.119.131]) by hub.freebsd.org (Postfix) with ESMTP id 070E837B400 for ; Tue, 9 Jan 2001 17:12:36 -0800 (PST) Received: (from lee@localhost) by lcremeans.homeip.net (8.11.0/8.11.0) id f0A1D4400705; Tue, 9 Jan 2001 20:13:04 -0500 (EST) (envelope-from lee) Date: Tue, 9 Jan 2001 20:13:03 -0500 From: Lee Cremeans To: Lauri Laupmaa Cc: stable@freebsd.org Subject: Re: Compaq dual processor & broken MP table Message-ID: <20010109201303.A671@lcremeans.homeip.net> References: <3A5B0F9D.E986E033@inspiral.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A5B0F9D.E986E033@inspiral.net>; from mauri@inspiral.net on Tue, Jan 09, 2001 at 03:18:21PM +0200 X-OS: FreeBSD 3.0-STABLE Organization: My room? Are you crazy? :) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 03:18:21PM +0200, Lauri Laupmaa wrote: > Hi > > On compaq ML350 dual processor kernel says: > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 > intpin 2 > APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > > Is it some major problem or just annoying message ? It's just saying it's working around a quirk in the IOAPIC setup. It seems to be common on Compaqs; I have a ProLiant 800 (dual PPro 200) that gives a similar message when it boots Linux 2.2. If the machine's working, it's nothing to worry about. -lee -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | | lcremeans@erols.com | http://wakky.dyndns.org/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 17:34:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from diana.infonets.hiroshima-u.ac.jp (diana.infonets.hiroshima-u.ac.jp [133.41.33.53]) by hub.freebsd.org (Postfix) with ESMTP id BC51A37B402 for ; Tue, 9 Jan 2001 17:34:10 -0800 (PST) Received: from cal.infonets.hiroshima-u.ac.jp (cal.infonets.hiroshima-u.ac.jp [133.41.33.61]) by diana.infonets.hiroshima-u.ac.jp (8.11.1/3.7W) with ESMTP id f0A1Ukr61170 for ; Wed, 10 Jan 2001 10:30:46 +0900 (JST) Received: from localhost (localhost.infonets.hiroshima-u.ac.jp [127.0.0.1]) by cal.infonets.hiroshima-u.ac.jp (8.9.3/3.6W) with ESMTP id KAA63033 for ; Wed, 10 Jan 2001 10:34:18 +0900 (JST) To: freebsd-stable@FreeBSD.org Subject: mailinglist From: IMAI Hidetoshi X-Mailer: Mew version 1.94.1 on XEmacs 21.1 (Channel Islands) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010110103418D.hidepin@unknown-domain> Date: Wed, 10 Jan 2001 10:34:18 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 17:41:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 01DA737B400 for ; Tue, 9 Jan 2001 17:41:12 -0800 (PST) Received: (qmail 68081 invoked from network); 10 Jan 2001 01:41:11 -0000 Received: from unknown (HELO prydn.tacni.net) (204.155.159.57) by 216.178.136.168 with SMTP; 10 Jan 2001 01:41:11 -0000 Received: (qmail 92637 invoked by uid 1001); 10 Jan 2001 01:41:08 -0000 Date: Tue, 9 Jan 2001 19:41:08 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Weird files in root Message-ID: <20010109194108.A92622@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For some resaon this keeps appearing in / 0 lrwxr-xr-x 1 root wheel 10 Jan 9 14:49 ttyv0 -> /dev/ttyv0 Anyone know why? -- Erich Zigler I'm locked in a maze of little projects, all of which suck. -- Chris "Saundo" Saunderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 18: 2:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nssolutions.com (unknown [208.37.124.245]) by hub.freebsd.org (Postfix) with ESMTP id 0DD4837B400 for ; Tue, 9 Jan 2001 18:01:54 -0800 (PST) Received: from bradcompaq ([10.0.1.231]) by nssolutions.com (8.8.8/8.8.8) with SMTP id VAA27962 for ; Tue, 9 Jan 2001 21:01:25 -0500 Reply-To: From: "Brad Clemmons" To: Subject: subscribe Date: Tue, 9 Jan 2001 20:56:32 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 18:17:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 60AD637B401 for ; Tue, 9 Jan 2001 18:17:11 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA05199; Tue, 9 Jan 2001 19:17:05 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200101100217.TAA05199@freeway.dcfinc.com> Subject: Re: Intel PRO/100+ driver or hardware? In-Reply-To: <14939.15999.339574.284445@onceler.kciLink.com> from Vivek Khera at "Jan 9, 1 11:38:23 am" To: khera@kciLink.com (Vivek Khera) Date: Tue, 9 Jan 2001 19:17:04 -0700 (MST) Cc: freebsd-stable@FreeBSD.org Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition 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 As I recall, Vivek Khera wrote: > It isn't connected. Note the "media" line as compared to the output > of mine: > > [onceler]% ifconfig fxp0 > fxp0: flags=8843 mtu 1500 > inet 208.184.13.196 netmask 0xffffff00 broadcast 208.184.13.255 > ether 00:e0:18:ac:14:21 > media: autoselect (100baseTX ) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP I've been having an off-line conversation with David Kelley about this. I believe the behavior of displaying the media type selected in the probe output started in the 3.5-RELEASE, and this system is a 2.2.8-RELEASE. I found in /sys/src/pci/if_fxp.c that there is an IOCTL (SIOCGIFMEDIA) that should do the trick with just a small C wrapper program... > Is the link light on the card on or off? There should also be a > 10/100 light that is on for 100baseT (full or half). Link and 100meg is on on both the NIC and the hub. If I trust the Ethernet hardware to properly report what it negotiated (and no reason not to), we got the 100Mbit. No way to know for sure about FDX/HDX. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Vivek Khera, Ph.D. Khera Communications, Inc. > Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 > AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 18:19:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 7988B37B404 for ; Tue, 9 Jan 2001 18:19:18 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id kmosaaaa for ; Wed, 10 Jan 2001 13:27:22 +1100 Message-ID: <3A5BC6C5.96B87778@quake.com.au> Date: Wed, 10 Jan 2001 13:19:49 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable Subject: gif & faith needed? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiyas, I am just wondering if gif and faith pseudo devices are needed for anything? (Besides IPv6 stuff) And what they are for... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 18:20:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 095F437B698 for ; Tue, 9 Jan 2001 18:20:01 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0A2JFf55797; Tue, 9 Jan 2001 18:19:15 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Jan 2001 18:19:15 -0800 (PST) From: Matt Dillon Message-Id: <200101100219.f0A2JFf55797@earth.backplane.com> To: Tor.Egge@fast.no, iedowse@maths.tcd.ie Cc: freebsd-stable@freebsd.org Subject: Re: Repeated panic in 4.2-stable References: <200101100106.f0A16gH54559@earth.backplane.com> <200101100115.CAA03955@midten.fast.no> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ( I think -stable will be interested in this so I'm including -stable in the thread ) ----------> TO EVERYONE RUNNING STABLE!!! Do not use a filesystem block size greater then 16384. 8192 is ok, 16384 should be ok. Anything bigger will hit this bug. :Yes. PR 20609, assigned to you for some time. : :> The buffer map is a system map, right? Which means it allocates :> map_entry elements out of kmapentzone, which is a ZONE_INTERRUPT zone, :> which can't block. : :No. It is not a system map. It should be a system map. : :> There is a vm_object_allocate() call, which uses a non-interrupt zone, :> but I don't think it applies to buffer-cache buffers. Buffer cache :> buffer KVM is not backed by arbitrary VM objects. : :_vm_map_clip_end() and _vm_map_clip_start() calls vm_object_allocate() :if the entry being split has no object. So it certainly applies to :the buffer cache buffers due to vm objects incorrectly being allocated :for buffer map entries. : :- Tor Egge Yes, well, there are two dozen PR's assigned to me... sometimes I loose track :-) Grr. You know what Tor, your mail from middle of last year is *still* in my inbox! Ok, I'll look into it and not forget this time. The patch you include in the PR seems reasonable after a quick look. The VFS/BIO subsystem never calls vm_map_simplify_entry() or vm_map_lookup(), which means that as long as the filesystem block size does not exceed the buffer cache KVM granularity the clipping routines will never be called. The buffer cache KVM granularity is 16384 bytes. So as long as one does not use a block size greater then 16384 bytes it should be reasonably safe (we still have to fix this, of course, I'm trying to diagnose the likelyhood of a problem for people using standard block sizes). A block size of exactly 16384 bytes should work fine. It looks like with the above stricture, the only exposed hole is the vm_map_entry allocation routine. If we block there it is possible for a second entry in the VFS/BIO subsystem to allocate the same KVM address range and create a second buffer sharing the same backing memory. (Side note: If bitmap blocks exceed 16384K, this could cause serious filesystem corruption. I'm not sure whether this is possible or not but it's something to think about. It could be related to why filesystems with extreme newfs parameters seems to have more then their fair share of problems). I will say that of course we have to fix this bug, but in the current released systems there is virtually no chance of zalloc() blocking due to the low memory deadlock fixes I put in after christmas. So as long as people are not using a filesystem block size larger then 16384 bytes I think their systems will be fine. This is a great example of how fragile code can wind up in a relatively stable system with no alarm bells ringing. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 18:43:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from axis.tdd.lt (axis.tdd.lt [193.219.211.5]) by hub.freebsd.org (Postfix) with ESMTP id 38DE237B402 for ; Tue, 9 Jan 2001 18:43:15 -0800 (PST) Received: from localhost (midom@localhost) by axis.tdd.lt (8.11.1/8.11.1) with ESMTP id f0A2h3B47496; Wed, 10 Jan 2001 04:43:04 +0200 (EET) Date: Wed, 10 Jan 2001 04:43:03 +0200 (EET) From: Domas Mituzas X-Sender: midom@axis.tdd.lt To: Kal Torak Cc: FreeBSD-stable Subject: Re: gif & faith needed? In-Reply-To: <3A5BC6C5.96B87778@quake.com.au> 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, 10 Jan 2001, Kal Torak wrote: > Hiyas, > > I am just wondering if gif and faith pseudo devices are needed for > anything? (Besides IPv6 stuff) > And what they are for... > You've mentioned the reason for those devices. If you're more deep into IPv6, you'll find they're used for tunneling. And if you wish to use just ipv4 for one month more, you dont need this. Domas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 19: 3:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id D81E837B401 for ; Tue, 9 Jan 2001 19:02:58 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0A32vl17077 for stable@freebsd.org; Tue, 9 Jan 2001 22:02:57 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0A32qd17069 for ; Tue, 9 Jan 2001 22:02:53 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010109220057.052067c0@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 09 Jan 2001 22:02:51 -0500 To: stable@freebsd.org From: Mike Tancsa Subject: cvsup12 out of sync ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is cvsup12 really out of sync? I installed a snap from today, did a cvsup to get a few extra commits from this afternoon and Checkout src/sys/conf/files Checkout src/sys/conf/newvers.sh Delete src/sys/dev/aac/aac.c Delete src/sys/dev/aac/aac_compat.h Delete src/sys/dev/aac/aac_debug.c Delete src/sys/dev/aac/aac_disk.c Delete src/sys/dev/aac/aac_ioctl.h Delete src/sys/dev/aac/aac_pci.c Delete src/sys/dev/aac/aac_tables.h Delete src/sys/dev/aac/aacreg.h Delete src/sys/dev/aac/aacvar.h Checkout src/sys/dev/aic7xxx/aic7xxx.c Checkout src/sys/dev/aic7xxx/aic7xxx_freebsd.c Checkout src/sys/dev/aic7xxx/aic7xxx_inline.h Checkout src/sys/i386/conf/LINT Delete src/sys/modules/aac/Makefile Checkout src/sys/netgraph/ng_base.c Checkout src/sys/netgraph/ng_message.h Checkout src/sys/netgraph/ng_rfc1490.c Checkout src/sys/sys/syslog.h SetAttrs src/usr.bin/lex/mkskel.sh,v Checkout src/usr.sbin/ngctl/Makefile Delete src/usr.sbin/ngctl/config.c Checkout src/usr.sbin/ngctl/main.c Checkout src/usr.sbin/ngctl/ngctl.8 Checkout src/usr.sbin/ngctl/ngctl.h SetAttrs src/usr.sbin/pkg_install/tkpkg,v Checkout src/usr.sbin/syslogd/syslogd.c Shutting down connection to server Finished successfully compared to cvsup11 Edit src/sys/conf/files Add delta 1.340.2.43 2001.01.09.01.01.46 scottl Checkout src/sys/dev/aac/aac.c Checkout src/sys/dev/aac/aac_compat.h Checkout src/sys/dev/aac/aac_debug.c Checkout src/sys/dev/aac/aac_disk.c Checkout src/sys/dev/aac/aac_ioctl.h Checkout src/sys/dev/aac/aac_pci.c Checkout src/sys/dev/aac/aac_tables.h Checkout src/sys/dev/aac/aacreg.h Checkout src/sys/dev/aac/aacvar.h Edit src/sys/dev/aic7xxx/aic7xxx.c Add delta 1.41.2.13 2001.01.09.00.46.53 gibbs Edit src/sys/dev/aic7xxx/aic7xxx_freebsd.c Add delta 1.3.2.13 2001.01.09.00.46.55 gibbs Edit src/sys/dev/aic7xxx/aic7xxx_inline.h Add delta 1.2.2.6 2001.01.09.00.46.55 gibbs Edit src/sys/i386/conf/LINT Add delta 1.749.2.41 2001.01.09.01.03.31 scottl Checkout src/sys/modules/aac/Makefile Edit src/sys/netgraph/ng_base.c Add delta 1.11.2.8 2001.01.09.06.52.20 phk Edit src/sys/netgraph/ng_message.h Add delta 1.4.2.4 2001.01.09.06.52.20 phk Edit src/sys/netgraph/ng_rfc1490.c Add delta 1.6.2.3 2001.01.09.00.52.45 julian Edit src/sys/netinet/ip_fw.h Add delta 1.47.2.4 2001.01.09.18.11.40 rwatson Edit src/sys/netinet/tcp.h Add delta 1.13.2.1 2001.01.09.18.20.22 rwatson Add delta 1.13.2.2 2001.01.09.18.25.18 rwatson Edit src/sys/sys/syslog.h Add delta 1.19.2.1 2001.01.09.06.51.34 phk Edit src/sys/ufs/ufs/ufs_disksubr.c Add delta 1.44.2.1 2001.01.09.12.26.17 phk Edit src/usr.sbin/ngctl/Makefile Add delta 1.4.2.1 2001.01.09.06.52.25 phk Checkout src/usr.sbin/ngctl/config.c Edit src/usr.sbin/ngctl/main.c Add delta 1.4.2.3 2001.01.09.06.52.25 phk Edit src/usr.sbin/ngctl/ngctl.8 Add delta 1.5.2.3 2001.01.09.06.52.25 phk Edit src/usr.sbin/ngctl/ngctl.h Add delta 1.6.2.2 2001.01.09.06.52.25 phk Edit src/usr.sbin/syslogd/syslogd.c Add delta 1.59.2.4 2001.01.09.06.51.37 phk Shutting down connection to server Finished successfully -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 19:18:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id DF96437B401 for ; Tue, 9 Jan 2001 19:17:59 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.20 #1) id 14GBL7-000Muq-00; Wed, 10 Jan 2001 02:50:17 +0000 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.1/8.11.1) id f0A2oGw91065; Wed, 10 Jan 2001 02:50:16 GMT (envelope-from ben) Date: Wed, 10 Jan 2001 02:50:14 +0000 From: Ben Smithurst To: Erich Zigler Cc: stable@freebsd.org Subject: Re: Weird files in root Message-ID: <20010110025014.L79365@strontium.scientia.demon.co.uk> References: <20010109194108.A92622@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010109194108.A92622@superhero.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erich Zigler wrote: > For some resaon this keeps appearing in / > > 0 lrwxr-xr-x 1 root wheel 10 Jan 9 14:49 ttyv0 -> /dev/ttyv0 > > Anyone know why? Probably /etc/rc.devfs combined with a /dev/vga symlink pointing at nothing. Not sure how that broken symlink got there, but it was there on three of my machines.. :-/ -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 19:23:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id EF56837B400 for ; Tue, 9 Jan 2001 19:23:06 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0A3N1R33130; Tue, 9 Jan 2001 21:23:01 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101100323.f0A3N1R33130@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Bert Driehuis Cc: stable@FreeBSD.ORG From: David Kelly Subject: Re: Intel PRO/100+ driver or hardware? (Update) In-reply-to: Message from Bert Driehuis of "Tue, 09 Jan 2001 20:43:20 +0100." <3A5B69D8.C46CE2D1@nl.compuware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jan 2001 21:23:01 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bert Driehuis writes: > "Jeroen C. van Gelderen" wrote: > > > My conclusion is that the Intel cards I have are broken. They refuse to > > work reliably in an otherwise healthy low-end network. I may have a bad > > batch or maybe these cards are broken by design. > > It is possible your motherboard vendor screwed up: > > http://developer.intel.com/design/support/faq/82559.htm > > Apparently, some motherboard vendors let boards go out with wrong wiring > or capacitors (see the bottom of the page), and the symptoms match yours > (which, I must stress, may very well be a coincidence). If I'm following correctly Jeroen's problem is with genuine Intel Etherexpress Pro boards with the '59 chip. Not with an integrated chipset as discussed in the above URL. Intel offers an interesting diagnostic suggestions: if it doesn't work with a short wire, try a long wire. Suspect Jeroen's most timely solution is to permanently replace his cards with something else. Altho he makes mention of a PCI riser card which may alter the electrical reference the Intel card has to work against. Am also thinking the computer power supply, or clock frequency can be part of the problem. Or part of the solution. Wonder if underclocking the system would make any differnce? Have seen unreliable computers fixed by replacing the PS. And this was before CPU's started running off of anything other than plain old 5V. As for non-Intel ethernet cards, 3 or 4 years ago when I first got to play with fast ethernet, found by accident that a 3Com card connected to a 3Com switch was more forgiving of wrongly pairing the cat5 wires than anything else connected to the same switch and wire. IMHO am surprised this sort of thing doesn't happen more often. -- David Kelly N4HHE, dkelly@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 Jan 9 19:32:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 0958137B400 for ; Tue, 9 Jan 2001 19:32:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0A3WXR52560; Tue, 9 Jan 2001 21:32:33 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101100332.f0A3WXR52560@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Jeroen C. van Gelderen" Cc: stable@FreeBSD.ORG From: David Kelly Subject: Re: Intel PRO/100+ driver or hardware? (Update) In-reply-to: Message from "Jeroen C. van Gelderen" of "Tue, 09 Jan 2001 15:47:15 -0400." <179010000.979069635@grolsch.ai> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jan 2001 21:32:33 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeroen C. van Gelderen" writes: > I tried 2 hubs, one claims to be a cheap 8816TPC, the other NetGear DS108. > Both give problems. Replacing the Intel card with a 3Com or SMC solves the > problem. Of course I've tried multiple cables as well. > > Maybe this is relevant. The DS108 actually is a dual speed hub. IIRC it has > a 10 Mbit bus and a 100 Mbit bus, connected with a little switch. The > machine I'm testing against has a 10Mbit card. I tried forcing to Intel to > 10Mbit and tried to transfer the file. It stalls after a couple of > megabytes. In the same place every time, I hope? > I then forced the Intel card to 100Mbit mode and tried the > transfer again (so it would have to go trough the switching device in the > hub); That got me a little further (22 MB) but this transfer too stalled > eventually. Same question, "Fails in the same place each time you try?" > > Any chance you can capture and/or share the problem data? > > More than willing to, but I'm not sure how to do it most effectively. You > just want the tcpdump data? Do I need to give any special arguments to > tcpdump? If its file transfer the easiest thing to do would be to transfer the exact same file. But 22 MB into it, sounds like a system backup. Ideally if you had a small file which failed with ftp, it would be easy for others to attempt to duplicate your failure. Am far from a tcpdump guru but it would be rough dumping headers and packets until problems start 22MB of data later. Especially if done on the same machine as the problem is happening because the tcpdump processing may be all it takes to clear up the problem. Or make it worse. Ideally one would only want to dump packets which fail checksum. So maybe wait to start tcpdump until the transfer stops. It may be time to "cut bait" and simply accept the Intel cards didn't work in your situation and go on with things. Know I'm using an Intel card right now (with an AMD CPU :-) ) but forgot to look and see what chip was on it. My other 3 Intel cards are 58's, in other machines. -- David Kelly N4HHE, dkelly@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 Jan 9 19:34: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.ip.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id C58F837B400 for ; Tue, 9 Jan 2001 19:33:47 -0800 (PST) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.11.1/8.11.1) with ESMTP id f0A3Xam78383; Tue, 9 Jan 2001 19:33:36 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) To: David Kelly Cc: Bert Driehuis , stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? (Update) In-Reply-To: Message from David Kelly of "Tue, 09 Jan 2001 21:23:01 CST." <200101100323.f0A3N1R33130@grumpy.dyndns.org> Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Tue, 09 Jan 2001 19:33:36 -0800 Message-ID: <78379.979097616@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 09 Jan 2001 21:23:01 CST, David Kelly wrote: > >Suspect Jeroen's most timely solution is to permanently replace his >cards with something else. Altho he makes mention of a PCI riser card >which may alter the electrical reference the Intel card has to work >against. I've had lots of trouble with an "L"-style riser card (for 1U cases) and several different enet and a few other cards. Got rid of the riser and things work fine. I haven't tried an Intel EEPRO in the riser though. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 22: 7:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id CE61B37B402 for ; Tue, 9 Jan 2001 22:07:13 -0800 (PST) Received: (qmail 86622 invoked from network); 10 Jan 2001 06:07:12 -0000 Received: from unknown (HELO prydn.tacni.net) (204.155.159.50) by 216.178.136.168 with SMTP; 10 Jan 2001 06:07:12 -0000 Received: (qmail 90998 invoked by uid 1001); 10 Jan 2001 06:07:08 -0000 Date: Wed, 10 Jan 2001 00:07:08 -0600 From: Erich Zigler To: Ben Smithurst Cc: stable@freebsd.org Subject: Re: Weird files in root Message-ID: <20010110000708.A90963@superhero.org> References: <20010109194108.A92622@superhero.org> <20010110025014.L79365@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010110025014.L79365@strontium.scientia.demon.co.uk>; from ben@FreeBSD.org on Wed, Jan 10, 2001 at 02:50:14AM +0000 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 02:50:14AM +0000, Ben Smithurst wrote: > > For some resaon this keeps appearing in / > > 0 lrwxr-xr-x 1 root wheel 10 Jan 9 14:49 ttyv0 -> /dev/ttyv0 > > Anyone know why? > Probably /etc/rc.devfs combined with a /dev/vga symlink pointing at > nothing. Not sure how that broken symlink got there, but it was there > on three of my machines.. :-/ What should /dev/vga point too? -- Erich Zigler Artificial Intelligence: the art of making computers that behave like the ones in movies. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 9 22:11:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id CA06637B400; Tue, 9 Jan 2001 22:11:00 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id inosaaaa for ; Wed, 10 Jan 2001 17:19:02 +1100 Message-ID: <3A5BFD13.EBDEA9BD@quake.com.au> Date: Wed, 10 Jan 2001 17:11:31 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Erich Zigler Cc: Ben Smithurst , stable@freebsd.org Subject: Re: Weird files in root References: <20010109194108.A92622@superhero.org> <20010110025014.L79365@strontium.scientia.demon.co.uk> <20010110000708.A90963@superhero.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erich Zigler wrote: > > On Wed, Jan 10, 2001 at 02:50:14AM +0000, Ben Smithurst wrote: > > > > For some resaon this keeps appearing in / > > > 0 lrwxr-xr-x 1 root wheel 10 Jan 9 14:49 ttyv0 -> /dev/ttyv0 > > > Anyone know why? > > Probably /etc/rc.devfs combined with a /dev/vga symlink pointing at > > nothing. Not sure how that broken symlink got there, but it was there > > on three of my machines.. :-/ > > What should /dev/vga point too? It should point to /dev/ttyv0 unless you use a diffrent terminal device... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 0:47:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aifhs8.alcatel.fr (aifhs8.alcatel.fr [212.208.74.153]) by hub.freebsd.org (Postfix) with ESMTP id 31B7E37B400 for ; Wed, 10 Jan 2001 00:47:00 -0800 (PST) Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs8.alcatel.fr (ALCANET/SMTP2) with SMTP id JAA22399; Wed, 10 Jan 2001 09:46:19 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id C12569D0.00302B7F ; Wed, 10 Jan 2001 09:46:08 +0100 X-Lotus-FromDomain: ALCATEL From: Thierry.Herbelot@alcatel.fr To: Parag Patel Cc: stable@FreeBSD.ORG Message-ID: Date: Wed, 10 Jan 2001 09:46:00 +0100 Subject: Re: Intel PRO/100+ driver or hardware? (Update) Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Does someone have a reference for "known good" riser cards ? (I'm using rack-mount PCs with an extension board, so I can't get rid of the riser - anyway, I'm using a 4-port D-LINK board which does not seem to suffer from interference) TfH Parag Patel on 10/01/2001 04:33:36 To: David Kelly cc: Bert Driehuis , stable@FreeBSD.ORG(bcc: Thierry HERBELOT/FR/ALCATEL) Subject: Re: Intel PRO/100+ driver or hardware? (Update) On Tue, 09 Jan 2001 21:23:01 CST, David Kelly wrote: > >Suspect Jeroen's most timely solution is to permanently replace his >cards with something else. Altho he makes mention of a PCI riser card >which may alter the electrical reference the Intel card has to work >against. I've had lots of trouble with an "L"-style riser card (for 1U cases) and several different enet and a few other cards. Got rid of the riser and things work fine. I haven't tried an Intel EEPRO in the riser though. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 2: 3:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gryphon.itssa.curtin.edu.au (gryphon.itssa.curtin.edu.au [134.7.72.31]) by hub.freebsd.org (Postfix) with ESMTP id 7854137B401 for ; Wed, 10 Jan 2001 02:03:32 -0800 (PST) Received: (from www@localhost) by gryphon.itssa.curtin.edu.au (8.9.3/8.9.3) id SAA06757; Wed, 10 Jan 2001 18:03:18 +0800 (WST) (envelope-from satherrl@gryphon.itssa.curtin.edu.au) Date: Wed, 10 Jan 2001 18:03:18 +0800 (WST) From: Richard Sather Message-Id: <200101101003.SAA06757@gryphon.itssa.curtin.edu.au> X-Authentication-Warning: gryphon.itssa.curtin.edu.au: www set sender to satherrl@itssa.curtin.edu.au using -f To: freebsd-stable@freebsd.org Reply-To: satherrl@gryphon.itssa.curtin.edu.au References: <6D5097D4B56AD31190D50008C7B1579BC97DD7@exlan5.rjf.com> In-Reply-To: <6D5097D4B56AD31190D50008C7B1579BC97DD7@exlan5.rjf.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 Subject: RE: Intel PRO/100+ driver or hardware? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Ian Cartwright : > A few weeks back I mentioned a similar problem I was having with a Compaq > Dexkpro EN. It has a built in 82559 chip. Under FreeBSD it would hang every > so often with a device timeout. Under Win2k it works great. I tried > everything I could think of (swapping cables, hubs, etc.) with no success > for FreeBSD. I tried the mailing lists but no one saw my post I guess. ;-/ ok - I have 12 CompaQ EN's sitting next to me aswell. Exactly the same timeout problem. 3.5.1-RELEASE also refuses to acknowledge their existence. We have tried a netgear 10Base hub at autonegotiate and fixed at 10Mbps aswell as through a Netgear FS 116 16 port switch with the same effect. We tried locking the card at 100Mbps which 'seemed' to cure the problem but our solution for the time being has been to use Pro 100/10B's. Regards Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 2:26:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id 8950D37B401 for ; Wed, 10 Jan 2001 02:26:23 -0800 (PST) Received: from laa@localhost by burka.carrier.kiev.ua id MJQ50293; Wed, 10 Jan 2001 12:25:05 +0200 (EET) (envelope-from laa@zgia.zp.ua) X-Authentication-Warning: burka.carrier.kiev.ua: laa set sender to laa@zgia.zp.ua using -f Date: Wed, 10 Jan 2001 12:25:04 +0200 From: "Alexandr A. Listopad" To: bind-users@isc.org, freebsd-stable@freebsd.org Subject: bind crashes Message-ID: <20010110122504.A48198@burka.carrier.kiev.ua> Reply-To: laa@zgia.zp.ua Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi! I have repeated bind crashes. I have FreeBSD-4.2-STABLE with named (8.2.3-T6B Mon Dec 25 12:11:51 EET 2000) and only this in logs: Jan 9 23:32:11 my-host named[1277]: /usr/src/lib/libbind/../../contrib/bind/lib/isc/ev_timers.c:114: INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000) failed. Jan 9 23:32:11 my-host named[1277]: /usr/src/lib/libbind/../../contrib/bind/lib/isc/ev_timers.c:114: INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000) failed. how can I fix this? -- Laa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 2:42:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fractal.fractalconcept.com (unknown [213.11.22.162]) by hub.freebsd.org (Postfix) with ESMTP id 8C56C37B404 for ; Wed, 10 Jan 2001 02:42:28 -0800 (PST) Received: from marcnt (test.fractalconcept.com [213.11.22.164]) by fractal.fractalconcept.com (8.11.0/8.11.0) with SMTP id f0AAgLe60931 for ; Wed, 10 Jan 2001 11:42:24 +0100 (CET) (envelope-from marc.battyani@fractalconcept.com) Message-ID: <004701c07af2$0d6c0070$a4160bd5@marcnt> Reply-To: "Marc Battyani" From: "Marc Battyani" To: Subject: suscribe Date: Wed, 10 Jan 2001 11:42:35 +0100 Organization: Fractal Concept MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0044_01C07AFA.6D02B300" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0044_01C07AFA.6D02B300 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable suscribe ------=_NextPart_000_0044_01C07AFA.6D02B300 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

suscribe

------=_NextPart_000_0044_01C07AFA.6D02B300-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 2:47:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 07A3C37B402 for ; Wed, 10 Jan 2001 02:47:13 -0800 (PST) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.1/8.11.1) with ESMTP id f0AAkI835513; Wed, 10 Jan 2001 21:46:20 +1100 (EST) (envelope-from marka@nominum.com) Message-Id: <200101101046.f0AAkI835513@drugs.dv.isc.org> To: laa@zgia.zp.ua Cc: bind-users@isc.org, freebsd-stable@freebsd.org From: Mark.Andrews@nominum.com Subject: Re: bind crashes In-reply-to: Your message of "Wed, 10 Jan 2001 12:25:04 +0200." <20010110122504.A48198@burka.carrier.kiev.ua> Date: Wed, 10 Jan 2001 21:46:18 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "sysctl -w kern.timecounter.method=1" helps most bsd boxes. Mark > hi! > > I have repeated bind crashes. I have FreeBSD-4.2-STABLE with named > (8.2.3-T6B Mon Dec 25 12:11:51 EET 2000) > > and only this in logs: > > Jan 9 23:32:11 my-host named[1277]: /usr/src/lib/libbind/../../contrib/bind/ > lib/isc/ev_timers.c:114: INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000) fa > iled. > Jan 9 23:32:11 my-host named[1277]: /usr/src/lib/libbind/../../contrib/bind/ > lib/isc/ev_timers.c:114: INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000) fa > iled. > > how can I fix this? > > -- > Laa > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 3:22:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.camelot.de (mailout.camelot.de [195.30.224.18]) by hub.freebsd.org (Postfix) with ESMTP id 8DA8937B401 for ; Wed, 10 Jan 2001 03:21:53 -0800 (PST) Received: from robin.camelot.de (knarf@mail.camelot.de [195.30.224.10]) by mail.camelot.de (8.11.1/8.11.1) with ESMTP id f0ABLps97938 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Wed, 10 Jan 2001 12:21:51 +0100 (CET) Received: (from knarf@localhost) by robin.camelot.de (8.11.1/8.11.1) id f0ABLoZ97935 for freebsd-stable@FreeBSD.ORG; Wed, 10 Jan 2001 12:21:50 +0100 (CET) Date: Wed, 10 Jan 2001 12:21:50 +0100 From: Frank Bartels To: freebsd-stable@FreeBSD.ORG Subject: NODESCRYPTLINKS=true Message-ID: <20010110122150.A95886@camelot.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Heya all, we still use DES passwords on our system. If I do a make world (4.2-STABLE), the libcrypt links in /usr/lib are replaced by ones to libscript. I found NODESCRYPTLINKS=3Dtrue in /etc/defaults/make.conf and have put it into /etc/make.conf. But the links still get replaced. The bad thing is, I cannot login after a reboot. I _think_ libscrypt was able to detect des/md5 passwords in 3.x and logins were still possible. Is there a complete documentation about libcrypt, libscrypt, libdescrypt, passwd_format=3Ddes and the upgrading procedure from 3.x to 4.x? Thanks for your help. Bye, Knarf --=20 Frank Bartels | Tel: +49-89-849308-0 | CameloT - Der "sagenhafte" knarf@camelot.de | http://www.camelot.de/ | Internet-Provider --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQEVAwUBOlxFzv1lXGS2C2FpAQFVqAgAke3aQrGyT8kZkouQoU7L5SvVVtGx2f9u w/5k51lbFzvHjcZKeiCkgw+peAx+9t6WtCIJHAQlqHGUgVizkudQM14k6jc+JShk w2GIiojngdt+JV9NNGzbOrbwralgPVyqY980iRl+oPKdynMfezI3l+rkUwHK2l+C j3GJsos5AmUdpjxbfJ1Ogkd8v4E6wvvu+Jv0feRfYtZo29dpmaGW5Jp3udEBZIbS Q3b0g5auLrxzVjeXOy96ewbAEiNrA/hwf3Ms47v6+/iXc7WPGZcZ1DDXxGbS+IDU iJLvyvlFbwJCBuuCwUj1zzTzPoRj15Z9/fuPM439eNPjE+tfdkt6LA== =qXLB -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 3:55:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id B2C3037B69B for ; Wed, 10 Jan 2001 03:55:03 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id zposaaaa for ; Wed, 10 Jan 2001 23:03:05 +1100 Message-ID: <3A5C4DB9.1C9F0949@quake.com.au> Date: Wed, 10 Jan 2001 22:55:37 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Frank Bartels Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NODESCRYPTLINKS=true References: <20010110122150.A95886@camelot.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Bartels wrote: > > Heya all, > > we still use DES passwords on our system. If I do a make world > (4.2-STABLE), the libcrypt links in /usr/lib are replaced by ones > to libscript. I found NODESCRYPTLINKS=true in /etc/defaults/make.conf > and have put it into /etc/make.conf. But the links still get > replaced. > > The bad thing is, I cannot login after a reboot. I _think_ libscrypt > was able to detect des/md5 passwords in 3.x and logins were still > possible. > > Is there a complete documentation about libcrypt, libscrypt, > libdescrypt, passwd_format=des and the upgrading procedure from > 3.x to 4.x? Hmmm, did you cvsup and install the crypto dists? They used to be export restricted until recently so if you have an old sup file it probably dosent get them... If the crypto dist is installed the default password scheme used is DES, but the system should be able to understand both DES and MD5 passwords... /usr/src/UPDATING is a good place to find out about the procedure... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 4:50: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.camelot.de (mailout.camelot.de [195.30.224.18]) by hub.freebsd.org (Postfix) with ESMTP id BF1C637B401 for ; Wed, 10 Jan 2001 04:49:43 -0800 (PST) Received: from robin.camelot.de (knarf@mail.camelot.de [195.30.224.10]) by mail.camelot.de (8.11.1/8.11.1) with ESMTP id f0ACnLs14190 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Wed, 10 Jan 2001 13:49:42 +0100 (CET) Received: (from knarf@localhost) by robin.camelot.de (8.11.1/8.11.1) id f0ACnKL14187; Wed, 10 Jan 2001 13:49:20 +0100 (CET) Date: Wed, 10 Jan 2001 13:49:20 +0100 From: Frank Bartels To: Kal Torak Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NODESCRYPTLINKS=true Message-ID: <20010110134920.N34155@camelot.de> References: <20010110122150.A95886@camelot.de> <3A5C4DB9.1C9F0949@quake.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="SuSGaIqs99hP22V3" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5C4DB9.1C9F0949@quake.com.au>; from kaltorak@quake.com.au on Wed, Jan 10, 2001 at 10:55:37PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --SuSGaIqs99hP22V3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Heya Kal, On Wed, Jan 10, 2001 at 10:55:37PM +1100, Kal Torak wrote: > Frank Bartels wrote: > > we still use DES passwords on our system. If I do a make world > > (4.2-STABLE), the libcrypt links in /usr/lib are replaced by ones > > to libscript. I found NODESCRYPTLINKS=3Dtrue in /etc/defaults/make.conf > > and have put it into /etc/make.conf. But the links still get > > replaced. > >=20 > > The bad thing is, I cannot login after a reboot. I _think_ libscrypt > > was able to detect des/md5 passwords in 3.x and logins were still > > possible. > >=20 > > Is there a complete documentation about libcrypt, libscrypt, > > libdescrypt, passwd_format=3Ddes and the upgrading procedure from > > 3.x to 4.x? >=20 > Hmmm, did you cvsup and install the crypto dists? They used to be > export restricted until recently so if you have an old sup file > it probably dosent get them... I've installed 4.2-RELEASE (bin+crypto), took the stable-supfile from /usr/share/examples/cvsup and changed the host and compress lines, cvsupped (from my own cvsup-mirror) and ran make world. As I understand, there is no longer a separated crypto tree. My own cvsup-mirror seems to be okay, as running cvsup -h cvsup.de.freebsd.org does not make changes to my local source tree. > If the crypto dist is installed the default password scheme used > is DES, but the system should be able to understand both DES and > MD5 passwords... I know it should, but it does not. > /usr/src/UPDATING is a good place to find out about the procedure... The information is not really helpful for my problem (I check UPDATING often). So there are still two questions: - why are the links replaced? - why does my libscrypt not understand DES passwords? My make.conf says: NODESCRYPTLINKS=3Dtrue # do not replace libcrypt -> libscrypt links NOPROFILE=3D true # Avoid compiling profiled libraries MAKE_IDEA=3D YES # IDEA (128 bit symmetric encryption) USA_RESIDENT=3D NO Bye, Knarf --=20 Frank Bartels | Tel: +49-89-849308-0 | CameloT - Der "sagenhafte" knarf@camelot.de | http://www.camelot.de/ | Internet-Provider --SuSGaIqs99hP22V3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQEVAwUBOlxaUP1lXGS2C2FpAQEkzQf/YqxzaHEcQJ3ZF+7C+IiJRIscqxb6MvH5 hGZn6VGebq/gK/J29/txnY4mXhOfowJImwYlSm0DHKk5S7/obB7ckogUYGjiHl/N GFcNRhTOC9BzsvPIozkxIGPsgYsuOkAvHEj5V3TANd1blnLLVZ1K5P7SEJ65vns2 fGfbkrEW5lbqGXnyrNDSDu8YuJlbWcKyHpDxiL5gh6R26Xxo/MuRL8JZtWsGEvZH 1m2LdZZoc8sgHH9lDV6OsEPK4+Gpa9RoMo95w5Gj9wI+WMxLUdG5yzyyCFp5okF3 xzxR5p67J28qqaR4H+y8yg03jg+6blGruUH50h38Y6QK406IX8Y+eA== =yVGf -----END PGP SIGNATURE----- --SuSGaIqs99hP22V3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 5: 2:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hq1.tyfon.net (hq1.tyfon.net [217.27.162.35]) by hub.freebsd.org (Postfix) with ESMTP id A256637B400 for ; Wed, 10 Jan 2001 05:01:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id DAA121C7DA for ; Wed, 10 Jan 2001 14:01:48 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id DE7891C5C9 for ; Wed, 10 Jan 2001 14:01:45 +0100 (CET) Date: Wed, 10 Jan 2001 14:01:45 +0100 (CET) From: Dan Larsson To: FreeBSD Stable List Subject: Cleaning out old/unused files after make world Message-ID: Organization: Tyfon Svenska AB X-NCC-NIC: DL1999-RIPE X-NCC-RegID: se.tyfon MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by hq1.tyfon.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The machine i question has stepwise been updated from 3.2R to 4.2S, and I'm guessing some files are nolonger needed by the system. How can I find out which files can be removed? Regards +------ Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 GPG and PGP keys | finger dl@hq1.tyfon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 5:10:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 519C837B401 for ; Wed, 10 Jan 2001 05:10:28 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id AFA9E323F; Wed, 10 Jan 2001 13:10:32 +0000 (GMT) Date: Wed, 10 Jan 2001 13:10:32 +0000 From: Josef Karthauser To: Domas Mituzas Cc: Kal Torak , FreeBSD-stable Subject: Re: gif & faith needed? Message-ID: <20010110131032.D735@tao.org.uk> Mail-Followup-To: Josef Karthauser , Domas Mituzas , Kal Torak , FreeBSD-stable References: <3A5BC6C5.96B87778@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from domas.mituzas@delfi.lt on Wed, Jan 10, 2001 at 04:43:03AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 04:43:03AM +0200, Domas Mituzas wrote: > > > On Wed, 10 Jan 2001, Kal Torak wrote: > > > Hiyas, > > > > I am just wondering if gif and faith pseudo devices are needed for > > anything? (Besides IPv6 stuff) > > And what they are for... > > > > You've mentioned the reason for those devices. If you're more deep into > IPv6, you'll find they're used for tunneling. And if you wish to use just > ipv4 for one month more, you dont need this. Gif at least is usable for creating IPv4overIPv4 tunnels (using IPenc encapsulation protocol). Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 5:21: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pluton.ispras.ru (pluton.ispras.ru [194.186.94.6]) by hub.freebsd.org (Postfix) with ESMTP id C727537B6A1 for ; Wed, 10 Jan 2001 05:20:39 -0800 (PST) Received: from gate.ispras.ru (gate [194.67.37.200]) by pluton.ispras.ru (8.11.1/8.11.1) with ESMTP id f0A3Sjv22219 for ; Wed, 10 Jan 2001 06:28:45 +0300 (MSK) Received: from ispgate (ispgate [194.67.37.200]) by gate.ispras.ru (8.11.1/8.11.0.Beta1) with ESMTP id f0ADK9822246 for ; Wed, 10 Jan 2001 16:20:09 +0300 (MSK) Date: Wed, 10 Jan 2001 16:20:08 +0300 (MSK) From: Grigory Kljuchnikov To: stable@FreeBSD.ORG Subject: Cannot start Xserver 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 Hello, I installed 4.2-RELEASE with XFree86, but after this I cannot start Xserver, I have got => error message: Fatal server error: xf86OpenConsole: KDENABIO failed (Operation not permitted) But I did setup X with XF86Setup into installation process and X worked properly. Now XF86Setup don't start and say: "I cannot start X..." What is wrong? I have not any idea. Thank you... Grigory Klyuchnikov, System Engineer, Institute for System Programming Russian Academy of Sciences To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 5:31:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id C718E37B699 for ; Wed, 10 Jan 2001 05:30:50 -0800 (PST) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id OAA60885; Wed, 10 Jan 2001 14:30:36 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Wed, 10 Jan 2001 14:30:36 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= To: Grigory Kljuchnikov Cc: Subject: Re: Cannot start Xserver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Jan 2001, Grigory Kljuchnikov wrote: > Fatal server error: > xf86OpenConsole: KDENABIO failed (Operation not permitted) You are probably running with securelevel greater than 0. Switch to single user mode with 'shutdown now' and edit /etc/rc.conf to set securelevel to 0 or -1. Return to multi user mode with exit. -- ---------------------------------------------------------------------- Trond Endrestшl | trond@ramstind.gtf.ol.no Patron of The Art of Computer Programming| FreeBSD 3.5-S & Pine 4.31 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 5:44:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 063F637B698 for ; Wed, 10 Jan 2001 05:44:25 -0800 (PST) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.112.212]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/5) with ESMTP id f0ADi9m12681; Wed, 10 Jan 2001 14:44:09 +0100 (MET) Received: from agamemnon.informatik.rwth-aachen.de (agamemnon.Informatik.RWTH-Aachen.DE [137.226.194.74]) by hyperion.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1/2) with ESMTP id OAA07766; Wed, 10 Jan 2001 14:43:15 +0100 (MET) Received: (from stolz@localhost) by agamemnon.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id OAA23741; Wed, 10 Jan 2001 14:44:04 +0100 (MET) Date: Wed, 10 Jan 2001 14:44:04 +0100 From: Volker Stolz To: grn@ispras.ru, stable@FreeBSD.ORG Subject: Re: Cannot start Xserver Message-ID: <20010110144404.A23628@agamemnon.informatik.rwth-aachen.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: Organization: Chair for CS II 1/2, Anomalous Programming Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In local.freebsd-stable, you wrote: >I installed 4.2-RELEASE with XFree86, >but after this I cannot start Xserver, >Fatal server error: >xf86OpenConsole: KDENABIO failed (Operation not permitted) http://www.FreeBSD.org/cgi/search.cgi?words=KDENABIO&max=25&sort=score\ &index=recent&source=freebsd-questions "> Check your kernal secure level. If it's greater than zero, X can't start. If you are in FreeBSD 4.1.1 just set the kern.securelevel variable in the /etc/rc.conf file to 0." The xwrapper-port might help, too (not sure, though). -- \usepackage[latin1]{inputenc}! Volker Stolz * stolz@i2.informatik.rwth-aachen.de * PGP + S/MIME To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 6:11:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from prioris.mini.pw.edu.pl (prioris.mini.pw.edu.pl [148.81.80.7]) by hub.freebsd.org (Postfix) with ESMTP id 6C23F37B69D for ; Wed, 10 Jan 2001 06:11:29 -0800 (PST) Received: by prioris.mini.pw.edu.pl (Postfix, from userid 1368) id 83BA87D2AD; Wed, 10 Jan 2001 15:11:21 +0100 (CET) Date: Wed, 10 Jan 2001 15:11:20 +0100 From: Grzegorz Czaplinski To: Frank Bartels Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NODESCRYPTLINKS=true Message-ID: <20010110151120.A55352@prioris.mini.pw.edu.pl> References: <20010110122150.A95886@camelot.de> <3A5C4DB9.1C9F0949@quake.com.au> <20010110134920.N34155@camelot.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20010110134920.N34155@camelot.de> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I had the same problem on the server. Have a look at the handbook first, chapter 8 - security, section "DES, MD5, and Crypt". I suppose you have something like: ls -l libcrypt.* lrwxr-xr-x 1 root wheel 11 Jan 9 20:00 libcrypt.a -> libscrypt.a lrwxr-xr-x 1 root wheel 12 Jan 9 20:00 libcrypt.so -> libscrypt.so lrwxr-xr-x 1 root wheel 14 Jan 9 20:00 libcrypt.so.2 -> libscrypt.so.2 The solution is to link it like that: ls -l libcrypt.* lrwxr-xr-x 1 root wheel 13 Jan 9 20:05 libcrypt.a -> libdescrypt.a lrwxr-xr-x 1 root wheel 14 Jan 9 20:06 libcrypt.so -> libdescrypt.so lrwxr-xr-x 1 root wheel 16 Jan 9 20:06 libcrypt.so.2 -> libdescrypt.so.2 Considering make.conf I think you should comment out the line NODESCRYPTLINKS=true # do not replace libcrypt -> libscrypt links but I am not sure about that in 100%. I hope this will help. Best Regards -gregory On Wed, Jan 10, 2001 at 01:49:20PM +0100, Frank Bartels wrote: > Heya Kal, > > On Wed, Jan 10, 2001 at 10:55:37PM +1100, Kal Torak wrote: > > Frank Bartels wrote: > > > > we still use DES passwords on our system. If I do a make world > > > (4.2-STABLE), the libcrypt links in /usr/lib are replaced by ones > > > to libscript. I found NODESCRYPTLINKS=true in /etc/defaults/make.conf > > > and have put it into /etc/make.conf. But the links still get > > > replaced. > > > > > > The bad thing is, I cannot login after a reboot. I _think_ libscrypt > > > was able to detect des/md5 passwords in 3.x and logins were still > > > possible. > > > > > > Is there a complete documentation about libcrypt, libscrypt, > > > libdescrypt, passwd_format=des and the upgrading procedure from > > > 3.x to 4.x? > > > > Hmmm, did you cvsup and install the crypto dists? They used to be > > export restricted until recently so if you have an old sup file > > it probably dosent get them... > > I've installed 4.2-RELEASE (bin+crypto), took the stable-supfile > from /usr/share/examples/cvsup and changed the host and compress > lines, cvsupped (from my own cvsup-mirror) and ran make world. > > As I understand, there is no longer a separated crypto tree. > > My own cvsup-mirror seems to be okay, as running cvsup -h > cvsup.de.freebsd.org does not make changes to my local source tree. > > > If the crypto dist is installed the default password scheme used > > is DES, but the system should be able to understand both DES and > > MD5 passwords... > > I know it should, but it does not. > > > /usr/src/UPDATING is a good place to find out about the procedure... > > The information is not really helpful for my problem (I check > UPDATING often). > > So there are still two questions: > > - why are the links replaced? > - why does my libscrypt not understand DES passwords? > Check handbook first. ;) > My make.conf says: > > NODESCRYPTLINKS=true # do not replace libcrypt -> libscrypt links > NOPROFILE= true # Avoid compiling profiled libraries > MAKE_IDEA= YES # IDEA (128 bit symmetric encryption) > USA_RESIDENT= NO > > Bye, > Knarf > -- > Frank Bartels | Tel: +49-89-849308-0 | CameloT - Der "sagenhafte" > knarf@camelot.de | http://www.camelot.de/ | Internet-Provider -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 6:12:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id A3BC637B402 for ; Wed, 10 Jan 2001 06:12:36 -0800 (PST) Received: from netcom1.netcom.com (user-2inis5b.dialup.mindspring.com [165.121.112.171]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id JAA01682; Wed, 10 Jan 2001 09:12:31 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 519C2E6A2D; Wed, 10 Jan 2001 06:12:27 -0800 (PST) From: Mike Harding To: Robin_Blanchard@gactr.uga.edu Cc: stable@freebsd.org In-reply-to: <3A5B87EE.8ACA0D05@gactr.uga.edu> (Robin_Blanchard@gactr.uga.edu) Subject: Re: buildworld over nfs failing consistently References: <3A5B87EE.8ACA0D05@gactr.uga.edu> Message-Id: <20010110141227.519C2E6A2D@netcom1.netcom.com> Date: Wed, 10 Jan 2001 06:12:27 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if /etc/make.conf is not identical on all machines the make/install can fail... Date: Tue, 09 Jan 2001 16:51:42 -0500 From: "Robin P. Blanchard" X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk ok. i really need some help here. i've got several (identical) dell poweredge servers that i've been trying to update for a few weeks now -- all to no avail. i put together a fresh new install on one this morning, cvsup'ed the source and successfully built and installed world. marvelous. now for the other six machines... the fresh box is the NFS server with /etc/exports like so: /usr -alldirs -maproot=root:staff (this is a private network so i'm not too concerned about who's connecting -- only me) the six other servers have this in their /etc/fstab: castro.servers.nat:/usr/src /usr/src nfs rw 0 0 castro.servers.nat:/usr/obj /usr/obj nfs rw 0 0 an installworld on *any* of these machines goes along just fine until getting to: ===> gnu/usr.bin/perl/library/B cd /usr/obj/usr/src/gnu/usr.bin/perl/library/B/ext/B ; make -B install INSTALLP RIVLIB=/usr/libdata/perl/5.00503 INSTALLARCHLIB=/usr/libdata/perl/5.00503/mach where it plods along a bit more until: [...snip...] vm/vnode_pager.h -> vm/vnode_pager.ph *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 6:18:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id BD7A837B401 for ; Wed, 10 Jan 2001 06:18:02 -0800 (PST) Received: (qmail 17364 invoked by uid 0); 10 Jan 2001 14:17:51 -0000 Received: from p3ee21655.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.85) by mail.gmx.net (mail10) with SMTP; 10 Jan 2001 14:17:51 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id WAA29131 for stable@freebsd.org; Tue, 9 Jan 2001 22:27:50 +0100 Date: Tue, 9 Jan 2001 22:27:50 +0100 From: Gerhard Sittig To: stable@freebsd.org Subject: Re: Intel PRO/100+ driver or hardware? (Update) Message-ID: <20010109222750.J253@speedy.gsinet> Mail-Followup-To: stable@freebsd.org References: <200101081521.f08FLDi31948@prism.flugsvamp.com> <89010000.979063602@grolsch.ai> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <89010000.979063602@grolsch.ai>; from jeroen@vangelderen.org on Tue, Jan 09, 2001 at 02:06:42PM -0400 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 14:06 -0400, Jeroen C. van Gelderen wrote: > > > Does this happen even if you connect the machines back to > > back (with a crossover cable?) > > I don't have a cross-over cable unfortunately, and I won't be > able to buy one where I am :-( I seem to recall however that > Intel cards don't like being connected back2back? I used to run two Intel EEPro100 cards (i82557) connected cross-over for some two years. The cable was "self produced and bottled", had a length of some four meters and ran fine at 100MBps. The wiring was taken from the (Linux) Net-3 HowTo. I've seen the pictures in IBM hubs' manuals, too. As well as any decent basic network literature (hardware wise) or your favourite cable FAQ should tell you how to do it. All it takes is some cable and two RJ-45 plugs. This will make you independent of what lengths these cables are sold at and should enable you to test this scenario without waiting for a dealer to get you those. And it will save a hub/switch (maybe of interest in a home LAN with less than three machines or for speeding up a "very important" link between two specially interdependent machines). virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 6:44:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay3.inwind.it (relay3.inwind.it [212.141.53.74]) by hub.freebsd.org (Postfix) with ESMTP id 36D2F37B402 for ; Wed, 10 Jan 2001 06:44:37 -0800 (PST) Received: from [62.98.41.58] (62.98.41.58) by relay3.inwind.it (5.1.056) id 3A40BF860041DD2D for freebsd-stable@FreeBSD.ORG; Wed, 10 Jan 2001 15:44:34 +0100 Received: (qmail 1871 invoked by uid 1000); 10 Jan 2001 14:42:50 -0000 Date: Wed, 10 Jan 2001 15:42:50 +0100 From: Francesco Casadei To: Frank Bartels Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NODESCRYPTLINKS=true Message-ID: <20010110154250.A1801@goku.kasby> Mail-Followup-To: Frank Bartels , freebsd-stable@FreeBSD.ORG References: <20010110122150.A95886@camelot.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010110122150.A95886@camelot.de>; from knarf@camelot.de on Wed, Jan 10, 2001 at 12:21:50PM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 12:21:50PM +0100, Frank Bartels wrote: > Heya all, > > we still use DES passwords on our system. If I do a make world > (4.2-STABLE), the libcrypt links in /usr/lib are replaced by ones > to libscript. I found NODESCRYPTLINKS=true in /etc/defaults/make.conf > and have put it into /etc/make.conf. But the links still get > replaced. > > The bad thing is, I cannot login after a reboot. I _think_ libscrypt > was able to detect des/md5 passwords in 3.x and logins were still > possible. > > Is there a complete documentation about libcrypt, libscrypt, > libdescrypt, passwd_format=des and the upgrading procedure from > 3.x to 4.x? > > Thanks for your help. > > Bye, > Knarf > -- > Frank Bartels | Tel: +49-89-849308-0 | CameloT - Der "sagenhafte" > knarf@camelot.de | http://www.camelot.de/ | Internet-Provider > end of the original message Make sure libcrypt.* are symlinked to libdescrypt.*. libdescrypt recognizes both DES and MD5 passwords, but the default format is DES (i.e. new passwords are DES-encrypted). To force a specific password format set the passwd_format capability in /etc/loginf.conf. For more information: - man login.conf(5) - read section 8.4 of the handbook. Francesco Casadei To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 7:32:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 80E0E37B400 for ; Wed, 10 Jan 2001 07:32:33 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id nrosaaaa for ; Thu, 11 Jan 2001 02:40:35 +1100 Message-ID: <3A5C80B4.2E5B97BE@quake.com.au> Date: Thu, 11 Jan 2001 02:33:08 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Frank Bartels Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NODESCRYPTLINKS=true References: <20010110122150.A95886@camelot.de> <3A5C4DB9.1C9F0949@quake.com.au> <20010110134920.N34155@camelot.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So there are still two questions: > > - why are the links replaced? Well with the changes they should point to libdescrypt AFAIK... > - why does my libscrypt not understand DES passwords? libdescrypt understands both, perhaps libscrypt dose not... I think I read DES libs can read des and md5 but md5 cant read DES... > My make.conf says: > > NODESCRYPTLINKS=true # do not replace libcrypt -> libscrypt links > NOPROFILE= true # Avoid compiling profiled libraries > MAKE_IDEA= YES # IDEA (128 bit symmetric encryption) > USA_RESIDENT= NO I dont think you should use NODESCRYPTLINKS since you want libdescrypt to be linked... USA_RESIDENT is redundant now... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 7:54:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id 1F96937B401 for ; Wed, 10 Jan 2001 07:54:30 -0800 (PST) Received: (qmail 21822 invoked from network); 10 Jan 2001 15:54:24 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 10 Jan 2001 15:54:24 -0000 Message-ID: <3A5C85B0.4CB3C20D@gactr.uga.edu> Date: Wed, 10 Jan 2001 10:54:24 -0500 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Harding Cc: stable@freebsd.org Subject: Re: buildworld over nfs failing consistently References: <3A5B87EE.8ACA0D05@gactr.uga.edu> <20010110141227.519C2E6A2D@netcom1.netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG no good. same problem, same place. 1) nfs server: /etc/exports: /export -alldirs -maproot=root /usr -alldirs -maproot=root /etc/make.conf: FETCH_BEFORE_ARGS=-p USA_RESIDENT=yes WITH_PNG_MMX=yes cvsup'ed last night. rebuilt and installed world successfully this morning. 2) nfs client: /etc/fstab: castro.servers.nat:/usr/src /usr/src nfs rw 0 0 castro.servers.nat:/usr/obj /usr/obj nfs rw 0 0 /etc/make.conf FETCH_BEFORE_ARGS=-p USA_RESIDENT=yes WITH_PNG_MMX=yes installworld still fails at same point. any other ideas? Mike Harding wrote: > > if /etc/make.conf is not identical on all machines the make/install > can fail... > > Date: Tue, 09 Jan 2001 16:51:42 -0500 > From: "Robin P. Blanchard" > X-Accept-Language: en > Content-Type: text/plain; charset=us-ascii > Sender: owner-freebsd-stable@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > > ok. i really need some help here. i've got several (identical) > dell poweredge servers that i've been trying to update for a few > weeks now -- all to no avail. i put together a fresh new install > on one this morning, cvsup'ed the source and successfully built and > installed world. marvelous. now for the other six machines... > > the fresh box is the NFS server with /etc/exports like so: > > /usr -alldirs -maproot=root:staff (this is a private network so i'm not > too concerned about > who's connecting -- only me) > > the six other servers have this in their /etc/fstab: > > castro.servers.nat:/usr/src /usr/src nfs rw 0 0 > castro.servers.nat:/usr/obj /usr/obj nfs rw 0 0 > > an installworld on *any* of these machines goes along just fine until > getting to: > > ===> gnu/usr.bin/perl/library/B > cd /usr/obj/usr/src/gnu/usr.bin/perl/library/B/ext/B ; make -B install > INSTALLP > RIVLIB=/usr/libdata/perl/5.00503 > INSTALLARCHLIB=/usr/libdata/perl/5.00503/mach > > where it plods along a bit more until: > > [...snip...] > vm/vnode_pager.h -> vm/vnode_pager.ph > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl/utils. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin. > *** Error code 1 > > Stop in /usr/src/gnu. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 8:33:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D18B537B400 for ; Wed, 10 Jan 2001 08:33:21 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 10 Jan 2001 16:33:20 +0000 (GMT) To: "Robin P. Blanchard" Cc: stable@freebsd.org Subject: Re: buildworld over nfs failing consistently In-Reply-To: Your message of "Wed, 10 Jan 2001 10:54:24 EST." <3A5C85B0.4CB3C20D@gactr.uga.edu> Date: Wed, 10 Jan 2001 16:33:20 +0000 From: Ian Dowse Message-ID: <200101101633.aa16973@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A5C85B0.4CB3C20D@gactr.uga.edu>, "Robin P. Blanchard" writes: >no good. >same problem, same place. Try looking carefully at the lines of output preceding the first '*** Error code 1' message. The 'h2ph' program will give out if it was unable to open any of the files in /usr/include that it tries to convert. I've seen an installworld fail because of this before. Among all the 'xxx.h -> xxx.ph' messages there should be something like: blah.h -> blah.ph Can't open blah.h: No such file or directory Usually when I've seen this, it is because of a dangling symlink on the machine where the installworld is being performed. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 8:39:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id A819937B400 for ; Wed, 10 Jan 2001 08:39:21 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0AGdKq71472 for ; Wed, 10 Jan 2001 17:39:20 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@[134.157.10.102]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0AGdJ313373 for ; Wed, 10 Jan 2001 17:39:19 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f0AGdJ301557 for stable@FreeBSD.ORG; Wed, 10 Jan 2001 17:39:19 +0100 (CET) (envelope-from michel) Date: Wed, 10 Jan 2001 17:39:19 +0100 From: Michel Talon To: stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? (Update) Message-ID: <20010110173919.A311@lpthe.jussieu.fr> Mail-Followup-To: stable@FreeBSD.ORG References: <20010109130439.A48418@grumpy.dyndns.org> <179010000.979069635@grolsch.ai> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <179010000.979069635@grolsch.ai> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 09, 2001 at 03:47:15PM -0400, Jeroen C. van Gelderen wrote: > > Hard to say if the problem is the hub or the Intel card. But seemingly > > the combination. Changing either to a different model and/or brand > > solves the problem? > > I tried 2 hubs, one claims to be a cheap 8816TPC, the other NetGear DS108. > Both give problems. Replacing the Intel card with a 3Com or SMC solves the > problem. Of course I've tried multiple cables as well. > > Maybe this is relevant. The DS108 actually is a dual speed hub. IIRC it has > a 10 Mbit bus and a 100 Mbit bus, connected with a little switch. The > machine I'm testing against has a 10Mbit card. I tried forcing to Intel to > 10Mbit and tried to transfer the file. It stalls after a couple of > megabytes. I then forced the Intel card to 100Mbit mode and tried the Just as a comparison point. I am at the moment playing installing 3 machines with resp. FreeBSD, NetBSD and OpenBSD. All 3 are connected by a small ultracheap 10MB/s hub to the net, and have Intel 10/100 cards. The FreeBSD and OpenBSD downloads were fine, but the NetBSD stalled horribly. I have tried all settings of half-duplex and full duplex without getting anything. At home i have a 3Com and i had similar stalls but solved by setting half-duplex. The settings that work are 10baseT/UTP. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 9: 4:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.21]) by hub.freebsd.org (Postfix) with SMTP id 92F6337B401 for ; Wed, 10 Jan 2001 09:04:34 -0800 (PST) Received: (qmail 29191 invoked from network); 10 Jan 2001 17:04:33 -0000 Received: from qat.noc.nat (HELO gactr.uga.edu) ([10.10.100.125]) (envelope-sender ) by mail.servers.nat (qmail-ldap-1.03) with SMTP for ; 10 Jan 2001 17:04:33 -0000 Message-ID: <3A5C9621.1D8D74F@gactr.uga.edu> Date: Wed, 10 Jan 2001 12:04:33 -0500 From: "Robin P. Blanchard" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: stable@freebsd.org Subject: Re: buildworld over nfs failing consistently References: <200101101633.aa16973@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the only message was as originally posted: vm/vnode_pager.h -> vm/vnode_pager.ph *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. *** Error code 1 it never complained about not being able to find a file, etc. it simply spat out "Error code 1" after dealing with vnode_pager.h. in desperation, i did a "make -k installworld" on all of these nfs clients. the _only_ error was the original one: vm/vnode_pager.h -> vm/vnode_pager.ph *** Error code 1 (continuing) `install' not remade because of errors. ===> gnu/usr.bin/perl/utils/h2xs install -c -o root -g wheel -m 555 h2xs /usr/bin install -c -o root -g wheel -m 444 h2xs.1.gz /usr/share/man/man1 what could be the ramifications of this? are these machines irreparably wanked? how do i prevent this from happening again? > Try looking carefully at the lines of output preceding the > first '*** Error code 1' message. The 'h2ph' program will give out > if it was unable to open any of the files in /usr/include that it > tries to convert. I've seen an installworld fail because of this > before. Among all the 'xxx.h -> xxx.ph' messages there should be > something like: > > blah.h -> blah.ph > Can't open blah.h: No such file or directory > > Usually when I've seen this, it is because of a dangling symlink > on the machine where the installworld is being performed. > > Ian -- ------------------------------------ Robin P. Blanchard Network Engineering & Support Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 9:10:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from forrie.net (forrie.net [216.67.14.69]) by hub.freebsd.org (Postfix) with ESMTP id A590537B698 for ; Wed, 10 Jan 2001 09:09:59 -0800 (PST) Received: from boomer.forrie.com (dhcp-north-71-168.navipath.net [64.20.71.168]) by forrie.net with id f0AH9mO11300; Wed, 10 Jan 2001 12:09:48 -0500 (EST) Message-Id: <5.0.2.1.2.20010110120541.02420ec0@216.67.14.69> X-Sender: forrie@216.67.14.69 X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 10 Jan 2001 12:08:59 -0500 To: freebsd-stable@freebsd.org From: Forrest Aldrich Subject: Console redirection issues Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We recently purchased a couple machines from VALinux (2U and 1U). The first machine works just fine. You can set the console redirection in the BIOS so that you can also interact with the BIOS over an out-of-band modem (very useful!). However, when we went to install the 1U system, we were only able to see the prompts up to the point where FreeBSD began the boot process. This doesn't make sense, as our configs are all the same (port address, boot.config, etc.). Our boot.config files contain "-P -D -h". So, while we have a support call into VALinux about this issue, I'm wondering if there might be a FreeBSD-related issue instead. Surely someone else has been bitten by this. Any pointers would be greatly appreciated. Thanks. _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 9:23:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 642CC37B400 for ; Wed, 10 Jan 2001 09:23:29 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 10 Jan 2001 17:23:27 +0000 (GMT) To: "Robin P. Blanchard" Cc: stable@freebsd.org, iedowse@maths.tcd.ie Subject: Re: buildworld over nfs failing consistently In-Reply-To: Your message of "Wed, 10 Jan 2001 12:04:33 EST." <3A5C9621.1D8D74F@gactr.uga.edu> Date: Wed, 10 Jan 2001 17:23:27 +0000 From: Ian Dowse Message-ID: <200101101723.aa25474@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A5C9621.1D8D74F@gactr.uga.edu>, "Robin P. Blanchard" writes: >the only message was as originally posted: > >vm/vnode_pager.h -> vm/vnode_pager.ph >*** Error code 1 Sorry, I probably wasn't very clear. Before the first '*** Error code 1' message there will be a long list of 'xxx.h -> xxx.ph' messages, looking something like a.out.h -> a.out.ph aio.h -> aio.ph alias.h -> alias.ph ... cam/cam_ccb.h -> cam/cam_ccb.ph cam/cam_debug.h -> cam/cam_debug.ph ... vm/vm_zone.h -> vm/vm_zone.ph vm/vnode_pager.h -> vm/vnode_pager.ph (there are probably about 900 lines in this list altogether). Somewhere among this long list will be an error message, and the filename preceeding the error message will be the file that h2ph couldn't open. Ian >> Try looking carefully at the lines of output preceding the >> first '*** Error code 1' message. The 'h2ph' program will give out >> if it was unable to open any of the files in /usr/include that it >> tries to convert. I've seen an installworld fail because of this >> before. Among all the 'xxx.h -> xxx.ph' messages there should be >> something like: >> >> blah.h -> blah.ph >> Can't open blah.h: No such file or directory >> >> Usually when I've seen this, it is because of a dangling symlink >> on the machine where the installworld is being performed. >> >> Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 9:37:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bitbucket.extern.uniface.nl (bitbucket.extern.uniface.nl [193.78.88.139]) by hub.freebsd.org (Postfix) with ESMTP id 9563A37B401 for ; Wed, 10 Jan 2001 09:37:20 -0800 (PST) Received: from bh2.nl.compuware.com (unknown [172.16.17.82]) by bitbucket.extern.uniface.nl (Postfix) with ESMTP id D05CB829D; Wed, 10 Jan 2001 18:37:18 +0100 (CET) Received: from c1111.nl.compuware.com ([172.16.16.36]) by bh2.nl.compuware.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id CV7M63N8; Wed, 10 Jan 2001 18:37:18 +0100 Received: from nl.compuware.com (bertd@localhost [127.0.0.1]) by c1111.nl.compuware.com (8.9.3/8.9.3) with ESMTP id SAA28315; Wed, 10 Jan 2001 18:37:18 +0100 (CET) Message-ID: <3A5C9DCE.7D7964D1@nl.compuware.com> Date: Wed, 10 Jan 2001 18:37:18 +0100 From: Bert Driehuis Organization: Compuware Europe (but I only speak for myself) X-Mailer: Mozilla 4.74 [en] (X11; U; BSD/OS 4.1 i386) X-Accept-Language: en, fr MIME-Version: 1.0 To: Forrest Aldrich Cc: freebsd-stable@freebsd.org Subject: Re: Console redirection issues References: <5.0.2.1.2.20010110120541.02420ec0@216.67.14.69> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forrest Aldrich wrote: > However, when we went to install the 1U system, we were only able to see > the prompts up to the point where FreeBSD began the boot process. This > doesn't make sense, as our configs are all the same (port address, > boot.config, etc.). Our boot.config files contain "-P -D -h". I haven't actually tested this, but the documentation for boot(8) says that '-D' and 'h' toggle the bhavior, and that '-P' sets -D and -h. This might mean that -P sets -D and -h, and the subsequent -D and -h *reset* them once again. I'd suggest removing them; I'm running with just -D just fine. Cheers, --- Bert -- Bert Driehuis, MIS -- bert_driehuis@nl.compuware.com -- +31-20-3116119 Dihydrogen Monoxide kills! Join the campaign at http://www.dhmo.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 10: 5: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id F061537B699 for ; Wed, 10 Jan 2001 10:04:38 -0800 (PST) Received: (qmail 33949 invoked from network); 10 Jan 2001 18:04:37 -0000 Received: from unknown (HELO prydn.tacni.net) (207.55.167.106) by 216.178.136.168 with SMTP; 10 Jan 2001 18:04:37 -0000 Received: (qmail 334 invoked by uid 1001); 10 Jan 2001 18:04:36 -0000 Date: Wed, 10 Jan 2001 12:04:36 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Userland and Kernel out of sync Message-ID: <20010110120435.A271@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am still getting ps and top errors. I followed /usr/src/UPDATING instructions completely. I then figured okay /usr/src is out of sync so I rm -rf'ed /usr/src and /usr/sup/src-all I then cvsup'ed the entire RELENG_4 source tree down again and then I cvsup'ed one more time to make sure no changes were committed during this download. I then followed /usr/src/UPDATING again and ps and top still error out. I did last week downgrade from 4.2-STABLE to 4.2-RELEASE and then back up to 4.2-STABLE for some testing purposes, could this be the problem? -- Erich Zigler Reality is just Chaos with better lighting. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 11: 3:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 0AA7937B402 for ; Wed, 10 Jan 2001 11:03:35 -0800 (PST) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.1/8.11.0) with ESMTP id f0AJ7NI03745 for ; Wed, 10 Jan 2001 20:07:23 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Wed, 10 Jan 2001 20:07:23 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: massive SMP problems ... 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 Within the last thee weeks I did many changes on our central server and some of them seems not to be very "cure" to them. The first change was to exchange the older Adaptec 2940U2W against a two channel LSI Logik 21040 (64 Bit PCI connector, but fits and works with PCI 32). I changed the appropriate things for the new controller in the kernel. Then I changed console driver from VT to SC. I installed "option VESA" into the kernel config file although the system is a SMP machine and I read in the past, I think it was FBSD 3.x, that VESA and SMP turns into problems. Then i "cleaned" up the kernel config file, I pulled out some config options which seems to be "tweaking parameters to come alongside with "GENERIC" and an optimized config without ballast. Then, several days ago, I made the first cvsupdate and today the same. The end of the story is, that our server is very instable. Sometimes I get obscure errors about not working gcc, cpp ends up with a fatal error 11. The changes in the kernel seems not to be subject of suspicion, I think. It's really small, except the change VT -> SC code. I try now to extract the VESA code and leave the kernel without it to see what happens. At this stage I would like to ask the FBSD community whether there are still known problems with SMP systems and some kernel facilities? the other question is about LSI Logik 21040 controller vs. Adaptec 2940U2W controller. It seems, as of my point of view, that the LSI Logik is a little bit slower than the Adaptec controller (I did not change the drives, they are still 80MB/s LVD IBM drives). thanks for some hints or kicks ... - MfG O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 11: 4:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 0C9E437B698 for ; Wed, 10 Jan 2001 11:03:56 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id A3AB53E5D; Wed, 10 Jan 2001 20:03:54 +0100 (CET) Date: Wed, 10 Jan 2001 20:03:54 +0100 From: Jesper Skriver To: Michel Talon Cc: stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? (Update) Message-ID: <20010110200354.B17398@skriver.dk> References: <20010109130439.A48418@grumpy.dyndns.org> <179010000.979069635@grolsch.ai> <20010110173919.A311@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010110173919.A311@lpthe.jussieu.fr>; from michel@lpthe.jussieu.fr on Wed, Jan 10, 2001 at 05:39:19PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 05:39:19PM +0100, Michel Talon wrote: > On Tue, Jan 09, 2001 at 03:47:15PM -0400, Jeroen C. van Gelderen wrote: > > > Hard to say if the problem is the hub or the Intel card. But seemingly > > > the combination. Changing either to a different model and/or brand > > > solves the problem? > > > > I tried 2 hubs, one claims to be a cheap 8816TPC, the other NetGear DS108. > > Both give problems. Replacing the Intel card with a 3Com or SMC solves the > > problem. Of course I've tried multiple cables as well. > > > > Maybe this is relevant. The DS108 actually is a dual speed hub. IIRC it has > > a 10 Mbit bus and a 100 Mbit bus, connected with a little switch. The > > machine I'm testing against has a 10Mbit card. I tried forcing to Intel to > > 10Mbit and tried to transfer the file. It stalls after a couple of > > megabytes. I then forced the Intel card to 100Mbit mode and tried the > > Just as a comparison point. I am at the moment playing installing 3 machines > with resp. FreeBSD, NetBSD and OpenBSD. All 3 are connected by a small > ultracheap 10MB/s hub to the net, and have Intel 10/100 cards. The FreeBSD ^^^ > and OpenBSD downloads were fine, but the NetBSD stalled horribly. I have tried > all settings of half-duplex and full duplex without getting anything. At home ^^^^^^^^^^^ ^^^^^^^^^^^ > i have a 3Com and i had similar stalls but solved by setting half-duplex. ^^^^^^^^^^^ When using a hub you MUST use half-duplex. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 11:38:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 5CD1537B402 for ; Wed, 10 Jan 2001 11:38:26 -0800 (PST) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.11.1/8.11.1) with ESMTP id f0AJcQm31242 for ; Wed, 10 Jan 2001 11:38:26 -0800 (PST) (envelope-from nsayer@medusa.kfu.com) Received: (from nsayer@localhost) by medusa.kfu.com (8.11.1/8.11.0) id f0AJcPL58553 for freebsd-stable@freebsd.org; Wed, 10 Jan 2001 11:38:25 -0800 (PST) (envelope-from nsayer) Date: Wed, 10 Jan 2001 11:38:25 -0800 (PST) From: Nick Sayer Message-Id: <200101101938.f0AJcPL58553@medusa.kfu.com> To: freebsd-stable@freebsd.org Subject: SMP on a Dell Precision 220? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The symptom is that if I turn on the 2nd cpu in the BIOS, I can't get through a buildworld without a symptom indicative of memory corruption (cc1 SEGVs that happen in different spots, etc). Without changing the kernel, disabling the 2nd cpu yields a system that works just fine. mptable tells me that the default kernel options should be fine on this machine (they're what I used). I am attaching the config file and dmesg of it in its current, usable, UP state. Anyone have any suggestions? (I am running a vmware guest on this machine, but that doesn't seem to have anything to do with the problem). # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.20 2000/10/31 23:16:07 n_hibma Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident BEAST maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # ATA and ATAPI devices #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family #device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? #disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card #device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 #device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device tx # SMC 9432TX (83c170 ``EPIC'') #device vx # 3Com 3c590, 3c595 (``Vortex'') #device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device pcn # AMD Am79C79x PCI 10/100 NICs #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex #device ep #device fe0 at isa? port 0x300 # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. #device an # Xircom Ethernet #device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 device pcm # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) #pseudo-device md # Memory "disks" #pseudo-device gif 4 # IPv6 and IPv4 tunneling #pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #1: Tue Jan 9 10:04:22 PST 2001 root@temp.TALARIAN.COM:/usr/src/sys/compile/BEAST Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (794.66-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 536469504 (523896K bytes) config> di atkbdc0 config> di atkbd0 config> di psm0 config> q avail memory = 518713344 (506556K bytes) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170020, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc039e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc039e09c. Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 16 pcib2: at device 30.0 on pci0 pci2: on pcib2 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec80-0xecff mem 0xfafffc00-0xfafffc7f irq 18 at device 12.0 on pci2 xl0: Ethernet address: 00:b0:d0:24:3a:ae miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xff80-0xff9f irq 19 at device 31.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ukbd0: Sun Microsystems Type 6 USB, rev 1.00/1.01, addr 2, iclass 3/1 kbd0 at ukbd0 ums0: Primax Electronics product 0x4d03, rev 1.00/4.41, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 17 pcm0: port 0xdc80-0xdcbf,0xd800-0xd8ff irq 17 at device 31.5 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 ad0: 39082MB [79406/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $ /dev/vmmon: Module vmmon: initialized xl0: promiscuous mode enabled vmnet1: promiscuous mode enabled To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 12: 4:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id F1B6437B404 for ; Wed, 10 Jan 2001 12:04:28 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0AK38Y14826; Wed, 10 Jan 2001 12:03:08 -0800 (PST) Date: Wed, 10 Jan 2001 12:03:07 -0800 From: Alfred Perlstein To: "O. Hartmann" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: massive SMP problems ... Message-ID: <20010110120307.G7240@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Wed, Jan 10, 2001 at 08:07:23PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No mention of what version of FreeBSD you're actually running makes it hard to diagnose except for: * O. Hartmann [010110 11:04] wrote: > the first cvsupdate and today the same. The end of the story is, that > our server is very instable. Sometimes I get obscure errors about not > working gcc, cpp ends up with a fatal error 11. The changes in the kernel Looks like you have some sort of heat/memory/cache issue here, gcc should not die under sig11, and sig11 is a pretty well known indicator of hardware problems. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 12:38:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.ihug.co.nz (smtp2.ihug.co.nz [203.109.252.8]) by hub.freebsd.org (Postfix) with ESMTP id 282B537B401 for ; Wed, 10 Jan 2001 12:38:00 -0800 (PST) Received: from spandex (203-173-201-176.nzwide.ihug.co.nz [203.173.201.176]) by smtp2.ihug.co.nz (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id JAA29126; Thu, 11 Jan 2001 09:37:28 +1300 X-Authentication-Warning: smtp2.ihug.co.nz: Host 203-173-201-176.nzwide.ihug.co.nz [203.173.201.176] claimed to be spandex Message-ID: <008901c07b45$b66e0f80$b0c9adcb@spandex> From: "Matthew Luckie" To: "Dan Larsson" Cc: References: Subject: Re: Cleaning out old/unused files after make world Date: Thu, 11 Jan 2001 09:41:00 +1300 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm no expert on this, having only done one cvsup - the other day This could be taken a few ways - i can think of three: - removing intermediary files /usr/obj - removing source files that were in 3.2 but no longer needed in 4.2 - removing configuration files that are no longer used The handbook says what to do with the /usr/obj files (18.4.5 && 18.4.13.3) As far as i could tell when doing the cvsup, i could see files being deleted when i was going from 4.2R to 4.2S. I guess that those source files no longer needed were deleted. As for the configuration files - i can only guess that the filenames of these files dont change very often, and are thus unlikely to be not needed. I'm sure /usr/src/UPDATING would say something if there were some config files that could be deleted. Or perhaps mergemaster takes care of this. To others on the list - if this is wrong please correct me - i was just guessing. Matthew Luckie kluckie@ihug.co.nz http://homepages.ihug.co.nz/~kluckie/ ----- Original Message ----- From: Dan Larsson To: FreeBSD Stable List Sent: Thursday, January 11, 2001 2:01 AM Subject: Cleaning out old/unused files after make world > The machine i question has stepwise been updated from 3.2R > to 4.2S, and I'm guessing some files are nolonger needed by > the system. > > How can I find out which files can be removed? > > Regards > +------ > Dan Larsson | Tel: +46 8 550 120 21 > Tyfon Svenska AB | Fax: +46 8 550 120 02 > GPG and PGP keys | finger dl@hq1.tyfon.net > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 13:15:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 468A337B6A2 for ; Wed, 10 Jan 2001 13:15:01 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.20 #1) id 14GSWg-0002RW-00; Wed, 10 Jan 2001 21:11:22 +0000 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.1/8.11.1) id f0ALBLt28368; Wed, 10 Jan 2001 21:11:21 GMT (envelope-from ben) Date: Wed, 10 Jan 2001 21:11:21 +0000 From: Ben Smithurst To: Dan Larsson Cc: FreeBSD Stable List Subject: Re: Cleaning out old/unused files after make world Message-ID: <20010110211121.W79365@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Larsson wrote: > The machine i question has stepwise been updated from 3.2R > to 4.2S, and I'm guessing some files are nolonger needed by > the system. > > How can I find out which files can be removed? Start with find(1)'s -mtime option, removing files older than your last buildworld in appropriate directories. Where `appropriate directories' are those completely updated by buildworld (i.e. NOT /etc, /usr/local, and so on). Mainly I'd go for /bin /sbin /usr/bin /usr/sbin /usr/libexec /usr/share /usr/libdata. Also, I wouldn't remove old libraries from /usr/lib since stuff in /usr/local might still be using them. And be careful what you delete, of course. :-) -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 14: 7:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.javanet.com (mail1.javanet.com [205.219.162.10]) by hub.freebsd.org (Postfix) with ESMTP id 4DAE837B69D for ; Wed, 10 Jan 2001 14:07:11 -0800 (PST) Received: from wintermute.sekt7.org (146-115-74-28.c5-0.brl-ubr1.sbo-brl.ma.cable.rcn.com [146.115.74.28]) by mail1.javanet.com (8.9.3/8.9.2) with ESMTP id RAA27328 for ; Wed, 10 Jan 2001 17:07:10 -0500 (EST) Date: Wed, 10 Jan 2001 17:10:37 -0500 (EST) From: Evan S X-Sender: kaworu@wintermute.sekt7 To: freebsd-stable@freebsd.org Subject: encrypted loopback filesystems 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 Hey, I was wondering if FreeBSD supported encrypted loopback filesystems. I've searched the mailing lists and deja.com to no avil. Does anyone know about this? Thanks, Evan Sarmiento (kaworu@sektor7.ath.cx) http://sekt7.org/es To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 14:11:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id F035137B69D for ; Wed, 10 Jan 2001 14:10:54 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 10 Jan 2001 22:10:54 +0000 (GMT) Date: Wed, 10 Jan 2001 22:10:53 +0000 From: David Malone To: Nick Sayer Cc: freebsd-stable@freebsd.org Subject: Re: SMP on a Dell Precision 220? Message-ID: <20010110221053.A33238@walton.maths.tcd.ie> References: <200101101938.f0AJcPL58553@medusa.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101101938.f0AJcPL58553@medusa.kfu.com>; from nsayer@quack.kfu.com on Wed, Jan 10, 2001 at 11:38:25AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 11:38:25AM -0800, Nick Sayer wrote: > The symptom is that if I turn on the 2nd cpu in the BIOS, I can't get through > a buildworld without a symptom indicative of memory corruption (cc1 SEGVs > that happen in different spots, etc). We had some problems like this and it turned out to be cruddy CPU fans. The CPUs run hotter in SMP mode, I think because it doesn't use the halt instruction then. In the end we bolted the fans on more tightly and the problem stopped. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 14:13:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from staff.nyi.net (staff.nyi.net [204.248.157.16]) by hub.freebsd.org (Postfix) with SMTP id 181EE37B6A0 for ; Wed, 10 Jan 2001 14:12:50 -0800 (PST) Received: (qmail 15713 invoked by uid 1004); 10 Jan 2001 22:08:02 -0000 Message-ID: <20010110220802.15712.qmail@staff.nyi.net> From: "Javier Frias" To: freebsd-questions@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Central Source Updates Date: Wed, 10 Jan 2001 22:08:02 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm wondering what everyone here is doing to do centralized source updates on their server farms. Right now we've been doing it manually on each server, but now we are trying to come up with procedures to try to centralized the situation a bit. I've come up with two basical startegies. One central and one localized. 1) Central Having one source repository server and one compile/build server. the source repository would be just a basic freebsd mirror. The build server would be a machine that would keep different versions of FreeBSD in both source and binary form, compiled witht he optimazations to our liking ie /disk01/FreeBSD4-STABLE/00010120/src /disk01/FreeBSD4-STABLE/00010120/obj these directories woud be nfs exportable read-only. so when a machine wants to update it's system would mount thses dir's over their /usr and /usr/obj and do a make install. PROS: quick CONS: donot get to test machines, i like make world since they are usually good at detecting hardware issues ( memory disk etc ) 2) Localized Having one source repository server the source repository would be just a basic freebsd mirror. machines would use cvs to update to a specify version date combination. and build locally Packages would mostly not be an issue, since we are pushing all developers to make custom freebsd packages for all the software we use, and we'll test each on the specific OS combinations. SO, does anyone have any comments or pointers on how to better these solutions or which is better to use. any pointers to articles, documents etc? ( besides the handbook section on updating :-P ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 14:14:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2FF6C37B69D for ; Wed, 10 Jan 2001 14:14:05 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0AMDwT19258; Wed, 10 Jan 2001 14:13:58 -0800 (PST) Date: Wed, 10 Jan 2001 14:13:58 -0800 From: Alfred Perlstein To: Evan S Cc: freebsd-stable@FreeBSD.ORG Subject: Re: encrypted loopback filesystems Message-ID: <20010110141358.M7240@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kaworu@sektor7.ath.cx on Wed, Jan 10, 2001 at 05:10:37PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Evan S [010110 14:08] wrote: > Hey, > > I was wondering if FreeBSD supported encrypted loopback filesystems. I've > searched the mailing lists and deja.com to no avil. Does anyone know about > this? /usr/ports/security/cfs -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 14:15:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jura.pi.solnet.ch (skye.pi.solnet.ch [212.101.5.253]) by hub.freebsd.org (Postfix) with ESMTP id AA65A37B6A0 for ; Wed, 10 Jan 2001 14:14:50 -0800 (PST) Received: (from pi@localhost) by jura.pi.solnet.ch (8.11.1/8.11.1) id f0AMEfY03208 for freebsd-stable@FreeBSD.ORG; Wed, 10 Jan 2001 23:14:41 +0100 (CET) (envelope-from pi) Date: Wed, 10 Jan 2001 23:14:41 +0100 From: Reto Trachsel To: freebsd-stable@FreeBSD.ORG Subject: USB to RS232 Converter Message-ID: <20010110231441.A3189@inalp.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All I have a Laptop without a RS232 Port. But there's a USB Connector. I've a USB to RS232 Device. But i don't get it to work. Here's the Kernel message: ugen0: MCT Corp. product 0x0230, rev 1.10/1.02, addr 2 Can anybode help me, or has some ideas? -- Regards Reto Trachsel _____/\/\/\__ InAlp Networks Inc. - www.inalp.com Mobile: +41 79 279 44 41 eMail: reto.trachsel@inalp.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 14:48:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.ihug.co.nz (smtp2.ihug.co.nz [203.109.252.8]) by hub.freebsd.org (Postfix) with ESMTP id 2026C37B698 for ; Wed, 10 Jan 2001 14:48:12 -0800 (PST) Received: from spandex (203-173-201-176.nzwide.ihug.co.nz [203.173.201.176]) by smtp2.ihug.co.nz (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id LAA12584; Thu, 11 Jan 2001 11:47:55 +1300 X-Authentication-Warning: smtp2.ihug.co.nz: Host 203-173-201-176.nzwide.ihug.co.nz [203.173.201.176] claimed to be spandex Message-ID: <00d401c07b57$e8990ed0$b0c9adcb@spandex> From: "Matthew Luckie" To: Cc: References: <20010110141358.M7240@fw.wintelcom.net> Subject: Re: encrypted loopback filesystems Date: Thu, 11 Jan 2001 11:44:07 +1300 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.freebsddiary.org/encrypted-fs.html did a piece on using encrypted file systems this may be of use to you. Matthew Luckie kluckie@ihug.co.nz http://homepages.ihug.co.nz/~kluckie/ ----- Original Message ----- From: Alfred Perlstein To: Evan S Cc: Sent: Thursday, January 11, 2001 11:13 AM Subject: Re: encrypted loopback filesystems > * Evan S [010110 14:08] wrote: > > Hey, > > > > I was wondering if FreeBSD supported encrypted loopback filesystems. I've > > searched the mailing lists and deja.com to no avil. Does anyone know about > > this? > > /usr/ports/security/cfs > > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 17: 0:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scribe.pobox.com (scribe.pobox.com [208.210.124.35]) by hub.freebsd.org (Postfix) with ESMTP id 4F22A37B400 for ; Wed, 10 Jan 2001 17:00:26 -0800 (PST) Received: from daemon (unknown [207.8.144.30]) by scribe.pobox.com (Postfix) with SMTP id 1B46632597; Wed, 10 Jan 2001 20:00:25 -0500 (EST) From: "Jamil Taylor" To: "David Malone" , "Nick Sayer" Cc: Subject: RE: SMP on a Dell Precision 220? Date: Wed, 10 Jan 2001 20:00:24 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010110221053.A33238@walton.maths.tcd.ie> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what it's worth, I'm running 4.2 Stable on an SMP Precision 420. My Dell does not include CPU fans, and I have not run into problems. Did you try Dell's diagnostic utility from the bootable CD-ROM at all? -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of David Malone Sent: Wednesday, January 10, 2001 5:11 PM To: Nick Sayer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP on a Dell Precision 220? On Wed, Jan 10, 2001 at 11:38:25AM -0800, Nick Sayer wrote: > The symptom is that if I turn on the 2nd cpu in the BIOS, I can't get through > a buildworld without a symptom indicative of memory corruption (cc1 SEGVs > that happen in different spots, etc). We had some problems like this and it turned out to be cruddy CPU fans. The CPUs run hotter in SMP mode, I think because it doesn't use the halt instruction then. In the end we bolted the fans on more tightly and the problem stopped. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 19:34:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pro.fais.net (unknown [208.249.141.254]) by hub.freebsd.org (Postfix) with ESMTP id EEE7D37B400 for ; Wed, 10 Jan 2001 19:34:20 -0800 (PST) Received: from drnet.fais.net (root@drnet.fais.net [208.249.141.246]) by pro.fais.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id WAA17017 for ; Wed, 10 Jan 2001 22:18:14 -0600 Received: from wks01.drnet.fais.net (wks01.drnet.fais.net [10.0.0.10]) by drnet.fais.net (8.11.0/8.11.0) with SMTP id f0B3YEw22626 for ; Wed, 10 Jan 2001 21:34:16 -0600 (CST) (envelope-from jwpauler@jwpages.com) From: "Justin W. Pauler" Reply-To: jwpauler@jwpages.com Date: Wed, 10 Jan 2001 21:34:12 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" To: freebsd-stable@freebsd.org Subject: Next release MIME-Version: 1.0 Message-Id: <01011021341201.00227@wks01.drnet.fais.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey everyone... Whats the next release date, 4.2-R I presume... -- Justin W. Pauler FlexiShell Internet Services E-Mail: jwpauler@jwpages.com WWW: http://www.jwpages.com IRC: drnet@#EggDrop, Undernet IRC Network ----------------------------------------------------------------------- Hanlon's Razor: Never attribute to malice that which is adequately explained by stupidity. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 19:41:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.bna.bellsouth.net (mail1.bna.bellsouth.net [205.152.150.13]) by hub.freebsd.org (Postfix) with ESMTP id C3A7337B400 for ; Wed, 10 Jan 2001 19:41:21 -0800 (PST) Received: from planetwe.com (adsl-20-109-209.bna.bellsouth.net [66.20.109.209]) by mail1.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id WAA10646; Wed, 10 Jan 2001 22:41:19 -0500 (EST) Message-ID: <3A5D2AF5.2050807@planetwe.com> Date: Wed, 10 Jan 2001 21:39:33 -0600 From: Drew Sanford User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.12 i386; en-US; m18) Gecko/20001107 Netscape6/6.0 X-Accept-Language: en MIME-Version: 1.0 To: jwpauler@jwpages.com Cc: freebsd-stable@freebsd.org Subject: Re: Next release References: <01011021341201.00227@wks01.drnet.fais.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, the next release should be 4.3 - And I expect those in the know will tell you it'll be released when they see a need to - just because thats usually how it happens, not because anyone's trying to make you mad:) Justin W. Pauler wrote: > Hey everyone... > > Whats the next release date, 4.2-R I presume... -- Drew Sanford Systems Administrator drew@planetwe.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 19:47:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id DF32837B401 for ; Wed, 10 Jan 2001 19:47:20 -0800 (PST) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 14GYhp-000PFr-00; Wed, 10 Jan 2001 19:47:18 -0800 Date: Wed, 10 Jan 2001 19:47:12 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Justin W. Pauler" Cc: freebsd-stable@freebsd.org Subject: Re: Next release In-Reply-To: <01011021341201.00227@wks01.drnet.fais.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 On Wed, 10 Jan 2001, Justin W. Pauler wrote: > Whats the next release date, 4.2-R I presume... 4.2-RELEASE was released in late November. To anyone using cvsup, releases are growing increasingly meaningless. In fact, releases of the stable branch seem to cause everyone and their dog to rush in new patches into the tree Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 20: 7:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from changeofhabit.mr.itd.umich.edu (changeofhabit.mr.itd.umich.edu [141.211.144.17]) by hub.freebsd.org (Postfix) with ESMTP id C5F1637B401 for ; Wed, 10 Jan 2001 20:06:56 -0800 (PST) Received: from tim.elnsng1.mi.home.com (c1129767-a.elnsng1.mi.home.com [24.183.248.20]) by changeofhabit.mr.itd.umich.edu (8.9.3/3.2r) with SMTP id XAA24126; Wed, 10 Jan 2001 23:06:39 -0500 (EST) From: Tim McMillen To: Drew Sanford , jwpauler@jwpages.com Subject: Re: Next release Date: Wed, 10 Jan 2001 23:10:46 -0500 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-stable@FreeBSD.ORG References: <01011021341201.00227@wks01.drnet.fais.net> <3A5D2AF5.2050807@planetwe.com> In-Reply-To: <3A5D2AF5.2050807@planetwe.com> MIME-Version: 1.0 Message-Id: <01011023093805.00498@tim.elnsng1.mi.home.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually it says right now on http://www.freebsd.org/releases/ that 4.3 will be available in late March. It seems unusual that such a precise time would be placed on the release already. I think the date is fairly arbitrary and is just to give people an idea. If problems show up in the tree around that time, I'm sure they would get fixed and the release delayed to make sure they are fixed. That is the beauty of free software. A release won't be made just because it is deemed time, it will be made when it is a good time. I'm sure most on this list know all this, so most of that was for you, Justin. Tim On Wednesday January 10, 2001 22:39, Drew Sanford wrote: > Actually, the next release should be 4.3 - And I expect those in the > know will tell you it'll be released when they see a need to - just > because thats usually how it happens, not because anyone's trying to > make you mad:) > > Justin W. Pauler wrote: > > Hey everyone... > > > > Whats the next release date, 4.2-R I presume... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 20:23:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id B71C537B400 for ; Wed, 10 Jan 2001 20:23:08 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0B4MDi15448; Wed, 10 Jan 2001 20:22:14 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Tim McMillen Cc: Drew Sanford , jwpauler@jwpages.com, freebsd-stable@FreeBSD.ORG Subject: Re: Next release In-Reply-To: Message from Tim McMillen of "Wed, 10 Jan 2001 23:10:46 EST." <01011023093805.00498@tim.elnsng1.mi.home.com> Date: Wed, 10 Jan 2001 20:22:13 -0800 Message-ID: <15444.979186933@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Actually it says right now on http://www.freebsd.org/releases/ > that 4.3 will be available in late March. It seems unusual that such a > precise time would be placed on the release already. I think the date Not really. We schedule the releases for every 4 months, that being 3 a year, and they thus fall on predictable months (the day is a little more loose, usually specified with no more than 2 weeks precision). The schedule is set on a date vs feature basis because the former practice leads to a better track record in getting releases out on a timely basis and because if you want to do things like provide CD media, you need to pre-schedule time with the CD replicators and they don't work to fuzzy schedules. That said, a release has been known to be delayed or even cancelled due to some major problem, but that's a rare event and one which will hopefully remain so. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 20:34:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id EB65537B402 for ; Wed, 10 Jan 2001 20:34:40 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id UAA10840; Wed, 10 Jan 2001 20:33:51 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101110433.UAA10840@spammie.svbug.com> Date: Wed, 10 Jan 2001 20:33:49 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: Next release To: jkh@winston.osd.bsdi.com Cc: timcm@umich.edu, drew@planetwe.com, jwpauler@jwpages.com, freebsd-stable@FreeBSD.ORG In-Reply-To: <15444.979186933@winston.osd.bsdi.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll go even further. Yesterday Apple (http://www.apple.com) anounce the formal release date of March 24, 2001 for OS X. Jessem. On 10 Jan, Jordan Hubbard wrote: >> >> Actually it says right now on http://www.freebsd.org/releases/ >> that 4.3 will be available in late March. It seems unusual that such a >> precise time would be placed on the release already. I think the date > > Not really. We schedule the releases for every 4 months, that being 3 > a year, and they thus fall on predictable months (the day is a little > more loose, usually specified with no more than 2 weeks precision). > > The schedule is set on a date vs feature basis because the former > practice leads to a better track record in getting releases out on a > timely basis and because if you want to do things like provide CD > media, you need to pre-schedule time with the CD replicators and they > don't work to fuzzy schedules. > > That said, a release has been known to be delayed or even cancelled > due to some major problem, but that's a rare event and one which will > hopefully remain so. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 21:15:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from changeofhabit.mr.itd.umich.edu (changeofhabit.mr.itd.umich.edu [141.211.144.17]) by hub.freebsd.org (Postfix) with ESMTP id 6596E37B401 for ; Wed, 10 Jan 2001 21:15:02 -0800 (PST) Received: from tim.elnsng1.mi.home.com (c1129767-a.elnsng1.mi.home.com [24.183.248.20]) by changeofhabit.mr.itd.umich.edu (8.9.3/3.2r) with SMTP id AAA00023; Thu, 11 Jan 2001 00:14:56 -0500 (EST) From: Tim McMillen To: Jordan Hubbard Subject: Re: Next release Date: Thu, 11 Jan 2001 00:19:13 -0500 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" Cc: Drew Sanford , jwpauler@jwpages.com, freebsd-stable@FreeBSD.ORG References: <15444.979186933@winston.osd.bsdi.com> In-Reply-To: <15444.979186933@winston.osd.bsdi.com> MIME-Version: 1.0 Message-Id: <0101110019130B.00498@tim.elnsng1.mi.home.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday January 10, 2001 23:22, Jordan Hubbard wrote: > > Actually it says right now on http://www.freebsd.org/releases/ > > that 4.3 will be available in late March. It seems unusual that > > such a precise time would be placed on the release already. I > > think the date > > Not really. We schedule the releases for every 4 months, that being > 3 a year, and they thus fall on predictable months (the day is a > little more loose, usually specified with no more than 2 weeks > precision). Good to know. Sorry for the slightly off topic reply to -stable now. I was going by the fact that the date for 4.2 was not mentioned on the website (even though I had seen it mentioned in the mailing lists), nor was the date for 4.1.1 I realize 4.1.1 was a special case. While I knew releases happen fairly regularly, I had never seen a date posted on the website this far in advance. Obviously with the CVS repository of the webpages I could be proved even further wrong possibly, but why would anybody do that? :~) And to further promulgate my mistake in the archives, I'll add a question. Is there any chance of a longer release candidate stage? More testing and bug fixing would lead to a more stable system, one would hope. Or is the release candidate too disruptive to stable anyway? Is there a way to separate of the release candidate and lift the stable freeze while the release candidates are tested further? Obviously I'm showing my ignorance of how this process works now by my questions, but oh well. :) Tim > The schedule is set on a date vs feature basis because the former > practice leads to a better track record in getting releases out on a > timely basis and because if you want to do things like provide CD > media, you need to pre-schedule time with the CD replicators and they > don't work to fuzzy schedules. > > That said, a release has been known to be delayed or even cancelled > due to some major problem, but that's a rare event and one which will > hopefully remain so. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 21:17:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 676A237B400 for ; Wed, 10 Jan 2001 21:17:40 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 4A30D177EF1 for ; Wed, 10 Jan 2001 23:17:35 -0600 (CST) Message-ID: <001b01c07b8d$cec81c40$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Subject: /modules Date: Wed, 10 Jan 2001 23:17:35 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG is there a list that describes each of the modules in /modules? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 21:59:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id A7C7237B400 for ; Wed, 10 Jan 2001 21:59:26 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0B5wVi15693; Wed, 10 Jan 2001 21:58:32 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Tim McMillen Cc: Drew Sanford , jwpauler@jwpages.com, freebsd-stable@FreeBSD.ORG Subject: Re: Next release In-Reply-To: Message from Tim McMillen of "Thu, 11 Jan 2001 00:19:13 EST." <0101110019130B.00498@tim.elnsng1.mi.home.com> Date: Wed, 10 Jan 2001 21:58:31 -0800 Message-ID: <15689.979192711@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Good to know. Sorry for the slightly off topic reply to -stable now. > I was going by the fact that the date for 4.2 was not mentioned on the > website (even though I had seen it mentioned in the mailing lists), nor But it IS listed on the web site and has for some time now. Please see http://www.freebsd.org/releases - I see 4.2 clearly there. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 22: 4:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 52D1F37B402; Wed, 10 Jan 2001 22:03:51 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA01324; Thu, 11 Jan 2001 01:03:50 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id BAA29354; Thu, 11 Jan 2001 01:03:49 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA29346; Thu, 11 Jan 2001 01:03:49 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Thu, 11 Jan 2001 01:03:49 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: wierd errors 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 got this wierd error from trying to install the latest windowmaker port: Jan 11 00:56:11 culverk /kernel: proc: table is full Jan 11 00:56:14 culverk last message repeated 1022 times I know this isn't supposed to happen... and I've never seen it happen before... any ideas? Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 22:13:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id B194137B400; Wed, 10 Jan 2001 22:13:05 -0800 (PST) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id RAA28084; Thu, 11 Jan 2001 17:12:54 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id RAA19541; Thu, 11 Jan 2001 17:12:53 +1100 (EST) Message-Id: <200101110612.RAA19541@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Kenneth Wayne Culver Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: wierd errors In-reply-to: Your message of Thu, 11 Jan 2001 01:03:49 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jan 2001 17:12:53 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jan 11 00:56:11 culverk /kernel: proc: table is full > Jan 11 00:56:14 culverk last message repeated 1022 times This says you have run out of process slots in the kernel - running too many jobs. Either run fewer processes (e.g. use "make -j4" rather than "make -j8") or build a new kernel with a higher maxusers parameter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 22:36:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 48FA137B401; Wed, 10 Jan 2001 22:36:04 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA27859; Thu, 11 Jan 2001 01:35:56 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id BAA01950; Thu, 11 Jan 2001 01:35:55 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA01946; Thu, 11 Jan 2001 01:35:55 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Thu, 11 Jan 2001 01:35:55 -0500 (EST) From: Kenneth Wayne Culver To: Gregory Bond Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: wierd errors In-Reply-To: <200101110612.RAA19541@lightning.itga.com.au> 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 hrmm, I tried that, same error (that was the first thing I tried actually) Ken ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 11 Jan 2001, Gregory Bond wrote: > > Jan 11 00:56:11 culverk /kernel: proc: table is full > > Jan 11 00:56:14 culverk last message repeated 1022 times > > This says you have run out of process slots in the kernel - running too many > jobs. Either run fewer processes (e.g. use "make -j4" rather than "make -j8") > or build a new kernel with a higher maxusers parameter. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 22:39:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 47B3837B401; Wed, 10 Jan 2001 22:39:26 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA25289; Thu, 11 Jan 2001 17:09:17 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 11 Jan 2001 17:09:17 +1030 (CST) From: "Daniel O'Connor" To: Kenneth Wayne Culver Subject: Re: wierd errors Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Gregory Bond Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Kenneth Wayne Culver wrote: > hrmm, I tried that, same error (that was the first thing I tried actually) Can't you just increase the kern.maxproc sysctl? --- 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 Wed Jan 10 22:56:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id AD4DA37B400; Wed, 10 Jan 2001 22:55:55 -0800 (PST) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id RAA28420; Thu, 11 Jan 2001 17:55:49 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id RAA22008; Thu, 11 Jan 2001 17:55:49 +1100 (EST) Message-Id: <200101110655.RAA22008@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: "Daniel O'Connor" Cc: Kenneth Wayne Culver , freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: wierd errors In-reply-to: Your message of Thu, 11 Jan 2001 17:09:17 +1030. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jan 2001 17:55:48 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can't you just increase the kern.maxproc sysctl? Nope, it's readonly, because various kernel internal hash tables are sized on it. See src/sys/kern/kern_{proc,resource,mib}.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 23: 5: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 0B03C37B401; Wed, 10 Jan 2001 23:04:49 -0800 (PST) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id SAA28488; Thu, 11 Jan 2001 18:04:47 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id SAA22366; Thu, 11 Jan 2001 18:04:47 +1100 (EST) Message-Id: <200101110704.SAA22366@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Kenneth Wayne Culver Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: wierd errors In-reply-to: Your message of Thu, 11 Jan 2001 01:35:55 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jan 2001 18:04:47 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hrmm, I tried that, same error (that was the first thing I tried actually) Hmm, it may be that the particular program you are building has some kind of error (in build scripts, or makefile, or whatever) that is causing an infinite loop somewhere. Examine the last N lines of output before the compile fails. Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 23: 5:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6F4B837B400 for ; Wed, 10 Jan 2001 23:05:16 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA25551; Thu, 11 Jan 2001 17:35:11 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101110655.RAA22008@lightning.itga.com.au> Date: Thu, 11 Jan 2001 17:35:11 +1030 (CST) From: "Daniel O'Connor" To: Gregory Bond Subject: Re: wierd errors Cc: freebsd-stable@FreeBSD.ORG, Kenneth Wayne Culver Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Gregory Bond wrote: > > Can't you just increase the kern.maxproc sysctl? > Nope, it's readonly, because various kernel internal hash tables are sized on > it. See src/sys/kern/kern_{proc,resource,mib}.c Hmm.. I thought that was changed a while back but I guess not. --- 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 Wed Jan 10 23: 8:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 1877537B400 for ; Wed, 10 Jan 2001 23:08:18 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Wed, 10 Jan 2001 23:06:29 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0B78CL85957; Wed, 10 Jan 2001 23:08:12 -0800 (PST) (envelope-from cjc) Date: Wed, 10 Jan 2001 23:08:12 -0800 From: "Crist J. Clark" To: "Robin P. Blanchard" Cc: Mike Harding , stable@FreeBSD.ORG Subject: Re: buildworld over nfs failing consistently Message-ID: <20010110230812.C989@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <3A5B87EE.8ACA0D05@gactr.uga.edu> <20010110141227.519C2E6A2D@netcom1.netcom.com> <3A5C85B0.4CB3C20D@gactr.uga.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A5C85B0.4CB3C20D@gactr.uga.edu>; from Robin_Blanchard@gactr.uga.edu on Wed, Jan 10, 2001 at 10:54:24AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 10, 2001 at 10:54:24AM -0500, Robin P. Blanchard wrote: [snip] Just to make sure, you have been completely nuking the messed up object tree on the client before these attempts, # chflags -R noschg /usr/obj/usr && rm -rf /usr/obj/usr Right? -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 10 23:20:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6E09C37B400 for ; Wed, 10 Jan 2001 23:20:13 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA25709; Thu, 11 Jan 2001 17:49:58 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010110230812.C989@rfx-64-6-211-149.users.reflexco> Date: Thu, 11 Jan 2001 17:49:58 +1030 (CST) From: "Daniel O'Connor" To: cjclark@alum.mit.edu Subject: Re: buildworld over nfs failing consistently Cc: stable@FreeBSD.ORG, Mike Harding , "Robin P. Blanchard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Crist J. Clark wrote: > Just to make sure, you have been completely nuking the messed up > object tree on the client before these attempts, > > # chflags -R noschg /usr/obj/usr && rm -rf /usr/obj/usr Yes, FYI rm -rf /usr/obj/usr ; chflags -R noschg /usr/obj/usr; rm -rf /usr/obj/usr is much faster. --- 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 Wed Jan 10 23:31:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 623A737B401; Wed, 10 Jan 2001 23:30:49 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Wed, 10 Jan 2001 23:29:02 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0B7Ujv86131; Wed, 10 Jan 2001 23:30:45 -0800 (PST) (envelope-from cjc) Date: Wed, 10 Jan 2001 23:30:45 -0800 From: "Crist J. Clark" To: stable@freebsd.org, current@freebsd.org Subject: sysinstall.8 Breaking buildworld Message-ID: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had some buildworld failures earlier this week. In src/share/man/man8 the Makefile includes code to get the sysinstall.8 manpage. Since the manpage lives in src/release, this requires that you CVSup src-release. I had not been. This broke buildworld which had worked in the past. sysinstall.8 is the only file in src-release that is required for a buildworld. It seems somewhat silly to me that you are required to grab the whole thing for that one file. I made the change to the Makefile which makes sysinstall.8 and src-release optional. I included it in a reply to the PR that precipitated the change, http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19818 Steven G. Kargl ealier, independently submitted the almost exact same thing, http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24122 In a separate PR. Anyone have a good reason why everyone _must_ have src-release to buildworld? -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 1:10:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id 0DCFC37B400 for ; Thu, 11 Jan 2001 01:09:52 -0800 (PST) Received: (qmail 28939 invoked by uid 1078); 11 Jan 2001 09:09:56 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 11 Jan 2001 09:09:56 -0000 Date: Thu, 11 Jan 2001 01:09:56 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: "David W. Chapman Jr." Cc: Subject: Re: /modules In-Reply-To: <001b01c07b8d$cec81c40$931576d8@inethouston.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 On Wed, 10 Jan 2001, David W. Chapman Jr. wrote: > is there a list that describes each of the modules in /modules? Not that I am aware of, but man usually works, otherwise, you need to look at the code. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 1:15:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id E41D037B404 for ; Thu, 11 Jan 2001 01:15:20 -0800 (PST) Received: (qmail 3941 invoked by uid 1078); 11 Jan 2001 09:15:30 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 11 Jan 2001 09:15:30 -0000 Date: Thu, 11 Jan 2001 01:15:30 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Javier Frias Cc: , Subject: Re: Central Source Updates In-Reply-To: <20010110220802.15712.qmail@staff.nyi.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 On Wed, 10 Jan 2001, Javier Frias wrote: > I'm wondering what everyone here is doing to do centralized source updates > on their server farms. Right now we've been doing it manually on each > server, but > now we are trying to come up with procedures to try to centralized the > situation a bit. > > I've come up with two basical startegies. > One central and one localized. > > 1) Central > Having one source repository server > and one compile/build server. [snip] > PROS: quick > CONS: donot get to test machines, i like make world since they are usually > good > at detecting hardware issues ( memory disk etc ) If these are server farms, the normal load they carry doesn't test the hardware enough? > 2) Localized > Having one source repository server > > the source repository would be just a basic freebsd mirror. > > machines would use cvs to update to a specify version date combination. > and build locally [snip] > SO, does anyone have any comments or pointers on how to better these > solutions > or which is better to use. I'm a big fan of a the single buildhost as our servers generally get enough of a workout as it is. I think that 'exercising' the disk just puts more miles on the device than anything else. Also, it's great for security since you can make a single set of md5 stamps for the all the binaries since all they are the same across all the machines. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 2:42:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [212.209.169.194]) by hub.freebsd.org (Postfix) with ESMTP id 8464337B402; Thu, 11 Jan 2001 02:42:24 -0800 (PST) Received: from palle.girgensohn.se (c193.150.249.140.cm-upc.chello.se [193.150.249.140]) by bastuba.partitur.se (8.9.3/8.9.3) with ESMTP id LAA69833; Thu, 11 Jan 2001 11:42:22 +0100 (CET) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by palle.girgensohn.se (8.11.1/8.11.1) with ESMTP id f0BAgKr13717; Thu, 11 Jan 2001 11:42:20 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <3A5D8E0B.C2D18B7D@partitur.se> Date: Thu, 11 Jan 2001 11:42:19 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: Mike Smith Cc: Kevin Way , freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org, henrik@partitur.se Subject: Re: ida driver - Compaq Smart Array 431 - 4.2-RELEASE References: <200012261414.eBQEENj85964@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have exactly the same problem here. Any progress? Regards, Palle Mike Smith wrote: > > > I'm attempting to install FreeBSD 4.2-RELEASE on a Compaq ML370 with a > > Compaq Smart Array 431 controller. > > We've seen a number of problems with these new Compaq machines, mostly > due to PCI resource assignments not being completed correctly. To start > with, the output of the PCI probe for the controller would be useful, as > it'd let us work out whether this is actually the problem. > > > What should I do next, to help get this problem fixed? I'll gladly > > provide any output that anybody would like. Seeing as FBSD isn't actually > > installed on the machine yet, I'm not sure how to best proceed. > > You might want to try moving the controller into a different slot; I've > seen this help in at least one occasion on this family of machines. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 2:51:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from orbix.mobilix.dk (orbix.mobilix.dk [212.97.216.244]) by hub.freebsd.org (Postfix) with ESMTP id 6B2B037B401 for ; Thu, 11 Jan 2001 02:50:59 -0800 (PST) Received: from ms04.mobilix.dk (ms04.mobilix.dk [172.16.1.24]) by orbix.mobilix.dk (8.11.0/8.11.0) with SMTP id f0BAopP23055 for ; Thu, 11 Jan 2001 11:50:52 +0100 Received: FROM ms07.mobilix.dk BY ms04.mobilix.dk ; Thu Jan 11 11:50:50 2001 +0100 Received: by ms07.mobilix.dk with Internet Mail Service (5.5.2650.21) id ; Thu, 11 Jan 2001 11:50:49 +0100 Message-ID: <2D3005375CAED31199D00008C784963F01C55561@ms02.mobilix.dk> From: Morten Vinding Nielsen To: "'satherrl@gryphon.itssa.curtin.edu.au'" , freebsd-stable@FreeBSD.ORG Subject: RE: Intel PRO/100+ driver or hardware? Date: Thu, 11 Jan 2001 11:50:46 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What MAC address is the driver reading from the cards? I have seen some Compaq branded Intel pro 100 cards getting there MAC address read incorrectly! Make sure the MAC from ifconfig is the same as the one printed on the board it self. Morten Vinding Nielsen INM Maintenance Mobilix A/S Denmark -----Original Message----- From: Richard Sather [mailto:satherrl@gryphon.itssa.curtin.edu.au] Sent: 10. januar 2001 11:03 To: freebsd-stable@FreeBSD.ORG Subject: RE: Intel PRO/100+ driver or hardware? Quoting Ian Cartwright : > A few weeks back I mentioned a similar problem I was having with a Compaq > Dexkpro EN. It has a built in 82559 chip. Under FreeBSD it would hang every > so often with a device timeout. Under Win2k it works great. I tried > everything I could think of (swapping cables, hubs, etc.) with no success > for FreeBSD. I tried the mailing lists but no one saw my post I guess. ;-/ ok - I have 12 CompaQ EN's sitting next to me aswell. Exactly the same timeout problem. 3.5.1-RELEASE also refuses to acknowledge their existence. We have tried a netgear 10Base hub at autonegotiate and fixed at 10Mbps aswell as through a Netgear FS 116 16 port switch with the same effect. We tried locking the card at 100Mbps which 'seemed' to cure the problem but our solution for the time being has been to use Pro 100/10B's. Regards Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 3:23: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 089BC37B401 for ; Thu, 11 Jan 2001 03:22:44 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id hxosaaaa for ; Thu, 11 Jan 2001 22:31:14 +1100 Message-ID: <3A5D979F.B8BF66BB@quake.com.au> Date: Thu, 11 Jan 2001 22:23:11 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? References: <2D3005375CAED31199D00008C784963F01C55561@ms02.mobilix.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morten Vinding Nielsen wrote: > > What MAC address is the driver reading from the cards? > > I have seen some Compaq branded Intel pro 100 cards getting there MAC > address read incorrectly! I have seen the same thing, its hard to tell what is going on at first since bizarre problems with no apparent cause appear... Windows usually gets it right and the problems arnt there, you should notice ARP messages about IP address changing MAC's if you boot one then the other... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 3:28: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id CF47C37B404 for ; Thu, 11 Jan 2001 03:27:49 -0800 (PST) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.20 #1) id 14GftO-0004lE-00; Thu, 11 Jan 2001 11:27:42 +0000 To: jwpauler@jwpages.com, tom@uniserve.com Subject: Re: Next release Cc: freebsd-stable@freebsd.org In-Reply-To: Message-Id: From: Pete French Date: Thu, 11 Jan 2001 11:27:42 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To anyone using cvsup, releases are growing increasingly meaningless. O.K., I am slightly confused here - I thought that tracking 4.2 stable just gives me bug fixes to 4.2, yet I am starting to get the impression that if I continue cvsupping regularly I will actually end up with 4.3 by the time it is released ? I was under the impression that tracking -stable did not attempt to add any new features, but instead simplt added bug fixes to the last release... Anybody point me in the direction of a concise explanation at all ? -bat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 3:38:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 1711D37B402 for ; Thu, 11 Jan 2001 03:38:23 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA04176; Thu, 11 Jan 2001 12:38:16 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Pete French Cc: jwpauler@jwpages.com, tom@uniserve.com, freebsd-stable@FreeBSD.ORG Subject: Re: Next release References: From: Dag-Erling Smorgrav Date: 11 Jan 2001 12:38:16 +0100 In-Reply-To: Pete French's message of "Thu, 11 Jan 2001 11:27:42 +0000" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete French writes: > O.K., I am slightly confused here - I thought that tracking 4.2 stable > just gives me bug fixes to 4.2, yet I am starting to get the impression that > if I continue cvsupping regularly I will actually end up with 4.3 by the > time it is released ? Releases are points along the -STABLE branch. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 5: 3:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 654B537B402; Thu, 11 Jan 2001 05:02:50 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA08273; Thu, 11 Jan 2001 08:02:37 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id IAA06793; Thu, 11 Jan 2001 08:02:37 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA06789; Thu, 11 Jan 2001 08:02:37 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Thu, 11 Jan 2001 08:02:37 -0500 (EST) From: Kenneth Wayne Culver To: "Daniel O'Connor" Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Gregory Bond Subject: Re: wierd errors 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 Well, I was also having wierd panics, this will seem unrelated, but I think I fixed it by upping the io voltage in the BIOS ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 11 Jan 2001, Daniel O'Connor wrote: > > On 11-Jan-01 Kenneth Wayne Culver wrote: > > hrmm, I tried that, same error (that was the first thing I tried actually) > > Can't you just increase the kern.maxproc sysctl? > > --- > 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 Jan 11 5: 3:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 1825D37B401; Thu, 11 Jan 2001 05:03:09 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA08278; Thu, 11 Jan 2001 08:03:04 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id IAA06861; Thu, 11 Jan 2001 08:03:04 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA06856; Thu, 11 Jan 2001 08:03:03 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Thu, 11 Jan 2001 08:03:03 -0500 (EST) From: Kenneth Wayne Culver To: Gregory Bond Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: wierd errors In-Reply-To: <200101110704.SAA22366@lightning.itga.com.au> 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 Will do. :-) ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 11 Jan 2001, Gregory Bond wrote: > > hrmm, I tried that, same error (that was the first thing I tried actually) > > Hmm, it may be that the particular program you are building has some kind of > error (in build scripts, or makefile, or whatever) that is causing an infinite > loop somewhere. Examine the last N lines of output before the compile fails. > > Greg. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 5: 5:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from net2.dinoex.sub.org (net2.dinoex.de [212.184.201.182]) by hub.freebsd.org (Postfix) with ESMTP id AC8FD37B402 for ; Thu, 11 Jan 2001 05:05:29 -0800 (PST) Received: from gate.dinoex.sub.org (dinoex@localhost) by net2.dinoex.sub.org (8.11.2/8.11.2) with BSMTP id f0BD54S15927 for ; Thu, 11 Jan 2001 14:05:04 +0100 (CET) (envelope-from dirk.meyer@dinoex.sub.org) X-MDaemon-Deliver-To: To: freebsd-stable@FreeBSD.ORG Message-ID: From: dirk.meyer@dinoex.sub.org (Dirk Meyer) Organization: privat Subject: Re: Cleaning out old/unused files after make world Date: Thu, 11 Jan 2001 13:59:21 +0100 X-Mailer: Dinoex 1.76 References: <20010110211121.W79365@strontium.scientia.demon.co.uk> X-Gateway: ZCONNECT gate.dinoex.sub.org [UNIX/Connect 0.90] X-Accept-Language: de,en X-PGP-Fingerprint: 44 16 EC 0A D3 3A 4F 28 8A 8A 47 93 F1 CF 2F 12 X-Noad: Please don't send me ad's by mail. I'm bored by this type of mail. X-Copyright: (C) Copyright 1999 by Dirk Meyer -- All rights reserved. X-Note: sending SPAM is a violation of both german and US law and will at least trigger a complaint at your provider's postmaster. X-PGP-Key-Avail: mailto:pgp-public-keys@keys.de.pgp.net Subject:GET 0x331CDA5D X-ZC-VIA: 20010111000000W+1@dinoex.sub.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > Start with find(1)'s -mtime option, removing files older than your > last buildworld in appropriate directories. Where `appropriate > directories' are those completely updated by buildworld (i.e. NOT /etc, > /usr/local, and so on). Mainly I'd go for /bin /sbin /usr/bin /usr/sbin > /usr/libexec /usr/share /usr/libdata. Also, I wouldn't remove old > libraries from /usr/lib since stuff in /usr/local might still be using > them. And be careful what you delete, of course. :-) It made sense to me to move all older libs and their corresponding sylinks into the compat directory. Then use ldconfig to amke teh system aware of the new location. benefits: - libpath ist clean - old ports can still access the lib - news builds will find the right libs, configure of a port might otherwise prefer to use an old lib. once you updated all your ports, its safe to clean the old libs. kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 5:39:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from orbix.mobilix.dk (orbix.mobilix.dk [212.97.216.244]) by hub.freebsd.org (Postfix) with ESMTP id 1A54137B402 for ; Thu, 11 Jan 2001 05:38:44 -0800 (PST) Received: from ms04.mobilix.dk (ms04.mobilix.dk [172.16.1.24]) by orbix.mobilix.dk (8.11.0/8.11.0) with SMTP id f0BDcgP30551 for ; Thu, 11 Jan 2001 14:38:42 +0100 Received: FROM ms07.mobilix.dk BY ms04.mobilix.dk ; Thu Jan 11 14:38:44 2001 +0100 Received: by ms07.mobilix.dk with Internet Mail Service (5.5.2650.21) id ; Thu, 11 Jan 2001 14:38:43 +0100 Message-ID: <2D3005375CAED31199D00008C784963F01C5556A@ms02.mobilix.dk> From: Morten Vinding Nielsen To: "'Kal Torak'" Cc: freebsd-stable@FreeBSD.ORG Subject: RE: Intel PRO/100+ driver or hardware? Date: Thu, 11 Jan 2001 14:38:40 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't noticed any ARP messages. Don't you mean MAC changing IP address since more than one card have the same MAC? Yes Windowz and Linux reads the MAC correctly. I have heard of others having the same problem, but getting a MAC address that differs from mine by a single digit, so I think it might be that the driver is reading the revision number of the card or something. /Morten -----Original Message----- From: Kal Torak [mailto:kaltorak@quake.com.au] Sent: 11. januar 2001 12:23 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? Morten Vinding Nielsen wrote: > > What MAC address is the driver reading from the cards? > > I have seen some Compaq branded Intel pro 100 cards getting there MAC > address read incorrectly! I have seen the same thing, its hard to tell what is going on at first since bizarre problems with no apparent cause appear... Windows usually gets it right and the problems arnt there, you should notice ARP messages about IP address changing MAC's if you boot one then the other... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 6:25:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id C868C37B400 for ; Thu, 11 Jan 2001 06:25:34 -0800 (PST) Received: from netcom1.netcom.com (user-2inis2d.dialup.mindspring.com [165.121.112.77]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id JAA25197; Thu, 11 Jan 2001 09:25:20 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 9D69EE6B8B; Thu, 11 Jan 2001 06:25:17 -0800 (PST) From: Mike Harding To: doconnor@gsoft.com.au Cc: cjclark@alum.mit.edu, stable@FreeBSD.ORG, Robin_Blanchard@gactr.uga.edu In-reply-to: Subject: Re: buildworld over nfs failing consistently References: Message-Id: <20010111142517.9D69EE6B8B@netcom1.netcom.com> Date: Thu, 11 Jan 2001 06:25:17 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the 4 tree, at least, you haven't had to do the 'chflags' bit for a while. I usually do a # cd /usr # mv obj oobj # rm -rf oobj & # cd /usr/src # make -DNOCLEAN buildworld |& tee buildresults | tail | mail mvh & so I can get out of the way in 30 or so seconds, and I get mail when it's done. I also have a log of the build which is useful if it fails - 'tail' doesn't generally go far back enough, though of course that is configurable. - Mike H. X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jan 2001 17:49:58 +1030 (CST) From: "Daniel O'Connor" Cc: stable@FreeBSD.ORG, Mike Harding , "Robin P. Blanchard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk On 11-Jan-01 Crist J. Clark wrote: > Just to make sure, you have been completely nuking the messed up > object tree on the client before these attempts, > > # chflags -R noschg /usr/obj/usr && rm -rf /usr/obj/usr Yes, FYI rm -rf /usr/obj/usr ; chflags -R noschg /usr/obj/usr; rm -rf /usr/obj/usr is much faster. --- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 6:51:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.sunflower.com (smtp.sunflower.com [24.124.0.137]) by hub.freebsd.org (Postfix) with ESMTP id 37D8137B400 for ; Thu, 11 Jan 2001 06:50:57 -0800 (PST) Received: from [192.168.28.134] (dv13m7.lawrence.ks.us [24.124.7.65]) by smtp.sunflower.com (8.9.3/8.9.3) with ESMTP id IAA30458 for ; Thu, 11 Jan 2001 08:50:00 -0600 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Thu, 11 Jan 2001 08:47:45 -0600 Subject: problems with build world From: Chris Jeter To: Message-ID: 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 been having problems with make buildworld finishing. following is output from the make. [snip] building standard pam_ssh library ranlib libpam_ssh.a cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/log-client.c -o log-client.So cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_s sh.c -o pam_ssh.So make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libcrypto.a. Stop *** Error code 2 Stop in /usr/src/lib/libpam/modules. *** Error code 1 Stop in /usr/src/lib/libpam. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. outcast# exit exit Script done on Wed Jan 10 16:17:05 2001 [end] output from uname FreeBSD outcast.sunflower.com 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC i386 I've looked over http://www.freebsd.org/handbook/makeworld.html and followed the directions there. I've also read over /usr/src/UPDATING. Also have removed /usr/src and /usr/obj and resup'd, the build dies at the same point. and help with this would be great. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 7:46: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from changeofhabit.mr.itd.umich.edu (changeofhabit.mr.itd.umich.edu [141.211.144.17]) by hub.freebsd.org (Postfix) with ESMTP id CA79237B400 for ; Thu, 11 Jan 2001 07:45:44 -0800 (PST) Received: from tim.elnsng1.mi.home.com (c1129767-a.elnsng1.mi.home.com [24.183.248.20]) by changeofhabit.mr.itd.umich.edu (8.9.3/3.2r) with SMTP id KAA17849; Thu, 11 Jan 2001 10:45:24 -0500 (EST) From: Tim McMillen To: Pete French , jwpauler@jwpages.com, tom@uniserve.com Subject: Re: Next release Date: Thu, 11 Jan 2001 10:49:35 -0500 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" Cc: freebsd-stable@FreeBSD.ORG References: In-Reply-To: MIME-Version: 1.0 Message-Id: <0101111049350E.00498@tim.elnsng1.mi.home.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday January 11, 2001 06:27, Pete French wrote: > > To anyone using cvsup, releases are growing increasingly > > meaningless. > > O.K., I am slightly confused here - I thought that tracking 4.2 > stable just gives me bug fixes to 4.2, I personally would like something like that, but that is not how it works. > yet I am starting to get the > impression that if I continue cvsupping regularly I will actually end > up with 4.3 by the time it is released ? Yes, the stable branch is continuously improved with bug fixes and new features. Every four months (now that I know that number :) or so a release is made from from the stable branch. > I was under the impression > that tracking -stable did not attempt to add any new features, but > instead simplt added bug fixes to the last release... > > Anybody point me in the direction of a concise explanation at all ? Chapter 19 of the handbook gives it. But section 19.2.2.2 seems to imply it is just a bug fix branch, but since new features sometimes bring bugs, that would seem misleading to me. Anyone more enlightened care to shed light on that? Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 9: 8:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apotheosis.org.za (apotheosis.org.za [137.158.128.27]) by hub.freebsd.org (Postfix) with ESMTP id B22AC37B401 for ; Thu, 11 Jan 2001 09:08:40 -0800 (PST) Date: Thu, 11 Jan 2001 19:08:08 +0200 From: Matthew West To: David Malone Cc: Ian Dowse , stable@freebsd.org Subject: Re: page faults on FreeBSD 4.2-STABLE Message-ID: <20010111190808.A86850@apotheosis.org.za> References: <20010108140521.A23828@apotheosis.org.za> <200101081256.aa88963@salmon.maths.tcd.ie> <20010108222316.A10341@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010108222316.A10341@walton.maths.tcd.ie>; from "David Malone" on Mon, Jan 08, 2001 at 10:23:16PM Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After applying your patch taken from -CURRENT, my 4.2-STABLE machine has been up for the past two days. http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/kern/sys_pipe.c.diff?r1=1.67&r2=1.68 Many thanks! -- mwest@uct.ac.za On Mon, Jan 08, 2001 at 10:23:16PM +0000, David Malone wrote: > On Mon, Jan 08, 2001 at 12:56:51PM +0000, Ian Dowse wrote: > > I've seen a similar trace on a machine here, but I haven't had a chance > > to analyse it properly yet. The source is from Dec 18: > > Ian and I tracked this down today, I've just committed a patch to > -current. I'll merge it in a couple of days. > > David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 9:26:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mindcrime.bit0.com (mindcrime.bit0.com [216.7.69.69]) by hub.freebsd.org (Postfix) with ESMTP id BCF4837B401 for ; Thu, 11 Jan 2001 09:26:10 -0800 (PST) Received: from localhost (mandrews@localhost) by mindcrime.bit0.com (8.11.1/8.11.1) with ESMTP id f0BHLpO23718 for ; Thu, 11 Jan 2001 12:21:51 -0500 (EST) (envelope-from mandrews@bit0.com) Date: Thu, 11 Jan 2001 12:21:51 -0500 (EST) From: Mike Andrews To: stable@freebsd.org Subject: Weird sporadic DNS resolution problems 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'm having a bizarre DNS resolution problem that I'm having a hell of a time tracking down. Someone tell me I'm just being stupid. :) For a few months now, I'm *sporadically* unable to resolve *some* external domains. This started happening approximately between 4.1.1-RELEASE and 4.2-RELEASE, when I believe Bind 8 was upgraded in the source tree. (I don't remember the exact date, sorry) Here's what appears to be going on: When one (but not both) of the nameservers for a domain replies non-authoritatively, named will cache a negative response, rather than asking the other nameserver. Subsequent lookups return an immediate failure. Restarting the nameserver, and then immediately querying the same problematic domain DOES work, but only the first query. After a few minutes/hours the domain stops working again. This is especially chronic because Sendmail tries to resolve domains on incoming email (for spam protection purposes)... it will give "Domain of sender address foo@bar does not resolve" and return a 451 code. This causes the other end to retry periodically, unless the other end is something like Outlook Express, in which case the customer calls me and complains. :) One example domain is "farmersfrankfort.com". This was moved from us to another site yesterday, but we still do MX for them. Looking at whois and at the root servers, you can see that their two new nameservers are now "cerberus.sbscorp.com" and "ns1.qwest.net". Querying the sbscorp server works great, querying qwest doesn't -- it appears Quest never added them to their nameserver config at all. (It has been only about 24 hours, so it's not *too* surprising I guess...) Anyway, when someone on one of our dialups tries to send mail with @farmersfrankfort.com on the end, our Sendmail is unable to resolve it and rejects the message. If I restart (not reload) named, it will start working for a while, then die on its own again. My theory is that if it happens to query sbscorp it's happy, if it happens to query qwest it isn't, and caches the fact that it isn't. Another example is "setel.com" and "se-tel.com". We sometimes have problems exchanging mail with them because one of their DNS servers appears to be answering non-authoritatively. Again, I can flush my backlog by restarting named and immediately running the sendmail queue manually (and I could probably flush their backlog by telnetting to their SMTP port and issuing an ETRN)... but obviously that's not exactly elegant :) I've tried adding "max-ncache-ttl 1" to my named config, hoping it would help. It didn't. In one sense this is "not my problem" because their name server shouldn't be answering non-authoritatively in the first place. But the fact that this started happening after a make world a few months ago, and that I feel it should be a slight bit more tolerant of other people's sloppy configurations, makes it my problem. Anyone have any ideas as to what's going on, or can tell me what debugging output to enable that I could send here that would help figure it out? Configuration options to named that would revert to older behavior? A whack on the head? (I could just compile an older named I guess, but I fear opening up security holes/DoS attacks.) Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet access for Frankfort, Lexington, Louisville and surrounding counties www.fark.com: If it's not news, it's Fark. (Or something like that.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 9:28:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id 2764537B401 for ; Thu, 11 Jan 2001 09:28:33 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id RAA57764 for freebsd-stable@freebsd.org; Thu, 11 Jan 2001 17:28:31 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101111728.RAA57764@ns.a1.org.uk> Subject: Re: Next release In-Reply-To: <0101111049350E.00498@tim.elnsng1.mi.home.com> from Tim McMillen at "Jan 11, 2001 10:49:35 am" To: freebsd-stable@freebsd.org Date: Thu, 11 Jan 2001 17:28:31 +0000 (GMT) Reply-To: freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (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 > > > I was under the impression > > that tracking -stable did not attempt to add any new features, but > > instead simplt added bug fixes to the last release... > > > > Anybody point me in the direction of a concise explanation at all ? > > Chapter 19 of the handbook gives it. But section 19.2.2.2 seems to > imply it is just a bug fix branch, but since new features sometimes > bring bugs, that would seem misleading to me. Anyone more enlightened > care to shed light on that? > New features are added to current where they are tested, and when are stable, merged from current into stable. Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 9:30:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id 8EE5137B401; Thu, 11 Jan 2001 09:29:47 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id JAA23289; Thu, 11 Jan 2001 09:29:49 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f0BHTji13857; Thu, 11 Jan 2001 09:29:45 -0800 (PST) (envelope-from bmah) Message-Id: <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2+ 01/03/2001 with nmh-1.0.4 To: cjclark@alum.mit.edu Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> References: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> Comments: In-reply-to "Crist J. Clark" message dated "Wed, 10 Jan 2001 23:30:45 -0800." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-203044208P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 11 Jan 2001 09:29:45 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-203044208P Content-Type: text/plain; charset=us-ascii If memory serves me right, "Crist J. Clark" wrote: > I had some buildworld failures earlier this week. In > src/share/man/man8 the Makefile includes code to get the sysinstall.8 > manpage. Since the manpage lives in src/release, this requires that > you CVSup src-release. I had not been. This broke buildworld which had > worked in the past. sysinstall.8 is the only file in src-release that > is required for a buildworld. It seems somewhat silly to me that you > are required to grab the whole thing for that one file. OK...I was one of the people who (indirectly) pushed for this. In a nutshell, I (and, independently, several other people) noticed that the sysinstall(8) manpage never gets installed as a part of the binary distributions or by an installworld. (I got highly confused by this while rewriting some other parts of the documentation.) The solution was to make sure that an installworld installs this manpage. > I made the change to the Makefile which makes sysinstall.8 and > src-release optional. I included it in a reply to the PR that > precipitated the change, > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19818 My personal opinion is that sysinstall.8 is a part of the base system and shouldn't be optional. If we take your suggestion, it means that installworld will sometimes install this manpage and sometimes it won't. A good counter-argument is that installworld doesn't touch /stand/sysinstall, and therefore shouldn't touch the manpage either. Idea: Maybe we need the release building process to do this instead? On all of my systems, the sysinstall binary came from a CD, and never got touched by any subsequent installworlds. > Anyone have a good reason why everyone _must_ have src-release to > buildworld? I never thought of trying to do a buildworld with anything less than src-all. I guess my counter question is: Anyone have a good reason to do buildworlds *without* /usr/src/release/? Bruce. --==_Exmh_-203044208P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6Xe2I2MoxcVugUsMRAi18AKDolT60SbJn+cmj+lw71PGWPBi47QCeMr+N 7oMXfcOVHa+sieC+tNY2cVw= =Pi8x -----END PGP SIGNATURE----- --==_Exmh_-203044208P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 9:35:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 26AF537B401 for ; Thu, 11 Jan 2001 09:35:15 -0800 (PST) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 14Gld2-000Mrb-00; Thu, 11 Jan 2001 09:35:12 -0800 Date: Thu, 11 Jan 2001 09:35:10 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mike Andrews Cc: stable@freebsd.org Subject: Re: Weird sporadic DNS resolution problems 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 Thu, 11 Jan 2001, Mike Andrews wrote: > When one (but not both) of the nameservers for a domain replies > non-authoritatively, named will cache a negative response, rather than > asking the other nameserver. Subsequent lookups return an immediate That is the way it is supposed to work. If there is a negative response (NXDOMAIN), the domain you are asking for does not exist. Servers need to send a referral, or just not answer at all, if you want your DNS server to check other servers. There are so many screwed DNS servers on the internet these days. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 9:41:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id D088B37B402; Thu, 11 Jan 2001 09:41:07 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0BHeEi18459; Thu, 11 Jan 2001 09:40:14 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: bmah@FreeBSD.ORG Cc: cjclark@alum.mit.edu, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: Message from "Bruce A. Mah" of "Thu, 11 Jan 2001 09:29:45 PST." <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com> Date: Thu, 11 Jan 2001 09:40:14 -0800 Message-ID: <18455.979234814@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My personal opinion is that sysinstall.8 is a part of the base system > and shouldn't be optional. If we take your suggestion, it means that > installworld will sometimes install this manpage and sometimes it won't. I think we should simply move the stupid man page into man8. It's a bit weird to have a man page and its utility live in seperate places, but the release/ directory in the hierarchy has always been a red-headed stepchild in any case. If I had it to do over, it would have all gone into /usr/src/sbin somewhere. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 9:51:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by hub.freebsd.org (Postfix) with ESMTP id EC01C37B400; Thu, 11 Jan 2001 09:51:18 -0800 (PST) Received: from localhost (marck@localhost) by woozle.rinet.ru (8.11.1/8.11.0) with ESMTP id f0BHpFR02360; Thu, 11 Jan 2001 20:51:16 +0300 (MSK) (envelope-from marck@rinet.ru) X-Authentication-Warning: woozle.rinet.ru: marck owned process doing -bs Date: Thu, 11 Jan 2001 20:51:15 +0300 (MSK) From: Dmitry Morozovsky To: sheldonh@freebsd.org Cc: stable@freebsd.org Subject: /etc/rc mounting NFS bug Message-ID: X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there, I found small bug (actually, just cosmetic) in NFS mounting in /etc/rc (at least in 4-stable branch). If you mount tree of NFSes, then call to `mount -d' in # Mount NFS filesystems if present in /etc/fstab case "`mount -d -a -t nfs`" in *mount_nfs*) echo -n "Mounting NFS file systems" mount -a -t nfs echo . ;; esac leads to nasty error message like mount: /pub/.1: No such file or directory (my NFS mounts are kucha:/ar/pub /pub nfs ro,tcp,soft,bg,intr 0 0 kucha:/ar/pub/.1 /pub/.1 nfs ro,tcp,soft,bg,intr 0 0 kucha:/ar/pub/.2 /pub/.2 nfs ro,tcp,soft,bg,intr 0 0 ) There are some ways to fix this; however, the simplest would be --- rc.orig Tue Sep 26 04:04:27 2000 +++ rc Thu Jan 11 20:49:35 2001 @@ -223,7 +223,7 @@ esac # Mount NFS filesystems if present in /etc/fstab -case "`mount -d -a -t nfs`" in +case "`mount -d -a -t nfs 2> /dev/null`" in *mount_nfs*) echo -n "Mounting NFS file systems" mount -a -t nfs --- because at lease top mounting point directory must exist for successive mounts ;-) Thanks for your attention; please let me know if I miss something vital :) Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 10: 1:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 10CEA37B404; Thu, 11 Jan 2001 10:00:53 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.20 #1) id 14GjSB-0003gU-00; Thu, 11 Jan 2001 15:15:51 +0000 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.1/8.11.1) id f0BFFoA81809; Thu, 11 Jan 2001 15:15:50 GMT (envelope-from ben) Date: Thu, 11 Jan 2001 15:15:50 +0000 From: Ben Smithurst To: stable@freebsd.org, current@freebsd.org Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111151549.Z79365@strontium.scientia.demon.co.uk> References: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Crist J. Clark wrote: > Anyone have a good reason why everyone _must_ have src-release to > buildworld? No. Sorry. I kind of assumed people doing buildworlds would just get src-all. Pointy hat this way please... As I said in a reply to a private mail to Crist, I'll commit a fix for this tonight and MFC it soon. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 10:16:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id EDFC137B401; Thu, 11 Jan 2001 10:16:25 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14GmFH-000AHT-00; Thu, 11 Jan 2001 21:14:45 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14GmGr-000PMy-00; Thu, 11 Jan 2001 21:16:21 +0300 Date: Thu, 11 Jan 2001 21:16:21 +0300 From: Odhiambo Washington To: FBSD-STABLE Cc: FBSD-Q Subject: 3.X --> 4.X - buildworld fails Message-ID: <20010111211621.A97461@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , FBSD-STABLE , FBSD-Q Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This one is for the gurus: I am updating a 3.5-S system to 4.X. I've done cvsup with RELENG_4 yesterday. Now while strictly following the update procedure in UPDATING (and referring to the text from the handbook, I get a failure while doing make buildworld, viz cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/us r/obj/usr/src/gnu/usr.bin/perl/miniperl -c opmini.c cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/us r/obj/usr/src/gnu/usr.bin/perl/miniperl -L/usr/obj/usr/src/gnu/usr.bin/perl/m iniperl/../libperl -static -o miniperl miniperlmain.o opmini.o /usr/obj/usr/src /gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): In fu nction `Perl_pp_aassign': pp_hot.o(.text+0x16a1): undefined reference to `setresuid' pp_hot.o(.text+0x16d4): undefined reference to `setresgid' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. I am not sure what this means ;-) but I've replicated it by going into /usr/src/gnu/usr.bin/perl and doing a 'make' in there. I highly appreciate all help that will get me past this one. TIA -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Presumably, we're all fully qualified computer nerds here, so we are allowed to use "access" as a verb. Be advised, however, that the practice in common usage drives English-language purists to scowling fidgets. -Erik Strom, "Perl CGI Programming" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 10:17:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from menzor.org (menzor.org [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id 69DA337B69C; Thu, 11 Jan 2001 10:16:53 -0800 (PST) Received: from sos (userhost.mdes.dk [130.228.127.200]) by menzor.org (8.8.8/8.8.8) with SMTP id TAA06051; Thu, 11 Jan 2001 19:26:56 +0100 (CET) (envelope-from morten@seeberg.dk) Message-ID: <002f01c07bfa$e6e917d0$c8280c0a@sos> From: "Morten Seeberg" To: "Bob Purdon" Cc: , References: Subject: Re: Compaq RAID? Date: Thu, 11 Jan 2001 19:18:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI for the mailinglists I havenґt had time or the oppotunity to test the new models, but I do know that Compaq will not support newer controllers for FreeBSD (or Linux at the moment). They talked about supporting their controllers in other kinds of hardware than Compaq, but that never happened (and probably never will now), so you actually need an NT partition on your server or a Compaq server (and the use the SmartStart CD) :( ----- Original Message ----- From: "Bob Purdon" To: Sent: Thursday, January 11, 2001 11:59 AM Subject: Compaq RAID? > > Hi, > > Been checking out your IDA RAID web pages and was hoping you might have > some useful information... > > I have a Compaq SMART Array 3200 controller (the dual channel unit), but > can't find any software to configure the actual arrays. The software your > site links to (the Softpaq - the one that extracts a copy of Win > 3.11 and runs in that) doesn't detect the card. > > The BIOS detects the card, and it runs it's power up diagnostics fine - > it's just the Compaq software that can't find it. > > I've tried downloading their newer ADU utility, but it only runs on NT or > Win-2000, and installing either of those just so I can configure an array > to install BSD on seems just a little drastic. > > Do you have any ideas I could try? > > Cheers, > > Bob. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 10:27:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 4FDB037B401 for ; Thu, 11 Jan 2001 10:27:31 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id BE75A177EF1; Thu, 11 Jan 2001 12:27:30 -0600 (CST) Message-ID: <00b801c07bfc$27284720$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Gordon Tetlow" Cc: References: Subject: Re: /modules Date: Thu, 11 Jan 2001 12:27:28 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG that worked for most of them, but one that I'm not sure about is atapi.ko I have a basic idea, but and not sure, is it for ide burners? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 10:30:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 70B5137B404 for ; Thu, 11 Jan 2001 10:30:06 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 169EC1360C; Thu, 11 Jan 2001 13:30:22 -0500 (EST) Date: Thu, 11 Jan 2001 13:30:21 -0500 From: Chris Faulhaber To: "David W. Chapman Jr." Cc: Gordon Tetlow , freebsd-stable@FreeBSD.ORG Subject: Re: /modules Message-ID: <20010111133021.B12629@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , "David W. Chapman Jr." , Gordon Tetlow , freebsd-stable@FreeBSD.ORG References: <00b801c07bfc$27284720$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00b801c07bfc$27284720$931576d8@inethouston.net>; from dwcjr@inethouston.net on Thu, Jan 11, 2001 at 12:27:28PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 12:27:28PM -0600, David W. Chapman Jr. wrote: > that worked for most of them, but one that I'm not sure about is > > atapi.ko > > I have a basic idea, but and not sure, is it for ide burners? > $ man -k atapi ata(4), acd(4), ad(4), afd(4), ast(4) - Generic ATA/ATAPI disk controller driver burncd(8) - control the ATAPI CD-R/RW driver wfd(4) - ATAPI floppy driver (LS-120 floppy driver) wst(4) - ATAPI Tape drive -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - 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 Thu Jan 11 10:50:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay.uclm.es (relay.uclm.es [161.67.124.26]) by hub.freebsd.org (Postfix) with ESMTP id 0093137B69E for ; Thu, 11 Jan 2001 10:50:24 -0800 (PST) Received: from europa.cc-cr.uclm.es (unknown [161.67.40.12]) by relay.uclm.es (Postfix) with ESMTP id 669B698B54 for ; Thu, 11 Jan 2001 19:50:21 +0100 (CET) Received: from est252.ind-cr.uclm.es (mail@est252.ind-cr.uclm.es [161.67.37.252]) by europa.cc-cr.uclm.es (8.9.3/UCLM.CReal) with ESMTP id TAA00486 for ; Thu, 11 Jan 2001 19:50:21 +0100 Received: from jjgarcia by est252.ind-cr.uclm.es with local (Exim 3.12 #1 (Debian)) id 14Gmnk-0000NE-00 for ; Thu, 11 Jan 2001 19:50:20 +0100 To: stable@freebsd.org Subject: Wierd rsync + ssh problems From: jjgarcia@ind-cr.uclm.es (Juan=?iso-8859-1?q?_Jos=E9_Garc=EDa?= Ripoll) Date: 11 Jan 2001 19:50:20 +0100 In-Reply-To: Dmitry Morozovsky's message of "Thu, 11 Jan 2001 20:51:15 +0300 (MSK)" Message-ID: <87zogxsz2r.fsf@est252.ind-cr.uclm.es> Lines: 31 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am experiencing random problems when using rsync over ssh. The problem is happens with this software when connecting two FreeBSD boxes or a FreeBSD box with a linux one. It happens with random files at random instants and the symptom is always rsync getting idle waiting for data. The problem disappears just by using "rsh" instead of "ssh" but this is definitively not what I would like to do. TIA Juanjo -------software versions below------- % ssh -V SSH Version OpenSSH_2.2.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). % rsync --version rsync version 2.4.1 protocol version 24 Written by Andrew Tridgell and Paul Mackerras % uname -a FreeBSD specia 4.2-STABLE FreeBSD 4.2-STABLE #0: Sun Dec 24 10:14:27 CET 2000 root@ripoll1:/usr/obj/usr/src/sys/LAPTOP i386 -- Juan Jose Garcia Ripoll www: http://matematicas.uclm.es/~jjgarcia/ Dpto. de Matematicas job: jjgarcia@ind-cr.uclm.es E.T.S.I. Industriales home: worm@arrakis.es Univ. de Castilla-La Mancha, Ciudad Real E-13071 (Spain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 10:54: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 78DDA37B401; Thu, 11 Jan 2001 10:53:38 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BIrI110455; Thu, 11 Jan 2001 10:53:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.4.0.FreeBSD:010111105204:458=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com> Date: Thu, 11 Jan 2001 10:53:43 -0800 (PST) From: John Baldwin To: "Bruce A. Mah" , jkh@FreeBSD.org Subject: Re: sysinstall.8 Breaking buildworld Cc: current@FreeBSD.org, stable@FreeBSD.org, cjclark@alum.mit.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.4.0.FreeBSD:010111105204:458=_ Content-Type: text/plain; charset=us-ascii On 11-Jan-01 Bruce A. Mah wrote: > If memory serves me right, "Crist J. Clark" wrote: >> I had some buildworld failures earlier this week. In >> src/share/man/man8 the Makefile includes code to get the sysinstall.8 >> manpage. Since the manpage lives in src/release, this requires that >> you CVSup src-release. I had not been. This broke buildworld which had >> worked in the past. sysinstall.8 is the only file in src-release that >> is required for a buildworld. It seems somewhat silly to me that you >> are required to grab the whole thing for that one file. > > OK...I was one of the people who (indirectly) pushed for this. In a > nutshell, I (and, independently, several other people) noticed that the > sysinstall(8) manpage never gets installed as a part of the binary > distributions or by an installworld. (I got highly confused by this > while rewriting some other parts of the documentation.) The solution > was to make sure that an installworld installs this manpage. > >> I made the change to the Makefile which makes sysinstall.8 and >> src-release optional. I included it in a reply to the PR that >> precipitated the change, >> >> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19818 > > My personal opinion is that sysinstall.8 is a part of the base system > and shouldn't be optional. If we take your suggestion, it means that > installworld will sometimes install this manpage and sometimes it won't. > > A good counter-argument is that installworld doesn't touch > /stand/sysinstall, and therefore shouldn't touch the manpage either. > > Idea: Maybe we need the release building process to do this instead? > On all of my systems, the sysinstall binary came from a CD, and never > got touched by any subsequent installworlds. > >> Anyone have a good reason why everyone _must_ have src-release to >> buildworld? > > I never thought of trying to do a buildworld with anything less than > src-all. I guess my counter question is: Anyone have a good reason to > do buildworlds *without* /usr/src/release/? The real fix is that sysinstall does not belong in /usr/src/release, it needs to move back into /sbin or /usr/sbin and be a part of the regular world build. Jordan, is there any reason why we keep sysinstall out of sync with world? We can still leave /stand on teh system, but having a 3.x sysinstall in /stand on a -current system is less than useless. Whereas having an up-to-date sysinstall in /sbin or /usr/sbin as well as an up-to-date sysinstall.8 manpage that doesn't require weird hacks to be installed would be useful. The new sysinstall isn't coming anytime soon and we both know that, so that is not a valid argument for not moving it. It used to live in /sbin, so my only question is which directory should it move to: /sbin or /usr/sbin? I will do all the legwork on this.. > Bruce. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ --_=XFMail.1.4.0.FreeBSD:010111105204:458=_ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6Xe2I2MoxcVugUsMRAi18AKDolT60SbJn+cmj+lw71PGWPBi47QCeMr+N 7oMXfcOVHa+sieC+tNY2cVw= =Pi8x -----END PGP SIGNATURE----- --_=XFMail.1.4.0.FreeBSD:010111105204:458=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 10:54:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 9EA4837B404; Thu, 11 Jan 2001 10:53:44 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BIrJ110459; Thu, 11 Jan 2001 10:53:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <18455.979234814@winston.osd.bsdi.com> Date: Thu, 11 Jan 2001 10:53:43 -0800 (PST) From: John Baldwin To: Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld Cc: current@FreeBSD.org, stable@FreeBSD.org, cjclark@alum.mit.edu, bmah@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Jordan Hubbard wrote: >> My personal opinion is that sysinstall.8 is a part of the base system >> and shouldn't be optional. If we take your suggestion, it means that >> installworld will sometimes install this manpage and sometimes it won't. > > I think we should simply move the stupid man page into man8. It's a bit > weird to have a man page and its utility live in seperate places, but > the release/ directory in the hierarchy has always been a red-headed > stepchild in any case. If I had it to do over, it would have all gone > into /usr/src/sbin somewhere. Let's put sysinstall back in sbin/ then. It _used_ to live there until someone moved it. :) -r--r--r-- 1 root src 62356 Dec 30 1995 /usr/cvs/src/sbin/sysinstall/Attic/sysinstall.c,v -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Jan 11 11: 0:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 6855F37B401; Thu, 11 Jan 2001 11:00:02 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 11 Jan 2001 10:58:18 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0BJ03O90286; Thu, 11 Jan 2001 11:00:03 -0800 (PST) (envelope-from cjc) Date: Thu, 11 Jan 2001 11:00:03 -0800 From: "Crist J. Clark" To: "Bruce A. Mah" Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111110003.A90221@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <20010110233045.D989@rfx-64-6-211-149.users.reflexco> <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200101111729.f0BHTji13857@bmah-freebsd-0.cisco.com>; from bmah@FreeBSD.ORG on Thu, Jan 11, 2001 at 09:29:45AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 09:29:45AM -0800, Bruce A. Mah wrote: [snip] > My personal opinion is that sysinstall.8 is a part of the base system > and shouldn't be optional. If we take your suggestion, it means that > installworld will sometimes install this manpage and sometimes it won't. Bu-ut, as you point out... > A good counter-argument is that installworld doesn't touch > /stand/sysinstall, and therefore shouldn't touch the manpage either. I think getting the sysinstall binary and manpages out of sync, which is what the current configuration promises to do, is in itself a bug. > Idea: Maybe we need the release building process to do this instead? > On all of my systems, the sysinstall binary came from a CD, and never > got touched by any subsequent installworlds. I had assumed that the 'release' target would do something like this which explains why I was so puzzled by this change. I now understand why some people wanted it. > > Anyone have a good reason why everyone _must_ have src-release to > > buildworld? > > I never thought of trying to do a buildworld with anything less than > src-all. I guess my counter question is: Anyone have a good reason to > do buildworlds *without* /usr/src/release/? When I was CVSup'ing over a phone line to a notebook PC with a 750MB HDD, I trimmed my supfile to only what I needed, no src-games, no src-kerberosIV, no src-kerberos5, no src-release, etc. But to reiterate, I think the best reason not to do this is the potential for getting /stand/sysinstall and sysinstall(8) out of sync on your system. That is Just Wrong. The manpage should only be installed when /stand/sysinstall changes. The fact that src-release is now required was just an annoyance since I lost a build before I tracked it down. I woulda got over it. ;) I had not even noticed the change on some builds over the weekend since I do ususally grab src-release. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 11: 9: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from Mail6.sc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 9CDF137B404; Thu, 11 Jan 2001 11:08:34 -0800 (PST) Received: from sc.rr.com ([24.88.102.101]) by Mail6.sc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 11 Jan 2001 14:08:32 -0500 Received: (from dmaddox@localhost) by sc.rr.com (8.11.1/8.11.1) id f0BJ9GN07028; Thu, 11 Jan 2001 14:09:16 -0500 (EST) (envelope-from dmaddox) Date: Thu, 11 Jan 2001 14:09:16 -0500 From: "Donald J . Maddox" To: Odhiambo Washington Cc: FBSD-STABLE , FBSD-Q Subject: Re: 3.X --> 4.X - buildworld fails Message-ID: <20010111140916.A6874@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: Odhiambo Washington , FBSD-STABLE , FBSD-Q References: <20010111211621.A97461@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010111211621.A97461@poeza.iconnect.co.ke>; from wash@iconnect.co.ke on Thu, Jan 11, 2001 at 09:16:21PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you rebuild libc first, it will work. Apparently you are using a libc from before the addition of the {set,get}res[ug]id calls. On Thu, Jan 11, 2001 at 09:16:21PM +0300, Odhiambo Washington wrote: > This one is for the gurus: > > I am updating a 3.5-S system to 4.X. I've done cvsup with RELENG_4 > yesterday. > Now while strictly following the update procedure in UPDATING (and > referring to the text from the handbook, I get a failure while doing > make buildworld, viz > > cc -O -pipe > -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/us > r/obj/usr/src/gnu/usr.bin/perl/miniperl -c opmini.c > cc -O -pipe > -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/us > r/obj/usr/src/gnu/usr.bin/perl/miniperl > -L/usr/obj/usr/src/gnu/usr.bin/perl/m > iniperl/../libperl -static -o miniperl miniperlmain.o opmini.o > /usr/obj/usr/src > /gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): > In fu > nction `Perl_pp_aassign': > pp_hot.o(.text+0x16a1): undefined reference to `setresuid' > pp_hot.o(.text+0x16d4): undefined reference to `setresgid' > *** Error code 1 > Stop. > *** Error code 1 > Stop. > *** Error code 1 > Stop. > *** Error code 1 > Stop. > > > I am not sure what this means ;-) but I've replicated it by going into > /usr/src/gnu/usr.bin/perl and doing a 'make' in there. > > I highly appreciate all help that will get me past this one. > > TIA > > > -Wash > > -- > Odhiambo Washington Inter-Connect Ltd., > wash@iconnect.co.ke 5th Flr Furaha Plaza > Tel: 254 11 222604 Nkrumah Rd., > Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. > > Presumably, we're all fully qualified computer nerds here, so we are allowed > to use "access" as a verb. Be advised, however, that the practice in common > usage drives English-language purists to scowling fidgets. -Erik Strom, "Perl > CGI Programming" > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 11: 9:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 7A0C137B69C; Thu, 11 Jan 2001 11:09:19 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 11 Jan 2001 11:07:18 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0BJ93090368; Thu, 11 Jan 2001 11:09:03 -0800 (PST) (envelope-from cjc) Date: Thu, 11 Jan 2001 11:09:03 -0800 From: "Crist J. Clark" To: John Baldwin Cc: Jordan Hubbard , current@FreeBSD.org, stable@FreeBSD.org, cjclark@alum.mit.edu, bmah@FreeBSD.org Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <18455.979234814@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Jan 11, 2001 at 10:53:43AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 10:53:43AM -0800, John Baldwin wrote: > > On 11-Jan-01 Jordan Hubbard wrote: > >> My personal opinion is that sysinstall.8 is a part of the base system > >> and shouldn't be optional. If we take your suggestion, it means that > >> installworld will sometimes install this manpage and sometimes it won't. > > > > I think we should simply move the stupid man page into man8. It's a bit > > weird to have a man page and its utility live in seperate places, but > > the release/ directory in the hierarchy has always been a red-headed > > stepchild in any case. If I had it to do over, it would have all gone > > into /usr/src/sbin somewhere. > > Let's put sysinstall back in sbin/ then. It _used_ to live there until someone > moved it. :) > > -r--r--r-- 1 root src 62356 Dec 30 1995 > /usr/cvs/src/sbin/sysinstall/Attic/sysinstall.c,v I had assumed that sysinstall was not part of the standard installworld for recovery purposes. That is, if a buildworld-installworld were to totally hose your system (but of course that _never_ happens), you would still have a reliable /stand/sysinstall uncorrupted by the errant installworld to aid in fixing things. Again, this is just what I assumed the reason for the design to be. And I have never actually used sysinstall to recover a hosed upgrade, I like the fixit.flp. But IMHO, either both /stand/sysinstall and sysinstall.8 get installed when building world or neither do. To me, that seems clear cut. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 11:14:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id D9D4437B401; Thu, 11 Jan 2001 11:14:01 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0BJE0i18987; Thu, 11 Jan 2001 11:14:01 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: John Baldwin Cc: current@FreeBSD.org, stable@FreeBSD.org, cjclark@alum.mit.edu, bmah@FreeBSD.org Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: Message from John Baldwin of "Thu, 11 Jan 2001 10:53:43 PST." Date: Thu, 11 Jan 2001 11:14:00 -0800 Message-ID: <18983.979240440@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Let's put sysinstall back in sbin/ then. It _used_ to live there until someo ne > moved it. :) I won't argue - move away! Just have one of the CVSmeisters do it as a repo-copy, of course. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 11:53: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 48EA137B400; Thu, 11 Jan 2001 11:52:48 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BJqM112128; Thu, 11 Jan 2001 11:52:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <18983.979240440@winston.osd.bsdi.com> Date: Thu, 11 Jan 2001 11:52:47 -0800 (PST) From: John Baldwin To: Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld Cc: bmah@FreeBSD.org, cjclark@alum.mit.edu, stable@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Jordan Hubbard wrote: >> Let's put sysinstall back in sbin/ then. It _used_ to live there until >> someo > ne >> moved it. :) > > I won't argue - move away! Just have one of the CVSmeisters do it as > a repo-copy, of course. Yay! Thanks. Will do. :) > - Jordan -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Jan 11 11:53:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D368337B699; Thu, 11 Jan 2001 11:53:10 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BJqJ112120; Thu, 11 Jan 2001 11:52:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> Date: Thu, 11 Jan 2001 11:52:43 -0800 (PST) From: John Baldwin To: cjclark@alum.mit.edu Subject: Re: sysinstall.8 Breaking buildworld Cc: bmah@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org, Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Crist J. Clark wrote: > On Thu, Jan 11, 2001 at 10:53:43AM -0800, John Baldwin wrote: >> >> On 11-Jan-01 Jordan Hubbard wrote: >> >> My personal opinion is that sysinstall.8 is a part of the base system >> >> and shouldn't be optional. If we take your suggestion, it means that >> >> installworld will sometimes install this manpage and sometimes it won't. >> > >> > I think we should simply move the stupid man page into man8. It's a bit >> > weird to have a man page and its utility live in seperate places, but >> > the release/ directory in the hierarchy has always been a red-headed >> > stepchild in any case. If I had it to do over, it would have all gone >> > into /usr/src/sbin somewhere. >> >> Let's put sysinstall back in sbin/ then. It _used_ to live there until >> someone >> moved it. :) >> >> -r--r--r-- 1 root src 62356 Dec 30 1995 >> /usr/cvs/src/sbin/sysinstall/Attic/sysinstall.c,v > > I had assumed that sysinstall was not part of the standard > installworld for recovery purposes. That is, if a > buildworld-installworld were to totally hose your system (but of > course that _never_ happens), you would still have a reliable > /stand/sysinstall uncorrupted by the errant installworld to aid in > fixing things. Erm, many things live in both /stand and other places: > ll /stand/ | wc -l 35 > ll /stand/rm /bin/rm -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm Putting it in world wouldn't touch /stand, it would just add it to either /usr/sbin or /sbin and keep that copy updated. > Again, this is just what I assumed the reason for the design to > be. And I have never actually used sysinstall to recover a hosed > upgrade, I like the fixit.flp. > > But IMHO, either both /stand/sysinstall and sysinstall.8 get installed > when building world or neither do. To me, that seems clear cut. I vote for both, but not to touch /stand. We don't keep rm.1 in sync with /stand/rm, we keep it in sync with /bin/rm, so this seems to be the most consistent.. > -- > Crist J. Clark cjclark@alum.mit.edu -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Jan 11 12: 6:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from redwood.he.net (redwood.he.net [216.218.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 832AD37B404 for ; Thu, 11 Jan 2001 12:05:59 -0800 (PST) Received: from 3jane (adsl-63-205-248-110.dsl.snfc21.pacbell.net [63.205.248.110]) by redwood.he.net (8.8.6/8.8.2) with SMTP id MAA28124; Thu, 11 Jan 2001 12:05:52 -0800 From: "Pete Slagle" To: Subject: subscribe freebsd-stable Date: Thu, 11 Jan 2001 12:05:53 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 12:10:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from redwood.he.net (redwood.he.net [216.218.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 20EDF37B400 for ; Thu, 11 Jan 2001 12:09:56 -0800 (PST) Received: from 3jane (adsl-63-205-248-110.dsl.snfc21.pacbell.net [63.205.248.110]) by redwood.he.net (8.8.6/8.8.2) with SMTP id MAA28634 for ; Thu, 11 Jan 2001 12:09:36 -0800 From: "Pete Slagle" To: Subject: subscribe freebsd-stable Date: Thu, 11 Jan 2001 12:09:38 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 12:53:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id ACDEB37B400 for ; Thu, 11 Jan 2001 12:53:17 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 11 Jan 2001 20:53:03 +0000 (GMT) Date: Thu, 11 Jan 2001 20:53:03 +0000 From: David Malone To: Matthew West Cc: Ian Dowse , stable@freebsd.org Subject: Re: page faults on FreeBSD 4.2-STABLE Message-ID: <20010111205303.A69516@walton.maths.tcd.ie> References: <20010108140521.A23828@apotheosis.org.za> <200101081256.aa88963@salmon.maths.tcd.ie> <20010108222316.A10341@walton.maths.tcd.ie> <20010111190808.A86850@apotheosis.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010111190808.A86850@apotheosis.org.za>; from mwest@uct.ac.za on Thu, Jan 11, 2001 at 07:08:08PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 07:08:08PM +0200, Matthew West wrote: > After applying your patch taken from -CURRENT, my 4.2-STABLE machine > has been up for the past two days. > > http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/kern/sys_pipe.c.diff?r1=1.67&r2=1.68 > > Many thanks! I've just merged the fix into -stable (including some minor style changes). We've actually been bitten by it a few times in the last couple of days. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 13:44:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 4E40537B404 for ; Thu, 11 Jan 2001 13:43:48 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id f0BLhae40979; Thu, 11 Jan 2001 16:43:37 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010111153833.01e40e30@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Thu, 11 Jan 2001 16:37:44 -0500 To: Mike Andrews , stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: Weird sporadic DNS resolution problems In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed the same thing, and posted the same question a while back to stable, and now recently to freebsd-isp. I am starting to wonder if its a FreeBSD/Sendmail interaction thing, as the same version of sendmail running on a LINUX box, asking the FreeBSD name server does not run into this problem. ---Mike At 12:21 PM 1/11/01 -0500, Mike Andrews wrote: >I'm having a bizarre DNS resolution problem that I'm having a hell of a >time tracking down. Someone tell me I'm just being stupid. :) > >For a few months now, I'm *sporadically* unable to resolve *some* external >domains. This started happening approximately between 4.1.1-RELEASE and >4.2-RELEASE, when I believe Bind 8 was upgraded in the source tree. (I >don't remember the exact date, sorry) > >Here's what appears to be going on: > >When one (but not both) of the nameservers for a domain replies >non-authoritatively, named will cache a negative response, rather than >asking the other nameserver. Subsequent lookups return an immediate >failure. Restarting the nameserver, and then immediately querying the >same problematic domain DOES work, but only the first query. After a few >minutes/hours the domain stops working again. > >This is especially chronic because Sendmail tries to resolve domains on >incoming email (for spam protection purposes)... it will give "Domain of >sender address foo@bar does not resolve" and return a 451 code. This >causes the other end to retry periodically, unless the other end is >something like Outlook Express, in which case the customer calls me and >complains. :) > >One example domain is "farmersfrankfort.com". This was moved from us to >another site yesterday, but we still do MX for them. Looking at whois and >at the root servers, you can see that their two new nameservers are now >"cerberus.sbscorp.com" and "ns1.qwest.net". Querying the sbscorp server >works great, querying qwest doesn't -- it appears Quest never added them >to their nameserver config at all. (It has been only about 24 hours, so >it's not *too* surprising I guess...) Anyway, when someone on one of our >dialups tries to send mail with @farmersfrankfort.com on the end, our >Sendmail is unable to resolve it and rejects the message. If I restart >(not reload) named, it will start working for a while, then die on its own >again. My theory is that if it happens to query sbscorp it's happy, if it >happens to query qwest it isn't, and caches the fact that it isn't. > >Another example is "setel.com" and "se-tel.com". We sometimes have >problems exchanging mail with them because one of their DNS servers >appears to be answering non-authoritatively. Again, I can flush my >backlog by restarting named and immediately running the sendmail queue >manually (and I could probably flush their backlog by telnetting to their >SMTP port and issuing an ETRN)... but obviously that's not exactly >elegant :) > >I've tried adding "max-ncache-ttl 1" to my named config, hoping it would >help. It didn't. > >In one sense this is "not my problem" because their name server shouldn't >be answering non-authoritatively in the first place. But the fact that >this started happening after a make world a few months ago, and that I >feel it should be a slight bit more tolerant of other people's sloppy >configurations, makes it my problem. > >Anyone have any ideas as to what's going on, or can tell me what debugging >output to enable that I could send here that would help figure it out? >Configuration options to named that would revert to older behavior? A >whack on the head? (I could just compile an older named I guess, but I >fear opening up security holes/DoS attacks.) > > >Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com >VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY >Internet access for Frankfort, Lexington, Louisville and surrounding counties >www.fark.com: If it's not news, it's Fark. (Or something like that.) > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 13:47: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 7491937B401; Thu, 11 Jan 2001 13:46:36 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 11 Jan 2001 13:44:36 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0BLkLK91229; Thu, 11 Jan 2001 13:46:21 -0800 (PST) (envelope-from cjc) Date: Thu, 11 Jan 2001 13:46:16 -0800 From: "Crist J. Clark" To: John Baldwin Cc: bmah@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org, Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Jan 11, 2001 at 11:52:43AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote: [snip] > Erm, many things live in both /stand and other places: > > > ll /stand/ | wc -l > 35 > > ll /stand/rm /bin/rm > -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm > -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm I am not clear what you are saying here. Only sysinstall lives in /stand, [592:~] ls -li /stand total 45250 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 -sh 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 [ 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 arp 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 boot_crunch 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 cpio 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 dhclient 3 drwx------ 3 root wheel 512 Jun 19 2000 etc 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 find 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 fsck 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 gunzip 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 gzip 29952 drwxr-xr-x 2 root wheel 1024 Jun 19 2000 help 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 hostname 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 ifconfig 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 minigzip 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 mount_mfs 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 mount_nfs 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 newfs 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 pccardc 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 pccardd 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 ppp 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 pwd 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 rm 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 route 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 sed 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 sh 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 slattach 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 sysinstall 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 test 22465 -r-xr-xr-x 28 root wheel 1645704 Mar 20 2000 zcat But it lives by many names. (Ignoring the directories.) > Putting it in world wouldn't touch /stand, it would just add it to either > /usr/sbin or /sbin and keep that copy updated. [snip] > I vote for both, but not to touch /stand. We don't keep rm.1 in sync with > /stand/rm, we keep it in sync with /bin/rm, so this seems to be the most > consistent.. Well, /stand/rm is not _really_ rm at all, but I get the point. I guess the only question is whether to put it in /sbin or /usr/sbin. I think /sbin makes sense (so it is bootable), but it is 1.6MB of /-bloat... But from another thread about making 250MB the default / size, I guess few care too much about that anymore. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 13:52:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www3.infolink.com.br (www3.infolink.com.br [200.255.108.4]) by hub.freebsd.org (Postfix) with ESMTP id 4C41937B400 for ; Thu, 11 Jan 2001 13:52:09 -0800 (PST) Received: from diala11 (unverified [200.255.108.11]) by www3.infolink.com.br (Vircom SMTPRS 4.2.181) with SMTP id ; Thu, 11 Jan 2001 19:52:08 -0300 Message-ID: <002801c07c18$be357e50$0b6cffc8@infolink.com.br> From: "Antonio Carlos Pina" To: "Jonathan Pennington" Cc: References: <20010110232117.A10054@coastalgeology.org> Subject: Re: Cannot access certain sites through firewall Date: Thu, 11 Jan 2001 19:52:07 -0200 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 5.50.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the problem is your mtu. In fact, I have seen a lot of sites which have problems with mtu-path-discovery because their admins have DISABLED all icmp traffic. Sad, but it's true. Try to put everything in 1500. Best Regards, Cordialmente, Antonio Carlos Pina Diretor de Tecnologia INFOLINK Internet http://www.infolink.com.br ----- Original Message ----- From: "Jonathan Pennington" To: Sent: Thursday, January 11, 2001 2:21 AM Subject: Cannot access certain sites through firewall > Hello, > I am having a problem with accessing certain websites from my internal > network. > > System 4.2-STABLE, Dec-21. PPPoE through tun0 with an external Alcatel > modem connected to ed1 and an internal network with one windows > computer and my FreeBSD 4.2-STABLE laptop that can access most > websites, but not all. www.cityspree.com is the one in the logs, but > www.signals.com, www.pigglywiggly.com and others are on the list. > > I can access everything from the firewall computer, including the > sites that cannot be accessed from the internal network. The tun0 > interface is mtu 1492, ed0 (internal) and ed1 (external) were 1500, > but the same thing happens with all at 1492. (I read in the archives > about natd mangling packets due to different sizes). From the logs, it > looks like things are travelling through, but Netscape just > waits. Specifically, netscape stops at "Connect: Host... contacted. > Waiting for reply." However, I can ping those address and not loose > packets. Even when I open the firewall up by flushing all > rules and allowing everything, theses sites are not working. What am I > doing wrong? Is this a problem with my natd translation? I am using > natd unmodified (ie. I set no configs myself), but why would that stop > only some sites (I can access https). > > I'm not on this list, but will watch the geocrawler archives. I > appreciate any help. Log snippet of attempt to visit www.cityspree.com > and www.signals.com after successfully pinging signals.com and a copy > of my firewall rules follow. > > ---------------------------------------------------------------- > Jan 10 23:00:00 bullwinkle newsyslog[10356]: logfile turned over > ################## > Jan 10 23:01:50 bullwinkle /kernel: ipfw: 850 Accept TCP 216.78.159.182:62486 216.35.68.25:80 out via tun0 > Jan 10 23:02:47 bullwinkle /kernel: ipfw: 850 Accept TCP 216.78.159.182:33439 63.71.95.177:80 out via tun0 > Jan 10 23:03:11 bullwinkle /kernel: ipfw: 65435 Accept ICMP:8.0 216.78.159.182 216.35.68.25 out via tun0 > Jan 10 23:03:11 bullwinkle /kernel: ipfw: 65435 Accept ICMP:0.0 216.35.68.25 192.168.10.3 in via tun0 > Jan 10 23:03:12 bullwinkle /kernel: ipfw: 65435 Accept ICMP:8.0 216.78.159.182 216.35.68.25 out via tun0 > Jan 10 23:03:12 bullwinkle /kernel: ipfw: 65435 Accept ICMP:0.0 216.35.68.25 192.168.10.3 in via tun0 > Jan 10 23:03:13 bullwinkle /kernel: ipfw: 65435 Accept ICMP:8.0 216.78.159.182 216.35.68.25 out via tun0 > Jan 10 23:03:13 bullwinkle /kernel: ipfw: 65435 Accept ICMP:0.0 216.35.68.25 192.168.10.3 in via tun0 > Jan 10 23:03:14 bullwinkle /kernel: ipfw: 65435 Accept ICMP:8.0 216.78.159.182 216.35.68.25 out via tun0 > Jan 10 23:03:14 bullwinkle /kernel: ipfw: 65435 Accept ICMP:0.0 216.35.68.25 192.168.10.3 in via tun0 > Jan 10 23:03:22 bullwinkle /kernel: ipfw: 1550 Accept UDP 205.152.0.20:53 192.168.10.2:137 in via tun0 > Jan 10 23:03:25 bullwinkle /kernel: ipfw: 65435 Accept ICMP:8.0 216.78.159.182 63.71.95.177 out via tun0 > Jan 10 23:03:25 bullwinkle /kernel: ipfw: 65435 Accept ICMP:0.0 63.71.95.177 192.168.10.3 in via tun0 > Jan 10 23:03:26 bullwinkle /kernel: ipfw: 65435 Accept ICMP:8.0 216.78.159.182 63.71.95.177 out via tun0 > Jan 10 23:03:26 bullwinkle /kernel: ipfw: 65435 Accept ICMP:0.0 63.71.95.177 192.168.10.3 in via tun0 > Jan 10 23:03:27 bullwinkle /kernel: ipfw: 65435 Accept ICMP:8.0 216.78.159.182 63.71.95.177 out via tun0 > Jan 10 23:03:27 bullwinkle /kernel: ipfw: 65435 Accept ICMP:0.0 63.71.95.177 192.168.10.3 in via tun0 > Jan 10 23:03:28 bullwinkle /kernel: ipfw: 65435 Accept ICMP:8.0 216.78.159.182 63.71.95.177 out via tun0 > Jan 10 23:03:28 bullwinkle /kernel: ipfw: 65435 Accept ICMP:0.0 63.71.95.177 192.168.10.3 in via tun0 > Jan 10 23:03:48 bullwinkle /kernel: ipfw: 850 Accept TCP 216.78.159.182:58680 216.136.204.21:80 out via tun0 > Jan 10 23:03:49 bullwinkle /kernel: ipfw: 850 Accept TCP 216.78.159.182:56779 216.136.204.21:80 out via tun0 > Jan 10 23:03:49 bullwinkle /kernel: ipfw: 850 Accept TCP 216.78.159.182:46765 216.136.204.21:80 out via tun0 > Jan 10 23:03:50 bullwinkle /kernel: ipfw: 850 Accept TCP 216.78.159.182:35950 216.136.204.21:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1078 216.136.204.21:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1081 216.35.68.25:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:40600 216.136.204.21:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 850 Accept TCP 216.78.159.182:41953 216.35.68.25:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.35.68.25:80 216.78.159.182:1081 in via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 950 Accept TCP 216.35.68.25:80 192.168.10.3:1081 in via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1081 216.35.68.25:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:41953 216.35.68.25:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.136.204.21:80 216.78.159.182:1078 in via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 950 Accept TCP 216.136.204.21:80 192.168.10.3:1078 in via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1081 216.35.68.25:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:41953 216.35.68.25:80 out via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.35.68.25:80 216.78.159.182:1081 in via tun0 > Jan 10 23:05:48 bullwinkle /kernel: ipfw: 950 Accept TCP 216.35.68.25:80 192.168.10.3:1081 in via tun0 > Jan 10 23:05:57 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1071 66.37.205.21:80 out via tun0 > Jan 10 23:05:57 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:35306 66.37.205.21:80 out via tun0 > Jan 10 23:05:57 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1074 63.71.95.177:80 out via tun0 > Jan 10 23:05:57 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:59397 63.71.95.177:80 out via tun0 > Jan 10 23:07:01 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1071 66.37.205.21:80 out via tun0 > Jan 10 23:07:01 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:35306 66.37.205.21:80 out via tun0 > Jan 10 23:07:01 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1074 63.71.95.177:80 out via tun0 > Jan 10 23:07:01 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:59397 63.71.95.177:80 out via tun0 > Jan 10 23:08:05 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1071 66.37.205.21:80 out via tun0 > Jan 10 23:08:05 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:35306 66.37.205.21:80 out via tun0 > Jan 10 23:08:05 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1074 63.71.95.177:80 out via tun0 > Jan 10 23:08:05 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:59397 63.71.95.177:80 out via tun0 > Jan 10 23:09:09 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1071 66.37.205.21:80 out via tun0 > Jan 10 23:09:09 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:35306 66.37.205.21:80 out via tun0 > Jan 10 23:09:09 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1074 63.71.95.177:80 out via tun0 > Jan 10 23:09:09 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:59397 63.71.95.177:80 out via tun0 > Jan 10 23:10:13 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1071 66.37.205.21:80 out via tun0 > Jan 10 23:10:13 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:35306 66.37.205.21:80 out via tun0 > Jan 10 23:10:13 bullwinkle /kernel: ipfw: 350 Divert 8668 TCP 216.78.159.182:1074 63.71.95.177:80 out via tun0 > Jan 10 23:10:13 bullwinkle /kernel: ipfw: 950 Accept TCP 216.78.159.182:59397 63.71.95.177:80 out via tun0 > > > ------------------------------------------------------- > ${fwcmd} add 100 pass all from any to any via lo0 > ${fwcmd} add 200 deny all from any to 127.0.0.0/8 > ${fwcmd} add 250 allow tcp from 127.0.0.1 to 127.0.0.1 51966 > > $fwcmd add divert natd log all from any to any via tun0 > > $fwcmd add allow ip from any to any via lo0 > $fwcmd add allow ip from any to any via ed0 > $fwcmd add deny all from any to 192.168.10.0/24 in via ed1 > $fwcmd add deny all from 192.168.10.0/24 to any out via ed1 > > $fwcmd add allow log tcp from any to any out xmit tun0 setup > $fwcmd add allow log tcp from any to any via tun0 established > > $fwcmd add allow log tcp from any to any 80 setup > $fwcmd add allow log tcp from any 80 to any in via tun0 > $fwcmd add allow log tcp from any to any 22 setup > $fwcmd add allow log tcp from 209.85.3.25 to any 2222 setup > $fwcmd add pass tcp from any to any 25 setup > $fwcmd add allow log udp from any to 192.168.10.2 in via tun0 > $fwcmd add allow log tcp from any to 192.168.10.2 in via tun0 > > $fwcmd add allow log tcp from any to any 113 in recv tun0 > > $fwcmd add allow udp from any to 205.152.0.20 53 out xmit tun0 > $fwcmd add allow udp from any to 205.152.0.5 53 out xmit tun0 > > $fwcmd add allow udp from 205.152.0.0/16 53 to any in recv tun0 > > $fwcmd add 65435 allow log icmp from any to any > > $fwcmd add deny all from 192.168.10.0/24 to any in via tun0 > > $fwcmd add pass all from any to any frag > > $fwcmd add deny log tcp from any to any in via tun0 setup > > $fwcmd add 65435 allow ip from any to any out xmit tun0 > > $fwcmd add 65435 allow log udp from any to any 6970 in via tun0 > > $fwcmd add 65435 deny log ip from any to any in via tun0 > -------------------------------------------------------- > -- > Jonathan Pennington | http://coastalgeology.org > Site Manager | Protection and stewardship > CoastalGeology.Org (CGO) | through public education. > john@coastalgeology.org | Join CGO, make a difference. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 14: 1: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id CDDCA37B402; Thu, 11 Jan 2001 14:00:40 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.20 #1) id 14Gplf-0004UP-00; Thu, 11 Jan 2001 22:00:23 +0000 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.11.1/8.11.1) id f0BM0Ml93543; Thu, 11 Jan 2001 22:00:22 GMT (envelope-from ben) Date: Thu, 11 Jan 2001 22:00:21 +0000 From: Ben Smithurst To: cjclark@alum.mit.edu Cc: John Baldwin , bmah@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org, Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111220021.C79365@strontium.scientia.demon.co.uk> References: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Crist J. Clark wrote: > On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote: > >> Erm, many things live in both /stand and other places: >> >>> ll /stand/ | wc -l >> 35 >>> ll /stand/rm /bin/rm >> -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm >> -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm > > I am not clear what you are saying here. Only sysinstall lives in > /stand, yeah, but it can be used as many things. If invoked as "rm" sysinstall behaves just like the real rm, it happens to be one big binary. > Well, /stand/rm is not _really_ rm at all, but I get the point. I > guess the only question is whether to put it in /sbin or /usr/sbin. I > think /sbin makes sense (so it is bootable), but it is 1.6MB of > /-bloat... But from another thread about making 250MB the default / > size, I guess few care too much about that anymore. I'd prefer it in /usr/sbin, some of my root partitions are only 32MB, and that's not big enough at the moment. If your /usr is hosed to the extent you can't mount it you've probably got more problems than sysinstall will help you with. But that's just my opinion. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 14:16:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by hub.freebsd.org (Postfix) with ESMTP id 7F86D37B400; Thu, 11 Jan 2001 14:16:21 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id OAA12226; Thu, 11 Jan 2001 14:15:51 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f0BMFgT19311; Thu, 11 Jan 2001 14:15:42 -0800 (PST) (envelope-from bmah) Message-Id: <200101112215.f0BMFgT19311@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2+ 01/03/2001 with nmh-1.0.4 To: Ben Smithurst Cc: cjclark@alum.mit.edu, John Baldwin , bmah@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org, Jordan Hubbard Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: <20010111220021.C79365@strontium.scientia.demon.co.uk> References: <20010111110903.B90221@rfx-64-6-211-149.users.reflexco> <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> <20010111220021.C79365@strontium.scientia.demon.co.uk> Comments: In-reply-to Ben Smithurst message dated "Thu, 11 Jan 2001 22:00:21 +0000." From: bmah@FreeBSD.org (Bruce A. Mah) Reply-To: bmah@FreeBSD.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_454632526P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 11 Jan 2001 14:15:42 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_454632526P Content-Type: text/plain; charset=us-ascii If memory serves me right, Ben Smithurst wrote: > yeah, but it can be used as many things. If invoked as "rm" sysinstall > behaves just like the real rm, it happens to be one big binary. The thing in /stand is a crunchgen(8) binary. sysinstall itself is (chug, chug) 850K. After being stripped, it's 798K: 1616 -rwxr-xr-x 1 root wheel 817416 Jan 11 14:14 sysinstall Bruce. --==_Exmh_454632526P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6XjCO2MoxcVugUsMRAkxjAKCROr/S8NkW1Dhh4f1w9/NAvkspZgCglb77 qOredvmGB+Ekd7gsD8LEZcU= =RaKn -----END PGP SIGNATURE----- --==_Exmh_454632526P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 14:23: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 74E5537B699; Thu, 11 Jan 2001 14:22:39 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0BMMNQ69170; Thu, 11 Jan 2001 14:22:24 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101112222.f0BMMNQ69170@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jordan Hubbard Cc: John Baldwin , current@FreeBSD.ORG, stable@FreeBSD.ORG, cjclark@alum.mit.edu, bmah@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: <18983.979240440@winston.osd.bsdi.com> Date: Thu, 11 Jan 2001 14:22:23 -0800 From: Peter Wemm Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > Let's put sysinstall back in sbin/ then. It _used_ to live there until som eo > ne > > moved it. :) > > I won't argue - move away! Just have one of the CVSmeisters do it as > a repo-copy, of course. We cannot repo-copy it to src/sbin - there is a copy there already. We could blow the old one away and lose the history (RELEASE_2_0 and earlier) but I guess that is no big deal these days. Personally I would prefer it in src/usr.sbin/sysinstall and have it dynamically linked. The release crunchgen can still take the .o's and make the giant /stand version.. dynamic: 390769 shared: 892921 On the other hand, if we had the static version in src/sbin, we could have a "LINKS+= /sbin/sysinstall /stand/sysinstall" and blow away the old installed version with each make world. This would avoid POLA with people following old instructions to run /stand/sysinstall. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 14:23:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 26D2737B6BC; Thu, 11 Jan 2001 14:23:04 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0BMN2i19749; Thu, 11 Jan 2001 14:23:02 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Ben Smithurst Cc: cjclark@alum.mit.edu, John Baldwin , bmah@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: Message from Ben Smithurst of "Thu, 11 Jan 2001 22:00:21 GMT." <20010111220021.C79365@strontium.scientia.demon.co.uk> Date: Thu, 11 Jan 2001 14:23:02 -0800 Message-ID: <19745.979251782@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > yeah, but it can be used as many things. If invoked as "rm" sysinstall > behaves just like the real rm, it happens to be one big binary. This, however, is merely "post-installation behavior" - if you rebuild and reinstall sysinstall in order to catch up with a bug fix to it, however, then this behavior goes away. - Jordan > > > Well, /stand/rm is not _really_ rm at all, but I get the point. I > > guess the only question is whether to put it in /sbin or /usr/sbin. I > > think /sbin makes sense (so it is bootable), but it is 1.6MB of > > /-bloat... But from another thread about making 250MB the default / > > size, I guess few care too much about that anymore. > > I'd prefer it in /usr/sbin, some of my root partitions are only 32MB, > and that's not big enough at the moment. If your /usr is hosed to > the extent you can't mount it you've probably got more problems than > sysinstall will help you with. But that's just my opinion. > > -- > Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 14:39:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 6E2F037B401; Thu, 11 Jan 2001 14:38:50 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BMcS117827; Thu, 11 Jan 2001 14:38:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010111220021.C79365@strontium.scientia.demon.co.uk> Date: Thu, 11 Jan 2001 14:38:55 -0800 (PST) From: John Baldwin To: Ben Smithurst Subject: Re: sysinstall.8 Breaking buildworld Cc: Jordan Hubbard , current@FreeBSD.org, stable@FreeBSD.org, bmah@FreeBSD.org, cjclark@alum.mit.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Ben Smithurst wrote: > Crist J. Clark wrote: > >> On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote: >> >>> Erm, many things live in both /stand and other places: >>> >>>> ll /stand/ | wc -l >>> 35 >>>> ll /stand/rm /bin/rm >>> -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm >>> -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm >> >> I am not clear what you are saying here. Only sysinstall lives in >> /stand, > > yeah, but it can be used as many things. If invoked as "rm" sysinstall > behaves just like the real rm, it happens to be one big binary. > >> Well, /stand/rm is not _really_ rm at all, but I get the point. I >> guess the only question is whether to put it in /sbin or /usr/sbin. I >> think /sbin makes sense (so it is bootable), but it is 1.6MB of >> /-bloat... But from another thread about making 250MB the default / >> size, I guess few care too much about that anymore. > > I'd prefer it in /usr/sbin, some of my root partitions are only 32MB, > and that's not big enough at the moment. If your /usr is hosed to > the extent you can't mount it you've probably got more problems than > sysinstall will help you with. But that's just my opinion. Erm, sysinstall can be used as a replacement for fdisk and disklabel, both of which are in /sbin. In fact, in 4.2 the only tool you can realistically use to splat a virgin disklabel onto a slice w/o weird hoop jumping that isn't documented _is_ sysinstall. disklabel should have that fixed by 4.3, however. However, 800k is big for /sbin: > ll /sbin/ | sort -n -k 5 ... -r-xr-sr-x 2 root tty 299956 Jan 9 08:25 restore -r-xr-sr-x 2 root tty 299956 Jan 9 08:25 rrestore -r-xr-xr-x 1 root wheel 424448 Jan 9 08:24 ipfstat -r-xr-xr-x 1 root wheel 484912 Jan 9 08:24 fsdb -r-xr-xr-x 1 root wheel 513748 Jan 9 08:25 vinum -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Jan 11 14:39:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id BE56537B69C; Thu, 11 Jan 2001 14:38:55 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0BMcQ117823; Thu, 11 Jan 2001 14:38:27 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010111134616.A91185@rfx-64-6-211-149.users.reflexco> Date: Thu, 11 Jan 2001 14:38:53 -0800 (PST) From: John Baldwin To: "Crist J. Clark" Subject: Re: sysinstall.8 Breaking buildworld Cc: Jordan Hubbard , current@FreeBSD.org, stable@FreeBSD.org, bmah@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Crist J. Clark wrote: > On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote: > > [snip] > >> Erm, many things live in both /stand and other places: >> >> > ll /stand/ | wc -l >> 35 >> > ll /stand/rm /bin/rm >> -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm >> -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm > > I am not clear what you are saying here. Only sysinstall lives in > /stand, Heh, no. That is a crunch. It has the object code for _all_ of those binaries in it. So /stand/rm will remove a file just like the normal rm: > /stand/rm usage: rm [-f | -i] [-dPRrvW] file ... unlink file >> Putting it in world wouldn't touch /stand, it would just add it to either >> /usr/sbin or /sbin and keep that copy updated. > > [snip] > >> I vote for both, but not to touch /stand. We don't keep rm.1 in sync with >> /stand/rm, we keep it in sync with /bin/rm, so this seems to be the most >> consistent.. > > Well, /stand/rm is not _really_ rm at all, but I get the point. I > guess the only question is whether to put it in /sbin or /usr/sbin. I > think /sbin makes sense (so it is bootable), but it is 1.6MB of > /-bloat... But from another thread about making 250MB the default / > size, I guess few care too much about that anymore. It isn't that big: > file $owd/sysinstall /usr/obj/usr/src/sbin/sysinstall/sysinstall: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, not stripped > ll !:1 ll /usr/obj/usr/src/sbin/sysinstall/sysinstall -rwxrwxr-x 1 john src 899374 Jan 11 14:06 /usr/obj/usr/src/sbin/sysinstall/sysinstall The stripped version is about 840k, which isn't but so bad. That is if it lives in /sbin (which I vote for). The dynamic version if it goes in /usr/sbin would be smaller again. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Jan 11 14:51:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 019F037B400 for ; Thu, 11 Jan 2001 14:51:24 -0800 (PST) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id JAA24669 for ; Fri, 12 Jan 2001 09:51:21 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma024659; Fri, 12 Jan 01 09:51:18 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.11.1/8.11.0) with ESMTP id f0BMpIE85346 for ; Fri, 12 Jan 2001 09:51:18 +1100 (EST) (envelope-from carl@xena.ipaustralia.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Fri, 12 Jan 2001 09:51:18 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: stable@freebsd.org Subject: Running Linux kernel modules. 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 There are a couple of linux kernel modules that I'd love to run under FreeBSD. I've always assumed that I'd have to rewrite them substantially to make that happen. Can anyone give me some pointers on how hard it could be to port a linux kernel module to FreeBSD? Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 15:12: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 37F6B37B69B for ; Thu, 11 Jan 2001 15:11:41 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0BNBcm28858; Thu, 11 Jan 2001 15:11:38 -0800 (PST) Date: Thu, 11 Jan 2001 15:11:37 -0800 From: Alfred Perlstein To: Carl Makin Cc: stable@FreeBSD.ORG Subject: Re: Running Linux kernel modules. Message-ID: <20010111151137.L7240@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from carl@xena.ipaustralia.gov.au on Fri, Jan 12, 2001 at 09:51:18AM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Carl Makin [010111 14:52] wrote: > > There are a couple of linux kernel modules that I'd love to run under > FreeBSD. I've always assumed that I'd have to rewrite them substantially > to make that happen. > > Can anyone give me some pointers on how hard it could be to port a linux > kernel module to FreeBSD? Depends on how familiar you are with kernel internals, for instance after taking a quick look at the kernel module needed to run vmware it was pretty clear that someone with the experience and time could have it done in under a week, about 2 weeks later some maniac ( :) ) surfaced who had done just that. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 17: 3:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 90C7137B698 for ; Thu, 11 Jan 2001 17:03:08 -0800 (PST) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.1/8.11.1) with ESMTP id f0C12X863536; Fri, 12 Jan 2001 12:02:34 +1100 (EST) (envelope-from marka@nominum.com) Message-Id: <200101120102.f0C12X863536@drugs.dv.isc.org> To: Mike Andrews Cc: stable@freebsd.org From: Mark.Andrews@nominum.com Subject: Re: Weird sporadic DNS resolution problems In-reply-to: Your message of "Thu, 11 Jan 2001 12:21:51 CDT." Date: Fri, 12 Jan 2001 12:02:33 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When one (but not both) of the nameservers for a domain replies > non-authoritatively, named will cache a negative response, rather than > asking the other nameserver. No. It caches that the server is lame for the zone then tries other servers. > Subsequent lookups return an immediate > failure. And what is logged when that happens? > Restarting the nameserver, and then immediately querying the > same problematic domain DOES work, but only the first query. After a few > minutes/hours the domain stops working again. This sounds more like a bad delegation, parent and child zones dissagreeing on the nameserver RRset, than a lame server. > > This is especially chronic because Sendmail tries to resolve domains on > incoming email (for spam protection purposes)... it will give "Domain of > sender address foo@bar does not resolve" and return a 451 code. This > causes the other end to retry periodically, unless the other end is > something like Outlook Express, in which case the customer calls me and > complains. :) > > One example domain is "farmersfrankfort.com". This was moved from us to > another site yesterday, but we still do MX for them. Looking at whois and > at the root servers, you can see that their two new nameservers are now > "cerberus.sbscorp.com" and "ns1.qwest.net". Querying the sbscorp server > works great, querying qwest doesn't -- it appears Quest never added them > to their nameserver config at all. (It has been only about 24 hours, so > it's not *too* surprising I guess...) Servers are supposed to be serving the zone *before* they are delegated to. > Anyway, when someone on one of our > dialups tries to send mail with @farmersfrankfort.com on the end, our > Sendmail is unable to resolve it and rejects the message. If I restart > (not reload) named, it will start working for a while, then die on its own > again. My theory is that if it happens to query sbscorp it's happy, if it > happens to query qwest it isn't, and caches the fact that it isn't. > > Another example is "setel.com" and "se-tel.com". We sometimes have > problems exchanging mail with them because one of their DNS servers > appears to be answering non-authoritatively. Again, I can flush my > backlog by restarting named and immediately running the sendmail queue > manually (and I could probably flush their backlog by telnetting to their > SMTP port and issuing an ETRN)... but obviously that's not exactly > elegant :) Well both the servers for setel.com are lame as are se-tel.com. If all the sources of information are bad what do you expect the namesever to do. > > I've tried adding "max-ncache-ttl 1" to my named config, hoping it would > help. It didn't. It's not caching a negative answer so of course this has no effect. > > In one sense this is "not my problem" because their name server shouldn't > be answering non-authoritatively in the first place. But the fact that > this started happening after a make world a few months ago, and that I > feel it should be a slight bit more tolerant of other people's sloppy > configurations, makes it my problem. > > Anyone have any ideas as to what's going on, or can tell me what debugging > output to enable that I could send here that would help figure it out? > Configuration options to named that would revert to older behavior? A > whack on the head? (I could just compile an older named I guess, but I > fear opening up security holes/DoS attacks.) > > > Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com > VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY > Internet access for Frankfort, Lexington, Louisville and surrounding counties > www.fark.com: If it's not news, it's Fark. (Or something like that.) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 17: 7:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6BAC737B401 for ; Thu, 11 Jan 2001 17:07:30 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA07143; Fri, 12 Jan 2001 11:37:11 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010111142517.9D69EE6B8B@netcom1.netcom.com> Date: Fri, 12 Jan 2001 11:37:11 +1030 (CST) From: "Daniel O'Connor" To: Mike Harding Subject: Re: buildworld over nfs failing consistently Cc: Robin_Blanchard@gactr.uga.edu, stable@FreeBSD.ORG, cjclark@alum.mit.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Jan-01 Mike Harding wrote: > so I can get out of the way in 30 or so seconds, and I get mail when > it's done. I also have a log of the build which is useful if it fails > - 'tail' doesn't generally go far back enough, though of course that > is configurable. Hmm I wrote a makefile to update my tree and build.. Uses tee to store the log in /tmp for later perusal.. The mail idea is a good one though :) --- 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 Jan 11 17:22:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gateway.symark.com (firewall.symark.westlake.iswest.net [207.178.203.34]) by hub.freebsd.org (Postfix) with ESMTP id C723C37B400; Thu, 11 Jan 2001 17:22:36 -0800 (PST) Received: (from mailer@localhost) by gateway.symark.com (8.9.3/8.9.3) id RAA17294; Thu, 11 Jan 2001 17:22:30 -0800 Received: from camel.symark.com(128.1.1.97) by gateway.symark.com via smap (V2.1+anti-relay+anti-spam) id xma017290; Thu, 11 Jan 01 17:22:11 -0800 Received: by localhost with Microsoft MAPI; Thu, 11 Jan 2001 17:24:54 -0800 Message-ID: <01C07BF3.695D3780.ggross@symark.com> From: Glen Gross Reply-To: "ggross@symark.com" To: "'Alfred Perlstein'" , Carl Makin Cc: "stable@FreeBSD.ORG" Subject: RE: Running Linux kernel modules. Date: Thu, 11 Jan 2001 17:24:52 -0800 Organization: Symark Software X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 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 Is there a possibility of a generalized interface where any linux kernel module could be loaded, in the event that the linux emulator were loaded? Or would this require running the linux kernel in RAM, and therefore running two virtual machines? On Thursday, January 11, 2001 3:12 PM, Alfred Perlstein [SMTP:bright@wintelcom.net] wrote: > * Carl Makin [010111 14:52] wrote: > > > > There are a couple of linux kernel modules that I'd love to run under > > FreeBSD. I've always assumed that I'd have to rewrite them substantially > > to make that happen. > > > > Can anyone give me some pointers on how hard it could be to port a linux > > kernel module to FreeBSD? > > Depends on how familiar you are with kernel internals, for instance > after taking a quick look at the kernel module needed to run vmware > it was pretty clear that someone with the experience and time could > have it done in under a week, about 2 weeks later some maniac ( :) ) > surfaced who had done just that. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com pp-support@symark.com pb-support@symark.com Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 17:33: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 7896937B400 for ; Thu, 11 Jan 2001 17:32:39 -0800 (PST) Received: from deneb.dbai.tuwien.ac.at (deneb [128.130.111.2]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0C1Wa820473; Fri, 12 Jan 2001 02:32:37 +0100 (MET) Received: from localhost (pfeifer@localhost) by deneb.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0C1WZ875516; Fri, 12 Jan 2001 02:32:36 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: deneb.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Fri, 12 Jan 2001 02:32:35 +0100 (CET) From: Gerald Pfeifer To: Cc: Subject: passwd (still) broken in NIS environments 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 Someone changed passwd/yppasswd such that now (on 4.2-RELEASE, put presumably also -STABLE) it is broken. NIS-Server: Solaris 2.6 /SPARC with current Recommended Patches NIS-Client: FreeBSD 4.2 /i386 Changing NIS password for user on NIS-server. Old Password: New password: Retype new password: passwd: failed to change NIS password: RPC: Server can't decode arguments When trying to debug this on the Solaris box, I got the following output from snoop: client -> server PORTMAP C GETPORT prog=100009 (NISPASSWD) vers=1 proto=UDP server -> client PORTMAP R GETPORT port=819 client -> server NISPASSWD C server -> client RPC R (#196) XID=861861090 Garbage arguments Any ideas what might have caused this breakage? This worked w/o problems for the past three or four years (and corresponding FreeBSD releases). Anyone willing to help me debug this? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 17:43:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1532237B400; Thu, 11 Jan 2001 17:43:35 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA45854; Thu, 11 Jan 2001 17:43:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f0C1hXt79841; Thu, 11 Jan 2001 17:43:33 -0800 (PST) (envelope-from obrien) Date: Thu, 11 Jan 2001 17:43:32 -0800 From: "David O'Brien" To: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: sysinstall.8 Breaking buildworld Message-ID: <20010111174332.B74480@dragon.nuxi.com> Reply-To: current@FreeBSD.org, stable@FreeBSD.org References: <20010111220021.C79365@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Jan 11, 2001 at 02:38:55PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 02:38:55PM -0800, John Baldwin wrote: > Erm, sysinstall can be used as a replacement for fdisk and disklabel, > both of which are in /sbin. In fact, in 4.2 the only tool you can > realistically use to splat a virgin disklabel onto a slice w/o weird > hoop jumping that isn't documented _is_ sysinstall. disklabel should > have that fixed by 4.3, however. But disklabel/fdisk can't even accept MB's as a unit. Until they grow the functionality of the NetBSD and OpenBSD versions of them, sysinstall is really the only tolerable disk label manipulation tool our users have. This includes those with a bummed /usr that needs to install a new disk to get it back. On Thu, Jan 11, 2001 at 02:22:23PM -0800, Peter Wemm wrote: > Personally I would prefer it in src/usr.sbin/sysinstall and have it > dynamically linked. That would be OK, *once* our fdisk/disklable grows some modern [heck even late 1990's] user interface. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 17:44: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id AB26037B402 for ; Thu, 11 Jan 2001 17:43:49 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0C1hjc03519; Thu, 11 Jan 2001 17:43:45 -0800 (PST) Date: Thu, 11 Jan 2001 17:43:45 -0800 From: "'Alfred Perlstein'" To: Glen Gross Cc: Carl Makin , "stable@FreeBSD.ORG" Subject: Re: Running Linux kernel modules. Message-ID: <20010111174345.R7240@fw.wintelcom.net> References: <01C07BF3.695D3780.ggross@symark.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01C07BF3.695D3780.ggross@symark.com>; from ggross@symark.com on Thu, Jan 11, 2001 at 05:24:52PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Glen Gross [010111 17:23] wrote: > Is there a possibility of a generalized interface where any linux kernel module > could be loaded, in the event that the linux emulator were loaded? Or would > this require running the linux kernel in RAM, and therefore running two virtual > machines? please wrap lines at 70 characters. No, the kernel internal structures are pretty different, this would require quite a feat of abstraction to accomplish. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 18: 6:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 81C7837B400 for ; Thu, 11 Jan 2001 18:06:12 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id gqqsaaaa for ; Fri, 12 Jan 2001 13:14:37 +1100 Message-ID: <3A5E66B1.79B24A5C@quake.com.au> Date: Fri, 12 Jan 2001 13:06:41 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Morten Vinding Nielsen Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? References: <2D3005375CAED31199D00008C784963F01C5556A@ms02.mobilix.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morten Vinding Nielsen wrote: > > I haven't noticed any ARP messages. > Don't you mean MAC changing IP address since more than one card have the > same MAC? No, MAC address should be unique for EVERY nic in your local network... In fact it would be fairly hard to get two NICs with the same MAC address unless you were able to change it with some software (which you can)... IP is only for routing, the actual delivery of the data is made to the MAC address, ARP is responsible for converting IP's to MAC's... So you can see having two MAC address's the same on one network would cause all sorts of problems... > Yes Windowz and Linux reads the MAC correctly. > > I have heard of others having the same problem, but getting a MAC address > that differs from mine by a single digit, so I think it might be that the > driver is reading the revision number of the card or something. I found that the latest stable fixed my MAC address problems, but you may have a new one... You should file a PR on it or something, since as you said the driver is reading something wrong and needs updating/fixing To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 18: 9: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 99D6E37B401; Thu, 11 Jan 2001 18:08:40 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id iqqsaaaa for ; Fri, 12 Jan 2001 13:17:14 +1100 Message-ID: <3A5E6748.6897EB28@quake.com.au> Date: Fri, 12 Jan 2001 13:09:12 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Wayne Culver Cc: Daniel O'Connor , freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Gregory Bond Subject: Re: wierd errors References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > > Well, I was also having wierd panics, this will seem unrelated, but I > think I fixed it by upping the io voltage in the BIOS That sounds more like a hardware problem... Often overclocked CPUs need that sort of thing for the devices to work at strange bus speeds... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 20:32:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id E7CCA37B400 for ; Thu, 11 Jan 2001 20:32:21 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id VAA14768; Thu, 11 Jan 2001 21:30:16 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200101120430.VAA14768@freeway.dcfinc.com> Subject: Re: buildworld over nfs failing consistently In-Reply-To: from Daniel O'Connor at "Jan 11, 1 05:49:58 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Thu, 11 Jan 2001 21:30:16 -0700 (MST) Cc: cjclark@alum.mit.edu, stable@FreeBSD.ORG, mvh@ix.netcom.com, Robin_Blanchard@gactr.uga.edu Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition 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 As I recall, Daniel O'Connor wrote: > > Yes, FYI rm -rf /usr/obj/usr ; chflags -R noschg /usr/obj/usr; rm -rf /usr/obj/usr > > is much faster. And, "newfs /obj" is faster yet. :-) -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 20:45:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id D5B1537B400 for ; Thu, 11 Jan 2001 20:44:53 -0800 (PST) Received: (qmail 74322 invoked from network); 12 Jan 2001 04:44:52 -0000 Received: from unknown (HELO arthur.tacni.net) (207.55.167.106) by 216.178.136.168 with SMTP; 12 Jan 2001 04:44:52 -0000 Received: (qmail 292 invoked by uid 1000); 12 Jan 2001 04:44:51 -0000 Date: Thu, 11 Jan 2001 22:44:51 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Interesting plight Message-ID: <20010111224451.A277@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A couple days ago I was mentioning about my ps and top problems. Well at the advice of a FreeBSD user I went and installed the bin distribution for 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and everything was golden. I could ps and top and kill I was one happy guy. Well I cvsup'ed my source tree, and went through the process as is outlined in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish this procedure, and ps and top fail to work. What is wrong? Why will it work on 4.2-RELEASE but not 4.2-STABLE? -- Erich Zigler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 20:48:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 5258837B400 for ; Thu, 11 Jan 2001 20:47:54 -0800 (PST) Received: from bluto.jimking.net (root@bluto.jimking.net [216.54.255.8]) by cgi.sstar.com (8.11.1/8.11.1) with ESMTP id f0C4lo848116 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Thu, 11 Jan 2001 22:47:52 -0600 (CST) (envelope-from jim@jimking.net) Received: from marble (marble.lgc.com [134.132.228.4]) by bluto.jimking.net (8.11.1/8.11.1) with SMTP id f0C4lmo77451; Thu, 11 Jan 2001 22:47:50 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <00ca01c07c52$d1399bf0$04e48486@marble> From: "Jim King" To: "Erich Zigler" , References: <20010111224451.A277@superhero.org> Subject: Re: Interesting plight Date: Thu, 11 Jan 2001 22:47:48 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Erich Zigler" : > A couple days ago I was mentioning about my ps and top problems. Well at the > advice of a FreeBSD user I went and installed the bin distribution for > 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and everything was golden. > I could ps and top and kill I was one happy guy. > > Well I cvsup'ed my source tree, and went through the process as is outlined > in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish this > procedure, and ps and top fail to work. > > What is wrong? > > Why will it work on 4.2-RELEASE but not 4.2-STABLE? It sure sounds like your userland and kernel are out of sync. Are you absolutely sure you're building and installing a new kernel, and that you've rebooted? What's the timestamp on /kernel? Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 20:56:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 9CE3B37B400 for ; Thu, 11 Jan 2001 20:56:19 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id PAA21086; Fri, 12 Jan 2001 15:56:14 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01JYTQ5YH8XSEMXPVS@cim.alcatel.com.au>; Fri, 12 Jan 2001 15:56:22 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0C4uBs88181; Fri, 12 Jan 2001 15:56:11 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Fri, 12 Jan 2001 15:56:11 +1100 From: Peter Jeremy Subject: Re: Intel PRO/100+ driver or hardware? In-reply-to: <3A599400.A5A0CAE1@sigtrap.com>; from desti@sigtrap.com on Mon, Jan 08, 2001 at 10:18:40AM +0000 To: Edvard Fagerholm Cc: "Jeroen C. van Gelderen" , freebsd-stable@FreeBSD.ORG Mail-followup-to: Edvard Fagerholm , "Jeroen C. van Gelderen" , freebsd-stable@FreeBSD.ORG Message-id: <20010112155611.T91029@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <295980000.978920074@grolsch.ai> <3A599400.A5A0CAE1@sigtrap.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-08 10:18:40 +0000, Edvard Fagerholm wrote: >> The other cards connected to the hub are a mixture of 10 and 100 cards >> (3Com 905B, LinkSys LNE100TX, 3Com 509). All of these work fine. > >Funny, as I've got a quite similar problem. During high network >throughput (about 50mbit/s) one of my boxes just dies. This is why it >always crashes when doing backups and I had to put the backup computer >to 10mbit half-duplex mode to get it work... Just to add a further data-point: I have a Dell OptiPlex GXi (Pentium-133 with 96MB RAM) that had 3 genuine PRO/100+ cards. It used to regularly lock up (to the point where NMI had no effect) under load (disk+network+CPU). Replacing the PRO/100+ associated with the multiplexed interrupt with a DEC DE500 (21143) solved the problem. I initially ran into the problem with 3.4-STABLE last February. I can't recall if I re-checked after I installed 4.x on the machine. I wound up switching to feeding all the relevant networks via a VLAN trunk into a single PRO/100+ and haven't had any problems since. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 21: 1:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 5EC5037B400 for ; Thu, 11 Jan 2001 21:01:09 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA10835; Fri, 12 Jan 2001 15:30:46 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010111224451.A277@superhero.org> Date: Fri, 12 Jan 2001 15:30:46 +1030 (CST) From: "Daniel O'Connor" To: Erich Zigler Subject: RE: Interesting plight Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Jan-01 Erich Zigler wrote: > Well I cvsup'ed my source tree, and went through the process as is outlined > in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish this > procedure, and ps and top fail to work. > > What is wrong? There are several possiblities.. 1) You didn't cvsup everything (kernel and userland source) 2) You did cvsup everything OK but didn't build and/or install a new kernel AND userland (ie buildworld, buildkernel, installkernel, installworld) 3) Someone broke stable. I bet its 1 or 2 though :) --- 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 Jan 11 21: 2:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 6500137B401 for ; Thu, 11 Jan 2001 21:02:03 -0800 (PST) Received: (qmail 75493 invoked from network); 12 Jan 2001 05:02:01 -0000 Received: from unknown (HELO arthur.tacni.net) (207.55.167.106) by 216.178.136.168 with SMTP; 12 Jan 2001 05:02:01 -0000 Received: (qmail 466 invoked by uid 1000); 12 Jan 2001 05:01:59 -0000 Date: Thu, 11 Jan 2001 23:01:59 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Re: Interesting plight Message-ID: <20010111230158.A367@superhero.org> References: <20010111224451.A277@superhero.org> <00ca01c07c52$d1399bf0$04e48486@marble> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00ca01c07c52$d1399bf0$04e48486@marble>; from jim@jimking.net on Thu, Jan 11, 2001 at 10:47:48PM -0600 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 10:47:48PM -0600, Jim King wrote: > It sure sounds like your userland and kernel are out of sync. Are you > absolutely sure you're building and installing a new kernel, and that you've > rebooted? What's the timestamp on /kernel? 2040 -r-xr-xr-x 1 root wheel 2073107 Jan 11 22:18 kernel And for an example here is the timestamp taken out of something in /bin 456 -r-xr-xr-x 1 root wheel 457948 Jan 11 21:44 sh And here's modules... 120 -r-xr-xr-x 1 root wheel 114251 Jan 11 22:18 usb.ko Im not running linux proc or anything of that nature and I do have proc compiled into the kernel. -- Erich Zigler I've seen a look in dogs' eyes, a quickly vanishing look of amazed contempt, and I am convinced that basically dogs think humans are nuts. -- John Steinbeck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 21: 5:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from atlas.bit.net.au (atlas.bit.net.au [203.18.94.3]) by hub.freebsd.org (Postfix) with ESMTP id 81B6737B401 for ; Thu, 11 Jan 2001 21:05:41 -0800 (PST) Received: (from pdh@localhost) by atlas.bit.net.au (8.11.0/8.11.0) id f0C55XK13805; Fri, 12 Jan 2001 15:05:33 +1000 Date: Fri, 12 Jan 2001 15:05:33 +1000 From: Phil Homewood To: Erich Zigler Cc: stable@FreeBSD.ORG Subject: Re: Interesting plight Message-ID: <20010112150533.J9290@atlas.bit.net.au> References: <20010111224451.A277@superhero.org> <00ca01c07c52$d1399bf0$04e48486@marble> <20010111230158.A367@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010111230158.A367@superhero.org>; from erichz@superhero.org on Thu, Jan 11, 2001 at 11:01:59PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erich Zigler wrote: > 2040 -r-xr-xr-x 1 root wheel 2073107 Jan 11 22:18 kernel > 456 -r-xr-xr-x 1 root wheel 457948 Jan 11 21:44 sh What does what /kernel show? What steps are you taking to make the world/kernel (and in what order) ? -- Phil Homewood pdh@asiaonline.net Senior Technician +61 7 3620 1930 Asia Online http://www.asiaonline.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 21: 8:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp4.ihug.co.nz (smtp4.ihug.co.nz [203.109.252.5]) by hub.freebsd.org (Postfix) with ESMTP id 03A0137B400 for ; Thu, 11 Jan 2001 21:08:18 -0800 (PST) Received: from spandex (203-173-201-194.nzwide.ihug.co.nz [203.173.201.194]) by smtp4.ihug.co.nz (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id SAA09547; Fri, 12 Jan 2001 18:07:51 +1300 X-Authentication-Warning: smtp4.ihug.co.nz: Host 203-173-201-194.nzwide.ihug.co.nz [203.173.201.194] claimed to be spandex Message-ID: <001701c07c56$24bc0f30$c2c9adcb@spandex> From: "Matthew Luckie" To: Cc: "Jim King" , References: <20010111224451.A277@superhero.org> <00ca01c07c52$d1399bf0$04e48486@marble> Subject: Re: Interesting plight Date: Fri, 12 Jan 2001 18:11:27 +1300 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG additionally, are you sure you explicitly followed the instructions exactly as given in the handbook. I have updated from 4.2-release to stable myself and it works like a dream. make sure that /usr/obj as empty as the handbook suggests, and that you do a make buildworld seperately from a make installworld following that, re config your kernel makefile directory as laid out in the handbook using the new version of config, and then do a make depend make make install in your kernel compilation area (something like) /usr/src/sys/i386/compile/{kernel name} these instructions arent my any stretch of the imagination complete, but if you follow the instructions as laid out by http://www.freebsd.org/handbook/makeworld.html you should be fine. as an aside (and not directed at anyone), i'm surprised at the number of people that mail the stable list quoting updating the system as 'make world' make world went out a while ago, and while it may still work fine, the handbook says make buildworld make installworld so thats what I use and recommend. Matthew Luckie kluckie@ihug.co.nz http://homepages.ihug.co.nz/~kluckie/ ----- Original Message ----- From: Jim King To: Erich Zigler ; Sent: Friday, January 12, 2001 5:47 PM Subject: Re: Interesting plight > "Erich Zigler" : > > > A couple days ago I was mentioning about my ps and top problems. Well at > the > > advice of a FreeBSD user I went and installed the bin distribution for > > 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and everything was > golden. > > I could ps and top and kill I was one happy guy. > > > > Well I cvsup'ed my source tree, and went through the process as is > outlined > > in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish > this > > procedure, and ps and top fail to work. > > > > What is wrong? > > > > Why will it work on 4.2-RELEASE but not 4.2-STABLE? > > It sure sounds like your userland and kernel are out of sync. Are you > absolutely sure you're building and installing a new kernel, and that you've > rebooted? What's the timestamp on /kernel? > > Jim > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 22:35:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 3EA8F37B400 for ; Thu, 11 Jan 2001 22:35:18 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14GxmE-0000nr-00; Fri, 12 Jan 2001 09:33:31 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14Gxnu-0001d6-00; Fri, 12 Jan 2001 09:35:14 +0300 Date: Fri, 12 Jan 2001 09:35:14 +0300 From: Odhiambo Washington To: "Donald J . Maddox" Cc: FBSD-STABLE Subject: Re: 3.X --> 4.X - buildworld fails Message-ID: <20010112093514.B97461@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , "Donald J . Maddox" , FBSD-STABLE References: <20010111211621.A97461@poeza.iconnect.co.ke> <20010111140916.A6874@cae88-102-101.sc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010111140916.A6874@cae88-102-101.sc.rr.com>; from "Donald J . Maddox" on Thu, Jan 11, 2001 at 02:09:16PM -0500 X-Operating-System: FreeBSD poeza.iconnect.co.ke 3.5-STABLE FreeBSD 3.5-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Donald J . Maddox [20010111 22:09]: writing on the subject 'Re: 3.X --> 4.X - buildworld fails' Donald> If you rebuild libc first, it will work. Apparently you are using Donald> a libc from before the addition of the {set,get}res[ug]id calls. Donald> Hi Donald, Thanks for the quick response. Now how do I rebuild libc? I've gone into /usr/src/lib/libc/ and done 'make' but that fails too. Maybe I did the wrong thing??? TIA Donald> On Thu, Jan 11, 2001 at 09:16:21PM +0300, Odhiambo Washington wrote: Donald> > This one is for the gurus: Donald> > Donald> > I am updating a 3.5-S system to 4.X. I've done cvsup with RELENG_4 Donald> > yesterday. Donald> > Now while strictly following the update procedure in UPDATING (and Donald> > referring to the text from the handbook, I get a failure while doing Donald> > make buildworld, viz Donald> > Donald> > cc -O -pipe Donald> > -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/us Donald> > r/obj/usr/src/gnu/usr.bin/perl/miniperl -c opmini.c Donald> > cc -O -pipe Donald> > -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/us Donald> > r/obj/usr/src/gnu/usr.bin/perl/miniperl Donald> > -L/usr/obj/usr/src/gnu/usr.bin/perl/m Donald> > iniperl/../libperl -static -o miniperl miniperlmain.o opmini.o Donald> > /usr/obj/usr/src Donald> > /gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil Donald> > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): Donald> > In fu Donald> > nction `Perl_pp_aassign': Donald> > pp_hot.o(.text+0x16a1): undefined reference to `setresuid' Donald> > pp_hot.o(.text+0x16d4): undefined reference to `setresgid' Donald> > *** Error code 1 Donald> > Stop. Donald> > *** Error code 1 Donald> > Stop. Donald> > *** Error code 1 Donald> > Stop. Donald> > *** Error code 1 Donald> > Stop. Donald> > Donald> > Donald> > I am not sure what this means ;-) but I've replicated it by going into Donald> > /usr/src/gnu/usr.bin/perl and doing a 'make' in there. Donald> > Donald> > I highly appreciate all help that will get me past this one. Donald> > Donald> > TIA Donald> > Donald> > Donald> > -Wash Donald> > Donald> > -- Donald> > Odhiambo Washington Inter-Connect Ltd., Donald> > wash@iconnect.co.ke 5th Flr Furaha Plaza Donald> > Tel: 254 11 222604 Nkrumah Rd., Donald> > Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Donald> > Donald> > Presumably, we're all fully qualified computer nerds here, so we are allowed Donald> > to use "access" as a verb. Be advised, however, that the practice in common Donald> > usage drives English-language purists to scowling fidgets. -Erik Strom, "Perl Donald> > CGI Programming" Donald> > Donald> > Donald> > To Unsubscribe: send mail to majordomo@FreeBSD.org Donald> > with "unsubscribe freebsd-questions" in the body of the message Donald> Donald> Donald> To Unsubscribe: send mail to majordomo@FreeBSD.org Donald> with "unsubscribe freebsd-questions" in the body of the message -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. The last day of school before summer vacation is the shortest day of a mother's year. -Dee Eldrige To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 11 23:37: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 4904537B401 for ; Thu, 11 Jan 2001 23:36:45 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id xsqsaaaa for ; Fri, 12 Jan 2001 18:45:18 +1100 Message-ID: <3A5EB434.865FC56F@quake.com.au> Date: Fri, 12 Jan 2001 18:37:24 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Erich Zigler Cc: stable@freebsd.org Subject: Re: Interesting plight References: <20010111224451.A277@superhero.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erich Zigler wrote: > > A couple days ago I was mentioning about my ps and top problems. Well at the > advice of a FreeBSD user I went and installed the bin distribution for > 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and everything was golden. > I could ps and top and kill I was one happy guy. > > Well I cvsup'ed my source tree, and went through the process as is outlined > in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish this > procedure, and ps and top fail to work. > > What is wrong? > > Why will it work on 4.2-RELEASE but not 4.2-STABLE? This just doesnt make ANY sense... If you really did follow the instructions everything SHOULD work fine, I have cvsup'd many times and so long as you do it by the UPDATING file I have never had any problems (besides new/changed driver issues)... It seems to me that something MUST be out of synch... Make sure your stable-supfile is getting everything... Do the install in single user mode if your not already... Clean out /usr/obj before a build, some of the files you may need to allow deleting on with the chflags command... You are specifying what kernel to build right? make buildkernel KERNEL=GENERIC unless you have a custom kernel then specify that... If you are doing all this, you should try removing all of the /usr/src and /usr/obj and remove the cvsup logs and get everything again... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 3:27:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id 287DB37B400; Fri, 12 Jan 2001 03:27:16 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id LAA59696; Fri, 12 Jan 2001 11:27:14 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101121127.LAA59696@ns.a1.org.uk> Subject: Re: sysinstall.8 Breaking buildworld In-Reply-To: <20010111174332.B74480@dragon.nuxi.com> from "David O'Brien" at "Jan 11, 2001 05:43:32 pm" To: current@FreeBSD.ORG, stable@FreeBSD.ORG Date: Fri, 12 Jan 2001 11:27:13 +0000 (GMT) Reply-To: current@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Why does sysinstall have to move at all? Whenever I buildworld/installworld, I always go into release/sysinstall and do a make all install, as suggested in handbook/makeworld.html Why can't the man page be included and installed with this? Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 4:25:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailgate.abacus.co.uk (mailgate.abacus.co.uk [194.130.48.21]) by hub.freebsd.org (Postfix) with ESMTP id DE76237B401 for ; Fri, 12 Jan 2001 04:25:32 -0800 (PST) Received: from abacus.co.uk (pcantony.bl.abacus.co.uk [194.130.48.111]) by mailgate.abacus.co.uk (8.9.3/8.9.3) with ESMTP id MAA25472 for ; Fri, 12 Jan 2001 12:22:32 GMT Message-ID: <3A5EF7BA.95DA854D@abacus.co.uk> Date: Fri, 12 Jan 2001 12:25:30 +0000 From: Antony T Curtis Organization: Abacus Polar PLC (UK) X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: ** HEADS UP ** C++ threading believed to be fixed References: <6D5097D4B56AD31190D50008C7B1579BC97DD6@exlan5.rjf.com> <20010109103100.A77327@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Tue, Jan 09, 2001 at 01:16:09PM -0500, Ian Cartwright wrote: > > Does this mean a buildworld needs to be done to fix these problems? > > Yes. Any chance of a new point release and a new iso image for those not wanting to cvsup and rebuild? -- ANTONY T CURTIS Tel: +44 (1635) 36222 Abacus Polar Holdings Ltd Fax: +44 (1635) 38670 > Machines certainly can solve problems, store information, correlate, > and play games -- but not with pleasure. >  -- Leo Rosten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 4:29:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailgate.abacus.co.uk (mailgate.abacus.co.uk [194.130.48.21]) by hub.freebsd.org (Postfix) with ESMTP id 0515437B401 for ; Fri, 12 Jan 2001 04:29:26 -0800 (PST) Received: from abacus.co.uk (pcantony.bl.abacus.co.uk [194.130.48.111]) by mailgate.abacus.co.uk (8.9.3/8.9.3) with ESMTP id MAA26933 for ; Fri, 12 Jan 2001 12:26:27 GMT Message-ID: <3A5EF8A5.BC2E0AFD@abacus.co.uk> Date: Fri, 12 Jan 2001 12:29:25 +0000 From: Antony T Curtis Organization: Abacus Polar PLC (UK) X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: Bug in NFSv3 client References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> <200101032308.f03N84f51776@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > Bleh. I'm wrong twice. Don't bother with either patch. The version > is supposed to be 8 bytes. Scrap both patches. > > I'll have to look into this some more. There is definitely some > weirdness in the NFS code. It could be the VATTR_NULL() call on the > server side that is broken. > > -Matt Is FreeBSD's nfsd locking still broken? -- ANTONY T CURTIS Tel: +44 (1635) 36222 Abacus Polar Holdings Ltd Fax: +44 (1635) 38670 > "There was a boy called Eustace Clarence Scrubb, and he almost deserved > it." >  -- C. S. Lewis, The Chronicles of Narnia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 4:33:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailgate.abacus.co.uk (mailgate.abacus.co.uk [194.130.48.21]) by hub.freebsd.org (Postfix) with ESMTP id 7AA4737B401 for ; Fri, 12 Jan 2001 04:32:54 -0800 (PST) Received: from abacus.co.uk (pcantony.bl.abacus.co.uk [194.130.48.111]) by mailgate.abacus.co.uk (8.9.3/8.9.3) with ESMTP id MAA27983; Fri, 12 Jan 2001 12:29:39 GMT Message-ID: <3A5EF964.9EF5A8A4@abacus.co.uk> Date: Fri, 12 Jan 2001 12:32:36 +0000 From: Antony T Curtis Organization: Abacus Polar PLC (UK) X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Antonio Carlos Pina Cc: Jonathan Pennington , freebsd-stable@FreeBSD.ORG Subject: Re: Cannot access certain sites through firewall References: <20010110232117.A10054@coastalgeology.org> <002801c07c18$be357e50$0b6cffc8@infolink.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What works well for me is having the MTU on the tunX interface much smaller than the others - 576 works well. Antonio Carlos Pina wrote: > > I think the problem is your mtu. In fact, I have seen a lot of sites which > have problems with mtu-path-discovery because their admins have DISABLED all > icmp traffic. Sad, but it's true. > > Try to put everything in 1500. > > Best Regards, > > Cordialmente, > Antonio Carlos Pina > Diretor de Tecnologia > INFOLINK Internet > http://www.infolink.com.br > > ----- Original Message ----- > From: "Jonathan Pennington" > To: > Sent: Thursday, January 11, 2001 2:21 AM > Subject: Cannot access certain sites through firewall > > > Hello, > > I am having a problem with accessing certain websites from my internal > > network. > > > > System 4.2-STABLE, Dec-21. PPPoE through tun0 with an external Alcatel > > modem connected to ed1 and an internal network with one windows > > computer and my FreeBSD 4.2-STABLE laptop that can access most > > websites, but not all. www.cityspree.com is the one in the logs, but > > www.signals.com, www.pigglywiggly.com and others are on the list. > > > > I can access everything from the firewall computer, including the > > sites that cannot be accessed from the internal network. The tun0 > > interface is mtu 1492, ed0 (internal) and ed1 (external) were 1500, > > but the same thing happens with all at 1492. (I read in the archives > > about natd mangling packets due to different sizes). From the logs, it > > looks like things are travelling through, but Netscape just > > waits. Specifically, netscape stops at "Connect: Host... contacted. > > Waiting for reply." However, I can ping those address and not loose > > packets. Even when I open the firewall up by flushing all > > rules and allowing everything, theses sites are not working. What am I > > doing wrong? Is this a problem with my natd translation? I am using > > natd unmodified (ie. I set no configs myself), but why would that stop > > only some sites (I can access https). > > > > I'm not on this list, but will watch the geocrawler archives. I > > appreciate any help. Log snippet of attempt to visit www.cityspree.com > > and www.signals.com after successfully pinging signals.com and a copy > > of my firewall rules follow. > > -- ANTONY T CURTIS Tel: +44 (1635) 36222 Abacus Polar Holdings Ltd Fax: +44 (1635) 38670 > One good reason why computers can do more work than people is that they > never have to stop and answer the phone. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 4:52: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id D9C8337B401 for ; Fri, 12 Jan 2001 04:51:47 -0800 (PST) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.1/8.11.0) with ESMTP id f0CCtav85737 for ; Fri, 12 Jan 2001 13:55:36 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Fri, 12 Jan 2001 13:55:36 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: miniperl/perl.;ib problems when buildworld 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 Dear Sirs. Maybe this isn't a recent kind of subject, but I found no posting regarding a problem when building a new world. I freshly installed a system, built a custom kernel, then made a cvsupdate sucking in the newest stuff and then tried to "make buildworld". It failed due an error making lib.perl. I don not have the exact error message, so I have to tell you out of my memory. As I remember myself I think there was a related posting in the past ... sorry, I can not find it. Please give any kind of hint. Thanks a lot ... Oliver - MfG O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 5:47:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id EAAD537B401 for ; Fri, 12 Jan 2001 05:47:34 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0CDlXZ15101 for ; Fri, 12 Jan 2001 14:47:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: stable@freebsd.org Subject: patch for review. From: Poul-Henning Kamp Date: Fri, 12 Jan 2001 14:47:33 +0100 Message-ID: <15099.979307253@critter> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is my MFC candidate for the "/dev/console to syslog" facility. Please test & review on -stable. http://phk.freebsd.dk/patch/mfc_logging.txt -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 6:16:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from orbix.mobilix.dk (orbix.mobilix.dk [212.97.216.244]) by hub.freebsd.org (Postfix) with ESMTP id A832C37B401 for ; Fri, 12 Jan 2001 06:16:37 -0800 (PST) Received: from ms04.mobilix.dk (ms04.mobilix.dk [172.16.1.24]) by orbix.mobilix.dk (8.11.0/8.11.0) with SMTP id f0CEGZP06202 for ; Fri, 12 Jan 2001 15:16:35 +0100 Received: FROM ms07.mobilix.dk BY ms04.mobilix.dk ; Fri Jan 12 15:16:37 2001 +0100 Received: by ms07.mobilix.dk with Internet Mail Service (5.5.2650.21) id ; Fri, 12 Jan 2001 15:16:36 +0100 Message-ID: <2D3005375CAED31199D00008C784963F01C55572@ms02.mobilix.dk> From: Morten Vinding Nielsen To: "'Kal Torak'" Cc: freebsd-stable@FreeBSD.ORG Subject: RE: Intel PRO/100+ driver or hardware? Date: Fri, 12 Jan 2001 15:16:27 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried the card once more, and it is apparently fixed in 4.1-R! Thanks for the good work guys. :) Morten -----Original Message----- From: Kal Torak [mailto:kaltorak@quake.com.au] Sent: 12. januar 2001 03:07 To: Morten Vinding Nielsen Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Intel PRO/100+ driver or hardware? I found that the latest stable fixed my MAC address problems, but you may have a new one... You should file a PR on it or something, since as you said the driver is reading something wrong and needs updating/fixing To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 7: 3: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from picalon.gun.de (unknown [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id AC84637B400; Fri, 12 Jan 2001 07:02:46 -0800 (PST) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id QAA01321; Fri, 12 Jan 2001 16:00:28 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.11.1/8.11.1) id f0CErPG08762; Fri, 12 Jan 2001 15:53:25 +0100 (CET) (envelope-from andreas) Date: Fri, 12 Jan 2001 15:53:25 +0100 From: Andreas Klemm To: Garance A Drosihn Cc: Andreas Klemm , Ilya Martynov , gad@FreeBSD.ORG, apsfilter-current@apsfilter.org, freebsd-stable@FreeBSD.ORG, Garrett Wollman , apsfilter-devel@apsfilter.org Subject: Re: printer spooldirs wrong owner ?? (was Re: Fixes for apsfilter-current-09.12.2000 (printing via smbclient) ) Message-ID: <20010112155325.A8649@titan.klemm.gtn.com> References: <20001214080622.A11433@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drosih@rpi.edu on Thu, Dec 14, 2000 at 06:13:01PM -0500 X-Operating-System: FreeBSD 4.2-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 14, 2000 at 06:13:01PM -0500, Garance A Drosihn wrote: > At 8:06 AM +0100 12/14/00, Andreas Klemm wrote: > >On Wed, Dec 13, 2000 at 03:35:51PM +0300, Ilya Martynov wrote: > > > P.S. I forgot about another problem I meet while setting up > > > printing. SETUP creates smbclient.conf that is not readble > > > by lpd. For me it was created as: > > > > >> -rw------- 1 root daemon 156 Dec 12 16:41 smbclient.conf > >> > >> to make printing work I had to chmod g+r on it. > > > >I think this is an inconsistency in FreeBSD ... > > > >The filterscript (forked by llpd) runs under permissions > >daemon.wheel, but the spooldirs in FreeBSD by default are > >created with permissions root.daemon. > > > >I think this could easily be fixed, if you would > > chown -R dameon.wheel /var/spool/lpd > >and during apsfilter SETUP you should take care that owner > >and group are now setup right to match daemon.wheel. > > > >[ Cc'd to freebsd-stable ] > > > >What do the lpd maintaining authorities in FreeBSD say ? > > I haven't thought about permissions enough to say I have a > strong opinion on it, but my gut-level feeling is that the > spool directories are created with the right owner+group > (ie, root+daemon). > > What I don't understand here is what that has to do with > smbclient.conf. Well, the file contains passwords. So I have to protect it. I thought I could simply "clone" the permissions of the spool directory /var/spool/lpd. On the first glance it looked reasonable. drwxr-xr-x 3 root daemon 512 9 Jan 14:54 /var/spool/lpd So I choosed 600 root.daemon for the smbclient.conf file. But bad luck, the input filter runs with other permissions (other owner -> root) and therefore was unable to read the smbclient config file. When printing a job to a remote printer, you'll also notice, that files are created with owner root ... So, on remote printing you have owner root, whereas a local input filter runs with owner daemon. This confuses me somehow ... It would be fine, if the permissions of the spooldir would reflect owner and group under which lpd *always* runs, including scripts. This would make it easier to understand, what privileges are in use and for script writers it would be easier to choose the proper permissions. On the other hand I don't want you to do changes, that break compatibility in any way ... I'd really appreciate, if people, who know lpd code a little could tell me, if things have to be, as they are or if it would be useful, to have uniq permissions, no matter if we have to deal with remote print jobs or running input filters ... Andreas /// -- Andreas Klemm Apsfilter Homepage http://www.apsfilter.org Support over mailing-lists (only!) http://www.apsfilter.org/support Mailing-list archive http://www.apsfilter.org/Lists-Archives To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 7:13:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from p133.inode.at (p133.inode.at [195.58.160.3]) by hub.freebsd.org (Postfix) with ESMTP id 42E7037B400 for ; Fri, 12 Jan 2001 07:13:29 -0800 (PST) Received: from inode.at (line199.adsl.wien.inode.at [213.229.7.199]) by p133.inode.at (8.11.1/8.10.0.0) with ESMTP id f0CFDRh29889 for ; Fri, 12 Jan 2001 16:13:27 +0100 Message-ID: <3A5F1F43.EE70CB3C@inode.at> Date: Fri, 12 Jan 2001 16:14:11 +0100 From: Michael Bretterklieber X-Mailer: Mozilla 4.75 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: stable@FreeBSD.org Subject: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have problems with my Athlon Thunderbird 700 on an Asus K7M Motherboard (Bios 1009) and FreeBSD 4.2. The system is very very slow, like on an old 386. I have this problems since I updatet from an Athlon 500 to this Athlon Thunderbird 700. I have on the same Harddisk Win98 and Win2K and they work without problems, fast and stable. This situation is disastrous for me, because I had to work under FreeBSD, so I hope, that somebody can help. I tried the Generic-Kernel and my own Kernel-config, but the result was the same. kernel output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #1: Sat Dec 2 21:47:42 CET 2000 root@worf.jawa.at:/usr/src/sys/compile/WORF Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (704.94-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 134152192 (131008K bytes) config> q avail memory = 127262720 (124280K bytes) Preloaded elf kernel "kernel" at 0xc0354000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc035409c. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 5.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 9 chip1: at device 4.4 on pci0 pcm0: port 0xd000-0xd003,0xd400-0xd4ff irq 10 at device 4.5 on pci0 bktr0: mem 0xeddfd000-0xeddfdfff irq 5 at device 14.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 bktr0: Card has no configuration EEPROM. Cannot determine card make. bktr0: Pinnacle/Miro TV, Temic NTSC tuner. pci0: (vendor=0x109e, dev=0x0878) at 14.1 irq 5 sym0: <810a> port 0xd800-0xd8ff mem 0xefffff00-0xefffffff irq 10 at device 15.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using LOAD/STORE-based firmware. de0: port 0xc800-0xc87f mem 0xeffffe80-0xeffffeff irq 9 at device 16.0 on pci0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:99:b5:bf fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP Probing for PnP devices on ppbus0: ppbus0: PCL,MLC,PML lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 joy0 at port 0x201 on isa0 de0: enabling 10baseT port ad0: 29314MB [59560/16/63] at ata0-master UDMA66 ad2: 9641MB [19590/16/63] at ata1-master UDMA33 ad3: 6197MB [12592/16/63] at ata1-slave UDMA33 Waiting 5 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (probe5:sym0:0:5:0): phase change 6-7 6@07e2ef8c resid=4. Mounting root from ufs:/dev/ad0s3a cd0 at sym0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da0 at sym0 bus 0 target 5 lun 0 da0: Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present uhci0: port 0xcc00-0xcc1f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered bye, -- -------------------------------------- E-mail: Michael.Bretterklieber@jawa.at ---------------------------- JAWA MANAGEMENT und SOFTWARE Liebenauer Hauptstr. 200 A-8041 GRAZ Tel: ++43-(0)316-403274-12 Fax: ++43-(0)316-403274-10 GSM: ++43-(0)676-93 96 698 homepage: http://www.jawa.at --------- privat ----------- E-mail: mbretter@inode.at homepage: http://www.inode.at/mbretter -------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 8:11: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 7CC7837B6A5 for ; Fri, 12 Jan 2001 08:10:46 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Jan 2001 16:10:45 +0000 (GMT) Date: Fri, 12 Jan 2001 16:10:44 +0000 From: David Malone To: Michael Bretterklieber Cc: stable@FreeBSD.org Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Message-ID: <20010112161044.A97484@walton.maths.tcd.ie> References: <3A5F1F43.EE70CB3C@inode.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5F1F43.EE70CB3C@inode.at>; from mbretter@inode.at on Fri, Jan 12, 2001 at 04:14:11PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 12, 2001 at 04:14:11PM +0100, Michael Bretterklieber wrote: > I have problems with my Athlon Thunderbird 700 on an Asus K7M > Motherboard > (Bios 1009) and FreeBSD 4.2. > The system is very very slow, like on an old 386. I have this problems > since I updatet from an Athlon 500 to this Athlon Thunderbird 700. I > have on the same Harddisk Win98 and Win2K and they work without > problems, fast and stable. > This situation is disastrous for me, because I had to work under > FreeBSD, so I hope, that somebody can help. I wonder if it could be a problem with the BIOS not setting up the MTRR registers correctly. I have seen problems (on SMP machines) where the BIOS was not setting up the MTRR registers on some of the CPUs weren't caching any of memory. FreeBSD has a work around for this in the SMP case, but maybe not in the single processor case. I'd try looking for a BIOS upgrade, as it may be a problem with the old BIOS not initialising the new processor. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 8:20: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id E3B1137B6A0 for ; Fri, 12 Jan 2001 08:19:43 -0800 (PST) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id EBA0A177EF1; Fri, 12 Jan 2001 10:19:44 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by leviathan.inethouston.net (Postfix) with ESMTP id E0FC31D2F12; Fri, 12 Jan 2001 10:19:44 -0600 (CST) Date: Fri, 12 Jan 2001 10:19:44 -0600 (CST) From: "David W. Chapman Jr." To: David Malone Cc: Michael Bretterklieber , Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 In-Reply-To: <20010112161044.A97484@walton.maths.tcd.ie> 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 had this same motherboard with a 600Mhz. Although I haven't had any other cpu's in it, it didn't seem to run slow for me with the 600 I had in it in either windows98 or FreeBSD. I had the same bios version too. On Fri, 12 Jan 2001, David Malone wrote: > On Fri, Jan 12, 2001 at 04:14:11PM +0100, Michael Bretterklieber wrote: > > > I have problems with my Athlon Thunderbird 700 on an Asus K7M > > Motherboard > > (Bios 1009) and FreeBSD 4.2. > > The system is very very slow, like on an old 386. I have this problems > > since I updatet from an Athlon 500 to this Athlon Thunderbird 700. I > > have on the same Harddisk Win98 and Win2K and they work without > > problems, fast and stable. > > This situation is disastrous for me, because I had to work under > > FreeBSD, so I hope, that somebody can help. > > I wonder if it could be a problem with the BIOS not setting up the > MTRR registers correctly. I have seen problems (on SMP machines) > where the BIOS was not setting up the MTRR registers on some of > the CPUs weren't caching any of memory. FreeBSD has a work around > for this in the SMP case, but maybe not in the single processor > case. > > I'd try looking for a BIOS upgrade, as it may be a problem with > the old BIOS not initialising the new processor. > > David. > > > 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 Fri Jan 12 8:21: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from p133.inode.at (p133.inode.at [195.58.160.3]) by hub.freebsd.org (Postfix) with ESMTP id EE56B37B69C for ; Fri, 12 Jan 2001 08:20:45 -0800 (PST) Received: from inode.at (line199.adsl.wien.inode.at [213.229.7.199]) by p133.inode.at (8.11.1/8.10.0.0) with ESMTP id f0CGKfh03101; Fri, 12 Jan 2001 17:20:41 +0100 Message-ID: <3A5F2F05.FF0D8A4F@inode.at> Date: Fri, 12 Jan 2001 17:21:25 +0100 From: Michael Bretterklieber X-Mailer: Mozilla 4.75 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: David Malone Cc: stable@FreeBSD.org Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone schrieb: > On Fri, Jan 12, 2001 at 04:14:11PM +0100, Michael Bretterklieber wrote: > > > I have problems with my Athlon Thunderbird 700 on an Asus K7M > > Motherboard > > (Bios 1009) and FreeBSD 4.2. > > The system is very very slow, like on an old 386. I have this problems > > since I updatet from an Athlon 500 to this Athlon Thunderbird 700. I > > have on the same Harddisk Win98 and Win2K and they work without > > problems, fast and stable. > > This situation is disastrous for me, because I had to work under > > FreeBSD, so I hope, that somebody can help. > > I wonder if it could be a problem with the BIOS not setting up the > MTRR registers correctly. I have seen problems (on SMP machines) > where the BIOS was not setting up the MTRR registers on some of > the CPUs weren't caching any of memory. FreeBSD has a work around > for this in the SMP case, but maybe not in the single processor > case. > > I'd try looking for a BIOS upgrade, as it may be a problem with > the old BIOS not initialising the new processor. I already upgradet to the latest non-beta BIOS (V1009) for this Motherboard. thanx, -- -------------------------------------- E-mail: Michael.Bretterklieber@jawa.at ---------------------------- JAWA MANAGEMENT und SOFTWARE Liebenauer Hauptstr. 200 A-8041 GRAZ Tel: ++43-(0)316-403274-12 Fax: ++43-(0)316-403274-10 GSM: ++43-(0)676-93 96 698 homepage: http://www.jawa.at --------- privat ----------- E-mail: mbretter@inode.at homepage: http://www.inode.at/mbretter -------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 8:21:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f61.law12.hotmail.com [64.4.19.61]) by hub.freebsd.org (Postfix) with ESMTP id 6E76837B69C for ; Fri, 12 Jan 2001 08:21:35 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 12 Jan 2001 08:21:35 -0800 Received: from 202.208.39.14 by lw12fd.law12.hotmail.msn.com with HTTP; Fri, 12 Jan 2001 16:21:35 GMT X-Originating-IP: [202.208.39.14] From: "hashinoto yoshi" To: freebsd-stable@FreeBSD.org Date: Fri, 12 Jan 2001 16:21:35 -0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp; format=flowed Message-ID: X-OriginalArrivalTime: 12 Jan 2001 16:21:35.0161 (UTC) FILETIME=[BB696290:01C07CB3] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable subscribe cvs-all _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 8:45:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id 24E7E37B69C for ; Fri, 12 Jan 2001 08:45:24 -0800 (PST) Received: from HP2500B (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id C48278C5A; Fri, 12 Jan 2001 10:44:55 -0600 (CST) Message-ID: <009e01c07cb7$132d9e30$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: "Michael Bretterklieber" Cc: References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Date: Fri, 12 Jan 2001 10:45:30 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wasn't aware that they made any Slot A Thuderbird processors. I believe a Thunderbird will only run with the KT133 chipset (or better) or the AMD-760 chipset and not the AMD-750/751 chipset. Are you sure that CPU is what you think it is? Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "David Malone" To: "Michael Bretterklieber" Cc: Sent: Friday, January 12, 2001 10:10 AM Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > On Fri, Jan 12, 2001 at 04:14:11PM +0100, Michael Bretterklieber wrote: > > > I have problems with my Athlon Thunderbird 700 on an Asus K7M > > Motherboard > > (Bios 1009) and FreeBSD 4.2. > > The system is very very slow, like on an old 386. I have this problems > > since I updatet from an Athlon 500 to this Athlon Thunderbird 700. I > > have on the same Harddisk Win98 and Win2K and they work without > > problems, fast and stable. > > This situation is disastrous for me, because I had to work under > > FreeBSD, so I hope, that somebody can help. > > I wonder if it could be a problem with the BIOS not setting up the > MTRR registers correctly. I have seen problems (on SMP machines) > where the BIOS was not setting up the MTRR registers on some of > the CPUs weren't caching any of memory. FreeBSD has a work around > for this in the SMP case, but maybe not in the single processor > case. > > I'd try looking for a BIOS upgrade, as it may be a problem with > the old BIOS not initialising the new processor. > > David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 9: 4:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from danube.mindmaker.com (danube.mindmaker.com [209.66.98.152]) by hub.freebsd.org (Postfix) with ESMTP id 2974737B402 for ; Fri, 12 Jan 2001 09:04:13 -0800 (PST) Received: from hera.int.mindmaker.com (hera.int.mindmaker.com [192.168.10.16]) by danube.mindmaker.com (Postfix) with ESMTP id 9250EF83E; Fri, 12 Jan 2001 09:04:13 -0800 (PST) Received: from mindmaker.com (auth.int.mindmaker.com [192.168.10.15]) by hera.int.mindmaker.com (8.11.1/8.11.1) with ESMTP id f0CH6Vt12321; Fri, 12 Jan 2001 09:06:31 -0800 (PST) (envelope-from bbeck@mindmaker.com) Message-ID: <3A5F3951.9932EED5@mindmaker.com> Date: Fri, 12 Jan 2001 09:05:21 -0800 From: Bernhard Beck X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas T. Veldhouse" Cc: Michael Bretterklieber , stable@FreeBSD.ORG Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG AMD made a few Slot A Thunderbirds. As far as I know they were meant for the OEM market (so that the system integrator has to make sure it works with their environment), but some CPU's made it into retail. There were various incompatibilities with the existing Slot A motherboards. The CPU may work in one Slot A motherboard, but not in others. c't (a german computer magazine) published an article about this last year. Bernhard "Thomas T. Veldhouse" wrote: > > I wasn't aware that they made any Slot A Thuderbird processors. I believe a > Thunderbird will only run with the KT133 chipset (or better) or the AMD-760 > chipset and not the AMD-750/751 chipset. Are you sure that CPU is what you > think it is? > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "David Malone" > To: "Michael Bretterklieber" > Cc: > Sent: Friday, January 12, 2001 10:10 AM > Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > > > On Fri, Jan 12, 2001 at 04:14:11PM +0100, Michael Bretterklieber wrote: > > > > > I have problems with my Athlon Thunderbird 700 on an Asus K7M > > > Motherboard > > > (Bios 1009) and FreeBSD 4.2. > > > The system is very very slow, like on an old 386. I have this problems > > > since I updatet from an Athlon 500 to this Athlon Thunderbird 700. I > > > have on the same Harddisk Win98 and Win2K and they work without > > > problems, fast and stable. > > > This situation is disastrous for me, because I had to work under > > > FreeBSD, so I hope, that somebody can help. > > > > I wonder if it could be a problem with the BIOS not setting up the > > MTRR registers correctly. I have seen problems (on SMP machines) > > where the BIOS was not setting up the MTRR registers on some of > > the CPUs weren't caching any of memory. FreeBSD has a work around > > for this in the SMP case, but maybe not in the single processor > > case. > > > > I'd try looking for a BIOS upgrade, as it may be a problem with > > the old BIOS not initialising the new processor. > > > > David. > > 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 Fri Jan 12 9:19:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from viger.playstos.com (viger.playstos.com [194.79.208.10]) by hub.freebsd.org (Postfix) with ESMTP id 05DCB37B400; Fri, 12 Jan 2001 09:19:21 -0800 (PST) Received: from sunshine (gw2.playstos.com [194.79.208.2]) by viger.playstos.com (Postfix) with SMTP id B67D1D60F9; Fri, 12 Jan 2001 18:19:19 +0100 (CET) From: "Alessandro de Manzano" To: "smp@freebsd.org" Cc: "stable@freebsd.org" Date: Fri, 12 Jan 2001 18:20:18 +0100 Reply-To: "Alessandro de Manzano" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: PR #24059 - USB still broken in SMP ! Message-Id: <20010112171919.B67D1D60F9@viger.playstos.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I've submitted a PR, number 24059, for the problem I still experience in trying to use USB support with a SMP kernel on a 4.2-stable box. I please the maintainers of USB and SMP sections to read my PR :) If someone else is successfull in using USB with SMP kernel please tell me/us ! :-) Thanks a lot! Alessandro de Manzano Playstos - TIMA S.p.A. Corso Sempione 63 20149 Milano, Italy tel.: +39-023314153 fax: +39-02315678 email: demanzano@playstos.com http://www.playstos.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 9:37:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id 27C4B37B401 for ; Fri, 12 Jan 2001 09:37:11 -0800 (PST) Received: from HP2500B (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id BFD6B8C52; Fri, 12 Jan 2001 11:36:42 -0600 (CST) Message-ID: <00d101c07cbe$4f1f84b0$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: "Bernhard Beck" Cc: References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Date: Fri, 12 Jan 2001 11:37:17 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have done alot of looking for one myself - and I have always come back to the conclusion that the cheap internet vendors were just flashing keywords - and when you pressed them on it - you wouldn't get an answer - just an updated web page with Thunderbird removed. I have yet to find an actual Slot A thunderbird. There is an actual architectural difference that won't allow it to run with the current Slot A chipsets. L2 cache related I believe. I am willing to bet good money that Mr. Bretterklieber does NOT have a Thunderbird - but instead a regular Slot A 700 MHz Athlon. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Bernhard Beck" To: "Thomas T. Veldhouse" Cc: "Michael Bretterklieber" ; Sent: Friday, January 12, 2001 11:05 AM Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > AMD made a few Slot A Thunderbirds. As far as I know they were meant for > the OEM market (so that the system integrator has to make sure it works > with their environment), but some CPU's made it into retail. There were > various incompatibilities with the existing Slot A motherboards. The CPU > may work in one Slot A motherboard, but not in others. > c't (a german computer magazine) published an article about this last > year. > > Bernhard > > "Thomas T. Veldhouse" wrote: > > > > I wasn't aware that they made any Slot A Thuderbird processors. I believe a > > Thunderbird will only run with the KT133 chipset (or better) or the AMD-760 > > chipset and not the AMD-750/751 chipset. Are you sure that CPU is what you > > think it is? > > > > Tom Veldhouse > > veldy@veldy.net > > > > ----- Original Message ----- > > From: "David Malone" > > To: "Michael Bretterklieber" > > Cc: > > Sent: Friday, January 12, 2001 10:10 AM > > Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > > > > > On Fri, Jan 12, 2001 at 04:14:11PM +0100, Michael Bretterklieber wrote: > > > > > > > I have problems with my Athlon Thunderbird 700 on an Asus K7M > > > > Motherboard > > > > (Bios 1009) and FreeBSD 4.2. > > > > The system is very very slow, like on an old 386. I have this problems > > > > since I updatet from an Athlon 500 to this Athlon Thunderbird 700. I > > > > have on the same Harddisk Win98 and Win2K and they work without > > > > problems, fast and stable. > > > > This situation is disastrous for me, because I had to work under > > > > FreeBSD, so I hope, that somebody can help. > > > > > > I wonder if it could be a problem with the BIOS not setting up the > > > MTRR registers correctly. I have seen problems (on SMP machines) > > > where the BIOS was not setting up the MTRR registers on some of > > > the CPUs weren't caching any of memory. FreeBSD has a work around > > > for this in the SMP case, but maybe not in the single processor > > > case. > > > > > > I'd try looking for a BIOS upgrade, as it may be a problem with > > > the old BIOS not initialising the new processor. > > > > > > David. > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 9:41: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 06B5F37B400; Fri, 12 Jan 2001 09:40:39 -0800 (PST) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.33 2000/11/21 19:27:27 smothers Exp $) with ESMTP id KAA21067; Fri, 12 Jan 2001 10:40:11 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.14 2001/01/02 18:39:59 steved Exp $) with ESMTP id KAA24293; Fri, 12 Jan 2001 10:40:11 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id MAA25873; Fri, 12 Jan 2001 12:40:10 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14943.16761.965760.182463@hip186.ch.intel.com> Date: Fri, 12 Jan 2001 10:40:09 -0700 (MST) To: "Alessandro de Manzano" Cc: "smp@freebsd.org" , "stable@freebsd.org" Subject: Re: PR #24059 - USB still broken in SMP ! In-Reply-To: <20010112171919.B67D1D60F9@viger.playstos.com> References: <20010112171919.B67D1D60F9@viger.playstos.com> X-Mailer: VM 6.75 under Emacs 20.6.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Friday, January 12, Alessandro de Manzano wrote: ] > > If someone else is successfull in using USB with SMP kernel please tell > me/us ! :-) > > Thanks a lot! Ok. I've got a P2B-DS motherboard (rev 1.06 I believe with the latest BIOS) and I'm running an SMP kernel using two 500Mhz Pentium III's. I use USB to connect to my Canon S10 digital camera all the time. No problems. I've not used USB for anything other than this though--no mice, keyboards, disks, memory readers, etc. But, it does work for me with SMP. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 10: 5:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id DFDC637B69B for ; Fri, 12 Jan 2001 10:05:29 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 479A7177EF1; Fri, 12 Jan 2001 12:05:32 -0600 (CST) Message-ID: <007f01c07cc2$401e4880$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Thomas T. Veldhouse" Cc: "stable" References: <008401c07cb6$f18967a0$3028680a@tgt.com> <000901c07cbc$433f6d60$931576d8@inethouston.net> <00ea01c07cbe$ef398a90$3028680a@tgt.com> <006101c07cbf$394cb4e0$931576d8@inethouston.net> <010301c07cc0$9a772b00$3028680a@tgt.com> <007701c07cc1$05804a80$931576d8@inethouston.net> <011401c07cc1$754d81c0$3028680a@tgt.com> Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Date: Fri, 12 Jan 2001 12:05:30 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG what's not supposed to work on a Slot A? I have a few thunderbird 650 Slot A's, or atleast that's what was on the recipt. I'm still waiting for amd's site to go back up so I can take a look. CPU: AMD Athlon(tm) Processor (656.47-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 I'm not sure, but I think stepping 2 is thunderbird, I'm sure someone with more knowledge could verify that though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 11:22:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 18E3837B404 for ; Fri, 12 Jan 2001 11:22:09 -0800 (PST) Received: (qmail 30304 invoked from network); 12 Jan 2001 19:22:07 -0000 Received: from unknown (HELO arthur.tacni.net) (207.55.167.106) by 216.178.136.168 with SMTP; 12 Jan 2001 19:22:07 -0000 Received: (qmail 7724 invoked by uid 1000); 12 Jan 2001 19:22:03 -0000 Date: Fri, 12 Jan 2001 13:22:03 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Re: Interesting plight Message-ID: <20010112132203.A7616@superhero.org> References: <20010111224451.A277@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from doconnor@gsoft.com.au on Fri, Jan 12, 2001 at 03:30:46PM +1030 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 12, 2001 at 03:30:46PM +1030, Daniel O'Connor wrote: > There are several possiblities.. > 1) You didn't cvsup everything (kernel and userland source) Here is my cvsup file... *default host=cvsup3.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix *default compress src-all This is the configuration I got out of /usr/share/examples/cvsup > 2) You did cvsup everything OK but didn't build and/or install a new kernel AND > userland (ie buildworld, buildkernel, installkernel, installworld) Quite possible. -- Erich Zigler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 11:23:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 0007137B404 for ; Fri, 12 Jan 2001 11:23:16 -0800 (PST) Received: (qmail 30432 invoked from network); 12 Jan 2001 19:23:16 -0000 Received: from unknown (HELO arthur.tacni.net) (207.55.167.106) by 216.178.136.168 with SMTP; 12 Jan 2001 19:23:16 -0000 Received: (qmail 7736 invoked by uid 1000); 12 Jan 2001 19:23:11 -0000 Date: Fri, 12 Jan 2001 13:23:11 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Re: Interesting plight Message-ID: <20010112132311.B7616@superhero.org> References: <20010111224451.A277@superhero.org> <00ca01c07c52$d1399bf0$04e48486@marble> <20010111230158.A367@superhero.org> <20010112150533.J9290@atlas.bit.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010112150533.J9290@atlas.bit.net.au>; from pdh@bit.net.au on Fri, Jan 12, 2001 at 03:05:33PM +1000 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 12, 2001 at 03:05:33PM +1000, Phil Homewood wrote: > > 2040 -r-xr-xr-x 1 root wheel 2073107 Jan 11 22:18 kernel > > 456 -r-xr-xr-x 1 root wheel 457948 Jan 11 21:44 sh > What does > what /kernel > show? I dont understand the question. > What steps are you taking to make the world/kernel (and in what > order) ? make buildworld make buildkernel KERNEL=NEWKERNEL make installworld make installkernel KERNEL=NEWKERNEL mergemaster reboot -- Erich Zigler Death before decaf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 11:24:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from monterosa.urbanet.ch (monterosa.urbanet.ch [195.202.193.104]) by hub.freebsd.org (Postfix) with SMTP id 19DCE37B402 for ; Fri, 12 Jan 2001 11:24:28 -0800 (PST) Received: (qmail 16526 invoked from network); 12 Jan 2001 19:24:16 -0000 Received: from unknown (HELO Node07.urbanet.ch) (194.38.75.24) by monterosa.urbanet.ch with SMTP; 12 Jan 2001 19:24:16 -0000 Message-Id: <4.3.2.20010112201948.00be8210@node06.urbanet.ch> X-Sender: urba4737@mail.urbanet.ch (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Fri, 12 Jan 2001 20:24:15 +0100 To: "David W. Chapman Jr." , "Thomas T. Veldhouse" From: Francois E Jaccard Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Cc: "stable" In-Reply-To: <007f01c07cc2$401e4880$931576d8@inethouston.net> References: <008401c07cb6$f18967a0$3028680a@tgt.com> <000901c07cbc$433f6d60$931576d8@inethouston.net> <00ea01c07cbe$ef398a90$3028680a@tgt.com> <006101c07cbf$394cb4e0$931576d8@inethouston.net> <010301c07cc0$9a772b00$3028680a@tgt.com> <007701c07cc1$05804a80$931576d8@inethouston.net> <011401c07cc1$754d81c0$3028680a@tgt.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12/01/2001 19:05, David W. Chapman Jr. wrote: >what's not supposed to work on a Slot A? I have a few thunderbird 650 Slot >A's, or atleast that's what was on the recipt. I'm still waiting for amd's >site to go back up so I can take a look. > >CPU: AMD Athlon(tm) Processor (656.47-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 > >I'm not sure, but I think stepping 2 is thunderbird, I'm sure someone with >more knowledge could verify that though. > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message Hi, my Athlon 1Gz slot A is detected like this: CPU: AMD Athlon(tm) Processor (1000.04-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x622 Stepping = 2 Features=0x183f9ff AMD Features=0xc0400000 This is also a setting 2. Maybe Id 0x642 is Thunderbird and 0x622 is Athlon... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 11:37:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.catseye.net (dsl-64-34-131-193.telocity.com [64.34.131.193]) by hub.freebsd.org (Postfix) with SMTP id 290DC37B401 for ; Fri, 12 Jan 2001 11:37:09 -0800 (PST) Received: (qmail 17678 invoked by uid 1001); 12 Jan 2001 19:37:04 -0000 Date: Fri, 12 Jan 2001 13:37:04 -0600 From: Timothy Legant To: stable@freebsd.org Subject: Re: Interesting plight Message-ID: <20010112133703.A17573@mail.catseye.net> Mail-Followup-To: stable@freebsd.org References: <20010111224451.A277@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010111224451.A277@superhero.org>; from erichz@superhero.org on Thu, Jan 11, 2001 at 10:44:51PM -0600 X-Editor: Vim (http://www.vim.org/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 11, 2001 at 10:44:51PM -0600, Erich Zigler wrote: > A couple days ago I was mentioning about my ps and top problems. Well > at the advice of a FreeBSD user I went and installed the bin > distribution for 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and > everything was golden. I could ps and top and kill I was one happy > guy. > > Well I cvsup'ed my source tree, and went through the process as is > outlined in /usr/src/UPDATING of updating my source tree to > 4.2-STABLE. I finish this procedure, and ps and top fail to work. > > What is wrong? I went back and looked at your first email about ps and top. You listed there the following steps, which you claimed are outlined in UPDATING: make buildworld make installworld make buildkernel KERNEL= make installkernel KERNEL= However, that it not what UPDATING says at all. Maybe you mistyped what you actually did? If not, and you really did perform the above steps exactly as you wrote, then your kernel and userland are out of sync. Try the following (assuming a successful cvsup): rm -r /usr/obj/ # get rid of already compiled stuff cd /usr/src make buildworld # compile the world make buildkernel KERNEL=GENERIC # compile a kernel (you must specify one, # so start with GENERIC make installkernel KERNEL=GENERIC # install the GENERIC kernel now reboot into single-user mode and then... cd /usr/src make installworld # install the world mergemaster # merge your config files, etcetera If these steps (in this order!) are what you've already done, let us know. Otherwise, do them exactly in this order and you will have the same version kernel and userland. Good luck. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 11:51:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 35D4037B400; Fri, 12 Jan 2001 11:51:00 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14HADu-0006gX-00; Fri, 12 Jan 2001 19:50:54 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f0CJor400440; Fri, 12 Jan 2001 19:50:53 GMT (envelope-from jcm) Date: Fri, 12 Jan 2001 19:50:53 +0000 From: j mckitrick To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: question for parallel port users Message-ID: <20010112195053.A421@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone out there have any parallel port peripherals that work with the port set in ECP mode under 4.x? thanks, jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | ~~~~~~~~~~~~ Jonathon McKitrick ~~~~~~~~~~~~~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 11:55: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id E5CCF37B400 for ; Fri, 12 Jan 2001 11:54:42 -0800 (PST) Received: (qmail 32559 invoked from network); 12 Jan 2001 19:54:41 -0000 Received: from unknown (HELO arthur.tacni.net) (207.55.167.106) by 216.178.136.168 with SMTP; 12 Jan 2001 19:54:41 -0000 Received: (qmail 12301 invoked by uid 1000); 12 Jan 2001 19:54:36 -0000 Date: Fri, 12 Jan 2001 13:54:36 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Re: Interesting plight Message-ID: <20010112135436.A12202@superhero.org> References: <20010111224451.A277@superhero.org> <20010112133703.A17573@mail.catseye.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010112133703.A17573@mail.catseye.net>; from list-freebsd-stable@catseye.net on Fri, Jan 12, 2001 at 01:37:04PM -0600 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 12, 2001 at 01:37:04PM -0600, Timothy Legant wrote: > If these steps (in this order!) are what you've already done, let us > know. Otherwise, do them exactly in this order and you will have the > same version kernel and userland. Yeah I realized one of my mistakes was I at one time was doing make installworld before make buildkernel/installkernel. I rectified this, but am still having the same problems. -- Erich Zigler This 'telephone' has too many shortcomings to be seriously considered as a means of communication. The device is inherently of no value to us. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 12:36: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from libero.sunshine.ale (ppp-225-113.33-151.iol.it [151.33.113.225]) by hub.freebsd.org (Postfix) with ESMTP id 594C837B401; Fri, 12 Jan 2001 12:35:48 -0800 (PST) Received: by libero.sunshine.ale (Postfix, from userid 1001) id B76ED5F2A; Fri, 12 Jan 2001 21:36:10 +0100 (CET) Date: Fri, 12 Jan 2001 21:36:10 +0100 From: Alessandro de Manzano To: John Reynolds~ Cc: Alessandro de Manzano , "smp@freebsd.org" , "stable@freebsd.org" Subject: Re: PR #24059 - USB still broken in SMP ! Message-ID: <20010112213610.E615@libero.sunshine.ale> Reply-To: Alessandro de Manzano References: <20010112171919.B67D1D60F9@viger.playstos.com> <14943.16761.965760.182463@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14943.16761.965760.182463@hip186.ch.intel.com>; from jreynold@sedona.ch.intel.com on Fri, Jan 12, 2001 at 10:40:09AM -0700 X-Operating-System: FreeBSD 4.2-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok. I've got a P2B-DS motherboard (rev 1.06 I believe with the latest BIOS) > and I'm running an SMP kernel using two 500Mhz Pentium III's. I use USB to > connect to my Canon S10 digital camera all the time. No problems. I've not > used USB for anything other than this though--no mice, keyboards, disks, > memory readers, etc. Thanks for the answer ! :-) I'm happy to hear USB works for you, so I could only guess some things: 1) we have different USB controllers, the Asus P2B-DS (a MB I have where I work) use Intel chipset and my Microstar MS-6321 use an VIA one. 2) I tried with the mouse only, also if error reports are reported by kernel also if the USB bus is "empty" and idle. I really hope my problem could be resolved in a future evoltion of USB drivers.. ;-) Thanks a lot! -- bye! Ale aledema@iol.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 12:42:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 2270B37B402; Fri, 12 Jan 2001 12:42:26 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 16F93198B; Fri, 12 Jan 2001 15:42:24 -0500 (EST) Date: Fri, 12 Jan 2001 15:42:24 -0500 From: Will Andrews To: electro Cc: FreeBSD Stable Subject: Re: Bug in src tree? Message-ID: <20010112154224.E471@puck.firepipe.net> Reply-To: Will Andrews References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from electro_p@hotmail.com on Fri, Jan 12, 2001 at 08:17:01AM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ .. moved to -stable .. ] On Fri, Jan 12, 2001 at 08:17:01AM +0100, electro wrote: > I try to compile a new kernel with the latest source and I always end up > with this (in the end). Any suggestions? > I mean the error message is fun...dont match any know i386 instruction???? [...] > /tmp/ccmJEqq7.s:758: Error: operands given don't match any known 386 > instruction > /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 > instruction [...] You appear to be upgrading from a very old version of FreeBSD. The last time I encountered this was when binutils was upgraded in 4.x-STABLE around July or August 2000. In any case that means (most likely) that you may need to install the newer binutils manually before compiling. -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 13: 1:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mother.ludd.luth.se (mother.ludd.luth.se [130.240.16.3]) by hub.freebsd.org (Postfix) with ESMTP id 6C4D437B400 for ; Fri, 12 Jan 2001 13:01:04 -0800 (PST) Received: from speedy.ludd.luth.se (speedy.ludd.luth.se [130.240.16.164]) by mother.ludd.luth.se (8.9.3+Sun/8.9.3) with ESMTP id WAA26480; Fri, 12 Jan 2001 22:00:43 +0100 (MET) Date: Fri, 12 Jan 2001 22:00:39 +0100 (CET) From: hubbe snubbe To: Will Andrews Cc: electro , FreeBSD Stable Subject: Re: Bug in src tree? In-Reply-To: <20010112154224.E471@puck.firepipe.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 I have corrected that and sucessfully made make kernerlbuild but I seems to have problem with make world. Is there some where I can get the 4.2release source? and compile it and install my own kernel from the begining(I get system crash with generic 4.2 kernel). On Fri, 12 Jan 2001, Will Andrews wrote: > [ .. moved to -stable .. ] > > On Fri, Jan 12, 2001 at 08:17:01AM +0100, electro wrote: > > I try to compile a new kernel with the latest source and I always end up > > with this (in the end). Any suggestions? > > I mean the error message is fun...dont match any know i386 instruction???? > [...] > > /tmp/ccmJEqq7.s:758: Error: operands given don't match any known 386 > > instruction > > /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 > > instruction > [...] > > You appear to be upgrading from a very old version of FreeBSD. The last > time I encountered this was when binutils was upgraded in 4.x-STABLE > around July or August 2000. In any case that means (most likely) that > you may need to install the newer binutils manually before compiling. > > -- > wca > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------------------------------------------------------- http://www.ludd.luth.se/~electro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 13:39:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mindcrime.bit0.com (mindcrime.bit0.com [216.7.69.69]) by hub.freebsd.org (Postfix) with ESMTP id 3AFB337B402 for ; Fri, 12 Jan 2001 13:38:59 -0800 (PST) Received: from localhost (mandrews@localhost) by mindcrime.bit0.com (8.11.1/8.11.1) with ESMTP id f0CLYbp86417; Fri, 12 Jan 2001 16:34:38 -0500 (EST) (envelope-from mandrews@bit0.com) Date: Fri, 12 Jan 2001 16:34:37 -0500 (EST) From: Mike Andrews To: Mark.Andrews@nominum.com Cc: stable@FreeBSD.ORG Subject: Re: Weird sporadic DNS resolution problems In-Reply-To: <200101120102.f0C12X863536@drugs.dv.isc.org> 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, 12 Jan 2001 Mark.Andrews@nominum.com wrote: > > When one (but not both) of the nameservers for a domain replies > > non-authoritatively, named will cache a negative response, rather than > > asking the other nameserver. > > No. It caches that the server is lame for the zone then tries > other servers. > > > Subsequent lookups return an immediate > > failure. > > And what is logged when that happens? At the time of those lookups, nothing from Bind. Sendmail logs "Domain of sender address foo@bar does not resolve". When it caches that the server is lame, bind does log the expected "Lame server on foo.blah" message. > > Restarting the nameserver, and then immediately querying the > > same problematic domain DOES work, but only the first query. After a few > > minutes/hours the domain stops working again. > > This sounds more like a bad delegation, parent and child > zones dissagreeing on the nameserver RRset, than a lame > server. > Servers are supposed to be serving the zone *before* they are > delegated to. Either way, the other guys have their nameserver screwed up pretty badly. I knew this already, though... > Well both the servers for setel.com are lame as are se-tel.com. > > If all the sources of information are bad what do you expect > the namesever to do. Hm. My named thinks ns2.se-tel.com is definitely lame, but not ns1 (at least it's never logging ns1 as lame...) > > In one sense this is "not my problem" because their name server shouldn't > > be answering non-authoritatively in the first place. But the fact that > > this started happening after a make world a few months ago, and that I > > feel it should be a slight bit more tolerant of other people's sloppy > > configurations, makes it my problem. And this is the real question that remains: Why did receiving email from places with one lame and one not-lame nameserver work reliably in 4.1.1-RELEASE, and not in 4.2-STABLE? I realize (like in the farmersfrankfort.com) case that it's Qwest's problem (not mine) that the second nameserver for that domain is lame. But in 4.1.1-RELEASE it would still eventually get the right info from the one that did work. It doesn't anymore. What changed in Bind or Sendmail to make it less tolerant of everyone else's broken nameservers? I'm starting to wonder, like Mike Tancsa's earlier response, if this is maybe specific to Sendmail, or a Bind+Sendmail interaction... Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet access for Frankfort, Lexington, Louisville and surrounding counties www.fark.com: If it's not news, it's Fark. (Or something like that.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 14:28:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by hub.freebsd.org (Postfix) with ESMTP id 09A7037B401 for ; Fri, 12 Jan 2001 14:28:41 -0800 (PST) Received: from [216.64.45.172] (helo=[192.168.99.123]) by hobbiton.shire.net with esmtp (Exim 2.04 #5) id 14HCga-000DUD-00 for freebsd-stable@freebsd.org; Fri, 12 Jan 2001 15:28:41 -0700 Date: Fri, 12 Jan 2001 17:21:13 -0500 From: "Chad Leigh, Pengar Enterprises, Inc & Shire.Net LLC" Reply-To: chad@pengar.com To: freebsd-stable@freebsd.org Subject: 4.2-RELEASE ld-elf problem Message-ID: <67529996.979320073@[192.168.99.123]> X-Mailer: Mulberry/2.0.5 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========67549957==========" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==========67549957========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi I just upgraded by doing an upgrade install from 4.0-RELEASE to = 4.2-RELEASE. Now, the dirname and basename programs don't work correctly. I get /usr/libexec/ld-elf.so.1: basename: Undefined symbol "basename" (and the dirname equivalent) whenever they are used (like installing ports or compiling apps). It appears I have a missing library or ldconfig is screwed up or something. But I don't know where to start. Any hints appreciated. thanks Chad Pengar Enterprises, Inc. and Shire.Net LLC Web and Macintosh Consulting -- full service web hosting Chad Leigh chad@pengar.com chad@shire.net --==========67549957========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: Mulberry PGP Plugin v2.0 Comment: processed by Mulberry PGP Plugin iQA/AwUBOl+DWTrujlJKZPK5EQK5VgCg1moQXdPtcVVqfndK2CEUEi3cau0AoIph 8jgFKrM7kow/rPRxWtIlfYcr =4wfx -----END PGP SIGNATURE----- --==========67549957==========-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 15:39:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from danube.mindmaker.com (danube.mindmaker.com [209.66.98.152]) by hub.freebsd.org (Postfix) with ESMTP id 63E9737B401 for ; Fri, 12 Jan 2001 15:39:25 -0800 (PST) Received: from hera.int.mindmaker.com (hera.int.mindmaker.com [192.168.10.16]) by danube.mindmaker.com (Postfix) with ESMTP id 1C19DF843; Fri, 12 Jan 2001 15:39:27 -0800 (PST) Received: from mindmaker.com (host133.int.mindmaker.com [192.168.10.133]) by hera.int.mindmaker.com (8.11.1/8.11.1) with ESMTP id f0CNg2Y00493; Fri, 12 Jan 2001 15:42:03 -0800 (PST) (envelope-from bbeck@mindmaker.com) Message-ID: <3A5F95AF.F8B120D4@mindmaker.com> Date: Fri, 12 Jan 2001 15:39:27 -0800 From: Bernhard Beck Organization: Mindmaker, Inc. X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas T. Veldhouse" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to an article published in c't 14/2000, page 32 (online at http://www.heise.de/ct/00/14/032/default.shtml, use Altavista's Babelfish to translate), Slot A Thunderbirds do exist. In a nutshell among other things AMD slightly changed the bus interface design on the Thunderbirds so that you need chipsets like VIA KT133, KM133 or AMD 760. But under certain conditions the Thunderbird can also work with a KX133 or the Irongate chipset. There is a nice table at the end of the article listing a few Slot A motherboards and if they worked or not with the two sample Slot A Thunderbirds c't had available in their lab at that time. Michael's Asus K7M with Irongate chipset is listed as working with the exact same BIOS version. However, your milage may vary depending on your CPU. The T-Bird was not designed to be used in Slot A with any motherboard. AMD apparently made them only as a concession to their OEMs. What confuses me, though, is why the CPU works with normal speed in Windows 2000. Michael, maybe try booting with a SMP kernel (?) Bernhard "Thomas T. Veldhouse" wrote: > > I have done alot of looking for one myself - and I have always come back to > the conclusion that the cheap internet vendors were just flashing keywords - > and when you pressed them on it - you wouldn't get an answer - just an > updated web page with Thunderbird removed. I have yet to find an actual > Slot A thunderbird. There is an actual architectural difference that won't > allow it to run with the current Slot A chipsets. L2 cache related I > believe. I am willing to bet good money that Mr. Bretterklieber does NOT > have a Thunderbird - but instead a regular Slot A 700 MHz Athlon. > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "Bernhard Beck" > To: "Thomas T. Veldhouse" > Cc: "Michael Bretterklieber" ; > Sent: Friday, January 12, 2001 11:05 AM > Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > > > AMD made a few Slot A Thunderbirds. As far as I know they were meant for > > the OEM market (so that the system integrator has to make sure it works > > with their environment), but some CPU's made it into retail. There were > > various incompatibilities with the existing Slot A motherboards. The CPU > > may work in one Slot A motherboard, but not in others. > > c't (a german computer magazine) published an article about this last > > year. > > > > Bernhard > > > > "Thomas T. Veldhouse" wrote: > > > > > > I wasn't aware that they made any Slot A Thuderbird processors. I > believe a > > > Thunderbird will only run with the KT133 chipset (or better) or the > AMD-760 > > > chipset and not the AMD-750/751 chipset. Are you sure that CPU is what > you > > > think it is? > > > > > > Tom Veldhouse > > > veldy@veldy.net > > > > > > ----- Original Message ----- > > > From: "David Malone" > > > To: "Michael Bretterklieber" > > > Cc: > > > Sent: Friday, January 12, 2001 10:10 AM > > > Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD > 4.2 > > > > > > > On Fri, Jan 12, 2001 at 04:14:11PM +0100, Michael Bretterklieber > wrote: > > > > > > > > > I have problems with my Athlon Thunderbird 700 on an Asus K7M > > > > > Motherboard > > > > > (Bios 1009) and FreeBSD 4.2. > > > > > The system is very very slow, like on an old 386. I have this > problems > > > > > since I updatet from an Athlon 500 to this Athlon Thunderbird 700. > I > > > > > have on the same Harddisk Win98 and Win2K and they work without > > > > > problems, fast and stable. > > > > > This situation is disastrous for me, because I had to work under > > > > > FreeBSD, so I hope, that somebody can help. > > > > > > > > I wonder if it could be a problem with the BIOS not setting up the > > > > MTRR registers correctly. I have seen problems (on SMP machines) > > > > where the BIOS was not setting up the MTRR registers on some of > > > > the CPUs weren't caching any of memory. FreeBSD has a work around > > > > for this in the SMP case, but maybe not in the single processor > > > > case. > > > > > > > > I'd try looking for a BIOS upgrade, as it may be a problem with > > > > the old BIOS not initialising the new processor. > > > > > > > > David. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 16: 6:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from danube.mindmaker.com (danube.mindmaker.com [209.66.98.152]) by hub.freebsd.org (Postfix) with ESMTP id 76E7A37B404; Fri, 12 Jan 2001 16:06:18 -0800 (PST) Received: from hera.int.mindmaker.com (hera.int.mindmaker.com [192.168.10.16]) by danube.mindmaker.com (Postfix) with ESMTP id CC609F843; Fri, 12 Jan 2001 16:06:19 -0800 (PST) Received: from mindmaker.com (joe2000.int.mindmaker.com [192.168.10.49]) by hera.int.mindmaker.com (8.11.1/8.11.1) with ESMTP id f0D08tY00640; Fri, 12 Jan 2001 16:08:55 -0800 (PST) (envelope-from jfilla@mindmaker.com) Message-ID: <3A5F9BFB.9C24C85F@mindmaker.com> Date: Fri, 12 Jan 2001 16:06:19 -0800 From: Joseph Filla Organization: Mindmaker Inc. X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: vinum create causes my 4.2-Stable SMP machine to reboot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG System information: 4.2-STABLE FreeBSD 4.2-STABLE #3: Wed Dec 6 17:46:52 PST 2000 SMP 2 Promise ATA66 controllers 4 IDE drives: ad4 ad6 ad8 ad10 All dangerously dedicated For the last few months, I have had vinum running in a raid 10 configuration: su-2.03# vinum list 4 drives: D a State: up Device /dev/ad4s1e Avail: 0/11500 MB (0%) D b State: up Device /dev/ad6s1e Avail: 0/11500 MB (0%) D c State: up Device /dev/ad8s1f Avail: 0/11500 MB (0%) D d State: up Device /dev/ad10s1f Avail: 0/11500 MB (0%) 4 volumes: V swap State: up Plexes: 2 Size: 649 MB V var State: up Plexes: 2 Size: 1999 MB V usr State: up Plexes: 2 Size: 1999 MB V home State: up Plexes: 2 Size: 17 GB 8 plexes: P swap.p0 S State: up Subdisks: 2 Size: 649 MB P swap.p1 S State: up Subdisks: 2 Size: 649 MB P var.p0 S State: up Subdisks: 2 Size: 1999 MB P var.p1 S State: up Subdisks: 2 Size: 1999 MB P usr.p0 S State: up Subdisks: 2 Size: 1999 MB P usr.p1 S State: up Subdisks: 2 Size: 1999 MB P home.p0 S State: up Subdisks: 2 Size: 17 GB P home.p1 S State: up Subdisks: 2 Size: 17 GB 16 subdisks: S swap.p0.s0 State: up PO: 0 B Size: 324 MB S swap.p0.s1 State: up PO: 257 kB Size: 324 MB S swap.p1.s0 State: up PO: 0 B Size: 324 MB S swap.p1.s1 State: up PO: 257 kB Size: 324 MB S var.p0.s0 State: up PO: 0 B Size: 999 MB S var.p0.s1 State: up PO: 257 kB Size: 999 MB S var.p1.s0 State: up PO: 0 B Size: 999 MB S var.p1.s1 State: up PO: 257 kB Size: 999 MB S usr.p0.s0 State: up PO: 0 B Size: 999 MB S usr.p0.s1 State: up PO: 257 kB Size: 999 MB S usr.p1.s0 State: up PO: 0 B Size: 999 MB S usr.p1.s1 State: up PO: 257 kB Size: 999 MB S home.p0.s0 State: up PO: 0 B Size: 9174 MB S home.p0.s1 State: up PO: 257 kB Size: 9174 MB S home.p1.s0 State: up PO: 0 B Size: 9174 MB S home.p1.s1 State: up PO: 257 kB Size: 9174 MB After a few months of use on this box, I decided to use the remaining free space on the drives by creating another raid 10 volume. Through Sysinstall, I created a partition on each of the four drives, and changed the disklabels on all 4 new partitions to type vinum. I created another vinum config file vinum_home2.conf: drive e device /dev/ad4s1f drive f device /dev/ad6s1f drive g device /dev/ad8s1g drive h device /dev/ad10s1g volume home2 plex org striped 257k sd length 7705m drive e sd length 7705m drive f plex org striped 257k sd length 7705m drive g sd length 7705m drive h I know putting another volume on another partition in the same slice isn't optimal but I don't have any other drives. I ran 'vinum create /etc/vinum_home2.conf' and the machine rebooted. vinum_history doesn't show the the create command at all. The system rebooted into single user mode and I was eventually able to get back to a running system. vinum -l showed the new volume home2, the new plexes and the new subdisks but after running init and start, I could never get the subdisks past faulty. One of the striped plexes was always in state crashed. I eventually had to detach and rm all remnants of home2 and got my system back to the original state. Thinking I may have done something incorrectly, I retried the vinum create config and the system rebooted again. This time vinum_history recorded the following: 12 Jan 2001 14:05:27.960421 *** vinum started *** 12 Jan 2001 14:05:27.961106 create vinum_home2.conf 12 Jan 2001 14:05:37.293978 *** vinum started *** 12 Jan 2001 14:12:43.507023 *** vinum started *** 12 Jan 2001 14:12:44.694607 l ... This time the system came backup correctly, however this time, running vinum -l show me nothing regarding my desired volume home2. Here is the relevant stuff from /var/log/messages: Jan 10 16:03:34 hera /kernel: vinum: loaded Jan 10 16:03:34 hera /kernel: vinum: reading configuration from /dev/ad8s1f Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad10s1f Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad4s1e Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad6s1e Jan 12 14:05:37 hera /kernel: vinum: drive e is up Jan 12 14:05:37 hera /kernel: vinum: drive f is up Jan 12 14:05:37 hera /kernel: vinum: drive g is up Jan 12 14:05:37 hera /kernel: vinum: drive h is up Jan 12 14:10:37 hera /kernel: vinum: loaded Jan 12 14:10:37 hera /kernel: vinum: reading configuration from /dev/ad8s1f Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad10s1f Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad6s1e Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad4s1e Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad6s1f Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad6s1f is down Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad6s1f, error 5 Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad8s1g Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad8s1g is down Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad8s1g, error 5 Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad4s1f Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad4s1f is down Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad4s1f, error 5 Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad10s1g Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad10s1g is down Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad10s1g, error 5 Jan 12 14:10:37 hera /kernel: vinum: couldn't read configuration Neither reboots created any dumps in /var/crash Any advice? -- Joe Filla Systems Administrator Mindmaker, Inc. (408) 467-0468 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 16:31:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id A4B1F37B401; Fri, 12 Jan 2001 16:31:16 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id C0CB76ABFF; Sat, 13 Jan 2001 11:01:11 +1030 (CST) Date: Sat, 13 Jan 2001 11:01:11 +1030 From: Greg Lehey To: Joseph Filla Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: vinum create causes my 4.2-Stable SMP machine to reboot Message-ID: <20010113110111.B66238@wantadilla.lemis.com> References: <3A5F9BFB.9C24C85F@mindmaker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5F9BFB.9C24C85F@mindmaker.com>; from jfilla@mindmaker.com on Fri, Jan 12, 2001 at 04:06:19PM -0800 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] Please don't wrap log output. On Friday, 12 January 2001 at 16:06:19 -0800, Joseph Filla wrote: > System information: > 4.2-STABLE FreeBSD 4.2-STABLE #3: Wed Dec 6 17:46:52 PST 2000 > SMP > 2 Promise ATA66 controllers > 4 IDE drives: > ad4 > ad6 > ad8 > ad10 > All dangerously dedicated > > > For the last few months, I have had vinum running in a raid 10 > configuration: > > su-2.03# vinum list > 4 drives: > D a State: up Device /dev/ad4s1e Avail: 0/11500 MB (0%) > D b State: up Device /dev/ad6s1e Avail: 0/11500 MB (0%) > D c State: up Device /dev/ad8s1f Avail: 0/11500 MB (0%) > D d State: up Device /dev/ad10s1f Avail: 0/11500 MB (0%) > > 4 volumes: > V swap State: up Plexes: 2 Size: 649 MB > V var State: up Plexes: 2 Size: 1999 MB > V usr State: up Plexes: 2 Size: 1999 MB > V home State: up Plexes: 2 Size: 17 GB > > > > After a few months of use on this box, I decided to use the remaining > free space on the drives by creating another raid 10 volume. Through > Sysinstall, I created a partition on each of the four drives, and > changed the disklabels on all 4 new partitions to type vinum. > > I created another vinum config file vinum_home2.conf: > drive e device /dev/ad4s1f > drive f device /dev/ad6s1f > drive g device /dev/ad8s1g > drive h device /dev/ad10s1g > > volume home2 > plex org striped 257k > sd length 7705m drive e > sd length 7705m drive f > plex org striped 257k > sd length 7705m drive g > sd length 7705m drive h > > I know putting another volume on another partition in the same slice > isn't optimal but I don't have any other drives. You really need to make that a single partition. But that shouldn't be the problem. > I ran 'vinum create /etc/vinum_home2.conf' and the machine rebooted. Spontaneously, with no messages? > vinum_history doesn't show the the create command at all. No, it wouldn't. You had a crash. > The system rebooted into single user mode and I was eventually able > to get back to a running system. vinum -l showed the new volume > home2, the new plexes and the new subdisks but after running init > and start, I could never get the subdisks past faulty. One of the > striped plexes was always in state crashed. Where's the list? > I eventually had to detach and rm all remnants of home2 and got my > system back to the original state. Thinking I may have done > something incorrectly, I retried the vinum create config and the > system rebooted again. This time vinum_history recorded the > following: > > 12 Jan 2001 14:05:27.960421 *** vinum started *** > 12 Jan 2001 14:05:27.961106 create vinum_home2.conf The ten seconds here are hardly enough time for a reboot. Let's intersperse these messages: > 12 Jan 2001 14:05:37.293978 *** vinum started *** > 12 Jan 2001 14:12:43.507023 *** vinum started *** > 12 Jan 2001 14:12:44.694607 l > ... > > This time the system came backup correctly, however this time, running > vinum -l show me nothing regarding my desired volume home2. Here is the > relevant stuff from /var/log/messages: > Jan 10 16:03:34 hera /kernel: vinum: loaded > Jan 10 16:03:34 hera /kernel: vinum: reading configuration from /dev/ad8s1f > Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad10s1f > Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad4s1e > Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad6s1e > 12 Jan 2001 14:05:27.960421 *** vinum started *** > 12 Jan 2001 14:05:27.961106 create vinum_home2.conf > 12 Jan 2001 14:05:37.293978 *** vinum started *** > Jan 12 14:05:37 hera /kernel: vinum: drive e is up > Jan 12 14:05:37 hera /kernel: vinum: drive f is up > Jan 12 14:05:37 hera /kernel: vinum: drive g is up > Jan 12 14:05:37 hera /kernel: vinum: drive h is up > Jan 12 14:10:37 hera /kernel: vinum: loaded > Jan 12 14:10:37 hera /kernel: vinum: reading configuration from /dev/ad8s1f > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad10s1f > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad6s1e > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad4s1e > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad6s1f > Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad6s1f is down > Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad6s1f, error 5 > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad8s1g > Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad8s1g is down > Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad8s1g, error 5 > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad4s1f > Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad4s1f is down > Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad4s1f, error 5 > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad10s1g > Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad10s1g is down > Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad10s1g, error 5 > Jan 12 14:10:37 hera /kernel: vinum: couldn't read configuration > > Neither reboots created any dumps in /var/crash Do you have dumps enabled? The best I can guess here is that your partition layout is funny in some way. Let's have a look at the disklabel output for each spindle. Just the end, like this: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 4124640 0 unused 0 0 # (Cyl. 0 - 1006*) h: 4124640 0 vinum # (Cyl. 0 - 1006*) Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 16:49: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from web0.speakeasy.net (web0.speakeasy.net [216.254.0.11]) by hub.freebsd.org (Postfix) with SMTP id 21D8137B400 for ; Fri, 12 Jan 2001 16:48:52 -0800 (PST) Received: (qmail 22761 invoked by uid 701); 13 Jan 2001 00:48:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Jan 2001 00:48:51 -0000 Date: Fri, 12 Jan 2001 16:48:51 -0800 (PST) From: Chris D'Annunzio To: stable@FreeBSD.org 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 Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 17:16:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 3C70537B400 for ; Fri, 12 Jan 2001 17:16:01 -0800 (PST) Received: (qmail 75439 invoked from network); 13 Jan 2001 01:16:00 -0000 Received: from cognac.local.mindstep.com (HELO cognac) (192.168.10.9) by jacuzzi.local.mindstep.com with SMTP; 13 Jan 2001 01:16:00 -0000 From: "Patrick Bihan-Faou" To: Subject: MFC of OpenSSL 0.9.6 ? Date: Fri, 12 Jan 2001 20:17:15 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, OpenSSL 0.9.6 was integrated in -CURRENT in November. Could it be MFC'd to -STABLE ? While it was not really a problem until now, I am starting to see 3rd party software that relies on the latest OpenSSL to work. One that pops to mind is the latest version of netatalk (1.5.pre3). Are there any glaring problems that are preventing the MFC ? How can I help to make the MFC happen ? Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 17:31:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from danube.mindmaker.com (danube.mindmaker.com [209.66.98.152]) by hub.freebsd.org (Postfix) with ESMTP id EC3A037B401; Fri, 12 Jan 2001 17:31:23 -0800 (PST) Received: from hera.int.mindmaker.com (hera.int.mindmaker.com [192.168.10.16]) by danube.mindmaker.com (Postfix) with ESMTP id 60B6AF83E; Fri, 12 Jan 2001 17:31:25 -0800 (PST) Received: from mindmaker.com (joe2000.int.mindmaker.com [192.168.10.49]) by hera.int.mindmaker.com (8.11.1/8.11.1) with ESMTP id f0D1Y0Y01156; Fri, 12 Jan 2001 17:34:00 -0800 (PST) (envelope-from jfilla@mindmaker.com) Message-ID: <3A5FAFED.6F305826@mindmaker.com> Date: Fri, 12 Jan 2001 17:31:25 -0800 From: Joseph Filla Organization: Mindmaker Inc. X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: vinum create causes my 4.2-Stable SMP machine to reboot References: <3A5F9BFB.9C24C85F@mindmaker.com> <20010113110111.B66238@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > [Format recovered--see http://www.lemis.com/email/email-format.html] > > Please don't wrap log output. I've turned off wrapping of lines. Netscape 4.76 won't allow me to set outgoing message wrap to 0 characters. I've set it to 999. > > On Friday, 12 January 2001 at 16:06:19 -0800, Joseph Filla wrote: > > System information: > > 4.2-STABLE FreeBSD 4.2-STABLE #3: Wed Dec 6 17:46:52 PST 2000 > > SMP > > 2 Promise ATA66 controllers > > 4 IDE drives: > > ad4 > > ad6 > > ad8 > > ad10 > > All dangerously dedicated > > > > > > For the last few months, I have had vinum running in a raid 10 > > configuration: > > > > su-2.03# vinum list > > 4 drives: > > D a State: up Device /dev/ad4s1e Avail: 0/11500 MB (0%) > > D b State: up Device /dev/ad6s1e Avail: 0/11500 MB (0%) > > D c State: up Device /dev/ad8s1f Avail: 0/11500 MB (0%) > > D d State: up Device /dev/ad10s1f Avail: 0/11500 MB (0%) > > > > 4 volumes: > > V swap State: up Plexes: 2 Size: 649 MB > > V var State: up Plexes: 2 Size: 1999 MB > > V usr State: up Plexes: 2 Size: 1999 MB > > V home State: up Plexes: 2 Size: 17 GB > > > > > > > > After a few months of use on this box, I decided to use the remaining > > free space on the drives by creating another raid 10 volume. Through > > Sysinstall, I created a partition on each of the four drives, and > > changed the disklabels on all 4 new partitions to type vinum. > > > > I created another vinum config file vinum_home2.conf: > > drive e device /dev/ad4s1f > > drive f device /dev/ad6s1f > > drive g device /dev/ad8s1g > > drive h device /dev/ad10s1g > > > > volume home2 > > plex org striped 257k > > sd length 7705m drive e > > sd length 7705m drive f > > plex org striped 257k > > sd length 7705m drive g > > sd length 7705m drive h > > > > I know putting another volume on another partition in the same slice > > isn't optimal but I don't have any other drives. > > You really need to make that a single partition. But that shouldn't > be the problem. > > > I ran 'vinum create /etc/vinum_home2.conf' and the machine rebooted. > > Spontaneously, with no messages? I was on an ssh connection to the server both times. The first time, I got a few lines back but the second time nothing. By the time I walked over to the server, it had rebooted. > > > vinum_history doesn't show the the create command at all. > > No, it wouldn't. You had a crash. > > > The system rebooted into single user mode and I was eventually able > > to get back to a running system. vinum -l showed the new volume > > home2, the new plexes and the new subdisks but after running init > > and start, I could never get the subdisks past faulty. One of the > > striped plexes was always in state crashed. > > Where's the list? In the frustration of the moment, I didn't save a copy of the list. My bad. After reading some postings to -questions, I looked in /dev/vinum and there were no devices in drive, plex, sd etc for my new volumes. So I ran vinum -makedev and tried to init and start the new volumes. From /var/log/messages: Jan 9 17:04:07 hera /kernel: vinum: drive e is up Jan 9 17:04:07 hera /kernel: vinum: drive f is up Jan 9 17:04:07 hera /kernel: vinum: drive g is up Jan 9 17:04:07 hera /kernel: vinum: drive h is up Jan 9 17:04:07 hera /kernel: vinum: removing 80 blocks of partial stripe at the end o f home2.p0 Running makedev didn't solve my problem. I rebooted and here is /var/log/messages: Jan 9 17:57:10 hera /kernel: vinum: loaded Jan 9 17:57:10 hera /kernel: vinum: reading configuration from /dev/ad10s1f Jan 9 17:57:10 hera /kernel: vinum: home2.p0.s0 is crashed Jan 9 17:57:10 hera /kernel: vinum: home2.p0 is faulty Jan 9 17:57:10 hera /kernel: vinum: home2 is down Jan 9 17:57:10 hera /kernel: vinum: home2.p0.s1 is crashed Jan 9 17:57:10 hera /kernel: vinum: home2.p1.s0 is up Jan 9 17:57:10 hera /kernel: vinum: home2.p1 is up Jan 9 17:57:10 hera /kernel: vinum: home2 is up Jan 9 17:57:10 hera /kernel: vinum: home2.p1.s0 is up Jan 9 17:57:10 hera /kernel: vinum: home2.p1.s1 is up Jan 9 17:57:10 hera /kernel: vinum: updating configuration from /dev/ad8s1f Jan 9 17:57:10 hera /kernel: vinum: updating configuration from /dev/ad4s1e Jan 9 17:57:10 hera /kernel: vinum: updating configuration from /dev/ad6s1e Jan 9 17:57:10 hera /kernel: vinum: updating configuration from /dev/ad6s1f Jan 9 17:57:10 hera /kernel: vinum_scandisk: /dev/ad6s1f is down Jan 9 17:57:10 hera /kernel: vinum: Can't read device /dev/ad6s1f, error 5 Jan 9 17:57:10 hera /kernel: vinum: updating configuration from /dev/ad8s1g Jan 9 17:57:10 hera /kernel: vinum_scandisk: /dev/ad8s1g is down Jan 9 17:57:10 hera /kernel: vinum: Can't read device /dev/ad8s1g, error 5 Jan 9 17:57:10 hera /kernel: vinum: updating configuration from /dev/ad4s1f Jan 9 17:57:10 hera /kernel: vinum_scandisk: /dev/ad4s1f is down Jan 9 17:57:10 hera /kernel: vinum: Can't read device /dev/ad4s1f, error 5 Jan 9 17:57:10 hera /kernel: vinum: updating configuration from /dev/ad10s1g Jan 9 17:57:10 hera /kernel: vinum_scandisk: /dev/ad10s1g is down Jan 9 17:57:10 hera /kernel: vinum: Can't read device /dev/ad10s1g, error 5 Jan 9 17:57:10 hera /kernel: vinum: couldn't read configuration Similar results as I wrestled with it for a day before eventually doing a rm -f on it all > > > I eventually had to detach and rm all remnants of home2 and got my > > system back to the original state. Thinking I may have done > > something incorrectly, I retried the vinum create config and the > > system rebooted again. This time vinum_history recorded the > > following: > > > > 12 Jan 2001 14:05:27.960421 *** vinum started *** > > 12 Jan 2001 14:05:27.961106 create vinum_home2.conf > > The ten seconds here are hardly enough time for a reboot. Let's > intersperse these messages: > > > 12 Jan 2001 14:05:37.293978 *** vinum started *** > > 12 Jan 2001 14:12:43.507023 *** vinum started *** > > 12 Jan 2001 14:12:44.694607 l > > ... > > > > This time the system came backup correctly, however this time, running > > vinum -l show me nothing regarding my desired volume home2. Here is the > > relevant stuff from /var/log/messages: > > Jan 10 16:03:34 hera /kernel: vinum: loaded > > Jan 10 16:03:34 hera /kernel: vinum: reading configuration from /dev/ad8s1f > > Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad10s1f > > Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad4s1e > > Jan 10 16:03:34 hera /kernel: vinum: updating configuration from /dev/ad6s1e > > 12 Jan 2001 14:05:27.960421 *** vinum started *** > > 12 Jan 2001 14:05:27.961106 create vinum_home2.conf > > 12 Jan 2001 14:05:37.293978 *** vinum started *** > > Jan 12 14:05:37 hera /kernel: vinum: drive e is up > > Jan 12 14:05:37 hera /kernel: vinum: drive f is up > > Jan 12 14:05:37 hera /kernel: vinum: drive g is up > > Jan 12 14:05:37 hera /kernel: vinum: drive h is up > > Jan 12 14:10:37 hera /kernel: vinum: loaded > > Jan 12 14:10:37 hera /kernel: vinum: reading configuration from /dev/ad8s1f > > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad10s1f > > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad6s1e > > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad4s1e > > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad6s1f > > Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad6s1f is down > > Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad6s1f, error 5 > > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad8s1g > > Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad8s1g is down > > Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad8s1g, error 5 > > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad4s1f > > Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad4s1f is down > > Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad4s1f, error 5 > > Jan 12 14:10:37 hera /kernel: vinum: updating configuration from /dev/ad10s1g > > Jan 12 14:10:37 hera /kernel: vinum_scandisk: /dev/ad10s1g is down > > Jan 12 14:10:37 hera /kernel: vinum: Can't read device /dev/ad10s1g, error 5 > > Jan 12 14:10:37 hera /kernel: vinum: couldn't read configuration > > > > Neither reboots created any dumps in /var/crash > > Do you have dumps enabled? I do now... I can always run the create command again and catch it. > > The best I can guess here is that your partition layout is funny in > some way. Let's have a look at the disklabel output for each > spindle. Just the end, like this: > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 4124640 0 unused 0 0 # (Cyl. 0 - 1006*) > h: 4124640 0 vinum # (Cyl. 0 - 1006*) disklabel ad4: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 253952 0 4.2BSD 0 0 0 # (Cyl. 0 - 403*) c: 40088160 0 unused 0 0 # (Cyl. 0 - 63631) e: 23552000 253952 vinum # (Cyl. 403*- 37787*) f: 16282208 23805952 vinum # (Cyl. 37787*- 63631*) disklabel ad6: 8 partitions: # size offset fstype [fsize bsize bps/cpg] b: 253952 0 swap # (Cyl. 0 - 403*) c: 40088160 0 unused 0 0 # (Cyl. 0 - 63631) e: 23552000 253952 vinum # (Cyl. 403*- 37787*) f: 16282208 23805952 vinum # (Cyl. 37787*- 63631*) disklabel ad8: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 40088160 0 unused 0 0 # (Cyl. 0 - 63631) e: 251904 0 4.2BSD 0 0 0 # (Cyl. 0 - 399*) f: 23552000 251904 vinum # (Cyl. 399*- 37783*) g: 16284256 23803904 vinum # (Cyl. 37783*- 63631*) disklabel ad10: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 40088160 0 unused 0 0 # (Cyl. 0 - 63631) e: 253952 0 4.2BSD 0 0 0 # (Cyl. 0 - 403*) f: 23552000 253952 vinum # (Cyl. 403*- 37787*) g: 16282208 23805952 vinum # (Cyl. 37787*- 63631*) Note how ad8s1g has a different offset and size from the other related partitions. I noticed that before running create and I tried to make my lengths accordingly. I didn't intentionally do it this way. > > Greg > -- > When replying to this message, please copy the original recipients. > If you don't, I may ignore the reply. > For more information, see http://www.lemis.com/questions.html > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Joe Filla Systems Administrator Mindmaker, Inc. (408) 467-0468 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 17:54:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 2503737B402 for ; Fri, 12 Jan 2001 17:54:04 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id RAA24819; Fri, 12 Jan 2001 17:55:19 -0800 Date: Fri, 12 Jan 2001 17:55:19 -0800 From: Kris Kennaway To: Kal Torak Cc: FreeBSD-stable Subject: Re: gif & faith needed? Message-ID: <20010112175519.F23818@citusc.usc.edu> References: <3A5BC6C5.96B87778@quake.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3yNHWXBV/QO9xKNm" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A5BC6C5.96B87778@quake.com.au>; from kaltorak@quake.com.au on Wed, Jan 10, 2001 at 01:19:49PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --3yNHWXBV/QO9xKNm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 10, 2001 at 01:19:49PM +1100, Kal Torak wrote: > Hiyas, >=20 > I am just wondering if gif and faith pseudo devices are needed for > anything? (Besides IPv6 stuff) > And what they are for... That's what manual pages are there for.. Kris --3yNHWXBV/QO9xKNm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6X7WGWry0BWjoQKURAk/pAKDZ/+V/NZ4Po5+CyNkabcmDGJuwOQCdHqOa FFtyHQUcG5bXhf+Chq+gqzY= =PtTB -----END PGP SIGNATURE----- --3yNHWXBV/QO9xKNm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 17:59: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 42F5B37B404 for ; Fri, 12 Jan 2001 17:58:52 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id SAA24862; Fri, 12 Jan 2001 18:00:08 -0800 Date: Fri, 12 Jan 2001 18:00:08 -0800 From: Kris Kennaway To: Patrick Bihan-Faou Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MFC of OpenSSL 0.9.6 ? Message-ID: <20010112180008.G23818@citusc.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="XaUbO9McV5wPQijU" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from patrick@netzuno.com on Fri, Jan 12, 2001 at 08:17:15PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --XaUbO9McV5wPQijU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 12, 2001 at 08:17:15PM -0500, Patrick Bihan-Faou wrote: > Hi, >=20 >=20 > OpenSSL 0.9.6 was integrated in -CURRENT in November. Could it be MFC'd > to -STABLE ? While it was not really a problem until now, I am starting to > see 3rd party software that relies on the latest OpenSSL to work. One that > pops to mind is the latest version of netatalk (1.5.pre3). >=20 > Are there any glaring problems that are preventing the MFC ? How can I he= lp > to make the MFC happen ? You haven't run 'openssl version' in the past 2 months, have you? :-) Kris --XaUbO9McV5wPQijU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6X7aoWry0BWjoQKURAtS1AJsEqoJR2m0JgOY17Udtd/Tva7aGKgCfXCTW X12tLDjFJ/GbEMCAhVjgfDc= =Suqp -----END PGP SIGNATURE----- --XaUbO9McV5wPQijU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 18: 2:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id BFC1F37B400 for ; Fri, 12 Jan 2001 18:02:22 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id SAA24889; Fri, 12 Jan 2001 18:03:18 -0800 Date: Fri, 12 Jan 2001 18:03:18 -0800 From: Kris Kennaway To: Antony T Curtis Cc: stable@FreeBSD.ORG Subject: Re: ** HEADS UP ** C++ threading believed to be fixed Message-ID: <20010112180318.H23818@citusc.usc.edu> References: <6D5097D4B56AD31190D50008C7B1579BC97DD6@exlan5.rjf.com> <20010109103100.A77327@dragon.nuxi.com> <3A5EF7BA.95DA854D@abacus.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="54u2kuW9sGWg/X+X" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A5EF7BA.95DA854D@abacus.co.uk>; from antony@abacus.co.uk on Fri, Jan 12, 2001 at 12:25:30PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --54u2kuW9sGWg/X+X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 12, 2001 at 12:25:30PM +0000, Antony T Curtis wrote: > David O'Brien wrote: > >=20 > > On Tue, Jan 09, 2001 at 01:16:09PM -0500, Ian Cartwright wrote: > > > Does this mean a buildworld needs to be done to fix these problems? > >=20 > > Yes. >=20 > Any chance of a new point release and a new iso image for those not > wanting to cvsup and rebuild? Use one of the daily snapshots on ftp://releng4.freebsd.org. Not an ISO, but much more bandwidth friendly to download. Kris --54u2kuW9sGWg/X+X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6X7dlWry0BWjoQKURAlTQAJ48reucsfDj3FbVFZZxzpD9twA3lgCgqW7u q9faSU0RpDBCy1NGYVt8Elw= =b4FI -----END PGP SIGNATURE----- --54u2kuW9sGWg/X+X-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 18: 9:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 44DD237B401 for ; Fri, 12 Jan 2001 18:08:59 -0800 (PST) Received: (qmail 77572 invoked from network); 13 Jan 2001 02:08:58 -0000 Received: from cognac.local.mindstep.com (HELO cognac) (192.168.10.9) by jacuzzi.local.mindstep.com with SMTP; 13 Jan 2001 02:08:58 -0000 From: "Patrick Bihan-Faou" To: "Kris Kennaway" Cc: Subject: RE: MFC of OpenSSL 0.9.6 ? Date: Fri, 12 Jan 2001 21:10:13 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010112180008.G23818@citusc.usc.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You haven't run 'openssl version' in the past 2 months, have you? :-) Doh... Never mind.... I just looked at the cvs log for a couple of files and I could not see that it had been MFC'd... Sorry! Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 18:54:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 1BC2437B402 for ; Fri, 12 Jan 2001 18:54:29 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id tyqsaaaa for ; Sat, 13 Jan 2001 14:03:01 +1100 Message-ID: <3A5FC382.D163DFEA@quake.com.au> Date: Sat, 13 Jan 2001 13:54:58 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable Subject: [Fwd: Interesting plight (top/ps problem)] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Duane H. Hesser" wrote: > > The "top/ps" problem is discussed and answered in the mailing list > archives. I found the discussion after having the same problem > after an upgrade from 3.x to 4.2. > > The problem occurs if the kernel is booted directly from the second > stage boot, rather than from the boot loader. It appears that the > boot loader performs some initialization which is not otherwise > done. A source patch is included which purports to fix this. I > recall installing the patch, but I've never tested it. The patch > has never been committed, either because it is not robust, or > because no one has taken ownership. Perhaps no PR has been > submitted. > > To the original poster: you can verify that this is (or is not) > the problem simply by calling /boot/loader from the "boot:" prompt. > If that works, just change /boot.config to call /boot/loader rather > than /kernel. > > If you want the patch, you should be able to find it in the stable > or hacker list archives somewhere in the last couple of months > (lookfor "nlist", "loader", "kvm" ...). If you can't find it, I > can probably paw thru my disks to find it, but the workaround is > so easy that I haven't bothered to try the patch. > > It is possible that you have some *other* problem related to > out-of-sync kernel/world, as has been suggested, but if you're in > a position to reboot, this solution is easy to try, and it did the > trick for me. You might want to check /boot.config first, to make > sure that you're skipping the third boot stage. If it says something > like "da(0,a)/kernel" change the "/kernel" to "/boot/loader". If > it already says "/boot/loader"...never mind. > > FWIW, a quick search of mailing list archives is always a good idea > when a problem like this appears. > > On 12-Jan-01 Kal Torak wrote: > > Erich Zigler wrote: > >> > >> A couple days ago I was mentioning about my ps and top problems. Well at the > >> advice of a FreeBSD user I went and installed the bin distribution for > >> 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and everything was golden. > >> I could ps and top and kill I was one happy guy. > >> > >> Well I cvsup'ed my source tree, and went through the process as is outlined > >> in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish this > >> procedure, and ps and top fail to work. > >> > >> What is wrong? > >> > >> Why will it work on 4.2-RELEASE but not 4.2-STABLE? > > > > This just doesnt make ANY sense... > > If you really did follow the instructions everything SHOULD work fine, > > I have cvsup'd many times and so long as you do it by the UPDATING file > > I have never had any problems (besides new/changed driver issues)... > > > > It seems to me that something MUST be out of synch... > > Make sure your stable-supfile is getting everything... > > Do the install in single user mode if your not already... > > Clean out /usr/obj before a build, some of the files you may > > need to allow deleting on with the chflags command... > > > > You are specifying what kernel to build right? > > make buildkernel KERNEL=GENERIC > > unless you have a custom kernel then specify that... > > > > If you are doing all this, you should try removing all of the > > /usr/src and /usr/obj and remove the cvsup logs and get everything > > again... > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > -------------- > Duane H. Hesser > dhh@androcles.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 19:51: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail5.sdc1.sfba.home.com (femail5.sdc1.sfba.home.com [24.0.95.85]) by hub.freebsd.org (Postfix) with ESMTP id A543637B400; Fri, 12 Jan 2001 19:50:40 -0800 (PST) Received: from math.missouri.edu ([24.12.197.197]) by femail5.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010113035040.MUOQ29808.femail5.sdc1.sfba.home.com@math.missouri.edu>; Fri, 12 Jan 2001 19:50:40 -0800 Message-ID: <3A5FD090.E035557F@math.missouri.edu> Date: Fri, 12 Jan 2001 21:50:40 -0600 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, freebsd-mobile@freebsd.org Subject: disable mousepad taps on Dell Inspiron Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have submitted another PR describing how to do this: http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 I now know quite a few people who would like something like this. The old PR I submitted regarding this is now out of date. Could someone please commit this (and the required co-PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=20352 ) or something like this? Thanks, Stephen -- Stephen Montgomery-Smith stephen@math.missouri.edu http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 20: 4:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from world.std.com (world-f.std.com [199.172.62.5]) by hub.freebsd.org (Postfix) with ESMTP id ABD2737B402 for ; Fri, 12 Jan 2001 20:03:54 -0800 (PST) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id XAA29627; Fri, 12 Jan 2001 23:00:45 -0500 (EST) Date: Fri, 12 Jan 2001 23:00:45 -0500 (EST) From: Kenneth W Cochran Message-Id: <200101130400.XAA29627@world.std.com> To: hubbe snubbe Subject: Re: Bug in src tree? Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To get 4.2-RELEASE source: 1. (optional) cd /usr/src ; rm -rf * 2. cvsup with tag "RELENG_4_2_0_RELEASE" -kc >From owner-freebsd-stable@FreeBSD.ORG Fri Jan 12 18:22:46 2001 >Date: Fri, 12 Jan 2001 22:00:39 +0100 (CET) >From: hubbe snubbe >To: Will Andrews >Cc: electro , FreeBSD Stable >Subject: Re: Bug in src tree? > >I have corrected that and sucessfully made make kernerlbuild but I seems >to have problem with make world. >Is there some where I can get the 4.2release source? and compile it and >install my own kernel from the begining(I get system crash with generic >4.2 kernel). > >On Fri, 12 Jan 2001, Will Andrews wrote: > >> [ .. moved to -stable .. ] >> >> On Fri, Jan 12, 2001 at 08:17:01AM +0100, electro wrote: >> > I try to compile a new kernel with the latest source and I always end up >> > with this (in the end). Any suggestions? >> > I mean the error message is fun...dont match any know i386 instruction???? >> [...] >> > /tmp/ccmJEqq7.s:758: Error: operands given don't match any known 386 >> > instruction >> > /tmp/ccmJEqq7.s:822: Error: operands given don't match any known 386 >> > instruction >> [...] >> >> You appear to be upgrading from a very old version of FreeBSD. The last >> time I encountered this was when binutils was upgraded in 4.x-STABLE >> around July or August 2000. In any case that means (most likely) that >> you may need to install the newer binutils manually before compiling. >> >> -- >> wca > >------------------------------------------------------------------------ >http://www.ludd.luth.se/~electro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 22:26:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from realtime.net (dragon.realtime.net [205.238.128.89]) by hub.freebsd.org (Postfix) with SMTP id 500B437B401 for ; Fri, 12 Jan 2001 22:26:04 -0800 (PST) Received: from tigerfish2.my.domain ([205.238.153.210]) by realtime.net ; Sat, 13 Jan 2001 00:25:53 -0600 Received: (from brucegb@localhost) by tigerfish2.my.domain (8.11.1/8.11.1) id f0D6Qh833303 for freebsd-stable@freebsd.org; Sat, 13 Jan 2001 00:26:43 -0600 (CST) (envelope-from brucegb) Date: Sat, 13 Jan 2001 00:26:43 -0600 From: Bruce Burden To: freebsd-stable@freebsd.org Subject: /swap too large? What?? Message-ID: <20010113002643.A33278@tigerfish2.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi gang, Okay, I have downloaded 4.2, from January 10 or so. I have a ~1.7GB swap defined on da0s1b. When I attempt to mount it, however, I am told: exceeded maximum of 3355443 blocks per swap unit Hmmm. I can't find anything about this in the archives, nor am I able to: swapon /dev/da3s1b which was my old swap (1GB) space on a different disk. Now, you might argue that 1.7GB of swap is a bit excessive, and it probably is, but hey, so what? I have had up to 600MB of that space allocated previously (GIMP is hungry!), so I figured I would bump that with when I added another disk. I am concerned, however, as to why I can't mount my previous swap area on a different disk. Has something changed to limit the swap space you can create? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 22:31:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.wireless-isp.net (unknown [199.250.171.154]) by hub.freebsd.org (Postfix) with ESMTP id DA97537B400 for ; Fri, 12 Jan 2001 22:31:20 -0800 (PST) Received: from damoe.wireless-isp.net (damoe.wireless-isp.net [208.61.227.212]) by smtp.wireless-isp.net (8.9.3/8.9.3) with ESMTP id FAA25289; Wed, 10 Jan 2001 05:01:22 -0500 Date: Sat, 13 Jan 2001 01:33:42 -0500 (EST) From: David Raistrick To: Bruce Burden Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /swap too large? What?? In-Reply-To: <20010113002643.A33278@tigerfish2.my.domain> 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, 13 Jan 2001, Bruce Burden wrote: > > > Hi gang, > > Okay, I have downloaded 4.2, from January 10 or so. I have > a ~1.7GB swap defined on da0s1b. When I attempt to mount it, Odd. Jan8 stable handles my 2048M swap fine. Device 1K-blocks Used Avail Capacity Type /dev/da0s1b 2097024 0 2097024 0% Interleaved (running on the old "2x ram" rule..yeah yeah. Disk is cheap..) -- David Raistrick Digital Wireless Communications davidr@dwcinet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 22:44:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from p133.inode.at (p133.inode.at [195.58.160.3]) by hub.freebsd.org (Postfix) with ESMTP id D47C337B400 for ; Fri, 12 Jan 2001 22:44:01 -0800 (PST) Received: from inode.at (line205.adsl.wien.inode.at [213.229.7.205]) by p133.inode.at (8.11.1/8.10.0.0) with ESMTP id f0D6hxh20708 for ; Sat, 13 Jan 2001 07:43:59 +0100 Message-ID: <3A5FF95C.498B514F@inode.at> Date: Sat, 13 Jan 2001 07:44:44 +0100 From: Michael Bretterklieber X-Mailer: Mozilla 4.75 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: stable@FreeBSD.org Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> <3A5F95AF.F8B120D4@mindmaker.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Bernhard Beck schrieb: > > What confuses me, though, is why the CPU works with normal speed in > Windows 2000. Michael, maybe try booting with a SMP kernel (?) > No, I tried the GENERIC and my own kernel, same effect. Before I made the BIOS-upgrade, the system was slow, like on an PII 200 and unstable on all Win98, Win2k and FreeBSD. The BIOS has not recognized the CPU correctly ("AMD-(unknown)"). With 3DMark2000 it only reached about 600 points. After the BIOS-upgrade everything worked great on Win98 and Win2k, I reached 1771 points with 3DMark2000. bye, -- -------------------------------------- E-mail: Michael.Bretterklieber@jawa.at ---------------------------- JAWA MANAGEMENT und SOFTWARE Liebenauer Hauptstr. 200 A-8041 GRAZ Tel: ++43-(0)316-403274-12 Fax: ++43-(0)316-403274-10 GSM: ++43-(0)676-93 96 698 homepage: http://www.jawa.at --------- privat ----------- E-mail: mbretter@inode.at homepage: http://www.inode.at/mbretter -------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 12 22:48: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from p133.inode.at (p133.inode.at [195.58.160.3]) by hub.freebsd.org (Postfix) with ESMTP id 6555237B400 for ; Fri, 12 Jan 2001 22:47:48 -0800 (PST) Received: from inode.at (line205.adsl.wien.inode.at [213.229.7.205]) by p133.inode.at (8.11.1/8.10.0.0) with ESMTP id f0D6llh20831 for ; Sat, 13 Jan 2001 07:47:47 +0100 Message-ID: <3A5FFA40.F842FB31@inode.at> Date: Sat, 13 Jan 2001 07:48:32 +0100 From: Michael Bretterklieber X-Mailer: Mozilla 4.75 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: stable@FreeBSD.org Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs FreeBSD 4.2 References: <200101122233.RAA83180@coup.inode.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, David Jones schrieb: > Is your L2 cache turned on for all memory? > > The K7M BIOS does not enable L2 caching for anything other than base memory. > With the cache off, the system feels like a 200 MHz Pentium. The speed of the system was like a 200MHz Pentium before I made the BIOS-upgrade. Now it is fast on Win98 and Win2k (1771 points with 3DMark2000). On FreeBSD its like I work over a slow network, keyboard clicks are delayed, etc. > > > Try executing the following: > > /usr/sbin/memcontrol set -b 0 -l 268435456 write-back > I tried it, no effect. > > Replace that big number with the amount of memory you have, in bytes. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message bye, -- -------------------------------------- E-mail: Michael.Bretterklieber@jawa.at ---------------------------- JAWA MANAGEMENT und SOFTWARE Liebenauer Hauptstr. 200 A-8041 GRAZ Tel: ++43-(0)316-403274-12 Fax: ++43-(0)316-403274-10 GSM: ++43-(0)676-93 96 698 homepage: http://www.jawa.at --------- privat ----------- E-mail: mbretter@inode.at homepage: http://www.inode.at/mbretter -------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 0: 2:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chubby.gatewaybsd.au.com (CPE-203-45-153-231.qld.bigpond.net.au [203.45.153.231]) by hub.freebsd.org (Postfix) with ESMTP id 6D9C337B69B for ; Sat, 13 Jan 2001 00:02:22 -0800 (PST) Received: from win2k (win2k.gatewaybsd.au.com [10.0.0.1]) by chubby.gatewaybsd.au.com (8.11.1/8.11.1) with SMTP id f0D82E105316 for ; Sat, 13 Jan 2001 18:02:15 +1000 (EST) (envelope-from whisky@slipy.net) Message-ID: <00e701c07d37$53239cd0$0100000a@win2k> From: "whisky" To: Subject: Date: Sat, 13 Jan 2001 18:03:33 +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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it recommended to cvsup from 4.2-RELEASE to 4.x-STABLE Any exploits/bugs that might persuade me to defaintely do it......? Thanks.. whisky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 1:36:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 0360C37B400 for ; Sat, 13 Jan 2001 01:36:14 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id barsaaaa for ; Sat, 13 Jan 2001 20:44:45 +1100 Message-ID: <3A6021A4.AD9DCCF8@quake.com.au> Date: Sat, 13 Jan 2001 20:36:36 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: whisky Cc: freebsd-stable@freebsd.org Subject: Re: References: <00e701c07d37$53239cd0$0100000a@win2k> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG whisky wrote: > > Is it recommended to cvsup from 4.2-RELEASE to 4.x-STABLE > > Any exploits/bugs that might persuade me to defaintely do it......? > > Thanks.. whisky The procfs bug is a worthwhile reason... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 3: 1: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b044.neo.rr.com [24.93.181.44]) by hub.freebsd.org (Postfix) with ESMTP id D31DF37B400 for ; Sat, 13 Jan 2001 03:00:50 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id f0DAqWx31723; Sat, 13 Jan 2001 05:52:33 -0500 Date: Sat, 13 Jan 2001 05:52:32 -0500 (EST) From: Mike Nowlin To: Kal Torak Cc: Erich Zigler , stable@FreeBSD.ORG Subject: Re: Interesting plight In-Reply-To: <3A5EB434.865FC56F@quake.com.au> 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 > > A couple days ago I was mentioning about my ps and top problems. Well at the > > advice of a FreeBSD user I went and installed the bin distribution for > > 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and everything was golden. > > I could ps and top and kill I was one happy guy. > > > > Well I cvsup'ed my source tree, and went through the process as is outlined > > in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish this > > procedure, and ps and top fail to work. > > This just doesnt make ANY sense... > If you really did follow the instructions everything SHOULD work fine, > I have cvsup'd many times and so long as you do it by the UPDATING file > I have never had any problems (besides new/changed driver issues)... I have a system that went from 3.0, through a bunch of upgrades to 3.5, to 4.0, now up to 4.2. The 4.1.1 that was currently running seemed to work OK, but if I did a build/install world/kernel for 4.2, ps, top, and a few relatives died with some nlist error. I finally fixed it with "rm -fR /usr/src", re-CVSup, and rebuild... SOMETHING wasn't getting updated as it should... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 4:26: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chubby.gatewaybsd.au.com (CPE-203-45-153-231.qld.bigpond.net.au [203.45.153.231]) by hub.freebsd.org (Postfix) with ESMTP id E154337B400 for ; Sat, 13 Jan 2001 04:25:40 -0800 (PST) Received: from win2k (win2k.gatewaybsd.au.com [10.0.0.1]) by chubby.gatewaybsd.au.com (8.11.1/8.11.1) with SMTP id f0DCPXb11339 for ; Sat, 13 Jan 2001 22:25:39 +1000 (EST) (envelope-from whisky@slipy.net) Message-ID: <014301c07d5c$1fc9dc80$0100000a@win2k> From: "whisky" To: Subject: Date: Sat, 13 Jan 2001 22:26:52 +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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How does one use mergemaster correctly after a make installworld of 4.2-R to 4.x-S Help is much appreciated To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 5:12:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from level3.dynacom.net (level3.dynacom.net [206.107.213.213]) by hub.freebsd.org (Postfix) with SMTP id 883F437B400 for ; Sat, 13 Jan 2001 05:12:17 -0800 (PST) Received: (qmail 15253 invoked by uid 0); 13 Jan 2001 13:12:16 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 13 Jan 2001 13:12:16 -0000 Message-ID: <3A605430.5D32DB56@urx.com> Date: Sat, 13 Jan 2001 05:12:16 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: whisky Cc: freebsd-stable@freebsd.org Subject: Re: Mergemaster References: <014301c07d5c$1fc9dc80$0100000a@win2k> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG whisky wrote: > > How does one use mergemaster correctly after a make installworld of 4.2-R to > 4.x-S Very, very carefully. It will try to change all of the configuration files that have been updated. If you have added local mods, they disappear. I don't let it touch my firewall rules, ppp.conf, passwd, or groups. It will also try to change files root uses but I don't let it. I check when it changes my dot."*" files. If I have added local aliases or paths, I don't want them removed. The choices provided by mergemaster on them is always i(nstall new), d(elete new), or m(erge). On the special files, I usually press the enter key, which is none of the above and do them individually. Then, I go through after everything is done and merged what was important out of the files in /var/tmp/temproot/etc. If you include the header information at the top, it ignore that file in the future until the it is modified by the maintainer. The rest of the files I usually add the new mods. It is really convient to do this all from a second computer. Being able to do that depends on your system. You could also do it from x-windows but that really uses a lot of memory that would usually be more beneficial to the compilers. I just happen to set my system up such that I can do an installworld in multi-user mode. Not everyone can do this. It is discussed in /usr/src/UPDATING. The advantage is that it lets me telnet or ssh in and do everything from several sessions. When I get through, I reboot from the console. Kent > > Help is much appreciated > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 6:35:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from porgy.srv.nld.sonera.net (porgy.srv.nld.sonera.net [195.66.15.137]) by hub.freebsd.org (Postfix) with ESMTP id 3D55D37B401 for ; Sat, 13 Jan 2001 06:35:39 -0800 (PST) Received: from qn-212-58-190-140.quicknet.nl ([212.58.190.140]:1047 "EHLO quicknet.nl") by soneramail.nl with ESMTP id ; Sat, 13 Jan 2001 15:35:17 +0100 Message-ID: <3A6065F8.19D2AD27@quicknet.nl> Date: Sat, 13 Jan 2001 15:28:08 +0100 From: Paul Beers X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: SUBSCRUBI Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to join the FBSD - Stable mailing list To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 8:34:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id 3659E37B402 for ; Sat, 13 Jan 2001 08:34:24 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id IAA15896; Sat, 13 Jan 2001 08:34:11 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f0DGY8o36236; Sat, 13 Jan 2001 08:34:08 -0800 (PST) (envelope-from bmah) Message-Id: <200101131634.f0DGY8o36236@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2+ 01/03/2001 with nmh-1.0.4 To: kstewart@urx.com Cc: whisky , freebsd-stable@FreeBSD.ORG Subject: Re: Mergemaster In-Reply-To: <3A605430.5D32DB56@urx.com> References: <014301c07d5c$1fc9dc80$0100000a@win2k> <3A605430.5D32DB56@urx.com> Comments: In-reply-to Kent Stewart message dated "Sat, 13 Jan 2001 05:12:16 -0800." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-815710976P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sat, 13 Jan 2001 08:34:08 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-815710976P Content-Type: text/plain; charset=us-ascii If memory serves me right, Kent Stewart wrote: > whisky wrote: > > > > How does one use mergemaster correctly after a make installworld of 4.2-R t > o > > 4.x-S > > Very, very carefully. That applies to pretty much any system administration task. > It will try to change all of the configuration > files that have been updated. If you have added local mods, they > disappear. Say again?!? Your "local mods" only disappear if you let mergemaster overwrite them. It never does anything without telling you. > I don't let it touch my firewall rules, ppp.conf, passwd, > or groups. It will also try to change files root uses but I don't let > it. I check when it changes my dot."*" files. If I have added local > aliases or paths, I don't want them removed. The choices provided by > mergemaster on them is always i(nstall new), d(elete new), or m(erge). Have you actually tried the last of the three options? I've found that it works pretty well for merging in a set of local changes with a new version of a file. You need to pay attention when doing the merge, obviously. My advise: Run mergemaster after an installworld. Read the diffs it produces. The first time you run it (on a system updated from 4.2-RELEASE) you'll probably see a lot of changes. In general, if you know you didn't modify a file, you can probably just let it install the new version. Learn how sdiff works for handling merges of files, to handle the case where you made a local modification and the original, base file was also updated. The first few times you do this, make sure to have a backup of /etc so you can bail yourself out if necessary. Bruce. --==_Exmh_-815710976P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6YIOA2MoxcVugUsMRAi2rAJwJtTVjbkEdAg1+nA8VKm7EBB8WjwCg7H/O awCiHQSGIsGN0b/YXdv3hyk= =YpAZ -----END PGP SIGNATURE----- --==_Exmh_-815710976P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 8:37: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2296137B401 for ; Sat, 13 Jan 2001 08:36:46 -0800 (PST) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 14HTfZ-0000Zm-00 for freebsd-stable@freebsd.org; Sat, 13 Jan 2001 08:36:45 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Stable Subject: cur-dls disk lockups Message-Id: Date: Sat, 13 Jan 2001 08:36:45 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG system locks up can move cursor but it's sluggish can move between parts of virt desktop any request for disk i/o and that window is frozen asus cur-dls with lsi 896 ultra-2 scsi two ibm DDYS-T18350N 18g scsi onboard ati rage-xl pci vga with 4mb 4.2-stable of 00.12.18 (am cvsupping now) xfree86 4.0.1 this has been going on for multiple versions of -stable, ever since i moved to the cur-dls from a p2b-ds. anyone else seeing anything like this? randy --- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Wed Dec 20 22:08:48 PST 2000 root@rip.psg.com:/usr/obj/usr/src/sys/RIP Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 800034140 Hz CPU: Pentium III/Pentium III Xeon/Celeron (800.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 536850432 (524268K bytes) avail memory = 519397376 (507224K bytes) Preloaded elf kernel "kernel" at 0xc0334000. ccd0-5: Concatenated disk drivers Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 fxp0: port 0xd800-0xd83f mem 0xfc000000-0xfc0fffff,0xfc800000-0xfc800fff irq 5 at device 2.0 on pci0 fxp0: Ethernet address 00:e0:18:02:6e:c9 bktr0: mem 0xfe000000-0xfe000fff irq 11 at device 4.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 bktr0: Hauppauge Model 61111 A M bktr0: Detected a MSP3430G-A1 at 0x80 bktr0: Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. pci0: (vendor=0x109e, dev=0x0878) at 4.1 irq 11 pcm0: port 0xd400-0xd43f irq 10 at device 5.0 on pci0 pci0: at 7.0 isab0: at device 15.0 on pci0 isa0: on isab0 pci0: at 15.1 pci0: at 15.2 irq 9 pcib1: on motherboard pci1: on pcib1 sym0: <896> port 0xb400-0xb4ff mem 0xf9000000-0xf9001fff,0xf9800000-0xf98003ff irq 9 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym1: <896> port 0xb000-0xb0ff mem 0xf8000000-0xf8001fff,0xf8800000-0xf88003ff irq 9 at device 5.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A Waiting 5 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/da0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 8:39:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 4FE3E37B401 for ; Sat, 13 Jan 2001 08:39:13 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id IAA11782; Sat, 13 Jan 2001 08:39:24 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f0DGdDa36364; Sat, 13 Jan 2001 08:39:13 -0800 (PST) (envelope-from bmah) Message-Id: <200101131639.f0DGdDa36364@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.2+ 01/03/2001 with nmh-1.0.4 To: "whisky" Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <00e701c07d37$53239cd0$0100000a@win2k> References: <00e701c07d37$53239cd0$0100000a@win2k> Comments: In-reply-to "whisky" message dated "Sat, 13 Jan 2001 18:03:33 +1000." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-797506736P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sat, 13 Jan 2001 08:39:13 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-797506736P Content-Type: text/plain; charset=us-ascii If memory serves me right, "whisky" wrote: > Is it recommended to cvsup from 4.2-RELEASE to 4.x-STABLE > > Any exploits/bugs that might persuade me to defaintely do it......? The release notes will tell you what's changed since the last release along a branch, to within about a week. After you grab 4-STABLE sources to your system, read one of the following as appropriate to your architecture: /usr/src/release/texts/alpha/RELNOTES.TXT /usr/src/release/texts/i386/RELNOTES.TXT You can also browse these files in the on-line CVS repository. Bruce. --==_Exmh_-797506736P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6YISx2MoxcVugUsMRApMJAJ0fuLNYYjpRhpJpOyoRrx4gYtkm+gCeOaC9 jno7WvpMZi6MC3UyjkH5TuU= =25wr -----END PGP SIGNATURE----- --==_Exmh_-797506736P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 8:52:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id A049637B402 for ; Sat, 13 Jan 2001 08:52:39 -0800 (PST) Received: (qmail 18643 invoked from network); 13 Jan 2001 16:52:28 -0000 Received: from unknown (HELO arthur.tacni.net) (207.55.167.106) by 216.178.136.168 with SMTP; 13 Jan 2001 16:52:28 -0000 Received: (qmail 288 invoked by uid 1000); 13 Jan 2001 16:52:28 -0000 Date: Sat, 13 Jan 2001 10:52:28 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Re: Interesting plight Message-ID: <20010113105227.A248@superhero.org> References: <20010111224451.A277@superhero.org> <20010112133703.A17573@mail.catseye.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010112133703.A17573@mail.catseye.net>; from list-freebsd-stable@catseye.net on Fri, Jan 12, 2001 at 01:37:04PM -0600 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 12, 2001 at 01:37:04PM -0600, Timothy Legant wrote: > If these steps (in this order!) are what you've already done, let us > know. Otherwise, do them exactly in this order and you will have the > same version kernel and userland. I would like to thank everyone for their help in this matter. I have followed your directions explicitly and still get the same errors with ps and top. Could it be possible my procfs is corrupted. This is a standard FreeBSD install Im not runing linux procfs and I do have procfs compiled into the kernel. Could something not be getting updated? I'm very confused here and at a complete loss. -- Erich Zigler Censorship sucks^H^H^H^H^H is for your own good. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 10: 4:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id E0BB637B69C for ; Sat, 13 Jan 2001 10:04:25 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0DI4Li60227 for ; Sat, 13 Jan 2001 10:04:21 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: stable@freebsd.org Subject: Charlie Root: 4.x-stable build report for Sat Jan 13 02:16:35 CST 2001 Date: Sat, 13 Jan 2001 10:04:21 -0800 Message-ID: <60224.979409061@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Somebody broke the -stable release build yesterday, looks like. ------- Forwarded Message Return-Path: root@usw3.freebsd.org Delivery-Date: Sat Jan 13 05:24:55 2001 Return-Path: Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0DDOsi59538 for ; Sat, 13 Jan 2001 05:24:54 -0800 (PST) (envelope-from root@usw3.freebsd.org) Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D26C86E263B for ; Sat, 13 Jan 2001 05:24:55 -0800 (PST) Received: by hub.freebsd.org (Postfix) id C627F37B400; Sat, 13 Jan 2001 05:24:55 -0800 (PST) Delivered-To: jkh@freebsd.org Received: from usw3.freebsd.org (usw3.freebsd.org [209.180.6.227]) by hub.freebsd.org (Postfix) with ESMTP id 3A64737B698 for ; Sat, 13 Jan 2001 05:24:55 -0800 (PST) Received: (from root@localhost) by usw3.freebsd.org (8.11.1/8.11.0) id f0DDQ3v20298 for build-reports@freebsd.org; Sat, 13 Jan 2001 07:26:03 -0600 (CST) (envelope-from root) Date: Sat, 13 Jan 2001 07:26:03 -0600 (CST) From: Charlie Root Message-Id: <200101131326.f0DDQ3v20298@usw3.freebsd.org> To: build-reports@freebsd.org Subject: 4.x-stable build report for Sat Jan 13 02:16:35 CST 2001 Doing nightly build attempt for 4.2-20010113-STABLE at Sat Jan 13 02:16:35 CST 2001 Updating source tree... Making release... Release build of 4.2-20010113-STABLE was an abject failure. rmdir: krb5/usr/share/man/man8: Directory not empty rmdir: krb5/usr/share/man: Directory not empty rmdir: krb5/usr/share: Directory not empty rmdir: krb5/usr: Directory not empty rmdir: krb5: Directory not empty *** Error code 1 (ignored) touch release.5 rm -rf /R/stage/dists mkdir -p /R/stage/dists rolling bin/bin tarball tar: dev/sa0.ctl: minor number too large; not dumped bin distribution is finished. rolling manpages/manpages tarball manpages distribution is finished. rolling catpages/catpages tarball catpages distribution is finished. rolling games/games tarball games distribution is finished. rolling proflibs/proflibs tarball proflibs distribution is finished. rolling dict/dict tarball dict distribution is finished. rolling info/info tarball info distribution is finished. rolling doc/doc tarball doc distribution is finished. rolling compat1x/compat1x tarball compat1x distribution is finished. rolling compat20/compat20 tarball compat20 distribution is finished. rolling compat21/compat21 tarball compat21 distribution is finished. rolling compat22/compat22 tarball compat22 distribution is finished. rolling compat3x/compat3x tarball compat3x distribution is finished. rolling crypto/crypto tarball crypto distribution is finished. rolling krb4/krb4 tarball krb4 distribution is finished. rolling krb5/krb5 tarball krb5 distribution is finished. # More munition braindeadness. ( cd /R/stage/dists && if [ -f krb4/krb4.aa ] ; then mv krb4/* crypto && rmdir krb4 ; fi ) ( cd /R/stage/dists && if [ -f krb5/krb5.aa ] ; then mv krb5/* crypto && rmdir krb5 ; fi ) touch release.6 rolling src/sbase tarball rolling src/sbin tarball rolling src/scontrib tarball rolling src/scrypto tarball rolling src/setc tarball rolling src/sgames tarball rolling src/sgnu tarball rolling src/sinclude tarball rolling src/skrb5 tarball rolling src/skrb4 tarball rolling src/slib tarball rolling src/slibexec tarball rolling src/srelease tarball rolling src/ssbin tarball rolling src/ssecure tarball rolling src/sshare tarball rolling src/ssys tarball rolling src/stools tarball rolling src/subin tarball rolling src/susbin tarball if [ -d /R/stage/dists/crypto ] ; then ( cd /R/stage/dists/src && if [ -f ssecure.aa ] ; then mv ssecure.* ../crypto ; fi && if [ -f scrypto.aa ] ; then mv scrypto.* ../crypto ; fi && if [ -f skrb4.aa ] ; then mv skrb4.* ../crypto ; fi && if [ -f skrb5.aa ] ; then mv skrb5.* ../crypto ; fi ; ) ; fi src distribution is finished. touch release.7 cc -O -pipe -o write_mfs_in_kernel /usr/src/release/write_mfs_in_kernel.c rm -rf /R/stage/mfsfd mkdir /R/stage/mfsfd cd /R/stage/mfsfd && mkdir -p etc/defaults dev mnt stand/help ( cd /R/stage/trees/bin/dev && ls console tty bpf0 ttyv0 ttyv1 ttyv2 ttyv3 null zero card0 card1 card2 card3 usb usb0 uhid0 ums0 ulpt0 ugen0 kbd0 kmem mem | cpio -dump /R/stage/mfsfd/dev ) 0 blocks ( cd /R/stage/mfsfd/dev && rm -f *[swo]d*[bdefgh] ) ( cd /R/stage/mfsfd && for dir in bin sbin ; do ln -sf /stand $dir; done ) cp /sbin/dhclient-script /R/stage/mfsfd/stand cp /usr/src/release/../etc/defaults/pccard.conf /R/stage/mfsfd/etc/defaults/pccard.conf cp /usr/src/release/../etc/usbd.conf /R/stage/mfsfd/etc/usbd.conf cd /R/stage/trees/bin && ls etc/protocols etc/defaults/rc.conf | cpio -dump /R/stage/mfsfd/stand 48 blocks echo "nameserver 42/tcp name" > /R/stage/mfsfd/stand/etc/services echo "ftp 21/tcp" >> /R/stage/mfsfd/stand/etc/services echo "domain 53/tcp nameserver" >> /R/stage/mfsfd/stand/etc/services echo "domain 53/udp nameserver" >> /R/stage/mfsfd/stand/etc/services echo "cmd 514/tcp shell" >> /R/stage/mfsfd/stand/etc/services gzip -9c /usr/src/release/../COPYRIGHT > /R/stage/mfsfd/stand/help/COPYRIGHT.hlp.gz test -f /usr/src/release/install.cfg && cp /usr/src/release/install.cfg /R/stage/mfsfd Making the regular boot floppy. Compressing doc files... *** Error code 1 (ignored) sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/mfsfd 8000 minimum2 mknod: /dev/vnn0: File exists *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 11:27:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 2F7F037B400 for ; Sat, 13 Jan 2001 11:27:31 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0DJRSS34276; Sat, 13 Jan 2001 11:27:28 -0800 (PST) (envelope-from dillon) Date: Sat, 13 Jan 2001 11:27:28 -0800 (PST) From: Matt Dillon Message-Id: <200101131927.f0DJRSS34276@earth.backplane.com> To: Bruce Burden Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /swap too large? What?? References: <20010113002643.A33278@tigerfish2.my.domain> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Hi gang, : : Okay, I have downloaded 4.2, from January 10 or so. I have : a ~1.7GB swap defined on da0s1b. When I attempt to mount it, : however, I am told: : :exceeded maximum of 3355443 blocks per swap unit : : Hmmm. I can't find anything about this in the archives, nor am : I able to: The only thing that can cause this is if you have configured an absurdly large NSWAPDEV. : I am concerned, however, as to why I can't mount my previous : swap area on a different disk. Has something changed to limit the : swap space you can create? : : Bruce A sanity check was put in the code to ensure that the internal bitmap tree could not overflow. The default NSWAPDEV is 4 (up to 4 swap devices). The block limitation is (2GB / 16 / NSWAPDEV) 512 byte blocks, or: 2GB / 16 / NSWAPDEV * 512. If NSWAPPDEV is 4, each swap parition can theoretically be up to 17 GB in size. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 11:38:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from routermonkey.com (fry.routermonkey.com [204.209.9.25]) by hub.freebsd.org (Postfix) with ESMTP id 0CF8C37B400 for ; Sat, 13 Jan 2001 11:38:02 -0800 (PST) Received: (from jason@localhost) by routermonkey.com (8.11.1/8.11.1) id f0DJbtH21921; Sat, 13 Jan 2001 12:37:55 -0700 (MST) (envelope-from jason) Date: Sat, 13 Jan 2001 12:37:54 -0700 From: Jason F Wells To: Mike Andrews Cc: Mark.Andrews@nominum.com, stable@FreeBSD.ORG Subject: Re: Weird sporadic DNS resolution problems Message-ID: <20010113123754.B1299@fry.routermonkey.com> References: <200101120102.f0C12X863536@drugs.dv.isc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mandrews@bit0.com on Fri, Jan 12, 2001 at 04:34:37PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what it's worth, I've also experienced problems with Sendmail+BIND interaction. I've specifically had problems receiving mail from dml.com, which hosts the zebra mailing list. I finally had to resort to putting an entry in /etc/hosts so that I could get mail from the mailing list. Without the entry in /etc/hosts, I get the same sendmail error: Domain of sender address owner-zebra@dml.com does not resolve The interesting difference in my problem (I think it's interesting...) is that neither of the nameservers for dml.com are lame; they both return valid A records for dml.com using dig, but my named seems to think that there isn't an A record until I stop and restart named. Then, when I do an nslookup / dig, it returns the correct result for a while, until it stops working again. I'm pretty sure the problem is on my end (Sendmail and/or BIND) or else a lot of people on the zebra mailing list would be complaining about how dml.com doesn't resolve. On Fri, Jan 12, 2001 at 04:34:37PM -0500, Mike Andrews wrote: > On Fri, 12 Jan 2001 Mark.Andrews@nominum.com wrote: > > > > When one (but not both) of the nameservers for a domain replies > > > non-authoritatively, named will cache a negative response, rather than > > > asking the other nameserver. > > > > No. It caches that the server is lame for the zone then tries > > other servers. > > > > > Subsequent lookups return an immediate > > > failure. > > > > And what is logged when that happens? > > At the time of those lookups, nothing from Bind. Sendmail logs "Domain of > sender address foo@bar does not resolve". When it caches that the server > is lame, bind does log the expected "Lame server on foo.blah" message. > > > > > Restarting the nameserver, and then immediately querying the > > > same problematic domain DOES work, but only the first query. After a few > > > minutes/hours the domain stops working again. > > > > This sounds more like a bad delegation, parent and child > > zones dissagreeing on the nameserver RRset, than a lame > > server. > > > Servers are supposed to be serving the zone *before* they are > > delegated to. > > Either way, the other guys have their nameserver screwed up pretty badly. > I knew this already, though... > > > > Well both the servers for setel.com are lame as are se-tel.com. > > > > If all the sources of information are bad what do you expect > > the namesever to do. > > Hm. My named thinks ns2.se-tel.com is definitely lame, but not ns1 (at > least it's never logging ns1 as lame...) > > > > > In one sense this is "not my problem" because their name server shouldn't > > > be answering non-authoritatively in the first place. But the fact that > > > this started happening after a make world a few months ago, and that I > > > feel it should be a slight bit more tolerant of other people's sloppy > > > configurations, makes it my problem. > > And this is the real question that remains: > > Why did receiving email from places with one lame and one not-lame > nameserver work reliably in 4.1.1-RELEASE, and not in 4.2-STABLE? > > I realize (like in the farmersfrankfort.com) case that it's Qwest's > problem (not mine) that the second nameserver for that domain is lame. But > in 4.1.1-RELEASE it would still eventually get the right info from the one > that did work. It doesn't anymore. What changed in Bind or Sendmail to > make it less tolerant of everyone else's broken nameservers? I'm starting > to wonder, like Mike Tancsa's earlier response, if this is maybe specific > to Sendmail, or a Bind+Sendmail interaction... > > > Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com > VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY > Internet access for Frankfort, Lexington, Louisville and surrounding counties > www.fark.com: If it's not news, it's Fark. (Or something like that.) > > > > > > > > > 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 Sat Jan 13 13: 9:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from realtime.net (dragon.realtime.net [205.238.128.89]) by hub.freebsd.org (Postfix) with SMTP id D9B4937B69E for ; Sat, 13 Jan 2001 13:09:08 -0800 (PST) Received: from tigerfish2.my.domain ([205.238.153.169]) by realtime.net ; Sat, 13 Jan 2001 15:09:06 -0600 Received: (from brucegb@localhost) by tigerfish2.my.domain (8.11.1/8.11.1) id f0DL9uj37549 for freebsd-stable@freebsd.org; Sat, 13 Jan 2001 15:09:56 -0600 (CST) (envelope-from brucegb) Date: Sat, 13 Jan 2001 15:09:56 -0600 From: Bruce Burden To: freebsd-stable@freebsd.org Subject: Re: /swap too large? What?? Message-ID: <20010113150956.B37497@tigerfish2.my.domain> References: <20010113002643.A33278@tigerfish2.my.domain> <200101131927.f0DJRSS34276@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101131927.f0DJRSS34276@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Jan 13, 2001 at 11:27:28AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Matt, > > The only thing that can cause this is if you have configured an > absurdly large NSWAPDEV. > Well, I had NSWAPDEV set for 20 (why? I don't know!) but according to my calculations, that should still allow a 3.4GB swap, or 2x what I have. I have dropped things back to NSWAPDEV=3, and see if that does anything. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 13:16:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.tacni.net (unknown [216.178.136.166]) by hub.freebsd.org (Postfix) with SMTP id 46C4037B69B for ; Sat, 13 Jan 2001 13:16:07 -0800 (PST) Received: (qmail 36073 invoked from network); 13 Jan 2001 21:16:06 -0000 Received: from unknown (HELO arthur.tacni.net) (207.55.167.106) by 216.178.136.168 with SMTP; 13 Jan 2001 21:16:06 -0000 Received: (qmail 556 invoked by uid 1000); 13 Jan 2001 21:16:06 -0000 Date: Sat, 13 Jan 2001 15:16:06 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Re: Interesting plight Message-ID: <20010113151605.A530@superhero.org> References: <20010111224451.A277@superhero.org> <20010112133703.A17573@mail.catseye.net> <20010113105227.A248@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010113105227.A248@superhero.org>; from erichz@superhero.org on Sat, Jan 13, 2001 at 10:52:28AM -0600 X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 13, 2001 at 10:52:28AM -0600, Erich Zigler wrote: > Could something not be getting updated? I'm very confused here and at a > complete loss. Okay, I found the problem. I seemed to have gotten a extra COPTFLAGS in the bottom of my make.conf with some weird opts. So the kernel was being compiled with different optimizations then the world. This was fun. Thank you all for your help. -- Erich Zigler Hah! If they were going to do that, they'd be just as likely to buy some extra rope to keep the pigs from getting out of their rooftop aviary. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 13:28:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from level3.dynacom.net (level3.dynacom.net [206.107.213.213]) by hub.freebsd.org (Postfix) with SMTP id 5A9A037B6A0 for ; Sat, 13 Jan 2001 13:28:11 -0800 (PST) Received: (qmail 1344 invoked by uid 0); 13 Jan 2001 21:28:10 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 13 Jan 2001 21:28:10 -0000 Message-ID: <3A60C86A.5E60D4BB@urx.com> Date: Sat, 13 Jan 2001 13:28:10 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: bmah@FreeBSD.ORG Cc: whisky , freebsd-stable@FreeBSD.ORG Subject: Re: Mergemaster References: <014301c07d5c$1fc9dc80$0100000a@win2k> <3A605430.5D32DB56@urx.com> <200101131634.f0DGY8o36236@bmah-freebsd-0.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Bruce A. Mah" wrote: > > If memory serves me right, Kent Stewart wrote: > > > whisky wrote: > > > > > > How does one use mergemaster correctly after a make installworld of 4.2-R t > > o > > > 4.x-S > > > > Very, very carefully. > > That applies to pretty much any system administration task. > > > It will try to change all of the configuration > > files that have been updated. If you have added local mods, they > > disappear. > > Say again?!? Your "local mods" only disappear if you let mergemaster > overwrite them. It never does anything without telling you. That was my point. You have to recognize what you have modified and don't let mergemaster delete your changes unless they need to be. The addition of .../defaults solved most of my early problems. > > > I don't let it touch my firewall rules, ppp.conf, passwd, > > or groups. It will also try to change files root uses but I don't let > > it. I check when it changes my dot."*" files. If I have added local > > aliases or paths, I don't want them removed. The choices provided by > > mergemaster on them is always i(nstall new), d(elete new), or m(erge). > > Have you actually tried the last of the three options? I've found that > it works pretty well for merging in a set of local changes with a new > version of a file. You need to pay attention when doing the merge, > obviously. Yes, I have several times. On most of my files the merge option was ok but then I found a couple of files such as rc.firewall or ppp.conf where mergemaster was looking at such a small part of the picture that it was confusing. A poor choice and your access to the world suddenly disappears and you have to grab the backup and start over. I used its diff as a basis even when I did it manually. I also need to go back an try it on something other than the command line and I have more width available. Kent > > My advise: Run mergemaster after an installworld. Read the diffs it > produces. The first time you run it (on a system updated from > 4.2-RELEASE) you'll probably see a lot of changes. In general, if you > know you didn't modify a file, you can probably just let it install the > new version. Learn how sdiff works for handling merges of files, to > handle the case where you made a local modification and the original, > base file was also updated. The first few times you do this, make sure > to have a backup of /etc so you can bail yourself out if necessary. > > Bruce. > > ---------------------------------------------------------------------- > Part 1.2Type: application/pgp-signature -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 14: 6:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id DD4C937B402 for ; Sat, 13 Jan 2001 14:05:53 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0DM5pJ35749; Sat, 13 Jan 2001 14:05:51 -0800 (PST) (envelope-from dillon) Date: Sat, 13 Jan 2001 14:05:51 -0800 (PST) From: Matt Dillon Message-Id: <200101132205.f0DM5pJ35749@earth.backplane.com> To: Bruce Burden Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /swap too large? What?? References: <20010113002643.A33278@tigerfish2.my.domain> <200101131927.f0DJRSS34276@earth.backplane.com> <20010113150956.B37497@tigerfish2.my.domain> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Hi Matt, :> :> The only thing that can cause this is if you have configured an :> absurdly large NSWAPDEV. :> : Well, I had NSWAPDEV set for 20 (why? I don't know!) but : according to my calculations, that should still allow a 3.4GB : swap, or 2x what I have. : : I have dropped things back to NSWAPDEV=3, and see if that : does anything. : : Bruce That will fix it. Generally speaking the amount of bitmap space the kernel must allocate scales with (largest swap partition) * NSWAPDEV. An NSWAPDEV of 4 (the default) is reasonable for most swap configurations. But if you have NSWAPDEV of 20 and are only using one or two swap devices (and one of them is a gig), then the kernel winds up having to reserve bitmap space for (1 gig) x 20 blocks, which wastes a huge amount of kernel memory unnecessarily. This is all in the name of making interleaved swap work. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 15:49:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c007.snv.cp.net (c007-h008.c007.snv.cp.net [209.228.33.214]) by hub.freebsd.org (Postfix) with SMTP id 30FF637B401 for ; Sat, 13 Jan 2001 15:49:01 -0800 (PST) Received: (cpmta 9084 invoked from network); 13 Jan 2001 15:49:00 -0800 Received: from dsl-216-227-91-85.telocity.com (HELO zoso) (216.227.91.85) by smtp.telocity.com (209.228.33.214) with SMTP; 13 Jan 2001 15:49:00 -0800 X-Sent: 13 Jan 2001 23:49:00 GMT From: "Otter" To: , "whisky" Cc: Subject: RE: Date: Sat, 13 Jan 2001 18:54:09 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200101131639.f0DGdDa36364@bmah-freebsd-0.cisco.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -release is just a snapshot of -stable. the only difference between 4.2-release and 4.2-stable is that the code in -stable is a little newer, but basically the same userland functions and features. the only differnces would be the commits to -stable since the -release... about 2 months worth of changes, as i recall. -Otter }-----Original Message----- }From: owner-freebsd-stable@FreeBSD.ORG }[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Bruce A. Mah }Sent: Saturday, January 13, 2001 11:39 AM }To: whisky }Cc: freebsd-stable@FreeBSD.ORG }Subject: } } }If memory serves me right, "whisky" wrote: }> Is it recommended to cvsup from 4.2-RELEASE to 4.x-STABLE }> }> Any exploits/bugs that might persuade me to defaintely do it......? } }The release notes will tell you what's changed since the last release }along a branch, to within about a week. After you grab }4-STABLE sources }to your system, read one of the following as appropriate to your }architecture: } }/usr/src/release/texts/alpha/RELNOTES.TXT }/usr/src/release/texts/i386/RELNOTES.TXT } }You can also browse these files in the on-line CVS repository. } }Bruce. } } } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 16:57: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id AC05537B698 for ; Sat, 13 Jan 2001 16:56:40 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id CAA10348; Sun, 14 Jan 2001 02:53:55 +0200 To: Antony T Curtis Subject: Re: Bug in NFSv3 client Message-ID: <979433635.3a60f8a32794f@webmail.harmonic.co.il> Date: Sun, 14 Jan 2001 02:53:55 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG References: <20010103155533.B71238@math.uic.edu> <200101032243.f03Mhar51440@earth.backplane.com> <200101032308.f03N84f51776@earth.backplane.com> <3A5EF8A5.BC2E0AFD@abacus.co.uk> In-Reply-To: <3A5EF8A5.BC2E0AFD@abacus.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Antony T Curtis : > Matt Dillon wrote: > > > > Bleh. I'm wrong twice. Don't bother with either patch. The > version > > is supposed to be 8 bytes. Scrap both patches. > > > > I'll have to look into this some more. There is definitely some > > weirdness in the NFS code. It could be the VATTR_NULL() call on > the > > server side that is broken. > > > > -Matt > > Is FreeBSD's nfsd locking still broken? > Yes, AFAIK it's still not implemented. You can search the archives to find some university version of nfs.lockd which may or may not work. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 13 17: 3:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id C5E7137B402 for ; Sat, 13 Jan 2001 17:03:37 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id DAA10355; Sun, 14 Jan 2001 03:01:19 +0200 To: Alessandro de Manzano Subject: Re: PR #24059 - USB still broken in SMP ! Message-ID: <979434079.3a60fa5fc6469@webmail.harmonic.co.il> Date: Sun, 14 Jan 2001 03:01:19 +0200 (IST) From: Roman Shterenzon Cc: "stable@freebsd.org" References: <20010112171919.B67D1D60F9@viger.playstos.com> <14943.16761.965760.182463@hip186.ch.intel.com> <20010112213610.E615@libero.sunshine.ale> In-Reply-To: <20010112213610.E615@libero.sunshine.ale> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Alessandro de Manzano : > > Ok. I've got a P2B-DS motherboard (rev 1.06 I believe with the latest > BIOS) > > and I'm running an SMP kernel using two 500Mhz Pentium III's. I use > USB to > > connect to my Canon S10 digital camera all the time. No problems. I've > not > > used USB for anything other than this though--no mice, keyboards, > disks, > > memory readers, etc. > > Thanks for the answer ! :-) > > I'm happy to hear USB works for you, so I could only guess some things: > > 1) we have different USB controllers, the Asus P2B-DS (a MB I have > where I work) use Intel chipset and my Microstar MS-6321 use an VIA > one. > > 2) I tried with the mouse only, also if error reports are reported by > kernel also if the USB bus is "empty" and idle. > > I really hope my problem could be resolved in a future evoltion of USB > drivers.. ;-) > > Thanks a lot! > Check if your motherboard vendor has some BIOS updates that are relevant. --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message