From owner-freebsd-current Sun Mar 28 3:39:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiev.sovam.com (kiev.sovam.com [194.186.143.7]) by hub.freebsd.org (Postfix) with ESMTP id 5EF6C152CC for ; Sun, 28 Mar 1999 03:39:20 -0800 (PST) (envelope-from doka@kiev.sovam.com) Received: from doka (helo=localhost) by kiev.sovam.com with local-esmtp (Exim 2.12 #1) id 10RDu7-0006sv-00; Sun, 28 Mar 1999 14:38:59 +0300 Date: Sun, 28 Mar 1999 14:38:58 +0300 (EEST) From: Vladimir Litovka Reply-To: doka@triton.kiev.sovam.com To: "Scot W. Hetzel" Cc: freebsd-current@freebsd.org Subject: Re: Problem with "make release" In-Reply-To: <019001be7886$a7e4e7e0$8dfee0d1@westbend.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! On Sat, 27 Mar 1999, Scot W. Hetzel wrote: > > without errors. Optimization.... BTW do FreeBSD's team have plans to use > > egcs as main compiler or no? Or gcc 2.8.x at least... > > > The FreeBSD team is looking into adding egcs into 4.0-CURRENT as the next > compiler for FreeBSD. Currently, it appears to be working but hasn't been > integrated into the 4.0-CURRENT source tree. Thank you :-) BTW do you know - do they going to use PentiumGCC? This compiler - the set of patches to egcs, which makes egcs able to optimize code for Pentium and above processors. As said on the homepage of PentiumGCC, there is up to 25% perfomance improvement may be when using pgcc instead of gcc and egcs. It's homepage is http://www.goof.com/pcg/ -- Yours sincerely, Vladimir Litovka, hostmaster of Sovam Teleport Kiev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 5:27:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 17CFF14DFF for ; Sun, 28 Mar 1999 05:27:21 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id RAA12923 for ; Sun, 28 Mar 1999 17:27:01 +0400 (MSD) Date: Sun, 28 Mar 1999 17:27:01 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@freebsd.org Subject: -stable problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Why this happens? > telnet x.x.x.x nntp Trying x.x.x.x... Connected to x.x.x.x. Escape character is '^]'. assertion "nsegs == 2" failed: file "/usr/src/libexec/rtld-elf/map_object.c", line 158 Connection closed by foreign host. Also machine closes any connection to any port. It happens not too often, but happens. It running 3.1-STABLE. And INN 2.3-current. Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 9:38:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id C456A14DE9 for ; Sun, 28 Mar 1999 09:38:23 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a35 (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id NAA11574 for ; Sun, 28 Mar 1999 13:55:37 -0500 Message-ID: <000101be7941$1b2e3200$2300000a@a35.my.intranet> From: "RT" To: Subject: 3com Nic Problems Date: Sun, 28 Mar 1999 12:33:33 -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 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heres are the nic combinations I've tried in one machine: 3com 905 (at 100mbit) & 3com 905b (at 10mbit) 3com 905b (at 100mbit) & 3com 905 (at 10mbit) 3com 905 (at 100mbit) & realtek 8039 (at 10mbit) 3com 905b (at 100mbit) & realtek (at 10mbit) 3com 905b (at 100mbit) & ne2000 (at 10mbit) In each case the 3com operating at 100mbit failed to do so smoothly. In some cases I receive device time-outs, on bootup "xl0 command not completed", and in some cases no warning at all.. 100mbit will peak at 4MB/s, then all of a sudden stop, then go racing off, then stop... This doesn't happen if the 3com cards are operated by themselves. The realtek & ne2000 (while slow) perform without these problems. I believe the xl? drivers have a problem. My system is 4-current (updated weekly). I only starting using 2 nics in the machine last week. (When I got my cable modem). The problem occurs both with and without natd & ipfw. It also doesn't matter which of the 4 cards is receiving the data (as long as there is only one of them). Any more information needed? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 9:56:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id BC729156EF for ; Sun, 28 Mar 1999 09:56:16 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a35 (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id OAA11621 for ; Sun, 28 Mar 1999 14:13:31 -0500 Message-ID: <000501be7943$9b0c5900$2300000a@a35.my.intranet> From: "RT" To: Subject: Re: 3com Nic Problems Date: Sun, 28 Mar 1999 12:51:27 -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 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sure enough when reading my own bug report, I found something else: xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x30 int a irq 9 on pci0.3.0 xl0: command never completed! xl0: Ethernet address: 00:50:04:11:5f:16 xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) xl1: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 12 on pci0.4.0 xl1: Ethernet address: 00:60:97:de:4e:38 xl1: autoneg complete, link status good (half-duplex, 10Mbps) xl0 should be 100mbit --> Not detected xl1 should be 10mbit --> Detected I switched the cards around, same thing happens. But with only the 100mbit network attached, it's detected fine. Thanks again for any suggestions. -----Original Message----- From: RT To: current@FreeBSD.ORG Date: Sunday, March 28, 1999 1:56 PM Subject: 3com Nic Problems >Heres are the nic combinations I've tried in one machine: > >3com 905 (at 100mbit) & 3com 905b (at 10mbit) >3com 905b (at 100mbit) & 3com 905 (at 10mbit) >3com 905 (at 100mbit) & realtek 8039 (at 10mbit) -= Snip =- >Any more information needed? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 10:21:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id BCCDF1555B for ; Sun, 28 Mar 1999 10:21:53 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA04739 for current@freebsd.org; Sun, 28 Mar 1999 13:31:02 -0500 From: Bill Paul Message-Id: <199903281831.NAA04739@skynet.ctr.columbia.edu> Subject: Re: 3com Nic Problems To: current@freebsd.org Date: Sun, 28 Mar 1999 13:31:01 -0500 (EST) In-Reply-To: <000101be7941$1b2e3200$2300000a@a35.my.intranet> from "RT" at Mar 28, 99 12:33:33 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3778 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, RT had to walk into mine and say: > Heres are the nic combinations I've tried in one machine: > > 3com 905 (at 100mbit) & 3com 905b (at 10mbit) > 3com 905b (at 100mbit) & 3com 905 (at 10mbit) > 3com 905 (at 100mbit) & realtek 8039 (at 10mbit) > 3com 905b (at 100mbit) & realtek (at 10mbit) > 3com 905b (at 100mbit) & ne2000 (at 10mbit) > > In each case the 3com operating at 100mbit failed to do so smoothly. In > some cases I receive device time-outs, on bootup "xl0 command not > completed", Ignore the command failed to complete message. It's not fatal. It's amazing how many people get all flustered when they see this. > and in some cases no warning at all.. It's timing dependent. > 100mbit will peak at 4MB/s, then all of a sudden stop, then go racing off, > then stop... This is a classic "I didn't configure my card correctly" symptom. For the Nth time, both sides of the link must use the same modes. You can't mix and match speed and duplex settings like they're tuneable parameters that you can tweak to get more performance. Both sides must match. If they can't figure out how to match on their own using autonegotiation, make them match. (You're the one with the brain and the reasoning skills after all. Well, that's the theory anyway.) If you want two 100Mbps NICs connected back to back (via crossover cable), then do the following on _both_ sides: # ifconfig xl0 media 100baseTX mediaopt full-duplex The symptoms you're describing indicate a condition where one side of the link is set for full duplex and the other is set for half. This doesn't work: when the NIC is in full duplex mode, it turns off the collision detection logic (since in theory you're not supposed to have collisions on a full duplex link). If one side is doing collision detection and the other isn't, you tend to see 'stuttery' performance. If you're connecting a NIC to a 10Mbps hub (that's hub as in repeater, not a switch), then you must set the NIC for 10Mbps half-duplex: # ifconfig xl0 media 10baseT/UTP mediaopt half-duplex If you're connecting a NIC to a 100Mbps hub (again, that's a hub as in repeater, not a switch), then you must set the NIC for 100Mbps half-duplex: # ifconfig xl0 media 100baseTX mediaopt half-duplex If you're connecting a NIC to a 100Mbps switch port, then in theory the switch port and the NIC will perform NWAY autoselection and get the modes right on their own. Sometimes this fails though, in which case you should manually configure the switch for the mode you want and configure the NIC to match. When you connect two NICs back to back and one of them supports NWAY and the other doesn't, the NIC with NWAY autonegotiation support can sometimes get the mode wrong. In this case, you should manually configure the NIC with NWAY so that agrees with the other NIC's modes using ifconfig as shown above. The NE2000 and 8039 boards don't support full duplex. So if you connect a one of these to the 3c90x NICs via crossover cable, then you must force the 3Com nic to 10Mbps half-duplex: # ifconfig xl0 media 10baseT/UTP mediaopt half-duplex This is because the NE2K and 8039 (ne2k compatible) don't support full duplex mode. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 10:58:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7690C14E15 for ; Sun, 28 Mar 1999 10:58:54 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA55984 for current@freebsd.org; Sun, 28 Mar 1999 20:58:33 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199903281858.UAA55984@freebsd.dk> Subject: UPDATE4: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Sun, 28 Mar 1999 20:58:33 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fourth update to the new ATA/ATAPI driver: Well, better late than newer, but things has been hectic around here, sorry for the long delay. DMA support has been added to the ATA disk driver. This only works on Intel PIIX3/4, Acer Aladdin and Promise controllers. The promise support works without the BIOS on the board, and timing modes are set to support up to UDMA speed. This solves the problems with having more than one promise controller in the same system. There is support for "generic" DMA, that might work on other controllers, but now you have been warned :) More chipset specific code will come soon, I have to find testers with the approbiate HW, more on that when I have it ready. The system now uses its own major numbers, please run MAKEDEV with the devices you need (ad?, acd?, afd?, ast?). For now the disk driver will also attach to the old wd major so one can at least boot without this step, but be warned, this will eventually go away. The bootblocks will have to be changed before one can boot directly from an "ad" device though. Fixed problems: All known hang problems should be solved The probe code has been sligthly changed, this should solve the reports I have lying around (I hope). Hangs when accessing ata & atapi device on the same channel simultaniously. A real braino in ata_start caused this, fixed. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. Especially the DMA support can hose your disk real bad if anything goes wrong, agaiin you have been warned :) But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 14:58: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C55CC153E1 for ; Sun, 28 Mar 1999 14:57:44 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id RAA78492; Sun, 28 Mar 1999 17:55:57 -0500 (EST) Date: Sun, 28 Mar 1999 17:55:55 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: <199903281858.UAA55984@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried this out just as soon as I saw the announcement! Your driver is really coming along well. I have three basic problems with it: 1. A hard reset is necessary to get the CD-ROM drive to work with acd. wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked 2. My LS-120 still has no reliability with the driver, as reads are corrupted extremely often. wdc1: unit 0 (atapi): , removable, iordy wfd0: medium type unknown (no disk) 3. DMA is ineffective with file-system use. I can read from the raw device rad0 at 4.5MB/s with a 1mb block size, but when I use iozone performance is around 2.5MB/s. Mounting wd shouldn't affect that, should it? I used the same device special files to mount as before, with ATA_STATIC being used, and noticed this. Better yet, I'll try this with a corrected fstab then report back. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 15:14:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 4C18715073 for ; Sun, 28 Mar 1999 15:14:40 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (ts6-22-ppp.ipass.net [198.78.59.22]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id SAA24554 for ; Sun, 28 Mar 1999 18:14:17 -0500 (EST) Message-ID: <36FEB860.38A94122@ipass.net> Date: Sun, 28 Mar 1999 18:16:49 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re Post!: What to make of the script /usr/src/tools/LibraryReport/LibraryReport.tcl? References: <36FC43F5.2DA10D7F@ipass.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello again, Posted this a few days ago...no response... so I am trying again. Later Michael "Michael E. Mercer" wrote: > > Hello, > > Sorry for posting to two lists...not sure where this should go. > > I saw an email where someone mentioned this script... > > how do I make out what this script is telling me and even > though this script says a library is stale, does this mean > I can remove it??? > > Also I read someones post about the motherboard not getting enough > power and causing things to run slow...how do I check if I fall > into this catagory? and if I do fall into it, how do I remedy it? > > Thanks > Michael Mercer > mmercer@ipass.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 15:27:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 144671539E for ; Sun, 28 Mar 1999 15:27:43 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id SAA78880; Sun, 28 Mar 1999 18:25:27 -0500 (EST) Date: Sun, 28 Mar 1999 18:25:27 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Mar 1999, Brian Feldman wrote: > I tried this out just as soon as I saw the announcement! Your driver is > really coming along well. I have three basic problems with it: > > 1. A hard reset is necessary to get the CD-ROM drive to work with acd. > > wdc0: unit 1 (atapi): , removable, dma, iordy > wcd0: drive speed 2067KB/sec, 128KB cache > wcd0: supported read types: CD-R, CD-DA > wcd0: Audio: play, 16 volume levels > wcd0: Mechanism: ejectable tray > wcd0: Medium: no/blank disc inside, unlocked > > > 2. My LS-120 still has no reliability with the driver, as reads are > corrupted extremely often. > > wdc1: unit 0 (atapi): , removable, iordy > wfd0: medium type unknown (no disk) > > > 3. DMA is ineffective with file-system use. I can read from the raw > device rad0 at 4.5MB/s with a 1mb block size, but when I use iozone performance > is around 2.5MB/s. Mounting wd shouldn't affect that, should it? I used the > same device special files to mount as before, with ATA_STATIC being used, > and noticed this. Better yet, I'll try this with a corrected fstab then > report back. Didn't think it would help... I corrected fstab, but the slow speed is still there. (And I notice it's time to fix my sig.) > > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 19:20: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 526A614ECD for ; Sun, 28 Mar 1999 19:19:58 -0800 (PST) (envelope-from ganymede@cloud9.net) Received: from earl-grey.cloud9.net (earl-grey [168.100.1.1]) by russian-caravan.cloud9.net (Postfix) with ESMTP id 57CAE763AA; Sun, 28 Mar 1999 22:06:17 -0500 (EST) Date: Sun, 28 Mar 1999 22:06:17 -0500 (EST) From: Tugrul Galatali To: Soren Schmidt Cc: current@freebsd.org Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: <199903281858.UAA55984@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There seems to be an oopsie with the includes on a system without PCI in ata-dma.c: #include "ata.h" +#include + #if NATA > 0 -#include "pci.h" #if NPCI > 0 +#include "pci.h" #include #include #include My 486 still spits this out tho: [...] ata0 at 0x1f0-0x1f7 irq 14 on isa [...] ad0: ATA-? disk at ata0 as master ad0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=3, dmamode=1, udmamode=-1 ad0: 16 secs/int, 0 depth queue, PIO mode changing root device to wd0s1a ad0: invalid primary partition table: no magic changing root device to wd0a ad0: invalid primary partition table: no magic error 22: panic: cannot mount root (2) My PIIX3 box isn't happy with this update either: [...] ata-pci0: rev 0x00 on pci0.7.1 ata-pci0: Busmastering DMA supported [...] ata0 at 0x01f0 irq 14 on ata-pci0 [...] ata0: master: settting up WDMA2 mode on PIIX3/4 chip OK ad0: ATA-? disk at ata0 as master ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata0 as slave acd0: drive speed 1779 - 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s1a [...] acd0: rezero failed <-- Whenever I try to mount my cdrom drive. With or without a cd in there. mount gives me "mount: Input/output error" I can't eject the cd tray either after I mount the drive. Its fine after boot but before I attempt to mount something. Tugrul Galatali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 21: 9: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id E98D114D67; Sun, 28 Mar 1999 21:08:58 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (ts2-92-ppp.ipass.net [207.120.205.92]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id AAA09645; Mon, 29 Mar 1999 00:08:37 -0500 (EST) Message-ID: <36FF0B69.BD0C336E@ipass.net> Date: Mon, 29 Mar 1999 00:11:05 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-questions@FreeBSD.ORG" , freebsd-current@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: apache13-fp probs: fpsrvadm.exe core dumps. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I am running 4.0 current and am trying to get apache13-fp to install, however the executable fpsrvadm.exe core dumps. I have tried to do this on two different 4.0 machines, same thing happens on both. Is there something I am missing? later Michael Mercer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 21:15:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 81A6315472; Sun, 28 Mar 1999 21:15:19 -0800 (PST) (envelope-from norn@norn.ca.eu.org) Received: (from norn@localhost) by norn.ca.eu.org (8.9.3/8.9.3) id VAA00281; Sun, 28 Mar 1999 21:14:18 -0800 (PST) (envelope-from norn) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36FF0B69.BD0C336E@ipass.net> Date: Sun, 28 Mar 1999 21:14:18 -0800 (PST) Reply-To: Chris Piazza From: Chris Piazza To: "Michael E. Mercer" Subject: RE: apache13-fp probs: fpsrvadm.exe core dumps. Cc: freebsd-ports@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, "freebsd-questions@FreeBSD.ORG" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Mar-99 Michael E. Mercer wrote: > Hello all, > > I am running 4.0 current and am trying to get apache13-fp > to install, however the executable fpsrvadm.exe core dumps. > > I have tried to do this on two different 4.0 machines, > same thing happens on both. > > Is there something I am missing? > > later > Michael Mercer > > Yes, dg 1999/03/11 10:28:47 PST Modified files: sys/i386/conf Makefile.i386 kernel.script sys/i386/include pmap.h Log: Increased kernel virtual address space to 1GB. NOTE: You MUST have fixed bootblocks in order to boot the kernel after this! Also note that this change breaks BSDI BSD/OS compatibility. Also increased default NKPT to 17 so that FreeBSD can boot on machines with >=2GB of RAM. Booting on machines with exactly 4GB requires other patches, not included. Either manually back this out or use 3.1. --- Chris Piazza Abbotsford, BC, Canada cpiazza@home.net finger norn@norn.ca.eu.org for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 28 23:45:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5CD1715762 for ; Sun, 28 Mar 1999 23:45:23 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA57288; Mon, 29 Mar 1999 09:45:01 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199903290745.JAA57288@freebsd.dk> Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: from Brian Feldman at "Mar 28, 1999 5:55:55 pm" To: green@unixhelp.org (Brian Feldman) Date: Mon, 29 Mar 1999 09:45:01 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Feldman wrote: > I tried this out just as soon as I saw the announcement! Your driver is > really coming along well. I have three basic problems with it: > > 1. A hard reset is necessary to get the CD-ROM drive to work with acd. > > wdc0: unit 1 (atapi): , removable, dma, iordy > wcd0: drive speed 2067KB/sec, 128KB cache > wcd0: supported read types: CD-R, CD-DA > wcd0: Audio: play, 16 volume levels > wcd0: Mechanism: ejectable tray > wcd0: Medium: no/blank disc inside, unlocked Ugh, one of those NEC's again, it seems there are many problems with their CDROM's, I'll try to get ahold of some... > > 2. My LS-120 still has no reliability with the driver, as reads are > corrupted extremely often. > > wdc1: unit 0 (atapi): , removable, iordy > wfd0: medium type unknown (no disk) Hmm, my ZIP works just fine, I'll see what I can come up with.. > 3. DMA is ineffective with file-system use. I can read from the raw > device rad0 at 4.5MB/s with a 1mb block size, but when I use iozone performance > is around 2.5MB/s. Mounting wd shouldn't affect that, should it? I used the > same device special files to mount as before, with ATA_STATIC being used, > and noticed this. Better yet, I'll try this with a corrected fstab then > report back. This is more likely due to the last changes Julian/Matt has committed to vfs_bio.c et all, it hoses our I/O performance pretty badly. There is work underways to fix it though. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 0:12:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3305214C16 for ; Mon, 29 Mar 1999 00:12:11 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA57354; Mon, 29 Mar 1999 10:11:50 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199903290811.KAA57354@freebsd.dk> Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: from Tugrul Galatali at "Mar 28, 1999 10: 6:17 pm" To: ganymede@cloud9.net (Tugrul Galatali) Date: Mon, 29 Mar 1999 10:11:50 +0200 (CEST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Tugrul Galatali wrote: > > There seems to be an oopsie with the includes on a system without PCI in > ata-dma.c: > > #include "ata.h" > +#include > + > #if NATA > 0 > -#include "pci.h" > #if NPCI > 0 > +#include "pci.h" > #include > #include > #include The "pci.h" should be before the if NPCI or it will never be defined :) > My 486 still spits this out tho: > > [...] > ata0 at 0x1f0-0x1f7 irq 14 on isa > [...] > ad0: ATA-? disk at ata0 as master > ad0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S > ad0: piomode=3, dmamode=1, udmamode=-1 > ad0: 16 secs/int, 0 depth queue, PIO mode > changing root device to wd0s1a > ad0: invalid primary partition table: no magic > changing root device to wd0a > ad0: invalid primary partition table: no magic > error 22: panic: cannot mount root (2) Hmm, I'll bet the disk doesn't grok the 16 secs/int or the controller doesn't support 32bit transfers... This I really should check for... > My PIIX3 box isn't happy with this update either: > > [...] > ata-pci0: rev 0x00 on pci0.7.1 > ata-pci0: Busmastering DMA supported > [...] > ata0 at 0x01f0 irq 14 on ata-pci0 > [...] > ata0: master: settting up WDMA2 mode on PIIX3/4 chip OK > ad0: ATA-? disk at ata0 as master > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > ad0: piomode=4, dmamode=2, udmamode=-1 > ad0: 16 secs/int, 0 depth queue, DMA mode > acd0: CDROM drive at ata0 as slave > acd0: drive speed 1779 - 4134KB/sec, 128KB cache > acd0: supported read types: CD-R, CD-RW, CD-DA, packet track > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > changing root device to wd0s1a > [...] > acd0: rezero failed <-- Whenever I try to mount my cdrom drive. With or > without a cd in there. mount gives me "mount: Input/output error" You should only get the rezero when you are WRITING to the CD, really wierd... > I can't eject the cd tray either after I mount the drive. Its fine > after boot but before I attempt to mount something. If you open the device and mount it, the driver will lock the CD in the drive, if something goes wrong it might be stuck in there... Granted I should do something about that too... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 1:58:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from firewall2.lehman.com (firewall.Lehman.COM [192.147.65.67]) by hub.freebsd.org (Postfix) with ESMTP id 055FA14E6C; Mon, 29 Mar 1999 01:58:53 -0800 (PST) (envelope-from nclayton@lehman.com) Received: from relay.messaging-svcs2.lehman.com by firewall2.lehman.com (8.8.6/8.8.6) id EAA06431; Mon, 29 Mar 1999 04:58:14 -0500 (EST) Received: from lonmailhost.lehman.com by relay.messaging-svcs2.lehman.com (8.8.5/8.8.5) id EAA02039; Mon, 29 Mar 1999 04:57:42 -0500 (EST) Received: by lonmailhost.lehman.com (SMI-8.6/Lehman Bros. V1.5) id KAA14263; Mon, 29 Mar 1999 10:57:41 +0100 Message-ID: <19990329105741.L23968@lehman.com> Date: Mon, 29 Mar 1999 10:57:41 +0100 From: nclayton@lehman.com To: Kris Kennaway , Nik Clayton Cc: current@freebsd.org, doc@freebsd.org Subject: Re: Handbook DocBook cutover complete References: <19990327162554.K3136@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Kris Kennaway on Sun, Mar 28, 1999 at 04:40:22PM +0930 Organization: Lehman Brothers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris, On Sun, Mar 28, 1999 at 04:40:22PM +0930, Kris Kennaway wrote: > On Sat, 27 Mar 1999, Nik Clayton wrote: > > Almost a year ago I started the project to switch the Handbook over > > from LinuxDoc to DocBook. > > Can I ask what the differences and benefits are? As follows; * LinuxDoc is descended from the QWERTZ DTD, and was designed to serve the needs of the Linux Documentation Project. DocBook has been designed to mark up technical books and articles, and has been designed by representatives from a large number of companies (this, for once, has not been a bad thing). It's large, comprehensive, and well supported. * LinuxDoc is designed to be quite close to LaTeX. This means there's a lot of presentational markup (i.e., markup that describes things as being bold, or italic, and so on), a lot like HTML. DocBook contains *no* presentational markup, it's entirely semantic. To write a filename in LinuxDoc you would write /path/to/some/file where "" means "teletype", i.e., a monospaced font. If you wanted to write a command the user types in, you would use the same thing, ls /etc In DocBook, you would write /path/to/some/file ls /etc When processed, both those might be displayed in a monospaced font. However, the DocBook version includes extra information. We don't do it yet, but the DocBook Handbook will eventually include several indices. One of these will be a list of each page where each filename is mentioned, allowing you to quickly see all the places where (for example) ppp.conf is referred to. This index would catch every reference to ppp.conf used as a filename, but would ignore those where it was mentioned as part of a command. So "ppp.conf" would be indexed, but "vi ppp.conf" wouldn't. The only way to do this using LinuxDoc would be to index everywhere 'ppp.conf' appeared, which would *also* catch the second example, which is not what you want. * DocBook is extensible. It's relatively easy to add your own elements, for things that are missing from DocBook. I've done this for the Handbook, adding things like "" and "". This is harder to with LinuxDoc. * The Linux Documentation Project is moving away from LinuxDoc to DocBook. I *think* the FreeBSD Doc. Proj. switched first, and I'm pretty certain the FreeBSD Handbook is the largest free set of documentation that currently uses DocBook. I could be wrong about that though. * There's an XML implementation of DocBook (currently unofficial). This will be more important in the future, as XML browsers become more widespread. * Tools to convert DocBook to other formats are not quite as advanced as the LinuxDoc tools, but are getting their rapidly. As it currently stands in the repository, the DocBook Handbook can be converted to HTML, Postscript, plain text, and Microsoft RTF. A bug that I'll fix this week is currently preventing PDF generation. Word .doc support is in the pipeline as well, probably for the end of this week too (I've now given some money to the evil empire so I can test the output myself). Next on the list will be whatever internal format the Palm Pilot uses. I imagine this won't be too useful for the Handbook, but will probably be quite handy for the FAQ. . . More information at http://www.freebsd.org/~nik/primer/index.html N -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- --+==[ Year 2000 Testing: It's about time. . . ]==+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 3: 2:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6384D158D9; Mon, 29 Mar 1999 03:02:21 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id GAA86805; Mon, 29 Mar 1999 06:01:46 -0500 (EST) Date: Mon, 29 Mar 1999 06:01:45 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: nclayton@lehman.com Cc: Kris Kennaway , Nik Clayton , current@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: Handbook DocBook cutover complete In-Reply-To: <19990329105741.L23968@lehman.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Mar 1999 nclayton@lehman.com wrote: > Kris, > > On Sun, Mar 28, 1999 at 04:40:22PM +0930, Kris Kennaway wrote: > > On Sat, 27 Mar 1999, Nik Clayton wrote: > > > Almost a year ago I started the project to switch the Handbook over > > > from LinuxDoc to DocBook. > > > > Can I ask what the differences and benefits are? > > As it currently stands in the repository, the DocBook Handbook can be > converted to HTML, Postscript, plain text, and Microsoft RTF. A bug > that I'll fix this week is currently preventing PDF generation. > > Word .doc support is in the pipeline as well, probably for the end of > this week too (I've now given some money to the evil empire so I can > test the output myself). Why? We can use StarOffice 5.0x, after all. > > Next on the list will be whatever internal format the Palm Pilot uses. > I imagine this won't be too useful for the Handbook, but will probably > be quite handy for the FAQ. . . Do you mean the Memo format or the Doc format? I hope you mean Doc... It might not even be worth it to do this, since a very nice, fast browser (Palmscape) has been around for a while on the Palm, and an offline browser called Plucker. > > More information at > > http://www.freebsd.org/~nik/primer/index.html > > N > -- > --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- > --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- > --+==[ Year 2000 Testing: It's about time. . . ]==+-- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 3: 2:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E0EB614EB3 for ; Mon, 29 Mar 1999 03:02:48 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (d60-077.leach.ucdavis.edu [169.237.60.77]) by relay.nuxi.com (8.9.2/8.9.1) with ESMTP id DAA98793 for ; Mon, 29 Mar 1999 03:02:29 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA01309 for current@freebsd.org; Mon, 29 Mar 1999 11:02:28 GMT (envelope-from obrien) Date: Mon, 29 Mar 1999 03:02:28 -0800 From: "David O'Brien" To: current@freebsd.org Subject: HEADS UP!! NOAOUT `make world' knob changed Message-ID: <19990329030228.A1290@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just changed made a change concerning the building of legacy a.out bits during `make world'. Previous to my change, one would define "NOAOUT" to keep from building the legacy a.out bits. Now one would define "WANT_AOUT" to build them. The default of building a.out bits gets in the way of some other changes I will make to the `build world' process soon. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 3:23:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from firewall2.lehman.com (firewall.Lehman.COM [192.147.65.67]) by hub.freebsd.org (Postfix) with ESMTP id 4D4E415431; Mon, 29 Mar 1999 03:23:17 -0800 (PST) (envelope-from nclayton@lehman.com) Received: from relay.messaging-svcs2.lehman.com by firewall2.lehman.com (8.8.6/8.8.6) id GAA24861; Mon, 29 Mar 1999 06:22:56 -0500 (EST) Received: from lonmailhost.lehman.com by relay.messaging-svcs2.lehman.com (8.8.5/8.8.5) id GAA17941; Mon, 29 Mar 1999 06:22:24 -0500 (EST) Received: by lonmailhost.lehman.com (SMI-8.6/Lehman Bros. V1.5) id MAA20182; Mon, 29 Mar 1999 12:22:23 +0100 Message-ID: <19990329122223.D14492@lehman.com> Date: Mon, 29 Mar 1999 12:22:23 +0100 From: nclayton@lehman.com To: Brian Feldman Cc: Kris Kennaway , Nik Clayton , current@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: Handbook DocBook cutover complete References: <19990329105741.L23968@lehman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Brian Feldman on Mon, Mar 29, 1999 at 06:01:45AM -0500 Organization: Lehman Brothers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 29, 1999 at 06:01:45AM -0500, Brian Feldman wrote: > > Word .doc support is in the pipeline as well, probably for the end of > > this week too (I've now given some money to the evil empire so I can > > test the output myself). > > Why? We can use StarOffice 5.0x, after all. * Not if you're on a 2.2-stable system. Don't mock, because I still am, until I find the time to upgrade. At least, I could never get it to work solidly for any length of time. I know there have been updates, but there's only so many times I'm prepared to download it. * People who haven't yet switched to using FreeBSD can get a reasonably good printed copy of the documentation (at the moment just the Handbook, but eventually all the docs) on a Windows platform. * My accountant likes various bits and pieces to be entered in to their home grown Access DB. So I needed to get hold of Office anyway (and as an aside, the ODBC driver for Postgres works very nicely). > > Next on the list will be whatever internal format the Palm Pilot uses. > > I imagine this won't be too useful for the Handbook, but will probably > > be quite handy for the FAQ. . . > > Do you mean the Memo format or the Doc format? I hope you mean Doc... It > might not even be worth it to do this, since a very nice, fast browser > (Palmscape) has been around for a while on the Palm, and an offline browser > called Plucker. I don't know yet, I need to get a Pilot :-) I'm open to recommendations, and/or pointers to specifications for the format. And if there are any programmers out there looking for something to do, this could be quite a nice task. N -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- --+==[ Year 2000 Testing: It's about time. . . ]==+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 3:35: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7618D15524; Mon, 29 Mar 1999 03:34:57 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id GAA87088; Mon, 29 Mar 1999 06:34:28 -0500 (EST) Date: Mon, 29 Mar 1999 06:34:27 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: nclayton@lehman.com Cc: Kris Kennaway , Nik Clayton , current@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: Handbook DocBook cutover complete In-Reply-To: <19990329122223.D14492@lehman.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Mar 1999 nclayton@lehman.com wrote: > On Mon, Mar 29, 1999 at 06:01:45AM -0500, Brian Feldman wrote: > > > Word .doc support is in the pipeline as well, probably for the end of > > > this week too (I've now given some money to the evil empire so I can > > > test the output myself). > > > > Why? We can use StarOffice 5.0x, after all. > > * Not if you're on a 2.2-stable system. Don't mock, because I still am, > until I find the time to upgrade. At least, I could never get it to work > solidly for any length of time. I know there have been updates, but > there's only so many times I'm prepared to download it. I meant use StarOffice to test out the Office .docs. > > * People who haven't yet switched to using FreeBSD can get a reasonably > good printed copy of the documentation (at the moment just the Handbook, > but eventually all the docs) on a Windows platform. > > * My accountant likes various bits and pieces to be entered in to their > home grown Access DB. So I needed to get hold of Office anyway (and as > an aside, the ODBC driver for Postgres works very nicely). > > > > Next on the list will be whatever internal format the Palm Pilot uses. > > > I imagine this won't be too useful for the Handbook, but will probably > > > be quite handy for the FAQ. . . > > > > Do you mean the Memo format or the Doc format? I hope you mean Doc... It > > might not even be worth it to do this, since a very nice, fast browser > > (Palmscape) has been around for a while on the Palm, and an offline browser > > called Plucker. > > I don't know yet, I need to get a Pilot :-) I'm open to recommendations, > and/or pointers to specifications for the format. Doc is a nice format, but it's not hypertext. Check out ports/palm/pilot_makedoc > > And if there are any programmers out there looking for something to do, > this could be quite a nice task. > > N > -- > --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- > --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- > --+==[ Year 2000 Testing: It's about time. . . ]==+-- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 5:37:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 6A70314FD7 for ; Mon, 29 Mar 1999 05:37:36 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 11656 invoked from network); 29 Mar 1999 13:36:54 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 29 Mar 1999 13:36:54 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.3/8.9.1) id IAA00405; Mon, 29 Mar 1999 08:36:51 -0500 (EST) Message-Id: <199903291336.IAA00405@y.dyson.net> Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: <199903281858.UAA55984@freebsd.dk> from Soren Schmidt at "Mar 28, 99 08:58:33 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Mon, 29 Mar 1999 08:36:51 -0500 (EST) Cc: current@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt said: > > DMA support has been added to the ATA disk driver. > This only works on Intel PIIX3/4, Acer Aladdin and Promise controllers. > The promise support works without the BIOS on the board, > and timing modes are set to support up to UDMA speed. This > solves the problems with having more than one promise controller > in the same system. > Excellent!!! -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 5:58:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 83A5C15405 for ; Mon, 29 Mar 1999 05:58:55 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA57987; Mon, 29 Mar 1999 15:58:34 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199903291358.PAA57987@freebsd.dk> Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: <199903291336.IAA00405@y.dyson.net> from "John S. Dyson" at "Mar 29, 1999 8:36:51 am" To: dyson@iquest.net Date: Mon, 29 Mar 1999 15:58:34 +0200 (CEST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems John S. Dyson wrote: > Soren Schmidt said: > > > > DMA support has been added to the ATA disk driver. > > This only works on Intel PIIX3/4, Acer Aladdin and Promise controllers. > > The promise support works without the BIOS on the board, > > and timing modes are set to support up to UDMA speed. This > > solves the problems with having more than one promise controller > > in the same system. > Excellent!!! Yeah, except there is a bug in the code that always makes the promise use PIO mode :), fix coming as soon as I get home from work in an hour or so... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 6:36: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from room101.wuppy.rcs.ru (unknown [195.9.65.177]) by hub.freebsd.org (Postfix) with ESMTP id 4B751157B6 for ; Mon, 29 Mar 1999 06:35:43 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru (8.9.3.NOMIME/8.9.1) with ESMTP id SAA79370 for ; Mon, 29 Mar 1999 18:35:06 +0400 (MSD) (envelope-from romanp@wuppy.rcs.ru) Date: Mon, 29 Mar 1999 18:35:05 +0400 (MSD) From: "Roman V. Palagin" To: current@FreeBSD.ORG Subject: Status of 'tee' firewall action Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! What the status of 'tee' action? Anybody working on it? ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE, RP40-RIPE | Network Administrator ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 6:43:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 7574B14E92 for ; Mon, 29 Mar 1999 06:43:45 -0800 (PST) (envelope-from fanf@demon.net) Received: by noc.demon.net; id PAA23988; Mon, 29 Mar 1999 15:43:25 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma023964; Mon, 29 Mar 99 15:43:16 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10RdG0-0006C0-00; Mon, 29 Mar 1999 15:43:16 +0100 To: current@freebsd.org From: Tony Finch Subject: booting systems with lots of memory Message-Id: Date: Mon, 29 Mar 1999 15:43:16 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have a Quad 400MHz Xeon on evaluation here and we're trying to get a large memory configuration working. The machine is running a recent 3.1-STABLE with the kva patch from -CURRENT (appended below). When we have a working system with 1GB of RAM we'll increase it to 3GB of RAM and see how it runs. The boot blocks are from 3.0-RELEASE and they will boot the old a.out kernel via /boot/loader quite happily. We haven't yet managed to boot an ELF kernel, though (but we haven't tried to boot an unpatched one). It's also somewhat painful to debug because the machine is miles away and its serial console is causing trouble. Are there any obvious things we have missed? I assume the kernel load address is read by /boot/loader from the kernel's ELF header, so that a recent loader can cope. I also assume that the patch included below tweaks all of the required knobs. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/Makefile.i386,v retrieving revision 1.140 retrieving revision 1.141 diff -p -u -r1.140 -r1.141 --- src/sys/i386/conf/Makefile.i386 1999/03/01 09:54:51 1.140 +++ /home/ncvs/src/sys/i386/conf/Makefile.i386 1999/03/11 18:28:41 1.141 @@ -1,7 +1,7 @@ # Makefile.i386 -- with config changes. # Copyright 1990 W. Jolitz # from: @(#)Makefile.i386 7.1 5/10/91 -# $Id: Makefile.i386,v 1.140 1999/03/01 09:54:51 dt Exp $ +# $Id: Makefile.i386,v 1.141 1999/03/11 18:28:41 dg Exp $ # # Makefile for FreeBSD # @@ -56,7 +56,7 @@ CFLAGS+= -elf CFLAGS+= -aout .endif -LOAD_ADDRESS?= F0100000 +LOAD_ADDRESS?= C0100000 DEFINED_PROF= ${PROF} .if defined(PROF) CFLAGS+= -malign-functions=4 =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/kernel.script,v retrieving revision 1.1 retrieving revision 1.2 diff -p -u -r1.1 -r1.2 --- src/sys/i386/conf/kernel.script 1998/09/30 12:14:39 1.1 +++ /home/ncvs/src/sys/i386/conf/kernel.script 1999/03/11 18:28:42 1.2 @@ -5,7 +5,7 @@ SEARCH_DIR(/usr/lib); SEARCH_DIR(/usr/ob SECTIONS { /* Read-only sections, merged into text segment: */ - . = 0xf0100000 + SIZEOF_HEADERS; + . = 0xc0100000 + SIZEOF_HEADERS; .interp : { *(.interp) } .hash : { *(.hash) } .dynsym : { *(.dynsym) } =================================================================== RCS file: /home/ncvs/src/sys/i386/include/pmap.h,v retrieving revision 1.58 retrieving revision 1.59 diff -p -u -r1.58 -r1.59 --- src/sys/i386/include/pmap.h 1999/03/02 16:20:39 1.58 +++ /home/ncvs/src/sys/i386/include/pmap.h 1999/03/11 18:28:46 1.59 @@ -42,7 +42,7 @@ * * from: hp300: @(#)pmap.h 7.2 (Berkeley) 12/16/90 * from: @(#)pmap.h 7.4 (Berkeley) 5/12/91 - * $Id: pmap.h,v 1.58 1999/03/02 16:20:39 dg Exp $ + * $Id: pmap.h,v 1.59 1999/03/11 18:28:46 dg Exp $ */ #ifndef _MACHINE_PMAP_H_ @@ -88,13 +88,13 @@ #define VADDR(pdi, pti) ((vm_offset_t)(((pdi)<; Mon, 29 Mar 1999 07:32:05 -0800 (PST) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id HAA29105; Mon, 29 Mar 1999 07:30:57 -0800 (PST) Message-ID: <19990329073057.A28023@best.com> Date: Mon, 29 Mar 1999 07:30:57 -0800 From: "Jan B. Koum " To: Tony Finch , current@FreeBSD.ORG Subject: Re: booting systems with lots of memory References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Tony Finch on Mon, Mar 29, 1999 at 03:43:16PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 29, 1999 at 03:43:16PM +0100, Tony Finch wrote: > We have a Quad 400MHz Xeon on evaluation here and we're trying to get > a large memory configuration working. The machine is running a recent > 3.1-STABLE with the kva patch from -CURRENT (appended below). When we > have a working system with 1GB of RAM we'll increase it to 3GB of RAM > and see how it runs. > > The boot blocks are from 3.0-RELEASE and they will boot the old a.out > kernel via /boot/loader quite happily. We haven't yet managed to boot > an ELF kernel, though (but we haven't tried to boot an unpatched one). > It's also somewhat painful to debug because the machine is miles away > and its serial console is causing trouble. > > Are there any obvious things we have missed? I assume the kernel load > address is read by /boot/loader from the kernel's ELF header, so that > a recent loader can cope. I also assume that the patch included below > tweaks all of the required knobs. Yes, you need to patch load_elf.c -- here is what I have: nautilus% diff -u load_elf.c /usr/src/sys/boot/common/load_elf.c --- load_elf.c Mon Mar 29 07:29:18 1999 +++ /usr/src/sys/boot/common/load_elf.c Mon Jan 4 10:37:41 1999 @@ -229,7 +229,7 @@ firstaddr = lastaddr = 0; if (kernel) { #ifdef __i386__ - off = - (off & 0xff000000u); + off = 0x10000000; /* -0xf0000000 - i386 relocates after locore */ #else off = 0; /* alpha is direct mapped for kernels */ #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 7:59:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from vanessa.eliuk.org (pme75.sunshine.net [209.17.178.75]) by hub.freebsd.org (Postfix) with ESMTP id 8859315000 for ; Mon, 29 Mar 1999 07:59:03 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.3/8.9.3) with ESMTP id HAA00619 for ; Mon, 29 Mar 1999 07:58:29 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 29 Mar 1999 07:57:59 -0800 (PST) From: "Kevin G. Eliuk" To: current@FreeBSD.ORG Subject: make buildworld fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Updated as of the build ... Script started on Sun Mar 28 22:46:48 1999 # make -DCLOBBER -j6 buildworld -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp -------------------------------------------------------------- >>> Making make < .. skipping .. > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/getvfsent.c -o getvfsent.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/glob.c -o glob.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/initgroups.c -o initgroups.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/isatty.c -o isatty.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/jrand48.c -o jrand48.o In file included from /usr/src/lib/libc_r/../libc/gen/isatty.c:42: /usr/src/lib/libc_r/uthread/pthread_private.h:793: parse error before `_sched_switch_hook' /usr/src/lib/libc_r/uthread/pthread_private.h:797: warning: data definition has no type or storage class *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 8:26:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 385A414D0C for ; Mon, 29 Mar 1999 08:26:46 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA03889; Mon, 29 Mar 1999 11:25:56 -0500 (EST) Date: Mon, 29 Mar 1999 11:25:56 -0500 (EST) From: Daniel Eischen Message-Id: <199903291625.LAA03889@pcnet1.pcnet.com> To: current@FreeBSD.ORG, kevin_eliuk@sunshine.net Subject: Re: make buildworld fails Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin G. Eliuk wrote: > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include > -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale > -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include > -c /usr/src/lib/libc_r/../libc/gen/jrand48.c -o jrand48.o > In file included from /usr/src/lib/libc_r/../libc/gen/isatty.c:42: > /usr/src/lib/libc_r/uthread/pthread_private.h:793: parse error before `_sched_switch_hook' > /usr/src/lib/libc_r/uthread/pthread_private.h:797: warning: data definition has no type or storage class > *** Error code 1 Has src/include been updated? The missing type should be in src/include/pthread_np.h (pthread_switch_routine_t). Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 8:45:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id A4F9914C43 for ; Mon, 29 Mar 1999 08:45:28 -0800 (PST) (envelope-from fanf@demon.net) Received: by noc.demon.net; id RAA14781; Mon, 29 Mar 1999 17:45:09 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma014756; Mon, 29 Mar 99 17:45:03 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10Rf9p-0006JR-00; Mon, 29 Mar 1999 17:45:01 +0100 To: jkb@best.com, current@freebsd.org From: Tony Finch Cc: Tony Finch Subject: Re: booting systems with lots of memory In-Reply-To: <19990329073057.A28023@best.com> References: Message-Id: Date: Mon, 29 Mar 1999 17:45:02 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jan B. Koum " wrote: >Tony Finch wrote: >> >> Are there any obvious things we have missed? I assume the kernel load >> address is read by /boot/loader from the kernel's ELF header, so that >> a recent loader can cope. I also assume that the patch included below >> tweaks all of the required knobs. > > Yes, you need to patch load_elf.c Excellent! Thanks for the quick reply. Will /boot/loader still be able to boot old kernels after this patch? (I'm reluctant to completely hose the machine...) Also, w.r.t. the serial console problems, can I set the baud rate early in the boot sequence, and if so, how? The console works once getty puts up a login prompt but not before then, and I get a whole lot of garbage that I guess is baud barf (I wouldn't know for sure -- too much of a newbie). Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 8:55:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (Postfix) with ESMTP id 8D8AB14C0B for ; Mon, 29 Mar 1999 08:55:17 -0800 (PST) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id IAA13804; Mon, 29 Mar 1999 08:54:44 -0800 (PST) Message-ID: <19990329085443.A12419@best.com> Date: Mon, 29 Mar 1999 08:54:43 -0800 From: "Jan B. Koum " To: Tony Finch , current@freebsd.org Subject: Re: booting systems with lots of memory References: <19990329073057.A28023@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Tony Finch on Mon, Mar 29, 1999 at 05:45:02PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 29, 1999 at 05:45:02PM +0100, Tony Finch wrote: > "Jan B. Koum " wrote: > >Tony Finch wrote: > >> > >> Are there any obvious things we have missed? I assume the kernel load > >> address is read by /boot/loader from the kernel's ELF header, so that > >> a recent loader can cope. I also assume that the patch included below > >> tweaks all of the required knobs. > > > > Yes, you need to patch load_elf.c > > Excellent! Thanks for the quick reply. Will /boot/loader still be able > to boot old kernels after this patch? (I'm reluctant to completely > hose the machine...) AFAIK it should. Not sure myself to be honest :( > > Also, w.r.t. the serial console problems, can I set the baud rate > early in the boot sequence, and if so, how? The console works once > getty puts up a login prompt but not before then, and I get a whole > lot of garbage that I guess is baud barf (I wouldn't know for sure -- > too much of a newbie). > Don't know. I don't use serial console. Did you check http://www.freebsd.org/~msmith/FTL/bootstrap.txt for any info? -- Yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 9:18:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 75AC11502B for ; Mon, 29 Mar 1999 09:18:26 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id JAA65682; Mon, 29 Mar 1999 09:14:05 -0800 (PST) Date: Mon, 29 Mar 1999 09:14:05 -0800 (PST) From: Julian Elischer To: "Roman V. Palagin" Cc: current@FreeBSD.ORG Subject: Re: Status of 'tee' firewall action In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unfortunatly the 'tee' option is quite a bit more complicated than it looks.this is because teh normal way that packets get to divert sockets and the way it'd have to get there from a 'tee' are kinda incompatible. It can be done but it's just not quite as straight forward as it first appears.. julian On Mon, 29 Mar 1999, Roman V. Palagin wrote: > Hello! > > What the status of 'tee' action? Anybody working on it? > > ------------------------------------------------------------------------- > Roman V. Palagin | RVP1-6BONE, RP40-RIPE | Network Administrator > ------------------------------------------------------------------------- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 9:19:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [195.224.76.132]) by hub.freebsd.org (Postfix) with ESMTP id 5426C158D6 for ; Mon, 29 Mar 1999 09:19:10 -0800 (PST) (envelope-from fanf@chiark.greenend.org.uk) Received: from fanf by chiark.greenend.org.uk with local (Exim 2.02 #1) id 10RfgV-0006u1-00 (Debian); Mon, 29 Mar 1999 18:18:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14079.46583.208347.306328@chiark.greenend.org.uk> Date: Mon, 29 Mar 1999 18:18:47 +0100 (BST) From: Tony Finch To: "Jan B. Koum " Cc: Tony Finch , current@freebsd.org Subject: Re: booting systems with lots of memory In-Reply-To: <19990329085443.A12419@best.com> References: <19990329073057.A28023@best.com> <19990329085443.A12419@best.com> X-Mailer: VM 6.47 under Emacs 19.34.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jan B. Koum writes: > Tony Finch wrote: > > > > Excellent! Thanks for the quick reply. Will /boot/loader still be able > > to boot old kernels after this patch? (I'm reluctant to completely > > hose the machine...) > > AFAIK it should. Not sure myself to be honest :( Well, I took the plunge and booted with the new loader and the box came back fine, so I'm less worried about booting old kernels. Tomorrow we try it with 3GB of RAM :-) > > Also, w.r.t. the serial console problems, can I set the baud rate > > early in the boot sequence, and if so, how? The console works once > > getty puts up a login prompt but not before then, and I get a whole > > lot of garbage that I guess is baud barf (I wouldn't know for sure -- > > too much of a newbie). > > Don't know. I don't use serial console. Did you check > http://www.freebsd.org/~msmith/FTL/bootstrap.txt for any info? I did, yes. Most of that is now in the loader(8) manual. I tried changing /boot.config to contain "/boot/loader -h" which improved matters. There's still some garbage but it's fine after ">> FreeBSD BOOT @ 0x10000: 634/15360 k of memory, serial console". We suspect a BIOS that's being too damn clever for its own good. Tony. -- f.a.n.finch fanf@demon.net dot@dotat.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 11:42:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 493CB14CA3 for ; Mon, 29 Mar 1999 11:42:56 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id LAA28510; Mon, 29 Mar 1999 11:40:42 -0800 (PST) From: Archie Cobbs Message-Id: <199903291940.LAA28510@bubba.whistle.com> Subject: Re: Status of 'tee' firewall action In-Reply-To: from Julian Elischer at "Mar 29, 99 09:14:05 am" To: julian@whistle.com (Julian Elischer) Date: Mon, 29 Mar 1999 11:40:42 -0800 (PST) Cc: romanp@wuppy.rcs.ru, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > Unfortunatly the 'tee' option is quite a bit more complicated than it > looks.this is because teh normal way that packets get to divert sockets > and the way it'd have to get there from a 'tee' are kinda incompatible. > > It can be done but it's just not quite as straight forward as it first > appears.. > > On Mon, 29 Mar 1999, Roman V. Palagin wrote: > > > > What the status of 'tee' action? Anybody working on it? As a workaround, use "divert" instead of "tee" and immediately write any packet you read, using the same struct sockaddr, back to the socket. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 12:10:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id D0CC514C19 for ; Mon, 29 Mar 1999 12:10:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00525; Mon, 29 Mar 1999 12:03:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903292003.MAA00525@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tony Finch Cc: "Jan B. Koum " , current@freebsd.org Subject: Re: booting systems with lots of memory In-reply-to: Your message of "Mon, 29 Mar 1999 18:18:47 +0100." <14079.46583.208347.306328@chiark.greenend.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Mar 1999 12:03:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I did, yes. Most of that is now in the loader(8) manual. I tried > changing /boot.config to contain "/boot/loader -h" which improved > matters. There's still some garbage but it's fine after ">> FreeBSD > BOOT @ 0x10000: 634/15360 k of memory, serial console". We suspect a > BIOS that's being too damn clever for its own good. That sounds about right. If your BIOS on the Intel box is set for a serial console, you could try poking it again to make sure that it's set for 9600 bps and that the various 'magic' options relating to remote health monitoring are all off. I'd fire the one here up to be more specific, but it trips the breaker on this row of offices... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 12:29:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 89F4114DEE for ; Mon, 29 Mar 1999 12:29:55 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id WAA11475 for ; Mon, 29 Mar 1999 22:29:34 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id WAA27432 for ; Mon, 29 Mar 1999 22:29:34 +0200 (CEST) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id WAA13778 for ; Mon, 29 Mar 1999 22:29:32 +0200 (CEST) From: Alexander Leidinger Received: by vodix.aremorika; Mon, 29 Mar 1999 22:29:31 +0200 (MET DST) Date: Mon, 29 Mar 1999 22:29:31 +0200 (MET DST) Message-Id: <199903292029.WAA01377@vodix.aremorika> To: current@freebsd.org Subject: Bug with afd0 (zip-drive) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm not able to use msdos disks with afd0. It isn't usable with the mtools too (yes, I've used MAKEDEV to make the needed dev-nodes). cvsup at 7pm CET. "not able to use": > mdir z: init Z: non DOS media Cannot initialize 'Z:' > mount /zip msdos: /dev/afd0s4: Invalid argument Am I missing something? Bye, Alexander. P.S.: dmesg/... at request via private mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 12:41:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 60F9614BD6 for ; Mon, 29 Mar 1999 12:41:36 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id WAA11489 for ; Mon, 29 Mar 1999 22:41:16 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id WAA27472 for ; Mon, 29 Mar 1999 22:41:15 +0200 (CEST) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id WAA14711 for ; Mon, 29 Mar 1999 22:41:15 +0200 (CEST) From: Alexander Leidinger Received: by vodix.aremorika; Mon, 29 Mar 1999 22:41:14 +0200 (MET DST) Date: Mon, 29 Mar 1999 22:41:14 +0200 (MET DST) Message-Id: <199903292041.WAA01387@vodix.aremorika> To: current@freebsd.org Subject: Bug with VESA? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, cvsup 7pm CET. I'm not able to switch to 132x60 anymore. Last cvsup was around feb 1999. dmesg: VESA: v0.40, 40960k memory, flags:0x74610000, mode table: 0xc08de022 (280c000) ^^^^^ seems to be wrong (4096k) VESA: Matrox Graphics Inc. (it's a Mystique 220) vga0: rev 0x03 int a irq 11 on pci0.12.0 sc0: flags 0x6 on isa sc0: VGA color <16 virtual consoles, flags=0x6> More (dmesg/...) on request via private mail. Bye, Alexander. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 13: 0:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kar.net (n182.cdialup.kar.net [195.178.130.182]) by hub.freebsd.org (Postfix) with ESMTP id D967114D06 for ; Mon, 29 Mar 1999 12:59:42 -0800 (PST) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.3/8.8.8) with ESMTP id XAA32896; Mon, 29 Mar 1999 23:58:53 +0300 (EEST) (envelope-from kushn@mail.kar.net) Date: Mon, 29 Mar 1999 23:58:53 +0300 (EEST) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: "Kevin G. Eliuk" Cc: current@FreeBSD.ORG Subject: Re: make buildworld fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I had exactly the same. Have you by chance got an old /usr/src/lib/libc_r/uthread/pthread{.h,_nb.h}? Then remove them, they conflict with /usr/src/include/pthread{.h,_nb.h}. On Mon, 29 Mar 1999, Kevin G. Eliuk wrote: > > Updated as of the build ... > > Script started on Sun Mar 28 22:46:48 1999 > # make -DCLOBBER -j6 buildworld > -------------------------------------------------------------- > >>> Cleaning up the temporary elf build tree > -------------------------------------------------------------- > mkdir -p /usr/obj/usr/src/tmp > chflags -R noschg /usr/obj/usr/src/tmp/ > rm -rf /usr/obj/usr/src/tmp > -------------------------------------------------------------- > >>> Making make > > < .. skipping .. > > > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/getvfsent.c -o getvfsent.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/glob.c -o glob.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/initgroups.c -o initgroups.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/isatty.c -o isatty.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -DNOPOLL -I/usr/src/lib/libc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc_r/../libc/gen/jrand48.c -o jrand48.o > In file included from /usr/src/lib/libc_r/../libc/gen/isatty.c:42: > /usr/src/lib/libc_r/uthread/pthread_private.h:793: parse error before `_sched_switch_hook' > /usr/src/lib/libc_r/uthread/pthread_private.h:797: warning: data definition has no type or storage class > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > -- > Regards, > Kevin G. Eliuk > Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org > Regards, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 14: 9:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 74D1814F63 for ; Mon, 29 Mar 1999 14:09:55 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id RAA01741 for ; Mon, 29 Mar 1999 17:09:36 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA14749; Mon, 29 Mar 1999 17:09:35 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id RAA55894 for freebsd-current@freebsd.org; Mon, 29 Mar 1999 17:09:35 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199903292209.RAA55894@bb01f39.unx.sas.com> Subject: make release & doc failure To: freebsd-current@freebsd.org Date: Mon, 29 Mar 1999 17:09:35 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Subject says it all... Thanks, John ===> Cleaning for tidy-0.1.99.1 ===> Cleaning for docproj-1.0 ===> FAQ sgmlfmt -f html -links /usr/doc/FAQ/FAQ.sgml sgmlfmt: not found *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 15:52: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 09ABC14C4F for ; Mon, 29 Mar 1999 15:51:53 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA27471; Tue, 30 Mar 1999 09:21:32 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA24172; Tue, 30 Mar 1999 09:21:26 +0930 (CST) Message-ID: <19990330092126.U413@lemis.com> Date: Tue, 30 Mar 1999 09:21:26 +0930 From: Greg Lehey To: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: HEADS UP!! NOAOUT `make world' knob changed References: <19990329030228.A1290@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990329030228.A1290@dragon.nuxi.com>; from David O'Brien on Mon, Mar 29, 1999 at 03:02:28AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 29 March 1999 at 3:02:28 -0800, David O'Brien wrote: > I have just changed made a change concerning the building of legacy a.out > bits during `make world'. > > Previous to my change, one would define "NOAOUT" to keep from building > the legacy a.out bits. Now one would define "WANT_AOUT" to build them. OK, which bits? Does this mean that new systems will no longer run a.out binaries? Or will the libraries no longer be built? Will the existing ones be removed? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 15:56:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0D71015901 for ; Mon, 29 Mar 1999 15:56:47 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id PAA57047; Mon, 29 Mar 1999 15:56:20 -0800 (PST) (envelope-from obrien) Date: Mon, 29 Mar 1999 15:56:20 -0800 From: "David O'Brien" To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: HEADS UP!! NOAOUT `make world' knob changed Message-ID: <19990329155620.B56680@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990329030228.A1290@dragon.nuxi.com> <19990330092126.U413@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990330092126.U413@lemis.com>; from Greg Lehey on Tue, Mar 30, 1999 at 09:21:26AM +0930 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Previous to my change, one would define "NOAOUT" to keep from building > > the legacy a.out bits. Now one would define "WANT_AOUT" to build them. > Does this mean that new systems will no longer run a.out binaries? No. > Or will the libraries no longer be built? Yes. > Will the existing ones be removed? No. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 16:13:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id BDE3F14E4F for ; Mon, 29 Mar 1999 16:13:29 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:7DRp4+yMnDWdU/CmZMUxE9ZSVaW//Iij@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id JAA29186; Tue, 30 Mar 1999 09:12:56 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA01403; Tue, 30 Mar 1999 09:16:26 +0900 (JST) Message-Id: <199903300016.JAA01403@zodiac.mech.utsunomiya-u.ac.jp> To: Alexander Leidinger Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Bug with VESA? In-reply-to: Your message of "Mon, 29 Mar 1999 22:41:14 +0200." <199903292041.WAA01387@vodix.aremorika> References: <199903292041.WAA01387@vodix.aremorika> Date: Tue, 30 Mar 1999 09:16:25 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >cvsup 7pm CET. > >I'm not able to switch to 132x60 anymore. Last cvsup was around feb 1999. Please check the revision of /sys/i386/isa/vesa.c. Is it 1.18 or 1.19? I committed fix for a palette loading problem in vesa.c at 7am PST. This is the latest revision (1.19). The modification has nothing to do with the VESA BIOS initialization and shouldn't be causing this sort of problem. But,... >dmesg: >VESA: v0.40, 40960k memory, flags:0x74610000, mode table: 0xc08de022 (280c000) ~~~~~ ~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~ > ^^^^^ seems to be wrong (4096k) They all look wrong ;-< >VESA: Matrox Graphics Inc. > (it's a Mystique 220) Right. I think I can find one around here. >vga0: rev 0x03 int a ir >q >11 on pci0.12.0 >sc0: flags 0x6 on isa >sc0: VGA color <16 virtual consoles, flags=0x6> > >More (dmesg/...) on request via private mail. Please give the '-v' option at the boot loader prompt when starting the kernel. and send me the complete dmesg output and your kernel configuration file. Thank you for your cooperation. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 16:52:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (tele.visi.com [209.98.98.17]) by hub.freebsd.org (Postfix) with ESMTP id 429D41547E for ; Mon, 29 Mar 1999 16:52:47 -0800 (PST) (envelope-from mestery@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 952771F940 for ; Mon, 29 Mar 1999 18:52:13 -0600 (CST) Received: from localhost (mestery@localhost) by isis.visi.com (8.8.8/8.8.8) with SMTP id SAA26316 for ; Mon, 29 Mar 1999 18:52:13 -0600 (CST) X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs Date: Mon, 29 Mar 1999 18:52:13 -0600 (CST) From: To: freebsd-current@freebsd.org Subject: nfs_getpages: error 4, vm_fault Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I am running two machines with current from Sunday, March 28 at 3:20PM CST, but the problems I am seeing I have seen for a while now (about a month). I thought an upgrade might fix them. Here are the specs on the machines: Machine A: Dual PPro 200MHz, 128MB RAM, SCSI disks on an onboard Adaptec 7880, rl0 driver (Realtek 8139) Machine B: Dual Pentium 133, 64MB RAM, IDE disks, xl0 driver (3COM 905B) Both machines are connected via a 10/100 hub, and are operating at 100Mb/s half duplex. Machine A is the NFS server, and machine B is the client. Machine B runs apache and serves up some web pages over NFS from machine A. I am mounting with options rw,intr in machine B's fstab. According to the mount_nfs manpage, I am using nfsv3 since my server allows that. When certain files on machine A are accessed by the web daemon on machine B, the httpd process hangs, and when I eventually use apachectl to stop it, here is what is printed out on machine B's console: Mar 29 18:30:04 wall /kernel: nfs_getpages: error 4 Mar 29 18:30:04 wall /kernel: vm_fault: pager read error, pid 274 (httpd) I can reproduce this fairly easily if need be. I looked in the mail archives, but didn't see anyone else seeing this problem recently. Anyone have any clues on this one? I can provide more information if needed. Thanks. -- Kyle Mestery StorageTek's Storage Networking Group Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 18: 0:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7BC4914BD8 for ; Mon, 29 Mar 1999 18:00:23 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id RAA85632; Mon, 29 Mar 1999 17:55:05 -0800 (PST) Date: Mon, 29 Mar 1999 17:55:04 -0800 (PST) From: Julian Elischer To: mestery@visi.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: nfs_getpages: error 4, vm_fault In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You might try instrumenting nfs/nfs_bio.c to find where the EINTR is coming from. If it's reproducible then you should be able (with a few reboots) to track it back quite a distance. julian On Mon, 29 Mar 1999 mestery@visi.com wrote: > > Greetings, > > I am running two machines with current from Sunday, March 28 at 3:20PM > CST, but the problems I am seeing I have seen for a while now (about a > month). I thought an upgrade might fix them. Here are the specs on the > machines: > > Machine A: > Dual PPro 200MHz, 128MB RAM, SCSI disks on an onboard Adaptec 7880, rl0 > driver (Realtek 8139) > > Machine B: > Dual Pentium 133, 64MB RAM, IDE disks, xl0 driver (3COM 905B) > > Both machines are connected via a 10/100 hub, and are operating at > 100Mb/s half duplex. Machine A is the NFS server, and machine B is the > client. Machine B runs apache and serves up some web pages over NFS > from machine A. I am mounting with options rw,intr in machine B's > fstab. According to the mount_nfs manpage, I am using nfsv3 since my > server allows that. When certain files on machine A are accessed by the > web daemon on machine B, the httpd process hangs, and when I eventually > use apachectl to stop it, here is what is printed out on machine B's > console: > > Mar 29 18:30:04 wall /kernel: nfs_getpages: error 4 > Mar 29 18:30:04 wall /kernel: vm_fault: pager read error, pid 274 > (httpd) > > I can reproduce this fairly easily if need be. I looked in the mail > archives, but didn't see anyone else seeing this problem recently. Anyone > have any clues on this one? I can provide more information if needed. > Thanks. > > -- > Kyle Mestery > StorageTek's Storage Networking Group > Protect your right to privacy: www.freecrypto.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 20:46:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (57-sweet.camalott.com [208.239.153.57]) by hub.freebsd.org (Postfix) with ESMTP id A1F0A14DB7 for ; Mon, 29 Mar 1999 20:46:25 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.1) id WAA00584; Mon, 29 Mar 1999 22:45:28 -0600 (CST) (envelope-from joelh) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: HEADS UP!! NOAOUT `make world' knob changed References: <19990329030228.A1290@dragon.nuxi.com> From: Joel Ray Holveck Date: 29 Mar 1999 22:45:27 -0600 In-Reply-To: "David O'Brien"'s message of "Mon, 29 Mar 1999 03:02:28 -0800" Message-ID: <86pv5regbc.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have just changed made a change concerning the building of legacy a.out > bits during `make world'. > Previous to my change, one would define "NOAOUT" to keep from building > the legacy a.out bits. Now one would define "WANT_AOUT" to build them. > The default of building a.out bits gets in the way of some other changes > I will make to the `build world' process soon. Will WANT_AOUT be considered a supported option? That is, if I choose to build a.out libraries, will I be giving up the right to gripe when `make world' breaks, and be resigned to the ranks of the NOCLEAN masses? Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 20:56:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1400E14DB7 for ; Mon, 29 Mar 1999 20:56:41 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id UAA19905; Mon, 29 Mar 1999 20:56:21 -0800 (PST) (envelope-from obrien) Date: Mon, 29 Mar 1999 20:56:21 -0800 From: "David O'Brien" To: Joel Ray Holveck Cc: current@FreeBSD.ORG Subject: Re: HEADS UP!! NOAOUT `make world' knob changed Message-ID: <19990329205621.A19813@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990329030228.A1290@dragon.nuxi.com> <86pv5regbc.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <86pv5regbc.fsf@detlev.UUCP>; from Joel Ray Holveck on Mon, Mar 29, 1999 at 10:45:27PM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Will WANT_AOUT be considered a supported option? If I can get it to work. > That is, if I choose to build a.out libraries, will I be giving up the > right to gripe when `make world' breaks, and be resigned to the ranks > of the NOCLEAN masses? At this time (well... you will know when you time comes). Right now, I do need it tested that WANT_AOUT works. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 21: 7:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from vanessa.eliuk.org (pme170.sunshine.net [209.17.178.170]) by hub.freebsd.org (Postfix) with ESMTP id 233B2158E4 for ; Mon, 29 Mar 1999 21:07:14 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.3/8.9.3) with ESMTP id VAA00783; Mon, 29 Mar 1999 21:04:42 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 29 Mar 1999 21:04:33 -0800 (PST) From: "Kevin G. Eliuk" To: Vladimir Kushnir Cc: current@FreeBSD.ORG Subject: Re: make buildworld fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Mar 1999, Vladimir Kushnir wrote: > Hi, > I had exactly the same. Have you by chance got an old > /usr/src/lib/libc_r/uthread/pthread{.h,_nb.h}? That's an affirmative, I've moved them and will retry the build just as soon as I look into this new egcs stuff I checked out :) -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 29 23:26:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 1B8DB14D29 for ; Mon, 29 Mar 1999 23:26:35 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id CAA00246 for ; Tue, 30 Mar 1999 02:28:00 -0500 (EST) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Tue, 30 Mar 1999 02:28:00 -0500 (EST) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: current@freebsd.org Subject: the ATA driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just letting someone know/confirming something: The ata drivers cvsupped 10 minutes ago have slowed my disk access to a crawl. I went from 12 MB per second to 6 MB per second. Just thought I'd let someone know because this seems to be a major problem. Thanks. Kenneth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 1:34:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A3ABE15A06 for ; Tue, 30 Mar 1999 01:34:22 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA60345; Tue, 30 Mar 1999 11:33:45 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199903300933.LAA60345@freebsd.dk> Subject: Re: the ATA driver In-Reply-To: from Kenneth Wayne Culver at "Mar 30, 1999 2:28: 0 am" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Tue, 30 Mar 1999 11:33:45 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kenneth Wayne Culver wrote: > Just letting someone know/confirming something: > > The ata drivers cvsupped 10 minutes ago have slowed my disk access to a > crawl. I went from 12 MB per second to 6 MB per second. Just thought I'd > let someone know because this seems to be a major problem. Thanks. This can only be the case on a Promise controller, I have allready committed a fix for that (it always selected PIO mode). A current quick test on a 5400RPM IBM disk shows: IOZONE performance measurements: 9768393 bytes/second for writing the file 11820143 bytes/second for reading the file Remember that we have lost significant I/O bandwidth currently due to changes in vfs_bio and freinds. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 3:20: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 4286E15AB4 for ; Tue, 30 Mar 1999 03:19:58 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. (async3-30.iptelecom.net.ua [212.42.68.229]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id OAA14614; Tue, 30 Mar 1999 14:20:05 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id OAA11810; Tue, 30 Mar 1999 14:19:35 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3700B364.BCC35D7E@altavista.net> Date: Tue, 30 Mar 1999 14:20:04 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE4: ATA/ATAPI driver new version available. References: <199903281858.UAA55984@freebsd.dk> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Soren, New ata driver (cvsup'ed several minutes ago) locks my box solid (only reset button can help). Bug is fully reproducible on my machine (Toshiba Satellite Pro 445). I using the following command: dd if=/dev/zero of=/dev/ad0s2 bs=1024k. It works several minutes then IDE led turns off and box freezes. Interesting that when I looking at systat -vm measures, performance constantly degrades from 3.3MB/s to 2.5MB/s. Bug exist either in single-user and in multi-user mode. Following is relevant dmesg pieces from my dmesg output: --- ad0: ATA-? disk at ata0 as master ad0: 1376MB (2818368 sectors), 2796 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, PIO mode ---- ad0s1: type 0xa5, start 63, end = 1433375, size 1433313 : OK ad0s2: type 0xa5, start 1433376, end = 2818367, size 1384992 : OK Sincerely, Maxim Sobolev   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 3:29:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 68AF414E05 for ; Tue, 30 Mar 1999 03:29:30 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA60572; Tue, 30 Mar 1999 13:29:09 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199903301129.NAA60572@freebsd.dk> Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: <3700B364.BCC35D7E@altavista.net> from Maxim Sobolev at "Mar 30, 1999 2:20: 4 pm" To: sobomax@altavista.net Date: Tue, 30 Mar 1999 13:29:08 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > >New ata driver (cvsup'ed several minutes ago) locks my box solid (only >reset but ton can help). Bug is fully reproducible on my machine (Toshiba Satellite Pro 445). >I using the following command: dd if=/dev/zero of=/dev/ad0s2 bs=1024k. It >works several minutes then IDE led turns off and box freezes. Interesting that >when I looking at systat -vm measures, performance constantly degrades from >3.3MB/s to 2.5MB/s. >Bug exist either in single-user and in multi-user mode. Following is relevant dmesg pieces from my dmesg output: Hmm, are you sure you want to WRITE all those zeros to your disk ?? However it should not hang before the end of disk is reached that is. Have you tried reading all of the disk instead, does that hang ?? The degradation is probably becuse the transferrate of the disk slows down as you get closer to the center of the disk. Have you anu idea on how much data is transferred ?? how long is it running ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 3:43:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id CB22414E02 for ; Tue, 30 Mar 1999 03:43:13 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Tue, 30 Mar 1999 13:45:20 +0200 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097577@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Soren Schmidt' , sobomax@altavista.net Cc: current@FreeBSD.ORG Subject: RE: UPDATE4: ATA/ATAPI driver new version available. Date: Tue, 30 Mar 1999 13:39:53 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Soren Schmidt [SMTP:sos@freebsd.dk] > Sent: Tuesday, March 30, 1999 1:29 PM > To: sobomax@altavista.net > Cc: current@FreeBSD.ORG > Subject: Re: UPDATE4: ATA/ATAPI driver new version available. >=20 > It seems Maxim Sobolev wrote: > > > >New ata driver (cvsup'ed several minutes ago) locks my box solid > (only > >reset but ton can help). Bug is fully reproducible on my machine > (Toshiba Satellite Pro 445). > >I using the following command: dd if=3D/dev/zero of=3D/dev/ad0s2 > bs=3D1024k. It > >works several minutes then IDE led turns off and box freezes. > Interesting that > >when I looking at systat -vm measures, performance constantly > degrades from > >3.3MB/s to 2.5MB/s.=20 > >Bug exist either in single-user and in multi-user mode. Following is > relevant dmesg pieces from my dmesg output: >=20 > Hmm, are you sure you want to WRITE all those zeros to your disk ?? > However it should not hang before the end of disk is reached that is. > Have you tried reading all of the disk instead, does that hang ?? > The degradation is probably becuse the transferrate of the disk slows > down as you get closer to the center of the disk. > Have you anu idea on how much data is transferred ?? how long is it > running ?? [ML] Also, is there any swapping area on that slice? Because if there is and kernel has been told to use it (AFAIR swapon happens even in single user mode) you have just obliterated the kernel pages (kernel is pageable these days IIRC, at least the data if not the = code). /Marino > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 3:44: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4EEB714EDA for ; Tue, 30 Mar 1999 03:43:57 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA60602; Tue, 30 Mar 1999 13:43:35 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199903301143.NAA60602@freebsd.dk> Subject: Re: UPDATE4: ATA/ATAPI driver new version available. In-Reply-To: <199903301129.NAA60572@freebsd.dk> from Soren Schmidt at "Mar 30, 1999 1:29: 8 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Tue, 30 Mar 1999 13:43:35 +0200 (CEST) Cc: sobomax@altavista.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Soren Schmidt wrote: > It seems Maxim Sobolev wrote: > > > >New ata driver (cvsup'ed several minutes ago) locks my box solid (only > >reset but ton can help). Bug is fully reproducible on my machine (Toshiba Satellite Pro 445). > >I using the following command: dd if=/dev/zero of=/dev/ad0s2 bs=1024k. It > >works several minutes then IDE led turns off and box freezes. Interesting that > >when I looking at systat -vm measures, performance constantly degrades from > >3.3MB/s to 2.5MB/s. > >Bug exist either in single-user and in multi-user mode. Following is relevant dmesg pieces from my dmesg output: > > Hmm, are you sure you want to WRITE all those zeros to your disk ?? > However it should not hang before the end of disk is reached that is. > Have you tried reading all of the disk instead, does that hang ?? > The degradation is probably becuse the transferrate of the disk slows > down as you get closer to the center of the disk. > Have you anu idea on how much data is transferred ?? how long is it > running ?? OH, I forgot to ask if you have any powersaving stuff enabled too, as the new driver dont know about that yet, if the disk goes to sleep under its feet it will die, but given access to the disk thats probably not likely... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 4:24:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F99814E9A for ; Tue, 30 Mar 1999 04:24:16 -0800 (PST) (envelope-from matt@camtech.com.au) Received: from dialup-ad-12-79.camtech.net.au (dialup-ad-12-79.camtech.net.au [203.55.242.79]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id VAA18094; Tue, 30 Mar 1999 21:59:06 +0930 (CST) Date: Tue, 30 Mar 1999 21:53:36 +0930 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.com.au To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.ORG, wpaul@ctr.columbia.edu Subject: Re: RealTek driver woes In-Reply-To: <199903251417.WAA16592@ariadne.tensor.pgs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are certain RealTek chipsets that perform very badly in both Windows and FreeBSD in my experience. This is due to poor hardware design as far as the FreeBSD driver author could see. Replace your network card with a $30 PCI 10/100 card that is not a RealTek such as the VIA Technologies VT3043 `Rhine I' and VT86C100A `Rhine II' chips and you'll get much better performance (FreeBSD 'vr' driver). Search the cvs-all mailing list archives for mail re: the 'rl' driver. In my experience: A no-one could get files from a firend of mine's Windows 95 box but he copy them to other peoples machines. If you did manage to get a small file it was corrupt. Under FreeBSD we had the same lockups you are having (using UTP). If we used coax (BNC) it worked fine. This was all at 10 Mbps. We didn't test Windows on coax. Now that we have put a Rhine based card in his machine both Windows and FreeBSD are working fine at ~1 MB/s through put (at 10 Mbps) and NFS is working fine. On Thu, 25 Mar 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > I'm running a RealTek ethernet card in a 486dx4-100 machine and am having some > problems. Firstly, doing an ls on a nfs mounted directory exported from the > RealTek machine hangs. According to tcpdump it is receiving the readdir > packets. Secondly, it will hange solidly when acting as the receiver (haven't > tried it as the sender) running the netpipe tests (NPtcp -s -r receiving, the > sender runs NP -t -h host_rl -s) - no DDB, just a solid hang. An ISA SMC card > in the same machine is fine. I've tried it with RL_USEIOSPACE defined and > undefined. This is running a very current system, with the id string > > $Id: if_rl.c,v 1.12 1999/02/23 15:38:25 wpaul Exp$ > > Here's the dmesg output. > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #1: Thu Mar 25 21:37:03 WST 1999 > toor@bloop.craftncomp.com:/data/src/sys/compile/bleep > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) > Origin = "AuthenticAMD" Id = 0x484 Stepping=4 > Features=0x1 > real memory = 16777216 (16384K bytes) > avail memory = 13750272 (13428K bytes) > Preloaded elf kernel "kernel" at 0xc02c3000. > Preloaded elf module "linux.ko" at 0xc02c309c. > Probing for devices on PCI bus 0: > chip0: rev 0x00 on pci0.0.0 > rl0: rev 0x10 int a irq 9 on pci0.4.0 > rl0: Ethernet address: 00:00:e8:53:a2:3e > rl0: autoneg complete, link status good (half-duplex, 10Mbps) > Probing for PnP devices: > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa > ed0: address 00:00:c0:d2:b2:72, type SMC8216T (16 bit) > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > ppc0 at 0x378 irq 7 on isa > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > pca0 on motherboard > pca0: PC speaker audio driver > ata0 at 0x1f0-0x1f7 irq 14 on isa > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fd0: 1.44MB 3.5in > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > IP packet filtering initialized, divert enabled, rule-based forwarding > disabled, logging disabled > ad0: ATA-4 disk at ata0 as master > ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue > changing root device to ad0s2a > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "People often think of research as a form of development -- that it's about > doing exactly what you planned, doing it on time, and doing it with resources > that you said you'd use. But if you're going to do that, you have to know what > you are doing, and if you know what you are doing, it isn't really research." > --Dave Liddle, The New Yorker, Feb. 23/Mar.2, 1998, p 84 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 4:47:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id 264D714DCA for ; Tue, 30 Mar 1999 04:47:43 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 64499 invoked by uid 1000); 30 Mar 1999 12:48:32 -0000 Date: Tue, 30 Mar 1999 14:48:32 +0200 From: Andreas Braukmann To: freebsd-current@freebsd.org Subject: Subnotebook capable of running -current Message-ID: <19990330144832.A63763@paert.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I want to purchase some kind of 'subnotebook', that has to be as -current-compatible as possible. I anticipate the crowd whispering "Libretto, ... Libretto", but I have to say, that I don't like the Libretto very much for its crude screen resolution. Currently I'm tending towards the "Toshiba Portege 3010" or the "Fujitsu LifeBook B110 Biblo". Any experiences with these decices? I'm wondering about the CD-drives connected thru a PCMCIA-Card and FreeBSD-compatible PCMCIA-Network-Cards. Thanks, Andreas -- : TSE TeleService GmbH : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 5: 8:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 924DE15038 for ; Tue, 30 Mar 1999 05:08:37 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id IAA07224 for ; Tue, 30 Mar 1999 08:06:46 -0500 (EST) Date: Tue, 30 Mar 1999 08:06:45 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: ctm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look what the egcs import's done to ctm: ctm_dequeue: cvs-cur.5193.gz 1/92 sent 92 pieces .... well, that knocks ctm out of action for a few days, so they won't be complaining about things not building for awhile. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 5:12:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 2C48815038 for ; Tue, 30 Mar 1999 05:12:32 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA10313; Tue, 30 Mar 1999 15:12:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA24494; Tue, 30 Mar 1999 15:12:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: ctm In-reply-to: Your message of "Tue, 30 Mar 1999 08:06:45 CDT." Date: Tue, 30 Mar 1999 15:12:06 +0200 Message-ID: <24492.922799526@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chuck Robey writes: >Look what the egcs import's done to ctm: > >ctm_dequeue: cvs-cur.5193.gz 1/92 sent > >92 pieces .... well, that knocks ctm out of action for a few days, so >they won't be complaining about things not building for awhile. We've done better than that before. It think the record to date is 1/107... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 5:24:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5A17D15011 for ; Tue, 30 Mar 1999 05:24:34 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA60878 for current@freebsd.org; Tue, 30 Mar 1999 15:24:15 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199903301324.PAA60878@freebsd.dk> Subject: UPDATE5: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Tue, 30 Mar 1999 15:24:15 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fifth update to the new ATA/ATAPI driver: Fixed problems: Promise controllers always ended up in PIO mode. A real braino, fixed. Kernel with only ISA bus in it fails to compile. The dependency on NPCI was badly placed, fixed. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. Especially the DMA support can hose your disk real bad if anything goes wrong, again you have been warned :) Notebook owners should be carefull that their machines dont suspend as this might cause trouble... But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 5:38:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 5E6CD14CF2 for ; Tue, 30 Mar 1999 05:38:16 -0800 (PST) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.2/8.9.2) with SMTP id RAA17157 for ; Tue, 30 Mar 1999 17:37:56 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: freebsd-current@freebsd.org Date: Tue, 30 Mar 1999 17:28:06 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99033017375202.00385@camel.avias.com> Content-Transfer-Encoding: 8bit Subject: X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello i wonder what is the situation with AIC driver now? we're suffering without it :) -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 5:48:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 3E16914CF2 for ; Tue, 30 Mar 1999 05:48:01 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Ryqk-0002RI-00; Tue, 30 Mar 1999 15:46:38 +0200 From: Sheldon Hearn To: camel@avias.com Cc: freebsd-current@freebsd.org Subject: Re: In-reply-to: Your message of "Tue, 30 Mar 1999 17:28:06 +0400." <99033017375202.00385@camel.avias.com> Date: Tue, 30 Mar 1999 15:46:38 +0200 Message-ID: <9379.922801598@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 30 Mar 1999 17:28:06 +0400, Ilya Naumov wrote: > i wonder what is the situation with AIC driver now? we're suffering > without it :) All traces of it have been completely removed from CURRENT. You should follow your cvs mail. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 6: 5:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 8F8C915A21 for ; Tue, 30 Mar 1999 06:05:08 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Tue, 30 Mar 1999 16:07:16 +0200 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D09757A@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Sheldon Hearn' , camel@avias.com Cc: freebsd-current@freebsd.org Subject: RE: Date: Tue, 30 Mar 1999 16:01:48 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Sheldon Hearn [SMTP:sheldonh@iafrica.com] > Sent: Tuesday, March 30, 1999 3:47 PM > To: camel@avias.com > Cc: freebsd-current@freebsd.org > Subject: Re: > > > > On Tue, 30 Mar 1999 17:28:06 +0400, Ilya Naumov wrote: > > > i wonder what is the situation with AIC driver now? we're suffering > > without it :) > > All traces of it have been completely removed from CURRENT. > [ML] Hey, not all is lost. You can still use your 1510 as an el-cheapo external SCSI case connector. What I did after my ancient 386SX-16 died was to throw away the motherboard and use the case as a 5-bay case (it was a midi-tower). The 1510 came in handy because it was cheaper than the ribbon-to-50-pin-D SCSI adapter. Of course I did not bother to power the card :) /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 6:34:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id 474A514C1E for ; Tue, 30 Mar 1999 06:34:17 -0800 (PST) (envelope-from wpaul@ctr.columbia.edu) Received: (wpaul@localhost) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) id JAA00854; Tue, 30 Mar 1999 09:33:39 -0500 (EST) From: wpaul@ctr.columbia.edu (Bill Paul) Message-Id: <199903301433.JAA00854@sirius.ctr.columbia.edu> Subject: Re: RealTek driver woes To: thyerm@camtech.com.au Date: Tue, 30 Mar 1999 09:33:38 -0500 (EST) Cc: current@freebsd.org, shocking@prth.pgs.com In-Reply-To: from "Matthew Thyer" at Mar 30, 99 09:53:36 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Thyer had to walk into mine and say: > There are certain RealTek chipsets that perform very badly in both Windows > and FreeBSD in my experience. This is due to poor hardware design as far > as the FreeBSD driver author could see. It happens though that I only have one RealTek 8139 board for testing, which worked fine in all the machines I tried it in. However, I do not have any AMD 486dx/100 machines, so I can't easily duplicate the operating environment in order to reproduce the problem. And if I can't reproduce the problem, I can't fix it. I don't think people realize this: telling me that the board locks up under condition foo doesn't do me any good unless I can reproduce the hang myself under condition foo. I've certainly never had the whole machine wedge up while using the RealTek driver. From experience, having the whole machine freeze usually indicates one of two things: the kernel is stuck in an infinite loop somewhere with interrupts disabled (like in an interrupt handler), or there's some sort of weird hardware interaction that's actually hanging the CPU or bus. There shouldn't be any loop conditions in the driver if the hardware functions correctly -- there might be if it functions incorrectly, like if it asserts its interrupt and the interrupt handler is unable to clear it. Usually you can detect this by putting in a loop counter and bailing out if it reaches a certain ridiculously large value. If the machine does wedge up, then don't just sit there like a bump on a log looking at it. If you have DDB compiled into the kernel, try to break into the debugger on the console. If the system is caught in a tight loop somewhere then you probably won't be able to do it, but if you can, you can type 'trace' and get some idea of where the loop is occurring by examining the stack trace. If the interface just stops communicating with the other side, check for an obvious reason. Look at netstat -in and check for input or output errors. Do an 'ifconfig rl0' and see if the OACTIVE flag is set. This usually indicates a stuck transmitter (although in this case you'll probably also see a watchdog timeout error on the console). Lastly, don't leave out important information about the operating environment and conditions at the time the problem occurs. People sometimes forget to mention important things because they think they're obvious. This is wrong: nothing is obvious when I can't actually see the machine. This includes simple things like: were you running some program that places the interface in promiscuous mode, or were you running X11, or is the machine configured as a router, or were you using NAT of firewalling. Once you start noting down these things for your problem report, take it upon yourself to investigate what happens when you eliminate these conditions. > Replace your network card with a $30 PCI 10/100 card that is not a RealTek > such as the VIA Technologies VT3043 `Rhine I' and VT86C100A `Rhine II' > chips and you'll get much better performance (FreeBSD 'vr' driver). But not much better. :) At 10Mbps they're okay, but the VIA Rhine is still a little brain damaged. > Search the cvs-all mailing list archives for mail re: the 'rl' driver. > > In my experience: > > A no-one could get files from a firend of mine's Windows 95 box but he > copy them to other peoples machines. > > If you did manage to get a small file it was corrupt. > > Under FreeBSD we had the same lockups you are having (using UTP). > If we used coax (BNC) it worked fine. This was all at 10 Mbps. > We didn't test Windows on coax. I tested my sample board at both 10Mbps and 100Mbps and never had any lockups. This is what's frustrating. Now, if I actually had access to the machines that were experiencing the trouble I might actually be able to debug the problem. > Now that we have put a Rhine based card in his machine both Windows and > FreeBSD are working fine at ~1 MB/s through put (at 10 Mbps) and NFS is > working fine. > > On Thu, 25 Mar 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > I'm running a RealTek ethernet card in a 486dx4-100 machine and am having some > > problems. Firstly, doing an ls on a nfs mounted directory exported from the > > RealTek machine hangs. According to tcpdump it is receiving the readdir > > packets. Secondly, it will hange solidly when acting as the receiver (haven't > > tried it as the sender) running the netpipe tests (NPtcp -s -r receiving, the > > sender runs NP -t -h host_rl -s) - no DDB, just a solid hang. An ISA SMC card > > in the same machine is fine. I've tried it with RL_USEIOSPACE defined and > > undefined. This is running a very current system, with the id string > > > > $Id: if_rl.c,v 1.12 1999/02/23 15:38:25 wpaul Exp$ > > > > Here's the dmesg output. > > > > Copyright (c) 1992-1999 The FreeBSD Project. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights reserved. > > FreeBSD 4.0-CURRENT #1: Thu Mar 25 21:37:03 WST 1999 > > toor@bloop.craftncomp.com:/data/src/sys/compile/bleep > > Timecounter "i8254" frequency 1193182 Hz > > CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) > > Origin = "AuthenticAMD" Id = 0x484 Stepping=4 > > Features=0x1 > > real memory = 16777216 (16384K bytes) > > avail memory = 13750272 (13428K bytes) > > Preloaded elf kernel "kernel" at 0xc02c3000. > > Preloaded elf module "linux.ko" at 0xc02c309c. > > Probing for devices on PCI bus 0: > > chip0: rev 0x00 on pci0.0.0 > > rl0: rev 0x10 int a irq 9 on pci0.4.0 > > rl0: Ethernet address: 00:00:e8:53:a2:3e > > rl0: autoneg complete, link status good (half-duplex, 10Mbps) I'm going to go _way_ out on a limb here and suggest that you try and coerce your system BIOS to assign the RealTek interface an IRQ other than 9. I say 'try' because sometimes you aren't given the option to configure this. Usually there's some configuration menu that lets you 'reserve IRQs for legacy/ISA devices.' You should put IRQ 9 on the reserved list so that the BIOS will pick another. Hopefully it will be an IRQ that isn't shared with another device. If there aren't any free ones left. you can try disabling one of the serial ports in order to free up an IRQ (e.g. turn off COM2). -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 8:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 7837914CFD for ; Tue, 30 Mar 1999 08:34:51 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id SAA21202; Tue, 30 Mar 1999 18:34:08 +0200 (CEST) (envelope-from leifn@swimsuit.internet.dk) Date: Tue, 30 Mar 1999 18:34:08 +0200 (CEST) From: Leif Neland X-Sender: leifn@arnold.neland.dk To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: AIC In-Reply-To: <9379.922801598@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 30 Mar 1999, Sheldon Hearn wrote: > > > On Tue, 30 Mar 1999 17:28:06 +0400, Ilya Naumov wrote: > > > i wonder what is the situation with AIC driver now? we're suffering > > without it :) > > All traces of it have been completely removed from CURRENT. > > You should follow your cvs mail. :-) > Is it doomed forever? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 8:52: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D5B715B14 for ; Tue, 30 Mar 1999 08:52:06 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id IAA30736; Tue, 30 Mar 1999 08:51:06 -0800 Date: Tue, 30 Mar 1999 08:51:06 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Soren Schmidt Cc: Kenneth Wayne Culver , current@FreeBSD.ORG Subject: Re: the ATA driver In-Reply-To: <199903300933.LAA60345@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Remember that we have lost significant I/O bandwidth currently due > to changes in vfs_bio and freinds. > ?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 9:12:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 3302215C47 for ; Tue, 30 Mar 1999 09:12:46 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. (async2-00.iptelecom.net.ua [212.42.68.128]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id UAA01336; Tue, 30 Mar 1999 20:12:56 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id UAA12686; Tue, 30 Mar 1999 20:09:11 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37010558.D7364F52@altavista.net> Date: Tue, 30 Mar 1999 20:09:44 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE4: ATA/ATAPI driver new version available. References: <199903301143.NAA60602@freebsd.dk> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Soren, Following is answers on your (and other folks) questions concerning hang mentioned above. 1. Yes I have powersaving enabled, but as long as disk being accessed it should not to go sleep. 2. Don't mind why I need to zeroing my disk - leave it as it is. 3. Swapping on this partition was disabled (really it is not swap space it just empty partition). 4. Reading out of this partition working perfectly (dd if=/dev/... of=/dev/null bs=1024k). 5. Hang doesn't depend on partition type - I observed it on 165 (FreeBSD) and on 6 (FAT) partitions. 6. As long I can approximate - system hangs somewhere at the end of partition (I used reading time to approximate it). Sincerely, Maxim Sobolev Soren Schmidt wrote: > It seems Soren Schmidt wrote: > > It seems Maxim Sobolev wrote: > > > > > >New ata driver (cvsup'ed several minutes ago) locks my box solid (only > > >reset but ton can help). Bug is fully reproducible on my machine (Toshiba Satellite Pro 445). > > >I using the following command: dd if=/dev/zero of=/dev/ad0s2 bs=1024k. It > > >works several minutes then IDE led turns off and box freezes. Interesting that > > >when I looking at systat -vm measures, performance constantly degrades from > > >3.3MB/s to 2.5MB/s. > > >Bug exist either in single-user and in multi-user mode. Following is relevant dmesg pieces from my dmesg output: > > > > Hmm, are you sure you want to WRITE all those zeros to your disk ?? > > However it should not hang before the end of disk is reached that is. > > Have you tried reading all of the disk instead, does that hang ?? > > The degradation is probably becuse the transferrate of the disk slows > > down as you get closer to the center of the disk. > > Have you anu idea on how much data is transferred ?? how long is it > > running ?? > > OH, I forgot to ask if you have any powersaving stuff enabled too, > as the new driver dont know about that yet, if the disk goes to sleep > under its feet it will die, but given access to the disk thats probably > not likely... > > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 9:17:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id A7BA514F46 for ; Tue, 30 Mar 1999 09:16:54 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id TAA60569; Tue, 30 Mar 1999 19:16:32 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id TAA22023; Tue, 30 Mar 1999 19:16:31 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903301716.TAA22023@greenpeace.grondar.za> To: Chuck Robey Cc: freebsd-current@freebsd.org Subject: Re: ctm In-Reply-To: Your message of " Tue, 30 Mar 1999 08:06:45 EST." References: Date: Tue, 30 Mar 1999 19:16:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > Look what the egcs import's done to ctm: > > ctm_dequeue: cvs-cur.5193.gz 1/92 sent > > 92 pieces .... well, that knocks ctm out of action for a few days, so > they won't be complaining about things not building for awhile. Not really :-). It's already been built. The only problem now is mailing all that shit out... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 9:51:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A8E7314CE4 for ; Tue, 30 Mar 1999 09:51:51 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA49129; Tue, 30 Mar 1999 09:51:15 -0800 (PST) (envelope-from obrien) Message-ID: <19990330095115.A49115@nuxi.com> Date: Tue, 30 Mar 1999 09:51:15 -0800 From: "David O'Brien" To: Mark Murray , Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: ctm Reply-To: obrien@NUXI.com References: <199903301716.TAA22023@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903301716.TAA22023@greenpeace.grondar.za>; from Mark Murray on Tue, Mar 30, 1999 at 07:16:30PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Look what the egcs import's done to ctm: ..snip.. > Not really :-). It's already been built. The only problem now is mailing > all that shit out... Don't forget to trim out the entire copy of textinfo... now that *is* shit. ;-) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 12:31:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id A678914D54 for ; Tue, 30 Mar 1999 12:31:26 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id PAA12136; Tue, 30 Mar 1999 15:30:56 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id PAA19447; Tue, 30 Mar 1999 15:30:55 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903301129.NAA60572@freebsd.dk> Date: Tue, 30 Mar 1999 15:30:52 -0500 (EST) From: John Baldwin To: Soren Schmidt , freebsd-current@freebsd.org Subject: Re: UPDATE4: ATA/ATAPI driver new version available. Cc: sobomax@altavista.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Mar-99 Soren Schmidt wrote: > It seems Maxim Sobolev wrote: >> >>New ata driver (cvsup'ed several minutes ago) locks my box solid (only >>reset but ton can help). Bug is fully reproducible on my machine (Toshiba >>Satellite Pro 445). >>I using the following command: dd if=/dev/zero of=/dev/ad0s2 bs=1024k. It >>works several minutes then IDE led turns off and box freezes. Interesting >>that >>when I looking at systat -vm measures, performance constantly degrades from >>3.3MB/s to 2.5MB/s. >>Bug exist either in single-user and in multi-user mode. Following is relevant >>dmesg pieces from my dmesg output: > > Hmm, are you sure you want to WRITE all those zeros to your disk ?? > However it should not hang before the end of disk is reached that is. > Have you tried reading all of the disk instead, does that hang ?? > The degradation is probably becuse the transferrate of the disk slows > down as you get closer to the center of the disk. > Have you anu idea on how much data is transferred ?? how long is it > running ?? > > > -Søren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I had similar problems in -stable with the old ATA drivers. I was having weird swap errors, so I booted w/o swap and dd'd my swap partitions to check for read or write errors. I could do a dd if=/dev/wd0s3b of=/dev/null fine. But, when I tried a write from /dev/zero (dd if=/dev/zero of=/dev/wd0s3b) it locked up. If I specified the number of blocks to write, including enough blocks for the entire slice, the dd finished without a problem. If I let it figure out how much to write it locked the machine and I had to reset. However, that is with the old drivers on -stable, so I don't think it is your new stuff, Søren. ... Ok, I just checked on a -stable system built from sources dated March 28 and here is what I found: I can read and write from the raw devices (e.g. /dev/rwd0s3b) perfectly fine. I can read from the block devices (e.g. /dev/wd0s3b) fine. If I write to them with a specific count of blocks it works. The only problems are from writing without blockcounts. Here's the output (approx.) > dd if=/dev/zero of=/dev/rwd0s3b bs=64k warning /dev/rwd0s3b: data overflows device (or something similar) 1216+0 records in 1216+0 recorsd out 76xxxxxxxxxx bytes blah blah blah.. > dd if=/dev/zero of=/dev/wd0s3b bs=64k Disk activity for a while (i think it actually goes long enough to finish the write), and then the machine locks up. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 12:36:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.vr.IN-Berlin.DE (gnu.in-berlin.de [192.109.42.4]) by hub.freebsd.org (Postfix) with ESMTP id 961D914D21 for ; Tue, 30 Mar 1999 12:36:26 -0800 (PST) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: from hirsch.in-berlin.de (root@hirsch.in-berlin.de [192.109.42.6]) by mail.vr.IN-Berlin.DE (8.9.1a/8.9.1) with ESMTP id WAA03853 for ; Tue, 30 Mar 1999 22:35:58 +0200 (CEST) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: by hirsch.in-berlin.de (Smail3.2) id ; Tue, 30 Mar 1999 22:35:31 +0200 (CEST) Received: (from balu@localhost) by dva.in-berlin.de (8.9.3/8.9.1) id WAA05420 for freebsd-current@freebsd.org; Tue, 30 Mar 1999 22:31:32 +0200 (CEST) (envelope-from balu) Date: Tue, 30 Mar 1999 22:31:32 +0200 From: Boris Staeblow To: freebsd-current@freebsd.org Subject: mount of write protected fd's Message-ID: <19990330223132.A4808@dva.in-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mount should detect that a fd is write-protected and mount it "ro" although no "mount -r" is given... Isn't it possible to detect the w/p status from the fd-controller? Only a suggestion... Boris -- balu@dva.in-berlin.de Boris Staeblow To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 13:31:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [207.244.223.187]) by hub.freebsd.org (Postfix) with ESMTP id 6F4CD14CC5 for ; Tue, 30 Mar 1999 13:31:00 -0800 (PST) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id QAA12229 for ; Tue, 30 Mar 1999 16:36:35 -0500 (EST) Date: Tue, 30 Mar 1999 16:36:35 -0500 (EST) From: Kelly Yancey To: freebsd-current@freebsd.org Subject: support for larger memory Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Time and time again we have all seen people get bit in the rear because BSDI compatibility was broken. Broken for a good cause, mind you, because FreeBSD seemed to lose a little of that "power to serve" when it died horribly on newer servers :) So, the good news is, we can now support large memory configurations (and I recall that 4G might not be that far off). The bad news is, the fairly decent number of programs which are available for BSDI but not FreeBSD won't run on FreeBSD now. Anyway, we all know that. But what I would like to know is: how does BSDI support large memory configurations? I'm confused on how it is that the $1000+ commercial BSD derivative can't handle running on newer servers (although it is pleasing to think a $0 BSD derivative can :) ) Surely, this cannot be the case, though. So, I'm curious, why is it that we needed to break BSDI compatibility in order to support large memory configurations. It would seem that the two shouldn't be mutually exclusive. Thanks, Kelly ~kbyanc@posi.net~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 13:39:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 0F19514C25 for ; Tue, 30 Mar 1999 13:39:29 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id QAA47485; Tue, 30 Mar 1999 16:38:27 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199903302138.QAA47485@misha.cisco.com> Subject: Re: mount of write protected fd's In-Reply-To: <19990330223132.A4808@dva.in-berlin.de> from Boris Staeblow at "Mar 30, 1999 10:31:32 pm" To: balu@dva.in-berlin.de (Boris Staeblow) Date: Tue, 30 Mar 1999 16:38:27 -0500 (EST) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Boris Staeblow once wrote: > mount should detect that a fd is write-protected and mount it "ro" > although no "mount -r" is given... Isn't it possible to detect the w/p > status from the fd-controller? Actually, the existing behavior is rather horrible. If you forget to specify ro for a read-only floppy, mount will succeed, but the kernel will keep complaining. It will also NOT let you umount the damn thing (even with -f), until you take the floppy out and write-enable it. Which, sometimes, requires use of duct tape... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 13:48:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 8EAB714C25 for ; Tue, 30 Mar 1999 13:48:33 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 7F34D2C for ; Wed, 31 Mar 1999 01:48:12 +0400 (MSD) Date: Wed, 31 Mar 1999 01:48:12 +0400 (MSD) From: oZZ!!! To: freebsd-current@FreeBSD.org Subject: Your system is too old to use this bsd.port.mk..... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I cvsup my system at 30.03.1999 23.55 MSK, then make world, but can't understand following problem: when i try to build application from port i c following: ===> windowmaker-0.51.2 : Your system is too old to use this bsd.port.mk. You need a fresh make world or an upgrade kit. Please go to http://www.freebsd.org/ports/ or a mirror site and follow the instructions. I think my system is too YOUNG, not TOO OLD: 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Mar 30 02:52:13 MSD 1999 What does it mean? Rgdz, Sergey A. Osokin aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 14: 5:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 9BDA315AA6 for ; Tue, 30 Mar 1999 14:05:22 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA14643; Tue, 30 Mar 1999 13:52:02 -0800 (PST) Message-ID: <37014781.4487EB71@whistle.com> Date: Tue, 30 Mar 1999 13:52:01 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: Kelly Yancey Cc: freebsd-current@FreeBSD.ORG Subject: Re: support for larger memory References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelly Yancey wrote: > > Time and time again we have all seen people get bit in the rear because > BSDI compatibility was broken. Broken for a good cause, mind you, because > FreeBSD seemed to lose a little of that "power to serve" when it died > horribly on newer servers :) > So, the good news is, we can now support large memory configurations > (and I recall that 4G might not be that far off). The bad news is, the > fairly decent number of programs which are available for BSDI but not > FreeBSD won't run on FreeBSD now. > > Anyway, we all know that. But what I would like to know is: how does > BSDI support large memory configurations? I'm confused on how it is that > the $1000+ commercial BSD derivative can't handle running on newer > servers (although it is pleasing to think a $0 BSD derivative can :) ) > Surely, this cannot be the case, though. > > So, I'm curious, why is it that we needed to break BSDI compatibility in > order to support large memory configurations. It would seem that the two > shouldn't be mutually exclusive. > > Thanks, > > Kelly > ~kbyanc@posi.net~ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message The problem is that in the default configuration the two address spaces, (kernel and user) are arranged to use non-intersecting address spaces. This allows the kernel to directly read from the user's space, and also means that the address space need not be changed when the process goes to kernel mode, saving valuable TLB flushes etc. Unfortunatly as memory has grown, the kernels 'sparse' method of allocating addresses within it's space has required more and more space to keep track of potentially larger and larger structures. Eventually the space needed grew more that that 'left over' above the user space. This required shrinking the 'address space' seen by the application program which is, unfortunatly, not completely transparent to the user application binary. One answer would be to allow the kernel space and user space to overlap. THis is what the original Unix systems did, making use of the PDP11-60's ability to hold separate address spacess for the executinve and application programs. The use of copyin() and copyout(), rather than direct copies, is both a throwback to this time, and at the same time "insurance" that BSD will be able to run pretty much without modification on architectures where such separation is mandated, or, should the situation arise, we decide to split the tow spaces, even on architectures where it is presently not done (e.g. PC). In the specific case of BSDI compatibility, I believe that there is a patch available that allows BSDI binaries to run in the smaller addres space. (I vaguely remember it involving the initial value of a register at exec time). This suggests that the BSDI runtime libraries were written with an eye to the future where they may themselves need to do a similar thing. Knowing the people involved, I'd say that this is not unlikely. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 14:13: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from midgard.dhs.org (dhcp9557108.columbus.rr.com [24.95.57.108]) by hub.freebsd.org (Postfix) with ESMTP id 1D0F615423 for ; Tue, 30 Mar 1999 14:13:06 -0800 (PST) (envelope-from caa@midgard.dhs.org) Received: (from caa@localhost) by midgard.dhs.org (8.9.3/8.9.3) id RAA39388; Tue, 30 Mar 1999 17:12:30 -0500 (EST) (envelope-from caa) Date: Tue, 30 Mar 1999 17:12:30 -0500 From: Charles Anderson To: oZZ!!! Cc: freebsd-current@FreeBSD.ORG Subject: Re: Your system is too old to use this bsd.port.mk..... Message-ID: <19990330171230.A39371@midgard.dhs.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from oZZ!!! on Wed, Mar 31, 1999 at 01:48:12AM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 31, 1999 at 01:48:12AM +0400, oZZ!!! wrote: > > Hello! > I cvsup my system at 30.03.1999 23.55 MSK, then make world, but > can't understand following problem: when i try to build application from > port i c following: > ===> windowmaker-0.51.2 : Your system is too old to use this bsd.port.mk. > You need a fresh make world or an upgrade kit. Please go to > http://www.freebsd.org/ports/ or a mirror site and follow the > instructions. > I think my system is too YOUNG, not TOO OLD: > 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Mar 30 02:52:13 MSD 1999 > > What does it mean? > > Rgdz, > Sergey A. Osokin aka oZZ, > osa@etrust.ru I don't know what changed it but date +%Y%m%d > /var/db/pkg/.mkversion fixed it. -Charlie -- Charles Anderson caa@wavefront.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 14:15:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 113D914BF8 for ; Tue, 30 Mar 1999 14:15:24 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA13245; Tue, 30 Mar 1999 14:12:32 -0800 (PST) Message-Id: <199903302212.OAA13245@implode.root.com> To: Kelly Yancey Cc: freebsd-current@FreeBSD.ORG Subject: Re: support for larger memory In-reply-to: Your message of "Tue, 30 Mar 1999 16:36:35 EST." From: David Greenman Reply-To: dg@root.com Date: Tue, 30 Mar 1999 14:12:32 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Time and time again we have all seen people get bit in the rear because >BSDI compatibility was broken. Broken for a good cause, mind you, because >FreeBSD seemed to lose a little of that "power to serve" when it died >horribly on newer servers :) > So, the good news is, we can now support large memory configurations >(and I recall that 4G might not be that far off). The bad news is, the >fairly decent number of programs which are available for BSDI but not >FreeBSD won't run on FreeBSD now. > > Anyway, we all know that. But what I would like to know is: how does >BSDI support large memory configurations? I'm confused on how it is that >the $1000+ commercial BSD derivative can't handle running on newer >servers (although it is pleasing to think a $0 BSD derivative can :) ) >Surely, this cannot be the case, though. > > So, I'm curious, why is it that we needed to break BSDI compatibility in >order to support large memory configurations. It would seem that the two >shouldn't be mutually exclusive. BSD/OS compatibility for v2.0 static binaries can be had again with a few modifications. Someone with access to BSD/OS v2.0 binaries, time, and appropriate knowledge, just needs to make them. The brokeness actually comes from a design screwup that BSDI made in the v2.0 crt0 which they apparantly later fixed in v3.0. We should be able to run v3 and later static binaries. We've never had support for any version of their shared binaries. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 14:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.t.dk (freesbee.t.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with SMTP id 2FA8715584 for ; Tue, 30 Mar 1999 14:22:11 -0800 (PST) (envelope-from ncbp@freesbee.t.dk) Received: (qmail 29971 invoked by uid 1002); 30 Mar 1999 22:21:49 -0000 Date: Wed, 31 Mar 1999 00:21:49 +0200 From: "Niels Chr. Bank-Pedersen" To: freebsd-current@FreeBSD.org Subject: Re: Your system is too old to use this bsd.port.mk..... Message-ID: <19990331002149.A29506@bank-pedersen.dk> Mail-Followup-To: freebsd-current@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from oZZ!!! on Wed, Mar 31, 1999 at 01:48:12AM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 31, 1999 at 01:48:12AM +0400, oZZ!!! wrote: > > Hello! > I cvsup my system at 30.03.1999 23.55 MSK, then make world, but > can't understand following problem: when i try to build application from > port i c following: > ===> windowmaker-0.51.2 : Your system is too old to use this bsd.port.mk. > You need a fresh make world or an upgrade kit. Please go to > http://www.freebsd.org/ports/ or a mirror site and follow the > instructions. > I think my system is too YOUNG, not TOO OLD: > 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Mar 30 02:52:13 MSD 1999 > > What does it mean? It means what it says :) - your "make world" didn't update /usr/share/mk so parts of your system is to old. You'll have to "cd /usr/src/share/mk && make install" to update the make "include" files. It might be a good idea to bring the rest of the system up to date by use of http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html I don't know if "make world" _should_ update /usr/share/mk, but apparantly it doesn't for the time beeing... > Sergey A. Osokin aka oZZ, > osa@etrust.ru /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 1149?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 14:22:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id 38E2915C43 for ; Tue, 30 Mar 1999 14:22:31 -0800 (PST) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id PAA04585; Tue, 30 Mar 1999 15:21:58 -0700 (MST) (envelope-from handy@lambic.physics.montana.edu) Date: Tue, 30 Mar 1999 15:21:58 -0700 (MST) From: Brian Handy To: Kelly Yancey Cc: freebsd-current@FreeBSD.ORG Subject: Re: support for larger memory In-Reply-To: Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, I'm curious, why is it that we needed to break BSDI compatibility in >order to support large memory configurations. It would seem that the two >shouldn't be mutually exclusive. Or, perhaps, we broke BSDI compatibility for a lot of people (?) at the expense of those few people who are running > 1GB... Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 14:50:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 16DAB14C43 for ; Tue, 30 Mar 1999 14:50:20 -0800 (PST) (envelope-from schuerge@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id AAA16079 for ; Wed, 31 Mar 1999 00:49:57 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id AAA09804 for ; Wed, 31 Mar 1999 00:49:56 +0200 (CEST) Received: (from schuerge@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id AAA10220 for freebsd-current@freebsd.org; Wed, 31 Mar 1999 00:49:56 +0200 (CEST) From: Thomas Schuerger Message-Id: <199903302249.AAA10220@wurzelausix.cs.uni-sb.de> Subject: nfs problems To: freebsd-current@freebsd.org Date: Wed, 31 Mar 1999 00:49:55 +0200 (CEST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm experiencing serious NFS problems, when a remote NFS directory (also on FreeBSD) mounted on my machine goes down for whatever reason (e.g. normal shutdown). From then on, any processes accessing the mounted NFS directory (e.g. executing ls or even df) will die and stay non-removable (kill -9 shows no effect on them!) in the system. If the remote server goes up again, then sometimes these processes work again. I wonder if this is a general problem of NFS or just a problem with FreeBSD (haven't checked it with non-current machines). Any ideas/fixes? Ciao, Thomas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 14:55:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id 88B52151D4 for ; Tue, 30 Mar 1999 14:55:04 -0800 (PST) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id PAA04715 for ; Tue, 30 Mar 1999 15:50:22 -0700 (MST) (envelope-from handy@lambic.physics.montana.edu) Date: Tue, 30 Mar 1999 15:50:22 -0700 (MST) From: Brian Handy To: freebsd-current@FreeBSD.ORG Subject: Re: support for larger memory In-Reply-To: Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 30 Mar 1999, Brian Handy wrote: > [Grumbling about BSDI compatibility] I take all that back. Well, all except the part about grumbling about my own network here, I'm just feeling grumpy and took it out on random passerby. :-) Happy trails, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 15:13: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 357F114C2D for ; Tue, 30 Mar 1999 15:12:57 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id SAA28065; Tue, 30 Mar 1999 18:21:44 -0500 (EST) Date: Tue, 30 Mar 1999 18:21:43 -0500 (EST) From: Alfred Perlstein To: Thomas Schuerger Cc: freebsd-current@FreeBSD.ORG Subject: Re: nfs problems In-Reply-To: <199903302249.AAA10220@wurzelausix.cs.uni-sb.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 31 Mar 1999, Thomas Schuerger wrote: > Hi! > > I'm experiencing serious NFS problems, when > a remote NFS directory (also on FreeBSD) mounted on my > machine goes down for whatever reason (e.g. normal > shutdown). From then on, any processes accessing the mounted > NFS directory (e.g. executing ls or even df) will die and stay > non-removable (kill -9 shows no effect on them!) in the system. > If the remote server goes up again, then sometimes these > processes work again. > > I wonder if this is a general problem of NFS or just a > problem with FreeBSD (haven't checked it with non-current > machines). Any ideas/fixes? This is freebsd following the NFS spec, please read the mount_nfs man page for the workaround (hint: intr). Check out the ORA book on NFS and NIS, it's quite good. -Alfred > > > Ciao, > Thomas. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Alfred Perlstein - Admin, coder, and admirer of all things BSD. -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 15:20: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 684A714FF8 for ; Tue, 30 Mar 1999 15:19:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA43671; Tue, 30 Mar 1999 15:19:38 -0800 (PST) (envelope-from dillon) Date: Tue, 30 Mar 1999 15:19:38 -0800 (PST) From: Matthew Dillon Message-Id: <199903302319.PAA43671@apollo.backplane.com> To: Brian Handy Cc: Kelly Yancey , freebsd-current@FreeBSD.ORG Subject: Re: support for larger memory References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> So, I'm curious, why is it that we needed to break BSDI compatibility in :>order to support large memory configurations. It would seem that the two :>shouldn't be mutually exclusive. : :Or, perhaps, we broke BSDI compatibility for a lot of people (?) at the :expense of those few people who are running > 1GB... : : : :Brian Has anyone tried implementing the %ebx solution yet? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 16:19:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from stephens.ml.org (cm2081634025.ponderosa.ispchannel.com [208.163.40.25]) by hub.freebsd.org (Postfix) with ESMTP id BF3E514DFB for ; Tue, 30 Mar 1999 16:19:40 -0800 (PST) (envelope-from tas@stephens.ml.org) Received: from stephens.ml.org (localhost [127.0.0.1]) by stephens.ml.org (8.9.2/8.9.2) with ESMTP id BAA36066; Wed, 31 Mar 1999 01:19:06 +0100 (BST) (envelope-from tas@stephens.ml.org) Message-Id: <199903310019.BAA36066@stephens.ml.org> To: dg@root.com Cc: Kelly Yancey , freebsd-current@FreeBSD.ORG, Thomas Stephens From: Thomas Stephens Subject: Re: support for larger memory In-reply-to: Your message of "Tue, 30 Mar 1999 14:12:32 PST." <199903302212.OAA13245@implode.root.com> Date: Tue, 30 Mar 1999 16:19:05 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > BSD/OS compatibility for v2.0 static binaries can be had again with a >few modifications. Someone with access to BSD/OS v2.0 binaries, time, and >appropriate knowledge, just needs to make them. > The brokeness actually comes from a design screwup that BSDI made in >the v2.0 crt0 which they apparantly later fixed in v3.0. We should be able >to run v3 and later static binaries. We've never had support for any >version of their shared binaries. Speaking of which, are there any plans to support BSD/OS 4.0 ELF binaries, either static or shared? I expect most binaries for BSD/OS will eventually be distributed in ELF format, but the likelihood that they'll use dynamic linking complicates things. I'd be willing to make an effort to contribute, but haven't got access to BSD/OS 4.0 (don't know if I've got the requisite knowledge either). None of the BSD/OS binaries I use have been converted to ELF yet, but I'll certainly miss them if they are (though, if they use shared libraries, it may not matter anyway). Thomas Stephens tas@stephens.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 17:13:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A96AF14BF9 for ; Tue, 30 Mar 1999 17:13:15 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id RAA03858; Tue, 30 Mar 1999 17:12:55 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id RAA18549; Tue, 30 Mar 1999 17:12:54 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 30 Mar 1999 17:12:54 -0800 (PST) Message-Id: <199903310112.RAA18549@vashon.polstra.com> To: dillon@apollo.backplane.com Subject: Re: support for larger memory In-Reply-To: <199903302319.PAA43671@apollo.backplane.com> References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903302319.PAA43671@apollo.backplane.com>, Matthew Dillon wrote: > > Has anyone tried implementing the %ebx solution yet? Not as far as I know. I was hoping that somebody who cared about BSD/OS compatibility would pick up the description of the fix, test it, and submit diffs. No takers, so far. :-( John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 17:32:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (Postfix) with ESMTP id 2F01415346 for ; Tue, 30 Mar 1999 17:32:31 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.8.8/Debian/GNU) with ESMTP id DAA17165 for ; Wed, 31 Mar 1999 03:32:11 +0200 Date: Wed, 31 Mar 1999 03:32:11 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: freebsd-current@FreeBSD.ORG Subject: Re: Your system is too old to use this bsd.port.mk..... In-Reply-To: <19990330171230.A39371@midgard.dhs.org> Message-ID: <9903310330000.17103-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> You need a fresh make world or an upgrade kit. Please go to >> http://www.freebsd.org/ports/ or a mirror site and follow the >> instructions. > I don't know what changed it but > date +%Y%m%d > /var/db/pkg/.mkversion > fixed it. It broke `make release' as well; suddenly /var/db/pkg/ wasn't created anymore. This cost me two days' worth of CPU cycles on a machine that was (supposedly) running -STABLE. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 18:47:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 2870914DC8; Tue, 30 Mar 1999 18:47:57 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu ([207.92.173.144]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id SAA16491; Tue, 30 Mar 1999 18:47:46 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id SAA46577; Tue, 30 Mar 1999 18:47:06 -0800 (PST) Date: Tue, 30 Mar 1999 18:47:06 -0800 (PST) Message-Id: <199903310247.SAA46577@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: current@freebsd.org, stable@freebsd.org Subject: /var/db/pkg/.mkversion From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Some of you may have stumbled upon bsd.port.mk complaining about the lack of said file even after a make world. This was caused by my mistake of forgetting to update src/share/mk at the same time I committed the check to bsd.port.mk. I have since corrected it so if you cvsup again and make world again (actually just "make install" in src/share/mk), all will be well. As a workaround, "echo 19990328 > /var/db/pkg/.mkversion" will work equally fine. Sorry for the trouble, -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 19:13: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 31BFD15503 for ; Tue, 30 Mar 1999 19:13:04 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA10821 (5.67b8/IDA-1.5 for ); Tue, 30 Mar 1999 19:12:30 -0800 From: Rahul Dhesi Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA09775; Tue, 30 Mar 1999 19:11:06 -0800 Date: Tue, 30 Mar 1999 19:11:06 -0800 Message-Id: <199903310311.AA09775@waltz.rahul.net> To: freebsd-current@freebsd.org Subject: Re: nfs problems References: X-Newsreader: NN version 6.5.1 (NOV) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: >This is freebsd following the NFS spec, please read the mount_nfs >man page for the workaround (hint: intr). In my experience the 'intr' filesystem mount option does not always work. As an example, I am often unable to abort from a hung 'df' when a remote NFS server is down. (Even if my current directory is not NFS-mounted.) This might be a problem specific to 'df', though. Ideally 'df' should check to make sure a remote NFS server is responding (via the NFS null procedure) before trying to get any filesystem info for that filesystem. -- Rahul Dhesi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 20:33:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (Postfix) with ESMTP id EB7D9155A6 for ; Tue, 30 Mar 1999 20:33:57 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id VAA26242; Tue, 30 Mar 1999 21:51:23 -0700 (MST) Message-Id: <199903310451.VAA26242@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Andreas Braukmann Cc: freebsd-current@FreeBSD.ORG Subject: Re: Subnotebook capable of running -current In-reply-to: Your message of "Tue, 30 Mar 1999 14:48:32 +0200." <19990330144832.A63763@paert.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Mar 1999 21:51:23 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > I want to purchase some kind of 'subnotebook', that has to > be as -current-compatible as possible. > > I anticipate the crowd whispering "Libretto, ... Libretto", but > I have to say, that I don't like the Libretto very much for its > crude screen resolution. > > Currently I'm tending towards the "Toshiba Portege 3010" > or the "Fujitsu LifeBook B110 Biblo". > > Any experiences with these decices? > > I'm wondering about the CD-drives connected thru a PCMCIA-Card > and FreeBSD-compatible PCMCIA-Network-Cards. I just got my toshiba portege 7020CT yesterday (it took 35 days and 3 reschedules to actually reach my front door!). Loaded 4.0-0306-SNAP and XF86-3.3.3.1 without problems (well, sorta, had to run sysinstall-XF86 config program a half dozen times b4 it worked properly...) This is the big brother to the 3010, 13.1" 1024x768 TFT display, neomagic 2200 chipset. The really nice part is that the main unit has neither floppy or CDROM, making it reasonably small for a 13" display. It comes with an external floppy and port replicator, but I opted for the optional loading dock which comes with floppy, DVDROM, and fxp0 (intel) 10/100 ethernet. So I was able to to do an NFS (ie ethernet) install with the dock network, not needing to deal with pc cards. To load packages I inserted my 3.1R CD into the DVD drive and ran /stand/sysinstall, worked great. I used defrag and fips b4 installing FreeBSD, seems to have worked OK also. I will continue to use m$$ucks for hardware setup till I get a handle on APM and friends. Now I just need some free time to help with the card-bus stuff! -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 21:17: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 9C549154FA for ; Tue, 30 Mar 1999 21:16:57 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id AAA19979 for ; Wed, 31 Mar 1999 00:16:38 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA29535; Wed, 31 Mar 1999 00:16:37 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id AAA82863 for freebsd-current@freebsd.org; Wed, 31 Mar 1999 00:16:37 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199903310516.AAA82863@bb01f39.unx.sas.com> Subject: make release failure(/var/db/pkg/.mkversion) To: freebsd-current@freebsd.org Date: Wed, 31 Mar 1999 00:16:37 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Sources current as of 9:30pm EST... ===> share/misc install -c -o root -g wheel -m 444 ascii birthtoken bsd-family-tree eqnchar flowers init.ee inter.phone iso3166 iso639 man.template mdoc.template operator scsi_modes /usr/share/misc ===> share/mk install -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/share/mk date '+%Y%m%d' > /var/db/pkg/.mkversion cannot create /var/db/pkg/.mkversion: directory nonexistent *** Error code 2 Stop. *** Error code 1 /var/db/pkg doesn't exist in the make release area... I don't know if it should or not... Thanks for any insight... -John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 23: 2:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 4371314C2D; Tue, 30 Mar 1999 23:02:32 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.2/8.9.2) id JAA40747; Wed, 31 Mar 1999 09:01:56 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199903310701.JAA40747@zibbi.mikom.csir.co.za> Subject: Re: /var/db/pkg/.mkversion In-Reply-To: <199903310247.SAA46577@silvia.hip.berkeley.edu> from Satoshi Asami at "Mar 30, 1999 6:47: 6 pm" To: asami@cs.berkeley.edu (Satoshi Asami) Date: Wed, 31 Mar 1999 09:01:56 +0200 (SAT) Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Some of you may have stumbled upon bsd.port.mk complaining about the > lack of said file even after a make world. This was caused by my > mistake of forgetting to update src/share/mk at the same time I > committed the check to bsd.port.mk. > > I have since corrected it so if you cvsup again and make world again > (actually just "make install" in src/share/mk), all will be well. As > a workaround, "echo 19990328 > /var/db/pkg/.mkversion" will work > equally fine. Now that "make world" do something in /var/db/pkg, shouldn't /var/db/pkg be added to the mtree list for 3.1-STABLE and current? Otherwise a make release will break and also a make world if you haven't installed any packages yet. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 23: 3:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 3852715510 for ; Tue, 30 Mar 1999 23:03:39 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA00353; Wed, 31 Mar 1999 17:03:18 +1000 Date: Wed, 31 Mar 1999 17:03:18 +1000 From: Bruce Evans Message-Id: <199903310703.RAA00353@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, jobaldwi@vt.edu, sos@freebsd.dk Subject: Re: UPDATE4: ATA/ATAPI driver new version available. Cc: sobomax@altavista.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I had similar problems in -stable with the old ATA drivers. I was having weird >swap errors, so I booted w/o swap and dd'd my swap partitions to check for read >or write errors. I could do a dd if=/dev/wd0s3b of=/dev/null fine. But, when >I tried a write from /dev/zero (dd if=/dev/zero of=/dev/wd0s3b) it locked up. Writing beyond EOF to a buffered disk device hangs both 3.x and -current. The failing writes are retried forever. >> dd if=/dev/zero of=/dev/wd0s3b bs=64k > >Disk activity for a while (i think it actually goes long enough to finish the >write), and then the machine locks up. The easiest fix is: don't do that. Unbuffered disk devices are slower than buffered ones. Buffered disk devices are only useful for: - mounting on - finding bugs in the buffer cache. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 23: 4:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 45A1815510 for ; Tue, 30 Mar 1999 23:04:50 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 20495 invoked by uid 1001); 31 Mar 1999 07:04:30 +0000 (GMT) To: jhay@mikom.csir.co.za Cc: asami@cs.berkeley.edu, current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 31 Mar 1999 09:01:56 +0200 (SAT)" References: <199903310701.JAA40747@zibbi.mikom.csir.co.za> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 31 Mar 1999 09:04:30 +0200 Message-ID: <20493.922863870@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have since corrected it so if you cvsup again and make world again > > (actually just "make install" in src/share/mk), all will be well. As > > a workaround, "echo 19990328 > /var/db/pkg/.mkversion" will work > > equally fine. > > Now that "make world" do something in /var/db/pkg, shouldn't /var/db/pkg > be added to the mtree list for 3.1-STABLE and current? Otherwise a > make release will break and also a make world if you haven't installed > any packages yet. I definitely think so. I had to create /var/db/pkg by hand on a machine I upgraded to 3.1-STABLE yesterday. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 30 23: 9:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 2D62F153A3; Tue, 30 Mar 1999 23:09:13 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu ([207.92.173.144]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id XAA16730; Tue, 30 Mar 1999 23:09:02 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id XAA47424; Tue, 30 Mar 1999 23:08:20 -0800 (PST) Date: Tue, 30 Mar 1999 23:08:20 -0800 (PST) Message-Id: <199903310708.XAA47424@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: jhay@mikom.csir.co.za Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: <199903310701.JAA40747@zibbi.mikom.csir.co.za> (message from John Hay on Wed, 31 Mar 1999 09:01:56 +0200 (SAT)) Subject: Re: /var/db/pkg/.mkversion From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: <199903310701.JAA40747@zibbi.mikom.csir.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: John Hay * Now that "make world" do something in /var/db/pkg, shouldn't /var/db/pkg * be added to the mtree list for 3.1-STABLE and current? Otherwise a * make release will break and also a make world if you haven't installed * any packages yet. Oh, so *that* was what was breaking release! I didn't know that it's not in BSD.var.dist and thought there was some other reason that it was breaking release. Thanks, fixed. -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 0: 1:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id E8E55150E0 for ; Wed, 31 Mar 1999 00:01:37 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. (async2-07.iptelecom.net.ua [212.42.68.135]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id LAA03978; Wed, 31 Mar 1999 11:01:53 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA14263; Wed, 31 Mar 1999 10:59:43 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3701D617.F7F6253B@altavista.net> Date: Wed, 31 Mar 1999 11:00:24 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE5: ATA/ATAPI driver new version available. References: <199903301324.PAA60878@freebsd.dk> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Soren, Following is small patch for your great ata driver which intended to disable annoying "unwanted interrupt" console message on notebooks (personally I have it every 1 minute of absent disk activity ;)  ) Sincerely, Maxim Sobolev *** ata-all.c.orig      Wed Mar 31 10:28:05 1999 --- ata-all.c   Wed Mar 31 10:29:39 1999 *************** *** 456,462 **** --- 456,464 ----       default:       case ATA_IDLE:         if (intcount++ < 10) +       #ifndef SURPRESS_UNWANTED             printf("ata%d: unwanted interrupt %d\n", unit, intcount); +       #endif           inb(scp->ioaddr + ATA_STATUS);         return;       }   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 0: 1:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 08D89154B7 for ; Wed, 31 Mar 1999 00:01:39 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. (async2-07.iptelecom.net.ua [212.42.68.135]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id LAA03981 for ; Wed, 31 Mar 1999 11:01:55 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA14212 for ; Wed, 31 Mar 1999 10:48:27 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3701D373.F8D8045@altavista.net> Date: Wed, 31 Mar 1999 10:49:08 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Sysinstall is not friendly to foreign boot managers Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It seems that sysinstall silently marking FreeBSD partition as active even if I have other partition active (WinNT in my case) and have working NT boot manager to boot FreeBSD. This behaviour observed not only in Fdisk editor but in Label Editor as well. Sincerely, Maxim Sobolev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 0: 7:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 616DF150E0 for ; Wed, 31 Mar 1999 00:07:38 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10SG0N-0003G7-00; Wed, 31 Mar 1999 10:05:43 +0200 From: Sheldon Hearn To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: AIC In-reply-to: Your message of "Tue, 30 Mar 1999 18:34:08 +0200." Date: Wed, 31 Mar 1999 10:05:43 +0200 Message-ID: <12530.922867543@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 30 Mar 1999 18:34:08 +0200, Leif Neland wrote: > Is it doomed forever? Grrr, I think the whole reason it was removed was to avoid questions like this. ;-) The removed aic driver is not under active development, and there are no plans to revive it in the foreseeable future. See? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 0:53:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id E1D2915BFD; Wed, 31 Mar 1999 00:53:40 -0800 (PST) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Wed, 31 Mar 1999 09:53:13 +0100 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id GZL8KFK4; Wed, 31 Mar 1999 09:46:35 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10SGnA-0005bh-00; Wed, 31 Mar 1999 09:56:08 +0100 To: asami@cs.berkeley.edu (Satoshi Asami) Cc: current@freebsd.org, stable@freebsd.org Subject: Re: /var/db/pkg/.mkversion X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: Satoshi Asami's message of "Tue, 30 Mar 1999 18:47:06 -0800" <199903310247.SAA46577@silvia.hip.berkeley.edu> Date: Wed, 31 Mar 1999 09:56:07 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30 March 1999, Satoshi Asami proclaimed: > Some of you may have stumbled upon bsd.port.mk complaining about the > lack of said file even after a make world. This was caused by my > mistake of forgetting to update src/share/mk at the same time I > committed the check to bsd.port.mk. > > I have since corrected it so if you cvsup again and make world again > (actually just "make install" in src/share/mk), all will be well. As > a workaround, "echo 19990328 > /var/db/pkg/.mkversion" will work > equally fine. Just a side note; this new file breaks pkg_info. I've appended a simple patch below; somebody ought to do something better for the version in the src tree. Whilst I'm here, a tip. If you use the zsh, here's command completion for the some of the pkg commands: compctl -g '/var/db/pkg/*(/:t)' pkg_delete pkg_info -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Value of 2 may go down as well as up" -- FORTRAN programmers manual diff -urP /usr/src/usr.sbin/pkg_install/info/perform.c pkg_install/info/perform.c --- /usr/src/usr.sbin/pkg_install/info/perform.c Mon Jan 4 06:15:40 1999 +++ pkg_install/info/perform.c Wed Mar 31 09:43:41 1999 @@ -135,8 +135,10 @@ return 1; } if (chdir(log_dir) == FAIL) { - warnx("can't change directory to '%s'!", log_dir); - return 1; + if (strcmp(log_dir, "/var/db/pkg/.mkversion") != 0) { + warnx("can't change directory to '%s'!", log_dir); + return 1; + } } installed = TRUE; } -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 1: 8:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 8545B14C49; Wed, 31 Mar 1999 01:08:19 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca3-65.ix.netcom.com [209.109.233.65]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA16928; Wed, 31 Mar 1999 01:08:08 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id BAA48078; Wed, 31 Mar 1999 01:07:51 -0800 (PST) Date: Wed, 31 Mar 1999 01:07:51 -0800 (PST) Message-Id: <199903310907.BAA48078@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: Dom.Mitchell@palmerharvey.co.uk Cc: current@freebsd.org, jkh@freebsd.org In-reply-to: (message from Dom Mitchell on Wed, 31 Mar 1999 09:56:07 +0100) Subject: Re: /var/db/pkg/.mkversion From: asami@freebsd.org (Satoshi - the Wraith - Asami) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Dom Mitchell * Just a side note; this new file breaks pkg_info. I've appended a simple * patch below; somebody ought to do something better for the version in * the src tree. Eek. I didn't know it tries to open all files without checking whether it's a directory or not.... * if (chdir(log_dir) == FAIL) { * - warnx("can't change directory to '%s'!", log_dir); * - return 1; * + if (strcmp(log_dir, "/var/db/pkg/.mkversion") != 0) { * + warnx("can't change directory to '%s'!", log_dir); * + return 1; * + } This doesn't look right. I found where it's skipping "." and "..", either we add ".mkversion" there, skip all entries that start with an ".", or check whether a given entry is a directory. I implemented the second option, I think I can ensure that there will be no packages that start with a ".". Jordan, is this ok? === Index: perform.c =================================================================== RCS file: /usr/cvs/src/usr.sbin/pkg_install/info/perform.c,v retrieving revision 1.26 diff -u -r1.26 perform.c --- perform.c 1998/12/16 13:59:31 1.26 +++ perform.c 1999/03/31 09:04:50 @@ -57,7 +57,7 @@ dirp = opendir(tmp); if (dirp) { for (dp = readdir(dirp); dp != NULL; dp = readdir(dirp)) - if (strcmp(dp->d_name, ".") && strcmp(dp->d_name, "..")) + if (dp->d_name[0] != '.') err_cnt += pkg_do(dp->d_name); (void)closedir(dirp); } === -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 5: 5:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.nwnexus.com (smtp10.nwnexus.com [206.63.63.53]) by hub.freebsd.org (Postfix) with ESMTP id DAF2515C64; Wed, 31 Mar 1999 05:05:27 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx100-ip24.nwnexus.net [204.57.235.24]) by smtp10.nwnexus.com (8.8.8/8.8.8) with ESMTP id FAA29828; Wed, 31 Mar 1999 05:05:03 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.2/8.8.8) id FAA72625; Wed, 31 Mar 1999 05:01:14 -0800 (PST) (envelope-from wrsomsky) Date: Wed, 31 Mar 1999 05:01:14 -0800 From: "William R. Somsky" To: Dom Mitchell Cc: Satoshi Asami , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion Message-ID: <19990331050114.B72493@gramarye.halcyon.com> References: <199903310247.SAA46577@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dom Mitchell on Wed, Mar 31, 1999 at 09:56:07AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 31, 1999 at 09:56:07AM +0100, Dom Mitchell wrote: > On 30 March 1999, Satoshi Asami proclaimed: > > Just a side note; this new file breaks pkg_info. I've appended a simple > patch below; somebody ought to do something better for the version in > the src tree. > Yep, this definitely suggests that /var/db/pkg isn't the appropriate place for the "make version" file. I think /usr/share/mk would be better. After all, that's where the make files that it's saying what the date of are anyway. And potentially, things other than ports might want to refer to it as well. -- ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 10:36: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 80C9A14CD5 for ; Wed, 31 Mar 1999 10:35:35 -0800 (PST) (envelope-from imp@rover.village.org) Received: (from imp@localhost) by rover.village.org (8.9.3/8.9.3) id LAA00284; Wed, 31 Mar 1999 11:35:13 -0700 (MST) (envelope-from imp) Date: Wed, 31 Mar 1999 11:35:13 -0700 (MST) From: Warner Losh Message-Id: <199903311835.LAA00284@rover.village.org> To: leifn@neland.dk, sheldonh@iafrica.com Subject: Re: AIC Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <12530.922867543@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The aic driver will likely oneday be ported. However, no one has come forward to do it. It is a highly desirable driver to have (even if writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. However, the sad fact is that the development is less than active on this driver. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 10:53:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 2DF191552B for ; Wed, 31 Mar 1999 10:53:50 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id KAA22652 for freebsd-current@freebsd.org; Wed, 31 Mar 1999 10:51:39 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199903311851.KAA22652@troutmask.apl.washington.edu> Subject: egcs knob and objective C To: freebsd-current@freebsd.org Date: Wed, 31 Mar 1999 10:51:39 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a simple knob to turn to get the egcs compiler by default? I'm willing to help test egcs for the transition from gcc+2.7.x. I've looked through the Makefiles and the /usr/src/gnu directory, but I can't seem to locate a knob to turn for the egcs compiler (unless I need to mangle the .PATH variable). And, at the risk of being flamed, I noticed (after all these years) that we build some for Objective C stuff. Is this actually required within the base distribution? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 12:19:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 3C0EA15C8B for ; Wed, 31 Mar 1999 12:19:39 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 6C36F18C6; Wed, 31 Mar 1999 22:19:26 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 691AE4999; Wed, 31 Mar 1999 22:19:26 +0200 (CEST) Date: Wed, 31 Mar 1999 22:19:26 +0200 (CEST) From: Andrzej Bialecki To: Steve Kargl Cc: freebsd-current@FreeBSD.ORG Subject: Re: egcs knob and objective C In-Reply-To: <199903311851.KAA22652@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 31 Mar 1999, Steve Kargl wrote: > Is there a simple knob to turn to get the egcs compiler by > default? I'm willing to help test egcs for the transition > from gcc+2.7.x. > > I've looked through the Makefiles and the /usr/src/gnu directory, > but I can't seem to locate a knob to turn for the egcs compiler > (unless I need to mangle the .PATH variable). > > And, at the risk of being flamed, I noticed (after all these years) > that we build some for Objective C stuff. Is this actually required > within the base distribution? Also, I seem to recall that we already have another copy of libiberty (under gdb). Do we really need to have both of them? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 12:29: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 6F62615659 for ; Wed, 31 Mar 1999 12:29:08 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:1728@shell2.aracnet.com [205.159.88.20]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with ESMTP id MAA31605; Wed, 31 Mar 1999 12:28:47 -0800 Received: from localhost by shell2.aracnet.com (8.8.7) id MAA30935; Wed, 31 Mar 1999 12:28:48 -0800 X-Authentication-Warning: shell2.aracnet.com: beattie owned process doing -bs Date: Wed, 31 Mar 1999 12:28:47 -0800 (PST) From: Brian Beattie To: Warner Losh Cc: leifn@neland.dk, sheldonh@iafrica.com, freebsd-current@FreeBSD.ORG Subject: Re: AIC In-Reply-To: <199903311835.LAA00284@rover.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 31 Mar 1999, Warner Losh wrote: > The aic driver will likely oneday be ported. However, no one has come > forward to do it. It is a highly desirable driver to have (even if Umm, I'm still working on the aic driver. Slowly, but working on it. > writing it would be a pain) because the only pccard scsi cards that are > out there are aic-6[23]60 based. > Not having a pcmcia slot or card, I am not sure about support for this. > However, the sad fact is that the development is less than active on this > driver. > It is a fact, sad? Im not sure. except for the pccard stuff there is much better stuff than the 6x60 based hardware. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 15:26:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 0DA5B15635 for ; Wed, 31 Mar 1999 15:26:19 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id SAA01783 for ; Wed, 31 Mar 1999 18:24:31 -0500 (EST) Date: Wed, 31 Mar 1999 18:24:31 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: boot up messages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a reason to go check when I last installed my kernel, so I did a dmesg to take a look at the boot message, and the greeting from the Regents isn't there anymore. It wasn't there in the var/log/messages either. I'm not interested in the time (uname gave me that), but rather where the boot message got off to. It still shows on the console during boot (I checked) but that's all. I use the new loader.conf mechanism to boot with, and I also notice that the dmesg now is too short to catch teh entire boot message (I load about 8 modules, and the first couple get truncated). How would I increase the amount of memory given to boot messages for dmesg? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 15:47: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id B71E815C06; Wed, 31 Mar 1999 15:46:56 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id QAA26567; Wed, 31 Mar 1999 16:46:05 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903312346.QAA26567@freebie.dcfinc.com> Subject: Re: /var/db/pkg/.mkversion To: asami@cs.berkeley.edu (Satoshi Asami) Date: Wed, 31 Mar 1999 16:46:04 -0700 (MST) Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199903310247.SAA46577@silvia.hip.berkeley.edu> from Satoshi Asami at "Mar 30, 99 06:47:06 pm" Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > Some of you may have stumbled upon bsd.port.mk complaining about the > lack of said file even after a make world. This was caused by my > mistake of forgetting to update src/share/mk at the same time I > committed the check to bsd.port.mk. > > I have since corrected it so if you cvsup again and make world again > (actually just "make install" in src/share/mk), all will be well. As > a workaround, "echo 19990328 > /var/db/pkg/.mkversion" will work > equally fine. CVSup'd RELENG_2_2 this afternoon, did make install in /usr/src/share/mk. Still no good. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 16: 0:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id AE5B315635; Wed, 31 Mar 1999 16:00:34 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca2-121.ix.netcom.com [205.186.212.121]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id QAA17887; Wed, 31 Mar 1999 16:00:24 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id QAA51145; Wed, 31 Mar 1999 16:00:09 -0800 (PST) Date: Wed, 31 Mar 1999 16:00:09 -0800 (PST) Message-Id: <199904010000.QAA51145@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: chad@dcfinc.com Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: <199903312346.QAA26567@freebie.dcfinc.com> (chad@freebie.dcfinc.com) Subject: Re: /var/db/pkg/.mkversion From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: <199903312346.QAA26567@freebie.dcfinc.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Chad R. Larson" * CVSup'd RELENG_2_2 this afternoon, did make install in * /usr/src/share/mk. Still no good. Oh yes, RELENG_2_2. Sorry, fixed. -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 16:46:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 303F114CC4 for ; Wed, 31 Mar 1999 16:46:47 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from rcc.on.ca (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with ESMTP id VAA24224 for ; Wed, 31 Mar 1999 21:04:29 -0500 Message-ID: <370308C1.9B908465@rcc.on.ca> Date: Thu, 01 Apr 1999 00:48:50 -0500 From: Rod Taylor X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Games Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just out of curiosity, why are there games included in the FreeBSD source tree? For a group of people that was so worried about including dhcp because it's extra code, don't you think it's time to make those games into ports only? I say this under the assumption that they're not required for FreeBSD to function. (Not like IE for windows ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 18:14: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from stephens.ml.org (cm2081634025.ponderosa.ispchannel.com [208.163.40.25]) by hub.freebsd.org (Postfix) with ESMTP id 79B7014D8E for ; Wed, 31 Mar 1999 18:13:45 -0800 (PST) (envelope-from tas@stephens.ml.org) Received: from stephens.ml.org (localhost [127.0.0.1]) by stephens.ml.org (8.9.2/8.9.2) with ESMTP id DAA39218; Thu, 1 Apr 1999 03:12:56 +0100 (BST) (envelope-from tas@stephens.ml.org) Message-Id: <199904010212.DAA39218@stephens.ml.org> To: John Polstra Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG, Thomas Stephens From: Thomas Stephens Subject: Re: support for larger memory In-reply-to: Your message of "Tue, 30 Mar 1999 17:12:54 PST." <199903310112.RAA18549@vashon.polstra.com> Date: Wed, 31 Mar 1999 18:12:56 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: >In article <199903302319.PAA43671@apollo.backplane.com>, >Matthew Dillon wrote: >> >> Has anyone tried implementing the %ebx solution yet? > >Not as far as I know. I was hoping that somebody who cared about >BSD/OS compatibility would pick up the description of the fix, test >it, and submit diffs. No takers, so far. :-( I'll bite. I tried your fix this morning, and it's worked without a problem so far. I've just upgraded the world (had only built a kernel earlier), and haven't done any rigorous testing, but it looks good. I use the AT&T ksh for BSD/OS as my standard shell, which should be a reasonable test, but haven't got access to BSD/OS itself, so don't have much to test beyond the AT&T tools. Unless something goes wrong, I'll probably submit the diffs within the next day or so. Thomas Stephens tas@stephens.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 18:24:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 41C8B151A3 for ; Wed, 31 Mar 1999 18:24:25 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id SAA10715; Wed, 31 Mar 1999 18:24:00 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id SAA22496; Wed, 31 Mar 1999 18:24:00 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904010212.DAA39218@stephens.ml.org> Date: Wed, 31 Mar 1999 18:24:00 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Thomas Stephens Subject: Re: support for larger memory Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Stephens wrote: > I tried your fix this morning, and it's worked without a problem > so far. I've just upgraded the world (had only built a kernel > earlier), and haven't done any rigorous testing, but it looks good. > I use the AT&T ksh for BSD/OS as my standard shell, which should be > a reasonable test, but haven't got access to BSD/OS itself, so don't > have much to test beyond the AT&T tools. > > Unless something goes wrong, I'll probably submit the diffs within > the next day or so. Hey, thanks a million! If you'd like to send your diffs to me when they're ready, I'll be happy to review them and commit them for you. I have some BSD/OS binaries I can try here, too. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 18:35:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A26FC151A3 for ; Wed, 31 Mar 1999 18:35:33 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id SAA61071; Wed, 31 Mar 1999 18:31:39 -0800 (PST) Date: Wed, 31 Mar 1999 18:31:38 -0800 (PST) From: Julian Elischer To: Thomas Stephens Cc: John Polstra , dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: support for larger memory In-Reply-To: <199904010212.DAA39218@stephens.ml.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One presumes that the BSDI binaries fail without the diff? :-) julian On Wed, 31 Mar 1999, Thomas Stephens wrote: > John Polstra wrote: > >In article <199903302319.PAA43671@apollo.backplane.com>, > >Matthew Dillon wrote: > >> > >> Has anyone tried implementing the %ebx solution yet? > > > >Not as far as I know. I was hoping that somebody who cared about > >BSD/OS compatibility would pick up the description of the fix, test > >it, and submit diffs. No takers, so far. :-( > > I'll bite. I tried your fix this morning, and it's worked without a > problem so far. I've just upgraded the world (had only built a kernel > earlier), and haven't done any rigorous testing, but it looks good. I > use the AT&T ksh for BSD/OS as my standard shell, which should be a > reasonable test, but haven't got access to BSD/OS itself, so don't have > much to test beyond the AT&T tools. > > Unless something goes wrong, I'll probably submit the diffs within the > next day or so. > > Thomas Stephens > tas@stephens.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 18:37:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id F0AC3151A3 for ; Wed, 31 Mar 1999 18:37:08 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id SAA10789; Wed, 31 Mar 1999 18:36:46 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id SAA22600; Wed, 31 Mar 1999 18:36:46 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 31 Mar 1999 18:36:46 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Julian Elischer Subject: Re: support for larger memory Cc: current@FreeBSD.ORG, Thomas Stephens Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > One presumes that the BSDI binaries fail without the diff? :-) Yes, that's been confirmed by lots of people, myself included. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 19:11:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E73811516F for ; Wed, 31 Mar 1999 19:11:33 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id MAA19944; Thu, 1 Apr 1999 12:09:54 +0900 (JST) Message-ID: <3702E01B.75465F21@newsguy.com> Date: Thu, 01 Apr 1999 11:55:23 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Brian Beattie Cc: Warner Losh , leifn@neland.dk, sheldonh@iafrica.com, freebsd-current@FreeBSD.ORG Subject: Re: AIC References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Beattie wrote: > > > writing it would be a pain) because the only pccard scsi cards that are > > out there are aic-6[23]60 based. > > Not having a pcmcia slot or card, I am not sure about support for this. Once aic6[23]60 is working, the PCMCIA stuff is easily done. > > However, the sad fact is that the development is less than active on this > > driver. > > It is a fact, sad? Im not sure. except for the pccard stuff there is much > better stuff than the 6x60 based hardware. But there are *no* alternatives for notebooks, except parallel port SCSI. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Yes, I am an agent of Satan, but my duties are largely ceremonial." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 19:17:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from wna1.wna-linknet.com (wna1.wna-linknet.com [208.128.88.10]) by hub.freebsd.org (Postfix) with ESMTP id CE58615250 for ; Wed, 31 Mar 1999 19:17:43 -0800 (PST) (envelope-from frodo@wna-linknet.com) Received: from brenda (cust138.wna-linknet.com [208.128.88.138]) by wna1.wna-linknet.com (8.8.8/8.8.8) with SMTP id WAA18479 for ; Wed, 31 Mar 1999 22:17:23 -0500 (EST) Message-ID: <004e01be7bed$87e749a0$0200000a@wnalinknet.com> From: "Edward Rempala" To: Subject: Date: Wed, 31 Mar 1999 22:12:07 -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.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth c6825c35 subscribe freebsd-current frodo@wna-linknet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 19:35:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7FA1714BD8 for ; Wed, 31 Mar 1999 19:35:33 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id MAA22764; Thu, 1 Apr 1999 12:35:27 +0900 (JST) Message-ID: <3702E799.FFBEC314@newsguy.com> Date: Thu, 01 Apr 1999 12:27:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Rod Taylor Cc: current@FreeBSD.ORG Subject: Re: Games References: <370308C1.9B908465@rcc.on.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rod Taylor wrote: > > Just out of curiosity, why are there games included in the FreeBSD > source tree? > > For a group of people that was so worried about including dhcp because > it's extra code, don't you think it's time to make those games into > ports only? > > I say this under the assumption that they're not required for FreeBSD to > function. (Not like IE for windows ;) Well, first of all, .profile, .cshrc and signature scripts are broken in the absense of fortune. Aside from that, because that's the BSD heritage. It was once suggested taking them out if they could be made into ports. But, then, the first issue came up. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Yes, I am an agent of Satan, but my duties are largely ceremonial." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 21:48:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 0178814EC4 for ; Wed, 31 Mar 1999 21:48:31 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id AAA64539; Thu, 1 Apr 1999 00:48:09 -0500 (EST) Date: Thu, 1 Apr 1999 00:48:08 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: mi@aldan.algebra.com Cc: Boris Staeblow , current@FreeBSD.ORG Subject: Re: mount of write protected fd's In-Reply-To: <199903302138.QAA47485@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 30 Mar 1999, Mikhail Teterin wrote: > Boris Staeblow once wrote: > > > mount should detect that a fd is write-protected and mount it "ro" > > although no "mount -r" is given... Isn't it possible to detect the w/p > > status from the fd-controller? > > Actually, the existing behavior is rather horrible. If you forget > to specify ro for a read-only floppy, mount will succeed, but the > kernel will keep complaining. It will also NOT let you umount the > damn thing (even with -f), until you take the floppy out and > write-enable it. Which, sometimes, requires use of duct tape... > > -mi Mount -u -o ro also works. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 22:21:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 51CED151AF for ; Wed, 31 Mar 1999 22:21:35 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id IAA20127; Thu, 1 Apr 1999 08:21:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id IAA30940; Thu, 1 Apr 1999 08:21:07 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Rod Taylor Cc: current@FreeBSD.ORG Subject: Re: Games In-reply-to: Your message of "Thu, 01 Apr 1999 00:48:50 CDT." <370308C1.9B908465@rcc.on.ca> Date: Thu, 01 Apr 1999 08:21:06 +0200 Message-ID: <30938.922947666@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <370308C1.9B908465@rcc.on.ca>, Rod Taylor writes: >Just out of curiosity, why are there games included in the FreeBSD >source tree? because: 1. They've always been there. 2. Every now and then factor comes handy. 3. Fortune is cool. 4. Deleting games is something people without humour does. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 22:31: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id D08FE15D1E for ; Wed, 31 Mar 1999 22:31:01 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id IAA28451 for freebsd-current@FreeBSD.ORG; Thu, 1 Apr 1999 08:30:41 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 7A964886B; Thu, 1 Apr 1999 08:13:46 +0200 (CEST) Date: Thu, 1 Apr 1999 08:13:46 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: boot up messages Message-ID: <19990401081346.A60682@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Chuck Robey on Wed, Mar 31, 1999 at 06:24:31PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Chuck Robey: > about 8 modules, and the first couple get truncated). How would I > increase the amount of memory given to boot messages for dmesg? cf LINT: # Size of the kernel message buffer. Should be N * pagesize. options "MSGBUF_SIZE=40960" And remember that in /var/run/dmesg.boot, you have all the boot messages (within MSGBUF_SIZE of course). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 22:46:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id EAF51155E8; Wed, 31 Mar 1999 22:46:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA07324; Wed, 31 Mar 1999 22:46:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Hay Cc: asami@cs.berkeley.edu (Satoshi Asami), current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-reply-to: Your message of "Sat, 31 Mar 1999 09:01:56 +0200." <199903310701.JAA40747@zibbi.mikom.csir.co.za> Date: Wed, 31 Mar 1999 22:46:31 -0800 Message-ID: <7322.922949191@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Now that "make world" do something in /var/db/pkg, shouldn't /var/db/pkg > be added to the mtree list for 3.1-STABLE and current? Otherwise a > make release will break and also a make world if you haven't installed > any packages yet. I think this entire thing is a massive botch and needs to be removed as a bad idea ASAP. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 22:52:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 913F415C39; Wed, 31 Mar 1999 22:52:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA07366; Wed, 31 Mar 1999 22:52:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) Cc: jhay@mikom.csir.co.za, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-reply-to: Your message of "Tue, 30 Mar 1999 23:08:20 PST." <199903310708.XAA47424@silvia.hip.berkeley.edu> Date: Wed, 31 Mar 1999 22:52:29 -0800 Message-ID: <7364.922949549@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Committing /var/db/pkg to mtree was fine, it probably should have been there to begin with. Sticking things into it outside of pkg_add, however, is evil. pkg_add "owns" this directory and every time we've tried to go behind its back, so to speak, we've been raped for it. The whole mess with XFree68 was a total nightmare and is what happens when changes like this are made without really thinking things out. No more kludges, please. I'm not changing sysinstall and make world shouldn't be writing into /var/db/pkg either. If you've found it necessasry to do this, then you've made a mistake just as you did with XFree86 and need to think about the problem again. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 31 23:43:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from angel.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (Postfix) with ESMTP id 4D80E153F0; Wed, 31 Mar 1999 23:43:25 -0800 (PST) (envelope-from mvergall@ns.double-barrel.be) Received: from ns.double-barrel.be (ns.double-barrel.be [194.7.102.18]) by angel.double-barrel.be (8.9.1b+Sun/8.9.1) with ESMTP id JAA05560; Thu, 1 Apr 1999 09:42:24 +0200 (MET DST) Received: from localhost (mvergall@localhost) by ns.double-barrel.be (8.8.7/8.8.7) with ESMTP id JAA01490; Thu, 1 Apr 1999 09:42:22 +0200 Date: Thu, 1 Apr 1999 09:42:22 +0200 (CEST) From: "Michael C. Vergallen" To: "Jordan K. Hubbard" Cc: John Hay , Satoshi Asami , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-Reply-To: <7322.922949191@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to bud in... but shouldn't /var/db/pkg be only used for package admin purpouses and only for that. Otherwise things get sloppy if one needs to have a .mkversion shouldn't it be in /etc and automatically generated upon bootup from the kernel version number or if the file is used to assetain how to build a port i.e. ELF or a.out their are other ways to accomplish this ...but eh I think the switch to ELF should be finalyzed soon becuase keeping the a.out ports in the current release could be confusing for newbies... namely if they havent installed the compat module it may get sticky... ( note I could be wrong here ). Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Wed, 31 Mar 1999, Jordan K. Hubbard wrote: > > Now that "make world" do something in /var/db/pkg, shouldn't /var/db/pkg > > be added to the mtree list for 3.1-STABLE and current? Otherwise a > > make release will break and also a make world if you haven't installed > > any packages yet. > > I think this entire thing is a massive botch and needs to be removed > as a bad idea ASAP. > > - 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-current" in the body of the message From owner-freebsd-current Thu Apr 1 0:39:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [212.20.32.33]) by hub.freebsd.org (Postfix) with SMTP id 6A8B814D0F for ; Thu, 1 Apr 1999 00:35:38 -0800 (PST) (envelope-from nnd@itfs.nsk.su) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id PAA09231 for current@freebsd.org; Thu, 1 Apr 1999 15:35:15 +0700 Received: by itfs.nsk.su; Thu, 1 Apr 99 15:31:40 +0600 (NSK) To: current@freebsd.org Message-ID: Organization: Scientific & Technical Enterprise INFOTEKA From: nnd@itfs.nsk.su (Nickolay Dudorov) Date: Thu, 1 Apr 99 15:31:40 +0600 (NSK) MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Subject: Fools Day Joke ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is some strangenes in date on file ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/cvs-cur/cvs-cur.5198.gz -r--r--r- 1 603 207 49741 apr 1 1998 cvs-cur.5198.gz N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 0:40:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 0E23415D2A for ; Thu, 1 Apr 1999 00:39:07 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Sczy-0003T8-00; Thu, 1 Apr 1999 10:38:50 +0200 From: Sheldon Hearn To: Rod Taylor Cc: current@freebsd.org Subject: Re: Games In-reply-to: Your message of "Thu, 01 Apr 1999 00:48:50 EST." <370308C1.9B908465@rcc.on.ca> Date: Thu, 01 Apr 1999 10:38:50 +0200 Message-ID: <13337.922955930@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 01 Apr 1999 00:48:50 EST, Rod Taylor wrote: > Just out of curiosity, why are there games included in the FreeBSD > source tree? Politics and hysterical raisins. If you don't want the "gamey" games, apply the diffs below to your source. Caio, Sheldon. Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.65 diff -u -d -r1.65 Makefile.inc1 --- Makefile.inc1 1999/03/01 01:09:06 1.65 +++ Makefile.inc1 1999/03/01 09:26:18 @@ -828,9 +828,6 @@ .endif .for d in \ bin/sh \ - ${_adventure} \ - ${_hack} \ - ${_phantasia} \ gnu/usr.bin/cc/cc_tools \ lib/libmytinfo \ ${_linux} \ Index: games/Makefile =================================================================== RCS file: /home/ncvs/src/games/Makefile,v retrieving revision 1.15 diff -u -d -r1.15 Makefile --- Makefile 1998/08/30 20:58:16 1.15 +++ Makefile 1999/03/02 14:57:30 @@ -2,44 +2,19 @@ # $Id: Makefile,v 1.15 1998/08/30 20:58:16 gpalmer Exp $ # XXX missing: chess ching monop [copyright] -SUBDIR= adventure \ - arithmetic \ - atc \ - backgammon \ - battlestar \ +SUBDIR= \ bcd \ - bs \ caesar \ - canfield \ - cribbage \ - dm \ factor \ - fish \ fortune \ grdc \ - hack \ - hangman \ - larn \ - mille \ morse \ number \ - phantasia \ - piano \ pig \ pom \ ppt \ primes \ - quiz \ - rain \ random \ - robots \ - rogue \ - sail \ - snake \ - trek \ - wargames \ - worm \ - worms \ - wump + \ .include To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 2:19:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 98D7A151C7 for ; Thu, 1 Apr 1999 02:19:23 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id MAA21837; Thu, 1 Apr 1999 12:18:45 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id MAA23134; Thu, 1 Apr 1999 12:18:45 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (IDENT:nBeqyeqrIebNzadm3Jj+EmhJBLZK8W7A@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id MAA23086; Thu, 1 Apr 1999 12:18:35 +0200 (CEST) Message-Id: <199904011018.MAA23086@wurzelausix.cs.uni-sb.de> Date: Thu, 1 Apr 1999 12:18:32 +0200 (CEST) From: Alexander Leidinger Subject: Re: Games To: dcs@newsguy.com Cc: current@freebsd.org, tr49986@rcc.on.ca In-Reply-To: <3702E799.FFBEC314@newsguy.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 Apr, Daniel C. Sobral wrote: > Well, first of all, .profile, .cshrc and signature scripts are > broken in the absense of fortune. If I remember correctly .cshrc contains [ -x /usr/games/fortune ] && ... so this shouldn't be an issue. BTW.: My /usr/games contains nothing (3.1-Stable install, cvsup to current and make world with NOGAMES=YES). The only thing I've noticed is: hack istn't there anymore, but thats expected. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 2:37:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 6335C15318 for ; Thu, 1 Apr 1999 02:37:12 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca43-216.ix.netcom.com [209.111.209.216]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id CAA18577; Thu, 1 Apr 1999 02:36:32 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id CAA52719; Thu, 1 Apr 1999 02:36:14 -0800 (PST) Date: Thu, 1 Apr 1999 02:36:14 -0800 (PST) Message-Id: <199904011036.CAA52719@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: jkh@zippy.cdrom.com Cc: jhay@mikom.csir.co.za, current@FreeBSD.ORG In-reply-to: <7364.922949549@zippy.cdrom.com> (jkh@zippy.cdrom.com) Subject: Re: /var/db/pkg/.mkversion From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: <7364.922949549@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Jordan K. Hubbard" * * Committing /var/db/pkg to mtree was fine, it probably should have been * there to begin with. Sticking things into it outside of pkg_add, * however, is evil. pkg_add "owns" this directory and every time we've * tried to go behind its back, so to speak, we've been raped for it. * The whole mess with XFree68 was a total nightmare and is what happens * when changes like this are made without really thinking things out. The name of the directory where it resides doesn't matter. It's not a package file so the situation is totally different from XFree86. (The only reason pkg_info was affected was because I blindly assumed it will ignore non-directories in /var/db/pkg.) I can easily move it out of /var/db/pkg to some other place. * No more kludges, please. I'm not changing sysinstall and make world * shouldn't be writing into /var/db/pkg either. If you've found it * necessasry to do this, then you've made a mistake just as you did * with XFree86 and need to think about the problem again. The same situation arises whether the version info is in /var/db/pkg or /some/other/place. It has been pointed out many times in the past that we need something to ensure bsd.port.mk can synchronize itself with the rest of the system (simply because there are too many people who cvsup one without the other). The question is, can I ask you to make sysinstall write some kind of version info that can be used by bsd.port.mk to identify the age of the system? The problem is real, we've been bitten too many times in the past (haven't you seen all the "where's fetch -A?" and other more subtle breakages that are caused by ports and system mismatch), and I can solve it with or without your help. It will just be so much easier if you can help me out a little. -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 3:20:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 55EBA14E7A for ; Thu, 1 Apr 1999 03:20:20 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA24626; Thu, 1 Apr 1999 20:20:13 +0900 (JST) Message-ID: <370354DF.7BD4708E@newsguy.com> Date: Thu, 01 Apr 1999 20:13:35 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Alexander Leidinger Cc: current@freebsd.org, tr49986@rcc.on.ca Subject: Re: Games References: <199904011018.MAA23086@wurzelausix.cs.uni-sb.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger wrote: > > On 1 Apr, Daniel C. Sobral wrote: > > > Well, first of all, .profile, .cshrc and signature scripts are > > broken in the absense of fortune. > > If I remember correctly .cshrc contains > [ -x /usr/games/fortune ] && ... > so this shouldn't be an issue. Well, some people seem to be able to survive without fortune, but that's probably the exception to the rule... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 3:29: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id CDCB614F8A; Thu, 1 Apr 1999 03:28:59 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id FAA17165; Thu, 1 Apr 1999 05:28:39 -0600 (CST) Date: Thu, 1 Apr 1999 05:28:39 -0600 From: "Matthew D. Fuller" To: Satoshi - the Wraith - Asami Cc: jkh@zippy.cdrom.com, jhay@mikom.csir.co.za, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion Message-ID: <19990401052839.D11572@futuresouth.com> References: <7364.922949549@zippy.cdrom.com> <199904011036.CAA52719@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199904011036.CAA52719@silvia.hip.berkeley.edu>; from Satoshi - the Wraith - Asami on Thu, Apr 01, 1999 at 02:36:14AM -0800 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Yes, I'm sticking my nose in where it probably doesn't belong and should get chopped off for it. It's a hobby ;] On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me that Satoshi - the Wraith - Asami remarked > > The same situation arises whether the version info is in /var/db/pkg > or /some/other/place. It has been pointed out many times in the past > that we need something to ensure bsd.port.mk can synchronize itself > with the rest of the system (simply because there are too many people > who cvsup one without the other). > > The question is, can I ask you to make sysinstall write some kind of > version info that can be used by bsd.port.mk to identify the age of > the system? This would require a little more work on the 'back' side, but what would be so hard about just checking $Id$ strings around the .mk files? If not for the revision, at least for the date. > The problem is real, we've been bitten too many times in the past > (haven't you seen all the "where's fetch -A?" and other more subtle Well, certainly, it's not always feasible, but I never understood this one in particular. It always seemed like a PERFECT candidate for an OSVERSION (or whatever) bump; certainly the 3.1+ only, since pre-3.1 didn't have the -A (3.1 didn't either, but that would cut out all the complaints from pre-3.1'ers). --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 3:50:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 00F6915028 for ; Thu, 1 Apr 1999 03:50:07 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <2AY77JJP>; Thu, 1 Apr 1999 13:52:10 +0200 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097588@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: "'Daniel C. Sobral'" , Alexander Leidinger Cc: current@freebsd.org, tr49986@rcc.on.ca Subject: RE: Games Date: Thu, 1 Apr 1999 13:46:38 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Daniel C. Sobral [SMTP:dcs@newsguy.com] > Sent: Thursday, April 01, 1999 1:14 PM > To: Alexander Leidinger > Cc: current@freebsd.org; tr49986@rcc.on.ca > Subject: Re: Games > > Alexander Leidinger wrote: > > > > On 1 Apr, Daniel C. Sobral wrote: > > > > > Well, first of all, .profile, .cshrc and signature scripts are > > > broken in the absense of fortune. > > > > If I remember correctly .cshrc contains > > [ -x /usr/games/fortune ] && ... > > so this shouldn't be an issue. > > Well, some people seem to be able to survive without fortune, but > that's probably the exception to the rule... :-) > [ML] Oh, I can live without fortune(6), but pom(6) was invaluable in software malfunction diagnosis: luser: "My program fails when I do this or that." me: "No wonder, the moon is 73% full." /Marino > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "nothing better than the ability to perform cunning linguistics" > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 4: 0:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 8A1E915028 for ; Thu, 1 Apr 1999 04:00:49 -0800 (PST) (envelope-from fanf@demon.net) Received: by noc.demon.net; id NAA08212; Thu, 1 Apr 1999 13:00:28 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xmae08125; Thu, 1 Apr 99 13:00:17 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10Sg8u-0000pi-00; Thu, 1 Apr 1999 13:00:16 +0100 To: current@freebsd.org From: Tony Finch Subject: Re: booting systems with lots of memory In-Reply-To: <199903292003.MAA00525@dingo.cdrom.com> References: <14079.46583.208347.306328@chiark.greenend.org.uk> Message-Id: Date: Thu, 1 Apr 1999 13:00:16 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: >Tony Finch wrote: >[serial console problems] >> We suspect a BIOS that's being too damn clever for its own good. > >That sounds about right. If your BIOS on the Intel box is set for a >serial console, you could try poking it again to make sure that it's set >for 9600 bps and that the various 'magic' options relating to remote >health monitoring are all off. That did turn out to be the problem. The memory has finally followed the box from here to the Docklands and we now have a machine with the following dmesg. We'll be trying it out under load in the near future. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #25: Mon Mar 29 14:38:45 BST 1999 root@discord.news.demon.net:/usr/src/sys/compile/NCRXEON Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x653 Stepping=3 Features=0x183fbff> real memory = 3221225472 (3145728K bytes) avail memory = 3133857792 (3060408K bytes) Programming 64 pins in IOAPIC #0 IOAPIC #0 intpint 38 -> irq 17 IOAPIC #0 intpint 40 -> irq 18 IOAPIC #0 intpint 41 -> irq 15 IOAPIC #0 intpint 42 -> irq 10 IOAPIC #0 intpint 44 -> irq 7 IOAPIC #0 intpint 48 -> irq 11 IOAPIC #0 intpint 49 -> irq 16 IOAPIC #0 intpint 58 -> irq 14 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 3, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu2 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu3 (AP): apic id: 2, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 4, version: 0x003f0013, at 0xfec10000 Preloaded elf kernel "kernel" at 0xc02ea000. Probing for devices on PCI bus 0: ahc0: rev 0x01 int a irq 14 on pci0.10.0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x00 int a irq 11 on pci0.12.0 chip0: rev 0x02 on pci0.15.0 No driver for device 0x71118086 at pci0:15:1 No driver for device 0x71128086 at pci0:15:2 chip1: rev 0x02 on pci0.15.3 chip2: rev 0x03 on pci0.16.0 chip3: rev 0x02 on pci0.18.0 chip4: rev 0x02 on pci0.19.0 chip5: rev 0x02 on pci0.20.0 Probing for devices on PCI bus 1: ahc1: rev 0x00 int a irq 17 on pci1.4.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x04 int a irq 18 on pci1.5.0 fxp0: Ethernet address 00:a0:c9:a4:85:bd chip6: rev 0x03 on pci1.6.0 fpa0: rev 0x01 int a irq 7 on pci1.7.0 fpa0: DEC DEFPA PCI FDDI SAS Controller fpa0: FDDI address 00:00:f8:c9:91:56, FW=3.10, HW=0, SMT V7.2 fpa0: FDDI Port = S (PMD = Unshielded Twisted Pair) No driver for device 0x123d8086 at pci1:9:0 Probing for devices on PCI bus 2: de0: rev 0x22 int a irq 10 on pci2.4.0 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.2 de0: address 00:e0:29:26:53:71 de1: rev 0x22 int a irq 15 on pci2.5.0 de1: SMC 9332BDT 21140A [10-100Mb/s] pass 2.2 de1: address 00:e0:29:26:53:70 Probing for devices on PCI bus 3: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, unlimited logging Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! de0: enabling 10baseT port de1: autosense failed: cable problem? pass2 at ahc0 bus 0 target 6 lun 0 pass2: Fixed Processor SCSI-2 device pass2: 3.300MB/s transfers pass5 at ahc1 bus 0 target 6 lun 0 pass5: Fixed Processor SCSI-2 device pass5: 3.300MB/s transfers da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) da2 at ahc1 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) da3 at ahc1 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (5.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) changing root device to da0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates fpa0: Link Unavailable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 4:20:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id DF0D714C30 for ; Thu, 1 Apr 1999 04:20:09 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca43-216.ix.netcom.com [209.111.209.216]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id EAA18711; Thu, 1 Apr 1999 04:19:42 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id EAA53032; Thu, 1 Apr 1999 04:19:23 -0800 (PST) Date: Thu, 1 Apr 1999 04:19:23 -0800 (PST) Message-Id: <199904011219.EAA53032@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: fullermd@futuresouth.com Cc: jkh@zippy.cdrom.com, jhay@mikom.csir.co.za, current@FreeBSD.ORG In-reply-to: <19990401052839.D11572@futuresouth.com> (fullermd@futuresouth.com) Subject: Re: /var/db/pkg/.mkversion From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: <7364.922949549@zippy.cdrom.com> <199904011036.CAA52719@silvia.hip.berkeley.edu> <19990401052839.D11572@futuresouth.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Matthew D. Fuller" * [ Yes, I'm sticking my nose in where it probably doesn't belong and * should get chopped off for it. It's a hobby ;] Don't worry, I enjoy chopping off noses. :) * On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me * that Satoshi - the Wraith - Asami remarked What birdie? * This would require a little more work on the 'back' side, but what would * be so hard about just checking $Id$ strings around the .mk files? If * not for the revision, at least for the date. Which .mk files? Note that it's not bsd.port.mk's version we need -- we already have that. We need something on the system to compare against. * Well, certainly, it's not always feasible, but I never understood this * one in particular. It always seemed like a PERFECT candidate for an * OSVERSION (or whatever) bump; certainly the 3.1+ only, since pre-3.1 * didn't have the -A (3.1 didn't either, but that would cut out all the * complaints from pre-3.1'ers). That only works if the user recompiled the kernel, since that's where we're getting it from. (Or we can get it from but bsd.port.mk is not a compiler.) -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 4:53: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.132]) by hub.freebsd.org (Postfix) with ESMTP id E20691519D; Thu, 1 Apr 1999 04:52:54 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id GAA03406; Thu, 1 Apr 1999 06:52:35 -0600 (CST) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Thu, 1 Apr 1999 06:52:35 -0600 (CST) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: Satoshi - the Wraith - Asami Cc: jkh@zippy.cdrom.com, jhay@mikom.csir.co.za, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-Reply-To: <199904011036.CAA52719@silvia.hip.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have to agree that the problem is real. However, let me point out that a "one identifier" solution is very short sided. There are two distinct environments to be considered. The HOST environment and the TARGET environment. For convience, we should also consider a TOOLSET environment which is a cross between the two. Just as it is "wrong" to use compiler variables like, "__FreeBSD__" to control target compilations (except as a default), it is also "wrong" to do so for the ports. The group has come around to the idea that the files in /usr/include represent the HOST and not the TARGET. I suggest that you dig out my old proposal for tagging the HOST in /usr/include. The natural tag for the TARGET would be in /usr/src/include. However, I can see some problems with this for the ports tree. The more general mechanism allows us to "register" capabilities. (Shades of some commercial OS'es) However, we may not want to do things in such a unified manner :-) On Thu, 1 Apr 1999, Satoshi - the Wraith - Asami wrote: > It has been pointed out many times in the past > that we need something to ensure bsd.port.mk can synchronize itself > with the rest of the system > > The question is, can I ask you to make sysinstall write some kind of > version info that can be used by bsd.port.mk to identify the age of > the system? > > The problem is real, we've been bitten too many times in the past > (haven't you seen all the "where's fetch -A?" and other more subtle > breakages that are caused by ports and system mismatch) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 5: 0: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 24A5314F10; Thu, 1 Apr 1999 05:00:06 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id HAA05556; Thu, 1 Apr 1999 07:58:07 -0500 (EST) Date: Thu, 1 Apr 1999 07:58:07 -0500 (EST) From: Chuck Robey To: Richard Wackerbarth Cc: Satoshi - the Wraith - Asami , jkh@zippy.cdrom.com, jhay@mikom.csir.co.za, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Apr 1999, Richard Wackerbarth wrote: > I have to agree that the problem is real. > However, let me point out that a "one identifier" solution is > very short sided. > > There are two distinct environments to be considered. > The HOST environment and the TARGET environment. > For convience, we should also consider a TOOLSET > environment which is a cross between the two. > > Just as it is "wrong" to use compiler variables like, > "__FreeBSD__" to control target compilations (except > as a default), it is also "wrong" to do so for the ports. > > The group has come around to the idea that the files in /usr/include > represent the HOST and not the TARGET. > > I suggest that you dig out my old proposal for tagging the HOST in > /usr/include. The natural tag for the TARGET would be in > /usr/src/include. However, I can see some problems with this for > the ports tree. Richard, don't forget that having /usr/src isn't required to build ports. It seems a pretty draconian requirement to add. This is ports we're talking about, and nearly all of ports cannot build (as they are now) in cross-hosted environments. There's 2000 ports to consider, and the fix has to go in soon, not something for 2001. I would not be against changes in strategy for the longer run (and your ideas have merit for that view) but we need a short term fix here. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 5: 3:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from daytona.hkstar.com (daytona.hkstar.com [202.82.3.25]) by hub.freebsd.org (Postfix) with ESMTP id DEE5C14F10 for ; Thu, 1 Apr 1999 05:03:07 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by daytona.hkstar.com (8.9.1/8.9.1) with ESMTP id VAA01432 for ; Thu, 1 Apr 1999 21:02:46 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id VAA16692 for freebsd-current@freebsd.org; Thu, 1 Apr 1999 21:02:45 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199904011302.VAA16692@b1.hkstar.com> Subject: make world fail with ctm src-cur.3809 To: freebsd-current@freebsd.org Date: Thu, 1 Apr 1999 21:02:44 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I tried to update my system with ctm upto src-cur.3809 and found the following error. Can anyone help ? thanks. Clarence ======= Error ======= In file included from /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc:24: /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include/posix.h:25: osfcn.h: No such file or directory /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc: In function `void ewrite(const char *)': /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc:30: warning: implicit declaration of function `int write(...)' *** Error code 1 Stop. ======= Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 5: 9:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id B6F56150D0 for ; Thu, 1 Apr 1999 05:09:24 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca43-216.ix.netcom.com [209.111.209.216]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id FAA18797; Thu, 1 Apr 1999 05:08:57 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id FAA53495; Thu, 1 Apr 1999 05:08:41 -0800 (PST) Date: Thu, 1 Apr 1999 05:08:41 -0800 (PST) Message-Id: <199904011308.FAA53495@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: rkw@dataplex.net Cc: jkh@zippy.cdrom.com, jhay@mikom.csir.co.za, current@FreeBSD.ORG In-reply-to: (message from Richard Wackerbarth on Thu, 1 Apr 1999 06:52:35 -0600 (CST)) Subject: Re: /var/db/pkg/.mkversion From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Richard Wackerbarth * I have to agree that the problem is real. * However, let me point out that a "one identifier" solution is * very short sided. sighted :> * There are two distinct environments to be considered. * The HOST environment and the TARGET environment. * For convience, we should also consider a TOOLSET * environment which is a cross between the two. (Rolling my eyes.) This issue has nothing to do with hosts and targets. The ports tree has never supported building ports on a system with a version other than the one that is going to run it. (And we don't intend to start doing it any time soon either, sorry. ;) -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 5:12:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from newman.cs.purdue.edu (newman.cs.purdue.edu [128.10.2.6]) by hub.freebsd.org (Postfix) with ESMTP id C351215196 for ; Thu, 1 Apr 1999 05:12:36 -0800 (PST) (envelope-from splite@cs.purdue.edu) Received: from bugs.cs.purdue.edu (bugs.cs.purdue.edu [128.10.8.30]) by newman.cs.purdue.edu (8.8.7/8.8.7/PURDUE_CS-2.0) with ESMTP id IAA28205 for ; Thu, 1 Apr 1999 08:12:16 -0500 (EST) Received: (from splite@localhost) by bugs.cs.purdue.edu (8.8.7/8.8.7/PURDUE_CS-2.0) id IAA04851 for freebsd-current@FreeBSD.ORG; Thu, 1 Apr 1999 08:12:18 -0500 (EST) Date: Thu, 1 Apr 1999 08:12:18 -0500 From: Steven Plite To: freebsd-current@FreeBSD.ORG Subject: Re: AIC Message-ID: <19990401081218.A4803@bugs.cs.purdue.edu> References: <3702E01B.75465F21@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3702E01B.75465F21@newsguy.com>; from Daniel C. Sobral on Thu, Apr 01, 1999 at 11:55:23AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 01, 1999 at 11:55:23AM +0900, Daniel C. Sobral wrote: > Brian Beattie wrote: > > > > > writing it would be a pain) because the only pccard scsi cards that are > > > out there are aic-6[23]60 based. > > > > Not having a pcmcia slot or card, I am not sure about support for this. > > Once aic6[23]60 is working, the PCMCIA stuff is easily done. > > > > However, the sad fact is that the development is less than active on this > > > driver. > > > > It is a fact, sad? Im not sure. except for the pccard stuff there is much > > better stuff than the 6x60 based hardware. > > But there are *no* alternatives for notebooks, except parallel port > SCSI. This isn't true. The 3.0 version of Newtek's Bus Toaster uses a Symbios 53C500 chip. I think Newtek still makes them... Granted, we don't have a driver for that controller either, but the programming manual is readily available from LSI Logic. Seems to me that NetBSD has a driver for it, based on a Linux driver. (Been a while since I looked into it, so I may be misremembering.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 5:13:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 4E16C150D0 for ; Thu, 1 Apr 1999 05:13:29 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id HAA14746 for current@freebsd.org; Thu, 1 Apr 1999 07:57:10 -0500 (EST) From: Mikhail Teterin Message-Id: <199904011257.HAA14746@kot.ne.mediaone.net> Subject: latest bsd.port.mk and FETCH_CMD To: current@freebsd.org Date: Thu, 1 Apr 1999 07:57:10 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Reply-To: rkw@dataplex.net To: Chuck Robey Cc: Satoshi - the Wraith - Asami , jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Apr 1999, Chuck Robey wrote: > On Thu, 1 Apr 1999, Richard Wackerbarth wrote: > > > The natural tag for the TARGET would be in > > /usr/src/include. However, I can see some problems with this for > > the ports tree. > > Richard, don't forget that having /usr/src isn't required to build > ports. I don't think that I did forget. I explicitly reference that situation. The real solution (re the TARGET) has to depend on something that the USER sets for a particular "run". As such, it should be an environment variable which defaults to the HOST value. At the same time, the ports have to consider the purpose for which they need the identification. For example, "fetch -A" is a HOST/TOOLSET situation. But selecting the set of sysctls to compile into the code is a TARGET question. Nobody said cross compilation is easy :-) The "simple" solution for ports may be to build 3.1 packages on 3.1 machines and 4.0 packages only on 4.0 systems. In that case, TARGET == HOST and things are much easier. I still see nothing wrong with /usr/include for a place to store a tag about the HOST. Alternately, the traditional place would be /etc. The format of the tag should be considered. IMHO, it is best if we can have one knob which works for make, sh, and cc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 5:30:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 0B35615095 for ; Thu, 1 Apr 1999 05:30:42 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca43-216.ix.netcom.com [209.111.209.216]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id FAA18830; Thu, 1 Apr 1999 05:30:33 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id FAA53603; Thu, 1 Apr 1999 05:30:19 -0800 (PST) Date: Thu, 1 Apr 1999 05:30:19 -0800 (PST) Message-Id: <199904011330.FAA53603@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: mi@kot.ne.mediaone.net Cc: current@freebsd.org In-reply-to: <199904011257.HAA14746@kot.ne.mediaone.net> (message from Mikhail Teterin on Thu, 1 Apr 1999 07:57:10 -0500 (EST)) Subject: Re: latest bsd.port.mk and FETCH_CMD From: asami@freebsd.org (Satoshi - the Wraith - Asami) References: <199904011257.HAA14746@kot.ne.mediaone.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Mikhail Teterin * With the latest changes to the bsd.port.mk, my local setting (in * /etc/make.conf) of: * FETCH_CMD=/usr/local/bin/runsocks /usr/bin/fetch -p * is ignored. It uses the default /usr/bin/fetch, which does nto work * for me... That's weird. The only change around that area was to add a comment. FETCH_CMD is still defined with a "?=", so your make.conf should take precedence. -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 5:41:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from woodstock.monkey.net (mercury-2-131.mdm.mkt.execpc.com [169.207.86.196]) by hub.freebsd.org (Postfix) with ESMTP id 3EC3A15D75; Thu, 1 Apr 1999 05:41:20 -0800 (PST) (envelope-from hamilton@pobox.com) Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 7E7203E; Thu, 1 Apr 1999 07:40:54 -0600 (CST) To: "Matthew D. Fuller" Cc: Satoshi - the Wraith - Asami , jkh@zippy.cdrom.com, jhay@mikom.csir.co.za, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-reply-to: Your message of "Thu, 01 Apr 1999 05:28:39 CST." <19990401052839.D11572@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Apr 1999 07:40:54 -0600 From: Jon Hamilton Message-Id: <19990401134054.7E7203E@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990401052839.D11572@futuresouth.com>, "Matthew D. Fuller" wrote: } [ Yes, I'm sticking my nose in where it probably doesn't belong and } should get chopped off for it. It's a hobby ;] } } On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told me } that Satoshi - the Wraith - Asami remarked } > } > The same situation arises whether the version info is in /var/db/pkg } > or /some/other/place. It has been pointed out many times in the past } > that we need something to ensure bsd.port.mk can synchronize itself } > with the rest of the system (simply because there are too many people } > who cvsup one without the other). } > } > The question is, can I ask you to make sysinstall write some kind of } > version info that can be used by bsd.port.mk to identify the age of } > the system? } } This would require a little more work on the 'back' side, but what would } be so hard about just checking $Id$ strings around the .mk files? If } not for the revision, at least for the date. I think that's asking for trouble - it'll lose if someone keeps their .mk files in their own RCS (I do this for some files; admittedly not for the .mk files, but I could see someone doing that). -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 5:45:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.132]) by hub.freebsd.org (Postfix) with ESMTP id 20EA915DA4; Thu, 1 Apr 1999 05:45:48 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id HAA03612; Thu, 1 Apr 1999 07:45:29 -0600 (CST) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Thu, 1 Apr 1999 07:45:29 -0600 (CST) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: Satoshi - the Wraith - Asami Cc: current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-Reply-To: <199904011308.FAA53495@silvia.hip.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Apr 1999, Satoshi - the Wraith - Asami wrote: > * From: Richard Wackerbarth > * very short sided. > sighted :> Yes, a slight transfer error between my brain and 'sendmail'. > * There are two distinct environments to be considered. > * The HOST environment and the TARGET environment. > This issue has nothing to do with hosts and targets. The ports tree > has never supported building ports on a system with a version other > than the one that is going to run it. (And we don't intend to start > doing it any time soon either, sorry. ;) I recognize that. However, I bring it up because there are a number of programmers who still fail to recognize the distinction. I hope that we can get the rest (non-ports) of the build system into shape. Any "solution" for the ports should be one that also works elsewhere. As a result, I would hate to see yet another inadequate mechanism become entrenched. I don't think that "ports" ever stands a real chance in making it to cross compilation because too many of the components rely on autoconf style configuration. This often trys to decide which representation to use by "trial and error". It is virtually impossible for "you" to police all those ports authors and have them maintain cross-compile compliance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 7:44:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.intercom.com (mail.intercom.com [206.98.165.10]) by hub.freebsd.org (Postfix) with ESMTP id 6F7D614F12 for ; Thu, 1 Apr 1999 07:44:15 -0800 (PST) (envelope-from jason@intercom.com) Received: from mail.intercom.com (mail.intercom.com [206.98.165.10]) by mail.intercom.com (8.9.0/8.9.0) with ESMTP id KAA06701; Thu, 1 Apr 1999 10:43:51 -0500 (EST) Date: Thu, 1 Apr 1999 10:43:51 -0500 (EST) From: "Jason J. Horton" To: Rod Taylor Cc: current@FreeBSD.ORG Subject: Re: Games In-Reply-To: <370308C1.9B908465@rcc.on.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Apr 1999, Rod Taylor wrote: > Just out of curiosity, why are there games included in the FreeBSD > source tree? > > For a group of people that was so worried about including dhcp because > it's extra code, don't you think it's time to make those games into > ports only? > > I say this under the assumption that they're not required for FreeBSD to > function. (Not like IE for windows ;) As far as I am concerned, things like fortune, pom, pig and banner have been included with BSD-ish systems for ages... Tradition... I wouldn't feel the same if I didn't get my fortune every login. also, don't you have the option to not have the games? -Jason J. Horton Senior Network & Systems Engineer Intercom Online Inc. 212.378.2202 | http://www.intercom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 8:30:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4E2E214E3E for ; Thu, 1 Apr 1999 08:30:48 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10SkM2-0000PK-00; Thu, 1 Apr 1999 18:30:06 +0200 From: Sheldon Hearn To: "Jason J. Horton" Cc: Rod Taylor , current@FreeBSD.ORG Subject: Re: Games In-reply-to: Your message of "Thu, 01 Apr 1999 10:43:51 EST." Date: Thu, 01 Apr 1999 18:30:06 +0200 Message-ID: <1569.922984206@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 01 Apr 1999 10:43:51 EST, "Jason J. Horton" wrote: > also, don't you have the option to not have the games? The problem with NOGAMES is that it strips things that some people consider "useful". The diffs I posted earlier today (same subject line) rip out the "games" and leave behind the "utilities", where words in quotes are subjective matters, and hence not worth discussing. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 9:27:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B3325154D8 for ; Thu, 1 Apr 1999 09:27:24 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA28799; Fri, 2 Apr 1999 02:27:19 +0900 (JST) Message-ID: <3703A923.7F5810EF@newsguy.com> Date: Fri, 02 Apr 1999 02:13:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Steven Plite Cc: freebsd-current@FreeBSD.ORG Subject: Re: AIC References: <3702E01B.75465F21@newsguy.com> <19990401081218.A4803@bugs.cs.purdue.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steven Plite wrote: > > > But there are *no* alternatives for notebooks, except parallel port > > SCSI. > > This isn't true. The 3.0 version of Newtek's Bus Toaster uses a Symbios > 53C500 chip. I think Newtek still makes them... I meant that there are no alternatives available in 3.x. > Granted, we don't have a driver for that controller either, but the > programming manual is readily available from LSI Logic. Seems to me that > NetBSD has a driver for it, based on a Linux driver. (Been a while since > I looked into it, so I may be misremembering.) It seems programming manuals for the AIC 6[23]60 are also available, and there is even a FreeBSD driver for it... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 9:33:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 88606152BD for ; Thu, 1 Apr 1999 09:33:26 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA29198; Fri, 2 Apr 1999 02:32:59 +0900 (JST) Message-ID: <3703AC7A.F740BF26@newsguy.com> Date: Fri, 02 Apr 1999 02:27:22 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Sheldon Hearn Cc: "Jason J. Horton" , Rod Taylor , current@FreeBSD.ORG Subject: Re: Games References: <1569.922984206@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Thu, 01 Apr 1999 10:43:51 EST, "Jason J. Horton" wrote: > > > also, don't you have the option to not have the games? > > The problem with NOGAMES is that it strips things that some people > consider "useful". The diffs I posted earlier today (same subject line) > rip out the "games" and leave behind the "utilities", where words in > quotes are subjective matters, and hence not worth discussing. You stripped DM, which has it's uses. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 9:49:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id F264E14BFF; Thu, 1 Apr 1999 09:48:59 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id MAA06310; Thu, 1 Apr 1999 12:47:08 -0500 (EST) Date: Thu, 1 Apr 1999 12:47:08 -0500 (EST) From: Chuck Robey To: Richard Wackerbarth Cc: Satoshi - the Wraith - Asami , jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Apr 1999, Richard Wackerbarth wrote: > > Richard, don't forget that having /usr/src isn't required to build > > ports. > > I don't think that I did forget. I explicitly reference that situation. > > The real solution (re the TARGET) has to depend on something that the USER > sets for a particular "run". As such, it should be an environment variable > which defaults to the HOST value. > > At the same time, the ports have to consider the purpose for which they > need the identification. For example, "fetch -A" is a HOST/TOOLSET > situation. But selecting the set of sysctls to compile into the > code is a TARGET question. Nobody said cross compilation is easy :-) Well, seeing as FreeBSD doesn't have control over the software involved, and nearly all the software involved is broken for the kind of portability you're talking about, this seems unreasonable. It's one thing for ports to adapt a particular piece of software to run on FreeBSD hosts, it's quite a different thing to make it cross-build, any to any. That would convert doing a port from being a reasonably short job, to being (for each port) a major rewrite project. Seeing the extreme fluidity of many ports, and the large number of ports, this sounds like a very unreal expectation. Your statement "Nobody said cross compilation is easy :-)", well, the work involved is huge, and the demand ... huh, you're the ONLY one to demand it. OK, maybe even "demand" is wrong, but you get the idea, that it's a lot of work for something that isn't seen as necessary. If you were talking about the FreeBSD sources themselves, everything I said is out the window, because we *do* have total control of those, and the change rate is under our purview. For ports, with that outside our control, and no established need, it seems excessive. Go adapt one of the gnome things, see how long it takes you to do *one* port with the features you seem to be requiring. If it's less than what I envision, perhaps you're getting what you want over badly, and seeing a port done as you want would be instructive to the rest of us. I think you're going to spend a *lot* of time doing that one port. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 10:26:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id C880715631 for ; Thu, 1 Apr 1999 10:26:20 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id NAA21765; Thu, 1 Apr 1999 13:25:24 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id NAA21302; Thu, 1 Apr 1999 13:25:24 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1569.922984206@axl.noc.iafrica.com> Date: Thu, 01 Apr 1999 13:25:23 -0500 (EST) From: John Baldwin To: Sheldon Hearn Subject: Re: Games Cc: current@FreeBSD.ORG, Rod Taylor , "Jason J. Horton" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01-Apr-99 Sheldon Hearn wrote: > > > On Thu, 01 Apr 1999 10:43:51 EST, "Jason J. Horton" wrote: > >> also, don't you have the option to not have the games? > > The problem with NOGAMES is that it strips things that some people > consider "useful". The diffs I posted earlier today (same subject line) > rip out the "games" and leave behind the "utilities", where words in > quotes are subjective matters, and hence not worth discussing. They aren't exactly huge either, my /usr/obj/usr/src/games only has 4 Meg in it, and that's including all the object files in addition to the executables. > Ciao, > Sheldon. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 10:40:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.nobell.com [216.140.184.67]) by hub.freebsd.org (Postfix) with ESMTP id B0D5F15183; Thu, 1 Apr 1999 10:40:19 -0800 (PST) (envelope-from root@dataplex.net) Received: from localhost (root@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id MAA00914; Thu, 1 Apr 1999 12:39:50 -0600 (CST) (envelope-from root@dataplex.net) Date: Thu, 1 Apr 1999 12:39:50 -0600 (CST) From: Charlie ROOT Reply-To: rkw@dataplex.net To: Chuck Robey Cc: Richard Wackerbarth , Satoshi - the Wraith - Asami , jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Apr 1999, Chuck Robey wrote: > On Thu, 1 Apr 1999, Richard Wackerbarth wrote: > Your statement "Nobody said cross compilation is easy :-)" By this smiley, I mean to infer that it is far from easy. > you're the ONLY one to demand it. OK, maybe even "demand" is wrong > If you were talking about the FreeBSD sources themselves, everything I > said is out the window, because we *do* have total control I think that you have missed the entire point of what I am advocating. Within the ports Makefiles (and .mk), we DO have control. We SHOULD make certain that we do NOT REPEAT the past errors of using the wrong parameter when we CAN do it correctly. IOW, don't box the future development in by building a mechanism which works ONLY if HOST == TARGET. Provide a mechanism which can provide TARGET independent from HOST, but defaulting to the same value. In the code which we write for the FreeBSD tree, including /usr/ports, use the correct context. I ask this because the mechanism for ports SHOULD be the same mechanism that is used for OS builds. In the realm of OS building, I think that we are making progress toward cross build capability. I would hate to see this thing for ports be a step backward. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 10:46:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.flyingcroc.com (gilliam.flyingcroc.com [204.157.104.160]) by hub.freebsd.org (Postfix) with ESMTP id C369F15183; Thu, 1 Apr 1999 10:46:35 -0800 (PST) (envelope-from prez@flyingcroc.com) Received: from mail.flyingcroc.com (mail.flyingcroc.com [204.157.104.152]) by gilliam.flyingcroc.com (8.9.1a/8.9.1) with ESMTP id KAA09859; Thu, 1 Apr 1999 10:46:15 -0800 (PST) Date: Thu, 1 Apr 1999 10:46:15 -0800 (PST) From: "Andrew N. Edmond (Nero)" Reply-To: "Andrew Edmond (Chief Executive Officer)" To: questions@freebsd.org, current@freebsd.org Cc: Network Ops Center Subject: Adaptec 3950U2B Ver 2.11.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Our hardware vendor, in an effort to save us PCI slot space, fitted us with a new 3950U2B instead of the old 3940 (no longer in production!) cards we were used to. All documents on FreeBSD.org say that FreeBSD 3.1 supports this card. However, /stand/sysinstall refuses to see it when I try to mount drives on the card. What's the status of the 3950U2B CAM driver? -- andy edmond > After trying 3.1-REL, 3.1-STABLE and 3.0-REL it still won't see the > second scsi card. I've built it with 3.1-REL on just the 4gb drive > and will poke around in the mail lists and kernal configs to see if I > can find a magic switch. > > sshd is running on it if you want to take a crack at it. The card is > an Adaptec 3950U2B Ver 2.11.0 and is set for 80Mby transfer with 2 > 18Gby drives. > > The transfer of the Frontier feed to f0/0/0 took only about 3 minutes. > The graphs show longer because I did the mrtg config changes after a > smoke. > > It's 5:00AM now, I'm going home to get some more sleep and will be in > this afternoon. > > -Joe > > *----------------------------------------------------------------------* > | Joe Hamelin | joe@nethead.com & http://www.nethead.com | > | Seattle WA USA | Without love in the dream it will never come true. | > *----------------------------------------------------------------------* > -------------------------------------------------------------------------- Andrew N. Edmond S E X Chief Executive Officer president@sextracker.com T R A C K E R http://www.sextracker.com -------------------------------------------------------------------------- GET PAID BY SEXTRACKER! WINDOWS 95/98/NT STATISTICS http://moneytree.sextracker.com/ http://executive.sextracker.com/ BANNER EXCHANGE RANKS! DOWNLOAD SUPERBROWSER TODAY! http://stx.sextracker.com/ http://superbrowser.sextracker.com/ FREE CHAT FOR YOUR ADULT WEBSITE http://chatnet.sextracker.com/ FREE WEB HOSTING TODAY! http://www.sexspaces.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 11: 1:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E4CCB14E5B for ; Thu, 1 Apr 1999 11:01:28 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA14880; Thu, 1 Apr 1999 11:01:09 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id LAA23984; Thu, 1 Apr 1999 11:01:08 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 1 Apr 1999 11:01:08 -0800 (PST) Message-Id: <199904011901.LAA23984@vashon.polstra.com> To: nnd@itfs.nsk.su Subject: Dates off by 1 year (was: Fools Day Joke ?) In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Nickolay Dudorov wrote: > There is some strangenes in date on file > ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/cvs-cur/cvs-cur.5198.gz > > -r--r--r- 1 603 207 49741 apr 1 1998 cvs-cur.5198.gz I changed the subject because I think this may actually be a real bug somewhere. I happened to notice 2 days ago that some of the files in etinc's download area had dates exactly one year too old in this same way. I mentioned it to Dennis there, and he told me that the files had been created by a 2.2.7 machine onto a directory mounted via NFS from a 3.1 machine. The dates are set correctly on both machines, but the problem is reproduceable there. I haven't been able to duplicate it myself, but I suspect that it's a real bug. If anybody else is seeing similar problems, please speak up. And no, this message is not an April Fools joke. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 11:58:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id B9820151A4; Thu, 1 Apr 1999 11:58:11 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA261394577; Thu, 1 Apr 1999 14:22:58 -0500 Date: Thu, 1 Apr 1999 14:22:57 -0500 (EST) From: Bill Fumerola To: "Jordan K. Hubbard" Cc: John Hay , Satoshi Asami , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-Reply-To: <7322.922949191@zippy.cdrom.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 31 Mar 1999, Jordan K. Hubbard wrote: > I think this entire thing is a massive botch and needs to be removed > as a bad idea ASAP. I think that's jumping to conclusions a little too quickly. Jordan, we are eliminating a LOT more future PRs and FAQs by using this method. A few permission and installation oversights (no software can ever be tested on every possible instance.) should not constitute removal of the whole idea. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 12:29:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 5496D150D8 for ; Thu, 1 Apr 1999 12:29:30 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id OAA51913; Thu, 1 Apr 1999 14:28:55 -0600 (CST) Date: Thu, 1 Apr 1999 14:28:55 -0600 From: Dan Nelson To: John Polstra Cc: nnd@itfs.nsk.su, current@FreeBSD.ORG Subject: Re: Dates off by 1 year (was: Fools Day Joke ?) Message-ID: <19990401142855.A51574@dan.emsphone.com> References: <199904011901.LAA23984@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199904011901.LAA23984@vashon.polstra.com>; from "John Polstra" on Thu Apr 1 11:01:08 GMT 1999 X-OS: FreeBSD 3.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Apr 01), John Polstra said: > In article , Nickolay Dudorov wrote: > > There is some strangenes in date on file > > ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/cvs-cur/cvs-cur.5198.gz > > > > -r--r--r- 1 603 207 49741 apr 1 1998 cvs-cur.5198.gz > > I changed the subject because I think this may actually be a real bug > somewhere. I happened to notice 2 days ago that some of the files in > etinc's download area had dates exactly one year too old in this same > way. I mentioned it to Dennis there, and he told me that the files > had been created by a 2.2.7 machine onto a directory mounted via NFS > from a 3.1 machine. The dates are set correctly on both machines, > but the problem is reproduceable there. > > I haven't been able to duplicate it myself, but I suspect that it's a > real bug. If anybody else is seeing similar problems, please speak > up. I've seen this too, on other FTP servers. I doubt it's an NFS problem, since there is no reason for NFS to add/subtract exactly one year from the date. FTP, on the other hand, doesn't have a standard way of passing a date to the client (MDTM isn't always implemented). I can imagine an FTP client (especially NcFTP which parses the LIST command itself) getting confused about a file that was created a couple hours in the "future" , due to the fact that FTP servers work in the local timezone, but FTP client's cant easily determine the timezone of the server. aha! I just tested this, with stock 3.1 /usr/bin/ftp and with NcFTP3.0b18. I touched a file with a date four hours into the future, connected to my FTP server, and tried to list it: ftp> dir asdf 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. -rw-rw-r-- 1 dan 1000 0 Apr 1 22:00 asdf 226 Transfer complete. ftp> ncftp /pub > dir asdf -rw-rw-r-- 1 dan 1000 0 Apr 1 1998 asdf ncftp /pub > So I'd say it's a bug in NcFTP's date parser. I'm willing to bet that Nickolay is also using NcFTP, since the 'group' column in his 'ls' output is right-justified, just like my ncftp output sample :) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 12:41:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 785F114E3A for ; Thu, 1 Apr 1999 12:41:34 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id MAA15322; Thu, 1 Apr 1999 12:41:02 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id MAA27807; Thu, 1 Apr 1999 12:41:02 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990401142855.A51574@dan.emsphone.com> Date: Thu, 01 Apr 1999 12:41:02 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Dan Nelson Subject: Re: Dates off by 1 year (was: Fools Day Joke ?) Cc: current@FreeBSD.ORG, nnd@itfs.nsk.su Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > I've seen this too, on other FTP servers. I doubt it's an NFS problem, > since there is no reason for NFS to add/subtract exactly one year from > the date. ... > So I'd say it's a bug in NcFTP's date parser. Bingo! It looks like you're right. I noticed that the file's time was later than the current time, too (disregarding the year). > I'm willing to bet that Nickolay is also using NcFTP I don't doubt that. But for me it happened using Netscape. Thanks for solving this mystery! John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 12:56:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id CF67114C7F for ; Thu, 1 Apr 1999 12:56:56 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id OAA12077; Thu, 1 Apr 1999 14:56:06 -0600 (CST) From: Kevin Day Message-Id: <199904012056.OAA12077@home.dragondata.com> Subject: Re: Games In-Reply-To: from "Jason J. Horton" at "Apr 1, 1999 10:43:51 am" To: jason@intercom.com (Jason J. Horton) Date: Thu, 1 Apr 1999 14:56:06 -0600 (CST) Cc: tr49986@rcc.on.ca, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 1 Apr 1999, Rod Taylor wrote: > > Just out of curiosity, why are there games included in the FreeBSD > > source tree? > > > > For a group of people that was so worried about including dhcp because > > it's extra code, don't you think it's time to make those games into > > ports only? > > > > I say this under the assumption that they're not required for FreeBSD to > > function. (Not like IE for windows ;) > > As far as I am concerned, things like fortune, pom, pig and banner > have been included with BSD-ish systems for ages... Tradition... > I wouldn't feel the same if I didn't get my fortune every login. > > also, don't you have the option to not have the games? It's not just a matter of turning them off though. A few of the games in the distro are trademark infringements. While the product I'm developing that uses FreeBSD doesn't have the games installed, it brought up the comment from our lawyers "What else are they infringing on that we *are* using?" (see trek, mille, boggle, tetris, wargames) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 13:51:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C56B14CA4; Thu, 1 Apr 1999 13:51:51 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id OAA04652; Thu, 1 Apr 1999 14:51:18 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199904012151.OAA04652@panzer.plutotech.com> Subject: Re: Adaptec 3950U2B Ver 2.11.0 In-Reply-To: from "Andrew N. Edmond (Nero)" at "Apr 1, 1999 10:46:15 am" To: president@sextracker.com Date: Thu, 1 Apr 1999 14:51:17 -0700 (MST) Cc: questions@FreeBSD.ORG, current@FreeBSD.ORG, noc@nethead.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew N. Edmond (Nero) wrote... > Our hardware vendor, in an effort to save us PCI slot space, fitted us > with a new 3950U2B instead of the old 3940 (no longer in production!) > cards we were used to. All documents on FreeBSD.org say that FreeBSD 3.1 > supports this card. However, /stand/sysinstall refuses to see it when I > try to mount drives on the card. What's the status of the 3950U2B CAM > driver? Well, the 3950 *is* supported, if you get one of the newer 3.1-STABLE or 4.0-CURRENT snapshots. I know this for a fact, since Justin used my 3950U2 to get things working a couple of weeks ago: ahc0: rev 0x00 int a irq 12 on pci0.10.0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 12 on pci0.10.1 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs He checked support for that card into -stable on March 22nd/23rd, in revision 1.5.2.3 of sys/pci/ahc_pci.c, and revision 1.16.2.4 of sys/dev/aic7xxx/aic7xxx.c. The reason that the 3.1 release notes say that the 3950 is supported is that Justin has a prerelease 3950 board that works just fine. But, as it turns out, they changed the PCI ID and some of the features for the "real" 3950, so the kernel wouldn't recognize it. (for instance, his prerelease board has external SRAM, but my production 3950U2 does not) Anyway, you should be able to get things working if you get one of the post-March 23rd snapshots from here: ftp://releng3.FreeBSD.ORG/pub/FreeBSD/snapshots/i386 The board seems to work fine for me, but I've only got 4 narrow 2gig Seagate Hawks on it, so I'm hardly pushing it. > > After trying 3.1-REL, 3.1-STABLE and 3.0-REL it still won't see the > > second scsi card. I've built it with 3.1-REL on just the 4gb drive > > and will poke around in the mail lists and kernal configs to see if I > > can find a magic switch. > > > > sshd is running on it if you want to take a crack at it. The card is > > an Adaptec 3950U2B Ver 2.11.0 and is set for 80Mby transfer with 2 > > 18Gby drives. > > > > The transfer of the Frontier feed to f0/0/0 took only about 3 minutes. > > The graphs show longer because I did the mrtg config changes after a > > smoke. > > > > It's 5:00AM now, I'm going home to get some more sleep and will be in > > this afternoon. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 14:54:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5D23D155B2 for ; Thu, 1 Apr 1999 14:54:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA60185; Thu, 1 Apr 1999 14:53:46 -0800 (PST) (envelope-from dillon) Date: Thu, 1 Apr 1999 14:53:46 -0800 (PST) From: Matthew Dillon Message-Id: <199904012253.OAA60185@apollo.backplane.com> To: Kevin Day Cc: jason@intercom.com (Jason J. Horton), tr49986@rcc.on.ca, current@FreeBSD.ORG Subject: Re: Games References: <199904012056.OAA12077@home.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It's not just a matter of turning them off though. A few of the games in the :distro are trademark infringements. While the product I'm developing that :uses FreeBSD doesn't have the games installed, it brought up the comment :from our lawyers "What else are they infringing on that we *are* using?" : :(see trek, mille, boggle, tetris, wargames) : :Kevin Tetris hasn't been in the distribution for a while. Your lawyers need a dose of reality if they think the existance of the other games in a distribution could ever come back to haunt you or your company. Tell them to screw their heads on straight and try again. If your really worried, just delete them. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 15: 3:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 0EC8915189 for ; Thu, 1 Apr 1999 15:03:12 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id RAA04277; Thu, 1 Apr 1999 17:02:39 -0600 (CST) From: Kevin Day Message-Id: <199904012302.RAA04277@home.dragondata.com> Subject: Re: Games In-Reply-To: <199904012253.OAA60185@apollo.backplane.com> from Matthew Dillon at "Apr 1, 1999 2:53:46 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 1 Apr 1999 17:02:38 -0600 (CST) Cc: jason@intercom.com, tr49986@rcc.on.ca, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :It's not just a matter of turning them off though. A few of the games in the > :distro are trademark infringements. While the product I'm developing that > :uses FreeBSD doesn't have the games installed, it brought up the comment > :from our lawyers "What else are they infringing on that we *are* using?" > : > :(see trek, mille, boggle, tetris, wargames) > : > :Kevin > > Tetris hasn't been in the distribution for a while. > Oops, i did an 'ls /usr/games' on a machine that's been around since 2.2.2. Ok, forget tetris. > Your lawyers need a dose of reality if they think the existance of > the other games in a distribution could ever come back to haunt you > or your company. Tell them to screw their heads on straight and try > again. If your really worried, just delete them. > That wasn't really the issue though. It's that FreeBSD is infringing on trademarks in the games distribution, so what's to make them think that the vm system isn't an infringement? (i.e. "They're the type of people who don't care about trademarks/copyrights. How can we trust this code?") It also probably doesn't help things that i'm working for a video game company. /usr/games is deleted here, anyway. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 18:20:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from poo.smooch (ts08-059.dublin.indigo.ie [194.125.205.189]) by hub.freebsd.org (Postfix) with ESMTP id EA7CD15245 for ; Thu, 1 Apr 1999 18:20:30 -0800 (PST) (envelope-from blokey@indigo.ie) Received: (from plop@localhost) by poo.smooch (8.9.2/8.9.1) id DAA14368 for current@freebsd.org; Fri, 2 Apr 1999 03:20:06 +0100 (IST) (envelope-from plop) Message-ID: <19990402032005.A14355@smooch> Date: Fri, 2 Apr 1999 03:20:05 +0100 From: Smelly Pooh To: current@freebsd.org Subject: WORM & CAM CD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has the worm driver been taken out of current? If so does the CAM CD driver handle ATAPI CD-Rs or what is the new way of doing it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 18:23:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (Postfix) with ESMTP id 58E2615245; Thu, 1 Apr 1999 18:23:22 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: (from nugundam@localhost) by shell2.la.best.com (8.9.3/8.9.2/best.sh) id SAA07998; Thu, 1 Apr 1999 18:22:48 -0800 (PST) Message-ID: <19990401182248.A7359@la.best.com> Date: Thu, 1 Apr 1999 18:22:48 -0800 From: "Joseph T. Lee" To: freebsd-current@freebsd.org Cc: freebsd-doc@freebsd.org Subject: Re: Handbook DocBook cutover complete References: <19990329122223.D14492@lehman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brian Feldman on Mon, Mar 29, 1999 at 06:34:27AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 29, 1999 at 06:34:27AM -0500, Brian Feldman wrote: > Doc is a nice format, but it's not hypertext. Check out > ports/palm/pilot_makedoc TealDoc's version supports graphics and links. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 18:41:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C4BB615329; Thu, 1 Apr 1999 18:41:04 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA79964; Thu, 1 Apr 1999 21:40:50 -0500 (EST) Date: Thu, 1 Apr 1999 21:40:43 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Joseph T. Lee" Cc: freebsd-current@FreeBSD.ORG, freebsd-doc@FreeBSD.ORG Subject: Re: Handbook DocBook cutover complete In-Reply-To: <19990401182248.A7359@la.best.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Apr 1999, Joseph T. Lee wrote: > On Mon, Mar 29, 1999 at 06:34:27AM -0500, Brian Feldman wrote: > > Doc is a nice format, but it's not hypertext. Check out > > ports/palm/pilot_makedoc > > TealDoc's version supports graphics and links. Is it a published format, though? I know TealDoc is $$$, but the format must be open for it to be worth it to us Palm users. > > -- > Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ > # Anime Expo 1998 >> www.anime-expo.org/ > > # Redline Games >> www.redlinegames.com/ > > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > > # EX: The Online World of Anime & Manga >> www.ex.org/ / > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 20:14:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 85B6C15D3E for ; Thu, 1 Apr 1999 20:14:26 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id VAA06640; Thu, 1 Apr 1999 21:14:01 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199904020414.VAA06640@panzer.plutotech.com> Subject: Re: WORM & CAM CD In-Reply-To: <19990402032005.A14355@smooch> from Smelly Pooh at "Apr 2, 1999 3:20: 5 am" To: blokey@indigo.ie (Smelly Pooh) Date: Thu, 1 Apr 1999 21:14:01 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Smelly Pooh wrote... > Has the worm driver been taken out of current? Yes. You have to use cdrecord now for SCSI CD burners. > If so does the CAM CD driver > handle ATAPI CD-Rs or what is the new way of doing it? No, you need to use the IDE/ATAPI CDROM driver. wormcontrol will talk to that driver. Ask Soren Schmidt if you want more information on it.. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 20:57:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.nwnexus.com (smtp04.nwnexus.com [206.63.63.52]) by hub.freebsd.org (Postfix) with ESMTP id 8584C14DAA; Thu, 1 Apr 1999 20:57:22 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx100-ip34.nwnexus.net [204.57.235.34]) by smtp04.nwnexus.com (8.8.8/8.8.8) with ESMTP id UAA13236; Thu, 1 Apr 1999 20:56:59 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.2/8.8.8) id UAA02429; Thu, 1 Apr 1999 20:53:48 -0800 (PST) (envelope-from wrsomsky) Date: Thu, 1 Apr 1999 20:53:48 -0800 From: "William R. Somsky" To: Bill Fumerola Cc: "Jordan K. Hubbard" , John Hay , Satoshi Asami , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion Message-ID: <19990401205348.A2406@gramarye.halcyon.com> References: <7322.922949191@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Bill Fumerola on Thu, Apr 01, 1999 at 02:22:57PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 01, 1999 at 02:22:57PM -0500, Bill Fumerola wrote: > On Wed, 31 Mar 1999, Jordan K. Hubbard wrote: > > > I think this entire thing is a massive botch and needs to be removed > > as a bad idea ASAP. > > I think that's jumping to conclusions a little too quickly. > > Jordan, we are eliminating a LOT more future PRs and FAQs by using this > method. A few permission and installation oversights (no software can ever > be tested on every possible instance.) should not constitute removal of > the whole idea. At minimum, the implementation is off... What /var/db/pkg/.mkversion is tracking w/ the current implementation it the date of the last _installation_ of the make files... Wouldn't just a "MKPKG_VERSION=xxyyzz" inside of the relevant make file work easier? What's _really_ trying to be accomplished w/ .mkversion? Tracking the version/date of the "make" binary, of the full set of "share/mk" files, of just the ports related makefiles? ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 1 21:45:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2D11214FB1 for ; Thu, 1 Apr 1999 21:45:23 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (365 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 1 Apr 1999 21:45:04 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Thu, 1 Apr 1999 21:45:04 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@freebsd.org Subject: netscape: no recognized font Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG % netscape no recognized font charsets! 3.1-stable as of today navigator 4.5 freshly installed randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 0: 9:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 1ABFB15056 for ; Fri, 2 Apr 1999 00:09:22 -0800 (PST) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.2/8.9.2) with SMTP id MAA79911 for ; Fri, 2 Apr 1999 12:09:02 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: freebsd-current@FreeBSD.ORG Subject: Re: AIC Date: Fri, 2 Apr 1999 11:59:16 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <3703A923.7F5810EF@newsguy.com> MIME-Version: 1.0 Message-Id: <99040212091200.24669@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG th , 01 ÁÐÒ 1999, Daniel C. Sobral wrote: > > Granted, we don't have a driver for that controller either, but the > > programming manual is readily available from LSI Logic. Seems to me that > > NetBSD has a driver for it, based on a Linux driver. (Been a while since > > I looked into it, so I may be misremembering.) > It seems programming manuals for the AIC 6[23]60 are also available, > and there is even a FreeBSD driver for it... :-) and it is too popular controller to ignore it at all. how ironic - older 2.2.x do support it, but newer 3.1/4.0 does not. i guess that many people have to use 2.2.8 on their old hardware instead of much more progressive 3.1 due to this problem only. and it's a pity :( sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 2:40:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id A005115139 for ; Fri, 2 Apr 1999 02:40:37 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA07844 for ; Fri, 2 Apr 1999 12:40:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id MAA35326 for ; Fri, 2 Apr 1999 12:40:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: LINT broken! From: Poul-Henning Kamp Date: Fri, 02 Apr 1999 12:40:08 +0200 Message-ID: <35324.923049608@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG n file included from ../../ntfs/ntfs_vnops.c:66: ../../ntfs/ntfs.h:29: warning: `DIAGNOSTIC' redefined opt_global.h:13: warning: this is the location of the previous definition cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../net/bridge.c ../../net/bridge.c: In function `bdg_forward': ../../net/bridge.c:530: `ip' undeclared (first use this function) ../../net/bridge.c:530: (Each undeclared identifier is reported only once ../../net/bridge.c:530: for each function it appears in.) *** Error code 1 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 4:34:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 3A53D14E6F; Fri, 2 Apr 1999 04:34:04 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA18297; Fri, 2 Apr 1999 12:13:44 +0200 From: Luigi Rizzo Message-Id: <199904021013.MAA18297@labinfo.iet.unipi.it> Subject: Re: LINT broken! To: phk@FreeBSD.ORG (Poul-Henning Kamp) Date: Fri, 2 Apr 1999 12:13:43 +0200 (MET DST) Cc: current@FreeBSD.ORG In-Reply-To: <35324.923049608@critter.freebsd.dk> from "Poul-Henning Kamp" at Apr 2, 99 12:39:49 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1033 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > n file included from ../../ntfs/ntfs_vnops.c:66: > ../../ntfs/ntfs.h:29: warning: `DIAGNOSTIC' redefined > opt_global.h:13: warning: this is the location of the previous definition > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../net/bridge.c > ../../net/bridge.c: In function `bdg_forward': > ../../net/bridge.c:530: `ip' undeclared (first use this function) > ../../net/bridge.c:530: (Each undeclared identifier is reported only once > ../../net/bridge.c:530: for each function it appears in.) i think it wasn't me :) it probably has to do with being included only when both IPFIREWALL and DUMMYNET are defined, but then used even when just IPFIREWALL is defined. At least this is how it is in 2.2.X don't know who last edited the file, but the fix should be fairly straightforward. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 4:37:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (Postfix) with ESMTP id 4BB3F14E65; Fri, 2 Apr 1999 04:37:30 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.8.8/Debian/GNU) with ESMTP id OAA29486; Fri, 2 Apr 1999 14:37:04 +0200 Date: Fri, 2 Apr 1999 14:37:04 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: can't register udp portmap In-Reply-To: <199904021206.OAA31981@greenpeace.grondar.za> Message-ID: <9904021433010.29379-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [replies redirected to hopefullly the right place] > Please check these before potentially starting rumours. > TCP_WRAPPERS is NOT in STABLE. I can't really say it's in -CURRENT, either; it installs /usr/lib/libwrap.so.3 and /usr/include/tcpd.h, but no /usr/libexec/tcpd as far as I can see. The port (security/tcp_wrappers) installs tcpd, but also /usr/local/lib/libwrap.so.7, so applications linked against the port will complain when run on a -CURRENT system without the port. What is the reason behind not installing /usr/libexec/tcpd? I can see not mucking with /etc/inetd.conf by default, but having the binary around would definitely save a lot of people some work. My E 0.02... -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 4:48:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id AB22714E4D for ; Fri, 2 Apr 1999 04:48:05 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id OAA70199; Fri, 2 Apr 1999 14:47:45 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id OAA32230; Fri, 2 Apr 1999 14:47:45 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904021247.OAA32230@greenpeace.grondar.za> To: N Cc: current@FreeBSD.ORG Subject: Re: can't register udp portmap In-Reply-To: Your message of " Fri, 02 Apr 1999 14:37:04 +0200." <9904021433010.29379-100000@liquid.tpb.net> References: <9904021433010.29379-100000@liquid.tpb.net> Date: Fri, 02 Apr 1999 14:47:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG N wrote: > What is the reason behind not installing /usr/libexec/tcpd? I can see not > mucking with /etc/inetd.conf by default, but having the binary around > would definitely save a lot of people some work. RTFM inetd(8). RTFCM. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 5:18:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (Postfix) with ESMTP id 534CA14D11 for ; Fri, 2 Apr 1999 05:18:18 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.8.8/Debian/GNU) with ESMTP id PAA29884; Fri, 2 Apr 1999 15:17:53 +0200 Date: Fri, 2 Apr 1999 15:17:52 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: can't register udp portmap In-Reply-To: <199904021247.OAA32230@greenpeace.grondar.za> Message-ID: <9904021510030.29794-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> What is the reason behind not installing /usr/libexec/tcpd? I can see not >> mucking with /etc/inetd.conf by default, but having the binary around >> would definitely save a lot of people some work. > RTFCM. Cool. Excellent. Thanks for the pointer. [sounds of foot in mouth insertion] (shouldn't auth.info be sent somewhere? Currently successful connections don't seem to be logged at all.) -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 5:25:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id E1C7A15107 for ; Fri, 2 Apr 1999 05:25:18 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id PAA70262; Fri, 2 Apr 1999 15:24:58 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id PAA32357; Fri, 2 Apr 1999 15:24:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904021324.PAA32357@greenpeace.grondar.za> To: N Cc: current@FreeBSD.ORG Subject: Re: can't register udp portmap In-Reply-To: Your message of " Fri, 02 Apr 1999 15:17:52 +0200." <9904021510030.29794-100000@liquid.tpb.net> References: <9904021510030.29794-100000@liquid.tpb.net> Date: Fri, 02 Apr 1999 15:24:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG N wrote: > >> What is the reason behind not installing /usr/libexec/tcpd? I can see not > >> mucking with /etc/inetd.conf by default, but having the binary around > >> would definitely save a lot of people some work. > > RTFCM. > > Cool. Excellent. Thanks for the pointer. [sounds of foot in mouth insertion ] > > (shouldn't auth.info be sent somewhere? Currently successful connections > don't seem to be logged at all.) You didn't include the patch for this :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 7:27:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from cepheus.hkstar.com (cepheus.hkstar.com [202.82.3.12]) by hub.freebsd.org (Postfix) with ESMTP id 9744814C20 for ; Fri, 2 Apr 1999 07:27:47 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cepheus.hkstar.com (8.9.0/8.9.0) with ESMTP id XAA29899 for ; Fri, 2 Apr 1999 23:27:27 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id XAA28315 for freebsd-current@freebsd.org; Fri, 2 Apr 1999 23:27:25 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199904021527.XAA28315@b1.hkstar.com> Subject: make egcs-1.1.2 error To: freebsd-current@freebsd.org Date: Fri, 2 Apr 1999 23:27:25 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I recently tried to update the egcs-1.1.2 and got this error. My system is upto the current ctm src-cur.3811. The compiler is egcs-1.1.2. Any idea ? Thanks. Clarence ======= Error ======= ===> Building for egcs-1.1.2 gmake[1]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/libiberty' gmake[1]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/libiberty' gmake[1]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo' gmake all-recursive gmake[2]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo' Making all in intl gmake[3]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo/intl' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo/intl' Making all in lib gmake[3]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo/lib' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo/lib' Making all in makeinfo gmake[3]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo/makeinfo' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo/makeinfo' Making all in util gmake[3]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo/util' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo/util' gmake[2]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo' gmake[1]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/texinfo' Bootstrapping the compiler gmake[1]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/gcc' gmake CC="cc" libdir=/usr/local/lib LANGUAGES="c " gmake[2]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/gcc' cc -DIN_GCC -g -DHAVE_CONFIG_H -I. -I. -I./config \ -DGCC_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i386-portbld-freebsd4.0/egcs-2.91.66/include\" \ -DGPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i386-portbld-freebsd4.0/egcs-2.91.66/include/g++\" \ -DOLD_GPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/g++-include\" \ -DLOCAL_INCLUDE_DIR=\"/usr/local/include\" \ -DCROSS_INCLUDE_DIR=\"/usr/local/i386-portbld-freebsd4.0/sys-include\" \ -DTOOL_INCLUDE_DIR=\"/usr/local/i386-portbld-freebsd4.0/include\" \ -c `echo ./cccp.c | sed 's,^\./,,'` In file included from config/i386/freebsd.h:26, from config/i386/freebsd.h:26, . . . from tm.h:4, from config/i386/xm-i386.h:43, from config.h:2, from cccp.c:21: config/i386/freebsd.h:26: macro or `#include' recursion too deep gmake[2]: *** [cccp.o] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/gcc' gmake[1]: *** [bootstrap] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/egcs/work/egcs-1.1.2/gcc' gmake: *** [bootstrap] Error 2 *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ======= Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 8:31:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id BF32E14C13 for ; Fri, 2 Apr 1999 08:31:31 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA00876; Fri, 2 Apr 1999 08:31:07 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id IAA83314; Fri, 2 Apr 1999 08:31:04 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 2 Apr 1999 08:31:04 -0800 (PST) Message-Id: <199904021631.IAA83314@vashon.polstra.com> To: camel@avias.com Subject: Re: AIC In-Reply-To: <99040212091200.24669@camel.avias.com> References: <3703A923.7F5810EF@newsguy.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <99040212091200.24669@camel.avias.com>, Ilya Naumov wrote: > how ironic - older 2.2.x do support it, but newer 3.1/4.0 does not. What is ironic about that? Old OS versions support old hardware, and new OS versions support new hardware. It makes perfect sense to me. John "My Sun 3/180 supported SMD disks, but FreeBSD doesn't!" Polstra -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 9:20:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AFA4014E51 for ; Fri, 2 Apr 1999 09:20:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA63381; Fri, 2 Apr 1999 09:19:58 -0800 (PST) (envelope-from obrien) Message-ID: <19990402091958.A63372@nuxi.com> Date: Fri, 2 Apr 1999 09:19:58 -0800 From: "David O'Brien" To: Chan Yiu Wah , freebsd-current@FreeBSD.ORG Subject: Re: make egcs-1.1.2 error Reply-To: obrien@NUXI.com References: <199904021527.XAA28315@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904021527.XAA28315@b1.hkstar.com>; from Chan Yiu Wah on Fri, Apr 02, 1999 at 11:27:25PM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I recently tried to update the egcs-1.1.2 and got this error. Fixed. Please fetch the latest Port version. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 9:49:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8CA5514CA4 for ; Fri, 2 Apr 1999 09:49:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA63457; Fri, 2 Apr 1999 09:49:14 -0800 (PST) (envelope-from obrien) Message-ID: <19990402094914.D63372@nuxi.com> Date: Fri, 2 Apr 1999 09:49:14 -0800 From: "David O'Brien" To: Steve Kargl , freebsd-current@FreeBSD.ORG Subject: Re: egcs knob and objective C Reply-To: obrien@NUXI.com References: <199903311851.KAA22652@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903311851.KAA22652@troutmask.apl.washington.edu>; from Steve Kargl on Wed, Mar 31, 1999 at 10:51:39AM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a simple knob to turn to get the egcs compiler by > default? Not really. You would have to CVSup my src/gnu/ bits and spam them over the /usr/src/ tree. > And, at the risk of being flamed, I noticed (after all these years) > that we build some for Objective C stuff. Is this actually required > within the base distribution? Yes. It is too tightly tied into the reset of the Gnu compiler that it would be too hard to make a port out of it. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 10: 0: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from vanessa.eliuk.org (sec4d46.dial.uniserve.ca [204.244.165.205]) by hub.freebsd.org (Postfix) with ESMTP id 8F82F14FB1 for ; Fri, 2 Apr 1999 10:00:05 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.3/8.9.3) with ESMTP id JAA00574 for ; Fri, 2 Apr 1999 09:59:39 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Fri, 2 Apr 1999 09:59:08 -0800 (PST) From: "Kevin G. Eliuk" To: current@FreeBSD.ORG Subject: Restarting after power failure In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something that I have never experienced before this point and am not sure whether to apply the concern to softupdates or the ATA - drivers. After a power outage, restarting the computer in single user, running fsck on all the entries in /etc/fstab, and typing exit it would tell me that it could not mount "/" and drop me back to the shell choice to run fsck again. WARNING: R/W mount of / denied. Filesystem is not clean - run fsck After the third fsck, I sync'd four times and typed halt and shut down the machine. It was able to boot normally. I thought I'd report this in case there was any safeties that needed to be in place for such cases. On Thu, 1 Apr 1999, Kevin G. Eliuk wrote: > --- > COPTFLAGS= -O2 -pipe -m486 -fexpensive-optimizations -fomit-frame-pointer > > FreeBSD 4.0-CURRENT #0: Wed Mar 31 07:24:07 PST 1999 > cagey@vanessa.eliuk.org:/usr/src/sys/compile/CATHERNA > CPU: Pentium/P54C (99.88-MHz 586-class CPU) > real memory = 33554432 (32768K bytes) > avail memory = 29327360 (28640K bytes) > Found BIOS32 Service Directory header at 0xc00fdae0 > Entry = 0xfdaf0 (0xc00fdaf0) Rev = 0 Len = 1 > PCI BIOS entry at 0xdb11 > Bad DMI table checksum! > Other BIOS signatures found: > ACPI: 00000000 > pci_open(1): mode 1 addr port (0x0cf8) is 0x8000004c > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=153110b9) > Probing for devices on PCI bus 0: > found-> vendor=0x10b9, dev=0x1531, revid=0xb3 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > chip0: rev 0xb3 on pci0.0.0 > found-> vendor=0x10b9, dev=0x1533, revid=0xb4 > class=06-01-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > chip1: rev 0xb4 on pci0.2.0 > found-> vendor=0x5333, dev=0x5631, revid=0x06 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=0 > map[0]: type 1, range 32, base ec000000, size 26 > ata-pci0: rev 0x20 int a irq 0 on pci0.11.0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > found-> vendor=0x10b9, dev=0x5237, revid=0x03 > class=0c-03-10, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[0]: type 1, range 32, base ebfef000, size 12 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > ata0: master: settting up UDMA2 mode on Aladdin chip OK > ad0: ATA-4 disk at ata0 as master > ad0: 8010MB (16406208 sectors), 16276 cyls, 16 heads, 63 S/T, 512 B/S > ad0: piomode=4, dmamode=2, udmamode=2 > ad0: 16 secs/int, 0 depth queue, DMA mode > ata1: master: settting up WDMA2 mode on Aladdin chip OK > ad1: ATA-? disk at ata1 as master > ad1: 1036MB (2121840 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S > ad1: piomode=4, dmamode=2, udmamode=-1 > ad1: 16 secs/int, 0 depth queue, DMA mode > acd0: CDROM drive at ata1 as slave > acd0: drive speed 689KB/sec, 256KB cache > acd0: supported read types: CD-DA > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM unknown medium, unlocked > Considering FFS root f/s. > changing root device to wd0s2a > ad0s1: type 0xb, start 63, end = 5253254, size 5253192 : OK > ad0s2: type 0xa5, start 5253255, end = 16402364, size 11149110 > ad0s2: C/H/S end 1019/254/63 (16386299) != end 16402364: invalid > Start pid=2 > Start pid=3 > Start pid=4 > ad1s1: type 0xa5, start 63, end = 1842623, size 1842561 : OK > ad1s1: type 0xa5, start 63, end = 1842623, size 1842561 : OK > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > ad1s1: type 0xa5, start 63, end = 1842623, size 1842561 : OK > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 10:21:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7CEC214CC9 for ; Fri, 2 Apr 1999 10:21:43 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA00658; Fri, 2 Apr 1999 10:21:23 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id KAA16134; Fri, 2 Apr 1999 10:21:22 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 2 Apr 1999 10:21:22 -0800 (PST) Message-Id: <199904021821.KAA16134@vashon.polstra.com> To: kevin_eliuk@sunshine.net Subject: Re: Restarting after power failure In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Kevin G. Eliuk wrote: > > Something that I have never experienced before this point and am not > sure whether to apply the concern to softupdates or the ATA - drivers. > > After a power outage, restarting the computer in single user, running > fsck on all the entries in /etc/fstab, and typing exit it would tell me > that it could not mount "/" and drop me back to the shell choice to run > fsck again. > > WARNING: R/W mount of / denied. Filesystem is not clean - run fsck One possibility: Make sure your /etc/fstab lists the root device including the slice. For example, "/dev/wd0s1a" and _not_ "/dev/wd0a". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 10:42:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id ADE9F14D4D; Fri, 2 Apr 1999 10:42:13 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id MAA15785; Fri, 2 Apr 1999 12:41:53 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id MAA16687; Fri, 2 Apr 1999 12:41:53 -0600 (CST) Date: Fri, 2 Apr 1999 12:41:53 -0600 From: Alan Cox To: current@freebsd.org Cc: luoqi@freebsd.org Subject: SMP users (important) Message-ID: <19990402124153.H14114@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've committed the basic infrastructure to improve TLB management on SMPs. Translation: this will lead to the elimination of a LOT of interprocessor interrupts to invalidate TLB entries. I'll be "turning on" the new mechanisms slowly so we can carefully debug each step and (hopefully) avoid any problems. Now, if you're not using Luoqi's patches to enable multithreaded address spaces, you can stop reading here. If you are, you'll need to patch i386/i386/swtch.s as follows: Index: i386/i386/swtch.s =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/swtch.s,v retrieving revision 1.78 diff -c -r1.78 swtch.s *** swtch.s 1999/04/02 17:59:39 1.78 --- swtch.s 1999/04/02 18:37:29 *************** *** 466,472 **** #else xorl %eax, %eax #endif /* SMP */ ! btrl %eax, VM_PMAP+PM_ACTIVE(%edx) movl P_ADDR(%ecx),%edx --- 466,473 ---- #else xorl %eax, %eax #endif /* SMP */ ! movl VM_PMAP(%edx), %edx ! btrl %eax, PM_ACTIVE(%edx) movl P_ADDR(%ecx),%edx *************** *** 690,696 **** #else xorl %eax, %eax #endif ! btsl %eax, VM_PMAP+PM_ACTIVE(%ebx) /* restore context */ movl PCB_EBX(%edx),%ebx --- 691,698 ---- #else xorl %eax, %eax #endif ! movl VM_PMAP(%ebx), %ebx ! btsl %eax, PM_ACTIVE(%ebx) /* restore context */ movl PCB_EBX(%edx),%ebx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 11:38:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (Postfix) with ESMTP id 5CF9614BD3 for ; Fri, 2 Apr 1999 11:38:39 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.8.8/Debian/GNU) with ESMTP id VAA32322; Fri, 2 Apr 1999 21:38:17 +0200 Date: Fri, 2 Apr 1999 21:38:16 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: can't register udp portmap In-Reply-To: <199904021324.PAA32357@greenpeace.grondar.za> Message-ID: <9904022128150.32264-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> (shouldn't auth.info be sent somewhere? Currently successful connections >> don't seem to be logged at all.) > You didn't include the patch for this :-) --- /usr/src/etc/syslog.conf Wed Oct 14 23:59:55 1998 +++ /etc/syslog.conf Thu Feb 4 02:23:07 1999 @@ -11,6 +11,7 @@ *.notice;news.err root *.alert root *.emerg * +auth.debug /var/log/auth.log # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err --- /usr/src/etc/newsyslog.conf Tue Feb 23 00:34:51 1999 +++ /etc/newsyslog.conf Fri Apr 2 21:29:18 1999 @@ -4,6 +4,7 @@ # logfilename owner.group mode count size time [ZB] [/pid_file] [sig_num] /var/cron/log 600 3 100 * Z /var/log/amd.log 664 7 100 * Z +/var/log/auth.log 600 7 100 * Z /var/log/kerberos.log 664 7 100 * Z /var/log/lpd-errs 664 7 100 * Z /var/log/maillog 664 7 * 24 Z --- /usr/src/etc/defaults/rc.conf Fri Apr 2 15:20:24 1999 +++ /etc/defaults/rc.conf Fri Apr 2 21:34:42 1999 @@ -54,7 +54,9 @@ syslogd_enable="YES" # Run syslog daemon (or NO). syslogd_flags="" # Flags to syslogd (if enabled). inetd_enable="YES" # Run the network daemon dispatcher (or NO). -inetd_flags="" # Optional flags to inetd. +inetd_flags="" # Optional flags to inetd (use '-l' to log + # successful requests as well as those that + # were rejected via /etc/hosts.allow). # # named. It may be possible to run named in a sandbox, man security for # details. Not too hard. :-) -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 12:46:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CC1F214BDD for ; Fri, 2 Apr 1999 12:46:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA13472; Fri, 2 Apr 1999 12:45:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: Steve Kargl , freebsd-current@FreeBSD.ORG Subject: Re: egcs knob and objective C In-reply-to: Your message of "Fri, 02 Apr 1999 09:49:14 PST." <19990402094914.D63372@nuxi.com> Date: Fri, 02 Apr 1999 12:45:53 -0800 Message-ID: <13470.923085953@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there a simple knob to turn to get the egcs compiler by > > default? > > Not really. You would have to CVSup my src/gnu/ bits and spam them over > the /usr/src/ tree. When do you intend to "throw the switch" in bringing egcs in by default? A lot of people are asking and perhaps a bit of an advance schedule wouldn't hurt at this point, if for no other reason than that people wouldn't be able to scream (with any justification) about the transition, when it happens, taking them by total surprise. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 12:59:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7514E14BDD for ; Fri, 2 Apr 1999 12:59:17 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA64194; Fri, 2 Apr 1999 12:58:50 -0800 (PST) (envelope-from obrien) Message-ID: <19990402125850.A64180@nuxi.com> Date: Fri, 2 Apr 1999 12:58:50 -0800 From: "David O'Brien" To: Andrzej Bialecki Cc: freebsd-current@FreeBSD.ORG Subject: Re: egcs knob and objective C Reply-To: obrien@NUXI.com References: <199903311851.KAA22652@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Andrzej Bialecki on Wed, Mar 31, 1999 at 10:19:26PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also, I seem to recall that we already have another copy of libiberty > (under gdb). Do we really need to have both of them? The EGCS copy is newer. We are considering building a libiberty.* for /usr/lib/. Once we know which sources to use, the duplicate can be deleted. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 13: 8:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7876714E1A for ; Fri, 2 Apr 1999 13:06:21 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA64258 for freebsd-current@freebsd.org; Fri, 2 Apr 1999 13:06:02 -0800 (PST) (envelope-from obrien) Message-ID: <19990402130602.C64197@nuxi.com> Date: Fri, 2 Apr 1999 13:06:02 -0800 From: "David O'Brien" To: freebsd-current@freebsd.org Subject: Re: Dates off by 1 year (was: Fools Day Joke ?) Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the explanation for the problem from the NcFTP author: ----- Forwarded message from Mike Gleason ----- Date: Fri, 02 Apr 1999 12:39:07 -0600 Subject: Re: (FWD) Re: Dates off by 1 year (was: Fools Day Joke ?) The problem is that NcFTP 3 tries to parse the output of the listing and stores it in an internal format, and when the listing is actually displayed, it is recreated from the saved data. I.e., the listing's date is converted to a time_t, and then reformatted later. Due to timezone differences between client and server, this can never be 100% accurate (until more FTP servers adopt the new machine-readable directory listings). However, /bin/ls prints two different formats for the date. One is "mmm dd yyyy", and the other is "mmm dd HH:MM". The second format is used when the file is less than six months old, or less than one hour into the future. The beta 18 code's logic is flawed, since it guesses the year wrong when the file is very new and the timezone discrepancy make the preliminary time_t conversion appear that the file is "too far" into the future. The good news is that this is easily correctible. Sorry the wild goose chase :-) Mike Gleason ----- End forwarded message ----- -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 13:25: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C7F1714D61 for ; Fri, 2 Apr 1999 13:24:58 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA65994; Fri, 2 Apr 1999 22:25:59 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 2 Apr 1999 22:25:59 +0100 (BST) From: Doug Rabson To: "David O'Brien" Cc: Andrzej Bialecki , freebsd-current@freebsd.org Subject: Re: egcs knob and objective C In-Reply-To: <19990402125850.A64180@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Apr 1999, David O'Brien wrote: > > Also, I seem to recall that we already have another copy of libiberty > > (under gdb). Do we really need to have both of them? > > The EGCS copy is newer. We are considering building a libiberty.* for > /usr/lib/. Once we know which sources to use, the duplicate can be > deleted. We should also consider installing libbfd. If and when we bring in a newer version of gdb, it would be a good idea to avoid importing yet another version of libiberty and libbfd. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 13:34: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id EE72114D2D for ; Fri, 2 Apr 1999 13:33:55 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id PAA09431; Fri, 2 Apr 1999 15:33:21 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma009429; Fri, 2 Apr 99 15:33:19 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id PAA84656; Fri, 2 Apr 1999 15:32:37 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199904022132.PAA84656@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: lists/freebsd X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: egcs knob and objective C Mime-Version: 1.0 Content-Type: text/plain To: Doug Rabson Cc: "David O'Brien" , Andrzej Bialecki , freebsd-current@FreeBSD.ORG Date: Fri, 02 Apr 1999 15:32:37 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 April 1999 at 22:25, Doug Rabson wrote: > We should also consider installing libbfd. If and when we bring in a newer > version of gdb, it would be a good idea to avoid importing yet another > version of libiberty and libbfd. ... and GNU regex. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 13:46:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 71A7314D61 for ; Fri, 2 Apr 1999 13:46:31 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA64538 for current@freebsd.org; Fri, 2 Apr 1999 13:46:12 -0800 (PST) (envelope-from obrien) Message-ID: <19990402134612.I64197@nuxi.com> Date: Fri, 2 Apr 1999 13:46:12 -0800 From: "David O'Brien" To: current@freebsd.org Subject: HEADS UP -- move to EGCS as base compiler Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Baring unforeseen problems, I plan to pull the switch on Sunday that will make EGCS the base compiler in 4.0-CURRENT. A CVSup and a `build world' after I pull the switch should be all that is necessary to give you the new compiler. I have tested kernel builds and `make world' and believe it to be ready to go. However there are always unforeseen problems. So the less-adventurous might want to hold off on their next `make world' after the change for a few days to let the dust settle. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 13:50:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 3416414E84 for ; Fri, 2 Apr 1999 13:50:13 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id PAA21727; Fri, 2 Apr 1999 15:49:43 -0600 (CST) Date: Fri, 2 Apr 1999 15:49:43 -0600 (CST) From: Steve Price To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: HEADS UP -- move to EGCS as base compiler In-Reply-To: <19990402134612.I64197@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Apr 1999, David O'Brien wrote: # Hi all, # # Baring unforeseen problems, I plan to pull the switch on Sunday that will # make EGCS the base compiler in 4.0-CURRENT. # # A CVSup and a `build world' after I pull the switch should be all that is # necessary to give you the new compiler. # # I have tested kernel builds and `make world' and believe it to be ready # to go. However there are always unforeseen problems. So the # less-adventurous might want to hold off on their next `make world' after # the change for a few days to let the dust settle. Can you tell where the switch is so I can pull the switch early and start fixing some of the ports that are going to pop because of this change? Thanks. -steve # -- # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 13:50:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A754F150AF; Fri, 2 Apr 1999 13:50:28 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA00965; Fri, 2 Apr 1999 13:50:04 -0800 (PST) Date: Fri, 2 Apr 1999 13:50:04 -0800 (PST) From: Julian Elischer To: Alan Cox Cc: current@FreeBSD.ORG, luoqi@FreeBSD.ORG Subject: Re: SMP users (important) In-Reply-To: <19990402124153.H14114@nonpc.cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Apr 1999, Alan Cox wrote: > > Now, if you're not using Luoqi's patches to enable multithreaded > address spaces, you can stop reading here. If you are, you'll > need to patch i386/i386/swtch.s as follows: My suggestion is that we apply Luoqi's %fs patch to -current rather than have to track these changes manually.. Luoqi? Have you had any -ve feedback on this? (and what would be the equivalent ALPHA patch?) I can imagine the original PDE trick working on the alpha but they don't have a spare register sitting around.. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 13:55:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 36F7C14F49 for ; Fri, 2 Apr 1999 13:55:14 -0800 (PST) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-ra-nc1-121.netcologne.de [195.14.244.121]) by mail2.netcologne.de (8.9.1/8.9.1) with ESMTP id XAA23171; Fri, 2 Apr 1999 23:54:52 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.1/8.9.3) id XAA01336; Fri, 2 Apr 1999 23:55:46 +0200 (CEST) (envelope-from marc) Date: Fri, 2 Apr 1999 23:55:46 +0200 (CEST) Message-Id: <199904022155.XAA01336@oranje.my.domain> From: Marc van Woerkom To: freebsd-current@freebsd.org Subject: make buildworld fails Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! A fresh cvsup plus make buildworld did not complete on my 3.0-RELEASE system. ---------------------------------------------------------------------- root@oranje# date Fri Apr 2 22:37:32 CEST 1999 root@oranje# make buildworld; date -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp -------------------------------------------------------------- >>> Making make (...) install -c -o root -g wheel -m 444 libstdc++.so.2 /usr/obj/usr/src/tmp/usr/lib ln -sf libstdc++.so.2 /usr/obj/usr/src/tmp/usr/lib/libstdc++.so cd /usr/src/gnu/usr.bin/cc/libgcc; /usr/obj/usr/src/tmp/usr/bin/make all; /usr/obj/usr/src/tmp/usr/bin/make -B install install -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/tmp/mk usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Fri Apr 2 23:17:53 CEST 1999 root@oranje# ----------------------------------------------------------------------------------------- However these last attempts did run through without problems: -rw-r--r-- 1 root bin 8310232 Mar 22 19:36 1.log -rw-r--r-- 1 root bin 8346805 Mar 24 00:57 2.log -rw-r--r-- 1 root bin 8346878 Mar 26 22:39 3.log -rw-r--r-- 1 root bin 8357073 Mar 28 23:41 4.log -rw-r--r-- 1 root bin 5415813 Mar 30 00:18 5.log -rw-r--r-- 1 root bin 5588079 Apr 2 04:28 6.log Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 14:12:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id B946514E84 for ; Fri, 2 Apr 1999 14:12:38 -0800 (PST) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-ra-nc1-121.netcologne.de [195.14.244.121]) by mail2.netcologne.de (8.9.1/8.9.1) with ESMTP id AAA23880; Sat, 3 Apr 1999 00:12:16 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.1/8.9.3) id AAA01406; Sat, 3 Apr 1999 00:13:10 +0200 (CEST) (envelope-from marc) Date: Sat, 3 Apr 1999 00:13:10 +0200 (CEST) Message-Id: <199904022213.AAA01406@oranje.my.domain> From: Marc van Woerkom To: randy@psg.com Cc: freebsd-current@FreeBSD.ORG In-reply-to: (message from Randy Bush on Thu, 1 Apr 1999 21:45:04 -0800 (PST)) Subject: Re: netscape: no recognized font Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > % netscape > no recognized font charsets! > > 3.1-stable as of today > navigator 4.5 freshly installed I had similiar font problems when installing Navigator 4.5 under Solaris 2.6. They went away after I nuked all prior traces of Navigator, including my .netscape directory (you should rename it :-) Who knows, this might work here too. Good luck, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 14:16:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 727DA14E84; Fri, 2 Apr 1999 14:16:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA14177; Fri, 2 Apr 1999 14:16:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) Cc: jhay@mikom.csir.co.za, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion In-reply-to: Your message of "Thu, 01 Apr 1999 02:36:14 PST." <199904011036.CAA52719@silvia.hip.berkeley.edu> Date: Fri, 02 Apr 1999 14:16:23 -0800 Message-ID: <14175.923091383@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The name of the directory where it resides doesn't matter. It's not a As long as that directory is not /var/db/pkg, where I put my package information, I agree that it doesn't matter either. :-) > The same situation arises whether the version info is in /var/db/pkg > or /some/other/place. It has been pointed out many times in the past > that we need something to ensure bsd.port.mk can synchronize itself > with the rest of the system (simply because there are too many people > who cvsup one without the other). I'm not sure that this is a solution so much as a band-aid, however. > The question is, can I ask you to make sysinstall write some kind of > version info that can be used by bsd.port.mk to identify the age of > the system? I could record the version number of the system as it was when sysinstall installed it (3.1-RELEASE, X.X-YYYYMMDD-CURRENT, etc) but that's about it. > The problem is real, we've been bitten too many times in the past > (haven't you seen all the "where's fetch -A?" and other more subtle > breakages that are caused by ports and system mismatch), and I can Well, the fetch -A thing was another imprudent leap off the wire without a net, I'm not sure I'd use it to aid my arguments if I were you. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 14:27: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id BA38314C2B for ; Fri, 2 Apr 1999 14:27:01 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA00567; Fri, 2 Apr 1999 14:26:40 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id OAA35301; Fri, 2 Apr 1999 14:26:39 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 2 Apr 1999 14:26:39 -0800 (PST) Message-Id: <199904022226.OAA35301@vashon.polstra.com> To: dfr@nlsystems.com Subject: Re: egcs knob and objective C In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Doug Rabson wrote: > We should also consider installing libbfd. We can do that any time (ELF only), as far as I'm concerned. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 14:43:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from vanessa.eliuk.org (sec2d32.dial.uniserve.ca [204.244.165.95]) by hub.freebsd.org (Postfix) with ESMTP id B36DE14C9E for ; Fri, 2 Apr 1999 14:43:13 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.3/8.9.3) with ESMTP id OAA00489; Fri, 2 Apr 1999 14:42:46 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Fri, 2 Apr 1999 14:42:15 -0800 (PST) From: "Kevin G. Eliuk" To: John Polstra Cc: current@freebsd.org Subject: Re: Restarting after power failure In-Reply-To: <199904021821.KAA16134@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Apr 1999, John Polstra wrote: > In article , > Kevin G. Eliuk wrote: > > > > WARNING: R/W mount of / denied. Filesystem is not clean - run fsck > > One possibility: Make sure your /etc/fstab lists the root device > including the slice. For example, "/dev/wd0s1a" and _not_ "/dev/wd0a". Nope, # Device Mountpoint FStype Options Dump Pass# /dev/ad0s2b none swap sw 0 0 /dev/ad0s2a / ufs rw 1 1 /dev/ad0s2e /usr ufs rw 2 2 /dev/ad0s2f /var ufs rw 2 2 /dev/ad1s1e /cvs ufs rw 2 2 /dev/ad1s1f /usr/obj ufs rw 2 2 proc /proc procfs rw 0 0 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 -- Regards, Kevin G. Eliuk Box 67, Granthams Landing, BC VON 1X0 (604)886-4040 Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 14:56:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EC28214CA8 for ; Fri, 2 Apr 1999 14:56:11 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id OAA64817; Fri, 2 Apr 1999 14:55:21 -0800 (PST) (envelope-from obrien) Message-ID: <19990402145521.A64671@nuxi.com> Date: Fri, 2 Apr 1999 14:55:21 -0800 From: "David O'Brien" To: Steve Price Cc: current@FreeBSD.ORG Subject: Re: HEADS UP -- move to EGCS as base compiler Reply-To: obrien@NUXI.com References: <19990402134612.I64197@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Steve Price on Fri, Apr 02, 1999 at 03:49:43PM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can you tell where the switch is so I can pull the switch early The "switch" is me checking out src/gnu/usr.bin/cc, overlaying the bits I've been working on and then committing them. You can get the bits using the sup file I've posted to current last month. > and start fixing some of the ports that are going to pop because > of this change? Thanks. It might be easier to build the EGCS port, moving /usr/bin/{cc,c++,gcc,g++} out of the way and making links to the egcs binaries. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 17:26:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mordred.cs.ucla.edu (Mordred.CS.UCLA.EDU [131.179.48.34]) by hub.freebsd.org (Postfix) with ESMTP id 3FD0014BE6 for ; Fri, 2 Apr 1999 17:26:35 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.9.3/8.9.3) with ESMTP id RAA62422 for ; Fri, 2 Apr 1999 17:26:16 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199904030126.RAA62422@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: YP/NIS and passwd weirdness Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Apr 1999 17:26:15 -0800 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I didn't see anything along these lines the the archive, so here goes... (something different to the other threads running these days.) In 3.3.1 and 4.0-current, if one puts the following in /etc/passwd to enable NIS logins: +:*::::: then logins (console or ssh) of ordinary users don't work. After gdb-ing ssh, I found that getpwnam() consistently returns "*" as the user's password. Removing the "*" makes things work again, but the security check wails about a user w/o a password. Question: Was this intentional behavior or should I submit a pr with a patch? -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 17:29:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 32445152B7 for ; Fri, 2 Apr 1999 17:29:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id RAA14373; Fri, 2 Apr 1999 17:29:12 -0800 Date: Fri, 2 Apr 1999 17:29:12 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Scott Michel Cc: current@FreeBSD.ORG Subject: Re: YP/NIS and passwd weirdness In-Reply-To: <199904030126.RAA62422@mordred.cs.ucla.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Umm- it's never supposed to have been with a '*' in it for this YP implementation, I believe. Fixing the security check would be a good thing. Going to pam/nsswitch.conf would be even better. On Fri, 2 Apr 1999, Scott Michel wrote: > I didn't see anything along these lines the the archive, so > here goes... (something different to the other threads running > these days.) > > In 3.3.1 and 4.0-current, if one puts the following in /etc/passwd > to enable NIS logins: > > +:*::::: > > then logins (console or ssh) of ordinary users don't work. After > gdb-ing ssh, I found that getpwnam() consistently returns "*" as > the user's password. > > Removing the "*" makes things work again, but the security check > wails about a user w/o a password. > > Question: Was this intentional behavior or should I submit a pr with > a patch? > > > -scooter > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 17:39:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mordred.cs.ucla.edu (Mordred.CS.UCLA.EDU [131.179.48.34]) by hub.freebsd.org (Postfix) with ESMTP id 26C9E150EF for ; Fri, 2 Apr 1999 17:39:11 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.9.3/8.9.3) with ESMTP id RAA62524; Fri, 2 Apr 1999 17:38:51 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199904030138.RAA62524@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: current@freebsd.org Subject: Re: YP/NIS and passwd weirdness In-Reply-To: Your message of "Fri, 02 Apr 1999 17:29:12 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Apr 1999 17:38:51 -0800 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Umm- it's never supposed to have been with a '*' in it for this YP > implementation, I believe. Fixing the security check would be a good > thing. Going to pam/nsswitch.conf would be even better. Been that way for years, ever since I started supporting a SCO box oh these many years ago with a UUCP mail link. (System administration in the small company at the time was more than enough motivation to go to graduate school. Where I'm admining Lixia Zhang's machines. :-) Getting an nsswitch.conf-ish type file might not be such a bad thing and would consolidate some of the current set of hacks. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 17:40:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C6055150EF for ; Fri, 2 Apr 1999 17:40:41 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id RAA14501; Fri, 2 Apr 1999 17:40:10 -0800 Date: Fri, 2 Apr 1999 17:40:09 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Scott Michel Cc: current@freebsd.org Subject: Re: YP/NIS and passwd weirdness In-Reply-To: <199904030138.RAA62524@mordred.cs.ucla.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Apr 1999, Scott Michel wrote: > > Umm- it's never supposed to have been with a '*' in it for this YP > > implementation, I believe. Fixing the security check would be a good > > thing. Going to pam/nsswitch.conf would be even better. > > Been that way for years, ever since I started supporting a SCO box > oh these many years ago with a UUCP mail link. (System administration > in the small company at the time was more than enough motivation to > go to graduate school. Where I'm admining Lixia Zhang's machines. :-) By 'this YP implementation' I meant FreeBSD/OpenBSD implementation- not others. > > Getting an nsswitch.conf-ish type file might not be such a bad thing > and would consolidate some of the current set of hacks. > yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 2 18: 0:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 66CB114C9C for ; Fri, 2 Apr 1999 18:00:34 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id UAA72083; Fri, 2 Apr 1999 20:00:09 -0600 (CST) Date: Fri, 2 Apr 1999 20:00:08 -0600 From: Dan Nelson To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Dates off by 1 year (was: Fools Day Joke ?) Message-ID: <19990402200008.B71842@dan.emsphone.com> References: <19990402130602.C64197@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990402130602.C64197@nuxi.com>; from "David O'Brien" on Fri Apr 2 13:06:02 GMT 1999 X-OS: FreeBSD 3.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Apr 02), David O'Brien said: > Here is the explanation for the problem from the NcFTP author: Oh yeah. go and ask the author. That's cheating. -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 1:17:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 94D5414F2A for ; Sat, 3 Apr 1999 01:17:20 -0800 (PST) (envelope-from peter@FreeBSD.org) Received: (from peter@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id BAA36585 for current@freebsd.org; Sat, 3 Apr 1999 01:15:26 -0800 (PST) (envelope-from peter@FreeBSD.org) Date: Sat, 3 Apr 1999 01:15:26 -0800 (PST) From: Message-Id: <199904030915.BAA36585@freefall.freebsd.org> To: current@freebsd.org Subject: test to current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Just testing after hub was upgraded) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 2:25: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [195.24.160.51]) by hub.freebsd.org (Postfix) with ESMTP id DE28614A0B for ; Sat, 3 Apr 1999 02:24:58 -0800 (PST) (envelope-from anders@enterprise.sanyusan.se) Received: (from anders@localhost) by enterprise.sanyusan.se (8.9.2/8.9.2) id MAA12243 for freebsd-current@freebsd.org; Sat, 3 Apr 1999 12:22:21 +0200 (CEST) (envelope-from anders) Date: Sat, 3 Apr 1999 12:22:21 +0200 From: Anders Andersson To: freebsd-current@freebsd.org Subject: DES from source? Message-ID: <19990403122221.A12230@sanyusan.se> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [posted to -current after no response from -questions] Hi! I am looking for the correct way of installing DES (crypt) from sources. From the beginning I install most of my boxes from ftp and with the "minimal" option. After that I cvsup and do make world to fit my needs. On this test box I run 4.0-CURRENT and have cvsupped the: # The international secure collections. src-crypto src-eBones src-secure I plan to do 'make world' and from what I can tell I need to: ln -fs libdescrypt.so libcrypt.so ln -fs libdescrypt.so.2 libcrypt.so.2 ln -fs libdescrypt.a libcrypt.a after make world to use DES (crypt). Do I need to change all passwd with 'passwd {user}' to use DES passwd crypt? Is there any thing I have missed? Anders -- -------------------------------------------------------- Anders Andersson anders@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ Västgötagatan 11 Tel: +46-(0)31-168730 411 39 Gothenburg, SWEDEN Fax: +46-(0)31-209361 -------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 4:39:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from rem.club.gagarinclub.ru (unknown [195.34.16.51]) by hub.freebsd.org (Postfix) with ESMTP id 2AD7114CD4; Sat, 3 Apr 1999 04:39:27 -0800 (PST) (envelope-from firma@windoms.sitek.net) Received: from localhost (firma@localhost) by rem.club.gagarinclub.ru (8.9.3/8.9.3) with ESMTP id QAA19040; Sat, 3 Apr 1999 16:37:57 +0400 (MSD) X-Authentication-Warning: rem.club.gagarinclub.ru: firma owned process doing -bs Date: Sat, 3 Apr 1999 16:37:56 +0400 (MSD) From: REM X-Sender: firma@rem.club.gagarinclub.ru To: bugs@freebsd.org Cc: current@freebsd.org Subject: Error during compile EGCS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I made two steps in /usr/src/contrib/egsc # ./configure # make I have: gcc -DIN_GCC -g -O2 -DHAVE_CONFIG_H -I. -I. -I./config -DGCC_INCLUDE_DIR=\"/usr/local/lib/gcc-lib/i386-unknown-freebsdelf4.0/egcs-2.91.66/include\" -DGPLUSPLUS_INCLUDE_DIR=\"/usr/local/include/g++\" -DOLD_GPLUSPLUS_INCLUDE_DIR=\"/usr/local/lib/g++-include\" -DLOCAL_INCLUDE_DIR=\"/usr/local/include\" -DCROSS_INCLUDE_DIR=\"/usr/local/i386-unknown-freebsdelf4.0/sys-include\" -DTOOL_INCLUDE_DIR=\"/usr/local/i386-unknown-freebsdelf4.0/include\" -c `echo ./cccp.c | sed 's,^\./,,'` In file included from config/i386/xm-i386.h:43, from config.h:2, from cccp.c:21: tm.h:3: linux.h: No such file or directory tm.h:4: i386/freebsd-elf.h: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. What does it mean? REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 5:18: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 91DA714E91 for ; Sat, 3 Apr 1999 05:18:06 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 17424 invoked from network); 3 Apr 1999 13:16:09 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 3 Apr 1999 13:16:09 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.3/8.9.1) id IAA45781; Sat, 3 Apr 1999 08:16:08 -0500 (EST) Message-Id: <199904031316.IAA45781@y.dyson.net> Subject: Re: SMP users (important) In-Reply-To: <19990402124153.H14114@nonpc.cs.rice.edu> from Alan Cox at "Apr 2, 99 12:41:53 pm" To: alc@cs.rice.edu (Alan Cox) Date: Sat, 3 Apr 1999 08:16:08 -0500 (EST) Cc: current@freebsd.org, luoqi@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alan Cox said: > > I've committed the basic infrastructure to improve TLB management > on SMPs. Translation: this will lead to the elimination of a LOT > of interprocessor interrupts to invalidate TLB entries. I'll be > "turning on" the new mechanisms slowly so we can carefully debug > each step and (hopefully) avoid any problems. > (To the rest of the team, Alan and Luoqi already know my opinion.) I just wanted to "chime in" and say that the new patches are based on a really good concept, and is much cleaner than the previous method. Also, many RISC architectures can utilize this method due to the availability of lots of general registers. (One could go so far as to have the compiler reserve the register.) Non-threaded user mode apps could optionally use the reserved register, but for threaded user mode apps, that reserved register could also be used as a per-thread base pointer. I believe that NT does the above (%fs for X86, and general register for Alpha.) On PPC, there are several local, per-processor registers that one could use (but loading a general register with that per processor register would be needed for access.) Also, since the PPC has lots of registers, one could? permanently reserve one of the general registers (r13?). All in all, this change has the potential for better context switching time (and less memory/better performance for multi-threaded processes.) This is a serious, non-trivial movement in the *right* direction!!! :-). SMP users should be pleased with this movement (I certainly am!!!) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 5:56: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id F3E5014C85 for ; Sat, 3 Apr 1999 05:56:04 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id PAA95407; Sat, 3 Apr 1999 15:54:07 +0200 (CEST) (envelope-from des) To: Ladavac Marino Cc: "'Soren Schmidt'" , sobomax@altavista.net, current@FreeBSD.ORG Subject: Re: UPDATE4: ATA/ATAPI driver new version available. References: <97A8CA5BF490D211A94F0000F6C2E55D097577@s-lmh-wi-900.corpnet.at> From: Dag-Erling Smorgrav Date: 03 Apr 1999 15:54:06 +0200 In-Reply-To: Ladavac Marino's message of "Tue, 30 Mar 1999 13:39:53 +0200" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ladavac Marino writes: > [ML] Also, is there any swapping area on that slice? Because > if there is and kernel has been told to use it (AFAIR swapon happens > even in single user mode) Not unless you run it manually. > you have just obliterated the kernel pages > (kernel is pageable these days IIRC, at least the data if not the code). It's not, as far as I know. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 6: 2:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 5BE1014DC0 for ; Sat, 3 Apr 1999 06:02:07 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id QAA75576; Sat, 3 Apr 1999 16:00:11 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id QAA39661; Sat, 3 Apr 1999 16:00:10 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904031400.QAA39661@greenpeace.grondar.za> To: Anders Andersson Cc: freebsd-current@freebsd.org Subject: Re: DES from source? In-Reply-To: Your message of " Sat, 03 Apr 1999 12:22:21 +0200." <19990403122221.A12230@sanyusan.se> References: <19990403122221.A12230@sanyusan.se> Date: Sat, 03 Apr 1999 16:00:09 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anders Andersson wrote: > I am looking for the correct way of installing DES (crypt) from sources. Nothing to do, except for... > From the beginning I install most of my boxes from ftp and with the > "minimal" option. After that I cvsup and do make world to fit my needs. > > On this test box I run 4.0-CURRENT and have cvsupped the: > > # The international secure collections. > src-crypto > src-eBones > src-secure ...this. > I plan to do 'make world' and from what I can tell I need to: > > ln -fs libdescrypt.so libcrypt.so > ln -fs libdescrypt.so.2 libcrypt.so.2 > ln -fs libdescrypt.a libcrypt.a > > after make world to use DES (crypt). This should happen automagically. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 6:20:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 8E06D14DC0 for ; Sat, 3 Apr 1999 06:20:25 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: from [194.222.242.30] (helo=extremis.demon.co.uk) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 10TRFj-0003fu-0A for freebsd-current@freebsd.org; Sat, 3 Apr 1999 14:18:29 +0000 Received: (from gjvc@localhost) by extremis.demon.co.uk (8.9.3/8.9.1) id PAA79867 for freebsd-current@freebsd.org; Sat, 3 Apr 1999 15:18:36 GMT (envelope-from gjvc) Date: Sat, 3 Apr 1999 15:18:36 +0000 From: George Cox To: freebsd-current@freebsd.org Subject: Headers changed? Message-ID: <19990403151836.A79776@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it goes like this: I cvsupped to CURRENT from 3.1 some time ago (like a month or something) and everything was going great. Friday night I cvsupped and tried to make world, but without success -- yacc complained during something in cc1. Anyhoo, I then successfully did a make world -DNOTOOLS, and the result is somewhat suboptimal, in that "Hello world" does not compile, and I can't make world at the moment. Are these changes related to the introduction of egcs? Any help gratefully received! (Including telling me if this is the wrong place to ask) gcc output follows. In file included from /usr/include/stdio.h:44, from hw.c:1: /usr/include/machine/ansi.h:103: syntax error before `__attribute__' /usr/include/machine/ansi.h:104: syntax error before `__attribute__' In file included from hw.c:1: /usr/include/stdio.h:55: syntax error before `fpos_t' gcc: Internal compiler error: program cc1 got fatal signal 11 -- [gjvc] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 6:48:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B6FE314D01; Sat, 3 Apr 1999 06:48:44 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA71904; Sat, 3 Apr 1999 15:48:27 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 3 Apr 1999 15:48:27 +0100 (BST) From: Doug Rabson To: "John S. Dyson" Cc: Alan Cox , current@freebsd.org, luoqi@freebsd.org Subject: Re: SMP users (important) In-Reply-To: <199904031316.IAA45781@y.dyson.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, John S. Dyson wrote: > Alan Cox said: > > > > I've committed the basic infrastructure to improve TLB management > > on SMPs. Translation: this will lead to the elimination of a LOT > > of interprocessor interrupts to invalidate TLB entries. I'll be > > "turning on" the new mechanisms slowly so we can carefully debug > > each step and (hopefully) avoid any problems. > > > (To the rest of the team, Alan and Luoqi already know my opinion.) > > I just wanted to "chime in" and say that the new patches are based > on a really good concept, and is much cleaner than the previous > method. Also, many RISC architectures can utilize this > method due to the availability of lots of general registers. > (One could go so far as to have the compiler reserve the > register.) Non-threaded user mode apps could optionally > use the reserved register, but for threaded user mode apps, > that reserved register could also be used as a per-thread > base pointer. > > I believe that NT does the above (%fs for X86, and general > register for Alpha.) On PPC, there are several local, > per-processor registers that one could use (but loading a > general register with that per processor register would be > needed for access.) Also, since the PPC has lots of registers, > one could? permanently reserve one of the general registers (r13?). > > All in all, this change has the potential for better context > switching time (and less memory/better performance for multi-threaded > processes.) This is a serious, non-trivial movement in the *right* > direction!!! :-). SMP users should be pleased with this movement (I > certainly am!!!) The alpha palcode supports a per-thread unique value which can be used by any threading system (user or kernel). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 7:36: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3236614CBF for ; Sat, 3 Apr 1999 07:36:03 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id RAA96596; Sat, 3 Apr 1999 17:34:06 +0200 (CEST) (envelope-from des) To: Anders Andersson Cc: freebsd-current@FreeBSD.ORG Subject: Re: DES from source? References: <19990403122221.A12230@sanyusan.se> From: Dag-Erling Smorgrav Date: 03 Apr 1999 17:34:06 +0200 In-Reply-To: Anders Andersson's message of "Sat, 3 Apr 1999 12:22:21 +0200" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Synker! Anders Andersson writes: > I am looking for the correct way of installing DES (crypt) from sources. *grumble* why do people keep wanting to install me? ;) > I plan to do 'make world' and from what I can tell I need to: > > ln -fs libdescrypt.so libcrypt.so > ln -fs libdescrypt.so.2 libcrypt.so.2 > ln -fs libdescrypt.a libcrypt.a # cd /usr/src # for f in libdescrypt* ; do ln -fs $f $(echo $f | sed s/des//) ; done > Do I need to change all passwd with 'passwd {user}' to use DES passwd crypt? Existing MD5 passwords will still work. New users will get DES passwords. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 7:52:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id E3D5914C8B for ; Sat, 3 Apr 1999 07:52:12 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.2/8.9.1) with SMTP id PAA74709 for ; Sat, 3 Apr 1999 15:47:12 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19990403074908.00977100@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 03 Apr 1999 07:49:08 -0800 To: freebsd-current@freebsd.org From: "Kurt D. Zeilenga" Subject: GNU regex (Was: egcs knob and objective C) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:32 PM 4/2/99 -0600, Jacques Vidrine wrote: >On 2 April 1999 at 22:25, Doug Rabson wrote: >> We should also consider installing libbfd. If and when we bring in a newer >> version of gdb, it would be a good idea to avoid importing yet another >> version of libiberty and libbfd. > >... and GNU regex. If you mean a version of regex included in the LGPL'ed libc, yes, then this point might be mute. However, if you mean the regex/rx distributions, please, no. GNU regex and GNU rx distributions are both under the GPL. Henry Spencer's regex has a promiscious license. Even if a LGPL'ed distribution was available, I wouldn't recommend switching without a significant and demonstrated technical advantage. I've found that each implementation is even with the others. I would suggest GNU regex be made ports unless some base application required the -lgnuregex. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 7:54:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1DAD214D25 for ; Sat, 3 Apr 1999 07:54:51 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id RAA16913 for freebsd-current@FreeBSD.ORG; Sat, 3 Apr 1999 17:52:55 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 1EA198848; Sat, 3 Apr 1999 17:46:30 +0200 (CEST) Date: Sat, 3 Apr 1999 17:46:30 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: -Werrors in CFLAGS ? Message-ID: <19990403174630.A80637@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is "make world" showing these just now ? cc -fpic -DPIC -g -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/src/src/lib/libskey -W -Wall -Werror -I/usr/obj/src/src/tmp/usr/include -c /src/src/lib/libskey/skey_getpass.c -o skey_getpass.So cc1: warnings being treated as errors /usr/obj/src/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used cc1: warnings being treated as errors /usr/obj/src/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used *** Error code 1 *** Error code 1 cc1: warnings being treated as errors /usr/obj/src/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used *** Error code 1 I'm at cvs-cur #5203 made on 1999/04/02 16:24:18. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 8: 0:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 51B4514C8B for ; Sat, 3 Apr 1999 08:00:21 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id CAA03905; Sun, 4 Apr 1999 02:01:11 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma003900; Sun, 4 Apr 99 02:00:54 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id BAA25541 for ; Sun, 4 Apr 1999 01:57:53 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id BAA00295 for ; Sun, 4 Apr 1999 01:57:52 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id BAA03125; Sun, 4 Apr 1999 01:57:50 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199904031557.BAA03125@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Fatal trap 1: privileged instruction fault while in kernel mode Date: Sun, 04 Apr 1999 01:57:50 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just got what seems an unlikely panic. How could I get a privileged instruction fault while in kernel mode? This is from a week old 4.0-current kernel on a 16Mb 486. It has an AHA1542CF a slow SCSI-1 disk, and a rebadged TDC4200 (2GB QIC). I run soft updates but nothing else fancy. I was doing a make buildworld, and rewinding a tape at the time. It seemed like the panic occurred when the tape stopped, but I wasn't actually watching at the time. The fatal instruction is: 0xc016abc9 : movl $0xc023355c,0xffffffdc(%ebp) which looks pretty ordinary. Can this be a software bug? Or has my hardware gone funny? It has done a good number of make worlds in the last few months with only the normal (software) troubles you expect from -current. Stephen. Here are the gory bits, in case anyone can offer any hints: IdlePTD 2834432 initial pcb at 248774 panicstr: from debugger panic messages: --- Fatal trap 1: privileged instruction fault while in kernel mode instruction pointer = 0x8:0xc016abc9 stack pointer = 0x10:0xc30a6c20 frame pointer = 0x10:0xc30a6c54 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 = 12245 (sh) interrupt mask = bio panic: from debugger panic: from debugger dumping to dev 30401, offset 163840 dump 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:287 #1 0xc0148095 in panic (fmt=0xc021bda8 "from debugger") at ../../kern/kern_shutdown.c:448 #2 0xc0129575 in db_panic (addr=-1072256055, have_addr=0, count=-1, modif=0xc30a6acc "") at ../../ddb/db_command.c:432 #3 0xc0129515 in db_command (last_cmdp=0xc023558c, cmd_table=0xc02353ec, aux_cmd_tablep=0xc0245f8c) at ../../ddb/db_command.c:332 #4 0xc01295da in db_command_loop () at ../../ddb/db_command.c:454 #5 0xc012b95b in db_trap (type=1, code=0) at ../../ddb/db_trap.c:71 #6 0xc01f9bea in kdb_trap (type=1, code=0, regs=0xc30a6be4) at ../../i386/i386/db_interface.c:157 #7 0xc0203a00 in trap_fatal (frame=0xc30a6be4, eva=0) at ../../i386/i386/trap.c:938 #8 0xc02034b0 in trap (frame={tf_es = 16, tf_ds = -1023541232, tf_edi = -1023478144, tf_esi = 0, tf_ebp = -1022727084, tf_isp = -1022727156, tf_ebx = -1024550784, tf_edx = 12245, tf_ecx = -1023478144, tf_eax = 0, tf_trapno = 1, tf_err = 0, tf_eip = -1072256055, tf_cs = -1072300024, tf_eflags = 66194, tf_esp = -1024550784, tf_ss = -1024177152}) at ../../i386/i386/trap.c:586 #9 0xc016abc9 in vclean (vp=0xc2ee9880, flags=8, p=0xc2fef680) at vnode_if.h:835 #10 0xc016adb7 in vgonel (vp=0xc2ee9880, p=0xc2fef680) at ../../kern/vfs_subr.c:1830 #11 0xc01698b1 in getnewvnode (tag=VT_UFS, mp=0xc05c5e00, vops=0xc05aa000, vpp=0xc30a6d04) at ../../kern/vfs_subr.c:467 #12 0xc01d4e69 in ffs_vget (mp=0xc05c5e00, ino=20442, vpp=0xc30a6d84) at ../../ufs/ffs/ffs_vfsops.c:1082 #13 0xc01d8b1a in ufs_lookup (ap=0xc30a6ddc) at ../../ufs/ufs/ufs_lookup.c:538 #14 0xc01dd38d in ufs_vnoperate (ap=0xc30a6ddc) at ../../ufs/ufs/ufs_vnops.c:2309 #15 0xc0166978 in vfs_cache_lookup (ap=0xc30a6e38) at vnode_if.h:55 #16 0xc01dd38d in ufs_vnoperate (ap=0xc30a6e38) at ../../ufs/ufs/ufs_vnops.c:2309 #17 0xc0168dc1 in lookup (ndp=0xc30a6eb8) at vnode_if.h:31 #18 0xc0168894 in namei (ndp=0xc30a6eb8) at ../../kern/vfs_lookup.c:152 #19 0xc016e124 in stat (p=0xc2fef680, uap=0xc30a6f94) at ../../kern/vfs_syscalls.c:1651 #20 0xc0203c83 in syscall (frame={tf_es = 134873135, tf_ds = -1078001617, tf_edi = 0, tf_esi = 134890328, tf_ebp = -1077946844, tf_isp = -1022726172, tf_ebx = 134890372, tf_edx = -1077946944, tf_ecx = 134890388, tf_eax = 188, tf_trapno = 22, tf_err = 2, tf_eip = 134656096, tf_cs = 31, tf_eflags = 518, tf_esp = -1077946968, tf_ss = 47}) at ../../i386/i386/trap.c:1101 #21 0xc01fa53c in Xint0x80_syscall () #22 0x804b5f1 in ?? () #23 0x804a879 in ?? () #24 0x804a7f3 in ?? () #25 0x804a7f3 in ?? () #26 0x804a6fe in ?? () #27 0x804a7f3 in ?? () #28 0x804ab8a in ?? () #29 0x804a7ab in ?? () #30 0x804aa23 in ?? () #31 0x804a812 in ?? () #32 0x8051257 in ?? () #33 0x8051183 in ?? () #34 0x80480e9 in ?? () (kgdb) The End. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 8:44: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32]) by hub.freebsd.org (Postfix) with ESMTP id D496914A12 for ; Sat, 3 Apr 1999 08:44:01 -0800 (PST) (envelope-from myself@conterra.com) Received: from dmaddox.conterra.com (myself@dmaddox.conterra.com [209.12.169.48]) by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id LAA13232 for ; Sat, 3 Apr 1999 11:42:04 -0500 (EST) Received: (from myself@localhost) by dmaddox.conterra.com (8.9.3/8.9.1) id LAA00728 for current@FreeBSD.ORG; Sat, 3 Apr 1999 11:42:23 -0500 (EST) (envelope-from myself) Date: Sat, 3 Apr 1999 11:42:23 -0500 From: "Donald J . Maddox" To: current@FreeBSD.ORG Subject: AWE broken by recent commits to i386/isa/sound files? Message-ID: <19990403114223.A707@dmaddox.conterra.com> Reply-To: dmaddox@conterra.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a 'make world' last night, everytime I use any of the AWE utilities (as ported by Randall Hopper) I get this: AWE32: unsupported ioctl -1064546046 AWE32: unsupported ioctl -1064546046 I remember seeing a couple of commits to some of the files in sys/i386/isa/sound, but I don't remember exactly which files were changed... Is it possible that these changes broke AWE support? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 8:52: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id A354A14C90 for ; Sat, 3 Apr 1999 08:52:04 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id KAA15888 for ; Sat, 3 Apr 1999 10:50:09 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma015880; Sat, 3 Apr 99 10:49:55 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id KAA84516 for ; Sat, 3 Apr 1999 10:49:07 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199904031649.KAA84516@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: lists/freebsd X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine In-reply-to: <3.0.5.32.19990403074908.00977100@localhost> References: <3.0.5.32.19990403074908.00977100@localhost> Subject: Re: GNU regex (Was: egcs knob and objective C) Mime-Version: 1.0 Content-Type: text/plain To: freebsd-current@FreeBSD.ORG Date: Sat, 03 Apr 1999 10:49:07 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 April 1999 at 7:49, "Kurt D. Zeilenga" wrote: [snip] > If you mean a version of regex included in the LGPL'ed libc, > yes, then this point might be mute. However, if you mean > the regex/rx distributions, please, no. We're talking about gdb, so I mean the GNU regex implementation that is distributed as part of gdb. [snip] > I would suggest GNU regex be made ports unless some base > application required the -lgnuregex. As much as I would like to see us shipping only one regex implementation, and a BSD-style licensed one at that, some base applications require GNU regex, notably those found under src/gnu. However, as we import new things (a new GDB, a new CVS) perhaps we can try to drop the regex implementations that come with those, and use one that is already in the system. Then again, perhaps not. No telling what subtle bugs could be created by changing the regex implementation used in complex applications such as CVS. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 9:52:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 82F5E14F4D for ; Sat, 3 Apr 1999 09:52:10 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id TAA28786 for ; Sat, 3 Apr 1999 19:50:13 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id TAA55995 for current@FreeBSD.ORG; Sat, 3 Apr 1999 19:36:33 +0200 (CEST) (envelope-from andreas) Date: Sat, 3 Apr 1999 19:36:33 +0200 From: Andreas Klemm To: current@FreeBSD.ORG Subject: X problems using egcs as compiler Message-ID: <19990403193632.A55975@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Got the latest egcs port # $Id: Makefile,v 1.53 1999/03/30 02:58:02 obrien Exp $ Build X11R6 with the following CFLAGS: -pipe -mpentiumpro -O2 I'm still running X11 and after ,make install' I'm unable to launch x applications (xterm, ...) andreas@titan{1001} $ xterm /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXaw.so.6: Undefined symbol "__deregister_frame_info" Exit 1 Is this a problem with egcs ? Or did I overlook something ? My freebsd 3.1-STABLE kernel, compiled with -pipe -O2 -mpentiumpro, runs fine since half a day. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 9:53:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id A359B14F4D for ; Sat, 3 Apr 1999 09:53:23 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem12.masternet.it [194.184.65.22]) by kirk.giovannelli.it (8.9.2/8.9.2) with SMTP id RAA10359 for ; Sat, 3 Apr 1999 17:51:04 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990403194903.00988100@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 03 Apr 1999 19:52:07 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: make world is broken ... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The make world (4.0-current) broke yesterday and after a day of cvsupping is still broke ... I can't send the output but it stopped in the libc I presume ... Please check... Happy Easter to everybody (also to whom broke world :-)) Thanks for attention Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 10: 0: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 5CE4E14F4D for ; Sat, 3 Apr 1999 09:59:56 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id LAA14632; Sat, 3 Apr 1999 11:57:58 -0600 (CST) Date: Sat, 3 Apr 1999 11:57:58 -0600 (CST) From: Steve Price To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-Reply-To: <19990403193632.A55975@titan.klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien forwarded me a message a couple of days ago that contains a fix that may help. You need to add the following line at line 301 in target.make -u __deregister_frame_info \ -steve On Sat, 3 Apr 1999, Andreas Klemm wrote: # Got the latest egcs port # # # $Id: Makefile,v 1.53 1999/03/30 02:58:02 obrien Exp $ # # Build X11R6 with the following CFLAGS: # # -pipe -mpentiumpro -O2 # # I'm still running X11 and after ,make install' I'm unable # to launch x applications (xterm, ...) # # andreas@titan{1001} $ xterm # /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXaw.so.6: Undefined symbol "__deregister_frame_info" # Exit 1 # # Is this a problem with egcs ? Or did I overlook something ? # # My freebsd 3.1-STABLE kernel, compiled with -pipe -O2 -mpentiumpro, # runs fine since half a day. # # -- # Andreas Klemm http://www.FreeBSD.ORG/~andreas # http://www.freebsd.org/~fsmp/SMP/SMP.html # powered by Symmetric MultiProcessor FreeBSD # # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-current" in the body of the message # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 10:49: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 57BB914CFC for ; Sat, 3 Apr 1999 10:49:04 -0800 (PST) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 9046 invoked from network); 3 Apr 1999 18:47:08 -0000 Received: from userag37.uk.uudial.com (HELO k2c.co.uk) (62.188.132.123) by smtp.dial.pipex.com with SMTP; 3 Apr 1999 18:47:08 -0000 Message-ID: <370661A9.1CD05919@k2c.co.uk> Date: Sat, 03 Apr 1999 19:44:57 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: CVS-all mailing list problems? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know this is the -current list, but... I haven't received a single message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup just gave me a loads of commits today... this does not seem to be a local issue, since I receive -current normally (or so it seems, at least). Any clues? PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 11:18: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 82F8514E16 for ; Sat, 3 Apr 1999 11:18:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id LAA56145; Sat, 3 Apr 1999 11:14:43 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904031914.LAA56145@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Price Cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-reply-to: Your message of "Sat, 03 Apr 1999 11:57:58 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Apr 1999 11:14:43 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, it probably means that the program must be compiled with "-fexecptions". Here is a little clue: from egcs-1.1.2: ./gcc/frame.c:/* Called from crtbegin.o to deregister the unwind info for an object. */ ./gcc/frame.c:__deregister_frame_info (void *begin) ./gcc/frame.c:__deregister_frame (void *begin) ./gcc/frame.c: free (__deregister_frame_info (begin)); Just tried to compile apache and apache's jserv and got hit by the above bug so I hope that this gets resolved prior to using egcs as the default. Amancio > David O'Brien forwarded me a message a couple of days ago that > contains a fix that may help. You need to add the following > line at line 301 in target.make > > -u __deregister_frame_info \ > > -steve > > On Sat, 3 Apr 1999, Andreas Klemm wrote: > > # Got the latest egcs port > # > # # $Id: Makefile,v 1.53 1999/03/30 02:58:02 obrien Exp $ > # > # Build X11R6 with the following CFLAGS: > # > # -pipe -mpentiumpro -O2 > # > # I'm still running X11 and after ,make install' I'm unable > # to launch x applications (xterm, ...) > # > # andreas@titan{1001} $ xterm > # /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXaw.so.6: Undefined symbol "__deregister_frame_info" > # Exit 1 > # > # Is this a problem with egcs ? Or did I overlook something ? > # > # My freebsd 3.1-STABLE kernel, compiled with -pipe -O2 -mpentiumpro, > # runs fine since half a day. > # > # -- > # Andreas Klemm http://www.FreeBSD.ORG/~andreas > # http://www.freebsd.org/~fsmp/SMP/SMP.html > # powered by Symmetric MultiProcessor FreeBSD > # > # > # To Unsubscribe: send mail to majordomo@FreeBSD.org > # with "unsubscribe freebsd-current" in the body of the message > # > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 11:22:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 80A4414E16 for ; Sat, 3 Apr 1999 11:22:43 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA34318; Sat, 3 Apr 1999 14:19:08 -0500 (EST) Date: Sat, 3 Apr 1999 14:19:08 -0500 (EST) From: Chuck Robey To: "Pierre Y. Dampure" Cc: current@FreeBSD.ORG Subject: Re: CVS-all mailing list problems? In-Reply-To: <370661A9.1CD05919@k2c.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Pierre Y. Dampure wrote: > > I know this is the -current list, but... I haven't received a single > message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup > just gave me a loads of commits today... this does not seem to be a > local issue, since I receive -current normally (or so it seems, at > least). > > Any clues? Yeah, heavy maint on hub last night, moving it to 3.1. Much breakage, not all made up for yet. They didn't go to sleep until it was in useable shape (nice guys) so let 'em sleep a little more before raising a ruckus. It'll come back. I'm waiting some repairs myself. > > PYD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 11:24: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3CEC314E16 for ; Sat, 3 Apr 1999 11:23:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA21228; Sat, 3 Apr 1999 11:21:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: REM Cc: current@FreeBSD.ORG Subject: Re: Error during compile EGCS In-reply-to: Your message of "Sat, 03 Apr 1999 16:37:56 +0400." Date: Sat, 03 Apr 1999 11:21:29 -0800 Message-ID: <21226.923167289@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I made two steps in /usr/src/contrib/egsc > # ./configure Don't do that - that isn't how egcs or anything else in /usr/src/contrib is supposed to be used and you appear to be fundamentally confused about the sources, so much so that I wouldn't suggest attempting to build anything from them until you've taken more time to study the build mechanism. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 11:32:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B576514F4D for ; Sat, 3 Apr 1999 11:32:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id LAA16845; Sat, 3 Apr 1999 11:29:47 -0800 Date: Sat, 3 Apr 1999 11:29:46 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Chuck Robey Cc: "Pierre Y. Dampure" , current@FreeBSD.ORG Subject: Re: CVS-all mailing list problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Chuck Robey wrote: > On Sat, 3 Apr 1999, Pierre Y. Dampure wrote: > > > > > I know this is the -current list, but... I haven't received a single > > message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup > > just gave me a loads of commits today... this does not seem to be a > > local issue, since I receive -current normally (or so it seems, at > > least). > > > > Any clues? > > Yeah, heavy maint on hub last night, moving it to 3.1. Much breakage, > not all made up for yet. They didn't go to sleep until it was in > useable shape (nice guys) so let 'em sleep a little more before raising > a ruckus. It'll come back. I'm waiting some repairs myself. > Yes, and: feral.com > ping freefall.freebsd.org PING freefall.freebsd.org (204.216.27.21): 56 data bytes feral.com > traceroute freefall.freebsd.org traceroute to freefall.freebsd.org (204.216.27.21), 30 hops max, 40 byte packets 1 goblo (192.67.166.126) 0.889 ms 0.836 ms 0.814 ms 2 lm2feral.dsl.lmi.net (208.25.75.25) 23.746 ms 29.699 ms 29.732 ms 3 incaroads.lanminds.com (140.174.208.210) 24.258 ms 25.777 ms 23.455 ms 4 207.238.136.57 (207.238.136.57) 33.077 ms 36.649 ms 29.455 ms 5 sjc1-core1-fa5-1-0.atlas.digex.net (165.117.50.145) 23.774 ms 25.707 ms 24.509 ms 6 sjc2-core2-h4-0-0.atlas.digex.net (165.117.50.45) 35.657 ms 30.942 ms 24.629 ms 7 mae-west1.US.CRL.NET (198.32.136.10) 31.125 ms 30.113 ms 28.640 ms 8 sfo-ames.1.gw3.us.crl.net (165.113.50.41) 33.651 ms 32.090 ms 34.386 ms 9 T1-CDROM-00-EX.US.CRL.NET (165.113.118.2) 54.947 ms 39.097 ms 46.532 ms 10 * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 11:53:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6540814C34 for ; Sat, 3 Apr 1999 11:53:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA72966; Sat, 3 Apr 1999 11:51:54 -0800 (PST) (envelope-from obrien) Message-ID: <19990403115154.A72956@nuxi.com> Date: Sat, 3 Apr 1999 11:51:54 -0800 From: "David O'Brien" To: Andreas Klemm , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Reply-To: obrien@NUXI.com References: <19990403193632.A55975@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990403193632.A55975@titan.klemm.gtn.com>; from Andreas Klemm on Sat, Apr 03, 1999 at 07:36:33PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > andreas@titan{1001} $ xterm > /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXaw.so.6: Undefined symbol "__deregister_frame_info" > Exit 1 > > Is this a problem with egcs ? Or did I overlook something ? Please recompile everything you did with the "-v" option, and send the output. You may easily be linking with the wrong crt*.o or *.a files. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 11:58:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1495A14E67 for ; Sat, 3 Apr 1999 11:58:28 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA72994; Sat, 3 Apr 1999 11:56:32 -0800 (PST) (envelope-from obrien) Message-ID: <19990403115632.B72956@nuxi.com> Date: Sat, 3 Apr 1999 11:56:32 -0800 From: "David O'Brien" To: Amancio Hasty , Steve Price Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Reply-To: obrien@NUXI.com References: <199904031914.LAA56145@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904031914.LAA56145@rah.star-gate.com>; from Amancio Hasty on Sat, Apr 03, 1999 at 11:14:43AM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just tried to compile apache and apache's jserv and got hit by the > above bug so I hope that this gets resolved prior to using egcs as the > default. I doubt it will. I expect there will be significant breakage of non-world after the commit. I've significantly tested kernel and world, but I haven't tried ports at all. People may be well advised to CVSup and `make world' (or don't CVSup again for a while) sometime before Sunday California PDT time (-7hrs Zulu). The rockiness of -CURRENT is about to be upon us. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 12: 2:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3390E14C34 for ; Sat, 3 Apr 1999 12:02:14 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA73027; Sat, 3 Apr 1999 12:00:12 -0800 (PST) (envelope-from obrien) Message-ID: <19990403120012.C72956@nuxi.com> Date: Sat, 3 Apr 1999 12:00:12 -0800 From: "David O'Brien" To: George Cox , freebsd-current@FreeBSD.ORG Subject: Re: Headers changed? Reply-To: obrien@NUXI.com References: <19990403151836.A79776@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990403151836.A79776@extremis.demon.co.uk>; from George Cox on Sat, Apr 03, 1999 at 03:18:36PM +0000 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Hello world" does not compile, and I can't make world at the moment. > Are these changes related to the introduction of egcs? No. No EGCS-only changes have been made to the base system yet. The somewhat EGCS-related change I've made so far fixed breakage in `make world' in that the wrong compiler was building libgcc.a. We were using the base compiler, rather than the one built in `make world'. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 12: 4:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1BEFC14C34 for ; Sat, 3 Apr 1999 12:04:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA21417; Sat, 3 Apr 1999 12:02:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: Chuck Robey , "Pierre Y. Dampure" , current@FreeBSD.ORG Subject: Re: CVS-all mailing list problems? In-reply-to: Your message of "Sat, 03 Apr 1999 11:29:46 PST." Date: Sat, 03 Apr 1999 12:02:30 -0800 Message-ID: <21415.923169750@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, and: > > feral.com > ping freefall.freebsd.org Separate problem - we're working on it. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 13: 9:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id D7D9C14BD6 for ; Sat, 3 Apr 1999 13:09:11 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.2/8.9.1) with SMTP id VAA77528; Sat, 3 Apr 1999 21:04:12 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19990403130603.009991b0@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 03 Apr 1999 13:06:03 -0800 To: Jacques Vidrine From: "Kurt D. Zeilenga" Subject: Re: GNU regex (Was: egcs knob and objective C) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199904031649.KAA84516@spawn.nectar.com> References: <3.0.5.32.19990403074908.00977100@localhost> <3.0.5.32.19990403074908.00977100@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:49 AM 4/3/99 -0600, Jacques Vidrine wrote: >On 3 April 1999 at 7:49, "Kurt D. Zeilenga" wrote: >[snip] >> If you mean a version of regex included in the LGPL'ed libc, >> yes, then this point might be mute. However, if you mean >> the regex/rx distributions, please, no. >We're talking about gdb, so I mean the GNU regex implementation >that is distributed as part of gdb. Thanks for clarification. I have no issue with how regex is used within base applications, only with base libraries that place redistribution restrictions upon linked software. BTW, does anyone have a list of which libraries in the FreeBSD base system which place redistribution restrictions (such as those within the GPL) upon linked software? Please respond directly, I'll compile responses and post a summary. -- Kurt OpenLDAP - powered by FreeBSD! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 13:18:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 13CF514BD6 for ; Sat, 3 Apr 1999 13:18:31 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id PAA10691; Sat, 3 Apr 1999 15:16:30 -0600 (CST) Date: Sat, 3 Apr 1999 15:16:30 -0600 (CST) From: Steve Price To: "David O'Brien" Cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-Reply-To: <19990403115632.B72956@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, David O'Brien wrote: # > Just tried to compile apache and apache's jserv and got hit by the # > above bug so I hope that this gets resolved prior to using egcs as the # > default. # # I doubt it will. Me too. :/ # I expect there will be significant breakage of non-world after the # commit. I've significantly tested kernel and world, but I haven't tried # ports at all. I got everything setup to build the entire ports collection and sometime during the night the big IDE disk that I keep all the distfiles and packages on went south. :( It had been acting funny lately. I think it finally decided it had seen enough. I'm off to the store to pick up another and then by work where I have a T1 to grab all the distfiles that are not on the 3.1 CDs. I sure hope Satoshi is following this because it doesn't look like I'm going to be able to get very far before the switch is thrown. In fact now is probably a good time to post something to the ports mailing list. I'll send out something brief before I head off to the store. # People may be well advised to CVSup and `make world' (or don't CVSup # again for a while) sometime before Sunday California PDT time (-7hrs # Zulu). # # The rockiness of -CURRENT is about to be upon us. Committers brush up on your edit-pr skills, we're in for a load of fun in the following weeks. -steve # -- # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 13:34:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 5C9F814DBD for ; Sat, 3 Apr 1999 13:34:25 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA02242; Sat, 3 Apr 1999 23:32:20 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 3001F8848; Sat, 3 Apr 1999 22:51:47 +0200 (CEST) Date: Sat, 3 Apr 1999 22:51:47 +0200 From: Ollivier Robert To: Amancio Hasty Cc: Steve Price , Andreas Klemm , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Message-ID: <19990403225146.A99040@keltia.freenix.fr> Mail-Followup-To: Amancio Hasty , Steve Price , Andreas Klemm , current@FreeBSD.ORG References: <199904031914.LAA56145@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <199904031914.LAA56145@rah.star-gate.com>; from Amancio Hasty on Sat, Apr 03, 1999 at 11:14:43AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Amancio Hasty: > Actually, it probably means that the program must be compiled with > "-fexecptions". The problem is that egcs 1.1.2 has its own crt*.o files and use them in place of the FreeBSD one. By moving the files elsewhere, it works. I don't know the effect on exceptions though. I tumbled in this problem when compiling Perl 5.005_03 with egcs and moving the files away "solved" the problem. I don't know what David plan to do with these crt*.o files. David ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 13:48:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id D3A2B14E58 for ; Sat, 3 Apr 1999 13:48:32 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id XAA03702; Sat, 3 Apr 1999 23:46:33 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id XAA29101; Sat, 3 Apr 1999 23:46:15 +0200 (CEST) (envelope-from andreas) Date: Sat, 3 Apr 1999 23:46:14 +0200 From: Andreas Klemm To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Message-ID: <19990403234614.A28774@titan.klemm.gtn.com> References: <19990403193632.A55975@titan.klemm.gtn.com> <19990403115154.A72956@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990403115154.A72956@nuxi.com>; from David O'Brien on Sat, Apr 03, 1999 at 11:51:54AM -0800 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 03, 1999 at 11:51:54AM -0800, David O'Brien wrote: > > andreas@titan{1001} $ xterm > > /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXaw.so.6: Undefined symbol "__deregister_frame_info" > > Exit 1 > > > > Is this a problem with egcs ? Or did I overlook something ? > > Please recompile everything you did with the "-v" option, and send the > output. You may easily be linking with the wrong crt*.o or *.a files. Some output from building something in xterm subdir of XFree86 making all in programs/xterm... /usr/local/bin/egcc -v -pipe -mpentiumpro -O2 -ansi -pedantic -Dasm=__asm -I. ./.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -I. -DSCROLLBAR_RIGHT -c resize.c Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/s pecs gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/cpp -lang-c89 -v -I ../.. -I../../exports/include -I. -undef -D__GNUC__=2 -D__GNUC_MINOR__=91 -trigr aphs -D__STRICT_ANSI__ -D__i386__ -D__ELF__ -D__unix__ -D__FreeBSD__=3 -D__i386 -D__unix -Acpu(i386) -Amachine(i386) -Asystem(unix) -Asystem(FreeBSD) -D__OPTIMI ZE__ -pedantic -Asystem(unix) -Acpu(i386) -Amachine(i386) -D__i386 -D__i386__ -D __i686 -D__i686__ -D__pentiumpro -D__pentiumpro__ -Dasm=__asm -DCSRG_BASED -DFUN CPROTO=15 -DNARROWPROTO -DSCROLLBAR_RIGHT resize.c | /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/cc1 -quiet -dumpbas e resize.c -mpentiumpro -ansi -O2 -pedantic -ansi -version -o - | as -V -Qy -o resize.o - GNU CPP version egcs-2.91.66 19990314 (egcs-1.1.2 release) (i386 FreeBSD/ELF) #include "..." search starts here: GNU C version egcs-2.91.66 19990314 (egcs-1.1.2 release)#include <...> search st arts here: (i386-portbld-freebsd3.1)GNU assembler version 2.9.1 (i386-unknown-freebsdelf) ../.. compiled by GNU C version egcs-2.91.66 19990314 (egcs-1.1.2 release). ../../exports/include . /usr/local/include /usr/local/i386-portbld-freebsd3.1/include /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/include /usr/include End of search list. , using BFD version 2.9.1 rm -f resize /usr/local/bin/egcc -o resize -v -pipe -mpentiumpro -O2 -ansi -pedantic -Dasm=__ asm -L../../exports/lib resize.o -L/usr/X11R6/lib -lxpg4 -lrpcsvc -lkrb -ldes -lcrypt -ltermcap -Wl,-rpath,/usr/X11R6/lib Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/s pecs gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/collect2 -m elf_i38 6 -dynamic-linker /usr/libexec/ld-elf.so.1 -o resize /usr/lib/crt1.o /usr/lib/cr ti.o /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/crtbegin.o -L.. /../exports/lib -L/usr/X11R6/lib -L/usr/local/lib/gcc-lib/i386-portbld-freebsd3. 1/egcs-2.91.66 -L/usr/local/i386-portbld-freebsd3.1/lib -L/usr/local/lib resize. o -lxpg4 -lrpcsvc -lkrb -ldes -lcrypt -ltermcap -rpath /usr/X11R6/lib -lgcc -lc -lgcc /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/crtend.o /usr/ lib/crtn.o -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 13:49:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-3.ppp.wenet.net [206.15.85.3]) by hub.freebsd.org (Postfix) with ESMTP id B7DF214F32 for ; Sat, 3 Apr 1999 13:49:52 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id NAA11947; Sat, 3 Apr 1999 13:47:11 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 3 Apr 1999 13:47:11 -0800 (PST) From: Alex Zepeda To: Ollivier Robert Cc: Amancio Hasty , Steve Price , Andreas Klemm , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-Reply-To: <19990403225146.A99040@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Ollivier Robert wrote: > According to Amancio Hasty: > > Actually, it probably means that the program must be compiled with > > "-fexecptions". > > The problem is that egcs 1.1.2 has its own crt*.o files and use them in > place of the FreeBSD one. By moving the files elsewhere, it works. I don't > know the effect on exceptions though. > > I tumbled in this problem when compiling Perl 5.005_03 with egcs and moving > the files away "solved" the problem. > > I don't know what David plan to do with these crt*.o files. David ? Personally, I'd vote for using the new runtime objects, and forcing binary incompatibility. It's worth it IMO for the exception handling support if nothing else. However, if you're dead set against it, just back up your runtime objects, and edit the spec file (like the egcs port forced you to do at one time, and probably still does). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 14: 0:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8B78414F78 for ; Sat, 3 Apr 1999 14:00:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA73310; Sat, 3 Apr 1999 13:58:17 -0800 (PST) (envelope-from obrien) Message-ID: <19990403135817.A73304@nuxi.com> Date: Sat, 3 Apr 1999 13:58:17 -0800 From: "David O'Brien" To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Reply-To: obrien@NUXI.com References: <19990403193632.A55975@titan.klemm.gtn.com> <19990403115154.A72956@nuxi.com> <19990403234614.A28774@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990403234614.A28774@titan.klemm.gtn.com>; from Andreas Klemm on Sat, Apr 03, 1999 at 11:46:14PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) > /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/collect2 -m elf_i38 > 6 -dynamic-linker /usr/libexec/ld-elf.so.1 -o resize /usr/lib/crt1.o /usr/lib/cr > ti.o /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/crtbegin.o -L.. > /../exports/lib -L/usr/X11R6/lib -L/usr/local/lib/gcc-lib/i386-portbld-freebsd3. > 1/egcs-2.91.66 -L/usr/local/i386-portbld-freebsd3.1/lib -L/usr/local/lib resize. > o -lxpg4 -lrpcsvc -lkrb -ldes -lcrypt -ltermcap -rpath /usr/X11R6/lib -lgcc -lc > -lgcc /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/crtend.o /usr/ > lib/crtn.o Looking at the link line, I don't see anything wrong on 1st glance. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 14:21:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 48D411517A for ; Sat, 3 Apr 1999 14:20:22 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id OAA73359; Sat, 3 Apr 1999 14:18:24 -0800 (PST) (envelope-from obrien) Message-ID: <19990403141824.B73304@nuxi.com> Date: Sat, 3 Apr 1999 14:18:24 -0800 From: "David O'Brien" To: Steve Price Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Reply-To: obrien@NUXI.com References: <19990403115632.B72956@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Steve Price on Sat, Apr 03, 1999 at 03:16:30PM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I got everything setup to build the entire ports collection and > sometime during the night the big IDE disk that I keep all the I'm not sure the best way to approach this. The specification file used in the port is different from the one that will be in the base system. (the on in the Port is more stock EGCS) The base system will have many more of our hacks. So the fix we mentioned might not be needed with the base EGCS. Maybe you can just compile all the ports just to see where we stand. I don't expect *any* problems with ports that use the C compiler. All the problems I think we might have are C++ compiler issues. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 14:26:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 0BF8214CC7 for ; Sat, 3 Apr 1999 14:26:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id OAA57052; Sat, 3 Apr 1999 14:21:58 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904032221.OAA57052@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert Cc: Steve Price , Andreas Klemm , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-reply-to: Your message of "Sat, 03 Apr 1999 22:51:47 +0200." <19990403225146.A99040@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Apr 1999 14:21:58 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been compiling Netscape's Java VM Electric Fire which is written on C++ with no problems however I have been using the "-fexceptions" flag. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 14:36:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0759E14CAC for ; Sat, 3 Apr 1999 14:36:37 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id OAA73406; Sat, 3 Apr 1999 14:34:33 -0800 (PST) (envelope-from obrien) Message-ID: <19990403143433.A73396@nuxi.com> Date: Sat, 3 Apr 1999 14:34:33 -0800 From: "David O'Brien" To: Ollivier Robert , Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Reply-To: obrien@NUXI.com References: <199904031914.LAA56145@rah.star-gate.com> <19990403225146.A99040@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990403225146.A99040@keltia.freenix.fr>; from Ollivier Robert on Sat, Apr 03, 1999 at 10:51:47PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is that egcs 1.1.2 has its own crt*.o files and use them in > place of the FreeBSD one. By moving the files elsewhere, it works. I don't > know the effect on exceptions though. If that is the problem, then it sounds like a DWARF2_UNWIND issue. > I don't know what David plan to do with these crt*.o files. David ? src/lib/csu/i386-elf will build and install crtbegin.o and crtend.o from the EGCS sources. Otherwise we have to use the poorer exception unwinding method. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 14:47:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 1436F14D42 for ; Sat, 3 Apr 1999 14:47:34 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id OAA57143; Sat, 3 Apr 1999 14:44:13 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904032244.OAA57143@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: Ollivier Robert , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-reply-to: Your message of "Sat, 03 Apr 1999 14:34:33 PST." <19990403143433.A73396@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Apr 1999 14:44:13 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, it is most likely a DWARF2_UNWIND issue at least that is what I concluded in trying to support Electric Fire also someone should investigate whether egcs supports exception handling without thread support if memory does not fail me egcs requires thread support for exception handling. Perhaps it is a good time to review the egcs docs with respect to frame handling and exception handling. Amancio > > The problem is that egcs 1.1.2 has its own crt*.o files and use them in > > place of the FreeBSD one. By moving the files elsewhere, it works. I don't > > know the effect on exceptions though. > > If that is the problem, then it sounds like a DWARF2_UNWIND issue. > > > I don't know what David plan to do with these crt*.o files. David ? > > src/lib/csu/i386-elf will build and install crtbegin.o and crtend.o from > the EGCS sources. Otherwise we have to use the poorer exception > unwinding method. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 15: 6: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5F48B14E62; Sat, 3 Apr 1999 15:05:59 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (d60-077.leach.ucdavis.edu [169.237.60.77]) by relay.nuxi.com (8.9.2/8.9.1) with ESMTP id PAA73508; Sat, 3 Apr 1999 15:04:03 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA87310; Sat, 3 Apr 1999 23:04:03 GMT (envelope-from obrien) Date: Sat, 3 Apr 1999 15:04:02 -0800 From: "David O'Brien" To: committers@freebsd.org, current@freebsd.org Subject: Re: make world is hosed Message-ID: <19990403150402.A76142@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <41398.923132926@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <41398.923132926@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Apr 03, 1999 at 11:48:46AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - --------------------------------------------------------------------- > Last section: >>> Building elf libraries > - --------------------------------------------------------------------- > Last arrow: ===> libstdc++ > - --------------------------------------------------------------------- > Last 20 lines before first error: > - --------------------------------------------------------------------- > install -c -o root -g wheel -m 444 libreadline_p.a /usr/obj/usr/src/tmp/usr/lib > install -c -o root -g wheel -m 444 libreadline.so.3 /usr/obj/usr/src/tmp/usr/lib > ln -sf libreadline.so.3 /usr/obj/usr/src/tmp/usr/lib/libreadline.so > ===> libreadline/doc > ===> libreadline/doc/history > ===> libreadline/doc/readline > ===> libstdc++ ..snip.. > cd /usr/src/gnu/usr.bin/cc/libgcc; /usr/obj/usr/src/tmp/usr/bin/make all; /usr/obj/usr/src/tmp/usr/bin/make -B install > install -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/tmp/mk > usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 > install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... > fileN directory > install -d [-g group] [-m mode] [-o owner] directory ... > *** Error code 64 Is anyone else experiencing this? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 15:12: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-33.ppp.wenet.net [206.15.85.33]) by hub.freebsd.org (Postfix) with ESMTP id 822F714E6C for ; Sat, 3 Apr 1999 15:12:03 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id PAA13852; Sat, 3 Apr 1999 15:10:22 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 3 Apr 1999 15:10:22 -0800 (PST) From: Alex Zepeda To: Amancio Hasty Cc: current Subject: Re: X problems using egcs as compiler In-Reply-To: <199904032244.OAA57143@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Amancio Hasty wrote: > Yes, it is most likely a DWARF2_UNWIND issue at least that is what I > concluded in trying to support Electric Fire also someone should > investigate whether egcs supports exception handling without thread > support if memory does not fail me egcs requires thread support for > exception handling. Perhaps it is a good time to review the egcs docs > with respect to frame handling and exception handling. How can I tell if I've got thread support enabled? I've used ksirc before which uses exceptions to parse irc output, and it's obviously not threaded (cause Qt isn't). Sure, I don't like ksirc, and I got some odd perl related errors, but it worked. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 15:22:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 5DD2014D42 for ; Sat, 3 Apr 1999 15:22:37 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id AAA24727 for freebsd.org!current; Sun, 4 Apr 1999 00:20:42 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 4 Apr 1999 00:05:52 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 4 Apr 1999 00:05:59 +0000 To: current@freebsd.org From: Bob Bishop Subject: make world broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, If today's going to be a flag day, the following isn't going to help: [cvsup at Sat Apr 3 21:27:16 BST 1999] make all; /usr/obj/source/cleansrc/tmp/usr/bin/make -B install install -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.ob j.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/source/cleansrc/tmp/mk usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. [etc] -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 15:24:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id E112E14E11; Sat, 3 Apr 1999 15:24:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id PAA57353; Sat, 3 Apr 1999 15:20:58 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904032320.PAA57353@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: make world is hosed In-reply-to: Your message of "Sat, 03 Apr 1999 15:04:02 PST." <19990403150402.A76142@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Apr 1999 15:20:58 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a cvsup and a make world around 8:00 PM last nite and went without a hitch . Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 15:41: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 8210614CD1 for ; Sat, 3 Apr 1999 15:41:02 -0800 (PST) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 28381 invoked from network); 3 Apr 1999 23:39:03 -0000 Received: from userai31.uk.uudial.com (HELO k2c.co.uk) (62.188.133.61) by smtp.dial.pipex.com with SMTP; 3 Apr 1999 23:39:03 -0000 Message-ID: <3706A615.B5BBB04@k2c.co.uk> Date: Sun, 04 Apr 1999 00:36:53 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@NUXI.com Cc: committers@freebsd.org, current@freebsd.org Subject: Re: make world is hosed References: <41398.923132926@critter.freebsd.dk> <19990403150402.A76142@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > > Is anyone else experiencing this? > > -- I did earlier on today; I removed /usr/src/gnu/usr.bin/cc/libgcc, and all went fine. It might in fact have been a consequence of one of your earlier commits (when you moved the Makefile to the Attic)? Best Regards, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16: 5:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 0146B14E7B for ; Sat, 3 Apr 1999 16:05:08 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id SAA02202; Sat, 3 Apr 1999 18:03:12 -0600 (CST) Date: Sat, 3 Apr 1999 18:03:12 -0600 (CST) From: Steve Price To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-Reply-To: <19990403141824.B73304@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, David O'Brien wrote: # I'm not sure the best way to approach this. The specification file used # in the port is different from the one that will be in the base system. # (the on in the Port is more stock EGCS) The base system will have many # more of our hacks. I don't know what we'd prove if the ports tree was built with an un-FreeBSD'd egcs. It might get us close, then again it might get us chasing (mis)features that aren't going to be present when it is the system compiler. I certainly would feel better about using the real thing. # So the fix we mentioned might not be needed with the base EGCS. Maybe # you can just compile all the ports just to see where we stand. I don't # expect *any* problems with ports that use the C compiler. All the # problems I think we might have are C++ compiler issues. See above. Can you send me a set of instructions for turning gcc off and egcs on in the base distribution? -steve # -- # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:18:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id AA50214DAD for ; Sat, 3 Apr 1999 16:18:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA22047; Sat, 3 Apr 1999 16:16:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Steve Price Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-reply-to: Your message of "Sat, 03 Apr 1999 18:03:12 CST." Date: Sat, 03 Apr 1999 16:16:08 -0800 Message-ID: <22045.923184968@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > See above. Can you send me a set of instructions for turning gcc > off and egcs on in the base distribution? Better yet, can we just run with this today instead of tomorrow? I see no reason to wait any further, and some of us have more time this weekend to work on testing things which a Sunday schedule would collapse to less than half a day. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:28:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id F064914D73 for ; Sat, 3 Apr 1999 16:28:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA73825; Sat, 3 Apr 1999 16:26:40 -0800 (PST) (envelope-from obrien) Message-ID: <19990403162640.D73487@nuxi.com> Date: Sat, 3 Apr 1999 16:26:40 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Switching to EGCS on Saturday (PST) Reply-To: obrien@NUXI.com References: <22045.923184968@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <22045.923184968@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Apr 03, 1999 at 04:16:08PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Better yet, can we just run with this today instead of tomorrow? I guess we could do it today. But there might be some that were planning on doing a final CVSup tonight, since the announcement was for Sunday. Opinions? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:31: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D95014E62 for ; Sat, 3 Apr 1999 16:31:03 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA73846; Sat, 3 Apr 1999 16:28:51 -0800 (PST) (envelope-from obrien) Message-ID: <19990403162851.A73829@nuxi.com> Date: Sat, 3 Apr 1999 16:28:51 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" , Steve Price Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Reply-To: obrien@NUXI.com References: <22045.923184968@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <22045.923184968@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Apr 03, 1999 at 04:16:08PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Better yet, can we just run with this today instead of tomorrow? Can someone with a FAST machine do a CVSup from Freefall and `make world' to verify that it is not broken? My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make world'. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:31:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B7B3714E52 for ; Sat, 3 Apr 1999 16:31:14 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id SAA22952; Sat, 3 Apr 1999 18:29:02 -0600 (CST) Date: Sat, 3 Apr 1999 18:29:00 -0600 (CST) From: Steve Price To: "Jordan K. Hubbard" Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-Reply-To: <22045.923184968@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Jordan K. Hubbard wrote: # Better yet, can we just run with this today instead of tomorrow? I # see no reason to wait any further, and some of us have more time this # weekend to work on testing things which a Sunday schedule would # collapse to less than half a day. You're right, even better yet. Throw the switch already! :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:35:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 659C714F5A for ; Sat, 3 Apr 1999 16:35:43 -0800 (PST) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 238 invoked from network); 4 Apr 1999 00:33:47 -0000 Received: from userai31.uk.uudial.com (HELO k2c.co.uk) (62.188.133.61) by smtp.dial.pipex.com with SMTP; 4 Apr 1999 00:33:47 -0000 Message-ID: <3706B2E8.6FDCE2E5@k2c.co.uk> Date: Sun, 04 Apr 1999 01:31:36 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@NUXI.com Cc: "Jordan K. Hubbard" , Steve Price , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler References: <22045.923184968@zippy.cdrom.com> <19990403162851.A73829@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > > Better yet, can we just run with this today instead of tomorrow? > > Can someone with a FAST machine do a CVSup from Freefall and `make world' > to verify that it is not broken? > > My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make > world'. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Just did that... results in roughly 1 hour 1/2, ok? (unless it breaks, of course). PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:36:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 325FE14F5A for ; Sat, 3 Apr 1999 16:36:27 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id SAA03038; Sat, 3 Apr 1999 18:34:10 -0600 (CST) Date: Sat, 3 Apr 1999 18:34:10 -0600 (CST) From: Steve Price To: "David O'Brien" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: <19990403162640.D73487@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, David O'Brien wrote: # I guess we could do it today. # # But there might be some that were planning on doing a final CVSup # tonight, since the announcement was for Sunday. They can always CVSup the latest bits and 'cvs co -D...' if they are getting the repository. They can also do this with a 'date=...' line in their cvsup-supfile. Just note the date/time just before the switch is thrown and let's get this show on the road. # Opinions? Do it. # -- # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:38:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1219F14E7B for ; Sat, 3 Apr 1999 16:38:24 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA17577; Sat, 3 Apr 1999 16:35:56 -0800 Date: Sat, 3 Apr 1999 16:35:55 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Steve Price Cc: "David O'Brien" , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No. Don't. Please stick to reported change times. 'cvs co -D' is a desperate last measure. On Sat, 3 Apr 1999, Steve Price wrote: > On Sat, 3 Apr 1999, David O'Brien wrote: > > # I guess we could do it today. > # > # But there might be some that were planning on doing a final CVSup > # tonight, since the announcement was for Sunday. > > They can always CVSup the latest bits and 'cvs co -D...' if they > are getting the repository. They can also do this with a 'date=...' > line in their cvsup-supfile. Just note the date/time just before > the switch is thrown and let's get this show on the road. > > # Opinions? > > Do it. > > # -- > # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:38:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat192.236.mpoweredpc.net [142.177.192.236]) by hub.freebsd.org (Postfix) with ESMTP id B5829151B5 for ; Sat, 3 Apr 1999 16:38:39 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id UAA08303; Sat, 3 Apr 1999 20:36:31 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 3 Apr 1999 20:36:31 -0400 (AST) From: The Hermit Hacker To: "David O'Brien" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: <19990403162640.D73487@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, David O'Brien wrote: > > Better yet, can we just run with this today instead of tomorrow? > > I guess we could do it today. > > But there might be some that were planning on doing a final CVSup > tonight, since the announcement was for Sunday. > > Opinions? Its -CURRENT ... go for it. As soon as I see the announcement go out, I'll be one of those upgrading to it, I've been looking forward to seeing EGCS integrated for a long time now :) 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-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:41:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 8A20914FD7 for ; Sat, 3 Apr 1999 16:41:26 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id SAA25679; Sat, 3 Apr 1999 18:39:13 -0600 (CST) Date: Sat, 3 Apr 1999 18:39:13 -0600 (CST) From: Steve Price To: "David O'Brien" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-Reply-To: <19990403162851.A73829@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, David O'Brien wrote: # > Better yet, can we just run with this today instead of tomorrow? # # Can someone with a FAST machine do a CVSup from Freefall and `make world' # to verify that it is not broken? Doing it now. Going out to grab a bite to eat with the family but I should be back before it finishes. It usually only takes a little over an hour to do a 'make world' from scratch on my box at work. I'll let you know when it gets done. # My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make # world'. # # -- # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:46:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id DD5BF14FCF for ; Sat, 3 Apr 1999 16:46:28 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id QAA02923; Sat, 3 Apr 1999 16:44:18 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.0.32.19990403164154.00a46520@216.101.162.50> X-Sender: null@216.101.162.50 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.32 (Beta) Date: Sat, 03 Apr 1999 16:44:17 -0800 To: obrien@NUXI.com, "Jordan K. Hubbard" , Steve Price From: Manfred Antar Subject: Re: X problems using egcs as compiler Cc: current@FreeBSD.ORG In-Reply-To: <19990403162851.A73829@nuxi.com> References: <22045.923184968@zippy.cdrom.com> <22045.923184968@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:28 PM 4/3/99 -0800, David O'Brien wrote: >> Better yet, can we just run with this today instead of tomorrow? > >Can someone with a FAST machine do a CVSup from Freefall and `make world' >to verify that it is not broken? > >My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make >world'. > >-- >-- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message I started a Make world about 1 hour ago with current as of then sources. It should be done in about 30min's. The only thing is I don't build xntpd but every thing else is built. I'll post when completed Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:47:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id E078614BF1 for ; Sat, 3 Apr 1999 16:47:09 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id SAA13767; Sat, 3 Apr 1999 18:44:36 -0600 (CST) Date: Sat, 3 Apr 1999 18:44:36 -0600 (CST) From: Steve Price To: Matthew Jacob Cc: "David O'Brien" , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Matthew Jacob wrote: # # # No. Don't. Please stick to reported change times. 'cvs co -D' is a # desperate last measure. Something that someone playing with bleeding edge bits should be willing to do, IMHO. # # On Sat, 3 Apr 1999, Steve Price wrote: # # > On Sat, 3 Apr 1999, David O'Brien wrote: # > # > # I guess we could do it today. # > # # > # But there might be some that were planning on doing a final CVSup # > # tonight, since the announcement was for Sunday. # > # > They can always CVSup the latest bits and 'cvs co -D...' if they # > are getting the repository. They can also do this with a 'date=...' # > line in their cvsup-supfile. Just note the date/time just before # > the switch is thrown and let's get this show on the road. # > # > # Opinions? # > # > Do it. # > # > # -- # > # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:49:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AEEB514BD5 for ; Sat, 3 Apr 1999 16:49:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA74037; Sat, 3 Apr 1999 16:47:39 -0800 (PST) (envelope-from obrien) Message-ID: <19990403164739.A74026@nuxi.com> Date: Sat, 3 Apr 1999 16:47:39 -0800 From: "David O'Brien" To: mjacob@feral.com, Steve Price Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew Jacob on Sat, Apr 03, 1999 at 04:35:55PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We could also tag the repository... would that be better? > No. Don't. Please stick to reported change times. 'cvs co -D' is a > desperate last measure. > > > They can always CVSup the latest bits and 'cvs co -D...' if they > > are getting the repository. They can also do this with a 'date=...' > > line in their cvsup-supfile. Just note the date/time just before > > the switch is thrown and let's get this show on the road. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:50:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5934D14BD5 for ; Sat, 3 Apr 1999 16:50:36 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA17637; Sat, 3 Apr 1999 16:48:09 -0800 Date: Sat, 3 Apr 1999 16:48:08 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Steve Price Cc: "David O'Brien" , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 3 Apr 1999, Matthew Jacob wrote: > > # > # > # No. Don't. Please stick to reported change times. 'cvs co -D' is a > # desperate last measure. > > Something that someone playing with bleeding edge bits should > be willing to do, IMHO. That's ridiculous. There's substantial work ongoing in 4.0 with enough people involved that changing things around for the hell of it and not sticking to broadcast times is just plain stupid. It's called 'dufus engineering', or 'freshman humour' or some such. Just because it's so-called 'bleeding edge' doesn't mean you can just integrate any old crap and just say "well- it's bleeding edge". Harumph. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 16:51:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 92B4B14BD5 for ; Sat, 3 Apr 1999 16:51:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA17643; Sat, 3 Apr 1999 16:48:49 -0800 Date: Sat, 3 Apr 1999 16:48:49 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "David O'Brien" Cc: Steve Price , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: <19990403164739.A74026@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For a major change like using a different compiler- seems like A Good Idea(tm). On Sat, 3 Apr 1999, David O'Brien wrote: > We could also tag the repository... would that be better? > > > No. Don't. Please stick to reported change times. 'cvs co -D' is a > > desperate last measure. > > > > > They can always CVSup the latest bits and 'cvs co -D...' if they > > > are getting the repository. They can also do this with a 'date=...' > > > line in their cvsup-supfile. Just note the date/time just before > > > the switch is thrown and let's get this show on the road. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17: 1:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id EFB9114FEB for ; Sat, 3 Apr 1999 17:01:12 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (540 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 3 Apr 1999 16:59:12 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 3 Apr 1999 16:59:12 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Marc van Woerkom Cc: FreeBSD Current Subject: Re: netscape: no recognized font Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > They went away after I nuked all prior traces of Navigator, including > my .netscape directory (you should rename it :-) that was it. i cleaned out much of .netscrape and it worked fine. thanks. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17: 3:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id EC6EE14F87 for ; Sat, 3 Apr 1999 17:03:13 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id TAA09999; Sat, 3 Apr 1999 19:00:57 -0600 (CST) Date: Sat, 3 Apr 1999 19:00:57 -0600 (CST) From: Steve Price To: Matthew Jacob Cc: "David O'Brien" , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Matthew Jacob wrote: # > Something that someone playing with bleeding edge bits should # > be willing to do, IMHO. # # That's ridiculous. There's substantial work ongoing in 4.0 with enough # people involved that changing things around for the hell of it and not # sticking to broadcast times is just plain stupid. It's called 'dufus # engineering', or 'freshman humour' or some such. Just because it's # so-called 'bleeding edge' doesn't mean you can just integrate any old crap # and just say "well- it's bleeding edge". Harumph. We are not changing it for the hell of it. From what I gather David already has things ready and is just waiting for Sunday to come to commit the changes. Committing them now gives much of the people who will work to fix things that get broken a whole day more this weekend to work on them. This isn't 'dufus engineering' it is called advancing the state-of-the-art. It has been a long time coming and needs to be done, sooner than later. Just because the compiler changes doesn't mean development on the 4.0 branch have to stop. We need to get this change in the hands of as many people as we can so that we can work out any remaining hitches. Waiting another 24 hours == wasting another 24 hours, IMHO. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17: 6: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 789E514D83 for ; Sat, 3 Apr 1999 17:06:00 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id TAA19809; Sat, 3 Apr 1999 19:04:00 -0600 (CST) Date: Sat, 3 Apr 1999 19:04:00 -0600 From: "Matthew D. Fuller" To: Dag-Erling Smorgrav Cc: Anders Andersson , freebsd-current@FreeBSD.ORG Subject: crypt algorithms (was Re: DES from source?) Message-ID: <19990403190359.B12711@futuresouth.com> References: <19990403122221.A12230@sanyusan.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Dag-Erling Smorgrav on Sat, Apr 03, 1999 at 05:34:06PM +0200 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 03, 1999 at 05:34:06PM +0200, a little birdie told me that Dag-Erling Smorgrav remarked > > > Do I need to change all passwd with 'passwd {user}' to use DES passwd crypt? > > Existing MD5 passwords will still work. New users will get DES > passwords. Did we ever hash out a mechanism to do this the other way (or integrate new algorithms) and set 'try' vs. 'use' algorithms? I'm unclear as to whether PAM is supposed to/capable of addressing this. --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17: 8:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 5034C14E32 for ; Sat, 3 Apr 1999 17:08:20 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA25852; Sun, 4 Apr 1999 10:36:24 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA04156; Sun, 4 Apr 1999 10:36:24 +0930 (CST) Message-ID: <19990404103623.M2142@lemis.com> Date: Sun, 4 Apr 1999 10:36:23 +0930 From: Greg Lehey To: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: Fatal trap 1: privileged instruction fault while in kernel mode References: <199904031557.BAA03125@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904031557.BAA03125@nymph.detir.qld.gov.au>; from Stephen McKay on Sun, Apr 04, 1999 at 01:57:50AM +1000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 4 April 1999 at 1:57:50 +1000, Stephen McKay wrote: > I've just got what seems an unlikely panic. How could I get a privileged > instruction fault while in kernel mode? Sounds like a hardware (processor) problem to me. What was the instruction it was trying to execute? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17:10:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0C03F152F5 for ; Sat, 3 Apr 1999 17:09:00 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id RAA17710; Sat, 3 Apr 1999 17:06:38 -0800 Date: Sat, 3 Apr 1999 17:06:38 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Steve Price Cc: "David O'Brien" , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 3 Apr 1999, Matthew Jacob wrote: > > # > Something that someone playing with bleeding edge bits should > # > be willing to do, IMHO. > # > # That's ridiculous. There's substantial work ongoing in 4.0 with enough > # people involved that changing things around for the hell of it and not > # sticking to broadcast times is just plain stupid. It's called 'dufus > # engineering', or 'freshman humour' or some such. Just because it's > # so-called 'bleeding edge' doesn't mean you can just integrate any old crap > # and just say "well- it's bleeding edge". Harumph. > Sorry- let me apologize for bad tone. Bad day for me. > We are not changing it for the hell of it. From what I gather > David already has things ready and is just waiting for Sunday > to come to commit the changes. Committing them now gives much > of the people who will work to fix things that get broken a > whole day more this weekend to work on them. This isn't 'dufus > engineering' it is called advancing the state-of-the-art. It > has been a long time coming and needs to be done, sooner than > later. > > Just because the compiler changes doesn't mean development on > the 4.0 branch have to stop. We need to get this change in the > hands of as many people as we can so that we can work out any > remaining hitches. Waiting another 24 hours == wasting another > 24 hours, IMHO. I suppose. It's also fair to state that sticking to stated plans is good too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17:10:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id C20BA14D1E for ; Sat, 3 Apr 1999 17:10:33 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id UAA37453; Sat, 3 Apr 1999 20:06:19 -0500 (EST) Date: Sat, 3 Apr 1999 20:06:19 -0500 (EST) From: Chuck Robey To: Steve Price Cc: Matthew Jacob , "David O'Brien" , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Apr 1999, Steve Price wrote: > On Sat, 3 Apr 1999, Matthew Jacob wrote: > > # > Something that someone playing with bleeding edge bits should > # > be willing to do, IMHO. > # > # That's ridiculous. There's substantial work ongoing in 4.0 with enough > # people involved that changing things around for the hell of it and not > # sticking to broadcast times is just plain stupid. It's called 'dufus > # engineering', or 'freshman humour' or some such. Just because it's > # so-called 'bleeding edge' doesn't mean you can just integrate any old crap > # and just say "well- it's bleeding edge". Harumph. > > We are not changing it for the hell of it. From what I gather > David already has things ready and is just waiting for Sunday > to come to commit the changes. Committing them now gives much > of the people who will work to fix things that get broken a > whole day more this weekend to work on them. This isn't 'dufus > engineering' it is called advancing the state-of-the-art. It > has been a long time coming and needs to be done, sooner than > later. > > Just because the compiler changes doesn't mean development on > the 4.0 branch have to stop. We need to get this change in the > hands of as many people as we can so that we can work out any > remaining hitches. Waiting another 24 hours == wasting another > 24 hours, IMHO. I don't like to disagree with you, Matthew, but the cvsup line to get what you need is pretty simple. This thing needs to get tested, asap, and the weekend is a better time for it. Your argument is basically "do what you said" ... the rest, likening it to freshman antics, is emotionalism. We have a good reason to push ahead here, and an easy recovery path. Some folks might get surprised, but that seems like a small thing, actually, because nearly all of them are reading this. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17:13:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 37FA014C45 for ; Sat, 3 Apr 1999 17:13:50 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id RAA17740; Sat, 3 Apr 1999 17:11:21 -0800 Date: Sat, 3 Apr 1999 17:11:21 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Chuck Robey Cc: Steve Price , "David O'Brien" , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Just because the compiler changes doesn't mean development on > > the 4.0 branch have to stop. We need to get this change in the > > hands of as many people as we can so that we can work out any > > remaining hitches. Waiting another 24 hours == wasting another > > 24 hours, IMHO. > > I don't like to disagree with you, Matthew, but the cvsup line to get > what you need is pretty simple. This thing needs to get tested, asap, > and the weekend is a better time for it. Your argument is basically > "do what you said" ... the rest, likening it to freshman antics, is > emotionalism. We have a good reason to push ahead here, and an easy > recovery path. Some folks might get surprised, but that seems like a > small thing, actually, because nearly all of them are reading this. > Yeah, yeah, yeah, yeah.... I'm a grumpy idiot...sorry... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17:36:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id EB21214BDB for ; Sat, 3 Apr 1999 17:36:26 -0800 (PST) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 1779 invoked from network); 4 Apr 1999 01:34:30 -0000 Received: from userai31.uk.uudial.com (HELO k2c.co.uk) (62.188.133.61) by smtp.dial.pipex.com with SMTP; 4 Apr 1999 01:34:30 -0000 Message-ID: <3706C123.8CB7734D@k2c.co.uk> Date: Sun, 04 Apr 1999 02:32:19 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler References: <22045.923184968@zippy.cdrom.com> <19990403162851.A73829@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > Can someone with a FAST machine do a CVSup from Freefall and `make world' > to verify that it is not broken? > CVSupped from 01:25 BST, make -j12 -DCLOBBER world on an SMP box, both ELF and aout libraries generated, compile options -02 -m486, all clear. The word is go. PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 17:49:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 3D67F14BDB for ; Sat, 3 Apr 1999 17:49:09 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id RAA58128; Sat, 3 Apr 1999 17:45:58 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904040145.RAA58128@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Pierre Y. Dampure" Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-reply-to: Your message of "Sun, 04 Apr 1999 02:32:19 +0100." <3706C123.8CB7734D@k2c.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Apr 1999 17:45:58 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just finished doing a cvsup and currently doing a make world. Should be done in less than 80 minutes . Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18: 1:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E0BC814DFC for ; Sat, 3 Apr 1999 18:01:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA22379; Sat, 3 Apr 1999 17:59:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: Steve Price , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-reply-to: Your message of "Sat, 03 Apr 1999 16:28:51 PST." <19990403162851.A73829@nuxi.com> Date: Sat, 03 Apr 1999 17:59:30 -0800 Message-ID: <22376.923191170@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Once you say the word that egcs is the default and a make world will actually use it, I'll be more than happy to do so immediately with my dual PII-450 box here. - Jordan > > Better yet, can we just run with this today instead of tomorrow? > > Can someone with a FAST machine do a CVSup from Freefall and `make world' > to verify that it is not broken? > > My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make > world'. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18: 3:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 52E5D14DFC for ; Sat, 3 Apr 1999 18:03:33 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA22403; Sat, 3 Apr 1999 18:01:32 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-reply-to: Your message of "Sat, 03 Apr 1999 16:26:40 PST." <19990403162640.D73487@nuxi.com> Date: Sat, 03 Apr 1999 18:01:32 -0800 Message-ID: <22401.923191292@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -current comes without any warranties whatsoever. I say just pull the switch! :) > > Better yet, can we just run with this today instead of tomorrow? > > I guess we could do it today. > > But there might be some that were planning on doing a final CVSup > tonight, since the announcement was for Sunday. > > Opinions? > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18: 5: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9CC1914DFC for ; Sat, 3 Apr 1999 18:04:58 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA22418; Sat, 3 Apr 1999 18:02:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: mjacob@feral.com, Steve Price , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-reply-to: Your message of "Sat, 03 Apr 1999 16:47:39 PST." <19990403164739.A74026@nuxi.com> Date: Sat, 03 Apr 1999 18:02:55 -0800 Message-ID: <22416.923191375@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's really not necessary given that -D gives us the same functionality. It's also hardly a desperation measure to use a commonly available feature of CVS, especially not when one is already crazed enough to track -current in the first place. - Jordan > We could also tag the repository... would that be better? > > > No. Don't. Please stick to reported change times. 'cvs co -D' is a > > desperate last measure. > > > > > They can always CVSup the latest bits and 'cvs co -D...' if they > > > are getting the repository. They can also do this with a 'date=...' > > > line in their cvsup-supfile. Just note the date/time just before > > > the switch is thrown and let's get this show on the road. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18: 7:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8533E14E5F for ; Sat, 3 Apr 1999 18:07:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA22436; Sat, 3 Apr 1999 18:05:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: Steve Price , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-reply-to: Your message of "Sat, 03 Apr 1999 16:48:08 PST." Date: Sat, 03 Apr 1999 18:05:25 -0800 Message-ID: <22434.923191525@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dude, we're talking about advancing by a day an event which is already seriously late anyway. The end of the world isn't going to come out of this and, even if it were, 24 more hours to live wouldn't make the slightest bit of difference to you anyway. I think you just need to chill out and let -current do what it needs to do. It's more important for us to get testing started than it is for us to safeguard your box and if zero risk is what you seek, don't run -current at all. Enough said - this isn't even worth arguing about. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18:10:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 032D914D42 for ; Sat, 3 Apr 1999 18:10:07 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA74479 for current@freebsd.org; Sat, 3 Apr 1999 18:08:12 -0800 (PST) (envelope-from obrien) Message-ID: <19990403180812.A74386@nuxi.com> Date: Sat, 3 Apr 1999 18:08:12 -0800 From: "David O'Brien" To: current@freebsd.org Subject: Re: Switching to EGCS on Saturday (PST) Reply-To: obrien@NUXI.com References: <22045.923184968@zippy.cdrom.com> <22045.923184968@zippy.cdrom.com> <19990403162640.D73487@nuxi.com> <3.0.5.32.19990403174542.009988c0@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3.0.5.32.19990403174542.009988c0@localhost>; from Kurt D. Zeilenga on Sat, Apr 03, 1999 at 05:45:42PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's already Sunday GMT. That it is. Well then that is good enough for me. (although Zulu time sounds more cool to me). I just "upgraded" my main EGCS development machine to the March 31st CURRENT snapshot and am doing a `make buildworld' to ensure things are ready go to. I will be gone from 7pm-10pm Saturday PST. Destroying^H^H^H^Hupgrading the compiler will commence after that time. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18:13:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 42E8814BF1 for ; Sat, 3 Apr 1999 18:13:22 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id SAA17913; Sat, 3 Apr 1999 18:11:09 -0800 Date: Sat, 3 Apr 1999 18:11:09 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: Steve Price , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Switching to EGCS on Saturday (PST) In-Reply-To: <22434.923191525@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG alright alright! On Sat, 3 Apr 1999, Jordan K. Hubbard wrote: > Dude, we're talking about advancing by a day an event which is already > seriously late anyway. The end of the world isn't going to come out > of this and, even if it were, 24 more hours to live wouldn't make the > slightest bit of difference to you anyway. I think you just need to > chill out and let -current do what it needs to do. It's more > important for us to get testing started than it is for us to safeguard > your box and if zero risk is what you seek, don't run -current at all. > Enough said - this isn't even worth arguing about. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18:17:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.galea.com (mail.galea.com [205.237.227.60]) by hub.freebsd.org (Postfix) with SMTP id 5785414D9A for ; Sat, 3 Apr 1999 18:17:13 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from ASSURANCETOURIX ([205.237.227.162]) by mail.galea.com (Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) with SMTP id 85256749.000C3F05; Sat, 3 Apr 1999 21:13:45 -0500 Message-ID: <0c1001be7e41$c5d75470$0100000a@ASSURANCETOURIX.Galea.com> From: "Stephane E. Potvin" To: , "Jordan K. Hubbard" , "Steve Price" Cc: Subject: Re: X problems using egcs as compiler Date: Sat, 3 Apr 1999 21:20:56 -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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: David O'Brien To: Jordan K. Hubbard ; Steve Price Cc: current@FreeBSD.ORG Date: Saturday, April 03, 1999 19:29 Subject: Re: X problems using egcs as compiler >> Better yet, can we just run with this today instead of tomorrow? > >Can someone with a FAST machine do a CVSup from Freefall and `make world' >to verify that it is not broken? > >My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make >world'. Done. cvsupped at 19:48 EST from cvsup2.freebsd.org buildworld with stock make.conf just finished without any problems. I'd say go for it :) Steph --- Stephane E. Potvin Galea Network Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18:23: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id D1A5714EE4 for ; Sat, 3 Apr 1999 18:22:59 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id DAA26169; Sun, 4 Apr 1999 03:20:58 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 4 Apr 1999 03:09:27 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19990403162851.A73829@nuxi.com> References: <22045.923184968@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Apr 03, 1999 at 04:16:08PM -0800 <22045.923184968@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 4 Apr 1999 03:09:35 +0000 To: obrien@NUXI.com From: Bob Bishop Subject: Re: X problems using egcs as compiler Cc: "Jordan K. Hubbard" , Steve Price , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:28 pm -0800 3/4/99, David O'Brien wrote: >Can someone with a FAST machine do a CVSup from Freefall and `make world' >to verify that it is not broken? >>> elf make world completed on Sun Apr 4 03:07:53 BST 1999 cvsup'd (from the UK server) at Sun Apr 4 01:50:56 BST 1999 -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18:50:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 9222D14E90 for ; Sat, 3 Apr 1999 18:50:39 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id SAA58479; Sat, 3 Apr 1999 18:47:23 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904040247.SAA58479@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bob Bishop Cc: obrien@NUXI.com, "Jordan K. Hubbard" , Steve Price , current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler In-reply-to: Your message of "Sun, 04 Apr 1999 03:09:35 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Apr 1999 18:47:23 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup around 17:30 PST -------------------------------------------------------------- >>> elf make world started on Sat Apr 3 17:33:29 PST 1999 -------------------------------------------------------------- -------------------------------------------------------------- >>> elf make world completed on Sat Apr 3 18:33:39 PST 1999 -------------------------------------------------------------- Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 18:59:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 4147914D91; Sat, 3 Apr 1999 18:59:31 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA21584; Sun, 4 Apr 1999 12:27:48 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA13780; Sun, 4 Apr 1999 12:27:44 +0930 Date: Sun, 4 Apr 1999 12:27:43 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: jmb@freebsd.org Cc: obrien@nuxi.com, "Jordan K. Hubbard" , Steve Price , current@freebsd.org Subject: Re: X problems using egcs as compiler In-Reply-To: <199904040247.SAA58479@rah.star-gate.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Only thing I can see to note is that the cvs mailing lists are still apparently down, so notification of this (and any other changes which take place) won't go out to the interested listeners. If jmb is planning to re-send all of the bounced email when he fixes the problem, that's okay. Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 22:27:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EB15614D3D for ; Sat, 3 Apr 1999 22:27:10 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id WAA75098 for current@freebsd.org; Sat, 3 Apr 1999 22:25:15 -0800 (PST) (envelope-from obrien) Message-ID: <19990403222515.A75073@nuxi.com> Date: Sat, 3 Apr 1999 22:25:15 -0800 From: "David O'Brien" To: current@freebsd.org Subject: show stopper for EGCS import Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from the EGCS source rather than our home-grown ones. This afternoon I switch my EGCS development machine back to a purely stock 4.0 SNAPSHOT and found that GCC 2.7.2 cannot compile the new sources. This is the same problem I had with libgcc. I've made the same fix to lib/csu as I did libgcc, but now am getting the same weird "install" problem Poul-Henning was getting. I'm working on fixing this problem now. Sorry to have the import delayed. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 22:49:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id ABCF415024 for ; Sat, 3 Apr 1999 22:49:44 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA26818; Sun, 4 Apr 1999 16:17:47 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA04710; Sun, 4 Apr 1999 16:17:45 +0930 (CST) Message-ID: <19990404161744.V2142@lemis.com> Date: Sun, 4 Apr 1999 16:17:44 +0930 From: Greg Lehey To: Stephen McKay Cc: FreeBSD current users Subject: Re: Fatal trap 1: privileged instruction fault while in kernel mode References: <199904031557.BAA03125@nymph.detir.qld.gov.au> <19990404103623.M2142@lemis.com> <199904040509.PAA19475@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904040509.PAA19475@nymph.detir.qld.gov.au>; from Stephen McKay on Sun, Apr 04, 1999 at 03:09:48PM +1000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 4 April 1999 at 15:09:48 +1000, Stephen McKay wrote: > On Sunday, 4th April 1999, Greg Lehey wrote: > >> On Sunday, 4 April 1999 at 1:57:50 +1000, Stephen McKay wrote: >>> I've just got what seems an unlikely panic. How could I get a privileged >>> instruction fault while in kernel mode? >> >> Sounds like a hardware (processor) problem to me. What was the >> instruction it was trying to execute? > > You were distracted by the large amount of extraneous fluff. ;-) Oops. > I wrote: > >> The fatal instruction is: >> 0xc016abc9 : movl $0xc023355c,0xffffffdc(%ebp) >> which looks pretty ordinary. Certainly not a privileged instruction. If the processor gets a privileged instruction fault on this one, I would say it's wrong. > What sort of hardware error happens once in 3 months? This one. > I often hammer it. It has done long tape operations before too. I > don't want to believe it is hardware yet. I'd say the truth is staring you in the face. Don't come too close, it might grab you. > I was hoping somebody knew the precise conditions that could produce > this trap. I'd guess that you'll never see exactly this trap again. But I do recall seeing some other similar ones. > I think I'll have to cruise the Intel web site and download some big > pdfs. Well, at least you'll learn something, but I don't expect you to find the solution to your problem there. > Could it be heat? If it's hot, yes. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 3 23:51:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 700DC15106 for ; Sat, 3 Apr 1999 23:51:28 -0800 (PST) (envelope-from br@netland.inka.de) Received: from stiller.netland.inka.de by mail.inka.de with uucp (rmailwrap 0.4) id 10Theu-0001t9-00; Sun, 4 Apr 1999 09:49:32 +0200 Received: from localhost (localhost [127.0.0.1]) by stiller.netland.inka.de (8.9.3/8.9.1) with ESMTP id JAA72635 for ; Sun, 4 Apr 1999 09:31:45 +0200 (CEST) (envelope-from br@netland.inka.de) Message-Id: <199904040731.JAA72635@stiller.netland.inka.de> To: freebsd-current@freebsd.org Subject: contrib/egcs Date: Sun, 04 Apr 1999 09:31:45 +0200 From: Bernd Rosauer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have noticed that egcs-1.1.2 made it into /usr/src/contrib. But 'make buildworld' does not touch it. What is the intended use of egcs? Thanks -Bernd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 1: 5:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 30531151B5 for ; Sun, 4 Apr 1999 01:05:23 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-51.ix.netcom.com [209.109.235.51]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA25736; Sun, 4 Apr 1999 01:03:26 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id BAA68274; Sun, 4 Apr 1999 01:02:26 -0800 (PST) Date: Sun, 4 Apr 1999 01:02:26 -0800 (PST) Message-Id: <199904040902.BAA68274@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: obrien@NUXI.com Cc: sprice@hiwaay.net, current@FreeBSD.ORG In-reply-to: <19990403141824.B73304@nuxi.com> (obrien@NUXI.com) Subject: Re: X problems using egcs as compiler From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: <19990403115632.B72956@nuxi.com> <19990403141824.B73304@nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "David O'Brien" * So the fix we mentioned might not be needed with the base EGCS. Maybe * you can just compile all the ports just to see where we stand. I don't Well, as soon as the first snapshot with the system egcs is released, I'm planning to grab it and run the build through it. The logs will be at the normal place (http://bento/~asami/errorlogs/). -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 1:15:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 6DB5614D79 for ; Sun, 4 Apr 1999 01:15:29 -0800 (PST) (envelope-from shocking@bandicoot.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id RAA01504; Sun, 4 Apr 1999 17:13:25 +0800 (WST) Received: by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id RAA26683; Sun, 4 Apr 1999 17:13:25 +0800 Date: Sun, 4 Apr 1999 17:13:25 +0800 From: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Message-Id: <199904040913.RAA26683@ariadne.tensor.pgs.com> To: current@freebsd.org, wpaul@ctr.columbia.edu Subject: More on rl0 woes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the offchance that mty problems were chipset related, I swapped the RealTek with the de0 card in my other machine, a 233MHz k6. It being a socket 7 mboard presumably has a later PCI bios. Still the same symptoms - hangs on NFS access. These can be interrupted and other network traffic continues fine. To reproduce, take your RealTek equipped machine and place a copy of /usr/src on it. Export /usr/src so that it can be NFS mounted by other machines. From the other machines, do an ls -CFR of /usr/src. It will hang partway through. Stephen .e w. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 1:23:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id CA24414E7E for ; Sun, 4 Apr 1999 01:23:41 -0800 (PST) (envelope-from ian@apdata.com.au) Received: from apdata.com.au (localhost [127.0.0.1]) by rose.niw.com.au (Postfix) with ESMTP id D725DA3203 for ; Sun, 4 Apr 1999 18:51:44 +0930 (CST) Message-ID: <37072F28.3AAC565E@apdata.com.au> Date: Sun, 04 Apr 1999 18:51:44 +0930 From: Ian West Organization: Applied Data Control X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Atime not set on execution ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it normal for atime not to be set on execution of a file ? I should have thought this would class as an access ? (I do not have the filesystem mounted -o noatime :-) This may be questions, but I am running current... Thankyou. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 3:19: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 1663F14F4E for ; Sun, 4 Apr 1999 03:18:59 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA29125; Sun, 4 Apr 1999 20:17:02 +1000 Date: Sun, 4 Apr 1999 20:17:02 +1000 From: Bruce Evans Message-Id: <199904041017.UAA29125@godzilla.zeta.org.au> To: current@FreeBSD.ORG, ian@apdata.com.au Subject: Re: Atime not set on execution ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is it normal for atime not to be set on execution of a file ? >I should have thought this would class as an access ? It's normal in FreeBSD, although this breaks POSIX.1 conformance. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 3:21:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 108F515297 for ; Sun, 4 Apr 1999 03:21:52 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-51.ix.netcom.com [209.109.235.51]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id DAA25850; Sun, 4 Apr 1999 03:20:01 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id DAA68539; Sun, 4 Apr 1999 03:19:41 -0700 (PDT) Date: Sun, 4 Apr 1999 03:19:41 -0700 (PDT) Message-Id: <199904041019.DAA68539@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: jkh@zippy.cdrom.com Cc: jhay@mikom.csir.co.za, current@FreeBSD.ORG In-reply-to: <14175.923091383@zippy.cdrom.com> (jkh@zippy.cdrom.com) Subject: Re: /var/db/pkg/.mkversion From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: <14175.923091383@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Jordan K. Hubbard" * As long as that directory is not /var/db/pkg, where I put my package * information, I agree that it doesn't matter either. :-) Ok. I'll move it out then. * I'm not sure that this is a solution so much as a band-aid, however. Of course. It's more of a safety belt, to avoid having people shooting off their own toes. :> The real problem is that people try to track ports-current with a release system. There is no solution to that, that's why I'm providing a series of band-aids.... * I could record the version number of the system as it was when * sysinstall installed it (3.1-RELEASE, X.X-YYYYMMDD-CURRENT, etc) but * that's about it. Actually, as you may have read in another message, it seems the problem was caused by a failing install due to to /var/db/pkg missing from the mtree list. Since the release build uses installworld, there really isn't anything special you need to do. * Well, the fetch -A thing was another imprudent leap off the wire * without a net, I'm not sure I'd use it to aid my arguments if I were * you. :-) Aw, touche. But it's no fun leaping if there's a net! -W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 3:55: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx2.io.com (mx2.io.com [199.170.88.18]) by hub.freebsd.org (Postfix) with ESMTP id 1768114DF7 for ; Sun, 4 Apr 1999 03:55:05 -0700 (PDT) (envelope-from watkins@io.com) Received: from io.com (as1-dialup-66.io.com [206.224.82.66]) by mx2.io.com (8.9.1a/8.9.1a) with SMTP id FAA08035; Sun, 4 Apr 1999 05:52:38 -0500 Date: Sun, 4 Apr 1999 05:52:38 -0500 From: watkins@io.com Message-Id: <199904041052.FAA08035@mx2.io.com> To: watkins@io.com Subject: Do you have one? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some people called the Ricky Willaims Heiman Siloutte shirt, others call it the Dreaded Football Player shirt. UT and the Downtown Athletic Club have tried to ban them through the Collegiate Licensing Company, but unsuccessfully. Thousands of people have got their hands on one of these shirts. We have some as well and are offering you a chance to get yours. This is the exact same shirt that was featured in the Austin American Stateman on December 15, 1998 in the Lifestyles section. Prices are as follows: White shirt with burnt orange siloutte. Sizes are S, M, L, XL, and XXL. XXL's ARE $3.00 MORE!!! 1. $16 +3.20 shipping =$19.20 2. $32 +3.20 shipping =$36.20 3. $48 +4.30 shipping =$52.30 4. $62 +4.30 shipping =$66.30 5. $70 +5.40 shipping =$75.40 Each shirt after 5 shirts is $14.00 each. Please add $1.10 shipping for every 2 shirts over 5 shirts. Burnt orange shirt with white siloutte. Sizes are L, XL, and XXL. XXL's ARE $3.00 MORE!!! 1. $18 +3.20 shipping =$21.20 2. $36 +3.20 shipping =$39.20 3. $52 +4.30 shipping =$56.30 4. $66 +4.30 shipping =$70.30 5. $80 +5.40 shipping =$85.40 Each shirt after 5 shirts is $16.00 each. Please add $1.10 shipping for every 2 shirts over 5 shirts. WE ALSO HAVE 3.5" x 3.5" PEELOUT VINYL STICKERS THAT GO GREAT ON WINDOWS. We will ship one free sticker per tshirt ordered. If you would like extras they are $2 each. Shipping prices reflect US Priority Mail which takes 2-3 day delivery. REMEMBER TO ADD $3.00 IF YOU WANT XXL. IF YOU DO NOT ADD THE $3.00 WE WILL SEND YOU AN XL INSTEAD. Please send check or money order to: JERIMIAH DOWDY PO BOX 2596 AUSTIN, TX 78768 Thank you for your time and have a Happy Easter. PS: If you are still skeptical about this offer, please send a Self Addressed Stamped Envelope along with your email address and/or telephone # and we will contact you to give you more information and a URL. We will not call you if it is long distance, so be sure to send an email address as well. THIS IS LIMITED OFFER! AFTER MAY 1, 1999, WE WILL NOT BE ACCEPTING ANY MORE ORDERS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 4:45:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id A01661521F for ; Sun, 4 Apr 1999 04:45:37 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id NAA25452 for ; Sun, 4 Apr 1999 13:43:39 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id NAA01246 for current@FreeBSD.ORG; Sun, 4 Apr 1999 13:42:51 +0200 (CEST) (envelope-from andreas) Date: Sun, 4 Apr 1999 13:42:50 +0200 From: Andreas Klemm To: current@FreeBSD.ORG Subject: different systat -vmstat output when using egcs to compile kernel Message-ID: <19990404134250.A995@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See the leading \n's in the Interrupts column (see !!!) 1st is ok using our cc 2nd is using egcs with different compile options. But error remains the same even with no optimitation -------------------------------------------------------------------------------- kernel compiled with FreeBSD 3.1-STABLE C compiler, -pipe -O -------------------------------------------------------------------------------- 1 users Load 0.97 0.39 0.16 So 4 Apr 12:41 Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out Act 35180 4348 3773760 6632 9000 count All 92160 14304 785608 20952 pages 91 cow Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt 430 zfod 236 total 1 3 21 88 597 909 237 60 582 15516 wire 100 clk0 irq2 52868 act 128 rtc0 irq8 5.3%Sys 0.2%Intr 47.6%User 0.0%Nice 47.0%Idl 16624 inact pci irq19 | | | | | | | | | | 6956 cache 7 pci irq17 ===>>>>>>>>>>>>>>>>>>>>>>>> 2044 free 1 pci irq16 daefr atkbd0 irq Namei Name-cache Dir-cache 29 prcfr psm0 irq12 Calls hits % hits % react ed0 irq10 1039 1015 98 3 0 pdwak isic0 irq9 pdpgs Discs ccd0 ccd1 ccd2 ccd3 da0 da1 da2 intrn KB/t 0.00 0.00 5.25 8.00 8.00 4.33 8.00 8345 buf tps 0 0 1 0 4 1 0 7506 desiredvnodes MB/s 0.00 0.00 0.00 0.00 0.03 0.00 0.00 1626 numvnodes 24 freevnodes -------------------------------------------------------------------------------- kernel compiled on FreeBSD 3.1-STABLE with egcs, tried these different compile options ... -mpentiumpro -pipe -O -pipe -O -mpentiumpro -pipe -pipe -------------------------------------------------------------------------------- 1 users Load 0.42 0.23 0.09 So 4 Apr 12:51 Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out Act 30724 3976 3736388 6632 11800 count All 92768 11544 736712 18172 pages cow Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt zfod 455 total 1 1 22 407 2 2533 456 264 1 13908 wire 243 \nclk0 irq ^^ !!! 53972 act 128 \nrtc0 irq ^^ !!! 9.0%Sys 0.4%Intr 4.3%User 0.0%Nice 86.3%Idl 14284 inact \natkbd0 i ^^ !!! | | | | | | | | | | 10404 cache 84 \npsm0 irq ^^ !!! =====>> 1396 free \ned0 irq1 ^^ !!! daefr \nisic0 ir ^^ !!! Namei Name-cache Dir-cache prcfr Calls hits % hits % react 3831 525 14 1994 52 pdwake pdpgs Discs ccd0 ccd1 ccd2 ccd3 da0 da1 da2 intrn KB/t 0.00 0.00 0.00 0.00 5.07 0.00 0.00 8343 buf tps 0 0 0 0 86 0 0 7503 desiredvnodes MB/s 0.00 0.00 0.00 0.00 0.42 0.00 0.00 1148 numvnodes 428 freevnodes -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 5:26:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mana.s.notwork.org (tok295.airnet.ne.jp [210.159.89.39]) by hub.freebsd.org (Postfix) with SMTP id 28BFF14D94 for ; Sun, 4 Apr 1999 05:26:10 -0700 (PDT) (envelope-from mrt@notwork.org) Received: (qmail 15147 invoked from network); 4 Apr 1999 12:24:14 -0000 Received: from kotonoha.s.notwork.org (192.168.1.1) by mana.s.notwork.org with SMTP; 4 Apr 1999 12:24:14 -0000 To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Cc: current@freebsd.org, wpaul@ctr.columbia.edu Subject: Re: More on rl0 woes X-cite: xcite 1.20 References: <199904040913.RAA26683@ariadne.tensor.pgs.com> MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII From: Murata Shuuichirou Date: 04 Apr 1999 21:24:12 +0900 In-Reply-To: <199904040913.RAA26683@ariadne.tensor.pgs.com> (Stephen Hocking-Senior Programmer PGS Tensor Perth's message of "Sun, 4 Apr 1999 17:13:25 +0800") Message-ID: <87soagd15f.fsf@kotonoha.s.notwork.org> Lines: 24 User-Agent: T-gnus/6.10.062 (based on Pterodactyl Gnus v0.80) SEMI/1.13.4 (Terai) FLIM/1.12.6 (=?ISO-8859-4?Q?Family-K=F2enmae?=) MULE XEmacs/21.2 (beta13) (Demeter) (i386-unknown-freebsd4.0) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904040913.RAA26683@ariadne.tensor.pgs.com>, `shocking@prth.pgs.com' wrote: > On the offchance that mty problems were chipset related, I swapped the > RealTek with the de0 card in my other machine, a 233MHz k6. It being a > socket 7 mboard presumably has a later PCI bios. Still the same symptoms - > hangs on NFS access. These can be interrupted and other network traffic > continues fine. To reproduce, take your RealTek equipped machine and place a > copy of /usr/src on it. Export /usr/src so that it can be NFS mounted by > other machines. From the other machines, do an ls -CFR of /usr/src. It will > hang partway through. I have probably same problem here. NFS hangs and other network traffic is still alive. Though, my situation differs a little from yours. I have two RealTek NFS clients and NFS server has another chip. Both of RealTek NFS clients (Celeron 300MHz and MediaGX 266MHz) have the problem. To reproduce: Install bytebench on the RealTek machine. Set env var TMPDIR to somewhere NFS mounted dir. Do "bytebench fstime". -- Murata Shuuichirou To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 5:50:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id DB6EB151F7 for ; Sun, 4 Apr 1999 05:50:08 -0700 (PDT) (envelope-from gjvc@extremis.demon.co.uk) Received: from [194.222.242.30] (helo=extremis.demon.co.uk) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 10TmJq-000CBJ-0C for freebsd-current@freebsd.org; Sun, 4 Apr 1999 12:48:12 +0000 Received: (from gjvc@localhost) by extremis.demon.co.uk (8.9.3/8.9.1) id MAA62774 for freebsd-current@freebsd.org; Sun, 4 Apr 1999 12:48:04 GMT (envelope-from gjvc) Date: Sun, 4 Apr 1999 12:48:04 +0000 From: George Cox To: freebsd-current@freebsd.org Subject: cvsupped libgcc grief Message-ID: <19990404124804.A35193@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, the troubles continue, after much buggering around with an incorrectly linked cc1 binary, cooked up from I don't know where I ask "Is anyone else seeing this kind of error on make buildworld'ing" In file included from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/config/i386/freebsd.h:28, from tm.h:1, from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/config/i386/xm-i386.h:43, from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/config/i386/xm-freebsd.h:3, from config.h:1, from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c:35: /usr/src/gnu/lib/libgcc/../../../contrib/gcc/config/i386/i386.h:530: syntax error before `,' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/config/i386/i386.h:540: warning: no semicolon at end of struct or union cc: Internal compiler error: program cc1 got fatal signal 11 -- [gjvc] FreeBSD-CURRENT -- Because I'm worth it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 6:22:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 13ADE14D8C for ; Sun, 4 Apr 1999 06:22:49 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id PAA09482 for current@FreeBSD.ORG; Sun, 4 Apr 1999 15:20:50 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id F01518848; Sun, 4 Apr 1999 13:43:30 +0200 (CEST) Date: Sun, 4 Apr 1999 13:43:30 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Message-ID: <19990404134330.B3397@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19990403225146.A99040@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Alex Zepeda on Sat, Apr 03, 1999 at 01:47:11PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alex Zepeda: > Personally, I'd vote for using the new runtime objects, and forcing binary > incompatibility. It's worth it IMO for the exception handling support if > nothing else. However, if you're dead set against it, just back up your > runtime objects, and edit the spec file (like the egcs port forced you to > do at one time, and probably still does). The problem I see is that exceptions are for C++ and forcing ANSI C files to be compiled with -fexceptions and linked with new runtime objects is probably not the best way... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 6:25:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 2019C14F90 for ; Sun, 4 Apr 1999 06:25:32 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id PAA09527 for current@FreeBSD.ORG; Sun, 4 Apr 1999 15:23:34 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id C570A8848; Sun, 4 Apr 1999 13:49:03 +0200 (CEST) Date: Sun, 4 Apr 1999 13:49:03 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Message-ID: <19990404134903.D3397@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199904031914.LAA56145@rah.star-gate.com> <19990403225146.A99040@keltia.freenix.fr> <19990403143433.A73396@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990403143433.A73396@nuxi.com>; from David E . O'Brien on Sat, Apr 03, 1999 at 02:34:33PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David E . O'Brien: > src/lib/csu/i386-elf will build and install crtbegin.o and crtend.o from > the EGCS sources. Otherwise we have to use the poorer exception > unwinding method. Is there a runtime overhead of using these files even for C programs ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 6:29:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id E539614F90; Sun, 4 Apr 1999 06:29:32 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.179]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2DC; Sun, 4 Apr 1999 15:27:32 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id PAA26256; Sun, 4 Apr 1999 15:28:05 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 04 Apr 1999 15:28:05 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Make world of 990404 14:20 GMT Cc: George Cox , George Cox , FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for the stats: ===> gnu/lib/libg++/doc ===> gnu/lib/libgcc cd: can't cd to /work/FreeBSD/src/gnu/lib/libgcc *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Looking in /usr/src/gnu/lib there's no libgcc directory, yet the Makefile proclaims: [asmodai@daemon] (15) # more Makefile # $Id: Makefile,v 1.20 1999/03/31 06:30:40 obrien Exp $ SUBDIR= libdialog libg++ libgcc libgmp libmp libobjc libregex libreadline libstdc++ .include Does the libgcc target have to be removed? --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 7:21:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 256C6151B5 for ; Sun, 4 Apr 1999 07:21:23 -0700 (PDT) (envelope-from tr49986@rcc.on.ca) Received: from rcc.on.ca (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with ESMTP id LAA02268 for ; Sun, 4 Apr 1999 11:37:58 -0400 Message-ID: <3707BBE3.D197F21C@rcc.on.ca> Date: Sun, 04 Apr 1999 15:22:11 -0400 From: Rod Taylor X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: More on rl0 woes References: <199904040913.RAA26683@ariadne.tensor.pgs.com> <87soagd15f.fsf@kotonoha.s.notwork.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On the offchance that mty problems were chipset related, I swapped the > > RealTek with the de0 card in my other machine, a 233MHz k6. It being a > > I have probably same problem here. NFS hangs and other > network traffic is still alive. Though, my situation > differs a little from yours. I have two RealTek NFS clients > and NFS server has another chip. Both of RealTek NFS clients > (Celeron 300MHz and MediaGX 266MHz) have the problem. > > To reproduce: > Install bytebench on the RealTek machine. > Set env var TMPDIR to somewhere NFS mounted dir. > Do "bytebench fstime". heh... i guess I too have similar problems. Though, I've always assumed it was nfs, not the network card. 3coms in the server, realteks in the clients. I've found that inbound traffic on a read-only mount doesn't hang anything. Heavy writes kill me all the time. (Make world for example). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 8:30:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id BEAF314F87 for ; Sun, 4 Apr 1999 08:30:16 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA21552; Sun, 4 Apr 1999 11:28:19 -0400 (EDT) Date: Sun, 4 Apr 1999 11:28:19 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: different systat -vmstat output when using egcs to compile kernel In-Reply-To: <19990404134250.A995@titan.klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Apr 1999, Andreas Klemm wrote: > See the leading \n's in the Interrupts column (see !!!) > 1st is ok using our cc > 2nd is using egcs with different compile options. > But error remains the same even with no optimitation Very strange. It could have something to do with the following, though, maybe? 1.160 Sun Apr 4 7:11:02 1999 UTC by alc CVS Tags: HEAD Diffs to 1.159 Two changes to vm_map_delete: 1. Don't bother checking object->ref_count == 1 in order to set OBJ_ONEMAPPING. It's a waste of time. If object->ref_count == 1, vm_map_entry_delete will "run-down" the object and its pages. 2. If object->ref_count == 1, ignore OBJ_ONEMAPPING. Wait for vm_map_entry_delete to "run-down" the object and its pages. Otherwise, we're calling two different procedures to delete the object's pages. Note: "vmstat -s" will once again show a non-zero value for "pages freed by exiting processes". Also, MAYBE the entire world needs to be compiled by egcs as well to have the correct sizes for structs and such, that might be different. > > -------------------------------------------------------------------------------- > kernel compiled with FreeBSD 3.1-STABLE C compiler, -pipe -O > -------------------------------------------------------------------------------- > 1 users Load 0.97 0.39 0.16 So 4 Apr 12:41 > > Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER > Tot Share Tot Share Free in out in out > Act 35180 4348 3773760 6632 9000 count > All 92160 14304 785608 20952 pages > 91 cow Interrupts > Proc:r p d s w Csw Trp Sys Int Sof Flt 430 zfod 236 total > 1 3 21 88 597 909 237 60 582 15516 wire 100 clk0 irq2 > 52868 act 128 rtc0 irq8 > 5.3%Sys 0.2%Intr 47.6%User 0.0%Nice 47.0%Idl 16624 inact pci irq19 > | | | | | | | | | | 6956 cache 7 pci irq17 > ===>>>>>>>>>>>>>>>>>>>>>>>> 2044 free 1 pci irq16 > daefr atkbd0 irq > Namei Name-cache Dir-cache 29 prcfr psm0 irq12 > Calls hits % hits % react ed0 irq10 > 1039 1015 98 3 0 pdwak isic0 irq9 > pdpgs > Discs ccd0 ccd1 ccd2 ccd3 da0 da1 da2 intrn > KB/t 0.00 0.00 5.25 8.00 8.00 4.33 8.00 8345 buf > tps 0 0 1 0 4 1 0 7506 desiredvnodes > MB/s 0.00 0.00 0.00 0.00 0.03 0.00 0.00 1626 numvnodes > 24 freevnodes > -------------------------------------------------------------------------------- > kernel compiled on FreeBSD 3.1-STABLE with egcs, > tried these different compile options ... > -mpentiumpro -pipe -O > -pipe -O > -mpentiumpro -pipe > -pipe > -------------------------------------------------------------------------------- > 1 users Load 0.42 0.23 0.09 So 4 Apr 12:51 > > Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER > Tot Share Tot Share Free in out in out > Act 30724 3976 3736388 6632 11800 count > All 92768 11544 736712 18172 pages > cow Interrupts > Proc:r p d s w Csw Trp Sys Int Sof Flt zfod 455 total > 1 1 22 407 2 2533 456 264 1 13908 wire 243 \nclk0 irq > ^^ !!! > 53972 act 128 \nrtc0 irq > ^^ !!! > 9.0%Sys 0.4%Intr 4.3%User 0.0%Nice 86.3%Idl 14284 inact \natkbd0 i > ^^ !!! > | | | | | | | | | | 10404 cache 84 \npsm0 irq > ^^ !!! > =====>> 1396 free \ned0 irq1 > ^^ !!! > daefr \nisic0 ir > ^^ !!! > Namei Name-cache Dir-cache prcfr > Calls hits % hits % react > 3831 525 14 1994 52 pdwake > pdpgs > Discs ccd0 ccd1 ccd2 ccd3 da0 da1 da2 intrn > KB/t 0.00 0.00 0.00 0.00 5.07 0.00 0.00 8343 buf > tps 0 0 0 0 86 0 0 7503 desiredvnodes > MB/s 0.00 0.00 0.00 0.00 0.42 0.00 0.00 1148 numvnodes > 428 freevnodes > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > http://www.freebsd.org/~fsmp/SMP/SMP.html > powered by Symmetric MultiProcessor FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 8:59:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 43CCB14E15 for ; Sun, 4 Apr 1999 08:59:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id IAA65108; Sun, 4 Apr 1999 08:54:38 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904041554.IAA65108@troutmask.apl.washington.edu> Subject: Re: contrib/egcs In-Reply-To: <199904040731.JAA72635@stiller.netland.inka.de> from Bernd Rosauer at "Apr 4, 1999 9:31:45 am" To: br@stiller.netland.inka.de (Bernd Rosauer) Date: Sun, 4 Apr 1999 08:54:38 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bernd Rosauer wrote: > Hi! > > I have noticed that egcs-1.1.2 made it into /usr/src/contrib. But 'make > buildworld' does not touch it. What is the intended use of egcs? > Are you running -current? Are you subscribed to the cvs-all and freebsd-current mailing lists? The intended use of egcs ti to compile files. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 9: 6:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id AF4A61503D for ; Sun, 4 Apr 1999 09:06:25 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id SAA14933; Sun, 4 Apr 1999 18:03:56 +0200 (CEST) Date: Sun, 4 Apr 1999 18:03:56 +0200 (CEST) From: Martin Blapp To: netchild@wurzelausix.CS.Uni-SB.DE Cc: freebsd-current@freebsd.org Subject: Re: Bug with afd0 (zip-drive) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have the same problems with Soren's new ATA driver: fuchur# mount_msdos -o noauto /dev/afd0s4 /zip mount_msdos: /dev/afd0s4: Invalid argument With the old driver and slice wfd0s4, this worked with msdos formatted zip-mediums. kernel konfig: -------------- controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives I've removed the old wdc* controller- and device- options completly. dmesg output with the old driver: --------------------------------- wdc1: unit 1 (atapi): , removable,intr,iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set dmesg output with the new driver: --------------------------------- (cvsup from 3 Apr) FreeBSD 4.0-CURRENT #6: Sat Apr 3 17:14:27 CEST 1999 root@fuchur.lan.attic.ch:/usr/src/sys/compile/FUCHUR ... ... acd0: CDROM drive at ata0 as master acd0: drive speed 5512KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked afd0: rewriteable drive at ata0 as slave afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: Unknown media (0x0) >Hi, I'm not able to use msdos disks with afd0. It isn't usable with the >mtools too (yes, I've used MAKEDEV to make the needed dev-nodes). > > cvsup at 7pm CET. > > "not able to use": > > mdir z: > init Z: non DOS media > Cannot initialize 'Z:' > > > mount /zip > msdos: /dev/afd0s4: Invalid argument > > Am I missing something? > > Bye, > Alexander. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 9:28: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 442DE14D40 for ; Sun, 4 Apr 1999 09:28:05 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA09813; Sun, 4 Apr 1999 11:36:38 -0500 (EST) Date: Sun, 4 Apr 1999 11:36:36 -0500 (EST) From: Alfred Perlstein To: Murata Shuuichirou Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.ORG, wpaul@ctr.columbia.edu Subject: Re: More on rl0 woes In-Reply-To: <87soagd15f.fsf@kotonoha.s.notwork.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4 Apr 1999, Murata Shuuichirou wrote: > In message <199904040913.RAA26683@ariadne.tensor.pgs.com>, > `shocking@prth.pgs.com' wrote: > > On the offchance that mty problems were chipset related, I swapped the > > RealTek with the de0 card in my other machine, a 233MHz k6. It being a > > socket 7 mboard presumably has a later PCI bios. Still the same symptoms - > > hangs on NFS access. These can be interrupted and other network traffic > > continues fine. To reproduce, take your RealTek equipped machine and place a > > copy of /usr/src on it. Export /usr/src so that it can be NFS mounted by > > other machines. From the other machines, do an ls -CFR of /usr/src. It will > > hang partway through. > > I have probably same problem here. NFS hangs and other > network traffic is still alive. Though, my situation > differs a little from yours. I have two RealTek NFS clients > and NFS server has another chip. Both of RealTek NFS clients > (Celeron 300MHz and MediaGX 266MHz) have the problem. > > To reproduce: > Install bytebench on the RealTek machine. > Set env var TMPDIR to somewhere NFS mounted dir. > Do "bytebench fstime". I have a solution and a workaround for you guys, solution: ditch the cheap PoS cards and get an fxp or xl card workaround: switch from UDP to TCP mounts or TCP to UDP, make sure the packet size used for the NFS mounts is a small value, try NFSv3, or if you are already using NFSv3, try NFSv2. Yes, the workaround seems like "just try several permutations", but I experianced the same problems, tweaking my NFS mounts, especially to use smaller read/write values made the problem go away. I think that switching to TCP may help. When i got some decent network hardware, my problems went away. -Alfred > > -- > Murata Shuuichirou > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Alfred Perlstein - Admin, coder, and admirer of all things BSD. -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 9:40:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 18D2A1526D for ; Sun, 4 Apr 1999 09:40:44 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA76205 for current@FreeBSD.ORG; Sun, 4 Apr 1999 09:38:48 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404093848.A76160@nuxi.com> Date: Sun, 4 Apr 1999 09:38:48 -0700 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: show stopper for EGCS import Reply-To: obrien@NUXI.com References: <19990403222515.A75073@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990403222515.A75073@nuxi.com>; from David O'Brien on Sat, Apr 03, 1999 at 10:25:15PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from > the EGCS source rather than our home-grown ones. ..snip.. > I've made the same fix to lib/csu as I did libgcc, but now am getting > the same weird "install" problem Poul-Henning was getting. Well FMH! I found a typo I made in Makefile.inc1. However, there is still a bootstrapping problem related to using the EGCS crtbegin.o/crtend.o. So boys and girls, are are going to use the "sjlj-exceptions" type exception machanism for a while. THE SWITCH HAS BEEN PULLED! -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 9:55:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 97B2E15080 for ; Sun, 4 Apr 1999 09:55:28 -0700 (PDT) (envelope-from andreasd@ifi.uio.no) Received: from skidbladnir.ifi.uio.no (3034@skidbladnir.ifi.uio.no [129.240.64.76]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA21712 for ; Sun, 4 Apr 1999 18:53:32 +0200 (MET DST) Received: (from andreasd@localhost) by skidbladnir.ifi.uio.no ; Sun, 4 Apr 1999 18:53:31 +0200 (MET DST) To: current@freebsd.org Subject: Re: WORM & CAM CD References: From: Andreas Dobloug Date: 04 Apr 1999 18:53:31 +0200 In-Reply-To: Message-ID: Lines: 8 User-Agent: Gnus/5.070066 (Pterodactyl Gnus v0.66) Emacs/20.3 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kenneth D. Merry | > Has the worm driver been taken out of current? | Yes. You have to use cdrecord now for SCSI CD burners. cdrecord lacks support for a whole lot of CD-burners... -- Andreas Dobloug : email: andreasd@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 10:34:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from csmd2.cs.uni-magdeburg.de (csmd2.CS.Uni-Magdeburg.De [141.44.22.2]) by hub.freebsd.org (Postfix) with ESMTP id A919A14E15 for ; Sun, 4 Apr 1999 10:34:31 -0700 (PDT) (envelope-from jesse@mail.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (jesse@knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.9.1a/8.9.1) with ESMTP id TAA01416 for ; Sun, 4 Apr 1999 19:32:34 +0200 (MET DST) Received: (from jesse@localhost) by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id TAA24451; Sun, 4 Apr 1999 19:32:42 +0200 (MET DST) From: Roland Jesse MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14087.41529.948562.990465@cs.uni-magdeburg.de> Date: Sun, 4 Apr 1999 19:32:41 +0200 (MET DST) To: freebsd-current@freebsd.org Subject: Linuxthreads & /usr/src/include/pthread/uthread/pthread.h X-Mailer: VM 6.70 under 20.4 "Emerald" XEmacs Lucid Reply-To: jesse@mail.CS.Uni-Magdeburg.De X-Pgp-Fingerprint: 5D 08 5A E3 B4 AA 68 C1 FF 67 06 29 62 DD 9A D7 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Linuxthreads (http://lt.tar.com/) is supposed to "compile cleanly against 4.0-current after March 22." (quote from the mentioned web page) However, I cvsuped -current on March 31. As the Makefile for the linuxthreads port contains: .if !exists(${SRC_BASE}/include/pthread/uthread/pthread.h) BROKEN= "requires pthread.h from /usr/src/include/pthread/uthread" .endif and this file does not exist, it failed to do a 'make' in /usr/ports/devel/linuxthreads. In case it matters: I am actually running 3.1-stable (as of March 25) and only cvsuped the -current source without making the world. (I do not really want to switch over to -current if I don't really have to.) Any ideas about what I am missing here? Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 10:41:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1D73D14F39 for ; Sun, 4 Apr 1999 10:41:39 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id KAA10758; Sun, 4 Apr 1999 10:39:43 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id KAA27506; Sun, 4 Apr 1999 10:39:42 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 4 Apr 1999 10:39:42 -0700 (PDT) Message-Id: <199904041739.KAA27506@vashon.polstra.com> To: obrien@NUXI.com Subject: Re: show stopper for EGCS import In-Reply-To: <19990403222515.A75073@nuxi.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990403222515.A75073@nuxi.com>, David O'Brien wrote: > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o > from the EGCS source rather than our home-grown ones. This > afternoon I switch my EGCS development machine back to a purely > stock 4.0 SNAPSHOT and found that GCC 2.7.2 cannot compile the new > sources. I guess if you can't find a better solution, you could always fall back on a hack like this for crt{begin,end}.c: #if __GNUC__ > 2 || __GNUC__ == 2 && __GNUC_MINOR__ >= 91 #include #else #include #endif John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 10:42:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 1791614F39 for ; Sun, 4 Apr 1999 10:42:30 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id KAA62815; Sun, 4 Apr 1999 10:39:15 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904041739.KAA62815@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: show stopper for EGCS import In-reply-to: Your message of "Sun, 04 Apr 1999 09:38:48 PDT." <19990404093848.A76160@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Apr 1999 10:39:15 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cool, What do you mean by: we are going to have to use ""sjlj-exceptions" type exception machanism for a while? Tnks, Amancio > > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from > > the EGCS source rather than our home-grown ones. > ..snip.. > > I've made the same fix to lib/csu as I did libgcc, but now am getting > > the same weird "install" problem Poul-Henning was getting. > > Well FMH! I found a typo I made in Makefile.inc1. However, there is > still a bootstrapping problem related to using the EGCS > crtbegin.o/crtend.o. So boys and girls, are are going to use the > "sjlj-exceptions" type exception machanism for a while. > > THE SWITCH HAS BEEN PULLED! > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 10:50:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5B7B715018 for ; Sun, 4 Apr 1999 10:50:18 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id KAA76438; Sun, 4 Apr 1999 10:48:22 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404104822.I75313@nuxi.com> Date: Sun, 4 Apr 1999 10:48:22 -0700 From: "David O'Brien" To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: show stopper for EGCS import Reply-To: obrien@NUXI.com References: <19990404093848.A76160@nuxi.com> <199904041739.KAA62815@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904041739.KAA62815@rah.star-gate.com>; from Amancio Hasty on Sun, Apr 04, 1999 at 10:39:15AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 04, 1999 at 10:39:15AM -0700, Amancio Hasty wrote: > > What do you mean by: we are going to have to use ""sjlj-exceptions" type > exception machanism for a while? -fsjlj-exceptions is on by default. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 11: 2:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-26.ppp.wenet.net [206.15.85.26]) by hub.freebsd.org (Postfix) with ESMTP id 0D1AE14F39 for ; Sun, 4 Apr 1999 11:02:56 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id LAA88849; Sun, 4 Apr 1999 11:01:11 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sun, 4 Apr 1999 11:01:11 -0700 (PDT) From: Alex Zepeda To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: show stopper for EGCS import In-Reply-To: <19990404093848.A76160@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Apr 1999, David O'Brien wrote: > > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from > > the EGCS source rather than our home-grown ones. > ..snip.. > > I've made the same fix to lib/csu as I did libgcc, but now am getting > > the same weird "install" problem Poul-Henning was getting. > > Well FMH! I found a typo I made in Makefile.inc1. However, there is > still a bootstrapping problem related to using the EGCS > crtbegin.o/crtend.o. So boys and girls, are are going to use the > "sjlj-exceptions" type exception machanism for a while. Is there any way to tell gcc not to do this by default, or should I stick to my egcs built from ports (complete with egcs runtime objets) for now? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 11:11:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 8860214F39 for ; Sun, 4 Apr 1999 11:11:03 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id LAA62995; Sun, 4 Apr 1999 11:07:48 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904041807.LAA62995@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: show stopper for EGCS import In-reply-to: Your message of "Sun, 04 Apr 1999 10:48:22 PDT." <19990404104822.I75313@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Apr 1999 11:07:48 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why are exceptions handling on by default better yet do we know why exception handling is not needed by default with gcc-2.8? and has anyone spent time reading the egcs requirements for exception handling? Amancio > On Sun, Apr 04, 1999 at 10:39:15AM -0700, Amancio Hasty wrote: > > > > What do you mean by: we are going to have to use ""sjlj-exceptions" type > > exception machanism for a while? > > -fsjlj-exceptions is on by default. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 11:14:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 01831152D0 for ; Sun, 4 Apr 1999 11:14:37 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA76512; Sun, 4 Apr 1999 11:12:41 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404111241.J75313@nuxi.com> Date: Sun, 4 Apr 1999 11:12:41 -0700 From: "David O'Brien" To: Alex Zepeda Cc: current@FreeBSD.ORG Subject: Re: show stopper for EGCS import Reply-To: obrien@NUXI.com References: <19990404093848.A76160@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alex Zepeda on Sun, Apr 04, 1999 at 11:01:11AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "sjlj-exceptions" type exception machanism for a while. > > Is there any way to tell gcc not to do this by default, Yes, "-fno-sjlj-exceptions", but you will proably get core dumps when you throw an exception. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 12: 7:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E57C14CBB for ; Sun, 4 Apr 1999 12:07:48 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id UAA03131; Sun, 4 Apr 1999 20:05:50 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 4 Apr 1999 20:03:38 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19990403162851.A73829@nuxi.com> References: <22045.923184968@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Apr 03, 1999 at 04:16:08PM -0800 <22045.923184968@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 4 Apr 1999 20:03:48 +0000 To: obrien@NUXI.com From: Bob Bishop Subject: Looks broken to me... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, -------------------------------------------------------------- >>> Rebuilding tools needed to build libraries -------------------------------------------------------------- [...] ===> cc_int make: don't know how to make insn-attrtab.c. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 12:14: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0D2AC1502C for ; Sun, 4 Apr 1999 12:14:03 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA08063; Sun, 4 Apr 1999 13:12:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA84643; Sun, 4 Apr 1999 13:12:46 -0600 (MDT) Message-Id: <199904041912.NAA84643@harmony.village.org> To: obrien@NUXI.com Subject: World Breakage? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 04 Apr 1999 09:38:48 PDT." <19990404093848.A76160@nuxi.com> References: <19990404093848.A76160@nuxi.com> <19990403222515.A75073@nuxi.com> Date: Sun, 04 Apr 1999 13:12:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990404093848.A76160@nuxi.com> "David O'Brien" writes: : THE SWITCH HAS BEEN PULLED! cc -O -pipe -DFREEBSD_ELF -I/home/imp/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc -I/home/imp/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/home/imp/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_tools -I/home/imp/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_tools -I/usr/obj/home/imp/FreeBSD/src/tmp/usr/include -static -o cc gcc.o /usr/obj/home/imp/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a /usr/obj/home/imp/FreeBSD/src/tmp/usr/lib/libc.a(mktemp.o): In function `mkstemps': mktemp.o(.text+0x0): multiple definition of `mkstemps' /usr/obj/home/imp/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(mkstemp.o)(.text+0x0): first defined here /usr/libexec/elf/ld: Warning: size of symbol `mkstemps' changed from 573 to 39 in mktemp.o I suspect that mkstemp shouldn't be defined in libcc_drv.a. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 12:40:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 69F1B15280 for ; Sun, 4 Apr 1999 12:40:09 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id VAA15268; Sun, 4 Apr 1999 21:38:12 +0200 (CEST) Date: Sun, 4 Apr 1999 21:38:12 +0200 (CEST) From: Martin Blapp To: freebsd-current@freebsd.org Cc: rb@gid.co.uk Subject: Re: Looks broken to me... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Only if you make world with -j x ... without -j it's working. make buildworld -j10 > /tmp/build.out 2>&1 & breaks the same time making the cc_tools : `gencheck.c' is up to date. `c-parse.in' is up to date. `gencheck.c' is up to date. `c-parse.in' is up to date. ===> cc_int make: don't know how to make insn-attrtab.c. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 12:43:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 7496015281 for ; Sun, 4 Apr 1999 12:43:42 -0700 (PDT) (envelope-from camel@avias.com) Received: from CAMEL (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.2/8.9.2) with SMTP id XAA30866 for ; Sun, 4 Apr 1999 23:41:36 +0400 (MSD) (envelope-from camel@avias.com) Date: Sun, 4 Apr 1999 23:41:01 +0400 From: Ilya Naumov X-Mailer: The Bat! (v1.22) UNREG Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <4986.990404@avias.com> To: Bob Bishop Subject: Re: Looks broken to me... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Bob, Monday, April 05, 1999, 12:03:48 AM, you wrote: BB> -------------------------------------------------------------- >>>> Rebuilding tools needed to build libraries BB> -------------------------------------------------------------- BB> [...] ===>> cc_int BB> make: don't know how to make insn-attrtab.c. Stop BB> *** Error code 2 BB> 1 error BB> *** Error code 2 BB> 1 error BB> *** Error code 2 BB> 1 error BB> *** Error code 2 BB> 1 error BB> *** Error code 2 BB> 1 error try "make clean" before building world. but it is seems to be broken anyway: c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe -fno-for-scope -I/usr/src/gnu/usr.bin/groff/libgroff/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -fno-rtti -fno-exceptions -c /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc -o new.o *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 12:57:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9087E152AE for ; Sun, 4 Apr 1999 12:57:49 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA25146; Sun, 4 Apr 1999 12:55:41 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: show stopper for EGCS import In-reply-to: Your message of "Sun, 04 Apr 1999 09:38:48 PDT." <19990404093848.A76160@nuxi.com> Date: Sun, 04 Apr 1999 12:55:41 -0700 Message-ID: <25144.923255741@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG YAY!! David, consider yourself signed up for a six pack of anything you like to drink come the next USENIX. First 6 beers are on me (assuming you don't mind if I pound a 7-up for each beer you drink, that is). :-) - Jordan > > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from > > the EGCS source rather than our home-grown ones. > ..snip.. > > I've made the same fix to lib/csu as I did libgcc, but now am getting > > the same weird "install" problem Poul-Henning was getting. > > Well FMH! I found a typo I made in Makefile.inc1. However, there is > still a bootstrapping problem related to using the EGCS > crtbegin.o/crtend.o. So boys and girls, are are going to use the > "sjlj-exceptions" type exception machanism for a while. > > THE SWITCH HAS BEEN PULLED! > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 13: 0:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F79E14D5A for ; Sun, 4 Apr 1999 13:00:42 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id NAA17607; Sun, 4 Apr 1999 13:58:39 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199904041958.NAA17607@panzer.plutotech.com> Subject: Re: WORM & CAM CD In-Reply-To: from Andreas Dobloug at "Apr 4, 1999 6:53:31 pm" To: andreasd@ifi.uio.no (Andreas Dobloug) Date: Sun, 4 Apr 1999 13:58:39 -0600 (MDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Dobloug wrote... > * Kenneth D. Merry > | > Has the worm driver been taken out of current? > | Yes. You have to use cdrecord now for SCSI CD burners. > > cdrecord lacks support for a whole lot of CD-burners... Oh really? The old Worm driver only supported HP/Philips and Plasmon drives. cdrecord supports those drives, and many more. What CD burner do you have that cdrecord doesn't support? Have you talked to Joerg Schilling about it? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 13: 4:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id C40251501E for ; Sun, 4 Apr 1999 13:04:38 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: (wpaul@localhost) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) id QAA14549; Sun, 4 Apr 1999 16:02:30 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Message-Id: <199904042002.QAA14549@sirius.ctr.columbia.edu> Subject: Re: More on rl0 woes To: bright@rush.net (Alfred Perlstein) Date: Sun, 4 Apr 1999 16:02:29 -0400 (EDT) Cc: mrt@notwork.org, shocking@prth.pgs.com, current@freebsd.org In-Reply-To: from "Alfred Perlstein" at Apr 4, 99 11:36:36 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Alfred Perlstein had to walk into mine and say: > On 4 Apr 1999, Murata Shuuichirou wrote: > > > In message <199904040913.RAA26683@ariadne.tensor.pgs.com>, > > `shocking@prth.pgs.com' wrote: > > > On the offchance that mty problems were chipset related, I swapped the > > > RealTek with the de0 card in my other machine, a 233MHz k6. It being a > > > socket 7 mboard presumably has a later PCI bios. Still the same symptoms - > > > hangs on NFS access. These can be interrupted and other network traffic > > > continues fine. To reproduce, take your RealTek equipped machine and place a > > > copy of /usr/src on it. Export /usr/src so that it can be NFS mounted by > > > other machines. From the other machines, do an ls -CFR of /usr/src. It will > > > hang partway through. > > > > I have probably same problem here. NFS hangs and other > > network traffic is still alive. Though, my situation > > differs a little from yours. I have two RealTek NFS clients > > and NFS server has another chip. Both of RealTek NFS clients > > (Celeron 300MHz and MediaGX 266MHz) have the problem. Wait wait wait! You're claiming you have the same problem your configurations are different! He's saying he has a problem when the RealTek card is in the server, and the client is using some other NIC. You're saying you have a problem when the RealTek in the client, and the server is using some other NIC. These are completely different scenarios! I will not allow a bunch of you to all jump on me at the same time claiming you've all got the same problem when you CLEARLY DON'T! EVERYBODY PAY ATTENTION TO WHAT THE OTHER IS SAYING AND WAIT YOUR DAMN TURN OR I'M JUST GOING TO IGNORE THE WHOLE LOT OF YOU AND YOU CAN FIX YOUR OWN DAMN PROBLEMS! I can't believe I'm getting so worked up because you cheap bastards insist on buying the absolute worst network adapter in the world. Go buy an ASIX card for crying out loud. They're cheap, and they actually work worth a damn. Now, as punishment for making me mad, I'm going to address Steven's problem, and the rest of you can just lump it. There are things you should be checking when your problem happens. What does ifconfig rl0 show you? Is the OACTIVE flag set? What does netstat -in say? What does netstat -m say? You say 'traffic continues normally.' This is very confusing: SHOW ME AN EXAMPLE OF WHAT YOU MEAN. When the NFS transfer stops, can you still ping the server host, or do you have to interrupt the transfer and wait for a while before you can communicate with the server again? Can you run tcpdump on the client and observe what happens when the transfer stops? Is the client still sending out read requests? Is the server replying or not? Are the replies garbled? Is there a lot of other activity on the network at the time? Can you initiate another (smaller) NFS transfer when the first one wedges? You have to give me as much information as you can. I need to be able to clearly identify the symptoms of the problem with out all the 'oh my god it doesn't work and I tried this and this and this' crap. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 13:14:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3A1AB14CAD for ; Sun, 4 Apr 1999 13:14:15 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA77062; Sun, 4 Apr 1999 13:12:05 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404131205.A77056@nuxi.com> Date: Sun, 4 Apr 1999 13:12:05 -0700 From: "David O'Brien" To: Ilya Naumov , Bob Bishop Subject: Re: Looks broken to me... Reply-To: obrien@NUXI.com References: <4986.990404@avias.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4986.990404@avias.com>; from Ilya Naumov on Sun, Apr 04, 1999 at 11:41:01PM +0400 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe -fno-for-scope -I/usr/src/gnu/usr.bin/groff/libgroff/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -fno-rtti -fno-exceptions -c /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc -o new.o > *** Error code 1 Did you get any other output? While ``make'' saw an error, ``c++'' didn't report it for some reason. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 13:18: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BAAFF14D5A; Sun, 4 Apr 1999 13:18:06 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA77082; Sun, 4 Apr 1999 13:16:10 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404131610.B77056@nuxi.com> Date: Sun, 4 Apr 1999 13:16:10 -0700 From: "David O'Brien" To: current@freebsd.org, freebsd-alpha@freebsd.org Subject: EGCS and Alpha builds Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I should mention that ``make world'' on the alpha should be considered totally broken until an Alpha developer can tweak the contrib/egcs/gcc/config/freebsd.h and contrib/egcs/gcc/config/alpha/freebsd*.h bits. I would really like to see contrib/egcs/gcc/config/alpha/freebsd*.h combined into one file. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 13:22:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 42C6114CAD for ; Sun, 4 Apr 1999 13:22:51 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id VAA03682; Sun, 4 Apr 1999 21:20:54 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 4 Apr 1999 21:13:17 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 4 Apr 1999 21:13:27 +0000 To: Martin Blapp From: Bob Bishop Subject: Re: Looks broken to me... Cc: obrien@NUXI.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 9:38 pm +0200 4/4/99, Martin Blapp wrote: >Only if you make world with -j x ... >without -j it's working. > >make buildworld -j10 > /tmp/build.out 2>&1 & >breaks the same time making the cc_tools : > >`gencheck.c' is up to date. >`c-parse.in' is up to date. >`gencheck.c' is up to date. >`c-parse.in' is up to date. >===> cc_int >make: don't know how to make insn-attrtab.c. Stop >*** Error code 2 >1 error >*** Error code 2 >1 error >*** Error code 2 >1 error >*** Error code 2 Looks like you're right. Bit of a bummer if you are running SMP... -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 13:23:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E2E7215309 for ; Sun, 4 Apr 1999 13:23:12 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA77104; Sun, 4 Apr 1999 13:21:14 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404132114.C77056@nuxi.com> Date: Sun, 4 Apr 1999 13:21:14 -0700 From: "David O'Brien" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: World Breakage? Reply-To: obrien@NUXI.com References: <19990404093848.A76160@nuxi.com> <19990403222515.A75073@nuxi.com> <19990404093848.A76160@nuxi.com> <199904041912.NAA84643@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904041912.NAA84643@harmony.village.org>; from Warner Losh on Sun, Apr 04, 1999 at 01:12:46PM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /usr/obj/home/imp/FreeBSD/src/tmp/usr/lib/libc.a(mktemp.o): In function `mkstemps': > mktemp.o(.text+0x0): multiple definition of `mkstemps' > /usr/obj/home/imp/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(mkstemp.o)(.text+0x0): first defined here > /usr/libexec/elf/ld: Warning: size of symbol `mkstemps' changed from 573 to 39 in mktemp.o I can't duplicate this problem. Just to be sure... you aren't using -DNOCLEAN, -O2 or anything like that, right? Would it be possible for you to take the March 31st CURRENT snapshot, do a fresh CVSup/cvs checkout and try a build? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 13:25:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E3EA814E05 for ; Sun, 4 Apr 1999 13:25:16 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA77126; Sun, 4 Apr 1999 13:23:12 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404132312.D77056@nuxi.com> Date: Sun, 4 Apr 1999 13:23:12 -0700 From: "David O'Brien" To: Martin Blapp , freebsd-current@FreeBSD.ORG Cc: rb@gid.co.uk Subject: Re: Looks broken to me... Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Martin Blapp on Sun, Apr 04, 1999 at 09:38:12PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Only if you make world with -j x ... > without -j it's working. OH YES! DON'T -j at this time. I know there are a few dependency problems in the Makefiles at this time. I wanted to do the minimum number of changes to them to get EGCS'ifed. (so cvs diff would be useful) They will be cleaned up once people are successfully doing `make world's. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 13:27:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1273014E05 for ; Sun, 4 Apr 1999 13:27:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA08289; Sun, 4 Apr 1999 14:25:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA31920; Sun, 4 Apr 1999 14:26:07 -0600 (MDT) Message-Id: <199904042026.OAA31920@harmony.village.org> To: obrien@NUXI.com Subject: Re: World Breakage? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 04 Apr 1999 13:21:14 PDT." <19990404132114.C77056@nuxi.com> References: <19990404132114.C77056@nuxi.com> <19990404093848.A76160@nuxi.com> <19990403222515.A75073@nuxi.com> <19990404093848.A76160@nuxi.com> <199904041912.NAA84643@harmony.village.org> Date: Sun, 04 Apr 1999 14:26:07 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990404132114.C77056@nuxi.com> "David O'Brien" writes: : I can't duplicate this problem. Just to be sure... you aren't using : -DNOCLEAN, -O2 or anything like that, right? : : Would it be possible for you to take the March 31st CURRENT snapshot, do : a fresh CVSup/cvs checkout and try a build? I already have mkstemps in my tree. I had imported it from OpenBSD a while ago, but hadn't committed it. I'll do that now, as well as remove the mktemp.c from the offending makefile. It works w/o it and eliminates an XXX comment. So you shouldn't be able to reproduce this in a clean tree. :-) Warner P.S. here's what I have in my tree that I'll commit soon. Index: mktemp.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/lib/libc/stdio/mktemp.c,v retrieving revision 1.12 diff -d -u -r1.12 mktemp.c --- mktemp.c 1998/10/20 15:33:21 1.12 +++ mktemp.c 1999/04/04 19:31:50 @@ -50,29 +50,39 @@ char *_mktemp __P((char *)); -static int _gettemp __P((char *, int *, int)); +static int _gettemp __P((char *, int *, int, int)); int +mkstemps(path, slen) + char *path; + int slen; +{ + int fd; + + return (_gettemp(path, &fd, 0, slen) ? fd : -1); +} + +int mkstemp(path) char *path; { int fd; - return (_gettemp(path, &fd, 0) ? fd : -1); + return (_gettemp(path, &fd, 0, 0) ? fd : -1); } char * mkdtemp(path) char *path; { - return(_gettemp(path, (int *)NULL, 1) ? path : (char *)NULL); + return(_gettemp(path, (int *)NULL, 1, 0) ? path : (char *)NULL); } char * _mktemp(path) char *path; { - return(_gettemp(path, (int *)NULL, 0) ? path : (char *)NULL); + return(_gettemp(path, (int *)NULL, 0, 0) ? path : (char *)NULL); } #ifdef UNSAFE_WARN @@ -88,12 +98,13 @@ } static int -_gettemp(path, doopen, domkdir) +_gettemp(path, doopen, domkdir, slen) char *path; register int *doopen; int domkdir; + int slen; { - register char *start, *trv; + register char *start, *trv, *suffp; struct stat sbuf; int pid, rval; @@ -105,7 +116,13 @@ pid = getpid(); for (trv = path; *trv; ++trv) ; + trv -= slen; + suffp = trv; --trv; + if (trv < path) { + errno = EINVAL; + return (0); + } while (*trv == 'X' && pid != 0) { *trv-- = (pid % 10) + '0'; pid /= 10; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 14: 8:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from dei.calldei.com (dei.calldei.com [205.179.37.1]) by hub.freebsd.org (Postfix) with ESMTP id 67149152FF for ; Sun, 4 Apr 1999 14:08:25 -0700 (PDT) (envelope-from chris@calldei.com) Received: (from chris@localhost) by dei.calldei.com (8.9.0/8.9.0) id OAA20121 for freebsd-current@freebsd.org; Sun, 4 Apr 1999 14:06:28 -0700 (PDT) Date: Sun, 4 Apr 1999 14:06:28 -0700 (PDT) From: Chris Costello Message-Id: <199904042106.OAA20121@dei.calldei.com> To: freebsd-current@freebsd.org Subject: 4.0-CURRENT world broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The FreeBSD 4.0-CURRENT world appears to be broken. The file that appears to be causing the problem is pthread_private.h, included by isatty.c. I can't find anything as to what's causing the breakage _yet_, but I hope to produce a patch today. I CVSup'd only minutes ago. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 14:10:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 06619152FA for ; Sun, 4 Apr 1999 14:10:28 -0700 (PDT) (envelope-from ctapang@aracnet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id OAA12533; Sun, 4 Apr 1999 14:08:24 -0700 Message-ID: <041a01be7edf$84fe7cf0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: , Subject: Re: Linuxthreads & /usr/src/include/pthread/uthread/pthread.h Date: Sun, 4 Apr 1999 14:10:08 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try doing a "make buildworld". The .if statement in the linuxthreads Makefile prevents people from using the wrong version of pthread.h. There is another pthread.h that pertains to using the Posix threads library. Carlos C. Tapang http://www.genericwindows.com -----Original Message----- From: Roland Jesse To: freebsd-current@FreeBSD.ORG Date: Sunday, April 04, 1999 10:32 AM Subject: Linuxthreads & /usr/src/include/pthread/uthread/pthread.h >Hi, > >Linuxthreads (http://lt.tar.com/) is supposed to "compile cleanly >against 4.0-current after March 22." (quote from the mentioned web >page) > >However, I cvsuped -current on March 31. As the Makefile for the >linuxthreads port contains: > >.if !exists(${SRC_BASE}/include/pthread/uthread/pthread.h) >BROKEN= "requires pthread.h from /usr/src/include/pthread/uthread" >.endif > >and this file does not exist, it failed to do a 'make' in >/usr/ports/devel/linuxthreads. > >In case it matters: I am actually running 3.1-stable (as of March 25) >and only cvsuped the -current source without making the world. (I do >not really want to switch over to -current if I don't really have to.) > >Any ideas about what I am missing here? > > Roland > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 14:11:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1BC77152FA; Sun, 4 Apr 1999 14:11:11 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA79101; Sun, 4 Apr 1999 22:11:17 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 4 Apr 1999 22:11:17 +0100 (BST) From: Doug Rabson To: "David O'Brien" Cc: current@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: EGCS and Alpha builds In-Reply-To: <19990404131610.B77056@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Apr 1999, David O'Brien wrote: > I should mention that ``make world'' on the alpha should be considered > totally broken until an Alpha developer can tweak the > contrib/egcs/gcc/config/freebsd.h and > contrib/egcs/gcc/config/alpha/freebsd*.h > bits. I would really like to see > contrib/egcs/gcc/config/alpha/freebsd*.h combined into one file. I'll try to take a look tomorrow but I have visitors coming so I can't promise anything. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 14:34:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.ne.mediaone.net (jbloom.ne.mediaone.net [24.128.100.196]) by hub.freebsd.org (Postfix) with ESMTP id 7946814E0A for ; Sun, 4 Apr 1999 14:34:38 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by jbloom.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id RAA00449; Sun, 4 Apr 1999 17:32:08 -0400 (EDT) (envelope-from bloom@acm.org) Message-ID: <3707DA58.AE49C2C0@acm.org> Date: Sun, 04 Apr 1999 17:32:08 -0400 From: Jim Bloom X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@NUXI.com Cc: Ilya Naumov , current@FreeBSD.ORG Subject: Re: Looks broken to me... References: <4986.990404@avias.com> <19990404131205.A77056@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get the same error. This is more to the error message which I have included below. I am doing a "make buildworld" after deleting everything in /usr/obj. Cvsup from freebsd3.freebsd.org at around 21:00 GMT. Jim Bloom bloom@acm.org c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe -fno-for-scope -I/usr/src/gnu/usr.bin/groff/libgroff/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -fno-rtti -fno-exceptions -c /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc -o new.o In file included from /usr/obj/usr/src/tmp/usr/include/g++/osfcn.h:5, from /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include/posix.h:25, from /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc:24: /usr/obj/usr/src/tmp/usr/include/g++/std.h:23: stddef: No such file or directory *** Error code 1 Stop. David O'Brien wrote: > > > c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe -fno-for-scope -I/usr/src/gnu/usr.bin/groff/libgroff/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -fno-rtti -fno-exceptions -c /usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc -o new.o > > *** Error code 1 > > Did you get any other output? While ``make'' saw an error, ``c++'' > didn't report it for some reason. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 14:57:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E4F9514E28 for ; Sun, 4 Apr 1999 14:57:19 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id OAA77653; Sun, 4 Apr 1999 14:55:18 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404145518.A77643@nuxi.com> Date: Sun, 4 Apr 1999 14:55:18 -0700 From: "David O'Brien" To: Chris Costello , freebsd-current@FreeBSD.ORG Subject: Re: 4.0-CURRENT world broken Reply-To: obrien@NUXI.com References: <199904042106.OAA20121@dei.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904042106.OAA20121@dei.calldei.com>; from Chris Costello on Sun, Apr 04, 1999 at 02:06:28PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The FreeBSD 4.0-CURRENT world appears to be broken. The file that > appears to be causing the problem is pthread_private.h, included by > isatty.c. You're the only one reporting this problem. Possibly your /usr/obj isn't clean? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 15: 0:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 9236014E28 for ; Sun, 4 Apr 1999 15:00:48 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id XAA09179 for ; Sun, 4 Apr 1999 23:58:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id XAA53845 for ; Sun, 4 Apr 1999 23:58:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: 8MB machine hangs in 'newbuf' From: Poul-Henning Kamp Date: Sun, 04 Apr 1999 23:58:38 +0200 Message-ID: <53843.923263118@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to install -CURRENT on a 8MB machine, and it invariably seems to hang sooner or later in "newbuf". What have we done recently which would screw small-RAM machines ? It seems to run fine on the 0318 SNAP, so that should provide some timeframe... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 15: 8: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [206.154.101.226]) by hub.freebsd.org (Postfix) with ESMTP id E9C1114E28 for ; Sun, 4 Apr 1999 15:07:59 -0700 (PDT) (envelope-from staylor@mrynet.com) Received: (from staylor@localhost) by mrynet.com (8.9.3/8.9.3) id PAA97205 for freebsd-current@freebsd.org; Sun, 4 Apr 1999 15:06:08 -0700 (PDT) (envelope-from staylor) Message-Id: <199904042206.PAA97205@mrynet.com> From: staylor@mrynet.com (S. Akmentins-Teilors) Date: Sun, 4 Apr 1999 15:06:08 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: WORLD failing in sys/boot/i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CVSup'd at approx 1100 Pacific time: ===> sys/boot/i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/boot/i386/boot2/boot2.c (cd /usr/src/sys/boot/i386/boot2; m4 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 sio.s) | as -o sio.o ld -nostdlib -static -N -Ttext 0x1000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x1000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.01 size=6f0 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=1520 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1e10 text=200 data=1c10 org=0 entry=0 -16 bytes available *** Error code 1 Stop. Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@idt.net, staylor@mrynet.lv Westlake Village, CA USA (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 15:12:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id BED0C14E0A for ; Sun, 4 Apr 1999 15:12:21 -0700 (PDT) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id PAA00335; Sun, 4 Apr 1999 15:10:16 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.2.0.32.19990404150920.00a33cf0@216.101.162.50> X-Sender: null@216.101.162.50 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.32 (Beta) Date: Sun, 04 Apr 1999 15:10:14 -0700 To: staylor@mrynet.com (S. Akmentins-Teilors), freebsd-current@FreeBSD.ORG From: Manfred Antar Subject: Re: WORLD failing in sys/boot/i386 In-Reply-To: <199904042206.PAA97205@mrynet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:06 PM 4/4/99 +0000, S. Akmentins-Teilors wrote: >CVSup'd at approx 1100 Pacific time: > >===> sys/boot/i386/boot2 >(cd /usr/src/sys/boot/i386/boot2; m4 boot1.m4 boot1.s) | as -o boot1.o >ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o >objcopy -S -O binary boot1.out boot1 >dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null >cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -O2 >-malign-functions=0 -malign-jumps=0 >-malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast >-Wcast-align -Wmissing-declarations >-Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow >-Wstrict-prototypes -Wwrite-strings >-I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/boot/i386/boot2/boot2.c >(cd /usr/src/sys/boot/i386/boot2; m4 >-DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 sio.s) | as -o sio.o >ld -nostdlib -static -N -Ttext 0x1000 -o >boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o >boot2.o sio.o >objcopy -S -O binary boot2.out boot2.bin >btxld -v -E 0x1000 -f bin -b >/usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o >boot2.ld -P >1 boot2.bin >kernel: ver=1.01 size=6f0 load=9000 entry=9010 map=16M pgctl=1:1 >client: fmt=bin size=1520 text=0 data=0 bss=0 entry=0 >output: fmt=bin size=1e10 text=200 data=1c10 org=0 entry=0 >-16 bytes available >*** Error code 1 I think this was Just fixed, try re-supping and rebuilding Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 15:21:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kar.net (n178.cdialup.kar.net [195.178.130.178]) by hub.freebsd.org (Postfix) with ESMTP id 11A1515330 for ; Sun, 4 Apr 1999 15:20:55 -0700 (PDT) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.3/8.8.8) with ESMTP id BAA64993; Mon, 5 Apr 1999 01:16:43 +0300 (EEST) (envelope-from kushn@mail.kar.net) Date: Mon, 5 Apr 1999 01:16:42 +0300 (EEST) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: "David O'Brien" Cc: Chris Costello , freebsd-current@FreeBSD.ORG Subject: Re: 4.0-CURRENT world broken In-Reply-To: <19990404145518.A77643@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Apr 1999, David O'Brien wrote: > > The FreeBSD 4.0-CURRENT world appears to be broken. The file that > > appears to be causing the problem is pthread_private.h, included by > > isatty.c. > > > You're the only one reporting this problem. Possibly your /usr/obj isn't > clean? > No, I had the same breakage awhile ago. It comes from old headers /usr/src/lib/libc_r/uthread/pthread{.h,_np.h} (don't remember where they come from, but they were there and conflicted with the correct headers from /usr/src/include). Removing of those headers has fixed everything > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 15:22:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [206.154.101.226]) by hub.freebsd.org (Postfix) with ESMTP id 9477A15330 for ; Sun, 4 Apr 1999 15:22:31 -0700 (PDT) (envelope-from staylor@mrynet.com) Received: (from staylor@localhost) by mrynet.com (8.9.3/8.9.3) id PAA97289; Sun, 4 Apr 1999 15:20:33 -0700 (PDT) (envelope-from staylor) Message-Id: <199904042220.PAA97289@mrynet.com> From: staylor@mrynet.com (S. Akmentins-Teilors) Date: Sun, 4 Apr 1999 15:20:33 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Manfred Antar Subject: Re: WORLD failing in sys/boot/i386 Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 03:06 PM 4/4/99 +0000, S. Akmentins-Teilors wrote: > >CVSup'd at approx 1100 Pacific time: > > > >===> sys/boot/i386/boot2 > >(cd /usr/src/sys/boot/i386/boot2; m4 boot1.m4 boot1.s) | as -o boot1.o > >ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o > >objcopy -S -O binary boot1.out boot1 > >dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null > >cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -O2 > >-malign-functions=0 -malign-jumps=0 > >-malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast > >-Wcast-align -Wmissing-declarations > >-Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow > >-Wstrict-prototypes -Wwrite-strings > >-I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/boot/i386/boot2/boot2.c > >(cd /usr/src/sys/boot/i386/boot2; m4 > >-DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 sio.s) | as -o sio.o > >ld -nostdlib -static -N -Ttext 0x1000 -o > >boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o > >boot2.o sio.o > >objcopy -S -O binary boot2.out boot2.bin > >btxld -v -E 0x1000 -f bin -b > >/usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o > >boot2.ld -P > >1 boot2.bin > >kernel: ver=1.01 size=6f0 load=9000 entry=9010 map=16M pgctl=1:1 > >client: fmt=bin size=1520 text=0 data=0 bss=0 entry=0 > >output: fmt=bin size=1e10 text=200 data=1c10 org=0 entry=0 > >-16 bytes available > >*** Error code 1 > > I think this was Just fixed, try re-supping and rebuilding > > Manfred > ===================== > || mantar@pacbell.net || > || Ph. (415) 681-6235 || > ===================== Just CVSup'd, and the only updates were: Connected to cvsup.freebsd.org Updating collection src-all/cvs Edit src/gnu/lib/libgcc/Makefile Edit src/gnu/usr.bin/cc/cc_drv/Makefile Edit src/gnu/usr.bin/cc/cc_tools/Makefile Edit src/lib/libc/stdio/mktemp.c Edit src/sys/kern/kern_ntptime.c Finished successfully I don't see any of this affecting it, but I've started the world again. Lemme know if something there somehow indeed resolves the issue, or if another commit is made. Cheers, -skots -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@idt.net, staylor@mrynet.lv Westlake Village, CA USA (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 15:52: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B5F8914CE1; Sun, 4 Apr 1999 15:51:54 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id SAA42540; Sun, 4 Apr 1999 18:48:18 -0400 (EDT) Date: Sun, 4 Apr 1999 18:48:18 -0400 (EDT) From: Chuck Robey To: "David E. O'Brien" Cc: freebsd-current@FreeBSD.org Subject: egcs In-Reply-To: <199904042246.PAA00499@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm busily making world, but in the meantime, what's the name of the system compiler going to be, egcs or gcc, or cc? And the C++ one? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16: 4:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6380A14CE1 for ; Sun, 4 Apr 1999 16:04:26 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (d60-077.leach.ucdavis.edu [169.237.60.77]) by relay.nuxi.com (8.9.2/8.9.1) with ESMTP id QAA78032; Sun, 4 Apr 1999 16:02:29 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA22687; Sun, 4 Apr 1999 23:02:28 GMT (envelope-from obrien) Date: Sun, 4 Apr 1999 16:02:28 -0700 From: "David O'Brien" To: Chuck Robey Cc: freebsd-current@FreeBSD.org Subject: Re: egcs Message-ID: <19990404160228.A22669@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199904042246.PAA00499@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Chuck Robey on Sun, Apr 04, 1999 at 06:48:18PM -0400 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > what's the name of the system compiler going to be, egcs or gcc, or cc? > And the C++ one? No change in names. cc/gcc and c++/g++/CC -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16: 7:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3D36814CE1 for ; Sun, 4 Apr 1999 16:07:19 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA78063; Sun, 4 Apr 1999 16:05:20 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404160520.A78038@nuxi.com> Date: Sun, 4 Apr 1999 16:05:20 -0700 From: "David O'Brien" To: "S. Akmentins-Teilors" Cc: freebsd-current@FreeBSD.ORG Subject: Re: WORLD failing in sys/boot/i386 Reply-To: obrien@NUXI.com References: <199904042220.PAA97289@mrynet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904042220.PAA97289@mrynet.com>; from S. Akmentins-Teilors on Sun, Apr 04, 1999 at 03:20:33PM +0000 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just CVSup'd, and the only updates were: Try again. It can take an hour or so for changes to make it your favorate CVSup server. The "fix" is to remove the string ``>> FreeBSD/i386 BOOT\n'' from src/sys/boot/i386/boot2/boot2.c. The fix is a stopgap messure until the boot2 authors can take a look at it. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16:10:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 10BA614CE1 for ; Sun, 4 Apr 1999 16:10:09 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA25141; Sun, 4 Apr 1999 19:07:31 -0400 (EDT) Date: Sun, 4 Apr 1999 19:07:31 -0400 (EDT) From: Daniel Eischen Message-Id: <199904042307.TAA25141@pcnet1.pcnet.com> To: kushn@mail.kar.net, obrien@NUXI.com Subject: Re: 4.0-CURRENT world broken Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vladimir Kushnir wrote: > On Sun, 4 Apr 1999, David O'Brien wrote: > > > > The FreeBSD 4.0-CURRENT world appears to be broken. The file that > > > appears to be causing the problem is pthread_private.h, included by > > > isatty.c. > > > > > > You're the only one reporting this problem. Possibly your /usr/obj isn't > > clean? > > > > No, I had the same breakage awhile ago. It comes from old headers > /usr/src/lib/libc_r/uthread/pthread{.h,_np.h} (don't remember where they > come from, but they were there and conflicted with the correct headers > from /usr/src/include). > Removing of those headers has fixed everything Possibly from LinuxThreads changes? You've got to remember that if you make any local modifications to the source tree, things are liable to break. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16:14:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id EF78414CE1 for ; Sun, 4 Apr 1999 16:14:13 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id BAA75474; Mon, 5 Apr 1999 01:10:57 +0200 (SAT) (envelope-from reg) Date: Mon, 5 Apr 1999 01:10:56 +0200 From: Jeremy Lea To: "David O'Brien" Cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: egcs Message-ID: <19990405011056.A11991@shale.csir.co.za> References: <199904042246.PAA00499@freefall.freebsd.org> <19990404160228.A22669@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990404160228.A22669@dragon.nuxi.com>; from David O'Brien on Sun, Apr 04, 1999 at 04:02:28PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sun, Apr 04, 1999 at 04:02:28PM -0700, David O'Brien wrote: > > what's the name of the system compiler going to be, egcs or gcc, or cc? > > And the C++ one? > > No change in names. cc/gcc and c++/g++/CC Experience says there are a lot of ports which look for egcc and eg++, so it might be nice to add these (and all the other names used for the port) as hardlinks. Won't cost anything (well a few bytes...), and also will help with the depends checking on ports. Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16:18:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 61CCE14FBB for ; Sun, 4 Apr 1999 16:18:10 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA78130; Sun, 4 Apr 1999 16:14:47 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404161447.F77839@nuxi.com> Date: Sun, 4 Apr 1999 16:14:47 -0700 From: "David O'Brien" To: Jeremy Lea Cc: freebsd-current@FreeBSD.ORG Subject: Re: egcs Reply-To: obrien@NUXI.com References: <199904042246.PAA00499@freefall.freebsd.org> <19990404160228.A22669@dragon.nuxi.com> <19990405011056.A11991@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990405011056.A11991@shale.csir.co.za>; from Jeremy Lea on Mon, Apr 05, 1999 at 01:10:56AM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Experience says there are a lot of ports which look for egcc and eg++, I thought those that do have exlicit CC=egcc and CXX=eg++ in the Makefiles. We will just remove them. > so it might be nice to add these (and all the other names used for the > port) as hardlinks. Nope. I still want the port around to do comparison testing with the base Egcs. Plus I'm reading a egcs-devel port. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16:18:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 1F03214F6C for ; Sun, 4 Apr 1999 16:18:38 -0700 (PDT) (envelope-from ian@apdata.com.au) Received: from apdata.com.au (localhost [127.0.0.1]) by rose.niw.com.au (Postfix) with ESMTP id 66A70A3203; Mon, 5 Apr 1999 08:46:39 +0930 (CST) Message-ID: <3707F2D6.C37B4B7D@apdata.com.au> Date: Mon, 05 Apr 1999 08:46:38 +0930 From: Ian West Organization: Applied Data Control X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Cc: Bruce Evans Subject: Re: Atime not set on execution ? References: <199904041017.UAA29125@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > >Is it normal for atime not to be set on execution of a file ? > >I should have thought this would class as an access ? > > It's normal in FreeBSD, although this breaks POSIX.1 conformance. > > Bruce Thanks for the response, there isn't per chance an option to turn this on is there ? I am doing some maintenance on a few machines, and it would be really nice to know when some programs were last run, this seems like the ideal way to do it ? Is this a fault, or has this been done for some good reason ? Is it something I should try and fix ? Thanks for any feedback.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16:22:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id AF2A714CE1 for ; Sun, 4 Apr 1999 16:22:52 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id AAA05190; Mon, 5 Apr 1999 00:20:54 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 5 Apr 1999 00:05:22 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 5 Apr 1999 00:05:32 +0000 To: obrien@NUXI.com From: Bob Bishop Subject: Re: Looks broken to me... Cc: Ilya Naumov , Jim Bloom , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've hit this one now too. Jim Bloom wrote: >I get the same error. This is more to the error message which I have >included below. I am doing a "make buildworld" after deleting >everything in /usr/obj. Cvsup from freebsd3.freebsd.org at around 21:00 >GMT. > >Jim Bloom >bloom@acm.org > >c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe >-fno-for-scope -I/usr/src/gnu/usr.bin/groff/libgroff/../include >-DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 >-DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 >-DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 >-DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 >-DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 >-DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 >-I/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include >-fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -fno-rtti >-fno-exceptions -c >/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc >-o new.o >In file included from /usr/obj/usr/src/tmp/usr/include/g++/osfcn.h:5, > from >/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/include/posix.h:2 >5, > from >/usr/src/gnu/usr.bin/groff/libgroff/../../../../contrib/groff/libgroff/new.cc:2 >4: >/usr/obj/usr/src/tmp/usr/include/g++/std.h:23: stddef: No such file or >directory >*** Error code 1 > >Stop. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16:23:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 367BA14CE1 for ; Sun, 4 Apr 1999 16:23:56 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 18920 invoked from network); 4 Apr 1999 23:21:59 -0000 Received: from userac63.uk.uudial.com (HELO k2c.co.uk) (62.188.131.7) by smtp.dial.pipex.com with SMTP; 4 Apr 1999 23:21:59 -0000 Message-ID: <3707F392.B43CC6D6@k2c.co.uk> Date: Mon, 05 Apr 1999 00:19:46 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: David O'Brien , current@FreeBSD.ORG Subject: Switch to EGCS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just succeeded a make world and kernel recompile. A round of applause for David, please ! David: I'm starting with the PPro optimisations on right now. PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16:26:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id CED1B14CE1 for ; Sun, 4 Apr 1999 16:26:56 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA78209; Sun, 4 Apr 1999 16:24:57 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404162457.B78186@nuxi.com> Date: Sun, 4 Apr 1999 16:24:57 -0700 From: "David O'Brien" To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: Looks broken to me... Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Bob Bishop on Mon, Apr 05, 1999 at 12:05:32AM +0000 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've hit this one now too. I'm trying to duplicate the problem. My guess at the fix is to remove the "-DHAVE_CC_OSFCN_H=1\" line from src/gnu/usr.bin/groff/Makefile.cfg. But I can't tell what other problems this may cause. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 16:28:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kar.net (n178.cdialup.kar.net [195.178.130.178]) by hub.freebsd.org (Postfix) with ESMTP id 34C01153A9 for ; Sun, 4 Apr 1999 16:26:54 -0700 (PDT) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.3/8.8.8) with ESMTP id CAA68761; Mon, 5 Apr 1999 02:22:49 +0300 (EEST) (envelope-from kushn@mail.kar.net) Date: Mon, 5 Apr 1999 02:22:34 +0300 (EEST) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: Daniel Eischen Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4.0-CURRENT world broken In-Reply-To: <199904042307.TAA25141@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Apr 1999, Daniel Eischen wrote: > Vladimir Kushnir wrote: > > On Sun, 4 Apr 1999, David O'Brien wrote: > > > > > > The FreeBSD 4.0-CURRENT world appears to be broken. The file that > > > > appears to be causing the problem is pthread_private.h, included by > > > > isatty.c. > > > > > > > > > You're the only one reporting this problem. Possibly your /usr/obj isn't > > > clean? > > > > > > > No, I had the same breakage awhile ago. It comes from old headers > > /usr/src/lib/libc_r/uthread/pthread{.h,_np.h} (don't remember where they > > come from, but they were there and conflicted with the correct headers > > from /usr/src/include). > > Removing of those headers has fixed everything > > Possibly from LinuxThreads changes? Yes, from some very old port. > > You've got to remember that if you make any local modifications > to the source tree, things are liable to break. > Yes, I was bitten a couple of times and now usually run patch on anything in /usr/src with "-b .ctm" and keep logs (to have the possibility to at least fix what I've broken). > Dan Eischen > eischen@vigrid.com > > ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 17:21:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id B706714C56 for ; Sun, 4 Apr 1999 17:20:59 -0700 (PDT) (envelope-from veldy@visi.com) Received: from barley (h-181-168.mn.mediaone.net [209.32.181.168]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id UAA27315; Sun, 4 Apr 1999 20:14:56 -0400 (EDT) From: "Thomas T. Veldhouse" To: "Jeremy Lea" , "David O'Brien" Cc: "Chuck Robey" , Subject: RE: egcs Date: Sun, 4 Apr 1999 19:16:13 -0500 Message-ID: <000001be7ef9$83af1ac0$0100a8c0@veldy.org> 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 8.5, Build 4.71.2173.0 In-Reply-To: <19990405011056.A11991@shale.csir.co.za> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Besides, I can not imagine the base system is going to track egcs. At some point we will have a newer egcs port and the older system compiler, much as it was before. At least that is my take on things. Tom Veldhouse veldy@visi.com > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Jeremy Lea > Sent: Sunday, April 04, 1999 6:11 PM > To: David O'Brien > Cc: Chuck Robey; freebsd-current@FreeBSD.ORG > Subject: Re: egcs > > > Hi, > > On Sun, Apr 04, 1999 at 04:02:28PM -0700, David O'Brien wrote: > > > what's the name of the system compiler going to be, egcs or > gcc, or cc? > > > And the C++ one? > > > > No change in names. cc/gcc and c++/g++/CC > > Experience says there are a lot of ports which look for egcc and eg++, > so it might be nice to add these (and all the other names used for the > port) as hardlinks. Won't cost anything (well a few bytes...), and also > will help with the depends checking on ports. > > Regards, > -Jeremy > > -- > | "I could be anything I wanted to, but one things true > --+-- Never gonna be as big as Jesus, never gonna hold the world > in my hand > | Never gonna be as big as Jesus, never gonna build a promised land > | But that's, that's all right, OK with me..." -Audio Adrenaline > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 18:18:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B919915288 for ; Sun, 4 Apr 1999 18:18:18 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Mon, 5 Apr 1999 11:03:14 +1000 Date: Mon, 5 Apr 1999 11:16:09 +1000 From: Peter Jeremy Subject: Re: different systat -vmstat output when using egcs to compile kernel To: andreas@klemm.gtn.com Cc: freebsd-current@FreeBSD.ORG Message-Id: <99Apr5.110314est.40323@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Klemm wrote: >See the leading \n's in the Interrupts column (see !!!) >1st is ok using our cc >2nd is using egcs with different compile options. >But error remains the same even with no optimitation ... > 1 1 22 407 2 2533 456 264 1 13908 wire 243 \nclk0 irq > ^^ !!! I recognize that from gcc-2.8.1: The cpp behaviour changed and resulted in the DEVICE_NAMES macro in vector.h being incorrectly expanded. I suspect the same `bug' is in EGCS. The problem is that cpp (from gcc 2.8.1) _does_not_ remove backslash-newline sequences from string constants (and maybe elsewhere as well). This causes problems with the DEVICE_NAMES macro defined in vector.h and used in vector.s. I have reported this to bug-gcc (in mid-June) but haven't seen any response. At this time, I don't know of any way to disable this - the only work- around is to use a gcc-2.7.x derived cpp (eg the standard cpp). This implies changing NORMAL_S and DRIVER_S in /sys/i386/conf/Makefile.i386 to explicitly use the old (2.7.2.1-derived) cpp in front of as. [Note that according to the GNU as documentation, gas handles backslashes inside strings in the same way as C. This is not (and, according to one of the gas maintainers, has never been) true]. Given that it seems unlikely that we're going to get a fix in either egcs or gas in a hurry, our options appear to be: 1) Keep the gcc2.7.2 cpp around for pre-processing .S 2) switch to m4 (yuk) 3) change config to work around the bug. 4) write a sed (or similar script) to pre-process vector.s Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 18:56:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.ne.mediaone.net (jbloom.ne.mediaone.net [24.128.100.196]) by hub.freebsd.org (Postfix) with ESMTP id 9233A14D9B for ; Sun, 4 Apr 1999 18:56:14 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by jbloom.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id VAA41912; Sun, 4 Apr 1999 21:54:04 -0400 (EDT) (envelope-from bloom@acm.org) Message-ID: <370817BB.17A45956@acm.org> Date: Sun, 04 Apr 1999 21:54:03 -0400 From: Jim Bloom X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@NUXI.com Cc: Bob Bishop , current@FreeBSD.ORG Subject: Re: Looks broken to me... References: <19990404162457.B78186@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This seems to fix the problem. I got all the through buildworld and have installed the code. Man(1) seems to work fine, but I haven't done a major stress test of groff and the related programs. Jim Bloom bloom@acm.org David O'Brien wrote: > > > I've hit this one now too. > > I'm trying to duplicate the problem. > > My guess at the fix is to remove the "-DHAVE_CC_OSFCN_H=1\" line from > src/gnu/usr.bin/groff/Makefile.cfg. But I can't tell what other problems > this may cause. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 18:59:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6AAC314F13 for ; Sun, 4 Apr 1999 18:59:57 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA12692; Sun, 4 Apr 1999 18:58:00 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id SAA34046; Sun, 4 Apr 1999 18:57:59 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 4 Apr 1999 18:57:59 -0700 (PDT) Message-Id: <199904050157.SAA34046@vashon.polstra.com> To: andreas@klemm.gtn.com Subject: Re: X problems using egcs as compiler In-Reply-To: <19990403193632.A55975@titan.klemm.gtn.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990403193632.A55975@titan.klemm.gtn.com>, Andreas Klemm wrote: > Got the latest egcs port > > # $Id: Makefile,v 1.53 1999/03/30 02:58:02 obrien Exp $ > > Build X11R6 with the following CFLAGS: > > -pipe -mpentiumpro -O2 > > I'm still running X11 and after ,make install' I'm unable > to launch x applications (xterm, ...) > > andreas@titan{1001} $ xterm > /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXaw.so.6: Undefined symbol "__deregister_frame_info" There are two things going on here. First, I believe you must have built libXaw.so.6 using egcs, but you must have linked xterm using the normal system compiler. (Or else you or the Makefile used "ld" directly, which is always a bad idea.) If the executable is linked using egcs, then this error won't happen. Second, egcs actually contains a hack which attempts to make it work anyway, even if you linked the program using the old compiler. But there is a dynamic linker bug (which I just discovered) that prevents the hack from working. I am testing the fix for that now. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 19:25:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 064A914D94 for ; Sun, 4 Apr 1999 19:25:13 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id TAA12769; Sun, 4 Apr 1999 19:23:16 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id TAA69686; Sun, 4 Apr 1999 19:23:16 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 4 Apr 1999 19:23:16 -0700 (PDT) Message-Id: <199904050223.TAA69686@vashon.polstra.com> To: obrien@NUXI.com Subject: Re: Looks broken to me... In-Reply-To: <19990404162457.B78186@nuxi.com> References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990404162457.B78186@nuxi.com>, David O'Brien wrote: > > I've hit this one now too. > > I'm trying to duplicate the problem. > > My guess at the fix is to remove the "-DHAVE_CC_OSFCN_H=1\" line from > src/gnu/usr.bin/groff/Makefile.cfg. But I can't tell what other problems > this may cause. I've been looking into this. The main problem of course is that we're trying to use an old libg++ (and its headers) with a new C++ compiler (and its headers). I think the best fix is to edit "src/contrib/libg++/libg++/src/std.h" and change "#include " to "#include ". That's the correct name of the file according to the C++ standard. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 20: 2:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E196814D1D for ; Sun, 4 Apr 1999 20:02:14 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id UAA78876; Sun, 4 Apr 1999 20:00:16 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404200016.B78679@nuxi.com> Date: Sun, 4 Apr 1999 20:00:16 -0700 From: "David O'Brien" To: John Polstra Cc: current@freebsd.org Subject: Re: Looks broken to me... Reply-To: obrien@NUXI.com References: <19990404162457.B78186@nuxi.com> <199904050223.TAA69686@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904050223.TAA69686@vashon.polstra.com>; from John Polstra on Sun, Apr 04, 1999 at 07:23:16PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been looking into this. The main problem of course is that we're > trying to use an old libg++ Yes. > I think the best fix is to edit "src/contrib/libg++/libg++/src/std.h" But src/contrib/libg++ & src/gnu/lib/libg++ is about to be ``cvs rm''ed. IF we wanted to continue to offer libg++ I would need to import libg++ 2.8.1.3. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 20:38:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id AC08414F13 for ; Sun, 4 Apr 1999 20:38:51 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id UAA12942; Sun, 4 Apr 1999 20:36:54 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id UAA78550; Sun, 4 Apr 1999 20:36:54 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990404200016.B78679@nuxi.com> Date: Sun, 04 Apr 1999 20:36:54 -0800 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: "David O'Brien" Subject: Re: Looks broken to me... Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: >> I think the best fix is to edit "src/contrib/libg++/libg++/src/std.h" > > But src/contrib/libg++ & src/gnu/lib/libg++ is about to be ``cvs rm''ed. That's even better. :-) > IF we wanted to continue to offer libg++ I would need to import libg++ > 2.8.1.3. Ick. I'm all for ditching libg++. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 21: 8:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 68BAF1504F for ; Sun, 4 Apr 1999 21:08:41 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id NAA09610; Mon, 5 Apr 1999 13:06:31 +0900 (JST) Message-ID: <3708366D.1F1FEB94@newsguy.com> Date: Mon, 05 Apr 1999 13:05:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: obrien@NUXI.com Cc: "S. Akmentins-Teilors" , freebsd-current@FreeBSD.ORG Subject: Re: WORLD failing in sys/boot/i386 References: <199904042220.PAA97289@mrynet.com> <19990404160520.A78038@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > > Just CVSup'd, and the only updates were: > > Try again. It can take an hour or so for changes to make it your > favorate CVSup server. > > The "fix" is to remove the string ``>> FreeBSD/i386 BOOT\n'' from > src/sys/boot/i386/boot2/boot2.c. > > The fix is a stopgap messure until the boot2 authors can take a look at > it. I take the size increase was caused by the compiler replacement? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 21:20:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6481914C43 for ; Sun, 4 Apr 1999 21:20:53 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id VAA00556; Sun, 4 Apr 1999 21:18:54 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404211853.A458@nuxi.com> Date: Sun, 4 Apr 1999 21:18:53 -0700 From: "David O'Brien" To: "Daniel C. Sobral" Cc: "S. Akmentins-Teilors" , freebsd-current@FreeBSD.ORG Subject: Re: WORLD failing in sys/boot/i386 Reply-To: obrien@NUXI.com References: <199904042220.PAA97289@mrynet.com> <19990404160520.A78038@nuxi.com> <3708366D.1F1FEB94@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3708366D.1F1FEB94@newsguy.com>; from Daniel C. Sobral on Mon, Apr 05, 1999 at 01:05:01PM +0900 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The "fix" is to remove the string ``>> FreeBSD/i386 BOOT\n'' from > > src/sys/boot/i386/boot2/boot2.c. > I take the size increase was caused by the compiler replacement? AFAIK. BTW, there is now a ``-Os'' "size" optimzation. It includes all -O2 optimizations that don't increase the size + some size-only optimizations. Maybe this is the trick of us? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 22:11:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E931914F9A for ; Sun, 4 Apr 1999 22:11:42 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA06171; Sun, 4 Apr 1999 22:08:29 -0700 (PDT) (envelope-from dillon) Date: Sun, 4 Apr 1999 22:08:29 -0700 (PDT) From: Matthew Dillon Message-Id: <199904050508.WAA06171@apollo.backplane.com> To: Peter Jeremy Cc: andreas@klemm.gtn.com, freebsd-current@FreeBSD.ORG Subject: Re: different systat -vmstat output when using egcs to compile kernel References: <99Apr5.110314est.40323@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> 1 1 22 407 2 2533 456 264 1 13908 wire 243 \nclk0 irq :> ^^ !!! : :I recognize that from gcc-2.8.1: The cpp behaviour changed and resulted :in the DEVICE_NAMES macro in vector.h being incorrectly expanded. I :suspect the same `bug' is in EGCS. : :The problem is that cpp (from gcc 2.8.1) _does_not_ remove :backslash-newline sequences from string constants (and maybe elsewhere :as well). This causes problems with the DEVICE_NAMES macro defined in :vector.h and used in vector.s. I have reported this to bug-gcc (in :mid-June) but haven't seen any response. : :At this time, I don't know of any way to disable this - the only work- :around is to use a gcc-2.7.x derived cpp (eg the standard cpp). This :implies changing NORMAL_S and DRIVER_S in /sys/i386/conf/Makefile.i386 :to explicitly use the old (2.7.2.1-derived) cpp in front of as. I suggest using ANSI string constants instead of K&R string constants. This is perfectly legal: char *s = "abcdefghi"; char *s = "abc" "def" "ghi"; char *s = "abc" "def" "ghi"; :Given that it seems unlikely that we're going to get a fix in either :egcs or gas in a hurry, our options appear to be: :1) Keep the gcc2.7.2 cpp around for pre-processing .S :2) switch to m4 (yuk) :3) change config to work around the bug. :4) write a sed (or similar script) to pre-process vector.s : :Peter -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 22:15:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5EFA515346 for ; Sun, 4 Apr 1999 22:15:05 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA09708 for ; Sun, 4 Apr 1999 23:13:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA69299 for ; Sun, 4 Apr 1999 23:13:49 -0600 (MDT) Message-Id: <199904050513.XAA69299@harmony.village.org> To: current@freebsd.org Subject: Boot blocks Date: Sun, 04 Apr 1999 23:13:49 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wanted to let people know that the unmodified boot blocks have 144 bytes free if you compile them -Os and -16 free if you compile them -O2. -fno-exceptions didn't seem to impact things at all, nor did -fno-sjlj-exceptions. At least in terms of size. So it looks like the right fix for the boot blocks is to use -Os rather than -O2. This will make them slightly slower, but no body[*] is going to be able to convince me that they can measure the difference. Warner [*] With the possible exception of Bruce. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 22:25:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2B3F814D0D; Sun, 4 Apr 1999 22:25:38 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA06416; Sun, 4 Apr 1999 22:23:40 -0700 (PDT) (envelope-from dillon) Date: Sun, 4 Apr 1999 22:23:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199904050523.WAA06416@apollo.backplane.com> To: Julian Elischer Cc: Alan Cox , current@FreeBSD.ORG, luoqi@FreeBSD.ORG Subject: Re: SMP users (important) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Fri, 2 Apr 1999, Alan Cox wrote: :> :> Now, if you're not using Luoqi's patches to enable multithreaded :> address spaces, you can stop reading here. If you are, you'll :> need to patch i386/i386/swtch.s as follows: : :My suggestion is that we apply Luoqi's %fs patch to -current rather than :have to track these changes manually.. : :Luoqi? Have you had any -ve feedback on this? : :(and what would be the equivalent ALPHA patch?) :I can imagine the original PDE trick working on the alpha but :they don't have a spare register sitting around.. : :julian I'd like to see this too. I will soon have two SMP boxes of my own to play with for my own personal use and for an upcoming project, and at least one will be available for SMP life-testing purposes for several months. I really want to see two things: (1) Actual sharing of the physical pmap between rfork(RFMEM|RFPROC)'d processes, and (2) Avoiding the %cr3 reload ( which clears the TLB ) when switching between such processes. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 23:18:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from dei.calldei.com (dei.calldei.com [205.179.37.1]) by hub.freebsd.org (Postfix) with ESMTP id CA17914FAD for ; Sun, 4 Apr 1999 23:18:28 -0700 (PDT) (envelope-from chris@calldei.com) Received: (from chris@localhost) by dei.calldei.com (8.9.0/8.9.0) id XAA01625 for current@FreeBSD.ORG; Sun, 4 Apr 1999 23:16:30 -0700 (PDT) Date: Sun, 4 Apr 1999 23:16:30 -0700 (PDT) From: Chris Costello Message-Id: <199904050616.XAA01625@dei.calldei.com> To: current@FreeBSD.ORG Subject: libstdc++ is broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Best described in gnu/10956, libstdc++ has strange undefined reference errors when compiling anything C++. These are the errors: /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' Please consult the pr for more information. Thanks! Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 23:22: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6773D15302; Sun, 4 Apr 1999 23:22:00 -0700 (PDT) (envelope-from julian@whistle.com) Received: from s204m82.isp.whistle.com (s204m82.isp.whistle.com [207.76.204.82] (may be forged)) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id XAA53560; Sun, 4 Apr 1999 23:18:59 -0700 (PDT) Date: Sun, 4 Apr 1999 23:18:40 -0700 (PDT) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Matthew Dillon Cc: Alan Cox , current@FreeBSD.ORG, luoqi@FreeBSD.ORG Subject: Re: SMP users (important) In-Reply-To: <199904050523.WAA06416@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Apr 1999, Matthew Dillon wrote: > :(and what would be the equivalent ALPHA patch?) > :I can imagine the original PDE trick working on the alpha but > :they don't have a spare register sitting around.. do they? > : > :julian > > I'd like to see this too. I will soon have two SMP boxes of my own to play > with for my own personal use and for an upcoming project, and at least one > will be available for SMP life-testing purposes for several months. > I really want to see two things: (1) Actual sharing of the physical pmap > between rfork(RFMEM|RFPROC)'d processes, and (2) Avoiding the %cr3 reload > ( which clears the TLB ) when switching between such processes. This would also suggest shceduler changes that would increasr the likelyhood of 'related' processes being scheduled together. One scheme I remember id the A-list/B-list scheme, where each scheduling priority has two list that are alternated. whichever list is being drained is not eligible for receiving new items. They must go to the other list. When the active list is drained and theya are switched, the new list is first sorted accoring to affinity related effects. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 4 23:30:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 10D1714FAD for ; Sun, 4 Apr 1999 23:30:53 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id XAA05306; Sun, 4 Apr 1999 23:28:54 -0700 (PDT) (envelope-from obrien) Message-ID: <19990404232854.A5300@nuxi.com> Date: Sun, 4 Apr 1999 23:28:54 -0700 From: "David O'Brien" To: Warner Losh , current@FreeBSD.ORG Subject: Re: Boot blocks Reply-To: obrien@NUXI.com References: <199904050513.XAA69299@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904050513.XAA69299@harmony.village.org>; from Warner Losh on Sun, Apr 04, 1999 at 11:13:49PM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just wanted to let people know that the unmodified boot blocks have > 144 bytes free if you compile them -Os and -16 free if you compile > them -O2. Were you able to actually boot the bootblocks compiled with EGCS and -Os ? (I know the optimization gives us the space we need, but I'm not upto testing new bootblocks at this moment) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 0:21: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0368015039 for ; Mon, 5 Apr 1999 00:20:59 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id AAA05453; Mon, 5 Apr 1999 00:19:01 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405001901.B5432@nuxi.com> Date: Mon, 5 Apr 1999 00:19:01 -0700 From: "David O'Brien" To: Glenn Johnson Cc: freebsd-current@FreeBSD.ORG Subject: Re: egcs Reply-To: obrien@NUXI.com References: <199904042246.PAA00499@freefall.freebsd.org> <19990404160228.A22669@dragon.nuxi.com> <19990404223001.A449@gforce.johnson.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990404223001.A449@gforce.johnson.home>; from Glenn Johnson on Sun, Apr 04, 1999 at 10:30:01PM -0500 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What will become of f77 which is in "src/gnu/usr.bin/cc/f77"? This > seems to be a good time to decide what will happen with Fortran in the > base FreeBSD system. VERY good question. I have no opinion in the matter, but will follow the wishes of others (or Core, or committers, or who ever should make this decision and who ever tells me which way to go). -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 0:37:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 5566514F55 for ; Mon, 5 Apr 1999 00:37:48 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id JAA80204; Mon, 5 Apr 1999 09:35:45 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id JAA04997; Mon, 5 Apr 1999 09:35:43 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904050735.JAA04997@greenpeace.grondar.za> To: obrien@NUXI.com Cc: Glenn Johnson , freebsd-current@freebsd.org Subject: Re: egcs In-Reply-To: Your message of " Mon, 05 Apr 1999 00:19:01 MST." <19990405001901.B5432@nuxi.com> References: <199904042246.PAA00499@freefall.freebsd.org> <19990404160228.A22669@dragon.nuxi.com> <19990404223001.A449@gforce.johnson.home> <19990405001901.B5432@nuxi.com> Date: Mon, 05 Apr 1999 09:35:41 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > > What will become of f77 which is in "src/gnu/usr.bin/cc/f77"? This > > seems to be a good time to decide what will happen with Fortran in the > > base FreeBSD system. > > VERY good question. I have no opinion in the matter, but will follow the > wishes of others (or Core, or committers, or who ever should make this > decision and who ever tells me which way to go). My take on this is that it could be a lot more difficult to make as a port than as a SUBDIR+= ? My (non-binding and unemotional) vote is for Fortran to be in the base system. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 0:49:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 5818115128 for ; Mon, 5 Apr 1999 00:49:27 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.3/8.9.3/Netplex) with ESMTP id PAA07291; Mon, 5 Apr 1999 15:47:10 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199904050747.PAA07291@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: Glenn Johnson , freebsd-current@FreeBSD.ORG Subject: Re: egcs In-reply-to: Your message of "Mon, 05 Apr 1999 00:19:01 MST." <19990405001901.B5432@nuxi.com> Date: Mon, 05 Apr 1999 15:47:10 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > > What will become of f77 which is in "src/gnu/usr.bin/cc/f77"? This > > seems to be a good time to decide what will happen with Fortran in the > > base FreeBSD system. > > VERY good question. I have no opinion in the matter, but will follow the > wishes of others (or Core, or committers, or who ever should make this > decision and who ever tells me which way to go). My preference is to have g77 as part of the base egcs in the tree, and if we need f77 (ie: the Fortran->C translator), port-ify it since it is easily made standalone while g77 isn't. The sticky bit is what how to handle libI77 and libF77.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 0:51:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5BF1715128 for ; Mon, 5 Apr 1999 00:51:30 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id AAA14320; Mon, 5 Apr 1999 00:49:32 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id AAA15720; Mon, 5 Apr 1999 00:49:32 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 5 Apr 1999 00:49:32 -0700 (PDT) Message-Id: <199904050749.AAA15720@vashon.polstra.com> To: imp@harmony.village.org Subject: Re: Boot blocks In-Reply-To: <199904050513.XAA69299@harmony.village.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904050513.XAA69299@harmony.village.org>, Warner Losh wrote: > -fno-exceptions didn't seem to impact things at all, nor > did -fno-sjlj-exceptions. At least in terms of size. That's because the default for C programs is -fno-exceptions. That option still should be added to the Makefiles for boot in such a way as to override a possible "-fexceptions" in /etc/make.conf. When there are conflicting options, the last one wins. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 1:36:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B74ED14E0B for ; Mon, 5 Apr 1999 01:36:21 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40328>; Mon, 5 Apr 1999 18:21:20 +1000 Date: Mon, 5 Apr 1999 18:34:16 +1000 From: Peter Jeremy Subject: Re: different systat -vmstat output when using egcs to compile kernel To: dillon@apollo.backplane.com Cc: andreas@klemm.gtn.com, freebsd-current@FreeBSD.ORG Message-Id: <99Apr5.182120est.40328@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: >:The problem is that cpp (from gcc 2.8.1) _does_not_ remove >:backslash-newline sequences from string constants (and maybe elsewhere >:as well). This causes problems with the DEVICE_NAMES macro defined in >:vector.h and used in vector.s. ... > I suggest using ANSI string constants instead of K&R string constants. > > This is perfectly legal: > > char *s = "abcdefghi"; > > char *s = "abc" "def" "ghi"; > > char *s = "abc" > "def" > "ghi"; Currently we have something like: #define DEVICE_NAMES "\ clk0 irqnn\0\ rtc0 irqnn\0\ pci irqnn\0\ pci irqnn\0\ pci irqnn\0\ " .ascii DEVICE_NAMES Which expands and assembles into something like: 000020: 5c 6e 63 6c 6b 30 20 69 72 71 6e 6e 00 5c 6e 72 |\nclk0 irqnn.\nr| 000030: 74 63 30 20 69 72 71 6e 6e 00 5c 6e 70 63 69 20 |tc0 irqnn.\npci | 000040: 69 72 71 6e 6e 00 5c 6e 70 63 69 20 69 72 71 6e |irqnn.\npci irqn| Surprisingly, ANSI-C string concatenation _does_ work in gas, so the following works correctly: #define DEVICE_NAMES \ "clk0 irqnn\0" \ "rtc0 irqnn\0" \ "pci irqnn\0" \ "pci irqnn\0" \ "pci irqnn\0" .ascii DEVICE_NAMES This suggests that what's needed is a patch to config to make it generate ANSI strings. The following (untested) patch should do it: Index: mkglue.c =================================================================== RCS file: /home/CVSROOT/./src/usr.sbin/config/mkglue.c,v retrieving revision 1.14 diff -u -r1.14 mkglue.c --- mkglue.c 1998/04/02 04:25:39 1.14 +++ mkglue.c 1999/04/05 08:31:55 @@ -368,17 +368,17 @@ fprintf(fp, " * Macros for interrupt vector routines\n"); fprintf(fp, " * Generated by config program\n"); fprintf(fp, " */\n\n"); - fprintf(fp, "#define\tDEVICE_NAMES \"\\\n"); - fprintf(fp, "clk0 irqnn\\0\\\n"); - fprintf(fp, "rtc0 irqnn\\0\\\n"); - fprintf(fp, "pci irqnn\\0\\\n"); - fprintf(fp, "pci irqnn\\0\\\n"); - fprintf(fp, "pci irqnn\\0\\\n"); - fprintf(fp, "pci irqnn\\0\\\n"); - fprintf(fp, "ipi irqnn\\0\\\n"); - fprintf(fp, "ipi irqnn\\0\\\n"); - fprintf(fp, "ipi irqnn\\0\\\n"); - fprintf(fp, "ipi irqnn\\0\\\n"); + fprintf(fp, "#define\tDEVICE_NAMES \\\n"); + fprintf(fp, "\"clk0 irqnn\\0\" \\\n"); + fprintf(fp, "\"rtc0 irqnn\\0\" \\\n"); + fprintf(fp, "\"pci irqnn\\0\" \\\n"); + fprintf(fp, "\"pci irqnn\\0\" \\\n"); + fprintf(fp, "\"pci irqnn\\0\" \\\n"); + fprintf(fp, "\"pci irqnn\\0\" \\\n"); + fprintf(fp, "\"ipi irqnn\\0\" \\\n"); + fprintf(fp, "\"ipi irqnn\\0\" \\\n"); + fprintf(fp, "\"ipi irqnn\\0\" \\\n"); + fprintf(fp, "\"ipi irqnn\\0\" \\\n"); dev_id = 10; vector_devtab(fp, "bio", &dev_id); vector_devtab(fp, "tty", &dev_id); @@ -386,7 +386,7 @@ vector_devtab(fp, "cam", &dev_id); vector_devtab(fp, "ha", &dev_id); vector_devtab(fp, "null", &dev_id); - fprintf(fp, "\"\n\n"); + fprintf(fp, "\n"); fprintf(fp, "#define\tNR_DEVICES\t%d\n", dev_id); (void) fclose(fp); moveifchanged(path("vector.h.new"), path("vector.h")); @@ -406,7 +406,7 @@ mp = dp->d_conn; if (mp == NULL || mp == TO_NEXUS || !eq(mp->d_name, "isa")) continue; - fprintf(fp, "%s%d irqnn\\0\\\n", dp->d_name, dp->d_unit); + fprintf(fp, "\"%s%d irqnn\\0\" \\\n", dp->d_name, dp->d_unit); (*dev_idp)++; } } Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 1:45:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (Postfix) with ESMTP id AFD9E14F8D; Mon, 5 Apr 1999 01:45:16 -0700 (PDT) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (Postfix) with ESMTP id DBAC655; Mon, 5 Apr 1999 10:43:14 +0200 (MET DST) Received: by ariel.xaa.iae.nl (Postfix, from userid 1008) id 287D01903; Mon, 5 Apr 1999 10:43:13 +0200 (CEST) Date: Mon, 5 Apr 1999 10:43:13 +0200 From: Mark Huizer To: obrien@freebsd.org, current@freebsd.org Subject: gnu/usr.bin/genclass Message-ID: <19990405104313.A80394@ariel.xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG genclass has GPPDIR=${BLA}/libg++ in its Makefile breaking the make world, not sure if you noticed already, didn't see a commit message about it :-) Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 2:10:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id BD4ED14E0B for ; Mon, 5 Apr 1999 02:10:24 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.203]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6DA4; Mon, 5 Apr 1999 11:08:26 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id LAA61068; Mon, 5 Apr 1999 11:08:30 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990404232854.A5300@nuxi.com> Date: Mon, 05 Apr 1999 11:08:30 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Re: Boot blocks Cc: current@FreeBSD.ORG, Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 David O'Brien wrote: >> Just wanted to let people know that the unmodified boot blocks have >> 144 bytes free if you compile them -Os and -16 free if you compile >> them -O2. > > Were you able to actually boot the bootblocks compiled with EGCS and -Os ? > (I know the optimization gives us the space we need, but I'm not upto > testing new bootblocks at this moment) Funny thing is that I get an option unknown: -Os when trying that solution. A -O instead of -O2 however solves my problem and leaves me with 188 bytes free. Guess that means that my make world still uses (g)cc offcourse as it does not recognise the -Os flag. --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 2:32:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 5497914E0B for ; Mon, 5 Apr 1999 02:32:54 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.78]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6347; Mon, 5 Apr 1999 11:30:56 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id LAA79606; Mon, 5 Apr 1999 11:31:03 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 05 Apr 1999 11:31:01 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Re: Boot blocks Cc: Warner Losh , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Jeroen Ruigrok/Asmodai wrote: > On 05-Apr-99 David O'Brien wrote: >>> Just wanted to let people know that the unmodified boot blocks have >>> 144 bytes free if you compile them -Os and -16 free if you compile >>> them -O2. >> >> Were you able to actually boot the bootblocks compiled with EGCS and -Os >> ? (I know the optimization gives us the space we need, but I'm not upto >> testing new bootblocks at this moment) > > Funny thing is that I get an option unknown: -Os when trying that > solution. A -O instead of -O2 however solves my problem and leaves me with > 188 bytes free. > > Guess that means that my make world still uses (g)cc offcourse as it > does not recognise the -Os flag. Hmmm, hate to return on my own messages, but this is funny: set -Os in make.conf and compiled everything with it, yet the bootblocks don't like that option. In the meantime I changed -O2 to -O in the boot2/Makefile Something I missed here? --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 2:37:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 53A45153D7 for ; Mon, 5 Apr 1999 02:37:35 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id LAA31518; Mon, 5 Apr 1999 11:31:41 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id WAA25492; Sun, 4 Apr 1999 22:36:12 +0200 (CEST) From: Wilko Bulte Message-Id: <199904042036.WAA25492@yedi.iaf.nl> Subject: Re: WORM & CAM CD In-Reply-To: from Andreas Dobloug at "Apr 4, 1999 6:53:31 pm" To: andreasd@ifi.uio.no (Andreas Dobloug) Date: Sun, 4 Apr 1999 22:36:12 +0200 (CEST) Cc: current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Andreas Dobloug wrote ... > * Kenneth D. Merry > | > Has the worm driver been taken out of current? > | Yes. You have to use cdrecord now for SCSI CD burners. > > cdrecord lacks support for a whole lot of CD-burners... ? Having just a while ago downloaded the latest cdrecord source I'd say the list of supported hardware for cdrecord is a helluvalot longer than the worm stuff ever had. Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 2:37:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 36C1415416 for ; Mon, 5 Apr 1999 02:37:35 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id LAA31517; Mon, 5 Apr 1999 11:31:41 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id WAA25500; Sun, 4 Apr 1999 22:38:31 +0200 (CEST) From: Wilko Bulte Message-Id: <199904042038.WAA25500@yedi.iaf.nl> Subject: Re: show stopper for EGCS import In-Reply-To: <19990404093848.A76160@nuxi.com> from "David O'Brien" at "Apr 4, 1999 9:38:48 am" To: obrien@NUXI.com Date: Sun, 4 Apr 1999 22:38:31 +0200 (CEST) Cc: current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As David O'Brien wrote ... > > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from > > the EGCS source rather than our home-grown ones. > ..snip.. > > I've made the same fix to lib/csu as I did libgcc, but now am getting > > the same weird "install" problem Poul-Henning was getting. > > Well FMH! I found a typo I made in Makefile.inc1. However, there is > still a bootstrapping problem related to using the EGCS > crtbegin.o/crtend.o. So boys and girls, are are going to use the > "sjlj-exceptions" type exception machanism for a while. > > THE SWITCH HAS BEEN PULLED! FWIW, my Aspen Alpine AXP doing a buildworld on freshly (this afternoon) supped -current: ..... ===> etc/sendmail rm -f freebsd.cf (cd /usr/src/etc/sendmail && m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/ sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc ) > freebsd.cf chmod 444 freebsd.cf 16293.67 real 12302.28 user 3910.24 sys Buildworld seems to work fine on the alpha port. Congrats I'd say. Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 4:14:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (Postfix) with ESMTP id 1520B15040 for ; Mon, 5 Apr 1999 04:14:49 -0700 (PDT) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id NAA19708 for ; Mon, 5 Apr 1999 13:12:51 +0200 (CEST) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.8.5) with ESMTP id NAA22210 for ; Mon, 5 Apr 1999 13:12:51 +0200 (MET DST) Message-Id: <199904051112.NAA22210@trantor.xs4all.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: CPP broken on egcs current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Apr 1999 13:12:50 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A make buildworld fails on an freshly rebuilt system. The following error is shown: -------------------------------------------------------------- >>> Rebuilding /usr/include -------------------------------------------------------------- cd /usr/source/src; SHARED=copies PATH=/usr/obj/usr/source/src/tmp/sbin:/usr/obj /usr/source/src/tmp/usr/sbin:/usr/obj/usr/source/src/tmp/bin:/usr/obj/usr/source /src/tmp/usr/bin:/home/paulz/bin:/home/paulz/bin/trantor.xs4all.nl:/usr/local/bi n:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/games:/sbin:/bin:/usr/l ocal/jdk1.1.7/bin:/usr/local/pilot/bin:/usr/local/pgsql/bin BISON_SIMPLE=/usr/ob j/usr/source/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/sou rce/src/tmp/usr/libexec:/usr/obj/usr/source/src/tmp/usr/bin GCC_EXEC_PREFIX=/us r/obj/usr/source/src/tmp/usr/lib:/usr/obj/usr/source/src/tmp/usr/lib/ LD_LIBRAR Y_PATH=/usr/obj/usr/source/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/source/src /tmp/usr/lib:/usr/obj/usr/source/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH =/usr/obj/usr/source/src/tmp/usr/libexec:/usr/libexec /usr/obj/usr/source/src/tm p/usr/bin/make DESTDIR=/usr/obj/usr/source/src/tmp -f Makefile.inc1 includes cd /usr/source/src/include; /usr/obj/usr/source/src/tmp/usr/ bin/make -B all install creating osreldate.h from newvers.sh setvar PARAMFILE /usr/source/src/include/../sys/sys/param.h; . /usr/source/src/ include/../sys/conf/newvers.sh; echo "$COPYRIGHT" > osreldate.h ; echo \#'undef __FreeBSD_version' >> osreldate.h; echo \#'define __FreeBSD_version' $RELDATE >> osreldate.h ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/source/src/include/rpcsvc/key_prot.x -o key_prot.h /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Int ernal compiler error in function main *** Error code 33 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. I get the same internal error when xrdb tries to run my .Xresources file thru CPP so does xdm trying the run Xresources thru cpp.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 4:21:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.linet.it (relay.linet.it [194.185.24.71]) by hub.freebsd.org (Postfix) with SMTP id B977814D21; Mon, 5 Apr 1999 04:21:39 -0700 (PDT) (envelope-from andrea.franceschini@linet.it) Received: from oma (unverified [194.185.24.73]) by relay.linet.it (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 05 Apr 1999 13:05:55 +0200 Message-ID: <011d01be7f56$a7fad060$2100a8c0@oma> Reply-To: "andrea" From: "andrea" To: , , , "freebsd-questions" Subject: arp. Date: Mon, 5 Apr 1999 13:22:56 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have to add a gateway to my net for experimental reasons. Actually there are : a main-router that works as interface to the Internet, and some hosts on my sub net. Internet-----MyRouter----MySubNet NOw i need to configure one host of MYSubNet to act as a gatway for the secondary subnet. Both the 1SubNet and 2 SubNEt share the same ip-range. Internet-----MyRouter----MySubNet-----My2SubNet All the sub.net have to be seen from the Internet so I'll need to add a route to MainRouter in order to route the Secondary Subnet. The problem is that i cannot change configuration of the mainroute,so i wonder if is possible to configure the new gateway to do a sort of "proxy arp" for my secondary Subnet. But arp-tables are system-wide so if i change arp entry to cacth request on PrimaryNet the 2subnet dont'works anymore. Is possible to catch arp request only on a single subnet,without broke any other subnet connected to the same host.? thank you! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 4:30: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 8B32F15419; Mon, 5 Apr 1999 04:29:57 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.10]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3588; Mon, 5 Apr 1999 13:27:59 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id NAA01798; Mon, 5 Apr 1999 13:27:59 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 05 Apr 1999 13:27:58 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Success! Cc: "David O'Brien" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, make world completed ok. Even rebooted to test the bootblocks (see previous messages) and all is well. Well, sorta, lotsa errors when trying to make a new kernel, fonts are fuqed, Window Maker all of a sudden acts weird with its general menu, ppp gives an ioctl error... This might mean that people runnin CURRENT might have to recompile a lot of things. Suggestions, hints, tips, advice? =) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 4:54: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat192.236.mpoweredpc.net [142.177.192.236]) by hub.freebsd.org (Postfix) with ESMTP id 943A31540F for ; Mon, 5 Apr 1999 04:54:06 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id IAA41196; Mon, 5 Apr 1999 08:52:06 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 5 Apr 1999 08:52:06 -0300 (ADT) From: The Hermit Hacker To: Wilko Bulte Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: show stopper for EGCS import In-Reply-To: <199904042038.WAA25500@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What does 'cc -v' show on your system? I just finished a 'make world' on mine, and it still says 2.7.2.1 ... am I missing something here? :( On Sun, 4 Apr 1999, Wilko Bulte wrote: > As David O'Brien wrote ... > > > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from > > > the EGCS source rather than our home-grown ones. > > ..snip.. > > > I've made the same fix to lib/csu as I did libgcc, but now am getting > > > the same weird "install" problem Poul-Henning was getting. > > > > Well FMH! I found a typo I made in Makefile.inc1. However, there is > > still a bootstrapping problem related to using the EGCS > > crtbegin.o/crtend.o. So boys and girls, are are going to use the > > "sjlj-exceptions" type exception machanism for a while. > > > > THE SWITCH HAS BEEN PULLED! > > FWIW, my Aspen Alpine AXP doing a buildworld on freshly (this afternoon) > supped -current: > > ..... > ===> etc/sendmail > rm -f freebsd.cf > (cd /usr/src/etc/sendmail && m4 > -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/ > sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 > freebsd.mc > ) > freebsd.cf > chmod 444 freebsd.cf > 16293.67 real 12302.28 user 3910.24 sys > > Buildworld seems to work fine on the alpha port. Congrats I'd say. > > Groeten / Cheers, > Wilko > _ ______________________________________________________________________ > | / o / / _ Arnhem, The Netherlands > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl > _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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-current" in the body of the message From owner-freebsd-current Mon Apr 5 4:55: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from muffin.highwire.local (pool-1-p12.innotts.co.uk [212.56.33.12]) by hub.freebsd.org (Postfix) with ESMTP id 25F1714D21; Mon, 5 Apr 1999 04:54:55 -0700 (PDT) (envelope-from robmel@innotts.co.uk) Received: from [172.16.17.20] (robsmac.highwire.local [172.16.17.20]) by muffin.highwire.local (8.9.2/8.9.2) with ESMTP id MAA11638; Mon, 5 Apr 1999 12:52:13 +0100 (BST) (envelope-from robmel@innotts.co.uk) X-Sender: robmel@muffin.highwire.local Message-Id: In-Reply-To: <011d01be7f56$a7fad060$2100a8c0@oma> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 5 Apr 1999 12:50:03 +0100 To: "andrea" , , , , "freebsd-questions" From: Robin Melville Subject: Re: arp. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:22 pm +0100 5/4/99, andrea wrote: >I have to add a gateway to my net for experimental reasons. >Actually there are : a main-router that works as interface to the Internet, >and some hosts on my sub net. > > Internet-----MyRouter----MySubNet > >NOw i need to configure one host of MYSubNet to act as a gatway for the >secondary subnet. >Both the 1SubNet and 2 SubNEt share the same ip-range. > > Internet-----MyRouter----MySubNet-----My2SubNet > >All the sub.net have to be seen from the Internet so I'll need to add a >route to MainRouter in order to route the Secondary Subnet. >The problem is that i cannot change configuration of the mainroute,so i >wonder if is possible to configure the new gateway to do a sort of "proxy >arp" for my secondary Subnet. >But arp-tables are system-wide so if i change arp entry to cacth request on >PrimaryNet the 2subnet dont'works anymore. >Is possible to catch arp request only on a single subnet,without broke any >other subnet connected to the same host.? >thank you! Assuming that these are IP routers and not ethernet switches, the arp tables aren't particularly relevent. If the main router is running 'routed' or some other RIP routing daemon, all you need to do is run a similar daemon and your new subnet route will be propagated. Alternatively, or essentially if you are using unregistered IP, you could use 'natd' on 'MyRouter' to masquerade the internal addresses onto the external interface. The handbook pages on natd make it very easy to set up. Good luck Robin. ---------------------------------------------------------------------- Robin Melville, Addiction Information Services Nottingham Alcohol & Drug Team Tel: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 work: robmel@nadt.org.uk home: robmel@innotts.co.uk Pages: http://www.innotts.co.uk/~robmel (home page) http://www.innotts.co.uk/nadt (substance misuse pages) ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 6: 8:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id B776114F4B; Mon, 5 Apr 1999 06:08:51 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.10]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2DE5; Mon, 5 Apr 1999 15:06:53 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id PAA13935; Mon, 5 Apr 1999 15:06:53 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 05 Apr 1999 15:06:53 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: C++ Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, we're coming a long way David, but the thing for which egcs was chosen doesn't quite work according to autoconf: checking for gcc... cc checking whether the C compiler (cc -Os -pipe ) works... yes checking whether the C compiler (cc -Os -pipe ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether cc accepts -g... yes checking for c++... c++ checking whether the C++ compiler (c++ ) works... no configure: error: installation or configuration problem: C++ compiler cannot create executables. *** Error code 1 That's the www/libwww port. Here's the config.log which might help ye troubleshoot c++: configure:1285: checking for c++ configure:1317: checking whether the C++ compiler (c++ ) works configure:1333: c++ -o conftest conftest.C 1>&5 /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' configure: failed program was: #line 1328 "configure" #include "confdefs.h" int main(){return(0);} Keep going mate, we're coming closer =) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 6:24:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 66E7514F85 for ; Mon, 5 Apr 1999 06:24:10 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id IAA00842; Mon, 5 Apr 1999 08:22:04 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id IAA00837; Mon, 5 Apr 1999 08:22:02 -0500 (CDT) Message-ID: <002801be7f67$72ce6300$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "The Hermit Hacker" , "Wilko Bulte" Cc: , Subject: Re: show stopper for EGCS import Date: Mon, 5 Apr 1999 08:23:06 -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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mine shows: Using builtin specs. gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) Everything is well. I haven't tried out C++ yet though. Tom Veldhouse veldy@visi.com -----Original Message----- From: The Hermit Hacker To: Wilko Bulte Cc: obrien@NUXI.com ; current@FreeBSD.ORG Date: Monday, April 05, 1999 6:52 AM Subject: Re: show stopper for EGCS import > >What does 'cc -v' show on your system? I just finished a 'make world' on >mine, and it still says 2.7.2.1 ... am I missing something here? :( > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 6:29:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 4D68C150C5 for ; Mon, 5 Apr 1999 06:29:06 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id IAA00909 for ; Mon, 5 Apr 1999 08:27:01 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id IAA00905 for ; Mon, 5 Apr 1999 08:27:01 -0500 (CDT) Message-ID: <003001be7f68$23cce730$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: egcs c++ problems Date: Mon, 5 Apr 1999 08:28:06 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002D_01BE7F3E.3AD09280" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_002D_01BE7F3E.3AD09280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I get the following when trying to build the following very simple C++ = test: // begin program #include using namespace std; int main(int argc, char** argv) { cout << "Hello World!!!\n" << endl; return 0; } // end program c++ foobar.cc -o foobar /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' Are there any parts of world that are going to have a hard time building = under egcs because of this? Tom Veldhouse veldy@visi.com ------=_NextPart_000_002D_01BE7F3E.3AD09280 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I get the following when trying to = build the=20 following very simple C++ test:
 
// begin program
#include = <iostream>
 
using namespace std;
 
int main(int argc, char** argv)=20 {
        cout << = "Hello=20 World!!!\n" << = endl;
       =20 return 0;
}
// end program
c++ foobar.cc -o=20 foobar
/usr/lib/libstdc++.so: undefined reference to `filebuf virtual = table'
/usr/lib/libstdc++.so: undefined reference to `stdiobuf = virtual=20 table'
 
Are there any parts of world that are going to have = a hard=20 time building under egcs because of this?
 
Tom Veldhouse
veldy@visi.com
------=_NextPart_000_002D_01BE7F3E.3AD09280-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 6:43: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail5.svr.pol.co.uk (mail5.svr.pol.co.uk [195.92.193.20]) by hub.freebsd.org (Postfix) with ESMTP id EC16014CE1 for ; Mon, 5 Apr 1999 06:42:58 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: from modem-27.cerium.dialup.pol.co.uk ([62.136.28.155] helo=k2c.co.uk) by mail5.svr.pol.co.uk with esmtp (Exim 2.12 #1) id 10U9cZ-0002Gs-00; Mon, 5 Apr 1999 14:40:59 +0100 Message-ID: <3708BCDF.BC580DDE@k2c.co.uk> Date: Mon, 05 Apr 1999 14:38:39 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas T. Veldhouse" Cc: FreeBSD-Current Subject: Re: egcs c++ problems References: <003001be7f68$23cce730$236319ac@w142844.carlson.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Thomas T. Veldhouse" wrote: > > Are there any parts of world that are going to have a hard time > building under egcs because of this? > There would be if it had stay like that... the last changes from David : cvs commit: src/gnu/lib/libstdc++/doc Makefile Date: Mon, 5 Apr 1999 03:21:31 -0700 (PDT) fix it. I just recompiled your program with the new libstdc++.so.3, and it's fine. PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 7:42:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat192.236.mpoweredpc.net [142.177.192.236]) by hub.freebsd.org (Postfix) with ESMTP id 4F70414D21 for ; Mon, 5 Apr 1999 07:42:05 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id LAA41859; Mon, 5 Apr 1999 11:39:54 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 5 Apr 1999 11:39:54 -0300 (ADT) From: The Hermit Hacker To: "Thomas T. Veldhouse" Cc: Wilko Bulte , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: show stopper for EGCS import In-Reply-To: <002801be7f67$72ce6300$236319ac@w142844.carlson.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hrmmm...have to try that again tonight whenI get home then...maybe I cvsup'd a snapshot just before it got updated :( On Mon, 5 Apr 1999, Thomas T. Veldhouse wrote: > Mine shows: > > > Using builtin specs. > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) > > Everything is well. I haven't tried out C++ yet though. > > Tom Veldhouse > veldy@visi.com > > -----Original Message----- > From: The Hermit Hacker > To: Wilko Bulte > Cc: obrien@NUXI.com ; current@FreeBSD.ORG > > Date: Monday, April 05, 1999 6:52 AM > Subject: Re: show stopper for EGCS import > > > > > >What does 'cc -v' show on your system? I just finished a 'make world' on > >mine, and it still says 2.7.2.1 ... am I missing something here? :( > > > > > > 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-current" in the body of the message From owner-freebsd-current Mon Apr 5 8:22:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 5539D15452 for ; Mon, 5 Apr 1999 08:22:36 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id QAA11993; Mon, 5 Apr 1999 16:20:39 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 5 Apr 1999 16:13:32 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19990404162457.B78186@nuxi.com> References: ; from Bob Bishop on Mon, Apr 05, 1999 at 12:05:32AM +0000 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 5 Apr 1999 16:13:43 +0000 To: obrien@NUXI.com From: Bob Bishop Subject: make -jn ? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG World builds OK here now, kernel, bootblocks and all. Good job! Is `make -jn' safe yet? Could turn these test builds round a lot faster :-) -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 8:30:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 37CCC14C0D for ; Mon, 5 Apr 1999 08:30:44 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id LAA34990 for ; Mon, 5 Apr 1999 11:30:58 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Mon, 5 Apr 1999 11:30:58 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: Make world Broken on my machine Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What am I doing wrong here, this is my error, CVSup was run 10 minutes ago. cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/objc -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc - I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config -DFREEBSD_ NATIVE -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386 -unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr /src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c In file included from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/ gcc/config/i386/xm-i386.h:43, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/ gcc/hconfig.h:2, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/ gcc/gengenrtl.c:22: /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: linux.h: N o such file or directory /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:4: i386/freeb sd-elf.h: No such file or directory *** Error code 1 Stop. with a bunch more of the error code 1 and Stop. can someone help? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 8:56:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 7ECB314BE7 for ; Mon, 5 Apr 1999 08:56:01 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA20397; Mon, 5 Apr 1999 11:53:59 -0400 (EDT) (envelope-from wollman) Date: Mon, 5 Apr 1999 11:53:59 -0400 (EDT) From: Garrett Wollman Message-Id: <199904051553.LAA20397@khavrinen.lcs.mit.edu> To: Ian West Cc: current@FreeBSD.ORG Subject: Re: Atime not set on execution ? In-Reply-To: <3707F2D6.C37B4B7D@apdata.com.au> References: <199904041017.UAA29125@godzilla.zeta.org.au> <3707F2D6.C37B4B7D@apdata.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Thanks for the response, there isn't per chance an option to turn this > on is there ? The way programs are executed (by intention) does not run through the code path which would touch the access time. The POSIX.1 specification, IIRC, requires that the atime be updated when the program exits -- this would be very inefficient to do in our VM system. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 8:57:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 6296614BE7 for ; Mon, 5 Apr 1999 08:57:36 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.140]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA906; Mon, 5 Apr 1999 17:55:36 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id RAA17709; Mon, 5 Apr 1999 17:55:37 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990404132114.C77056@nuxi.com> Date: Mon, 05 Apr 1999 17:55:36 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Re: World Breakage? Cc: current@FreeBSD.ORG, Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Apr-99 David O'Brien wrote: >> /usr/obj/home/imp/FreeBSD/src/tmp/usr/lib/libc.a(mktemp.o): In function >> `mkstemps': >> mktemp.o(.text+0x0): multiple definition of `mkstemps' >> /usr/obj/home/imp/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(mks >> temp.o)(.text+0x0): first defined here >> /usr/libexec/elf/ld: Warning: size of symbol `mkstemps' changed from 573 >> to 39 in mktemp.o > > I can't duplicate this problem. Just to be sure... you aren't using > -DNOCLEAN, -O2 or anything like that, right? I now can =) using a freshly cvsupped repository, cvs checkout of src, and make with a clean obj tree. So -DNOCLEAN isn't the issue, I replace -O2 in the /etc/make.conf with -Os. Funny thing that it bombs now, whereas I made world fine before. ===> gnu/usr.bin/cc/cc cc -Os -pipe -DFREEBSD_ELF -I/work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc -I/work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"\" -I/usr/obj/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_tools -I/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_tools -c /work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/gcc.c In file included from /work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/gcc.c:555: /usr/obj/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_tools/multilib.h:4: warning: initialization from incompatible pointer type /work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/gcc.c:1178: warning: initialization from incompatible pointer type /work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/gcc.c: In function `print_multilib_info': /work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/gcc.c:5919: warning: assignment from incompatible pointer type cc -Os -pipe -DFREEBSD_ELF -I/work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc -I/work/FreeBSD/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"\" -I/usr/obj/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_tools -I/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_tools -o cc gcc.o /usr/obj/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a /usr/obj/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-tem p.o): In function `make_temp_file': choose-temp.o(.text+0x278): undefined reference to `mkstemps' *** Error code 1 Stop. Going to look at Warner's patches just in case... --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 9:11:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id C17D61543C for ; Mon, 5 Apr 1999 09:11:45 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id JAA24355; Mon, 5 Apr 1999 09:05:29 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904051605.JAA24355@troutmask.apl.washington.edu> Subject: Re: egcs In-Reply-To: <199904050747.PAA07291@spinner.netplex.com.au> from Peter Wemm at "Apr 5, 1999 3:47:10 pm" To: peter@netplex.com.au (Peter Wemm) Date: Mon, 5 Apr 1999 09:05:29 -0700 (PDT) Cc: obrien@NUXI.com, gljohns@bellsouth.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > "David O'Brien" wrote: > > > What will become of f77 which is in "src/gnu/usr.bin/cc/f77"? This > > > seems to be a good time to decide what will happen with Fortran in the > > > base FreeBSD system. > > > > VERY good question. I have no opinion in the matter, but will follow the > > wishes of others (or Core, or committers, or who ever should make this > > decision and who ever tells me which way to go). > > My preference is to have g77 as part of the base egcs in the tree, and if > we need f77 (ie: the Fortran->C translator), port-ify it since it is easily > made standalone while g77 isn't. I already have a port of f2c and a new f77 wrapper to deal with f2c+gcc. The includes the runtime libraries libI77 and libF77. > > The sticky bit is what how to handle libI77 and libF77.. > g77 has combined these libraries into is libg77. If g77 were brought into the tree, I think we could delete src/gnu/usr.bin/cc/f77, src/lib/{f2c, libI77, libF77}, and src/usr.bin/f2c. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 9:19:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 944EE1543C for ; Mon, 5 Apr 1999 09:19:39 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA10930; Mon, 5 Apr 1999 10:17:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA70978; Mon, 5 Apr 1999 10:18:31 -0600 (MDT) Message-Id: <199904051618.KAA70978@harmony.village.org> To: obrien@NUXI.com Subject: Re: Boot blocks Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 04 Apr 1999 23:28:54 PDT." <19990404232854.A5300@nuxi.com> References: <19990404232854.A5300@nuxi.com> <199904050513.XAA69299@harmony.village.org> Date: Mon, 05 Apr 1999 10:18:31 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990404232854.A5300@nuxi.com> "David O'Brien" writes: : Were you able to actually boot the bootblocks compiled with EGCS and -Os ? : (I know the optimization gives us the space we need, but I'm not upto : testing new bootblocks at this moment) To be honest, I didn't test them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 9:24:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 04B02153E8 for ; Mon, 5 Apr 1999 09:24:54 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA10950; Mon, 5 Apr 1999 10:23:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA71285; Mon, 5 Apr 1999 10:23:47 -0600 (MDT) Message-Id: <199904051623.KAA71285@harmony.village.org> To: Jeroen Ruigrok/Asmodai Subject: Re: World Breakage? Cc: "David O'Brien" , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 05 Apr 1999 17:55:36 +0200." References: Date: Mon, 05 Apr 1999 10:23:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jeroen Ruigrok/Asmodai writes: : Funny thing that it bombs now, whereas I made world fine before. Looks like you didn't get the other of my two changes. It was to src/gnu/usr.bin/cc/cc_drv/Makefile. Make sure that it doesn't have mkstemp.o listed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 9:27:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 07808153E8 for ; Mon, 5 Apr 1999 09:27:38 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id SAA79966; Mon, 5 Apr 1999 18:25:07 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904051625.SAA79966@freebsd.dk> Subject: Re: make -jn ? In-Reply-To: from Bob Bishop at "Apr 5, 1999 4:13:43 pm" To: rb@gid.co.uk (Bob Bishop) Date: Mon, 5 Apr 1999 18:25:06 +0200 (CEST) Cc: obrien@NUXI.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bob Bishop wrote: > World builds OK here now, kernel, bootblocks and all. Good job! > > Is `make -jn' safe yet? Could turn these test builds round a lot faster :-) Nope... ===> cc_int make: don't know how to make insn-attrtab.c. Stop *** Error code 2 -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 9:47:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 7654F1544D for ; Mon, 5 Apr 1999 09:47:44 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.44]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6A2C; Mon, 5 Apr 1999 18:45:34 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id SAA17761; Mon, 5 Apr 1999 18:45:36 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904051618.KAA70978@harmony.village.org> Date: Mon, 05 Apr 1999 18:45:36 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Warner Losh Subject: Re: Boot blocks Cc: current@FreeBSD.ORG, obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Warner Losh wrote: > In message <19990404232854.A5300@nuxi.com> "David O'Brien" writes: >: Were you able to actually boot the bootblocks compiled with EGCS and -Os >: ? >: (I know the optimization gives us the space we need, but I'm not upto >: testing new bootblocks at this moment) > > To be honest, I didn't test them. I did, they work, with -O though, due to -Os not working at that point yet... Just tried a make of boot2 after rebooting with the original Makefile which has -Os in it, it compiles. Haven't tested that situation yet, but I don't think it oughtta be that different. --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 9:57:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id D116D14D23 for ; Mon, 5 Apr 1999 09:57:21 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.44]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1976; Mon, 5 Apr 1999 18:55:22 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id SAA17792; Mon, 5 Apr 1999 18:55:25 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904051623.KAA71285@harmony.village.org> Date: Mon, 05 Apr 1999 18:55:25 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Warner Losh Subject: Re: World Breakage? Cc: current@FreeBSD.ORG, "David O'Brien" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Warner Losh wrote: > In message Jeroen Ruigrok/Asmodai > writes: >: Funny thing that it bombs now, whereas I made world fine before. > > Looks like you didn't get the other of my two changes. It was to > src/gnu/usr.bin/cc/cc_drv/Makefile. Make sure that it doesn't have > mkstemp.o listed. Looking at that file now: # $Id: Makefile,v 1.2 1999/04/04 20:29:43 imp Exp $ That seems right... [asmodai@daemon] (13) $ more Makefile | grep mkstemp [asmodai@daemon] (14) $ That's odd... Will nuke /usr/obj again just be sure for 100% on that part, but I think that I oughtta had that problem on my earlier builds as well though... Hmmm... --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 9:58:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id ABCD414D23 for ; Mon, 5 Apr 1999 09:58:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA11112; Mon, 5 Apr 1999 10:57:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA71494; Mon, 5 Apr 1999 10:57:46 -0600 (MDT) Message-Id: <199904051657.KAA71494@harmony.village.org> To: Jeroen Ruigrok/Asmodai Subject: Re: World Breakage? Cc: current@FreeBSD.ORG, "David O'Brien" In-reply-to: Your message of "Mon, 05 Apr 1999 18:55:25 +0200." References: Date: Mon, 05 Apr 1999 10:57:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jeroen Ruigrok/Asmodai writes: : Will nuke /usr/obj again just be sure for 100% on that part, but I think : that I oughtta had that problem on my earlier builds as well though... Odd. I completed a make world with my changes... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:12:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id A371D14D08 for ; Mon, 5 Apr 1999 10:12:29 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA12232; Tue, 6 Apr 1999 03:10:31 +1000 Date: Tue, 6 Apr 1999 03:10:31 +1000 From: Bruce Evans Message-Id: <199904051710.DAA12232@godzilla.zeta.org.au> To: ian@apdata.com.au, wollman@khavrinen.lcs.mit.edu Subject: Re: Atime not set on execution ? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The way programs are executed (by intention) does not run through the >code path which would touch the access time. The POSIX.1 >specification, IIRC, requires that the atime be updated when the >program exits -- this would be very inefficient to do in our VM >system. It requires only _marking_ for update "upon successful completion". Completion of exec doesn't seem to be specified properly, but it's clear that it is related to replacement of the process image and not to process lifetime. Since POSIX.1 doesn't and shouldn't specify virtual memory, we can consider the process image to be replaced when it is only replaced virtually. My quick and dirty implementation does a VOP_SETATTR(). This does a full update of the atime, but syncing the update to disk is delayed for ufs file systems, so setting atimes for exec is no worse than setting them for read. However, for nfs the updates are synchronous (or at least they were when I last tested this under nfsv2 a couple of years ago), so they are relatively expensive. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:20:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 91E94150CA; Mon, 5 Apr 1999 10:19:59 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA10118; Mon, 5 Apr 1999 19:18:01 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 398CA884F; Mon, 5 Apr 1999 18:52:46 +0200 (CEST) Date: Mon, 5 Apr 1999 18:52:46 +0200 From: Ollivier Robert To: Jeroen Ruigrok/Asmodai Cc: FreeBSD Current , "David O'Brien" Subject: Re: Success! Message-ID: <19990405185246.A44439@keltia.freenix.fr> Mail-Followup-To: Jeroen Ruigrok/Asmodai , FreeBSD Current , David O'Brien References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Apr 05, 1999 at 01:27:58PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jeroen Ruigrok/Asmodai: > make world completed ok. Even rebooted to test the bootblocks (see previous > messages) and all is well. Same here except that I don't seem to experiment your problems below. The machine is up and running, WindowMaker is fine and ntpd too. 2x PPro/200, SMP kernel, 64 MB RAM, make world w/o -j. FreeBSD tara.freenix.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Apr 5 16:12:25 CEST 1999 root@tara:/src/src/sys/compile/nTARA i386 6:49PM up 2:34, 6 users, load averages: 0.00, 0.00, 0.00 remote refid st t when poll reach delay offset disp ============================================================================== 127.127.1.0 127.127.1.0 10 - 26 64 377 0.00 0.000 0.93 *127.127.8.0 .DCFa. 0 - 27 64 177 0.00 35.446 0.01 > Well, sorta, lotsa errors when trying to make a new kernel, fonts are > fuqed, Window Maker all of a sudden acts weird with its general menu, ppp > gives an ioctl error... My sources are from CTM cvs-cur #5210 made on 1999/04/04 23:14:46. Congrats David ! -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:37:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id C456414D93 for ; Mon, 5 Apr 1999 10:37:11 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id NAA00246 for ; Mon, 5 Apr 1999 13:37:01 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Mon, 5 Apr 1999 13:37:01 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: I still get errors on make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I still get errors, would killing all the source, and re-supping do the trick?? Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:37:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 20F7814D93 for ; Mon, 5 Apr 1999 10:37:34 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id TAA25010 for freebsd-current@freebsd.org; Mon, 5 Apr 1999 19:35:35 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id 7B38139; Mon, 5 Apr 1999 19:35:06 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 70E7B1E2E for ; Mon, 5 Apr 1999 19:35:06 +0200 (CEST) Date: Mon, 5 Apr 1999 19:35:06 +0200 (CEST) From: Blaz Zupan To: freebsd-current@freebsd.org Subject: C++ with egcs - no go Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just successfully completed a make world and everything appears to be working correctly (good job, David!), except compiling C++ programs: /tmp/x> cat test.c #include main() { cout << "Hello world!\n"; } /tmp/x> c++ test.c /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' /tmp/x> I remember someone mentioning this same problem here and it was supposedly fixed with a later commit. I just cvsupped and got some changes to ppbus by peter, which as far as I remember were after the latest changes by David O'Brien, so I guess I do have the latest sources. Anybody else seeing this after the latest cvsup (as of 15 minutes ago)? Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:40:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (Postfix) with ESMTP id 60D621544D for ; Mon, 5 Apr 1999 10:40:13 -0700 (PDT) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id TAA27417 for ; Mon, 5 Apr 1999 19:38:15 +0200 (CEST) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.8.5) with ESMTP id TAA24484 for ; Mon, 5 Apr 1999 19:37:36 +0200 (MET DST) Message-Id: <199904051737.TAA24484@trantor.xs4all.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: cpp breakage on egcs -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Apr 1999 19:37:36 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just found that just calling /usr/libexec/cpp -traditional causes it to abort with the following error: /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Internal compiler error in function main This breaks rpcgen thus breaking make buildworld in my box . In addition xdm and xdrb also suffer .. This is on a system on which I ran a succesfull make world last night. The kernel is also built using egcs. This is the only problem I have found so far. The CFLAGS for make world were -O2 -pipe, for the kernel -O -pipe. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:40:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id C0F9015469 for ; Mon, 5 Apr 1999 10:40:37 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id KAA16359; Mon, 5 Apr 1999 10:38:39 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id KAA91678; Mon, 5 Apr 1999 10:38:39 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 5 Apr 1999 10:38:39 -0700 (PDT) Message-Id: <199904051738.KAA91678@vashon.polstra.com> To: paulz@trantor.xs4all.nl Subject: Re: CPP broken on egcs current In-Reply-To: <199904051112.NAA22210@trantor.xs4all.nl> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904051112.NAA22210@trantor.xs4all.nl>, Paul van der Zwan wrote: > > A make buildworld fails on an freshly rebuilt system. > The following error is shown: ... > /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Int > ernal compiler error in function main > *** Error code 33 Your installed cpp was built from slightly old sources. Make sure your source tree is up-to-date. Then manually "make cleandir; make cleandir; make obj; make depend; make all install" in "src/gnu/usr.bin/cc". It will be OK after that. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:42: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id A5D961547C for ; Mon, 5 Apr 1999 10:41:54 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id NAA22365; Mon, 5 Apr 1999 13:39:46 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Mon, 5 Apr 1999 13:39:45 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: terry@whistle.com Cc: current@freebsd.org Subject: aio_read Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry, In the BUGS section of the 4.0-CURRENT aio_read man page, the following comment is made: The value of iocb->aio_offset is ignored. Is this actually the case, and what would be required to fix it? Does this comment imply that reads always occur at the current file offset from the open file structure? What I would like to do is have a child process read from an inherited file descriptor without affecting the parent process's access to the descriptor (for example, the offset it reads from using a normal read() or readv()). I address this to you because you seem to be listed in the man page as the author of the man page (although it looks like John Dyson has the copyright on the source code?) Thanks, Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:44:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 2C39115465 for ; Mon, 5 Apr 1999 10:44:10 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.141]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1CE4; Mon, 5 Apr 1999 19:42:12 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA48997; Mon, 5 Apr 1999 19:42:14 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904051657.KAA71494@harmony.village.org> Date: Mon, 05 Apr 1999 19:42:14 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Warner Losh Subject: Re: World Breakage? Cc: "David O'Brien" , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Warner Losh wrote: > In message Jeroen Ruigrok/Asmodai > writes: >: Will nuke /usr/obj again just be sure for 100% on that part, but I think >: that I oughtta had that problem on my earlier builds as well though... > > Odd. I completed a make world with my changes... Oops, said that wrong: I did _not_ have that problem on my earlier build. Anyways I just rm -rf'd the contents of /usr/obj and trying it again with a fresh cvsup. ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /work/FreeBSD/src/include/rpcsvc/klm_prot.x -o klm_prot.h /work/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:188 2: Internal compiler error in function main *** Error code 33 Stop. *** Error code 1 *sigh* and it's so easy to find what those error messages mean. Btw, using my previous make world the egcs info files didn't get installed. Seems that the make install target doesn't get called. Need to verify that though. A make && make install from the subdir works though as it should. --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:46:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6A7B21544D for ; Mon, 5 Apr 1999 10:46:39 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA11155; Mon, 5 Apr 1999 10:44:25 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 10:44:25 -0700 (PDT) From: Matthew Dillon Message-Id: <199904051744.KAA11155@apollo.backplane.com> To: Robert Watson Cc: terry@whistle.com, current@FreeBSD.ORG Subject: Re: aio_read References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Terry, : :In the BUGS section of the 4.0-CURRENT aio_read man page, the following :comment is made: : : The value of iocb->aio_offset is ignored. : :Is this actually the case, and what would be required to fix it? Does :this comment imply that reads always occur at the current file offset from :the open file structure? What I would like to do is have a child process :... : :Thanks, : : Robert N Watson : :robert@fledge.watson.org http://www.watson.org/~robert/ I believe this either has been fixed or is about to be fixed by Alan. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:53: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 8A50A153F1 for ; Mon, 5 Apr 1999 10:52:58 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.141]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3541; Mon, 5 Apr 1999 19:50:59 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA49038; Mon, 5 Apr 1999 19:51:02 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 05 Apr 1999 19:51:02 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Blaz Zupan Subject: RE: C++ with egcs - no go Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Blaz Zupan wrote: > /tmp/x> c++ test.c > /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' > /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' > /tmp/x> > Anybody else seeing this after the latest cvsup (as of 15 minutes ago)? Those errors are still present. Watch the cvs messages closely or -current ;) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 10:53:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 4C519154FA for ; Mon, 5 Apr 1999 10:53:08 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.141]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6EDD; Mon, 5 Apr 1999 19:50:58 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA49032; Mon, 5 Apr 1999 19:51:00 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 05 Apr 1999 19:51:00 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Kenneth Wayne Culver Subject: RE: I still get errors on make world Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Kenneth Wayne Culver wrote: > I still get errors, would killing all the source, and re-supping do the > trick?? To ensure a complete clean build try to do this: rm -rf the whole of /usr/obj cvsup one last time then make world or buildworld WITHOUT -j flags. Takes a while, but ensure accurate errors for the remaining errors. That's how I am trying to `help' David ;) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 11:18: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id F0D0914E1C for ; Mon, 5 Apr 1999 11:18:06 -0700 (PDT) (envelope-from terry@whistle.com) Received: from whistle.com (tlambert.whistle.com [207.76.205.208]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA67832; Mon, 5 Apr 1999 11:06:08 -0700 (PDT) Message-ID: <3708F93A.B2810187@whistle.com> Date: Mon, 05 Apr 1999 10:56:10 -0700 From: Terry Lambert X-Mailer: Mozilla 4.06 [en] (Win95; I) MIME-Version: 1.0 To: Robert Watson Cc: current@freebsd.org Subject: Re: aio_read References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson wrote: > > Terry, > > In the BUGS section of the 4.0-CURRENT aio_read man page, > the following comment is made: > > The value of iocb->aio_offset is ignored. > > Is this actually the case, and what would be required to > fix it? Does this comment imply that reads always occur > at the current file offset from the open file structure? It was true at the time I wrote the manual page, which I verified against the source code for the bugs section. It would be fairly trivial (IMO) to fix this, either by setting the current file offset before doing the read, or, more correctly, using the element offset itself instead (which would allow concurrent aio_read calls on the same fd at staggered offsets). > What I would like to do is have a child process read > from an inherited file descriptor without affecting the > parent process's access to the descriptor (for example, > the offset it reads from using a normal read() or readv()). This should be the way it works anyway. The offset is an artifact of the struct file, not the vnode, and a child process inheriting a descriptor does so by making a copy of the parent's open file table into its own open file table -- and thus the child gets its own struct file that points to the vnode, and thus a seperate "current offset". An exception to this would be where the parent and child share kernel structures as a result of an rfork() without the RFFDG flag set. > I address this to you because you seem to be listed in the > man page as the author of the man page (although it looks > like John Dyson has the copyright on the source code?) John did the code. I did the man page because I wanted to use it with some test code, but there wasn't a man page. 8-). -- Terry Lambert -- Whistle Communications, Inc. -- terry@whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 11:28:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8D138154BA for ; Mon, 5 Apr 1999 11:28:11 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id OAA22574; Mon, 5 Apr 1999 14:26:13 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Mon, 5 Apr 1999 14:26:12 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Terry Lambert Cc: current@freebsd.org Subject: Re: aio_read In-Reply-To: <3708F93A.B2810187@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, Terry Lambert wrote: > > What I would like to do is have a child process read > > from an inherited file descriptor without affecting the > > parent process's access to the descriptor (for example, > > the offset it reads from using a normal read() or readv()). > > This should be the way it works anyway. The offset is an > artifact of the struct file, not the vnode, and a child > process inheriting a descriptor does so by making a copy > of the parent's open file table into its own open file > table -- and thus the child gets its own struct file that > points to the vnode, and thus a seperate "current offset". This was not my impression; I thought that children had their own descriptor entries on a per-process basis, but that they all pointed to the same open file entry when inherited. I was contemplating adding a modified dup call to allow the duplication of an open file entry to add the behavior you describe, as that is actually the behavior I want. The BSD4.4 book, anyway, fairly clearly states that the behavior is a shared file offset per open file entry, and multiple open file entries pointing to a vnode. (page 205, and better yet, p207 paragraph 3). In some ways this is behavior is nice (multiple processes round-robining on data from a file, for example, or writing to a file, and in particular compatible socket-like or pipe-like behavior), in some ways it is not (desire to have an independent child). > An exception to this would be where the parent and child > share kernel structures as a result of an rfork() without > the RFFDG flag set. > > > I address this to you because you seem to be listed in the > > man page as the author of the man page (although it looks > > like John Dyson has the copyright on the source code?) > > John did the code. I did the man page because I wanted to > use it with some test code, but there wasn't a man page. 8-). Sounds good to me; I'm all for documentation. We seem to also need an aio_write page, and an aio_cancel page that documents its brokedness, etc. Maybe I'll stick them together once I finish with this project. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 11:33:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 79CD714D3E for ; Mon, 5 Apr 1999 11:32:55 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.141]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1FD4; Mon, 5 Apr 1999 20:30:57 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id UAA50672; Mon, 5 Apr 1999 20:31:00 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 05 Apr 1999 20:31:00 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Warner Losh Subject: Re: World Breakage? Cc: current@FreeBSD.ORG, "David O'Brien" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Jeroen Ruigrok/Asmodai wrote: > On 05-Apr-99 Warner Losh wrote: >> In message Jeroen Ruigrok/Asmodai >> writes: > > ===> rpcsvc > rpcgen -C -h -DWANT_NFS3 /work/FreeBSD/src/include/rpcsvc/klm_prot.x -o > klm_prot.h > /work/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1 > 882: Internal compiler error in function main > *** Error code 33 > > Stop. > *** Error code 1 Tried to remake the cc stuff first as suggested in a previous mail by John Polstra. However this returns me to the mkstemps problem with a source tree which _is_ accurate though... --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 11:36:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 730F6153F1 for ; Mon, 5 Apr 1999 11:36:34 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA11656; Mon, 5 Apr 1999 11:34:35 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 11:34:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199904051834.LAA11656@apollo.backplane.com> To: Robert Watson Cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: aio_read References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :This was not my impression; I thought that children had their own :descriptor entries on a per-process basis, but that they all pointed to :the same open file entry when inherited. I was contemplating adding a They do indeed point to the same file entry. Also, when you dup() a descriptor the two descriptors are pointing to the same file entry. This means that they share the same seek offset... seeking in one descriptor changes the seek position in the other descriptor and even the other descriptor in the other process. UNIX has been broken this way from day 1. It was a major design mistake. The only way to get your own descriptor seek offset is to open() the file again. The aio stuff gets around this by introducing a seek offset in the syscall, but historical use of the file descriptor seek offset broke aio's syscall-based offset. Alan has committed fixes to much of the historical code (in vn_read() and vn_write()) that should mean that aio offsets now work, but I haven't tested it myself. -Matt Matthew Dillon : Robert N Watson : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 11:51:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (Postfix) with ESMTP id 7070E14D23 for ; Mon, 5 Apr 1999 11:51:20 -0700 (PDT) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id UAA08992; Mon, 5 Apr 1999 20:49:22 +0200 (CEST) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.8.5) with ESMTP id UAA70097; Mon, 5 Apr 1999 20:30:27 +0200 (MET DST) Message-Id: <199904051830.UAA70097@trantor.xs4all.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: current@freebsd.org Subject: Re: CPP broken on egcs current In-reply-to: Your message of "Mon, 05 Apr 1999 10:38:39 PDT." <199904051738.KAA91678@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Apr 1999 20:30:27 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <199904051112.NAA22210@trantor.xs4all.nl>, > Paul van der Zwan wrote: > > > > A make buildworld fails on an freshly rebuilt system. > > The following error is shown: > ... > > /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Int > > ernal compiler error in function main > > *** Error code 33 > > Your installed cpp was built from slightly old sources. Make sure > your source tree is up-to-date. Then manually "make cleandir; > make cleandir; make obj; make depend; make all install" in > "src/gnu/usr.bin/cc". It will be OK after that. > That seems to fix it.. Thanks. BTW why the double make cleandir ?? a typo ? or is there some magic. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 11:52:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail15.svr.pol.co.uk (mail15.svr.pol.co.uk [195.92.193.25]) by hub.freebsd.org (Postfix) with ESMTP id 2EA8614D3E for ; Mon, 5 Apr 1999 11:50:32 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: from [195.92.197.25] (helo=mail17.svr.pol.co.uk) by mail15.svr.pol.co.uk with esmtp (Exim 2.12 #1) id 10UEQ2-0000cP-00; Mon, 5 Apr 1999 19:48:22 +0100 Received: from modem-97.torchbearer.dialup.pol.co.uk ([62.136.108.97] helo=k2c.co.uk) by mail17.svr.pol.co.uk with esmtp (Exim 2.12 #1) id 10UENl-0005el-00; Mon, 5 Apr 1999 19:46:01 +0100 Message-ID: <3709045E.DFA21C9B@k2c.co.uk> Date: Mon, 05 Apr 1999 19:43:42 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai Cc: Blaz Zupan , freebsd-current@freebsd.org Subject: Re: C++ with egcs - no go References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > > Those errors are still present. > Wrong: [(dampurep)~/src]: cat hello.cc // begin program #include using namespace std; int main(int argc, char** argv) { cout << "Hello World!!!\n" << endl; return 0; } // end program [(dampurep)~/src]: c++ -Os -march=pentiumpro -o hello hello.cc [(dampurep)~/src]: ./hello Hello World!!! [(dampurep)~/src]: PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 11:54:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D22B714D3E for ; Mon, 5 Apr 1999 11:54:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA16722; Mon, 5 Apr 1999 11:52:55 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id LAA91888; Mon, 5 Apr 1999 11:52:55 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904051830.UAA70097@trantor.xs4all.nl> Date: Mon, 05 Apr 1999 11:52:55 -0800 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Paul van der Zwan Subject: Re: CPP broken on egcs current Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul van der Zwan wrote: > BTW why the double make cleandir ?? a typo ? or is there some magic. It helps to ensure that there aren't any old object files in your source tree. The first make cleandir removes the "obj" directory. The second one removes any generated files from the source directory. There shouldn't be any generated files there, but if there are any it can cause confusing problems. So I usually do the make cleandir twice just to be sure. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 11:59:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5EF8A14D3E for ; Mon, 5 Apr 1999 11:59:17 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA11474; Mon, 5 Apr 1999 12:57:24 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA72303; Mon, 5 Apr 1999 12:58:08 -0600 (MDT) Message-Id: <199904051858.MAA72303@harmony.village.org> To: Jeroen Ruigrok/Asmodai Subject: Re: World Breakage? Cc: current@FreeBSD.ORG, "David O'Brien" In-reply-to: Your message of "Mon, 05 Apr 1999 20:31:00 +0200." References: Date: Mon, 05 Apr 1999 12:58:08 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jeroen Ruigrok/Asmodai writes: : Tried to remake the cc stuff first as suggested in a previous mail by John : Polstra. However this returns me to the mkstemps problem with a source tree : which _is_ accurate though... Can you do an ar: ar tv /usr/obj//gnu/usr.bin/cc/cc_drv/libcc_drv.a Also make sure that you have version 1.2 of src/gnu/usr.sbin/cc/cc_drv/Makefile. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12: 0:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 2C13814D3F for ; Mon, 5 Apr 1999 12:00:34 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id NAA04965; Mon, 5 Apr 1999 13:58:29 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id NAA04959; Mon, 5 Apr 1999 13:58:21 -0500 (CDT) Message-ID: <023c01be7f96$72c222a0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Pierre Y. Dampure" , "Jeroen Ruigrok/Asmodai" Cc: "Blaz Zupan" , Subject: Re: C++ with egcs - no go Date: Mon, 5 Apr 1999 13:59:28 -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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I made the original post with the below program. I have rebuilt the entire world using -O2 -pipe -mpentiumpro and all works well. I can safely report the problem has disappeared. I though I would attempt compiling Qt and see how that works. I will report back if a problem arrises. Tom Veldhouse veldy@visi.com -----Original Message----- From: Pierre Y. Dampure To: Jeroen Ruigrok/Asmodai Cc: Blaz Zupan ; freebsd-current@FreeBSD.ORG Date: Monday, April 05, 1999 1:51 PM Subject: Re: C++ with egcs - no go >Jeroen Ruigrok/Asmodai wrote: >> >> Those errors are still present. >> > >Wrong: > >[(dampurep)~/src]: cat >hello.cc // begin >program >#include > >using namespace std; > >int main(int argc, char** argv) { > cout << "Hello World!!!\n" << endl; > return 0; >} >// end program >[(dampurep)~/src]: c++ -Os -march=pentiumpro -o hello hello.cc >[(dampurep)~/src]: ./hello >Hello World!!! > >[(dampurep)~/src]: > >PYD > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12: 3:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 472DE1515F for ; Mon, 5 Apr 1999 12:03:27 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.141]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3E27; Mon, 5 Apr 1999 21:01:25 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id VAA50769; Mon, 5 Apr 1999 21:01:24 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3709045E.DFA21C9B@k2c.co.uk> Date: Mon, 05 Apr 1999 21:01:24 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "Pierre Y. Dampure" Subject: Re: C++ with egcs - no go Cc: freebsd-current@freebsd.org, Blaz Zupan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Pierre Y. Dampure wrote: > Jeroen Ruigrok/Asmodai wrote: >> >> Those errors are still present. >> > > Wrong: > > [(dampurep)~/src]: c++ -Os -march=pentiumpro -o hello hello.cc > [(dampurep)~/src]: ./hello > Hello World!!! > > [(dampurep)~/src]: OK, they were/are present here =) glad to know they are/might be fixed now. Would gladly test it if my make world would continue, or that I could get rid of this mkstemps. --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12: 7:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 83760154C2 for ; Mon, 5 Apr 1999 12:07:43 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA21948; Mon, 5 Apr 1999 12:05:39 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405120539.A21900@nuxi.com> Date: Mon, 5 Apr 1999 12:05:39 -0700 From: "David O'Brien" To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: World Breakage? Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Apr 05, 1999 at 08:31:00PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ===> rpcsvc > > rpcgen -C -h -DWANT_NFS3 /work/FreeBSD/src/include/rpcsvc/klm_prot.x -o > > klm_prot.h > > /work/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1 > > 882: Internal compiler error in function main > > *** Error code 33 This has been fixed. > Tried to remake the cc stuff first as suggested in a previous mail by John > Polstra. However this returns me to the mkstemps problem with a source tree > which _is_ accurate though... Sounds like maybe you should try a different CVSup server. Maybe there is one out there that isn't up to date? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:10:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 04F5F1547F; Mon, 5 Apr 1999 12:10:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA12939; Mon, 5 Apr 1999 12:08:31 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 12:08:31 -0700 (PDT) From: Matthew Dillon Message-Id: <199904051908.MAA12939@apollo.backplane.com> To: Julian Elischer Cc: Alan Cox , current@FreeBSD.ORG, luoqi@FreeBSD.ORG Subject: Re: SMP users (important) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :julian :> :> I'd like to see this too. I will soon have two SMP boxes of my own to play :> with for my own personal use and for an upcoming project, and at least one :> will be available for SMP life-testing purposes for several months. :> I really want to see two things: (1) Actual sharing of the physical pmap :> between rfork(RFMEM|RFPROC)'d processes, and (2) Avoiding the %cr3 reload :> ( which clears the TLB ) when switching between such processes. : :This would also suggest shceduler changes that would increasr the :likelyhood of 'related' processes being scheduled together. : :One scheme I remember id the A-list/B-list scheme, where :each scheduling priority has two list that are alternated. :whichever list is being drained is not eligible for receiving new items. :They must go to the other list. When the active list is drained and theya :are switched, the new list is first sorted accoring to affinity :related effects. : :julian This can get real tricky. I think the scheduler will almost do this anyway, just due to the way threads tend to go to sleep and get woken up, so adding a lot of sophistication here may not help. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:11:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 38716153D9 for ; Mon, 5 Apr 1999 12:11:36 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA21989; Mon, 5 Apr 1999 12:09:37 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405120937.C21900@nuxi.com> Date: Mon, 5 Apr 1999 12:09:37 -0700 From: "David O'Brien" To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: World Breakage? Reply-To: obrien@NUXI.com References: <199904051657.KAA71494@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Apr 05, 1999 at 07:42:14PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ===> rpcsvc > rpcgen -C -h -DWANT_NFS3 /work/FreeBSD/src/include/rpcsvc/klm_prot.x -o > klm_prot.h > /work/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:188 > 2: Internal compiler error in function main > *** Error code 33 The fix for this is to CVSup, cd /usr/src/gnu/usr.bin/cc do a build and install from there. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:14:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 978C315096 for ; Mon, 5 Apr 1999 12:14:53 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.141]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2E40; Mon, 5 Apr 1999 21:12:55 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id VAA50796; Mon, 5 Apr 1999 21:12:58 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904051858.MAA72303@harmony.village.org> Date: Mon, 05 Apr 1999 21:12:58 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Warner Losh Subject: Re: World Breakage? Cc: "David O'Brien" , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 Warner Losh wrote: > In message Jeroen Ruigrok/Asmodai > writes: >: Tried to remake the cc stuff first as suggested in a previous mail by >: John Polstra. However this returns me to the mkstemps problem with a >: source tree which _is_ accurate though... > > Can you do an ar: > > ar tv /usr/obj//gnu/usr.bin/cc/cc_drv/libcc_drv.a [root@daemon] (9) # ar tv libcc_drv.a rw-r--r-- 0/0 920 Apr 5 20:09 1999 version.o rw-r--r-- 0/0 2035 Apr 5 20:09 1999 pexecute.o rw-r--r-- 0/0 1889 Apr 5 20:09 1999 prefix.o rw-r--r-- 0/0 2313 Apr 5 20:09 1999 obstack.o rw-r--r-- 0/0 2545 Apr 5 20:09 1999 choose-temp.o > Also make sure that you have version 1.2 of > src/gnu/usr.sbin/cc/cc_drv/Makefile. [root@daemon] (19) # more Makefile # # $Id: Makefile,v 1.2 1999/04/04 20:29:43 imp Exp $ # .include "../Makefile.inc" .PATH: ../cc_tools ${GCCDIR} SRCS= multilib.h choose-temp.c obstack.c prefix.c pexecute.c version.c CFLAGS+= -DPREFIX=\"/usr\" CFLAGS+= -DIN_GCC LIB= cc_drv NOPROFILE= YES NOPIC= YES install: @true ${OUT_OBJ}.o ${OUT_OBJ}.so: ${OUT_FILE} .include Before I tried the make world again with the latest stuff from cvsup I nuked /usr/obj to obilivion just to be sure... --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:23:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id C7967153D9 for ; Mon, 5 Apr 1999 12:23:12 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id VAA09400; Mon, 5 Apr 1999 21:21:11 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id VAA02130; Mon, 5 Apr 1999 21:17:09 +0200 (CEST) (envelope-from andreas) Date: Mon, 5 Apr 1999 21:17:09 +0200 From: Andreas Klemm To: Jeroen Ruigrok/Asmodai Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: I still get errors on make world Message-ID: <19990405211709.A1814@titan.klemm.gtn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Apr 05, 1999 at 07:51:00PM +0200 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 05, 1999 at 07:51:00PM +0200, Jeroen Ruigrok/Asmodai wrote: > On 05-Apr-99 Kenneth Wayne Culver wrote: > > I still get errors, would killing all the source, and re-supping do the > > trick?? > > To ensure a complete clean build try to do this: > > rm -rf the whole of /usr/obj > > cvsup one last time > > then make world or buildworld WITHOUT -j flags. > > Takes a while, but ensure accurate errors for the remaining errors. That's > how I am trying to `help' David ;) I did additionally the following: rm -rf /usr/include/* cd /usr/src make includes cd /usr/src/gnu/usr.bin/gcc make clean all install -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:25:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C598F14DC8 for ; Mon, 5 Apr 1999 12:25:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA22122; Mon, 5 Apr 1999 12:23:32 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405122332.A22022@nuxi.com> Date: Mon, 5 Apr 1999 12:23:32 -0700 From: "David O'Brien" To: Blaz Zupan , freebsd-current@FreeBSD.ORG Subject: Re: C++ with egcs - no go Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Blaz Zupan on Mon, Apr 05, 1999 at 07:35:06PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /tmp/x> c++ test.c The the list as a whole. For the next week or so, please use the "-v" flag when reporting compiler problems. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:27:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 83B8A14DC8 for ; Mon, 5 Apr 1999 12:27:16 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA22142; Mon, 5 Apr 1999 12:25:16 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405122516.B22022@nuxi.com> Date: Mon, 5 Apr 1999 12:25:16 -0700 From: "David O'Brien" To: Andreas Klemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: I still get errors on make world Reply-To: obrien@NUXI.com References: <19990405211709.A1814@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990405211709.A1814@titan.klemm.gtn.com>; from Andreas Klemm on Mon, Apr 05, 1999 at 09:17:09PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I did additionally the following: > rm -rf /usr/include/* > cd /usr/src > make includes cd /usr/src make -DCLOBBER includes -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:29:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 885AD14DC8 for ; Mon, 5 Apr 1999 12:29:41 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA22155; Mon, 5 Apr 1999 12:26:27 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405122627.C22022@nuxi.com> Date: Mon, 5 Apr 1999 12:26:27 -0700 From: "David O'Brien" To: Paul van der Zwan , current@FreeBSD.ORG Subject: Re: cpp breakage on egcs -current Reply-To: obrien@NUXI.com References: <199904051737.TAA24484@trantor.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904051737.TAA24484@trantor.xs4all.nl>; from Paul van der Zwan on Mon, Apr 05, 1999 at 07:37:36PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just found that just calling /usr/libexec/cpp -traditional causes it to > abort with the following error: > /usr/source/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Internal compiler error in function main This has been fixed. Please CVSup. Then you either need to go back to a pre-EGCS snapshot, or "cd /usr/src/gnu/usr.bin/cc && make depend && make && make install". -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:30:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 02D7A1515F for ; Mon, 5 Apr 1999 12:30:21 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.141]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA5A9D; Mon, 5 Apr 1999 21:28:22 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id VAA50835; Mon, 5 Apr 1999 21:28:24 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990405120539.A21900@nuxi.com> Date: Mon, 05 Apr 1999 21:28:24 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Re: World Breakage? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 David O'Brien wrote: >> > ===> rpcsvc >> > rpcgen -C -h -DWANT_NFS3 /work/FreeBSD/src/include/rpcsvc/klm_prot.x >> > -o klm_prot.h >> > /work/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp. >> > c:1882: Internal compiler error in function main >> > *** Error code 33 > > This has been fixed. I thought so as well. >> Tried to remake the cc stuff first as suggested in a previous mail by >> John Polstra. However this returns me to the mkstemps problem with a >> source tree which _is_ accurate though... > > Sounds like maybe you should try a different CVSup server. Maybe there > is one out there that isn't up to date? cvsup.nl.freebsd.org is one of the better, tracks changes very fast. Anyways, see my mail to Warner in which he asks about an ar and the Makefile revision. Just tried a cvsup again and nothing else came from it. I got all the cvs changes which were mailed to cvs-all, including the Makefile 1.2 from cc_drv. I also nuked /usr/obj, so where else can it get _any_ reference to mkstemps from? --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:33:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 72E0A154E6 for ; Mon, 5 Apr 1999 12:33:16 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA22199; Mon, 5 Apr 1999 12:31:11 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405123111.D22022@nuxi.com> Date: Mon, 5 Apr 1999 12:31:11 -0700 From: "David O'Brien" To: Jeroen Ruigrok/Asmodai , Warner Losh Cc: current@FreeBSD.ORG Subject: Re: World Breakage? Reply-To: obrien@NUXI.com References: <199904051858.MAA72303@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Apr 05, 1999 at 09:12:58PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Also make sure that you have version 1.2 of > > src/gnu/usr.sbin/cc/cc_drv/Makefile. You might also need to build libc manually. Looks like maybe you are building parts of the tree manually (to fix the cpp problem), and src/gnu/usr.sbin/cc/cc_drv/Makefile changed between your various compiles. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 12:51:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0C1FA14CF9 for ; Mon, 5 Apr 1999 12:51:28 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA22294; Mon, 5 Apr 1999 12:49:26 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405124926.E22022@nuxi.com> Date: Mon, 5 Apr 1999 12:49:26 -0700 From: "David O'Brien" To: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: Make world Broken on my machine Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kenneth Wayne Culver on Mon, Apr 05, 1999 at 11:30:58AM -0400 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/ > gcc/gengenrtl.c:22: > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: > linux.h: No such file or directory ^^^^^^^ I'm not sure where this came from. I never commited bits that created tm.h that specified "linux.h" to be included. How are you building "cc" and friends? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13: 1:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D463B14C8F for ; Mon, 5 Apr 1999 13:01:29 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA22324; Mon, 5 Apr 1999 12:59:31 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405125931.F22022@nuxi.com> Date: Mon, 5 Apr 1999 12:59:31 -0700 From: "David O'Brien" To: Jeroen Ruigrok/Asmodai Cc: FreeBSD Current Subject: Re: C++ Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Apr 05, 1999 at 03:06:53PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > configure:1333: c++ -o conftest conftest.C 1>&5 > /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' > /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' Some people are getting these errors, but I'm not sure why. It comes from not compiling the compiler and C++ libs with the same ``#define DEFAULT_VTABLE_THUNKS'' value. There may have been a short time window when all the bits were not in sync. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13: 4:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 36D53150DE for ; Mon, 5 Apr 1999 13:04:19 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA22343; Mon, 5 Apr 1999 13:02:11 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405130211.G22022@nuxi.com> Date: Mon, 5 Apr 1999 13:02:11 -0700 From: "David O'Brien" To: Mark Huizer , current@FreeBSD.ORG Subject: Re: gnu/usr.bin/genclass Reply-To: obrien@NUXI.com References: <19990405104313.A80394@ariel.xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990405104313.A80394@ariel.xaa.iae.nl>; from Mark Huizer on Mon, Apr 05, 1999 at 10:43:13AM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > genclass has GPPDIR=${BLA}/libg++ in its Makefile breaking the make > world, not sure if you noticed already, didn't see a commit message > about it :-) Fixed. `genclass' was a little behind libg++ in being disconnected from the build. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13: 8:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 92B1B15046 for ; Mon, 5 Apr 1999 13:08:43 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA22368; Mon, 5 Apr 1999 13:05:29 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405130529.H22022@nuxi.com> Date: Mon, 5 Apr 1999 13:05:29 -0700 From: "David O'Brien" To: paulz@trantor.xs4all.nl Cc: current@FreeBSD.ORG Subject: Re: CPP broken on egcs current Reply-To: obrien@NUXI.com References: <199904051112.NAA22210@trantor.xs4all.nl> <199904051738.KAA91678@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904051738.KAA91678@vashon.polstra.com>; from John Polstra on Mon, Apr 05, 1999 at 10:38:39AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Your installed cpp was built from slightly old sources. Make sure > your source tree is up-to-date. Then manually "make cleandir; > make cleandir; make obj; make depend; make all install" in > "src/gnu/usr.bin/cc". It will be OK after that. Thinking about it... some people might need to build libc to get one with mkstemp() in it. Of course that is hard to do if `cpp' is totally broken. If this is the case, people can try adding "SRCS += mkstemp.c" to src/gnu/usr.bin/cc/cc_drv/Makefile. Once a working ``cpp'' is installed, please remove the above hack though. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13:16: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 675EA1545C for ; Mon, 5 Apr 1999 13:14:18 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id QAA96385; Mon, 5 Apr 1999 16:09:39 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Mon, 5 Apr 1999 16:09:38 +0000 (GMT) From: eagle To: Bob Bishop Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: make -jn ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, Bob Bishop wrote: > World builds OK here now, kernel, bootblocks and all. Good job! > > Is `make -jn' safe yet? Could turn these test builds round a lot faster :-) > I'm running a test build at -j3 now following the reccomended ncpus +1 formula everything looks great so far. if it fails i'll let you know rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13:27:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 9A45315152 for ; Mon, 5 Apr 1999 13:27:42 -0700 (PDT) (envelope-from terry@whistle.com) Received: from whistle.com (tlambert.whistle.com [207.76.205.208]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA74651; Mon, 5 Apr 1999 13:21:53 -0700 (PDT) Message-ID: <37091909.B0257CB7@whistle.com> Date: Mon, 05 Apr 1999 13:11:53 -0700 From: Terry Lambert X-Mailer: Mozilla 4.06 [en] (Win95; I) MIME-Version: 1.0 To: Matthew Dillon Cc: Robert Watson , current@FreeBSD.ORG Subject: Re: aio_read References: <199904051834.LAA11656@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :This was not my impression; I thought that children had > :their own descriptor entries on a per-process basis, but > :that they all pointed to the same open file entry when > :inherited. I was contemplating adding a > > They do indeed point to the same file entry. Also, when > you dup() a descriptor the two descriptors are pointing > to the same file entry. > > This means that they share the same seek offset... seeking > in one descriptor changes the seek position in the other > descriptor and even the other descriptor in the other > process. > > UNIX has been broken this way from day 1. It was a major > design mistake. > The only way to get your own descriptor seek offset is to > open() the file again. After you said this, I found it so hard to believe that I had to go look. All I can say is, well I'll be damned; you could knock me over with a feather, and that doesn't happen often. I'm sure SVR4 and UnixWare is not like this; I had to write code explicitly for UnixWare, Solaris, and AIX to get, among other things, this type of behaviour. Here's the comment from Solaris: /* * One file structure is allocated for each open/creat/pipe call. * Main use is to hold the read/write pointer associated with * each open file. */ typedef struct file { It also credits SVr4 11.28 for file.h itself. I'm pretty sure Ultrix didn't have this bug, either, and it was 4.3 based. I think it's an artifact of the way the struct file is used on a list to create the system open file table in BSD 4.4 based systems (I checked BSDI; it has the bug). -- Terry Lambert -- Whistle Communications, Inc. -- terry@whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13:35: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id CCF21154DC for ; Mon, 5 Apr 1999 13:35:06 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id QAA23615; Mon, 5 Apr 1999 16:33:00 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Mon, 5 Apr 1999 16:33:00 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Terry Lambert Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: aio_read In-Reply-To: <37091909.B0257CB7@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, Terry Lambert wrote: > After you said this, I found it so hard to believe that I had > to go look. :-) > All I can say is, well I'll be damned; you could knock me over > with a feather, and that doesn't happen often. > > I'm sure SVR4 and UnixWare is not like this; I had to write > code explicitly for UnixWare, Solaris, and AIX to get, among > other things, this type of behaviour. > > Here's the comment from Solaris: > > /* > * One file structure is allocated for each open/creat/pipe call. > * Main use is to hold the read/write pointer associated with > * each open file. > */ > typedef struct file { > > It also credits SVr4 11.28 for file.h itself. Solaris fork() man page reports: SunOS 5.6 Last change: 28 Dec 1996 1 System Calls fork(2) o The child process has its own copy of the parent's file descriptors and directory streams. Each of the child's file descriptors shares a common file pointer with the corresponding file descriptor of the parent. Sorry :-). Sounds like this is in fact the documented correct behavior on all the platforms I can get to. And HPUX: Each of the child's file descriptors shares a common open file description with the corresponding file descriptor of the parent. This implies that changes to the file offset, file access mode, and file status flags of file descriptors in the parent also affect those in the child, and vice-versa. Hewlett-Packard Company - 1 - HP-UX Release 9.0: August 1992 The linux fork man page doesn't discuss it, but I did note they implement vfork() as an alias to fork(), suggesting that their fork and exec should be less efficient than ours? Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13:37:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 22660154EF for ; Mon, 5 Apr 1999 13:37:25 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id WAA23384; Mon, 5 Apr 1999 22:35:24 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id 44E7237; Mon, 5 Apr 1999 22:33:33 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 388FC1E11; Mon, 5 Apr 1999 22:33:33 +0200 (CEST) Date: Mon, 5 Apr 1999 22:33:33 +0200 (CEST) From: Blaz Zupan To: "David O'Brien" Cc: FreeBSD Current Subject: Re: C++ In-Reply-To: <19990405125931.F22022@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > configure:1333: c++ -o conftest conftest.C 1>&5 > > /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' > > /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' > Some people are getting these errors, but I'm not sure why. It comes Never mind, I fixed the problem by doing: cd /usr/src/gnu/lib/libstdc++ make obj make make install Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13:41:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id C46A614FCA for ; Mon, 5 Apr 1999 13:41:23 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.58.6]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1B41; Mon, 5 Apr 1999 22:39:24 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id WAA72681; Mon, 5 Apr 1999 22:39:28 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990405123111.D22022@nuxi.com> Date: Mon, 05 Apr 1999 22:39:28 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Re: World Breakage? Cc: current@FreeBSD.ORG, Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 David O'Brien wrote: >> > Also make sure that you have version 1.2 of >> > src/gnu/usr.sbin/cc/cc_drv/Makefile. > > You might also need to build libc manually. Looks like maybe you are > building parts of the tree manually (to fix the cpp problem), and > src/gnu/usr.sbin/cc/cc_drv/Makefile changed between your various > compiles. [root@daemon] (2) # pwd /usr/src/lib/libc [root@daemon] (3) # make rpcgen -C -h -o yp.h /usr/include/rpcsvc/yp.x /work/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:188 2: Internal compiler error in function main *** Error code 33 Uggh, ok. Let's try egcs first again: /usr/obj/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-tem p.o): In function `make_temp_file': choose-temp.o(.text+0x278): undefined reference to `mkstemps' *** Error code 1 Nice case of chicken <> egg =) Will try yer suggestion from the reply to John D. Polstra about adding mkstemp.c to the SRCS: just to get egcs working again. Will let ye know how I'd fare... Thanks for yer patience thus far =) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13:43:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C5A39154FC for ; Mon, 5 Apr 1999 13:43:32 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA22564; Mon, 5 Apr 1999 13:41:33 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405134133.E22383@nuxi.com> Date: Mon, 5 Apr 1999 13:41:33 -0700 From: "David O'Brien" To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: World Breakage? Reply-To: obrien@NUXI.com References: <19990405123111.D22022@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Apr 05, 1999 at 10:39:28PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Uggh, ok. Let's try egcs first again: > > /usr/obj/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-tem > p.o): In function `make_temp_file': > choose-temp.o(.text+0x278): undefined reference to `mkstemps' > *** Error code 1 > > Nice case of chicken <> egg =) > > Will try yer suggestion from the reply to John D. Polstra about adding > mkstemp.c to the SRCS: just to get egcs working again. You really need to do ``cd /usr/src/lib/libc'' and make from there. But I think you will have another chicken<>egg problem. The mkstemp.c in SRCS should over come is one. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 13:55:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 190B415523 for ; Mon, 5 Apr 1999 13:55:24 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.58.52]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4D75; Mon, 5 Apr 1999 22:53:26 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id WAA74817; Mon, 5 Apr 1999 22:53:30 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990405134133.E22383@nuxi.com> Date: Mon, 05 Apr 1999 22:53:29 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Re: World Breakage? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Apr-99 David O'Brien wrote: >> Uggh, ok. Let's try egcs first again: >> >> /usr/obj/work/FreeBSD/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose- >> tem >> p.o): In function `make_temp_file': >> choose-temp.o(.text+0x278): undefined reference to `mkstemps' >> *** Error code 1 >> >> Nice case of chicken <> egg =) >> >> Will try yer suggestion from the reply to John D. Polstra about adding >> mkstemp.c to the SRCS: just to get egcs working again. > > You really need to do ``cd /usr/src/lib/libc'' and make from there. But > I think you will have another chicken<>egg problem. The mkstemp.c in > SRCS should over come is one. That's what my error 33 before the egcs was about. So I am _forced_ to use the temporary hack, else I cannot compile either egcs nor libc =( Ah well, at least I gained some more insight into the whole makefile system, will make excellent documention for the PDP. And hurray, it worked! =) David, when we ever meet, mayhaps in one of the coming Dutch FreeBSD cons, remember to buy ye a few drinks =) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 14: 0: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id B3286154A5 for ; Mon, 5 Apr 1999 13:58:59 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id QAA43895; Mon, 5 Apr 1999 16:54:15 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Mon, 5 Apr 1999 16:54:15 +0000 (GMT) From: eagle To: Bob Bishop Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: make -jn ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, eagle wrote: > > > On Mon, 5 Apr 1999, Bob Bishop wrote: > > > World builds OK here now, kernel, bootblocks and all. Good job! > > > > Is `make -jn' safe yet? Could turn these test builds round a lot faster :-) > > > > I'm running a test build at -j3 now following the reccomended ncpus +1 > formula everything looks great so far. if it fails i'll let you know > > rob > > build completed successfully will experment some more rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 14:16:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 861721547D for ; Mon, 5 Apr 1999 14:16:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA17600; Mon, 5 Apr 1999 14:14:31 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 14:14:31 -0700 (PDT) From: Matthew Dillon Message-Id: <199904052114.OAA17600@apollo.backplane.com> To: Terry Lambert Cc: Robert Watson , current@FreeBSD.ORG Subject: Re: aio_read References: <199904051834.LAA11656@apollo.backplane.com> <37091909.B0257CB7@whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> design mistake. :> The only way to get your own descriptor seek offset is to :> open() the file again. : :After you said this, I found it so hard to believe that I had :to go look. : :All I can say is, well I'll be damned; you could knock me over :with a feather, and that doesn't happen often. Same thing happened to me 12 years ago when I first understood this particular brokedness. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 14:48:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 1FA5515162 for ; Mon, 5 Apr 1999 14:48:26 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id RAA19386; Mon, 5 Apr 1999 17:43:49 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Mon, 5 Apr 1999 17:43:48 +0000 (GMT) From: eagle To: Bob Bishop Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: make -jn ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, eagle wrote: > > On Mon, 5 Apr 1999, Bob Bishop wrote: > > > > > World builds OK here now, kernel, bootblocks and all. Good job! > > > > > > Is `make -jn' safe yet? Could turn these test builds round a lot faster :-) > > > > > > > I'm running a test build at -j3 now following the reccomended ncpus +1 > > formula everything looks great so far. if it fails i'll let you know > build completed successfully will experment some more > make -j anything greater than 3 fails rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 18:17: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 2192615063 for ; Mon, 5 Apr 1999 18:16:53 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id JAA25004; Tue, 6 Apr 1999 09:14:51 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA27863; Tue, 6 Apr 1999 09:14:50 +0800 Message-Id: <199904060114.JAA27863@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: wpaul@ctr.columbia.edu (Bill Paul) Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org Subject: Re: More on rl0 woes In-reply-to: Your message of "Sun, 04 Apr 1999 16:02:29 -0400." <199904042002.QAA14549@sirius.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Apr 1999 09:14:50 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I can't believe I'm getting so worked up because you cheap bastards > insist on buying the absolute worst network adapter in the world. Go > buy an ASIX card for crying out loud. They're cheap, and they actually > work worth a damn. Weeelll... I'm a cheap bastard & I actually expected it to work - not real fast, but work reliably anyway. I'm trying to convert my home network over to 100Mbs and the box this is going into is not a performance monster. > Now, as punishment for making me mad, I'm going to address Steven's > problem, and the rest of you can just lump it. > > There are things you should be checking when your problem happens. > What does ifconfig rl0 show you? Is the OACTIVE flag set? What does > netstat -in say? What does netstat -m say? I'll check that tonight. > You say 'traffic continues > normally.' This is very confusing: SHOW ME AN EXAMPLE OF WHAT YOU MEAN. OK - the "ls" of the directory remains hung, but I can still ping the box. It's as if NFS reckons it's sent the reply to the READDIR packet, but it never actually made its way out of the card. > When the NFS transfer stops, can you still ping the server host, > or do you have to interrupt the transfer and wait for a while > before you can communicate with the server again? Can you run tcpdump > on the client and observe what happens when the transfer stops? Is > the client still sending out read requests? Is the server replying > or not? I ran tcpdump on the server and observed READDIR packets being received, but no response being emitted. > Are the replies garbled? Is there a lot of other activity on > the network at the time? Can you initiate another (smaller) NFS > transfer when the first one wedges? I'll try this when I get home. Don't know enough about the contents of NFS packets yet to tell if it's garbled. > > You have to give me as much information as you can. I need to be > able to clearly identify the symptoms of the problem with out all > the 'oh my god it doesn't work and I tried this and this and this' > crap. Orright.. Just give me a little time. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 18:21:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 9438714E68 for ; Mon, 5 Apr 1999 18:21:45 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id JAA00031; Tue, 6 Apr 1999 09:19:39 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA27896; Tue, 6 Apr 1999 09:19:39 +0800 Message-Id: <199904060119.JAA27896@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Cc: shocking@bandicoot.prth.tensor.pgs.com, obrien@nuxi.com Subject: Re: egcs In-reply-to: Your message of "Mon, 05 Apr 1999 10:53:18 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Apr 1999 09:19:38 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> What will become of f77 which is in "src/gnu/usr.bin/cc/f77"? This >> seems to be a good time to decide what will happen with Fortran in the >> base FreeBSD system. > >VERY good question. I have no opinion in the matter, but will follow the >wishes of others (or Core, or committers, or who ever should make this >decision and who ever tells me which way to go). My vote is to include the sources for g77 that go with the egcs suite, but to have a knob in /etc/make.conf (BUILD_G77=yes) to control if they get built or not. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 18:30:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id D979515573 for ; Mon, 5 Apr 1999 18:30:30 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: from startide.ctr.columbia.edu (wpaul@startide.ctr.columbia.edu [128.59.64.52]) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id VAA23271; Mon, 5 Apr 1999 21:28:15 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Received: (wpaul@localhost) by startide.ctr.columbia.edu (8.9.1/8.6.4.788743) id VAA21701; Mon, 5 Apr 1999 21:28:13 -0400 (EDT) Message-Id: <199904060128.VAA21701@startide.ctr.columbia.edu> Subject: Patched RealTek driver -- please test To: current@freebsd.org Date: Mon, 5 Apr 1999 21:28:12 -0400 (EDT) Cc: bright@rush.net, mrt@notwork.org, shocking@prth.pgs.com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, today (and over part of the weekend) I ripped the RealTek driver apart and put it back together again, this time in a hopefully working form. The temporary patch version is at the following locations: http://www.freebsd.org/~wpaul/RealTek/test/2.2 source for FreeBSD 2.2.x http://www.freebsd.org/~wpaul/RealTek/test/3.0 source for FreeBSD 3.x/4.x If you've been having problems with RealTek 8139 cards, please try this version and let me know if it makes a differences. All of the main changes are in the transmit code. I also think I know why the transmitter was getting wedged. The sort answer: I'm a twit. The long answer: when ifinit() was changed so that it warned about ifq_maxlen not being set by the driver, I went in and set it to RL_TX_LIST_CNT - 1, which is approximately what I'd done for the other drivers. However the RealTek only has four transmit 'descriptors' which means the ifq_maxlen for the interface was being set to the ridiculously low value of 3. This causes transmissions of large packet sequences to quickly fill up the send queue. (For example, try doing a ping -s 8100 and see if it actually works. My bet is that it won't, because this will generate a series of six or seven frames in rapid succession, and after the first 3 or 4, the queue fills up.) In addition to fixing this, I also re-wrote rl_start() and rl_txeof() to hopefully be a little simpler and less brain damaged. I still need to fill in rl_txeoc() correctly, but once I know for sure that I've fixed all the major problems, I can probably do that in an hour or two. I experimented with this driver version using a FreeBSD 2.2.7 server and a FreeBSD 3.0 client (sorry, it's all I had) and I couldn't get NFS to hang. I also bombarded the server with a TCP stream from the client while the NFS test was running and it didn't lock up. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 18:38:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8AED2151F4 for ; Mon, 5 Apr 1999 18:38:41 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA42992 for ; Mon, 5 Apr 1999 21:36:17 -0400 (EDT) Date: Mon, 5 Apr 1999 21:36:16 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: EGCS breaks what(1) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, let me be a little clearer ;) What(1) on the kernel no longer works because previously, the char sccs[] = { '@', '(', '#', ')' }; char version[] = blahhhfoooooo; Was contiguous. However, nowadays, nice EGCS pads 4 bytes (WHY?!?!) between those. So it appears "@(#)\0\0\0\0FreeBSD....." in the binary. Of course, strings are null-terminated... :P I don't know why EGCS does this! Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 18:54:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 0F2C215515 for ; Mon, 5 Apr 1999 18:54:10 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA17097 for ; Mon, 5 Apr 1999 21:50:26 -0400 (EDT) Date: Mon, 5 Apr 1999 21:50:26 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: loader Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just finished a buildworld, and I'm not sure about the laoder binary. In my obj/usr/src/sys/boot/i386/loader directory, I have 3 files that might be loader: -rw-r--r-- 1 root wheel 135168 Apr 5 19:01 loader -rwxr-xr-x 1 root wheel 121672 Apr 5 19:01 loader.bin* -rwxr-xr-x 1 root wheel 259171 Apr 5 19:01 loader.sym* None of them are the size of my existing (gcc) /boot/loader: -r-xr-xr-x 1 root wheel 126976 Apr 4 17:10 loader* I use CFLAGS of -O -pipe. Can anyone tell me which of the above files gets installed as /boot/loader, and if (from the filesize) I have a good loader or not? This is the last thing worrying me about giong to egcs, and I'm just playing it very cautiously. Thanks. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 18:55: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (Postfix) with ESMTP id 7C42D15515 for ; Mon, 5 Apr 1999 18:55:02 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.3/8.9.3) with ESMTP id SAA00486 for ; Mon, 5 Apr 1999 18:53:05 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Date: Mon, 5 Apr 1999 18:53:05 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: current@freebsd.org Subject: Post-egcs switch console problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just cvsupped a few hours ago and rebuild world and the kernel. After the build, I noticed that my CD-ROM drives no longer worked, corrected the kernel config file to use wcd0 instead of acd0, and while I was at it, updated the bootloader config as per the instructions in /usr/src/sys/boot/README. Upon rebooting with the new kernel, I attempted to log in, but random text began appearing on the console, and then the machine ceased to be responsive. I power-cycled, logged in, started x, putzed around, switched back to the console, left for a while, and returned to find the console hosed again. It seemed to be accepting keystrokes, as I could produce audio, but the display would not change. Anyone else having this problem? Any clues as to what might be wrong? -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org daemon(n): 1. an attendant power or spirit : GENIUS 2. the cute little mascot of the FreeBSD operating system To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 18:59: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8CA151557C for ; Mon, 5 Apr 1999 18:58:58 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA84557; Mon, 5 Apr 1999 18:56:56 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 18:56:56 -0700 (PDT) From: Matthew Dillon Message-Id: <199904060156.SAA84557@apollo.backplane.com> To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: EGCS breaks what(1) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Okay, let me be a little clearer ;) What(1) on the kernel no longer works :because previously, the :char sccs[] = { '@', '(', '#', ')' }; :char version[] = blahhhfoooooo; :Was contiguous. However, nowadays, nice EGCS pads 4 bytes (WHY?!?!) between :those. So it appears "@(#)\0\0\0\0FreeBSD....." in the binary. Of course, :strings are null-terminated... :P I don't know why EGCS does this! : : Brian Feldman _ __ ___ ____ ___ ___ ___ : green@unixhelp.org _ __ ___ | _ ) __| \ : FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | : http://www.freebsd.org _ |___/___/___/ 'what' is broken. C does not impose any sort of address ordering restriction on globals or autos that are declared next to each other. While it is true that programmers regularly make assumptions in regards to the placement and alignment of fields in structures and the placement and alignment of arguments to procedures, it does not follow that programmers can make assumptions in regards to the placement and alignment of globals. EGCS is trying to optimize access to the array by aligning it, in order to reduce cache line burst-from-meory inefficiencies. It happens to break bad assumptions made in 'what'. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 18:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B68551556E for ; Mon, 5 Apr 1999 18:59:15 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA24467; Mon, 5 Apr 1999 18:57:15 -0700 (PDT) (envelope-from obrien) Message-ID: <19990405185715.A24435@nuxi.com> Date: Mon, 5 Apr 1999 18:57:15 -0700 From: "David O'Brien" To: Chris Costello , current@FreeBSD.ORG Subject: Re: libstdc++ is broken Reply-To: obrien@NUXI.com References: <199904050616.XAA01625@dei.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904050616.XAA01625@dei.calldei.com>; from Chris Costello on Sun, Apr 04, 1999 at 11:16:30PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Best described in gnu/10956, libstdc++ has strange undefined reference > errors when compiling anything C++. > > These are the errors: > > /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' > /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' I'm looking into this. But I haven't seen anything oblivious as to the problem. If you do a 2nd `build world' you will get a working C++ system. The problem is part of the the C++ bits get compiled by the old 2.7.2 compiler and some with EGCS. Everything installed in /usr/ that concerns C++ should have been compiled with EGCS. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 19:26:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from h24-64-221-247.gv.wave.shaw.ca (24.64.221.247.bc.wave.home.com [24.64.221.247]) by hub.freebsd.org (Postfix) with ESMTP id F413E14DB9 for ; Mon, 5 Apr 1999 19:26:24 -0700 (PDT) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.3/8.9.2) with ESMTP id TAA01546 for ; Mon, 5 Apr 1999 19:23:21 -0700 (PDT) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199904060223.TAA01546@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Re: libstdc++ is broken Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Apr 1999 19:23:21 -0700 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' > > /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' > > I'm looking into this. But I haven't seen anything oblivious as to the > problem. > > If you do a 2nd `build world' you will get a working C++ system. The > problem is part of the the C++ bits get compiled by the old 2.7.2 > compiler and some with EGCS. Everything installed in /usr/ that concerns > C++ should have been compiled with EGCS. agreed. Yesterday I was seeing the same thing, but today I did the first full egcs make world and it works fine now. Cool! -- we are but packets in the internet of life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 19:53:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 076FE15524 for ; Mon, 5 Apr 1999 19:53:33 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id TAA18776 for ; Mon, 5 Apr 1999 19:51:35 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id TAA78276 for current@freebsd.org; Mon, 5 Apr 1999 19:51:35 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 05 Apr 1999 19:51:34 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: cvsup4.freebsd.org is running behind Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It has been brought to my attention that cvsup4.freebsd.org has been lagging freefall significantly in recent days. I checked the logs and its hourly updates from freefall are failing every time. I've written to the maintainers, but haven't reached them yet. If you are trying to follow the fast pace in -current right now, I'd suggest that you avoid cvsup4 until it's fixed. I'll announce that when it happens. Sorry for the inconvenience. Stuff happens. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 20: 9:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (tele.visi.com [209.98.98.17]) by hub.freebsd.org (Postfix) with ESMTP id AE06314BDE for ; Mon, 5 Apr 1999 20:09:43 -0700 (PDT) (envelope-from mestery@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 7CB701F8DE; Mon, 5 Apr 1999 22:07:45 -0500 (CDT) Received: from localhost (mestery@localhost) by isis.visi.com (8.8.8/8.8.8) with SMTP id WAA21442; Mon, 5 Apr 1999 22:07:45 -0500 (CDT) X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs Date: Mon, 5 Apr 1999 22:07:45 -0500 (CDT) From: To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Patched RealTek driver -- please test In-Reply-To: <199904060128.VAA21701@startide.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bill, Just tried the new Realtek driver with 4.0, and it works MUCH better. I was seeing weird NFS transmit errors with UDP, and the ping you suggested below did not work with the old driver (it reported an out of buffer space message and didn't transmit any packets). With the new driver, the ping works, and nfsv3 with UDP works flawlessly. Also, ftping into my machine with the Realtek used to yield a max of 66K per second. Now I see closer to 2MB per second. Looks good so far! Thanks! -- Kyle Mestery StorageTek's Storage Networking Group Protect your right to privacy: www.freecrypto.org On Mon, 5 Apr 1999, Bill Paul wrote: > Okay, today (and over part of the weekend) I ripped the RealTek driver > apart and put it back together again, this time in a hopefully working > form. The temporary patch version is at the following locations: > > http://www.freebsd.org/~wpaul/RealTek/test/2.2 source for FreeBSD 2.2.x > http://www.freebsd.org/~wpaul/RealTek/test/3.0 source for FreeBSD 3.x/4.x > > If you've been having problems with RealTek 8139 cards, please try this > version and let me know if it makes a differences. All of the main > changes are in the transmit code. I also think I know why the transmitter > was getting wedged. The sort answer: I'm a twit. The long answer: > when ifinit() was changed so that it warned about ifq_maxlen not being set > by the driver, I went in and set it to RL_TX_LIST_CNT - 1, which is > approximately what I'd done for the other drivers. However the RealTek > only has four transmit 'descriptors' which means the ifq_maxlen for the > interface was being set to the ridiculously low value of 3. This causes > transmissions of large packet sequences to quickly fill up the send > queue. (For example, try doing a ping -s 8100 and see if it > actually works. My bet is that it won't, because this will generate a > series of six or seven frames in rapid succession, and after the first > 3 or 4, the queue fills up.) > > In addition to fixing this, I also re-wrote rl_start() and rl_txeof() > to hopefully be a little simpler and less brain damaged. I still need > to fill in rl_txeoc() correctly, but once I know for sure that I've > fixed all the major problems, I can probably do that in an hour or two. > > I experimented with this driver version using a FreeBSD 2.2.7 server and > a FreeBSD 3.0 client (sorry, it's all I had) and I couldn't get NFS > to hang. I also bombarded the server with a TCP stream from the client > while the NFS test was running and it didn't lock up. > > -Bill > > -- > ============================================================================= > -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu > Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research > Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City > ============================================================================= > "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." > ============================================================================= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 21:59:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 185811518C for ; Mon, 5 Apr 1999 21:59:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA01999; Mon, 5 Apr 1999 21:57:34 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 21:57:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199904060457.VAA01999@apollo.backplane.com> To: current@FreeBSD.ORG Subject: EGCS optimizations Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I played around with egcs a bit. I had blown away my original gcc install so I couldn't compare egcs w/ gcc, but I did mess around with egcs's optimization options. My conclusion: Don't bother with -mpentiumpro or -march=pentiumpro. Not only do they not result in better performance, -march=pentiumpro will not run on a K6-2. I dunno about a K6-3. -m does not change the assembly output at all. -march= does change the assembly output, but does not appear to result in any noticeable improvement in performance over not using -m at all. However, -Os does seem to produce slightly smaller binaries compared with -O2 and actually does not appear to cost performance on my PPro-200. before -r--r--r-- 1 root wheel 543096 Apr 5 21:29 /usr/lib/libc.so.3 -r-xr-xr-x 1 root wheel 1517032 Apr 5 20:37 /usr/libexec/cc1 -r-xr-xr-x 1 root wheel 1580456 Apr 5 20:37 /usr/libexec/cc1obj -r-xr-xr-x 1 root wheel 1928112 Apr 5 20:37 /usr/libexec/cc1plus after -r--r--r-- 1 root wheel 538872 Apr 5 21:35 /usr/lib/libc.so.3 -r-xr-xr-x 1 root wheel 1479240 Apr 5 21:47 /usr/libexec/cc1 -r-xr-xr-x 1 root wheel 1538376 Apr 5 21:47 /usr/libexec/cc1obj -r-xr-xr-x 1 root wheel 1876464 Apr 5 21:47 /usr/libexec/cc1plus Compiling up /usr/src/usr.sbin with egcs and libc compiled with: -O2 160 seconds -O2 -march=pentiumpro 162 seconds -Os 161 seconds Which leads me to believe that using -Os might be beneficial. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:16: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id CF43514C12 for ; Mon, 5 Apr 1999 22:16:05 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA04106; Mon, 5 Apr 1999 22:14:08 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 22:14:08 -0700 (PDT) From: Matthew Dillon Message-Id: <199904060514.WAA04106@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Re: EGCS optimizations Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm. interesting. My test kernel under GCC was considerably smaller then my test kernel under EGCS, even with -Os. text data bss dec hex filename 1287575 95512 122972 1506059 16fb0b kernel.gcc -O2 1326304 111628 125708 1563640 17dbf8 kernel.egcs -Os -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:19:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (sf3-74.ppp.wenet.net [206.15.84.74]) by hub.freebsd.org (Postfix) with ESMTP id 3967114C12 for ; Mon, 5 Apr 1999 22:19:31 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id WAA67952; Mon, 5 Apr 1999 22:17:36 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Mon, 5 Apr 1999 22:17:36 -0700 (PDT) From: Alex Zepeda To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: EGCS optimizations In-Reply-To: <199904060457.VAA01999@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, Matthew Dillon wrote: > My conclusion: Don't bother with -mpentiumpro or -march=pentiumpro. > Not only do they not result in better performance, -march=pentiumpro > will not run on a K6-2. I dunno about a K6-3. -m does not change > the assembly output at all. -march= does change the assembly output, > but does not appear to result in any noticeable improvement in performance > over not using -m at all. Totally informally, I replaced libc (compiled with -O2) with one compiled with -mpentiumpro and -O6, and compiling kdebase seemed to run a bit slower (GNU make took longer to traverse directories and egcs took a bit longer to run). > Which leads me to believe that using -Os might be beneficial. Have you tried anything beyond -O2? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:24:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 4EEAE14C12; Mon, 5 Apr 1999 22:24:09 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.16]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4213; Tue, 6 Apr 1999 07:22:10 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id HAA36386; Tue, 6 Apr 1999 07:22:13 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 06 Apr 1999 07:22:13 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Success, again! Cc: FreeBSD Current , Robert Garrett Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David, after my initial round of chicken<>egg, I got egcs and libc to build with the temporary hack in the Makefile of cc_drv. I then proceeded to do a make world with -Os -pipe, it took about 5 hours with no -j flags, but it succeeded nicely. Kernel built with -pipe -Os -g, lotsa warnings though, but that was expected. Nice job! --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:27:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 63C8915455 for ; Mon, 5 Apr 1999 22:27:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA04269; Mon, 5 Apr 1999 22:25:32 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 22:25:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199904060525.WAA04269@apollo.backplane.com> To: Alex Zepeda Cc: current@FreeBSD.ORG Subject: Re: EGCS optimizations References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Totally informally, I replaced libc (compiled with -O2) with one compiled :with -mpentiumpro and -O6, and compiling kdebase seemed to run a bit :slower (GNU make took longer to traverse directories and egcs took a bit :longer to run). : :> Which leads me to believe that using -Os might be beneficial. : :Have you tried anything beyond -O2? : :- alex There is nothing beyond -O2. Well, there's -O3, which tries to inline static functions, but that typically isn't beneficial because it really bloats up the code and subroutine calls on intel cpus are very fast. The only other optimization that might be useful is -fomit-frame-pointer, but it makes debugging impossible. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:33:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7F61315455; Mon, 5 Apr 1999 22:33:16 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA04305; Mon, 5 Apr 1999 22:31:07 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 22:31:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199904060531.WAA04305@apollo.backplane.com> To: Jeroen Ruigrok/Asmodai Cc: "David O'Brien" , FreeBSD Current , Robert Garrett Subject: Re: Success, again! References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :David, : :after my initial round of chicken<>egg, I got egcs and libc to build with :the temporary hack in the Makefile of cc_drv. : :I then proceeded to do a make world with -Os -pipe, it took about 5 hours :with no -j flags, but it succeeded nicely. : :Kernel built with -pipe -Os -g, lotsa warnings though, but that was :expected. : :Nice job! : :--- :Jeroen Ruigrok van der Werven :asmodai(at)wxs.nl The idea does not replace the work... :Network/Security Specialist :*BSD: Powered by Knowledge & Know-how Same here. I didn't have any chicken-an-egg problems, though, but I pulled the tree out of cvs as of early this afternoon after a bunch of fixes went in. I'm running a -Os EGCS kernel on my test box as we speak! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:40:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 8410714CF0 for ; Mon, 5 Apr 1999 22:40:35 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id PAA24791; Tue, 6 Apr 1999 15:42:12 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma024761; Tue, 6 Apr 99 15:41:57 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA05362 for ; Tue, 6 Apr 1999 15:38:07 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id PAA29409 for ; Tue, 6 Apr 1999 15:38:06 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA03323; Tue, 6 Apr 1999 15:38:04 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199904060538.PAA03323@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Re: EGCS breaks what(1) References: <199904060156.SAA84557@apollo.backplane.com> In-Reply-To: <199904060156.SAA84557@apollo.backplane.com> from Matthew Dillon at "Mon, 05 Apr 1999 18:56:56 -0700" Date: Tue, 06 Apr 1999 15:38:03 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 5th April 1999, Matthew Dillon wrote: >:char sccs[] = { '@', '(', '#', ')' }; >:char version[] = blahhhfoooooo; >:Was contiguous. > 'what' is broken. C does not impose any sort of address ordering > restriction on globals or autos that are declared next to each other. Well, it's really an abuse of 'what', and not anything wrong with 'what' ifself. It will continue to work fine doing the job it was designed to do. The NetBSD folks faced this problem some time ago, and I believe their solution was to duplicate the version information. So, version[] is the same as it used to be, and sccs[] is 4 bytes longer than version[] to hold a complete copy, and the @(#) prefix. This is then completely portable. Alternately, we could jimmy around with the current hack, and prefix it with 4 NULs, and see what happened. Sorry, I haven't tested this idea, as I've not yet made the EGCS jump. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:40:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (sf3-74.ppp.wenet.net [206.15.84.74]) by hub.freebsd.org (Postfix) with ESMTP id F3E661558E for ; Mon, 5 Apr 1999 22:40:46 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id WAA89458; Mon, 5 Apr 1999 22:38:47 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Mon, 5 Apr 1999 22:38:47 -0700 (PDT) From: Alex Zepeda To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: EGCS optimizations In-Reply-To: <199904060525.WAA04269@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, Matthew Dillon wrote: > There is nothing beyond -O2. Well, there's -O3, which tries to > inline static functions, but that typically isn't beneficial because > it really bloats up the code and subroutine calls on intel cpus are > very fast. Really? The pgcc web page (goof.com/pcg) lead me to believe that there were a few more optimizations turned on by -O5 && -O6.. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:44: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 198B114C12 for ; Mon, 5 Apr 1999 22:44:02 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id NAA03926; Tue, 6 Apr 1999 13:41:56 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id NAA29001; Tue, 6 Apr 1999 13:41:56 +0800 Message-Id: <199904060541.NAA29001@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: wpaul@ctr.columbia.edu (Bill Paul) Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org Subject: Re: Patched RealTek driver -- please test In-reply-to: Your message of "Mon, 05 Apr 1999 21:28:12 -0400." <199904060128.VAA21701@startide.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Apr 1999 13:41:56 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I nipped home over my lunch break & gave it a try - some progress, of a sort. My NFS problems have gone away (at least under light activity), but it now seems rather sensitive to sending lots of stuff. The symptoms observed are a hard hang of the whole machine, no response to pings or keyboard action. I cant even break into DDB. How I reproduced this is as follows - get the netpipe program off ports, then set up a receiver on the non-realtek machine as follows - NPtcp -s -r Then on the RealTek machine do this - NPtcp -s -t -h non-realtek-hostname -P After about 5 or so lines of throughput stats, it dies in the bum. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 22:54:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8E95D14C12 for ; Mon, 5 Apr 1999 22:54:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA04470; Mon, 5 Apr 1999 22:52:32 -0700 (PDT) (envelope-from dillon) Date: Mon, 5 Apr 1999 22:52:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199904060552.WAA04470@apollo.backplane.com> To: Alex Zepeda Cc: current@FreeBSD.ORG Subject: Re: EGCS optimizations References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Mon, 5 Apr 1999, Matthew Dillon wrote: : :> There is nothing beyond -O2. Well, there's -O3, which tries to :> inline static functions, but that typically isn't beneficial because :> it really bloats up the code and subroutine calls on intel cpus are :> very fast. : :Really? : :The pgcc web page (goof.com/pcg) lead me to believe that there were a few :more optimizations turned on by -O5 && -O6.. : :- alex pgcc != egcs. PGcc is a patchset on top of egcs and I suppose they might have added additinoal -O options, but egcs itself does not go beyond -O3. The PGcc faq indicates that they are slowly folding their stuff into egcs. Hopefully they've fixed the bugs :-). I have not tried compiling a kernel under pgcc but now that FreeBSD has moved to EGCS, it may actually work! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 23: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id B137414F99 for ; Mon, 5 Apr 1999 23:02:34 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.2/8.9.2) id BAA58221; Tue, 6 Apr 1999 01:00:31 -0500 (CDT) (envelope-from dan) Date: Tue, 6 Apr 1999 01:00:31 -0500 From: Dan Nelson To: Alex Zepeda Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: EGCS optimizations Message-ID: <19990406010031.A57657@dan.emsphone.com> References: <199904060457.VAA01999@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from "Alex Zepeda" on Mon Apr 5 22:17:36 GMT 1999 X-OS: FreeBSD 3.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Apr 05), Alex Zepeda said: > > Have you tried anything beyond -O2? > There is only -O3, which is just like -O2 except that it tries to inline all functions. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 23: 5:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 78EFE14C12 for ; Mon, 5 Apr 1999 23:05:32 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA18049; Tue, 6 Apr 1999 16:03:34 +1000 Date: Tue, 6 Apr 1999 16:03:34 +1000 From: Bruce Evans Message-Id: <199904060603.QAA18049@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: EGCS breaks what(1) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Alternately, we could jimmy around with the current hack, and prefix it >with 4 NULs, and see what happened. Sorry, I haven't tested this idea, as >I've not yet made the EGCS jump. egcs aligns long (>= about 28 bytes) strings to 32-byte boundaries. This adds up to 27 NULs to sccsid[] depending on the alignment of sccsidp[]. Aligning long strings to 32-byte boundaries is a pessimisation in kernels (because it makes poor locality poorer), especially on 486's where the cache line size is 16. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 23:14:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 12AFF15013 for ; Mon, 5 Apr 1999 23:10:59 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id PAA05117; Tue, 6 Apr 1999 15:39:11 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA04424; Tue, 6 Apr 1999 15:38:59 +0930 Date: Tue, 6 Apr 1999 15:38:59 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Matthew Dillon Cc: Alex Zepeda , current@freebsd.org Subject: Re: EGCS optimizations In-Reply-To: <199904060525.WAA04269@apollo.backplane.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, Matthew Dillon wrote: > There is nothing beyond -O2. Well, there's -O3, which tries to > inline static functions, but that typically isn't beneficial because > it really bloats up the code and subroutine calls on intel cpus are > very fast. When I tested this last year, -O3 on egcs produced a 10-15% slowdown for things like 'gzip'. OTOH, gcc's -O3 produced slightly faster code (as I recall). I /do/ however see noticeable (10-20%) speed improvements using -O2 -mpentium -march=pentium compared to -O2 -mno-486 on gcc. Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 23:21:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id D945C15013 for ; Mon, 5 Apr 1999 23:21:36 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: (wpaul@localhost) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) id CAA01436; Tue, 6 Apr 1999 02:19:28 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Message-Id: <199904060619.CAA01436@sirius.ctr.columbia.edu> Subject: Re: Patched RealTek driver -- please test To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Date: Tue, 6 Apr 1999 02:19:27 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: <199904060541.NAA29001@ariadne.tensor.pgs.com> from "Stephen Hocking-Senior Programmer PGS Tensor Perth" at Apr 6, 99 01:41:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Stephen Hocking-Senior Programmer PGS Tensor Perth had to walk into mine and say: > Well, I nipped home over my lunch break & gave it a try - some progress, of a > sort. My NFS problems have gone away (at least under light activity), but it > now seems rather sensitive to sending lots of stuff. The symptoms observed are > a hard hang of the whole machine, no response to pings or keyboard action. I > cant even break into DDB. How I reproduced this is as follows - get the > netpipe program off ports, then set up a receiver on the non-realtek machine > as follows - [chop] Sorry, I did traffic generation tests. I banged on it as hard as I could. I didn't have any problems with lockups. > NPtcp -s -r > > Then on the RealTek machine do this - > > NPtcp -s -t -h non-realtek-hostname -P > > After about 5 or so lines of throughput stats, it dies in the bum. Don't tell me 'after about 5 lines.' Tell me in minutes. Seconds. Hours. Weeks. How _LONG_ does it run before it locks up!! And what do the stats sat anyway! Alright, now see here: I put up yet another test version. This one has code in every conceivable place where the driver might get caught in an infinite loop (which is the only thing that might cause the system to appear to hang, short of executing a halt instruction). Same place (www.freebsd.org:/~wpaul/RealTek/test/3.0). Try _THIS_ version. Tell me if it locks up. Watch the console. Tell me if you see any messages (i.e. "rl0: looping in "). If you do, report them to me VERBATIM. (No paraphrasing, no inventing new messages which you think represent what you saw. VERBATIM. Or else.) If it still locks up and you don't see any errors, then the problem you're experiencing is either not related to the driver, or is related in some way that only manifiests itself on your hardware and which I will never be able to reproduce (since your hardware is over there, and I'm way over here). Maybe it's some peculiar kind of hardware fault. Maybe your PCI chipset blows. Maybe the RealTek blows when used in combination with your PCI chipset. Regardless, it's a condition which I can't reproduce on my own hardware, and if I can't reproduce the problem, I can't fix it. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 23:22:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.84.217]) by hub.freebsd.org (Postfix) with SMTP id 78D2715013 for ; Mon, 5 Apr 1999 23:22:44 -0700 (PDT) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id CAA05150; Tue, 6 Apr 1999 02:15:28 -0700 Date: Tue, 6 Apr 1999 02:15:28 -0700 From: Daniel Berlin To: Matthew Dillon Cc: Alex Zepeda , current@FreeBSD.ORG Subject: Re: EGCS optimizations In-Reply-To: <199904060525.WAA04269@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There is nothing beyond -O2. Well, there's -O3, which tries to > inline static functions, but that typically isn't beneficial because > it really bloats up the code and subroutine calls on intel cpus are > very fast. > > The only other optimization that might be useful is -fomit-frame-pointer, > but it makes debugging impossible. Incorrect. gdb 4.18 supports frame-pointerless debugging, and gcc will generate the proper DWARF2 info to support it. I've done it before many times. In fact, two of the test programs in the testsuite i use to test my BeOS port of GDB are compiled specifically *with* -fomit-frame-pointer to amke sure the DWARF2 reading and unwinding is working properly. I don't know if it's in the 1.1 branch, i know it's been in the HEAD branch for a while. on the gdb side, i remember seeing it sometime after february, and i've used it since march. Also, if you guys want to play the EGCS benchmark game, let me point you to the *surprise* BENCHMARKS, a link to which can be found on the egcs homepage (as well as test suite results). They are very well organized. Go submit some results so people have more to compare against. Also, -mpentiumpro will actually usually generate WORSE code for a pentium pro. -mpentium and -march=pentium do better at it. I would use -O2 with the 1.1 branch, and -O99 with the head branch. As the benchmarks note, -O6 *IS* faster than -O3 which *IS* faster than -O2. They usually use the higher -O levels to test out experimental optimizations. Another useful optimization is -funroll-loops, which does what you think it does. > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 5 23:53:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ACC.sim.net.ua (ACC.sim.net.ua [62.244.20.221]) by hub.freebsd.org (Postfix) with ESMTP id 218FF1544C for ; Mon, 5 Apr 1999 23:53:29 -0700 (PDT) (envelope-from pasha@sim.net.ua) Received: from GW.sim.net.ua (GW.sumy.net [62.244.20.220]) by ACC.sim.net.ua (8.9.3/8.8.4) with SMTP id JAA21242 for ; Tue, 6 Apr 1999 09:51:29 +0300 (EEST) Message-ID: <3709AEF1.446B9B3D@sim.net.ua> Date: Tue, 06 Apr 1999 06:51:29 +0000 From: Pavel Narozhniy X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: EGCS optimizations References: <199904060525.WAA04269@apollo.backplane.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :Totally informally, I replaced libc (compiled with -O2) with one compiled > :with -mpentiumpro and -O6, and compiling kdebase seemed to run a bit > :slower (GNU make took longer to traverse directories and egcs took a bit > :longer to run). > : > :> Which leads me to believe that using -Os might be beneficial. > : > :Have you tried anything beyond -O2? > : > :- alex > > There is nothing beyond -O2. Well, there's -O3, which tries to > inline static functions, but that typically isn't beneficial because > it really bloats up the code and subroutine calls on intel cpus are > very fast. > > The only other optimization that might be useful is -fomit-frame-pointer, > but it makes debugging impossible. I don't have oppurtunity to use CURRENT, but on 3.1-RELEASE and 2.2.8 -fomit-frame-pointer applied to kernel compilation leads to system crash. If you want to reproduce this, compile kernel with -O -fomit-frame-pointer, reboot, and try, for example, to build kernel with make -j 16 ;) > -Matt > Matthew Dillon > -- Pavel Narozhniy nic-hdl: PN395-RIPE http://www.sumy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 0:35:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id D2771152C5 for ; Tue, 6 Apr 1999 00:35:24 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async3-24.iptelecom.net.ua [212.42.68.215]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id KAA07323 for ; Tue, 6 Apr 1999 10:34:06 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA02787 for ; Tue, 6 Apr 1999 10:33:18 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3709B8ED.DEF790CA@altavista.net> Date: Tue, 06 Apr 1999 10:34:06 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Today CURRENT breakage Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following is error output from 'make -j6 buildworld' on sources cvsup'ed today: `gencheck.c' is up to date. `c-parse.in' is up to date. ===> cc_int make: don't know how to make insn-attrtab.c. Stop *** Error code 2   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 0:37:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 1831D1556C for ; Tue, 6 Apr 1999 00:37:29 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id IAA19832; Tue, 6 Apr 1999 08:35:31 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 6 Apr 1999 08:20:15 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 6 Apr 1999 08:20:13 +0000 To: eagle From: Bob Bishop Subject: Re: make -jn ? Cc: obrien@NUXI.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:54 pm +0000 5/4/99, eagle wrote: >On Mon, 5 Apr 1999, eagle wrote: > >> I'm running a test build at -j3 now following the reccomended ncpus +1 >> formula everything looks great so far. if it fails i'll let you know >> >> rob >> >> >build completed successfully will experment some more Hmm. -j3 still fails here, in the usual place. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 0:39:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AE861556C for ; Tue, 6 Apr 1999 00:39:28 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id IAA19851; Tue, 6 Apr 1999 08:37:27 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 6 Apr 1999 08:30:15 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: <199904060525.WAA04269@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 6 Apr 1999 08:30:13 +0000 To: Daniel Berlin From: Bob Bishop Subject: Re: EGCS optimizations Cc: Matthew Dillon , Alex Zepeda , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 2:15 am -0700 6/4/99, Daniel Berlin wrote: > >Also, -mpentiumpro will actually usually generate WORSE code for a pentium >pro. >-mpentium and -march=pentium do better at it. OK, but according to man cc: >NAME > gcc, g++ - GNU project C and C++ Compiler (egcs-1.1.2) [...] > -mpentium > Synonym for -mcpu=pentium [...] > Specifying -march=cpu > type implies -mcpu=cpu type. If this is right, then -mpentium is redundant in the presence of -march=pentium. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 0:44:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.84.217]) by hub.freebsd.org (Postfix) with SMTP id 3E0E815582 for ; Tue, 6 Apr 1999 00:44:45 -0700 (PDT) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id DAA05409; Tue, 6 Apr 1999 03:37:37 -0700 Date: Tue, 6 Apr 1999 03:37:37 -0700 From: Daniel Berlin To: Bob Bishop Cc: Daniel Berlin , Matthew Dillon , Alex Zepeda , current@FreeBSD.ORG Subject: Re: EGCS optimizations In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I always use both (because it's in my darn makefiles :P), but that sounds correct to me. If it said -mpentium implied -march=pentium, i'd say it's lying. most of the -m alone are worthless, it's the -march's that matter (note i say most to mean of the 4 architectures i've played with -m and -march on). On Tue, 6 Apr 1999, Bob Bishop wrote: > Hi, > > At 2:15 am -0700 6/4/99, Daniel Berlin wrote: > > > >Also, -mpentiumpro will actually usually generate WORSE code for a pentium > >pro. > >-mpentium and -march=pentium do better at it. > > OK, but according to man cc: > > >NAME > > gcc, g++ - GNU project C and C++ Compiler (egcs-1.1.2) > [...] > > -mpentium > > Synonym for -mcpu=pentium > [...] > > Specifying -march=cpu > > type implies -mcpu=cpu type. > > If this is right, then -mpentium is redundant in the presence of > -march=pentium. > > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 1:17:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from room101.wuppy.rcs.ru (shadow.rcs.ru [194.84.13.18]) by hub.freebsd.org (Postfix) with ESMTP id 26C0615573 for ; Tue, 6 Apr 1999 01:17:05 -0700 (PDT) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru (8.9.3.NOMIME/8.9.1) with ESMTP id MAA31997; Tue, 6 Apr 1999 12:14:18 +0400 (MSD) (envelope-from romanp@wuppy.rcs.ru) Date: Tue, 6 Apr 1999 12:14:17 +0400 (MSD) From: "Roman V. Palagin" To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: Today CURRENT breakage In-Reply-To: <3709B8ED.DEF790CA@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Apr 1999, Maxim Sobolev wrote: > Following is error output from 'make -j6 buildworld' on sources cvsup'ed > today: > > `gencheck.c' is up to date. > `c-parse.in' is up to date. > ===> cc_int > make: don't know how to make insn-attrtab.c. Stop > *** Error code 2 don't use -j x. >   > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE, RP40-RIPE | Network Administrator ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 1:27:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from volodya.prime.net.ua (volodya.prime.net.ua [195.64.229.17]) by hub.freebsd.org (Postfix) with ESMTP id 36C6815348; Tue, 6 Apr 1999 01:27:37 -0700 (PDT) (envelope-from andyo@prime.net.ua) Received: from prime.net.ua (localhost.prime.net.ua [127.0.0.1]) by volodya.prime.net.ua (8.8.8/8.8.8) with ESMTP id LAA00420; Tue, 6 Apr 1999 11:30:40 +0300 (EEST) (envelope-from andyo@prime.net.ua) Message-ID: <3709C62B.C6315A50@prime.net.ua> Date: Tue, 06 Apr 1999 11:30:37 +0300 From: "Andy V. Oleynik" Organization: M-Info X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: ru, uk, en MIME-Version: 1.0 To: andrea Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, tech-net@netbsd.org, freebsd-questions Subject: Re: arp. References: <011d01be7f56$a7fad060$2100a8c0@oma> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG andrea wrote: > I have to add a gateway to my net for experimental reasons. > Actually there are : a main-router that works as interface to the Internet, > and some hosts on my sub net. > > Internet-----MyRouter----MySubNet > > NOw i need to configure one host of MYSubNet to act as a gatway for the > secondary subnet. > Both the 1SubNet and 2 SubNEt share the same ip-range. > > Internet-----MyRouter----MySubNet-----My2SubNet As I understood U have smth like this : Internet-----MyRouter----MySubNet |----2ndRouter-----My2SubNet Then U have to cut My2SubNet from ur MySubNet and configure routes to appropriate subnets on appropriate hosts. As long as ur 2ndsubnet is part of ur mainsubnet the hosts from 2ndsubnet will be seen from internet & wise a versa. U may need to run DNS for reverse zone of ur My2SubNet > > > All the sub.net have to be seen from the Internet so I'll need to add a > route to MainRouter in order to route the Secondary Subnet. > The problem is that i cannot change configuration of the mainroute,so i > in fact this isnt big problem as soon as U have properly configured subnets:) . Correct me if I wrong. > wonder if is possible to configure the new gateway to do a sort of "proxy > arp" for my secondary Subnet. > But arp-tables are system-wide so if i change arp entry to cacth request on > PrimaryNet the 2subnet dont'works anymore. > Is possible to catch arp request only on a single subnet,without broke any > other subnet connected to the same host.? > thank you! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- WBW Andy V. Oleynik (When U work in virtual office U have good chance to obtain virtual money ö%-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 1:29: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 30175155B8 for ; Tue, 6 Apr 1999 01:28:59 -0700 (PDT) (envelope-from andreasd@ifi.uio.no) Received: from skidbladnir.ifi.uio.no (3034@skidbladnir.ifi.uio.no [129.240.64.76]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id KAA05777 for ; Tue, 6 Apr 1999 10:27:01 +0200 (MET DST) Received: (from andreasd@localhost) by skidbladnir.ifi.uio.no ; Tue, 6 Apr 1999 10:27:00 +0200 (MET DST) To: current@freebsd.org Subject: Re: WORM & CAM CD References: From: Andreas Dobloug User-Agent: Gnus/5.070066 (Pterodactyl Gnus v0.66) Emacs/20.3 Content-Transfer-Encoding: 8bit Date: 06 Apr 1999 10:27:00 +0200 In-Reply-To: Message-ID: Lines: 17 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kenneth D. Merry | > | > Has the worm driver been taken out of current? | > | Yes. You have to use cdrecord now for SCSI CD burners. | > cdrecord lacks support for a whole lot of CD-burners... | Oh really? The old Worm driver only supported HP/Philips and Plasmon | drives. cdrecord supports those drives, and many more. Sorry, didn't get a chance to test the worm driver. Thought it supported more. | What CD burner do you have that cdrecord doesn't support? Have you talked | to Joerg Schilling about it? I've got a Matsushita CW-7501. I'll send him a mail. -- Andreas Dobloug : email: andreasd@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 1:36:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D6B5D1516C for ; Tue, 6 Apr 1999 01:36:14 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id BAA25598; Tue, 6 Apr 1999 01:32:53 -0700 (PDT) (envelope-from obrien) Message-ID: <19990406013253.A25564@nuxi.com> Date: Tue, 6 Apr 1999 01:32:53 -0700 From: "David O'Brien" To: Bob Bishop , eagle Cc: current@FreeBSD.ORG Subject: Re: make -jn ? Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Bob Bishop on Tue, Apr 06, 1999 at 08:20:13AM +0000 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm. -j3 still fails here, in the usual place. I haven't even started looking at the -j problem. There is still some bootstrap problem with C++ (appears to be in libstdc++). Sorry. (of course patches gladly accepted :-) ) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 2: 2:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5EC7B14CBE for ; Tue, 6 Apr 1999 02:02:12 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA92357; Tue, 6 Apr 1999 10:01:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 6 Apr 1999 10:01:10 +0100 (BST) From: Doug Rabson To: "David O'Brien" Cc: current@freebsd.org Subject: Vtable thunks with egcs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm assuming that the default for egcs uses vtable thunks instead of offsets in the vtable to handle multiple inheritance. It occurred to me that since this changes the C++ calling convention, we have to bump the major version number of all c++ libraries, particularly the ones in ports. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 2: 9:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 8E220152C5; Tue, 6 Apr 1999 02:09:27 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id FAA26799; Tue, 6 Apr 1999 05:07:15 -0400 (EDT) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199904060907.FAA26799@cc942873-a.ewndsr1.nj.home.com> Subject: Re: arp. In-Reply-To: <3709C62B.C6315A50@prime.net.ua> from "Andy V. Oleynik" at "Apr 6, 99 11:30:37 am" To: andyo@prime.net.ua (Andy V. Oleynik) Date: Tue, 6 Apr 1999 05:07:15 -0400 (EDT) Cc: andrea.franceschini@linet.it, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, tech-net@netbsd.org, freebsd-questions@FreeBSD.ORG Reply-To: cjclark@home.com 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andy V. Oleynik wrote, [Charset koi8-r unsupported, filtering to ASCII...] > andrea wrote: > > > I have to add a gateway to my net for experimental reasons. > > Actually there are : a main-router that works as interface to the Internet, > > and some hosts on my sub net. > > > > Internet-----MyRouter----MySubNet > > > > NOw i need to configure one host of MYSubNet to act as a gatway for the > > secondary subnet. > > Both the 1SubNet and 2 SubNEt share the same ip-range. > > > > Internet-----MyRouter----MySubNet-----My2SubNet > > As I understood U have smth like this : > Internet-----MyRouter----MySubNet > |----2ndRouter-----My2SubNet > Then U have to cut My2SubNet from ur MySubNet and configure > routes to appropriate subnets on appropriate hosts. As long as ur 2ndsubnet > is part of ur mainsubnet the hosts from 2ndsubnet will be seen from internet > > & wise a versa. U may need to run DNS for reverse zone of ur My2SubNet DNS has nothing really to do with this problem. I believe the original poster is describing the following (this may be what the second poster meant to write, but proportional fonts, tab damage, or his character set wiped it out), Internet------PrimaryRouter------SubNet1 | SecondaryRouter-----SubNet2 > > > > > > All the sub.net have to be seen from the Internet so I'll need to add a > > route to MainRouter in order to route the Secondary Subnet. > > The problem is that i cannot change configuration of the mainroute,so i > > > > in fact this isnt big problem as soon as U have properly configured > subnets:) . Correct me if I wrong. This is a problem. You are wrong. But back to the original poster, why can you not change the configuration on the Primary Router[0]? If this is your network, and you want to be able to do things like this, you need to be able to change the Primary Router configuration. To the second poster, when the Primary Router receives a packet destined for a machine on SubNet1 or SubNet2, since the Router believes all of those machines are still on its LAN, it will try to use the MAC address (layer 2) to send the packet directly to the machine. However, now this machine has been moved behind the Secondary Router. The Secondary Router is not listening for other machines' packets at layer 2 (in a typical router setup), so it never gets the packet and never tries to forward it. It also would not respond to ARP calls by the Primary Router when it is looking for a machine on SubNet2. > > wonder if is possible to configure the new gateway to do a sort of "proxy > > arp" for my secondary Subnet. > > But arp-tables are system-wide so if i change arp entry to cacth request on > > PrimaryNet the 2subnet dont'works anymore. > > Is possible to catch arp request only on a single subnet,without broke any > > other subnet connected to the same host.? It is possible. But I am unaware of a tool to do this[1] (which does not mean there is not one). Might you be better off building a 'new' net behind your Secondary Router? Say using NAT and a 10.0.0 subnet? [0] All you need to do on the router is add a route to Secondary Router for IPs on SubNet2. All you need is the address for the Secondary Router and a subnet mask. [1] The Secondary Router would not actually be doing routing in this case. It's acting more like a switch. You did not really tell us why you are doing this. Would getting a switch be a better option for you? -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 2:16:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id 8CFE7151C4 for ; Tue, 6 Apr 1999 02:16:37 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 18296 invoked by uid 1001); 6 Apr 1999 09:14:38 -0000 To: dyson@iquest.net Cc: current@freebsd.org Subject: Re: SMP users (important) References: <199904031316.IAA45781@y.dyson.net.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 06 Apr 1999 12:14:37 +0300 In-Reply-To: "John S. Dyson"'s message of "3 Apr 1999 16:16:28 +0300" Message-ID: <86wvzqm7pe.fsf@not.oeno.com> Lines: 47 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John S. Dyson" writes: > I just wanted to "chime in" and say that the new patches are based > on a really good concept, and is much cleaner than the previous > method. Also, many RISC architectures can utilize this > method due to the availability of lots of general registers. > (One could go so far as to have the compiler reserve the > register.) Non-threaded user mode apps could optionally > use the reserved register, but for threaded user mode apps, > that reserved register could also be used as a per-thread > base pointer. Reserving an arbitrary register can make binary compatibility with other systems more difficult. On the i386 it isn't bad since only a few horribly machine-dependent programs might use %fs for anything. Something to look at as a precedent for other processors should be what commercial Unix systems on various non-i386 processors do. > I believe that NT does the above (%fs for X86, and general > register for Alpha.) On PPC, there are several local, Digital UNIX does not reserve a register. Based on a quick check it would seem to be using a call to PALcode to find the thread-specific data. Note that this is nothing like a system call, it's much faster (something like 10 clocks). > per-processor registers that one could use (but loading a > general register with that per processor register would be > needed for access.) Also, since the PPC has lots of registers, > one could? permanently reserve one of the general registers (r13?). I really don't like the idea of breaking the normal language conventions for any processor. For the i386, the use of segment registers is not relevant to C language conventions, but reserving a general register on any architecture should, IMHO, be avoided if at all possible. > All in all, this change has the potential for better context > switching time (and less memory/better performance for multi-threaded I believe that having meaningful values context-switched in segment registers can add context switch overhead. It shouldn't be significant, though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 2:56: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id 5BE911542C for ; Tue, 6 Apr 1999 02:56:05 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 19457 invoked by uid 1001); 6 Apr 1999 09:54:07 -0000 To: Matthew Dillon Cc: current@freebsd.org Subject: Re: aio_read References: <199904051834.LAA11656@apollo.backplane.com.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 06 Apr 1999 12:54:04 +0300 In-Reply-To: Matthew Dillon's message of "5 Apr 1999 21:34:54 +0300" Message-ID: <86vhfam5vn.fsf@not.oeno.com> Lines: 14 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > UNIX has been broken this way from day 1. It was a major design mistake. > The only way to get your own descriptor seek offset is to open() the > file again. It's not necessarily breakage. Not having any mechanism other than open to get your own seek offset is nasty, but sharing a seek offset can also be useful. File descriptors can't be "reverse-inherited", so in order to continue writing to the same redirected output file, a sequence of commands executed by a shell needs to be able to share the actual file offset. I believe this was the original reason for the behavior. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 4:27:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from volodya.prime.net.ua (volodya.prime.net.ua [195.64.229.17]) by hub.freebsd.org (Postfix) with ESMTP id B6EFD15067; Tue, 6 Apr 1999 04:26:22 -0700 (PDT) (envelope-from andyo@prime.net.ua) Received: from prime.net.ua (localhost.prime.net.ua [127.0.0.1]) by volodya.prime.net.ua (8.8.8/8.8.8) with ESMTP id OAA00643; Tue, 6 Apr 1999 14:29:32 +0300 (EEST) (envelope-from andyo@prime.net.ua) Message-ID: <3709F019.6B2D651C@prime.net.ua> Date: Tue, 06 Apr 1999 14:29:30 +0300 From: "Andy V. Oleynik" Organization: M-Info X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: ru, uk, en MIME-Version: 1.0 To: cjclark@home.com Cc: andrea.franceschini@linet.it, freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, tech-net@netbsd.org, freebsd-questions@FreeBSD.ORG Subject: Re: arp. References: <199904060907.FAA26799@cc942873-a.ewndsr1.nj.home.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Crist J. Clark" wrote: > Andy V. Oleynik wrote, > [Charset koi8-r unsupported, filtering to ASCII...] > > andrea wrote: > > > > > I have to add a gateway to my net for experimental reasons. > > > Actually there are : a main-router that works as interface to the Internet, > > > and some hosts on my sub net. > > > > > > Internet-----MyRouter----MySubNet > > > > > > NOw i need to configure one host of MYSubNet to act as a gatway for the > > > secondary subnet. > > > Both the 1SubNet and 2 SubNEt share the same ip-range. > > > > > > Internet-----MyRouter----MySubNet-----My2SubNet > > > > As I understood U have smth like this : > > Internet-----MyRouter----MySubNet > > |----2ndRouter-----My2SubNet > I mean 2ndrouter is on MySubNet, sorrey for unclearity:) > > Then U have to cut My2SubNet from ur MySubNet and configure > > routes to appropriate subnets on appropriate hosts. As long as ur 2ndsubnet > > is part of ur mainsubnet the hosts from 2ndsubnet will be seen from internet > > > > & wise a versa. U may need to run DNS for reverse zone of ur My2SubNet > > DNS has nothing really to do with this problem. I believe the original > I said "U may" not "U must". At least I run DNS for revzones of my subnets. > poster is describing the following (this may be what the second poster > meant to write, but proportional fonts, tab damage, or his character > set wiped it out), > > Internet------PrimaryRouter------SubNet1 > | > SecondaryRouter-----SubNet2 > > > > > > > > > > All the sub.net have to be seen from the Internet so I'll need to add a > > > route to MainRouter in order to route the Secondary Subnet. > > > The problem is that i cannot change configuration of the mainroute,so i > > > > > > > in fact this isnt big problem as soon as U have properly configured > > subnets:) . Correct me if I wrong. > > This is a problem. You are wrong. But back to the original poster, why Sorrey Crist, but there is no need to connect 2nd router to 1st. If U have to have 2nd subnet just insert 2nd NIC into 1st router and as I sad above configure ur subnets (with appropriate routes on router off cause & defaulterouter on hosts on subnets :). > > can you not change the configuration on the Primary Router[0]? If this is > your network, and you want to be able to do things like this, you need > to be able to change the Primary Router configuration. > > To the second poster, when the Primary Router receives a packet > destined for a machine on SubNet1 or SubNet2, since the Router > believes all of those machines are still on its LAN, it will try to > use the MAC address (layer 2) to send the packet directly to the > Is this true if 1strouter knows that a route to 2ndsubnet is throught 2ndrouter which is on same subnet as 1strouter? > machine. However, now this machine has been moved behind the Secondary > Router. The Secondary Router is not listening for other machines' > why not if it's configured as gateway to 2ndsnet? > packets at layer 2 (in a typical router setup), so it never gets the > > packet and never tries to forward it. It also would not respond to ARP > > calls by the Primary Router when it is looking for a machine on > SubNet2. > > > > > wonder if is possible to configure the new gateway to do a sort of "proxy > > > arp" for my secondary Subnet. > > > But arp-tables are system-wide so if i change arp entry to cacth request on > > > PrimaryNet the 2subnet dont'works anymore. > > > Is possible to catch arp request only on a single subnet,without broke any > > > other subnet connected to the same host.? > > It is possible. But I am unaware of a tool to do this[1] (which does not > mean there is not one). Might you be better off building a 'new' net > behind your Secondary Router? Say using NAT and a 10.0.0 subnet? > > [0] All you need to do on the router is add a route to Secondary > Router for IPs on SubNet2. All you need is the address for the > Secondary Router and a subnet mask. > > [1] The Secondary Router would not actually be doing routing in this > case. It's acting more like a switch. You did not really tell us why > you are doing this. Would getting a switch be a better option for you? > -- > Crist J. Clark cjclark@home.com -- WBW Andy V. Oleynik (When U work in virtual office U have good chance to obtain virtual money ö%-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 4:38: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A7AC15067 for ; Tue, 6 Apr 1999 04:38:01 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id TAA21669; Tue, 6 Apr 1999 19:35:59 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id TAA29847; Tue, 6 Apr 1999 19:35:59 +0800 Message-Id: <199904061135.TAA29847@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: wpaul@ctr.columbia.edu (Bill Paul) Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org Subject: Re: Patched RealTek driver -- please test In-reply-to: Your message of "Tue, 06 Apr 1999 02:19:27 -0400." <199904060619.CAA01436@sirius.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Apr 1999 19:35:58 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK - I've banged on the new version with extra debug messages and it still locks up, but without any messages! I can only conclude that the 486MB BIOS is iffy. I haven't tried any other slots in the MB, but have tried various PCI settings, all to no avail. I have swapped the de0 and the rl0 between machines, and the rl0 is happy in it's new home - hasn't fallen over, although it's netpipe performance sucks with very small packets. I think we can write this one off as a faulty PCI implementation on the 486 motherboard. Thanks for your patience & time. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 5:43:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9153E1516E; Tue, 6 Apr 1999 05:43:20 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id FAA26374; Tue, 6 Apr 1999 05:41:17 -0700 (PDT) (envelope-from obrien) Message-ID: <19990406054117.A26361@nuxi.com> Date: Tue, 6 Apr 1999 05:41:17 -0700 From: "David O'Brien" To: Doug Rabson Cc: current@freebsd.org, ports@freebsd.org Subject: Re: Vtable thunks with egcs Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug Rabson on Tue, Apr 06, 1999 at 10:01:10AM +0100 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm assuming that the default for egcs uses vtable thunks instead of > offsets in the vtable to handle multiple inheritance. At the moment, yes. > It occurred to me that since this changes the C++ calling convention, > we have to bump the major version number of all c++ libraries, > particularly the ones in ports. Not only that, but the differences in exceptions, rtti, etc... it is well known that you can't even use C++ libs compiled with g++ 2.8.{0,1} with EGCS. Guess Steve is in for some fun when he sees just how broken Ports are with EGCS. ;-) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) P.S. There is a problem with bootstraping right now that causes something not to be compiled by EGCS that needs to be. I'm working on this right now... so we might not want to change any ports just yet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 6:29:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.sitaranetworks.com (apollo.sitaranetworks.com [199.103.141.105]) by hub.freebsd.org (Postfix) with SMTP id 92D6B1516E for ; Tue, 6 Apr 1999 06:29:33 -0700 (PDT) (envelope-from loverso@sitara.net) Received: from sitara.net (jamaica.sitaranetworks.com [199.103.141.147]) by apollo.sitaranetworks.com (8.9.1a/8.9.1) with ESMTP id JAA12276; Tue, 6 Apr 1999 09:27:28 -0400 (EDT) Message-ID: <370A0B4D.2A710364@sitara.net> Date: Tue, 06 Apr 1999 09:25:33 -0400 From: "John R. LoVerso" Reply-To: loverso@sitaranetworks.com Organization: Sitara Networks, http://surf.to/loverso/ X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon , current@FreeBSD.ORG Subject: Re: EGCS breaks what(1) References: <199904060156.SAA84557@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 'what' is broken. C does not impose any sort of address ordering > restriction on globals or autos that are declared next to each other. Right, except that 'what' isn't broken. It is vers.c (and conf/newvers.sh) that is broken, believing that the two variables will be allocating in contiguous memory. Changing newvers.sh to generate char sccs[] = "@(" "#)" "FreeBSD ..."; char version = "FreeBSD ..."; will make "what" on the kernel work again, at the expense of about 100 duplicated bytes. The real question is whether the extreme alignment and padding used by EGCS can be turned off, especially for 486s. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 6:50:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E9B00150A2 for ; Tue, 6 Apr 1999 06:50:38 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10UWCt-0005ra-00; Tue, 6 Apr 1999 15:47:59 +0200 From: Sheldon Hearn To: Scott Michel Cc: current@freebsd.org Subject: Re: YP/NIS and passwd weirdness In-reply-to: Your message of "Fri, 02 Apr 1999 17:26:15 PST." <199904030126.RAA62422@mordred.cs.ucla.edu> Date: Tue, 06 Apr 1999 15:47:59 +0200 Message-ID: <22541.923406479@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 02 Apr 1999 17:26:15 PST, Scott Michel wrote: > Removing the "*" makes things work again, but the security check > wails about a user w/o a password. The entries should not use "*" in the first place. With regard to the security check, see PR 9639 at: http://www.freebsd.org/cgi/query-pr.cgi?pr=9639 While no diffs are supplied with the PR, you could try the kludge below. There's a very good reason why this 5-second abortion isn't attached to the PR -- it's ugly. But it sounds like you care, so knock yourself out. :-) Ciao, Sheldon. Index: security =================================================================== RCS file: /home/ncvs/src/etc/security,v retrieving revision 1.29 diff -u -d -r1.29 security --- security 1999/01/10 11:18:59 1.29 +++ security 1999/04/06 13:27:58 @@ -54,7 +54,7 @@ separator echo "checking for passwordless accounts:" -awk -F: '$2=="" {print $0}' /etc/master.passwd +grep -v '^\+' /etc/master.passwd | awk -F: '$2=="" {print $0}' # show denied packets if ipfw -a l 2>/dev/null | egrep "deny|reset|unreach" > $TMP; then To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 6:56:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id EBA11156E7 for ; Tue, 6 Apr 1999 06:56:23 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id XAA27397; Tue, 6 Apr 1999 23:58:07 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma027389; Tue, 6 Apr 99 23:57:55 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id XAA24362 for ; Tue, 6 Apr 1999 23:53:58 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id XAA25053 for ; Tue, 6 Apr 1999 23:53:58 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id XAA19881; Tue, 6 Apr 1999 23:53:56 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199904061353.XAA19881@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Slightly wonky auto memory probe + fix Date: Tue, 06 Apr 1999 23:53:56 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I posted this to -current because the technology is the same in -current even though this box will never run -current. Bear with me.] We've just got a new Dell PowerEdge (very nice) with 512MB of ram. By default, 3.1-stable sees only 64MB. Looking carefully, it sees 8KB less than 64MB, so it doesn't probe for the rest. I applied this patch, which fiddles the "Hmm got 64MB so probe for the rest" heuristic. With this patch, it found all 512MB, to the exact byte. Unfortunately, it kinda changes it from a "heuristic" to a "hack". :-( --- machdep.c Fri Feb 19 15:31:36 1999 +++ /tmp/sgm/machdep.c Tue Apr 6 23:40:36 1999 @@ -1428,7 +1428,7 @@ * the MAXMEM option or the npx0 "msize", then don't do the speculative * memory probe. */ - if (Maxmem >= 0x4000) + if (Maxmem >= 0x3f00) speculative_mprobe = TRUE; else speculative_mprobe = FALSE; @@ -1538,7 +1538,7 @@ if (phys_avail[pa_indx] == target_page) { phys_avail[pa_indx] += PAGE_SIZE; if (speculative_mprobe == TRUE && - phys_avail[pa_indx] >= (64*1024*1024)) + phys_avail[pa_indx] >= (63*1024*1024)) Maxmem++; } else { pa_indx++; Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 7: 2:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A29A0151AA for ; Tue, 6 Apr 1999 07:02:15 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10UWOP-0005vp-00; Tue, 6 Apr 1999 15:59:53 +0200 From: Sheldon Hearn To: George Cox Cc: freebsd-current@freebsd.org Subject: Re: cvsupped libgcc grief In-reply-to: Your message of "Sun, 04 Apr 1999 12:48:04 GMT." <19990404124804.A35193@extremis.demon.co.uk> Date: Tue, 06 Apr 1999 15:59:53 +0200 Message-ID: <22804.923407193@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 04 Apr 1999 12:48:04 GMT, George Cox wrote: > cc: Internal compiler error: program cc1 got fatal signal 11 [...] > FreeBSD-CURRENT -- Because I'm worth it. How did you find out about CURRENT without finding out about the FAQ? Please read section 4 of the FreeBSD FAQ, available online at http://www.freebsd.org/FAQ/FAQ.html, paying particular attention to the question "My programs occasionally die with ``Signal 11'' errors.". Then see if you get the same error in the same place consistently with a clean obj tree. My money's on dud hardware. :-( Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 7:49:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 55F0115662 for ; Tue, 6 Apr 1999 07:49:44 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id IAA28917; Tue, 6 Apr 1999 08:47:42 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199904061447.IAA28917@panzer.plutotech.com> Subject: Re: WORM & CAM CD In-Reply-To: from Andreas Dobloug at "Apr 6, 1999 10:27: 0 am" To: andreasd@ifi.uio.no (Andreas Dobloug) Date: Tue, 6 Apr 1999 08:47:42 -0600 (MDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Dobloug wrote... > * Kenneth D. Merry > | > | > Has the worm driver been taken out of current? > | > | Yes. You have to use cdrecord now for SCSI CD burners. > | > cdrecord lacks support for a whole lot of CD-burners... > | Oh really? The old Worm driver only supported HP/Philips and Plasmon > | drives. cdrecord supports those drives, and many more. > > Sorry, didn't get a chance to test the worm driver. Thought it > supported more. > > | What CD burner do you have that cdrecord doesn't support? Have you talked > | to Joerg Schilling about it? > > I've got a Matsushita CW-7501. I'll send him a mail. My guess is that cdrecord won't support it. See: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdr-unsup.html And remember that Matsushita == Panasonic. From what I can tell, Plasmon made a clone of the CW-7501, but the worm driver never supported that model anyway. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 7:50:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 93F261510C; Tue, 6 Apr 1999 07:47:11 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 6 Apr 99 15:44:52 +0100 (BST) To: freebsd-current@freebsd.org, grog@freebsd.org Subject: New SiS 5591 ide chipset support. X-Request-Do: Date: Tue, 06 Apr 1999 15:44:51 +0100 From: David Malone Message-ID: <9904061544.aa29995@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having trouble with a kernel built from this mornings make world. It seems to be related to the new SiS 5591 ide chipset support. It gets as far as the automatic reboot in progress and then says: wd0: interrupt timeout (status 50 error 0) wd0: wdtimeout() DMA status 0 wd0: interrupt timeout (status 50 error 1) wd0: wdtimeout() DMA status 0 wd0: interrupt timeout (status 50 error 1) wd0: wdtimeout() DMA status 0 wd0: interrupt timeout (status 50 error 1) wd0: wdtimeout() DMA status 0 . . . The first thing is that I guess the should be , the second is that it seems to sit there doing that for longer than I was willing to wait (it eventually prints a message saying that it presumes it is a laptop and shouldn't print any more of these messages). Backing out the last change to ide_pci.c seems to fix the problem. I've lots of flags turned on in the kernel config file (0xa0ffa0ff), the old kernel complains a little but works fine, the new kernel spots that it is a SiS 5591, but grinds to a halt. If it helps any, the older working kernel prints one timeout message when booting after the bad kernel has been booted, and my root filesystem is actually on wd1. Is my drive/controller not up to the flags I've set, or is this a problem with the new chipset support? Relivent quotes from boot messages/kernel config file below. All the messages from the new kernel are copied by hand, so there will be mistakes. David. In config file: --------------- controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff The old kernel says: -------------------- ide_pci0: rev 0xc1 int a irq 14 on pci0.1.1 ide_pci: generic_dmainit 01f0:0: warning, IDE controller timing not set The new kernel reports this: ---------------------------- ide_pci0: rev 0xc1 int a irq 14 on pci0.1.1 New kernel with -v: ------------------- SiS 5591 dmainit: primary drive 0 setting ultra DMA mode 2 wd0: wdsetmode() setting transfer mode to 42 SiS 5591 status: CRTC 12 PCICLK, CATC12 PCICLK, applies to all IDE drives SiS 5591 status: burst cycles enabeled, fast post write control enabeled SiS 5591 status: primary drive 0 DRTC 1 PCICLK, DATC 3 PCICLK SiS 5591 status: primary drive 0 Ultra DMA enabeled, 1PCICLK data out SiS 5591 status: primary drive 0 postwrite enabeled, prefetch enabeled prefetch count is 512 SiS 5591 status: primary drive 0 has been configured for DMA wdc0: unit 0 (wd0) , DMA, 32-bit, multi-block-16 wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmaword = 0007, apio = 0003, vdma = 0407 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 7:56:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 1EA1315092 for ; Tue, 6 Apr 1999 07:56:25 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id KAA50310 for ; Tue, 6 Apr 1999 10:54:26 -0400 (EDT) Date: Tue, 6 Apr 1999 10:54:25 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: panic: vm_page_bits: illegal base/size 4096/512 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This occurs when I'm copying from a floppy (MS-DOS) to my home dir which is on an FFS file system. Any ideas? Reproduced of course. Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ cript started on Tue Apr 6 10:34:54 1999 {"/home/crash"}# gdb -k kernel.0 vmcore.0 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 2887680 initial pcb at 23f440 panicstr: vm_page_bits: illegal base/size 4096/512 panic messages: --- panic: vm_page_bits: illegal base/size 4096/512 syncing disks... 21 19 14 11 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 giving up dumping to dev 20001, offset 8192 dump 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xc01378a5 in panic () at ../../kern/kern_shutdown.c:448 #2 0xc019f491 in vm_page_bits (base=4096, size=512) at ../../vm/vm_page.c:1449 #3 0xc01a1cc8 in vnode_pager_input_smlfs (object=0xc6f55e0c, m=0xc054f6a0) at ../../vm/vnode_pager.c:401 #4 0xc01a219f in vnode_pager_generic_getpages (vp=0xc6fc5bc0, m=0xc6e8ccf0, bytecount=4096, reqpage=0) at ../../vm/vnode_pager.c:625 #5 0xc0f4b183 in ?? () #6 0xc01a201a in vnode_pager_getpages (object=0xc6f55e0c, m=0xc6e8ccf0, count=1, reqpage=0) at vnode_if.h:1067 #7 0xc019633f in vm_fault (map=0xc6efeac0, vaddr=671449088, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_pager.h:120 #8 0xc01cb10c in trap_pfault (frame=0xc6e8cd98, usermode=0, eva=671449088) at ../../i386/i386/trap.c:817 #9 0xc01cade7 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -1025695744, tf_esi = 671449088, tf_ebp = -957821440, tf_isp = -957821504, tf_ebx = 8192, tf_edx = 671453184, tf_ecx = 1024, tf_eax = -957829120, tf_trapno = 12, tf_err = 0, tf_eip = -1071867086, tf_cs = 8, tf_eflags = 66070, tf_esp = -957821184, tf_ss = -957821192}) at ../../i386/i386/trap.c:438 #10 0xc01c9b32 in slow_copyin () #11 0xc018d5e8 in ffs_write (ap=0xc6e8ceb8) at ../../ufs/ufs/ufs_readwrite.c:468 #12 0xc01635f9 in vn_write (fp=0xc0e8cac0, uio=0xc6e8cf00, cred=0xc0e32580, flags=0) at vnode_if.h:331 #13 0xc0142abc in dofilewrite (p=0xc66e2d60, fp=0xc0e8cac0, fd=4, buf=0x28057000, nbyte=13180, offset=0xffffffffffffffff, flags=0) at ../../kern/sys_generic.c:363 #14 0xc01429cb in write (p=0xc66e2d60, uap=0xc6e8cf84) ---Type to continue, or q to quit--- at ../../kern/sys_generic.c:298 #15 0xc01cb70e in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = 671444992, tf_esi = 671444992, tf_ebp = -1077946852, tf_isp = -957820972, tf_ebx = 13180, tf_edx = -1, tf_ecx = 4, tf_eax = 4, tf_trapno = 0, tf_err = 2, tf_eip = 134522044, tf_cs = 31, tf_eflags = 531, tf_esp = -1077946992, tf_ss = 47}) at ../../i386/i386/trap.c:1101 #16 0xc01bec4c in Xint0x80_syscall () #17 0x80488a6 in ?? () #18 0x804849c in ?? () #19 0x80480e9 in ?? () (kgdb) quit {"/home/crash"}# ^D Script done on Tue Apr 6 10:35:07 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 8: 0:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 4CC5314C33 for ; Tue, 6 Apr 1999 08:00:34 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id LAA58486 for ; Tue, 6 Apr 1999 11:00:49 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Tue, 6 Apr 1999 11:00:49 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: I still get a problem with make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This time, I resupped at about 3 this morning (Eastern Standard Time) and typed "make -DNOGAMES world" and now I get an error when it compiles dd, and it quits compiling after that. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 8: 9:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id D598014C28 for ; Tue, 6 Apr 1999 08:09:47 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: from startide.ctr.columbia.edu (wpaul@startide.ctr.columbia.edu [128.59.64.52]) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id LAA16000; Tue, 6 Apr 1999 11:07:48 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Received: (wpaul@localhost) by startide.ctr.columbia.edu (8.9.1/8.6.4.788743) id LAA23216; Tue, 6 Apr 1999 11:07:46 -0400 (EDT) Message-Id: <199904061507.LAA23216@startide.ctr.columbia.edu> Subject: Re: Patched RealTek driver -- please test To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Date: Tue, 6 Apr 1999 11:07:46 -0400 (EDT) Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org In-Reply-To: <199904061135.TAA29847@ariadne.tensor.pgs.com> from "Stephen Hocking-Senior Programmer PGS Tensor Perth" at Apr 6, 99 07:35:58 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Stephen Hocking-Senior Programmer PGS Tensor Perth had to walk into mine and say: > OK - I've banged on the new version with extra debug messages and it still > locks up, but without any messages! Grr. > I can only conclude that the 486MB BIOS is > iffy. I haven't tried any other slots in the MB, but have tried various PCI > settings, all to no avail. I have swapped the de0 and the rl0 between > machines, and the rl0 is happy in it's new home - hasn't fallen over, although > it's netpipe performance sucks with very small packets. I think we can write > this one off as a faulty PCI implementation on the 486 motherboard. Thanks for > your patience & time. I have one more thing you can try for me (I hope it's not too much trouble to put the NIC back where it was). This latest test version has a small change to rl_start() which modifies the transmit behavior: instead of trying to fill up as many transmit 'descriptors' as possible, it should never be possible now to have more than one transmission in progress at any one time. That is, instead of trying to fill up all four TX 'descriptors' and issue four transmissions in rapid succession and then waiting to clean up the buffers later, it issues a single transmission, waits for completion, then issues another transmission, waits for completion, and so on. This will probably worsen performance at 100Mbps, but it would be interesting to see if it fixes your problem. Please try it and let me know what happens. (I left the loop detection code in place just for giggles.) -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 8:20:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EEC7914C8A for ; Tue, 6 Apr 1999 08:20:14 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id IAA26799; Tue, 6 Apr 1999 08:18:14 -0700 (PDT) (envelope-from obrien) Message-ID: <19990406081814.A26784@nuxi.com> Date: Tue, 6 Apr 1999 08:18:14 -0700 From: "David O'Brien" To: loverso@sitaranetworks.com, current@FreeBSD.ORG Subject: Re: EGCS breaks what(1) Reply-To: obrien@NUXI.com References: <199904060156.SAA84557@apollo.backplane.com> <370A0B4D.2A710364@sitara.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <370A0B4D.2A710364@sitara.net>; from John R. LoVerso on Tue, Apr 06, 1999 at 09:25:33AM -0400 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The real question is whether the extreme alignment and padding used by > EGCS can be turned off, especially for 486s. Considering it... probably based on -m486. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 8:36:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60]) by hub.freebsd.org (Postfix) with ESMTP id 8F8F515077 for ; Tue, 6 Apr 1999 08:36:09 -0700 (PDT) (envelope-from wpaul@ctr.columbia.edu) Received: from startide.ctr.columbia.edu (wpaul@startide.ctr.columbia.edu [128.59.64.52]) by sirius.ctr.columbia.edu (8.9.1/8.6.4.287) with ESMTP id LAA17177; Tue, 6 Apr 1999 11:34:10 -0400 (EDT) From: wpaul@ctr.columbia.edu (Bill Paul) Received: (wpaul@localhost) by startide.ctr.columbia.edu (8.9.1/8.6.4.788743) id LAA23282; Tue, 6 Apr 1999 11:34:09 -0400 (EDT) Message-Id: <199904061534.LAA23282@startide.ctr.columbia.edu> Subject: Re: Patched RealTek driver -- please test To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Date: Tue, 6 Apr 1999 11:34:09 -0400 (EDT) Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org In-Reply-To: <199904061135.TAA29847@ariadne.tensor.pgs.com> from "Stephen Hocking-Senior Programmer PGS Tensor Perth" at Apr 6, 99 07:35:58 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whoops... I just noticed I made a small boo-boo in that last patch, which I just fixed. When downloading, make sure you get the version of if_rl.c with the following ID strings: for 3.0: $Id: if_rl.c,v 1.28 1999/04/06 15:29:01 wpaul Exp $ for 2.2: $Id: if_rl.c,v 1.17 1999/04/06 15:29:26 wpaul Exp $ Sorry about that. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "Mulder, toads just fell from the sky!" "I guess their parachutes didn't open." ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 8:49:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 022A215028 for ; Tue, 6 Apr 1999 08:49:22 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 21032 invoked from network); 6 Apr 1999 15:47:22 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 6 Apr 1999 15:47:22 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id KAA28401; Tue, 6 Apr 1999 10:47:21 -0500 (EST) From: "John S. Dyson" Message-Id: <199904061547.KAA28401@dyson.iquest.net> Subject: Re: SMP users (important) In-Reply-To: <86wvzqm7pe.fsf@not.oeno.com> from Ville-Pertti Keinonen at "Apr 6, 99 12:14:37 pm" To: will@iki.fi (Ville-Pertti Keinonen) Date: Tue, 6 Apr 1999 10:47:21 -0500 (EST) Cc: dyson@iquest.net, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > per-processor registers that one could use (but loading a > > general register with that per processor register would be > > needed for access.) Also, since the PPC has lots of registers, > > one could? permanently reserve one of the general registers (r13?). > > I really don't like the idea of breaking the normal language > conventions for any processor. For the i386, the use of segment > registers is not relevant to C language conventions, but reserving a > general register on any architecture should, IMHO, be avoided if at > all possible. > I believe that SYSV might do it. > > I believe that having meaningful values context-switched in segment > registers can add context switch overhead. It shouldn't be > significant, though. > It is probably *much* cheaper than the VM approaches. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 10: 3:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5AEB815097 for ; Tue, 6 Apr 1999 10:03:56 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA09326; Tue, 6 Apr 1999 10:01:36 -0700 (PDT) (envelope-from dillon) Date: Tue, 6 Apr 1999 10:01:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199904061701.KAA09326@apollo.backplane.com> To: Ville-Pertti Keinonen Cc: current@freebsd.org Subject: Re: aio_read References: <199904051834.LAA11656@apollo.backplane.com.newsgate.clinet.fi> <86vhfam5vn.fsf@not.oeno.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : :Matthew Dillon writes: : :> UNIX has been broken this way from day 1. It was a major design mistake. :> The only way to get your own descriptor seek offset is to open() the :> file again. : :It's not necessarily breakage. Not having any mechanism other than :open to get your own seek offset is nasty, but sharing a seek offset :can also be useful. File descriptors can't be "reverse-inherited", so :in order to continue writing to the same redirected output file, a :sequence of commands executed by a shell needs to be able to share the :actual file offset. I believe this was the original reason for the :behavior. If it's a redirected output file you simply make it O_APPEND, at which point the seek offset in the descriptor becomes irrelevant. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 12:22:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 7BE58156EF for ; Tue, 6 Apr 1999 12:22:32 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id VAA13314 for current@FreeBSD.ORG; Tue, 6 Apr 1999 21:20:34 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B92D7884E; Tue, 6 Apr 1999 20:47:18 +0200 (CEST) Date: Tue, 6 Apr 1999 20:47:18 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: make -jn ? Message-ID: <19990406204718.A53880@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Bob Bishop on Tue, Apr 06, 1999 at 08:20:13AM +0000 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5173 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bob Bishop: > Hmm. -j3 still fails here, in the usual place. Even -j2 failed here. I completed a "make world" at around 15H GMT (suppoed minutes before) w/o any problem and the machine is now happily running an egcs-compiled kernel. Congrats again David. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 12:23:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 5F5DC1544E for ; Tue, 6 Apr 1999 12:23:15 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id UAA01500; Tue, 6 Apr 1999 20:20:35 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 6 Apr 1999 20:15:15 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 6 Apr 1999 20:15:13 +0000 To: current@FreeBSD.ORG From: Bob Bishop Subject: Band-aid for building world with -jn [PATCH] Cc: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The following patch makes -jn work. I don't claim it's any sort of long-term solution. The hack consists of simply dropping .NOTPARALLEL: into the right Makefile, but since .NOTPARALLEL is broken (see bin/10985 for the gory details) you'll need the attached patch for make too. Index: src/gnu/usr.bin/cc/cc_tools/Makefile =================================================================== RCS file: /CVSROOT/src/gnu/usr.bin/cc/cc_tools/Makefile,v retrieving revision 1.18 diff -c -r1.18 Makefile *** Makefile 1999/04/05 10:18:50 1.18 --- Makefile 1999/04/06 17:29:50 *************** *** 2,7 **** --- 2,10 ---- # $Id: Makefile,v 1.18 1999/04/05 10:18:50 peter Exp $ # + # XXX band-aid for -jn + .NOTPARALLEL: + # # This could probably be merged with ../cc_int/Makefile, but bsd.lib.mk # is such a !@#!*#% nightmare because of how it reprograms the dependencies, Index: src/usr.bin/make/main.c =================================================================== RCS file: /CVSROOT/src/usr.bin/make/main.c,v retrieving revision 1.30 diff -c -r1.30 main.c *** main.c 1999/03/01 06:01:05 1.30 --- main.c 1999/04/06 12:59:59 *************** *** 123,129 **** static Lst variables; /* list of variables to print */ int maxJobs; /* -j argument */ static Boolean forceJobs; /* -j argument given */ ! static int maxLocal; /* -L argument */ Boolean compatMake; /* -B argument */ Boolean debug; /* -d flag */ Boolean noExecute; /* -n flag */ --- 123,129 ---- static Lst variables; /* list of variables to print */ int maxJobs; /* -j argument */ static Boolean forceJobs; /* -j argument given */ ! int maxLocal; /* -L argument */ Boolean compatMake; /* -B argument */ Boolean debug; /* -d flag */ Boolean noExecute; /* -n flag */ Index: src/usr.bin/make/parse.c =================================================================== RCS file: /CVSROOT/src/usr.bin/make/parse.c,v retrieving revision 1.20 diff -c -r1.20 parse.c *** parse.c 1999/01/08 18:37:34 1.20 --- parse.c 1999/04/06 16:34:14 *************** *** 874,881 **** --- 874,884 ---- case NotParallel: { extern int maxJobs; + extern int maxLocal; maxJobs = 1; + maxLocal = 1; + compatMake = 1; /* would have been turned on if no -j */ break; } case SingleShell: -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 12:29:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id A0FF815700 for ; Tue, 6 Apr 1999 12:29:31 -0700 (PDT) (envelope-from spud@i.am) Received: from i.am (RAS1-p66.hfa.netvision.net.il [62.0.145.66]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id VAA11795 for ; Tue, 6 Apr 1999 21:26:50 +0200 (IST) Message-ID: <370A5D23.DAA599DD@i.am> Date: Tue, 06 Apr 1999 22:14:44 +0300 From: Tomer Weller X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: C++ cannot create executables ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG im having problems compiling the giCQ port under 4.0-current. configuration says my C++ compiler cannot create executables, any idea what's the problem ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 12:34:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 36CFC15679 for ; Tue, 6 Apr 1999 12:34:07 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id OAA23219; Tue, 6 Apr 1999 14:32:01 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id OAA23215; Tue, 6 Apr 1999 14:31:58 -0500 (CDT) Message-ID: <032601be8064$53cb7440$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Tomer Weller" , Subject: Re: C++ cannot create executables ? Date: Tue, 6 Apr 1999 14:33:17 -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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Read the recent posts. Let me guess, you have probably done a fairly recent cvsup (sunday evening?) and you built world. You now have egcs as your compiler (gcc -v). The best thing to do, at least the easiest to tell you to do, is to simply cvsup the sources again and make the world. You probably caught the sources in a transient state during the commit of the egcs compiler as the system compiler. Tom Veldhouse veldy@visi.com -----Original Message----- From: Tomer Weller To: freebsd-current@FreeBSD.ORG Date: Tuesday, April 06, 1999 2:28 PM Subject: C++ cannot create executables ? >im having problems compiling the giCQ port under 4.0-current. >configuration says my C++ compiler cannot create executables, any idea >what's the problem ? > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 13: 1: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 10892151D6 for ; Tue, 6 Apr 1999 13:01:00 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id <2CP9J2GW>; Tue, 6 Apr 1999 20:57:05 +0100 Message-ID: From: paul@originative.co.uk To: dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: RE: EGCS optimizations Date: Tue, 6 Apr 1999 20:57:04 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Matthew Dillon [mailto:dillon@apollo.backplane.com] > Sent: 06 April 1999 05:58 > To: current@FreeBSD.ORG > Subject: EGCS optimizations > > .... > Compiling up /usr/src/usr.sbin with egcs and libc compiled with: > > -O2 160 seconds > -O2 -march=pentiumpro 162 seconds > -Os 161 seconds > > Which leads me to believe that using -Os might be beneficial. > If I'm reading that right you timed how long it took to build /usr/src/usr.sbin using egcs and libc compiled with the above optimisations? I doubt that that sort of benchmark is going to say an awful lot about the performance of the optimisation levels since compiling /usr/sr/usr.sbin is going to be affected by disk i/o performance far more than it would be by cpu performance. The relative speed differences of the different egcs/libc binaries is probably smoothed out by the i/o affects which is why the times look so similar. Something that is more cpu bound would be a better benchmark for comparing the optimisation options. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 13: 3:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 93F73151D6 for ; Tue, 6 Apr 1999 13:03:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA10310; Tue, 6 Apr 1999 13:01:07 -0700 (PDT) (envelope-from dillon) Date: Tue, 6 Apr 1999 13:01:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199904062001.NAA10310@apollo.backplane.com> To: paul@originative.co.uk Cc: current@FreeBSD.ORG Subject: Re: RE: EGCS optimizations References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I doubt that that sort of benchmark is going to say an awful lot about the :performance of the optimisation levels since compiling /usr/sr/usr.sbin is :going to be affected by disk i/o performance far more than it would be by :cpu performance. The relative speed differences of the different egcs/libc :binaries is probably smoothed out by the i/o affects which is why the times :look so similar. : :Something that is more cpu bound would be a better benchmark for comparing :the optimisation options. : : :Paul. That test was 100% cpu bound. There was no ( significant ) I/O. I ran it a few times to build the cache before timing it. It's no big deal, really. I think the EGCS bandwagon is going to continue to move forward and PGCS runs on top of it, so moving to EGCS puts FreeBSD in a better position in the long term. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 13:14: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id C151D14D70 for ; Tue, 6 Apr 1999 13:13:52 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id WAA24018; Tue, 6 Apr 1999 22:11:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id WAA63445; Tue, 6 Apr 1999 22:11:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: paul@originative.co.uk, current@FreeBSD.ORG Subject: Re: EGCS optimizations In-reply-to: Your message of "Tue, 06 Apr 1999 13:01:07 PDT." <199904062001.NAA10310@apollo.backplane.com> Date: Tue, 06 Apr 1999 22:11:37 +0200 Message-ID: <63443.923429497@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904062001.NAA10310@apollo.backplane.com>, Matthew Dillon writes: > That test was 100% cpu bound. There was no ( significant ) I/O. I ran > it a few times to build the cache before timing it. What is the stddev on your measurements ? a delta-T 1 second need a very tight stddev to be significant. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 13:37:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 4837A14C8E for ; Tue, 6 Apr 1999 13:36:55 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id QAA76816; Tue, 6 Apr 1999 16:32:21 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Tue, 6 Apr 1999 16:32:20 +0000 (GMT) From: eagle To: Alex Zepeda Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: EGCS optimizations In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, Alex Zepeda wrote: > On Mon, 5 Apr 1999, Matthew Dillon wrote: > > > There is nothing beyond -O2. Well, there's -O3, which tries to > > inline static functions, but that typically isn't beneficial because > > it really bloats up the code and subroutine calls on intel cpus are > > very fast. > > Really? > > The pgcc web page (goof.com/pcg) lead me to believe that there were a few > more optimizations turned on by -O5 && -O6.. pgcc isn't the same as egcs the current -mpentiumpro and -mpentiumarch stuff were taken from pgcc and ported back to egcs but i believe that pgcc has gone way beyond what it was when that happened. rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 13:38:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id A54C815516 for ; Tue, 6 Apr 1999 13:38:40 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id QAA76823; Tue, 6 Apr 1999 16:35:05 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Tue, 6 Apr 1999 16:35:05 +0000 (GMT) From: eagle To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: EGCS breaks what(1) In-Reply-To: <199904060603.QAA18049@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Apr 1999, Bruce Evans wrote: > >Alternately, we could jimmy around with the current hack, and prefix it > >with 4 NULs, and see what happened. Sorry, I haven't tested this idea, as > >I've not yet made the EGCS jump. > > egcs aligns long (>= about 28 bytes) strings to 32-byte boundaries. This > adds up to 27 NULs to sccsid[] depending on the alignment of sccsidp[]. > > Aligning long strings to 32-byte boundaries is a pessimisation in kernels > (because it makes poor locality poorer), especially on 486's where the > cache line size is 16. > > Bruce > not aligning data is extremely expensive on PII's rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 13:40:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8461D14EFA for ; Tue, 6 Apr 1999 13:40:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA10567; Tue, 6 Apr 1999 13:34:09 -0700 (PDT) (envelope-from dillon) Date: Tue, 6 Apr 1999 13:34:09 -0700 (PDT) From: Matthew Dillon Message-Id: <199904062034.NAA10567@apollo.backplane.com> To: Poul-Henning Kamp Cc: paul@originative.co.uk, current@FreeBSD.ORG Subject: Re: EGCS optimizations References: <63443.923429497@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> it a few times to build the cache before timing it. : :What is the stddev on your measurements ? : :a delta-T 1 second need a very tight stddev to be significant. The timing was +/- 0.5 second ( I ran the test four times ). But, remember, this is not comparing against GCC. This was simply comparing various EGCC optimization features. stddev on ~160 seconds +/- 0.5s is basically 0, so it is not a useful measurement beyond noting that it is near 0. I would love to see a comparison against GCC. I blew away my GCC :-( and do not want to spend time reinstalling it. :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 13:42:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A86514CC4 for ; Tue, 6 Apr 1999 13:42:26 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA10593; Tue, 6 Apr 1999 13:35:35 -0700 (PDT) (envelope-from dillon) Date: Tue, 6 Apr 1999 13:35:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199904062035.NAA10593@apollo.backplane.com> To: Poul-Henning Kamp Cc: paul@originative.co.uk, current@FreeBSD.ORG Subject: Re: EGCS optimizations References: <63443.923429497@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :What is the stddev on your measurements ? : :a delta-T 1 second need a very tight stddev to be significant. I would say that a 1% increase or decrease in performance is not significant, so stddev is not significant either. There are too many other factors ( such as running a single program suite - EGCC, that does one task - compiling, instead of many different suites ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 13:50:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (spain-37.ppp.hooked.net [206.169.228.37]) by hub.freebsd.org (Postfix) with ESMTP id 1FAE614DB9 for ; Tue, 6 Apr 1999 13:50:36 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id NAA02188; Tue, 6 Apr 1999 13:48:41 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Tue, 6 Apr 1999 13:48:41 -0700 (PDT) From: Alex Zepeda To: Matthew Dillon Cc: paul@originative.co.uk, current@FreeBSD.ORG Subject: Re: RE: EGCS optimizations In-Reply-To: <199904062001.NAA10310@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Apr 1999, Matthew Dillon wrote: > It's no big deal, really. I think the EGCS bandwagon is going to continue > to move forward and PGCS runs on top of it, so moving to EGCS puts FreeBSD > in a better position in the long term. Well what would be the chances of getting the pgcc patches committed? It seems like this wouldn't have a negative impact on other non x86 hardware, but might be a win for us stuck with Pentiums or PIIs. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 15:18:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0533D15361 for ; Tue, 6 Apr 1999 15:18:32 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id PAA28376; Tue, 6 Apr 1999 15:16:33 -0700 (PDT) (envelope-from obrien) Message-ID: <19990406151633.A28346@nuxi.com> Date: Tue, 6 Apr 1999 15:16:33 -0700 From: "David O'Brien" To: Alex Zepeda Cc: current@FreeBSD.ORG Subject: Re: RE: EGCS optimizations Reply-To: obrien@NUXI.com References: <199904062001.NAA10310@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alex Zepeda on Tue, Apr 06, 1999 at 01:48:41PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well what would be the chances of getting the pgcc patches committed? I'm quite interested in doing this, BUT only after the dust has settled on the EGCS import and the Alpha build is fixed. Also the 1.1.2 PGCC patches aren't available yet. jdp and I have another round of bootstraping to fix our current less-than-optimal exception handling. I want to wait a week or so until putting the changes into the tree. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 15:18:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-52.camalott.com [208.229.74.52]) by hub.freebsd.org (Postfix) with ESMTP id D9744156FF for ; Tue, 6 Apr 1999 15:18:26 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.1) id RAA91771; Tue, 6 Apr 1999 17:16:17 -0500 (CDT) (envelope-from joelh) To: loverso@sitaranetworks.com Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: EGCS breaks what(1) References: <199904060156.SAA84557@apollo.backplane.com> <370A0B4D.2A710364@sitara.net> From: Joel Ray Holveck Date: 06 Apr 1999 17:16:16 -0500 In-Reply-To: "John R. LoVerso"'s message of "Tue, 06 Apr 1999 09:25:33 -0400" Message-ID: <86hfqtbdjj.fsf@detlev.UUCP> Lines: 29 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>'what' is broken. C does not impose any sort of address ordering >>>restriction on globals or autos that are declared next to each other. > Right, except that 'what' isn't broken. It is vers.c (and conf/newvers.sh) > that is broken, believing that the two variables will be allocating in > contiguous memory. > Changing newvers.sh to generate > char sccs[] = "@(" "#)" "FreeBSD ..."; > char version = "FreeBSD ..."; I will assume you meant "char *version" here. > will make "what" on the kernel work again, at the expense of about 100 > duplicated > bytes. Check me if I'm wrong, but could we not do the same thing without the duplication: char sccs[] = "@(" "#)" "FreeBSD ..."; char *version = sccs + 4; Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 15:19:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A5B19155DA for ; Tue, 6 Apr 1999 15:19:49 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id PAA28402; Tue, 6 Apr 1999 15:17:51 -0700 (PDT) (envelope-from obrien) Message-ID: <19990406151750.B28346@nuxi.com> Date: Tue, 6 Apr 1999 15:17:50 -0700 From: "David O'Brien" To: Tomer Weller , freebsd-current@FreeBSD.ORG Subject: Re: C++ cannot create executables ? Reply-To: obrien@NUXI.com References: <370A5D23.DAA599DD@i.am> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <370A5D23.DAA599DD@i.am>; from Tomer Weller on Tue, Apr 06, 1999 at 10:14:44PM +0300 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > im having problems compiling the giCQ port under 4.0-current. > configuration says my C++ compiler cannot create executables, any idea > what's the problem ? On the bootstrap `make world' to EGCS libstdc++ is broken. Do a second `make world' and you will have a working system. I know what the problem with libstdc++ is, but not why it is occuring. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 15:20:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (spain-37.ppp.hooked.net [206.169.228.37]) by hub.freebsd.org (Postfix) with ESMTP id 281A7155D0 for ; Tue, 6 Apr 1999 15:20:40 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id PAA33299; Tue, 6 Apr 1999 15:18:53 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Tue, 6 Apr 1999 15:18:53 -0700 (PDT) From: Alex Zepeda To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: RE: EGCS optimizations In-Reply-To: <19990406151633.A28346@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Apr 1999, David O'Brien wrote: > > Well what would be the chances of getting the pgcc patches committed? > > I'm quite interested in doing this, BUT only after the dust has settled > on the EGCS import and the Alpha build is fixed. Also the 1.1.2 PGCC > patches aren't available yet. Cool!! > jdp and I have another round of bootstraping to fix our current > less-than-optimal exception handling. I want to wait a week or so > until putting the changes into the tree. Well, congrats on the reasonably smooth job so far. The only other thing I'd have on my wish list is the ability to not build the gcc related bits (so I could say drop in TenDRA) by adding -DNO_GCC or something. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 15:30:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m1-12-dbn.dial-up.net [196.34.155.12]) by hub.freebsd.org (Postfix) with ESMTP id 2CDCE1573B for ; Tue, 6 Apr 1999 15:30:44 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA21754; Wed, 7 Apr 1999 00:24:10 +0200 (SAT) From: Robert Nordier Message-Id: <199904062224.AAA21754@ceia.nordier.com> Subject: Re: loader In-Reply-To: from Chuck Robey at "Apr 5, 99 09:50:26 pm" To: chuckr@mat.net (Chuck Robey) Date: Wed, 7 Apr 1999 00:24:08 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > I just finished a buildworld, and I'm not sure about the laoder binary. > In my obj/usr/src/sys/boot/i386/loader directory, I have 3 files that > might be loader: > > -rw-r--r-- 1 root wheel 135168 Apr 5 19:01 loader > -rwxr-xr-x 1 root wheel 121672 Apr 5 19:01 loader.bin* > -rwxr-xr-x 1 root wheel 259171 Apr 5 19:01 loader.sym* > > None of them are the size of my existing (gcc) /boot/loader: > > -r-xr-xr-x 1 root wheel 126976 Apr 4 17:10 loader* > > I use CFLAGS of -O -pipe. Can anyone tell me which of the above files > gets installed as /boot/loader, and if (from the filesize) I have a good > loader or not? This is the last thing worrying me about giong to egcs, > and I'm just playing it very cautiously. The file "loader" gets installed. (The .bin file is created from the .sym file and fed into btxld(8), which outputs loader after binding in the BTX bits.) The 135168-byte loader works fine here, and I can't think of any reason it should cause problems for you. (It's to be expected that a more recent compiler will emit different object code, so size comparisons are apples and oranges.) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 16: 5: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 31C7314E75 for ; Tue, 6 Apr 1999 16:05:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA11340; Tue, 6 Apr 1999 16:03:07 -0700 (PDT) (envelope-from dillon) Date: Tue, 6 Apr 1999 16:03:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199904062303.QAA11340@apollo.backplane.com> To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: panic: vm_page_bits: illegal base/size 4096/512 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This occurs when I'm copying from a floppy (MS-DOS) to my home dir which is :on an FFS file system. Any ideas? Reproduced of course. : : Brian Feldman _ __ ___ ____ ___ ___ ___ : green@unixhelp.org _ __ ___ | _ ) __| \ Brian, if the contents of the floppy is not sensitive, could you gzip it up and email it to me mime-encoded so I can reproduce the panic on my test box? This panic was recently added to catch illegal requests to set/clear dirty/valid bits in VM pages. -Matt :initial pcb at 23f440 :panicstr: vm_page_bits: illegal base/size 4096/512 :panic messages: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 16:13:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6608414EE9 for ; Tue, 6 Apr 1999 16:13:18 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA86917; Tue, 6 Apr 1999 19:09:12 -0400 (EDT) Date: Tue, 6 Apr 1999 19:09:12 -0400 (EDT) From: Chuck Robey To: Robert Nordier Cc: freebsd-current@FreeBSD.ORG Subject: Re: loader In-Reply-To: <199904062224.AAA21754@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, Robert Nordier wrote: > Chuck Robey wrote: > > > I just finished a buildworld, and I'm not sure about the laoder binary. > > In my obj/usr/src/sys/boot/i386/loader directory, I have 3 files that > > might be loader: > > > > -rw-r--r-- 1 root wheel 135168 Apr 5 19:01 loader > > -rwxr-xr-x 1 root wheel 121672 Apr 5 19:01 loader.bin* > > -rwxr-xr-x 1 root wheel 259171 Apr 5 19:01 loader.sym* > > > > None of them are the size of my existing (gcc) /boot/loader: > > > > -r-xr-xr-x 1 root wheel 126976 Apr 4 17:10 loader* > > > > I use CFLAGS of -O -pipe. Can anyone tell me which of the above files > > gets installed as /boot/loader, and if (from the filesize) I have a good > > loader or not? This is the last thing worrying me about giong to egcs, > > and I'm just playing it very cautiously. > > The file "loader" gets installed. (The .bin file is created from the > .sym file and fed into btxld(8), which outputs loader after binding in > the BTX bits.) > > The 135168-byte loader works fine here, and I can't think of any > reason it should cause problems for you. (It's to be expected that > a more recent compiler will emit different object code, so size > comparisons are apples and oranges.) Thanks, Robert. I booted it, it all works just fine; maybe I was just being extra cautious. > > -- > Robert Nordier > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 16:27:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id EF33E1570E for ; Tue, 6 Apr 1999 16:27:14 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id TAA55483; Tue, 6 Apr 1999 19:25:16 -0400 (EDT) Date: Tue, 6 Apr 1999 19:25:16 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: panic: vm_page_bits: illegal base/size 4096/512 In-Reply-To: <199904062303.QAA11340@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Apr 1999, Matthew Dillon wrote: > :This occurs when I'm copying from a floppy (MS-DOS) to my home dir which is > :on an FFS file system. Any ideas? Reproduced of course. > : > : Brian Feldman _ __ ___ ____ ___ ___ ___ > : green@unixhelp.org _ __ ___ | _ ) __| \ > > Brian, if the contents of the floppy is not sensitive, could you gzip > it up and email it to me mime-encoded so I can reproduce the panic on my > test box? This panic was recently added to catch illegal requests to > set/clear dirty/valid bits in VM pages. I hope no hardware is triggering this, because today I also got a double page fault... I took out 32 mb of RAM I don't think is very good, and I need to see if this system approaches stability. > > -Matt > > > :initial pcb at 23f440 > :panicstr: vm_page_bits: illegal base/size 4096/512 > :panic messages: > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 17: 2:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8140715453 for ; Tue, 6 Apr 1999 17:02:21 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id RAA02533; Tue, 6 Apr 1999 17:00:22 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id RAA00584; Tue, 6 Apr 1999 17:00:21 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 6 Apr 1999 17:00:21 -0700 (PDT) Message-Id: <199904070000.RAA00584@vashon.polstra.com> To: dillon@apollo.backplane.com Subject: Re: aio_read In-Reply-To: <199904061701.KAA09326@apollo.backplane.com> References: <199904051834.LAA11656@apollo.backplane.com.newsgate.clinet.fi> <86vhfam5vn.fsf@not.oeno.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904061701.KAA09326@apollo.backplane.com>, Matthew Dillon wrote: > : > :It's not necessarily breakage. Not having any mechanism other than > :open to get your own seek offset is nasty, but sharing a seek offset > :can also be useful. File descriptors can't be "reverse-inherited", so > :in order to continue writing to the same redirected output file, a > :sequence of commands executed by a shell needs to be able to share the > :actual file offset. I believe this was the original reason for the > :behavior. > > If it's a redirected output file you simply make it O_APPEND, at which > point the seek offset in the descriptor becomes irrelevant. But O_APPEND didn't exist in early versions of Unix. I'm sure it wasn't present in V6, and I'm pretty sure it wasn't present in V7 either. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 17:20: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 4936A156DE for ; Tue, 6 Apr 1999 17:20:05 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id CAA59835; Wed, 7 Apr 1999 02:17:57 +0200 (CEST) (envelope-from des) To: Sheldon Hearn Cc: Scott Michel , current@FreeBSD.ORG Subject: Re: YP/NIS and passwd weirdness References: <22541.923406479@axl.noc.iafrica.com> From: Dag-Erling Smorgrav Date: 07 Apr 1999 02:17:56 +0200 In-Reply-To: Sheldon Hearn's message of "Tue, 06 Apr 1999 15:47:59 +0200" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn writes: > -awk -F: '$2=="" {print $0}' /etc/master.passwd > +grep -v '^\+' /etc/master.passwd | awk -F: '$2=="" {print $0}' auuuuuuuuuuuugh! awk -F: '$1 !~ /^\+/ && $2=="" {print $0}' /etc/master.passwd DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 17:23: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E2A4156FA for ; Tue, 6 Apr 1999 17:22:48 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id BAA04386; Wed, 7 Apr 1999 01:20:46 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 7 Apr 1999 01:14:59 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199904070000.RAA00584@vashon.polstra.com> References: <199904061701.KAA09326@apollo.backplane.com> <199904051834.LAA11656@apollo.backplane.com.newsgate.clinet.fi> <86vhfam5vn.fsf@not.oeno.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 7 Apr 1999 01:14:56 +0000 To: John Polstra From: Bob Bishop Subject: Re: aio_read Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:00 pm -0700 6/4/99, John Polstra wrote: >[...] >But O_APPEND didn't exist in early versions of Unix. I'm sure it >wasn't present in V6, and I'm pretty sure it wasn't present in V7 >either. [Blows dust off V7 manual] You're right: it wasn't. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 17:40:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 2608F14C17 for ; Tue, 6 Apr 1999 17:40:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id CAA25609 for ; Wed, 7 Apr 1999 02:38:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id CAA64592 for ; Wed, 7 Apr 1999 02:38:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: I'll be in the Reading/London area this weekend... From: Poul-Henning Kamp Date: Wed, 07 Apr 1999 02:38:18 +0200 Message-ID: <64590.923445498@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll be in the Reading / London area from Friday morning until Sunday evening. If there are any FreeBSD events taking place send me email and I'll try to pop around... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 17:43:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 978F215518 for ; Tue, 6 Apr 1999 17:43:19 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id RAA02710 for ; Tue, 6 Apr 1999 17:41:20 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id RAA00732; Tue, 6 Apr 1999 17:41:19 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 6 Apr 1999 17:41:19 -0700 (PDT) Message-Id: <199904070041.RAA00732@vashon.polstra.com> To: current@freebsd.org Subject: Re: cvsup4.freebsd.org is running behind In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , John Polstra wrote: > > If you are trying to follow the fast pace in -current right now, I'd > suggest that you avoid cvsup4 until it's fixed. I'll announce that > when it happens. It's looking like cvsup4 may be down for the count. We've made cvsup4.freebsd.org an alias for cvsup5.freebsd.org for now. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 18:15:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id EA3C114E02 for ; Tue, 6 Apr 1999 18:15:53 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA11482; Wed, 7 Apr 1999 10:43:52 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA12928; Wed, 7 Apr 1999 10:43:51 +0930 (CST) Message-ID: <19990407104350.S2142@lemis.com> Date: Wed, 7 Apr 1999 10:43:50 +0930 From: Greg Lehey To: David Malone , freebsd-current@freebsd.org Subject: Re: New SiS 5591 ide chipset support. References: <9904061544.aa29995@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <9904061544.aa29995@salmon.maths.tcd.ie>; from David Malone on Tue, Apr 06, 1999 at 03:44:51PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 6 April 1999 at 15:44:51 +0100, David Malone wrote: > I'm having trouble with a kernel built from this mornings make world. > It seems to be related to the new SiS 5591 ide chipset support. It > gets as far as the automatic reboot in progress and then says: > > wd0: interrupt timeout (status 50 error 0) > wd0: wdtimeout() DMA status 0 > wd0: interrupt timeout (status 50 error 1) > wd0: wdtimeout() DMA status 0 > wd0: interrupt timeout (status 50 error 1) > wd0: wdtimeout() DMA status 0 > wd0: interrupt timeout (status 50 error 1) > wd0: wdtimeout() DMA status 0 > . > . > . > > The first thing is that I guess the should be , My understanding is that it stands for "no damage". > the second is that it seems to sit there doing that for longer than > I was willing to wait (it eventually prints a message saying that it > presumes it is a laptop and shouldn't print any more of these > messages). Right, it's timing out on something. > Backing out the last change to ide_pci.c seems to fix the problem. > I've lots of flags turned on in the kernel config file (0xa0ffa0ff), > the old kernel complains a little but works fine, the new kernel > spots that it is a SiS 5591, but grinds to a halt. Interesting. What motherboard do you have? Does it also have a 5595 on board? > If it helps any, the older working kernel prints one timeout message > when booting after the bad kernel has been booted, and my root > filesystem is actually on wd1. Is my drive/controller not up to the > flags I've set, or is this a problem with the new chipset support? One way or another it's a problem with the new chipset support if it makes a previously working system no longer work. > In config file: > --------------- > controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff > > The old kernel says: > -------------------- > ide_pci0: rev 0xc1 int a irq 14 on pci0.1.1 > ide_pci: generic_dmainit 01f0:0: warning, IDE controller timing not set > > The new kernel reports this: > ---------------------------- > ide_pci0: rev 0xc1 int a irq 14 on pci0.1.1 Hmm. This is an older version than mine. I have: ide_pci0: rev 0xd0 int a irq 14 on pci0.0.1 chip1: rev 0x01 on pci0.1.0 chip2: rev 0x00 on pci0.2.0 Do you have the other chip reports as well? > New kernel with -v: > ------------------- > SiS 5591 dmainit: primary drive 0 setting ultra DMA mode 2 > wd0: wdsetmode() setting transfer mode to 42 > SiS 5591 status: CRTC 12 PCICLK, CATC12 PCICLK, applies to all IDE drives > SiS 5591 status: burst cycles enabeled, fast post write control enabeled > SiS 5591 status: primary drive 0 DRTC 1 PCICLK, DATC 3 PCICLK > SiS 5591 status: primary drive 0 Ultra DMA enabeled, 1PCICLK data out > SiS 5591 status: primary drive 0 postwrite enabeled, prefetch enabeled prefetch count is 512 > SiS 5591 status: primary drive 0 has been configured for DMA > wdc0: unit 0 (wd0) , DMA, 32-bit, multi-block-16 > wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > wd0: ATA INQUIRE valid = 0007, dmaword = 0007, apio = 0003, vdma = 0407 OK. Can I assume that you have only one drive on the machine? Have you tried a smaller DMA transfer size (say, to start with, 0xa001a001)? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 18:19: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D258214E02 for ; Tue, 6 Apr 1999 18:18:59 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA19579; Wed, 7 Apr 1999 10:46:48 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904061447.IAA28917@panzer.plutotech.com> Date: Wed, 07 Apr 1999 10:46:48 +0930 (CST) From: "Daniel O'Connor" To: "Kenneth D. Merry" Subject: Re: WORM & CAM CD Cc: current@FreeBSD.ORG, (Andreas Dobloug) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Apr-99 Kenneth D. Merry wrote: > > I've got a Matsushita CW-7501. I'll send him a mail. > My guess is that cdrecord won't support it. See: > http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/c > dr-unsup.html > > And remember that Matsushita == Panasonic. > > From what I can tell, Plasmon made a clone of the CW-7501, but the worm > driver never supported that model anyway. Umm.. I can't see that drive mentioned in the list of unsupported drives on that page :) I have a CW-7502 which works very well.. cdrecord -scanbus says -> 6) 'MATSHITA' 'CD-R CW-7502 ' '4.10' Removable CD-ROM The 7501 isn't mentioned as being compatible anywhere I can see 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-current" in the body of the message From owner-freebsd-current Tue Apr 6 19:17:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 62375156C9 for ; Tue, 6 Apr 1999 19:17:15 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id UAA32428; Tue, 6 Apr 1999 20:15:09 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199904070215.UAA32428@panzer.plutotech.com> Subject: Re: WORM & CAM CD In-Reply-To: from "Daniel O'Connor" at "Apr 7, 1999 10:46:48 am" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Tue, 6 Apr 1999 20:15:09 -0600 (MDT) Cc: current@FreeBSD.ORG, andreasd@ifi.uio.no X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote... > > On 06-Apr-99 Kenneth D. Merry wrote: > > > I've got a Matsushita CW-7501. I'll send him a mail. > > My guess is that cdrecord won't support it. See: > > http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/c > > dr-unsup.html > > > > And remember that Matsushita == Panasonic. > > > > From what I can tell, Plasmon made a clone of the CW-7501, but the worm > > driver never supported that model anyway. > > Umm.. I can't see that drive mentioned in the list of unsupported drives on > that page :) Look at the line just below the URL above, and then look at the web page again. > I have a CW-7502 which works very well.. cdrecord -scanbus says -> > 6) 'MATSHITA' 'CD-R CW-7502 ' '4.10' Removable CD-ROM > > The 7501 isn't mentioned as being compatible anywhere I can see though. That's becuase it isn't. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 19:22: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id CF511154D4 for ; Tue, 6 Apr 1999 19:21:53 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA20074; Wed, 7 Apr 1999 11:49:36 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904070215.UAA32428@panzer.plutotech.com> Date: Wed, 07 Apr 1999 11:49:35 +0930 (CST) From: "Daniel O'Connor" To: "Kenneth D. Merry" Subject: Re: WORM & CAM CD Cc: andreasd@ifi.uio.no, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Apr-99 Kenneth D. Merry wrote: > Look at the line just below the URL above, and then look at the web page > again. Ack I am blind. I did read that line but proceeded to not read the web page properly > > The 7501 isn't mentioned as being compatible anywhere I can see though. > That's becuase it isn't. heh :) --- 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-current" in the body of the message From owner-freebsd-current Tue Apr 6 19:46: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from 7thsun.piermont.com (7thsun.piermont.com [206.1.51.22]) by hub.freebsd.org (Postfix) with ESMTP id D265B154D4; Tue, 6 Apr 1999 19:45:57 -0700 (PDT) (envelope-from cjs@cynic.net) Received: from localhost (localhost [[UNIX: localhost]]) by 7thsun.piermont.com (8.8.8/8.8.8) with ESMTP id WAA15461; Tue, 6 Apr 1999 22:43:53 -0400 (EDT) X-Authentication-Warning: 7thsun.piermont.com: cjs owned process doing -bs Date: Tue, 6 Apr 1999 22:43:52 -0400 (EDT) From: Curt Sampson X-Sender: cjs@7thsun.piermont.com To: andrea Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, tech-net@netbsd.org, freebsd-questions Subject: Re: arp. In-Reply-To: <011d01be7f56$a7fad060$2100a8c0@oma> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Apr 1999, andrea wrote: > [etc.] If I read you correctly, what you want to do is something like this: internet | main router 192.168.1.1/24 | |-- other hosts on 192.168.1.0/25 subnet | 192.168.1.2/25 sub-router 192.168.1.129/25 | |-- other hosts on 192.168.1.128/25 subnet | In other words, you have split your network into two subnets, but because you have no control over the `main router' above, you cannot inform it of the new subnet mask, so it believes that all the hosts on the 192.168.1.128 subnet are local. This is not hard to solve; you just turn on routing in the sub-router box and enable proxy-arp. This will cause the subrouter box, when it receives an arp request for the 128/25 subnet on the 0/25 interface, to reply to that ARP with its own address. The host that requested the arp then sends all packets to the sub-router, and normal routing gets it to its destination. The question is, does NetBSD do this properly? I think it does, but I'm lacking the AUI/10base-T transceiver I need to test this out right now. However, in theory, if you have a host 192.168.1.130 that needs to talk to the main router, you type the following command on the sub-router: arp -s 192.168.1.130 pub (The sub-router's MAC address can be gotten from an `ifconfig -a' or `netstat -i'; it will be a sequence of six hex numbers separated by colons, such as `8:0:20:1f:77:e0'.) The unfortunate part about this is that you have to add a separate arp entry for each host you want to proxy-arp for. On a cisco router, the proxy-arp option allows you to arp for anything it knows how to route to. This feature wouldn't be too hard to add to NetBSD, actually; you'd just have to modify arplookup to generate and add a new (pub, temp) arp entry for any IP address it can find a route for in its routing tables. (This would be controlled by a sysctl that would default to off, of course.) I may look at doing this after the 1.4 release. Or someone else could do it and save me the trouble. :-) cjs -- Curt Sampson 604 801 5335 De gustibus, aut bene aut nihil. The most widely ported operating system in the world: http://www.netbsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 20:52:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-136.camalott.com [208.229.74.136]) by hub.freebsd.org (Postfix) with ESMTP id 6E8A7154E3 for ; Tue, 6 Apr 1999 20:52:39 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.1) id WAA54527; Tue, 6 Apr 1999 22:50:41 -0500 (CDT) (envelope-from joelh) To: freebsd-current@freebsd.org Subject: gcc build count From: Joel Ray Holveck Date: 06 Apr 1999 22:50:40 -0500 Message-ID: <86zp4l9jhr.fsf@detlev.UUCP> Lines: 11 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How many times does gcc get built in a make buildworld? I had assumed only twice, is this wrong? Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 6 22:57:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id DBB1614BEF; Tue, 6 Apr 1999 22:57:11 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id GAA10081; Wed, 7 Apr 1999 06:55:12 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA48579; Wed, 7 Apr 1999 06:55:10 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904070555.GAA48579@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: I'll be in the Reading/London area this weekend... In-reply-to: Your message of "Wed, 07 Apr 1999 02:38:18 +0200." <64590.923445498@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Apr 1999 06:55:10 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'll be in the Reading / London area from Friday morning until > Sunday evening. If there are any FreeBSD events taking place send > me email and I'll try to pop around... There's one this evening (Wednesday) in London, but nothing on the weekend. If you're interested in a beer on Sunday afternoon, I'm sure I could persuade the family to let me out ;-) > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 0:53:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id CD436155FF for ; Wed, 7 Apr 1999 00:53:48 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id AAA48313 for current@freebsd.org; Wed, 7 Apr 1999 00:51:50 -0700 (PDT) (envelope-from obrien) Message-ID: <19990407005150.A48297@nuxi.com> Date: Wed, 7 Apr 1999 00:51:50 -0700 From: "David O'Brien" To: current@freebsd.org Subject: EGCS bootstrapping believed to be working Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I just committed a fix to the libstdc++ errors people see on the initial bootstrap from gcc 2.7.2 to EGCS. AFAIK, there are *NO* remaining bootstrap problems. If anybody has *ANY* bootstraping problems going from a pre-April 1st -CURRENT to the latest and greatest I want to hear about it. (only applies to the i386 platform) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 0:55:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 72BBD155FF for ; Wed, 7 Apr 1999 00:55:10 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id AAA48333 for current@FreeBSD.ORG; Wed, 7 Apr 1999 00:53:11 -0700 (PDT) (envelope-from obrien) Message-ID: <19990407005311.B48297@nuxi.com> Date: Wed, 7 Apr 1999 00:53:11 -0700 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: EGCS bootstrapping believed to be working Reply-To: obrien@NUXI.com References: <19990407005150.A48297@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990407005150.A48297@nuxi.com>; from David O'Brien on Wed, Apr 07, 1999 at 12:51:50AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 07, 1999 at 12:51:50AM -0700, David O'Brien wrote: > AFAIK, there are *NO* remaining bootstrap problems. NOTE, I am assuming one is *NOT* using the "-j" option. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 1:28:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 2BFE214FB8 for ; Wed, 7 Apr 1999 01:28:16 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca12-101.ix.netcom.com [205.186.214.229]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA00386; Wed, 7 Apr 1999 01:26:35 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id BAA76965; Wed, 7 Apr 1999 01:26:13 -0700 (PDT) Date: Wed, 7 Apr 1999 01:26:13 -0700 (PDT) Message-Id: <199904070826.BAA76965@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: obrien@NUXI.com Cc: current@freebsd.org In-reply-to: <19990407005150.A48297@nuxi.com> (obrien@NUXI.com) Subject: Re: EGCS bootstrapping believed to be working From: asami@freebsd.org (Satoshi - the Wraith - Asami) References: <19990407005150.A48297@nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "David O'Brien" * * Hi all, * * I just committed a fix to the libstdc++ errors people see on the initial * bootstrap from gcc 2.7.2 to EGCS. AFAIK, there are *NO* remaining * bootstrap problems. I don't know about the bootstrapping problems but 4.0-snaps started showing up again on current.freebsd.org today (19990406) so I rebuilt the XFree86 (private) package and just started a whole-tree package build. Errors are starting to appear in http://bento.freebsd.org/~asami/errorlogs/4-latest/ -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 1:30:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E02E314FB8; Wed, 7 Apr 1999 01:30:41 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id BAA48454; Wed, 7 Apr 1999 01:28:43 -0700 (PDT) (envelope-from obrien) Message-ID: <19990407012843.B48413@nuxi.com> Date: Wed, 7 Apr 1999 01:28:43 -0700 From: "David O'Brien" To: Satoshi - the Wraith - Asami Cc: current@freebsd.org Subject: Re: EGCS bootstrapping believed to be working Reply-To: obrien@NUXI.com References: <19990407005150.A48297@nuxi.com> <199904070826.BAA76965@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904070826.BAA76965@silvia.hip.berkeley.edu>; from Satoshi - the Wraith - Asami on Wed, Apr 07, 1999 at 01:26:13AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know about the bootstrapping problems but 4.0-snaps started > showing up again on current.freebsd.org today (19990406) I wouldn't trust that 4.0-snap. That one should have a broken /usr/lib/libstdc++. I can send you working versions if you need. The 19990407 4.0-snap should be gold (well silver as we are still using the worse of the excptions stack unwinding method, jdp and I will change this soon) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 1:33: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 0A8281531E for ; Wed, 7 Apr 1999 01:32:53 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 28684 invoked by uid 1008); 7 Apr 1999 08:14:19 -0000 Message-ID: <19990407081419.28682.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: freebsd-current@freebsd.org Subject: Re: I'll be in the Reading/London area this weekend... In-reply-to: Your message of "Wed, 07 Apr 1999 06:55:10 +0100." <199904070555.GAA48579@keep.lan.Awfulhak.org> Date: Wed, 07 Apr 1999 16:14:19 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers writes: >> I'll be in the Reading / London area from Friday morning until >> Sunday evening. If there are any FreeBSD events taking place send >> me email and I'll try to pop around... > >There's one this evening (Wednesday) in London, but nothing on the >weekend. > >If you're interested in a beer on Sunday afternoon, I'm sure I could >persuade the family to let me out ;-) > Perhaps a stopover here in Amsterdam might be on the order? :) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 1:54:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [195.24.160.51]) by hub.freebsd.org (Postfix) with ESMTP id D197715655 for ; Wed, 7 Apr 1999 01:54:19 -0700 (PDT) (envelope-from anders@enterprise.sanyusan.se) Received: (from anders@localhost) by enterprise.sanyusan.se (8.9.2/8.9.2) id KAA06938; Wed, 7 Apr 1999 10:51:26 +0200 (CEST) (envelope-from anders) Date: Wed, 7 Apr 1999 10:51:26 +0200 From: Anders Andersson To: Dag-Erling Smorgrav Cc: freebsd-current@FreeBSD.ORG Subject: Re: DES from source? Message-ID: <19990407105126.A6886@sanyusan.se> References: <19990403122221.A12230@sanyusan.se> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: =?iso-8859-1?Q?=3Cxzplng9oh01=2Efsf=40flood=2Eping=2Euio=2Eno=3E=3B_from?= =?iso-8859-1?Q?_Dag-Erling_Smorgrav_on_L=F6r=2C_Apr_03=2C_1999_at_05:34:?= =?iso-8859-1?Q?06pm_+0200?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dag-Erling Smorgrav (des@flood.ping.uio.no) [990403 17:33]: > Existing MD5 passwords will still work. New users will get DES > passwords. Thanks, but how do I get all my "old" users to use DES crypted passwords? Maybe I just should purify my network to loose those DES boxes and run FreeBSD md5 native only, that would be more secure and faster right? Not necessary at all to use the crypt and secure dirs in /usr/src right? If you dont need DES crypt that is, or is there any other advantage? I hope not, because then I will be happy and do no more cvsup to cvsup.internat.freebsd.org :-) Cheers! Anders -- -------------------------------------------------------- Anders Andersson anders@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ Västgötagatan 11 Tel: +46-(0)31-168730 411 39 Gothenburg, SWEDEN Fax: +46-(0)31-209361 -------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 1:56:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 50CF915655 for ; Wed, 7 Apr 1999 01:56:49 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Apr 99 09:54:50 +0100 (BST) To: Greg Lehey Cc: freebsd-current@freebsd.org Subject: Re: New SiS 5591 ide chipset support. In-reply-to: Your message of "Wed, 07 Apr 1999 10:43:50 +0930." <19990407104350.S2142@lemis.com> X-Request-Do: Date: Wed, 07 Apr 1999 09:54:49 +0100 From: David Malone Message-ID: <9904070954.aa22814@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The first thing is that I guess the should be , > > My understanding is that it stands for "no damage". OK - I just thought it might have been a typo. > > Backing out the last change to ide_pci.c seems to fix the problem. > > I've lots of flags turned on in the kernel config file (0xa0ffa0ff), > > the old kernel complains a little but works fine, the new kernel > > spots that it is a SiS 5591, but grinds to a halt. > > Interesting. What motherboard do you have? Does it also have a 5595 > on board? Its quite a cheap and nasty thing, but it works. I'll have a look when I get home and check. > One way or another it's a problem with the new chipset support if it > makes a previously working system no longer work. > ide_pci0: rev 0xd0 int a irq 14 on pci0.0 > chip1: rev 0x01 on pci0.1.0 > chip2: rev 0x00 on pci0.2.0 > > Do you have the other chip reports as well? I'll have to check again when I get home. > OK. Can I assume that you have only one drive on the machine? Have > you tried a smaller DMA transfer size (say, to start with, > 0xa001a001)? I actually have three drives and a cdrom on the two IDE busses, but it only seems to complain about the first one - I don't know if that is because it is the first one it tries to access or becauser the others work OK. I didn't take down the details of the other drives 'cos it takes ages to copy the stuff down. I did notice that it programed wd1 with transfer mode 22. Maybe I should try to take wd0 out of fstab and see if it works OK with wd1. I'll try it with a lower DMA transfer size too. David. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2: 6:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id D292315752 for ; Wed, 7 Apr 1999 02:05:16 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 29005 invoked by uid 1008); 7 Apr 1999 08:46:47 -0000 Message-ID: <19990407084647.29003.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Anders Andersson Cc: freebsd-current@freebsd.org Subject: Re: DES from source? In-reply-to: Your message of "Wed, 07 Apr 1999 10:51:26 +0200." <19990407105126.A6886@sanyusan.se> Date: Wed, 07 Apr 1999 16:46:46 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anders Andersson writes: >* Dag-Erling Smorgrav (des@flood.ping.uio.no) [990403 17:33]: > >> Existing MD5 passwords will still work. New users will get DES >> passwords. > >Thanks, but how do I get all my "old" users to use DES crypted passwords? Well, the short answer is 'you get them to change their password' . Which is true - you can't take an MD5 hash and turn it into a DES crypt, you'll need their cleartext password first. There are ways of achieving this in a large extent without their knowledge - firstly run crack, see what cleartext passwords you get. That is the easiest. My favourite though is to modify a daemon that uses cleartext authentication (say login, or the pop3 server you're using) to log sucessful attempts to a file which you can then troll for people's cleartext passwords, convert them to DES, and then only ask the few people left for a new password. >Maybe I just should purify my network to loose those DES boxes and run >FreeBSD md5 native only, that would be more secure and faster right? It depends entirely on the setup. I run DES purely because I have solaris and Digital UNIX boxen running DES. >Not necessary at all to use the crypt and secure dirs in /usr/src right? >If you dont need DES crypt that is, or is there any other advantage? > >I hope not, because then I will be happy and do no more cvsup to >cvsup.internat.freebsd.org :-) If you need DES then you'll have to get the sources from a non-US site. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2: 9:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 6CF3C15752 for ; Wed, 7 Apr 1999 02:09:42 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.3/8.9.3/Netplex) with ESMTP id RAA10768; Wed, 7 Apr 1999 17:07:25 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199904070907.RAA10768@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Anders Andersson Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: DES from source? In-reply-to: Your message of "Wed, 07 Apr 1999 10:51:26 +0200." <19990407105126.A6886@sanyusan.se> Content-Transfer-Encoding: 8bit Date: Wed, 07 Apr 1999 17:07:25 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anders Andersson wrote: > * Dag-Erling Smorgrav (des@flood.ping.uio.no) [990403 17:33]: > > > Existing MD5 passwords will still work. New users will get DES > > passwords. > > Thanks, but how do I get all my "old" users to use DES crypted passwords? Unfortunately, passwd(1) will helpfully maintain the same encryption method as was used before. ie: if a user has a MD5 passwd, the new one will also be MD5, regardless of the default. What I've wanted to do for some time is have a passwd re-coder launched from things like login etc when the plaintext password is available. I have wanted to be able to enable a transition to a new method over time. Of course, passwd(1) should ideally be able to be told to ignore the old method too - it looks like /etc/auth.conf is in the beginnings of this. (note that I'm not advocating changing the present system, just having the ability to do the two things above). Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2:16:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3326215575 for ; Wed, 7 Apr 1999 02:16:37 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id LAA66636; Wed, 7 Apr 1999 11:14:37 +0200 (CEST) (envelope-from des) To: Anders Andersson Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: DES from source? References: <19990403122221.A12230@sanyusan.se> <19990407105126.A6886@sanyusan.se> From: Dag-Erling Smorgrav Date: 07 Apr 1999 11:14:37 +0200 In-Reply-To: Anders Andersson's message of "Wed, 7 Apr 1999 10:51:26 +0200" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anders Andersson writes: > Maybe I just should purify my network to loose those DES boxes and run > FreeBSD md5 native only, that would be more secure and faster right? More secure and *slower*. When it comes to password hashing, slower is better, because it makes brute force and dictionary attacks more expensive. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2:16:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [195.24.160.51]) by hub.freebsd.org (Postfix) with ESMTP id 9DC57157A9 for ; Wed, 7 Apr 1999 02:16:53 -0700 (PDT) (envelope-from anders@enterprise.sanyusan.se) Received: (from anders@localhost) by enterprise.sanyusan.se (8.9.2/8.9.2) id LAA07215; Wed, 7 Apr 1999 11:13:51 +0200 (CEST) (envelope-from anders) Date: Wed, 7 Apr 1999 11:13:51 +0200 From: Anders Andersson To: Peter Wemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: DES from source? Message-ID: <19990407111350.A7171@sanyusan.se> References: <19990407105126.A6886@sanyusan.se> <199904070907.RAA10768@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <199904070907.RAA10768@spinner.netplex.com.au>; from Peter Wemm on Ons, Apr 07, 1999 at 05:07:25pm +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Peter Wemm (peter@netplex.com.au) [990407 11:07]: > > Unfortunately, passwd(1) will helpfully maintain the same encryption > method as was used before. ie: if a user has a MD5 passwd, the new one > will also be MD5, regardless of the default. > > What I've wanted to do for some time is have a passwd re-coder launched > from things like login etc when the plaintext password is available. I > have wanted to be able to enable a transition to a new method over time. > > Of course, passwd(1) should ideally be able to be told to ignore the old > method too - it looks like /etc/auth.conf is in the beginnings of this. > > (note that I'm not advocating changing the present system, just having the > ability to do the two things above). > > Cheers, > -Peter That sounds great Peter! Please let me know if you want me to test it for you. Anders -- -------------------------------------------------------- Anders Andersson anders@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ Västgötagatan 11 Tel: +46-(0)31-168730 411 39 Gothenburg, SWEDEN Fax: +46-(0)31-209361 -------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2:48:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0FD8014FA5 for ; Wed, 7 Apr 1999 02:47:50 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA85003; Wed, 7 Apr 1999 11:44:24 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904070944.LAA85003@freebsd.dk> Subject: Re: New SiS 5591 ide chipset support. In-Reply-To: <9904070954.aa22814@salmon.maths.tcd.ie> from David Malone at "Apr 7, 1999 9:54:49 am" To: dwmalone@maths.tcd.ie (David Malone) Date: Wed, 7 Apr 1999 11:44:23 +0200 (CEST) Cc: grog@lemis.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OK. Can I assume that you have only one drive on the machine? Have > > you tried a smaller DMA transfer size (say, to start with, > > 0xa001a001)? > > I actually have three drives and a cdrom on the two IDE busses, but it > only seems to complain about the first one - I don't know if that is > because it is the first one it tries to access or becauser the others > work OK. I didn't take down the details of the other drives 'cos it > takes ages to copy the stuff down. I did notice that it programed > wd1 with transfer mode 22. Maybe I should try to take wd0 out of fstab > and see if it works OK with wd1. I'll try it with a lower DMA transfer > size too. Erhm, the DMA transfer size has nothing to do with the multisector support that the 0x00ff00ff flags configures, it is all setup in ide_pci.c. It works by setting up a table of memory areas and lengths that should be transferred, and then the DMA hw does that all by magic ... If you want to mess with the transfer sizes thats where you could change it, but take my advise DONT!, that is not the cause of your problem. Did it work with generic DMA before, or did it just do PIO ?? If it worked, its the SISXXXX support code thats at fault. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2:50:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 5A79F157BA for ; Wed, 7 Apr 1999 02:50:11 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id TAA13334; Wed, 7 Apr 1999 19:18:07 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id TAA17999; Wed, 7 Apr 1999 19:18:06 +0930 (CST) Message-ID: <19990407191806.V2142@lemis.com> Date: Wed, 7 Apr 1999 19:18:06 +0930 From: Greg Lehey To: Soren Schmidt , David Malone Cc: freebsd-current@FreeBSD.ORG Subject: Re: New SiS 5591 ide chipset support. References: <9904070954.aa22814@salmon.maths.tcd.ie> <199904070944.LAA85003@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904070944.LAA85003@freebsd.dk>; from Soren Schmidt on Wed, Apr 07, 1999 at 11:44:23AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 7 April 1999 at 11:44:23 +0200, Soren Schmidt wrote: >>> OK. Can I assume that you have only one drive on the machine? Have >>> you tried a smaller DMA transfer size (say, to start with, >>> 0xa001a001)? >> >> I actually have three drives and a cdrom on the two IDE busses, but it >> only seems to complain about the first one - I don't know if that is >> because it is the first one it tries to access or becauser the others >> work OK. I didn't take down the details of the other drives 'cos it >> takes ages to copy the stuff down. I did notice that it programed >> wd1 with transfer mode 22. Maybe I should try to take wd0 out of fstab >> and see if it works OK with wd1. I'll try it with a lower DMA transfer >> size too. > > Erhm, the DMA transfer size has nothing to do with the multisector > support that the 0x00ff00ff flags configures, it is all setup in > ide_pci.c. It works by setting up a table of memory areas and lengths > that should be transferred, and then the DMA hw does that all by magic ... > If you want to mess with the transfer sizes thats where you could > change it, but take my advise DONT!, that is not the cause of your > problem. Oops. > Did it work with generic DMA before, or did it just do PIO ?? > If it worked, its the SISXXXX support code thats at fault. It's beginning to look like the latter. David's going to look at his system and find out what his chipset is. It looks like a relatively early version (it's older than my 18-month-old chipset), so maybe we'll have to do something based on revision level. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2:52:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id EFEFE14D12 for ; Wed, 7 Apr 1999 02:52:27 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 438 invoked by uid 1001); 7 Apr 1999 09:50:27 -0000 Date: 7 Apr 1999 09:50:27 -0000 Message-ID: <19990407095027.435.qmail@ns.oeno.com> From: Ville-Pertti Keinonen To: dillon@apollo.backplane.com Cc: current@freebsd.org In-reply-to: <199904061701.KAA09326@apollo.backplane.com> (message from Matthew Dillon on Tue, 6 Apr 1999 10:01:36 -0700 (PDT)) Subject: Re: aio_read Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If it's a redirected output file you simply make it O_APPEND, at which > point the seek offset in the descriptor becomes irrelevant. As others have pointed out, O_APPEND is much newer than the offset-sharing behavior. It also doesn't fix things for inputs. Of course with buffering, it's hard for it to have sensible semantics, but for some commands, it does work and can even useful. While I doubt many scripts rely on such behavior, it does avoid inconsistencies between internal and external commands, as well as files, ttys and pipes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2:55:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id B03721577B for ; Wed, 7 Apr 1999 02:55:33 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca12-101.ix.netcom.com [205.186.214.229]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id CAA00518; Wed, 7 Apr 1999 02:53:52 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id CAA77717; Wed, 7 Apr 1999 02:53:30 -0700 (PDT) Date: Wed, 7 Apr 1999 02:53:30 -0700 (PDT) Message-Id: <199904070953.CAA77717@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: obrien@NUXI.com Cc: current@freebsd.org In-reply-to: <19990407012843.B48413@nuxi.com> (obrien@NUXI.com) Subject: Re: EGCS bootstrapping believed to be working From: asami@freebsd.org (Satoshi - the Wraith - Asami) References: <19990407005150.A48297@nuxi.com> <199904070826.BAA76965@silvia.hip.berkeley.edu> <19990407012843.B48413@nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "David O'Brien" * I wouldn't trust that 4.0-snap. That one should have a broken * /usr/lib/libstdc++. I can send you working versions if you need. * * The 19990407 4.0-snap should be gold (well silver as we are still using * the worse of the excptions stack unwinding method, jdp and I will change * this soon) Thanks for the notice, but don't worry too much. I just meant to say I've restarted the regular package building on both 3.1 and 4.0 trees. By the way, do I need to rebuild the private XFree86 package when I grab a better snap or is that not necessary? (That part is not automatic....) -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 2:58:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 199AE15757; Wed, 7 Apr 1999 02:58:10 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id CAA69329; Wed, 7 Apr 1999 02:56:11 -0700 (PDT) (envelope-from obrien) Message-ID: <19990407025611.B61301@nuxi.com> Date: Wed, 7 Apr 1999 02:56:11 -0700 From: "David O'Brien" To: Satoshi - the Wraith - Asami Cc: current@freebsd.org Subject: Re: EGCS bootstrapping believed to be working Reply-To: obrien@NUXI.com References: <19990407005150.A48297@nuxi.com> <199904070826.BAA76965@silvia.hip.berkeley.edu> <19990407012843.B48413@nuxi.com> <199904070953.CAA77717@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904070953.CAA77717@silvia.hip.berkeley.edu>; from Satoshi - the Wraith - Asami on Wed, Apr 07, 1999 at 02:53:30AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > By the way, do I need to rebuild the private XFree86 package when I > grab a better snap or is that not necessary? (That part is not > automatic....) I don't believe there are any C++ programs in XFree86, so you would be Ok. You would have noticed that C++ programs would not link. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 4: 2:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 6DB9814D12 for ; Wed, 7 Apr 1999 04:02:52 -0700 (PDT) (envelope-from shocking@bandicoot.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id TAA25643; Wed, 7 Apr 1999 19:00:33 +0800 (WST) Received: by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id TAA02348; Wed, 7 Apr 1999 19:00:33 +0800 Date: Wed, 7 Apr 1999 19:00:33 +0800 From: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Message-Id: <199904071100.TAA02348@ariadne.tensor.pgs.com> To: current@freebsd.org, wpaul@ctr.columbia.edu Subject: Re: Patched RealTek driver -- please test Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This version survived for a little longer, but hung (on the 486 box) whilst doing a recursive ls of a large directory tree. Again, no messages, except for one which came up as the box was booting, whilst it was starting squid. The box was OK for about 4 minutes after this message, which was "rl0: watchdog timeout" Hope this helps. Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 4:37:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 28999157CE for ; Wed, 7 Apr 1999 04:37:41 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca12-101.ix.netcom.com [205.186.214.229]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id EAA00649; Wed, 7 Apr 1999 04:35:45 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id EAA79051; Wed, 7 Apr 1999 04:34:32 -0700 (PDT) Date: Wed, 7 Apr 1999 04:34:32 -0700 (PDT) Message-Id: <199904071134.EAA79051@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: obrien@NUXI.com Cc: current@freebsd.org In-reply-to: <19990407025611.B61301@nuxi.com> (obrien@NUXI.com) Subject: Re: EGCS bootstrapping believed to be working From: asami@freebsd.org (Satoshi - the Wraith - Asami) References: <19990407005150.A48297@nuxi.com> <199904070826.BAA76965@silvia.hip.berkeley.edu> <19990407012843.B48413@nuxi.com> <199904070953.CAA77717@silvia.hip.berkeley.edu> <19990407025611.B61301@nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "David O'Brien" * I don't believe there are any C++ programs in XFree86, so you would be * Ok. You would have noticed that C++ programs would not link. Ok, thanks. BTW, the list of ports that built in 3.1 but failed in 4.0 are in http://bento.freebsd.org/~asami/errorlogs/4-latest-3-latest.html The netscape's are a known problem (no a.out libs), I don't know about the rest. -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 7:16:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from cepheus.hkstar.com (cepheus.hkstar.com [202.82.3.12]) by hub.freebsd.org (Postfix) with ESMTP id 528A514DA1 for ; Wed, 7 Apr 1999 07:16:51 -0700 (PDT) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cepheus.hkstar.com (8.9.0/8.9.0) with ESMTP id WAA15063 for ; Wed, 7 Apr 1999 22:14:51 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id WAA29134 for freebsd-current@freebsd.org; Wed, 7 Apr 1999 22:14:48 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199904071414.WAA29134@b1.hkstar.com> Subject: make world error with ctm src-cur.3819 To: freebsd-current@freebsd.org Date: Wed, 7 Apr 1999 22:14:47 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just wanted to make egcs as the default compiler and tried to make world wit ctm src-cur.3819. I got the error message. Can anyone help ? Thanks. Clarence ======= Error ======= In file included from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/xm-i386.h:43, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/hconfig.h:2, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:22: /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: linux.h: No such file or directory /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:4: i386/freebsd-elf.h: No such file or directory *** Error code 1 Stop. ======= Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 8:34:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 34F4714CE1 for ; Wed, 7 Apr 1999 08:34:07 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS3-p102.hfa.netvision.net.il [62.0.146.102]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id RAA28121 for ; Wed, 7 Apr 1999 17:31:36 +0200 (IST) From: Tomer Weller To: freebsd-current@freebsd.org Subject: something's wrong with the in the last 24 hours with the sources Date: Wed, 7 Apr 1999 18:12:03 +0300 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99040718193100.15019@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. ===> cc_int make : dont know how to make insn-attrtab.c. Stop =============================== Tomer Weller spud@i.am wellers@netvision.net.il "Drugs are good, and if you do'em pepole think that you're cool", NoFX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 8:38:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73]) by hub.freebsd.org (Postfix) with ESMTP id E336814CE1 for ; Wed, 7 Apr 1999 08:38:29 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id TAA68852 for current@freebsd.org; Wed, 7 Apr 1999 19:36:28 +0400 (MSD) (envelope-from ache) Date: Wed, 7 Apr 1999 19:36:27 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: /sys/boot, egcs vs. gcc, -Os Message-ID: <19990407193627.A68829@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now /sys/boot can't be compiled with gcc due to non-existent -Os added. Is it intentional or can be removed for backward compatibility? -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 8:40: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 3F58214E13 for ; Wed, 7 Apr 1999 08:39:56 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id QAA80482; Wed, 7 Apr 1999 16:37:49 +0100 (BST) Message-ID: <370B7BCC.B5726B2A@tdx.co.uk> Date: Wed, 07 Apr 1999 16:37:48 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Tomer Weller Cc: freebsd-current@FreeBSD.ORG Subject: Re: something's wrong with the in the last 24 hours with the sources References: <99040718193100.15019@Tomer.DrugsAreGood.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tomer Weller wrote: > > doesn't matter how much i attempt to cvsup and make world in the last 24 hours > i get this error, this is after i made world while interducing EGCS to FreeBSD, > i had to do another make world cuz my C++ compiler couldn't make executables > and that produces this situation. > > ===> cc_int > make : dont know how to make insn-attrtab.c. Stop Same here... I got the error and decided it was be being out of date on all the egcs stuff going around (I've been away recently)... I just did a straight 'buildworld' -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 8:42:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from vision.vc3.com (vision.vc3.com [209.12.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 2E91F14E13 for ; Wed, 7 Apr 1999 08:42:40 -0700 (PDT) (envelope-from tatemj@vision.vc3.com) Received: from localhost (tatemj@localhost) by vision.vc3.com (8.9.1/8.9.1) with ESMTP id LAA14190; Wed, 7 Apr 1999 11:40:17 -0400 Date: Wed, 7 Apr 1999 11:40:16 -0400 (EDT) From: Jason Tatem To: Tomer Weller Cc: freebsd-current@FreeBSD.ORG Subject: Re: something's wrong with the in the last 24 hours with the sources In-Reply-To: <99040718193100.15019@Tomer.DrugsAreGood.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had this same problem last night after a fresh cvsup. I redid the make world without my normal -j4 and it completed fine. ----------------------------------------------------------------- Jason Tatem "What you want is irrelevant. VC3, Inc. What you have chosen is at hand!" tatemj@vc3.com --Spock, Star Trek VI ----------------------------------------------------------------- On Wed, 7 Apr 1999, Tomer Weller wrote: > > doesn't matter how much i attempt to cvsup and make world in the last 24 hours > i get this error, this is after i made world while interducing EGCS to FreeBSD, > i had to do another make world cuz my C++ compiler couldn't make executables > and that produces this situation. > > ===> cc_int > make : dont know how to make insn-attrtab.c. Stop > > =============================== > Tomer Weller > spud@i.am > wellers@netvision.net.il > "Drugs are good, and if you do'em > pepole think that you're cool", NoFX > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 9:14:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 77B7E15043 for ; Wed, 7 Apr 1999 09:13:57 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async2-05.iptelecom.net.ua [212.42.68.133]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id TAA08788; Wed, 7 Apr 1999 19:12:47 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id TAA29660; Wed, 7 Apr 1999 19:11:52 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <370B83C7.9AD6ACBF@altavista.net> Date: Wed, 07 Apr 1999 19:11:51 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Jason Tatem Cc: Tomer Weller , freebsd-current@FreeBSD.ORG Subject: Re: something's wrong with the in the last 24 hours with the sources References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As it was pointed earlier in this list currently make world fails when -jn option is used. Try to compile without -jn. Jason Tatem wrote: > I had this same problem last night after a fresh cvsup.  I redid the make > world without my normal -j4 and it completed fine. > > ----------------------------------------------------------------- > Jason Tatem                     "What you want is irrelevant. > VC3, Inc.                       What you have chosen is at hand!" > tatemj@vc3.com                          --Spock, Star Trek VI > ----------------------------------------------------------------- > > On Wed, 7 Apr 1999, Tomer Weller wrote: > > > > > doesn't matter how much i attempt to cvsup and make world in the last 24 hours > > i get this error, this is after i made world while interducing EGCS to FreeBSD, > > i had to do another make world cuz my C++ compiler couldn't make executables > > and that produces this situation. > > > > ===> cc_int > > make : dont know how to make insn-attrtab.c. Stop > > > > =============================== > >  Tomer Weller > >  spud@i.am > >  wellers@netvision.net.il > >  "Drugs are good, and if you do'em > >  pepole think that you're cool", NoFX > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 9:20:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2506215043 for ; Wed, 7 Apr 1999 09:20:55 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA29897; Thu, 8 Apr 1999 01:18:44 +0900 (JST) Message-ID: <370B84A4.3818F8A@newsguy.com> Date: Thu, 08 Apr 1999 01:15:32 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os References: <19990407193627.A68829@nagual.pp.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > > Now /sys/boot can't be compiled with gcc due to non-existent -Os added. > Is it intentional or can be removed for backward compatibility? It can be removed for backward compatibility. What it does is produce a smaller code. Egcs needs it, gcc doesn't. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 9:21:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 9106215790 for ; Wed, 7 Apr 1999 09:21:38 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS6-p45.hfa.netvision.net.il [62.0.147.173]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id SAA08474 for ; Wed, 7 Apr 1999 18:19:29 +0200 (IST) From: Tomer Weller To: freebsd-current@freebsd.org Subject: current@ Date: Wed, 7 Apr 1999 19:05:59 +0300 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99040719072300.00329@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just wanted to point out i think this is a great mailing list, i just post a msg and get 4 replys in 30 minutes, keep up the good work guys/gals ! ====================================== Tomer Weller spud@i.am wellers@netvision.net.il "Drugs are good, and if you do'em pepole think that you're cool", NoFX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 9:57:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9F33114CF5; Wed, 7 Apr 1999 09:57:55 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA56386; Wed, 7 Apr 1999 09:56:21 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: Satoshi - the Wraith - Asami , current@FreeBSD.ORG Subject: Re: EGCS bootstrapping believed to be working In-reply-to: Your message of "Wed, 07 Apr 1999 01:28:43 PDT." <19990407012843.B48413@nuxi.com> Date: Wed, 07 Apr 1999 09:56:21 -0700 Message-ID: <56384.923504181@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The 19990407 4.0-snap should be gold (well silver as we are still using > the worse of the excptions stack unwinding method, jdp and I will change > this soon) That snap and those following it are pending... Peter broke the compat lib stuff last night so the snaps are falling over again. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 10: 4:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 44DD114D37; Wed, 7 Apr 1999 10:04:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id TAA29100; Wed, 7 Apr 1999 19:02:34 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id TAA66718; Wed, 7 Apr 1999 19:02:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: adrian@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: I'll be in the Reading/London area this weekend... In-reply-to: Your message of "Wed, 07 Apr 1999 16:14:19 +0800." <19990407081419.28682.qmail@ewok.creative.net.au> Date: Wed, 07 Apr 1999 19:02:18 +0200 Message-ID: <66716.923504538@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990407081419.28682.qmail@ewok.creative.net.au>, adrian@FreeBSD.OR G writes: >Brian Somers writes: >>> I'll be in the Reading / London area from Friday morning until >>> Sunday evening. If there are any FreeBSD events taking place send >>> me email and I'll try to pop around... >> >>There's one this evening (Wednesday) in London, but nothing on the >>weekend. >> >>If you're interested in a beer on Sunday afternoon, I'm sure I could >>persuade the family to let me out ;-) >> > >Perhaps a stopover here in Amsterdam might be on the order? Sorry, I'd have to bring a gun to make the flight do that... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 10: 7:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 3937814C27 for ; Wed, 7 Apr 1999 10:07:05 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.33]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2F32 for ; Wed, 7 Apr 1999 19:05:01 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA41039 for ; Wed, 7 Apr 1999 19:05:05 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 07 Apr 1999 19:05:05 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Some gcc/egcs comparisons Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG gcc compilation with -pipe -O2: 96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse* 1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32 coolbrowse.static* 2064 -rwxr-xr-x 1 root wheel - 2104523 Mar 14 10:31 cooledit* 2992 -rwxr-xr-x 1 root wheel - 3054807 Mar 14 10:32 cooledit.static* 408 -rwxr-xr-x 1 root wheel - 405283 Mar 14 10:32 coolicon* 1360 -rwxr-xr-x 1 root wheel - 1378690 Mar 14 10:32 coolicon.static* 95 -rwxr-xr-x 1 root wheel - 96919 Mar 14 10:32 coolinput* 1064 -rwxr-xr-x 1 root wheel - 1075824 Mar 14 10:32 coolinput.static* 112 -rwxr-xr-x 1 root wheel - 104093 Mar 14 10:32 coollistbox* 1064 -rwxr-xr-x 1 root wheel - 1081051 Mar 14 10:32 coollistbox.static* 160 -rwxr-xr-x 1 root wheel - 148628 Mar 14 10:31 coolman* 1120 -rwxr-xr-x 1 root wheel - 1132445 Mar 14 10:32 coolman.static* 96 -rwxr-xr-x 1 root wheel - 97866 Mar 14 10:32 coolmessage* 1064 -rwxr-xr-x 1 root wheel - 1076561 Mar 14 10:32 coolmessage.static* 95 -rwxr-xr-x 1 root wheel - 96808 Mar 14 10:32 coolquery* 1064 -rwxr-xr-x 1 root wheel - 1075721 Mar 14 10:32 coolquery.static* egcs compilation with -pipe -Os: 112 -rwxr-xr-x 1 root wheel - 105524 Apr 7 18:58 coolbrowse* 880 -rwxr-xr-x 1 root wheel - 889540 Apr 7 18:58 coolbrowse.static* 1992 -rwxr-xr-x 1 root wheel - 2029127 Apr 7 18:57 cooledit* 2720 -rwxr-xr-x 1 root wheel - 2770319 Apr 7 18:57 cooledit.static* 416 -rwxr-xr-x 1 root wheel - 410957 Apr 7 18:58 coolicon* 1160 -rwxr-xr-x 1 root wheel - 1177536 Apr 7 18:58 coolicon.static* 112 -rwxr-xr-x 1 root wheel - 105020 Apr 7 18:58 coolinput* 880 -rwxr-xr-x 1 root wheel - 889228 Apr 7 18:58 coolinput.static* 120 -rwxr-xr-x 1 root wheel - 112610 Apr 7 18:58 coollistbox* 888 -rwxr-xr-x 1 root wheel - 894763 Apr 7 18:58 coollistbox.static* 176 -rwxr-xr-x 1 root wheel - 167248 Apr 7 18:57 coolman* 936 -rwxr-xr-x 1 root wheel - 948849 Apr 7 18:58 coolman.static* 112 -rwxr-xr-x 1 root wheel - 106107 Apr 7 18:58 coolmessage* 880 -rwxr-xr-x 1 root wheel - 889977 Apr 7 18:58 coolmessage.static* 112 -rwxr-xr-x 1 root wheel - 104861 Apr 7 18:58 coolquery* 880 -rwxr-xr-x 1 root wheel - 889073 Apr 7 18:58 coolquery.static* Seems like egcs really makes smaller binaries, except when the binary is small in itself already. Seems that after the size reaches roughly 100000 bytes that egcs gets really active for optimisations. Featured program: CoolEdit 3.9.0 I unfortunately forgot to get the size of the static and shared libaries. Anyone got some details on that front? --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 10:12:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 684B014D6D; Wed, 7 Apr 1999 10:12:55 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.33]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2696; Wed, 7 Apr 1999 19:10:55 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA41055; Wed, 7 Apr 1999 19:10:59 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904070826.BAA76965@silvia.hip.berkeley.edu> Date: Wed, 07 Apr 1999 19:10:58 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: (Satoshi - the Wraith - Asami) Subject: Re: EGCS bootstrapping believed to be working Cc: current@freebsd.org, obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Apr-99 Satoshi - the Wraith - Asami wrote: > Errors are starting to appear in > > http://bento.freebsd.org/~asami/errorlogs/4-latest/ Weird that CoolEdit is on that list. I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both work a-ok after patching up ltconfig to make shared libs. --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 10:13:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 83A9B15833 for ; Wed, 7 Apr 1999 10:12:57 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id NAA00244 for ; Wed, 7 Apr 1999 13:13:05 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Wed, 7 Apr 1999 13:13:04 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: EGCS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can't get a make world to work with egcs. I deleted the whole obj directory, and recvsuppped the entire source tree, and it still doesn't work. Every time I cvsup I get a different error while compiling. Please Help. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 10:17:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id A7E0114D37 for ; Wed, 7 Apr 1999 10:17:00 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.33]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1335; Wed, 7 Apr 1999 19:14:57 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA41065; Wed, 7 Apr 1999 19:15:00 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <370B7BCC.B5726B2A@tdx.co.uk> Date: Wed, 07 Apr 1999 19:15:00 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Karl Pielorz Subject: Re: something's wrong with the in the last 24 hours with the sou Cc: freebsd-current@FreeBSD.ORG, Tomer Weller Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Apr-99 Karl Pielorz wrote: > >> doesn't matter how much i attempt to cvsup and make world in the last 24 >> hours i get this error, this is after i made world while interducing EGCS >> to FreeBSD, i had to do another make world cuz my C++ compiler couldn't >> make executables and that produces this situation. >> >> ===> cc_int >> make : dont know how to make insn-attrtab.c. Stop > > Same here... I got the error and decided it was be being out of date on > all the egcs stuff going around (I've been away recently)... I just did a > straight 'buildworld' The problem lies with the function that -j tries to do: spawn multiple processes per cpu +1. This requires dependancy tuning in the Makefiles IIRC and wasn't be done yet in order to just focus on getting egcs to work. I believed Warner or someone else fixed that problem and its either commited or waiting for inclusion. In the meantime use no -j flags or try the -j[# of CPU + 1] thing. On a side note: profiled (-g) kernels with egcs work AFAICT. --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 10:20:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 9D68114D37 for ; Wed, 7 Apr 1999 10:20:16 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.33]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4833; Wed, 7 Apr 1999 19:17:39 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA41181; Wed, 7 Apr 1999 19:17:42 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 07 Apr 1999 19:17:42 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Kenneth Wayne Culver Subject: RE: EGCS Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Apr-99 Kenneth Wayne Culver wrote: > I can't get a make world to work with egcs. I deleted the whole obj > directory, and recvsuppped the entire source tree, and it still doesn't > work. Every time I cvsup I get a different error while compiling. OK, make sure ye go to /usr/src/gnu/usr.bin/cc first make clean, make obj, make depend, make, make install then try the libs in /usr/src/lib/ with roughly the same make targets. Then try to make a world again. HTH, --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 10:22:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B132014D37 for ; Wed, 7 Apr 1999 10:22:46 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id KAA07404; Wed, 7 Apr 1999 10:20:46 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id KAA61868; Wed, 7 Apr 1999 10:20:46 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 7 Apr 1999 10:20:46 -0700 (PDT) Message-Id: <199904071720.KAA61868@vashon.polstra.com> To: asmodai@wxs.nl Subject: Re: Some gcc/egcs comparisons In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jeroen Ruigrok/Asmodai wrote: > gcc compilation with -pipe -O2: > > 96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse* > 1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32 coolbrowse.static* ... File sizes don't mean much. It would be more interesting to compare the outputs of size(1). John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 10:45:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id F0D2414BFF for ; Wed, 7 Apr 1999 10:45:29 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.91]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3BC7; Wed, 7 Apr 1999 19:43:17 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA55094; Wed, 7 Apr 1999 19:43:15 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904071720.KAA61868@vashon.polstra.com> Date: Wed, 07 Apr 1999 19:43:14 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: John Polstra Subject: Re: Some gcc/egcs comparisons Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Apr-99 John Polstra wrote: > In article , > Jeroen Ruigrok/Asmodai wrote: >> gcc compilation with -pipe -O2: >> >> 96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse* >> 1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32 >> coolbrowse.static* > ... > > File sizes don't mean much. It would be more interesting to compare > the outputs of size(1). As thou wishes: gcc with -pipe -O2: [asmodai@daemon] (47) $ ll xfmail 760 -r-xr-xr-x 1 bin bin - 767720 Jan 1 16:08 xfmail* [asmodai@daemon] (49) $ size xfmail text data bss dec hex filename 711165 53244 149924 914333 df39d xfmail [asmodai@daemon] (52) $ ll libxforms.so.0 512 -rw-r--r-- 1 root wheel - 513411 Jan 1 16:00 libxforms.so.0 [asmodai@daemon] (53) $ size libxforms.so.0 text data bss dec hex filename 412781 29556 53092 495429 78f45 libxforms.so.0 Now for egcs with -pipe -Os: [asmodai@daemon] (30) # ll xfmail 808 -r-xr-xr-x 1 bin bin - 811812 Apr 7 19:39 xfmail* [asmodai@daemon] (31) # size xfmail text data bss dec hex filename 753039 53616 150596 957251 e9b43 xfmail [asmodai@daemon] (16) # ll libxforms.so.0 512 -rw-r--r-- 1 root wheel - 513411 Apr 7 19:31 libxforms.so.0 [root@daemon] (18) # size libxforms.so.0 text data bss dec hex filename 412781 29556 53092 495429 78f45 libxforms.so.0 --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 11:10:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 4C34F15887 for ; Wed, 7 Apr 1999 11:09:29 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id OAA84321; Wed, 7 Apr 1999 14:06:12 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Wed, 7 Apr 1999 14:06:12 +0000 (GMT) From: eagle To: Tomer Weller Cc: freebsd-current@FreeBSD.ORG Subject: Re: something's wrong with the in the last 24 hours with the sources In-Reply-To: <99040718193100.15019@Tomer.DrugsAreGood.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, Tomer Weller wrote: > > doesn't matter how much i attempt to cvsup and make world in the last 24 hours > i get this error, this is after i made world while interducing EGCS to FreeBSD, > i had to do another make world cuz my C++ compiler couldn't make executables > and that produces this situation. > > ===> cc_int > make : dont know how to make insn-attrtab.c. Stop > dont use make -j anything it is currently broken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 11:21: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 2060614C10 for ; Wed, 7 Apr 1999 11:21:04 -0700 (PDT) (envelope-from brad@mail.his.com) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with SMTP id UAA27032 for ; Wed, 7 Apr 1999 20:18:53 +0200 (MET DST) X-Mailer: CTM PowerMail 2.4b2 x-sender: brad@mail.his.com Date: Wed, 7 Apr 1999 20:16:37 +0200 To: freebsd-current@freebsd.org From: Brad Knowles Subject: Installation changes? Message-Id: <19990407201637.031282@relay.skynet.be> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I'm wondering if there have been some changes made in the installation procedure for -CURRENT from -STABLE? What I'm hoping for is a completely unattended installation procedure. Once I select what I want installed, I want to be able to select the installation method, input my configuration details for the machine, and then be able to walk away. I don't want to see any warnings about XFree-whatever being a required package but not (yet) installed, etc.... I certainly don't want to have to hit return a bazillion times to get through the warnings about XFree. If there is an ftp server timeout, I'd like to be able to have the program re-try with the same server after a specified amount of delay, specify a set of alternate servers to attempt to install with, or perhaps even have the program automatically test and determine which servers are responding most quickly. I'd also like to see an http installation method, one that would hopefully successfully make it through firewalls (and/or proxy servers), much better than either NFS or ftp. Thanks! I appreciate any information you can give me about upcoming changes to the installation procedure. -- Brad Knowles Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 11:22:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73]) by hub.freebsd.org (Postfix) with ESMTP id 0E6DF1594E for ; Wed, 7 Apr 1999 11:22:16 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id WAA91130; Wed, 7 Apr 1999 22:19:42 +0400 (MSD) (envelope-from ache) Date: Wed, 7 Apr 1999 22:19:41 +0400 From: "Andrey A. Chernov" To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os Message-ID: <19990407221941.A91075@nagual.pp.ru> References: <19990407193627.A68829@nagual.pp.ru> <370B84A4.3818F8A@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <370B84A4.3818F8A@newsguy.com>; from dcs@newsguy.com on Thu, Apr 08, 1999 at 01:15:32AM +0900 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 08, 1999 at 01:15:32AM +0900, Daniel C. Sobral wrote: > "Andrey A. Chernov" wrote: > > > > Now /sys/boot can't be compiled with gcc due to non-existent -Os added. > > Is it intentional or can be removed for backward compatibility? > > It can be removed for backward compatibility. What it does is > produce a smaller code. Egcs needs it, gcc doesn't. The problem is deeper. When I reemove it, I got this error: -2100 bytes available it seems that boot2 needs to be reduced, and I don't know why it becomes that big and what can be reduced. First candidates are static cmd[512] and kernel[1024]. Please fix so it can be still compiled with gcc. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 11:35:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mgate2.telekabel.at (mgate2.telekabel.at [195.34.133.21]) by hub.freebsd.org (Postfix) with ESMTP id 04D7214C89 for ; Wed, 7 Apr 1999 11:35:19 -0700 (PDT) (envelope-from hfwirth@teleweb.at) Received: from teleweb.at ([212.17.91.153]) by mgate2.telekabel.at (Post.Office MTA v3.1.2 release (PO203-101c) ID# 0-57067U15000L15000S0V35) with ESMTP id AAA14029; Wed, 7 Apr 1999 20:33:08 +0200 Message-ID: <370BA4C7.831215CE@teleweb.at> Date: Wed, 07 Apr 1999 20:32:39 +0200 From: Helmut Wirth Reply-To: hfwirth@teleweb.at X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: Alex Zepeda , current@freebsd.org Subject: Re: EGCS optimizations References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > > On Mon, 5 Apr 1999, Matthew Dillon wrote: > > > There is nothing beyond -O2. Well, there's -O3, which tries to > > inline static functions, but that typically isn't beneficial because > > it really bloats up the code and subroutine calls on intel cpus are > > very fast. > > Really? > > The pgcc web page (goof.com/pcg) lead me to believe that there were a few > more optimizations turned on by -O5 && -O6.. > > - alex > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message As far as I know, pgcc is different from egcs. I had pgcc, it did *significantly* better code than gcc at the time (about 1 to 2 years before), especially in floating point code, but it was buggy. I have egcs-1.2 (on a current-3.0) and I am rather disappointed with the code performance. With standard code without floating point calculations it does a bit worse than old gcc-2.7.x. In floating point (as in Mesa, ..) it is awful. It generates much slower code, than gcc-2.7.x. I am using an old Linpack benchmark (Calculate n linear equations) and I can get best perfomance usually with gcc-2.7.x using -O (*not* -O2!!). The same seems to be true with egcs, but more so. Egcs with x86-prozessors work best with -O, don't use more (-marchxxx does nothing significant). I understand there are reasons to switch to egcs (exceptions, C++ enhancements,..) but I hope they will do something for egcs' code performance. (Does code size really matter that much. Sure, it accumulates, but...). -- Helmut F. Wirth Email: hfwirth@teleweb.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 11:40:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E326D14E42 for ; Wed, 7 Apr 1999 11:40:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA56903; Wed, 7 Apr 1999 11:38:42 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installation changes? In-reply-to: Your message of "Wed, 07 Apr 1999 20:16:37 +0200." <19990407201637.031282@relay.skynet.be> Date: Wed, 07 Apr 1999 11:38:42 -0700 Message-ID: <56901.923510322@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm wondering if there have been some changes made in the > installation procedure for -CURRENT from -STABLE? Not enough to give you what you're asking for here, really. :( > installed, etc.... I certainly don't want to have to hit return a > bazillion times to get through the warnings about XFree. That, at least, is fixed however. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 11:52:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 159BB14BDC for ; Wed, 7 Apr 1999 11:52:15 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id UAA09534 for ; Wed, 7 Apr 1999 20:49:27 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id UAA17817 for ; Wed, 7 Apr 1999 20:50:04 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id UAA27579 for freebsd-current@freebsd.org; Wed, 7 Apr 1999 20:50:27 +0200 (CEST) (envelope-from ticso) Date: Wed, 7 Apr 1999 20:50:26 +0200 From: Bernd Walter To: freebsd-current@freebsd.org Subject: fsck -p free() warnings on unconfigured drive Message-ID: <19990407205026.A27482@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # fsck -p /dev/rda0s1a: 2291 files, 34981 used, 4010 free (274 frags, 467 blocks, 0.7% fragmentation) /dev/rccd0c: CANNOT READ: BLK 16 /dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: page is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rccd0c: CANNOT SEEK: BLK -1 /dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rda0f: 12924 files, 157017 used, 26908 free (7796 frags, 2389 blocks, 4.2% fragmentation) /dev/rda0e: 2340 files, 21107 used, 58252 free (212 frags, 7255 blocks, 0.3% fragmentation) ccd0 was not configured the time I started fsck -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 11:56: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id C45D81586E for ; Wed, 7 Apr 1999 11:56:01 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA07880; Wed, 7 Apr 1999 11:54:01 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id LAA96158; Wed, 7 Apr 1999 11:54:00 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 7 Apr 1999 11:54:00 -0700 (PDT) Message-Id: <199904071854.LAA96158@vashon.polstra.com> To: ache@nagual.pp.ru Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <19990407221941.A91075@nagual.pp.ru> References: <19990407193627.A68829@nagual.pp.ru> <370B84A4.3818F8A@newsguy.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990407221941.A91075@nagual.pp.ru>, Andrey A. Chernov wrote: > On Thu, Apr 08, 1999 at 01:15:32AM +0900, Daniel C. Sobral wrote: > > "Andrey A. Chernov" wrote: > > > > > > Now /sys/boot can't be compiled with gcc due to non-existent -Os added. > > > Is it intentional or can be removed for backward compatibility? > > > > It can be removed for backward compatibility. What it does is > > produce a smaller code. Egcs needs it, gcc doesn't. > > The problem is deeper. When I reemove it, I got this error: > > -2100 bytes available > > it seems that boot2 needs to be reduced, and I don't know why it becomes > that big and what can be reduced. First candidates are static cmd[512] and > kernel[1024]. Please fix so it can be still compiled with gcc. Why? The compiler in -current is egcs, not gcc. If you want to use the old compiler, then use the old sources for boot too. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 12: 8:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 7192C14DDA for ; Wed, 7 Apr 1999 12:07:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id VAA29738; Wed, 7 Apr 1999 21:05:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA67488; Wed, 7 Apr 1999 21:05:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bernd Walter Cc: freebsd-current@FreeBSD.ORG Subject: Re: fsck -p free() warnings on unconfigured drive In-reply-to: Your message of "Wed, 07 Apr 1999 20:50:26 +0200." <19990407205026.A27482@cicely8.cicely.de> Date: Wed, 07 Apr 1999 21:05:35 +0200 Message-ID: <67486.923511935@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep. It would be very good if you could capture a preferably small image of a filesystem which makes this happen and make it available to the committers via a PR Poul-Henning In message <19990407205026.A27482@cicely8.cicely.de>, Bernd Walter writes: ># fsck -p >/dev/rda0s1a: 2291 files, 34981 used, 4010 free (274 frags, 467 blocks, 0.7% fragmentation) >/dev/rccd0c: CANNOT READ: BLK 16 >/dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. >fsck in free(): warning: pointer to wrong page. >fsck in free(): warning: page is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: pointer to wrong page. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >/dev/rccd0c: CANNOT SEEK: BLK -1 >/dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. >fsck in free(): warning: pointer to wrong page. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: pointer to wrong page. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >/dev/rda0f: 12924 files, 157017 used, 26908 free (7796 frags, 2389 blocks, 4.2% fragmentation) >/dev/rda0e: 2340 files, 21107 used, 58252 free (212 frags, 7255 blocks, 0.3% fragmentation) > >ccd0 was not configured the time I started fsck > >-- > B.Walter > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 12: 9:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id EA5CA14D2C for ; Wed, 7 Apr 1999 12:09:39 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.66]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3000; Wed, 7 Apr 1999 21:07:30 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id VAA61252; Wed, 7 Apr 1999 21:07:34 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990407221941.A91075@nagual.pp.ru> Date: Wed, 07 Apr 1999 21:07:34 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "Andrey A. Chernov" Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG, "Daniel C. Sobral" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Apr-99 Andrey A. Chernov wrote: > The problem is deeper. When I reemove it, I got this error: > > -2100 bytes available tried with -O2 yet? > it seems that boot2 needs to be reduced, and I don't know why it becomes > that big and what can be reduced. First candidates are static cmd[512] > and kernel[1024]. Please fix so it can be still compiled with gcc. This raises an interesting point I think. Do we need to maintain gcc/egcs compatibility? Or do we, since we track CURRENT, say: "alas, that's progression for ye?" Has there been an `official' consensus reached about this from core or commiters? --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 12:18:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 39E0214D2C for ; Wed, 7 Apr 1999 12:18:33 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id VAA11049; Wed, 7 Apr 1999 21:14:08 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id VAA18024; Wed, 7 Apr 1999 21:14:40 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id VAA27637; Wed, 7 Apr 1999 21:15:09 +0200 (CEST) (envelope-from ticso) Date: Wed, 7 Apr 1999 21:15:08 +0200 From: Bernd Walter To: Poul-Henning Kamp Cc: Bernd Walter , freebsd-current@FreeBSD.ORG Subject: Re: fsck -p free() warnings on unconfigured drive Message-ID: <19990407211508.A27608@cicely8.cicely.de> References: <19990407205026.A27482@cicely8.cicely.de> <67486.923511935@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <67486.923511935@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Apr 07, 1999 at 09:05:35PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 07, 1999 at 09:05:35PM +0200, Poul-Henning Kamp wrote: > > Yep. It would be very good if you could capture a preferably small > image of a filesystem which makes this happen and make it available > to the committers via a PR > nothing to capure - because there ist no filesystem. I just needed to use fsck -p in single user mode without the need for any ccd volume so ccd0 was not configured. > Poul-Henning > > In message <19990407205026.A27482@cicely8.cicely.de>, Bernd Walter writes: > ># fsck -p > >/dev/rda0s1a: 2291 files, 34981 used, 4010 free (274 frags, 467 blocks, 0.7% fragmentation) > >/dev/rccd0c: CANNOT READ: BLK 16 > >/dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. > >fsck in free(): warning: pointer to wrong page. > >fsck in free(): warning: page is already free. > >fsck in free(): warning: page is already free. > >fsck in free(): warning: chunk is already free. > >fsck in free(): warning: pointer to wrong page. > >fsck in free(): warning: chunk is already free. > >fsck in free(): warning: page is already free. > >fsck in free(): warning: chunk is already free. > >fsck in free(): warning: page is already free. > >fsck in free(): warning: chunk is already free. > >/dev/rccd0c: CANNOT SEEK: BLK -1 > >/dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. > >fsck in free(): warning: pointer to wrong page. > >fsck in free(): warning: page is already free. > >fsck in free(): warning: chunk is already free. > >fsck in free(): warning: page is already free. > >fsck in free(): warning: chunk is already free. > >fsck in free(): warning: pointer to wrong page. > >fsck in free(): warning: chunk is already free. > >fsck in free(): warning: page is already free. > >fsck in free(): warning: chunk is already free. > >fsck in free(): warning: page is already free. > >fsck in free(): warning: chunk is already free. > >/dev/rda0f: 12924 files, 157017 used, 26908 free (7796 frags, 2389 blocks, 4.2% fragmentation) > >/dev/rda0e: 2340 files, 21107 used, 58252 free (212 frags, 7255 blocks, 0.3% fragmentation) > > > >ccd0 was not configured the time I started fsck > > -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 12:30:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 97C221585E for ; Wed, 7 Apr 1999 12:30:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id VAA29932; Wed, 7 Apr 1999 21:28:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA67662; Wed, 7 Apr 1999 21:27:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bernd Walter Cc: freebsd-current@FreeBSD.ORG Subject: Re: fsck -p free() warnings on unconfigured drive In-reply-to: Your message of "Wed, 07 Apr 1999 21:15:08 +0200." <19990407211508.A27608@cicely8.cicely.de> Date: Wed, 07 Apr 1999 21:27:48 +0200 Message-ID: <67660.923513268@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990407211508.A27608@cicely8.cicely.de>, Bernd Walter writes: >On Wed, Apr 07, 1999 at 09:05:35PM +0200, Poul-Henning Kamp wrote: >> >> Yep. It would be very good if you could capture a preferably small >> image of a filesystem which makes this happen and make it available >> to the committers via a PR >> >nothing to capure - because there ist no filesystem. >I just needed to use fsck -p in single user mode without the need for any >ccd volume so ccd0 was not configured. Cool, even better then. Make a small shell script that does the needed stuff and send-pr the thing. It is always the most important bit of information to include in a PR: detailed instructions on how to reproduce it. And I mean detailed! the best thing is a shell-script. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 14:16: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 297D214DB9 for ; Wed, 7 Apr 1999 14:16:00 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id RAA74004; Wed, 7 Apr 1999 17:13:56 -0400 (EDT) Date: Wed, 7 Apr 1999 17:13:54 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "David O'Brien" Cc: Alex Zepeda , current@FreeBSD.ORG Subject: Re: RE: EGCS optimizations In-Reply-To: <19990406151633.A28346@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Apr 1999, David O'Brien wrote: > > Well what would be the chances of getting the pgcc patches committed? > > I'm quite interested in doing this, BUT only after the dust has settled > on the EGCS import and the Alpha build is fixed. Also the 1.1.2 PGCC > patches aren't available yet. > > jdp and I have another round of bootstraping to fix our current > less-than-optimal exception handling. I want to wait a week or so until > putting the changes into the tree. It's important to note that PGCC is NOWHERE NEAR production quality, last time I tried it, and not proven at all. I express no animosity toward PGCC itself, but unless it's been proven, I'd strongly oppose anything like this. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 16:23:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1787C14CE4 for ; Wed, 7 Apr 1999 16:23:26 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA25599; Thu, 8 Apr 1999 08:21:20 +0900 (JST) Message-ID: <370BE5B7.2A1561FC@newsguy.com> Date: Thu, 08 Apr 1999 08:09:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os References: <19990407193627.A68829@nagual.pp.ru> <370B84A4.3818F8A@newsguy.com> <19990407221941.A91075@nagual.pp.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > > The problem is deeper. When I reemove it, I got this error: > > -2100 bytes available > > it seems that boot2 needs to be reduced, and I don't know why it becomes > that big and what can be reduced. First candidates are static cmd[512] and > kernel[1024]. Please fix so it can be still compiled with gcc. I didn't see any changes to loader/boot[012] lately. EGCS requires -Os, but gcc should be able to compile it within limits, just like in -stable. Are you sure you didn't test with egcs after removing -Os? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 17: 6:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73]) by hub.freebsd.org (Postfix) with ESMTP id 977FC14E10 for ; Wed, 7 Apr 1999 17:06:36 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id EAA74903; Thu, 8 Apr 1999 04:04:33 +0400 (MSD) (envelope-from ache) Date: Thu, 8 Apr 1999 04:04:32 +0400 From: "Andrey A. Chernov" To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os Message-ID: <19990408040432.A74787@nagual.pp.ru> References: <19990407193627.A68829@nagual.pp.ru> <370B84A4.3818F8A@newsguy.com> <19990407221941.A91075@nagual.pp.ru> <370BE5B7.2A1561FC@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <370BE5B7.2A1561FC@newsguy.com>; from dcs@newsguy.com on Thu, Apr 08, 1999 at 08:09:43AM +0900 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 08, 1999 at 08:09:43AM +0900, Daniel C. Sobral wrote: > > -2100 bytes available > > > > it seems that boot2 needs to be reduced, and I don't know why it becomes > > that big and what can be reduced. First candidates are static cmd[512] and > > kernel[1024]. Please fix so it can be still compiled with gcc. > > I didn't see any changes to loader/boot[012] lately. EGCS requires > -Os, but gcc should be able to compile it within limits, just like > in -stable. Are you sure you didn't test with egcs after removing > -Os? Yes, of course I am shure. BTW, I see lots of malign options in cc call, maybe they play role. cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c /usr/src/sys/boot/i386/boot2/boot2.c -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 17:25:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-11-dbn.dial-up.net [196.34.155.75]) by hub.freebsd.org (Postfix) with ESMTP id D75C814F28 for ; Wed, 7 Apr 1999 17:25:36 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id CAA26034; Thu, 8 Apr 1999 02:18:07 +0200 (SAT) From: Robert Nordier Message-Id: <199904080018.CAA26034@ceia.nordier.com> Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <19990408040432.A74787@nagual.pp.ru> from "Andrey A. Chernov" at "Apr 8, 99 04:04:32 am" To: ache@nagual.pp.ru (Andrey A. Chernov) Date: Thu, 8 Apr 1999 02:18:05 +0200 (SAT) Cc: dcs@newsguy.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrey A. Chernov wrote: > On Thu, Apr 08, 1999 at 08:09:43AM +0900, Daniel C. Sobral wrote: > > > -2100 bytes available > > > > > > it seems that boot2 needs to be reduced, and I don't know why it becomes > > > that big and what can be reduced. First candidates are static cmd[512] and > > > kernel[1024]. Please fix so it can be still compiled with gcc. > > > > I didn't see any changes to loader/boot[012] lately. EGCS requires > > -Os, but gcc should be able to compile it within limits, just like > > in -stable. Are you sure you didn't test with egcs after removing > > -Os? > > Yes, of course I am shure. BTW, I see lots of malign options in cc call, > maybe they play role. > > cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin > -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall > -Waggregate-return -Wbad-function-cast -Wcast-align > -Wmissing-declarations -Wmissing-prototypes -Wnested-externs > -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c > /usr/src/sys/boot/i386/boot2/boot2.c Revision 1.12 of the Makefile contains option changes for egcs. If you want to use gcc, use rev 1.11 of the Makefile. (Jeez, guys!) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 17:25:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 6246715907 for ; Wed, 7 Apr 1999 17:25:52 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca12-101.ix.netcom.com [205.186.214.229]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id RAA03115; Wed, 7 Apr 1999 17:23:52 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id RAA84742; Wed, 7 Apr 1999 17:22:24 -0700 (PDT) Date: Wed, 7 Apr 1999 17:22:24 -0700 (PDT) Message-Id: <199904080022.RAA84742@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: asmodai@wxs.nl Cc: current@freebsd.org, obrien@NUXI.com In-reply-to: (message from Jeroen Ruigrok/Asmodai on Wed, 07 Apr 1999 19:10:58 +0200 (CEST)) Subject: Re: EGCS bootstrapping believed to be working From: asami@freebsd.org (Satoshi - the Wraith - Asami) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Weird that CoolEdit is on that list. * * I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both work * a-ok after patching up ltconfig to make shared libs. Did you click on the links to see what it's complaining about? "It worked here" doesn't mean much in this context, as the package building is done in a much more strict environment (empty /usr/local, PLIST checked (implicitly) by building package, etc.). -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 17:29:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A477E14F28 for ; Wed, 7 Apr 1999 17:29:44 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Apr 99 01:27:45 +0100 (BST) To: Greg Lehey Cc: freebsd-current@freebsd.org Subject: Re: New SiS 5591 ide chipset support. In-reply-to: Your message of "Wed, 07 Apr 1999 10:43:50 +0930." <19990407104350.S2142@lemis.com> X-Request-Do: Date: Thu, 08 Apr 1999 01:27:44 +0100 From: David Malone Message-ID: <9904080127.aa16592@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK - I've made a little progress. It only seems to be the first drive that it doesn't like. I can boot the system fine with the new kernel as long as I don't go near wd0. I dunno if it likes wd2. I've included what seem to be the useful bits of a boot -v as seen by dmesg for both the new and the old kernel. I'm not sure if the old kernel was doing DMA - I think it was as it says it configured some drives for DMA, but it also says: generic_status: no PCI IDE timing info available I can't see far enough into the machine at the moment to see what is written on any of thi chips, but I guess that can be figured out from the PCI probes. The motherboard is an el cheapo "P5SV-B Mainboard" with what has to be one of the least professional pieces of documentation I've ever seen as a manual. David. Old kernel PCI probe: ===================== Probing for devices on PCI bus 0: found-> vendor=0x1039, dev=0x5571, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x01 on pci0.0.0 found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x1039, dev=0x5513, revid=0xc1 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 000001f0, size 3 map[1]: type 4, range 32, base 000003f4, size 2 map[2]: type 4, range 32, base 00000170, size 3 map[3]: type 4, range 32, base 00000374, size 2 map[4]: type 4, range 32, base 00004000, size 4 ide_pci0: rev 0xc1 int a irq 14 on pci0.1.1 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 0 status: 64 from port: 00004002 ide_pci: ide0:0 has been configured for DMA by BIOS ide_pci: ide0:1 has been configured for DMA by BIOS generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 1 status: 04 from port: 0000400a found-> vendor=0x1039, dev=0x7001, revid=0xe0 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=9 found-> vendor=0x1002, dev=0x4750, revid=0x5c class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base e0000000, size 24 map[1]: type 4, range 32, base 00006000, size 8 map[2]: type 1, range 32, base e1000000, size 12 vga0: rev 0x5c on pci0.11.0 found-> vendor=0x10cd, dev=0x1300, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 00006100, size 8 map[1]: type 1, range 32, base e1001000, size 8 adv0: rev 0x03 int a irq 10 on pci0.13.0 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 16 Old kernel wd probe =================== wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): , 32-bit, multi-block-64 wd2: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0003, dmamword = 0101, apio = 0000, udma = 0000 wdc1: unit 1 (atapi): , removable, intr, iordis New kernel PCI probe ==================== Probing for devices on PCI bus 0: found-> vendor=0x1039, dev=0x5571, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x01 on pci0.0.0 found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x1039, dev=0x5513, revid=0xc1 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 000001f0, size 3 map[1]: type 4, range 32, base 000003f4, size 2 map[2]: type 4, range 32, base 00000170, size 3 map[3]: type 4, range 32, base 00000374, size 2 map[4]: type 4, range 32, base 00004000, size 4 ide_pci0: rev 0xc1 int a irq 14 on pci0.1.1 SiS 5591 status: CRTC 12 PCICLK, CATC 12 PCICLK, applies to all IDE devices SiS 5591 status: burst cycles enabled, fast post write control enabled SiS 5591 status: primary drive 0 DRTC 2 PCICLK, DATC 3 PCICLK SiS 5591 status: primary drive 0 Ultra DMA enabled, 1 PCICLK data out SiS 5591 status: primary drive 0 postwrite enabled, prefetch enabled prefetch count is 512 SiS 5591 status: primary drive 0 has been configured for DMA SiS 5591 status: primary drive 1 DRTC 2 PCICLK, DATC 3 PCICLK SiS 5591 status: primary drive 1 Ultra DMA enabled, 1 PCICLK data out SiS 5591 status: primary drive 1 postwrite enabled, prefetch enabled prefetch count is 512 SiS 5591 status: primary drive 1 has been configured for DMA ide_pci: busmaster 0 status: 64 from port: 00004002 ide_pci: ide0:0 has been configured for DMA by BIOS ide_pci: ide0:1 has been configured for DMA by BIOS SiS 5591 status: secondary drive 0 DRTC 10 PCICLK, DATC 6 PCICLK SiS 5591 status: secondary drive 0 Ultra DMA enabled, 1 PCICLK data out SiS 5591 status: secondary drive 0 postwrite enabled, prefetch enabled prefetch count is 512 SiS 5591 status: secondary drive 0 has not been configured for DMA SiS 5591 status: secondary drive 1 DRTC 3 PCICLK, DATC 4 PCICLK SiS 5591 status: secondary drive 1 Ultra DMA enabled, 1 PCICLK data out SiS 5591 status: secondary drive 1 postwrite disabled, prefetch disabled prefetch count is 512 SiS 5591 status: secondary drive 1 has not been configured for DMA ide_pci: busmaster 1 status: 04 from port: 0000400a found-> vendor=0x1039, dev=0x7001, revid=0xe0 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=9 found-> vendor=0x1002, dev=0x4750, revid=0x5c class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base e0000000, size 24 map[1]: type 4, range 32, base 00006000, size 8 map[2]: type 1, range 32, base e1000000, size 12 vga0: rev 0x5c on pci0.11.0 found-> vendor=0x10cd, dev=0x1300, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 00006100, size 8 map[1]: type 1, range 32, base e1001000, size 8 adv0: rev 0x03 int a irq 10 on pci0.13.0 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 16 New kernel wd probe: ==================== wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): , 32-bit, multi-block-64 wd2: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0003, dmamword = 0101, apio = 0000, udma = 0000 wdc1: unit 1 (atapi): , removable, intr, iordis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 17:39:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 15E14158F9 for ; Wed, 7 Apr 1999 17:39:14 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip189.houston13.tx.pub-ip.psi.net [38.27.213.189]) by leap.innerx.net (Postfix) with ESMTP id 77CFF37012; Wed, 7 Apr 1999 20:37:09 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id TAA22085; Wed, 7 Apr 1999 19:37:08 -0500 (CDT) (envelope-from chris) Date: Wed, 7 Apr 1999 19:37:07 -0500 From: Chris Costello To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: EGCS Message-ID: <19990407193707.D19995@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Kenneth Wayne Culver on Wed, Apr 07, 1999 at 01:13:04PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 7, 1999, Kenneth Wayne Culver wrote: > I can't get a make world to work with egcs. I deleted the whole obj > directory, and recvsuppped the entire source tree, and it still doesn't > work. Every time I cvsup I get a different error while compiling. CVSup now, and build world. Do _not_ attempt to build world with the -j flag, dependancies will fail to build properly and the compile will certainly fail. -Chris > > Please Help. > > Kenneth Culver > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ============================================= * "This process can check if this value is * * zero, and if it is, it does something * * child-like." -Forbes Burkowski, CS 454 * ============================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 17:51: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 40F7F15835 for ; Wed, 7 Apr 1999 17:51:05 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id RAA09352; Wed, 7 Apr 1999 17:49:05 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id RAA76863; Wed, 7 Apr 1999 17:49:04 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 7 Apr 1999 17:49:04 -0700 (PDT) Message-Id: <199904080049.RAA76863@vashon.polstra.com> To: asmodai@wxs.nl Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jeroen Ruigrok/Asmodai wrote: > This raises an interesting point I think. Do we need to maintain > gcc/egcs compatibility? Or do we, since we track CURRENT, say: > "alas, that's progression for ye?" Yep, alas, that's progression for ye. We have never supported mix & match of sourceballs from different releases. We do our best to support running old executables on newer systems, but that's a completely different issue. > Has there been an `official' consensus reached about this from core or > commiters? I am only speaking for John Polstra, a compiler guy, here. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 17:52:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CE0C415914 for ; Wed, 7 Apr 1999 17:52:24 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id RAA09367; Wed, 7 Apr 1999 17:50:25 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id RAA76881; Wed, 7 Apr 1999 17:50:24 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 7 Apr 1999 17:50:24 -0700 (PDT) Message-Id: <199904080050.RAA76881@vashon.polstra.com> To: ache@nagual.pp.ru Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <19990408040432.A74787@nagual.pp.ru> References: <19990407193627.A68829@nagual.pp.ru> <370B84A4.3818F8A@newsguy.com> <19990407221941.A91075@nagual.pp.ru> <370BE5B7.2A1561FC@newsguy.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990408040432.A74787@nagual.pp.ru>, Andrey A. Chernov wrote: > > Yes, of course I am shure. BTW, I see lots of malign options in cc call, > maybe they play role. > > cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin > -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall > -Waggregate-return -Wbad-function-cast -Wcast-align > -Wmissing-declarations -Wmissing-prototypes -Wnested-externs > -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c > /usr/src/sys/boot/i386/boot2/boot2.c You removed the "-Os" but you didn't add back the "-O2" that originally was there. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18: 1:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 1DEDC1592A for ; Wed, 7 Apr 1999 18:01:25 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca12-101.ix.netcom.com [205.186.214.229]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id RAA03258; Wed, 7 Apr 1999 17:59:26 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id RAA84894; Wed, 7 Apr 1999 17:58:11 -0700 (PDT) Date: Wed, 7 Apr 1999 17:58:11 -0700 (PDT) Message-Id: <199904080058.RAA84894@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: jdp@polstra.com Cc: asmodai@wxs.nl, current@freebsd.org In-reply-to: <199904080049.RAA76863@vashon.polstra.com> (message from John Polstra on Wed, 7 Apr 1999 17:49:04 -0700 (PDT)) Subject: Re: /sys/boot, egcs vs. gcc, -Os From: asami@freebsd.org (Satoshi - the Wraith - Asami) References: <199904080049.RAA76863@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: John Polstra * Yep, alas, that's progression for ye. We have never supported mix * & match of sourceballs from different releases. We do our best * to support running old executables on newer systems, but that's a * completely different issue. : * I am only speaking for John Polstra, a compiler guy, here. Speaking for Satoshi Asami, the ports guy, I agree with John. I for one will hate to see the ports people having to worry about 4.0-gcc (they already have 4.0-egcs and 3.1-gcc to worry about...). -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18: 2: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5431A14C46 for ; Wed, 7 Apr 1999 18:02:07 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id RAA07000; Wed, 7 Apr 1999 17:59:52 -0700 (PDT) (envelope-from obrien) Message-ID: <19990407175951.A6979@nuxi.com> Date: Wed, 7 Apr 1999 17:59:51 -0700 From: "David O'Brien" To: Chan Yiu Wah , freebsd-current@FreeBSD.ORG Subject: Re: make world error with ctm src-cur.3819 Reply-To: obrien@NUXI.com References: <199904071414.WAA29134@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904071414.WAA29134@b1.hkstar.com>; from Chan Yiu Wah on Wed, Apr 07, 1999 at 10:14:47PM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just wanted to make egcs as the default compiler and tried to make world ... > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: linux.h: No such file or directory The fact you are refering to "linux.h" says you've some kind of error... I never commited linux.h or refered to it in what I commited. IF you grabed my earily EGCS from my personal machine, then you could have this reference. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18: 2:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (nagual.pp.ru [193.125.27.73]) by hub.freebsd.org (Postfix) with ESMTP id E22C714E1A for ; Wed, 7 Apr 1999 18:02:10 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id FAA75506; Thu, 8 Apr 1999 05:00:05 +0400 (MSD) (envelope-from ache) Date: Thu, 8 Apr 1999 05:00:05 +0400 From: "Andrey A. Chernov" To: John Polstra Cc: current@freebsd.org Subject: Re: /sys/boot, egcs vs. gcc, -Os Message-ID: <19990408050005.A75477@nagual.pp.ru> References: <19990407193627.A68829@nagual.pp.ru> <370B84A4.3818F8A@newsguy.com> <19990407221941.A91075@nagual.pp.ru> <370BE5B7.2A1561FC@newsguy.com> <19990408040432.A74787@nagual.pp.ru> <199904080050.RAA76881@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904080050.RAA76881@vashon.polstra.com>; from jdp@polstra.com on Wed, Apr 07, 1999 at 05:50:24PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 07, 1999 at 05:50:24PM -0700, John Polstra wrote: > You removed the "-Os" but you didn't add back the "-O2" that > originally was there. Thanx, it works now. It was the reason I overlook. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18: 4:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 50D661592A for ; Wed, 7 Apr 1999 18:04:48 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA07029 for freebsd-current@FreeBSD.ORG; Wed, 7 Apr 1999 18:02:49 -0700 (PDT) (envelope-from obrien) Message-ID: <19990407180248.B6979@nuxi.com> Date: Wed, 7 Apr 1999 18:02:48 -0700 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: Re: DES from source? Reply-To: obrien@NUXI.com References: <19990407105126.A6886@sanyusan.se> <199904070907.RAA10768@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904070907.RAA10768@spinner.netplex.com.au>; from Peter Wemm on Wed, Apr 07, 1999 at 05:07:25PM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Of course, passwd(1) should ideally be able to be told to ignore the old > method too - it looks like /etc/auth.conf is in the beginnings of this. When I proposed changing this and adding a knob in auth.conf, it was said PAM is really the place for this. Actually a committed (forgot who) tried to overhall the crypt stuff a few months ago and it blew up in his face. I don't think anyone has changed since. A shame. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18:16: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 8525014C46 for ; Wed, 7 Apr 1999 18:16:02 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA15050; Wed, 7 Apr 1999 21:10:45 -0400 (EDT) Date: Wed, 7 Apr 1999 21:10:45 -0400 (EDT) From: Chuck Robey To: chris@calldei.com Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: EGCS In-Reply-To: <19990407193707.D19995@holly.dyndns.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, Chris Costello wrote: > On Wed, Apr 7, 1999, Kenneth Wayne Culver wrote: > > I can't get a make world to work with egcs. I deleted the whole obj > > directory, and recvsuppped the entire source tree, and it still doesn't > > work. Every time I cvsup I get a different error while compiling. > > CVSup now, and build world. Do _not_ attempt to build world with > the -j flag, dependancies will fail to build properly and the compile > will certainly fail. And note that there have been several little bugs that have been cleared already, so if it doesn't do it the first time, have faith and cvsup again. It's built twice bad for me (the first 2 times) and since, twice good. > > -Chris > > > > > Please Help. > > > > Kenneth Culver > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > ============================================= > * "This process can check if this value is * > * zero, and if it is, it does something * > * child-like." -Forbes Burkowski, CS 454 * > ============================================= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18:23:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 8718F14D54 for ; Wed, 7 Apr 1999 18:23:05 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA15082; Wed, 7 Apr 1999 21:19:00 -0400 (EDT) Date: Wed, 7 Apr 1999 21:18:59 -0400 (EDT) From: Chuck Robey To: John Polstra Cc: asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <199904080049.RAA76863@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, John Polstra wrote: > In article , Jeroen > Ruigrok/Asmodai wrote: > > > This raises an interesting point I think. Do we need to maintain > > gcc/egcs compatibility? Or do we, since we track CURRENT, say: > > "alas, that's progression for ye?" > > Yep, alas, that's progression for ye. We have never supported mix > & match of sourceballs from different releases. We do our best > to support running old executables on newer systems, but that's a > completely different issue. > > > Has there been an `official' consensus reached about this from core or > > commiters? > > I am only speaking for John Polstra, a compiler guy, here. John, no complaint (I figure some recompiling is the cost of running current) but could you please repost here some stuff that I think you said once already? I'm sorry, but I have an error, and I want to make sure it's recompile time. Here's the last part of the dump: configure:4096: /bin/sh ./libtool --silent --mode=link c++ -o conftest -Os -pipe -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include -I/usr/l ocal/include/giflib -s -L/usr/local/lib -L/usr/X11R6/lib conftest.C -lkdecore -lqt -lXext -lX11 -rpath /usr/local/lib -rpath /usr/X11R6/lib 1>&5 /usr/libexec/elf/ld: warning: libstdc++.so.2, needed by /usr/local/lib/libkdecore.so, may conflict with libstdc++.so.3 /usr/lib/libstdc++.so.2: undefined reference to `__unwind_function' /usr/lib/libstdc++.so.2: undefined reference to `__find_first_exception_table_match' /usr/local/lib/libkdecore.so: undefined reference to `_vt$11QPushButton$12QPaint Device' /usr/lib/libstdc++.so.2: undefined reference to `__register_exceptions' /usr/local/lib/libkdecore.so: undefined reference to `_vt$11QPushButton' I thought you had patched ld-elf.so.1 so this (__register_exceptions) wouldn't get hit again, but maybe I'm wrong, could you please bang me on the head with the story, and THIS TIME I'll try to remember it? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18:38: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id BE57315871 for ; Wed, 7 Apr 1999 18:37:37 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA09573; Wed, 7 Apr 1999 18:35:34 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id SAA76999; Wed, 7 Apr 1999 18:35:34 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 07 Apr 1999 18:35:34 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Chuck Robey Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG, asmodai@wxs.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > configure:4096: /bin/sh ./libtool --silent --mode=link c++ -o conftest -Os -pipe > -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include -I/usr/l > ocal/include/giflib -s -L/usr/local/lib -L/usr/X11R6/lib conftest.C -lkdecore > -lqt -lXext -lX11 -rpath /usr/local/lib -rpath /usr/X11R6/lib 1>&5 > /usr/libexec/elf/ld: warning: libstdc++.so.2, needed by > /usr/local/lib/libkdecore.so, may conflict with libstdc++.so.3 Bzzt. You've got something old that's still using libstdc++.so.2. You can't combine that with something that uses libstdc++.so.3. I.e., you can't use both versions at the same time. I'd suggest rebuilding the port and everything that it depends upon. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18:44:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id A26DC14E54 for ; Wed, 7 Apr 1999 18:44:20 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA15157; Wed, 7 Apr 1999 21:40:23 -0400 (EDT) Date: Wed, 7 Apr 1999 21:40:23 -0400 (EDT) From: Chuck Robey To: John Polstra Cc: current@FreeBSD.ORG, asmodai@wxs.nl Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, John Polstra wrote: > Chuck Robey wrote: > > > configure:4096: /bin/sh ./libtool --silent --mode=link c++ -o conftest -Os -pipe > > -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include -I/usr/l > > ocal/include/giflib -s -L/usr/local/lib -L/usr/X11R6/lib conftest.C -lkdecore > > -lqt -lXext -lX11 -rpath /usr/local/lib -rpath /usr/X11R6/lib 1>&5 > > /usr/libexec/elf/ld: warning: libstdc++.so.2, needed by > > /usr/local/lib/libkdecore.so, may conflict with libstdc++.so.3 > > Bzzt. You've got something old that's still using libstdc++.so.2. > You can't combine that with something that uses libstdc++.so.3. I.e., > you can't use both versions at the same time. I'd suggest rebuilding > the port and everything that it depends upon. Thanks for the clue, John! As much as I hate redoing the KDE and gnome ports, it looks like doing that again ... > > John > --- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18:46:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7091415054 for ; Wed, 7 Apr 1999 18:46:47 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA09646; Wed, 7 Apr 1999 18:44:48 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id SAA77016; Wed, 7 Apr 1999 18:44:47 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 07 Apr 1999 18:44:47 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Chuck Robey Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: asmodai@wxs.nl, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > Thanks for the clue, John! As much as I hate redoing the KDE and > gnome ports, it looks like doing that again ... I don't blame you. I've never even built them, for the simple (lazy) reason that they looked like they'd be too painful to upgrade. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 18:54:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id AF7B014C3D for ; Wed, 7 Apr 1999 18:54:36 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA28698; Wed, 7 Apr 1999 21:48:30 -0400 (EDT) Date: Wed, 7 Apr 1999 21:48:30 -0400 (EDT) From: Chuck Robey To: John Polstra Cc: asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, John Polstra wrote: > Chuck Robey wrote: > > > Thanks for the clue, John! As much as I hate redoing the KDE and > > gnome ports, it looks like doing that again ... > > I don't blame you. I've never even built them, for the simple (lazy) > reason that they looked like they'd be too painful to upgrade. I'm very close to relying on packages for them. I'll have to see if there are *very* up-to-date packages. If there aren't, and I end up having to rebuild the mess, would you want to pack up some packages from me? They'll be strictly current-based, and I won't bother you until a collection is complete (if you have interest .. some are interesting). Understand I'll probably take at least 10 days to do this. > > John > --- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 19: 1: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 60E4A14E2A for ; Wed, 7 Apr 1999 19:01:08 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca12-101.ix.netcom.com [205.186.214.229]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id SAA03333; Wed, 7 Apr 1999 18:59:07 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id SAA85199; Wed, 7 Apr 1999 18:58:13 -0700 (PDT) Date: Wed, 7 Apr 1999 18:58:13 -0700 (PDT) Message-Id: <199904080158.SAA85199@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: chuckr@mat.net Cc: jdp@polstra.com, asmodai@wxs.nl, current@FreeBSD.ORG In-reply-to: (message from Chuck Robey on Wed, 7 Apr 1999 21:48:30 -0400 (EDT)) Subject: Re: /sys/boot, egcs vs. gcc, -Os From: asami@FreeBSD.ORG (Satoshi - the Wraith - Asami) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Chuck Robey * I'm very close to relying on packages for them. I'll have to see if * there are *very* up-to-date packages. If there aren't, and I end up As long as they build, FTP packages are usually within one week (usually less) of the ports tree on both 3.1 and 4.0. -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 20: 0: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 4F54E15177 for ; Wed, 7 Apr 1999 20:00:06 -0700 (PDT) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id XAA00404 for current@freebsd.org; Wed, 7 Apr 1999 23:17:32 -0400 (EDT) (envelope-from dervish) Date: Wed, 7 Apr 1999 23:17:32 -0400 From: Natty Rebel To: current@freebsd.org Subject: System hangs when booting with (update5) of ata/atapi driver Message-ID: <19990407231732.A350@ikhala.tcimet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 2C CE A5 D7 FA 4D D5 FD 9A CC 2B 23 04 46 48 F8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG my system hangs when booting with update5 of the ata/atapi driver with the following in my kernel config: controller ata0 device atadisk0 # ATA disks device atapifd0 # ATAPI floppy drives the boot messages: Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 ata-pci0: rev 0xd0 int a irq 14 on pci0.0.1 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq on ata-pci0 chip1: rev 0x01 on pci0.1.0 chip2: rev 0x00 on pci0.2.0 [snippage ...] ata0: master: setting up generic WDMA2 mode OK ad0: ATA-3 disk at ata0 as master ad0: 3039MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s1a and then the system hangs. pressing reset and booting /kernel.old brings it back to life. now with the following entries in my kernel config: controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x80ff80ff disk wd0 at wdc0 drive 0 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM i get the following on boot and all is well ... Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 ide_pci0: rev 0xd0 int a irq 14 on pci0.0.1 chip1: rev 0x01 on pci0.1.0 chip2: rev 0x00 on pci0.2.0 [snip ...] wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 3093MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S my motherboard is a gigabyte ga-5sg11 with SIS 5591/5595 chipset.. hope this info is helpful ... #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 20:10:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 8EC9E1513A for ; Wed, 7 Apr 1999 20:10:43 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA02002; Thu, 8 Apr 1999 13:08:29 +1000 Date: Thu, 8 Apr 1999 13:08:29 +1000 From: Bruce Evans Message-Id: <199904080308.NAA02002@godzilla.zeta.org.au> To: ache@nagual.pp.ru, jdp@polstra.com Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> it seems that boot2 needs to be reduced, and I don't know why it becomes >> that big and what can be reduced. First candidates are static cmd[512] and >> kernel[1024]. Please fix so it can be still compiled with gcc. > >Why? The compiler in -current is egcs, not gcc. If you want to >use the old compiler, then use the old sources for boot too. Everything should be buildable with CC=aac (any ANSI compiler), but that's asking too much for programs like kernels and boot blocks. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 20:19:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A38A9151CA for ; Wed, 7 Apr 1999 20:19:54 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id UAA09960; Wed, 7 Apr 1999 20:17:54 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id UAA77210; Wed, 7 Apr 1999 20:17:53 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904080308.NAA02002@godzilla.zeta.org.au> Date: Wed, 07 Apr 1999 20:17:53 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Bruce Evans Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > Everything should be buildable with CC=aac (any ANSI compiler), but > that's asking too much for programs like kernels and boot blocks. The problem in this case is just that the compilers require different command line options. It's asking _way_ too much to require those to be identical. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 20:29:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 8B15D15223 for ; Wed, 7 Apr 1999 20:29:12 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA03975; Thu, 8 Apr 1999 13:27:12 +1000 Date: Thu, 8 Apr 1999 13:27:12 +1000 From: Bruce Evans Message-Id: <199904080327.NAA03975@godzilla.zeta.org.au> To: bde@zeta.org.au, jdp@polstra.com Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Everything should be buildable with CC=aac (any ANSI compiler), but >> that's asking too much for programs like kernels and boot blocks. > >The problem in this case is just that the compilers require >different command line options. It's asking _way_ too much to >require those to be identical. Actually, they don't. Compiler-specific options can be put in ${CC}. Perhaps they even should be. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 20:34:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A7C4115228 for ; Wed, 7 Apr 1999 20:34:25 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id UAA10086; Wed, 7 Apr 1999 20:32:25 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id UAA77280; Wed, 7 Apr 1999 20:32:25 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904080327.NAA03975@godzilla.zeta.org.au> Date: Wed, 07 Apr 1999 20:32:25 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Bruce Evans Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: >>The problem in this case is just that the compilers require >>different command line options. It's asking _way_ too much to >>require those to be identical. > > Actually, they don't. Compiler-specific options can be put in ${CC}. > Perhaps they even should be. But in this case, we want "-Os" (egcs) or "-O2" (gcc) only for building boot -- not for everything. It could be parameterized with make macros like "OPT_SMALL" and "OPT_FAST" in the *.mk files, I suppose. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 20:50:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 78BC815228 for ; Wed, 7 Apr 1999 20:50:52 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem11.masternet.it [194.184.65.21]) by kirk.giovannelli.it (8.9.2/8.9.2) with SMTP id DAA16697 for ; Thu, 8 Apr 1999 03:48:49 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990408054254.00a4ab80@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 08 Apr 1999 05:49:52 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: ftp hangs on -current Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "ftp" on 4.0-very-current (post egcs make world) randomly hangs during sessions... I never succeded in finishing a session lately. To transfer some files from my home to my isp server I had to do an "ftp" from the server and a "get" to them... The ftp server works normally and fetch is ok ... Probably it is a fault of my system, if no other experiences it. Thanks for attention... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 21:11: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-4.ppp.wenet.net [206.15.85.4]) by hub.freebsd.org (Postfix) with ESMTP id DEECD1525B for ; Wed, 7 Apr 1999 21:11:04 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id VAA26787; Wed, 7 Apr 1999 21:09:16 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Wed, 7 Apr 1999 21:09:16 -0700 (PDT) From: Alex Zepeda To: Chuck Robey Cc: current Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, Chuck Robey wrote: > > Bzzt. You've got something old that's still using libstdc++.so.2. > > You can't combine that with something that uses libstdc++.so.3. I.e., > > you can't use both versions at the same time. I'd suggest rebuilding > > the port and everything that it depends upon. > > Thanks for the clue, John! As much as I hate redoing the KDE and gnome > ports, it looks like doing that again ... That was one of the BIG pitfalls of egcs, binary incompatable C++ programs and libs. Sounds like you're overdue for your favorite shot of caffiene. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 21:12:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-4.ppp.wenet.net [206.15.85.4]) by hub.freebsd.org (Postfix) with ESMTP id D51191562E for ; Wed, 7 Apr 1999 21:12:43 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id VAA26798; Wed, 7 Apr 1999 21:10:43 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Wed, 7 Apr 1999 21:10:43 -0700 (PDT) From: Alex Zepeda To: John Polstra Cc: Chuck Robey , asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, John Polstra wrote: > Chuck Robey wrote: > > > Thanks for the clue, John! As much as I hate redoing the KDE and > > gnome ports, it looks like doing that again ... > > I don't blame you. I've never even built them, for the simple (lazy) > reason that they looked like they'd be too painful to upgrade. Bah, if the ports-tree can make building Gnome easy, it's hardly painful (and I know KDE is easy to build from tarballs). It just takes a bit of patience. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 21:38:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id BFF1E1528A for ; Wed, 7 Apr 1999 21:38:25 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA11412; Thu, 8 Apr 1999 14:36:24 +1000 Date: Thu, 8 Apr 1999 14:36:24 +1000 From: Bruce Evans Message-Id: <199904080436.OAA11412@godzilla.zeta.org.au> To: bde@zeta.org.au, jdp@polstra.com Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Actually, they don't. Compiler-specific options can be put in ${CC}. >> Perhaps they even should be. > >But in this case, we want "-Os" (egcs) or "-O2" (gcc) only for >building boot -- not for everything. It could be parameterized with >make macros like "OPT_SMALL" and "OPT_FAST" in the *.mk files, I >suppose. "CC+=-Os" in individual Makefiles works about as well as "CFLAGS+=-Os" for adding flags. That's not very well. Removing unwanted additions is hard. BTW, boot2/Makefile uses "CFLAGS=" to override any previous definition of CFLAGS. This may break `make world' by removing -nostdinc. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 22:19:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 7BF38152FD; Wed, 7 Apr 1999 22:19:48 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.26]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA5E5B; Thu, 8 Apr 1999 07:17:48 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id HAA63028; Thu, 8 Apr 1999 07:17:55 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904080022.RAA84742@silvia.hip.berkeley.edu> Date: Thu, 08 Apr 1999 07:17:55 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: (Satoshi - the Wraith - Asami) Subject: Re: EGCS bootstrapping believed to be working Cc: obrien@NUXI.com, current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Apr-99 Satoshi - the Wraith - Asami wrote: > * Weird that CoolEdit is on that list. > * > * I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both > work > * a-ok after patching up ltconfig to make shared libs. > > Did you click on the links to see what it's complaining about? > > "It worked here" doesn't mean much in this context, as the package > building is done in a much more strict environment (empty /usr/local, > PLIST checked (implicitly) by building package, etc.). Sure it means much, I am the libtool nagging guy *g* This means that I always verify ltconfig. Now go look at the cooledit logs, someone forgot to patch ltconfig to create shared libraries. The patch is straightforward and I believe 3.9.0 has this incorporated and else maintainer oughtta be nagging the programmers about migrating to libtool 1.2f to at least solve the shared library problem on FreeBSD 4.x. Probably tons of others in that list... I will look at the log today and give ye an oversight of the ltconfig problemcases... --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 23: 6:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 66310153BC for ; Wed, 7 Apr 1999 23:06:33 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA62174; Wed, 7 Apr 1999 23:04:48 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Bruce Evans Cc: jdp@polstra.com, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-reply-to: Your message of "Thu, 08 Apr 1999 13:27:12 +1000." <199904080327.NAA03975@godzilla.zeta.org.au> Date: Wed, 07 Apr 1999 23:04:48 -0700 Message-ID: <62172.923551488@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, they don't. Compiler-specific options can be put in ${CC}. I'm leading him... leading... *BLAM!* *BLAM!* Yes! Got him with both barrels, and he was really moving too! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 23:17: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (c1-64-dbn.dial-up.net [196.34.155.64]) by hub.freebsd.org (Postfix) with ESMTP id BCFD8153BC for ; Wed, 7 Apr 1999 23:16:49 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id IAA26867; Thu, 8 Apr 1999 08:09:24 +0200 (SAT) From: Robert Nordier Message-Id: <199904080609.IAA26867@ceia.nordier.com> Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: from John Polstra at "Apr 7, 99 08:17:53 pm" To: jdp@polstra.com (John Polstra) Date: Thu, 8 Apr 1999 08:09:22 +0200 (SAT) Cc: bde@zeta.org.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > Bruce Evans wrote: > > > Everything should be buildable with CC=aac (any ANSI compiler), but > > that's asking too much for programs like kernels and boot blocks. > > The problem in this case is just that the compilers require > different command line options. It's asking _way_ too much to > require those to be identical. The main issue with supporting both gcc and egcs -- at least beyond the next few weeks -- is really that they have different optimization characteristics. Space is sufficiently tight in boot2 that it's often been necessary to refer to the emitted code, and move C statements around, or do things like change ints to chars, just to get everything to fit. So supporting anything other than egcs is likely to become much more than a makefile problem. Also for reasons of space, internal boot2 functions in assembly language require use of a non-standard calling convention (the called functions pop argument from the stack), so ability to use some arbitrary ISO compiler can't be guaranteed on principle, and is fairly unlikely in practice. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 7 23:22:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 586C71587D for ; Wed, 7 Apr 1999 23:22:26 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id IAA89646; Thu, 8 Apr 1999 08:20:24 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id IAA02081; Thu, 8 Apr 1999 08:20:23 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904080620.IAA02081@greenpeace.grondar.za> To: obrien@NUXI.com Cc: freebsd-current@freebsd.org Subject: Re: DES from source? In-Reply-To: Your message of " Wed, 07 Apr 1999 18:02:48 MST." <19990407180248.B6979@nuxi.com> References: <19990407105126.A6886@sanyusan.se> <199904070907.RAA10768@spinner.netplex.com.au> <19990407180248.B6979@nuxi.com> Date: Thu, 08 Apr 1999 08:20:22 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > Actually a committed (forgot who) tried to overhall the crypt stuff a few > months ago and it blew up in his face. I don't think anyone has changed > since. A shame. Brandon Gillespie. I have a copy of his code (almost) ready-to-go. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 0:43: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 266671597D for ; Thu, 8 Apr 1999 00:42:55 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id JAA20891; Thu, 8 Apr 1999 09:40:51 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id JAA63737; Thu, 8 Apr 1999 09:13:47 +0200 (CEST) (envelope-from andreas) Date: Thu, 8 Apr 1999 09:13:47 +0200 From: Andreas Klemm To: Jeroen Ruigrok/Asmodai Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: EGCS Message-ID: <19990408091346.A63654@titan.klemm.gtn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Wed, Apr 07, 1999 at 07:17:42PM +0200 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 07, 1999 at 07:17:42PM +0200, Jeroen Ruigrok/Asmodai wrote: > On 07-Apr-99 Kenneth Wayne Culver wrote: > > I can't get a make world to work with egcs. I deleted the whole obj > > directory, and recvsuppped the entire source tree, and it still doesn't > > work. Every time I cvsup I get a different error while compiling. > > OK, make sure ye go to /usr/src/gnu/usr.bin/cc first > > make clean, make obj, make depend, make, make install > > then try the libs in /usr/src/lib/ with roughly the same make targets. > > Then try to make a world again. remove /usr/include and build it freshly before doing the above with make includes I remeember somebody mentioned, that there might be some old header files .... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 1: 5:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from tube.ors.kirov.ru (gw-lepse.kirov.ru [194.84.203.204]) by hub.freebsd.org (Postfix) with ESMTP id A5CE414C30 for ; Thu, 8 Apr 1999 01:04:58 -0700 (PDT) (envelope-from alex@ors.kirov.ru) Received: from ors.kirov.ru (alex.ors.kirov.ru [194.84.150.3]) by tube.ors.kirov.ru (8.9.3/ors-1.3.76) with ESMTP id MAA08446 for ; Thu, 8 Apr 1999 12:02:51 +0400 Message-ID: <370C6284.923A9E1A@ors.kirov.ru> Date: Thu, 08 Apr 1999 12:02:13 +0400 From: "Alexey J. Suvorov" Organization: ORS Company X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 1:32: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 93F85158A5 for ; Thu, 8 Apr 1999 01:32:03 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id BAA15251; Thu, 8 Apr 1999 01:29:47 -0700 (PDT) (envelope-from obrien) Message-ID: <19990408012947.A15235@nuxi.com> Date: Thu, 8 Apr 1999 01:29:47 -0700 From: "David O'Brien" To: Andreas Klemm , Jeroen Ruigrok/Asmodai Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: EGCS Reply-To: obrien@NUXI.com References: <19990408091346.A63654@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990408091346.A63654@titan.klemm.gtn.com>; from Andreas Klemm on Thu, Apr 08, 1999 at 09:13:47AM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > remove /usr/include and build it freshly before doing the above with > > make includes cd /usr/src make -DCLOBBER includes is the perfered method. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 3: 9:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id D22B81505C for ; Thu, 8 Apr 1999 03:09:24 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async3-32.iptelecom.net.ua [212.42.68.223]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id NAA14068 for ; Thu, 8 Apr 1999 13:07:26 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id NAA32083 for ; Thu, 8 Apr 1999 13:07:19 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <370C7EFC.81D6FBC7@altavista.net> Date: Thu, 08 Apr 1999 13:03:41 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: EGCS -O2 vs -Os optimisation on kernels Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that -Os is not wery effective on kernels: -O2: -r-xr-xr-x  1 root  wheel  1418829 Apr  6 16:50 kernel    text    data     bss     dec     hex filename 1044102  111964  123592 1279658  1386aa kernel -Os: -rwxr-xr-x  1 root  wheel  1411885 Apr  8 12:57 kernel    text    data     bss     dec     hex filename 1037138  111960  123592 1272690  136b72 kernel   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 4:59:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 0500D14E1A for ; Thu, 8 Apr 1999 04:59:14 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async3-12.iptelecom.net.ua [212.42.68.204]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id OAA19836 for ; Thu, 8 Apr 1999 14:57:17 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id OAA62829 for ; Thu, 8 Apr 1999 14:57:09 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <370C9920.962266C4@altavista.net> Date: Thu, 08 Apr 1999 14:55:13 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: EGCS troubles Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, While this problem might not belongs to this list however it is difficult in this case to distinguish exactly. Something broken in new egcs c++ compiler - jade doesn't work with following symptoms (checked on two machines). ===> handbook /usr/local/bin/jade -V html-manifest -ioutput.html  -c ../../share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/ docbook/3.0/catalog -c /usr/local/share/sgml/jade/catalog -d ../../share/sgml/fr eebsd.dsl -t sgml handbook.sgml *** Signal 11 Interesting that when it was compiled using pgcc port it worked just fine. Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 5:22:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (Postfix) with ESMTP id 9CA39159A6 for ; Thu, 8 Apr 1999 05:22:19 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.9.3/8.9.3) with ESMTP id IAA25389 for ; Thu, 8 Apr 1999 08:20:18 -0400 (EDT) Date: Thu, 8 Apr 1999 08:20:18 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: freebsd-current@freebsd.org Subject: make world breakage Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trying to make world today and last night, with fairly up-to-the-minute source, I keep bombing out with: `/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/i386. md' is up to date. `genattr.c' is up to date. `gencodes.c' is up to date. `genconfig.c' is up to date. `genemit.c' is up to date. `genextract.c' is up to date. `genflags.c' is up to date. `genopinit.c' is up to date. `genoutput.c' is up to date. `genpeep.c' is up to date. `genrecog.c' is up to date. `gencheck.c' is up to date. `gengenrtl.c' is up to date. `gengenrtl.c' is up to date. `gengenrtl.c' is up to date. `genattrtab.c' is up to date. `gencheck.c' is up to date. `c-parse.in' is up to date. `gencheck.c' is up to date. `c-parse.in' is up to date. ===> cc_int make: don't know how to make insn-attrtab.c. Stop *** Error code 2 Does anyone know why this might be the case? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 5:28: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4039F159C1 for ; Thu, 8 Apr 1999 05:27:57 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA88439; Thu, 8 Apr 1999 14:25:54 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904081225.OAA88439@freebsd.dk> Subject: Re: make world breakage In-Reply-To: from Snob Art Genre at "Apr 8, 1999 8:20:18 am" To: ben@rosengart.com Date: Thu, 8 Apr 1999 14:25:54 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Snob Art Genre wrote: Dont use -jN on the make world, that broke with the EGCS import. > Trying to make world today and last night, with fairly up-to-the-minute > source, I keep bombing out with: > > `/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/i386. > md' is up to date. > `genattr.c' is up to date. > `gencodes.c' is up to date. > `genconfig.c' is up to date. > `genemit.c' is up to date. > `genextract.c' is up to date. > `genflags.c' is up to date. > `genopinit.c' is up to date. > `genoutput.c' is up to date. > `genpeep.c' is up to date. > `genrecog.c' is up to date. > `gencheck.c' is up to date. > `gengenrtl.c' is up to date. > `gengenrtl.c' is up to date. > `gengenrtl.c' is up to date. > `genattrtab.c' is up to date. > `gencheck.c' is up to date. > `c-parse.in' is up to date. > `gencheck.c' is up to date. > `c-parse.in' is up to date. > ===> cc_int > make: don't know how to make insn-attrtab.c. Stop > *** Error code 2 > > Does anyone know why this might be the case? > > > Ben > > "You have your mind on computers, it seems." > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 5:35:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 32B7414C28 for ; Thu, 8 Apr 1999 05:35:40 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async2-12.iptelecom.net.ua [212.42.68.140]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id PAA21845; Thu, 8 Apr 1999 15:33:44 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id PAA68107; Thu, 8 Apr 1999 15:33:36 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <370CA21F.C668B4A2@altavista.net> Date: Thu, 08 Apr 1999 15:33:35 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: ben@rosengart.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world breakage References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please don't disregard to read rpevious messages from this list! As it was pointed earlier make world now fails if -jN option used. Try to build without -j.   Snob Art Genre wrote: > Trying to make world today and last night, with fairly up-to-the-minute > source, I keep bombing out with: > > `/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/i386. > md' is up to date. > `genattr.c' is up to date. > `gencodes.c' is up to date. > `genconfig.c' is up to date. > `genemit.c' is up to date. > `genextract.c' is up to date. > `genflags.c' is up to date. > `genopinit.c' is up to date. > `genoutput.c' is up to date. > `genpeep.c' is up to date. > `genrecog.c' is up to date. > `gencheck.c' is up to date. > `gengenrtl.c' is up to date. > `gengenrtl.c' is up to date. > `gengenrtl.c' is up to date. > `genattrtab.c' is up to date. > `gencheck.c' is up to date. > `c-parse.in' is up to date. > `gencheck.c' is up to date. > `c-parse.in' is up to date. > ===> cc_int > make: don't know how to make insn-attrtab.c. Stop > *** Error code 2 > > Does anyone know why this might be the case? > >  Ben > > "You have your mind on computers, it seems." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 5:42:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (Postfix) with ESMTP id 86CDC14C28 for ; Thu, 8 Apr 1999 05:42:32 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.9.3/8.9.3) with ESMTP id IAA29042; Thu, 8 Apr 1999 08:40:03 -0400 (EDT) Date: Thu, 8 Apr 1999 08:40:03 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Maxim Sobolev Cc: ben@rosengart.com, freebsd-current@FreeBSD.ORG Subject: Re: make world breakage In-Reply-To: <370CA21F.C668B4A2@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, Maxim Sobolev wrote: > Please don't disregard to read rpevious messages from this list! Sorry, I just started running current again the other day, I didn't re-subscribe until last night. > As it was pointed earlier make world now fails if -jN option used. >Try to build without -j. OK, thank you. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 9:35:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 42A1615A6E for ; Thu, 8 Apr 1999 09:35:36 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id MAA16091; Thu, 8 Apr 1999 12:31:24 -0400 (EDT) Date: Thu, 8 Apr 1999 12:31:24 -0400 (EDT) From: Chuck Robey To: Alex Zepeda Cc: John Polstra , asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, Alex Zepeda wrote: > On Wed, 7 Apr 1999, John Polstra wrote: > > > Chuck Robey wrote: > > > > > Thanks for the clue, John! As much as I hate redoing the KDE and > > > gnome ports, it looks like doing that again ... > > > > I don't blame you. I've never even built them, for the simple (lazy) > > reason that they looked like they'd be too painful to upgrade. > > Bah, if the ports-tree can make building Gnome easy, it's hardly painful > (and I know KDE is easy to build from tarballs). It just takes a bit of > patience. If that were true, but it's not. Older versions of the config files and libraries can very easily cause the ports to fail to build. Every time I upgrade stuff, I have to go about doing search and destroy on old stuff. On top of that, there are various mistakes in dependencies; there's one lib (I forget which) which installs under one name, but all of the dependencies on it are under another name. The stuff seems to change it's mind on whether it wants to install under /usr/local or /usr/X11R6, so finding stuff is pretty complicated, and very dependent on version, because the darn install dirs change, just to make things worse. When Satoshi builds stuff, it's in a real clean environment, but in fact, all the gnome and kde ports are extraordinarly sensitive to stuff from older ports hanging around. That's why folks are wary of upgrading those guys. The gnome stuff is really neat, else I'd never even bother. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 9:46:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 313F515A75 for ; Thu, 8 Apr 1999 09:46:26 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA18124 for current@freebsd.org; Thu, 8 Apr 1999 09:44:22 -0700 (PDT) (envelope-from obrien) Message-ID: <19990408094422.A18106@nuxi.com> Date: Thu, 8 Apr 1999 09:44:22 -0700 From: "David O'Brien" To: current@freebsd.org Subject: -jN make world Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I may have fixed the problem in the Makefile... well I might have fixed another smaller problem, but it is now more broken than before and -jN should work. Please give it a try and let me know. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 9:47:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2897B1599A for ; Thu, 8 Apr 1999 09:47:56 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA18145; Thu, 8 Apr 1999 09:45:53 -0700 (PDT) (envelope-from obrien) Message-ID: <19990408094553.B18106@nuxi.com> Date: Thu, 8 Apr 1999 09:45:53 -0700 From: "David O'Brien" To: sobomax@altavista.net, current@FreeBSD.ORG Subject: Re: EGCS troubles Reply-To: obrien@NUXI.com References: <370C9920.962266C4@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <370C9920.962266C4@altavista.net>; from Maxim Sobolev on Thu, Apr 08, 1999 at 02:55:13PM +0300 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > eebsd.dsl -t sgml handbook.sgml > *** Signal 11 > > Interesting that when it was compiled using pgcc port it worked just > fine. Then it would probably do fine using the EGCS Port. But, the port != /usr/src. The library setup of EGCS in /usr/src is very different than the Port -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 10:16:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 3503914CB9; Thu, 8 Apr 1999 10:16:32 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id MAA06748; Thu, 8 Apr 1999 12:14:19 -0500 (CDT) Date: Thu, 8 Apr 1999 12:14:19 -0500 (CDT) From: Steve Price To: "David O'Brien" Cc: Doug Rabson , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Vtable thunks with egcs In-Reply-To: <19990406054117.A26361@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Apr 1999, David O'Brien wrote: # > I'm assuming that the default for egcs uses vtable thunks instead of # > offsets in the vtable to handle multiple inheritance. # # At the moment, yes. # # > It occurred to me that since this changes the C++ calling convention, # > we have to bump the major version number of all c++ libraries, # > particularly the ones in ports. # # Not only that, but the differences in exceptions, rtti, etc... it is well # known that you can't even use C++ libs compiled with g++ 2.8.{0,1} with # EGCS. # # Guess Steve is in for some fun when he sees just how broken Ports are # with EGCS. ;-) The one I'm fretting over right now is emacs. I haven't quite figured out why, but invoking it brings up the window, but never displays anything in the window. Using a version built with the old compiler doesn't seem to make any difference. :( -steve # -- # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) # # P.S. There is a problem with bootstraping right now that causes something # not to be compiled by EGCS that needs to be. I'm working on this right # now... so we might not want to change any ports just yet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 10:24:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 9834614C4A; Thu, 8 Apr 1999 10:24:53 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.56]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2BC0; Thu, 8 Apr 1999 19:22:52 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA64254; Thu, 8 Apr 1999 19:23:03 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <370C9920.962266C4@altavista.net> Date: Thu, 08 Apr 1999 19:23:03 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Maxim Sobolev Subject: RE: EGCS troubles Cc: current@freebsd.org, "David O'Brien" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Apr-99 Maxim Sobolev wrote: > Hi, > > While this problem might not belongs to this list however it is > difficult in this case to distinguish exactly. > > Something broken in new egcs c++ compiler - jade doesn't work with > following symptoms (checked on two machines). Apr 7 20:26:04 daemon /kernel: pid 61135 (jade), uid 0: exited on signal 11 (core dumped) Verified... David, might this be due to the compiler itself of the libraries? Any way of making certain? --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 10:34:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 79AAB14C4A for ; Thu, 8 Apr 1999 10:34:40 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA21552; Thu, 8 Apr 1999 11:32:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA54417; Thu, 8 Apr 1999 11:34:03 -0600 (MDT) Message-Id: <199904081734.LAA54417@harmony.village.org> To: obrien@NUXI.com Subject: Re: CPP broken on egcs current Cc: paulz@trantor.xs4all.nl, current@FreeBSD.ORG In-reply-to: Your message of "Mon, 05 Apr 1999 13:05:29 PDT." <19990405130529.H22022@nuxi.com> References: <19990405130529.H22022@nuxi.com> <199904051112.NAA22210@trantor.xs4all.nl> <199904051738.KAA91678@vashon.polstra.com> Date: Thu, 08 Apr 1999 11:34:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990405130529.H22022@nuxi.com> "David O'Brien" writes: : Thinking about it... some people might need to build libc to get one with : mkstemp() in it. Of course that is hard to do if `cpp' is totally : broken. If this is the case, people can try adding "SRCS += mkstemp.c" : to src/gnu/usr.bin/cc/cc_drv/Makefile. : : Once a working ``cpp'' is installed, please remove the above hack though. I'm getting cpp internal error, and I know I have a mkstemps in my libc. ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /home/imp/FreeBSD/src/include/rpcsvc/key_prot.x -o key_prot.h /home/imp/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Internal compiler error in function main Looks like rpcgen is giving cpp a -A argument that it is barfing big time on. At least that is what line 1882 is in the middle of parsing. This is with a cvsup of last night's CVS tree. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 10:47:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id EC11A15B8B for ; Thu, 8 Apr 1999 10:47:37 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id NAA22838; Thu, 8 Apr 1999 13:45:36 -0400 (EDT) Message-ID: <19990408134534.A22184@netmonger.net> Date: Thu, 8 Apr 1999 13:45:36 -0400 From: Christopher Masto To: current@freebsd.org Subject: /etc/hosts.allow Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why are we installing a hosts.allow with live entries in it? Why are we allowing the people at mydomain.com (MyInternet Services in Seattle) access to sendmail, while blocking the currently-non-existant d00d.org and spamnest.org from various services? I think it would make sense to have "sample" entries commented out (the addition of ALL : ALL : allow at the top is not quite the same). It may also make sense to use reserved domains like example.com. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 11: 0:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 53BFB15EC5 for ; Thu, 8 Apr 1999 11:00:08 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA21615 for ; Thu, 8 Apr 1999 11:58:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA55575 for ; Thu, 8 Apr 1999 11:59:34 -0600 (MDT) Message-Id: <199904081759.LAA55575@harmony.village.org> Subject: Re: CPP broken on egcs current To: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Apr 1999 11:34:03 MDT." <199904081734.LAA54417@harmony.village.org> References: <199904081734.LAA54417@harmony.village.org> <19990405130529.H22022@nuxi.com> <199904051112.NAA22210@trantor.xs4all.nl> <199904051738.KAA91678@vashon.polstra.com> Date: Thu, 08 Apr 1999 11:59:34 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904081734.LAA54417@harmony.village.org> Warner Losh writes: : I'm getting cpp internal error, and I know I have a mkstemps in my : libc. I did rebuild cpp w/o any hacks and reinstalled it from the latest sources, and things seem to be working now (the rpcgen command that was failing works, but I'm not yet to that point in the buildworld I'm doing). Must have hit a window with my previously installed cpp or something. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 11: 3:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 426AA15B3F for ; Thu, 8 Apr 1999 11:03:49 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA21633; Thu, 8 Apr 1999 12:01:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA64451; Thu, 8 Apr 1999 12:03:15 -0600 (MDT) Message-Id: <199904081803.MAA64451@harmony.village.org> To: Alex Zepeda Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: Chuck Robey , current In-reply-to: Your message of "Wed, 07 Apr 1999 21:09:16 PDT." References: Date: Thu, 08 Apr 1999 12:03:15 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Alex Zepeda writes: : That was one of the BIG pitfalls of egcs, binary incompatable C++ programs : and libs. Sounds like you're overdue for your favorite shot of caffiene. g++ and its derivitives have never been binary compatible for long. I'm aware of at least three ABI breakagese since 2.4.x. This is one reason that OI/uib will no longer work on Linux systems :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 11: 5:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 812F815ADC for ; Thu, 8 Apr 1999 11:05:13 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id NAA20763; Thu, 8 Apr 1999 13:59:19 -0400 (EDT) Date: Thu, 8 Apr 1999 13:59:18 -0400 (EDT) From: Chuck Robey To: Soren Schmidt Cc: ben@rosengart.com, freebsd-current@FreeBSD.ORG Subject: Re: make world breakage In-Reply-To: <199904081225.OAA88439@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, Soren Schmidt wrote: > It seems Snob Art Genre wrote: > > Dont use -jN on the make world, that broke with the EGCS import. Soren, (if we know) is it the build of egcs (in whole or part) or is it the effect of using egcs, that's broken the rest of the -j build? > > > Trying to make world today and last night, with fairly up-to-the-minute > > source, I keep bombing out with: > > > > `/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/i386. > > md' is up to date. > > `genattr.c' is up to date. > > `gencodes.c' is up to date. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 11:26:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 7373014CE4 for ; Thu, 8 Apr 1999 11:26:20 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id OAA24570; Thu, 8 Apr 1999 14:24:20 -0400 (EDT) Message-ID: <19990408142419.A24545@netmonger.net> Date: Thu, 8 Apr 1999 14:24:19 -0400 From: Christopher Masto To: current@freebsd.org Subject: UPDATING needs updating Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mightn't it be a good idea to mention the egcs move in /usr/src/UPDATING? -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 11:27:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C571914C8A for ; Thu, 8 Apr 1999 11:27:07 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA42177; Thu, 8 Apr 1999 14:24:48 -0400 (EDT) Date: Thu, 8 Apr 1999 14:24:47 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans Cc: jdp@polstra.com, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <199904080436.OAA11412@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, Bruce Evans wrote: > >> Actually, they don't. Compiler-specific options can be put in ${CC}. > >> Perhaps they even should be. > > > >But in this case, we want "-Os" (egcs) or "-O2" (gcc) only for > >building boot -- not for everything. It could be parameterized with > >make macros like "OPT_SMALL" and "OPT_FAST" in the *.mk files, I > >suppose. > > "CC+=-Os" in individual Makefiles works about as well as "CFLAGS+=-Os" for > adding flags. That's not very well. Removing unwanted additions is hard. > > BTW, boot2/Makefile uses "CFLAGS=" to override any previous definition > of CFLAGS. This may break `make world' by removing -nostdinc. Why don't we have a -= operator in make(1)? > > Bruce > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 11:50:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-15.ppp.wenet.net [206.15.85.15]) by hub.freebsd.org (Postfix) with ESMTP id 9463715A58 for ; Thu, 8 Apr 1999 11:45:40 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id LAA00967; Thu, 8 Apr 1999 11:42:44 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Thu, 8 Apr 1999 11:42:44 -0700 (PDT) From: Alex Zepeda To: Chuck Robey Cc: John Polstra , asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, Chuck Robey wrote: > When Satoshi builds stuff, it's in a real clean environment, but in > fact, all the gnome and kde ports are extraordinarly sensitive to > stuff from older ports hanging around. That's why folks are wary of > upgrading those guys. That's news to me. Perhaps the ports are poorly designed or whathaveyou, but I can't imagine what "older ports" the kde ports are so sensitive to. Then of course, I tend to install from the CVS tree into /usr/local/kde... > The gnome stuff is really neat, else I'd never even bother. Yup. Nothing like a load of core dumps in your home directory to make one's day :) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 11:53:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 99BCD15A82 for ; Thu, 8 Apr 1999 11:51:01 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA14532; Thu, 8 Apr 1999 11:49:01 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id LAA79680; Thu, 8 Apr 1999 11:49:00 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 08 Apr 1999 11:49:00 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Alex Zepeda Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > On Thu, 8 Apr 1999, Chuck Robey wrote: > >> When Satoshi builds stuff, it's in a real clean environment, but in >> fact, all the gnome and kde ports are extraordinarly sensitive to >> stuff from older ports hanging around. That's why folks are wary of >> upgrading those guys. > > That's news to me. Perhaps the ports are poorly designed or whathaveyou, > but I can't imagine what "older ports" the kde ports are so sensitive to. Here's the deal. The KDE and gnome ports both have many dependencies on other ports, mainly shared libraries. Some of those may in turn depend on still other ports. In any case, it's a complicated dependency graph with a lot of nodes. Everything works fine for the initial installation. But now 3 months later you want to upgrade to the new version. About the only reliable way to do that is to manually track down all the dependencies, pkg_delete every one of them, and then make install in the KDE or gnome port. Otherwise you end up with a hodge-podge of new ports and old dependencies, and they don't play together nicely. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 12: 1: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from unix.tfs.net (as2-p76.tfs.net [139.146.205.76]) by hub.freebsd.org (Postfix) with ESMTP id 7151714F01 for ; Thu, 8 Apr 1999 12:00:55 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.3/8.8.5) id NAA00962 for freebsd-current@freebsd.org; Thu, 8 Apr 1999 13:58:54 -0500 (CDT) From: Jim Bryant Message-Id: <199904081858.NAA00962@unix.tfs.net> Subject: f77 not working. To: freebsd-current@freebsd.org Date: Thu, 8 Apr 1999 13:58:53 -0500 (CDT) Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I attempted to run some fortran benchmarks to see the improvement that egcs gives with the pentium opts... 1:56:13pm argus(57): f77 -O2 -mpentium -fomit-frame-pointer -pipe -o pitest.mx=14 pi4.f mp.f cc: pi4.f: Fortran compiler not installed on this system cc: mp.f: Fortran compiler not installed on this system cc: installation problem, cannot exec `#Fortran#Fortranld': No such file or directory jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 12: 3: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 927F514D3F for ; Thu, 8 Apr 1999 12:02:54 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id VAA91232; Thu, 8 Apr 1999 21:00:52 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id VAA00863; Thu, 8 Apr 1999 21:00:53 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904081900.VAA00863@greenpeace.grondar.za> To: Christopher Masto Cc: current@freebsd.org Subject: Re: /etc/hosts.allow In-Reply-To: Your message of " Thu, 08 Apr 1999 13:45:36 -0400." <19990408134534.A22184@netmonger.net> References: <19990408134534.A22184@netmonger.net> Date: Thu, 08 Apr 1999 21:00:49 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Masto wrote: > Why are we installing a hosts.allow with live entries in it? Why are > we allowing the people at mydomain.com (MyInternet Services in > Seattle) access to sendmail, while blocking the currently-non-existant > d00d.org and spamnest.org from various services? No problem; fix coming. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 12:12:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id AD83814D9D for ; Thu, 8 Apr 1999 12:12:17 -0700 (PDT) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id OAA16473; Thu, 8 Apr 1999 14:10:08 -0500 (CDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma016471; Thu, 8 Apr 99 14:10:04 -0500 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id OAA88107; Thu, 8 Apr 1999 14:08:59 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Message-Id: <199904081908.OAA88107@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: lists/freebsd X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: /sys/boot, egcs vs. gcc, -Os Mime-Version: 1.0 Content-Type: text/plain To: John Polstra Cc: Alex Zepeda , current@FreeBSD.ORG Date: Thu, 08 Apr 1999 14:08:59 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 April 1999 at 11:49, John Polstra wrote: [snip] > Everything works fine for the initial installation. But now 3 months > later you want to upgrade to the new version. About the only reliable > way to do that is to manually track down all the dependencies, > pkg_delete every one of them, and then make install in the KDE or > gnome port. Otherwise you end up with a hodge-podge of new ports and > old dependencies, and they don't play together nicely. Maintainers of these ports would appreciate PRs if the dependencies are broken. The ports infrastructure has the mechanisms necessary to handle these dependencies, but the port maintainer may not catch every dependency. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 12:17:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 7BEBA15024 for ; Thu, 8 Apr 1999 12:17:35 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id MAA42930; Thu, 8 Apr 1999 12:12:51 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904081912.MAA42930@troutmask.apl.washington.edu> Subject: Re: f77 not working. In-Reply-To: <199904081858.NAA00962@unix.tfs.net> from Jim Bryant at "Apr 8, 1999 01:58:53 pm" To: jbryant@unix.tfs.net Date: Thu, 8 Apr 1999 12:12:51 -0700 (PDT) Cc: freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bryant wrote: > > I attempted to run some fortran benchmarks to see the improvement that > egcs gives with the pentium opts... > > 1:56:13pm argus(57): f77 [flags elided] -o pitest.mx=14 pi4.f mp.f > cc: pi4.f: Fortran compiler not installed on this system > cc: mp.f: Fortran compiler not installed on this system Yep. A decision has not been made on whether to bring g77 into the source tree. Thus, egcs hasn't been modified to pick up gnu/usr.bin/cc/cc/f2c-specs.h. If you're bold and daring, then %rm /usr/bin/f77 /usr/bin/f2c /usr/lib/*f2c* %ldconfig -R %rm /usr/share/man/man1/f2c.1 /usr/share/man/man1/f77.1 %cd ~/tmp %ftp troutmask.apl.washington.edu ftp>cd pub ftp>bin ftp>prompt ftp>mget *.tgz ftp>quit %ls f2c-freebsd.tgz f77-freebsd.tgz %tar zxf f2c-freebsd.tgz %tar zxf f77-freebsd.tgz %mv f2c-freebsd /usr/ports/lang %mv f77-freebsd /usr/ports/lang %cd /usr/ports/lang/f77-freebsd %make install -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 12:23:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 7FBF614D7E; Thu, 8 Apr 1999 12:23:19 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id UAA11041; Thu, 8 Apr 1999 20:21:16 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 8 Apr 1999 20:11:45 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19990408094422.A18106@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 8 Apr 1999 20:11:43 +0000 To: obrien@FreeBSD.ORG From: Bob Bishop Subject: Re: -jN make world Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:44 am -0700 8/4/99, David O'Brien wrote: >I think I may have fixed the problem in the Makefile... well I might have >fixed another smaller problem, but it is now more broken than before and >-jN should work. > >Please give it a try and let me know. Still broken here at v1.23. Luoqi's patch against v1.21 works though -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 12:27: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5C5E314CFC for ; Thu, 8 Apr 1999 12:27:00 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id MAA14797; Thu, 8 Apr 1999 12:24:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id MAA79735; Thu, 8 Apr 1999 12:24:59 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904081908.OAA88107@spawn.nectar.com> Date: Thu, 08 Apr 1999 12:24:58 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Jacques Vidrine Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jacques Vidrine wrote: > > Maintainers of these ports would appreciate PRs if the dependencies > are broken. The ports infrastructure has the mechanisms necessary to > handle these dependencies, but the port maintainer may not catch > every dependency. I am not saying the dependencies are broken. I'm just lamenting the general problem that it's difficult to upgrade a port that depends on a lot of things. It's a general structural problem, and I don't know how to fix it. Say you've got a bunch of ports that all depend on the same shared library -- maybe libjpeg or libXpm. You've had them installed for a few months, and they all work fine. Now you decide to upgrade one of them, the "foo" port. Oops, it requires a newer version of libjpeg. You have to remove the old libjpeg so that the newer one can be installed without a lot of complaints. Oops, a bunch of other ports used the old libjpeg. Now you have to upgrade those ports too. Oops, some of those ports depend on libXpm, and a new version of it is needed now. Oops, now some other ports that used the old libXpm need to be upgraded. At this point, you throw up your hands, pkg_delete -f everything, and reinstall all your ports from scratch. And the next time you're tempted to upgrade a port, you decide it would be easier to just buy a new machine. :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 12:28:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 82B5314BE3 for ; Thu, 8 Apr 1999 12:28:11 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA19106; Thu, 8 Apr 1999 12:26:07 -0700 (PDT) (envelope-from obrien) Message-ID: <19990408122607.A19098@nuxi.com> Date: Thu, 8 Apr 1999 12:26:07 -0700 From: "David O'Brien" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: CPP broken on egcs current Reply-To: obrien@NUXI.com References: <19990405130529.H22022@nuxi.com> <199904051112.NAA22210@trantor.xs4all.nl> <199904051738.KAA91678@vashon.polstra.com> <19990405130529.H22022@nuxi.com> <199904081734.LAA54417@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904081734.LAA54417@harmony.village.org>; from Warner Losh on Thu, Apr 08, 1999 at 11:34:03AM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ===> rpcsvc > rpcgen -C -h -DWANT_NFS3 /home/imp/FreeBSD/src/include/rpcsvc/key_prot.x -o key_prot.h > /home/imp/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Internal compiler error in function main What rev of contrib/egcs/gcc/config/freebsd.h do you have? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 13:56:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id C83AB14F3D for ; Thu, 8 Apr 1999 13:56:45 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id NAA28205; Thu, 8 Apr 1999 13:54:31 -0700 (PDT) Date: Thu, 8 Apr 1999 13:54:34 -0700 (PDT) From: Tom Bartol To: John Polstra Cc: Jacques Vidrine , current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, John Polstra wrote: > > I am not saying the dependencies are broken. I'm just lamenting the > general problem that it's difficult to upgrade a port that depends on > a lot of things. It's a general structural problem, and I don't know > how to fix it. > > Say you've got a bunch of ports that all depend on the same shared > library -- maybe libjpeg or libXpm. You've had them installed for > a few months, and they all work fine. Now you decide to upgrade > one of them, the "foo" port. Oops, it requires a newer version of > libjpeg. You have to remove the old libjpeg so that the newer one > can be installed without a lot of complaints. Oops, a bunch of other > ports used the old libjpeg. Now you have to upgrade those ports too. > Oops, some of those ports depend on libXpm, and a new version of it is > needed now. Oops, now some other ports that used the old libXpm need > to be upgraded. > > At this point, you throw up your hands, pkg_delete -f everything, > and reinstall all your ports from scratch. And the next time you're > tempted to upgrade a port, you decide it would be easier to just buy > a new machine. :-) > > John I agree completely. I had just recently run into this problem in a big way over gnome. I am not familiar at all with the inner workings of the ports/package database system but it occurred to me that perhaps the database is currently only storing which packages a given package depends upon and is NOT storing which packages depend upon a given package -- i.e. the leaves know which branch they are on but the branches don't know which leaves they bear. If this is in fact the case then it seems to me that a first step in improving the behaviour of the port/package system is to make the database be a leaf-to-branch and branch-to-leaf linked relationship tree that can be traversed as needed. I'm not sure of the standard Computer Science jargon to describe such a tree. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 15:21:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id AF6FD14EDC; Thu, 8 Apr 1999 15:21:45 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 9 Apr 1999 08:06:24 +1000 Date: Fri, 9 Apr 1999 08:19:21 +1000 From: Peter Jeremy Subject: Re: Vtable thunks with egcs To: sprice@hiwaay.net Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Message-Id: <99Apr9.080624est.40323@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Price wrote: >The one I'm fretting over right now is emacs. I haven't quite >figured out why, but invoking it brings up the window, but never >displays anything in the window. Using a version built with the >old compiler doesn't seem to make any difference. :( I submitted ports/10783 covering this about 2 weeks ago. The port on the 3.1-RELEASE CD is OK, but I can't get it to work with -CURRENT. (I suspect it's been broken for some time). I have tried mixing and matching the X11 libs and the problem is in emacs, not X11. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 15:24:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id 1176114E5F for ; Thu, 8 Apr 1999 15:24:17 -0700 (PDT) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id OAA16588; Thu, 8 Apr 1999 14:38:39 -0500 (CDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma016586; Thu, 8 Apr 99 14:38:33 -0500 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id OAA88810; Thu, 8 Apr 1999 14:37:29 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Message-Id: <199904081937.OAA88810@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: lists/freebsd X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine In-reply-to: References: Subject: port dependencies (was Re: /sys/boot, egcs vs. gcc, -Os) Mime-Version: 1.0 Content-Type: text/plain To: John Polstra Cc: Jacques Vidrine , current@FreeBSD.ORG Date: Thu, 08 Apr 1999 14:37:28 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 April 1999 at 12:24, John Polstra wrote: [snip] > Say you've got a bunch of ports that all depend on the same shared > library -- maybe libjpeg or libXpm. You've had them installed for > a few months, and they all work fine. Now you decide to upgrade > one of them, the "foo" port. Oops, it requires a newer version of > libjpeg. You have to remove the old libjpeg so that the newer one > can be installed without a lot of complaints. Oops, a bunch of other > ports used the old libjpeg. Now you have to upgrade those ports too. > Oops, some of those ports depend on libXpm, and a new version of it is > needed now. Oops, now some other ports that used the old libXpm need > to be upgraded. Now I understand what you are saying. The current ports structure only goes one way through the dependency graph. Maybe when building a particular port, not only should dependencies be checked, but anything that depends on the port needs to be rebuilt. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 15:38:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id D58AA14BD4 for ; Thu, 8 Apr 1999 15:38:20 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id AAA05779; Fri, 9 Apr 1999 00:36:18 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id AAA13497; Fri, 9 Apr 1999 00:36:18 +0200 (MET DST) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id AAA09374; Fri, 9 Apr 1999 00:35:07 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Fri, 9 Apr 1999 00:35:07 +0200 (CEST) From: Michael Reifenberger To: greg@lemis.com Cc: FreeBSD-Current Subject: Panic: Invalid longjmp with vinum configured by novice Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I often get to above message while trying to configure vinum. Trying the examples from the manpage works, of course. Next try. What I want to do: First creating a non mirrored but striped volume and later add one mirror plex. I do: # vinum start # vinum resetconfig ... # cat x drive d1 device /dev/da1d drive d2 device /dev/da2d volume raid plex org stripe 256k sd length 50m drive d1 sd length 50m drive d2 vinum create x ... (Please note the missing 'd' in stripe) I get: ..the panic.. Now with the missing 'd' `vinum create x` works as expected. vinum l shows: # vinum l Configuration summary Drives: 2 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D d1 State: up Device /dev/da1d Avail: 8664/8714 MB (99%) D d2 State: up Device /dev/da2d Avail: 8664/8714 MB (99%) V raid State: up Plexes: 1 Size: 100 MB P raid.p0 S State: up Subdisks: 2 Size: 100 MB S raid.p0.s0 State: up PO: 0 B Size: 50 MB S raid.p0.s1 State: up PO: 256 kB Size: 50 MB Now adding the second plex: # cat z plex org striped volume raid sd length 50m drive d2 sd length 50m drive d1 (please note the missing stripesize) # vinum create z I get: ..the panic.. Sigh. After correcting z the `vinum create z` works as expected. BTW: Any chance that the create commands will work interactive from within vinum? I suspect one will not have a r/w filesystem in worst case scenarios for creating vinum createfiles (And even if, `ed` is not my friend.) Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16: 1:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id EF52514C83; Thu, 8 Apr 1999 16:01:04 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id RAA23960; Thu, 8 Apr 1999 17:58:59 -0500 (CDT) Date: Thu, 8 Apr 1999 17:58:59 -0500 (CDT) From: Steve Price To: Peter Jeremy Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: emacs* broken in -current (was Re: Vtable thunks with egcs) In-Reply-To: <99Apr9.080624est.40323@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You are absolutely right. I just tried the new version of emacs that I built on my pre-egcs box and it doesn't work on that box either. This definitely doesn't appear to be anything caused by changing to egcs. Not that it matters much but for grins I just built/installed the xemacs port and it _does_ appear to work. -steve On Fri, 9 Apr 1999, Peter Jeremy wrote: # I submitted ports/10783 covering this about 2 weeks ago. The port # on the 3.1-RELEASE CD is OK, but I can't get it to work with -CURRENT. # (I suspect it's been broken for some time). # # I have tried mixing and matching the X11 libs and the problem is # in emacs, not X11. # # Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:12: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 05E0214D1D for ; Thu, 8 Apr 1999 16:11:58 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40354>; Fri, 9 Apr 1999 08:56:46 +1000 Date: Fri, 9 Apr 1999 09:09:46 +1000 From: Peter Jeremy Subject: Re: /sys/boot, egcs vs. gcc, -Os To: bartol@salk.edu Cc: current@FreeBSD.ORG Message-Id: <99Apr9.085646est.40354@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Bartol wrote: >ports/package database system but it occurred to me that perhaps the >database is currently only storing which packages a given package depends >upon and is NOT storing which packages depend upon a given >package The port source tree stores a list of pre-requisite packages in each Makefile. The `required-by' list is not stored - it would be a nightmare to maintain. On installation, the packages database stores both dependency directions. /var/db/pkg//+CONTENTS contains the list of pre-requisite packages in `@pkgdep' records. The +CONTENTS file is part of the package. /var/db/pkg//+REQUIRED_BY contains the `required-by' list and is maintained automatically by the package management tools (eg installing `foo' which depends on `bar' adds a line `foo' to /var/db/pkg/bar/+REQUIRED_BY, which is removed if the package in removed). The problem is that the package management system provides `add' and `delete' functions only, and the delete function (by default) requires all dependent packages to be deleted first. (You can force the delete to ignore the dependent packages, but that loses the +REQUIRED_BY file contents). There's no mechanism for updating a package - and it's not clear (to me anyway) how this can be done safely in a general way. Where the update is only minor (and won't affect the dependent packages), you can use something like: mv /var/db/pkg/bar-1.1/+REQUIRED_BY /var/db/pkg/save pkg_delete bar-1.1 pkg_add bar-1.2 mv /var/db/pkg/save /var/db/pkg/bar-1.2/+REQUIRED_BY This approach can't pick up the dependent packages that really do need to be re-compiled against the newly installed package. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:22:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id 4CF3F15134 for ; Thu, 8 Apr 1999 16:22:22 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id PAA02343; Thu, 8 Apr 1999 15:55:18 -0700 (PDT) Date: Thu, 8 Apr 1999 15:55:22 -0700 (PDT) From: Tom Bartol To: Jacques Vidrine Cc: John Polstra , current@FreeBSD.ORG Subject: Re: port dependencies (was Re: /sys/boot, egcs vs. gcc, -Os) In-Reply-To: <199904081937.OAA88810@spawn.nectar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, Jacques Vidrine wrote: > On 8 April 1999 at 12:24, John Polstra wrote: > [snip] > > Say you've got a bunch of ports that all depend on the same shared > > library -- maybe libjpeg or libXpm. You've had them installed for > > a few months, and they all work fine. Now you decide to upgrade > > one of them, the "foo" port. Oops, it requires a newer version of > > libjpeg. You have to remove the old libjpeg so that the newer one > > can be installed without a lot of complaints. Oops, a bunch of other > > ports used the old libjpeg. Now you have to upgrade those ports too. > > Oops, some of those ports depend on libXpm, and a new version of it is > > needed now. Oops, now some other ports that used the old libXpm need > > to be upgraded. > > Now I understand what you are saying. The current ports structure > only goes one way through the dependency graph. Maybe when building a > particular port, not only should dependencies be checked, but anything > that depends on the port needs to be rebuilt. > > Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org Exactly correct. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:29:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 9ECBE14D1D for ; Thu, 8 Apr 1999 16:29:23 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA21860; Thu, 8 Apr 1999 19:25:13 -0400 (EDT) Date: Thu, 8 Apr 1999 19:25:13 -0400 (EDT) From: Chuck Robey To: John Polstra Cc: Jacques Vidrine , current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, John Polstra wrote: > Jacques Vidrine wrote: > > > > Maintainers of these ports would appreciate PRs if the dependencies > > are broken. The ports infrastructure has the mechanisms necessary to > > handle these dependencies, but the port maintainer may not catch > > every dependency. > > I am not saying the dependencies are broken. I'm just lamenting the > general problem that it's difficult to upgrade a port that depends on > a lot of things. It's a general structural problem, and I don't know > how to fix it. > > Say you've got a bunch of ports that all depend on the same shared > library -- maybe libjpeg or libXpm. You've had them installed for > a few months, and they all work fine. Now you decide to upgrade > one of them, the "foo" port. Oops, it requires a newer version of > libjpeg. You have to remove the old libjpeg so that the newer one > can be installed without a lot of complaints. Oops, a bunch of other > ports used the old libjpeg. Now you have to upgrade those ports too. > Oops, some of those ports depend on libXpm, and a new version of it is > needed now. Oops, now some other ports that used the old libXpm need > to be upgraded. And on top of that, there are about 5 top tracks of libs, each of these 5 tracks (that have lots depending on them) has lived in both /usr/local and in /usr/X11R6 in recent times, both leave ascii configuration files behind (and in both sets of directories, depending on the age of the older ports). Just to make everything totally confused, because some insane folks want to have multiple versions active concurrently, the name of those config files, which exist in multiple places, have multiple names. Each of the ports of the apps, which need all these libs, have configuration scripts that go looking for all these misnamed and misfiled config scripts, and those configuration scripts alway seem to find the oldest and most out-of-date config script possible. Bleah! > > At this point, you throw up your hands, pkg_delete -f everything, > and reinstall all your ports from scratch. And the next time you're > tempted to upgrade a port, you decide it would be easier to just buy > a new machine. :-) > > John > --- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:37: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx4.dynasty.net (mail.dynasty.net [208.200.172.236]) by hub.freebsd.org (Postfix) with ESMTP id 6114914DDE for ; Thu, 8 Apr 1999 16:37:00 -0700 (PDT) (envelope-from cpinckard@dynasty.net) Received: from dynasty.net ([12.14.196.174]) by mx4.dynasty.net (Netscape Messaging Server 3.52) with ESMTP id 449; Thu, 8 Apr 1999 18:34:47 -0500 Message-ID: <370D3C38.355F26A0@dynasty.net> Date: Thu, 08 Apr 1999 18:31:04 -0500 From: Chas Pinckard X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Jeremy Cc: bartol@salk.edu, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os References: <99Apr9.085646est.40354@border.alcanet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Suggestion: How bout a version detection flag for the update pkgs and a version requirement to the newly built ports? C~P Peter Jeremy wrote: > Tom Bartol wrote: > >ports/package database system but it occurred to me that perhaps the > >database is currently only storing which packages a given package depends > >upon and is NOT storing which packages depend upon a given > >package > > The port source tree stores a list of pre-requisite packages in each > Makefile. The `required-by' list is not stored - it would be a > nightmare to maintain. > > On installation, the packages database stores both dependency > directions. /var/db/pkg//+CONTENTS contains the list of > pre-requisite packages in `@pkgdep' records. The +CONTENTS file is > part of the package. /var/db/pkg//+REQUIRED_BY contains the > `required-by' list and is maintained automatically by the package > management tools (eg installing `foo' which depends on `bar' adds > a line `foo' to /var/db/pkg/bar/+REQUIRED_BY, which is removed if > the package in removed). > > The problem is that the package management system provides `add' and > `delete' functions only, and the delete function (by default) requires > all dependent packages to be deleted first. (You can force the delete > to ignore the dependent packages, but that loses the +REQUIRED_BY file > contents). > > There's no mechanism for updating a package - and it's not clear (to > me anyway) how this can be done safely in a general way. Where the > update is only minor (and won't affect the dependent packages), you > can use something like: > > mv /var/db/pkg/bar-1.1/+REQUIRED_BY /var/db/pkg/save > pkg_delete bar-1.1 > pkg_add bar-1.2 > mv /var/db/pkg/save /var/db/pkg/bar-1.2/+REQUIRED_BY > > This approach can't pick up the dependent packages that really do need > to be re-compiled against the newly installed package. > > Peter > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:46:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 25FC814DDE for ; Thu, 8 Apr 1999 16:46:19 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA20505; Thu, 8 Apr 1999 16:44:14 -0700 (PDT) (envelope-from obrien) Message-ID: <19990408164414.A20453@nuxi.com> Date: Thu, 8 Apr 1999 16:44:14 -0700 From: "David O'Brien" To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: -jN make world Reply-To: obrien@NUXI.com References: <19990408094422.A18106@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Bob Bishop on Thu, Apr 08, 1999 at 08:11:43PM +0000 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Still broken here at v1.23. Luoqi's patch against v1.21 works though Please try rev 1.24 of src/gnu/usr.bin/cc/cc_tools/Makefile. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:49: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E6D88150AA for ; Thu, 8 Apr 1999 16:48:59 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA20534; Thu, 8 Apr 1999 16:45:14 -0700 (PDT) (envelope-from obrien) Message-ID: <19990408164514.B20453@nuxi.com> Date: Thu, 8 Apr 1999 16:45:14 -0700 From: "David O'Brien" To: Chuck Robey , Soren Schmidt Cc: ben@rosengart.com, freebsd-current@FreeBSD.ORG Subject: Re: make world breakage Reply-To: obrien@NUXI.com References: <199904081225.OAA88439@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Thu, Apr 08, 1999 at 01:59:18PM -0400 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It seems Snob Art Genre wrote: > > > > Dont use -jN on the make world, that broke with the EGCS import. > > Soren, (if we know) is it the build of egcs (in whole or part) or is it > the effect of using egcs, that's broken the rest of the -j build? The build of egcs. ``cd src/gnu/usr.bin/cc && make -j 8'' is/was broken. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:50:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8CFE314DDE for ; Thu, 8 Apr 1999 16:50:32 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA20552; Thu, 8 Apr 1999 16:48:30 -0700 (PDT) (envelope-from obrien) Message-ID: <19990408164830.C20453@nuxi.com> Date: Thu, 8 Apr 1999 16:48:30 -0700 From: "David O'Brien" To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: EGCS troubles Reply-To: obrien@NUXI.com References: <370C9920.962266C4@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Thu, Apr 08, 1999 at 07:23:03PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Something broken in new egcs c++ compiler - jade doesn't work with > > following symptoms (checked on two machines). > > Apr 7 20:26:04 daemon /kernel: pid 61135 (jade), uid 0: exited on signal > 11 (core dumped) > > Verified... > > David, might this be due to the compiler itself of the libraries? > Any way of making certain? Compile Jade with "-g" and see where in the coredump the signal 11 is occuring. What does ``ldd jade'' show? You might be mixing shared libs, that doesn't work for C++. Could also be an exceptions problem. Try compiling with -fnoexpcetions. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:51:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 43F0314DB2 for ; Thu, 8 Apr 1999 16:51:28 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.2/8.9.1) with ESMTP id SAA31014; Thu, 8 Apr 1999 18:49:13 -0500 (EST) Date: Thu, 8 Apr 1999 18:49:13 -0500 (EST) From: John Fieber To: Peter Jeremy Cc: bartol@salk.edu, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <99Apr9.085646est.40354@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Peter Jeremy wrote: > There's no mechanism for updating a package - and it's not clear (to > me anyway) how this can be done safely in a general way. Where the > update is only minor (and won't affect the dependent packages), you > can use something like: For an update to work, files that must be preserved (shared libraries mainly) over an update must be tagged. If libfoo-1.0 is installed and I upgrade to libfoo-2.3, the libfoo-1.0 package should be removed except /usr/local/share/libfoo.so.1.0. Then libfoo-2.3 gets installed and *inherits* /usr/local/share/libfoo.so.1.0 in its +CONTENTS so that if you want to do a wholesale removal of the libfoo package in the future, you can do it. A completely different approach to this dependency nightmare is to link statically. I know there are drawbacks to this and the costs are too great in numerous situations. But if you *can* practically do this, you can demote a runtime dependency to a build time dependency which is a Good Thing for your sanity. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 16:53: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 41402151B0; Thu, 8 Apr 1999 16:52:56 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA20592; Thu, 8 Apr 1999 16:50:56 -0700 (PDT) (envelope-from obrien) Message-ID: <19990408165056.D20453@nuxi.com> Date: Thu, 8 Apr 1999 16:50:56 -0700 From: "David O'Brien" To: current@freebsd.org Cc: hackers@freebsd.org Subject: ATTENTION PLEASE: g77 in base system. Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've only heard back from 4 folks about adding EGCS's g77 to the base system -- all 4 said "yes". Unless I get more feedback, I will add g77 to the base system this weekend. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17: 0: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id E075914DB2; Thu, 8 Apr 1999 17:00:01 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA03173; Fri, 9 Apr 1999 09:28:17 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA30616; Fri, 9 Apr 1999 09:28:14 +0930 Date: Fri, 9 Apr 1999 09:28:13 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Peter Jeremy Cc: bartol@salk.edu, current@freebsd.org, ports@freebsd.org Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <99Apr9.085646est.40354@border.alcanet.com.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Peter Jeremy wrote: > On installation, the packages database stores both dependency > directions. /var/db/pkg//+CONTENTS contains the list of > pre-requisite packages in `@pkgdep' records. The +CONTENTS file is > part of the package. /var/db/pkg//+REQUIRED_BY contains the > `required-by' list and is maintained automatically by the package > management tools (eg installing `foo' which depends on `bar' adds > a line `foo' to /var/db/pkg/bar/+REQUIRED_BY, which is removed if > the package in removed). I've never found the +REQUIRED_BY data to be consistently maintained for me - i.e. there are usually dependent packages referenced there which no longer exist on my system, several versions of packages when I've done a remove old/add new version, etc. I should spend some time to try and figure out what's causing this inconsistency..does anyone else see behaviour like this? Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17: 1:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 72B2314DB2 for ; Thu, 8 Apr 1999 17:01:43 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA21988; Thu, 8 Apr 1999 19:57:20 -0400 (EDT) Date: Thu, 8 Apr 1999 19:57:20 -0400 (EDT) From: Chuck Robey To: John Fieber Cc: Peter Jeremy , bartol@salk.edu, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, John Fieber wrote: > On Fri, 9 Apr 1999, Peter Jeremy wrote: > > > There's no mechanism for updating a package - and it's not clear (to > > me anyway) how this can be done safely in a general way. Where the > > update is only minor (and won't affect the dependent packages), you > > can use something like: > > For an update to work, files that must be preserved (shared > libraries mainly) over an update must be tagged. If libfoo-1.0 > is installed and I upgrade to libfoo-2.3, the libfoo-1.0 package > should be removed except /usr/local/share/libfoo.so.1.0. Then > libfoo-2.3 gets installed and *inherits* > /usr/local/share/libfoo.so.1.0 in its +CONTENTS so that if you > want to do a wholesale removal of the libfoo package in the > future, you can do it. > > A completely different approach to this dependency nightmare is > to link statically. I know there are drawbacks to this and the > costs are too great in numerous situations. But if you *can* > practically do this, you can demote a runtime dependency to a > build time dependency which is a Good Thing for your sanity. Don't forget, with all the gnome and gtk ports (and the kde things) there are various files with "config" in their names, that a bunch of other ports depend on ... just to add confusion, and the rules for these dependencies aren't as cut and dried as the libs, because the libs follow usually one set of rules (laid down by the runtime linker) but the config files, every port seems to use it's own set of rules. And there is no "static linking" for config files, to save you. A lot of these config files only take effect while building other libs or applications, which means they sometimes won't affect regular runtime problems, just beating the heck out of the upgrade nightmare. > > -john > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17: 4:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6E37014DB2; Thu, 8 Apr 1999 17:04:11 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id UAA22010; Thu, 8 Apr 1999 20:00:10 -0400 (EDT) Date: Thu, 8 Apr 1999 20:00:10 -0400 (EDT) From: Chuck Robey To: "David O'Brien" Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <19990408165056.D20453@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, David O'Brien wrote: > I've only heard back from 4 folks about adding EGCS's g77 to the base > system -- all 4 said "yes". Unless I get more feedback, I will add g77 > to the base system this weekend. Personally, yes, lets do it. In fact, I'd like to hear serious discussion, now that libgcj is available, of making gcj (a part of egcs) also get installed. Java is extremely popular, and libgcj is going to increase that a great deal. Yeah, I'm serious, I would really like gcj+libgcj, to get java stuff compiled (non portably) into binaries on FreeBSD. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17:26:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-36.ppp.wenet.net [206.15.85.36]) by hub.freebsd.org (Postfix) with ESMTP id 3B3F514BEC for ; Thu, 8 Apr 1999 17:26:12 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id RAA61253 for ; Thu, 8 Apr 1999 17:24:10 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Thu, 8 Apr 1999 17:24:10 -0700 (PDT) From: Alex Zepeda To: current Subject: msdosfs problems? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got all my mp3s stored on my fat16 partition so I can easily share them between Win98 and fbsd. However recently mpg123 has been complaining about once valid mp3s: zippy:~/mp3s#mpg123 -b10240 U2/U2\ -\ Sunday\ Bloody\ Sunday.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. Version 0.59q (1999/Jan/26). Written and copyrights by Michael Hipp. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Title : Sunday Bloody Sunday Artist: U2 Album : Year: 83 Comment: Genre: Alternative Directory: U2/ Playing MPEG stream from U2 - Sunday Bloody Sunday.mp3 ... MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo Illegal Audio-MPEG-Header 0x00000000 at offset 0x80af. Skipped 4170 bytes in input. mpg123: Can't rewind stream by 679 bits! And gqmpeg can realiably freeze my machine if I try and play an mp3 off of a fat16 formatted zip disk. And no I haven't recently upgraded mpg123, but oddly enough, copying files to and from a floppy disk works fine.. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17:36: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id AEB8414C94 for ; Thu, 8 Apr 1999 17:36:03 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40374>; Fri, 9 Apr 1999 10:20:50 +1000 Date: Fri, 9 Apr 1999 10:33:43 +1000 From: Peter Jeremy Subject: Re: /sys/boot, egcs vs. gcc, -Os To: current@FreeBSD.ORG Message-Id: <99Apr9.102050est.40374@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Fieber wrote: >For an update to work, files that must be preserved (shared >libraries mainly) over an update must be tagged. This is why I said my approach only worked for `minor' updates - which means those that don't bump library versions etc (eg XFree86-3.3.3 to XFree86-3.3.3.1). > If libfoo-1.0 >is installed and I upgrade to libfoo-2.3, the libfoo-1.0 package >should be removed except /usr/local/share/libfoo.so.1.0. Then >libfoo-2.3 gets installed and *inherits* >/usr/local/share/libfoo.so.1.0 in its +CONTENTS so that if you >want to do a wholesale removal of the libfoo package in the >future, you can do it. The problem with this approach is that you lose the fact that xbar depends on libfoo-1.0, whilst xyzzy depends on libfoo-2.3. This makes updating libfoo-2.3 to libfoo-3.1 messy - especially if xbar has been deleted in the interim (meaning libfoo.so.1.0 is no longer needed). I'd prefer to see the upgrade delete the unnecessary bits of libfoo-1.0, but leave the db/pkg entry in place - with a cut-down +CONTENTS. This makes it easier to get rid of the remaining bits when any dependencies are deleted. (For extra marks, add a flag so that libfoo-1.0 is deleted automatically when the last dependency is removed). (Of course, as Chuck Robey points out, this becomes much harder when config files are taken into account). Kris Kennaway wrote: >I've never found the +REQUIRED_BY data to be consistently maintained for me - I've seen the same, but I've never bothered digging into the problem. Feel free to look into the problem. It might be worthwhile asking Jordan if he is aware of the problem and/or has any ideas. Chuck Robey wrote: >Don't forget, with all the gnome and gtk ports (and the kde things) tcl and tk also install various version-specific information (and has anyone else noticed that tk depends on X11 (ie XFree86) and the XFree86 configuration (xf86site.def) changes depending on whether or not tk exists). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17:41:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id 5A0AC15041 for ; Thu, 8 Apr 1999 17:41:02 -0700 (PDT) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id TAA17513; Thu, 8 Apr 1999 19:38:58 -0500 (CDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma017511; Thu, 8 Apr 99 19:38:52 -0500 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id TAA35590; Thu, 8 Apr 1999 19:37:46 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Message-Id: <199904090037.TAA35590@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 MX-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: /sys/boot, egcs vs. gcc, -Os Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Chuck Robey Cc: current@FreeBSD.ORG Date: Thu, 08 Apr 1999 19:37:45 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 April 1999 at 19:25, Chuck Robey wrote: [snip] > And on top of that, there are about 5 top tracks of libs, each of these > 5 tracks (that have lots depending on them) has lived in both /usr/local > and in /usr/X11R6 in recent times, both leave ascii configuration files > behind (and in both sets of directories, depending on the age of the > older ports). Yes, I do find that very annoying. I'd like to see everything (including X) use one prefix. The next time that I install a system from scratch, I'll have everything under /opt (I use /usr/X11R6 and /opt right now) to see how it goes. I can't recall why we have /usr/X11R6, other than because of assumptions in lotsa X packages. > Just to make everything totally confused, because some > insane folks want to have multiple versions active concurrently, the > name of those config files, which exist in multiple places, have > multiple names. Insane? ``Though this be madness, yet there is a method in 't.'' If we were to remove all gtk ports but the latest (gtk12), as an example, then we would have to remove also approximately 34 ports that depend upon the older versions of GTK. > Each of the ports of the apps, which need all these > libs, have configuration scripts that go looking for all these misnamed > and misfiled config scripts, and those configuration scripts alway seem > to find the oldest and most out-of-date config script possible. AFAIK, all of the ports that depend upon gtk (again for example), correctly search for the version-dependant configuration script name (i.e. gtk10-config, gtk12-config ...). If there are those that do not, please send-pr them. If you have a better suggestion for handling this necessary complexity, I'd like to hear it. Upgrading the ports is hard enough without tilting at windmills. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17:46: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id D576815466 for ; Thu, 8 Apr 1999 17:46:03 -0700 (PDT) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id TAA17529; Thu, 8 Apr 1999 19:43:58 -0500 (CDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma017527; Thu, 8 Apr 99 19:43:55 -0500 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id TAA35633; Thu, 8 Apr 1999 19:42:49 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Message-Id: <199904090042.TAA35633@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: /sys/boot, egcs vs. gcc, -Os Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Chuck Robey Cc: current@FreeBSD.ORG Date: Thu, 08 Apr 1999 19:42:49 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 April 1999 at 19:57, Chuck Robey wrote: > Don't forget, with all the gnome and gtk ports (and the kde things) > there are various files with "config" in their names, that a bunch of > other ports depend on ... just to add confusion, and the rules for these > dependencies aren't as cut and dried as the libs, because the libs > follow usually one set of rules (laid down by the runtime linker) but > the config files, every port seems to use it's own set of rules. And > there is no "static linking" for config files, to save you. > > A lot of these config files only take effect while building other libs > or applications, which means they sometimes won't affect regular runtime > problems, just beating the heck out of the upgrade nightmare. Maybe I'm misunderstanding ... are we talking about scripts such as gnome-config or gtk12-config? These seem to be a blessing to me. It would be an order of magnitude harder to maintain GTK using ports if it weren't for the simplicity of passing GTK_CONFIG="gtk12-config" (or whichever applies) to the configure script. What problems do you believe these are causing for upgrades? Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17:53:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id CA1A414FA0 for ; Thu, 8 Apr 1999 17:53:29 -0700 (PDT) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id TAA17551 for ; Thu, 8 Apr 1999 19:51:29 -0500 (CDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma017549; Thu, 8 Apr 99 19:51:00 -0500 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id TAA35671 for ; Thu, 8 Apr 1999 19:49:54 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Message-Id: <199904090049.TAA35671@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: lists/freebsd X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine In-reply-to: <99Apr9.102050est.40374@border.alcanet.com.au> References: <99Apr9.102050est.40374@border.alcanet.com.au> Subject: Re: /sys/boot, egcs vs. gcc, -Os Mime-Version: 1.0 Content-Type: text/plain To: current@FreeBSD.ORG Date: Thu, 08 Apr 1999 19:49:53 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get the feeling (not for the first time) that perhaps it is a mistake to have the package database indexed by PKGNAME. Or at least, it seems that there isn't an easy way to get from what I'll refer to as the ``port name'' from PKGNAME. For example, the port gtk12 was once gtk-1.2.0. Now it is gtk-1.2.1. I think this contributes to the upgrade problem and tracking dependencies with the information in /var/db/pkg. I just reread that and seem to be having trouble making myself clear right now. If that didn't make perfect sense, I'll try again tomorrow after some sleep. ;-) Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 17:56:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id CB7E814FA0 for ; Thu, 8 Apr 1999 17:56:19 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id UAA22175; Thu, 8 Apr 1999 20:52:08 -0400 (EDT) Date: Thu, 8 Apr 1999 20:52:08 -0400 (EDT) From: Chuck Robey To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <99Apr9.102050est.40374@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Peter Jeremy wrote: > Chuck Robey wrote: > >Don't forget, with all the gnome and gtk ports (and the kde things) > > tcl and tk also install various version-specific information (and has > anyone else noticed that tk depends on X11 (ie XFree86) and the > XFree86 configuration (xf86site.def) changes depending on whether or > not tk exists). And if the tcl/tk stuff updated as often as the gtk/glib/gnome/kde stuff does, you'd be hearing the blues about that too. Some folks here remember my vociferous opposition to the tcl multiple version support, but once I lost the battle, it would have been poor grace to keep on fighting that. I know Satoshi won't forget that. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 18:15: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.lig.bellsouth.net (mail1.lig.bellsouth.net [205.152.0.55]) by hub.freebsd.org (Postfix) with ESMTP id 3138C14CB4; Thu, 8 Apr 1999 18:15:00 -0700 (PDT) (envelope-from gljohns@bellsouth.net) Received: from gforce.johnson.home (host-216-76-187-94.sld.bellsouth.net [216.76.187.94]) by mail1.lig.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id VAA04486; Thu, 8 Apr 1999 21:12:43 -0400 (EDT) Received: (from glenn@localhost) by gforce.johnson.home (8.9.3/8.9.3) id UAA31320; Thu, 8 Apr 1999 20:12:55 -0500 (CDT) (envelope-from glenn) From: Glenn Johnson Date: Thu, 8 Apr 1999 20:12:20 -0500 To: "David O'Brien" Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. Message-ID: <19990408201220.A26477@gforce.johnson.home> References: <19990408165056.D20453@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990408165056.D20453@nuxi.com>; from David O'Brien on Thu, Apr 08, 1999 at 04:50:56PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 08, 1999 at 04:50:56PM -0700, David O'Brien wrote: > I've only heard back from 4 folks about adding EGCS's g77 to the base > system -- all 4 said "yes". Unless I get more feedback, I will add g77 > to the base system this weekend. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) David, First off, great job on the egcs import. Maybe you have already counted me among the four, but if not, add me to the list. I would love to see g77 in the base system. Thanks. -- Glenn Johnson gljohns@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 18:18:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CC62914EF2; Thu, 8 Apr 1999 18:18:45 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id DAA95729; Fri, 9 Apr 1999 03:16:41 +0200 (CEST) (envelope-from des) To: obrien@NUXI.com Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. References: <19990408165056.D20453@nuxi.com> From: Dag-Erling Smorgrav Date: 09 Apr 1999 03:16:41 +0200 In-Reply-To: "David O'Brien"'s message of "Thu, 8 Apr 1999 16:50:56 -0700" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: > I've only heard back from 4 folks about adding EGCS's g77 to the base > system -- all 4 said "yes". Unless I get more feedback, I will add g77 > to the base system this weekend. I beg your pardon? You're adding g77 to the system because you know of four people who would find it useful? Where's the logic in that? If you do add it to the base system, make it optional. I don't care if it defaults to on, as long as I have the option to turn it off. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 18:20:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id BCE4C14EF2; Thu, 8 Apr 1999 18:20:38 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA22293; Thu, 8 Apr 1999 21:16:28 -0400 (EDT) Date: Thu, 8 Apr 1999 21:16:28 -0400 (EDT) From: Chuck Robey To: Dag-Erling Smorgrav Cc: obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Apr 1999, Dag-Erling Smorgrav wrote: > "David O'Brien" writes: > > I've only heard back from 4 folks about adding EGCS's g77 to the base > > system -- all 4 said "yes". Unless I get more feedback, I will add g77 > > to the base system this weekend. > > I beg your pardon? You're adding g77 to the system because you know of > four people who would find it useful? Where's the logic in that? > > If you do add it to the base system, make it optional. I don't care if > it defaults to on, as long as I have the option to turn it off. If that gives me the option to bring in gcj and libgcj, then I think it's a GREAT idea. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 18:20:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 0FE8814EF2; Thu, 8 Apr 1999 18:20:45 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id NAA19082; Fri, 9 Apr 1999 13:18:42 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.2/8.9.2) id NAA52526; Fri, 9 Apr 1999 13:18:24 +1200 (NZST) (envelope-from jabley) Date: Fri, 9 Apr 1999 13:18:24 +1200 From: Joe Abley To: Dag-Erling Smorgrav Cc: obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: ATTENTION PLEASE: g77 in base system. Message-ID: <19990409131824.A52442@clear.co.nz> References: <19990408165056.D20453@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Apr 09, 1999 at 03:16:41AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 09, 1999 at 03:16:41AM +0200, Dag-Erling Smorgrav wrote: > "David O'Brien" writes: > > I've only heard back from 4 folks about adding EGCS's g77 to the base > > system -- all 4 said "yes". Unless I get more feedback, I will add g77 > > to the base system this weekend. > > I beg your pardon? You're adding g77 to the system because you know of > four people who would find it useful? Where's the logic in that? > > If you do add it to the base system, make it optional. I don't care if > it defaults to on, as long as I have the option to turn it off. Oh good lord, not again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 18:25: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 7D1DB1515C for ; Thu, 8 Apr 1999 18:24:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA23078; Fri, 9 Apr 1999 10:52:55 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA24142; Fri, 9 Apr 1999 10:52:53 +0930 (CST) Message-ID: <19990409105253.S2142@lemis.com> Date: Fri, 9 Apr 1999 10:52:53 +0930 From: Greg Lehey To: Michael Reifenberger , greg@lemis.com Cc: FreeBSD-Current Subject: Re: Panic: Invalid longjmp with vinum configured by novice References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Michael Reifenberger on Fri, Apr 09, 1999 at 12:35:07AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Friday, 9 April 1999 at 0:35:07 +0200, Michael Reifenberger wrote: > Hi, > I often get to above message while trying to configure vinum. > Trying the examples from the manpage works, of course. > Next try. > What I want to do: > First creating a non mirrored but striped volume and later add one mirror plex. > > I do: > # vinum start You don't need to do this unless you already have objects defined from an earlier run of vinum. > # vinum resetconfig You never need to do this after a start. To quote vinum(8): resetconfig The resetconfig command completely obliterates the vinum configu- ration on a system. Use this command only when you want to com- pletely delete the configuration. vinum will ask for confirma- tion: you must type in the words NO FUTURE exactly as shown: # vinum resetconfig WARNING! This command will completely wipe out your vinum configuration. All data will be lost. If you really want to do this, enter the text NO FUTURE Enter text -> NO FUTURE Vinum configuration obliterated As the message suggests, this is a last-ditch command. Don't use it unless you have an existing configuration which you never want to see again. Later: 3. Some of the commands currently supported by vinum are not really needed. For reasons which I don't understand, however, I find that users frequently try the label and resetconfig commands, though es- pecially resetconfig outputs all sort of dire warnings. Don't use these commands unless you have a good reason to do so. > # cat x > drive d1 device /dev/da1d > drive d2 device /dev/da2d > volume raid > plex org stripe 256k > sd length 50m drive d1 > sd length 50m drive d2 > vinum create x > ... > (Please note the missing 'd' in stripe) > > I get: > ..the panic.. > > Sigh. Agreed. *sigh*. I found about this problem last night, and I've fixed it, but I have only just committed it. It's a result of the change in the kernel address space. > BTW: Any chance that the create commands will work interactive from > within vinum? Not much. It's trivial to implement, but just another way of shooting yourself in the foot. > I suspect one will not have a r/w filesystem in worst case scenarios > for creating vinum createfiles (And even if, `ed` is not my friend.) Hmm. I suppose that might be an argument. But vinum(8) doesn't offer you much in the way of editing facilities either. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 18:29:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id E7CBF14CD1 for ; Thu, 8 Apr 1999 18:29:24 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id JAA09941 for ; Fri, 9 Apr 1999 09:27:19 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA07086; Fri, 9 Apr 1999 09:27:19 +0800 Message-Id: <199904090127.JAA07086@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: CAM changes causing prob? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Apr 1999 09:27:19 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After the last lot of CAM changes, I occasionally get processes hanging attempting to access my QIC-525 tape drive. They can't be killed, so doing backups can be a mite troublesome. Sometimes it works, sometimes it doesn't. There seems to be some relation to how recently the last lot of tape activity was (althought this is rather tenuous). Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 18:57:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 0A42114C15; Thu, 8 Apr 1999 18:57:32 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-146.ix.netcom.com [209.109.232.146]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id SAA05254; Thu, 8 Apr 1999 18:55:50 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id SAA98077; Thu, 8 Apr 1999 18:55:26 -0700 (PDT) Date: Thu, 8 Apr 1999 18:55:26 -0700 (PDT) Message-Id: <199904090155.SAA98077@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: obrien@NUXI.com Cc: current@freebsd.org, hackers@freebsd.org In-reply-to: <19990408165056.D20453@nuxi.com> (obrien@NUXI.com) Subject: Re: ATTENTION PLEASE: g77 in base system. From: asami@freebsd.org (Satoshi - the Ports Wraith - Asami) References: <19990408165056.D20453@nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "David O'Brien" * I've only heard back from 4 folks about adding EGCS's g77 to the base * system -- all 4 said "yes". Unless I get more feedback, I will add g77 * to the base system this weekend. Sorry, I wasn't paying enough attention I guess. What's wrong with it being a port? If the answer is "it's very hard to separate just the g77 functionality into /usr/local", then count me as a yes. If it is "some people want it in the base system", then count me as a no. -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 19: 3:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id DC76914CAB for ; Thu, 8 Apr 1999 19:03:49 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id WAA13233; Thu, 8 Apr 1999 22:01:32 -0400 (EDT) Message-ID: <19990408220132.A12977@netmonger.net> Date: Thu, 8 Apr 1999 22:01:32 -0400 From: Christopher Masto To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: UPDATING needs updating References: <19990408142419.A24545@netmonger.net> <63587.923622867@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <63587.923622867@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Apr 09, 1999 at 03:54:27AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 09, 1999 at 03:54:27AM +0200, Sheldon Hearn wrote: > > > On Thu, 08 Apr 1999 14:24:19 -0400, Christopher Masto wrote: > > > Mightn't it be a good idea to mention the egcs move in /usr/src/UPDATING? > > Now that both bootstrapping and -j8 seem to be working, it wouldn't be > very useful. Not very useful to tell people about the first major compiler change in years? It may not break "make world", but it certainly breaks things like C++ library compatability and a large part of the ports collection. Suprises should be documented. -current users should be reading -current, but that doesn't mean someone might not join after the egcs discussion. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 19:12:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id D372514E87 for ; Thu, 8 Apr 1999 19:12:30 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-146.ix.netcom.com [209.109.232.146]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id TAA05271; Thu, 8 Apr 1999 19:10:48 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id TAA98121; Thu, 8 Apr 1999 19:10:18 -0700 (PDT) Date: Thu, 8 Apr 1999 19:10:18 -0700 (PDT) Message-Id: <199904090210.TAA98121@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: n@nectar.com Cc: current@FreeBSD.ORG In-reply-to: <199904090049.TAA35671@spawn.nectar.com> (message from Jacques Vidrine on Thu, 08 Apr 1999 19:49:53 -0500) Subject: ports dependencies (Re: /sys/boot, egcs vs. gcc, -Os) From: asami@FreeBSD.ORG (Satoshi - the Ports Wraith - Asami) References: <99Apr9.102050est.40374@border.alcanet.com.au> <199904090049.TAA35671@spawn.nectar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm just skimming through this discussion, as I don't have time to read them all. People, I know you are annoyed by many stupid things software authors have done in the past to make your life miserable (and believe me, I probably have more horror stories than most of you), but can you trim those bits a little so we can have a meaningful discussion? :) About the shlib stuff: the biggest problem is not the lack of support by the ports system, but the incompatibilities between various "libfoo.so.N"s floating around. The shlib versions are almost never bumped correctly, and that results in the "why doesn't my libintl.so.1 work with the latest gnome when it's building on Satoshi's machine" problems. To (at least partially) solve this problem, I added a ALWAYS_BUILD_DEPENDS variable to the latest bsd.port.mk. Please recommend people to try it if they are having these kinds of stuff. * From: Jacques Vidrine * I get the feeling (not for the first time) that perhaps it is a * mistake to have the package database indexed by PKGNAME. Or at * least, it seems that there isn't an easy way to get from what * I'll refer to as the ``port name'' from PKGNAME. For example, * the port gtk12 was once gtk-1.2.0. Now it is gtk-1.2.1. I * think this contributes to the upgrade problem and tracking * dependencies with the information in /var/db/pkg. Finally! I've been talking about this for years, the only part that was missing was a programmer. Now, do I hear a volunteer? :) -PW P.S. The past few "volunteers" have disappeared without trace but I have a feeling Jacques is different. :> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 19:14:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-82.camalott.com [208.229.74.82]) by hub.freebsd.org (Postfix) with ESMTP id 0822E14DA4; Thu, 8 Apr 1999 19:13:53 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.1) id VAA67418; Thu, 8 Apr 1999 21:11:55 -0500 (CDT) (envelope-from joelh) To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: -jN make world References: <19990408094422.A18106@nuxi.com> From: Joel Ray Holveck Date: 08 Apr 1999 21:11:53 -0500 In-Reply-To: "David O'Brien"'s message of "Thu, 8 Apr 1999 09:44:22 -0700" Message-ID: <86n20iwniu.fsf@detlev.UUCP> Lines: 13 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think I may have fixed the problem in the Makefile... well I might have > fixed another smaller problem, but it is now more broken than before and > -jN should work. If it's not yet fixed, why don't we add something to the buildworld target that checks MAKEFLAGS for -j and issues an error or warning if it's found? -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 19:20: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-82.camalott.com [208.229.74.82]) by hub.freebsd.org (Postfix) with ESMTP id 1E62014F89; Thu, 8 Apr 1999 19:19:36 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.1) id VAA78893; Thu, 8 Apr 1999 21:17:34 -0500 (CDT) (envelope-from joelh) To: Steve Price Cc: Peter Jeremy , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: emacs* broken in -current (was Re: Vtable thunks with egcs) References: From: Joel Ray Holveck Date: 08 Apr 1999 21:17:31 -0500 In-Reply-To: Steve Price's message of "Thu, 8 Apr 1999 17:58:59 -0500 (CDT)" Message-ID: <86lng2wn9g.fsf@detlev.UUCP> Lines: 23 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You are absolutely right. I just tried the new version of emacs > that I built on my pre-egcs box and it doesn't work on that box > either. This definitely doesn't appear to be anything caused by > changing to egcs. Not that it matters much but for grins I just > built/installed the xemacs port and it _does_ appear to work. I've been having no problems with an Emacs 20.3 and X11R6 built in October on a -current system from April 6. (The Emacs is ELF, and built from my own sources instead of the port.) I'd like to track this down; could people give me more info privately? rms is looking at releasing a mostly bugfix Emacs, possibly tommorow, but it may be another month (he's about to leave town). I haven't been watching the changes; there may be some X-related fixes in there. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 19:21: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from h24-64-221-247.gv.wave.shaw.ca (24.64.221.247.bc.wave.home.com [24.64.221.247]) by hub.freebsd.org (Postfix) with ESMTP id F210D15A61 for ; Thu, 8 Apr 1999 19:21:06 -0700 (PDT) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.3/8.9.2) with ESMTP id TAA05753; Thu, 8 Apr 1999 19:19:04 -0700 (PDT) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199904090219.TAA05753@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Zepeda Cc: current Subject: Re: msdosfs problems? In-reply-to: Your message of "Thu, 08 Apr 1999 17:24:10 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Apr 1999 19:19:04 -0700 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got all my mp3s stored on my fat16 partition so I can easily share > them between Win98 and fbsd. However recently mpg123 has been complaining > about once valid mp3s: Hmm, odd, I'm doing exactly the same thing and have never had any problems. I play them from a 3 gig FAT16 partition with 64K clusters. I usually use x11amp, but haven't had any problems with mpg123 either, same version you're using. I'm running -current as of yesterday; I load msdosfs as a KLD. If yours is statically compiled in, maybe try the module? good luck, Jake -- we are but packets in the internet of life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 19:26:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7EE4715A50 for ; Thu, 8 Apr 1999 19:26:23 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA47347 for ; Thu, 8 Apr 1999 22:23:41 -0400 (EDT) Date: Thu, 8 Apr 1999 22:23:39 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: make world breakage?!? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am I the only one to get this error?? cc -nostdinc -O -pipe -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd -I. -I/usr/src/usr.sbin/amd/amd -I/usr/src/usr.sbin/amd/amd/../include -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/include -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd/clock.c /usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd/clock.c:66: redefinition of `struct callout' *** Error code 1 Stop. It's been like this here for days, and noone's reported it. I can't figure out what's wrong with it :( I don't see how it could possibly be including sys/callout.h! *breaks down into sobbing and gibberish* Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 19:56:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 44D0915A1E for ; Thu, 8 Apr 1999 19:56:42 -0700 (PDT) (envelope-from tr49986@rcc.on.ca) Received: from rcc.on.ca (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with ESMTP id AAA19376 for ; Fri, 9 Apr 1999 00:13:49 -0400 Message-ID: <370DB2F1.95CE6490@rcc.on.ca> Date: Fri, 09 Apr 1999 03:57:38 -0400 From: Rod Taylor X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: CD Mount Troubles Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My Joliet formated cd's aren't mounting with the Joliet extensions. I believe I saw that FreeBSD supported these extensions. I'm mounting mostly recorded cds, in older nec cdrom drives. (OS/2 mounts joliet extensions fine on same machine). Some disks done mount at all, and are complained about. It reports that the cd just plain old 'does not exist'. This is with the older atapi drivers, as the new ones don't support my nec 4x4 changers (as per the last time I tried them). If required, access can be given to the system. (for the appropriate person, whoever they might be). Thanks!. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 19:57:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from s3000-01.magna.com.au (s3000-01.magna.com.au [203.4.212.1]) by hub.freebsd.org (Postfix) with ESMTP id 58EA215AB3 for ; Thu, 8 Apr 1999 19:57:22 -0700 (PDT) (envelope-from guru@b0rk.looksharp.net) Received: from EventHorizon (maccess-01-033.magna.com.au [203.111.85.33]) by s3000-01.magna.com.au (8.9.1/8.9.1/Magna Data/1.2) with SMTP id MAA12226 for ; Fri, 9 Apr 1999 12:55:17 +1000 (EST) Message-Id: <3.0.3.32.19990409125246.00990d60@b0rk.looksharp.net> X-Sender: guru@b0rk.looksharp.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 09 Apr 1999 12:52:46 +1000 To: freebsd-current@freebsd.org From: GuRu Subject: PPP problems in -CURRENT Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsupped, built CURRENT as of April 8th, upgrading a 3.1-STABLE system to 4.0. A reboot later, all seems fine, except that I'm experiencing severe problems connecting to my ISP. Everything goes well till after the login phase, when entering the lcp negotiation phase, then things get FUBARed. (passwords have been deliberately blanked, of course. :P) I believe that both peers are attempting to negotiate an IP address, but are failing to do so as shown by the repeated negotiation attempts. The same PPP configuration file worked as of 24 hours ago on 3.1-STABLE. Any insight would be greatly appreciated. Apr 8 21:15:56 Tasha ppp[294]: Phase: Using interface: tun0 Apr 8 21:15:56 Tasha ppp[294]: Phase: deflink: Created in closed state Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: set device /dev/cuaa1 Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: set speed 115200 Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: deny lqr Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: set dial ABORT BUSY ABORT NO\sCARRIER TIMEOUT 5 "" AT OK-AT-OK ATE1Q0 OK \dATDT\T TIMEOUT 40 CONNECT Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: alias enable yes Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set phone xxxxxxx Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set login ABORT NO\sCARRIER TIMEOUT 5 ogin:--ogin: login word: word Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set server xxxx ******** Apr 8 21:15:56 Tasha ppp[294]: tun0: Phase: Listening at port 4040. Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set timeout 0 Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set ifaddr 10.0.0.1/0 10.0.0.2/0 0.0.0.0 0.0.0.0 Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: add default HISADDR Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: PPP Started (background mode). Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: bundle: Establish Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: deflink: closed -> opening Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: deflink: Connected! Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: deflink: opening -> dial Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: Phone: xxxxxxx Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: deflink: Dial attempt 1 of 1 Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Send: AT^M Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Expect(5): OK Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Received: AT^M^M Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Received: OK^M Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Send: ATE1Q0^M Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Expect(5): OK Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Received: ATE1Q0^M^M Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Received: OK^M Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Send: ATDTxxxxxxxx^M Apr 8 21:15:58 Tasha ppp[295]: tun0: Chat: Expect(40): CONNECT Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: ATDTxxxxxxxx^M^M Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: CONNECT 33600/ARQ/V34/LAPM/V42BIS^M Apr 8 21:16:13 Tasha ppp[295]: tun0: Phase: deflink: dial -> login Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Expect(5): ogin: Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: ^M Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: login: Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Send: login^M Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Expect(5): word: Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: Password: Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Send: password^M Apr 8 21:16:13 Tasha ppp[295]: tun0: Phase: deflink: login -> lcp Apr 8 21:16:13 Tasha ppp[295]: tun0: LCP: FSM: Using "deflink" as a transport Apr 8 21:16:13 Tasha ppp[295]: tun0: LCP: deflink: State change Initial --> Closed Apr 8 21:16:13 Tasha ppp[295]: tun0: LCP: deflink: State change Closed --> Stopped Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: deflink: LayerStart Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x00000000 Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: deflink: State change Stopped --> Req-Sent Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(6) state = Req-Sent Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(6) state = Req-Sent Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: deflink: State change Req-Sent --> Ack-Sent Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(2) state = Ack-Sent Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(7) state = Ack-Sent Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(7) state = Ack-Sent Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(2) state = Ack-Sent Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(8) state = Ack-Sent Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(8) state = Ack-Sent Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(9) state = Ack-Sent Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(9) state = Ack-Sent Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(2) state = Ack-Sent Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(10) state = Ack-Sent Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(10) state = Ack-Sent Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(2) state = Ack-Sent Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(11) state = Ack-Sent Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(11) state = Ack-Sent Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] Apr 8 21:16:29 Tasha ppp[295]: tun0: LCP: deflink: LayerFinish Apr 8 21:16:29 Tasha ppp[295]: tun0: LCP: deflink: State change Ack-Sent --> Stopped Apr 8 21:16:29 Tasha ppp[295]: tun0: LCP: deflink: State change Stopped --> Closed Apr 8 21:16:29 Tasha ppp[295]: tun0: LCP: deflink: State change Closed --> Initial Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: deflink: Disconnected! Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: deflink: lcp -> hangup Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: deflink: Connect time: 33 secs: 408 octets in, 539 octets out Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: total 28 bytes/sec, peak 76 bytes/sec on Thu Apr 8 21:16:29 1999 Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: deflink: hangup -> closed Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: bundle: Dead Apr 8 21:16:59 Tasha ppp[295]: tun0: Phase: PPP Terminated (normal). Apr 8 21:16:59 Tasha ppp[295]: tun0: Phase: Parent notified of success. Apr 8 21:16:59 Tasha ppp[294]: tun0: Phase: Parent: Child failed (errdead). -- K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 20: 1:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id 1614515A1E; Thu, 8 Apr 1999 20:01:22 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id UAA19600; Thu, 8 Apr 1999 20:59:04 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Thu, 8 Apr 1999 20:59:04 -0600 (MDT) From: Brian Handy To: Dag-Erling Smorgrav Cc: obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Apr 1999, Dag-Erling Smorgrav wrote: >> [4 people said "YES! Add g77!"] >I beg your pardon? You're adding g77 to the system because you know of >four people who would find it useful? Where's the logic in that? Well, statistically speaking, that's a bunch of "ayes" and no "noes". Lots of things happen via implicit acceptance. (I was one of the people who spoke up in favor of this after David mentioned this.) >If you do add it to the base system, make it optional. I don't care if >it defaults to on, as long as I have the option to turn it off. This doesn't seem unreasonable. (I also really like Chuck's idea of adding gcj in the same light.) Happy trails, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 20: 3:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id BABDA15A1E for ; Thu, 8 Apr 1999 20:03:21 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA17234; Fri, 9 Apr 1999 12:31:12 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <370DB2F1.95CE6490@rcc.on.ca> Date: Fri, 09 Apr 1999 12:32:08 +0930 (CST) From: "Daniel O'Connor" To: Rod Taylor Subject: RE: CD Mount Troubles Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Apr-99 Rod Taylor wrote: > My Joliet formated cd's aren't mounting with the Joliet extensions. I > believe I saw that FreeBSD supported these extensions. I'm mounting > mostly recorded cds, in older nec cdrom drives. (OS/2 mounts joliet > extensions fine on same machine). There are patches which add Joliet support, but they don't work 100%.. I have a CD which gets mangled with the patches, so I haven't submitted them yet :) > Some disks done mount at all, and are complained about. It reports that > the cd just plain old 'does not exist'. ? You mean you get an I/O error? A Joliet CD should mount, just that you'll get Windows short names instead of long names. --- 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-current" in the body of the message From owner-freebsd-current Thu Apr 8 20:37:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (Postfix) with ESMTP id B1A0C14FC3 for ; Thu, 8 Apr 1999 20:37:37 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id WAA14496; Thu, 8 Apr 1999 22:35:30 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.9.3/8.9.3) id WAA84513; Thu, 8 Apr 1999 22:27:48 -0500 (CDT) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Date: Thu, 8 Apr 1999 22:27:32 -0500 (CDT) To: Chuck Robey Cc: Alex Zepeda , John Polstra , asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14093.29000.147643.10859@zuhause.mn.org> Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey writes: > If that were true, but it's not. Older versions of the config files and > libraries can very easily cause the ports to fail to build. Every time > I upgrade stuff, I have to go about doing search and destroy on old > stuff. On top of that, there are various mistakes in dependencies; > there's one lib (I forget which) which installs under one name, but all > of the dependencies on it are under another name. The stuff seems to > change it's mind on whether it wants to install under /usr/local or > /usr/X11R6, so finding stuff is pretty complicated, and very dependent > on version, because the darn install dirs change, just to make things > worse. I'll bet the library you're thinking of is libtix. David O'Brien just committed fixes for it yesterday. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 21:26:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 6F98E14EB5; Thu, 8 Apr 1999 21:26:45 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id VAA93282; Thu, 8 Apr 1999 21:21:58 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904090421.VAA93282@troutmask.apl.washington.edu> Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <199904090155.SAA98077@silvia.hip.berkeley.edu> from Satoshi - the Ports Wraith - Asami at "Apr 8, 1999 06:55:26 pm" To: asami@FreeBSD.ORG (Satoshi - the Ports Wraith - Asami) Date: Thu, 8 Apr 1999 21:21:58 -0700 (PDT) Cc: obrien@NUXI.com, current@FreeBSD.ORG, hackers@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi - the Ports Wraith - Asami wrote: > * From: "David O'Brien" > > * I've only heard back from 4 folks about adding EGCS's g77 to the base > * system -- all 4 said "yes". Unless I get more feedback, I will add g77 > * to the base system this weekend. > > Sorry, I wasn't paying enough attention I guess. What's wrong with it > being a port? > > If the answer is "it's very hard to separate just the g77 > functionality into /usr/local", then count me as a yes. If it is > "some people want it in the base system", then count me as a no. > Speaking of ports, I have a working port of f2c and a new f77(1) wrapper sitting on my machine. The f2c port includes all of the FreeBSD changes to the f2c in usr/src. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 21:30:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id B304814EB5; Thu, 8 Apr 1999 21:30:48 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id VAA93304; Thu, 8 Apr 1999 21:25:59 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904090425.VAA93304@troutmask.apl.washington.edu> Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: from Dag-Erling Smorgrav at "Apr 9, 1999 03:16:41 am" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Thu, 8 Apr 1999 21:25:59 -0700 (PDT) Cc: obrien@NUXI.com, current@FreeBSD.ORG, hackers@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > "David O'Brien" writes: > > I've only heard back from 4 folks about adding EGCS's g77 to the base > > system -- all 4 said "yes". Unless I get more feedback, I will add g77 > > to the base system this weekend. > > I beg your pardon? You're adding g77 to the system because you know of > four people who would find it useful? Where's the logic in that? Please add g77. That's five. Search the mail archive for the last round of Fortran discussion. > If you do add it to the base system, make it optional. I don't care if > it defaults to on, as long as I have the option to turn it off. A knob would be fine, but you're saving yourself 100k or so of disk space and 5 minutes during "make world". -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 22:23:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id A4A6B14FAD for ; Thu, 8 Apr 1999 22:23:40 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.167]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA36BB; Fri, 9 Apr 1999 07:21:38 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id HAA65708; Fri, 9 Apr 1999 07:21:55 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990408164830.C20453@nuxi.com> Date: Fri, 09 Apr 1999 07:21:54 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "David O'Brien" Subject: Re: EGCS troubles Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Apr-99 David O'Brien wrote: >> > Something broken in new egcs c++ compiler - jade doesn't work with >> > following symptoms (checked on two machines). >> >> Apr 7 20:26:04 daemon /kernel: pid 61135 (jade), uid 0: exited on >> signal >> 11 (core dumped) >> >> Verified... >> >> David, might this be due to the compiler itself of the libraries? >> Any way of making certain? > > Compile Jade with "-g" and see where in the coredump the signal 11 is > occuring. What does ``ldd jade'' show? You might be mixing shared libs, > that doesn't work for C++. Could also be an exceptions problem. Try > compiling with -fnoexpcetions. [asmodai@daemon] (163) $ ldd /usr/local/bin/jade /usr/local/bin/jade: libstyle.so.1 => /usr/local/lib/libstyle.so.1 (0x280b6000) libspgrove.so.1 => /usr/local/lib/libspgrove.so.1 (0x282ac000) libgrove.so.1 => /usr/local/lib/libgrove.so.1 (0x282ef000) libsp.so.1 => /usr/local/lib/libsp.so.1 (0x282f7000) libintl.so.1 => /usr/local/lib/libintl.so.1 (0x284ce000) libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x284d2000) libm.so.2 => /usr/lib/libm.so.2 (0x2850d000) libc.so.3 => /usr/lib/libc.so.3 (0x28527000) I know for certain that libintl is gcc. Will go and do recompilations of all stuff this weekend *sigh* ;) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 22:52: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E6CCE14F25 for ; Thu, 8 Apr 1999 22:51:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA23692; Thu, 8 Apr 1999 23:49:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA10900; Thu, 8 Apr 1999 23:51:20 -0600 (MDT) Message-Id: <199904090551.XAA10900@harmony.village.org> To: Christopher Masto Subject: Re: UPDATING needs updating Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Apr 1999 14:24:19 EDT." <19990408142419.A24545@netmonger.net> References: <19990408142419.A24545@netmonger.net> Date: Thu, 08 Apr 1999 23:51:20 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990408142419.A24545@netmonger.net> Christopher Masto writes: : Mightn't it be a good idea to mention the egcs move in /usr/src/UPDATING? I suppose. What should we say about it? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 23:26:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 41B4A14D7F for ; Thu, 8 Apr 1999 23:26:36 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA23744; Fri, 9 Apr 1999 00:24:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA53843; Fri, 9 Apr 1999 00:26:08 -0600 (MDT) Message-Id: <199904090626.AAA53843@harmony.village.org> To: obrien@NUXI.com Subject: Re: CPP broken on egcs current Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Apr 1999 12:26:07 PDT." <19990408122607.A19098@nuxi.com> References: <19990408122607.A19098@nuxi.com> <19990405130529.H22022@nuxi.com> <199904051112.NAA22210@trantor.xs4all.nl> <199904051738.KAA91678@vashon.polstra.com> <19990405130529.H22022@nuxi.com> <199904081734.LAA54417@harmony.village.org> Date: Fri, 09 Apr 1999 00:26:07 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990408122607.A19098@nuxi.com> "David O'Brien" writes: : > ===> rpcsvc : > rpcgen -C -h -DWANT_NFS3 /home/imp/FreeBSD/src/include/rpcsvc/key_prot.x -o key_prot.h : > /home/imp/FreeBSD/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Internal compiler error in function main : : What rev of contrib/egcs/gcc/config/freebsd.h do you have? One that was new enough, but the cpp that was installed was bogus. The make clean make all make install in cpp (with a little hackery) did the trick. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 8 23:29:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EA51114CCB for ; Thu, 8 Apr 1999 23:29:34 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA23754; Fri, 9 Apr 1999 00:27:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA54901; Fri, 9 Apr 1999 00:29:04 -0600 (MDT) Message-Id: <199904090629.AAA54901@harmony.village.org> To: Christopher Masto Subject: Re: UPDATING needs updating Cc: Sheldon Hearn , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Apr 1999 22:01:32 EDT." <19990408220132.A12977@netmonger.net> References: <19990408220132.A12977@netmonger.net> <19990408142419.A24545@netmonger.net> <63587.923622867@axl.noc.iafrica.com> Date: Fri, 09 Apr 1999 00:29:04 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990408220132.A12977@netmonger.net> Christopher Masto writes: : Not very useful to tell people about the first major compiler change : in years? It may not break "make world", but it certainly breaks : things like C++ library compatability and a large part of the ports : collection. : : Suprises should be documented. -current users should be reading -current, : but that doesn't mean someone might not join after the egcs discussion. Check out what I just committed and let me know if it is what you had in mind. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 0: 2: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 7218614F96 for ; Fri, 9 Apr 1999 00:02:02 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async3-00.iptelecom.net.ua [212.42.68.192]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id KAA08170; Fri, 9 Apr 1999 10:00:10 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id JAA74176; Fri, 9 Apr 1999 09:58:48 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <370DA528.A37CFCD6@altavista.net> Date: Fri, 09 Apr 1999 09:58:48 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: EGCS troubles References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Compile Jade with "-g" and see where in the coredump the signal 11 is > > occuring.  What does ``ldd jade'' show?  You might be mixing shared libs, > > that doesn't work for C++.  Could also be an exceptions problem.  Try > > compiling with -fnoexpcetions. > > [asmodai@daemon] (163) $ ldd /usr/local/bin/jade > /usr/local/bin/jade: >         libstyle.so.1 => /usr/local/lib/libstyle.so.1 (0x280b6000) >         libspgrove.so.1 => /usr/local/lib/libspgrove.so.1 (0x282ac000) >         libgrove.so.1 => /usr/local/lib/libgrove.so.1 (0x282ef000) >         libsp.so.1 => /usr/local/lib/libsp.so.1 (0x282f7000) >         libintl.so.1 => /usr/local/lib/libintl.so.1 (0x284ce000) >         libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x284d2000) >         libm.so.2 => /usr/lib/libm.so.2 (0x2850d000) >         libc.so.3 => /usr/lib/libc.so.3 (0x28527000) > > I know for certain that libintl is gcc. > > Will go and do recompilations of all stuff this weekend *sigh*  ;) >   In my case (it seems all libs compiled under egcs - exactly when jade compiled): /usr/local/bin/jade:         libstyle.so.1 => /usr/local/lib/libstyle.so.1 (0x280b9000)         libspgrove.so.1 => /usr/local/lib/libspgrove.so.1 (0x282b6000)         libgrove.so.1 => /usr/local/lib/libgrove.so.1 (0x282f9000)         libsp.so.1 => /usr/local/lib/libsp.so.1 (0x28301000)         libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x284e4000)         libm.so.2 => /usr/lib/libm.so.2 (0x28521000)         libc.so.3 => /usr/lib/libc.so.3 (0x2853c000)   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 0: 3: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id E243314F96 for ; Fri, 9 Apr 1999 00:03:00 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA26586; Fri, 9 Apr 1999 17:00:59 +1000 Date: Fri, 9 Apr 1999 17:00:59 +1000 From: Bruce Evans Message-Id: <199904090700.RAA26586@godzilla.zeta.org.au> To: bde@zeta.org.au, green@unixhelp.org Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG, jdp@polstra.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "CC+=-Os" in individual Makefiles works about as well as "CFLAGS+=-Os" for >> adding flags. That's not very well. Removing unwanted additions is hard. >Why don't we have a -= operator in make(1)? Substitution can replace -= in may cases, e.g.: CC:= ${CC:S/-Os//} This is "hard" because it has to be coded in the makefile, while additions can be passed to make. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 0:49: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (ghana-169.ppp.hooked.net [206.169.228.169]) by hub.freebsd.org (Postfix) with ESMTP id A2EC014FD4 for ; Fri, 9 Apr 1999 00:48:58 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id AAA00306; Fri, 9 Apr 1999 00:46:44 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Fri, 9 Apr 1999 00:46:43 -0700 (PDT) From: Alex Zepeda To: Jake Cc: current Subject: Re: msdosfs problems? In-Reply-To: <199904090219.TAA05753@h24-64-221-247.gv.wave.shaw.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, Jake wrote: > I usually use x11amp, but haven't had any problems with mpg123 either, > same version you're using. > > I'm running -current as of yesterday; I load msdosfs as a KLD. > If yours is statically compiled in, maybe try the module? Yes, it's statically linked in, and it truely seems to be some problem with fbsd. I booted into 98 and used Winamp and it played fine. I'm reasonably afraid to touch the zip drive... - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 0:52:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id A2A5F14D74 for ; Fri, 9 Apr 1999 00:52:49 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id IAA17759; Fri, 9 Apr 1999 08:50:48 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Fri, 9 Apr 1999 08:42:55 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19990408164414.A20453@nuxi.com> References: ; from Bob Bishop on Thu, Apr 08, 1999 at 08:11:43PM +0000 <19990408094422.A18106@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 9 Apr 1999 08:42:52 +0000 To: obrien@NUXI.com From: Bob Bishop Subject: Re: -jN make world Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 4:44 pm -0700 8/4/99, David O'Brien wrote: > >Please try rev 1.24 of src/gnu/usr.bin/cc/cc_tools/Makefile. That one works -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 2:30:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.mishkei.org.il (mail.mishkei.org.il [62.0.64.8]) by hub.freebsd.org (Postfix) with ESMTP id E5DEA1523E for ; Fri, 9 Apr 1999 02:30:23 -0700 (PDT) (envelope-from rom_glsa@ein-hashofet.co.il) Received: from ein-hashofet.co.il (host40-68.mishkei.org.il [62.0.68.40]) by mail.mishkei.org.il (8.9.3/8.9.3) with ESMTP id MAA01519 for ; Fri, 9 Apr 1999 12:27:33 +0300 (IDT) Message-ID: <370DF25C.9AE69160@ein-hashofet.co.il> Date: Fri, 09 Apr 1999 12:28:13 +0000 From: Gilad Rom X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Make world is broken for days now... :( Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, For the past week, I've been trying to build world, in order to get then new egcs up and running. Everytime I try to make world, I get the following: ===> cc_tools cc -O -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/objc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -c /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c In file included from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/xm-i386.h:43, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/hconfig.h:2, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:22: /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: linux.h: No such file or directory /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:4: i386/freebsd-elf.h: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. This has been happening to me ever since monday. CVSupped several times a day ever since, And I cant seem to get past it. I must have done something wrnog, Im sure of it, but I cant seem to track it down. Last cvsup on Friday morning. -- Gilad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 2:34:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 2355C15480 for ; Fri, 9 Apr 1999 02:34:36 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id LAA26424; Fri, 9 Apr 1999 11:32:34 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id LAA14632; Fri, 9 Apr 1999 11:32:34 +0200 (MET DST) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id LAA10385; Fri, 9 Apr 1999 11:31:19 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Fri, 9 Apr 1999 11:31:18 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: FreeBSD-Current Subject: Re: Panic: Invalid longjmp with vinum configured by novice In-Reply-To: <19990409105253.S2142@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 9 Apr 1999, Greg Lehey wrote: ... > > # vinum start > > You don't need to do this unless you already have objects defined from > an earlier run of vinum. Ah, ok. > > > # vinum resetconfig > > You never need to do this after a start. To quote vinum(8): I was aware of the fact that this command ist not for the normal use. I just wanted to set a clean startingpoint for this example. > Not much. It's trivial to implement, but just another way of shooting > yourself in the foot. I find the configfile appropriate for initial confiurations. But what is the best method if one disk faults and gets replaced. Then I shouldn't need the overall confguration. Unfortunately the documentation is not that specific about this point, one should need only to recreate the subdisks which laid on the faulty disk after creating a vinum slice on the fresh disk, right? Or does vinum replicates itself after the failure onto the fresh disk? > > > I suspect one will not have a r/w filesystem in worst case scenarios > > for creating vinum createfiles (And even if, `ed` is not my friend.) > > Hmm. I suppose that might be an argument. But vinum(8) doesn't offer > you much in the way of editing facilities either. A command history and commandline editing :-) And many thanks for helping anyway! Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 2:40: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id AF246151C5; Fri, 9 Apr 1999 02:39:58 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA67981; Fri, 9 Apr 1999 02:37:38 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Chuck Robey Cc: "David O'Brien" , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-reply-to: Your message of "Thu, 08 Apr 1999 20:00:10 EDT." Date: Fri, 09 Apr 1999 02:37:37 -0700 Message-ID: <67979.923650657@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yeah, I'm serious, I would really like gcj+libgcj, to get java stuff > compiled (non portably) into binaries on FreeBSD. 1. I agree in principle. 2. I'd sort of like to see a second release of this, at least, before we start talking seriously of bringing it into -current. I predict a rapidly changing Doppler on this target. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 6: 4:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 3BE5014F20 for ; Fri, 9 Apr 1999 06:04:38 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id PAA03555; Fri, 9 Apr 1999 15:02:33 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id PAA14955; Fri, 9 Apr 1999 15:02:32 +0200 (MET DST) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id PAA10719; Fri, 9 Apr 1999 15:01:52 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Fri, 9 Apr 1999 15:01:51 +0200 (CEST) From: Michael Reifenberger To: greg@lemis.com Cc: FreeBSD-Current Subject: panic: integer divide fault with vinum Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, next try. Please forgive if gets too stupid :-) # cat x drive d1 device /dev/da1d drive d2 device /dev/da2d volume raid plex org stripe 256k sd length 50m drive d1 sd length 50m drive d2 (please note again the misspelling of striped) # vinum create x 1: drive d1 device /dev/da1d ** 1 Can't initialize drive d1: Device not configured 2: drive d2 device /dev/da2d ** 2 Can't initialize drive d2: Device not configured 4: plex org stripe 256k ** 4 Invalid plex organization: Invalid argument 5: sd length 50m drive d1 ** 5 Unnamed sd is not associated with a plex: Invalid argument 6: sd length 50m drive d2 ** 6 Unnamed sd is not associated with a plex: Invalid argument Configuration summary Drives: 0 (4 configured) Volumes: 1 (4 configured) Plexes: 0 (8 configured) Subdisks: 0 (16 configured) V raid State: down Plexes: 0 Size: 0 B (juppie no panic!) (Ok, after repairing 'striped' in x) # vinum create x Configuration summary Drives: 0 (4 configured) Volumes: 2 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) V raid State: down Plexes: 1 Size: 100 MB P raid.p0 S State: down Subdisks: 2 Size: 100 MB S raid.p0.s0 State: stale PO: 0 B Size: 50 MB S raid.p0.s1 State: stale PO: 256 kB Size: 50 MB (Hmm, stale sigh. The vinum(8) GOTCHAS 2. is not explicit about my situation. this time, no `vinum resetconfig`, so:) # vinum detach raid.p0 # vinum detach raid.p0.s0 # vinum detach raid.p0.s1 (Maybe this was too stupid and I get a deserved:) ..panic.. IdlePTD 3686400 initial pcb at 2f747c panicstr: integer divide fault panic messages: --- Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc0283b27 stack pointer = 0x10:0xc377cc64 frame pointer = 0x10:0xc377ccd8 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 = 330 (vinum) interrupt mask = trap number = 18 panic: integer divide fault syncing disks... 3 3 done running gdb post mortem: #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xc016e6f5 in panic (fmt=0xc02c9ea9 "integer divide fault") at ../../kern/kern_shutdown.c:448 #2 0xc025a8ce in trap_fatal (frame=0xc377cc28, eva=0) at ../../i386/i386/trap.c:943 #3 0xc025a32c in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = 102400, tf_ebp = -1015558952, tf_isp = -1015559088, tf_ebx = 0, tf_edx = 0, tf_ecx = 102400, tf_eax = 1, tf_trapno = 18, tf_err = 0, tf_eip = -1071105241, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = -1065135960}) at ../../i386/i386/trap.c:586 #4 0xc0283b27 in __qdivrem (uq=102400, vq=0, arq=0xc377ccf4) at ../../libkern/qdivrem.c:100 #5 0xc028496f in __umoddi3 (a=102400, b=0) at ../../libkern/umoddi3.c:51 #6 0xc0842fe6 in ?? () #7 0xc0848dc4 in ?? () #8 0xc0848528 in ?? () #9 0xc01a0567 in spec_ioctl (ap=0xc377ce0c) at ../../miscfs/specfs/spec_vnops.c:440 #10 0xc019fe79 in spec_vnoperate (ap=0xc377ce0c) at ../../miscfs/specfs/spec_vnops.c:129 #11 0xc02309a9 in ufs_vnoperatespec (ap=0xc377ce0c) at ../../ufs/ufs/ufs_vnops.c:2327 #12 0xc019aae5 in vn_ioctl (fp=0xc0811040, com=3223602776, data=0xc377ced0 "\001", p=0xc352b780) at vnode_if.h:395 #13 0xc017a114 in ioctl (p=0xc352b780, uap=0xc377cf84) at ../../kern/sys_generic.c:564 #14 0xc025ab17 in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = -1077945576, tf_esi = 1, tf_ebp = -1077945696, tf_isp = -1015558188, tf_ebx = -1077945732, tf_edx = 0, tf_ecx = 134781696, tf_eax = 54, tf_trapno = 12, tf_err = 2, tf_eip = 134619728, tf_cs = 31, tf_eflags = 663, tf_esp = -1077945760, tf_ss = 47}) at ../../i386/i386/trap.c:1101 #15 0xc024f20c in Xint0x80_syscall () #16 0x80483d1 in ?? () #17 0x8048295 in ?? () #18 0x80480ec in ?? () Anything else I can do or inspect? Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 6:34:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gate.etoile.net (gate.etoile.net [205.210.70.252]) by hub.freebsd.org (Postfix) with ESMTP id A5FCE14F20 for ; Fri, 9 Apr 1999 06:34:33 -0700 (PDT) (envelope-from dana@etoile.net) Received: from etoile.net (celeron.etoile.net [205.210.70.205]) by gate.etoile.net (8.9.2.Beta4/8.9.2.Beta4) with ESMTP id GAA01676 for ; Fri, 9 Apr 1999 06:32:30 -0700 (PDT) Message-ID: <370E016E.B3633D6A@etoile.net> Date: Fri, 09 Apr 1999 06:32:30 -0700 From: Dana Huggard X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: building world Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see there has been some discussions around building world. I may have missed or forgotten something, or even not read the right README. Also seen some captured text of builds and where they fail. In gnu/usr.bin/cc mine fails as well, but complains of a missing `hconfig.h`, which in turn causes a screenfull of errrors. Two days ago I cvsup'ed the complete /src. After a few attempts it's been building fine at least once a day till this missing header. Cheers, Dana_H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 6:37:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat192.236.mpoweredpc.net [142.177.192.236]) by hub.freebsd.org (Postfix) with ESMTP id 3C0EC151E1; Fri, 9 Apr 1999 06:37:44 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA10678; Fri, 9 Apr 1999 10:35:47 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 9 Apr 1999 10:35:43 -0300 (ADT) From: The Hermit Hacker To: Joe Abley Cc: Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <19990409131824.A52442@clear.co.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Joe Abley wrote: > On Fri, Apr 09, 1999 at 03:16:41AM +0200, Dag-Erling Smorgrav wrote: > > "David O'Brien" writes: > > > I've only heard back from 4 folks about adding EGCS's g77 to the base > > > system -- all 4 said "yes". Unless I get more feedback, I will add g77 > > > to the base system this weekend. > > > > I beg your pardon? You're adding g77 to the system because you know of > > four people who would find it useful? Where's the logic in that? > > > > If you do add it to the base system, make it optional. I don't care if > > it defaults to on, as long as I have the option to turn it off. > > Oh good lord, not again. I have to agree here...I personally know noone that actually uses Fortran...having it as an option to turn off would be nice...one less thing to compile on a buildworld... I personally liked the whole ports concept... 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-current" in the body of the message From owner-freebsd-current Fri Apr 9 6:40: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat192.236.mpoweredpc.net [142.177.192.236]) by hub.freebsd.org (Postfix) with ESMTP id D32BD151EA; Fri, 9 Apr 1999 06:39:53 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA10682; Fri, 9 Apr 1999 10:37:55 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 9 Apr 1999 10:37:55 -0300 (ADT) From: The Hermit Hacker To: Brian Handy Cc: Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Apr 1999, Brian Handy wrote: > On 9 Apr 1999, Dag-Erling Smorgrav wrote: > > >> [4 people said "YES! Add g77!"] > > >I beg your pardon? You're adding g77 to the system because you know of > >four people who would find it useful? Where's the logic in that? > > Well, statistically speaking, that's a bunch of "ayes" and no "noes". > Lots of things happen via implicit acceptance. (I was one of the people > who spoke up in favor of this after David mentioned this.) > > >If you do add it to the base system, make it optional. I don't care if > >it defaults to on, as long as I have the option to turn it off. > > This doesn't seem unreasonable. (I also really like Chuck's idea of > adding gcj in the same light.) Geez, and I used to think it was only the commercial OSs that had a problem with bloat and creeping featurisms ... :( Chuck's idea makes more sense...how many programs does the average system run that needs a fortran compiler? *raised eyebrow* 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-current" in the body of the message From owner-freebsd-current Fri Apr 9 6:57:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 14B6B15187 for ; Fri, 9 Apr 1999 06:57:16 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip241.houston2.tx.pub-ip.psi.net [38.11.201.241]) by leap.innerx.net (Postfix) with ESMTP id 500BB37094; Fri, 9 Apr 1999 09:55:12 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id IAA02273; Fri, 9 Apr 1999 08:55:26 -0500 (CDT) (envelope-from chris) Date: Fri, 9 Apr 1999 08:55:25 -0500 From: Chris Costello To: Dana Huggard Cc: current@FreeBSD.ORG Subject: Re: building world Message-ID: <19990409085525.D510@holly.dyndns.org> Reply-To: chris@calldei.com References: <370E016E.B3633D6A@etoile.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <370E016E.B3633D6A@etoile.net>; from Dana Huggard on Fri, Apr 09, 1999 at 06:32:30AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 9, 1999, Dana Huggard wrote: > I see there has been some discussions around building world. I may have > missed or forgotten something, or even not read the right README. Also > seen some captured text of builds and where they fail. In > gnu/usr.bin/cc mine fails as well, but complains of a missing > `hconfig.h`, which in turn causes a screenfull of errrors. Two days ago > I cvsup'ed the complete /src. After a few attempts it's been building > fine at least once a day till this missing header. Let me guess. You ran 'make -j4 buildworld' (or make -janything buildworld)? :) > > Cheers, > Dana_H > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ============================================= * "This process can check if this value is * * zero, and if it is, it does something * * child-like." -Forbes Burkowski, CS 454 * ============================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 6:59: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 02AD815285; Fri, 9 Apr 1999 06:58:43 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id PAA05783; Fri, 9 Apr 1999 15:52:58 +0200 (SAT) (envelope-from reg) Date: Fri, 9 Apr 1999 15:52:58 +0200 From: Jeremy Lea To: The Hermit Hacker Cc: Brian Handy , Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. Message-ID: <19990409155258.A3791@shale.csir.co.za> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from The Hermit Hacker on Fri, Apr 09, 1999 at 10:37:55AM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, Apr 09, 1999 at 10:37:55AM -0300, The Hermit Hacker wrote: > Geez, and I used to think it was only the commercial OSs that had a > problem with bloat and creeping featurisms ... :( Chuck's idea makes more > sense...how many programs does the average system run that needs a fortran > compiler? *raised eyebrow* I always thought the criteria for inclusion of things into the base system was: 1. Needed for 'make world'; 2. Needed to get a basic functioning server up and running; 3. Something usefull only within FreeBSD (like the kernel ;), or 4. Can't be effectively built outside of /usr/src. If {g77|f77} can be built as a port, using the system EGCS, then to port's it goes. Otherwise why don't we include the Top 20 ports, or maybe the Top 25, or... Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 7: 3:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 40E6E15285; Fri, 9 Apr 1999 07:03:18 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA05783; Fri, 9 Apr 1999 10:02:32 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id KAA18477; Fri, 9 Apr 1999 10:01:01 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id KAA32326; Fri, 9 Apr 1999 10:01:01 -0400 (EDT) Date: Fri, 9 Apr 1999 10:01:01 -0400 (EDT) From: Thomas David Rivers Message-Id: <199904091401.KAA32326@lakes.dignus.com> To: handy@lambic.physics.montana.edu, scrappy@hub.org Subject: Re: ATTENTION PLEASE: g77 in base system. Cc: current@FreeBSD.ORG, des@flood.ping.uio.no, hackers@FreeBSD.ORG, obrien@NUXI.com In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc G. Fournier wrote: > On Thu, 8 Apr 1999, Brian Handy wrote: > > > On 9 Apr 1999, Dag-Erling Smorgrav wrote: > > > > >> [4 people said "YES! Add g77!"] > > > > >I beg your pardon? You're adding g77 to the system because you know of > > >four people who would find it useful? Where's the logic in that? > > > > Well, statistically speaking, that's a bunch of "ayes" and no "noes". > > Lots of things happen via implicit acceptance. (I was one of the people > > who spoke up in favor of this after David mentioned this.) > > > > >If you do add it to the base system, make it optional. I don't care if > > >it defaults to on, as long as I have the option to turn it off. > > > > This doesn't seem unreasonable. (I also really like Chuck's idea of > > adding gcj in the same light.) > > Geez, and I used to think it was only the commercial OSs that had a > problem with bloat and creeping featurisms ... :( Chuck's idea makes more > sense...how many programs does the average system run that needs a fortran > compiler? *raised eyebrow* Personally, I'm not sure g77 is needed, but let me play devil's advocate here and turn your question around: "How many programs does the average system not run because the system doesn't have a FORTRAN compiler?" That seems to be a more pertinent question... and - a good bit more difficult to answer. - Dave Rivers - (My personal preference is to put it in there, with an option to disable it in "make world". ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 7:11:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from gate.etoile.net (gate.etoile.net [205.210.70.252]) by hub.freebsd.org (Postfix) with ESMTP id F3650152FE for ; Fri, 9 Apr 1999 07:11:24 -0700 (PDT) (envelope-from dana@etoile.net) Received: from etoile.net (celeron.etoile.net [205.210.70.205]) by gate.etoile.net (8.9.2.Beta4/8.9.2.Beta4) with ESMTP id HAA01746 for ; Fri, 9 Apr 1999 07:09:21 -0700 (PDT) Message-ID: <370E0A11.C264330A@etoile.net> Date: Fri, 09 Apr 1999 07:09:21 -0700 From: Dana Huggard X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: [Fwd: building world] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dana Huggard wrote: > > Chris Costello wrote: > > > > On Fri, Apr 9, 1999, Dana Huggard wrote: > > > I see there has been some discussions around building world. I may have > > > missed or forgotten something, or even not read the right README. Also > > > seen some captured text of builds and where they fail. In > > > gnu/usr.bin/cc mine fails as well, but complains of a missing > > > `hconfig.h`, which in turn causes a screenfull of errrors. Two days ago > > > I cvsup'ed the complete /src. After a few attempts it's been building > > > fine at least once a day till this missing header. > > > > Let me guess. You ran 'make -j4 buildworld' (or make > > -janything buildworld)? :) > > > > no. I always just use 'make buildworld'. In the last case I just used > 'make' from within '/usr/src/gnu/usr.bin/cc'. > > I've used 'find' a couple of times and this 'hconfig.h' file does not > exist. > > Cheers, > Dana_H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 7:26:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id DF4DE150E8 for ; Fri, 9 Apr 1999 07:26:20 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA23133; Fri, 9 Apr 1999 23:22:33 +0900 (JST) Message-ID: <370E0C68.3F59295C@newsguy.com> Date: Fri, 09 Apr 1999 23:19:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Jeremy Lea Cc: The Hermit Hacker , Brian Handy , Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. References: <19990409155258.A3791@shale.csir.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cc trimmed to avoid cross-posting] Jeremy Lea wrote: > > I always thought the criteria for inclusion of things into the base > system was: > > 1. Needed for 'make world'; > 2. Needed to get a basic functioning server up and running; > 3. Something usefull only within FreeBSD (like the kernel ;), or > 4. Can't be effectively built outside of /usr/src. Right or wrong, you forgot: 5. BSD tradition. Case 5 justifies Fortran. Me, I'd rather have Fortran as a port. I'd even grudgingly accept fortune as a port, as a matter of fact. Our base system is bloated. While a lot of widely used programs are only available through ports, a lot of obscure and obsolete stuff remains on our tree. They are there because of 5. As long as 5 exists, Fortran belongs in the tree. If we ever get rid of 5, then it's time to get the knife to our tree... Or the axe, if the vikings decide to have the first cut. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 7:30:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id 739A014E68 for ; Fri, 9 Apr 1999 07:30:20 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id IAA24243; Fri, 9 Apr 1999 08:27:42 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Fri, 9 Apr 1999 08:27:41 -0600 (MDT) From: Brian Handy To: The Hermit Hacker Cc: Joe Abley , Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, The Hermit Hacker wrote: > [g77 in the source tree] >I have to agree here...I personally know noone that actually uses >Fortran...having it as an option to turn off would be nice...one less >thing to compile on a buildworld... I know *lots* of people that use FORTRAN. That aside, I think I'd be satisfied with a port. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 7:54:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 4699715721 for ; Fri, 9 Apr 1999 07:54:50 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id IAA04121; Fri, 9 Apr 1999 08:43:16 -0600 (MDT) Date: Fri, 9 Apr 1999 08:43:16 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199904091443.IAA04121@narnia.plutotech.com> To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.org Subject: Re: CAM changes causing prob? X-Newsgroups: pluto.freebsd.current In-Reply-To: <199904090127.JAA07086@ariadne.tensor.pgs.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904090127.JAA07086@ariadne.tensor.pgs.com> you wrote: > After the last lot of CAM changes, I occasionally get processes hanging > attempting to access my QIC-525 tape drive. They can't be killed, so doing > backups can be a mite troublesome. Sometimes it works, sometimes it doesn't. > There seems to be some relation to how recently the last lot of tape activity > was (althought this is rather tenuous). It would be usefull to see the "ps -l" output for the hung process so we know what resource it is blocking on. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 7:56:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 3C6981557A for ; Fri, 9 Apr 1999 07:56:12 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id QAA06540; Fri, 9 Apr 1999 16:51:21 +0200 (SAT) (envelope-from reg) Date: Fri, 9 Apr 1999 16:51:21 +0200 From: Jeremy Lea To: Chuck Robey Cc: Alex Zepeda , John Polstra , asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os Message-ID: <19990409165121.A6250@shale.csir.co.za> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Chuck Robey on Thu, Apr 08, 1999 at 12:31:24PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Thu, Apr 08, 1999 at 12:31:24PM -0400, Chuck Robey wrote: > [much whining snipped :)] Your confusing a bunch of different issues here: 1. Poor porting. a. Ports should not leave behind old files, other than site configuration files (like samba.conf). If a port leaves any files behind after a pkg_delete then it is broken and must be fixed. b. Shared library numbers should be bumped when the interface changes. I've made a number of mistakes with this on the GNOME ports, I'll admit. 2. FreeBSD Ports infrastructure problems. a. Depending on binaries without being able to get a version number. b. Not being able to upgrade a port in place. Jacques pointed to one solution to this: using one directory in /var/db/pkg per port. 3. GNOME problems. a. GNOME has no release engineering. The libraries break APIs for every pico number bump just about. Or they fix bugs and remove workarounds at higher levels. Also ESR's $%^*@ advice of release early and release often means that they often manage three releases in a 48 hour period. b. The GNOME ports must be seen as a unity. In fact I'm currently considering installing tests to stop the base packages being built from anything other than x11/gnome. The general rule for these packages is to pkg_delete gnomelibs-x.x.x and *everything* which depends on it, and then build x11/gnome. I'm going to add messages to the ports which announce this at uninstall time. I've been thinking a lot about this and other porting problems presented by GNOME and am trying to come up with solutions. At the moment I'm more concerned with actually getting the ports compiled right. But some thoughts: 1. Use -soname for binaries. Add this to $LDFLAGS or something, to get a version number installed into a binary then create extra magic or a script to test this in the DEPENDS. I don't know if this is possible, but there must be some field available which can be got with either file(1) or objdump(1). Same idea for scripts. 2. Add a version history in files. Each time a port is upgraded, add the new PKGNAME to files/history. Recreate these from the CVS history using a very clever script. Then use this to deinstall all old versions, or for upgrading. Upgrading requires much more dynamic PLISTs. Maybe a port should check for all files in PLIST before installing and refuse to install unless they are cleaned out first. 3. Change the DEPENDS mechanism in ports to use a Makefile.depends in each subdir. The port's makefile includes this, which in term includes all those from the ports it requires. Each port can then setup the environment for ports which depend on it, and check if it is correctly installed (using the appropriate magic in bsd.port.mk). There are a lot of other things need in a perfect ports/package system... Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 13:48: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 46E80151CB for ; Fri, 9 Apr 1999 13:47:53 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA54844; Fri, 9 Apr 1999 11:52:57 -0400 (EDT) Date: Fri, 9 Apr 1999 11:52:56 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans Cc: current@FreeBSD.ORG, jdp@polstra.com Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <199904091534.BAA01723@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Bruce Evans wrote: > >But what's wrong with having a specific -= operator? It would make code more > >readable, which is a plus. It would be obvious for people to look for such > >before resorting to substition rules. > > Creeping featurism. Obscure semantics (would it do nothing if the rvalue > is not in the lvalue? What about if the rvalue is added later?). You say "creeping features", I say "something that would have made sense since the beginning". The semantics would be "yes" and "yes", respectively > > Bruce > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 13:48:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6893915AFB for ; Fri, 9 Apr 1999 13:47:53 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA54399; Fri, 9 Apr 1999 11:09:18 -0400 (EDT) Date: Fri, 9 Apr 1999 11:09:18 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans Cc: current@FreeBSD.ORG, jdp@polstra.com Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <199904090700.RAA26586@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Bruce Evans wrote: > >> "CC+=-Os" in individual Makefiles works about as well as "CFLAGS+=-Os" for > >> adding flags. That's not very well. Removing unwanted additions is hard. > > >Why don't we have a -= operator in make(1)? > > Substitution can replace -= in may cases, e.g.: > > CC:= ${CC:S/-Os//} > > This is "hard" because it has to be coded in the makefile, while additions > can be passed to make. But what's wrong with having a specific -= operator? It would make code more readable, which is a plus. It would be obvious for people to look for such before resorting to substition rules. > > Bruce > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14: 7:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.sitaranetworks.com (apollo.sitaranetworks.com [199.103.141.105]) by hub.freebsd.org (Postfix) with SMTP id 49B9B1604B for ; Fri, 9 Apr 1999 14:07:41 -0700 (PDT) (envelope-from loverso@sitara.net) Received: from sitara.net (jamaica.sitaranetworks.com [199.103.141.147]) by apollo.sitaranetworks.com (8.9.1a/8.9.1) with ESMTP id LAA28436 for ; Fri, 9 Apr 1999 11:24:22 -0400 (EDT) Message-ID: <370E1B31.A35C417@sitara.net> Date: Fri, 09 Apr 1999 11:22:25 -0400 From: "John R. LoVerso" Reply-To: loverso@sitaranetworks.com Organization: Sitara Networks, http://surf.to/loverso/ X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. References: <19990409155258.A3791@shale.csir.co.za> <370E0C68.3F59295C@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Right or wrong, you forgot: > > 5. BSD tradition. > > Case 5 justifies Fortran. By that logic, you'd also have to add a Pascal compiler to the base system. Neither makes much sense when they can both be ports (or packages) easily addable at install or compile time by the small % of the FreeBSD population that will actually use them. John "BSD & me: together since 1983" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:32:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 8EEA115E35 for ; Fri, 9 Apr 1999 13:52:17 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA01723; Sat, 10 Apr 1999 01:34:49 +1000 Date: Sat, 10 Apr 1999 01:34:49 +1000 From: Bruce Evans Message-Id: <199904091534.BAA01723@godzilla.zeta.org.au> To: bde@zeta.org.au, green@unixhelp.org Subject: Re: /sys/boot, egcs vs. gcc, -Os Cc: current@FreeBSD.ORG, jdp@polstra.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >But what's wrong with having a specific -= operator? It would make code more >readable, which is a plus. It would be obvious for people to look for such >before resorting to substition rules. Creeping featurism. Obscure semantics (would it do nothing if the rvalue is not in the lvalue? What about if the rvalue is added later?). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:32:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id 416C015DFC for ; Fri, 9 Apr 1999 13:52:12 -0700 (PDT) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id MAA20119; Fri, 9 Apr 1999 12:31:52 -0500 (CDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma020117; Fri, 9 Apr 99 12:31:52 -0500 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id MAA74248; Fri, 9 Apr 1999 12:30:41 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Message-Id: <199904091730.MAA74248@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: lists/freebsd X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: Panic: Invalid longjmp with vinum configured by novice Mime-Version: 1.0 Content-Type: text/plain To: Michael Reifenberger Cc: Greg Lehey , FreeBSD-Current Date: Fri, 09 Apr 1999 12:30:41 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 April 1999 at 11:31, Michael Reifenberger wrote: [snip] > > But vinum(8) doesn't offer > > you much in the way of editing facilities either. > A command history and commandline editing :-) Use ile in ports/misc/lile [sic], e.g. ``ile vinum'' Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:33: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from gauntlet2b.bridge.com (ns2.bridge.com [159.43.254.220]) by hub.freebsd.org (Postfix) with ESMTP id 0F6B615EA6; Fri, 9 Apr 1999 13:52:32 -0700 (PDT) (envelope-from DDeatherage@bridge.com) Received: by gauntlet2b.bridge.com; id KAA24533; Fri, 9 Apr 1999 10:22:20 -0500 (CDT) Received: from dns1srv.bridge.com(167.76.56.13) by gauntlet2b.bridge.com via smap (4.1) id xma024427; Fri, 9 Apr 99 10:22:13 -0500 Received: from eximcx2.bridge.com (eximcx2.bridge.com [167.76.56.15]) by dns1srv.bridge.com (8.7.6/8.7.3) with ESMTP id KAA12981; Fri, 9 Apr 1999 10:22:12 -0500 (CDT) Received: by eximcx2.bridge.com with Internet Mail Service (5.5.2448.0) id <2N26130A>; Fri, 9 Apr 1999 10:25:18 -0500 Message-ID: From: "Deatherage, David" To: "'Joel Ray Holveck'" , Steve Price Cc: Peter Jeremy , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: RE: emacs* broken in -current (was Re: Vtable thunks with egcs) Date: Fri, 9 Apr 1999 10:19:21 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've found where this problem is coming from. It's in emacs20.3/src/s/freebsd.h. It sets a macro called BSD_SYSTEM based upon the version number contained in __FreeBSD__, checking for 1, 2 and 3. Of course, -current uses 4. I have found that you can check for __FreeBSD__ >= 3, and it will work, but this feels a bit like a hack. I've never updated a port, so I can either get some instruction from someone to put in a patch, or let someone else do it. David Deatherage -----Original Message----- From: Joel Ray Holveck [mailto:joelh@gnu.org] Sent: Thursday, April 08, 1999 9:18 PM To: Steve Price Cc: Peter Jeremy; current@FreeBSD.ORG; ports@FreeBSD.ORG Subject: Re: emacs* broken in -current (was Re: Vtable thunks with egcs) > You are absolutely right. I just tried the new version of emacs > that I built on my pre-egcs box and it doesn't work on that box > either. This definitely doesn't appear to be anything caused by > changing to egcs. Not that it matters much but for grins I just > built/installed the xemacs port and it _does_ appear to work. I've been having no problems with an Emacs 20.3 and X11R6 built in October on a -current system from April 6. (The Emacs is ELF, and built from my own sources instead of the port.) I'd like to track this down; could people give me more info privately? rms is looking at releasing a mostly bugfix Emacs, possibly tommorow, but it may be another month (he's about to leave town). I haven't been watching the changes; there may be some X-related fixes in there. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:33:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 20EB215F56 for ; Fri, 9 Apr 1999 13:52:54 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA25220 for ; Fri, 9 Apr 1999 12:29:18 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA36251 for ; Fri, 9 Apr 1999 12:30:56 -0600 (MDT) Message-Id: <199904091830.MAA36251@harmony.village.org> To: current@freebsd.org Subject: Confused about egcs and c++ Date: Fri, 09 Apr 1999 12:30:56 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. I've done two make worlds. One on April 2 or 3 and One on April 8th. I'm still getting the C++ error for simple C++ programs. Do I need to do yet another one to fix the problem? I'm doing one anyway, but am confused because I thought this had been fixed (or would be fixed by two build worlds). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:35:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 82FD515035; Fri, 9 Apr 1999 14:32:27 -0700 (PDT) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 10VhRJ-0001dz-00; Fri, 9 Apr 1999 12:59:45 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id MAA10768; Fri, 9 Apr 1999 12:59:33 -0700 Date: Fri, 9 Apr 1999 12:59:33 -0700 (PDT) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: ATTENTION PLEASE: g77 in base system. To: Jeremy Lea Cc: The Hermit Hacker , Brian Handy , Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <19990409155258.A3791@shale.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I always thought the criteria for inclusion of things into the base > system was: > > 1. Needed for 'make world'; > 2. Needed to get a basic functioning server up and running; > 3. Something usefull only within FreeBSD (like the kernel ;), or > 4. Can't be effectively built outside of /usr/src. > > If {g77|f77} can be built as a port, using the system EGCS, then to > port's it goes. Otherwise why don't we include the Top 20 ports, or > maybe the Top 25, or... The criteria for adding something to the base system is different than the criteria for removing something from it. In both cases, it requires compelling reasons to change the status quo. Replacing an existing component is somewhat easier, particularly if backwards compatability is retained. I may be mistaken, but I believe the current discussion is whether or not to replace f77 with g77. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:35:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-133.camalott.com [208.229.74.133]) by hub.freebsd.org (Postfix) with ESMTP id 6F86D14D07; Fri, 9 Apr 1999 14:31:21 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.1) id KAA75676; Fri, 9 Apr 1999 10:51:28 -0500 (CDT) (envelope-from joelh) To: "Deatherage, David" Cc: Steve Price , Peter Jeremy , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: emacs* broken in -current (was Re: Vtable thunks with egcs) References: From: Joel Ray Holveck Date: 09 Apr 1999 10:51:27 -0500 In-Reply-To: "Deatherage, David"'s message of "Fri, 9 Apr 1999 10:19:21 -0500" Message-ID: <8690c1x05c.fsf@detlev.UUCP> Lines: 15 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've found where this problem is coming from. It's in > emacs20.3/src/s/freebsd.h. It sets a macro called BSD_SYSTEM based upon the > version number contained in __FreeBSD__, checking for 1, 2 and 3. Of > course, -current uses 4. I have found that you can check for __FreeBSD__ >= > 3, and it will work, but this feels a bit like a hack. I've never updated a > port, so I can either get some instruction from someone to put in a patch, > or let someone else do it. I'll make the patch if a committer can get it in. -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:36:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 79A21151D3 for ; Fri, 9 Apr 1999 14:32:24 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem11.masternet.it [194.184.65.21]) by kirk.giovannelli.it (8.9.3/8.9.2) with SMTP id PAA02039 for ; Fri, 9 Apr 1999 15:22:02 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990409171844.0097b990@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 09 Apr 1999 17:23:19 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: 990409 make world fail & more Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After cvsupping a couple of times make world still fails at : ===> c++filt rm -f .depend /usr/obj/usr/src/gnu/usr.bin/cc/c++filt/GPATH /usr/obj/usr/src/gnu/usr.bin/cc/c++filt/GRTAGS /usr/obj/usr/src/gnu/usr.bin/cc/c++filt/GSYMS /usr/obj/usr/src/gnu/usr.bin/cc/c++filt/GTAGS ===> cc_tools cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/objc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:22 : hconfig.h: No such file or directory In file included from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:23: /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/system.h:235: conflicting types for `sys_errlist' /usr/obj/usr/src/tmp/usr/include/stdio.h:225: previous declaration of `sys_errlist' In file included from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:30: /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:931: warning: `enum reg_class' declared inside parameter list /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:931: warning: its scope is only this definition or declaration, /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:931: warning: which is probably not what you want. /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:931: warning: parameter has incomplete type /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:1369: warning: parameter has incomplete type /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:1443: warning: parameter has incomplete type /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:1443: warning: parameter has incomplete type /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:1444: warning: parameter has incomplete type /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/rtl.h:1444: warning: parameter has incomplete type /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c: In function `type_from_format': /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:87 : `FATAL_EXIT_CODE' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:87 : (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:87 : for each function it appears in.) /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c: In function `accessor_from_format': /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:11 3: `FATAL_EXIT_CODE' undeclared (first use in this function) *** Error code 1 Stop. *** Error code 1 It's a 4.0-current box... Thanks for attention... P.s. The "more" part is : Is there a good soul that can confirm that "ftp" (client) works on his box ? Mine (two boxes) fail at the first "ls" Thanks again... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:38:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id BEFF515151 for ; Fri, 9 Apr 1999 14:34:06 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.0) with SMTP id BAA08150 for ; Sat, 10 Apr 1999 01:18:49 +0400 (MSD) Date: Sat, 10 Apr 1999 01:18:49 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@freebsd.org Subject: DoS from local users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Try it: cat > qqq echo $$ echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq Ctrl-D ./qqq Is there Any way to fix it? Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:46: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 99F78166EB for ; Fri, 9 Apr 1999 14:41:27 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id QAA61789; Fri, 9 Apr 1999 16:22:23 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904092022.QAA61789@misha.cisco.com> Subject: Re: -soname and shared libs (was Re: /sys/boot, egcs vs. gcc, -Os) In-Reply-To: from Alex Zepeda at "Apr 9, 1999 11:11:21 am" To: garbanzo@hooked.net (Alex Zepeda) Date: Fri, 9 Apr 1999 16:22:23 -0400 (EDT) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda once wrote: > > This is a good knews. Does this mean, I can drop-in some GTk library > > and make libXaw.so a symlink to it? This would only support my > > point... > That's like trying to replace libz with libc. Did you notice what I > said about the themes? I noticed, that you discarded my example of a useful drop-in replacement of shared libXaw.so with libXaw3d.so, saying: az: Besides, most of the functionality that libXaw3d az: provides over libXaw is provided by Gtk+ themes. This lead me to conclude, you are aware of some other drop-in replacement for libXaw. > > But in any case, the drop-in replacement is one of the promises > > shared libraries pledge to deliver and do indeed deliver quite > > often. Using smth like -soname _may_ break this, if the run-time > > linker will refuse to use a different version of a library even if I > > want it to. > Drop in replacements are perhaps a promise to you, but hardly a > guarantee. I resent the personal reference here. > The reason shared lib numbers were bumped up (or this was proposed > anyways) was because of source and binary incompatable changes being > made. Leaving the version number the same would introduce problems. I have no objections whatsoever to changes to shared lib numbers. I oppose to storing the information _in the binary_ and _relying on it_. The initial post I responded to, did not suggest such reliance outside of resolving interports' dependencies, but I'm afraid we may end up using it in the run-time linker. > Nothing's stopping you from creating a replacement for an older > version of Gtk+ or symlinking a specific version of Gtk+ to another > library. Nothing currently does, indeed. > Besides why whine hopelessly about something I'm sure you're never > going to do? Think about all the other things that shared libs > provide, like a reduction in disk and memory usage. As I mentioned, I'm using libXaw3d instead of libXaw on all of my machines. I also like NOT having to rebuild my little programs when I install new TCL libraries. I'm glad I do not have to recompile tcsh (and lots of other things) when I upgrade FreeBSD. Reduction in disk and memory usage is indeed _another_ promise shared libraries deliver... But it is NOT the one I was talking about. > Exhale once in a while. It helps. Yeah, right, will you shave your back then? I asked you privately to change your tone and attitude, and to apologise. You refused. This would be my last response to you on this subject (probably on other subjects too). -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:47:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 8341516734 for ; Fri, 9 Apr 1999 14:41:27 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id NAA61386; Fri, 9 Apr 1999 13:44:46 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904091744.NAA61386@misha.cisco.com> Subject: -soname and shared libs (was Re: /sys/boot, egcs vs. gcc, -Os) In-Reply-To: from Alex Zepeda at "Apr 9, 1999 10:28:15 am" To: garbanzo@hooked.net (Alex Zepeda) Date: Fri, 9 Apr 1999 13:44:46 -0400 (EDT) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda once wrote: > > I'd like to voice my opposition to this. While it maybe an ^^^^^^^^^^^^^^^^^ > > acceptable way to work around poor (or non-existant) release ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > engineering of SOME software, making this a rule may defeat one of ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > the major purposes of shared libraries: drop-in replacement. Think > > of libXaw3d, for example. What's wrong with different filenames for > > different libs? > Do you think that the Gnome libs are going to stand still long enough > for someone (you) to write a drop in replacement? See the the underlined part for reflection of my view on dealing with SOME software (Gnome). > Besides, most of the functionality that libXaw3d provides over libXaw > is provided by Gtk+ themes. This is a good knews. Does this mean, I can drop-in some GTk library and make libXaw.so a symlink to it? This would only support my point... But in any case, the drop-in replacement is one of the promises shared libraries pledge to deliver and do indeed deliver quite often. Using smth like -soname _may_ break this, if the run-time linker will refuse to use a different version of a library even if I want it to. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 14:48:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id D52B616763 for ; Fri, 9 Apr 1999 14:41:27 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id MAA61019; Fri, 9 Apr 1999 12:06:35 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904091606.MAA61019@misha.cisco.com> Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <19990409165121.A6250@shale.csir.co.za> from Jeremy Lea at "Apr 9, 1999 04:51:21 pm" To: reg@shale.csir.co.za (Jeremy Lea) Date: Fri, 9 Apr 1999 12:06:35 -0400 (EDT) Cc: chuckr@mat.net, garbanzo@hooked.net, jdp@polstra.com, asmodai@wxs.nl, current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremy Lea once wrote: > 3. GNOME problems. > a. GNOME has no release engineering. The libraries break APIs for > every pico number bump just about. Or they fix bugs and remove > workarounds at higher levels. Also ESR's $%^*@ advice of release > early and release often means that they often manage three > releases in a 48 hour period. [...] > 1. Use -soname for binaries. Add this to $LDFLAGS or something, to get > a version number installed into a binary then create extra magic or > a script to test this in the DEPENDS. I don't know if this is > possible, but there must be some field available which can be got > with either file(1) or objdump(1). Same idea for scripts. I'd like to voice my opposition to this. While it maybe an acceptable way to work around poor (or non-existant) release engineering of SOME software, making this a rule may defeat one of the major purposes of shared libraries: drop-in replacement. Think of libXaw3d, for example. What's wrong with different filenames for different libs? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 6:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (unknown [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A4FCE15F4B for ; Fri, 9 Apr 1999 14:45:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA24969; Fri, 9 Apr 1999 11:18:31 -0700 (PDT) (envelope-from obrien) Message-ID: <19990409111831.B24938@nuxi.com> Date: Fri, 9 Apr 1999 11:18:31 -0700 From: "David O'Brien" To: Dana Huggard , current@FreeBSD.ORG Subject: Re: building world Reply-To: obrien@NUXI.com References: <370E016E.B3633D6A@etoile.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <370E016E.B3633D6A@etoile.net>; from Dana Huggard on Fri, Apr 09, 1999 at 06:32:30AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In gnu/usr.bin/cc mine fails as well, but complains of a missing > `hconfig.h`, which in turn causes a screenfull of errrors. cd /usr/src make cleandir ; make cleandir then build your world normally and tell me if you still have the error. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 6:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (unknown [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 861AB15F45 for ; Fri, 9 Apr 1999 14:45:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA26158; Fri, 9 Apr 1999 13:59:44 -0700 (PDT) (envelope-from obrien) Message-ID: <19990409135944.A26149@nuxi.com> Date: Fri, 9 Apr 1999 13:59:44 -0700 From: "David O'Brien" To: Dana Huggard , current@FreeBSD.ORG Subject: Re: building world Reply-To: obrien@NUXI.com References: <370E016E.B3633D6A@etoile.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <370E016E.B3633D6A@etoile.net>; from Dana Huggard on Fri, Apr 09, 1999 at 06:32:30AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > gnu/usr.bin/cc mine fails as well, but complains of a missing > `hconfig.h`, which in turn causes a screenfull of errrors. Two days ago I know you've heard this before WRT to cc_tools/, but... is should be fixed now. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 7: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (unknown [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2ABCF15F4E for ; Fri, 9 Apr 1999 14:45:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA24536; Fri, 9 Apr 1999 09:37:00 -0700 (PDT) (envelope-from obrien) Message-ID: <19990409093700.B24462@nuxi.com> Date: Fri, 9 Apr 1999 09:37:00 -0700 From: "David O'Brien" To: Manfred Antar Cc: current@FreeBSD.ORG Subject: Re: EGCS troubles Reply-To: obrien@NUXI.com References: <370DA528.A37CFCD6@altavista.net> <4.2.0.32.19990409092450.00a3f960@216.101.162.50> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4.2.0.32.19990409092450.00a3f960@216.101.162.50>; from Manfred Antar on Fri, Apr 09, 1999 at 09:31:58AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The Only way I could get Jade to work with the new compiler > was with CFLAGS= -O -pipe That is not so bad. Before EGCS, we would state that "-O" is the only optimization that is know to always work and what we tell people to use. Mike Smith has written about this many times in Hackers and Current. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 7: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (unknown [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3C1A415F2E for ; Fri, 9 Apr 1999 14:45:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA24958; Fri, 9 Apr 1999 11:16:21 -0700 (PDT) (envelope-from obrien) Message-ID: <19990409111621.A24938@nuxi.com> Date: Fri, 9 Apr 1999 11:16:21 -0700 From: "David O'Brien" To: Gilad Rom , current@FreeBSD.ORG Subject: Re: Make world is broken for days now... :( Reply-To: obrien@NUXI.com References: <370DF25C.9AE69160@ein-hashofet.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <370DF25C.9AE69160@ein-hashofet.co.il>; from Gilad Rom on Fri, Apr 09, 1999 at 12:28:13PM +0000 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Everytime I try to make world, I get the following: ..snip.. > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: > linux.h: No such file or directory > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:4: > i386/freebsd-elf.h: No such file or directory Something is seriously wrong with your CVSup'ing. I have never committed (to the main source tree) any reference to linux.h and freebsd-elf.h. I have *NO* idea where you are getting this from. What is the revision of /usr/src/gnu/usr.bin/cc/cc_tools/Makefile? Can you send it to me? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 7:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 41B3615DEB for ; Fri, 9 Apr 1999 14:46:19 -0700 (PDT) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id JAA37453; Fri, 9 Apr 1999 09:31:59 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.2.0.32.19990409092450.00a3f960@216.101.162.50> X-Sender: null@216.101.162.50 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.32 (Beta) Date: Fri, 09 Apr 1999 09:31:58 -0700 To: sobomax@altavista.net, Jeroen Ruigrok/Asmodai From: Manfred Antar Subject: Re: EGCS troubles Cc: "David O'Brien" , current@FreeBSD.ORG In-Reply-To: <370DA528.A37CFCD6@altavista.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:58 AM 4/9/99 +0300, Maxim Sobolev wrote: >> > Compile Jade with "-g" and see where in the coredump the signal 11 is >> > occuring. What does ``ldd jade'' show? You might be mixing shared libs, >> > that doesn't work for C++. Could also be an exceptions problem. Try >> > compiling with -fnoexpcetions. >> >> [asmodai@daemon] (163) $ ldd /usr/local/bin/jade >> /usr/local/bin/jade: >> libstyle.so.1 => /usr/local/lib/libstyle.so.1 (0x280b6000) >> libspgrove.so.1 => /usr/local/lib/libspgrove.so.1 (0x282ac000) >> libgrove.so.1 => /usr/local/lib/libgrove.so.1 (0x282ef000) >> libsp.so.1 => /usr/local/lib/libsp.so.1 (0x282f7000) >> libintl.so.1 => /usr/local/lib/libintl.so.1 (0x284ce000) >> libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x284d2000) >> libm.so.2 => /usr/lib/libm.so.2 (0x2850d000) >> libc.so.3 => /usr/lib/libc.so.3 (0x28527000) >> >> I know for certain that libintl is gcc. >> >> Will go and do recompilations of all stuff this weekend *sigh* ;) >> > >In my case (it seems all libs compiled under egcs - exactly when jade >compiled): > >/usr/local/bin/jade: > libstyle.so.1 => /usr/local/lib/libstyle.so.1 (0x280b9000) > libspgrove.so.1 => /usr/local/lib/libspgrove.so.1 (0x282b6000) > libgrove.so.1 => /usr/local/lib/libgrove.so.1 (0x282f9000) > libsp.so.1 => /usr/local/lib/libsp.so.1 (0x28301000) > libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x284e4000) > libm.so.2 => /usr/lib/libm.so.2 (0x28521000) > libc.so.3 => /usr/lib/libc.so.3 (0x2853c000) The Only way I could get Jade to work with the new compiler was with CFLAGS= -O -pipe The only way I have tested it is by building the Handbook -O2 -pipe built ,but Signal 11 -O2 -fno-exceptions won't build Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 7:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (haiti-75.ppp.hooked.net [206.169.228.75]) by hub.freebsd.org (Postfix) with ESMTP id 9237815FB8 for ; Fri, 9 Apr 1999 14:50:12 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id OAA31268; Fri, 9 Apr 1999 14:47:51 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Fri, 9 Apr 1999 14:47:51 -0700 (PDT) From: Alex Zepeda To: Doug White Cc: current Subject: Re: msdosfs problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Doug White wrote: > mpg123 is an ancient player. It won't play most newer MP3s. Use a newer > player, like x11amp or xaudio. It's not mpg123. There were some files that never caused a problem with the same version of mpg123 before. And besides, x11amp is based on mpg123 isn't it? That still doesn't explain how it would cause my system to hang. Grr. Back to CDs it is. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 7:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (haiti-75.ppp.hooked.net [206.169.228.75]) by hub.freebsd.org (Postfix) with ESMTP id 4DDB115B16 for ; Fri, 9 Apr 1999 14:53:55 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id LAA02450; Fri, 9 Apr 1999 11:11:21 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Fri, 9 Apr 1999 11:11:21 -0700 (PDT) From: Alex Zepeda To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: -soname and shared libs (was Re: /sys/boot, egcs vs. gcc, -Os) In-Reply-To: <199904091744.NAA61386@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Mikhail Teterin wrote: > This is a good knews. Does this mean, I can drop-in some GTk library > and make libXaw.so a symlink to it? This would only support my > point... That's like trying to replace libz with libc. Did you notice what I said about the themes? > But in any case, the drop-in replacement is one of the promises shared > libraries pledge to deliver and do indeed deliver quite often. Using > smth like -soname _may_ break this, if the run-time linker will refuse > to use a different version of a library even if I want it to. Drop in replacements are perhaps a promise to you, but hardly a guarantee. The reason shared lib numbers were bumped up (or this was proposed anyways) was because of source and binary incompatable changes being made. Leaving the version number the same would introduce problems. Nothing's stopping you from creating a replacement for an older version of Gtk+ or symlinking a specific version of Gtk+ to another library. Besides why whine hopelessly about something I'm sure you're never going to do? Think about all the other things that shared libs provide, like a reduction in disk and memory usage. Exhale once in a while. It helps. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 7:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (haiti-75.ppp.hooked.net [206.169.228.75]) by hub.freebsd.org (Postfix) with ESMTP id 6953D15B3E for ; Fri, 9 Apr 1999 14:53:55 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id KAA02246; Fri, 9 Apr 1999 10:28:15 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Fri, 9 Apr 1999 10:28:15 -0700 (PDT) From: Alex Zepeda To: mi@aldan.algebra.com Cc: Jeremy Lea , chuckr@mat.net, jdp@polstra.com, asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-Reply-To: <199904091606.MAA61019@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'd like to voice my opposition to this. While it maybe an acceptable > way to work around poor (or non-existant) release engineering of SOME > software, making this a rule may defeat one of the major purposes of > shared libraries: drop-in replacement. Think of libXaw3d, for example. > What's wrong with different filenames for different libs? Do you think that the Gnome libs are going to stand still long enough for someone (you) to write a drop in replacement? Besides, most of the functionality that libXaw3d provides over libXaw is provided by Gtk+ themes. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 8:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E675216022 for ; Fri, 9 Apr 1999 14:57:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA20949; Fri, 9 Apr 1999 09:57:20 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA81816; Fri, 9 Apr 1999 09:57:20 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 9 Apr 1999 09:57:20 -0700 (PDT) Message-Id: <199904091657.JAA81816@vashon.polstra.com> To: rom_glsa@ein-hashofet.co.il Subject: Re: Make world is broken for days now... :( In-Reply-To: <370DF25C.9AE69160@ein-hashofet.co.il> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <370DF25C.9AE69160@ein-hashofet.co.il>, Gilad Rom wrote: > Hello, > > For the past week, I've been trying to build world, in order to > get then new egcs up and running. > > Everytime I try to make world, I get the following: > > ===> cc_tools > cc -O > -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/objc > -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc > -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config > -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" > -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" > -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -c > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c > > In file included from > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/xm-i386.h:43, > from > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/hconfig.h:2, > from > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:22: > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: > linux.h: No such file or directory > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:4: > i386/freebsd-elf.h: No such file or directory > *** Error code 1 Your sources are unclean. The files "hconfig.h" and "tm.h" should not exist in "src/contrib/egcs/gcc". You must have run ./configure in there at some point (don't do that). I recommend that you delete "src/contrib/egcs" and fetch a fresh copy of it. Or, if there is a Makefile in there too, you could try running "make distclean" to see if that solves the problem. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 8:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 13D3216023 for ; Fri, 9 Apr 1999 14:57:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA20918; Fri, 9 Apr 1999 09:47:08 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA81768; Fri, 9 Apr 1999 09:47:07 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 9 Apr 1999 09:47:07 -0700 (PDT) Message-Id: <199904091647.JAA81768@vashon.polstra.com> To: green@unixhelp.org Subject: Re: make world breakage?!? In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brian Feldman wrote: > Am I the only one to get this error?? > cc -nostdinc -O -pipe -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd -I. -I/usr/src/usr.sbin/amd/amd -I/usr/src/usr.sbin/amd/amd/../include -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/include -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd/clock.c > /usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd/clock.c:66: redefinition of `struct callout' > *** Error code 1 > > Stop. > > It's been like this here for days, and noone's reported it. I've been doing a lot of make worlds the past few days, and I haven't run into it. It didn't appear in the make world I did last night. Have you tried "make cleandir; make cleandir" (yes, twice) in "src/usr.sbin/amd"? If you have, I can only suggest that you wipe out the amd trees in both contrib and usr.sbin, grab fresh sources, and try again. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 8:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id E153015B39 for ; Fri, 9 Apr 1999 15:00:59 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id NAA57245 for ; Fri, 9 Apr 1999 13:27:35 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Fri, 9 Apr 1999 13:27:35 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: latest make world problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the latest error that I get with make world cvsupped about an hour ago: /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c: In fu nction `type_from_format': /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:87: `F ATAL_EXIT_CODE' undeclared (first use this function) /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:87: (E ach undeclared identifier is reported only once /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:87: fo r each function it appears in.) /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c: In fu nction `accessor_from_format': /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:113: ` FATAL_EXIT_CODE' undeclared (first use this function) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 8:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id B6B5D16065; Fri, 9 Apr 1999 14:58:46 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id OAA21686; Fri, 9 Apr 1999 14:17:30 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904092117.OAA21686@troutmask.apl.washington.edu> Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <19990409140618.B26149@nuxi.com> from "David O'Brien" at "Apr 9, 1999 02:06:18 pm" To: obrien@NUXI.com Date: Fri, 9 Apr 1999 14:17:30 -0700 (PDT) Cc: current@FreeBSD.ORG, hackers@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > Speaking of ports, I have a working port of f2c and a new > > f77(1) wrapper sitting on my machine. > > I guess naming is going to get sticky here... if f2c has `f77', then *if* > I put egcs/g77 in the main tree, do I install it as `g77' or `f77'? > > The Egcs port installs it as `g77'... and what if someone makes some port > of an updated g77? > I would expect that you'll want to have a symlink from f77 to g77 in /usr/bin. If g77 includes a man page, you'll also want a symlink from f77.1 to g77.1. In the Makefile for the port of my f77 wrapper I have: do-install: ${INSTALL_PROGRAM} ${WRKSRC}/f77 ${PREFIX}/bin ${INSTALL_MAN} ${WRKSRC}/f77.1 ${PREFIX}/man/man1 This could be changed to: do-install: ${INSTALL_PROGRAM} ${WRKSRC}/f77 ${PREFIX}/bin/${F77NAME} ${INSTALL_MAN} ${WRKSRC}/f77.1 ${PREFIX}/man/man1/${F77NAME}.1 where F77NAME would default to fc. Why fc? Because, f2c provides an old Bourne shell script of the same name. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 8:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6031B16071; Fri, 9 Apr 1999 14:58:49 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id RAA57494; Fri, 9 Apr 1999 17:24:41 -0400 (EDT) Date: Fri, 9 Apr 1999 17:24:40 -0400 (EDT) From: Chuck Robey To: Thomas David Rivers Cc: handy@lambic.physics.montana.edu, scrappy@hub.org, current@FreeBSD.ORG, des@flood.ping.uio.no, hackers@FreeBSD.ORG, obrien@NUXI.com Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <199904091401.KAA32326@lakes.dignus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Thomas David Rivers wrote: > > Geez, and I used to think it was only the commercial OSs that had a > > problem with bloat and creeping featurisms ... :( Chuck's idea makes more > > sense...how many programs does the average system run that needs a fortran > > compiler? *raised eyebrow* > > Personally, I'm not sure g77 is needed, but let me play devil's > advocate here and turn your question around: > > "How many programs does the average system not run because > the system doesn't have a FORTRAN compiler?" > > That seems to be a more pertinent question... and - a good bit > more difficult to answer. Not as hard as all that. Just go about compiling from ports/math, and notice how many programs use f2c. Some also from graphics, and from others. Especially when you consider the low cost in terms of source size and executeable size, getting rid of fortran, or not allowing the upgraded fortran, it just doesn't make sense. We have NO_SENDMAIL now as a precedent, we just need NO_FORTRAN and NO_GCJ. This is very, very doable, and can only make FreeBSD look better. OTOH, as Jordan pointed out, maybe we need a *little* more experience with gcj, but fortran, it's ready *now*. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15: 8:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40]) by hub.freebsd.org (Postfix) with ESMTP id 5AB12160A9; Fri, 9 Apr 1999 15:00:29 -0700 (PDT) (envelope-from gjohnson@nola.srrc.usda.gov) Received: (from glenn@localhost) by symbion.srrc.usda.gov (8.9.2/8.9.2) id LAA14881; Fri, 9 Apr 1999 11:28:52 -0500 (CDT) (envelope-from glenn) From: Glenn Johnson Date: Fri, 9 Apr 1999 11:28:52 -0500 To: Jeremy Lea Cc: The Hermit Hacker , Brian Handy , Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. Message-ID: <19990409112852.A14614@symbion.srrc.usda.gov> References: <19990409155258.A3791@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990409155258.A3791@shale.csir.co.za>; from Jeremy Lea on Fri, Apr 09, 1999 at 03:52:58PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 09, 1999 at 03:52:58PM +0200, Jeremy Lea wrote: > Hi, > > On Fri, Apr 09, 1999 at 10:37:55AM -0300, The Hermit Hacker wrote: > > Geez, and I used to think it was only the commercial OSs that had a > > problem with bloat and creeping featurisms ... :( Chuck's idea makes more > > sense...how many programs does the average system run that needs a fortran > > compiler? *raised eyebrow* > > I always thought the criteria for inclusion of things into the base > system was: > > 1. Needed for 'make world'; > 2. Needed to get a basic functioning server up and running; > 3. Something usefull only within FreeBSD (like the kernel ;), or > 4. Can't be effectively built outside of /usr/src. > > If {g77|f77} can be built as a port, using the system EGCS, then to > port's it goes. Otherwise why don't we include the Top 20 ports, or > maybe the Top 25, or... > > Regards, > -Jeremy First off, g77 is not your typical port. The build of g77 depends on having the source to gcc on your system. The last time I checked, installing the source was optional. The reason the current port of g77 is marked broken is because of this. History: Newer versions of g77 cannot be built against gcc 2.7.2 and older versions that can be built against gcc 2.7.2 don't work with FreeBSD. This is because the FreeBSD gcc 2.7.2 was hacked too far away from what g77 was developed for. I would expect to see the same type of scenario arise with egcs as the FreeBSD version becomes significantly changed from stock egcs. David has already said that "ports/egcs != src/contrib/egcs". Future: Now it may be true that newer versions of g77 may not build against whatever version of egcs we have but at least we would be guaranteed of having a functional Fortran compiler. Many people don't seem to understand that FreeBSD can be used for workstations as well as servers and Fortran is *essential* on a scientific/engineering workstation. I don't doubt that there are more people using FreeBSD as a server but that doesn't mean that workstation users should be denied an essential tool because it takes up a few hundred kilobytes. I would predict that with SGI's entry into the NT market you will see more people looking at "Unix on Intel" to replace their aging SGI Irix boxes. It would be a shame for them to choose Linux over FreeBSD because Linux can compile their Fortran programs and FreeBSD cannot. -- Glenn Johnson Technician USDA, ARS, SRRC New Orleans, LA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15:24:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B62141634D; Fri, 9 Apr 1999 15:15:32 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id RAA30046; Fri, 9 Apr 1999 17:12:58 -0500 (CDT) Date: Fri, 9 Apr 1999 17:12:58 -0500 (CDT) From: Steve Price To: Joel Ray Holveck Cc: "Deatherage, David" , Peter Jeremy , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: emacs* broken in -current (was Re: Vtable thunks with egcs) In-Reply-To: <8690c1x05c.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Apr 1999, Joel Ray Holveck wrote: # > I've found where this problem is coming from. It's in # > emacs20.3/src/s/freebsd.h. It sets a macro called BSD_SYSTEM based upon the # > version number contained in __FreeBSD__, checking for 1, 2 and 3. Of # > course, -current uses 4. I have found that you can check for __FreeBSD__ >= # > 3, and it will work, but this feels a bit like a hack. I've never updated a # > port, so I can either get some instruction from someone to put in a patch, # > or let someone else do it. # # I'll make the patch if a committer can get it in. Send it to me. I'll commit it. :) BTW, good catch David! -steve # -- # Joel Ray Holveck - joelh@gnu.org # Fourth law of programming: # Anything that can go wrong wi # sendmail: segmentation violation - core dumped # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15:26:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id F40F115A18 for ; Fri, 9 Apr 1999 15:23:12 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id SAA57752; Fri, 9 Apr 1999 18:18:49 -0400 (EDT) Date: Fri, 9 Apr 1999 18:18:49 -0400 (EDT) From: Chuck Robey To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Confused about egcs and c++ In-Reply-To: <199904091830.MAA36251@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Warner Losh wrote: > > OK. I've done two make worlds. One on April 2 or 3 and One on April > 8th. I'm still getting the C++ error for simple C++ programs. Do I > need to do yet another one to fix the problem? I'm doing one anyway, > but am confused because I thought this had been fixed (or would be > fixed by two build worlds). I had to do two build/installworlds before the simple C++ progs worked right, and then I had to dive in and check that any libs that linked in libstdc++.so.2 got relinked, so that they used libstdc++.so.3 instead. This killed some unobvious things, like the kde apps which used converters/kdeutils, which has a libQwSpriteField, which itself linked in libstdc++.so.2, which caused some progs to link BOTH versions 2 and 3 (fatal and unobvious problem). Keep recompiling, Warner, it does work. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15:26:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 50B8415B8D for ; Fri, 9 Apr 1999 15:24:39 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id WAA17197; Fri, 9 Apr 1999 22:23:54 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id WAA15468; Fri, 9 Apr 1999 22:23:53 +0200 (MET DST) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id VAA10940; Fri, 9 Apr 1999 21:59:57 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Fri, 9 Apr 1999 21:59:57 +0200 (CEST) From: Michael Reifenberger To: Jacques Vidrine Cc: Greg Lehey , FreeBSD-Current Subject: Re: Panic: Invalid longjmp with vinum configured by novice In-Reply-To: <199904091730.MAA74248@spawn.nectar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Jacques Vidrine wrote: > Date: Fri, 09 Apr 1999 12:30:41 -0500 > From: Jacques Vidrine > To: Michael Reifenberger > Cc: Greg Lehey , FreeBSD-Current > Subject: Re: Panic: Invalid longjmp with vinum configured by novice > > On 9 April 1999 at 11:31, Michael Reifenberger wrote: > [snip] > > > But vinum(8) doesn't offer > > > you much in the way of editing facilities either. > > A command history and commandline editing :-) > > Use ile in ports/misc/lile [sic], e.g. ``ile vinum'' No, vinum has allready a command history which makes it superior over `ed`. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15:29:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id A4BDB14D8C for ; Fri, 9 Apr 1999 15:29:35 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 5D40744; Fri, 9 Apr 1999 22:27:22 +0000 (GMT) Date: Sat, 10 Apr 1999 02:27:22 +0400 (MSD) From: oZZ!!! To: Dmitry Valdov Cc: freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi! > Try it: > > cat > qqq > echo $$ > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > > Ctrl-D > > ./qqq > > Is there Any way to fix it? > > Dmitry. > % cat > qqq echo $$ echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq % ./qqq ./qqq: Permission denied. % & what fix? Rgdz, Osokin Sergey aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15:40: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6073014BD4 for ; Fri, 9 Apr 1999 15:39:54 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id PAA14508 for ; Fri, 9 Apr 1999 15:37:24 -0700 Date: Fri, 9 Apr 1999 15:37:23 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: 3.1 stable bootloader vs. 4.0 kernel... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did I miss something obvious here? I have a system over in England somewhere which I'm remotely booting. It's 3.1Stable. When I try and put a 4.0/-current kernel (which boots fine on *my* much overwritten and not reinstalled since 2.2.2 system), I get: Type '?' for a list of commands, 'help' for more detailed help. disk1s1a:> boot kernel.tst /kernel.tst text=0x1a312e elf_loadexec: archsw.readin failed can't load module '/kernel.tst': input/output error Eh? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 15:43:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id CC45C14A12 for ; Fri, 9 Apr 1999 15:43:39 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA05304; Fri, 9 Apr 1999 15:41:25 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 9 Apr 1999 15:41:24 -0700 (PDT) From: Doug White To: Alex Zepeda Cc: current Subject: Re: msdosfs problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Alex Zepeda wrote: > On Fri, 9 Apr 1999, Doug White wrote: > > > mpg123 is an ancient player. It won't play most newer MP3s. Use a newer > > player, like x11amp or xaudio. > > It's not mpg123. There were some files that never caused a problem with > the same version of mpg123 before. And besides, x11amp is based on mpg123 > isn't it? No. How does xaudio react? I don't buy that it's a FS-related difficulty; you can play MP3s over NFS without trouble. > That still doesn't explain how it would cause my system to hang. > Grr. Back to CDs it is. Sound system problem? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 16: 4:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9547514C0E for ; Fri, 9 Apr 1999 16:04:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA25969; Fri, 9 Apr 1999 17:02:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA56835; Fri, 9 Apr 1999 17:03:54 -0600 (MDT) Message-Id: <199904092303.RAA56835@harmony.village.org> To: Chuck Robey Subject: Re: Confused about egcs and c++ Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 09 Apr 1999 18:18:49 EDT." References: Date: Fri, 09 Apr 1999 17:03:54 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : Keep recompiling, Warner, it does work. Yup. My build world just finished, and now it works. Yippie! Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 16:11: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5768014DD9 for ; Fri, 9 Apr 1999 16:10:47 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10VchO-000HHX-00 for current@freebsd.org; Fri, 9 Apr 1999 16:56:02 +0200 From: Sheldon Hearn To: asami@FreeBSD.ORG (Satoshi - the Ports Wraith - Asami) Cc: ports@FreeBSD.ORG Subject: Re: ports dependencies In-reply-to: Your message of "Thu, 08 Apr 1999 19:10:18 MST." <199904090210.TAA98121@silvia.hip.berkeley.edu> Date: Fri, 09 Apr 1999 16:55:50 +0200 Message-ID: <66424.923669750@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 08 Apr 1999 19:10:18 MST, Satoshi - the Ports Wraith - Asami wrote: > People, I know you are annoyed by many stupid things software authors > have done in the past to make your life miserable Actually, the only thing having any negative impact on my life right now is the lengthy discussion on port dependencies that's taking place on the freebsd-current mailing list. :-P Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 16:17:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 06CBA14D4A for ; Fri, 9 Apr 1999 16:17:29 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id QAA22776; Fri, 9 Apr 1999 16:15:13 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA03845; Fri, 9 Apr 1999 16:15:12 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 9 Apr 1999 16:15:12 -0700 (PDT) Message-Id: <199904092315.QAA03845@vashon.polstra.com> To: obrien@NUXI.com Subject: Re: Make world is broken for days now... :( In-Reply-To: <19990409111621.A24938@nuxi.com> References: <370DF25C.9AE69160@ein-hashofet.co.il> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990409111621.A24938@nuxi.com>, David O'Brien wrote: > > Everytime I try to make world, I get the following: > ..snip.. > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: > > linux.h: No such file or directory > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:4: > > i386/freebsd-elf.h: No such file or directory > > Something is seriously wrong with your CVSup'ing. I have never committed > (to the main source tree) any reference to linux.h and freebsd-elf.h. > > I have *NO* idea where you are getting this from. I bet he ran ./configure in contrib/egcs at some point in the past. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 16:18:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (unknown [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 31AFC15059 for ; Fri, 9 Apr 1999 16:18:30 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA27417 for current@freebsd.org; Fri, 9 Apr 1999 16:16:18 -0700 (PDT) (envelope-from obrien) Message-ID: <19990409161618.E26910@nuxi.com> Date: Fri, 9 Apr 1999 16:16:18 -0700 From: "David O'Brien" To: current@freebsd.org Subject: Re: Make world is broken for days now... :( Reply-To: obrien@NUXI.com References: <370DF25C.9AE69160@ein-hashofet.co.il> <19990409111621.A24938@nuxi.com> <199904092315.QAA03845@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904092315.QAA03845@vashon.polstra.com>; from John Polstra on Fri, Apr 09, 1999 at 04:15:12PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have *NO* idea where you are getting this from. > > I bet he ran ./configure in contrib/egcs at some point in the past. I think I'll commit a change to ./configure so that it tells the person the right thing to do. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 16:21:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (unknown [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3442F14F7C for ; Fri, 9 Apr 1999 16:21:43 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id QAA27437; Fri, 9 Apr 1999 16:19:05 -0700 (PDT) (envelope-from obrien) Message-ID: <19990409161904.A27421@nuxi.com> Date: Fri, 9 Apr 1999 16:19:04 -0700 From: "David O'Brien" To: Gianmarco Giovannelli , current@FreeBSD.ORG Subject: Re: 990409 make world fail & more Reply-To: obrien@NUXI.com References: <4.1.19990409171844.0097b990@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4.1.19990409171844.0097b990@194.184.65.4>; from Gianmarco Giovannelli on Fri, Apr 09, 1999 at 05:23:19PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After cvsupping a couple of times make world still fails at : ..snip.. BDE fixed this in rev 1.25 of src/gnu/usr.bin/cc/cc_tools/Makefile. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 16:32:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id A959314DB1; Fri, 9 Apr 1999 16:32:39 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip241.houston2.tx.pub-ip.psi.net [38.11.201.241]) by leap.innerx.net (Postfix) with ESMTP id 0501937068; Fri, 9 Apr 1999 19:30:20 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id SAA03198; Fri, 9 Apr 1999 18:30:32 -0500 (CDT) (envelope-from chris) Date: Fri, 9 Apr 1999 18:30:31 -0500 From: Chris Costello To: Dmitry Valdov Cc: freebsd-questions@FreeBSD.ORG Subject: Re: DoS from local users Message-ID: <19990409183031.F510@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Dmitry Valdov on Sat, Apr 10, 1999 at 01:18:49AM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 9, 1999, Dmitry Valdov wrote: > Hi! > > Try it: > > cat > qqq > echo $$ > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > > Ctrl-D > > ./qqq > > Is there Any way to fix it? You typically want to set a restriction as to how many processes a user can spawn. This is done by editing /etc/login.conf and changing the user's login class, see the man page for 'login.conf'. > > Dmitry. > Followups set to -questions. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ============================================= * "This process can check if this value is * * zero, and if it is, it does something * * child-like." -Forbes Burkowski, CS 454 * ============================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 16:52: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E800D14D00 for ; Fri, 9 Apr 1999 16:51:58 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA29510; Sat, 10 Apr 1999 09:19:45 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA34774; Sat, 10 Apr 1999 09:19:41 +0930 (CST) Message-ID: <19990410091941.T2142@lemis.com> Date: Sat, 10 Apr 1999 09:19:41 +0930 From: Greg Lehey To: Michael Reifenberger , Jacques Vidrine Cc: FreeBSD-Current Subject: Re: Panic: Invalid longjmp with vinum configured by novice References: <199904091730.MAA74248@spawn.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Michael Reifenberger on Fri, Apr 09, 1999 at 09:59:57PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 9 April 1999 at 21:59:57 +0200, Michael Reifenberger wrote: > On Fri, 9 Apr 1999, Jacques Vidrine wrote: > >> Date: Fri, 09 Apr 1999 12:30:41 -0500 >> From: Jacques Vidrine >> To: Michael Reifenberger >> Cc: Greg Lehey , FreeBSD-Current >> Subject: Re: Panic: Invalid longjmp with vinum configured by novice >> >> On 9 April 1999 at 11:31, Michael Reifenberger wrote: >> [snip] >>>> But vinum(8) doesn't offer >>>> you much in the way of editing facilities either. >>> A command history and commandline editing :-) >> >> Use ile in ports/misc/lile [sic], e.g. ``ile vinum'' > > No, vinum has allready a command history which makes it superior over `ed`. You can't go back a line with vinum. Once you've entered it, it gets processed. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 17:37:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id BC4BB14F6C for ; Fri, 9 Apr 1999 17:37:17 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA29807; Sat, 10 Apr 1999 10:05:04 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA34907; Sat, 10 Apr 1999 10:05:03 +0930 (CST) Message-ID: <19990410100502.Y2142@lemis.com> Date: Sat, 10 Apr 1999 10:05:03 +0930 From: Greg Lehey To: Michael Reifenberger , greg@lemis.com Cc: FreeBSD-Current Subject: Re: panic: integer divide fault with vinum References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Michael Reifenberger on Fri, Apr 09, 1999 at 03:01:51PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 9 April 1999 at 15:01:51 +0200, Michael Reifenberger wrote: > Hi, > next try. > Please forgive if gets too stupid :-) > > # cat x > drive d1 device /dev/da1d > drive d2 device /dev/da2d > volume raid > plex org stripe 256k > sd length 50m drive d1 > sd length 50m drive d2 > (please note again the misspelling of striped) > # vinum create x > 1: drive d1 device /dev/da1d > ** 1 Can't initialize drive d1: Device not configured You need to configure it. Use disklabel -e. > 2: drive d2 device /dev/da2d > ** 2 Can't initialize drive d2: Device not configured > 4: plex org stripe 256k > ** 4 Invalid plex organization: Invalid argument As advertised. But this isn't your primary fault, it's the one above. > 5: sd length 50m drive d1 > ** 5 Unnamed sd is not associated with a plex: Invalid argument Since you don't have a plex, you don't have a subdisk. > 6: sd length 50m drive d2 > ** 6 Unnamed sd is not associated with a plex: Invalid argument > Configuration summary > > Drives: 0 (4 configured) > Volumes: 1 (4 configured) > Plexes: 0 (8 configured) > Subdisks: 0 (16 configured) > > > V raid State: down Plexes: 0 Size: 0 B > (juppie no panic!) Not much of anything, in fact. > (Ok, after repairing 'striped' in x) > # vinum create x > Configuration summary > > Drives: 0 (4 configured) > Volumes: 2 (4 configured) > Plexes: 1 (8 configured) > Subdisks: 2 (16 configured) > > > V raid State: down Plexes: 1 Size: 100 MB > > P raid.p0 S State: down Subdisks: 2 Size: 100 MB > > S raid.p0.s0 State: stale PO: 0 B Size: 50 MB > S raid.p0.s1 State: stale PO: 256 kB Size: 50 MB > (Hmm, stale sigh. The vinum(8) GOTCHAS 2. is not explicit about my > situation. Well, I would have thought that the fact you have no drives would give you something to think about. > this time, no `vinum resetconfig`, so:) > > # vinum detach raid.p0 > # vinum detach raid.p0.s0 > # vinum detach raid.p0.s1 > > (Maybe this was too stupid and I get a deserved:) > ..panic.. > > IdlePTD 3686400 > initial pcb at 2f747c > panicstr: integer divide fault > panic messages: > --- > Fatal trap 18: integer divide fault while in kernel mode > instruction pointer = 0x8:0xc0283b27 > stack pointer = 0x10:0xc377cc64 > frame pointer = 0x10:0xc377ccd8 > 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 = 330 (vinum) > interrupt mask = > trap number = 18 > panic: integer divide fault > > syncing disks... 3 3 done > > running gdb post mortem: > > #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 > #1 0xc016e6f5 in panic (fmt=0xc02c9ea9 "integer divide fault") > at ../../kern/kern_shutdown.c:448 > #2 0xc025a8ce in trap_fatal (frame=0xc377cc28, eva=0) > at ../../i386/i386/trap.c:943 > #3 0xc025a32c in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, > tf_esi = 102400, tf_ebp = -1015558952, tf_isp = -1015559088, tf_ebx = 0, > tf_edx = 0, tf_ecx = 102400, tf_eax = 1, tf_trapno = 18, tf_err = 0, > tf_eip = -1071105241, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, > tf_ss = -1065135960}) at ../../i386/i386/trap.c:586 > #4 0xc0283b27 in __qdivrem (uq=102400, vq=0, arq=0xc377ccf4) > at ../../libkern/qdivrem.c:100 > #5 0xc028496f in __umoddi3 (a=102400, b=0) at ../../libkern/umoddi3.c:51 > #6 0xc0842fe6 in ?? () > #7 0xc0848dc4 in ?? () > #8 0xc0848528 in ?? () > #9 0xc01a0567 in spec_ioctl (ap=0xc377ce0c) > at ../../miscfs/specfs/spec_vnops.c:440 > #10 0xc019fe79 in spec_vnoperate (ap=0xc377ce0c) > at ../../miscfs/specfs/spec_vnops.c:129 > #11 0xc02309a9 in ufs_vnoperatespec (ap=0xc377ce0c) > at ../../ufs/ufs/ufs_vnops.c:2327 > #12 0xc019aae5 in vn_ioctl (fp=0xc0811040, com=3223602776, > data=0xc377ced0 "\001", p=0xc352b780) at vnode_if.h:395 > #13 0xc017a114 in ioctl (p=0xc352b780, uap=0xc377cf84) > at ../../kern/sys_generic.c:564 > #14 0xc025ab17 in syscall (frame={tf_es = 47, tf_ds = 47, > tf_edi = -1077945576, tf_esi = 1, tf_ebp = -1077945696, > tf_isp = -1015558188, tf_ebx = -1077945732, tf_edx = 0, > tf_ecx = 134781696, tf_eax = 54, tf_trapno = 12, tf_err = 2, > tf_eip = 134619728, tf_cs = 31, tf_eflags = 663, tf_esp = -1077945760, > tf_ss = 47}) at ../../i386/i386/trap.c:1101 > #15 0xc024f20c in Xint0x80_syscall () > #16 0x80483d1 in ?? () > #17 0x8048295 in ?? () > #18 0x80480ec in ?? () > > Anything else I can do or inspect? Well, you could RTFM, in this case vinum(4). It tells you in some detail what to do if you have a panic. The stack trace you have there doesn't help. If you give me (root) access to your machine, I'll take a look at it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 17:44: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 4A4AC14DD5 for ; Fri, 9 Apr 1999 17:43:36 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from scientia.demon.co.uk (ident=ben) by scientia.demon.co.uk with local (Exim 2.12 #4) id 10VkhM-000DnQ-00; Sat, 10 Apr 1999 00:28:32 +0100 (envelope-from ben@scientia.demon.co.uk) Date: Sat, 10 Apr 1999 00:28:32 +0100 From: Ben Smithurst To: Dmitry Valdov Cc: freebsd-current@freebsd.org Subject: Re: DoS from local users Message-ID: <19990410002832.A52130@scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Valdov wrote: > Is there Any way to fix it? Yes. Limit the number of processes they can have in /etc/login.conf. If they've already done it once, appropriate use of a baseball bat may make them think twice about doing it again. -- Ben Smithurst ben@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 18:40: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 384961518D; Fri, 9 Apr 1999 18:39:13 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id UAA33242; Fri, 9 Apr 1999 20:29:18 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Fri, 9 Apr 1999 20:29:15 +0000 (GMT) From: eagle To: patl@phoenix.volant.org Cc: Jeremy Lea , The Hermit Hacker , Brian Handy , Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999 patl@phoenix.volant.org wrote: > > I always thought the criteria for inclusion of things into the base > > system was: > > > > 1. Needed for 'make world'; > > 2. Needed to get a basic functioning server up and running; > > 3. Something usefull only within FreeBSD (like the kernel ;), or > > 4. Can't be effectively built outside of /usr/src. > > > > If {g77|f77} can be built as a port, using the system EGCS, then to > > port's it goes. Otherwise why don't we include the Top 20 ports, or > > maybe the Top 25, or... > > The criteria for adding something to the base system is different > than the criteria for removing something from it. In both cases, > it requires compelling reasons to change the status quo. > > Replacing an existing component is somewhat easier, particularly > if backwards compatability is retained. I may be mistaken, but I > believe the current discussion is whether or not to replace f77 > with g77. Didn't we just have this discussion a few months ago??? just put it in the tree already ;) rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 18:40:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 2425015337 for ; Fri, 9 Apr 1999 18:40:33 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id DAA26932; Sat, 10 Apr 1999 03:38:19 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id DAA19991; Sat, 10 Apr 1999 03:38:19 +0200 (MET DST) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id DAA11657; Sat, 10 Apr 1999 03:37:48 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sat, 10 Apr 1999 03:37:47 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: greg@lemis.com, FreeBSD-Current Subject: Re: panic: integer divide fault with vinum In-Reply-To: <19990410100502.Y2142@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Greg Lehey wrote: ... > You need to configure it. Use disklabel -e. No, they where configured. I have one ' d: 17848151 63 vinum ' slice per drive. The only fault where the misspelling of 'stripe' versus 'striped' in the configfile! ... > Not much of anything, in fact. > > > (Ok, after repairing 'striped' in x) > > # vinum create x > > Configuration summary > > > > Drives: 0 (4 configured) > > Volumes: 2 (4 configured) > > Plexes: 1 (8 configured) > > Subdisks: 2 (16 configured) > > > > > > V raid State: down Plexes: 1 Size: 100 MB > > > > P raid.p0 S State: down Subdisks: 2 Size: 100 MB > > > > S raid.p0.s0 State: stale PO: 0 B Size: 50 MB > > S raid.p0.s1 State: stale PO: 256 kB Size: 50 MB > > (Hmm, stale sigh. The vinum(8) GOTCHAS 2. is not explicit about my > > situation. > > Well, I would have thought that the fact you have no drives would give > you something to think about. Hmm, strange - see my above comment regarding the drive configuration. The same disks, the same configfile (but with proper spelled 'striped': # cat x drive d1 device /dev/da1d drive d2 device /dev/da2d volume raid plex org striped 256k sd length 50m drive d1 sd length 50m drive d2 # vinum create x Configuration summary Drives: 2 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D d1 State: up Device /dev/da1d Avail: 8664/8714 MB (99%) D d2 State: up Device /dev/da2d Avail: 8664/8714 MB (99%) V raid State: up Plexes: 1 Size: 100 MB P raid.p0 S State: up Subdisks: 2 Size: 100 MB S raid.p0.s0 State: up PO: 0 B Size: 50 MB S raid.p0.s1 State: up PO: 256 kB Size: 50 MB The panic occurs only, if I first use the incorrect config file with 'stripe', then the corrected one with 'striped' and then detaching the plex and the subdisks. BTW: It should'n panic in any case. ... > Well, you could RTFM, in this case vinum(4). It tells you in some > detail what to do if you have a panic. The stack trace you have there I haven't set up remote debugging. Sorry, its behind a firewall which I can't manipulate and it blocks telnet and ssh at the moment. But I'm shure you can reproduce the panic by following the steps I have taken. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 18:47:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id A34EB1523B for ; Fri, 9 Apr 1999 18:47:13 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA00175; Sat, 10 Apr 1999 11:15:00 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA35028; Sat, 10 Apr 1999 11:14:59 +0930 (CST) Message-ID: <19990410111458.B2142@lemis.com> Date: Sat, 10 Apr 1999 11:14:58 +0930 From: Greg Lehey To: Michael Reifenberger Cc: greg@lemis.com, FreeBSD-Current Subject: Re: panic: integer divide fault with vinum References: <19990410100502.Y2142@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Michael Reifenberger on Sat, Apr 10, 1999 at 03:37:47AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Saturday, 10 April 1999 at 3:37:47 +0200, Michael Reifenberger wrote: > On Sat, 10 Apr 1999, Greg Lehey wrote: > ... >> You need to configure it. Use disklabel -e. > > No, they where configured. > I have one ' d: 17848151 63 vinum ' slice per drive. It looks like you have them now, but you didn't then. > The only fault where the misspelling of 'stripe' versus 'striped' in > the configfile! That's not what your error messages are trying to tell you. >>> (Ok, after repairing 'striped' in x) >>> # vinum create x >>> Configuration summary >>> >>> Drives: 0 (4 configured) >>> Volumes: 2 (4 configured) >>> Plexes: 1 (8 configured) >>> Subdisks: 2 (16 configured) >>> >>> >>> V raid State: down Plexes: 1 Size: 100 MB >>> >>> P raid.p0 S State: down Subdisks: 2 Size: 100 MB >>> >>> S raid.p0.s0 State: stale PO: 0 B Size: 50 MB >>> S raid.p0.s1 State: stale PO: 256 kB Size: 50 MB >>> (Hmm, stale sigh. The vinum(8) GOTCHAS 2. is not explicit about my >>> situation. >> >> Well, I would have thought that the fact you have no drives would give >> you something to think about. > > Hmm, strange - see my above comment regarding the drive configuration. Nope, the error messages are clear. > The same disks, the same configfile (but with proper spelled 'striped': > > # cat x > drive d1 device /dev/da1d > drive d2 device /dev/da2d > volume raid > plex org striped 256k > sd length 50m drive d1 > sd length 50m drive d2 > # vinum create x > Configuration summary > > Drives: 2 (4 configured) This isn't what you had last time > Volumes: 1 (4 configured) > Plexes: 1 (8 configured) > Subdisks: 2 (16 configured) > > D d1 State: up Device /dev/da1d Avail: 8664/8714 MB (99%) > D d2 State: up Device /dev/da2d Avail: 8664/8714 MB (99%) > > V raid State: up Plexes: 1 Size: 100 MB > > P raid.p0 S State: up Subdisks: 2 Size: 100 MB > > S raid.p0.s0 State: up PO: 0 B Size: 50 MB > S raid.p0.s1 State: up PO: 256 kB Size: 50 MB > > The panic occurs only, if I first use the incorrect config file with > 'stripe', then the corrected one with 'striped' and then detaching > the plex and the subdisks. > BTW: It should'n panic in any case. Of course not. >> Well, you could RTFM, in this case vinum(4). It tells you in some >> detail what to do if you have a panic. The stack trace you have there > I haven't set up remote debugging. > > Sorry, its behind a firewall which I can't manipulate and it blocks > telnet and ssh at the moment. Well, then at least you could do what I explain in vinum(4). > But I'm shure you can reproduce the panic by following the steps I > have taken. Possibly. I'll try it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 18:50:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 08E471523B for ; Fri, 9 Apr 1999 18:50:38 -0700 (PDT) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id SAA21553; Fri, 9 Apr 1999 18:48:25 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.2.0.32.19990409184036.00a525e0@216.101.162.50> X-Sender: null@216.101.162.50 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.32 (Beta) Date: Fri, 09 Apr 1999 18:48:25 -0700 To: obrien@NUXI.com From: Manfred Antar Subject: Re: EGCS troubles Cc: current@FreeBSD.ORG In-Reply-To: <19990409093700.B24462@nuxi.com> References: <4.2.0.32.19990409092450.00a3f960@216.101.162.50> <370DA528.A37CFCD6@altavista.net> <4.2.0.32.19990409092450.00a3f960@216.101.162.50> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:37 AM 4/9/99 -0700, David O'Brien wrote: >> The Only way I could get Jade to work with the new compiler >> was with CFLAGS= -O -pipe > >That is not so bad. Before EGCS, we would state that "-O" is the only >optimization that is know to always work and what we tell people to use. > >Mike Smith has written about this many times in Hackers and Current. mysql322 from ports is another one, if you try and compile it with the stock -O -pipe it builds up till almost the end but when it gets to sql.yacc.cc the machine just hangs there and finally dies (no input or output). I have to go into the debugger and reboot. But if you add -fno-exceptions it builds fine.It's taken a couple of days but I've weeded out all of the programs that depended on old gcc libs and rebuilt them. Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 19: 3:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 94665152DA for ; Fri, 9 Apr 1999 19:03:01 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id JAA20291; Fri, 9 Apr 1999 09:24:34 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA57701; Fri, 9 Apr 1999 09:24:30 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904090824.JAA57701@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: GuRu Cc: freebsd-current@freebsd.org Subject: Re: PPP problems in -CURRENT In-reply-to: Your message of "Fri, 09 Apr 1999 12:52:46 +1000." <3.0.3.32.19990409125246.00990d60@b0rk.looksharp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Apr 1999 09:24:29 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anything different happen if you set accmap 000a0000 in your ppp.conf ? If not, you're going to have to approach your ISP and ask them why their ppp implementation is ignoring our requests (which needless to say violates the rfc). > cvsupped, built CURRENT as of April 8th, upgrading a 3.1-STABLE system to > 4.0. A reboot later, all seems fine, except that I'm experiencing severe > problems connecting to my ISP. Everything goes well till after the login > phase, when entering the lcp negotiation phase, then things get FUBARed. > > (passwords have been deliberately blanked, of course. :P) > > I believe that both peers are attempting to negotiate an IP address, but > are failing to do so as shown by the repeated negotiation attempts. The > same PPP configuration file worked as of 24 hours ago on 3.1-STABLE. Any > insight would be greatly appreciated. > > Apr 8 21:15:56 Tasha ppp[294]: Phase: Using interface: tun0 > Apr 8 21:15:56 Tasha ppp[294]: Phase: deflink: Created in closed state > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: set device /dev/cuaa1 > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: set speed 115200 > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: deny lqr > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: set dial ABORT BUSY > ABORT NO\sCARRIER TIMEOUT 5 "" AT > OK-AT-OK ATE1Q0 OK \dATDT\T TIMEOUT 40 CONNECT > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: default: alias enable yes > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set phone xxxxxxx > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set login ABORT > NO\sCARRIER TIMEOUT 5 ogin:--ogin: > login word: word > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set server xxxx > ******** > Apr 8 21:15:56 Tasha ppp[294]: tun0: Phase: Listening at port 4040. > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set timeout 0 > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: set ifaddr > 10.0.0.1/0 10.0.0.2/0 0.0.0.0 0.0.0.0 > Apr 8 21:15:56 Tasha ppp[294]: tun0: Command: pmdemand: add default HISADDR > Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: PPP Started (background mode). > Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: bundle: Establish > Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: deflink: closed -> opening > Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: deflink: Connected! > Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: deflink: opening -> dial > Apr 8 21:15:56 Tasha ppp[295]: tun0: Phase: Phone: xxxxxxx > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: deflink: Dial attempt 1 of 1 > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Send: AT^M > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Expect(5): OK > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Received: AT^M^M > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Received: OK^M > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Send: ATE1Q0^M > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Expect(5): OK > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Received: ATE1Q0^M^M > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Received: OK^M > Apr 8 21:15:56 Tasha ppp[295]: tun0: Chat: Send: ATDTxxxxxxxx^M > Apr 8 21:15:58 Tasha ppp[295]: tun0: Chat: Expect(40): CONNECT > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: ATDTxxxxxxxx^M^M > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: CONNECT > 33600/ARQ/V34/LAPM/V42BIS^M > Apr 8 21:16:13 Tasha ppp[295]: tun0: Phase: deflink: dial -> login > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Expect(5): ogin: > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: ^M > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: login: > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Send: login^M > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Expect(5): word: > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Received: Password: > Apr 8 21:16:13 Tasha ppp[295]: tun0: Chat: Send: password^M > Apr 8 21:16:13 Tasha ppp[295]: tun0: Phase: deflink: login -> lcp > Apr 8 21:16:13 Tasha ppp[295]: tun0: LCP: FSM: Using "deflink" as a > transport > Apr 8 21:16:13 Tasha ppp[295]: tun0: LCP: deflink: State change Initial > --> Closed > Apr 8 21:16:13 Tasha ppp[295]: tun0: LCP: deflink: State change Closed --> > Stopped > Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: deflink: LayerStart > Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(1) state > = Stopped > Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x00000000 > Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 > Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff > Apr 8 21:16:14 Tasha ppp[295]: tun0: LCP: deflink: State change Stopped > --> Req-Sent > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(6) state > = Req-Sent > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(6) state > = Req-Sent > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:16 Tasha ppp[295]: tun0: LCP: deflink: State change Req-Sent > --> Ack-Sent > Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(2) state > = Ack-Sent > Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 > Apr 8 21:16:17 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(7) state > = Ack-Sent > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(7) state > = Ack-Sent > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:19 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(2) state > = Ack-Sent > Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 > Apr 8 21:16:20 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(8) state > = Ack-Sent > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(8) state > = Ack-Sent > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:21 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(9) state > = Ack-Sent > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(9) state > = Ack-Sent > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(2) state > = Ack-Sent > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 > Apr 8 21:16:23 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(10) state > = Ack-Sent > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(10) state > = Ack-Sent > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:25 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: deflink: SendConfigReq(2) state > = Ack-Sent > Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: MRU[4] 1500 > Apr 8 21:16:26 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x49e522ff > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: deflink: RecvConfigReq(11) state > = Ack-Sent > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: deflink: SendConfigAck(11) state > = Ack-Sent > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: ACCMAP[6] 0x000a0000 > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: MAGICNUM[6] 0x987dd166 > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: PROTOCOMP[2] > Apr 8 21:16:27 Tasha ppp[295]: tun0: LCP: ACFCOMP[2] > Apr 8 21:16:29 Tasha ppp[295]: tun0: LCP: deflink: LayerFinish > Apr 8 21:16:29 Tasha ppp[295]: tun0: LCP: deflink: State change Ack-Sent > --> Stopped > Apr 8 21:16:29 Tasha ppp[295]: tun0: LCP: deflink: State change Stopped > --> Closed > Apr 8 21:16:29 Tasha ppp[295]: tun0: LCP: deflink: State change Closed --> > Initial > Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: deflink: Disconnected! > Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: deflink: lcp -> hangup > Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: deflink: Connect time: 33 > secs: 408 octets in, 539 octets out > Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: total 28 bytes/sec, peak 76 > bytes/sec on Thu Apr 8 21:16:29 1999 > Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: deflink: hangup -> closed > Apr 8 21:16:29 Tasha ppp[295]: tun0: Phase: bundle: Dead > Apr 8 21:16:59 Tasha ppp[295]: tun0: Phase: PPP Terminated (normal). > Apr 8 21:16:59 Tasha ppp[295]: tun0: Phase: Parent notified of success. > Apr 8 21:16:59 Tasha ppp[294]: tun0: Phase: Parent: Child failed (errdead). > > > -- > K -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 19: 8:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id E505514CFA for ; Fri, 9 Apr 1999 19:08:01 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id EAA00334; Sat, 10 Apr 1999 04:05:49 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id EAA20070; Sat, 10 Apr 1999 04:05:49 +0200 (MET DST) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id EAA15511; Sat, 10 Apr 1999 04:05:11 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sat, 10 Apr 1999 04:05:10 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: greg@lemis.com, FreeBSD-Current Subject: Re: panic: integer divide fault with vinum In-Reply-To: <19990410111458.B2142@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Greg Lehey wrote: ... > It looks like you have them now, but you didn't then. Strange, I'm shure I haven't touched them. > > > The only fault where the misspelling of 'stripe' versus 'striped' in > > the configfile! > > That's not what your error messages are trying to tell you. That seems right. > ... > >>> S raid.p0.s0 State: stale PO: 0 B Size: 50 MB > >>> S raid.p0.s1 State: stale PO: 256 kB Size: 50 MB > >>> (Hmm, stale sigh. The vinum(8) GOTCHAS 2. is not explicit about my > >>> situation. > >> ... > > The panic occurs only, if I first use the incorrect config file with > > 'stripe', then the corrected one with 'striped' and then detaching > > the plex and the subdisks. This point is still valid. I just reproduced the panic again. This time the disks showed up and the errormessages where slightly different. They are not important for the panic. I did: )# vinum l Configuration summary Drives: 2 (4 configured) Volumes: 2 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D d1 State: up Device /dev/da1d Avail: 8664/8714 MB (99%) D d2 State: up Device /dev/da2d Avail: 8664/8714 MB (99%) V raid State: down Plexes: 1 Size: 100 MB P raid.p0 S State: down Subdisks: 2 Size: 100 MB S raid.p0.s0 State: stale PO: 0 B Size: 50 MB S raid.p0.s1 State: stale PO: 256 kB Size: 50 MB # vinum detach raid.p0 # vinum detach raid.p0.s0 # vinum detach raid.p0.s1 ..panic.. It seems to be important to remove the last stale subdisk. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 19:32:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 9964314EFF for ; Fri, 9 Apr 1999 19:32:38 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA00341; Sat, 10 Apr 1999 12:00:25 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA35172; Sat, 10 Apr 1999 12:00:24 +0930 (CST) Message-ID: <19990410120023.F2142@lemis.com> Date: Sat, 10 Apr 1999 12:00:23 +0930 From: Greg Lehey To: Michael Reifenberger Cc: greg@lemis.com, FreeBSD-Current Subject: Re: panic: integer divide fault with vinum References: <19990410111458.B2142@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Michael Reifenberger on Sat, Apr 10, 1999 at 04:05:10AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 10 April 1999 at 4:05:10 +0200, Michael Reifenberger wrote: > On Sat, 10 Apr 1999, Greg Lehey wrote: >>> The panic occurs only, if I first use the incorrect config file with >>> 'stripe', then the corrected one with 'striped' and then detaching >>> the plex and the subdisks. > > This point is still valid. In fact, it's not necessary. It happens any time you detach the last subdisk from a striped or RAID-5 plex. > # vinum detach raid.p0 > # vinum detach raid.p0.s0 > # vinum detach raid.p0.s1 > ..panic.. > > It seems to be important to remove the last stale subdisk. Correct. What happened to the stack traces? Don't bother, though, I've reproduced it here. Expect a fix in a couple of hours. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 19:44: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B2F9214F8B for ; Fri, 9 Apr 1999 19:44:04 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA27301; Fri, 9 Apr 1999 19:41:45 -0700 (PDT) (envelope-from dillon) Date: Fri, 9 Apr 1999 19:41:45 -0700 (PDT) From: Matthew Dillon Message-Id: <199904100241.TAA27301@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.1 stable bootloader vs. 4.0 kernel... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Did I miss something obvious here? I have a system over in England :somewhere which I'm remotely booting. It's 3.1Stable. When I try and put a :4.0/-current kernel (which boots fine on *my* much overwritten and not :reinstalled since 2.2.2 system), I get: : :Type '?' for a list of commands, 'help' for more detailed help. :disk1s1a:> :boot kernel.tst :/kernel.tst text=0x1a312e :elf_loadexec: archsw.readin failed :can't load module '/kernel.tst': input/output error : :Eh? : :-matt Update your sources and install a new /boot. 4.x kernels need the latest boot code due to the kernel's new start address. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 19:46:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id ACABD14F8B for ; Fri, 9 Apr 1999 19:46:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id TAA15305; Fri, 9 Apr 1999 19:44:00 -0700 Date: Fri, 9 Apr 1999 19:43:59 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.1 stable bootloader vs. 4.0 kernel... In-Reply-To: <199904100241.TAA27301@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Update your sources and install a new /boot. 4.x kernels need the > latest boot code due to the kernel's new start address. > Ah. Well, I'm fine at Feral where I do stuff- it's just an interesting gotcha for folks running 3.X now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 20:35:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6D70814D28 for ; Fri, 9 Apr 1999 20:35:42 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA62071; Fri, 9 Apr 1999 23:33:33 -0400 (EDT) Date: Fri, 9 Apr 1999 23:33:32 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Doug White Cc: Alex Zepeda , current Subject: Re: msdosfs problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Doug White wrote: > On Thu, 8 Apr 1999, Alex Zepeda wrote: > > > I've got all my mp3s stored on my fat16 partition so I can easily share > > them between Win98 and fbsd. However recently mpg123 has been complaining > > about once valid mp3s: > > > > zippy:~/mp3s#mpg123 -b10240 U2/U2\ -\ Sunday\ Bloody\ Sunday.mp3 > > High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. > > Version 0.59q (1999/Jan/26). Written and copyrights by Michael Hipp. > > Uses code from various people. See 'README' for more! > > THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! > > Title : Sunday Bloody Sunday Artist: U2 > > Album : Year: 83 > > Comment: Genre: Alternative > > > > Directory: U2/ > > Playing MPEG stream from U2 - Sunday Bloody Sunday.mp3 ... > > MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo > > Illegal Audio-MPEG-Header 0x00000000 at offset 0x80af. > > Skipped 4170 bytes in input. > > mpg123: Can't rewind stream by 679 bits! > > mpg123 is an ancient player. It won't play most newer MP3s. Use a newer > player, like x11amp or xaudio. In its defense, mpg123 is not ancient, and is the _BEST_ MP3 player. I have no idea what kinda of b0rked up MP3s there are nowadays it won't play. > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 20:39:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (libya-207.ppp.hooked.net [206.169.227.207]) by hub.freebsd.org (Postfix) with ESMTP id 0A6DE14D28 for ; Fri, 9 Apr 1999 20:39:15 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id UAA33141; Fri, 9 Apr 1999 20:36:57 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Fri, 9 Apr 1999 20:36:57 -0700 (PDT) From: Alex Zepeda To: Doug White Cc: current Subject: Re: msdosfs problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Doug White wrote: > > It's not mpg123. There were some files that never caused a problem with > > the same version of mpg123 before. And besides, x11amp is based on mpg123 > > isn't it? > > No. Hrm. I thought I saw that x11amp 0.9* was based on mpg123.. > How does xaudio react? > I don't buy that it's a FS-related difficulty; > you can play MP3s over NFS without trouble. Over UFS. The only NFS related mount I have is via Sharity-Lite (rumba), over a 33.6 modem. I already know how that would turn out. > > That still doesn't explain how it would cause my system to hang. > > Grr. Back to CDs it is. > > Sound system problem? No. The mp3s stored on the UFS partition are fine. And it's not just some of the MP3s on the fat partition, it's all of them, which is really really weird. I couldn't find xaudio, but amp belched a bit too. All in all it's really strange, I'm willing to accept random data corruption (although, scandisk didn't find any problems with the partition).. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 20:42: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 03C9E1517C for ; Fri, 9 Apr 1999 20:41:58 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 16061 invoked by uid 1008); 10 Apr 1999 03:39:20 -0000 Message-ID: <19990410033920.16059.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: freebsd-current@freebsd.org Subject: Re: msdosfs problems? In-reply-to: Your message of "Fri, 09 Apr 1999 23:33:32 -0400." Date: Sat, 10 Apr 1999 11:39:20 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: [snip] >> mpg123 is an ancient player. It won't play most newer MP3s. Use a newer >> player, like x11amp or xaudio. > >In its defense, mpg123 is not ancient, and is the _BEST_ MP3 player. I have >no idea what kinda of b0rked up MP3s there are nowadays it won't play. Crappy Windows encoders. I have a bunch of mp3s that play under xaudio but not mpg123. The mp3s I've encoded under various unix based encoders happily played under unix. But windows ones have all sorts of fun - some don't play at all, some have large skips (sound like 'smudges' in the music where it says "can't rewind stream by x bits!"..) but play perfect in xaudio/windows players. Which is all fine and good, except xaudio for some reason doesn't like my 2.2.7-REL laptop (plays sound at a fraction of the real speed).. Whether mpg123 is at fault from a 'standards' point of view, or the encoder is just crappy (more likely IMHO) and xaudio caters for it is something I don't have the answer for. MPEG heads out there, care to comment .. ? Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 20:43:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id A7300151DB for ; Fri, 9 Apr 1999 20:43:37 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 16086 invoked by uid 1008); 10 Apr 1999 03:41:00 -0000 Message-ID: <19990410034100.16084.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Alex Zepeda Cc: freebsd-current@freebsd.org Subject: Re: msdosfs problems? In-reply-to: Your message of "Fri, 09 Apr 1999 20:36:57 MST." Date: Sat, 10 Apr 1999 11:41:00 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Sound system problem? > >No. The mp3s stored on the UFS partition are fine. And it's not just >some of the MP3s on the fat partition, it's all of them, which is really >really weird. I couldn't find xaudio, but amp belched a bit too. All in >all it's really strange, I'm willing to accept random data corruption >(although, scandisk didn't find any problems with the partition).. > Ok, so if you copy them onto your UFS partition first, do they play ok? (Just to be clear here..) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 20:54:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 26656151D4 for ; Fri, 9 Apr 1999 20:54:16 -0700 (PDT) (envelope-from tr49986@rcc.on.ca) Received: from rcc.on.ca (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with ESMTP id BAA23489; Sat, 10 Apr 1999 01:11:12 -0400 Message-ID: <370F11DF.F0BBACFF@rcc.on.ca> Date: Sat, 10 Apr 1999 04:54:56 -0400 From: Rod Taylor X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: "Daniel O'Connor" , current@freebsd.org Subject: Re: CD Mount Troubles References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > On 09-Apr-99 Rod Taylor wrote: > > My Joliet formated cd's aren't mounting with the Joliet extensions. I > > believe I saw that FreeBSD supported these extensions. I'm mounting > > mostly recorded cds, in older nec cdrom drives. (OS/2 mounts joliet > > extensions fine on same machine). > > There are patches which add Joliet support, but they don't work 100%.. > > I have a CD which gets mangled with the patches, so I haven't submitted them > yet :) > > > Some disks done mount at all, and are complained about. It reports that > > the cd just plain old 'does not exist'. > > ? You mean you get an I/O error? A Joliet CD should mount, just that you'll get > Windows short names instead of long names. Nope (Nec 4x4 changer using OLD drivers). --- in fstab --- /dev/wcd0a /mnt/cd0 cd9660 ro,noauto 0 0 /dev/wcd1a /mnt/cd1 cd9660 ro,noauto 0 0 /dev/wcd2a /mnt/cd2 cd9660 ro,noauto 0 0 /dev/wcd3a /mnt/cd3 cd9660 ro,noauto 0 0 -------- mount /mnt/cd0 cd9660: Invalid argument mount /mnt/cd1 mount /mnt/cd2 cd9660: Invalid argument mount /mnt/cd3 (cd0, cd1, cd2 ==> CD's burned with easy cd for windows (joliet filesystem)) (cd3 ==> Purchassed cd. 'Regular Filesystem'). cd1 mounted, but without the joliet extensions. cd0, cd2 didn't mount (with above error). cd3 mounted with long filenames (unsure of filesystem type). That help clarify things a bit more? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 20:54:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (libya-206.ppp.hooked.net [206.169.227.206]) by hub.freebsd.org (Postfix) with ESMTP id AE8CA1535C; Fri, 9 Apr 1999 20:54:34 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id UAA00261; Fri, 9 Apr 1999 20:52:10 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Fri, 9 Apr 1999 20:52:10 -0700 (PDT) From: Alex Zepeda To: adrian@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: msdosfs problems? In-Reply-To: <19990410034100.16084.qmail@ewok.creative.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999 adrian@FreeBSD.ORG wrote: > >No. The mp3s stored on the UFS partition are fine. And it's not just > >some of the MP3s on the fat partition, it's all of them, which is really > >really weird. I couldn't find xaudio, but amp belched a bit too. All in > >all it's really strange, I'm willing to accept random data corruption > >(although, scandisk didn't find any problems with the partition).. > > > > Ok, so if you copy them onto your UFS partition first, do they play ok? > (Just to be clear here..) No. I'm thinking a big magnet walked up while I was sleeping or something, b/c if I copy from UFS -> FAT it plays fine from FAT. Well, I just tried playing an mp3 from the zip drive and here's the panic I got (couldn't catch it from X): panic: vm_page_bits: illegal base/size 4096/2048 Haven't run scandisk on the disk recently, but windows groks it fine.... - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 21: 9:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 17CFB151D4 for ; Fri, 9 Apr 1999 21:09:53 -0700 (PDT) (envelope-from tr49986@rcc.on.ca) Received: from rcc.on.ca (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with ESMTP id BAA23528 for ; Sat, 10 Apr 1999 01:26:57 -0400 Message-ID: <370F1592.8AF97FD1@rcc.on.ca> Date: Sat, 10 Apr 1999 05:10:42 -0400 From: Rod Taylor X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: ATTENTION PLEASE: g77 in base system. References: <19990409155258.A3791@shale.csir.co.za> <370E0C68.3F59295C@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Right or wrong, you forgot: > > 5. BSD tradition. > > Case 5 justifies Fortran. > > Me, I'd rather have Fortran as a port. I'd even grudgingly accept > fortune as a port, as a matter of fact. Our base system is bloated. > While a lot of widely used programs are only available through > ports, a lot of obscure and obsolete stuff remains on our tree. They > are there because of 5. As long as 5 exists, Fortran belongs in the > tree. If we ever get rid of 5, then it's time to get the knife to > our tree... Or the axe, if the vikings decide to have the first cut. > :-) > Whelp... I vote to break tradition. Hack away... The installer takes care of alot of stuff like ports installs. Perhaps different standard setups could be configured as ports. Ie. 'bloated setup' would require all the ports which are currently included. 'Server setup' port wouldn't have any Client stuff. 'Desktop' could install a 'nicer' windomanager (kde? gnome?) for teh user, and be pre-setup to start xdm, etc. The installer can currently install packages, so reworking those 'system install options' to fit simpler naming convention than 'Kernel Hacker, X user, X+ source, etc.' may be appropriate. I know.. lots of talk and no action. Oh well... my thoughts :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 21:25:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 6E8DC14F06 for ; Fri, 9 Apr 1999 21:25:19 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id XAA20962; Fri, 9 Apr 1999 23:21:15 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Fri, 9 Apr 1999 23:21:14 +0000 (GMT) From: eagle To: Rod Taylor Cc: current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <370F1592.8AF97FD1@rcc.on.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Rod Taylor wrote: > > Right or wrong, you forgot: > > > > 5. BSD tradition. > > > > Case 5 justifies Fortran. > > > > Me, I'd rather have Fortran as a port. I'd even grudgingly accept > > fortune as a port, as a matter of fact. Our base system is bloated. > > While a lot of widely used programs are only available through > > ports, a lot of obscure and obsolete stuff remains on our tree. They > > are there because of 5. As long as 5 exists, Fortran belongs in the > > tree. If we ever get rid of 5, then it's time to get the knife to > > our tree... Or the axe, if the vikings decide to have the first cut. > > :-) > > > > Whelp... I vote to break tradition. Hack away... The installer takes > care of alot of stuff like ports installs. Perhaps different standard > setups could be configured as ports. Ie. 'bloated setup' would require > all the ports which are currently included. > > 'Server setup' port wouldn't have any Client stuff. > > 'Desktop' could install a 'nicer' windomanager (kde? gnome?) for teh user, > and be pre-setup to start xdm, etc. > > The installer can currently install packages, so reworking those 'system > install options' to fit simpler naming convention than 'Kernel Hacker, X > user, X+ source, etc.' may be appropriate. > > I know.. lots of talk and no action. Oh well... my thoughts :) > well geeze Xwindows isnt in the base source tree anymore, what more do ya want ;) rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 21:29:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5548E14F06 for ; Fri, 9 Apr 1999 21:29:43 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id AAA84921; Sat, 10 Apr 1999 00:24:27 -0400 (EDT) Date: Sat, 10 Apr 1999 00:24:26 -0400 (EDT) From: Chuck Robey To: eagle Cc: Rod Taylor , current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, eagle wrote: > > Whelp... I vote to break tradition. Hack away... The installer takes > > care of alot of stuff like ports installs. Perhaps different standard > > setups could be configured as ports. Ie. 'bloated setup' would require > > all the ports which are currently included. > > > > 'Server setup' port wouldn't have any Client stuff. > > > > 'Desktop' could install a 'nicer' windomanager (kde? gnome?) for teh user, > > and be pre-setup to start xdm, etc. > > > > The installer can currently install packages, so reworking those 'system > > install options' to fit simpler naming convention than 'Kernel Hacker, X > > user, X+ source, etc.' may be appropriate. > > > > I know.. lots of talk and no action. Oh well... my thoughts :) > > > well geeze Xwindows isnt in the base source tree anymore, what more do > ya want ;) Anymore? It's never been there to begin with. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 21:33:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 14F5F14F06 for ; Fri, 9 Apr 1999 21:33:06 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id XAA21005; Fri, 9 Apr 1999 23:28:09 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Fri, 9 Apr 1999 23:28:09 +0000 (GMT) From: eagle To: Chuck Robey Cc: Rod Taylor , current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Chuck Robey wrote: > On Fri, 9 Apr 1999, eagle wrote: > > > > Whelp... I vote to break tradition. Hack away... The installer takes > > > care of alot of stuff like ports installs. Perhaps different standard > > > setups could be configured as ports. Ie. 'bloated setup' would require > > > all the ports which are currently included. > > > > > > 'Server setup' port wouldn't have any Client stuff. > > > > > > 'Desktop' could install a 'nicer' windomanager (kde? gnome?) for teh user, > > > and be pre-setup to start xdm, etc. > > > > > > The installer can currently install packages, so reworking those 'system > > > install options' to fit simpler naming convention than 'Kernel Hacker, X > > > user, X+ source, etc.' may be appropriate. > > > > > > I know.. lots of talk and no action. Oh well... my thoughts :) > > > > > well geeze Xwindows isnt in the base source tree anymore, what more do > > ya want ;) > > Anymore? It's never been there to begin with. perhaps i'm wrong but i woulda swore it was in /usr/src/contrib in 4.4lite2 at least rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 21:37: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id BA2B714D7D for ; Fri, 9 Apr 1999 21:36:49 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id AAA86596; Sat, 10 Apr 1999 00:31:46 -0400 (EDT) Date: Sat, 10 Apr 1999 00:31:45 -0400 (EDT) From: Chuck Robey To: eagle Cc: Rod Taylor , current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, eagle wrote: > > > On Sat, 10 Apr 1999, Chuck Robey wrote: > > > On Fri, 9 Apr 1999, eagle wrote: > > > > > > Whelp... I vote to break tradition. Hack away... The installer takes > > > > care of alot of stuff like ports installs. Perhaps different standard > > > > setups could be configured as ports. Ie. 'bloated setup' would require > > > > all the ports which are currently included. > > > > > > > > 'Server setup' port wouldn't have any Client stuff. > > > > > > > > 'Desktop' could install a 'nicer' windomanager (kde? gnome?) for teh user, > > > > and be pre-setup to start xdm, etc. > > > > > > > > The installer can currently install packages, so reworking those 'system > > > > install options' to fit simpler naming convention than 'Kernel Hacker, X > > > > user, X+ source, etc.' may be appropriate. > > > > > > > > I know.. lots of talk and no action. Oh well... my thoughts :) > > > > > > > well geeze Xwindows isnt in the base source tree anymore, what more do > > > ya want ;) > > > > Anymore? It's never been there to begin with. > perhaps i'm wrong but i woulda swore it was in /usr/src/contrib in > 4.4lite2 at least It's never ever been in any FreeBSD sources. I didn't take a look at the 4.4Lite2 sources before they were brought into FreeBSD, but it's not been any part of FreeBSD, of that I'm certain. > > > rob > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 21:51: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.24]) by hub.freebsd.org (Postfix) with ESMTP id EC84B14D7D; Fri, 9 Apr 1999 21:50:31 -0700 (PDT) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id EAA75751; Sat, 10 Apr 1999 04:46:57 GMT (envelope-from zach) Date: Fri, 9 Apr 1999 23:46:57 -0500 From: Zach Heilig To: adrian@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: msdosfs problems? Message-ID: <19990409234657.A75720@k6n1.znh.org> References: <19990410033920.16059.qmail@ewok.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990410033920.16059.qmail@ewok.creative.net.au>; from adrian@freebsd.org on Sat, Apr 10, 1999 at 11:39:20AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 10, 1999 at 11:39:20AM +0800, adrian@freebsd.org wrote: > >In its defense, mpg123 is not ancient, and is the _BEST_ MP3 player. I have > >no idea what kinda of b0rked up MP3s there are nowadays it won't play. > Crappy Windows encoders. I have a bunch of mp3s that play under xaudio but > not mpg123. And I have several mp3s that play just fine for mpg123 but not for xaudio. Maybe I just have an older version of xaudio (April 24, 1998 is the timestamp). -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 23:24:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 750E814D51 for ; Fri, 9 Apr 1999 23:24:06 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.0) with SMTP id KAA25103; Sat, 10 Apr 1999 10:21:49 +0400 (MSD) Date: Sat, 10 Apr 1999 10:21:49 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: oZZ!!! Cc: freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, oZZ!!! wrote: > Date: Sat, 10 Apr 1999 02:27:22 +0400 (MSD) > From: oZZ!!! > To: Dmitry Valdov > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: DoS from local users > > > > Hi! > > Try it: > > > > cat > qqq > > echo $$ > > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > > > > Ctrl-D > > > > ./qqq > > > > Is there Any way to fix it? > > > > Dmitry. > > > % cat > qqq > echo $$ > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > % ./qqq > ./qqq: Permission denied. > % > & what fix? > Oh, sorry, chmod 555 qqq. I was drunk a little :) Machine will have load average about 20-40. Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 23:44:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 41B0415048 for ; Fri, 9 Apr 1999 23:44:46 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.0) with SMTP id KAA00627 for ; Sat, 10 Apr 1999 10:42:33 +0400 (MSD) Date: Sat, 10 Apr 1999 10:42:33 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@freebsd.org Subject: Re: DoS from local users (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Chris Costello wrote: > Date: Fri, 9 Apr 1999 18:30:31 -0500 > From: Chris Costello > Reply-To: chris@calldei.com > To: Dmitry Valdov > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: DoS from local users > > On Fri, Apr 9, 1999, Dmitry Valdov wrote: > > Hi! > > > > Try it: > > > > cat > qqq > > echo $$ > > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > > > > Ctrl-D > > > > ./qqq > > > > Is there Any way to fix it? > > You typically want to set a restriction as to how many > processes a user can spawn. This is done by editing > /etc/login.conf and changing the user's login class, see the man > page for 'login.conf'. > I'm about CPU usage, not about many processes. See: CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% idle on any (tested on P2-45) machine. CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf And load average can be up to 20-40 :( Please don't redirect me to -questions, it's a kernel problem, not just config. Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 9 23:50: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from EventHorizon.STARDreams.org (maccess-01-011.magna.com.au [203.111.85.11]) by hub.freebsd.org (Postfix) with ESMTP id B94AD15048 for ; Fri, 9 Apr 1999 23:49:57 -0700 (PDT) (envelope-from guru@b0rk.looksharp.net) Received: from EventHorizon ([10.144.144.1]) by EventHorizon.STARDreams.org (Netscape Mail Server v2.01) with SMTP id AAA241; Sat, 10 Apr 1999 16:49:03 +1000 Message-Id: <3.0.3.32.19990410164553.00b326f0@b0rk.looksharp.net> X-Sender: guru@b0rk.looksharp.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 10 Apr 1999 16:45:53 +1000 To: Brian Somers From: GuRu Subject: Re: PPP problems in -CURRENT Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199904090824.JAA57701@keep.lan.Awfulhak.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:24 4/9/99 +0100, Brian Somers wrote: >Does anything different happen if you > > set accmap 000a0000 > >in your ppp.conf ? If not, you're going to have to approach your ISP >and ask them why their ppp implementation is ignoring our requests >(which needless to say violates the rfc). It would appear that a few more things are wrong, because the setting doesn't help on my 4.0-CURRENT box, but downgrading to 3.1-RELEASE fixes the problem. With this in mind, I copied and gzipped the 3.1-RELEASE ppp binaries (known to work) to a safe place, upgraded to 4.0-CURRENT once more, and attempted to use the 3.1-REL binaries with 4.0. The strange thing is that it doesn't work. I'm retreating to the relative sanity of 3.1-STABLE, will let you know what happens. -- K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 0: 8:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id E1E8015398; Sat, 10 Apr 1999 00:08:09 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip241.houston2.tx.pub-ip.psi.net [38.11.201.241]) by leap.innerx.net (Postfix) with ESMTP id F082F37087; Sat, 10 Apr 1999 03:05:37 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id CAA08096; Sat, 10 Apr 1999 02:05:35 -0500 (CDT) (envelope-from chris) Date: Sat, 10 Apr 1999 02:05:33 -0500 From: Chris Costello To: Dmitry Valdov Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: DoS from local users (fwd) Message-ID: <19990410020533.A8083@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Dmitry Valdov on Sat, Apr 10, 1999 at 10:42:33AM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > You typically want to set a restriction as to how many > > processes a user can spawn. This is done by editing > > /etc/login.conf and changing the user's login class, see the man > > page for 'login.conf'. > > > > I'm about CPU usage, not about many processes. > See: > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > idle > on any (tested on P2-45) machine. > > CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf > And load average can be up to 20-40 :( > > Please don't redirect me to -questions, it's a kernel problem, not just > config. How is it a kernel problem? It's a forkbomb. It spawns many processes. You can also limit CPU usage with login.conf, I believe. > > Dmitry. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- =================================================== * Using TSO is like kicking a dead whale down the * * beach. -- S. C. Johnson * =================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 0:15: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id DAA0614DCC for ; Sat, 10 Apr 1999 00:15:06 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.0) with SMTP id LAA09630 for ; Sat, 10 Apr 1999 11:12:53 +0400 (MSD) Date: Sat, 10 Apr 1999 11:12:53 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@freebsd.org Subject: pipe DOS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Just tested it with user who has maxproc 32 set. Here is the results: last pid: 58668; load averages: 27.06, 19.94, 12.67 up 0+09:40:46 11:06:11 77 processes: 31 running, 46 sleeping CPU states: 14.9% user, 0.0% nice, 85.1% system, 0.0% interrupt, 0.0% idle Mem: 26M Active, 12M Inact, 10M Wired, 5392K Cache, 2371K Buf, 7440K Free Swap: 130M Total, 130M Free CPU usage limit also will not fix it because CPU time is used by system :( Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 0:17: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 2BE9514DCC; Sat, 10 Apr 1999 00:16:55 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.0) with SMTP id LAA09722; Sat, 10 Apr 1999 11:14:37 +0400 (MSD) Date: Sat, 10 Apr 1999 11:14:37 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: chris@calldei.com Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-Reply-To: <19990410020533.A8083@holly.dyndns.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Chris Costello wrote: > Date: Sat, 10 Apr 1999 02:05:33 -0500 > From: Chris Costello > Reply-To: chris@calldei.com > To: Dmitry Valdov > Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG > Subject: Re: DoS from local users (fwd) > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > You typically want to set a restriction as to how many > > > processes a user can spawn. This is done by editing > > > /etc/login.conf and changing the user's login class, see the man > > > page for 'login.conf'. > > > > > > > I'm about CPU usage, not about many processes. > > See: > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > > idle > > on any (tested on P2-45) machine. > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf > > And load average can be up to 20-40 :( > > > > Please don't redirect me to -questions, it's a kernel problem, not just > > config. > > How is it a kernel problem? It's a forkbomb. It spawns many > processes. You can also limit CPU usage with login.conf, I > believe. Hmm. How I can limit CPU usage by SYSTEM? See top's output below. Dmitry. PS. I've just tried it. And I'm right - CPU usage limit can't help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 1:21: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 3D09514E2D for ; Sat, 10 Apr 1999 01:20:51 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id QAA08119; Sat, 10 Apr 1999 16:18:35 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id QAA12901; Sat, 10 Apr 1999 16:18:35 +0800 Message-Id: <199904100818.QAA12901@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Cc: shocking@bandicoot.prth.tensor.pgs.com Subject: Re: ATTENTION PLEASE: g77 in base system. In-reply-to: Your message of "Fri, 09 Apr 1999 19:08:13 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Apr 1999 16:18:35 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Brian Handy >On Fri, 9 Apr 1999, The Hermit Hacker wrote: > >> [g77 in the source tree] > >>I have to agree here...I personally know noone that actually uses >>Fortran...having it as an option to turn off would be nice...one less >>thing to compile on a buildworld... > >I know *lots* of people that use FORTRAN. That aside, I think I'd be >satisfied with a port. > > >Brian I can see that it would get out of sync very rapidly with our cc - Please put the sources in with egcs and have a know to turn it *on* rather like profiled libs. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 1:51: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 8D61614E86; Sat, 10 Apr 1999 01:50:59 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id KAA98564; Sat, 10 Apr 1999 10:48:45 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id KAA93819; Sat, 10 Apr 1999 10:48:44 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904100848.KAA93819@greenpeace.grondar.za> To: jdp@freebsd.org, obrien@freebsd.org Cc: current@freebsd.org Subject: Libraries with library dependancies Date: Sat, 10 Apr 1999 10:48:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I've been helping somebody along with getting the new libcrypt going, and something has broken recently (post-egcs?), and I'm having a wee problem debugging it. Libcrypt uses routines out of libmd (MD[45]* and SHA*), and a while back (pre-egcs), it was possible to have an "LDADD+=-lmd" in libcrypt's Makefile and have anything using libcrypt also automagically pick up the -lmd dependancy requirement. This no longer seems to work: cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlmain.c cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/include -static -o miniperl miniperlmain.o -lperl -lm -lcrypt /usr/obj/usr/src/tmp/usr/lib/libcrypt.a(crypt-shs.o): In function `crypt_shs': crypt-shs.o(.text+0x11): undefined reference to `SHA_Init' crypt-shs.o(.text+0x1f): undefined reference to `SHA_Update' crypt-shs.o(.text+0x3c): undefined reference to `SHA_Update' The "undefined references" are all in libmd which is listed as above in libcrypt's Makefile. I would hate to have to hunt down all usages of -lcrypt to add -lmd. Any ideas? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 2:30: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from hermes.rz.uni-sb.de (hermes.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id C265C14C80; Sat, 10 Apr 1999 02:29:56 -0700 (PDT) (envelope-from netchild@vodix.cs.uni-sb.de) Received: from mars.rz.uni-sb.de (mars.rz.uni-sb.de [134.96.7.5]) by hermes.rz.uni-sb.de (8.8.8/8.8.7/8.7.7) with ESMTP id LAA11175; Sat, 10 Apr 1999 11:27:36 +0200 (CST) Received: from vodix.cs.uni-sb.de (maxtnt-088.rz.uni-sb.de [134.96.70.215]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id LAA12244; Sat, 10 Apr 1999 11:27:35 +0200 (CST) Received: (from netchild@localhost) by vodix.cs.uni-sb.de (8.9.3/8.9.3) id LAA00689; Sat, 10 Apr 1999 11:27:25 +0200 (CEST) (envelope-from netchild) Date: Sat, 10 Apr 1999 11:27:25 +0200 From: Alexander Leidinger To: Alex Zepeda Cc: adrian@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: msdosfs problems? Message-ID: <19990410112725.B411@work.net.local> Reply-To: Alexander Leidinger Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: x-unknown X-Mailer: Balsa 0.4.9 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sa , 10 Apr 1999 05:52:10 Alex Zepeda wrote: > > Ok, so if you copy them onto your UFS partition first, do they play ok? > > (Just to be clear here..) > > No. I'm thinking a big magnet walked up while I was sleeping or > something, b/c if I copy from UFS -> FAT it plays fine from FAT. What if you copy them with the mtools from FAT to UFS? Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 2:48:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id D172D14FB4 for ; Sat, 10 Apr 1999 02:48:55 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id LAA13648; Sat, 10 Apr 1999 11:46:42 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id LAA20636; Sat, 10 Apr 1999 11:46:42 +0200 (MET DST) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id LAA17855; Sat, 10 Apr 1999 11:46:03 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sat, 10 Apr 1999 11:46:02 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: greg@lemis.com, FreeBSD-Current Subject: Re: panic: integer divide fault with vinum In-Reply-To: <19990410120023.F2142@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Greg Lehey wrote: ... > In fact, it's not necessary. It happens any time you detach the last > subdisk from a striped or RAID-5 plex. Ups... > Correct. What happened to the stack traces? Don't bother, though, > I've reproduced it here. Expect a fix in a couple of hours. Sorry, the stack traces had to be abandoned due to sleep :-) And many thanks for fixing the problem that quickly. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 3:13:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 7CD1814CB7; Sat, 10 Apr 1999 03:13:13 -0700 (PDT) (envelope-from peter@spinner.netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id EF0BC1F4D; Sat, 10 Apr 1999 18:10:50 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray Cc: jdp@freebsd.org, obrien@freebsd.org, current@freebsd.org Subject: Re: Libraries with library dependancies In-reply-to: Your message of "Sat, 10 Apr 1999 10:48:37 +0200." <199904100848.KAA93819@greenpeace.grondar.za> Date: Sat, 10 Apr 1999 18:10:50 +0800 From: Peter Wemm Message-Id: <19990410101057.EF0BC1F4D@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > Hi > > I've been helping somebody along with getting the new libcrypt going, > and something has broken recently (post-egcs?), and I'm having a wee > problem debugging it. > > Libcrypt uses routines out of libmd (MD[45]* and SHA*), and a while > back (pre-egcs), it was possible to have an "LDADD+=-lmd" in libcrypt's > Makefile and have anything using libcrypt also automagically pick up the > -lmd dependancy requirement. This no longer seems to work: > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I /usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/inc lude -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/minipe rlmain.c > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I /usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/inc lude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt ^^^^^^^^^^^^^^^ > /usr/obj/usr/src/tmp/usr/lib/libcrypt.a(crypt-shs.o): In function `crypt_shs' : > crypt-shs.o(.text+0x11): undefined reference to `SHA_Init' > crypt-shs.o(.text+0x1f): undefined reference to `SHA_Update' > crypt-shs.o(.text+0x3c): undefined reference to `SHA_Update' > > The "undefined references" are all in libmd which is listed as above > in libcrypt's Makefile. This is only the case for -static.. Shared libraries have dependency information, static libraries do not. > I would hate to have to hunt down all usages of -lcrypt to add -lmd. It would affect ports too, breaking a lot of things that know about -lcrypt and have never heard of -lmd. The way I see it, you've got several choices.. 1) add -lmd for the cases where things are compiled static and leave the rest 2) compile libcrypt.a differently to libcrypt.so, ie: add in the md*.o and sha*.o static binaries into libcrypt by using SRCS+= sha.c in the !PIC case 3) help move ld.so to / so we can link everything dynamic.. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 3:54:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 3529114EDB; Sat, 10 Apr 1999 03:54:30 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id MAA98914; Sat, 10 Apr 1999 12:52:16 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id MAA94100; Sat, 10 Apr 1999 12:52:14 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904101052.MAA94100@greenpeace.grondar.za> To: Peter Wemm Cc: jdp@freebsd.org, obrien@freebsd.org, current@freebsd.org Subject: Re: Libraries with library dependancies In-Reply-To: Your message of " Sat, 10 Apr 1999 18:10:50 +0800." <19990410101057.EF0BC1F4D@spinner.netplex.com.au> References: <19990410101057.EF0BC1F4D@spinner.netplex.com.au> Date: Sat, 10 Apr 1999 12:52:13 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i nc > lude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt > ^^^^^^^^^^^^^^^ > > /usr/obj/usr/src/tmp/usr/lib/libcrypt.a(crypt-shs.o): In function `crypt_sh s' : > This is only the case for -static.. Shared libraries have dependency > information, static libraries do not. This makes some degree of sense, but could there not be (was there not?) a mechanism that resolves ans many of the symbols as possible at "ar time", so that... > 2) compile libcrypt.a differently to libcrypt.so, ie: add in the md*.o and > sha*.o static binaries into libcrypt by using SRCS+= sha.c in the !PIC case ... happens automagically? > 3) help move ld.so to / so we can link everything dynamic.. :-) Hmm. It will still be broken for the diehards who insist on having everything static :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 4:14:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id AB0D614C94 for ; Sat, 10 Apr 1999 04:14:40 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id MAA01250; Sat, 10 Apr 1999 12:12:25 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA02921; Sat, 10 Apr 1999 12:12:22 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904101112.MAA02921@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: GuRu Cc: Brian Somers , freebsd-current@FreeBSD.ORG Subject: Re: PPP problems in -CURRENT In-reply-to: Your message of "Sat, 10 Apr 1999 16:45:53 +1000." <3.0.3.32.19990410164553.00b326f0@b0rk.looksharp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Apr 1999 12:12:22 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Any chance of sending me the logs for both when the connection works (3.1) and when it doesn't work (4.0) ? set log command tun phase chat lcp ipcp TIA. > At 09:24 4/9/99 +0100, Brian Somers wrote: > >Does anything different happen if you > > > > set accmap 000a0000 > > > >in your ppp.conf ? If not, you're going to have to approach your ISP > >and ask them why their ppp implementation is ignoring our requests > >(which needless to say violates the rfc). > > It would appear that a few more things are wrong, because the setting > doesn't help on my 4.0-CURRENT box, but downgrading to 3.1-RELEASE fixes > the problem. With this in mind, I copied and gzipped the 3.1-RELEASE ppp > binaries (known to work) to a safe place, upgraded to 4.0-CURRENT once > more, and attempted to use the 3.1-REL binaries with 4.0. The strange thing > is that it doesn't work. I'm retreating to the relative sanity of > 3.1-STABLE, will let you know what happens. > > -- > K > > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 6:31:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B336114D28; Sat, 10 Apr 1999 06:31:37 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id JAA69978; Sat, 10 Apr 1999 09:29:19 -0400 (EDT) Date: Sat, 10 Apr 1999 09:29:19 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dmitry Valdov Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > On Sat, 10 Apr 1999, Chris Costello wrote: > > > Date: Sat, 10 Apr 1999 02:05:33 -0500 > > From: Chris Costello > > Reply-To: chris@calldei.com > > To: Dmitry Valdov > > Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG > > Subject: Re: DoS from local users (fwd) > > > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > > You typically want to set a restriction as to how many > > > > processes a user can spawn. This is done by editing > > > > /etc/login.conf and changing the user's login class, see the man > > > > page for 'login.conf'. > > > > > > > > > > I'm about CPU usage, not about many processes. > > > See: > > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > > > idle > > > on any (tested on P2-45) machine. > > > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf > > > And load average can be up to 20-40 :( > > > > > > Please don't redirect me to -questions, it's a kernel problem, not just > > > config. > > > > How is it a kernel problem? It's a forkbomb. It spawns many > > processes. You can also limit CPU usage with login.conf, I > > believe. > > Hmm. How I can limit CPU usage by SYSTEM? See top's output below. > > Dmitry. > > PS. I've just tried it. And I'm right - CPU usage limit can't help. > So? Processes that run a while go down in priority [McKusick95 I believe, THE book] so they are preempted easily. Look in top and see if they're all at the top of the list. I bet they're not! Also, you can set per-user niceness levels, and why are you being so liberal giving a standard LUSER 32 processes? This is a system administration problem. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 6:37:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 3B11A14D28; Sat, 10 Apr 1999 06:37:16 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id JAA70053; Sat, 10 Apr 1999 09:34:37 -0400 (EDT) Date: Sat, 10 Apr 1999 09:34:36 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Peter Wemm Cc: Mark Murray , jdp@FreeBSD.ORG, obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Libraries with library dependancies In-Reply-To: <19990410101057.EF0BC1F4D@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Peter Wemm wrote: > Mark Murray wrote: > > Hi > > > > I've been helping somebody along with getting the new libcrypt going, > > and something has broken recently (post-egcs?), and I'm having a wee > > problem debugging it. > > > > Libcrypt uses routines out of libmd (MD[45]* and SHA*), and a while > > back (pre-egcs), it was possible to have an "LDADD+=-lmd" in libcrypt's > > Makefile and have anything using libcrypt also automagically pick up the > > -lmd dependancy requirement. This no longer seems to work: > > > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/inc > lude -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/minipe > rlmain.c > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/inc > lude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt > ^^^^^^^^^^^^^^^ > > /usr/obj/usr/src/tmp/usr/lib/libcrypt.a(crypt-shs.o): In function `crypt_shs' > : > > crypt-shs.o(.text+0x11): undefined reference to `SHA_Init' > > crypt-shs.o(.text+0x1f): undefined reference to `SHA_Update' > > crypt-shs.o(.text+0x3c): undefined reference to `SHA_Update' > > > > The "undefined references" are all in libmd which is listed as above > > in libcrypt's Makefile. > > This is only the case for -static.. Shared libraries have dependency > information, static libraries do not. > > > I would hate to have to hunt down all usages of -lcrypt to add -lmd. > > It would affect ports too, breaking a lot of things that know about -lcrypt > and have never heard of -lmd. > > The way I see it, you've got several choices.. > > 1) add -lmd for the cases where things are compiled static and leave the > rest > > 2) compile libcrypt.a differently to libcrypt.so, ie: add in the md*.o and > sha*.o static binaries into libcrypt by using SRCS+= sha.c in the !PIC case YES! Make the mdXXX symbols all weak, so libmd can be added manually! > > 3) help move ld.so to / so we can link everything dynamic.. :-) ld.so, ld-elf.so.1 SHOULD be in /, and fschg. They're definitely up there in importance with the kernel. This would allow something nice: /stand being a storage location for shared libraries. /stand meaning "standalone", hinting that only the root partition is necessary to run a shared program if necessary... let's move /usr/lib ELF libraries to /stand and keep all a.out and static libs (other than libgcc, foo) in /usr/lib. On the other hand, maybe that's a little radical! > > Cheers, > -Peter > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 7: 6:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id BDC5C150A9; Sat, 10 Apr 1999 07:06:01 -0700 (PDT) (envelope-from peter@spinner.netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 6825E1F4D; Sat, 10 Apr 1999 22:03:46 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman Cc: Mark Murray , jdp@FreeBSD.ORG, obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Libraries with library dependancies In-reply-to: Your message of "Sat, 10 Apr 1999 09:34:36 -0400." Date: Sat, 10 Apr 1999 22:03:45 +0800 From: Peter Wemm Message-Id: <19990410140348.6825E1F4D@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > On Sat, 10 Apr 1999, Peter Wemm wrote: > > > Mark Murray wrote: > > > Hi > > > > > > I've been helping somebody along with getting the new libcrypt going, > > > and something has broken recently (post-egcs?), and I'm having a wee > > > problem debugging it. > > > > > > Libcrypt uses routines out of libmd (MD[45]* and SHA*), and a while > > > back (pre-egcs), it was possible to have an "LDADD+=-lmd" in libcrypt's > > > Makefile and have anything using libcrypt also automagically pick up the > > > -lmd dependancy requirement. This no longer seems to work: > > > > > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl 5 -I > > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr /inc > > lude -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/mi nipe > > rlmain.c > > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl 5 -I > > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr /inc > > lude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt > > ^^^^^^^^^^^^^^^ > > > /usr/obj/usr/src/tmp/usr/lib/libcrypt.a(crypt-shs.o): In function `crypt_ shs' > > : > > > crypt-shs.o(.text+0x11): undefined reference to `SHA_Init' > > > crypt-shs.o(.text+0x1f): undefined reference to `SHA_Update' > > > crypt-shs.o(.text+0x3c): undefined reference to `SHA_Update' > > > > > > The "undefined references" are all in libmd which is listed as above > > > in libcrypt's Makefile. > > > > This is only the case for -static.. Shared libraries have dependency > > information, static libraries do not. > > > > > I would hate to have to hunt down all usages of -lcrypt to add -lmd. > > > > It would affect ports too, breaking a lot of things that know about -lcrypt > > and have never heard of -lmd. > > > > The way I see it, you've got several choices.. > > > > 1) add -lmd for the cases where things are compiled static and leave the > > rest > > > > 2) compile libcrypt.a differently to libcrypt.so, ie: add in the md*.o and > > sha*.o static binaries into libcrypt by using SRCS+= sha.c in the !PIC case > > YES! Make the mdXXX symbols all weak, so libmd can be added manually! It's not going to be needed, it's a static library remember, they only get pulled in if needed. You could have mdXXX in your main program and it would still work, and you could add -lmd as well with no side effects. > > 3) help move ld.so to / so we can link everything dynamic.. :-) > > ld.so, ld-elf.so.1 SHOULD be in /, and fschg. They're definitely up > there in importance with the kernel. This would allow something nice: > /stand being a storage location for shared libraries. > > /stand meaning "standalone", hinting that only the root partition is > necessary to run a shared program if necessary... let's move /usr/lib > ELF libraries to /stand and keep all a.out and static libs (other than libgcc , > foo) in /usr/lib. > > On the other hand, maybe that's a little radical! What I would like is a minimal /lib, containing a few key libraries like libc.so, libutil.so, etc and have everything dynamic. This costs some speed, PIC code is slower than non-pic code since %ebx is "consumed". However, on the plus side you get to do a proper name server switch, can do dynamic crypt() selection on the fly based on a config file *and* have /sbin/init use it (for checking the single user password on a non-secure console), *and* have some support for alternative getpwnam() style interfaces (eg: usernames from a mysql database, if you're twisted enough, and having the entire OS support it). We can get the DNS resolver out of libc, possibly even YP too, etc. I measured it once, a long time ago early in the ELF development and (if I recall correctly), making /bin and /sbin shared freed up *more* space on the root partition than the extra shared libs and ld.so took up - ie: it saved disk space on /. Incidently, making / shared isn't the only way of doing it if you're prepared to get creative and compile static and dynamic libraries differently.... ie: dynamic libc uses dlopen() to implement the switches, while the static libc does a pipe/fork/etc and makes a pipe-based procedure call instead of a dlsym() direct call. Nah, that's much too radical, they'll never buy it. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 7:14: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id CE45814EB7 for ; Sat, 10 Apr 1999 07:14:00 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.0) with SMTP id SAA07726; Sat, 10 Apr 1999 18:11:44 +0400 (MSD) Date: Sat, 10 Apr 1999 18:11:44 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Brian Feldman Cc: freebsd-current@freebsd.org Subject: Re: DoS from local users (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Once again - HOW I can limit CPU usage by *kernel* ? Also, I've just tried set maxprocesses 5. And it helpless. With 5 processes limit user was able to slow down P2-450 computer. Switching between windows in X was VERY slow. Mouse movements was slow down too. CPU states: 32.3% user, 0.0% nice, 67.2% system, 0.0% interrupt, 0.5% idle Please, just try it. On Sat, 10 Apr 1999, Brian Feldman wrote: > Date: Sat, 10 Apr 1999 09:29:19 -0400 (EDT) > From: Brian Feldman > To: Dmitry Valdov > Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG, > freebsd-questions@FreeBSD.ORG > Subject: Re: DoS from local users (fwd) > > On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > > > > > On Sat, 10 Apr 1999, Chris Costello wrote: > > > > > Date: Sat, 10 Apr 1999 02:05:33 -0500 > > > From: Chris Costello > > > Reply-To: chris@calldei.com > > > To: Dmitry Valdov > > > Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG > > > Subject: Re: DoS from local users (fwd) > > > > > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > > > You typically want to set a restriction as to how many > > > > > processes a user can spawn. This is done by editing > > > > > /etc/login.conf and changing the user's login class, see the man > > > > > page for 'login.conf'. > > > > > > > > > > > > > I'm about CPU usage, not about many processes. > > > > See: > > > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > > > > idle > > > > on any (tested on P2-45) machine. > > > > > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf > > > > And load average can be up to 20-40 :( > > > > > > > > Please don't redirect me to -questions, it's a kernel problem, not just > > > > config. > > > > > > How is it a kernel problem? It's a forkbomb. It spawns many > > > processes. You can also limit CPU usage with login.conf, I > > > believe. > > > > Hmm. How I can limit CPU usage by SYSTEM? See top's output below. > > > > Dmitry. > > > > PS. I've just tried it. And I'm right - CPU usage limit can't help. > > > > So? Processes that run a while go down in priority [McKusick95 I believe, THE > book] so they are preempted easily. Look in top and see if they're all at > the top of the list. I bet they're not! Also, you can set per-user niceness > levels, and why are you being so liberal giving a standard LUSER 32 processes? > This is a system administration problem. > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | > http://www.freebsd.org _ |___/___/___/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 7:32:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 9F16A14EB7 for ; Sat, 10 Apr 1999 07:32:23 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id KAA26327 for current@freebsd.org; Sat, 10 Apr 1999 10:29:50 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904101429.KAA26327@kot.ne.mediaone.net> Subject: Re: DoS from local users (fwd) In-Reply-To: from Dmitry Valdov at "Apr 10, 1999 06:11:44 pm" To: current@freebsd.org Date: Sat, 10 Apr 1999 10:29:49 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Sat, 10 Apr 1999 09:09:07 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA28367; Sun, 11 Apr 1999 01:06:47 +0900 (JST) Message-ID: <370F6CD9.15587122@newsguy.com> Date: Sun, 11 Apr 1999 00:23:05 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Alex Zepeda Cc: Doug White , current Subject: Re: msdosfs problems? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > > No. The mp3s stored on the UFS partition are fine. And it's not just > some of the MP3s on the fat partition, it's all of them, which is really > really weird. I couldn't find xaudio, but amp belched a bit too. All in > all it's really strange, I'm willing to accept random data corruption > (although, scandisk didn't find any problems with the partition).. Please, this is trivial to test. cp a file from msdosfs to ufs. Play it on ufs. Does it work? Then it's a msdosfs-related problem. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9: 9:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E636D15111 for ; Sat, 10 Apr 1999 09:09:18 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA28374; Sun, 11 Apr 1999 01:06:51 +0900 (JST) Message-ID: <370F6F7A.76A4058F@newsguy.com> Date: Sun, 11 Apr 1999 00:34:18 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: loverso@sitaranetworks.com Cc: current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. References: <19990409155258.A3791@shale.csir.co.za> <370E0C68.3F59295C@newsguy.com> <370E1B31.A35C417@sitara.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John R. LoVerso" wrote: > > > Right or wrong, you forgot: > > > > 5. BSD tradition. > > > > Case 5 justifies Fortran. > > By that logic, you'd also have to add a Pascal compiler to the base system. Does gcc has a Pascal? :-) I think we have a Pascal doc under share. > Neither makes much sense when they can both be ports (or packages) easily > addable at install or compile time by the small % of the FreeBSD population that > will actually use them. You are taking for granted the easyness. g77 is part of egcs. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:11:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 0036114E6E; Sat, 10 Apr 1999 09:11:06 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id SAA77648; Sat, 10 Apr 1999 18:05:32 +0200 (SAT) (envelope-from reg) Date: Sat, 10 Apr 1999 18:05:32 +0200 From: Jeremy Lea To: Glenn Johnson Cc: The Hermit Hacker , Brian Handy , Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. Message-ID: <19990410180531.E6250@shale.csir.co.za> References: <19990409155258.A3791@shale.csir.co.za> <19990409112852.A14614@symbion.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990409112852.A14614@symbion.srrc.usda.gov>; from Glenn Johnson on Fri, Apr 09, 1999 at 11:28:52AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, Apr 09, 1999 at 11:28:52AM -0500, Glenn Johnson wrote: > On Fri, Apr 09, 1999 at 03:52:58PM +0200, Jeremy Lea wrote: > > I always thought the criteria for inclusion of things into the base > > system was: > > > > 1. Needed for 'make world'; > > 2. Needed to get a basic functioning server up and running; > > 3. Something usefull only within FreeBSD (like the kernel ;), or > > 4. Can't be effectively built outside of /usr/src. > > > > If {g77|f77} can be built as a port, using the system EGCS, then to > > port's it goes. Otherwise why don't we include the Top 20 ports, or > > maybe the Top 25, or... > > First off, g77 is not your typical port. The build of g77 depends on > having the source to gcc on your system. The last time I checked, > installing the source was optional. The reason the current port of g77 > is marked broken is because of this. See (4) above. Adding it to /usr/src, with a NO_FORTRAN option, would get my vote. > Future: Now it may be true that newer versions of g77 may not build > against whatever version of egcs we have but at least we would be > guaranteed of having a functional Fortran compiler. lang/g77-devel? Depends on lang/egcs-devel? > Many people don't seem to understand that FreeBSD can be used for > workstations as well as servers and Fortran is *essential* on a > scientific/engineering workstation. I don't doubt that there are more > people using FreeBSD as a server but that doesn't mean that workstation > users should be denied an essential tool because it takes up a few > hundred kilobytes. I'm a civil engineer, specialising in data analysis... Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:16:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (seoul-227.ppp.hooked.net [206.169.228.227]) by hub.freebsd.org (Postfix) with ESMTP id E899C14EB6 for ; Sat, 10 Apr 1999 09:16:08 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id JAA24235; Sat, 10 Apr 1999 09:13:48 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sat, 10 Apr 1999 09:13:48 -0700 (PDT) From: Alex Zepeda To: "Daniel C. Sobral" Cc: Doug White , current Subject: Re: msdosfs problems? In-Reply-To: <370F6CD9.15587122@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Daniel C. Sobral wrote: > > No. The mp3s stored on the UFS partition are fine. And it's not just > > some of the MP3s on the fat partition, it's all of them, which is really > > really weird. I couldn't find xaudio, but amp belched a bit too. All in > > all it's really strange, I'm willing to accept random data corruption > > (although, scandisk didn't find any problems with the partition).. > > Please, this is trivial to test. cp a file from msdosfs to ufs. Play > it on ufs. Does it work? Then it's a msdosfs-related problem. I thought I already answered this? No I doesn't work. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:17: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 330D614F98 for ; Sat, 10 Apr 1999 09:17:04 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA28349; Sat, 10 Apr 1999 09:14:51 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA34261; Sat, 10 Apr 1999 09:14:51 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904100848.KAA93819@greenpeace.grondar.za> Date: Sat, 10 Apr 1999 09:14:51 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Mark Murray Subject: RE: Libraries with library dependancies Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > The "undefined references" are all in libmd which is listed as above > in libcrypt's Makefile. > > I would hate to have to hunt down all usages of -lcrypt to add -lmd. As Peter already mentioned, the problem is that library dependencies aren't recorded in archive libraries. I ran into a similar problem for static PAM. After some discussion with Bruce, I held my nose and put this into bsd.libnames.mk: # The static PAM library doesn't know its secondary dependencies, # so we have to specify them explictly. LIBPAM?= ${DESTDIR}${LIBDIR}/libpam.a # XXX doesn't exist MINUSLPAM?= -lpam .if defined(NOSHARED) && ${NOSHARED} != "no" && ${NOSHARED} != "NO" .ifdef MAKE_KERBEROS4 LIBPAM+= ${LIBKRB} ${LIBDES} MINUSLPAM+= -lkrb -ldes .endif LIBPAM+= ${LIBRADIUS} ${LIBTACPLUS} ${LIBSKEY} ${LIBCRYPT} ${LIBMD} MINUSLPAM+= -lradius -ltacplus -lskey -lcrypt -lmd .endif Then in utilities such a login: DPADD+= ${LIBPAM} LDADD+= ${MINUSLPAM} This could get out of hand pretty quickly, but it may be the most reasonable solution at this time. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:23:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8207914EB6 for ; Sat, 10 Apr 1999 09:23:15 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA28386; Sat, 10 Apr 1999 09:21:01 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA34280; Sat, 10 Apr 1999 09:21:00 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 10 Apr 1999 09:21:00 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Brian Feldman Subject: Re: Libraries with library dependancies Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > YES! Make the mdXXX symbols all weak, so libmd can be added manually! Peter already mentioned why that isn't necessary. I just want to add a caution to folks out there. Don't go wild with weak symbols. Think VERY carefully (and get a review) before using them. They should be treated as an absolute last resort. You can paint yourself into a corner before you know it, and you won't find out until it's time to upgrade something and you suddenly realize that none of your old executables will run any more. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:28: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 934A414EB6 for ; Sat, 10 Apr 1999 09:28:02 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id SAA99699; Sat, 10 Apr 1999 18:23:17 +0200 (SAT) (envelope-from reg) Date: Sat, 10 Apr 1999 18:23:16 +0200 From: Jeremy Lea To: "Daniel C. Sobral" Cc: The Hermit Hacker , Brian Handy , Dag-Erling Smorgrav , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. Message-ID: <19990410182316.G6250@shale.csir.co.za> References: <19990409155258.A3791@shale.csir.co.za> <370E0C68.3F59295C@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <370E0C68.3F59295C@newsguy.com>; from Daniel C. Sobral on Fri, Apr 09, 1999 at 11:19:21PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, Apr 09, 1999 at 11:19:21PM +0900, Daniel C. Sobral wrote: > Right or wrong, you forgot: > > 5. BSD tradition. > > Case 5 justifies Fortran. > Me, I'd rather have Fortran as a port. I'd even grudgingly accept > fortune as a port, as a matter of fact. Our base system is bloated. > While a lot of widely used programs are only available through > ports, a lot of obscure and obsolete stuff remains on our tree. They > are there because of 5. As long as 5 exists, Fortran belongs in the > tree. If we ever get rid of 5, then it's time to get the knife to > our tree... Or the axe, if the vikings decide to have the first cut. > :-) Invoking: 6. Whoever brings patches wins. :) -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:29:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 519CC14EB6 for ; Sat, 10 Apr 1999 09:29:56 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA28420; Sat, 10 Apr 1999 09:27:42 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA34302; Sat, 10 Apr 1999 09:27:41 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990410140348.6825E1F4D@spinner.netplex.com.au> Date: Sat, 10 Apr 1999 09:27:41 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Peter Wemm Subject: Re: Libraries with library dependancies Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > What I would like is a minimal /lib, containing a few key libraries like > libc.so, libutil.so, etc and have everything dynamic. I support that idea too. It's time. We can't support all-static systems forever. It's becoming a ball and chain as more and more applications use loadable modules with dlopen(). [Note to Terry: Aww, shut up and show me the code! ;-)] > Incidently, making / shared isn't the only way of doing it if you're > prepared to get creative and compile static and dynamic libraries > differently.... ie: dynamic libc uses dlopen() to implement the > switches, while the static libc does a pipe/fork/etc and makes a > pipe-based procedure call instead of a dlsym() direct call. *gag* *choke* *cough* > Nah, that's much too radical, they'll never buy it. Ya got that right! :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:34:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id B26D014EB6 for ; Sat, 10 Apr 1999 09:34:15 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id SAA99470; Sat, 10 Apr 1999 18:31:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id SAA82343; Sat, 10 Apr 1999 18:31:53 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904101631.SAA82343@greenpeace.grondar.za> To: John Polstra Cc: current@freebsd.org Subject: Re: Libraries with library dependancies In-Reply-To: Your message of " Sat, 10 Apr 1999 09:14:51 MST." References: Date: Sat, 10 Apr 1999 18:31:39 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > I ran into a similar problem for static PAM. After some discussion > with Bruce, I held my nose and put this into bsd.libnames.mk: :-) I can see why you don't like that solution; I can also see why it is unavoidable. Any objections to me doing something similar with libcrypt/libmd? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:38:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id C02A814EB6 for ; Sat, 10 Apr 1999 09:38:43 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id JAA05519; Sat, 10 Apr 1999 09:36:27 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: "Daniel C. Sobral" Cc: loverso@sitaranetworks.com, current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: Message from "Daniel C. Sobral" of "Sun, 11 Apr 1999 00:34:18 +0900." <370F6F7A.76A4058F@newsguy.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 X-URL: http://www.codegen.com Date: Sat, 10 Apr 1999 09:36:27 -0700 Message-ID: <5515.923762187@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does gcc has a Pascal? :-) Actually, yes. It's not a part of it yet, but drops in and builds easily with gcc-2.8.1, and with very little extra work for egcs. Check out . Unlike Modula-3 and Gnat, they wrote the front-end in C, so it's a whole lot easier to port. It drops into a "p" subdir much like the Fortran front-end and includes a bunch of tests. It's a pretty nice dialect too - mostly compatible with Borland's Pascal with object extensions. I personally don't need Fortran or Objective-C, but could use C, C++, gjc (the new Java compiler), and gpc. I'm used to building my own compilers and cross-compilers, so it's no big deal for me either way. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 9:41:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 59FDD14EB6 for ; Sat, 10 Apr 1999 09:41:36 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA28468; Sat, 10 Apr 1999 09:39:23 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA34355; Sat, 10 Apr 1999 09:39:22 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904101631.SAA82343@greenpeace.grondar.za> Date: Sat, 10 Apr 1999 09:39:22 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Mark Murray Subject: Re: Libraries with library dependancies Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > John Polstra wrote: >> I ran into a similar problem for static PAM. After some discussion >> with Bruce, I held my nose and put this into bsd.libnames.mk: > >:-) I can see why you don't like that solution; I can also see why > it is unavoidable. > > Any objections to me doing something similar with libcrypt/libmd? I can't very well object, can I? :-) If it's necessary, then do it. Please fix the definitions of LIBPAM and MINUSLPAM then, to remove the newly-redundant mentions of libmd. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 11: 9:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7641B15154 for ; Sat, 10 Apr 1999 11:09:50 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA01047; Sat, 10 Apr 1999 14:07:28 -0400 (EDT) Date: Sat, 10 Apr 1999 14:07:27 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dmitry Valdov Cc: freebsd-current@freebsd.org Subject: Re: DoS from local users (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Dmitry Valdov wrote: > Hi! > > Once again - HOW I can limit CPU usage by *kernel* ? > Also, I've just tried set maxprocesses 5. > And it helpless. > With 5 processes limit user was able to slow down P2-450 computer. > Switching between windows in X was VERY slow. Mouse movements was slow down > too. > CPU states: 32.3% user, 0.0% nice, 67.2% system, 0.0% interrupt, 0.5% idle > > Please, just try it. If you want to preempt other tasks, make that user's tasks niced!! > > > On Sat, 10 Apr 1999, Brian Feldman wrote: > > > Date: Sat, 10 Apr 1999 09:29:19 -0400 (EDT) > > From: Brian Feldman > > To: Dmitry Valdov > > Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG, > > freebsd-questions@FreeBSD.ORG > > Subject: Re: DoS from local users (fwd) > > > > On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > > > > > > > > > On Sat, 10 Apr 1999, Chris Costello wrote: > > > > > > > Date: Sat, 10 Apr 1999 02:05:33 -0500 > > > > From: Chris Costello > > > > Reply-To: chris@calldei.com > > > > To: Dmitry Valdov > > > > Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG > > > > Subject: Re: DoS from local users (fwd) > > > > > > > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > > > > You typically want to set a restriction as to how many > > > > > > processes a user can spawn. This is done by editing > > > > > > /etc/login.conf and changing the user's login class, see the man > > > > > > page for 'login.conf'. > > > > > > > > > > > > > > > > I'm about CPU usage, not about many processes. > > > > > See: > > > > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > > > > > idle > > > > > on any (tested on P2-45) machine. > > > > > > > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf > > > > > And load average can be up to 20-40 :( > > > > > > > > > > Please don't redirect me to -questions, it's a kernel problem, not just > > > > > config. > > > > > > > > How is it a kernel problem? It's a forkbomb. It spawns many > > > > processes. You can also limit CPU usage with login.conf, I > > > > believe. > > > > > > Hmm. How I can limit CPU usage by SYSTEM? See top's output below. > > > > > > Dmitry. > > > > > > PS. I've just tried it. And I'm right - CPU usage limit can't help. > > > > > > > So? Processes that run a while go down in priority [McKusick95 I believe, THE > > book] so they are preempted easily. Look in top and see if they're all at > > the top of the list. I bet they're not! Also, you can set per-user niceness > > levels, and why are you being so liberal giving a standard LUSER 32 processes? > > This is a system administration problem. > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | > > http://www.freebsd.org _ |___/___/___/ > > > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 11:12:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id A192214E61 for ; Sat, 10 Apr 1999 11:12:17 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA01105; Sat, 10 Apr 1999 14:10:00 -0400 (EDT) Date: Sat, 10 Apr 1999 14:10:00 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Libraries with library dependancies In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, John Polstra wrote: > Brian Feldman wrote: > > > YES! Make the mdXXX symbols all weak, so libmd can be added manually! > > Peter already mentioned why that isn't necessary. I just want to add > a caution to folks out there. Don't go wild with weak symbols. Think > VERY carefully (and get a review) before using them. They should > be treated as an absolute last resort. You can paint yourself into > a corner before you know it, and you won't find out until it's time > to upgrade something and you suddenly realize that none of your old > executables will run any more. > Which is why I do NOT advocate making / shared, but shared libs there would be useful still. > John > --- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong > > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 11:40:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 09FAC14EE0 for ; Sat, 10 Apr 1999 11:40:51 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id LAA42133; Sat, 10 Apr 1999 11:33:43 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904101833.LAA42133@troutmask.apl.washington.edu> Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <19990410182316.G6250@shale.csir.co.za> from Jeremy Lea at "Apr 10, 1999 06:23:16 pm" To: reg@shale.csir.co.za (Jeremy Lea) Date: Sat, 10 Apr 1999 11:33:43 -0700 (PDT) Cc: dcs@newsguy.com (Daniel C. Sobral), scrappy@hub.org (The Hermit Hacker), handy@lambic.physics.montana.edu (Brian Handy), des@flood.ping.uio.no (Dag-Erling Smorgrav), obrien@NUXI.com, current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremy Lea wrote: > Hi, > > On Fri, Apr 09, 1999 at 11:19:21PM +0900, Daniel C. Sobral wrote: > > Right or wrong, you forgot: > > > > 5. BSD tradition. > > > > Case 5 justifies Fortran. > > Me, I'd rather have Fortran as a port. I'd even grudgingly accept > > fortune as a port, as a matter of fact. Our base system is bloated. > > While a lot of widely used programs are only available through > > ports, a lot of obscure and obsolete stuff remains on our tree. They > > are there because of 5. As long as 5 exists, Fortran belongs in the > > tree. If we ever get rid of 5, then it's time to get the knife to > > our tree... Or the axe, if the vikings decide to have the first cut. > > :-) > > Invoking: > > 6. Whoever brings patches wins. > Doesn't apply for getting something *removed* from the tree. I've had *patches* and *ports* for f2c and f77 sitting around for at least 2 months. Search the mailing list. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 11:58:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 698E6150A7 for ; Sat, 10 Apr 1999 11:58:07 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA97690 for current@freebsd.org; Sat, 10 Apr 1999 20:55:54 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904101855.UAA97690@freebsd.dk> Subject: UPDATE6: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Sat, 10 Apr 1999 20:55:54 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sixth update to the new ATA/ATAPI driver: Fixed problems: Promise controllers was not always set up correctly. Parantheses are a good thing, fixed. Some older CDROM's could hang the probe. Proberly wait for the drive to catch its breath after IDENTIFY. Some CD writers fails because they dont support rezero. Rearranged the code to not use rezero. Warnings now that we use EGCS. Fixed. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. Especially the DMA support can hose your disk real bad if anything goes wrong, again you have been warned :) Notebook owners should be carefull that their machines dont suspend as this might cause trouble... But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 12:13:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 5DE0715291 for ; Sat, 10 Apr 1999 12:13:30 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id PAA26955 for current@freebsd.org; Sat, 10 Apr 1999 15:10:52 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904101910.PAA26955@kot.ne.mediaone.net> Subject: Re: DoS from local users (fwd) In-Reply-To: from Brian Feldman at "Apr 10, 1999 02:07:27 pm" To: current@freebsd.org Date: Sat, 10 Apr 1999 15:10:52 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Once again - HOW I can limit CPU usage by *kernel* ? Also, I've just => tried set maxprocesses 5. And it helpless. With 5 processes limit => user was able to slow down P2-450 computer. Switching between windows => in X was VERY slow. Mouse movements was slow down too. => CPU states: 32.3% user, 0.0% nice, 67.2% system, 0.0% interrupt, 0.5% idle =If you want to preempt other tasks, make that user's tasks niced!! Which user? You don't know until it happens... And the mentioned already baseball bat is more effective _after_ the fact. The question is, is it possible to prevent this from happening in the first place, without quering the Human Resources department for each user's mental profile?.. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 12:48:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 694C715292 for ; Sat, 10 Apr 1999 12:48:07 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.0) with SMTP id XAA10803; Sat, 10 Apr 1999 23:45:51 +0400 (MSD) Date: Sat, 10 Apr 1999 23:45:51 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Brian Feldman Cc: freebsd-current@freebsd.org Subject: Re: DoS from local users (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Brian Feldman wrote: > Date: Sat, 10 Apr 1999 14:07:27 -0400 (EDT) > From: Brian Feldman > To: Dmitry Valdov > Cc: freebsd-current@freebsd.org > Subject: Re: DoS from local users (fwd) > > On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > Hi! > > > > Once again - HOW I can limit CPU usage by *kernel* ? > > Also, I've just tried set maxprocesses 5. > > And it helpless. > > With 5 processes limit user was able to slow down P2-450 computer. > > Switching between windows in X was VERY slow. Mouse movements was slow down > > too. > > CPU states: 32.3% user, 0.0% nice, 67.2% system, 0.0% interrupt, 0.5% idle > > > > Please, just try it. > > If you want to preempt other tasks, make that user's tasks niced!! > Have You tried it? Please try. I think that it's a system call problem. When (pipe, exec, or something? I dont' known how it syscall named) is called many times at the same time, kernel starts using all CPU time while performing these syscalls. It's just my opinion. But I see no way to prevent users from overloading system by kernel. (hmmm, if not to limit maxproc to one or two ;-)))) > > > > > > On Sat, 10 Apr 1999, Brian Feldman wrote: > > > > > Date: Sat, 10 Apr 1999 09:29:19 -0400 (EDT) > > > From: Brian Feldman > > > To: Dmitry Valdov > > > Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG, > > > freebsd-questions@FreeBSD.ORG > > > Subject: Re: DoS from local users (fwd) > > > > > > On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > > > > > > > > > > > > > On Sat, 10 Apr 1999, Chris Costello wrote: > > > > > > > > > Date: Sat, 10 Apr 1999 02:05:33 -0500 > > > > > From: Chris Costello > > > > > Reply-To: chris@calldei.com > > > > > To: Dmitry Valdov > > > > > Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG > > > > > Subject: Re: DoS from local users (fwd) > > > > > > > > > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > > > > > You typically want to set a restriction as to how many > > > > > > > processes a user can spawn. This is done by editing > > > > > > > /etc/login.conf and changing the user's login class, see the man > > > > > > > page for 'login.conf'. > > > > > > > > > > > > > > > > > > > I'm about CPU usage, not about many processes. > > > > > > See: > > > > > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > > > > > > idle > > > > > > on any (tested on P2-45) machine. > > > > > > > > > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf > > > > > > And load average can be up to 20-40 :( > > > > > > > > > > > > Please don't redirect me to -questions, it's a kernel problem, not just > > > > > > config. > > > > > > > > > > How is it a kernel problem? It's a forkbomb. It spawns many > > > > > processes. You can also limit CPU usage with login.conf, I > > > > > believe. > > > > > > > > Hmm. How I can limit CPU usage by SYSTEM? See top's output below. > > > > > > > > Dmitry. > > > > > > > > PS. I've just tried it. And I'm right - CPU usage limit can't help. > > > > > > > > > > So? Processes that run a while go down in priority [McKusick95 I believe, THE > > > book] so they are preempted easily. Look in top and see if they're all at > > > the top of the list. I bet they're not! Also, you can set per-user niceness > > > levels, and why are you being so liberal giving a standard LUSER 32 processes? > > > This is a system administration problem. > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ > > > green@unixhelp.org _ __ ___ | _ ) __| \ > > > FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | > > > http://www.freebsd.org _ |___/___/___/ > > > > > > > > > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | > http://www.freebsd.org _ |___/___/___/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 13:14: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id BC3C714E46 for ; Sat, 10 Apr 1999 13:14:02 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA01133; Sat, 10 Apr 1999 13:11:45 -0700 (PDT) (envelope-from dillon) Date: Sat, 10 Apr 1999 13:11:45 -0700 (PDT) From: Matthew Dillon Message-Id: <199904102011.NAA01133@apollo.backplane.com> To: Dmitry Valdov Cc: Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is not possible to prevent a user from hogging the cpu on the system. What you *CAN* do is make it difficult for the user to crash the system by limiting the number of processes he is allowed to run, the maximum data segment size each process is allowed to allocate, and by placing quotas on disk partitions he has write access to. This allows a sysop to get on the system and blow the idiot user away without having to reboot. cpu utilization has nothing to do with system cpu verses user cpu. cpu is cpu. One process can hog the cpu, it doesn't really matter whether it is supervisor or user mode cpu. The system will attempt to balance cpu utilization when several processes need cpu. The worst a user can do cpu-wise is to start N cpu-bound processes. Starting N cpu-bound processes will drive the load up on the machine, but as long as N is limited it will not prevent a sysop from getting in there and taking out the user. You don't give user accounts away to people who you think might try to crash the system, so resource limits are mostly there to prevent users making stupid mistakes from taking the system down with them. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 13:32:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 2A28314C0D for ; Sat, 10 Apr 1999 13:32:32 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id NAA08796; Sat, 10 Apr 1999 13:30:02 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904102030.NAA08796@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-reply-to: Your message of "Sat, 10 Apr 1999 13:11:45 PDT." <199904102011.NAA01133@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Apr 1999 13:30:02 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It should be possible to prevent a user from hogging a system if the system's naive scheduler is improved. Amancio > It is not possible to prevent a user from hogging the cpu on the system. > What you *CAN* do is make it difficult for the user to crash the system > by limiting the number of processes he is allowed to run, the maximum > data segment size each process is allowed to allocate, and by placing > quotas on disk partitions he has write access to. This allows a > sysop to get on the system and blow the idiot user away without having > to reboot. > > cpu utilization has nothing to do with system cpu verses user cpu. cpu > is cpu. One process can hog the cpu, it doesn't really matter whether > it is supervisor or user mode cpu. The system will attempt to balance > cpu utilization when several processes need cpu. The worst a user can > do cpu-wise is to start N cpu-bound processes. > > Starting N cpu-bound processes will drive the load up on the machine, but > as long as N is limited it will not prevent a sysop from getting in there > and taking out the user. > > You don't give user accounts away to people who you think might > try to crash the system, so resource limits are mostly there to prevent > users making stupid mistakes from taking the system down with them. > > -Matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 13:35:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 64F3714C0D for ; Sat, 10 Apr 1999 13:35:36 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA07337; Sat, 10 Apr 1999 14:30:56 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA09814; Sat, 10 Apr 1999 14:30:54 -0600 Date: Sat, 10 Apr 1999 14:30:54 -0600 Message-Id: <199904102030.OAA09814@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Kargl Cc: reg@shale.csir.co.za (Jeremy Lea), dcs@newsguy.com (Daniel C. Sobral), scrappy@hub.org (The Hermit Hacker), handy@lambic.physics.montana.edu (Brian Handy), des@flood.ping.uio.no (Dag-Erling Smorgrav), obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <199904101833.LAA42133@troutmask.apl.washington.edu> References: <19990410182316.G6250@shale.csir.co.za> <199904101833.LAA42133@troutmask.apl.washington.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, Apr 09, 1999 at 11:19:21PM +0900, Daniel C. Sobral wrote: > > > Right or wrong, you forgot: > > > > > > 5. BSD tradition. > > > > > > Case 5 justifies Fortran. > > > Me, I'd rather have Fortran as a port. I'd even grudgingly accept > > > fortune as a port, as a matter of fact. Our base system is bloated. > > > While a lot of widely used programs are only available through > > > ports, a lot of obscure and obsolete stuff remains on our tree. They > > > are there because of 5. As long as 5 exists, Fortran belongs in the > > > tree. If we ever get rid of 5, then it's time to get the knife to > > > our tree... Or the axe, if the vikings decide to have the first cut. > > > :-) > > > > Invoking: > > > > 6. Whoever brings patches wins. > > > > Doesn't apply for getting something *removed* from the tree. > I've had *patches* and *ports* for f2c and f77 sitting around > for at least 2 months. Search the mailing list. I offered to do the commit work, but Jordan posted that removing Fortran from the base system wasn't something he considered acceptable, and I didn't feel like fighting him. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 13:39:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2CD11153A9 for ; Sat, 10 Apr 1999 13:39:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA01262; Sat, 10 Apr 1999 13:37:06 -0700 (PDT) (envelope-from dillon) Date: Sat, 10 Apr 1999 13:37:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199904102037.NAA01262@apollo.backplane.com> To: Amancio Hasty Cc: Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: <199904102030.NAA08796@rah.star-gate.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :It should be possible to prevent a user from hogging a system if the system's :naive scheduler is improved. : : Amancio No, it isn't. For a very simple reason: The resources users need to do real work are very similar to the resources users need to hog the system. Saying that the system should somehow be able to magically make the distinction between the two is a pipedream. It takes a human to make the distinction. Short of restricting the resources you give to users to the point where they can't even start a mail or news client, there is just no way to prevent said users from loading down the machine if they choose to. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 13:51:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (Postfix) with SMTP id 5B3C815046 for ; Sat, 10 Apr 1999 13:51:07 -0700 (PDT) (envelope-from herbelot@cybercable.fr) Received: (qmail 6453 invoked from network); 10 Apr 1999 22:48:47 +0200 Received: from d225.paris-21.cybercable.fr (HELO cybercable.fr) (212.198.21.225) by bouvreuil.cybercable.fr with SMTP; 10 Apr 1999 20:48:47 -0000 Message-ID: <370FB930.6EE6A95C@cybercable.fr> Date: Sat, 10 Apr 1999 22:48:48 +0200 From: Thierry Herbelot Organization: Les barbus =?iso-8859-1?Q?associ=E9s?=, Paris, France X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: <199904102030.NAA08796@rah.star-gate.com> <199904102037.NAA01262@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Let's remember a motto of J. Pournelle of the late Byte : one User, more than one CPU (let people hog their workstation as much as they want ...) And another good resolution : no shell accounts for normal users on sensitive servers (no lusers which could want to DoS the servers allowed) Every base covered ? Cheers TfH Matthew Dillon wrote: > > : > :It should be possible to prevent a user from hogging a system if the system's > :naive scheduler is improved. > : > : Amancio > > No, it isn't. For a very simple reason: The resources users need to do > real work are very similar to the resources users need to hog the system. > > Saying that the system should somehow be able to magically make the > distinction between the two is a pipedream. It takes a human to make > the distinction. > > Short of restricting the resources you give to users to the point where > they can't even start a mail or news client, there is just no way to > prevent said users from loading down the machine if they choose to. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 13:53:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (Postfix) with ESMTP id AEA7B1537F for ; Sat, 10 Apr 1999 13:53:47 -0700 (PDT) (envelope-from pantzer@obie.ludd.luth.se) Received: from obie.ludd.luth.se (pantzer@obie.ludd.luth.se [130.240.16.24]) by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id WAA07790; Sat, 10 Apr 1999 22:51:16 +0200 Message-Id: <199904102051.WAA07790@zed.ludd.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Amancio Hasty , Dmitry Valdov , Brian Feldman , freebsd-current@freebsd.org Subject: Re: DoS from local users (fwd) In-reply-to: Your message of "Sat, 10 Apr 1999 13:37:06 PDT." <199904102037.NAA01262@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Apr 1999 22:51:14 +0200 From: Mattias Pantzare Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : > :It should be possible to prevent a user from hogging a system if the system's > :naive scheduler is improved. > : > : Amancio > > No, it isn't. For a very simple reason: The resources users need to do > real work are very similar to the resources users need to hog the system. That has nothing to do with it. Not for cpu usage. If you have two users that are using all the CPU they can they ought to get 50% of the CPU each. Even if one of the users have 1 process and the other have 100 processes. Sun has a product for this, Solaris Resource Manager. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14: 0: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 97AA115404 for ; Sat, 10 Apr 1999 13:59:49 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA01570; Sat, 10 Apr 1999 13:57:32 -0700 (PDT) (envelope-from dillon) Date: Sat, 10 Apr 1999 13:57:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199904102057.NAA01570@apollo.backplane.com> To: Mattias Pantzare Cc: Amancio Hasty , Dmitry Valdov , Brian Feldman , freebsd-current@freebsd.org Subject: Re: DoS from local users (fwd) References: <199904102051.WAA07790@zed.ludd.luth.se> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> No, it isn't. For a very simple reason: The resources users need to do :> real work are very similar to the resources users need to hog the system. : :That has nothing to do with it. Not for cpu usage. If you have two users that :are using all the CPU they can they ought to get 50% of the CPU each. Even if :one of the users have 1 process and the other have 100 processes. : :Sun has a product for this, Solaris Resource Manager. ... and if one user is *supposed* to be running all those processes, then what? Oh, let me guess: Now you are supposed to tune each user's account independantly. For a system with general user accounts, this is a burden on the sysop. If one can't control one's users, one has no business managing them. The last thing FreeBSD needs is some overly complex, sophisticated scheduler designed to help bozo sysops stay on their feet. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14: 0:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 0188C14DF7 for ; Sat, 10 Apr 1999 14:00:19 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id PAA27724; Sat, 10 Apr 1999 15:57:27 -0500 (CDT) From: Kevin Day Message-Id: <199904102057.PAA27724@home.dragondata.com> Subject: Re: DoS from local users (fwd) In-Reply-To: <199904102037.NAA01262@apollo.backplane.com> from Matthew Dillon at "Apr 10, 1999 1:37: 6 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 10 Apr 1999 15:57:26 -0500 (CDT) Cc: hasty@rah.star-gate.com, dv@dv.ru, green@unixhelp.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : > :It should be possible to prevent a user from hogging a system if the system's > :naive scheduler is improved. > : > : Amancio > > No, it isn't. For a very simple reason: The resources users need to do > real work are very similar to the resources users need to hog the system. > > Saying that the system should somehow be able to magically make the > distinction between the two is a pipedream. It takes a human to make > the distinction. > > Short of restricting the resources you give to users to the point where > they can't even start a mail or news client, there is just no way to > prevent said users from loading down the machine if they choose to. > > -Matt > > On the shell servers I run, we've got 200-300 users running tasks. Occasionally, through intent or misconfiguration, a user either forkbombs, or gets a large number of processes running sucking lots of cpu. I'd like to see an option that makes all the processes run by one uid have the same weight as one process another uid is running. i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid 1002 starts up one process. Uid 1002's process gets 50% cpu, and uid 1001's 40 processes get 50% cpu shared between them. This way, one errant user can't have as significant of an impact. Is this plausable? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14:11: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 11E6314DFA for ; Sat, 10 Apr 1999 14:11:04 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA01678; Sat, 10 Apr 1999 14:08:41 -0700 (PDT) (envelope-from dillon) Date: Sat, 10 Apr 1999 14:08:41 -0700 (PDT) From: Matthew Dillon Message-Id: <199904102108.OAA01678@apollo.backplane.com> To: Kevin Day Cc: hasty@rah.star-gate.com, dv@dv.ru, green@unixhelp.org, freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: <199904102057.PAA27724@home.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On the shell servers I run, we've got 200-300 users running tasks. :Occasionally, through intent or misconfiguration, a user either forkbombs, :or gets a large number of processes running sucking lots of cpu. : :I'd like to see an option that makes all the processes run by one uid have :the same weight as one process another uid is running. : :i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid :1002 starts up one process. Uid 1002's process gets 50% cpu, and uid 1001's :40 processes get 50% cpu shared between them. : :This way, one errant user can't have as significant of an impact. : :Is this plausable? : :Kevin Plausable, yes. Useful: probably not as useful as you might think. I wouldn't even consider doing something like that for BEST, it could lead to cascade failures. For example, if a user is running procmail or cron on a relatively loaded system, the user's share of the cpu relative to other users might not be sufficient to handle the user's medium term mail and/or job load. If there are a few hundred users logged in, this could rapidly devolve into a cascade failure which fills the system's process table. This in turn can lockup sendmail's waiting to lock the user's mailbox which in turn can lead to a cascade failure with the root-run sendmails. Sometimes, the most noble of purposes can make a machine less stable in inobvious ways. In the above example, limitations on a user process might lead to a backup of root-run services. A user-run CGI is another example. Say you have a web server which runs CGI's under a user id. If the web site is loaded down and the user happens to run a log processing script, execs of the user's CGIs might slow down due to the load balancing 'feature'. The web server may now wind up in the situation where it is forking CGIs faster then it can retire them. Leading to another cascade failure. In general, it is best to treat process scheduling without taking into account other processes run by the same user. If a user misbehaves, the best solution is to stomp on him until he does behave, not try to shove the misbehavior under the run by making the system 'control' the user's resources. If you do not actively control the behavior of your users all you will accomplish is to have a large number of them misbehaving continuously rather then just one or two. The result is going to be the same: A loaded down server and lots of complaints. users, -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14:14:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (Postfix) with ESMTP id 2986F14C94 for ; Sat, 10 Apr 1999 14:14:25 -0700 (PDT) (envelope-from pantzer@obie.ludd.luth.se) Received: from obie.ludd.luth.se (pantzer@obie.ludd.luth.se [130.240.16.24]) by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id XAA08294; Sat, 10 Apr 1999 23:12:09 +0200 Message-Id: <199904102112.XAA08294@zed.ludd.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: DoS from local users (fwd) In-reply-to: Your message of "Sat, 10 Apr 1999 13:57:32 PDT." <199904102057.NAA01570@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 10 Apr 1999 23:12:08 +0200 From: Mattias Pantzare Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :That has nothing to do with it. Not for cpu usage. If you have two use= rs that> :are using all the CPU they can they ought to get 50% of the CPU= each. Even if> :one of the users have 1 process and the other have 100 p= rocesses. > : > :Sun has a product for this, Solaris Resource Manager. > = > ... and if one user is *supposed* to be running all those processes= , then > what? Oh, let me guess: Now you are supposed to tune each user's = account > independantly. For a system with general user accounts, this is a = burden > on the sysop. ? Then that user continue to run all those processes, but won't take a bi= gger = share of the resources than any other user. This is not diffrent from one= = process not using all the CPU when there are other processes that need CP= U. > If one can't control one's users, one has no business managing them= . The > last thing FreeBSD needs is some overly complex, sophisticated sche= duler > designed to help bozo sysops stay on their feet. You can't manage users today as you don't have anyting good to control th= em = with. We have that for processes, so you can manage processes. This helps for runaway daemons and things like that to. (The Web server g= ets = 75% and the rest to the sql server for example). Is it worth the trouble to implement? Maybe not. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14:15:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id CCFC414C94; Sat, 10 Apr 1999 14:15:00 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id BAA32060; Sun, 11 Apr 1999 01:03:35 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id BAA01088; Sun, 11 Apr 1999 01:02:29 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199904102102.BAA01088@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Alex Zepeda Cc: adrian@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: msdosfs problems? In-reply-to: Your message of "Fri, 09 Apr 1999 20:52:10 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Apr 1999 01:02:29 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > panic: vm_page_bits: illegal base/size 4096/2048 The panic is hopefully just fixed in vnode_pager.c rev.1.107. I didn't quite understand if you have other msdosfs problems. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14:19:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 18518153B6 for ; Sat, 10 Apr 1999 14:19:47 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id RAA97903; Sat, 10 Apr 1999 17:14:59 -0400 (EDT) Date: Sat, 10 Apr 1999 17:14:58 -0400 (EDT) From: Chuck Robey To: Matthew Dillon Cc: Kevin Day , hasty@rah.star-gate.com, dv@dv.ru, green@unixhelp.org, freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-Reply-To: <199904102108.OAA01678@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Matthew Dillon wrote: > :Kevin > > Plausable, yes. Useful: probably not as useful as you might think. I > wouldn't even consider doing something like that for BEST, it could lead > to cascade failures. > > For example, if a user is running procmail or cron on a relatively loaded > system, the user's share of the cpu relative to other users might not be > sufficient to handle the user's medium term mail and/or job load. If there > are a few hundred users logged in, this could rapidly devolve into a > cascade failure which fills the system's process table. This in turn can > lockup sendmail's waiting to lock the user's mailbox which in turn can > lead to a cascade failure with the root-run sendmails. > > Sometimes, the most noble of purposes can make a machine less stable in > inobvious ways. In the above example, limitations on a user process might > lead to a backup of root-run services. > > A user-run CGI is another example. Say you have a web server which runs > CGI's under a user id. If the web site is loaded down and the user happens > to run a log processing script, execs of the user's CGIs might slow down > due to the load balancing 'feature'. The web server may now wind up in the > situation where it is forking CGIs faster then it can retire them. Leading > to another cascade failure. > > In general, it is best to treat process scheduling without taking into > account other processes run by the same user. > > If a user misbehaves, the best solution is to stomp on him until he does > behave, not try to shove the misbehavior under the run by making the system > 'control' the user's resources. If you do not actively control the > behavior of your users all you will accomplish is to have a large number of > them misbehaving continuously rather then just one or two. The result > is going to be the same: A loaded down server and lots of complaints. > users, Matt, I agree with what you're saying, but what would you think about something that would take a look at the total cpu time that a process group had accumulated in the previous 120 seconds. That would be, I think, plenty long enough to catch most inadvertent things, and just kill the process leader. You could allow some users to have very high limits, but an attacker, someone purposely bringing the machine down (a hacker) would find only 2 minute capabilities. Do you think something like this would still contribute to the cascade failure scenarios? > > -Matt > Matthew Dillon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14:23:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 142AF153B6 for ; Sat, 10 Apr 1999 14:23:12 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id OAA42808; Sat, 10 Apr 1999 14:16:15 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904102116.OAA42808@troutmask.apl.washington.edu> Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <199904102030.OAA09814@mt.sri.com> from Nate Williams at "Apr 10, 1999 02:30:54 pm" To: nate@mt.sri.com (Nate Williams) Date: Sat, 10 Apr 1999 14:16:15 -0700 (PDT) Cc: reg@shale.csir.co.za (Jeremy Lea), dcs@newsguy.com (Daniel C. Sobral), scrappy@hub.org (The Hermit Hacker), handy@lambic.physics.montana.edu (Brian Handy), des@flood.ping.uio.no (Dag-Erling Smorgrav), obrien@NUXI.com, current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremy wrote: > > > 6. Whoever brings patches wins. > > > Steve wrote: > > > > Doesn't apply for getting something *removed* from the tree. > > I've had *patches* and *ports* for f2c and f77 sitting around > > for at least 2 months. Search the mailing list. Nate's comment: > I offered to do the commit work, but Jordan posted that removing Fortran > from the base system wasn't something he considered acceptable, and I > didn't feel like fighting him. Yes, I know you offered, and I did not mean to imply any negative critism. My comments were meant to convey that it takes more than having patches. Once something gets into the base tree, it suddenly gains a large amount of inertia to stay. If I recall, Jordan's position was to maintain the status quo until some decision on importing egcs was made. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14:31:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 53B3614D1E for ; Sat, 10 Apr 1999 14:31:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA01853; Sat, 10 Apr 1999 14:29:38 -0700 (PDT) (envelope-from dillon) Date: Sat, 10 Apr 1999 14:29:38 -0700 (PDT) From: Matthew Dillon Message-Id: <199904102129.OAA01853@apollo.backplane.com> To: Chuck Robey Cc: Kevin Day , hasty@rah.star-gate.com, dv@dv.ru, green@unixhelp.org, freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matt, I agree with what you're saying, but what would you think about :something that would take a look at the total cpu time that a process :group had accumulated in the previous 120 seconds. That would be, I :think, plenty long enough to catch most inadvertent things, and just :kill the process leader. You could allow some users to have very high :limits, but an attacker, someone purposely bringing the machine down (a :hacker) would find only 2 minute capabilities. : :Do you think something like this would still contribute to the cascade :failure scenarios? This would contribute to the number of complaints you receive from users about 'things getting killed at odd times'. Here you are assuming that users only run short-term cpu-intensive processes. This is, in fact, not true. For example, many BEST users run log processing scripts in the wee hours of the morning. These scripts are often cpu-intensive and can take as much as half an hour of cpu time before completing. While I instituted resource limits on BEST users, I had to make them relatively generous because BEST users often run things legally that eat a lot of resources. File descriptors ( log processing into breakdown files ), processes ( screen sessions ), memory ( tin, emacs ), cpu ( log processing, mailing list run, procmail ). Also, we do not want to penalize users when their accounts or web pages get attacked. If a user's web page is attacked, dozens of CGI's a second might be run on that user's behalf. The machine needs to be able to grin and brunt it while we go after the source of the attack to prevent the attacker from gaining his goal of disrupting that user. Which means: Even if you had such a mechanism, you would have to set *very* generous limits in order to avoid having it accidently kill a user's legitimate work. As I said, it really takes a human to figure out the difference between a mistake, a hack, or a valid operation. -Matt Matthew Dillon :----------------------------+----------------------------------------------- :Chuck Robey | Interests include any kind of voice or data :chuckr@picnic.mat.net | communications topic, C programming, and Unix. :213 Lakeside Drive Apt T-1 | :Greenbelt, MD 20770 | I run picnic (FreeBSD-current) :(301) 220-2114 | and jaunt (Solaris7). :----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14:51:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (spain-3.ppp.hooked.net [206.169.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 7579914D22; Sat, 10 Apr 1999 14:51:20 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id OAA57904; Sat, 10 Apr 1999 14:48:46 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sat, 10 Apr 1999 14:48:45 -0700 (PDT) From: Alex Zepeda To: Dmitrij Tejblum Cc: adrian@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: msdosfs problems? In-Reply-To: <199904102102.BAA01088@tejblum.dnttm.rssi.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Dmitrij Tejblum wrote: > Alex Zepeda wrote: > > panic: vm_page_bits: illegal base/size 4096/2048 > > The panic is hopefully just fixed in vnode_pager.c rev.1.107. I didn't > quite understand if you have other msdosfs problems. I'll try it out and see what happens. The other problems appear to be mmap related. If I change the -DREAD_MMAP and -DUSE_MMAP to -U's when compiling mpg123, it plays fine off the FAT partition (assuming the old mpg123 hasn't touched it yet). Rather odd.. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 14:56:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (unknown [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B4F3014D22; Sat, 10 Apr 1999 14:56:17 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id OAA35950; Sat, 10 Apr 1999 14:54:04 -0700 (PDT) (envelope-from obrien) Message-ID: <19990410145404.A35939@nuxi.com> Date: Sat, 10 Apr 1999 14:54:04 -0700 From: "David O'Brien" To: current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. Reply-To: obrien@FreeBSD.ORG References: <19990408165056.D20453@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990408165056.D20453@nuxi.com>; from David O'Brien on Thu, Apr 08, 1999 at 04:50:56PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Unless I get more feedback, I will add g77 to the base system this > weekend. I should have posted this yesterday... but I had hoped to just get it done. There has been suffient YES response to keep Fortran in the base system. As someone posted to the point: g77 will add very little additional size and compile time over the bits of EGCS we are already using. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 15:13: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 7874B14CC6 for ; Sat, 10 Apr 1999 15:12:55 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.0) with SMTP id CAA22567; Sun, 11 Apr 1999 02:10:28 +0400 (MSD) Date: Sun, 11 Apr 1999 02:10:27 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Matthew Dillon Cc: Kevin Day , hasty@rah.star-gate.com, green@unixhelp.org, freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-Reply-To: <199904102108.OAA01678@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Matthew Dillon wrote: > Date: Sat, 10 Apr 1999 14:08:41 -0700 (PDT) > From: Matthew Dillon > To: Kevin Day > Cc: hasty@rah.star-gate.com, dv@dv.ru, green@unixhelp.org, > freebsd-current@FreeBSD.ORG > Subject: Re: DoS from local users (fwd) > > A user-run CGI is another example. Say you have a web server which runs > CGI's under a user id. If the web site is loaded down and the user happens > to run a log processing script, execs of the user's CGIs might slow down > due to the load balancing 'feature'. The web server may now wind up in the > situation where it is forking CGIs faster then it can retire them. Leading > to another cascade failure. > Make it configurable then... Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 17:21: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 5871E1533F for ; Sat, 10 Apr 1999 17:20:23 -0700 (PDT) (envelope-from dhesi@rahul.net) Received: from q.bolero.rahul.net (bolero.rahul.net) by bolero-x.rahul.net with SMTP id AA21927 (5.67b8/IDA-1.5 for ); Sat, 10 Apr 1999 17:18:10 -0700 Message-Id: <199904110018.AA21927@bolero-x.rahul.net> Received: (qmail 21921 invoked from network); 11 Apr 1999 00:18:09 -0000 Received: from waltz.rahul.net (192.160.13.9) by bolero.rahul.net with SMTP; 11 Apr 1999 00:18:09 -0000 To: freebsd-current@freebsd.org Subject: showing full host names in output from who/finger/last Date: Sat, 10 Apr 1999 17:18:08 -0700 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For some years I have been using patched utilities under SunOS to show full host names in the output from the 'who', 'finger', and 'last' commands. (Traditional UNIXes truncate host names to about 16 characters.) I have been thinking of patching FreeBSD programs to do the same, but since I have been updating my source tree often, it will be a bit painful to maintain my changes through the updates. So I will do it only if the FreeBSD developers would be willing to incorporate my changes into the official FreeBSD source tree. Below is what I would do -- tell me if it could be make a part of FreeBSD. - Update all programs that write to utmp and wtmp to check the host name length, and if it's too long, insert the IP address instead - Update all of the above programs, if they accept a host name on the command line, to also accept an additional argument that specifies the IP address. - Update all programs that invoke the above programs and supply a host name to also supply the IP address. - Update all programs that look up wtmp and utmp such that, if they find an IP address, they do a double-reverse DNS resolution (IP address -> fqdn -> IP address) and, if successful and consistent, display the host name instead of the IP address. The user may if he wishes supply a command-line argument to suppress the reverse resolution and cause the IP address to be displayed directly. For example, rlogind might invoke /usr/bin/login as: /usr/bin/login -h 98.portland-23-24rs.or.dial-access.att.net -i 12.73.137.98 /usr/bin/login notices that the host name is too long, inserts 12.73.137.98 into utmp and wtmp. If no -i argument is available, /usr/bin/login would do a forward DNS resolution of the host name to get the IP address. Below are samples from the 'last' and 'finger' commands with only the really long host names included and some information x'd out to protect user privacy. (Obviously comumnar alignment doesn't work as well for very long host names, but only a small fraction are that long. The rest will display normally in aligned columns.) == output from 'finger == Login Name Idle When Where xxxxxx xxxxxxxxxxxxxx 7 Apr 9 13:14 kaibab.redbacknetworks.com xxx xxxxxxxxxxxxxxx Apr 10 16:37 dyn164.rahul.net xxxxxxxx xxxxxxxxxxxx 8 Apr 10 16:48 c166.ppp.tsoft.com xxxxx xxxxxxxxxxx Apr 9 23:35 \ cxxxxxxx-x.xxxxx.occa.home.com xxxxx xxxxxxxxxxxx * 10 Apr 10 16:44 01-025.006.popsite.net == output from 'last' == xxx s1 98.portland-23-24rs.or.dial-access.att.net Sat Apr 10 16:50 - 16:50 (00:00) xxxxxx rd oak-hiper1b-145-145.dialup.slip.net Sat Apr 10 16:48 - 16:51 (00:03) xxxx p6 netcom14.netcom.com Sat Apr 10 15:36 - 15:39 (00:03) xxxxx s2 adsl-xxx-xxx-xxx-10.dsl.snfc21.pacbell.net Sat Apr 10 13:51 - 13:52 (00:00) xxxxxxxx sb tnt9-xxx-xxx-17-189.dialup.HiWAAY.net Sat Apr 10 12:54 - 14:54 (02:00) xxxxxx s2 oak-hiper1a-15-79.dialup.slip.net Sat Apr 10 12:37 - 12:40 (00:02) xxxx r2 dnai-207-181-255-82.dialup.dnai.com Sat Apr 10 11:41 - 13:58 (02:17) xxxxxxx q8 sdn-ar-001casfraP195.dialsprint.net Sat Apr 10 08:28 - 13:30 (05:01) == END == To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 20:38: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 7813014CC1 for ; Sat, 10 Apr 1999 20:38:05 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id UAA10870; Sat, 10 Apr 1999 20:35:37 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904110335.UAA10870@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-reply-to: Your message of "Sat, 10 Apr 1999 13:37:06 PDT." <199904102037.NAA01262@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Apr 1999 20:35:37 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess any sufficiently advance science is indeed consider magic by some. Amancio > > : > :It should be possible to prevent a user from hogging a system if the system's > :naive scheduler is improved. > : > : Amancio > > No, it isn't. For a very simple reason: The resources users need to do > real work are very similar to the resources users need to hog the system. > > Saying that the system should somehow be able to magically make the > distinction between the two is a pipedream. It takes a human to make > the distinction. > > Short of restricting the resources you give to users to the point where > they can't even start a mail or news client, there is just no way to > prevent said users from loading down the machine if they choose to. > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 20:57:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 4884C14BFC for ; Sat, 10 Apr 1999 20:57:13 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id XAA28481; Sat, 10 Apr 1999 23:54:23 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904110354.XAA28481@kot.ne.mediaone.net> Subject: Re: DoS from local users (fwd) In-Reply-To: <199904102129.OAA01853@apollo.backplane.com> from Matthew Dillon at "Apr 10, 1999 02:29:38 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 10 Apr 1999 23:54:17 -0400 (EDT) Cc: current@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Sat, 10 Apr 1999 21:28:49 -0700 (PDT) (envelope-from tr49986@rcc.on.ca) Received: from rcc.on.ca (24.66.20.80.on.wave.home.com [24.66.20.80]) by speed.rcc.on.ca (8.6.12/8.6.9) with ESMTP id BAA26445 for ; Sun, 11 Apr 1999 01:45:59 -0400 Message-ID: <37106B7D.50B2F49D@rcc.on.ca> Date: Sun, 11 Apr 1999 05:29:34 -0400 From: Rod Taylor X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: DoS from local users (fwd) References: <199904110354.XAA28481@kot.ne.mediaone.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > What about a new login-class capability specifying the maximum > percentage of CPU time a class of users can utilize? With standard > class having 90% (or 95%)? The machine would appear (to most of > the users) as if it had 10% slower CPU, with the remaining usable > by the root-class. This way, if the CPU consumption by system is > 30%, the most CPU time the standard users can get is 60%. > > Trusted users can be placed into a different class, of course. > > Plausible? > I like this, but the problem with that fork bomb program still exists. It was afterall system cpu that was doing all the work, not the users cpu. I can however see how this could be useful for even myself. People who want to run eggdrops can have 40% cpu max on my shell server ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 22:12:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from chen.ml.org (luoqi.watermarkgroup.com [207.202.73.170]) by hub.freebsd.org (Postfix) with ESMTP id 44E7014FC4 for ; Sat, 10 Apr 1999 22:12:15 -0700 (PDT) (envelope-from luoqi@chen.ml.org) Received: (from luoqi@localhost) by chen.ml.org (8.9.3/8.9.3) id BAA07448 for current@freebsd.org; Sun, 11 Apr 1999 01:10:01 -0400 (EDT) (envelope-from luoqi) Date: Sun, 11 Apr 1999 01:10:01 -0400 (EDT) From: Luoqi Chen Message-Id: <199904110510.BAA07448@chen.ml.org> To: current@freebsd.org Subject: thread-safe libgcc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For threaded applications to work correctly, we need a thread-safe version of libgcc. It is straight forward to build: define _PTHREADS in CFLAGS. We can have both versions just like libc and libc_r, and use the thread-safe version when linking threaded applications. If no one objects, I will add it to our tree and make necessary changes to gcc to use it. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 22:42:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.lig.bellsouth.net (mail1.lig.bellsouth.net [205.152.0.55]) by hub.freebsd.org (Postfix) with ESMTP id DD0D4153FC; Sat, 10 Apr 1999 22:42:50 -0700 (PDT) (envelope-from gljohns@bellsouth.net) Received: from gforce.johnson.home (host-209-214-148-170.msy.bellsouth.net [209.214.148.170]) by mail1.lig.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id BAA18033; Sun, 11 Apr 1999 01:40:13 -0400 (EDT) Received: from gforce.johnson.home (localhost.johnson.home [127.0.0.1]) by gforce.johnson.home (8.9.3/8.9.3) with SMTP id AAA64761; Sun, 11 Apr 1999 00:40:23 -0500 (CDT) (envelope-from gljohns@bellsouth.net) From: gljohns@bellsouth.net Date: Thu, 8 Apr 1999 20:12:20 -0500 To: "David O'Brien" Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: ATTENTION PLEASE: g77 in base system. Message-ID: <19990408201220.A26477@gforce.johnson.home> References: <19990408165056.D20453@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990408165056.D20453@nuxi.com>; from David O'Brien on Thu, Apr 08, 1999 at 04:50:56PM -0700 Lines: 18 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 08, 1999 at 04:50:56PM -0700, David O'Brien wrote: > I've only heard back from 4 folks about adding EGCS's g77 to the base > system -- all 4 said "yes". Unless I get more feedback, I will add g77 > to the base system this weekend. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) David, First off, great job on the egcs import. Maybe you have already counted me among the four, but if not, add me to the list. I would love to see g77 in the base system. Thanks. -- Glenn Johnson gljohns@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 22:42:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.lig.bellsouth.net (mail1.lig.bellsouth.net [205.152.0.55]) by hub.freebsd.org (Postfix) with ESMTP id 8497E15428 for ; Sat, 10 Apr 1999 22:42:51 -0700 (PDT) (envelope-from gljohns@bellsouth.net) Received: from gforce.johnson.home (host-209-214-148-170.msy.bellsouth.net [209.214.148.170]) by mail1.lig.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id BAA18034; Sun, 11 Apr 1999 01:40:13 -0400 (EDT) Received: from gforce.johnson.home (localhost.johnson.home [127.0.0.1]) by gforce.johnson.home (8.9.3/8.9.3) with SMTP id AAA64743; Sun, 11 Apr 1999 00:40:18 -0500 (CDT) (envelope-from gljohns@bellsouth.net) From: gljohns@bellsouth.net Date: Sun, 4 Apr 1999 22:30:01 -0500 To: "David O'Brien" Cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: egcs Message-ID: <19990404223001.A449@gforce.johnson.home> References: <199904042246.PAA00499@freefall.freebsd.org> <19990404160228.A22669@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990404160228.A22669@dragon.nuxi.com>; from David O'Brien on Sun, Apr 04, 1999 at 04:02:28PM -0700 Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 04, 1999 at 04:02:28PM -0700, David O'Brien wrote: > > what's the name of the system compiler going to be, egcs or gcc, or cc? > > And the C++ one? > > No change in names. cc/gcc and c++/g++/CC > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) What will become of f77 which is in "src/gnu/usr.bin/cc/f77"? This seems to be a good time to decide what will happen with Fortran in the base FreeBSD system. Thanks. -- Glenn Johnson gljohns@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 10 23:57:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id EBBDF14BDC for ; Sat, 10 Apr 1999 23:57:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA03428; Sat, 10 Apr 1999 23:54:57 -0700 (PDT) (envelope-from dillon) Date: Sat, 10 Apr 1999 23:54:57 -0700 (PDT) From: Matthew Dillon Message-Id: <199904110654.XAA03428@apollo.backplane.com> To: Rahul Dhesi Cc: freebsd-current@FreeBSD.ORG Subject: Re: showing full host names in output from who/finger/last References: <199904110018.AA21927@bolero-x.rahul.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :For some years I have been using patched utilities under SunOS to show :full host names in the output from the 'who', 'finger', and 'last' :commands. (Traditional UNIXes truncate host names to about 16 :characters.) : :I have been thinking of patching FreeBSD programs to do the same, but :since I have been updating my source tree often, it will be a bit :painful to maintain my changes through the updates. So I will do it :only if the FreeBSD developers would be willing to incorporate my :changes into the official FreeBSD source tree. Below is what I would :do -- tell me if it could be make a part of FreeBSD. : :- Update all programs that write to utmp and wtmp to check the host name : length, and if it's too long, insert the IP address instead :- Update all of the above programs, if they accept a host name on the : command line, to also accept an additional argument that specifies : the IP address. :- Update all programs that invoke the above programs and supply a : host name to also supply the IP address. :- Update all programs that look up wtmp and utmp such that, if they find : an IP address, they do a double-reverse DNS resolution (IP address -> : fqdn -> IP address) and, if successful and consistent, display the : host name instead of the IP address. The user may if he wishes supply : a command-line argument to suppress the reverse resolution and cause : the IP address to be displayed directly. This sounds just dandy. Note that 'w' already does a reverse lookup, but not a double-reverse. For some programs, like 'last', it is not convenient to do the DNS lookup by default - in this case you would want to supply an option to 'last' to make it do the lookups. The reason you do not want to do it by default with 'last' is that wtmp can be huge and many people run 'last' output through greps from cron and expect it to not take forever. As long as we don't mess with the size of the utmp or wtmp structure, which by the above I believe you mean to say that we don't... then I'm all for it! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 0:11:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [206.154.101.226]) by hub.freebsd.org (Postfix) with ESMTP id B0F9F14F4A for ; Sun, 11 Apr 1999 00:11:39 -0700 (PDT) (envelope-from staylor@mrynet.com) Received: (from staylor@localhost) by mrynet.com (8.9.3/8.9.3) id AAA18816 for freebsd-current@freebsd.org; Sun, 11 Apr 1999 00:09:34 -0700 (PDT) (envelope-from staylor) Message-Id: <199904110709.AAA18816@mrynet.com> From: staylor@mrynet.com (S. Akmentins-Teilors) Date: Sun, 11 Apr 1999 00:09:34 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: WORLD fails at rpcsvc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've repeatedly cleared obj, clobbered, and whatnot. This has been a problem here for the last two days. Last cvsup was midnight PST on 11 Apr. ===> rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: Internal compiler error in function main *** Error code 33 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 1:21:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id A334614D98 for ; Sun, 11 Apr 1999 01:21:46 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.109]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA7C7; Sun, 11 Apr 1999 10:19:26 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id KAA54170; Sun, 11 Apr 1999 10:19:17 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904110709.AAA18816@mrynet.com> Date: Sun, 11 Apr 1999 10:19:16 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: (S. Akmentins-Teilors) Subject: RE: WORLD fails at rpcsvc Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Apr-99 S. Akmentins-Teilors wrote: > I've repeatedly cleared obj, clobbered, and whatnot. This has been a > problem > here for the last two days. > Last cvsup was midnight PST on 11 Apr. > > ===> rpcsvc > rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h > /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1882: > Internal compiler error in function main > *** Error code 33 Please browse back on the list, since we've covered this twice or thrice already. short version: rebuild /usr/src/lib first, then /usr/src/gnu/usr.bin/cc, then make world again, and mayhaps again. Also read UPDATING in /usr/src --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 1:21:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 1E83D153FE for ; Sun, 11 Apr 1999 01:21:54 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.109]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6BA7; Sun, 11 Apr 1999 10:19:35 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id KAA54176; Sun, 11 Apr 1999 10:19:25 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904110510.BAA07448@chen.ml.org> Date: Sun, 11 Apr 1999 10:19:25 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Luoqi Chen Subject: RE: thread-safe libgcc Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Apr-99 Luoqi Chen wrote: > For threaded applications to work correctly, we need a thread-safe > version of libgcc. It is straight forward to build: define _PTHREADS in > CFLAGS. We can have both versions just like libc and libc_r, and use the > thread-safe version when linking threaded applications. If no one objects, > I will add it to our tree and make necessary changes to gcc to use it. By all means, please do. Since GTk+ or Gnome likes threads as well, and a lot more Linux apps do as well... --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 1:29:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 9E14714EF3 for ; Sun, 11 Apr 1999 01:29:38 -0700 (PDT) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id RAA30009; Sun, 11 Apr 1999 17:57:12 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 11 Apr 1999 17:57:12 +0930 (CST) From: "Daniel J. O'Connor" To: Dmitry Valdov Subject: RE: DoS from local users Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Apr-99 Dmitry Valdov wrote: > cat > qqq > echo $$ > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > > Ctrl-D > > ./qqq > > Is there Any way to fix it? Give your users process limits. ie change the login class they use so it restricts the maximum number of processes they can run. --- 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-current" in the body of the message From owner-freebsd-current Sun Apr 11 15:31:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 0B6DE14C8F for ; Sun, 11 Apr 1999 15:31:24 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id QAA13037 for freebsd-current@FreeBSD.ORG; Sun, 11 Apr 1999 16:27:40 +0200 (CEST) (envelope-from olli) Date: Sun, 11 Apr 1999 16:27:40 +0200 (CEST) From: Oliver Fromme Message-Id: <199904111427.QAA13037@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: msdosfs problems? Newsgroups: list.freebsd-current Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG adrian@FreeBSD.ORG wrote in list.freebsd-current: > >> mpg123 is an ancient player. It won't play most newer MP3s. Use a newer > >> player, like x11amp or xaudio. > > > >In its defense, mpg123 is not ancient, and is the _BEST_ MP3 player. I have > >no idea what kinda of b0rked up MP3s there are nowadays it won't play. > [...] > Whether mpg123 is at fault from a 'standards' point of view, or the encoder > is just crappy (more likely IMHO) and xaudio caters for it is something I > don't have the answer for. MPEG heads out there, care to comment .. ? First of all, there is no such thing as "newer MP3s". The MPEG audio stream format is specified in the ISO documents IS11172-3 (MPEG 1.0) and IS13818-3 (MPEG 2.0), and these have been stable for years. I believe that mpg123 complies with these standards (in the sense that it reads and decodes standard-conforming MPEG audio streams correctly), and it even supports certain non-standard extensions, for example so-called "MPEG 2.5" (a low-bitrate extension invented by FHG). The latest version (mpg123 0.59q) also supports variable-bitrate streams ("VBR") which have become somewhat popular lately. However, it is unfortunately a fact that there are a lot of MPEG encoders and other MPEG tools around which create broken (i.e. not standard-conforming) MPEG streams. The various decoders and players have different ways to handle (or not to handle) those streams -- some are more tolerant and try to interpret everything as MPEG data and play it somehow (they would even try to play your /kernel), while others are more strict and try to enforce the standard. At the beginning, I tried to keep mpg123 strictly standard- conforming, i.e. rejecting broken files completely. My intention was to support the standard and make people aware of it (after all, standards _are_ a good thing, aren't they?). But unfortunately, you lose if you're the only one who's doing that... So we (i.e. mostly Michael) started to add all kinds of work-arounds and try to keep up with the brokenness of encoders. However, this is a bit like trying to write a Web browser that should display _all_ HTML pages which are out there correctly -- it's nearly impossible. Nevertheless, I believe that mpg123 decodes MPEG audio files created by all popular encoders correctly (including l3enc, mp3enc, bladeenc, 8hz, Xing, etc.). Regards Oliver (mpg123 co-author) -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 15:33: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 955571516F for ; Sun, 11 Apr 1999 15:32:56 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA22050; Sun, 11 Apr 1999 22:51:07 +0900 (JST) Message-ID: <37108E49.F3695F1D@newsguy.com> Date: Sun, 11 Apr 1999 20:58:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Amancio Hasty Cc: Matthew Dillon , Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: <199904102030.NAA08796@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > It should be possible to prevent a user from hogging a system if the system's > naive scheduler is improved. I think the problem is not related to the scheduler, but to the code path involved in running and reading the file at the same time, multiple times. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 15:36:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (Postfix) with ESMTP id E21AE155D1 for ; Sun, 11 Apr 1999 15:35:44 -0700 (PDT) (envelope-from oleg@ogurok.com) Received: from localhost (oleg@localhost) by ogurok.com (8.9.2/8.9.2) with ESMTP id KAA36013 for ; Sun, 11 Apr 1999 10:04:16 -0400 (EDT) (envelope-from oleg@ogurok.com) Date: Sun, 11 Apr 1999 10:04:15 -0400 (EDT) From: Oleg Ogurok To: freebsd-current@freebsd.org Subject: colour 'ls' Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there. Have you ever thought about putting colour listing in 'ls' command? First I saw it in linux and then there's a program called 'gnuls' in ports. It looks really cool when you do: gnuls --color=yes Files print as usual and directories print in colour ;-) I put ls as a symbolic link to gnuls, but every time I make world, the old 'ls' puts back ;-) Oleg Ogurok oleg@ogurok.com http://www.ogurok.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16: 8: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id F3C8915734 for ; Sun, 11 Apr 1999 15:40:53 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id XAA05617 for ; Sun, 11 Apr 1999 23:47:03 +0200 (CEST) Date: Sun, 11 Apr 1999 23:47:03 +0200 (CEST) From: Martin Blapp To: freebsd-current@freebsd.org Subject: Panic from today's current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While running a make 'buildworld -j 10', my SMP box crashed. I had a running nfs-server and softupdates enabled when it happened. The kernel-configfile and dmesg-output is available from: http://www.attic.ch/fuchur_kernel.html panic at: generic_bcopy+0x1a repe movsl (%esi), %es:(%edi) db> trace generic_bcopy(c02cc380,c7bb9b1f,0,a,0) at generic_bcopy+0x1a sccnputc(cff,1,c7bb9b80,c016c066) at sccnputc+0x180 cnputc(a,0,0,a,c7bb9bcc) at cnputc+0x3d putchar(a,c7bb9bf0) at putchar+0xa6 kvprintf(c028da63,c016bfc0,c7bb9bf0,a,c7bb9c04) at kvprintf+0x64 printf(c028da49,80000000,c1159b00,a8,c7bc3e60) at printf+0x3d trap(10,10,a8,c1159b00,c7bb9ce8) at trap+0x462 calltrap() at calltrap+0x3c --- trap 0x13, eip = 0xc7bb9c68, ebp = 0xc7bb9ce8 --- ufs_lookup(c7bb9d2c,c7bb9d40,c0184946,c7bb9d2c,c79ba00e) at ufs_lookup+0x353 ufs_vnoperate(c7bb9d2c,c79ba00e,c746e580,c7bb9f10,c746e580 at ufs_vnoperate+0x15 vfs_cache_lookup(c7bb9d84,c7bb9d94,c0186d2b,c7bb9d84,c7470e00) at vfs_cache_lookup+0x26a ufs_vnoperate(c7bb9d84,c7470e00,c7bb9f10,c1303a00,0) at ufs_vnoperate+0x15 lookup(c7bb9eec,0,c7bb9f84,fffffffc,c7b757f0) at lookup+0x2af namei(c7bb9eec,0,c7bb9f84,fffffffc,c02df240) at namei+0x291 vn_open(c7bb9eec603,1a4c7bc3e60,c029d3f0) at vn_open+0x59 open(c7bc3e60,c7bb9f84,8070aa0,10,8085680) at open+0xbb syscall(2f,2f,8085680,10,bfbfcb84) at syscall+0x182 Xint0x80_syscall() at Xint0x80_syscall+0x4c It seams to be ufs-related. Does anybody know what happened ? Martin Martin Blapp, mblapp@solnet.ch ---------------------------------------------- SolNet, Internet Solution Provider Bechburgstrasse 29, 4528 Zuchwil, Switzerland Phone: +41 32 686 82 82, Fax: +41 32 685 96 13 ---------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:17: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id BF3CF17496 for ; Sun, 11 Apr 1999 15:49:59 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id RAA04823; Sun, 11 Apr 1999 17:47:27 -0500 (CDT) From: Kevin Day Message-Id: <199904112247.RAA04823@home.dragondata.com> Subject: Re: DoS from local users (fwd) In-Reply-To: <199904112100.PAA05104@harmony.village.org> from Warner Losh at "Apr 11, 1999 3: 0:50 pm" To: imp@harmony.village.org (Warner Losh) Date: Sun, 11 Apr 1999 17:47:26 -0500 (CDT) Cc: dillon@apollo.backplane.com, hasty@rah.star-gate.com, dv@dv.ru, green@unixhelp.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199904102057.PAA27724@home.dragondata.com> Kevin Day writes: > : i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid > : 1002 starts up one process. Uid 1002's process gets 50% cpu, and uid 1001's > : 40 processes get 50% cpu shared between them. > > I've seen some experimental patches in the past that try to do just > this. However, there are some problems. What if uid 1002's process > does a sleep. Should the 40 processes that 1001 just get 50% of the > cpu? Or should there be other limits. It turns into an interesting > research problem in a hurry. > > Warner > I was thinking essentially just processes in the RUN state get applied to this. If the cpu would otherwise be sitting idle, by all means give it to someone. But, if two users have processes running, just because one user has 50 processes doesn't mean it should get 50x the cpu as one user who has one process running. If a process is in sleep or blocked(select, IO, whatever), it's taken out of consideration for the cpu, and the full cpu is given to those processes that actually have work to do. At least, that's my take on it. I run into this problem daily, and i get enough user complains of "User x has 50 processes running, eating as much cpu as they can, my compile just took 15 minutes". Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:17:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4A2C3156F9 for ; Sun, 11 Apr 1999 15:53:08 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA32643; Sun, 11 Apr 1999 15:03:02 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA05124; Sun, 11 Apr 1999 15:02:59 -0600 (MDT) Message-Id: <199904112102.PAA05124@harmony.village.org> To: Rod Taylor Subject: Re: DoS from local users (fwd) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Apr 1999 05:29:34 EDT." <37106B7D.50B2F49D@rcc.on.ca> References: <37106B7D.50B2F49D@rcc.on.ca> <199904110354.XAA28481@kot.ne.mediaone.net> Date: Sun, 11 Apr 1999 15:02:59 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37106B7D.50B2F49D@rcc.on.ca> Rod Taylor writes: : I like this, but the problem with that fork bomb program still exists. : It was afterall system cpu that was doing all the work, not the users : cpu. System CPU still gets charged to the user, so this is a non-issue. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:17:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3E6A114DA8 for ; Sun, 11 Apr 1999 15:53:08 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA32636; Sun, 11 Apr 1999 15:00:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA05104; Sun, 11 Apr 1999 15:00:50 -0600 (MDT) Message-Id: <199904112100.PAA05104@harmony.village.org> To: Kevin Day Subject: Re: DoS from local users (fwd) Cc: dillon@apollo.backplane.com (Matthew Dillon), hasty@rah.star-gate.com, dv@dv.ru, green@unixhelp.org, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 10 Apr 1999 15:57:26 CDT." <199904102057.PAA27724@home.dragondata.com> References: <199904102057.PAA27724@home.dragondata.com> Date: Sun, 11 Apr 1999 15:00:50 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904102057.PAA27724@home.dragondata.com> Kevin Day writes: : i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid : 1002 starts up one process. Uid 1002's process gets 50% cpu, and uid 1001's : 40 processes get 50% cpu shared between them. I've seen some experimental patches in the past that try to do just this. However, there are some problems. What if uid 1002's process does a sleep. Should the 40 processes that 1001 just get 50% of the cpu? Or should there be other limits. It turns into an interesting research problem in a hurry. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:17:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id EB63C14FE8 for ; Sun, 11 Apr 1999 15:53:50 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id LAA34824; Sun, 11 Apr 1999 11:29:09 -0500 (CDT) (envelope-from bob) Date: Sun, 11 Apr 1999 11:29:09 -0500 From: Bob Willcox To: Brian Beattie Cc: Warner Losh , leifn@neland.dk, sheldonh@iafrica.com, freebsd-current@FreeBSD.ORG Subject: Re: AIC Message-ID: <19990411112909.A34758@luke.pmr.com> Reply-To: Bob Willcox References: <199903311835.LAA00284@rover.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Brian Beattie on Wed, Mar 31, 1999 at 12:28:47PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 31, 1999 at 12:28:47PM -0800, Brian Beattie wrote: > On Wed, 31 Mar 1999, Warner Losh wrote: > > > The aic driver will likely oneday be ported. However, no one has come > > forward to do it. It is a highly desirable driver to have (even if > > Umm, I'm still working on the aic driver. Slowly, but working on it. > > > writing it would be a pain) because the only pccard scsi cards that are > > out there are aic-6[23]60 based. > > > > Not having a pcmcia slot or card, I am not sure about support for this. I have both and would be willing to test it on my laptop. -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:18: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B170914C02 for ; Sun, 11 Apr 1999 15:58:50 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA14662 for ; Sun, 11 Apr 1999 13:35:00 -0400 (EDT) Date: Sun, 11 Apr 1999 13:35:00 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.org Subject: swap-related problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that something has broken the good ol' swap behavior. For instance, I have my user-limits set to unlimited and I run something which uses up all RAM. Mallocing never FAILS in the program, as brk() doesn't fail, as etc etc etc. But mallocing continues, all swap space gets used, and both the runaway process and the next biggest gets killed (XF86, of course). Matt, perhaps you can shed light on a. why mallocs still succeed after swap_pager: out of swap space swap_pager_getswapspace: failed is displayed b. why the process continues and gets killed TWICE, or two different processes get killed ? Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:24:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 4DD6E1628C for ; Sun, 11 Apr 1999 16:08:00 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id TAA11443; Sun, 11 Apr 1999 19:05:30 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Sun, 11 Apr 1999 19:05:30 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Rahul Dhesi Cc: freebsd-current@freebsd.org Subject: Re: showing full host names in output from who/finger/last In-Reply-To: <199904110018.AA21927@bolero-x.rahul.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Rahul Dhesi wrote: > For some years I have been using patched utilities under SunOS to show > full host names in the output from the 'who', 'finger', and 'last' > commands. (Traditional UNIXes truncate host names to about 16 > characters.) > > I have been thinking of patching FreeBSD programs to do the same, but > since I have been updating my source tree often, it will be a bit > painful to maintain my changes through the updates. So I will do it > only if the FreeBSD developers would be willing to incorporate my > changes into the official FreeBSD source tree. Below is what I would > do -- tell me if it could be make a part of FreeBSD. > > - Update all programs that write to utmp and wtmp to check the host name > length, and if it's too long, insert the IP address instead Hi there. I'd actually like to see wtmp only use IP addresses, never hostnames. Spoofed names are fairly easy to arrange; with IP filtering on border routers, spoofed IPs are harder. Besides which, connections are from IPs and not names. :-) This of course sticks you with the task of DNS lookups when viewing wtmp, when you may already have done them at login time. Probably ideally, we'd have two variable length fields, one for a network-supplied source, and one for a transformed source such as name, display name (....:0), etc. But that requires modifying the record format, which is always a pain. I got sick of seing "invalid hostname" in my wtmps a while ago on my 2.x machines. That is an exceptionally useless piece of behavior, if you ask me. Sshd writes out IPs and I find that to be much more consistent (and useful). Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:33:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from wcug.wwu.edu (sloth.wcug.wwu.edu [140.160.164.200]) by hub.freebsd.org (Postfix) with SMTP id 087F415488 for ; Sun, 11 Apr 1999 16:12:38 -0700 (PDT) (envelope-from tcole@wcug.wwu.edu) Received: (qmail 21424 invoked by uid 1085); 11 Apr 1999 23:10:21 -0000 Date: Sun, 11 Apr 1999 16:10:21 -0700 From: Travis Cole To: Oleg Ogurok Cc: freebsd-current@freebsd.org Subject: Re: colour 'ls' Message-ID: <19990411161020.A19995@wcug.wwu.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Oleg Ogurok on Sun, Apr 11, 1999 at 10:04:15AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 11, 1999 at 10:04:15AM -0400, Oleg Ogurok wrote: > > Files print as usual and directories print in colour ;-) > I put ls as a symbolic link to gnuls, but every time I make world, the old > 'ls' puts back ;-) Instead of the symlink just try using a shell alias for it. alias ls="gnuls --color=auto" or some such. Put that in your shell init files. > > Oleg Ogurok > oleg@ogurok.com > http://www.ogurok.com -- --Travis Linux isn't the only free UNIX www.OpenBSD.org www.NetBSD.org www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:49:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from oldnews.quick.net (unknown [207.212.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 645E315413 for ; Sun, 11 Apr 1999 16:31:21 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id QAA15239; Sun, 11 Apr 1999 16:28:51 -0700 (PDT) Date: Sun, 11 Apr 1999 16:28:50 -0700 (PDT) From: "Steven P. Donegan" To: Martin Blapp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic from today's current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, a kernel built today results in an infinite boot/re-boot cycle on my system (SMP, Tomcat IV). Never gets to a point where a proper dump/tombstone happens. Sorry, no definitive trace here... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:50:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A5C3916097 for ; Sun, 11 Apr 1999 16:38:59 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA08407; Sun, 11 Apr 1999 16:36:40 -0700 (PDT) (envelope-from dillon) Date: Sun, 11 Apr 1999 16:36:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199904112336.QAA08407@apollo.backplane.com> To: Oleg Ogurok Cc: freebsd-current@FreeBSD.ORG Subject: Re: colour 'ls' References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi there. : :Have you ever thought about putting colour listing in 'ls' command? First :I saw it in linux and then there's a program called 'gnuls' in ports. It :looks really cool when you do: :gnuls --color=yes :Files print as usual and directories print in colour ;-) :I put ls as a symbolic link to gnuls, but every time I make world, the old :'ls' puts back ;-) : :Oleg Ogurok :oleg@ogurok.com :http://www.ogurok.com Color ls doesn't really belong in the base distribution, IMHO. It's simple enough to create a softlink to it in /usr/local/bin and then put /usr/local/bin in your path before /bin if you really want to have it as the 'default'. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:52:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 13936153D6 for ; Sun, 11 Apr 1999 16:48:10 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id TAA34660; Sun, 11 Apr 1999 19:45:40 -0400 (EDT) Date: Sun, 11 Apr 1999 19:45:39 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kevin Day Cc: Warner Losh , dillon@apollo.backplane.com, hasty@rah.star-gate.com, dv@dv.ru, freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-Reply-To: <199904112247.RAA04823@home.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Kevin Day wrote: > > In message <199904102057.PAA27724@home.dragondata.com> Kevin Day writes: > > : i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid > > : 1002 starts up one process. Uid 1002's process gets 50% cpu, and uid 1001's > > : 40 processes get 50% cpu shared between them. > > > > I've seen some experimental patches in the past that try to do just > > this. However, there are some problems. What if uid 1002's process > > does a sleep. Should the 40 processes that 1001 just get 50% of the > > cpu? Or should there be other limits. It turns into an interesting > > research problem in a hurry. > > > > Warner > > > > I was thinking essentially just processes in the RUN state get applied to > this. If the cpu would otherwise be sitting idle, by all means give it to > someone. But, if two users have processes running, just because one user has > 50 processes doesn't mean it should get 50x the cpu as one user who has one > process running. If a process is in sleep or blocked(select, IO, whatever), > it's taken out of consideration for the cpu, and the full cpu is given to > those processes that actually have work to do. > > > At least, that's my take on it. > > I run into this problem daily, and i get enough user complains of "User x > has 50 processes running, eating as much cpu as they can, my compile just > took 15 minutes". "What was their user name again?" *click xterm click* ps aux | grep ^user | wc -l "Hmm, you're right, fifty processes called 'cpuwaster'." rmuser user "They've been eliminated, thank you for letting us know of problems you have!" It's called "being a sysadmin". If someone's abusing the machine, delete em. > > > Kevin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 16:53:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3842D15581 for ; Sun, 11 Apr 1999 16:52:26 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40359>; Mon, 12 Apr 1999 09:36:43 +1000 Date: Mon, 12 Apr 1999 09:49:54 +1000 From: Peter Jeremy Subject: CTM problem(?) To: current@freebsd.org Message-Id: <99Apr12.093643est.40359@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't received anything from CTM for cvs-cur since around 0110 PDT yesterday (11th April). The last thing I got was "ctm-mail cvs-cur.5226.gz 29/39" and the ftp server shows that up to 5230 (at least) have been generated. Is anyone else having problems? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 17: 7:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2641C14FA4 for ; Sun, 11 Apr 1999 17:07:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA08629; Sun, 11 Apr 1999 17:04:56 -0700 (PDT) (envelope-from dillon) Date: Sun, 11 Apr 1999 17:04:56 -0700 (PDT) From: Matthew Dillon Message-Id: <199904120004.RAA08629@apollo.backplane.com> To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It seems that something has broken the good ol' swap behavior. For instance, :I have my user-limits set to unlimited and I run something which uses up :all RAM. Mallocing never FAILS in the program, as brk() doesn't fail, as etc :etc etc. But mallocing continues, all swap space gets used, and both the :runaway process and the next biggest gets killed (XF86, of course). : Matt, perhaps you can shed light on : a. why mallocs still succeed after :swap_pager: out of swap space :swap_pager_getswapspace: failed : is displayed : b. why the process continues and gets killed TWICE, or two different : processes get killed :? : : Brian Feldman _ __ ___ ____ ___ ___ ___ The thing with the processes getting killed twice or two different processes being killed is due to the latency between sending the signal to kill the process and the process actually going away. In order to be killed, the process must be woken up and allowed to run. malloc() still succeeds because it isn't actually touching the new memory, and so the system doesn't actually reserve the memory as of the time of the system call. That is done by the user program later on after malloc() returns. malloc()'s limitations are based on the process resources, not available memory. It would not be appropriate to make malloc() fail in this situation because this would result in N random programs getting malloc() failures rather then one or two processes getting killed. Having N random processes get malloc() failures can lead to serious instability with processes. What might help in a situation like this would a way to flag certain processes as being 'very important' ... that should only be killed as a last resort, even if they have a relatively large RSS. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 17:16:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1A83A14BF1 for ; Sun, 11 Apr 1999 17:16:40 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40359>; Mon, 12 Apr 1999 10:00:58 +1000 Date: Mon, 12 Apr 1999 10:13:58 +1000 From: Peter Jeremy Subject: Re: CTM problem(?) To: current@FreeBSD.ORG Message-Id: <99Apr12.100058est.40359@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: >I haven't received anything from CTM for cvs-cur since around 0110 PDT >yesterday (11th April). Two minutes after posting this, the CTM backlog started appearing. It looks like it Chi.Alameda.net was sitting on it (possibly because hub.freebsd.org wouldn't accept it). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 17:20: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 573F414BE0 for ; Sun, 11 Apr 1999 17:19:57 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id CAA08229; Mon, 12 Apr 1999 02:17:33 +0200 (CEST) (envelope-from des) To: Oleg Ogurok Cc: freebsd-current@FreeBSD.ORG Subject: Re: colour 'ls' References: From: Dag-Erling Smorgrav Date: 12 Apr 1999 02:17:32 +0200 In-Reply-To: Oleg Ogurok's message of "Sun, 11 Apr 1999 10:04:15 -0400 (EDT)" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oleg Ogurok writes: > I put ls as a symbolic link to gnuls, but every time I make world, the old > 'ls' puts back ;-) Don't do that. Instead, do: # cd /usr/local/bin # ln -s gnuls ls and fix your PATH so /usr/local/bin comes before /bin. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 17:25:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 964A815116 for ; Sun, 11 Apr 1999 17:25:40 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id UAA02720; Sun, 11 Apr 1999 20:21:26 -0400 (EDT) Date: Sun, 11 Apr 1999 20:21:26 -0400 (EDT) From: Chuck Robey To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: CTM problem(?) In-Reply-To: <99Apr12.100058est.40359@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Peter Jeremy wrote: > I wrote: > >I haven't received anything from CTM for cvs-cur since around 0110 PDT > >yesterday (11th April). > > Two minutes after posting this, the CTM backlog started appearing. It > looks like it Chi.Alameda.net was sitting on it (possibly because > hub.freebsd.org wouldn't accept it). Fact. All those refused mails from hub have been hogging my ppp line all day, as I watched the deltas go into the circular file. You'll get them all. If you don't by tomorrow, then please *do* complain. > > Peter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 18: 2:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id B378914CAE for ; Sun, 11 Apr 1999 18:02:21 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id UAA05905 for ; Sun, 11 Apr 1999 20:13:19 -0500 (EST) Date: Sun, 11 Apr 1999 20:13:18 -0500 (EST) From: Alfred Perlstein To: current@freebsd.org Subject: have live system with NFS client cache problems what do i do? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, i was just doing a kernel compile over NFS and i have a weird situtation. After compiling everything the linker barfs on linking. gensetdefs: cd9660_bmap.o: not an ELF file for about 12 files... the compile is being done on a laptop that has my desktop's src dir NFS mounted. the card in the laptop is a 3comIII and the dekstop a pn0 doing a 'file cd9660_bmap.o' on laptop (NFS client) gives me a cd9660_bmap.o: MS Windows COFF Unknown CPU while on the server: strlen.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stri it seems my client is having a really tough time with these files, i have copied the files that the client has corrupted to localdisk but now they seem fine... the client laptop is unable to link the kernel it's getting tons of corrupted data is seems, on the server i am able to link the kernel just fine. i'm using the default NFS mounts and no nfsiod. enabling nfsiod didn't help, however unmounting the NFS share and remounting seems to have fixed it.... i guess i should have taken a crash dump when the system was all hosed but it's fine now... *sigh* Alfred Perlstein - Admin, coder, and admirer of all things BSD. -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 18: 8:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B8E7D14CAE for ; Sun, 11 Apr 1999 18:08:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA11772; Sun, 11 Apr 1999 18:05:54 -0700 (PDT) (envelope-from dillon) Date: Sun, 11 Apr 1999 18:05:54 -0700 (PDT) From: Matthew Dillon Message-Id: <199904120105.SAA11772@apollo.backplane.com> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hey, i was just doing a kernel compile over NFS and i have a weird :situtation. After compiling everything the linker barfs on linking. : :gensetdefs: cd9660_bmap.o: not an ELF file What exact release of the kernel is running on the client and on the server? What is being NFS mounted? src tree? obj tree? both? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 18:13:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 11AA914CAE for ; Sun, 11 Apr 1999 18:13:22 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA35597; Sun, 11 Apr 1999 21:11:09 -0400 (EDT) Date: Sun, 11 Apr 1999 21:11:08 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <199904120004.RAA08629@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Matthew Dillon wrote: > :It seems that something has broken the good ol' swap behavior. For instance, > :I have my user-limits set to unlimited and I run something which uses up > :all RAM. Mallocing never FAILS in the program, as brk() doesn't fail, as etc > :etc etc. But mallocing continues, all swap space gets used, and both the > :runaway process and the next biggest gets killed (XF86, of course). > : Matt, perhaps you can shed light on > : a. why mallocs still succeed after > :swap_pager: out of swap space > :swap_pager_getswapspace: failed > : is displayed > : b. why the process continues and gets killed TWICE, or two different > : processes get killed > :? > : > : Brian Feldman _ __ ___ ____ ___ ___ ___ > > The thing with the processes getting killed twice or two different > processes being killed is due to the latency between sending the signal > to kill the process and the process actually going away. In order to be > killed, the process must be woken up and allowed to run. Then let's make sure the kill waits before it does that. > > malloc() still succeeds because it isn't actually touching the new memory, > and so the system doesn't actually reserve the memory as of the time of > the system call. That is done by the user program later on after malloc() > returns. malloc()'s limitations are based on the process resources, not > available memory. I use the memory as soon as it's malloced. If it reserves a page, then pagefaults it into existence, the VM system knows that that page is now allocated. When I malloc the last available page for user use, the VM system knows that it's the last page. I dirty it, and there are none free. If I malloc(), I want to know that there is no more memory, not have my process killed. This is POMA. Previously, the POLA, a NULL getting returned, WORKED CORRECTLY. It did this for a long time. My little test program always showed this, and shows that now something was broken. I'll attach it to the end. > > It would not be appropriate to make malloc() fail in this situation because > this would result in N random programs getting malloc() failures rather > then one or two processes getting killed. Having N random processes get > malloc() failures can lead to serious instability with processes. Only bad code doesn't check return values of malloc(). > > What might help in a situation like this would a way to flag certain > processes as being 'very important' ... that should only be killed as > a last resort, even if they have a relatively large RSS. Yes, I was thinking of something like this for the X server. > > -Matt > Matthew Dillon > > > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ ts=4 #include #include #include #define SIZE 1024*1024 #ifdef OTHER_VER const unsigned int junk[] = { 0xdeadbeef, 0xbeeff00d, 0x133751ff, 0xf33db34f }; #endif void main(void) { int count, yep = 0; void *stfu[SIZE]; void *mem; for (count = 0; count < SIZE; count++) { if ((mem = stfu[count] = malloc(1024))) { int where; printf("%p (%i) malloc'd\n", stfu[count], count); for (where = 0; where < (1024 / sizeof(unsigned)); where++) ((unsigned *)mem)[where] = #ifdef OTHER_VER junk[ #endif where #ifdef OTHER_VER % 4] #endif ; yep++; } else break; } /* free(stfu[yep--]); */ for (count = 0; count < yep; count++) { int where; mem = stfu[count]; for (where = 0; where < (1024 / sizeof(unsigned)); where++) if (((unsigned *)mem)[where] != #ifdef OTHER_VER junk[ #endif where #ifdef OTHER_VER % 4] #endif ) { fprintf(stderr, "memory check failed at %i of %i:\n" "%#x != %#x\n", count, yep, ((unsigned *)mem)[where], #ifdef OTHER_VER junk[ #endif where #ifdef OTHER_VER % 4] #endif ); exit(2); } free(stfu[count]); printf("%i free'd\n", count); } if (yep != SIZE) { printf("mallocs failed at %i\n", yep); exit (1); } else exit (0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 18:33:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 3D66A14EA7 for ; Sun, 11 Apr 1999 18:33:34 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id JAA15374 for ; Mon, 12 Apr 1999 09:31:10 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA14377; Mon, 12 Apr 1999 09:31:09 +0800 Message-Id: <199904120131.JAA14377@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Re: DoS from local users (fwd) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Apr 1999 09:31:09 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > What about a new login-class capability specifying the maximum > percentage of CPU time a class of users can utilize? With standard > class having 90% (or 95%)? The machine would appear (to most of > the users) as if it had 10% slower CPU, with the remaining usable > by the root-class. This way, if the CPU consumption by system is > 30%, the most CPU time the standard users can get is 60%. > > Trusted users can be placed into a different class, of course. > > Plausible? > What you guys are describing is the FAIR SHARE scheduler for Unix, as implemented by Softway in Sydney many years ago. It originated in Sydney University as part of the efforsts of the CS department there to share out an old Vax 11/780 amongst 80 odd users at a time. Students aren't noted for their common sense, so measures like this were necessary. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 18:55:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 99D5F14FF4 for ; Sun, 11 Apr 1999 18:55:46 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA12154; Sun, 11 Apr 1999 18:53:24 -0700 (PDT) (envelope-from dillon) Date: Sun, 11 Apr 1999 18:53:24 -0700 (PDT) From: Matthew Dillon Message-Id: <199904120153.SAA12154@apollo.backplane.com> To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I use the memory as soon as it's malloced. If it reserves a page, then :pagefaults it into existence, the VM system knows that that page is now :allocated. When I malloc the last available page for user use, the VM :system knows that it's the last page. I dirty it, and there are none :free. If I malloc(), I want to know that there is no more memory, not :have my process killed. This is POMA. : :Previously, the POLA, a NULL getting returned, WORKED CORRECTLY. It did this :for a long time. My little test program always showed this, and shows :that now something was broken. I'll attach it to the end. I ran your program. malloc() appears to work properly -- returns NULL when the datasize limit is reached. In my case, I set the datasize limit to 64MB and ran the program. ... mallocs failed at 64956 Under 4.0-current. :> then one or two processes getting killed. Having N random processes get :> malloc() failures can lead to serious instability with processes. : :Only bad code doesn't check return values of malloc(). You are volunteering to run through the thousands of programs & ports to make sure that every one checks the return value for malloc()? Declarations that don't solve problems are not relevant. It's bad enough that we have to kill something to handle an out-of-vm situation, we shouldn't go off and destabilize the rest of the system while we are at it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 18:56:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id D62E8153BE for ; Sun, 11 Apr 1999 18:56:33 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id VAA00498; Sun, 11 Apr 1999 21:07:23 -0500 (EST) Date: Sun, 11 Apr 1999 21:07:22 -0500 (EST) From: Alfred Perlstein To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? In-Reply-To: <199904120105.SAA11772@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Matthew Dillon wrote: > :Hey, i was just doing a kernel compile over NFS and i have a weird > :situtation. After compiling everything the linker barfs on linking. > : > :gensetdefs: cd9660_bmap.o: not an ELF file > > What exact release of the kernel is running on the client and on the > server? > > What is being NFS mounted? src tree? obj tree? both? -current as of tuesday night. although the laptop is now moved to -current as of today. i have 192.168.1.44:/usr/src on /usr/src this is only building the kernel in /usr/src/sys/compile/laptop server: FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Apr 9 11:34:01 PDT 1999 bright@myname.my.domain:/usr/src/sys/compile/halah i386 client: FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Apr 11 17:46:19 PDT 1999 bright@myname.my.domain:/usr/src/sys/compile/laptop i386 i think it may be easily reproducable. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 19: 3: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id D3949153AD for ; Sun, 11 Apr 1999 19:02:45 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id OAA06139; Sun, 11 Apr 1999 14:23:58 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA57685; Sun, 11 Apr 1999 14:23:51 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904111323.OAA57685@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Rahul Dhesi Cc: freebsd-current@FreeBSD.ORG Subject: Re: showing full host names in output from who/finger/last In-reply-to: Your message of "Sat, 10 Apr 1999 17:18:08 PDT." <199904110018.AA21927@bolero-x.rahul.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Apr 1999 14:23:49 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For some years I have been using patched utilities under SunOS to show > full host names in the output from the 'who', 'finger', and 'last' > commands. (Traditional UNIXes truncate host names to about 16 > characters.) > > I have been thinking of patching FreeBSD programs to do the same, but > since I have been updating my source tree often, it will be a bit > painful to maintain my changes through the updates. So I will do it > only if the FreeBSD developers would be willing to incorporate my > changes into the official FreeBSD source tree. Below is what I would > do -- tell me if it could be make a part of FreeBSD. > > - Update all programs that write to utmp and wtmp to check the host name > length, and if it's too long, insert the IP address instead I've been doing this in current in the last few days. There's now a new function in libutil called realhostname(). You pass it a maximum fields size (UT_HOSTSIZE?). If it can fit the gethostbyaddr() result into the field, AND that name resolves back to the same IP number, the full host name is used, otherwise the IP number is used. The trimdomain() function has also been fixed and documented. I believe all the stuff in libexec now works and I've just committed some ssh patches that'll do the same for sshd. > - Update all of the above programs, if they accept a host name on the > command line, to also accept an additional argument that specifies > the IP address. > - Update all programs that invoke the above programs and supply a > host name to also supply the IP address. I think the host name that's passed should be considered correct. However, if it doesn't fit in the ut_host field, a gethostbyname() is required. Passing an IP number would therefore probably be a quite good addition if it avoids that call. > - Update all programs that look up wtmp and utmp such that, if they find > an IP address, they do a double-reverse DNS resolution (IP address -> > fqdn -> IP address) and, if successful and consistent, display the > host name instead of the IP address. The user may if he wishes supply > a command-line argument to suppress the reverse resolution and cause > the IP address to be displayed directly. I'd agree with Matt here - don't make the default suddenly require lookups, but I'd say that if a lookup is being done, it should be a correct double lookup (realhostname() from libutil). > For example, rlogind might invoke /usr/bin/login as: > > /usr/bin/login -h 98.portland-23-24rs.or.dial-access.att.net -i 12.73.137.98 > > /usr/bin/login notices that the host name is too long, inserts > 12.73.137.98 into utmp and wtmp. If no -i argument is available, > /usr/bin/login would do a forward DNS resolution of the host name to get > the IP address. Yep. This sounds pretty rational. > Below are samples from the 'last' and 'finger' commands with only the > really long host names included and some information x'd out to protect > user privacy. (Obviously comumnar alignment doesn't work as well for > very long host names, but only a small fraction are that long. The rest > will display normally in aligned columns.) > > == output from 'finger == > Login Name Idle When Where > xxxxxx xxxxxxxxxxxxxx 7 Apr 9 13:14 kaibab.redbacknetworks.com > xxx xxxxxxxxxxxxxxx Apr 10 16:37 dyn164.rahul.net > xxxxxxxx xxxxxxxxxxxx 8 Apr 10 16:48 c166.ppp.tsoft.com > xxxxx xxxxxxxxxxx Apr 9 23:35 \ > cxxxxxxx-x.xxxxx.occa.home.com > xxxxx xxxxxxxxxxxx * 10 Apr 10 16:44 01-025.006.popsite.net > > == output from 'last' == > xxx s1 98.portland-23-24rs.or.dial-access.att.net Sat Apr 10 16:50 - 16:50 (00:00) > xxxxxx rd oak-hiper1b-145-145.dialup.slip.net Sat Apr 10 16:48 - 16:51 (00:03) > xxxx p6 netcom14.netcom.com Sat Apr 10 15:36 - 15:39 (00:03) > xxxxx s2 adsl-xxx-xxx-xxx-10.dsl.snfc21.pacbell.net Sat Apr 10 13:51 - 13:52 (00:00) > xxxxxxxx sb tnt9-xxx-xxx-17-189.dialup.HiWAAY.net Sat Apr 10 12:54 - 14:54 (02:00) > xxxxxx s2 oak-hiper1a-15-79.dialup.slip.net Sat Apr 10 12:37 - 12:40 (00:02) > xxxx r2 dnai-207-181-255-82.dialup.dnai.com Sat Apr 10 11:41 - 13:58 (02:17) > xxxxxxx q8 sdn-ar-001casfraP195.dialsprint.net Sat Apr 10 08:28 - 13:30 (05:01) > == END == This is fine for ``w'' as I believe it already does the lookup. But in the ``who'' and ``last'' cases, they should display the contents of ut_host by default unless some consistent option is used - it's a pity that this is the opposite of the -n option to route/netstat and probably others :-( I'll review & commit your changes when you've got them done if you haven't already got someone. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 19: 3:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 496D714BF4 for ; Sun, 11 Apr 1999 19:03:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA12253; Sun, 11 Apr 1999 19:01:09 -0700 (PDT) (envelope-from dillon) Date: Sun, 11 Apr 1999 19:01:09 -0700 (PDT) From: Matthew Dillon Message-Id: <199904120201.TAA12253@apollo.backplane.com> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :-current as of tuesday night. although the laptop is now moved :to -current as of today. : :i have 192.168.1.44:/usr/src on /usr/src : :this is only building the kernel in /usr/src/sys/compile/laptop : :server: :FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Apr 9 11:34:01 PDT 1999 bright@myname.my.domain:/usr/src/sys/compile/halah i386 : :client: :FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Apr 11 17:46:19 PDT 1999 bright@myname.my.domain:/usr/src/sys/compile/laptop i386 : :i think it may be easily reproducable. : :-Alfred This is very odd: doing a 'file cd9660_bmap.o' on laptop (NFS client) gives me a cd9660_bmap.o: MS Windows COFF Unknown CPU An MS Windows binary? Do you have any msdos mounts on the client or server? How is /usr/obj mounted? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 19:15:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id B1CCD151AB for ; Sun, 11 Apr 1999 19:15:31 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id VAA12675; Sun, 11 Apr 1999 21:26:26 -0500 (EST) Date: Sun, 11 Apr 1999 21:26:24 -0500 (EST) From: Alfred Perlstein To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? In-Reply-To: <199904120201.TAA12253@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Matthew Dillon wrote: > :-current as of tuesday night. although the laptop is now moved > :to -current as of today. > : > :i have 192.168.1.44:/usr/src on /usr/src > : > :this is only building the kernel in /usr/src/sys/compile/laptop > : > :server: > :FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Apr 9 11:34:01 PDT 1999 bright@myname.my.domain:/usr/src/sys/compile/halah i386 > : > :client: > :FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Apr 11 17:46:19 PDT 1999 bright@myname.my.domain:/usr/src/sys/compile/laptop i386 > : > :i think it may be easily reproducable. > : > :-Alfred > > This is very odd: > > doing a 'file cd9660_bmap.o' on laptop (NFS client) gives me a > cd9660_bmap.o: MS Windows COFF Unknown CPU > > An MS Windows binary? Do you have any msdos mounts on > the client or server? How is /usr/obj mounted? /usr/obj isn't mounted, i'm just compiling a kernel. no i have no msdos mounted filesystems, i do however have an unmounted win98 partition and a cdrom with joliet extentions mounted however the cdrom only contains mp3s. After doing more data manipulation (copying files around to flush the NFS cache) it seems to reload the data then it finds them ok and tries to link, during the link i get missing references to several symbols, symbol sizes changed etc etc... Just seems like bad data. Now if i just go into the dir on the server and link the kernel it's fine, no problems whatsoever. (compile on local disk) -Alfred PS, i suspect the 3comIII card in the laptop # ep: 3Com 3C509 (buggy) NFS perfomance and stability in 3.1-stable and 4.0 have been surperb lately. one reboot when i was killing a low ram NFS server a few weeks ago and just this today (which could be the NIC) otherwise very impressive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 19:33:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E4D7C151D6 for ; Sun, 11 Apr 1999 19:33:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA14835; Sun, 11 Apr 1999 19:31:11 -0700 (PDT) (envelope-from dillon) Date: Sun, 11 Apr 1999 19:31:11 -0700 (PDT) From: Matthew Dillon Message-Id: <199904120231.TAA14835@apollo.backplane.com> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :/usr/obj isn't mounted, i'm just compiling a kernel. : :no i have no msdos mounted filesystems, i do however have an :unmounted win98 partition and a cdrom with joliet extentions mounted :however the cdrom only contains mp3s. : :After doing more data manipulation (copying files around to flush :the NFS cache) it seems to reload the data then it finds them ok :and tries to link, during the link i get missing references to :several symbols, symbol sizes changed etc etc... : :Just seems like bad data. : :Now if i just go into the dir on the server and link the kernel :it's fine, no problems whatsoever. (compile on local disk) : :-Alfred : :PS, i suspect the 3comIII card in the laptop # ep: 3Com 3C509 (buggy) : :NFS perfomance and stability in 3.1-stable and 4.0 have been surperb lately. :one reboot when i was killing a low ram NFS server a few weeks ago and just :this today (which could be the NIC) otherwise very impressive. Ok. This is something to watch, then. The corruption is worrysome. It is odd to get this sort of corruption in a client's buffer cache when all the file I/O is running over NFS. The real question is : where did the corruption come from? The client's IDE drive or something originally on the server? Are there any dos partitions on the server at all? If not, then the corruption is occuring on the client. But if the make procedure is not accessing (much of) the client's hard drive, where on the client could the corruption be coming from? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 19:58:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 8EF14151F3 for ; Sun, 11 Apr 1999 19:58:43 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id WAA02545 for ; Sun, 11 Apr 1999 22:58:48 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Sun, 11 Apr 1999 22:58:48 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: EGCS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure what I'm doing wrong here, but I still can't get the EGCS make world to work properly.... I just cvsupped like 20 minutes ago, and I typed make -DNOGAMES world. I forgot the particular error, but I don't think I'm doing it right. Is there something that I have to do before I do a make world? Thanks. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 20:20: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 68BCB15270 for ; Sun, 11 Apr 1999 20:20:05 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA36852; Sun, 11 Apr 1999 23:17:53 -0400 (EDT) Date: Sun, 11 Apr 1999 23:17:53 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <199904120153.SAA12154@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Matthew Dillon wrote: > :I use the memory as soon as it's malloced. If it reserves a page, then > :pagefaults it into existence, the VM system knows that that page is now > :allocated. When I malloc the last available page for user use, the VM > :system knows that it's the last page. I dirty it, and there are none > :free. If I malloc(), I want to know that there is no more memory, not > :have my process killed. This is POMA. > : > :Previously, the POLA, a NULL getting returned, WORKED CORRECTLY. It did this > :for a long time. My little test program always showed this, and shows > :that now something was broken. I'll attach it to the end. > > I ran your program. malloc() appears to work properly -- returns NULL when > the datasize limit is reached. In my case, I set the datasize limit > to 64MB and ran the program. Unset the datasize limit. Now what happens? It used to return NULL, now it gets SIGKILLed. Seriously, about the killing thing, shouldn't we at least have a timer so two things don't get killed? > > ... > mallocs failed at 64956 > > Under 4.0-current. > > :> then one or two processes getting killed. Having N random processes get > :> malloc() failures can lead to serious instability with processes. > : > :Only bad code doesn't check return values of malloc(). > > You are volunteering to run through the thousands of programs & ports > to make sure that every one checks the return value for malloc()? > > Declarations that don't solve problems are not relevant. It's bad enough > that we have to kill something to handle an out-of-vm situation, we > shouldn't go off and destabilize the rest of the system while we are at it. > > -Matt > > I don't tend to use untrustworthy code for production things. I doubt there are any unchecked mallocs in something as tested as, say, X11R6.3. There could be.. Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 20:24:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 56F1F15284 for ; Sun, 11 Apr 1999 20:24:17 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA36926; Sun, 11 Apr 1999 23:22:02 -0400 (EDT) Date: Sun, 11 Apr 1999 23:22:01 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? In-Reply-To: <199904120201.TAA12253@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Matthew Dillon wrote: > :-current as of tuesday night. although the laptop is now moved > :to -current as of today. > : > :i have 192.168.1.44:/usr/src on /usr/src > : > :this is only building the kernel in /usr/src/sys/compile/laptop > : > :server: > :FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Apr 9 11:34:01 PDT 1999 bright@myname.my.domain:/usr/src/sys/compile/halah i386 > : > :client: > :FreeBSD myname.my.domain 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Apr 11 17:46:19 PDT 1999 bright@myname.my.domain:/usr/src/sys/compile/laptop i386 > : > :i think it may be easily reproducable. > : > :-Alfred > > This is very odd: > > doing a 'file cd9660_bmap.o' on laptop (NFS client) gives me a > cd9660_bmap.o: MS Windows COFF Unknown CPU > > An MS Windows binary? Do you have any msdos mounts on > the client or server? How is /usr/obj mounted? Hey Matt, 0 leshort 0x0000 MS Windows COFF Unknown CPU ;) > > -Matt > Matthew Dillon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 20:26:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id DCD2815259 for ; Sun, 11 Apr 1999 20:26:35 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA36951; Sun, 11 Apr 1999 23:24:17 -0400 (EDT) Date: Sun, 11 Apr 1999 23:24:17 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? In-Reply-To: <199904120231.TAA14835@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Matthew Dillon wrote: > :/usr/obj isn't mounted, i'm just compiling a kernel. > : > :no i have no msdos mounted filesystems, i do however have an > :unmounted win98 partition and a cdrom with joliet extentions mounted > :however the cdrom only contains mp3s. > : > :After doing more data manipulation (copying files around to flush > :the NFS cache) it seems to reload the data then it finds them ok > :and tries to link, during the link i get missing references to > :several symbols, symbol sizes changed etc etc... > : > :Just seems like bad data. > : > :Now if i just go into the dir on the server and link the kernel > :it's fine, no problems whatsoever. (compile on local disk) > : > :-Alfred > : > :PS, i suspect the 3comIII card in the laptop # ep: 3Com 3C509 (buggy) > : > :NFS perfomance and stability in 3.1-stable and 4.0 have been surperb lately. > :one reboot when i was killing a low ram NFS server a few weeks ago and just > :this today (which could be the NIC) otherwise very impressive. > > Ok. This is something to watch, then. The corruption is worrysome. It > is odd to get this sort of corruption in a client's buffer cache when > all the file I/O is running over NFS. The real question is : where did > the corruption come from? The client's IDE drive or something originally > on the server? > > Are there any dos partitions on the server at all? If not, then the > corruption is occuring on the client. But if the make procedure is not > accessing (much of) the client's hard drive, where on the client could > the corruption be coming from? This has nothing to do with DOS. In case you didn't get my other hint: {"/home/green"}$ dd if=/dev/zero count=1 2>/dev/null | file - standard input: MS Windows COFF Unknown CPU > > -Matt > Matthew Dillon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 20:31:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6133315259 for ; Sun, 11 Apr 1999 20:31:34 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA44541; Sun, 11 Apr 1999 20:29:54 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: EGCS In-reply-to: Your message of "Sun, 11 Apr 1999 22:58:48 EDT." Date: Sun, 11 Apr 1999 20:29:54 -0700 Message-ID: <44539.923887794@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I forgot the particular error, but I don't think I'm doing it right. Is The actual error would be most helpful, otherwise this is sort of a waste of email. :( > there something that I have to do before I do a make world? Thanks. A make world, assuming that you're already ELF, should do it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 21: 2:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 31B151521B for ; Sun, 11 Apr 1999 21:02:44 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA15072; Sun, 11 Apr 1999 21:00:24 -0700 (PDT) (envelope-from dillon) Date: Sun, 11 Apr 1999 21:00:24 -0700 (PDT) From: Matthew Dillon Message-Id: <199904120400.VAA15072@apollo.backplane.com> To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> I ran your program. malloc() appears to work properly -- returns NULL when :> the datasize limit is reached. In my case, I set the datasize limit :> to 64MB and ran the program. : :Unset the datasize limit. Now what happens? It used to return NULL, now :it gets SIGKILLed. Seriously, about the killing thing, shouldn't we at least :have a timer so two things don't get killed? If you unset the datasize limit and the program does not exceed the maximum system-supported datasize limit, malloc() should not return NULL even if the system is out of swap. I don't know why it apparently did before -- it shouldn't have. I seem to remember that the default datasize limit for the system was upped a few months ago. I don't think malloc() operation has changed. The correct solution is to set a maximum datasize limit. That is what it is there for. I generally unlimit the datasize for root and set it to around 64MB for all other users. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 21: 6: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 113A31535C for ; Sun, 11 Apr 1999 21:05:59 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA15110; Sun, 11 Apr 1999 21:03:40 -0700 (PDT) (envelope-from dillon) Date: Sun, 11 Apr 1999 21:03:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199904120403.VAA15110@apollo.backplane.com> To: Brian Feldman Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> corruption is occuring on the client. But if the make procedure is not :> accessing (much of) the client's hard drive, where on the client could :> the corruption be coming from? : :This has nothing to do with DOS. In case you didn't get my other hint: :{"/home/green"}$ dd if=/dev/zero count=1 2>/dev/null | file - :standard input: MS Windows COFF Unknown CPU Ah. In that case, next time it happens you need to make a copy of the broken file and a copy of the good file and save them, so we can look at the hexdumps. If 'cp' does not copy the corrupted file, try using 'cat' to copy it. 'cp' uses mmap. 'cat' does not. There are still a few minor issues when mmap()ing NFS files, but none that ought to effect the beginning of the file. We'll have to figure out a way to reproduce the problem to really track it down. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 21:45:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6EE6B1504D for ; Sun, 11 Apr 1999 21:45:32 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA33993; Sun, 11 Apr 1999 22:43:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA03473; Sun, 11 Apr 1999 22:42:55 -0600 (MDT) Message-Id: <199904120442.WAA03473@harmony.village.org> To: Kenneth Wayne Culver Subject: Re: EGCS Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Apr 1999 22:58:48 EDT." References: Date: Sun, 11 Apr 1999 22:42:55 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenneth Wayne Culver writes: : I forgot the particular error, but I don't think I'm doing it right. Is : there something that I have to do before I do a make world? Thanks. Read src/UPDATING for a start. If the error isn't there, then please post the error. We can't do anything without a specific error message. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 22: 2: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 93E8A153FA for ; Sun, 11 Apr 1999 22:01:47 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id OAA19531; Mon, 12 Apr 1999 14:58:59 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma019465; Mon, 12 Apr 99 14:58:37 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id OAA16131; Mon, 12 Apr 1999 14:58:37 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id OAA29876; Mon, 12 Apr 1999 14:58:36 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id OAA27488; Mon, 12 Apr 1999 14:58:35 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199904120458.OAA27488@nymph.detir.qld.gov.au> To: Alfred Perlstein Cc: freebsd-current@freebsd.org, Matthew Dillon , syssgm@detir.qld.gov.au Subject: Re: have live system with NFS client cache problems what do i do? References: In-Reply-To: from Alfred Perlstein at "Sun, 11 Apr 1999 21:26:24 -0500" Date: Mon, 12 Apr 1999 14:58:34 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 11th April 1999, Alfred Perlstein wrote: >On Sun, 11 Apr 1999, Matthew Dillon wrote: > >> doing a 'file cd9660_bmap.o' on laptop (NFS client) gives me a >> cd9660_bmap.o: MS Windows COFF Unknown CPU >> >> An MS Windows binary? Do you have any msdos mounts on >> the client or server? How is /usr/obj mounted? >no i have no msdos mounted filesystems, i do however have an >unmounted win98 partition and a cdrom with joliet extentions mounted >however the cdrom only contains mp3s. This is a red herring: $ dd if=/dev/zero of=foo count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.000114 secs (4487949 bytes/sec) $ file foo foo: MS Windows COFF Unknown CPU $ Look for the usual pack-of-nulls corruption instead. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 22:13: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 308DD14C18 for ; Sun, 11 Apr 1999 22:13:03 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id PAA22346; Mon, 12 Apr 1999 15:10:31 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma022296; Mon, 12 Apr 99 15:10:12 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA16716; Mon, 12 Apr 1999 15:10:11 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id PAA01548; Mon, 12 Apr 1999 15:10:10 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA28056; Mon, 12 Apr 1999 15:10:09 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199904120510.PAA28056@nymph.detir.qld.gov.au> To: Brian Feldman To: freebsd-current@freebsd.org, syssgm@detir.qld.gov.au Subject: Re: have live system with NFS client cache problems what do i do? References: In-Reply-To: from Brian Feldman at "Sun, 11 Apr 1999 23:24:17 -0400" Date: Mon, 12 Apr 1999 15:10:09 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 11th April 1999, Brian Feldman wrote: >This has nothing to do with DOS. In case you didn't get my other hint: >{"/home/green"}$ dd if=/dev/zero count=1 2>/dev/null | file - >standard input: MS Windows COFF Unknown CPU Don't ya just hate it when your mail is slow! Sigh... Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 11 22:18:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 91411153EC for ; Sun, 11 Apr 1999 22:18:11 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id BAA38113; Mon, 12 Apr 1999 01:15:54 -0400 (EDT) Date: Mon, 12 Apr 1999 01:15:54 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Stephen McKay Cc: freebsd-current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? In-Reply-To: <199904120510.PAA28056@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Stephen McKay wrote: > On Sunday, 11th April 1999, Brian Feldman wrote: > > >This has nothing to do with DOS. In case you didn't get my other hint: > >{"/home/green"}$ dd if=/dev/zero count=1 2>/dev/null | file - > >standard input: MS Windows COFF Unknown CPU > > Don't ya just hate it when your mail is slow! Sigh... Yep ;) You know, I think a much better idea for being in magic(5) would be a check for lots of NULLs and calling the file "NULL data", rather than MS Windows COFF Unknown CPU. This identification is a bug in the magic file, really, since you can't call a short 0x0000 any kind of magic number! > > Stephen. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 0: 2:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 6A8B5150B8 for ; Mon, 12 Apr 1999 00:02:37 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id JAA16661; Mon, 12 Apr 1999 09:00:07 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id IAA42375; Mon, 12 Apr 1999 08:34:49 +0200 (CEST) (envelope-from andreas) Date: Mon, 12 Apr 1999 08:34:49 +0200 From: Andreas Klemm To: Oleg Ogurok Cc: freebsd-current@FreeBSD.ORG Subject: Re: colour 'ls' Message-ID: <19990412083449.A42332@titan.klemm.gtn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Oleg Ogurok on Sun, Apr 11, 1999 at 10:04:15AM -0400 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 11, 1999 at 10:04:15AM -0400, Oleg Ogurok wrote: > Hi there. > > Have you ever thought about putting colour listing in 'ls' command? First > I saw it in linux and then there's a program called 'gnuls' in ports. It > looks really cool when you do: > gnuls --color=yes > Files print as usual and directories print in colour ;-) > I put ls as a symbolic link to gnuls, but every time I make world, the old > 'ls' puts back ;-) This is a matter of taste. I personally dislike the coloring, since not all colors give a good contrast and for me it's unfriendly for my eyes. If I were you, I'd put a shell alias into your shells init file: alias ls '/usr/local/bin/gnuls --color=yes' But this is nothing for -current. And I think most of us dislike such things... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 0: 9:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from cscfx.sytex.com (cscfx.sytex.com [205.147.190.131]) by hub.freebsd.org (Postfix) with SMTP id C7EAE150B6 for ; Mon, 12 Apr 1999 00:09:12 -0700 (PDT) (envelope-from rwc@cscfx.sytex.com) Received: (from rwc@localhost) by cscfx.sytex.com (8.6.12/8.6.9) id DAA04835 for freebsd-current@freebsd.org; Mon, 12 Apr 1999 03:00:42 -0400 From: Richard Cramer Message-Id: <199904120700.DAA04835@cscfx.sytex.com> To: freebsd-current@freebsd.org Date: Mon, 12 Apr 1999 03:00:41 -0400 (EDT) Reply-To: rcramer@sytex.net X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 208 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current rcramer@sytex.net -- Richard Cramer rcramer@sytex.net Phone: 703-425-2515 President Fax: 703-425-4585 SytexNet(tm) Sytex Access Ltd. POB 2385, Fairfax, VA 22031-0385 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 1: 1:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id C025414C80 for ; Mon, 12 Apr 1999 01:01:16 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <2AY77VJL>; Mon, 12 Apr 1999 10:01:31 +0200 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097590@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Amancio Hasty' , Matthew Dillon Cc: Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: RE: DoS from local users (fwd) Date: Mon, 12 Apr 1999 09:55:40 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Amancio Hasty [SMTP:hasty@rah.star-gate.com] > Sent: Sunday, April 11, 1999 5:36 AM > To: Matthew Dillon > Cc: Dmitry Valdov; Brian Feldman; freebsd-current@FreeBSD.ORG > Subject: Re: DoS from local users (fwd) > > > > I guess any sufficiently advance science is indeed consider magic by > some. > > Amancio > [ML] Then I would like to have a high-tech gizmo for reading my users' minds. Would you, perhaps, know where I could buy/borrow/steal one of these? :) /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 1:14:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id B0B9714FA3 for ; Mon, 12 Apr 1999 01:14:34 -0700 (PDT) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA11567 (5.67b8/IDA-1.5 for ); Mon, 12 Apr 1999 01:12:16 -0700 Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA16244; Mon, 12 Apr 1999 01:12:14 -0700 Message-Id: <199904120812.AA16244@waltz.rahul.net> To: freebsd-current@freebsd.org Subject: Re: showing full host names in output from who/finger/last In-Reply-To: Message from Robert Watson of Sun, 11 Apr 99 19:05:30 -0500 Date: Mon, 12 Apr 99 01:12:14 -0700 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson writes: > I'd actually like to see wtmp only use IP addresses, never hostnames. > Spoofed names are fairly easy to arrange; with IP filtering on border > routers, spoofed IPs are harder.... > This of course sticks you with the task of DNS > lookups when viewing wtmp, when you may already have done them at login > time.... The 'finger', 'who', and 'w' commands on the SunOS machines here all do DNS lookups for longer hostnames, and it's rare that there is any significant DNS lookup delay. The reasons are simple: The lookup was done when the user logged in, so the DNS server has the answer in its cache. And even if not, if anybody did finger/who/w in the recent past, that caused the answer to be brought into the name server's cache. (I do run BIND with negative caching enabled, which probably helps keep delays short for reverse lookups where some name server is not responding.) Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 1:21:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from vanessa.eliuk.org (sec2d4.dial.uniserve.ca [204.244.165.67]) by hub.freebsd.org (Postfix) with ESMTP id BDA5B1549A for ; Mon, 12 Apr 1999 01:21:28 -0700 (PDT) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.3/8.9.3) with ESMTP id BAA03793 for ; Mon, 12 Apr 1999 01:19:12 -0700 (PDT) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 12 Apr 1999 01:18:41 -0700 (PDT) From: "Kevin G. Eliuk" To: current@FreeBSD.ORG Subject: Netscape dumps core after XFree86 build Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, On Apr10 I rebuilt the XFree86 Port with aout compatibility libraries running current of Apr04. Immediately following Netscape Communicator would dump core with a bus error. I'm not sure if this is relevant or not, but when it dumps core the core file name is truncated. cagey@vanessa$ netscape Bus error cagey@vanessa$ ll *.core -rw------- 1 cagey cagey - 1425408 Apr 11 23:46 navigator-4.5.bi.core and log output gives pid 322 (navigator-4.5.bi), uid 1000: exited on signal 10 I installed linux-netscape-4.08 and it opens with bus error or signal 10. I have rebuilt world early today, built flawlessy, but have not built XFree as of yet. Could I expect any difference from a rebuilt XFree? I could supply requested data from ktrace or gdb though it should be easy to duplicate the same. -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 1:31:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from vanessa.eliuk.org (sec2d38.dial.uniserve.ca [204.244.165.101]) by hub.freebsd.org (Postfix) with ESMTP id 236391548B for ; Mon, 12 Apr 1999 01:31:49 -0700 (PDT) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.3/8.9.3) with ESMTP id BAA03916 for ; Mon, 12 Apr 1999 01:29:33 -0700 (PDT) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 12 Apr 1999 01:29:03 -0700 (PDT) From: "Kevin G. Eliuk" To: current@freebsd.org Subject: Re: Netscape dumps core after XFree86 build In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Kevin G. Eliuk wrote: > > I installed linux-netscape-4.08 and it opens with bus error or signal 10. ^^^^ That should be "without" -- Regards, Kevin G. Eliuk Box 67, Granthams Landing, BC VON 1X0 (604)886-4040 Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 2: 7:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 9AFCE1527D for ; Mon, 12 Apr 1999 02:07:47 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id FAA05906; Mon, 12 Apr 1999 05:04:55 -0400 (EDT) (envelope-from luoqi) Date: Mon, 12 Apr 1999 05:04:55 -0400 (EDT) From: Luoqi Chen Message-Id: <199904120904.FAA05906@lor.watermarkgroup.com> To: blapp@attic.ch, freebsd-current@FreeBSD.ORG Subject: Re: Panic from today's current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The kernel-configfile and dmesg-output is available from: > http://www.attic.ch/fuchur_kernel.html > > panic at: generic_bcopy+0x1a repe movsl (%esi), %es:(%edi) > > db> trace > generic_bcopy(c02cc380,c7bb9b1f,0,a,0) at generic_bcopy+0x1a > sccnputc(cff,1,c7bb9b80,c016c066) at sccnputc+0x180 > cnputc(a,0,0,a,c7bb9bcc) at cnputc+0x3d > putchar(a,c7bb9bf0) at putchar+0xa6 > kvprintf(c028da63,c016bfc0,c7bb9bf0,a,c7bb9c04) at kvprintf+0x64 > printf(c028da49,80000000,c1159b00,a8,c7bc3e60) at printf+0x3d > trap(10,10,a8,c1159b00,c7bb9ce8) at trap+0x462 > calltrap() at calltrap+0x3c > --- trap 0x13, eip = 0xc7bb9c68, ebp = 0xc7bb9ce8 --- Trap 19 (0x13) is NMI, this problem doesn't seem to be software related. > ufs_lookup(c7bb9d2c,c7bb9d40,c0184946,c7bb9d2c,c79ba00e) at ufs_lookup+0x353 > ufs_vnoperate(c7bb9d2c,c79ba00e,c746e580,c7bb9f10,c746e580 at ufs_vnoperate+0x15 > vfs_cache_lookup(c7bb9d84,c7bb9d94,c0186d2b,c7bb9d84,c7470e00) at vfs_cache_lookup+0x26a > ufs_vnoperate(c7bb9d84,c7470e00,c7bb9f10,c1303a00,0) at ufs_vnoperate+0x15 > lookup(c7bb9eec,0,c7bb9f84,fffffffc,c7b757f0) at lookup+0x2af > namei(c7bb9eec,0,c7bb9f84,fffffffc,c02df240) at namei+0x291 > vn_open(c7bb9eec603,1a4c7bc3e60,c029d3f0) at vn_open+0x59 > open(c7bc3e60,c7bb9f84,8070aa0,10,8085680) at open+0xbb > syscall(2f,2f,8085680,10,bfbfcb84) at syscall+0x182 > Xint0x80_syscall() at Xint0x80_syscall+0x4c > > It seams to be ufs-related. Does anybody know what happened ? > > Martin > > Martin Blapp, mblapp@solnet.ch > ---------------------------------------------- > SolNet, Internet Solution Provider > Bechburgstrasse 29, 4528 Zuchwil, Switzerland > Phone: +41 32 686 82 82, Fax: +41 32 685 96 13 > ---------------------------------------------- > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 2:39: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3B96614F0C for ; Mon, 12 Apr 1999 02:38:59 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA01279; Mon, 12 Apr 1999 18:36:37 +0900 (JST) Message-ID: <37116096.5C9E4A83@newsguy.com> Date: Mon, 12 Apr 1999 11:55:18 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Oleg Ogurok Cc: freebsd-current@FreeBSD.ORG Subject: Re: colour 'ls' References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oleg Ogurok wrote: > > Have you ever thought about putting colour listing in 'ls' command? First > I saw it in linux and then there's a program called 'gnuls' in ports. It > looks really cool when you do: > gnuls --color=yes > Files print as usual and directories print in colour ;-) > I put ls as a symbolic link to gnuls, but every time I make world, the old > 'ls' puts back ;-) There is also linuxls and colorls. Just put in your .profile: alias ls="gnuls --color=yes" -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 3: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id 996B414F0C for ; Mon, 12 Apr 1999 03:02:33 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 25382 invoked by uid 1001); 12 Apr 1999 10:00:14 -0000 To: Warner Losh Cc: current@freebsd.org Subject: Re: DoS from local users (fwd) References: <199904102057.PAA27724@home.dragondata.com> <199904112100.PAA05104@harmony.village.org.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 12 Apr 1999 12:59:59 +0300 In-Reply-To: Warner Losh's message of "12 Apr 1999 02:39:50 +0300" Message-ID: <86k8vignvk.fsf@not.demophon.com> Lines: 35 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message <199904102057.PAA27724@home.dragondata.com> Kevin Day writes: > : i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid > : 1002 starts up one process. Uid 1002's process gets 50% cpu, and uid 1001's > : 40 processes get 50% cpu shared between them. > > I've seen some experimental patches in the past that try to do just > this. However, there are some problems. What if uid 1002's process > does a sleep. Should the 40 processes that 1001 just get 50% of the > cpu? Or should there be other limits. It turns into an interesting > research problem in a hurry. That's a simple matter of implementation decisions. Naturally there's hardly ever a good reason to keep a processor idle, so the limits should only apply when the processor would not otherwise be idle. How this affects the amount of runtime the processes get later depends on how you compute percentages. An example approach is what the class scheduling feature in Digital UNIX does. I'll describe it from what I remember from playing with it a couple of years ago, so all of this is only true IIRC. It has some fixed scheduling period, for which it allocates cycles for that period to scheduling classes (threads, users, groups, whatever) based on the percentage limits. The only addition to the scheduler is having threads consume these cycles from the scheduling classes. When those cycles have been used up, threads in that class are not allowed to run. If an eligible processor would otherwise be idle, they may be allowed to run despite this (the behavior is configurable in some scope, I can't remember whether it was global or per class). The class scheduler in Digital UNIX is, in many respects, a kludge, and I'm not recommending that FreeBSD implement a similar mechanism. But it is semantically "sane", and unlikely to cause additional problems when configured with reasonable parameters. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 5:47:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 5E0E8154F0 for ; Mon, 12 Apr 1999 05:47:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id OAA16924; Mon, 12 Apr 1999 14:45:09 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id KAA00288; Thu, 8 Apr 1999 10:55:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: /sys/boot, egcs vs. gcc, -Os In-reply-to: Your message of "Wed, 07 Apr 1999 17:49:04 PDT." <199904080049.RAA76863@vashon.polstra.com> Date: Thu, 08 Apr 1999 10:55:08 +0200 Message-ID: <286.923561708@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904080049.RAA76863@vashon.polstra.com>, John Polstra writes: >In article , Jeroen >Ruigrok/Asmodai wrote: > >> This raises an interesting point I think. Do we need to maintain >> gcc/egcs compatibility? Or do we, since we track CURRENT, say: >> "alas, that's progression for ye?" > >Yep, alas, that's progression for ye. We have never supported mix >& match of sourceballs from different releases. We do our best >to support running old executables on newer systems, but that's a >completely different issue. > >> Has there been an `official' consensus reached about this from core or >> commiters? > >I am only speaking for John Polstra, a compiler guy, here. I agree. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 6:48: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (Postfix) with ESMTP id 2738414A2E for ; Mon, 12 Apr 1999 06:47:55 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id IAA10848; Mon, 12 Apr 1999 08:45:30 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.9.3/8.9.3) id IAA03655; Mon, 12 Apr 1999 08:40:47 -0500 (CDT) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Date: Mon, 12 Apr 1999 08:40:45 -0500 (CDT) To: Dag-Erling Smorgrav Cc: Oleg Ogurok , freebsd-current@FreeBSD.ORG Subject: Re: colour 'ls' In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14097.63258.197376.207383@zuhause.mn.org> Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Oleg Ogurok writes: > > I put ls as a symbolic link to gnuls, but every time I make world, the old > > 'ls' puts back ;-) > > Don't do that. Instead, do: > > # cd /usr/local/bin > # ln -s gnuls ls > > and fix your PATH so /usr/local/bin comes before /bin. Better yet, set up an alias of ls = "ls --color" when the shell is an interactive shell, and then you don't get the color escape sequences when running scripts or if you escape ls with \ls when outputting to a file. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 8: 8:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 2607B14E7A for ; Mon, 12 Apr 1999 08:08:12 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id LAA70241; Mon, 12 Apr 1999 11:05:21 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904121505.LAA70241@misha.cisco.com> Subject: Re: swap-related problems In-Reply-To: <199904120400.VAA15072@apollo.backplane.com> from Matthew Dillon at "Apr 11, 1999 09:00:24 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Mon, 12 Apr 1999 11:05:21 -0400 (EDT) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon once wrote: > If you unset the datasize limit and the program does not exceed > the maximum system-supported datasize limit, malloc() should not > return NULL even if the system is out of swap. Can you explain why? Our malloc(3) is a little fuzzy as to the circumstances under which malloc will fail, but on Solaris, it is more explicit: RETURN VALUES If there is no available memory, malloc(), realloc(), memalign(), valloc(), and calloc() return a null pointer. I consider being out-of-swap as having "no available memory". Wouldn't you? Now, for better diagnostics and for a possibility of smarter applications, they also have: ERRORS If malloc(), calloc(), or realloc() returns unsuccessfully, errno will be set to indicate the following: ENOMEM size bytes of memory exceeds the physical limits of your system, and cannot be allo- cated. EAGAIN There is not enough memory available AT THIS POINT IN TIME to allocate size bytes of memory; but the application could try again later. > The correct solution is to set a maximum datasize limit. That is > what it is there for. I generally unlimit the datasize for root > and set it to around 64MB for all other users. Wait, I want to give all the memory available to a program, but I want it to be NOTIFIED when no more memory is left. True, I can set the limit to the actual amount of my swap, but that would be hard to maintain and still does not solve a problem of running together with some other memory consuming application. The existing situation is sort of like killing a program for trying to write to disk in excess of the user's quota, or for being ready to RUN when the load is 1. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 8:32:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 64BDC15174 for ; Mon, 12 Apr 1999 08:32:05 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 77A781F4F; Mon, 12 Apr 1999 23:29:43 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Kevin G. Eliuk" Cc: current@freebsd.org Subject: Re: Netscape dumps core after XFree86 build In-reply-to: Your message of "Mon, 12 Apr 1999 01:29:03 MST." Date: Mon, 12 Apr 1999 23:29:43 +0800 From: Peter Wemm Message-Id: <19990412152946.77A781F4F@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kevin G. Eliuk" wrote: > On Mon, 12 Apr 1999, Kevin G. Eliuk wrote: > > > > I installed linux-netscape-4.08 and it opens with bus error or signal 10. > ^^^^ > That should be "without" I've applied Bruce Evans's patch to egcs to work around (yet another) problem with our crappy antique a.out gas. After rebuilding egcs, and rebuilding the a.out XFree86 libraries, netscape works again. I was having the same problem as you until then. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 8:36: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 60C0B155AC for ; Mon, 12 Apr 1999 08:35:59 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id QAA10052; Mon, 12 Apr 1999 16:33:36 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA02356; Mon, 12 Apr 1999 08:38:20 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904120738.IAA02356@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Watson Cc: Rahul Dhesi , freebsd-current@FreeBSD.org Subject: Re: showing full host names in output from who/finger/last In-reply-to: Your message of "Sun, 11 Apr 1999 19:05:30 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Apr 1999 08:38:19 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > I got sick of seing "invalid hostname" in my wtmps a while ago on my 2.x > machines. That is an exceptionally useless piece of behavior, if you ask > me. Sshd writes out IPs and I find that to be much more consistent (and > useful). Sshd gets it wrong though. It gets the full hostname and then a freebsd patch changes that to an IP if the name is >UT_HOSTSIZE. In -current, this behaviour has been changed to call trimdomain() (trimdomain() has just been documented too), and if the result still doesn't fit in UT_HOSTSIZE it reverts to an IP number. This should be pretty consistent for all the stuff in libexec now too. > Robert N Watson > > robert@fledge.watson.org http://www.watson.org/~robert/ > PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C > > Carnegie Mellon University http://www.cmu.edu/ > TIS Labs at Network Associates, Inc. http://www.tis.com/ > Safeport Network Services http://www.safeport.com/ -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 9: 8:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 5368115525 for ; Mon, 12 Apr 1999 09:07:53 -0700 (PDT) (envelope-from ip@albatross.mcc.ac.uk) Received: from albatross.mcc.ac.uk ([130.88.202.16]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for current@freebsd.org id 10WjD0-0002UJ-00; Mon, 12 Apr 1999 17:05:14 +0100 Received: (from ip@localhost) by albatross.mcc.ac.uk (8.9.2/8.9.1) id RAA47641 for current@freebsd.org; Mon, 12 Apr 1999 17:05:14 +0100 (BST) (envelope-from ip) From: Ian Pallfreeman Message-Id: <199904121605.RAA47641@albatross.mcc.ac.uk> Subject: Bad, reliable crash: Julian's "oltr" stuff & ARP To: current@freebsd.org Date: Mon, 12 Apr 1999 17:05:13 +0100 (BST) Reply-To: ip@mcc.ac.uk X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My -current trashbox is having some pretty severe problems which seem to stem from the token ring additions on March 10th. The box in question wouldn't stay up for more than a few minutes. ``savecore'' isn't working for me right now, but I've managed to delete a single line of code which lets the box stay up long enough for me to do a make world and get to grips with all this EGCS, uh, fun. This isn't a true solution, obviously. The ethernet segment to which the box is connected has lots of non-IP traffic (DECNET, Novell, etc), but I didn't expect to find token ring stuff on it. :-) Ian. *** if_ether.c.orig Mon Apr 12 16:11:12 1999 --- if_ether.c Mon Apr 12 16:13:22 1999 *************** *** 435,442 **** panic("arpintr"); if (m->m_len >= sizeof(struct arphdr) && (ar = mtod(m, struct arphdr *)) && ! (ntohs(ar->ar_hrd) == ARPHRD_ETHER || ! ntohs(ar->ar_hrd) == ARPHRD_IEEE802) && m->m_len >= sizeof(struct arphdr) + 2 * ar->ar_hln + 2 * ar->ar_pln) --- 435,441 ---- panic("arpintr"); if (m->m_len >= sizeof(struct arphdr) && (ar = mtod(m, struct arphdr *)) && ! ntohs(ar->ar_hrd) == ARPHRD_ETHER && m->m_len >= sizeof(struct arphdr) + 2 * ar->ar_hln + 2 * ar->ar_pln) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc017e590 stack pointer = 0x10:0xc02248d8 frame pointer = 0x10:0xc0224928 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres type 0x1b = DPL 0, press 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = kernel: type 12 trap, code=0 Stopped at in_arpinput+0x264: cmpb $0,0x8(%ecx) db> tr in_arpinput(c0744100,0,0,c01ee601,c01ee5a3) at in_arpinput+0x264 arpintr(c01ee5a3,80000000,10,10,0) at arpintr+0xb4 swi_net_next() at swi_net_next db> show registers cs 0x8 ds 0x7e8b0010 es 0x10 ss 0x10 eax 0x600 ecx 0 edx 0 ebx 0xc0a02490 esp 0xc02255ec __set_pcidevice_set_sym_ide_pci_device+0x2fc0 ebp 0xc022563c __set_pcidevice_set_sym_ide_pci_device+0x3010 esi 0xc073c820 edi 0xc0a2d600 eip 0xc017e3d4 in_arpinput+0x264 efl 0x10246 in_arpinput+0x264: cmpb $0,0x8(%ecx) db> panic Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Mon Apr 12 16:13:32 BST 1999 ip@trauma:/usr/src/sys/compile/TRAUMA Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400910920 Hz CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127995904 (124996K bytes) Preloaded elf kernel "kernel" at 0xc0291000. Pentium Pro MTRR support enabled, default memory type is uncacheable ccd0: Concatenated disk driver Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 ahc0: rev 0x00 int a irq 10 on pci0.15.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x05 int a irq 12 on pci0.17.0 fxp0: Ethernet address 00:90:27:10:2b:ea Probing for devices on PCI bus 1: vga0: rev 0x01 int a irq 255 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4121MB (8440992 sectors), 8374 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): wd3: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 ppi0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 2 seconds for SCSI devices to settle changing rootda1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 1001MB (2051000 512 byte sectors: 64H 32S/T 1001C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) device to wd0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 9:23:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5AFBD14CA7 for ; Mon, 12 Apr 1999 09:23:44 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id MAA19412; Mon, 12 Apr 1999 12:19:30 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Mon, 12 Apr 1999 12:19:30 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Brian Somers Cc: Rahul Dhesi , freebsd-current@FreeBSD.org Subject: Re: showing full host names in output from who/finger/last In-Reply-To: <199904120738.IAA02356@keep.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Brian Somers wrote: > [.....] > > I got sick of seing "invalid hostname" in my wtmps a while ago on my 2.x > > machines. That is an exceptionally useless piece of behavior, if you ask > > me. Sshd writes out IPs and I find that to be much more consistent (and > > useful). > > Sshd gets it wrong though. It gets the full hostname and then a > freebsd patch changes that to an IP if the name is >UT_HOSTSIZE. I don't use the FreeBSD patched version, as I use the version with the KerberosIV patches (unfortunately the FreeBSD port doesn't do that, but I don't have time just now to make it do that :-). It seems to put the IP address into the wtmp correctly. But anyhow; my preference is still to either a) using only IP addresses, or b) using two fields, one for each. Given that connections logically come from IP addresses, performing a transformation based on an unreliable insecure mechanism like DNS seems like a bad idea. It's convenient to look at (hence a look at option b). Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 10: 7:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 092FA14CAE for ; Mon, 12 Apr 1999 10:07:20 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id NAA21873; Mon, 12 Apr 1999 13:04:54 -0400 (EDT) (envelope-from lile@stdio.com) Date: Mon, 12 Apr 1999 13:04:54 -0400 (EDT) From: Larry Lile To: ip@mcc.ac.uk Cc: current@FreeBSD.ORG Subject: Re: Bad, reliable crash: Julian's "oltr" stuff & ARP In-Reply-To: <199904121605.RAA47641@albatross.mcc.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just so Julian doesn't get blamed here, I was the one who wrote the Olicom "oltr" driver and made the arp changes. Julian was just nice enough to commit them. The only thing I can figure, as I can't tell exactly what caused it to punt, is that you received a token-ring arp packet that is somewhat damaged. Is there a token-ring<->ethernet bridge on your network? What was it doing in in_arpinput when it panic'd? Larry Lile lile@stdio.com On Mon, 12 Apr 1999, Ian Pallfreeman wrote: > My -current trashbox is having some pretty severe problems which seem to > stem from the token ring additions on March 10th. The box in question > wouldn't stay up for more than a few minutes. > > ``savecore'' isn't working for me right now, but I've managed to delete a > single line of code which lets the box stay up long enough for me to do a > make world and get to grips with all this EGCS, uh, fun. This isn't a true > solution, obviously. > > The ethernet segment to which the box is connected has lots of non-IP traffic > (DECNET, Novell, etc), but I didn't expect to find token ring stuff on it. :-) > > Ian. > > *** if_ether.c.orig Mon Apr 12 16:11:12 1999 > --- if_ether.c Mon Apr 12 16:13:22 1999 > *************** > *** 435,442 **** > panic("arpintr"); > if (m->m_len >= sizeof(struct arphdr) && > (ar = mtod(m, struct arphdr *)) && > ! (ntohs(ar->ar_hrd) == ARPHRD_ETHER || > ! ntohs(ar->ar_hrd) == ARPHRD_IEEE802) && > m->m_len >= > sizeof(struct arphdr) + 2 * ar->ar_hln + 2 * ar->ar_pln) > > --- 435,441 ---- > panic("arpintr"); > if (m->m_len >= sizeof(struct arphdr) && > (ar = mtod(m, struct arphdr *)) && > ! ntohs(ar->ar_hrd) == ARPHRD_ETHER && > m->m_len >= > sizeof(struct arphdr) + 2 * ar->ar_hln + 2 * ar->ar_pln) > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x8 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc017e590 > stack pointer = 0x10:0xc02248d8 > frame pointer = 0x10:0xc0224928 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres type 0x1b > = DPL 0, press 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrupt mask = > kernel: type 12 trap, code=0 > Stopped at in_arpinput+0x264: cmpb $0,0x8(%ecx) > db> tr > in_arpinput(c0744100,0,0,c01ee601,c01ee5a3) at in_arpinput+0x264 > arpintr(c01ee5a3,80000000,10,10,0) at arpintr+0xb4 > swi_net_next() at swi_net_next > db> show registers > cs 0x8 > ds 0x7e8b0010 > es 0x10 > ss 0x10 > eax 0x600 > ecx 0 > edx 0 > ebx 0xc0a02490 > esp 0xc02255ec __set_pcidevice_set_sym_ide_pci_device+0x2fc0 > ebp 0xc022563c __set_pcidevice_set_sym_ide_pci_device+0x3010 > esi 0xc073c820 > edi 0xc0a2d600 > eip 0xc017e3d4 in_arpinput+0x264 > efl 0x10246 > in_arpinput+0x264: cmpb $0,0x8(%ecx) > db> panic > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #1: Mon Apr 12 16:13:32 BST 1999 > ip@trauma:/usr/src/sys/compile/TRAUMA > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 400910920 Hz > CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping=2 > Features=0x183f9ff > real memory = 134217728 (131072K bytes) > avail memory = 127995904 (124996K bytes) > Preloaded elf kernel "kernel" at 0xc0291000. > Pentium Pro MTRR support enabled, default memory type is uncacheable > ccd0: Concatenated disk driver > Probing for devices on PCI bus 0: > chip0: rev 0x02 on pci0.0.0 > chip1: rev 0x02 on pci0.1.0 > chip2: rev 0x02 on pci0.7.0 > ide_pci0: rev 0x01 on pci0.7.1 > chip3: rev 0x02 on pci0.7.3 > ahc0: rev 0x00 int a irq 10 on pci0.15.0 > ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs > fxp0: rev 0x05 int a irq 12 on pci0.17.0 > fxp0: Ethernet address 00:90:27:10:2b:ea > Probing for devices on PCI bus 1: > vga0: rev 0x01 int a irq 255 on pci1.0.0 > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <16 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A, console > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 4121MB (8440992 sectors), 8374 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): > wd2: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S > wdc1: unit 1 (wd3): > wd3: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S > ppc0 at 0x378 irq 7 on isa > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > plip0: on ppbus 0 > ppi0: on ppbus 0 > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > Waiting 2 seconds for SCSI devices to settle > changing rootda1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da1: 1001MB (2051000 512 byte sectors: 64H 32S/T 1001C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) > device to wd0s1a > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 10:59:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id A4FF014CF6; Mon, 12 Apr 1999 10:59:03 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 7DE5F1F4F; Tue, 13 Apr 1999 01:56:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org, committers@freebsd.org Subject: About that 'new-bus' stuff. Date: Tue, 13 Apr 1999 01:56:41 +0800 From: Peter Wemm Message-Id: <19990412175644.7DE5F1F4F@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As some have become aware, we have created a small sandbox repository alongside (but seperate to) the main FreeBSD sources. I've been asked a few times for info on what it is, so here's a quick summary. First, the background.. The original 386BSD and FreeBSD configuration interface was purely static. ie: you filled in your config(8) file, ran config, compiled the kernel and you were done. It pretty much supported ISA devices only. Back then, that was quite reasonable as the devices stayed put and required a considerable amount of effort to change. But it's not 1992 anymore. That nice cozy picture has changed somewhat. Now, we've got multi-layer busses and all sorts of dynamic stuff that changes on the fly (usb, pccard, cardbus being prime examples). You end up with scsi controllers on parallel ports, parallel printer bridges on usb, etc. As well, nearly all of these devices are self identifying. PCI, PnP, EISA etc all carry identification so the configuration can be determined by asking the device directly. This does not fit well into our nice static config system any more. The average system these days has very few or perhaps even no devices that require configuration "assistance". There was also the problem of duplication of information. Drivers in the kernel were written to attach to specific busses and the exact same information had to be duplicated in the user's config file. Some alternatives (the original config.new, for example) were worse because they added another copy - various Makefiles and rule files needed another set of information to say the same thing again. (As an aside, NetBSD has done wonderful things to config.new, but it wasn't the direction we wanted to go). And then along came the Alpha port. Rather than being a descendent of the old way of doing things, it was done from a different direction as it had no isa-like bus to fight with. It's configuration system is dynamic and "hint" based. The only place that hierarchy is enforced is in the drivers themselves. You don't need to duplicate that info in makefiles or config files. But you *can* be specific about something if you want. For example, if you wanted to wire da2 to a specific LUN on a specific bus on a specific controller, you could. And then along came the in-kernel linker. The old driver mechanism on the i386 cannot cope with this without serious hackery. Various people decided to take a shot at adapting the existing new-bus stuff to the i386. Well, it works very well, but isn't quite complete. Since the people involved were having synchronization problems and having trouble with large patchsets, we decided to set up a shared repository. Since the aim was that the i386 port would use this, it was closely linked with the freebsd repository and shared the same commit messages (the plan was that the developers would need to know about it and that others who were watching could see what was going on too). Anyway, here's the basic objectives: - remove (entirely) the need for static configuration, but still have *explicit* control when and as needed. If the if_de driver only works on a pci bus, then there's no point requiring you to configure it specifically to attach to a pci bus in the kernel config file - the minimum information required is that you want it. :-) Obviously an if_ed ISA driver needs hints about where to probe, but there is no reason why it can't have a built-in set of ports to try if the user chooses not to specify one. Of course, it will use the users settings if they are given. - ultimately, static configuration would be replaced with a boot-time dynamic method. ie: you will be able to specify things like isa IO and irq settings in a config file in /boot. You won't need to recompile to adjust the kernel settings, just edit the config file and reboot. - It may well turn out that even a reboot isn't required and that the resources for isa configuration can be changed at runtime and the device re-probed with the new settings. - userconfig would logically move to a fourth script in /boot, if not then it would merely be a resource editor. - full resource management. There is a single manager for resources like ports, interrupts, memory mappings etc. This replaces the *horrible* kludges that try and figure out what's been used at present. - minimize the disruption and workload for the developers. Backwards compatability shims work quite nicely and old drivers work mostly without modifications and interface with the resource manager via the shims and new mechanisms. (we could implement UDI this way!). No bombshells blowing -current out of the water with major loss of functionality. - *full* loadable module support, for all the busses. (This won't work for linker set based drivers obviously, but with some tinkering, an isa_device style driver could be made loadable, or preloaded via loader(8) at least.) - drastically reduce the role for config(8) or some replacement. Ideally, once static configuration is loadable, it's sole role will be for managing a build of a choice of components with given compile options, both as a unified kernel and as loadable modules. (A build of the kernel should do both the kernel and the kld's at the same time so they are in sync) - the opportunity for other interface shims to be written. It might be possible to write a netbsd-style newconfig interface shim like the existing old-style isa and pci shims. This would go part of the way to being able to use their drivers with less hassles. (There will be enough fun due to differences in bus_space and bus_dma, but that's another issue) - I'm sure there's a million things I've forgotten.. Right now, the core functionality is operating nicely, but there are a few key missing bits. Specifically, wd.c doesn't (and can't) build, it needs changes like the fd.c driver. The ISA PnP and EISA code hasn't been updated to use the new interfaces. (Soren's new ata driver works). The pccard etc driver compiles but has not been updated yet. The direction the pccard stuff will go in isn't clear yet. Hopefully Doug won't shoot me for misrepresenting something. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 11:24:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 3EDBC15568 for ; Mon, 12 Apr 1999 11:23:27 -0700 (PDT) (envelope-from schuerge@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id UAA29184 for ; Mon, 12 Apr 1999 20:20:46 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id UAA07605 for ; Mon, 12 Apr 1999 20:20:42 +0200 (CEST) Received: (from schuerge@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id UAA09661 for freebsd-current@freebsd.org; Mon, 12 Apr 1999 20:20:37 +0200 (CEST) From: Thomas Schuerger Message-Id: <199904121820.UAA09661@wurzelausix.cs.uni-sb.de> Subject: cvsup To: freebsd-current@freebsd.org Date: Mon, 12 Apr 1999 20:20:36 +0200 (CEST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Is there any way to make cvsup update its GUI properly? The window is almost dead when cvsup is performing updates, e.g. cvsup will update the window's contents very infrequently, which is rather anoying. Perhaps it would be a good idea to put GUI handling into a separate thread. Ciao, Thomas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 11:26:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B724615568 for ; Mon, 12 Apr 1999 11:26:52 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id OAA20062; Mon, 12 Apr 1999 14:23:29 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Mon, 12 Apr 1999 14:23:29 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: N Cc: freebsd-current@freebsd.org Subject: Re: showing full host names in output from who/finger/last In-Reply-To: <9904122015390.9313-100000@liquid.tpb.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, N wrote: > Hi, > > > I don't use the FreeBSD patched version, as I use the version with the > > KerberosIV patches (unfortunately the FreeBSD port doesn't do that, but I > > don't have time just now to make it do that :-). It seems to put the IP > > address into the wtmp correctly. > > Are those patches freely available somewhere? Niels, Dug Song's kerberosiv patches are available at http://www.monkey.org/~dugsong/ssh-afs-kerberos.html He also has various other kerberos patches on his page there. I submitted a fix or two a little while ago to correct some problems with multi-homed hosts. I imagine they're in there at this point, but I haven't checked. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 11:42: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (Postfix) with ESMTP id 32C5514EA2 for ; Mon, 12 Apr 1999 11:41:38 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.9.3/8.9.3) with ESMTP id OAA13323 for ; Mon, 12 Apr 1999 14:38:49 -0400 (EDT) Date: Mon, 12 Apr 1999 14:38:49 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@freebsd.org Subject: kernel size over the last week Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just built a kernel, from sources cvsupped last night. It's over 2 megs in size, compared to 1.3 megs for a kernel built from the same config file four days ago. Is this due to the change in the debugging symbol policy? file(1) reports both kernels as 'ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped'. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 11:45: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 007BF14D0F; Mon, 12 Apr 1999 11:44:57 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA45566; Mon, 12 Apr 1999 19:46:04 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 19:46:04 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: current@freebsd.org, committers@freebsd.org Subject: Re: About that 'new-bus' stuff. In-Reply-To: <19990412175644.7DE5F1F4F@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Apr 1999, Peter Wemm wrote: > [...] > Right now, the core functionality is operating nicely, but there are a few > key missing bits. Specifically, wd.c doesn't (and can't) build, it needs > changes like the fd.c driver. The ISA PnP and EISA code hasn't been > updated to use the new interfaces. (Soren's new ata driver works). The > pccard etc driver compiles but has not been updated yet. The direction > the pccard stuff will go in isn't clear yet. I should add that SMP machines will not work with the new-bus repository just yet since I haven't got my head around the apic interrupt remapping thing yet. An SMP machine with a UP kernel would work as a stopgap. > > Hopefully Doug won't shoot me for misrepresenting something. :-) Of course not :-) The only thing I would change in the history is that the kernel linker work pre-dates the alpha port and that the main reason I wrote it was to support the new driver model. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 11:52:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id D2324155C0 for ; Mon, 12 Apr 1999 11:51:55 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA21346; Mon, 12 Apr 1999 20:31:00 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id UAA00960; Mon, 12 Apr 1999 20:06:32 +0200 (CEST) From: Wilko Bulte Message-Id: <199904121806.UAA00960@yedi.iaf.nl> Subject: Re: Panic from today's current In-Reply-To: <199904120904.FAA05906@lor.watermarkgroup.com> from Luoqi Chen at "Apr 12, 1999 5: 4:55 am" To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Mon, 12 Apr 1999 20:06:32 +0200 (CEST) Cc: blapp@attic.ch, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Luoqi Chen wrote ... > > The kernel-configfile and dmesg-output is available from: > > http://www.attic.ch/fuchur_kernel.html > > > > panic at: generic_bcopy+0x1a repe movsl (%esi), %es:(%edi) > > > > db> trace > > generic_bcopy(c02cc380,c7bb9b1f,0,a,0) at generic_bcopy+0x1a > > sccnputc(cff,1,c7bb9b80,c016c066) at sccnputc+0x180 > > cnputc(a,0,0,a,c7bb9bcc) at cnputc+0x3d > > putchar(a,c7bb9bf0) at putchar+0xa6 > > kvprintf(c028da63,c016bfc0,c7bb9bf0,a,c7bb9c04) at kvprintf+0x64 > > printf(c028da49,80000000,c1159b00,a8,c7bc3e60) at printf+0x3d > > trap(10,10,a8,c1159b00,c7bb9ce8) at trap+0x462 > > calltrap() at calltrap+0x3c > > --- trap 0x13, eip = 0xc7bb9c68, ebp = 0xc7bb9ce8 --- > > Trap 19 (0x13) is NMI, this problem doesn't seem to be software related. NMI.. could be a RAM parity error or somebody/something fooling around with the IOCHKN line on the ISA bus. Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 11:59:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id E903715B10 for ; Mon, 12 Apr 1999 11:59:45 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (async3-46.iptelecom.net.ua [212.42.68.237]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id VAA14135; Mon, 12 Apr 1999 21:57:40 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37124221.B8D7C471@altavista.net> Date: Mon, 12 Apr 1999 21:57:37 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey I have pretty the same problems on my 4.0 cvsup'ed and builded few days ago! As NFS server I have 3.1-stable box. Sincerely, Maxim Sobolev Alfred Perlstein wrote: > Hey, i was just doing a kernel compile over NFS and i have a weird > situtation. After compiling everything the linker barfs on linking. > > gensetdefs: cd9660_bmap.o: not an ELF file > > for about 12 files... > > the compile is being done on a laptop that has my desktop's src dir > NFS mounted. > > the card in the laptop is a 3comIII and the dekstop a pn0 > > doing a 'file cd9660_bmap.o' on laptop (NFS client) gives me a > cd9660_bmap.o: MS Windows COFF Unknown CPU > > while on the server: > strlen.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stri > > it seems my client is having a really tough time with these files, i have > copied the files that the client has corrupted to localdisk but now > they seem fine... > > the client laptop is unable to link the kernel it's getting tons of > corrupted data is seems, on the server i am able to link the kernel just > fine. > > i'm using the default NFS mounts and no nfsiod. > > enabling nfsiod didn't help, however unmounting the NFS share and > remounting seems to have fixed it.... > > i guess i should have taken a crash dump when the system was all > hosed but it's fine now... *sigh* > > Alfred Perlstein - Admin, coder, and admirer of all things BSD. > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 4.0-current > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 12:19:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id 752E515053; Mon, 12 Apr 1999 12:19:38 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id OAA02852; Mon, 12 Apr 1999 14:16:53 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 12 Apr 1999 14:16:52 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: chat@freebsd.org Subject: Re: DoS from local users (fwd) X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14098.17765.31841.546055@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : "What was their user name again?" : *click xterm click* : ps aux | grep ^user | wc -l : "Hmm, you're right, fifty processes called 'cpuwaster'." : rmuser user : "They've been eliminated, thank you for letting us know of problems you have!" : : It's called "being a sysadmin". If someone's abusing the machine, delete em. [ Redirected to chat ] There are several points which I would like to make in response to this posting. 1) cpuwaster may be solving a significant problem. One man's cpuwaster is another man's breadandbutter. 2) Adding useful new scheduling policy options to the system allows a good sysadmin to be a better sysadmin. That's a Good Thing. 3) One man's sysadmin is another man's asshole. (Made you think, didn't I?) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 12:43: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3E30814D0A; Mon, 12 Apr 1999 12:43:04 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA36262; Mon, 12 Apr 1999 13:40:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA02397; Mon, 12 Apr 1999 13:40:27 -0600 (MDT) Message-Id: <199904121940.NAA02397@harmony.village.org> To: Peter Wemm Subject: Re: About that 'new-bus' stuff. Cc: current@FreeBSD.org, committers@FreeBSD.org In-reply-to: Your message of "Tue, 13 Apr 1999 01:56:41 +0800." <19990412175644.7DE5F1F4F@spinner.netplex.com.au> References: <19990412175644.7DE5F1F4F@spinner.netplex.com.au> Date: Mon, 12 Apr 1999 13:40:27 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990412175644.7DE5F1F4F@spinner.netplex.com.au> Peter Wemm writes: : to being able to use their drivers with less hassles. (There will be : enough fun due to differences in bus_space and bus_dma, but that's : another issue) I know that many people would like to see bus_space and bus_dma reimported from NetBSD. As far as I know, there is no compelling reason to have them be different. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 12:50:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D581D14BFF; Mon, 12 Apr 1999 12:50:42 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA47346; Mon, 12 Apr 1999 20:51:53 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Apr 1999 20:51:52 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: Peter Wemm , current@freebsd.org, committers@freebsd.org Subject: Re: About that 'new-bus' stuff. In-Reply-To: <199904121940.NAA02397@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Warner Losh wrote: > In message <19990412175644.7DE5F1F4F@spinner.netplex.com.au> Peter Wemm writes: > : to being able to use their drivers with less hassles. (There will be > : enough fun due to differences in bus_space and bus_dma, but that's > : another issue) > > I know that many people would like to see bus_space and bus_dma > reimported from NetBSD. As far as I know, there is no compelling > reason to have them be different. I don't think there are many differences with bus_space. I don't know about bus_dma though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 13: 3: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 28A1D14F62; Mon, 12 Apr 1999 13:02:59 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id MAA24645; Mon, 12 Apr 1999 12:59:44 -0700 Date: Mon, 12 Apr 1999 12:59:44 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Doug Rabson Cc: Warner Losh , Peter Wemm , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: About that 'new-bus' stuff. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Doug Rabson wrote: > On Mon, 12 Apr 1999, Warner Losh wrote: > > > In message <19990412175644.7DE5F1F4F@spinner.netplex.com.au> Peter Wemm writes: > > : to being able to use their drivers with less hassles. (There will be > > : enough fun due to differences in bus_space and bus_dma, but that's > > : another issue) > > > > I know that many people would like to see bus_space and bus_dma > > reimported from NetBSD. As far as I know, there is no compelling > > reason to have them be different. > > I don't think there are many differences with bus_space. I don't know > about bus_dma though. bus_dma is somewhat different. Justin and Jason have done minor celebrity deathmatches over this topic :-)... neither bus_dma nor bus_space are perhaps entirely sufficient in any case. bus_dma doesn't quite carry enough information along with it to correctly know whether the memory object being mapped is another device or memory. It currently can be inferred from the uses of pmap_extract, but information such as hierarchical constraints (address and access size limitations) has no context here. This is also a limitation for NetBSD's bus_dma limitation. There may be pieces missing from bus_space or another interface needs to be there. There's a notion of DMA synchronization to ensure coherent shared views of objects between CPUs and devices, but there isn't a notion of endian-ness and layout to write such objects- this leads devices to have to special case on a per-bus/per-architecture basis. Both of the above restrictions don't cause problems for simple machines like workstation Alphas or i386 boxes (well, it does if you wanted to do, e.g., PCI<>PCI transactions), but cause tremendous heartburn for snything more complex machines. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 13:12: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 86DBA14FC1 for ; Mon, 12 Apr 1999 13:12:01 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id NAA24700 for ; Mon, 12 Apr 1999 13:09:22 -0700 Date: Mon, 12 Apr 1999 13:09:22 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: we still have NFS problems in -current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Probably- but this is sure amusing (not!): Compiling a kernel... directory is NFS mounted on a solaris 2.6 machine: .... cd9660_bmap.o: file not recognized: File format not recognized *** Error code 1 Stop. quarm.feral.com > file cd9660_bmap.o cd9660_bmap.o: MS Windows COFF Unknown CPU Filesystem 1K-blocks Used Avail Capacity Mounted on bird:/src/freebsd-current/src 4124565 1602999 2480321 39% /usr/src quarm.feral.com > ls -l cd9660_bmap.o -rw-rw-r-- 1 mjacob 100 890 Apr 12 12:45 cd9660_bmap.o quarm.feral.com > rcp bird:/src/freebsd-current/src/sys/compile/QUARM_CHK/cd9660_bmap.o /tmp quarm.feral.com > file /tmp/cd9660_bmap.o /tmp/cd9660_bmap.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stripped quarm.feral.com > mv cd9660_bmap.o cd9660_bmap.o.SAVE quarm.feral.com > make cd9660_bmap.o cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../isofs/cd9660/cd9660_bmap.c quarm.feral.com > file cd9660_bmap.o cd9660_bmap.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stripped quarm.feral.com > cmp cd9660_bmap.o cd9660_bmap.o.SAVE quarm.feral.com > file !$ file cd9660_bmap.o.SAVE cd9660_bmap.o.SAVE: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stripped Hmmm! Ow! Ow! Ow! FreeBSD quarm.feral.com 4.0-CURRENT FreeBSD 4.0-CURRENT #57: Fri Apr 9 20:17:57 PDT 1999 mjacob@quarm.feral.com:/freebsd/FreeBSD-current/sys/compile/QUARM i386 This kernel from sources updated April 9.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 13:28:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id B06F615226 for ; Mon, 12 Apr 1999 13:28:39 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id NAA97599 for freebsd-current@freebsd.org; Mon, 12 Apr 1999 13:26:20 -0700 (PDT) Date: Mon, 12 Apr 1999 13:26:20 -0700 (PDT) From: David Wolfskill Message-Id: <199904122026.NAA97599@pau-amma.whistle.com> To: freebsd-current@freebsd.org Subject: Re: showing full host names in output from who/finger/last In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sun, 11 Apr 1999 19:05:30 -0400 (EDT) >From: Robert Watson >I'd actually like to see wtmp only use IP addresses, never hostnames. I would prefer to have that be an installation-selectable option, at least. >Spoofed names are fairly easy to arrange; with IP filtering on border >routers, spoofed IPs are harder. Besides which, connections are from IPs >and not names. :-) This of course sticks you with the task of DNS >lookups when viewing wtmp, when you may already have done them at login >time. Probably ideally, we'd have two variable length fields, one for a >network-supplied source, and one for a transformed source such as name, >display name (....:0), etc. But that requires modifying the record >format, which is always a pain. In my case, it's more because I expect the association of hostname <-> IP address to be rather transient compared to the interval during which the information might be useful: although it may be of interest to know what the hostname was at the time of the original event, it's more likely to be useful for me to know the IP address at the time. And merely because I know one of those *now* doesn't mean that I necessarily know what the other was *then*. (And yes, this is more of a concern when investigating such things as dropped (but logged) ICMP redirects targeted at some of our perimeter hosts, for example. I'm rather less concerned within our internal nets.) Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 13:32:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 794C114F1B for ; Mon, 12 Apr 1999 13:32:31 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA81084; Mon, 12 Apr 1999 13:30:00 -0700 (PDT) Date: Mon, 12 Apr 1999 13:30:00 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <199904120153.SAA12154@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems to me that you might kill the forst program the has a lot of ram in unse that has not specified a limit for itself.. programs that are wel enough behaved to set a limit for themselves should be rewarded. just a thought... julian On Sun, 11 Apr 1999, Matthew Dillon wrote: > :I use the memory as soon as it's malloced. If it reserves a page, then > :pagefaults it into existence, the VM system knows that that page is now > :allocated. When I malloc the last available page for user use, the VM > :system knows that it's the last page. I dirty it, and there are none > :free. If I malloc(), I want to know that there is no more memory, not > :have my process killed. This is POMA. > : > :Previously, the POLA, a NULL getting returned, WORKED CORRECTLY. It did this > :for a long time. My little test program always showed this, and shows > :that now something was broken. I'll attach it to the end. > > I ran your program. malloc() appears to work properly -- returns NULL when > the datasize limit is reached. In my case, I set the datasize limit > to 64MB and ran the program. > > ... > mallocs failed at 64956 > > Under 4.0-current. > > :> then one or two processes getting killed. Having N random processes get > :> malloc() failures can lead to serious instability with processes. > : > :Only bad code doesn't check return values of malloc(). > > You are volunteering to run through the thousands of programs & ports > to make sure that every one checks the return value for malloc()? > > Declarations that don't solve problems are not relevant. It's bad enough > that we have to kill something to handle an out-of-vm situation, we > shouldn't go off and destabilize the rest of the system while we are at it. > > -Matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 13:58:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3BD0F14E89 for ; Mon, 12 Apr 1999 13:58:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA06590; Mon, 12 Apr 1999 13:55:56 -0700 (PDT) (envelope-from dillon) Date: Mon, 12 Apr 1999 13:55:56 -0700 (PDT) From: Matthew Dillon Message-Id: <199904122055.NAA06590@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: we still have NFS problems in -current? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Probably- but this is sure amusing (not!): : :Compiling a kernel... directory is NFS mounted on a solaris 2.6 machine: : :.... : :cd9660_bmap.o: file not recognized: File format not recognized :*** Error code 1 I found it. The problem was introduced when we committed the mmap() zero-invalid-areas patch. !@#$@#$#$%#%#@%@#%#@ NFS is such a fragile piece of junk! NFS is doing some illegal shit. I'll get a patch out ASAP. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 14: 2:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A374614F04 for ; Mon, 12 Apr 1999 14:02:43 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id NAA24817; Mon, 12 Apr 1999 13:59:59 -0700 Date: Mon, 12 Apr 1999 13:59:59 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: we still have NFS problems in -current? In-Reply-To: <199904122055.NAA06590@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Matthew Dillon wrote: > :Probably- but this is sure amusing (not!): > : > :Compiling a kernel... directory is NFS mounted on a solaris 2.6 machine: > : > :.... > : > :cd9660_bmap.o: file not recognized: File format not recognized > :*** Error code 1 > > I found it. The problem was introduced when we committed the > mmap() zero-invalid-areas patch. !@#$@#$#$%#%#@%@#%#@ NFS is such > a fragile piece of junk! Why do you say that? :-) Bob Lyon still says: +Date: Mon, 22 Mar 1999 22:00:47 -0800 +From: Bob Lyon +To: mjacob@feral.com +Subject: Re: NFS - Will it ever be fixed? (fwd) + + +NFS is perfect. It needs no fixing. (Unless, we mean +"fix" as in what we do to dogs. + +/Bob > > NFS is doing some illegal shit. I'll get a patch out ASAP. Awesome. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 14:26:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2A2111562F for ; Mon, 12 Apr 1999 14:26:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA07023; Mon, 12 Apr 1999 14:24:07 -0700 (PDT) (envelope-from dillon) Date: Mon, 12 Apr 1999 14:24:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199904122124.OAA07023@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: we still have NFS problems in -current? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> I found it. The problem was introduced when we committed the :> mmap() zero-invalid-areas patch. !@#$@#$#$%#%#@%@#%#@ NFS is such :> a fragile piece of junk! : :Why do you say that? :-) What it come down to is that due to the way m->valid is set, it is possible for mmap() to believe that a page is entirely valid when, in fact, it isn't, because partial NFS I/O must set the valid and dirty bits in the vm_page_t 'inclusively'. So, for example, if a page contains valid data from offsets 130-4095, vm_page_t->valid will still be VM_PAGE_BITS_ALL ( 0xFF ) rather then 0xFE. This causes mmap() to believe that the page is entirely valid when it isn't. Before we zerod out invalid areas the 'stale' data from a prior partial write, e.g. say a write from offset 0 through 120, would stick around in the buffer. Hence, no crash. Now the data doesn't necessarily stick around. The write is committed, the valid bit is clear, the new write to offsets 130-4095 sets the valid bits again and clears the 'stale' data. I'm working on a patch. Sigh. I think we may have to implement a 'completely valid' flag for vm_page_t rather then depend on comparing m->valid against VM_PAGE_BITS_ALL. What a mess. For now, turn off the mmap zeroing fix. The patch is included below. -Matt Matthew Dillon Index: vm/vm_page.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_page.c,v retrieving revision 1.129 diff -u -r1.129 vm_page.c --- vm_page.c 1999/04/05 19:38:29 1.129 +++ vm_page.c 1999/04/12 21:22:28 @@ -1491,11 +1491,13 @@ if ((frag = base & ~(DEV_BSIZE - 1)) != base && (m->valid & (1 << (base >> DEV_BSHIFT))) == 0 ) { +#if 0 pmap_zero_page_area( VM_PAGE_TO_PHYS(m), frag, base - frag ); +#endif } /* @@ -1509,11 +1511,13 @@ if ((frag = endoff & ~(DEV_BSIZE - 1)) != endoff && (m->valid & (1 << (endoff >> DEV_BSHIFT))) == 0 ) { +#if 0 pmap_zero_page_area( VM_PAGE_TO_PHYS(m), endoff, DEV_BSIZE - (endoff & (DEV_BSIZE - 1)) ); +#endif } /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 14:32:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 05E4814CEE for ; Mon, 12 Apr 1999 14:32:25 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id QAA29134; Mon, 12 Apr 1999 16:43:36 -0500 (EST) Date: Mon, 12 Apr 1999 16:43:33 -0500 (EST) From: Alfred Perlstein To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? In-Reply-To: <37124221.B8D7C471@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Maxim Sobolev wrote: > Alfred Perlstein wrote: > > > Hey, i was just doing a kernel compile over NFS and i have a weird > > situtation. After compiling everything the linker barfs on linking. > > > > gensetdefs: cd9660_bmap.o: not an ELF file > > > > for about 12 files... > > > > the compile is being done on a laptop that has my desktop's src dir > > NFS mounted. > > > Hey I have pretty the same problems on my 4.0 cvsup'ed and builded few > days ago! > > As NFS server I have 3.1-stable box. Let's try to figure out some other commonalities to assist debugging this. can you please fill this in: Me You Server version 4.0-apr6th 3.1- ??? Netcard pn0 ?? local disk da options softupdates nfsd? yes ram 32meg Client version 4.0-apr9th 4.0- ??? Netcard ep0 3comIII pcmcia local disk wd options softupdates nfsiod don't think so ram 48meg Mount type: mount server:/usr/src /usr/src how bug build kernel in happened: NFS mounted /usr/src make depend && make -j6 all bug: client sees files are filled with zeros, but server has non-corrupted files will not link on client links fine on server if the files are copied from the NFS mount to local disk they "un-corrupt" themselves. well? I'm tempted to blame the 3com, but that doesn't make sense as when you copy to local disk the files seem to become normal again... -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 15: 2:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from web110.yahoomail.com (web110.yahoomail.com [205.180.60.80]) by hub.freebsd.org (Postfix) with SMTP id 556B915686 for ; Mon, 12 Apr 1999 15:02:48 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990412220119.488.rocketmail@web110.yahoomail.com> Received: from [147.226.112.101] by web110.yahoomail.com; Mon, 12 Apr 1999 15:01:19 PDT Date: Mon, 12 Apr 1999 15:01:19 -0700 (PDT) From: Valentin Shopov Subject: /usr permissions after upgrade To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After upgrade to 4.0-CURRENT , /usr permissions are 777, owner.group is bin.bin. In my case I don't have separated fs for /usr, /var, etc.,, so /usr is in root fs. Val _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 15:21:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id AC725155E5 for ; Mon, 12 Apr 1999 15:21:11 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id AAA08391 for ; Tue, 13 Apr 1999 00:18:52 +0200 (CEST) Date: Tue, 13 Apr 1999 00:18:52 +0200 (CEST) From: Martin Blapp To: freebsd-current@FreeBSD.ORG Subject: new panic from fresh current (SMP) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG But it's not related to that caused by the NMI, and it appears suddenly after probing soerens ATAPI drivers. hmm - SMP: AP CPU #1 Launched! does not appear ... what this ever means. the previos kernel as of yesterday had: IP Filter: initialized. Default = pass all, Logging = disabled SMP: AP CPU #1 Launched! acd0: CDROM drive at ata0 as master acd0: drive speed 5512KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked afd0: rewriteable drive at ata0 as slave afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: Unknown media (0x0) Waiting 5 seconds for SCSI devices to settle now the panic ... mp_lock = 0100001; cpuid = 1; lapic.id = 0100000 instruction pointer = 0x8:0xc024bfb8 stack pointer = 0x10:0xff804ff8 frame pointer = 0x10:0x0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = Idle interrupt mask = <- SMP: XXX kernel: type 29 trap, code=0 Stopped at default_halt: ret db> no trace Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 15:21:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 5731915688 for ; Mon, 12 Apr 1999 15:21:33 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.2/8.9.2) id UAA12888; Mon, 12 Apr 1999 20:02:01 +0100 (BST) (envelope-from nik) Date: Mon, 12 Apr 1999 20:02:01 +0100 From: Nik Clayton To: Bob Willcox Cc: Brian Beattie , Warner Losh , leifn@neland.dk, sheldonh@iafrica.com, freebsd-current@FreeBSD.ORG Subject: Re: AIC Message-ID: <19990412200201.A11448@catkin.nothing-going-on.org> References: <199903311835.LAA00284@rover.village.org> <19990411112909.A34758@luke.pmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990411112909.A34758@luke.pmr.com>; from Bob Willcox on Sun, Apr 11, 1999 at 11:29:09AM -0500 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 11, 1999 at 11:29:09AM -0500, Bob Willcox wrote: > On Wed, Mar 31, 1999 at 12:28:47PM -0800, Brian Beattie wrote: > > On Wed, 31 Mar 1999, Warner Losh wrote: > > > The aic driver will likely oneday be ported. However, no one has come > > > forward to do it. It is a highly desirable driver to have (even if > > > > Umm, I'm still working on the aic driver. Slowly, but working on it. > > > > > writing it would be a pain) because the only pccard scsi cards that are > > > out there are aic-6[23]60 based. > > > > > > > Not having a pcmcia slot or card, I am not sure about support for this. > > I have both and would be willing to test it on my laptop. If you need a desktop tester of the new AIC driver, give me a shout. Upgrading to 3.0 broke my CDROM and internal Zip drive :-( N -- Bagel: The carbohydrate with the hole To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 15:26:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 3039B150DA for ; Mon, 12 Apr 1999 15:26:25 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id AAA08400 for ; Tue, 13 Apr 1999 00:24:04 +0200 (CEST) Date: Tue, 13 Apr 1999 00:24:04 +0200 (CEST) From: Martin Blapp To: freebsd-current@FreeBSD.ORG Subject: new panic from fresh current (SMP) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG aeh - forgot to say ... it is reproducable - it can't boot And the kernel-gdbtrace isn't very useful :( Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 15:36:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 7754515681; Mon, 12 Apr 1999 15:36:04 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id QAA49323; Mon, 12 Apr 1999 16:33:31 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199904122233.QAA49323@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: Peter Wemm , current@FreeBSD.org, committers@FreeBSD.org Subject: Re: About that 'new-bus' stuff. In-reply-to: Your message of "Mon, 12 Apr 1999 13:40:27 MDT." <199904121940.NAA02397@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Apr 1999 16:24:04 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <19990412175644.7DE5F1F4F@spinner.netplex.com.au> Peter Wemm writes >: >: to being able to use their drivers with less hassles. (There will be >: enough fun due to differences in bus_space and bus_dma, but that's >: another issue) > >I know that many people would like to see bus_space and bus_dma >reimported from NetBSD. As far as I know, there is no compelling >reason to have them be different. For bus_space, no. For bus_dma, there are some reasons for them to be different in one area: the callback mechanism for returning a valid dma mapping. The rest of the differences are primarily from the fact that NetBSD has enhanced or modified their interfaces since my original work and I haven't found the time to sync us back up. >Warner -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 15:52:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5DBC314D34 for ; Mon, 12 Apr 1999 15:52:25 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA56931; Mon, 12 Apr 1999 15:50:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Peter Wemm Cc: current@FreeBSD.org Subject: Re: About that 'new-bus' stuff. In-reply-to: Your message of "Tue, 13 Apr 1999 01:56:41 +0800." <19990412175644.7DE5F1F4F@spinner.netplex.com.au> Date: Mon, 12 Apr 1999 15:50:35 -0700 Message-ID: <56929.923957435@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you very much for this summary! Like most people, I don't think this is a political issue between new-bus and newconfig, it's simply what we've already got on the Alpha and now need to bring to the x86 for consistency's sake. I also suspect that once this code is in -current, and I'd personally like to see that happen, what eventually evolves from it will probably represent the best of both newconfig and new-bus, it being the nature of software to constantly change. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 16:53:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 5862F157AA for ; Mon, 12 Apr 1999 16:53:24 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id TAA21485; Mon, 12 Apr 1999 19:04:06 -0500 (EST) Date: Mon, 12 Apr 1999 19:04:05 -0500 (EST) From: Alfred Perlstein Reply-To: Alfred Perlstein To: Doug Rabson Cc: Peter Wemm , current@freebsd.org Subject: Re: cvs commit: sys/pci pci.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Doug Rabson wrote: > On Mon, 12 Apr 1999, Alfred Perlstein wrote: > > > The problem that i faced was that the console stuff must be done even > > before the SYSINITs are done it's generally setup from machdep.c this > > is before a lot of stuff is really setup. > > > > How early can i expect this framework to be in place so i can attach > > a console bus/device or does it seem i have to hack this somehow? > > > > What i'm planning on is a way to modularize the console code enough > > so that during runtime the console can be moved from device to device > > and even support a forked console (i/o on both sio and sc) revoking > > a console and a split console (input serial, output syscons). > > That sounds very worthwhile. While you are at it, can you try to factor > out the common code from the i386 and alpha ports so that both can use the > new mechanism. I will try to, something i also wonder, why is there seperate sio.c for each port? it seems like a lot of the isa stuff is duplicated across each port making it hard to actually do this correctly. hopefull the new stuff going into the bus code will help this, i know drowning the code in #ifdef __alpha__/__i386__/etc is pretty nasty but trying to keep 3 sio.c and i presume more if the other arch ports in the works have the same isa device as even more difficult. the seperate i386/cons.c and such will be put into an arch independant form and i will impelement a spec to follow to be a console device. I will bring sio and syscons on i386 into this model and i hope developers with pc98 and alpha equip can move to it as well. > > btw, i'm not familiar with the proper way to use this list, am i generating > > noise by cc'ing the list or is that the proper way, or should move > > messages like this to -current? > > This is possibly material for the current list (although personally I > don't mind reading it here). moved to -current :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 17:28:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from fire.starkreality.com (fire.starkreality.com [208.24.48.226]) by hub.freebsd.org (Postfix) with ESMTP id 2EE4E153FA; Mon, 12 Apr 1999 17:28:13 -0700 (PDT) (envelope-from caesar@starkreality.com) Received: from grail (grail.starkreality.com [208.24.48.235]) by fire.starkreality.com (8.9.3/8.9.2) with SMTP id TAA03162; Mon, 12 Apr 1999 19:25:52 -0500 (CDT) Message-Id: <4.1.19990412191627.009b3100@imap.colltech.com> X-Sender: caesar@mail.starkreality.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 12 Apr 1999 19:25:31 -0500 To: freebsd-smp@freebsd.org From: "William S. Duncanson" Subject: SMP broken in -CURRENT? Cc: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't been able to get a working SMP kernel out of -CURRENT recently. I don't know exactly when it broke, because I usually rebuild on a weekly basis. The kernel hangs after: APIC_IO: Testing 8254 interrupt delivery and doesn't ever come back (panic or otherwise). The one thing that I noticed is that on the older kernels, CPU#1 is launched after the APIC_IO Testing and Routing. On the newer kernels, CPU#1 is launched far earlier. Anybody have any ideas? On a side note, the pn0 driver appears to be broken (uniprocessor kernels will boot, the pn0 device shows up, and is ifconfig'd, but there's no link light on it. It works fine with older (04/04/99) kernels). William S. Duncanson caesar@starkreality.com The driving force behind the NC is the belief that the companies who brought us things like Unix, relational databases, and Windows can make an appliance that is inexpensive and easy to use if they choose to do that. -- Scott Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 18:16:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id A57E3155E9 for ; Mon, 12 Apr 1999 18:16:39 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id JAA12959 for ; Tue, 13 Apr 1999 09:14:19 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA21725; Tue, 13 Apr 1999 09:14:19 +0800 Message-Id: <199904130114.JAA21725@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Further on tape & CAM problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Apr 1999 09:14:18 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When the tape hangs with an unkillable process, its relevant PS flags are "physstrat" and "DL+". It doesn't hang forever, just a very long time, like someone's confused milliseconds with microseconds, or some such. Also, when writing to the 2nd tape in a CPIO archive, it doesn't actually write to the tape. systat -vmstat records lots of stuff going to the tape device (a SCSI QIC-525 in this case) very quickly - way beyond the speed it can actually do but there's no actual activity. Dump on the otherhand seems fine. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 19:16:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id 4E23A14CEC; Mon, 12 Apr 1999 19:16:20 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.1/8.9.1) with ESMTP id EAA29557; Tue, 13 Apr 1999 04:13:54 +0200 (CEST) Message-Id: <199904130213.EAA29557@midten.fast.no> To: caesar@starkreality.com Cc: freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: SMP broken in -CURRENT? From: Tor.Egge@fast.no In-Reply-To: Your message of "Mon, 12 Apr 1999 19:25:31 -0500" References: <4.1.19990412191627.009b3100@imap.colltech.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 13 Apr 1999 04:13:53 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I haven't been able to get a working SMP kernel out of -CURRENT recently. > I don't know exactly when it broke, because I usually rebuild on a weekly > basis. The kernel hangs after: > APIC_IO: Testing 8254 interrupt delivery > and doesn't ever come back (panic or otherwise). > > The one thing that I noticed is that on the older kernels, CPU#1 is > launched after the APIC_IO Testing and Routing. On the newer kernels, > CPU#1 is launched far earlier. > > Anybody have any ideas? You might want to try this patch, which disables the early start of CPU#1. Index: mp_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mp_machdep.c,v retrieving revision 1.96 diff -u -r1.96 mp_machdep.c --- mp_machdep.c 1999/04/11 00:43:43 1.96 +++ mp_machdep.c 1999/04/13 02:08:54 @@ -1930,9 +1930,11 @@ for (i = 0; i < mp_ncpus; i++) { bcopy( (int *) PTD + KPTDI, (int *) IdlePTDS[i] + KPTDI, NKPDE * sizeof (int)); } +#if 0 wait_ap(1000000); if (smp_started == 0) printf("WARNING: Failed to start all APs\n"); +#endif /* number of APs actually started */ return mp_ncpus - 1; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 20:16: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (pax-ca27-08.ix.netcom.com [207.93.145.40]) by hub.freebsd.org (Postfix) with ESMTP id 8E52114BC9; Mon, 12 Apr 1999 20:16:00 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id UAA00338; Mon, 12 Apr 1999 20:13:39 -0700 (PDT) (envelope-from tomdean) Date: Mon, 12 Apr 1999 20:13:39 -0700 (PDT) Message-Id: <199904130313.UAA00338@ix.netcom.com> From: Thomas Dean To: freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: CVSUP, Make World, Patch mp_machdep.c, Make Kernel Works Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running 4.0-current SMP, as of an hour ago, cvsup about noon, today. I have been holding off, watching the egcs development. It all works. egcs all appears to work, I rebuilt some applications. I did a cvsup, make world, and, after applying the patch to delay starting cpu#1, built a kernel and it all works. I tried building a kernel before I applied the patch and the hang problem was there. Great job in getting it all together. Now, to rebuild 37 ports! Thanks, core team tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 20:34:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from fire.starkreality.com (fire.starkreality.com [208.24.48.226]) by hub.freebsd.org (Postfix) with ESMTP id BED1014D53; Mon, 12 Apr 1999 20:34:33 -0700 (PDT) (envelope-from caesar@starkreality.com) Received: from armageddon (armageddon.starkreality.com [208.24.48.227]) by fire.starkreality.com (8.9.3/8.9.2) with SMTP id WAA01039; Mon, 12 Apr 1999 22:31:42 -0500 (CDT) Message-Id: <4.1.19990412222940.03bde1e0@fire.starkreality.com> X-Sender: caesar@fire.starkreality.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 12 Apr 1999 22:31:28 -0500 To: Tor.Egge@fast.no From: "William S. Duncanson" Subject: Re: SMP broken in -CURRENT? Cc: freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <199904130213.EAA29557@midten.fast.no> References: <4.1.19990412191627.009b3100@imap.colltech.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That fixes it, thanks. At 04:13 4/13/99 +0200, Tor.Egge@fast.no wrote: >> I haven't been able to get a working SMP kernel out of -CURRENT recently. >> I don't know exactly when it broke, because I usually rebuild on a weekly >> basis. The kernel hangs after: >> APIC_IO: Testing 8254 interrupt delivery >> and doesn't ever come back (panic or otherwise). >> >> The one thing that I noticed is that on the older kernels, CPU#1 is >> launched after the APIC_IO Testing and Routing. On the newer kernels, >> CPU#1 is launched far earlier. >> >> Anybody have any ideas? > >You might want to try this patch, which disables the early start of CPU#1. > >Index: mp_machdep.c >=================================================================== >RCS file: /home/ncvs/src/sys/i386/i386/mp_machdep.c,v >retrieving revision 1.96 >diff -u -r1.96 mp_machdep.c >--- mp_machdep.c 1999/04/11 00:43:43 1.96 >+++ mp_machdep.c 1999/04/13 02:08:54 >@@ -1930,9 +1930,11 @@ > for (i = 0; i < mp_ncpus; i++) { > bcopy( (int *) PTD + KPTDI, (int *) IdlePTDS[i] + KPTDI, NKPDE * sizeof >(int)); > } >+#if 0 > wait_ap(1000000); > if (smp_started == 0) > printf("WARNING: Failed to start all APs\n"); >+#endif > > /* number of APs actually started */ > return mp_ncpus - 1; > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message William S. Duncanson caesar@starkreality.com The driving force behind the NC is the belief that the companies who brought us things like Unix, relational databases, and Windows can make an appliance that is inexpensive and easy to use if they choose to do that. -- Scott Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 22:36:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id E7F0E14CE2 for ; Mon, 12 Apr 1999 22:36:09 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip60.houston13.tx.pub-ip.psi.net [38.27.213.60]) by leap.innerx.net (Postfix) with ESMTP id 8637937071; Tue, 13 Apr 1999 01:33:47 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id AAA01992; Tue, 13 Apr 1999 00:34:10 -0500 (CDT) (envelope-from chris) Date: Tue, 13 Apr 1999 00:34:09 -0500 From: Chris Costello To: ben@rosengart.com Cc: current@FreeBSD.ORG Subject: Re: kernel size over the last week Message-ID: <19990413003409.A1968@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Snob Art Genre on Mon, Apr 12, 1999 at 02:38:49PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 12, 1999, Snob Art Genre wrote: > I just built a kernel, from sources cvsupped last night. It's over 2 > megs in size, compared to 1.3 megs for a kernel built from the same > config file four days ago. Is this due to the change in the debugging > symbol policy? file(1) reports both kernels as 'ELF 32-bit LSB > executable, Intel 80386, version 1 (FreeBSD), dynamically linked, not > stripped'. Were there any drastic configuration differences? It seems to me that egcs binaries are a bit larger as far as file size goes, but my size change went from about 1.1-1.3 MB to about 1.7 MB. > Ben > > "You have your mind on computers, it seems." -- Chris Costello It's redundant! It's redundant! -R. E. Dundant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 22:49:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id ECCC014E42 for ; Mon, 12 Apr 1999 22:49:32 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip60.houston13.tx.pub-ip.psi.net [38.27.213.60]) by leap.innerx.net (Postfix) with ESMTP id 0145537071; Tue, 13 Apr 1999 01:47:10 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id AAA02134; Tue, 13 Apr 1999 00:47:28 -0500 (CDT) (envelope-from chris) Date: Tue, 13 Apr 1999 00:47:28 -0500 From: Chris Costello To: Matthew Dillon Cc: Mattias Pantzare , Amancio Hasty , Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) Message-ID: <19990413004728.C1968@holly.dyndns.org> Reply-To: chris@calldei.com References: <199904102051.WAA07790@zed.ludd.luth.se> <199904102057.NAA01570@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <199904102057.NAA01570@apollo.backplane.com>; from Matthew Dillon on Sat, Apr 10, 1999 at 01:57:32PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 10, 1999, Matthew Dillon wrote: > :Sun has a product for this, Solaris Resource Manager. > > ... and if one user is *supposed* to be running all those processes, then > what? Oh, let me guess: Now you are supposed to tune each user's account > independantly. For a system with general user accounts, this is a burden > on the sysop. You don't need to tune user accounts, you need only put the users in a separate login class (if that hasn't already been done) and modify the resource limitation for that login restriction. > If one can't control one's users, one has no business managing them. The > last thing FreeBSD needs is some overly complex, sophisticated scheduler > designed to help bozo sysops stay on their feet. I agree with you very much here. Public shell systems are a bad idea. In my opinion, you should trust someone before you allow them to have an account on your system. > -Matt > Matthew Dillon > -- Chris Costello Computers talk to each other worse than their designers do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 22:55:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 24DE01509E for ; Mon, 12 Apr 1999 22:55:12 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA12856; Mon, 12 Apr 1999 22:52:53 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA73931; Mon, 12 Apr 1999 22:52:52 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 12 Apr 1999 22:52:52 -0700 (PDT) Message-Id: <199904130552.WAA73931@vashon.polstra.com> To: schuerge@wurzelausix.CS.Uni-SB.DE Subject: Re: cvsup In-Reply-To: <199904121820.UAA09661@wurzelausix.cs.uni-sb.de> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904121820.UAA09661@wurzelausix.cs.uni-sb.de>, Thomas Schuerger wrote: > > Is there any way to make cvsup update its GUI properly? The window > is almost dead when cvsup is performing updates, e.g. cvsup will update > the window's contents very infrequently, which is rather anoying. Perhaps > it would be a good idea to put GUI handling into a separate thread. It _is_ in a separate thread. You just need a faster CPU, or SCSI disks. :-) Running FreeBSD-3.1 with soft-updates enabled might help. Also, try the "-s" option. (Read about it first in cvsup(1).) It greatly reduces disk activity and will make your updates go faster, possibly with snappier GUI updates too. The GUI performance varies widely between systems. It was so-so on my old P/90, but it's pretty good on my PII/400. It may be the disk activity that kills the GUI performance. Disk operations are non-interruptible, so if the disk is really busy the GUI thread doesn't get control often enough. (I'm guessing and could be totally wrong, though.) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 23: 4:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 741F71509E for ; Mon, 12 Apr 1999 23:04:37 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip60.houston13.tx.pub-ip.psi.net [38.27.213.60]) by leap.innerx.net (Postfix) with ESMTP id 523B037012; Tue, 13 Apr 1999 02:02:14 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id BAA02247; Tue, 13 Apr 1999 01:02:36 -0500 (CDT) (envelope-from chris) Date: Tue, 13 Apr 1999 01:02:36 -0500 From: Chris Costello To: Gianmarco Giovannelli Cc: current@FreeBSD.ORG Subject: Re: ftp hangs on -current Message-ID: <19990413010236.A2189@holly.dyndns.org> Reply-To: chris@calldei.com References: <4.1.19990408054254.00a4ab80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <4.1.19990408054254.00a4ab80@194.184.65.4>; from Gianmarco Giovannelli on Thu, Apr 08, 1999 at 05:49:52AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 7, 1999, Gianmarco Giovannelli wrote: > > "ftp" on 4.0-very-current (post egcs make world) randomly hangs during > sessions... > I never succeded in finishing a session lately. > To transfer some files from my home to my isp server I had to do an "ftp" > from the server and a "get" to them... I don't know if this is proper behavior or not. I get this problem when sending an ABRT and the server doesn't respond (because it's a broken Windows FTPd, usually) or when I'm on a generally _bad_ route to that particular system. I'm not sure if it works, but I'll investigate into it: Perhaps a test to see if read/write failed with errno = EINTR - if it is EINTR, close() the socket and sit at the prompt, or perhaps just exit. Any opinions? -- Chris Costello Bad command or file name. Go stand in the corner. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 23:13:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 2B24F14C08 for ; Mon, 12 Apr 1999 23:13:08 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id BAA09924; Tue, 13 Apr 1999 01:10:33 -0500 (CDT) Date: Tue, 13 Apr 1999 01:10:33 -0500 From: "Matthew D. Fuller" To: John Polstra Cc: schuerge@wurzelausix.CS.Uni-SB.DE, current@FreeBSD.ORG Subject: Re: cvsup Message-ID: <19990413011033.V11572@futuresouth.com> References: <199904121820.UAA09661@wurzelausix.cs.uni-sb.de> <199904130552.WAA73931@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199904130552.WAA73931@vashon.polstra.com>; from John Polstra on Mon, Apr 12, 1999 at 10:52:52PM -0700 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 12, 1999 at 10:52:52PM -0700, a little birdie told me that John Polstra remarked > > Also, try the "-s" option. (Read about it first in cvsup(1).) It > greatly reduces disk activity and will make your updates go faster, > possibly with snappier GUI updates too. Damn, I should RTFM more often ;) I could definately like this. > The GUI performance varies widely between systems. It was so-so > on my old P/90, but it's pretty good on my PII/400. It may be the > disk activity that kills the GUI performance. Disk operations are > non-interruptible, so if the disk is really busy the GUI thread > doesn't get control often enough. (I'm guessing and could be totally > wrong, though.) As a data point, CVSup runs nicely, but if I iconify it and deiconify it, it takes about forEVER (maybe 10, 15 seconds on a PPro 180) to redisplay itself completely. Sucking down CVS repo to /usr/cvs (async, noatime). Under 2.2-S, mind you. --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 23:30: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id E8E4914D3B for ; Mon, 12 Apr 1999 23:30:05 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip60.houston13.tx.pub-ip.psi.net [38.27.213.60]) by leap.innerx.net (Postfix) with ESMTP id CBCBC37097; Tue, 13 Apr 1999 02:27:44 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id BAA02398; Tue, 13 Apr 1999 01:28:07 -0500 (CDT) (envelope-from chris) Date: Tue, 13 Apr 1999 01:28:06 -0500 From: Chris Costello To: ben@rosengart.com Cc: current@FreeBSD.ORG Subject: Re: kernel size over the last week Message-ID: <19990413012806.C2189@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990413003409.A1968@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Snob Art Genre on Tue, Apr 13, 1999 at 02:17:39AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 13, 1999, Snob Art Genre wrote: > On Tue, 13 Apr 1999, Chris Costello wrote: > > > On Mon, Apr 12, 1999, Snob Art Genre wrote: > > > I just built a kernel, from sources cvsupped last night. It's over 2 > > > megs in size, compared to 1.3 megs for a kernel built from the same > > > config file four days ago. > > > > Were there any drastic configuration differences? It seems to > > me that egcs binaries are a bit larger as far as file size goes, > > but my size change went from about 1.1-1.3 MB to about 1.7 MB. > > We were using egcs four days ago, weren't we? Anyway, no, there were no > configuration differences. We have been using egcs for much longer. This is the end of the second week. As I explained above, it's because egcs makes bigger binaries. -- Chris Costello Beware of programmers who carry screwdrivers. - Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 12 23:31:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id B0C6514D3B for ; Mon, 12 Apr 1999 23:31:07 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id IAA09129 for ; Tue, 13 Apr 1999 08:28:47 +0200 (CEST) Date: Tue, 13 Apr 1999 08:28:47 +0200 (CEST) From: Martin Blapp To: freebsd-current@FreeBSD.ORG Subject: RE: new panic from fresh current (SMP) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It seems to be fixed now with v 1.97 from /usr/src/sys/i386/i386/mp_machdep.c thanks ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 0:25:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id B99591527F for ; Tue, 13 Apr 1999 00:25:02 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async3-31.iptelecom.net.ua [212.42.68.222]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id KAA10929; Tue, 13 Apr 1999 10:22:53 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA85849; Tue, 13 Apr 1999 10:21:33 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3712F079.CDAD602@altavista.net> Date: Tue, 13 Apr 1999 10:21:29 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG   Alfred Perlstein wrote: > On Mon, 12 Apr 1999, Maxim Sobolev wrote: > > > Alfred Perlstein wrote: > > > > > Hey, i was just doing a kernel compile over NFS and i have a weird > > > situtation.  After compiling everything the linker barfs on linking. > > > > > > gensetdefs: cd9660_bmap.o: not an ELF file > > > > > > for about 12 files... > > > > > > the compile is being done on a laptop that has my desktop's src dir > > > NFS mounted. > > > > > Hey I have pretty the same problems on my 4.0 cvsup'ed and builded few > > days ago! > > > > As NFS server I have 3.1-stable box. >   > Let's try to figure out some other commonalities to assist debugging this. > can you please fill this in: >                      Me                              You Server version 4.0-apr6th                  3.1- apr6th  Netcard       pn0                               ed0 (Realtek 8029)  local disk    da                                  wd0  options       softupdates                    noatime  nfsd?         yes                                 yes  ram           32meg                            24meg Client version 4.0-apr9th                       4.0- apr6th  Netcard       ep0 3comIII pcmcia       ed0 (AR-P500 pcmcia)  local disk    wd                                   ad0  options       softupdates                       noatime  nfsiod        don't think so                    don't think so  ram           48meg                                32meg >   > Mount type:    mount server:/usr/src >                 /usr/src > > how bug        build kernel in > happened:      NFS mounted /usr/src >                make depend && make -j6 all > > bug:           client sees files are filled >                with zeros, but server has >                non-corrupted files > >                will not link on client >                links fine on server >                if the files are copied from >                the NFS mount to local disk >                they "un-corrupt" themselves. > > well?  I'm tempted to blame the 3com, but that doesn't make sense > as when you copy to local disk the files seem to become normal again... >   Mount type:    mount -o noatime server:/usr/src                       mount -o noatime server:/usr/ports how bug        build ports and kernel happened:      NFS mounted /usr/ports                      cd /usr/ports/textproc/docproj                      make all install                      NFS mounted /usr/src                      make depend && make -j4 bug:           client sees files are filled                  with zeros, but server has                  non-corrupted files                  will not link on client                links fine on server                if the files are copied from                the NFS mount to local disk                they "un-corrupt" themselves.                very good chance to link correctly is to try run make on client once more (cache flushes??) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 0:52:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1F1EC15676 for ; Tue, 13 Apr 1999 00:52:21 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA50769; Tue, 13 Apr 1999 08:53:58 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 13 Apr 1999 08:53:57 +0100 (BST) From: Doug Rabson To: Alfred Perlstein Cc: Peter Wemm , current@freebsd.org Subject: Re: cvs commit: sys/pci pci.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Alfred Perlstein wrote: > On Mon, 12 Apr 1999, Doug Rabson wrote: > > > On Mon, 12 Apr 1999, Alfred Perlstein wrote: > > > > > The problem that i faced was that the console stuff must be done even > > > before the SYSINITs are done it's generally setup from machdep.c this > > > is before a lot of stuff is really setup. > > > > > > How early can i expect this framework to be in place so i can attach > > > a console bus/device or does it seem i have to hack this somehow? > > > > > > What i'm planning on is a way to modularize the console code enough > > > so that during runtime the console can be moved from device to device > > > and even support a forked console (i/o on both sio and sc) revoking > > > a console and a split console (input serial, output syscons). > > > > That sounds very worthwhile. While you are at it, can you try to factor > > out the common code from the i386 and alpha ports so that both can use the > > new mechanism. > > I will try to, something i also wonder, why is there seperate sio.c > for each port? it seems like a lot of the isa stuff is duplicated > across each port making it hard to actually do this correctly. > > hopefull the new stuff going into the bus code will help this, i know > drowning the code in #ifdef __alpha__/__i386__/etc is pretty nasty > but trying to keep 3 sio.c and i presume more if the other arch ports > in the works have the same isa device as even more difficult. The one in sys/isa is the new-bus style one. It has diverged slightly from the i386 one but I intend to fix that. If/when the i386 new-bus implementation goes into current, there will be only one version of sio.c. > > the seperate i386/cons.c and such will be put into an arch independant > form and i will impelement a spec to follow to be a console device. > > I will bring sio and syscons on i386 into this model and i hope developers > with pc98 and alpha equip can move to it as well. Sounds good to me. I'm sure I can spend some time on adapting the alpha to the new model when it appears. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 1: 1:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from f77.nop.or.jp (f77.nop.or.jp [210.145.217.241]) by hub.freebsd.org (Postfix) with ESMTP id E456715665 for ; Tue, 13 Apr 1999 01:01:02 -0700 (PDT) (envelope-from uch@nop.or.jp) Received: from localhost (localhost [127.0.0.1]) by f77.nop.or.jp (8.9.1a/3.7W) with ESMTP id QAA05532 for ; Tue, 13 Apr 1999 16:58:36 +0900 (JST) To: current@FreeBSD.ORG Subject: newconfig/new-bus X-Mailer: Mew version 1.92 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990413165836K.uch@nop.or.jp> Date: Tue, 13 Apr 1999 16:58:36 +0900 From: UCHIYAMA Yasushi X-Dispatcher: imput version 971024 Lines: 34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/sys4c990410-newconfig990413.patch.gz This is newest newconfig patch against to 4.0-CURRENT(990410). FreeBSD/newconfig provides NetBSD compatible frame work ,bus_space(9) (bus_memio.h,bus_pio.h are no longer required.) and `bus name`_intr_establish. and also provides resource management. This feature makes easy to implement and feedback drivers among *BSD. As a sample, dev/pcmcia/ directory was imported from NetBSD. The amounts of #ifdef __FreeBSD__ is little. I'm working CardBus (dev/cardbus/) driver with NetBSD people. (originary written for NetBSD) Newconfig may not to be seem exciting, but this is powerful and flexible implementation in fact. please see this patch. Following table is guide map for comparison. newconfig new-bus framework: kern/subr_autoconf.c kern/subr_bus.c sys/device.h sys/bus.h resource management: kern/subr_rman.c kern/subr_rman.c i386/i386/resource.c i386/i386/nexus.c mainbus: i386/i386/mainbus.c i386/i386/nexus.c ISA bus: i386/isa/isa_machdep.c i386/i386/nisa.c PCI bus: i386/pci/pci_machdep.c pci/pci.c --- UCHIYAMA Yasushi uch@nop.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 1:23: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 9A58014DA1 for ; Tue, 13 Apr 1999 01:22:52 -0700 (PDT) (envelope-from schuerge@wurzelausix.CS.Uni-SB.DE) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by uni-sb.de (8.9.3/1999031900) with ESMTP id KAA01116 for ; Tue, 13 Apr 1999 10:20:23 +0200 (CEST) Received: (from schuerge@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id KAA21994 for freebsd-current@freebsd.org; Tue, 13 Apr 1999 10:13:47 +0200 (CEST) From: Thomas Schuerger Message-Id: <199904130813.KAA21994@wurzelausix.cs.uni-sb.de> Subject: FreeBSD won't boot To: freebsd-current@freebsd.org Date: Tue, 13 Apr 1999 10:13:46 +0200 (CEST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have Win95 and FreeBSD 4.0-Current on my system. Today I had to reinstall Win95, which overwrites the master boot record. After that I used fdisk to switch to FreeBSD and used /stand/sysinstall to install the FreeBSD selector boot record (I set the FreeBSD and the Win95 partition to bootable first). Now the boot selector will be displayed, but I cannot run FreeBSD from it anymore. It will just show the boot prompt in the boot loader and won't accept to boot from my SCSI drive, where the FreeBSD and Win95 partition are located (using "0:da(0,a)kernel", which should work). The boot loader just says "Invalid format!". Then I used the Fixit-Floppy and tried to boot FreeBSD from my harddrive, again using "0:da(0,a)kernel", which works perfectly. Am I missing something? Why doesn't the harddrive-installed bootloader accept my kernel, whereas the floppy bootloader does? Thanks for your help! Ciao, Thomas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 1:53: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 36DFD15012 for ; Tue, 13 Apr 1999 01:53:02 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async3-31.iptelecom.net.ua [212.42.68.222]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id LAA16546 for ; Tue, 13 Apr 1999 11:51:21 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id LAA87061 for ; Tue, 13 Apr 1999 11:50:24 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37130552.636D1DBE@altavista.net> Date: Tue, 13 Apr 1999 11:50:26 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: UPDATING need to be updated Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that as of today (13 Apr) make -j N world works fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 3:18:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7C20A156F2 for ; Tue, 13 Apr 1999 03:18:06 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA13348; Tue, 13 Apr 1999 19:15:22 +0900 (JST) Message-ID: <371317CD.475C2FC7@newsguy.com> Date: Tue, 13 Apr 1999 19:09:17 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Thomas Schuerger Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD won't boot References: <199904130813.KAA21994@wurzelausix.cs.uni-sb.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Schuerger wrote: > > I have Win95 and FreeBSD 4.0-Current on my system. What version of FreeBSD you originally had in your system? > Today I had to reinstall Win95, which overwrites the master boot record. > After that I used fdisk to switch to FreeBSD and used /stand/sysinstall > to install the FreeBSD selector boot record (I set the FreeBSD and the > Win95 partition to bootable first). This /stand/sysinstall is the one on the hard drive, correct? I assume you never, ever, did cd /usr/src/release/sysinstall; make all install, correct? Thus, this sysinstall corresponds to the originally installed FreeBSD version. One needs the latest loader to boot current -current kernels. I don't recall the exact dates for the latest loader, but the specific patch that is needed was committed sometime in march, I think. > Now the boot selector will be displayed, but I cannot run FreeBSD from > it anymore. It will just show the boot prompt in the boot loader and > won't accept to boot from my SCSI drive, where the FreeBSD and Win95 > partition are located (using "0:da(0,a)kernel", which should work). 0:da(0,a)kernel will certainly not work for loader, only boot2. Is loader being loaded at all? If not, you *definitely* don't have a latest version installed. In this case, try "0:da(0,a)/boot/loader". If that proceeds to boot your kernel correctly, do a "disklabel -B da0", and everything will be back to normal. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 3:20: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4782F15245 for ; Tue, 13 Apr 1999 03:20:01 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA13324; Tue, 13 Apr 1999 19:15:10 +0900 (JST) Message-ID: <37131436.644E6E48@newsguy.com> Date: Tue, 13 Apr 1999 18:53:58 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: chris@calldei.com Cc: Matthew Dillon , Mattias Pantzare , Amancio Hasty , Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: <199904102051.WAA07790@zed.ludd.luth.se> <199904102057.NAA01570@apollo.backplane.com> <19990413004728.C1968@holly.dyndns.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > > > If one can't control one's users, one has no business managing them. The > > last thing FreeBSD needs is some overly complex, sophisticated scheduler > > designed to help bozo sysops stay on their feet. > > I agree with you very much here. Public shell systems are a > bad idea. In my opinion, you should trust someone before you > allow them to have an account on your system. What you really mean is that "FreeBSD is not a solution for public shell systems", correct? Public shell systems is not a bad idea, it's a business opportunity and a public service. If the OS is not up to the task, don't blame the task. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 3:39:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 57A5A14C1C for ; Tue, 13 Apr 1999 03:39:23 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA59137; Tue, 13 Apr 1999 03:35:01 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Daniel C. Sobral" Cc: chris@calldei.com, Matthew Dillon , Mattias Pantzare , Amancio Hasty , Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-reply-to: Your message of "Tue, 13 Apr 1999 18:53:58 +0900." <37131436.644E6E48@newsguy.com> Date: Tue, 13 Apr 1999 03:35:01 -0700 Message-ID: <59135.923999701@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What you really mean is that "FreeBSD is not a solution for public > shell systems", correct? Public shell systems is not a bad idea, > it's a business opportunity and a public service. If the OS is not > up to the task, don't blame the task. Any Unix OS is going to give you more or less the same out-of-box experience for shell users, the real difference being in the administrators who manage the machine(s). For shell machines especially, the admin simply has to have a reasonably high level of clue or they can count on a world of grief from their own users, and I don't care if the box in question is running Linux, FreeBSD or Solaris. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 3:58:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 2EB9C14BD8 for ; Tue, 13 Apr 1999 03:58:35 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip60.houston13.tx.pub-ip.psi.net [38.27.213.60]) by leap.innerx.net (Postfix) with ESMTP id 2AFA83707E; Tue, 13 Apr 1999 06:55:48 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id FAA36625; Tue, 13 Apr 1999 05:56:00 -0500 (CDT) (envelope-from chris) Date: Tue, 13 Apr 1999 05:55:52 -0500 From: Chris Costello To: "Daniel C. Sobral" Cc: chris@calldei.com, Matthew Dillon , Mattias Pantzare , Amancio Hasty , Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) Message-ID: <19990413055552.G2189@holly.dyndns.org> Reply-To: chris@calldei.com References: <199904102051.WAA07790@zed.ludd.luth.se> <199904102057.NAA01570@apollo.backplane.com> <19990413004728.C1968@holly.dyndns.org> <37131436.644E6E48@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <37131436.644E6E48@newsguy.com>; from Daniel C. Sobral on Tue, Apr 13, 1999 at 06:53:58PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 13, 1999, Daniel C. Sobral wrote: > What you really mean is that "FreeBSD is not a solution for public > shell systems", correct? Public shell systems is not a bad idea, > it's a business opportunity and a public service. If the OS is not > up to the task, don't blame the task. If you close your eyes and run towards a brick wall with the goal being to destroy it, and instead you injure yourself, it's not your forehead's fault or the wall's fault (no matter how much you cuss out the wall), but the person behind it. If you were strong and determined enough, perhaps you could solve the problem, but your forehead wasn't meant to crash through walls by default, and the brick wall wasn't meant to have a forehead plow through it. Make any sense? The admin shouldn't expect a public shell service to be secure out of the box with anything. BSD/OS, Linux, FreeBSD, NetBSD, OpenBSD - are any of these born shell service OS? I doubt it. It takes a hefty bit of 'tweaking', I'd imagine, to make a system fit to run a public shell. In "theory", no OS I've heard of is a "solution" for shell systems, at least out of the box and with an unexperienced administrator. Does this clear it up? > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "nothing better than the ability to perform cunning linguistics" -- Chris Costello Be careful when a loop exits to the same place from side and bottom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 4:52:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A00E15074 for ; Tue, 13 Apr 1999 04:52:39 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id EAA14736; Tue, 13 Apr 1999 04:50:19 -0700 (PDT) (envelope-from dillon) Date: Tue, 13 Apr 1999 04:50:19 -0700 (PDT) From: Matthew Dillon Message-Id: <199904131150.EAA14736@apollo.backplane.com> To: "Daniel C. Sobral" Cc: chris@calldei.com, Mattias Pantzare , Amancio Hasty , Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: <199904102051.WAA07790@zed.ludd.luth.se> <199904102057.NAA01570@apollo.backplane.com> <19990413004728.C1968@holly.dyndns.org> <37131436.644E6E48@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :What you really mean is that "FreeBSD is not a solution for public :shell systems", correct? Public shell systems is not a bad idea, :it's a business opportunity and a public service. If the OS is not :up to the task, don't blame the task. : :-- :Daniel C. Sobral (8-DCS) I would note that BEST.COM has been running, effectively, public shell systems for 5 years. The last couple of years have been using FreeBSD. It works just dandy. We put 2000 users on each box. Just because people aren't willing to spend thousands of hours making the kernel handle every conceivable user abuse doesn't make the machine a bad solution for a particular problem. With that sort of attitude, no operating system ever made could live up to your standards. FreeBSD does the things most easily handled in a kernel. You, the sysop, are supposed to do the things that are most easily handled by a sysop. That is inclusive of writing monitoring and kill scripts. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 5:13:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id DC10B1542C for ; Tue, 13 Apr 1999 05:13:34 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA02040; Tue, 13 Apr 1999 21:08:34 +0900 (JST) Message-ID: <3713335B.25F7FB16@newsguy.com> Date: Tue, 13 Apr 1999 21:06:51 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Matthew Dillon Cc: chris@calldei.com, Mattias Pantzare , Amancio Hasty , Dmitry Valdov , Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) References: <199904102051.WAA07790@zed.ludd.luth.se> <199904102057.NAA01570@apollo.backplane.com> <19990413004728.C1968@holly.dyndns.org> <37131436.644E6E48@newsguy.com> <199904131150.EAA14736@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > I would note that BEST.COM has been running, effectively, public shell > systems for 5 years. The last couple of years have been using FreeBSD. > It works just dandy. We put 2000 users on each box. > > Just because people aren't willing to spend thousands of hours making > the kernel handle every conceivable user abuse doesn't make the machine > a bad solution for a particular problem. With that sort of attitude, > no operating system ever made could live up to your standards. FreeBSD > does the things most easily handled in a kernel. You, the sysop, are > supposed to do the things that are most easily handled by a sysop. That > is inclusive of writing monitoring and kill scripts. Ok, disclaimer in the vain attempt to prevent further replies. I took an issue with blaming public shell accounts for perceived problems with the way FreeBSD manages them. I do think FreeBSD, and Unix, generally speaking, is one of the best deals available. It could be improved, and it does require non-clueless sysadmins. Saying "public shell accounts are a bad idea" is dismissing the real issues, and blaming the messenger for the bad news. What you, Dillon, were saying in the message quoted in the message I originally replied to, is to the point. FreeBSD can handle it, as long as the sysadmin knows what s/he is doing. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 5:23: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id B67C51561C for ; Tue, 13 Apr 1999 05:23:04 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id IAA08601; Tue, 13 Apr 1999 08:20:20 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904131220.IAA08601@kot.ne.mediaone.net> Subject: Re: DoS from local users (fwd) In-Reply-To: <19990413004728.C1968@holly.dyndns.org> from Chris Costello at "Apr 13, 1999 00:47:28 am" To: chris@calldei.com Date: Tue, 13 Apr 1999 08:20:19 -0400 (EDT) Cc: current@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" :Sun has a product for this, Solaris Resource Manager. = You don't need to tune user accounts, you need only put the =users in a separate login class (if that hasn't already been =done) and modify the resource limitation for that login =restriction. Speaking of which. Can we have the login class database distributed over NIS? => If one can't control one's users, one has no business managing => them. The last thing FreeBSD needs is some overly complex, => sophisticated scheduler designed to help bozo sysops stay on => their feet. = I agree with you very much here. Public shell systems are a =bad idea. In my opinion, you should trust someone before you =allow them to have an account on your system. Can we, perhaps, have a configurable maximum load level for each class? The users of the class will not be allowed to start new processes if the current load is above that number? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 5:57:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id BF3D814CA9 for ; Tue, 13 Apr 1999 05:57:31 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id IAA03555; Tue, 13 Apr 1999 08:52:59 -0400 (EDT) Message-ID: <002a01be85ad$66979880$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: , "UCHIYAMA Yasushi" References: <19990413165836K.uch@nop.or.jp> Subject: Re: newconfig/new-bus Date: Tue, 13 Apr 1999 08:59:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I just wanted to say that I see this as very important work. BSD and Linux interoperability is the best way to insure the BSDs survive (and maybe better) the Linux mania. Rick Whitesel NBase-Xyplex "If it is easy it probably sucks." ----- Original Message ----- From: UCHIYAMA Yasushi To: Sent: Tuesday, April 13, 1999 3:58 AM Subject: newconfig/new-bus ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/sys4c990410-newconfig990413.pat ch.gz This is newest newconfig patch against to 4.0-CURRENT(990410). FreeBSD/newconfig provides NetBSD compatible frame work ,bus_space(9) (bus_memio.h,bus_pio.h are no longer required.) and `bus name`_intr_establish. and also provides resource management. This feature makes easy to implement and feedback drivers among *BSD. As a sample, dev/pcmcia/ directory was imported from NetBSD. The amounts of #ifdef __FreeBSD__ is little. I'm working CardBus (dev/cardbus/) driver with NetBSD people. (originary written for NetBSD) Newconfig may not to be seem exciting, but this is powerful and flexible implementation in fact. please see this patch. Following table is guide map for comparison. newconfig new-bus framework: kern/subr_autoconf.c kern/subr_bus.c sys/device.h sys/bus.h resource management: kern/subr_rman.c kern/subr_rman.c i386/i386/resource.c i386/i386/nexus.c mainbus: i386/i386/mainbus.c i386/i386/nexus.c ISA bus: i386/isa/isa_machdep.c i386/i386/nisa.c PCI bus: i386/pci/pci_machdep.c pci/pci.c --- UCHIYAMA Yasushi uch@nop.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 5:59: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id DBB1A14CA9 for ; Tue, 13 Apr 1999 05:59:04 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id IAA08835; Tue, 13 Apr 1999 08:56:22 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904131256.IAA08835@kot.ne.mediaone.net> Subject: Re: DoS from local users (fwd) In-Reply-To: <199904131150.EAA14736@apollo.backplane.com> from Matthew Dillon at "Apr 13, 1999 04:50:19 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 13 Apr 1999 08:56:21 -0400 (EDT) Cc: current@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli". Look, here is a little script, which allows any user to perform a DoS attack! <. Khmm, yes indeed, but you can remove any user who does this. >. But shouldn't the system be able to sustain/detect this sort of attack? [... Nice theoretical discussion is skipped. ...] <. No, it is your responsibility as a sysop, do not give accounts to those you don't trust. >. Oh, well, but what about public-shell systems? <. Public shell systems are a bad idea! >. Just because FreeBSD can not handle it, does not mean the task itself is a bad idea... <. [Now we are all upset, flames start to light the sky]: . FreeBSD handles this here and here! . No OS will handle it quite right... . You just need to be a better sysop. >. Sorry, no offense meant... Why don't we admit this possibility exists (as well as many others, perhaps) for a local user to cause a DoS and may be someday someone will address it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 6: 3:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 4C1CD14CA9 for ; Tue, 13 Apr 1999 06:03:23 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA23572; Tue, 13 Apr 1999 15:01:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA12289; Tue, 13 Apr 1999 15:01:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mikhail Teterin Cc: dillon@apollo.backplane.com (Matthew Dillon), current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-reply-to: Your message of "Tue, 13 Apr 1999 08:56:21 EDT." <199904131256.IAA08835@kot.ne.mediaone.net> Date: Tue, 13 Apr 1999 15:01:01 +0200 Message-ID: <12287.924008461@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904131256.IAA08835@kot.ne.mediaone.net>, Mikhail Teterin writes: >Why don't we admit this possibility exists (as well as many others, >perhaps) for a local user to cause a DoS and may be someday someone >will address it? Because we have (counts for a moment, but as he flips to the third page of notes sighs deeply and gives up) more than plenty of things we need to do before that becomes the top priority problem... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 6: 9:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D98FB14CA9 for ; Tue, 13 Apr 1999 06:09:39 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id JAA25393; Tue, 13 Apr 1999 09:05:11 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Tue, 13 Apr 1999 09:05:10 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Kevin Day Cc: Matthew Dillon , hasty@rah.star-gate.com, dv@dv.ru, green@unixhelp.org, freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-Reply-To: <199904102057.PAA27724@home.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Apr 1999, Kevin Day wrote: > On the shell servers I run, we've got 200-300 users running tasks. > Occasionally, through intent or misconfiguration, a user either forkbombs, > or gets a large number of processes running sucking lots of cpu. > > I'd like to see an option that makes all the processes run by one uid have > the same weight as one process another uid is running. > > i.e. uid 1001 starts 40 processes eating as much cpu as they can. Then uid > 1002 starts up one process. Uid 1002's process gets 50% cpu, and uid 1001's > 40 processes get 50% cpu shared between them. > > This way, one errant user can't have as significant of an impact. > > Is this plausable? A while ago on -current, I posted a reference to a paper on lottery scheduling in FreeBSD. It allows you to provide scheduling weightings that (on average) share the CPU as described. Do a search of the -current or -hackers archive and it should show up. If not, let me know and I can dig up the reference. I believe it was a section of a CMU Tech Report. I don't know what the source code availability of that is, but it presumably was a month-long project for two grad students or something, so should be quite feasible. However, because processes in kernel mode are non-preemptible, it is impossible to deal with some of the connotations of a hog process. But because these processes are billed for some of the resources they consume in kernel mode (i.e., the CPU spent by their kernel thread), at least that can be taken into account. Matt makes the excellent point in another email that once you have this facility, you need to make sure that your CPU policy actually reflects what you want: do you want some process to displace some other process for "fairness" when fairness impedes throughput in such a way that you might be denying something else service because that something else cannot be represented in the scheduling policy? A combination of priorities and lottery tickets might be the best solution. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 6:27:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 57B61155CC for ; Tue, 13 Apr 1999 06:27:41 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id JAA08930 for current@freebsd.org; Tue, 13 Apr 1999 09:25:05 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904131325.JAA08930@kot.ne.mediaone.net> Subject: Re: DoS from local users (fwd) In-Reply-To: <12287.924008461@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 13, 1999 03:01:01 pm" To: current@freebsd.org Date: Tue, 13 Apr 1999 09:25:05 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"Why don't we admit this possibility exists (as well as many others, =>perhaps) for a local user to cause a DoS and may be someday someone =>will address it? =Because we have (counts for a moment, but as he flips to the third =page of notes sighs deeply and gives up) more than plenty of things =we need to do before that becomes the top priority problem... Ok. So, make this the (n+1)th on the list... Why is somebody saying "FreeBSD can not do this" gets flamed with "other OSes can not either" or "OS is not supposed to do this"? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 6:51: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id A490015249 for ; Tue, 13 Apr 1999 06:51:02 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA23785; Tue, 13 Apr 1999 15:48:42 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA12474; Tue, 13 Apr 1999 15:48:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) In-reply-to: Your message of "Tue, 13 Apr 1999 09:25:05 EDT." <199904131325.JAA08930@kot.ne.mediaone.net> Date: Tue, 13 Apr 1999 15:48:40 +0200 Message-ID: <12472.924011320@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904131325.JAA08930@kot.ne.mediaone.net>, Mikhail Teterin writes: >Poul-Henning Kamp once stated: > >=>Why don't we admit this possibility exists (as well as many others, >=>perhaps) for a local user to cause a DoS and may be someday someone >=>will address it? > >=Because we have (counts for a moment, but as he flips to the third >=page of notes sighs deeply and gives up) more than plenty of things >=we need to do before that becomes the top priority problem... > >Ok. So, make this the (n+1)th on the list... Why is somebody saying >"FreeBSD can not do this" gets flamed with "other OSes can not >either" or "OS is not supposed to do this"? Because people would rather be hacking code than arguing fine points of irrellevant theoretical issues ? Please let this thread die now. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 8:32: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B84F1156B7 for ; Tue, 13 Apr 1999 08:32:05 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id IAA15924; Tue, 13 Apr 1999 08:29:31 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA74547; Tue, 13 Apr 1999 08:29:30 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990413011033.V11572@futuresouth.com> Date: Tue, 13 Apr 1999 08:29:30 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: "Matthew D. Fuller" Subject: Re: cvsup Cc: current@FreeBSD.ORG, schuerge@wurzelausix.CS.Uni-SB.DE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew D. Fuller wrote: > > As a data point, CVSup runs nicely, but if I iconify it and deiconify it, > it takes about forEVER (maybe 10, 15 seconds on a PPro 180) to redisplay > itself completely. Yes, that's when the problem is most obvious. Here's the bottom line from my point of view. CVSup is slow to update the GUI because it is busy doing more important things, i.e., updating your files as quickly as it can. I agree that it can be annoying. But would you really want me to slow down file updates just so the GUI could look better? John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 10:33:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id CE6F81572B for ; Tue, 13 Apr 1999 10:33:34 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id MAA99906; Tue, 13 Apr 1999 12:41:09 -0500 (CDT) From: Joe Greco Message-Id: <199904131741.MAA99906@aurora.sol.net> Subject: Bad attitudes (was Re: DoS from local users) To: phk@critter.freebsd.dk, dillon@apollo.backplane.com, current@freebsd.org, mi@kot.ne.mediaone.net Date: Tue, 13 Apr 1999 12:41:09 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wow, this is getting deep. Mikhail, give it a break. You _cannot_ prevent a determined attacker from cauing a system a lot of heartache. For every subsystem that you harden, you introduce new weaknesses and more performance hits which can themselves be used as vulnerabilities. I'd bet my reputation on being able to DoS any box you can present to me, given sufficient technical knowledge of the box and what measures you have implemented. Now, PHK, Matt Dillon, Jordan, and all these other fine hackers are hammering out code for this fine OS, and each has their own area of interest and specialty. (I don't mean to leave anyone out BTW). Each is doing their own bit to make the OS better. Sometimes you will be able to get one of them interested in a particularly good idea, sometimes you won't. There have often been things I've wanted to see in FreeBSD, and sometimes you just have to go hammer out the code yourself and submit it. I've done my own bits... anyone who looks at getty or some of the SLIP code will find my fingerprints on them. Sometimes I've talked people into doing useful things... John Dyson, thanks for madvise(), just for example. Is FreeBSD ideal for a public shell system? No. Yet it is a hell of a lot better than Solaris, which many ISP's use. It's a hell of a lot better than SunOS, which _I'VE_ used for a decade to provide public shell access. If you want to run a public shell system, you have to do so with your eyes wide open. You have to be an experienced admin, willing to take some time to make it work right, or you have to be a clueless newbie admin who is willing to live on the box 24/7. Once you establish this, then any help the OS provides merely falls into the "wonderful fantastic safety net" category. Now, if you'd LIKE the OS to provide a wonderful fantastic safety net, then by all means, STFU and go write one. I'm continually amazed at the fantastic improvements being introduced into FreeBSD on a regular basis... ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 10:36:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 87DC115773 for ; Tue, 13 Apr 1999 10:36:38 -0700 (PDT) (envelope-from camel@avias.com) Received: from CAMEL (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id VAA06616 for ; Tue, 13 Apr 1999 21:34:17 +0400 (MSD) (envelope-from camel@avias.com) Date: Tue, 13 Apr 1999 21:34:25 +0400 From: Ilya Naumov X-Mailer: The Bat! (v1.31) UNREG Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <12898.990413@avias.com> To: Gianmarco Giovannelli Subject: Re: ftp hangs on -current In-reply-To: <4.1.19990408054254.00a4ab80@194.184.65.4> References: <4.1.19990408054254.00a4ab80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Gianmarco, Thursday, April 08, 1999, 7:49:52 AM, you wrote: GG> "ftp" on 4.0-very-current (post egcs make world) randomly hangs during GG> sessions... GG> I never succeded in finishing a session lately. GG> To transfer some files from my home to my isp server I had to do an "ftp" GG> from the server and a "get" to them... GG> The ftp server works normally and fetch is ok ... GG> Probably it is a fault of my system, if no other experiences it. you're not alone with this problem here - i have the same one. and it seems that it is somehow related to natd, because ftp works quite well when i disable this daemon. any ideas? by the way, i have a question to natd gurus. i have faced with a strange trouble - natd alters _all_ packets passing through the interface (and it is clearly visible when i start natd with -v option) completely ignoring -u option. but i would like to alter packets for unregistered source addresses (192.168.0.0/16) only. what should i do? i run natd with "-u -n ed1" options and firewall rule for natd is: 00100 divert 8668 ip from any to any via ed1 Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 11:59:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from stephens.ml.org (cm2081634025.ponderosa.ispchannel.com [208.163.40.25]) by hub.freebsd.org (Postfix) with ESMTP id A643A158C6 for ; Tue, 13 Apr 1999 11:59:03 -0700 (PDT) (envelope-from tas@stephens.ml.org) Received: from stephens.ml.org (localhost [127.0.0.1]) by stephens.ml.org (8.9.2/8.9.2) with ESMTP id TAA05150; Tue, 13 Apr 1999 19:56:36 +0100 (BST) (envelope-from tas@stephens.ml.org) Message-Id: <199904131856.TAA05150@stephens.ml.org> To: current@FreeBSD.ORG Cc: "Matthew D. Fuller" , schuerge@wurzelausix.CS.Uni-SB.DE, John Polstra , Thomas Stephens From: Thomas Stephens Subject: Re: cvsup In-reply-to: Your message of "Tue, 13 Apr 1999 08:29:30 PDT." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5145.924029795.1@stephens.ml.org> Date: Tue, 13 Apr 1999 11:56:36 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: >Matthew D. Fuller wrote: >> >> As a data point, CVSup runs nicely, but if I iconify it and deiconify it, >> it takes about forEVER (maybe 10, 15 seconds on a PPro 180) to redisplay >> itself completely. > >Yes, that's when the problem is most obvious. > >Here's the bottom line from my point of view. CVSup is slow to update >the GUI because it is busy doing more important things, i.e., updating >your files as quickly as it can. I agree that it can be annoying. >But would you really want me to slow down file updates just so the GUI >could look better? In my view, the non-GUI mode provides excellent feedback (depending on the level of verbosity), so I'd certainly prefer to see the focus remain speed, as opposed to the GUI. I seem to recall that a certain OS, which will remain nameless, used to spend more file-copy time calculating and updating progress bars than actually moving data (all controlled I/O, IIRC). It looked nice, was very responsive and the progress bars were smooth and accurate to the pixel, but it isn't the route I'd choose! (To be fair, this was probably a relic of the floppy-drive days.) Thomas Stephens tas@stephens.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 12: 9:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7A23114C4A for ; Tue, 13 Apr 1999 12:09:35 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA54777; Tue, 13 Apr 1999 20:11:07 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 13 Apr 1999 20:11:07 +0100 (BST) From: Doug Rabson To: Rick Whitesel Cc: current@freebsd.org, UCHIYAMA Yasushi Subject: Re: newconfig/new-bus In-Reply-To: <002a01be85ad$66979880$d3e4b38c@xyplex.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Apr 1999, Rick Whitesel wrote: > Hi: > I just wanted to say that I see this as very important work. BSD and > Linux interoperability is the best way to insure the BSDs survive (and maybe > better) the Linux mania. I think the work is important too but it won't improve interoperability with Linux driver code... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 12:12: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DC10C14FAC for ; Tue, 13 Apr 1999 12:11:55 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id MAA16940 for ; Tue, 13 Apr 1999 12:09:35 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA75125 for current@freebsd.org; Tue, 13 Apr 1999 12:09:35 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 13 Apr 1999 12:09:35 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: "newbus" CVSup collection Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since some interested parties don't have CVSup access to freefall, I have made the "newbus" collection that Peter announced available on one public mirror site: cvsup2.freebsd.org. Use collection "newbus", release=cvs. Don't forget to specify a dedicated directory for the "prefix". This collection is entirely separate from the others, and you wouldn't want it to be blatted on top of your existing files. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 12:17:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 9B37814C4A for ; Tue, 13 Apr 1999 12:17:16 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id PAA92766; Tue, 13 Apr 1999 15:14:12 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904131914.PAA92766@misha.cisco.com> Subject: Re: cvsup In-Reply-To: from John Polstra at "Apr 13, 1999 08:29:30 am" To: jdp@polstra.com (John Polstra) Date: Tue, 13 Apr 1999 15:14:12 -0400 (EDT) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra once wrote: > > As a data point, CVSup runs nicely, but if I iconify it and > > deiconify it, it takes about forEVER (maybe 10, 15 seconds on a PPro > > 180) to redisplay itself completely. > Yes, that's when the problem is most obvious. > > Here's the bottom line from my point of view. CVSup is slow to update > the GUI because it is busy doing more important things, i.e., updating > your files as quickly as it can. I agree that it can be annoying. But > would you really want me to slow down file updates just so the GUI > could look better? No-no :-), please, don't... However, the CPU is not 100% busy, and the cvsup is still slow to update sometimes... Updating it does not need anything but the CPU, does it (on the local display)? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 12:24:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 4E4EB15180 for ; Tue, 13 Apr 1999 12:24:43 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id PAA09464; Tue, 13 Apr 1999 15:20:00 -0400 (EDT) Message-ID: <001101be85e3$77fd1e20$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Doug Rabson" Cc: , "UCHIYAMA Yasushi" References: Subject: Re: newconfig/new-bus Date: Tue, 13 Apr 1999 15:26:02 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I should have been more clear. BSD driver interoperability is a seperate issue from Linux application interoperability but I think both are important. Rick Whitesel Scientist NBase-Xyplex rwhitesel@nbase-xyplex.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 ----- Original Message ----- From: Doug Rabson To: Rick Whitesel Cc: ; UCHIYAMA Yasushi Sent: Tuesday, April 13, 1999 3:11 PM Subject: Re: newconfig/new-bus On Tue, 13 Apr 1999, Rick Whitesel wrote: > Hi: > I just wanted to say that I see this as very important work. BSD and > Linux interoperability is the best way to insure the BSDs survive (and maybe > better) the Linux mania. I think the work is important too but it won't improve interoperability with Linux driver code... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 12:26:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 48CA515180 for ; Tue, 13 Apr 1999 12:26:11 -0700 (PDT) (envelope-from schuerge@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id VAA05162; Tue, 13 Apr 1999 21:23:36 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id VAA08375; Tue, 13 Apr 1999 21:23:35 +0200 (CEST) Received: (from schuerge@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id VAA21668; Tue, 13 Apr 1999 21:23:30 +0200 (CEST) From: Thomas Schuerger Message-Id: <199904131923.VAA21668@wurzelausix.cs.uni-sb.de> Subject: Re: cvsup To: mi@aldan.algebra.com Date: Tue, 13 Apr 1999 21:23:30 +0200 (CEST) Cc: jdp@polstra.com, current@FreeBSD.ORG In-Reply-To: <199904131914.PAA92766@misha.cisco.com> from "Mikhail Teterin" at Apr 13, 99 03:14:12 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Here's the bottom line from my point of view. CVSup is slow to update > > the GUI because it is busy doing more important things, i.e., updating > > your files as quickly as it can. I agree that it can be annoying. But > > would you really want me to slow down file updates just so the GUI > > could look better? > > No-no :-), please, don't... However, the CPU is not 100% busy, and > the cvsup is still slow to update sometimes... Updating it does > not need anything but the CPU, does it (on the local display)? cvsup is mostly based on disk (and network) I/O, so there shouldn't be a problem with properly updating the GUI. Someone said it is done in a separate process, so I still wonder why the GUI is updated so slowly on my PII/450. Ciao, Thomas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 12:48:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C2D8E1551B for ; Tue, 13 Apr 1999 12:48:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id MAA28822; Tue, 13 Apr 1999 12:45:29 -0700 Date: Tue, 13 Apr 1999 12:45:28 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Rick Whitesel Cc: Doug Rabson , current@FreeBSD.ORG, UCHIYAMA Yasushi Subject: Re: newconfig/new-bus In-Reply-To: <001101be85e3$77fd1e20$d3e4b38c@xyplex.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi: > I should have been more clear. BSD driver interoperability is a seperate > issue from Linux application interoperability but I think both are > important. For an example of Linux/*BSD driver interoperability and the grief and difficulties therein, you might want to look at the Qlogic SCSI/FibreChannel driver I've done. It exists for FreeBSD,OpenBSD,NetBSD and Linux. It's a dicey business trying to straddle this broad of a set of fences. The take home lesson here is that in order to make a dirver work without overloading a platform specific areas is that the core driver has to be single threaded, not do locking and not do too much porpoising in and out of the platform layers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 12:57:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 76AD6152E7 for ; Tue, 13 Apr 1999 12:55:39 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 16D6A1F4F; Wed, 14 Apr 1999 03:53:16 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Rick Whitesel" Cc: "Doug Rabson" , current@FreeBSD.ORG, "UCHIYAMA Yasushi" Subject: Re: newconfig/new-bus In-reply-to: Your message of "Tue, 13 Apr 1999 15:26:02 -0400." <001101be85e3$77fd1e20$d3e4b38c@xyplex.com> Date: Wed, 14 Apr 1999 03:53:16 +0800 From: Peter Wemm Message-Id: <19990413195319.16D6A1F4F@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rick Whitesel" wrote: > Hi: > I should have been more clear. BSD driver interoperability is a seperate > issue from Linux application interoperability but I think both are > important. I don't want to get hopes up prematurely, but we think we might be able to emulate enough of the newconfig-style interface via the same sort of wrapper shims that we use for the old isa and pci drivers. If that works out, then it should make porting/using a NetBSD/OpenBSD/BSDI driver a lot easier. There's bound to be #ifdefs required no matter what, but it shouldn't require two totally different config interfaces. Of course, this is still a "might" case since it hasn't been written. However, it would be quite hard to get this to work seamlessly for sub-busses and devices, eg: PCIC->PCCARD->CARDBUS->etc. Simple devices shouldn't be too hard though, but even then there are seriously non-trivial differences in the tty, block/character devices, VM, networking, etc. Even if the config interface was compatable it wouldn't ever be a 'drop in' option, even with 'newconfig'. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 13: 3:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6C57714EAA for ; Tue, 13 Apr 1999 13:02:59 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA15998; Tue, 13 Apr 1999 12:55:41 -0700 (PDT) Date: Tue, 13 Apr 1999 12:55:40 -0700 (PDT) From: Julian Elischer To: UCHIYAMA Yasushi Cc: current@FreeBSD.ORG Subject: Re: newconfig/new-bus In-Reply-To: <19990413165836K.uch@nop.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So I've been lookin gat this patch set.. it seems to duplicate a lot of code already in FreeBSD, by just replacing it with the equivalent code from NetBSD. (or rather, jsut adding the NetBSD code and not using the FreeBSD version. This is acceptable in a test scenario). What is not so clear is what the chances are of us getting something that takes the best features from NetBSD and the best features from the new-bus code. There are similarities, but the differences are less obvious. The framework may be totally different, but how different do the DRIVERS have to be? julian (still reading the new-config stuff) On Tue, 13 Apr 1999, UCHIYAMA Yasushi wrote: > ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/sys4c990410-newconfig990413.patch.gz > This is newest newconfig patch against to 4.0-CURRENT(990410). > > FreeBSD/newconfig provides NetBSD compatible frame work ,bus_space(9) > (bus_memio.h,bus_pio.h are no longer required.) and `bus name`_intr_establish. > and also provides resource management. > This feature makes easy to implement and feedback drivers among *BSD. > As a sample, dev/pcmcia/ directory was imported from NetBSD. The > amounts of #ifdef __FreeBSD__ is little. > I'm working CardBus (dev/cardbus/) driver with NetBSD people. > (originary written for NetBSD) > > Newconfig may not to be seem exciting, but this is powerful and > flexible implementation in fact. please see this patch. > > Following table is guide map for comparison. > > newconfig new-bus > framework: > kern/subr_autoconf.c kern/subr_bus.c > sys/device.h sys/bus.h > resource management: > kern/subr_rman.c kern/subr_rman.c > i386/i386/resource.c i386/i386/nexus.c > > mainbus: > i386/i386/mainbus.c i386/i386/nexus.c > ISA bus: > i386/isa/isa_machdep.c i386/i386/nisa.c > PCI bus: > i386/pci/pci_machdep.c pci/pci.c > --- > UCHIYAMA Yasushi > uch@nop.or.jp > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 13:17:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id CB17714CED for ; Tue, 13 Apr 1999 13:17:07 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (postfix@myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id XAA03989 for ; Tue, 13 Apr 1999 23:14:46 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 43F63DF; Tue, 13 Apr 1999 23:14:47 +0300 (EEST) Message-ID: <19990413231447.A14761@matti.ee> Date: Tue, 13 Apr 1999 23:14:47 +0300 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: ATA disks can do command queueing? Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! Recently installed March 12 -current snapshot and compiled kernel with new IDE subsystem. I see interesting lines in dmesg: npx0: INT 16 interface ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata0: slave: settting up UDMA2 mode on PIIX4 chip OK ad1: ATA-4 disk at ata0 as slave ad1: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 31 depth queue, DMA mode ata1: master: settting up UDMA2 mode on PIIX4 chip OK ad2: ATA-4 disk at ata1 as master ad2: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 31 depth queue, DMA mode changing root device to wd0s1a vinum: loaded vinum: reading configuration from /dev/wd2e vinum: updating configuration from /dev/wd1e ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Does it mean that new ATA disks can queue up commands (something similar to SCSI disks?)? I feel like I heard something in the -current list lately but I'm not sure... -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 13:19:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 88D6914CED for ; Tue, 13 Apr 1999 13:19:19 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id WAA25479; Tue, 13 Apr 1999 22:17:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id WAA13881; Tue, 13 Apr 1999 22:16:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mi@aldan.algebra.com Cc: dillon@apollo.backplane.com (Matthew Dillon), current@FreeBSD.ORG Subject: Re: swap-related problems In-reply-to: Your message of "Mon, 12 Apr 1999 11:05:21 EDT." <199904121505.LAA70241@misha.cisco.com> Date: Tue, 13 Apr 1999 22:16:58 +0200 Message-ID: <13879.924034618@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904121505.LAA70241@misha.cisco.com>, Mikhail Teterin writes: >Matthew Dillon once wrote: > >> If you unset the datasize limit and the program does not exceed >> the maximum system-supported datasize limit, malloc() should not >> return NULL even if the system is out of swap. > >Can you explain why? Our malloc(3) is a little fuzzy as to the >circumstances under which malloc will fail, but on Solaris, it is >more explicit: > > RETURN VALUES > If there is no available memory, malloc(), realloc(), > memalign(), valloc(), and calloc() return a null pointer. > >I consider being out-of-swap as having "no available memory". Wouldn't you? The trouble is, there is no such thing as "no available memory". What we have instead is "not enough memory available for this specific request". For phkmalloc I can say in particular that there is a pool for each size of chunk (16,32,64...2048 bytes and for pages. If you run out of one of these there may still be stuff in the other pools. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 14: 1:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BE6D714C91 for ; Tue, 13 Apr 1999 14:01:08 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA06683; Tue, 13 Apr 1999 22:58:45 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904132058.WAA06683@freebsd.dk> Subject: Re: ATA disks can do command queueing? In-Reply-To: <19990413231447.A14761@matti.ee> from Vallo Kallaste at "Apr 13, 1999 11:14:47 pm" To: vallo@matti.ee Date: Tue, 13 Apr 1999 22:58:45 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Vallo Kallaste wrote: > Hello ! > > Recently installed March 12 -current snapshot and compiled kernel > with new IDE subsystem. I see interesting lines in dmesg: > ad1: 16 secs/int, 31 depth queue, DMA mode > Does it mean that new ATA disks can queue up commands (something > similar to SCSI disks?)? I feel like I heard something in the > -current list lately but I'm not sure... Yep that is exactly what it means, however the driver in -current doesn't take advantage of it yet, but its on my TODO list. The reason why I put in this verbosity, is so I can get a hint to which drives support it, and it seems IBM are on of the few that does. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 14:29:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D012E1508F for ; Tue, 13 Apr 1999 14:29:13 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id OAA17572; Tue, 13 Apr 1999 14:26:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA75285; Tue, 13 Apr 1999 14:26:53 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904131914.PAA92766@misha.cisco.com> Date: Tue, 13 Apr 1999 14:26:53 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: mi@aldan.algebra.com Subject: Re: cvsup Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > However, the CPU is not 100% busy, and the cvsup is still slow to > update sometimes... Updating it does not need anything but the CPU, > does it (on the local display)? Correct. I have not tried to analyze where the delays come from. But I do have a guess. CVSup uses user-level threads. If a thread gets blocked waiting for network I/O, the thread scheduler can run a different thread while it is waiting. A subsequent call to select() will inform the scheduler when the I/O can be resumed. But that isn't possible for disk I/O. If you call read() or write() on a disk file, it never returns EAGAIN. It always blocks in the kernel, non-interruptible by signals. When that happens, the process is blocked and it can't run any other threads or do anything else at all until the read/write call has completed. Since CVSup is so disk-intensive, I suspect it is wasting a lot of time blocked in those calls. An interested person could probably confirm or deny that using ktrace. If we had kernel threads and Modula-3 supported them, this wouldn't be a problem. But those are two very big ifs. :-( John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 14:29:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 6496214F21 for ; Tue, 13 Apr 1999 14:29:39 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id QAA02008; Tue, 13 Apr 1999 16:40:13 -0500 (EST) Date: Tue, 13 Apr 1999 16:40:11 -0500 (EST) From: Alfred Perlstein To: Thomas Schuerger Cc: mi@aldan.algebra.com, jdp@polstra.com, current@FreeBSD.ORG Subject: Re: cvsup In-Reply-To: <199904131923.VAA21668@wurzelausix.cs.uni-sb.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Apr 1999, Thomas Schuerger wrote: > > > Here's the bottom line from my point of view. CVSup is slow to update > > > the GUI because it is busy doing more important things, i.e., updating > > > your files as quickly as it can. I agree that it can be annoying. But > > > would you really want me to slow down file updates just so the GUI > > > could look better? > > > > No-no :-), please, don't... However, the CPU is not 100% busy, and > > the cvsup is still slow to update sometimes... Updating it does > > not need anything but the CPU, does it (on the local display)? > > cvsup is mostly based on disk (and network) I/O, so there shouldn't > be a problem with properly updating the GUI. Someone said it is > done in a separate process, so I still wonder why the GUI is updated > so slowly on my PII/450. My lame assumption is that modula3 uses userland threads that may be io blocking but intrupted with signals or some such if the io is blocked too long. generally i: a) use options -g -L 2 and use 'tee' to dump to a file and review that later, or b) i wait till the run is done before messing with the GUI. oh, and of course subscribe to freebsd-cvs list. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 14:30:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 92C5B14F47 for ; Tue, 13 Apr 1999 14:30:46 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id OAA17595; Tue, 13 Apr 1999 14:28:25 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA75294; Tue, 13 Apr 1999 14:28:25 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904131923.VAA21668@wurzelausix.cs.uni-sb.de> Date: Tue, 13 Apr 1999 14:28:25 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Thomas Schuerger Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Schuerger wrote: > cvsup is mostly based on disk (and network) I/O, so there shouldn't > be a problem with properly updating the GUI. Someone said it is > done in a separate process, so I still wonder why the GUI is updated > so slowly on my PII/450. Not a separate process -- a separate thread. It uses user-level threads. If the process blocks in a disk I/O call, all threads stop until the call completes. That's just the way Unix works. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 14:49:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from f77.nop.or.jp (f77.nop.or.jp [210.145.217.241]) by hub.freebsd.org (Postfix) with ESMTP id A10DD150D6 for ; Tue, 13 Apr 1999 14:49:27 -0700 (PDT) (envelope-from uch@nop.or.jp) Received: from localhost (localhost [127.0.0.1]) by f77.nop.or.jp (8.9.1a/3.7W) with ESMTP id GAA09217; Wed, 14 Apr 1999 06:46:57 +0900 (JST) To: current@FreeBSD.ORG Cc: julian@whistle.com Subject: Re: newconfig/new-bus In-Reply-To: Your message of "Tue, 13 Apr 1999 12:55:40 -0700 (PDT)" References: X-Mailer: Mew version 1.92 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990414064657B.uch@nop.or.jp> Date: Wed, 14 Apr 1999 06:46:57 +0900 From: UCHIYAMA Yasushi X-Dispatcher: imput version 971024 Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | it seems to duplicate a lot of code already in FreeBSD, by just replacing | it with the equivalent code from NetBSD. | | (or rather, jsut adding the NetBSD code and not using the FreeBSD | version. This is acceptable in a test scenario). ep at isa/pcmcia/cardbus ... I fully rewrote code to use newconfig/bus_space(9). (newconfig goal sample) sn ... not in FreeBSD (PAO has this) fe ... Originally same code. ne at pci ... My NetBSD compatiblity test sample. OK to remove. ne at pcmcia ... NetBSD drivers already bus-specific frontend code was separated from bus-independent(backend) code. So easy to adapt another buses. I've tested its separation for FreeBSD's ep code, but it was already done by NetBSD. ed case, I determined to use NetBSD driver.(rewriting was difficult...)But if you love FreeBSD origine, you can replace it. --- UCHIYAMA Yasushi uch@nop.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 14:51:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 1514314CBE for ; Tue, 13 Apr 1999 14:51:24 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA13399; Tue, 13 Apr 1999 17:48:31 -0400 (EDT) Date: Tue, 13 Apr 1999 17:48:31 -0400 (EDT) From: Daniel Eischen Message-Id: <199904132148.RAA13399@pcnet1.pcnet.com> To: jdp@polstra.com, mi@aldan.algebra.com Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > Correct. I have not tried to analyze where the delays come from. > But I do have a guess. > > CVSup uses user-level threads. If a thread gets blocked waiting for > network I/O, the thread scheduler can run a different thread while it > is waiting. A subsequent call to select() will inform the scheduler > when the I/O can be resumed. > > But that isn't possible for disk I/O. If you call read() or write() > on a disk file, it never returns EAGAIN. It always blocks in the > kernel, non-interruptible by signals. When that happens, the process > is blocked and it can't run any other threads or do anything else > at all until the read/write call has completed. Since CVSup is so > disk-intensive, I suspect it is wasting a lot of time blocked in those > calls. An interested person could probably confirm or deny that using > ktrace. > Does Modula-3 use libc_r, or does it have it's own user thread support? The recent set of commits to libc_r changed the thread scheduling mechanism to use ITIMER_PROF instead of ITIMER_VIRTUAL. This was to allow for fairer scheduling with I/O bound threads. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 14:58:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 9F3E21502D for ; Tue, 13 Apr 1999 14:58:09 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id OAA20145; Tue, 13 Apr 1999 14:50:27 -0700 (PDT) Date: Tue, 13 Apr 1999 14:50:26 -0700 (PDT) From: Julian Elischer To: UCHIYAMA Yasushi Cc: current@FreeBSD.ORG Subject: Re: newconfig/new-bus In-Reply-To: <19990414064657B.uch@nop.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, UCHIYAMA Yasushi wrote: > NetBSD drivers already bus-specific frontend code was separated from > bus-independent(backend) code. So easy to adapt another buses. > I've tested its separation for FreeBSD's ep code, but it was already > done by NetBSD. ed case, I determined to use NetBSD driver.(rewriting > was difficult...)But if you love FreeBSD origine, you can replace it. No, I was just curious. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15: 3:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id D9E0E14CBE for ; Tue, 13 Apr 1999 15:03:17 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id RAA28126; Tue, 13 Apr 1999 17:00:53 -0500 (CDT) Date: Tue, 13 Apr 1999 17:00:53 -0500 From: "Matthew D. Fuller" To: John Polstra Cc: current@FreeBSD.ORG, schuerge@wurzelausix.CS.Uni-SB.DE Subject: Re: cvsup Message-ID: <19990413170053.B25108@futuresouth.com> References: <19990413011033.V11572@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from John Polstra on Tue, Apr 13, 1999 at 08:29:30AM -0700 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 13, 1999 at 08:29:30AM -0700, a little birdie told me that John Polstra remarked > Matthew D. Fuller wrote: > > > > As a data point, CVSup runs nicely, but if I iconify it and deiconify it, > > it takes about forEVER (maybe 10, 15 seconds on a PPro 180) to redisplay > > itself completely. > > Yes, that's when the problem is most obvious. > > Here's the bottom line from my point of view. CVSup is slow to update > the GUI because it is busy doing more important things, i.e., updating > your files as quickly as it can. I agree that it can be annoying. > But would you really want me to slow down file updates just so the GUI > could look better? Oh god no; by all means, make the file updates faster!! After about 4 days without cvsup'ing (including lots of fun gcc/egcs) updates it took 6:16 to update my CVS repo including: *default release=cvs src-all src-eBones src-secure ports-all www doc-all --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15: 7:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 78B4114CBE for ; Tue, 13 Apr 1999 15:07:19 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (postfix@myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id AAA07586; Wed, 14 Apr 1999 00:58:17 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 4E5DDDF; Wed, 14 Apr 1999 00:58:18 +0300 (EEST) Message-ID: <19990414005818.A15299@matti.ee> Date: Wed, 14 Apr 1999 00:58:18 +0300 From: Vallo Kallaste To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA disks can do command queueing? Reply-To: vallo@matti.ee References: <19990413231447.A14761@matti.ee> <199904132058.WAA06683@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904132058.WAA06683@freebsd.dk>; from Soren Schmidt on Tue, Apr 13, 1999 at 10:58:45PM +0200 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 13, 1999 at 10:58:45PM +0200, Soren Schmidt wrote: > Yep that is exactly what it means, however the driver in -current > doesn't take advantage of it yet, but its on my TODO list. > The reason why I put in this verbosity, is so I can get a hint to > which drives support it, and it seems IBM are on of the few that > does. Nice. As you say you need hints I can try 14gig 7200rpm IBM also, one is on my table. I think it can behave similarly. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15:21: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id 8058F14C91 for ; Tue, 13 Apr 1999 15:21:06 -0700 (PDT) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.2/8.9.1) with SMTP id WAA49265 for ; Tue, 13 Apr 1999 22:17:42 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19990413151601.009b2100@localhost> X-Sender: kurt@localhost (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 13 Apr 1999 15:16:01 -0700 To: freebsd-current@freebsd.org From: "Kurt D. Zeilenga" Subject: compiler specs for -pthread/-kthread Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To facilate auto detection of the local threading environment, it would be nice if the -?thread options set all the necessary compiler/linker flags. It is a common practace for such options to specify both compilation and link options. I suggest the EGCS specs be adjusted to: -pthread => -D_THREAD_SAFE -D_UTHREADS -lc_r -kthread => -D_THREAD_SAFE -D_KTHREADS -lpthread If the LinuxThread "port" is targetted to be -kthread: -kthread => -D_REENRANT -D_LINUXTHREADS -lpthread If the LinuxThread "port" is NOT targetted to be -kthread, I suggest another -?thread option be added and the library specified as -llthread. -?thread => -D_REENTRANT -D_LINUXTHREADS -llthread After modify the specification, the headers/libraries would be adjusted as needed. I can easily submit diffs if desirable. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15:39:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id B430314C9C for ; Tue, 13 Apr 1999 15:39:09 -0700 (PDT) (envelope-from tim@scratch.demon.co.uk) Received: from [212.228.22.156] (helo=franklin.matlink) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 10XBnT-000CjA-0C for freebsd-current@freebsd.org; Tue, 13 Apr 1999 22:36:49 +0000 Received: (from tim@localhost) by franklin.matlink (8.9.3/8.9.3) id XAA52235 for freebsd-current@freebsd.org; Tue, 13 Apr 1999 23:34:03 +0100 (BST) (envelope-from tim) Date: Tue, 13 Apr 1999 23:34:03 +0100 From: Tim Preece To: freebsd-current@freebsd.org Subject: Re: ftp hangs on -current Message-ID: <19990413233402.A52219@franklin.matlink> Reply-To: Tim Preece Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: x-unknown X-Mailer: Balsa 0.4.9 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Apr 1999 18:34:25 Ilya Naumov wrote: > Hello Gianmarco, > > Thursday, April 08, 1999, 7:49:52 AM, you wrote: > > GG> "ftp" on 4.0-very-current (post egcs make world) randomly hangs during > GG> sessions... > GG> I never succeded in finishing a session lately. > GG> To transfer some files from my home to my isp server I had to do an "ftp" > GG> from the server and a "get" to them... > > GG> The ftp server works normally and fetch is ok ... > GG> Probably it is a fault of my system, if no other experiences it. > > you're not alone with this problem here - i have the same one. and it > seems that it is somehow related to natd, because ftp works quite > well when i disable this daemon. any ideas? Well I am also experiencing something like this with ports and sendmail connections - intermittently, unfortunatly I am not running natd ! > > by the way, i have a question to natd gurus. i have faced with a > strange trouble - natd alters _all_ packets passing through the > interface (and it is clearly visible when i start natd with -v option) > completely ignoring -u option. but i would like to alter packets > for unregistered source addresses (192.168.0.0/16) only. what should i do? > > i run natd with "-u -n ed1" options and firewall rule for natd is: > 00100 divert 8668 ip from any to any via ed1 > > > Best regards, > Ilya mailto:camel@avias.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Tim. I'd rather boot Bill Gates than Windoze any day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15:41: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6F55D14C9C for ; Tue, 13 Apr 1999 15:40:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id PAA17991; Tue, 13 Apr 1999 15:38:39 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA75600; Tue, 13 Apr 1999 15:38:38 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904132148.RAA13399@pcnet1.pcnet.com> Date: Tue, 13 Apr 1999 15:38:38 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Daniel Eischen Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > Does Modula-3 use libc_r, or does it have it's own user thread support? It has its own. It can be ported to use native threads, but it's a non-negligible amount of work. It hardly seems worth it for the GUI alone. > The recent set of commits to libc_r changed the thread scheduling > mechanism to use ITIMER_PROF instead of ITIMER_VIRTUAL. This was > to allow for fairer scheduling with I/O bound threads. My hunch is that it's not a fairness issue. It's just the fact that when you block in disk I/O, the whole process (all threads) blocks. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15:44: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 46A7B14C9C for ; Tue, 13 Apr 1999 15:44:06 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id PAA18006; Tue, 13 Apr 1999 15:41:46 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA75613; Tue, 13 Apr 1999 15:41:46 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990413170053.B25108@futuresouth.com> Date: Tue, 13 Apr 1999 15:41:46 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: "Matthew D. Fuller" Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew D. Fuller wrote: > After about 4 days without cvsup'ing (including lots of fun gcc/egcs) > updates it took 6:16 to update my CVS repo including: When CVSup is fetching entirely new files, it can't do anything much smarter than compress them. It can't avoid moving the bits from point A to point B. In the case of egcs, that's a lot of bits. But six hours and sixteen minutes? That's awfully slow. You must have had a really bad link that day. I'd try a few different mirror sites if I were you. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15:47:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 4FB7914C9C for ; Tue, 13 Apr 1999 15:47:36 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id SAA93415 for current@freebsd.org; Tue, 13 Apr 1999 18:45:15 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904132245.SAA93415@misha.cisco.com> Subject: Re: swap-related problems In-Reply-To: <13879.924034618@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 13, 1999 10:16:58 pm" To: current@freebsd.org Date: Tue, 13 Apr 1999 18:45:15 -0400 (EDT) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp once wrote: > >> If you unset the datasize limit and the program does not exceed > >> the maximum system-supported datasize limit, malloc() should > >> not return NULL even if the system is out of swap. > >Can you explain why? Our malloc(3) is a little fuzzy as to the > >circumstances under which malloc will fail, but on Solaris, it is > >more explicit: > > RETURN VALUES > > If there is no available memory, malloc(), realloc(), > > memalign(), valloc(), and calloc() return a null pointer. > > > >I consider being out-of-swap as having "no available memory". Wouldn't you? > The trouble is, there is no such thing as "no available memory". Well, this is just an implementation detail, is not it? I don't mean to critisize, or anything, but such thing as "no available memory" is a fairly intuitive... Coming down, again, the malloc should return a usable memory if available and NULL if it's not. Is not this a "natural" semantics? Why can a program die because _another_ program ate up all the rest of the memory? > What we have instead is "not enough memory available for this specific > request". > For phkmalloc I can say in particular that there is a pool for each > size of chunk (16,32,64...2048 bytes and for pages. If you run out of > one of these there may still be stuff in the other pools. Then the malloc may need to take its time rearranging the pools, or whatever... It gets it right if there is a datasize limit, right? But the current behaviour under low-memory conditions seems wrong to me, and is certainly different from what the Solaris' malloc(3C) states. -mi DISCLAIMER: a) this message was not meant to offend; b) I realize, the Solaris' malloc() may also be broken in many ways; c) FreeBSD is rightfully the OS of choice for many (including myself); d) I realize, that FreeBSD is wonderfull and I myself use it _all_ i386 machines under my control and on most i386 machines outside of my control. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15:47:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id 24CDD15095 for ; Tue, 13 Apr 1999 15:47:38 -0700 (PDT) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id RAA16507; Tue, 13 Apr 1999 17:45:08 -0500 (CDT) (envelope-from dick) Date: Tue, 13 Apr 1999 17:45:07 -0500 From: "Richard Seaman, Jr." To: "Kurt D. Zeilenga" Cc: freebsd-current@FreeBSD.ORG Subject: Re: compiler specs for -pthread/-kthread Message-ID: <19990413174507.A440@tar.com> References: <3.0.5.32.19990413151601.009b2100@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3.0.5.32.19990413151601.009b2100@localhost>; from Kurt D. Zeilenga on Tue, Apr 13, 1999 at 03:16:01PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 13, 1999 at 03:16:01PM -0700, Kurt D. Zeilenga wrote: > To facilate auto detection of the local threading environment, > it would be nice if the -?thread options set all the necessary > compiler/linker flags. It is a common practace for such > options to specify both compilation and link options. > > I suggest the EGCS specs be adjusted to: > > -pthread => -D_THREAD_SAFE -D_UTHREADS -lc_r > -kthread => -D_THREAD_SAFE -D_KTHREADS -lpthread A little known and not well documented fact is that FreeBSD also uses _REENTRANT in its header files. Ever wondered why you couldn't find declarations for gamma_r, lgamma_r, gammaf_r, or lgammaf_r? Check math.h. :) Personally I think conditional declarations should just be eliminated from math.h, rather than tell people they might have to add -D_REENTRANT. :) > > If the LinuxThread "port" is targetted to be -kthread: > > -kthread => -D_REENRANT -D_LINUXTHREADS -lpthread In FreeBSD, you should define -D_THREAD_SAFE for linuxthreads if you want the thread safe behaviour in stdio.h. Its a libc thing, not a linuxthreads thing. Adding -D_REENTRANT to linuxthreads doesn't get you anything except the added headers in math.h (same as libc_r). > After modify the specification, the headers/libraries would > be adjusted as needed. I can easily submit diffs if desirable. Nobody has offered to commit the changes to the header files I have requested, and the PR I submitted on Jan 29 has not been acted upon. As a result, I anticipate dropping the -DLINUXTHREADS solution to the header conflict problem in favor of stuffing all the linux threads specific headers into /usr/local/include/pthread/linuxthreads where they go now, and instead of -DLINUXTHREADS, people will have to add -I/usr/local/include/pthread/linuxthreads to their compile options. (This works now too). -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15:52:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 1C10214E9B for ; Tue, 13 Apr 1999 15:52:08 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA20531; Tue, 13 Apr 1999 18:49:14 -0400 (EDT) Date: Tue, 13 Apr 1999 18:49:14 -0400 (EDT) From: Daniel Eischen Message-Id: <199904132249.SAA20531@pcnet1.pcnet.com> To: eischen@vigrid.com, jdp@polstra.com Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > Does Modula-3 use libc_r, or does it have it's own user thread support? > > It has its own. It can be ported to use native threads, but it's a > non-negligible amount of work. It hardly seems worth it for the GUI > alone. No argmuent here. It's just that if it was using native threads, I would have been curious to see how CVSup worked before and after the recent changes to libc_r. But I guess I could have tested that myself :-) > My hunch is that it's not a fairness issue. It's just the fact that > when you block in disk I/O, the whole process (all threads) blocks. That statement made me think that Modula-3 had it's own threading support because our native threads using non-blocking file I/O. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 15:55:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from psf.Pinyon.ORG (ip-83-001.prc.primenet.com [207.218.83.1]) by hub.freebsd.org (Postfix) with ESMTP id 4601614CBE for ; Tue, 13 Apr 1999 15:55:22 -0700 (PDT) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.3/8.9.2) with ESMTP id PAA38373 for ; Tue, 13 Apr 1999 15:49:36 -0700 (MST) (envelope-from rcarter@psf.Pinyon.ORG) Message-Id: <199904132249.PAA38373@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.3 To: freebsd-current@freebsd.org Subject: Re: compiler specs for -pthread/-kthread In-Reply-To: Your message of "Tue, 13 Apr 1999 17:45:07 EST." <19990413174507.A440@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Apr 1999 15:49:35 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %On Tue, Apr 13, 1999 at 03:16:01PM -0700, Kurt D. Zeilenga wrote: %> To facilate auto detection of the local threading environment, %> it would be nice if the -?thread options set all the necessary %> compiler/linker flags. It is a common practace for such %> options to specify both compilation and link options. %> %> I suggest the EGCS specs be adjusted to: %> %> -pthread => -D_THREAD_SAFE -D_UTHREADS -lc_r %> -kthread => -D_THREAD_SAFE -D_KTHREADS -lpthread % %A little known and not well documented fact is that FreeBSD also %uses _REENTRANT in its header files. Ever wondered why you %couldn't find declarations for gamma_r, lgamma_r, gammaf_r, %or lgammaf_r? Check math.h. :) % %Personally I think conditional declarations should just be %eliminated from math.h, rather than tell people they might %have to add -D_REENTRANT. :) % %> %> If the LinuxThread "port" is targetted to be -kthread: %> %> -kthread => -D_REENRANT -D_LINUXTHREADS -lpthread and don't forget -lgcc_r... Russell [...] %-- %Richard Seaman, Jr. email: dick@tar.com %5182 N. Maple Lane phone: 414-367-5450 %Chenequa WI 53058 fax: 414-367-5852 % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 16: 7:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id C0FFB14D0D for ; Tue, 13 Apr 1999 16:07:46 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id SAA02427; Tue, 13 Apr 1999 18:05:19 -0500 (CDT) Date: Tue, 13 Apr 1999 18:05:19 -0500 From: "Matthew D. Fuller" To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: cvsup Message-ID: <19990413180518.D25108@futuresouth.com> References: <19990413170053.B25108@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from John Polstra on Tue, Apr 13, 1999 at 03:41:46PM -0700 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 13, 1999 at 03:41:46PM -0700, a little birdie told me that John Polstra remarked > Matthew D. Fuller wrote: > > > After about 4 days without cvsup'ing (including lots of fun gcc/egcs) > > updates it took 6:16 to update my CVS repo including: > > When CVSup is fetching entirely new files, it can't do anything much > smarter than compress them. It can't avoid moving the bits from point > A to point B. In the case of egcs, that's a lot of bits. > > But six hours and sixteen minutes? That's awfully slow. You must > have had a really bad link that day. I'd try a few different mirror > sites if I were you. Nono, 6 minutes and 16 seconds :P *lovin it* --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 16:25:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4179214F24 for ; Tue, 13 Apr 1999 16:25:15 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id QAA18241; Tue, 13 Apr 1999 16:22:55 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA75716; Tue, 13 Apr 1999 16:22:55 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904132249.SAA20531@pcnet1.pcnet.com> Date: Tue, 13 Apr 1999 16:22:55 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Daniel Eischen Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > John Polstra wrote: > >> My hunch is that it's not a fairness issue. It's just the fact that >> when you block in disk I/O, the whole process (all threads) blocks. > > That statement made me think that Modula-3 had it's own threading > support because our native threads using non-blocking file I/O. For disk I/O? Are you sure? If so then it must use the aio/lio calls or something similar. Disk I/O calls _always_ block, even if you've set O_NONBLOCK on the file descriptor. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 16:26:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id F3EEB14E62 for ; Tue, 13 Apr 1999 16:26:26 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id QAA18253; Tue, 13 Apr 1999 16:24:06 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA75721; Tue, 13 Apr 1999 16:24:06 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990413180518.D25108@futuresouth.com> Date: Tue, 13 Apr 1999 16:24:06 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: "Matthew D. Fuller" Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew D. Fuller wrote: >> But six hours and sixteen minutes? That's awfully slow. You must >> have had a really bad link that day. I'd try a few different mirror >> sites if I were you. > > Nono, 6 minutes and 16 seconds :P > *lovin it* Ohhhhhhh! Heh, you had me worried for a minute there. :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 16:53:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 82A4C14CC7 for ; Tue, 13 Apr 1999 16:53:49 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA27490; Tue, 13 Apr 1999 19:50:54 -0400 (EDT) Date: Tue, 13 Apr 1999 19:50:54 -0400 (EDT) From: Daniel Eischen Message-Id: <199904132350.TAA27490@pcnet1.pcnet.com> To: eischen@vigrid.com, jdp@polstra.com Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > That statement made me think that Modula-3 had it's own threading > > support because our native threads using non-blocking file I/O. > > For disk I/O? Are you sure? If so then it must use the aio/lio calls > or something similar. Disk I/O calls _always_ block, even if you've > set O_NONBLOCK on the file descriptor. No it doesn't use aio/lio (although I was recently thinking about trying it). It uses select for I/O readiness, then read/write on O_NONBLOCK files. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 17:24: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (Postfix) with ESMTP id 382EA15271 for ; Tue, 13 Apr 1999 17:23:58 -0700 (PDT) (envelope-from bford@uop.cs.uop.edu) Received: from heather (user156.pop2.cwia.com [209.142.32.156]) by uop.cs.uop.edu (8.8.8/8.8.8) with SMTP id RAA09013; Tue, 13 Apr 1999 17:21:26 -0700 (PDT) Message-ID: <000b01be860c$bd24fd00$0100a8c0@my.domain> From: "Bret Ford" To: "Tim Preece" Cc: References: <19990413233402.A52219@franklin.matlink> Subject: Re: ftp hangs on -current Date: Tue, 13 Apr 1999 17:21:20 -0700 Organization: University of the Pacific 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.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Tue, 13 Apr 1999 18:34:25 Ilya Naumov wrote: > > Hello Gianmarco, > > > > Thursday, April 08, 1999, 7:49:52 AM, you wrote: > > > > GG> "ftp" on 4.0-very-current (post egcs make world) randomly hangs during > > GG> sessions... > > GG> I never succeded in finishing a session lately. > > GG> To transfer some files from my home to my isp server I had to do an "ftp" > > GG> from the server and a "get" to them... > > > > GG> The ftp server works normally and fetch is ok ... > > GG> Probably it is a fault of my system, if no other experiences it. > > > > you're not alone with this problem here - i have the same one. and it > > seems that it is somehow related to natd, because ftp works quite > > well when i disable this daemon. any ideas? > > Well I am also experiencing something like this with ports and sendmail connections - intermittently, unfortunatly I am not running natd ! > I am getting problems similar to those outlined above. I don't run natd, either, but I do have a firewall enabled. (open rule) I've had to 'put' files rather than 'get' them, since my last build/installworld. (Yesterday's -current source) Bret Ford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 19: 4:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 9F2CA14C10 for ; Tue, 13 Apr 1999 19:04:29 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id LAA21644; Wed, 14 Apr 1999 11:02:00 +0900 (JST) Message-ID: <3713F187.798E170F@newsguy.com> Date: Wed, 14 Apr 1999 10:38:15 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: John Polstra Cc: mi@aldan.algebra.com, current@FreeBSD.ORG Subject: Re: cvsup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > If we had kernel threads and Modula-3 supported them, this wouldn't be > a problem. But those are two very big ifs. :-( Alternatively, if you could use aio.h in Module-3, this wouldn't be a problem either. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 13 23:29:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 19AAA153BD for ; Tue, 13 Apr 1999 23:29:13 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA07777; Wed, 14 Apr 1999 08:26:50 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904140626.IAA07777@freebsd.dk> Subject: Re: ATA disks can do command queueing? In-Reply-To: <19990414005818.A15299@matti.ee> from Vallo Kallaste at "Apr 14, 1999 0:58:18 am" To: vallo@matti.ee Date: Wed, 14 Apr 1999 08:26:50 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Vallo Kallaste wrote: > On Tue, Apr 13, 1999 at 10:58:45PM +0200, Soren Schmidt wrote: > > > Yep that is exactly what it means, however the driver in -current > > doesn't take advantage of it yet, but its on my TODO list. > > The reason why I put in this verbosity, is so I can get a hint to > > which drives support it, and it seems IBM are on of the few that > > does. > > Nice. As you say you need hints I can try 14gig 7200rpm IBM also, one > is on my table. I think it can behave similarly. It does, I have the 10G version it does have support. Nice drives BTW.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 0:42:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 58EAF14F40 for ; Wed, 14 Apr 1999 00:42:21 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <26KYCX4B>; Wed, 14 Apr 1999 09:42:36 +0200 Message-ID: <55586E7391ACD211B9730000C11002761795E9@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: "'mi@aldan.algebra.com'" , current@freebsd.org Subject: RE: swap-related problems Date: Wed, 14 Apr 1999 09:38:42 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mikhail Teterin [SMTP:mi@misha.cisco.com] > Sent: Wednesday, April 14, 1999 12:45 AM > To: current@freebsd.org > Subject: Re: swap-related problems > > > Well, this is just an implementation detail, is not it? I don't > mean to critisize, or anything, but such thing as "no available > memory" is a fairly intuitive... Coming down, again, the malloc > should return a usable memory if available and NULL if it's not. > Is not this a "natural" semantics? Why can a program die because > _another_ program ate up all the rest of the memory? > > [ML] This is a common problem for any OS that implements memory overcommit. This means that it is not possible to detect an out-of-swap condition sinchronously as the swap is reserved only when the pages are dirtied and not when brk is grown. This means that you can set brk a gigabyte higher (given that your user limits allow that), and you will not be using swap as long as you do not write to the pages you "allocated" to the process. Another strategy is to reserve the swap space as soon as it is allocated by the program. This strategy is much more conservative and inherently safer, but it needs much more space: for instance, if you have a program with WSS of a gigabyte and you want to system( "date" ), you will need at least 2 gigs of swap because system() does fork() first which means that you get 2 copies of your big program and the system cannot know that in one of the copies an exec() will be shortly forthcoming--thus, it has to reserve the full WSS for the copy because it will potentially write to all pages of its WSS. It would be nice if memory overcommit were configurable (on-off, or per process). /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 1:55:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id A6C8114E59 for ; Wed, 14 Apr 1999 01:55:11 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id EAA19725; Wed, 14 Apr 1999 04:06:16 -0500 (EST) Date: Wed, 14 Apr 1999 04:06:12 -0500 (EST) From: Alfred Perlstein To: Ladavac Marino Cc: "'mi@aldan.algebra.com'" , current@FreeBSD.ORG Subject: RE: swap-related problems In-Reply-To: <55586E7391ACD211B9730000C11002761795E9@r-lmh-wi-100.corpnet.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Ladavac Marino wrote: > > -----Original Message----- > > From: Mikhail Teterin [SMTP:mi@misha.cisco.com] > > Sent: Wednesday, April 14, 1999 12:45 AM > > To: current@freebsd.org > > Subject: Re: swap-related problems > > > > > > Well, this is just an implementation detail, is not it? I don't > > mean to critisize, or anything, but such thing as "no available > > memory" is a fairly intuitive... Coming down, again, the malloc > > should return a usable memory if available and NULL if it's not. > > Is not this a "natural" semantics? Why can a program die because > > _another_ program ate up all the rest of the memory? > > > > > [ML] This is a common problem for any OS that implements memory > overcommit. This means that it is not possible to detect an out-of-swap > condition sinchronously as the swap is reserved only when the pages are > dirtied and not when brk is grown. This means that you can set brk a > gigabyte higher (given that your user limits allow that), and you will > not be using swap as long as you do not write to the pages you > "allocated" to the process. > > Another strategy is to reserve the swap space as soon as it is > allocated by the program. This strategy is much more conservative and > inherently safer, but it needs much more space: for instance, if you > have a program with WSS of a gigabyte and you want to system( "date" ), > you will need at least 2 gigs of swap because system() does fork() first > which means that you get 2 copies of your big program and the system > cannot know that in one of the copies an exec() will be shortly > forthcoming--thus, it has to reserve the full WSS for the copy because > it will potentially write to all pages of its WSS. An interesting idea would be to mark this process as killable if COW causes an out of swap condition. Another interesting application would be a fork() call that checks this condition and fails if there is potential for overcommit. forkifavail() Basically anyone doing a system("date"); should be using vfork (yes i can see when vfork is not sufficient) This would sort of be like a soft limit on memory allocation and hint to the kernel of which processes are the ones causeing overcommit. basically at a certain point, sbrk will fail and forked processes would be marked killable... does this make sense? has the idea of processes running with uid < 10 or just root being excempt from this "frantic kill" ? -Alfred > > It would be nice if memory overcommit were configurable (on-off, > or per process). > > /Marino > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Alfred Perlstein - Admin, coder, and admirer of all things BSD. -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 2:49:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 67E6714F64 for ; Wed, 14 Apr 1999 02:49:33 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (the-menacing-troll.cybercity.dk [212.242.41.238]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id LAA28508; Wed, 14 Apr 1999 11:47:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id JAA00368; Wed, 14 Apr 1999 09:37:14 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mi@aldan.algebra.com Cc: current@freebsd.org Subject: Re: swap-related problems In-reply-to: Your message of "Tue, 13 Apr 1999 18:45:15 EDT." <199904132245.SAA93415@misha.cisco.com> Date: Wed, 14 Apr 1999 09:37:14 +0200 Message-ID: <366.924075434@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904132245.SAA93415@misha.cisco.com>, Mikhail Teterin writes: >Poul-Henning Kamp once wrote: >Well, this is just an implementation detail, is not it? I don't >mean to critisize, or anything, but such thing as "no available >memory" is a fairly intuitive... Coming down, again, the malloc >should return a usable memory if available and NULL if it's not. >Is not this a "natural" semantics? Why can a program die because >_another_ program ate up all the rest of the memory? You know, this strikes me about as productive a discussion as the "split infinitive should be outlawed by style(9)" we have every so often. Very very fundamental to UNIX philosophy is the maxim that it is roots responsibility to configure the system right. FreeBSD will defend itself against misconfigurations as best it can, this includes shooting processes down when things get too squeezy. Think of it as self-defence. The real problem is that you system isn't configured for what you use it for. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 5:21:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 25B5A14ED1 for ; Wed, 14 Apr 1999 05:21:30 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id IAA72511; Wed, 14 Apr 1999 08:19:00 -0400 (EDT) Date: Wed, 14 Apr 1999 08:18:59 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Alfred Perlstein Cc: Ladavac Marino , "'mi@aldan.algebra.com'" , current@FreeBSD.ORG Subject: RE: swap-related problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Alfred Perlstein wrote: > On Wed, 14 Apr 1999, Ladavac Marino wrote: > > > > -----Original Message----- > > > From: Mikhail Teterin [SMTP:mi@misha.cisco.com] > > > Sent: Wednesday, April 14, 1999 12:45 AM > > > To: current@freebsd.org > > > Subject: Re: swap-related problems > > > > > > > > > Well, this is just an implementation detail, is not it? I don't > > > mean to critisize, or anything, but such thing as "no available > > > memory" is a fairly intuitive... Coming down, again, the malloc > > > should return a usable memory if available and NULL if it's not. > > > Is not this a "natural" semantics? Why can a program die because > > > _another_ program ate up all the rest of the memory? > > > > > > > > [ML] This is a common problem for any OS that implements memory > > overcommit. This means that it is not possible to detect an out-of-swap > > condition sinchronously as the swap is reserved only when the pages are > > dirtied and not when brk is grown. This means that you can set brk a > > gigabyte higher (given that your user limits allow that), and you will > > not be using swap as long as you do not write to the pages you > > "allocated" to the process. > > > > Another strategy is to reserve the swap space as soon as it is > > allocated by the program. This strategy is much more conservative and > > inherently safer, but it needs much more space: for instance, if you > > have a program with WSS of a gigabyte and you want to system( "date" ), > > you will need at least 2 gigs of swap because system() does fork() first > > which means that you get 2 copies of your big program and the system > > cannot know that in one of the copies an exec() will be shortly > > forthcoming--thus, it has to reserve the full WSS for the copy because > > it will potentially write to all pages of its WSS. > > An interesting idea would be to mark this process as killable if COW > causes an out of swap condition. Another interesting application would > be a fork() call that checks this condition and fails if there is > potential for overcommit. forkifavail() > > Basically anyone doing a system("date"); should be using vfork (yes > i can see when vfork is not sufficient) > > This would sort of be like a soft limit on memory allocation and hint > to the kernel of which processes are the ones causeing overcommit. > > basically at a certain point, sbrk will fail and forked processes > would be marked killable... > > does this make sense? > > has the idea of processes running with uid < 10 or just root being > excempt from this "frantic kill" ? This isn't really a great idea since it would be changing the Unix API. However, I agree that processes with exclusive use of the video hardware should not be killed by the system *COUGH XFree86 COUGH*. > > -Alfred > > > > > It would be nice if memory overcommit were configurable (on-off, > > or per process). > > > > /Marino > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Alfred Perlstein - Admin, coder, and admirer of all things BSD. > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 4.0-current > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 5:26:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 09B1C14F75 for ; Wed, 14 Apr 1999 05:26:40 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id IAA72570; Wed, 14 Apr 1999 08:20:16 -0400 (EDT) Date: Wed, 14 Apr 1999 08:20:15 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Poul-Henning Kamp Cc: mi@aldan.algebra.com, current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <366.924075434@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Poul-Henning Kamp wrote: > In message <199904132245.SAA93415@misha.cisco.com>, Mikhail Teterin writes: > >Poul-Henning Kamp once wrote: > > >Well, this is just an implementation detail, is not it? I don't > >mean to critisize, or anything, but such thing as "no available > >memory" is a fairly intuitive... Coming down, again, the malloc > >should return a usable memory if available and NULL if it's not. > >Is not this a "natural" semantics? Why can a program die because > >_another_ program ate up all the rest of the memory? > > You know, this strikes me about as productive a discussion as the > "split infinitive should be outlawed by style(9)" we have every > so often. > > Very very fundamental to UNIX philosophy is the maxim that it is > roots responsibility to configure the system right. > > FreeBSD will defend itself against misconfigurations as best it > can, this includes shooting processes down when things get too > squeezy. > > Think of it as self-defence. > > The real problem is that you system isn't configured for what you > use it for. Fine. Let's have a kernel option for it, because a LOT of us want the old functionality back, and yes it _WAS_ there before. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 6:17:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id C0CA01570E for ; Wed, 14 Apr 1999 06:17:20 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id JAA24946 for current@freebsd.org; Wed, 14 Apr 1999 09:14:35 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904141314.JAA24946@kot.ne.mediaone.net> Subject: Re: swap-related problems In-Reply-To: <366.924075434@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 14, 1999 09:37:14 am" To: current@freebsd.org Date: Wed, 14 Apr 1999 09:14:35 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"Well, this is just an implementation detail, is not it? I don't =>mean to critisize, or anything, but such thing as "no available =>memory" is a fairly intuitive... Coming down, again, the malloc =>should return a usable memory if available and NULL if it's not. =>Is not this a "natural" semantics? Why can a program die because =>_another_ program ate up all the rest of the memory? = =You know, this strikes me about as productive a discussion as the [...] =Very very fundamental to UNIX philosophy is the maxim that it is =roots responsibility to configure the system right. I'm sorry I managed to annoy you. However, a program needs to be able to know if it can legally ask for more memory, right? And it is "very fundamental to malloc philosophy", that malloc returns NULL, when it can not get more memory. Which it apparently does now on FreeBSD, but only if the program exceeds an artificial datasize limit... And if it is not set, it the administrator's problem? May be... Should we, perhaps, have it documented in a number of places, including malloc(3)? My other problem with the artificial limits, is that I can only specify the absolute figures. Besides an ability to use Mb, Gb, Kb, I'd like to have % there... And, as I mentioned before, an ability to distribute the class database over NIS... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 6:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C8B8815763; Wed, 14 Apr 1999 06:30:32 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA27152; Wed, 14 Apr 1999 22:28:08 +0900 (JST) Message-ID: <37149716.582342ED@newsguy.com> Date: Wed, 14 Apr 1999 22:24:38 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Motomichi Matsuzaki Cc: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. References: <199904140620.XAA24224@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Motomichi Matsuzaki wrote: > > The patch gzip+uuencoded is following. Do you know of any problems resulting from applying this patch? I think it's way past the time of getting it in the tree, and if there are still any problems with it, we have to track them down and fix them. Anyone on -current objects to this patch? It has come a _long_ way now... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 6:30:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id D6363157E0 for ; Wed, 14 Apr 1999 06:30:36 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA27117; Wed, 14 Apr 1999 22:27:56 +0900 (JST) Message-ID: <3714925A.D348A0DB@newsguy.com> Date: Wed, 14 Apr 1999 22:04:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Ladavac Marino Cc: "'mi@aldan.algebra.com'" , current@FreeBSD.ORG Subject: Re: swap-related problems References: <55586E7391ACD211B9730000C11002761795E9@r-lmh-wi-100.corpnet.at> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ladavac Marino wrote: > > Another strategy is to reserve the swap space as soon as it is > allocated by the program. This strategy is much more conservative and > inherently safer, but it needs much more space: for instance, if you > have a program with WSS of a gigabyte and you want to system( "date" ), > you will need at least 2 gigs of swap because system() does fork() first > which means that you get 2 copies of your big program and the system > cannot know that in one of the copies an exec() will be shortly > forthcoming--thus, it has to reserve the full WSS for the copy because > it will potentially write to all pages of its WSS. > > It would be nice if memory overcommit were configurable (on-off, > or per process). On AIX, you can have it set as a global option and on/off per process. In my experience, though, setting it to off never solved anything: if you need memory, you have to add memory. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 6:39:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 564ED15068 for ; Wed, 14 Apr 1999 06:39:10 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id JAA47610; Wed, 14 Apr 1999 09:34:44 -0400 (EDT) Date: Wed, 14 Apr 1999 09:34:43 -0400 (EDT) From: Chuck Robey To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <199904141314.JAA24946@kot.ne.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Mikhail Teterin wrote: > Poul-Henning Kamp once stated: > > =>Well, this is just an implementation detail, is not it? I don't > =>mean to critisize, or anything, but such thing as "no available > =>memory" is a fairly intuitive... Coming down, again, the malloc > =>should return a usable memory if available and NULL if it's not. > =>Is not this a "natural" semantics? Why can a program die because > =>_another_ program ate up all the rest of the memory? > = > =You know, this strikes me about as productive a discussion as the > [...] > =Very very fundamental to UNIX philosophy is the maxim that it is > =roots responsibility to configure the system right. > > I'm sorry I managed to annoy you. However, a program needs to be > able to know if it can legally ask for more memory, right? And it > is "very fundamental to malloc philosophy", that malloc returns > NULL, when it can not get more memory. Which it apparently does > now on FreeBSD, but only if the program exceeds an artificial > datasize limit... He's not talking about an artificial limit, he's talking about another user making off with all the memory. This sounds very bizarre, how can you possibly ask the system to predict what other user's are going to ask for, in advance? You can't possibly get absolute permissions on malloc'ed area unless you reserve it (and thereby deny the area to other users, when you might only use a small portion of your reserved area yourself) or you restrict other's use of malloc'ed memory. In your request, less users would have their requests satisfied, because if they allocate 100 MB arrays (where they fill only 1KB with data) they would actually be hard-reserving all that 100MB. This doesn't sound like any reasonable policy for general purpose use (although it might very well suit your purposes). These are fundamental design problems (which you have been told already) and the way that FreeBSD chooses to act is arguably a very good one. There is nothing here that violates any fundamental rules, because we are talking about OS wide allocation strategies. If you need guarantees, then you have to buy more memory, more swap, and have less hungry users. > > And if it is not set, it the administrator's problem? May be... > > Should we, perhaps, have it documented in a number of places, > including malloc(3)? > > My other problem with the artificial limits, is that I can only > specify the absolute figures. Besides an ability to use Mb, Gb, > Kb, I'd like to have % there... And, as I mentioned before, an > ability to distribute the class database over NIS... > > -mi > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 6:56: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 7C27414FD0 for ; Wed, 14 Apr 1999 06:56:00 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id JAA25377 for current@freebsd.org; Wed, 14 Apr 1999 09:53:22 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904141353.JAA25377@kot.ne.mediaone.net> Subject: Re: swap-related problems In-Reply-To: from Chuck Robey at "Apr 14, 1999 09:34:43 am" To: current@freebsd.org Date: Wed, 14 Apr 1999 09:53:22 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Wed, 14 Apr 1999 07:27:18 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA09018; Wed, 14 Apr 1999 23:24:50 +0900 (JST) Message-ID: <3714A4C2.96BE6188@newsguy.com> Date: Wed, 14 Apr 1999 23:22:58 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: <199904141353.JAA25377@kot.ne.mediaone.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > > All I want is that a program gets NULL from malloc if there is no memory > available. I find that to be a very fundamental thing about malloc. > > In response, me and others are told at different times: > > . there is no such thing as "no memory available" (!!!) > . you can get that behaviour by limiting the user's maximum > datasize > . this wouldn't work without dumping the overcommit strategy, > which would demand more memory and will slow things down > . be a better sysadmin > . get more memory and swap > . this discussion is annoying and fruitless (!!!) > > I find this responses unacceptable, or only partially acceptable... There is two ways you can alloc memory: on-demand or pre-allocated. Most Unixes out there choose on-demand because it let you do more with less. A *lot* more. The only way to do what you want is to pre-allocate. Alas, suppose you set pre-allocation for your eat-all-memory application. You application starts, eat all memory and stabilizes. Then you move the mouse in X Free causing previously allocated memory to be accessed. There is no memory available, so the largest process is killed. That would be your eat-all-memory application. What some of us have been telling you is that there is no easy way out of this. Some have suggested "don't kill this process" solutions. This is a poor solution, because it requires much more sysadmin tweaking than limiting user's maximum datasize. If you pre-allocate all memory you'll find out you have much less memory available for you. MUCH less. Yeah, a pre-allocate all memory general system flag would be interesting, but mostly because we could then say "turn this on and see how you suddenly don't have memory to even start X Free". Or, in other words, if you set a maximum datasize for your application, you can allocate MUCH more memory to that application than if our allocation strategy was pre-allocate. Do you have a solution? We don't. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 7:41:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 66B541577D for ; Wed, 14 Apr 1999 07:41:31 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id QAA29212; Wed, 14 Apr 1999 16:39:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id QAA00637; Wed, 14 Apr 1999 16:39:09 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: swap-related problems In-reply-to: Your message of "Wed, 14 Apr 1999 09:14:35 EDT." <199904141314.JAA24946@kot.ne.mediaone.net> Date: Wed, 14 Apr 1999 16:39:09 +0200 Message-ID: <635.924100749@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904141314.JAA24946@kot.ne.mediaone.net>, Mikhail Teterin writes: >Poul-Henning Kamp once stated: > >=>Well, this is just an implementation detail, is not it? I don't >=>mean to critisize, or anything, but such thing as "no available >=>memory" is a fairly intuitive... Coming down, again, the malloc >=>should return a usable memory if available and NULL if it's not. >=>Is not this a "natural" semantics? Why can a program die because >=>_another_ program ate up all the rest of the memory? >= >=You know, this strikes me about as productive a discussion as the >[...] >=Very very fundamental to UNIX philosophy is the maxim that it is >=roots responsibility to configure the system right. > >I'm sorry I managed to annoy you. However, a program needs to be >able to know if it can legally ask for more memory, right? And it >is "very fundamental to malloc philosophy", that malloc returns >NULL, when it can not get more memory. Which it apparently does >now on FreeBSD, but only if the program exceeds an artificial >datasize limit... malloc() on FreeBSD returns NULL when it cannot allocate the memory asked for. If you have an example where this is not the case I would VERY much like to see it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 7:49:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 536A41577D; Wed, 14 Apr 1999 07:48:59 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id QAA14961; Wed, 14 Apr 1999 16:45:48 +0200 (CEST) Message-ID: <19990414164548.A14876@foobar.franken.de> Date: Wed, 14 Apr 1999 16:45:48 +0200 From: Harold Gutch To: "Daniel C. Sobral" , Motomichi Matsuzaki Cc: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. References: <199904140620.XAA24224@freefall.freebsd.org> <37149716.582342ED@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <37149716.582342ED@newsguy.com>; from Daniel C. Sobral on Wed, Apr 14, 1999 at 10:24:38PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 14, 1999 at 10:24:38PM +0900, Daniel C. Sobral wrote: > Motomichi Matsuzaki wrote: > > > > The patch gzip+uuencoded is following. > > Do you know of any problems resulting from applying this patch? I'm not sure if this applys to _this_ patch, but a couple of months ago I took some 3.0-patches and backported them to 2.2. They had the problem of using the Joliet extensions when mounting a hybrid-CD (a CD with Joliet and RockRidge extensions). Perhaps an option to mount_cd9660 would be the best idea, similar to the already existing -r it could get a -j which would make mount_cd9660 ignore the Joliet extensions. bye, Harold -- Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 8: 1:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 898AA14DCD for ; Wed, 14 Apr 1999 08:01:27 -0700 (PDT) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id LAA00947; Wed, 14 Apr 1999 11:17:31 -0400 (EDT) (envelope-from dervish) Date: Wed, 14 Apr 1999 11:17:31 -0400 From: Natty Rebel To: Soren Schmidt Cc: current@freebsd.org Subject: Lastest ATA/ATAPI driver boots with kernel.debug only. Message-ID: <19990414111731.B851@ikhala.tcimet.net> References: <19990414005818.A15299@matti.ee> <199904140626.IAA07777@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199904140626.IAA07777@freebsd.dk>; from Soren Schmidt on Wed, Apr 14, 1999 at 08:26:50AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 2C CE A5 D7 FA 4D D5 FD 9A CC 2B 23 04 46 48 F8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Soren and other -current users, I've used your new ATA/ATAPI driver flawlessly through the 4th version. I was not able to get past the 'changing root device to wd0s1a' message with version 5, so I just went back to the wd driver. Last nigh I tried version 6 and ran into the same problem. I finally decided to do a little investigating. First I found that I could do a 'ctrl-alt-del' to reboot. I then decided to install the debug kernel doing a 'make install.debug' in my kernel build directory. Lo! and behold! to my surprise my box booted flawlessly. The questions I have are 1) Why did the debug kernel boot and not the kernel without debug symbols? 2) What procedures/tools should I use to investigate this further? Of course any help/pointers are appreciated ... Thanxs. #;^) i'khala -- natty rebel harder than the rest ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 8: 3:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 04505151FE for ; Wed, 14 Apr 1999 08:03:42 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id LAA25847 for current@freebsd.org; Wed, 14 Apr 1999 11:01:03 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904141501.LAA25847@kot.ne.mediaone.net> Subject: Re: swap-related problems In-Reply-To: <635.924100749@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 14, 1999 04:39:09 pm" To: current@freebsd.org Date: Wed, 14 Apr 1999 11:01:03 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Wed, 14 Apr 1999 08:20:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA29357; Wed, 14 Apr 1999 17:17:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA00773; Wed, 14 Apr 1999 17:17:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: swap-related problems In-reply-to: Your message of "Wed, 14 Apr 1999 11:01:03 EDT." <199904141501.LAA25847@kot.ne.mediaone.net> Date: Wed, 14 Apr 1999 17:17:39 +0200 Message-ID: <771.924103059@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904141501.LAA25847@kot.ne.mediaone.net>, Mikhail Teterin writes: >Poul-Henning Kamp once stated: > >=malloc() on FreeBSD returns NULL when it cannot allocate the memory >=asked for. > >=If you have an example where this is not the case I would VERY >=much like to see it. > >I believe, a number of examples were given, when the use of the non-NULL >pointer returned by malloc resulted in the program being killed. No, the examples I have seen showed the system killing a (somewhat) random large process in an attempt to avoid deadlock. I guess you can interpret it the way above if you insist on using a very narrow application oriented focus. Ignoring the larger issues is not a modus operandi I subscribe to. Anyway, what you're asking for is really resource reservation. Sorry FreeBSD doesn't support resource reservation for memory. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 9: 3:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id DE7B01548D for ; Wed, 14 Apr 1999 09:03:01 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <26KYCYR9>; Wed, 14 Apr 1999 18:03:14 +0200 Message-ID: <55586E7391ACD211B9730000C11002761795EA@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: "'Daniel C. Sobral'" , Ladavac Marino Cc: "'mi@aldan.algebra.com'" , current@FreeBSD.ORG Subject: RE: swap-related problems Date: Wed, 14 Apr 1999 17:59:21 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Daniel C. Sobral [SMTP:dcs@newsguy.com] > Sent: Wednesday, April 14, 1999 3:04 PM > To: Ladavac Marino > Cc: 'mi@aldan.algebra.com'; current@FreeBSD.ORG > Subject: Re: swap-related problems > > Ladavac Marino wrote: > > > > Another strategy is to reserve the swap space as soon as it > is > > allocated by the program. This strategy is much more conservative > and > > inherently safer, but it needs much more space: for instance, if you > > have a program with WSS of a gigabyte and you want to system( "date" > ), > > you will need at least 2 gigs of swap because system() does fork() > first > > which means that you get 2 copies of your big program and the system > > cannot know that in one of the copies an exec() will be shortly > > forthcoming--thus, it has to reserve the full WSS for the copy > because > > it will potentially write to all pages of its WSS. > > > > It would be nice if memory overcommit were configurable > (on-off, > > or per process). > > On AIX, you can have it set as a global option and on/off per > process. In my experience, though, setting it to off never solved > anything: if you need memory, you have to add memory. > [ML] Oh, memory overcommit does have its applications. Remember the olden days of FORTRAN when "dynamic memory allocation" was a meaningless term :) Overcommit let the people "allocate" a 10000*10000 matrix and use only a 20*20 subset of it and have program execute instead of fail out-of-swap. Nowadays, vfork() could solve most of the problems on fork/exec. Sadly, a frightening number of unices "implement" vfork() as #define vfork fork /Marino > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "nothing better than the ability to perform cunning linguistics" > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 9: 5:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 39DCA152B4 for ; Wed, 14 Apr 1999 09:05:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA55729; Wed, 14 Apr 1999 09:03:11 -0700 (PDT) (envelope-from obrien) Message-ID: <19990414090311.A55444@nuxi.com> Date: Wed, 14 Apr 1999 09:03:11 -0700 From: "David O'Brien" To: Robert Watson Cc: freebsd-current@FreeBSD.ORG Subject: Re: DoS from local users (fwd) Reply-To: obrien@NUXI.com References: <199904102057.PAA27724@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Robert Watson on Tue, Apr 13, 1999 at 09:05:10AM -0400 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A while ago on -current, I posted a reference to a paper on lottery > scheduling in FreeBSD. It allows you to provide scheduling weightings > that (on average) share the CPU as described. It is also used by the UC-Berkeley CSUA on their shell account machines. http://www.csua.berkeley.edu:80/computing/software/lottery-sched.html -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 9:25: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 6280915497 for ; Wed, 14 Apr 1999 09:23:44 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <26KYCYSM>; Wed, 14 Apr 1999 18:23:57 +0200 Message-ID: <55586E7391ACD211B9730000C11002761795EB@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Mikhail Teterin' , current@freebsd.org Subject: RE: swap-related problems Date: Wed, 14 Apr 1999 18:20:03 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mikhail Teterin [SMTP:mi@kot.ne.mediaone.net] > Sent: Wednesday, April 14, 1999 5:01 PM > To: current@freebsd.org > Subject: Re: swap-related problems > > They then, rightfully exclaimed: > > . but should not malloc() have returned me NULL? > > And the rest is drowned in the explanations of why it is very hard to > assure. > I'm repeating myself here and so do others. We are probably facing the > major > disadvantange of the "overcommit" strategy, and there may not, indeed, > be a > way around this. > [ML] Short of disabling memory overcommit, no there is no answer. If you do disable overcommit, prepare to add humongous swap areas (or maybe not--some unices reserve the pages in the filesystem, stealing the free blocks, so to say, but write the dirty pages to the swap partitions. They also keep 2 counters: swap pages reserved, and swap pages actually used. They are capable of swapping into a filesystem should the need actually arise, but are very inefficient in doing so. However, having both numbers--swap reserved and swap used--allows the sysadmin to properly size the swap partitions). > Documenting this properly is what is definitely in order... > [ML] I would agree to this. Perhaps in the IMPLEMENTATION section of the corresponding manpages (malloc, s/brk, fork.) > While we are at this, what is the right way to find out if the > returned pointer > can be used? > [ML] Sadly, in the memory overcommit situation, there is no way to know whether a pointer returned by malloc will cause a process demise or not. The pointer is valid, but the swap area mapping is defered until the page is dirtied (basically, the pointer points to a readonly zero filled physical page and on write the trap handler tries to allocate a backing swap area for the page. If the swap is exhausted, the handler eventually fails. What the system does at this time is irrelevant. Please note that memory overcommit architectures are a rather common optimization; FreeBSD is one of them. They do, however, break the ISO/ANSI C conformance (strictly speaking). /Marino > -mi > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 9:32:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3A8C01570C for ; Wed, 14 Apr 1999 09:32:30 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA01610; Thu, 15 Apr 1999 01:29:19 +0900 (JST) Message-ID: <3714C1F2.2358B4CF@newsguy.com> Date: Thu, 15 Apr 1999 01:27:30 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Harold Gutch Cc: Motomichi Matsuzaki , freebsd-current@FreeBSD.ORG Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. References: <199904140620.XAA24224@freefall.freebsd.org> <37149716.582342ED@newsguy.com> <19990414164548.A14876@foobar.franken.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Harold Gutch wrote: > > I'm not sure if this applys to _this_ patch, but a couple of > months ago I took some 3.0-patches and backported them to 2.2. > They had the problem of using the Joliet extensions when mounting > a hybrid-CD (a CD with Joliet and RockRidge extensions). This latest patch is supposed to mount RockRidge by default on hybrid disks, so it is my guess it works around this specific problem. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 10: 8:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 78FA814F78 for ; Wed, 14 Apr 1999 10:08:22 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id SAA54285; Wed, 14 Apr 1999 18:06:00 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 14 Apr 1999 17:53:35 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 14 Apr 1999 17:53:34 +0000 To: current@freebsd.org From: Bob Bishop Subject: NFS, blocks of NULLs in files Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999) running both on server and client (except that the client's kernel is 24hrs older than that). It happens during a kernel build on the client, so both the sources and objects are being accessed via NFS. During the 'generating linker set emulation glue for ELF' phase, a lot of the .o's turn up with blocks of NULLs. The rest of the world builds fine, but /usr/obj is local so there is little or no NFS writing going on in that case. The client is SMP but it's been doing daily builds with -j8 since that got sorted out, and anyway it now fails in exactly the same way whether -j is used or not. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 10:14:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 17C5E157EC for ; Wed, 14 Apr 1999 10:14:22 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id NAA95762 for current@freebsd.org; Wed, 14 Apr 1999 13:12:00 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904141712.NAA95762@misha.cisco.com> Subject: Re: swap-related problems In-Reply-To: <55586E7391ACD211B9730000C11002761795EB@r-lmh-wi-100.corpnet.at> from Ladavac Marino at "Apr 14, 1999 06:20:03 pm" To: current@freebsd.org Date: Wed, 14 Apr 1999 13:12:00 -0400 (EDT) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ladavac Marino once wrote: > [ML] Sadly, in the memory overcommit situation, there is no way to > know whether a pointer returned by malloc will cause a process demise > or not. The pointer is valid, but the swap area mapping is defered > until the page is dirtied (basically, the pointer points to a readonly > zero filled physical page and on write the trap handler tries to > allocate a backing swap area for the page. If the swap is exhausted, > the handler eventually fails. What the system does at this time is > irrelevant. [...] > Please note that memory overcommit architectures are a rather common > optimization; FreeBSD is one of them. They do, however, break the > ISO/ANSI C conformance (strictly speaking). Aha, now its clearer. May be, since we are do not conform anyway, we can design some clever way of notifying a program rather then SIGKILL-ing it? Perhaps, SIGBUS? Something, a program can catch, if it is prepared to, and, may be, do some syscall to find out which chunk of memory can not actually be used by it... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 10:20:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from work.mzaki.nom (173.pool15.tokyo.att.ne.jp [165.76.220.188]) by hub.freebsd.org (Postfix) with ESMTP id 990021559F; Wed, 14 Apr 1999 10:20:21 -0700 (PDT) (envelope-from mzaki@e-mail.ne.jp) Received: from localhost (localhost [127.0.0.1]) by work.mzaki.nom (8.9.2/8.9.2) with ESMTP id CAA05208; Thu, 15 Apr 1999 02:17:37 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) To: logix@foobar.franken.de Cc: dcs@newsguy.com, freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. In-Reply-To: <19990414164548.A14876@foobar.franken.de> References: <199904140620.XAA24224@freefall.freebsd.org> <37149716.582342ED@newsguy.com> <19990414164548.A14876@foobar.franken.de> X-fingerprint: BD 86 CD D9 66 FD 75 B0 A8 43 4B C4 E2 1B F5 B5 X-Mailer: Mew version 1.94b7 on XEmacs 21.0 (20 minutes to Nikko) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990415021736I.mzaki@e-mail.ne.jp> Date: Thu, 15 Apr 1999 02:17:36 +0900 From: Motomichi Matsuzaki X-Dispatcher: imput version 990212(IM106) Lines: 55 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Harold Gutch Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. Date: Wed, 14 Apr 1999 16:45:48 +0200 logix> On Wed, Apr 14, 1999 at 10:24:38PM +0900, Daniel C. Sobral wrote: logix> > Motomichi Matsuzaki wrote: logix> > > The patch gzip+uuencoded is following. logix> > Do you know of any problems resulting from applying this patch? 1. this patch is for -stable. Some hunks would be failed for -current. 2. Only Page 00 Unicode is shown (for Joliet CDs). ISO-8859-1 is OK, CJK is NG. Each CJK character is replaced with '?' and file identity is lost e.g. both 'abc' and 'xyz' are shown '???', and an access to '???' is always directed for 'abc'. ( Note: 'abc', 'xyz' are CJK string, ASCII string has no such problems. ) I think it would be solved if kernel had NLS and multibyte functions(or their subsets). ( Linux 2.2.x has in-kernel-NLS and Linux's Joliet feature uses it; however, there are no official CJK supoprts.) Note. Byung's patch passes Unicode transparently. So CJK filenames are shown if terminals do Unicodes well. logix> I'm not sure if this applys to _this_ patch, but a couple of logix> months ago I took some 3.0-patches and backported them to 2.2. logix> They had the problem of using the Joliet extensions when mounting logix> a hybrid-CD (a CD with Joliet and RockRidge extensions). Would you tell me what kind of problem? Known bugs of Byung's (Already fixed): * Shortname is also shown not only longname on some Joliet CD-Rs. * Joliet support is not work with El Torito CD-ROMs. Changes from Joachim's: * With Joliet and RockRidge CD, Joachim's see Joliet, mine see RockRidge. logix> Perhaps an option to mount_cd9660 would be the best idea, similar logix> to the already existing -r it could get a -j which would make logix> mount_cd9660 ignore the Joliet extensions. -j is also available for my patch. # I'm sorry for my poor English... -- Motomichi Matsuzaki Dept. of Biological Science, Fuculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 10:49:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 145E215519; Wed, 14 Apr 1999 10:49:49 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id TAA15464; Wed, 14 Apr 1999 19:46:57 +0200 (CEST) Message-ID: <19990414194656.A15365@foobar.franken.de> Date: Wed, 14 Apr 1999 19:46:56 +0200 From: Harold Gutch To: Motomichi Matsuzaki Cc: dcs@newsguy.com, freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. References: <199904140620.XAA24224@freefall.freebsd.org> <37149716.582342ED@newsguy.com> <19990414164548.A14876@foobar.franken.de> <19990415021736I.mzaki@e-mail.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990415021736I.mzaki@e-mail.ne.jp>; from Motomichi Matsuzaki on Thu, Apr 15, 1999 at 02:17:36AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 15, 1999 at 02:17:36AM +0900, Motomichi Matsuzaki wrote: > From: Harold Gutch > logix> I'm not sure if this applys to _this_ patch, but a couple of > logix> months ago I took some 3.0-patches and backported them to 2.2. > logix> They had the problem of using the Joliet extensions when mounting > logix> a hybrid-CD (a CD with Joliet and RockRidge extensions). > > Would you tell me what kind of problem? > From what you say below, I guess that your patches do not have this problem. What I meant, was, that if you use a CD with both Joliet AND RockRidge extensions on it, "my" patches would give you the Joliet extensions. Yours however would show the RockRidge extensions, which _I_ prefer (I would like to be able to see the Joliet extensions if I explicitely specify so on the commandline though, say by using the "-r" option, which the "normal" mount_cd9660 already has. > Changes from Joachim's: > * With Joliet and RockRidge CD, Joachim's see Joliet, mine see RockRidge. > > logix> Perhaps an option to mount_cd9660 would be the best idea, similar > logix> to the already existing -r it could get a -j which would make > logix> mount_cd9660 ignore the Joliet extensions. > > -j is also available for my patch. bye, Harold -- Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 10:56:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 03C5915400 for ; Wed, 14 Apr 1999 10:56:39 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id NAA14604; Wed, 14 Apr 1999 13:54:06 -0400 (EDT) (envelope-from lile@stdio.com) Date: Wed, 14 Apr 1999 13:54:05 -0400 (EDT) From: Larry Lile To: ip@mcc.ac.uk Cc: current@FreeBSD.ORG Subject: Patch to fix [Re: Bad, reliable crash: Julian's "oltr" stuff & ARP] In-Reply-To: <199904121605.RAA47641@albatross.mcc.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1609105550-924112445=:3818" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1609105550-924112445=:3818 Content-Type: TEXT/PLAIN; charset=US-ASCII The problem Mr. Pallfreeman was seeing are related to how I was building the arp-reply based on the sources arp_hrd type. I never expected to see a token-ring arp arrive over an ethernet interface. Therefore the arp code was trying to check for and collect the source route that the arp took on its way. I have modified the arp code to go looking for the source-route information only if the arp comes from a token-ring station and is received on a token-ring interface. The arp-reply packet generated is based on the type of interface the arp was received on. I think the bridge should have changed the arp_hrd type when it forwarded the packet, while it was changing everything else, but I think that falls into a religous debate. Thanks to Mr. Pallfreeman for helping me debug this and testing my patch. What this means is: you should be able to arp in both directions over a token-ring<->ethernet (translational|non-translational) bridge. The inherent "brokenness" of translational bridging is left as an exercise for the reader :) Here's the patch, if someone would be kind enough to commit it. It seems to have resolved Mr. Pallfreeman's issue and doesn't seem to break anything else. Larry Lile lile@stdio.com --0-1609105550-924112445=:3818 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="if_ether.c.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: ARP fix Content-Disposition: attachment; filename="if_ether.c.patch" KioqIGlmX2V0aGVyLmMub3JpZwlXZWQgQXByIDE0IDA5OjU0OjM1IDE5OTkN Ci0tLSBpZl9ldGhlci5jCVdlZCBBcHIgMTQgMTI6NTA6MDIgMTk5OQ0KKioq KioqKioqKioqKioqDQoqKiogNTYwLDU2NyAqKioqDQogIAkJKHZvaWQpbWVt Y3B5KExMQUREUihzZGwpLCBlYS0+YXJwX3NoYSwgc2l6ZW9mKGVhLT5hcnBf c2hhKSk7DQogIAkJc2RsLT5zZGxfYWxlbiA9IHNpemVvZihlYS0+YXJwX3No YSk7DQogICAgICAgICAgICAgICAgICBzZGwtPnNkbF9yY2YgPSBOVUxMOw0K ISAJCS8qIFNhdmUgc291cmNlIHJvdXRpbmcgaW5mb3JtYXRpb24gZm9yIFRv a2VuLXJpbmcgaW50ZXJmYWNlcywgaWYgYXZhaWxhYmxlICovDQohIAkJaWYg KGVhLT5hcnBfaHJkID09IGh0b25zKEFSUEhSRF9JRUVFODAyKSkgew0KICAJ CQl0aCA9IChzdHJ1Y3QgaXNvODgwMjVfaGVhZGVyICopbS0+bV9wa3RoZHIu aGVhZGVyOw0KICAgICAgICAgICAgICAgICAgCWlmICgodGgtPmlzbzg4MDI1 X3Nob3N0WzBdICYgMHg4MCkgJiYgKCgobnRvaHModGgtPnJjZikgJiAweDFm MDApID4+IDgpID4gMikpIHsNCiAgCQkJCXNkbC0+c2RsX3JjZiA9IG50b2hz KHRoLT5yY2YpICYgMHgwMDgwID8gDQotLS0gNTYwLDU2OSAtLS0tDQogIAkJ KHZvaWQpbWVtY3B5KExMQUREUihzZGwpLCBlYS0+YXJwX3NoYSwgc2l6ZW9m KGVhLT5hcnBfc2hhKSk7DQogIAkJc2RsLT5zZGxfYWxlbiA9IHNpemVvZihl YS0+YXJwX3NoYSk7DQogICAgICAgICAgICAgICAgICBzZGwtPnNkbF9yY2Yg PSBOVUxMOw0KISAJCS8qIElmIHdlIHJlY2VpdmUgYW4gYXJwIGZyb20gYSB0 b2tlbi1yaW5nIHN0YXRpb24gb3ZlciBhIHRva2VuLXJpbmcgbmljDQohIAkJ ICogdGhlbiB0cnkgdG8gc2F2ZSB0aGUgc291cmNlIHJvdXRpbmcgaW5mby4N CiEgCQkgKi8NCiEgCQlpZiAoKGFjLT5hY19pZi5pZl90eXBlID09IElGVF9J U084ODAyNSkgJiYgKGVhLT5hcnBfaHJkID09IGh0b25zKEFSUEhSRF9JRUVF ODAyKSkpIHsNCiAgCQkJdGggPSAoc3RydWN0IGlzbzg4MDI1X2hlYWRlciAq KW0tPm1fcGt0aGRyLmhlYWRlcjsNCiAgICAgICAgICAgICAgICAgIAlpZiAo KHRoLT5pc284ODAyNV9zaG9zdFswXSAmIDB4ODApICYmICgoKG50b2hzKHRo LT5yY2YpICYgMHgxZjAwKSA+PiA4KSA+IDIpKSB7DQogIAkJCQlzZGwtPnNk bF9yY2YgPSBudG9ocyh0aC0+cmNmKSAmIDB4MDA4MCA/IA0KKioqKioqKioq KioqKioqDQoqKiogNTc4LDU4MyAqKioqDQotLS0gNTgwLDU4NyAtLS0tDQog IAkJCX0NCiAgCQkJdGgtPnJjZiA9IHNkbC0+c2RsX3JjZjsNCiAgCQkJDQor IAkJfSBlbHNlIHsNCisgCQkJc2RsLT5zZGxfcmNmID0gTlVMTDsNCiAgCQl9 DQogIAkJaWYgKHJ0LT5ydF9leHBpcmUpDQogIAkJCXJ0LT5ydF9leHBpcmUg PSB0aW1lX3NlY29uZCArIGFycHRfa2VlcDsNCioqKioqKioqKioqKioqKg0K KioqIDY0Nyw2NTQgKioqKg0KICAJKHZvaWQpbWVtY3B5KGVhLT5hcnBfc3Bh LCAmaXRhZGRyLCBzaXplb2YoZWEtPmFycF9zcGEpKTsNCiAgCWVhLT5hcnBf b3AgPSBodG9ucyhBUlBPUF9SRVBMWSk7DQogIAllYS0+YXJwX3BybyA9IGh0 b25zKEVUSEVSVFlQRV9JUCk7IC8qIGxldCdzIGJlIHN1cmUhICovDQohIAlz d2l0Y2ggKG50b2hzKGVhLT5hcnBfaHJkKSkgew0KISAJY2FzZSBBUlBIUkRf SUVFRTgwMjoNCiAgCQkvKiBSZS1hcnJhbmdlIHRoZSBzb3VyY2UvZGVzdCBh ZGRyZXNzICovDQogIAkJbWVtY3B5KHRoLT5pc284ODAyNV9kaG9zdCwgdGgt Pmlzbzg4MDI1X3Nob3N0LCBzaXplb2YodGgtPmlzbzg4MDI1X2Rob3N0KSk7 DQogIAkJbWVtY3B5KHRoLT5pc284ODAyNV9zaG9zdCwgYWMtPmFjX2VuYWRk ciwgc2l6ZW9mKHRoLT5pc284ODAyNV9zaG9zdCkpOw0KLS0tIDY1MSw2NTgg LS0tLQ0KICAJKHZvaWQpbWVtY3B5KGVhLT5hcnBfc3BhLCAmaXRhZGRyLCBz aXplb2YoZWEtPmFycF9zcGEpKTsNCiAgCWVhLT5hcnBfb3AgPSBodG9ucyhB UlBPUF9SRVBMWSk7DQogIAllYS0+YXJwX3BybyA9IGh0b25zKEVUSEVSVFlQ RV9JUCk7IC8qIGxldCdzIGJlIHN1cmUhICovDQohIAlzd2l0Y2ggKGFjLT5h Y19pZi5pZl90eXBlKSB7DQohIAljYXNlIElGVF9JU084ODAyNToNCiAgCQkv KiBSZS1hcnJhbmdlIHRoZSBzb3VyY2UvZGVzdCBhZGRyZXNzICovDQogIAkJ bWVtY3B5KHRoLT5pc284ODAyNV9kaG9zdCwgdGgtPmlzbzg4MDI1X3Nob3N0 LCBzaXplb2YodGgtPmlzbzg4MDI1X2Rob3N0KSk7DQogIAkJbWVtY3B5KHRo LT5pc284ODAyNV9zaG9zdCwgYWMtPmFjX2VuYWRkciwgc2l6ZW9mKHRoLT5p c284ODAyNV9zaG9zdCkpOw0KKioqKioqKioqKioqKioqDQoqKiogNjYzLDY2 OSAqKioqDQogIAkJc2Euc2FfZGF0YVsoc2l6ZW9mKHRoLT5pc284ODAyNV9k aG9zdCkgKiAyKV0gPSAweDEwOw0KICAJCXNhLnNhX2RhdGFbKHNpemVvZih0 aC0+aXNvODgwMjVfZGhvc3QpICogMikgKyAxXSA9IDB4NDA7DQogIAkJYnJl YWs7DQohIAljYXNlIEFSUEhSRF9FVEhFUjoNCiAgCQllaCA9IChzdHJ1Y3Qg ZXRoZXJfaGVhZGVyICopc2Euc2FfZGF0YTsNCiAgCQkodm9pZCltZW1jcHko ZWgtPmV0aGVyX2Rob3N0LCBlYS0+YXJwX3RoYSwgc2l6ZW9mKGVoLT5ldGhl cl9kaG9zdCkpOw0KICAJCWVoLT5ldGhlcl90eXBlID0gaHRvbnMoRVRIRVJU WVBFX0FSUCk7DQotLS0gNjY3LDY3MyAtLS0tDQogIAkJc2Euc2FfZGF0YVso c2l6ZW9mKHRoLT5pc284ODAyNV9kaG9zdCkgKiAyKV0gPSAweDEwOw0KICAJ CXNhLnNhX2RhdGFbKHNpemVvZih0aC0+aXNvODgwMjVfZGhvc3QpICogMikg KyAxXSA9IDB4NDA7DQogIAkJYnJlYWs7DQohIAljYXNlIElGVF9FVEhFUjoN CiAgCQllaCA9IChzdHJ1Y3QgZXRoZXJfaGVhZGVyICopc2Euc2FfZGF0YTsN CiAgCQkodm9pZCltZW1jcHkoZWgtPmV0aGVyX2Rob3N0LCBlYS0+YXJwX3Ro YSwgc2l6ZW9mKGVoLT5ldGhlcl9kaG9zdCkpOw0KICAJCWVoLT5ldGhlcl90 eXBlID0gaHRvbnMoRVRIRVJUWVBFX0FSUCk7DQo= --0-1609105550-924112445=:3818-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 11:49:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id EA46C15808 for ; Wed, 14 Apr 1999 11:49:51 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id OAA16847; Wed, 14 Apr 1999 14:47:22 -0400 (EDT) (envelope-from lile@stdio.com) Date: Wed, 14 Apr 1999 14:47:22 -0400 (EDT) From: Larry Lile To: ip@mcc.ac.uk Cc: current@FreeBSD.ORG Subject: Re: Patch to fix [Re: Bad, reliable crash: Julian's "oltr" stuff & ARP] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2124461379-924115642=:3818" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2124461379-924115642=:3818 Content-Type: TEXT/PLAIN; charset=US-ASCII Okay, that one is just a little too strong. It won't allow a FreeBSD token-ring station to arp-reply to an ethernet station on the other side of a "broken" translational bridge. This one will. Larry Lile lile@stdio.com On Wed, 14 Apr 1999, Larry Lile wrote: > > The problem Mr. Pallfreeman was seeing are related to how I was > building the arp-reply based on the sources arp_hrd type. I never > expected to see a token-ring arp arrive over an ethernet interface. > Therefore the arp code was trying to check for and collect the > source route that the arp took on its way. I have modified the > arp code to go looking for the source-route information only if > the arp comes from a token-ring station and is received on a > token-ring interface. The arp-reply packet generated is based > on the type of interface the arp was received on. I think > the bridge should have changed the arp_hrd type when it forwarded > the packet, while it was changing everything else, but I think > that falls into a religous debate. Thanks to Mr. Pallfreeman > for helping me debug this and testing my patch. > > What this means is: you should be able to arp in both directions > over a token-ring<->ethernet (translational|non-translational) bridge. > > The inherent "brokenness" of translational bridging is left as an > exercise for the reader :) > > Here's the patch, if someone would be kind enough to commit it. It > seems to have resolved Mr. Pallfreeman's issue and doesn't seem to > break anything else. > > Larry Lile > lile@stdio.com > --0-2124461379-924115642=:3818 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="if_ether.c.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: ARP Patch revisited Content-Disposition: attachment; filename="if_ether.c.patch" KioqIGlmX2V0aGVyLmMub3JpZwlNb24gTWFyICA4IDEzOjIyOjQxIDE5OTkN Ci0tLSBpZl9ldGhlci5jCVdlZCBBcHIgMTQgMTQ6NDM6NDEgMTk5OQ0KKioq KioqKioqKioqKioqDQoqKiogNTU5LDU2NiAqKioqDQogIAkJKHZvaWQpbWVt Y3B5KExMQUREUihzZGwpLCBlYS0+YXJwX3NoYSwgc2l6ZW9mKGVhLT5hcnBf c2hhKSk7DQogIAkJc2RsLT5zZGxfYWxlbiA9IHNpemVvZihlYS0+YXJwX3No YSk7DQogICAgICAgICAgICAgICAgICBzZGwtPnNkbF9yY2YgPSBOVUxMOw0K ISAJCS8qIFNhdmUgc291cmNlIHJvdXRpbmcgaW5mb3JtYXRpb24gZm9yIFRv a2VuLXJpbmcgaW50ZXJmYWNlcywgaWYgYXZhaWxhYmxlICovDQohIAkJaWYg KGVhLT5hcnBfaHJkID09IGh0b25zKEFSUEhSRF9JRUVFODAyKSkgew0KICAJ CQl0aCA9IChzdHJ1Y3QgaXNvODgwMjVfaGVhZGVyICopbS0+bV9wa3RoZHIu aGVhZGVyOw0KICAgICAgICAgICAgICAgICAgCWlmICgodGgtPmlzbzg4MDI1 X3Nob3N0WzBdICYgMHg4MCkgJiYgKCgobnRvaHModGgtPnJjZikgJiAweDFm MDApID4+IDgpID4gMikpIHsNCiAgCQkJCXNkbC0+c2RsX3JjZiA9IG50b2hz KHRoLT5yY2YpICYgMHgwMDgwID8gDQotLS0gNTU5LDU2OCAtLS0tDQogIAkJ KHZvaWQpbWVtY3B5KExMQUREUihzZGwpLCBlYS0+YXJwX3NoYSwgc2l6ZW9m KGVhLT5hcnBfc2hhKSk7DQogIAkJc2RsLT5zZGxfYWxlbiA9IHNpemVvZihl YS0+YXJwX3NoYSk7DQogICAgICAgICAgICAgICAgICBzZGwtPnNkbF9yY2Yg PSBOVUxMOw0KISAJCS8qIElmIHdlIHJlY2VpdmUgYW4gYXJwIGZyb20gYSB0 b2tlbi1yaW5nIHN0YXRpb24gb3ZlciBhIHRva2VuLXJpbmcgbmljDQohIAkJ ICogdGhlbiB0cnkgdG8gc2F2ZSB0aGUgc291cmNlIHJvdXRpbmcgaW5mby4N CiEgCQkgKi8NCiEgCQlpZiAoYWMtPmFjX2lmLmlmX3R5cGUgPT0gSUZUX0lT Tzg4MDI1KSB7DQogIAkJCXRoID0gKHN0cnVjdCBpc284ODAyNV9oZWFkZXIg KiltLT5tX3BrdGhkci5oZWFkZXI7DQogICAgICAgICAgICAgICAgICAJaWYg KCh0aC0+aXNvODgwMjVfc2hvc3RbMF0gJiAweDgwKSAmJiAoKChudG9ocyh0 aC0+cmNmKSAmIDB4MWYwMCkgPj4gOCkgPiAyKSkgew0KICAJCQkJc2RsLT5z ZGxfcmNmID0gbnRvaHModGgtPnJjZikgJiAweDAwODAgPyANCioqKioqKioq KioqKioqKg0KKioqIDU3Nyw1ODIgKioqKg0KLS0tIDU3OSw1ODYgLS0tLQ0K ICAJCQl9DQogIAkJCXRoLT5yY2YgPSBzZGwtPnNkbF9yY2Y7DQogIAkJCQ0K KyAJCX0gZWxzZSB7DQorIAkJCXNkbC0+c2RsX3JjZiA9IE5VTEw7DQogIAkJ fQ0KICAJCWlmIChydC0+cnRfZXhwaXJlKQ0KICAJCQlydC0+cnRfZXhwaXJl ID0gdGltZV9zZWNvbmQgKyBhcnB0X2tlZXA7DQoqKioqKioqKioqKioqKioN CioqKiA2NDYsNjUzICoqKioNCiAgCSh2b2lkKW1lbWNweShlYS0+YXJwX3Nw YSwgJml0YWRkciwgc2l6ZW9mKGVhLT5hcnBfc3BhKSk7DQogIAllYS0+YXJw X29wID0gaHRvbnMoQVJQT1BfUkVQTFkpOw0KICAJZWEtPmFycF9wcm8gPSBo dG9ucyhFVEhFUlRZUEVfSVApOyAvKiBsZXQncyBiZSBzdXJlISAqLw0KISAJ c3dpdGNoIChudG9ocyhlYS0+YXJwX2hyZCkpIHsNCiEgCWNhc2UgQVJQSFJE X0lFRUU4MDI6DQogIAkJLyogUmUtYXJyYW5nZSB0aGUgc291cmNlL2Rlc3Qg YWRkcmVzcyAqLw0KICAJCW1lbWNweSh0aC0+aXNvODgwMjVfZGhvc3QsIHRo LT5pc284ODAyNV9zaG9zdCwgc2l6ZW9mKHRoLT5pc284ODAyNV9kaG9zdCkp Ow0KICAJCW1lbWNweSh0aC0+aXNvODgwMjVfc2hvc3QsIGFjLT5hY19lbmFk ZHIsIHNpemVvZih0aC0+aXNvODgwMjVfc2hvc3QpKTsNCi0tLSA2NTAsNjU3 IC0tLS0NCiAgCSh2b2lkKW1lbWNweShlYS0+YXJwX3NwYSwgJml0YWRkciwg c2l6ZW9mKGVhLT5hcnBfc3BhKSk7DQogIAllYS0+YXJwX29wID0gaHRvbnMo QVJQT1BfUkVQTFkpOw0KICAJZWEtPmFycF9wcm8gPSBodG9ucyhFVEhFUlRZ UEVfSVApOyAvKiBsZXQncyBiZSBzdXJlISAqLw0KISAJc3dpdGNoIChhYy0+ YWNfaWYuaWZfdHlwZSkgew0KISAJY2FzZSBJRlRfSVNPODgwMjU6DQogIAkJ LyogUmUtYXJyYW5nZSB0aGUgc291cmNlL2Rlc3QgYWRkcmVzcyAqLw0KICAJ CW1lbWNweSh0aC0+aXNvODgwMjVfZGhvc3QsIHRoLT5pc284ODAyNV9zaG9z dCwgc2l6ZW9mKHRoLT5pc284ODAyNV9kaG9zdCkpOw0KICAJCW1lbWNweSh0 aC0+aXNvODgwMjVfc2hvc3QsIGFjLT5hY19lbmFkZHIsIHNpemVvZih0aC0+ aXNvODgwMjVfc2hvc3QpKTsNCioqKioqKioqKioqKioqKg0KKioqIDY2Miw2 NjggKioqKg0KICAJCXNhLnNhX2RhdGFbKHNpemVvZih0aC0+aXNvODgwMjVf ZGhvc3QpICogMildID0gMHgxMDsNCiAgCQlzYS5zYV9kYXRhWyhzaXplb2Yo dGgtPmlzbzg4MDI1X2Rob3N0KSAqIDIpICsgMV0gPSAweDQwOw0KICAJCWJy ZWFrOw0KISAJY2FzZSBBUlBIUkRfRVRIRVI6DQogIAkJZWggPSAoc3RydWN0 IGV0aGVyX2hlYWRlciAqKXNhLnNhX2RhdGE7DQogIAkJKHZvaWQpbWVtY3B5 KGVoLT5ldGhlcl9kaG9zdCwgZWEtPmFycF90aGEsIHNpemVvZihlaC0+ZXRo ZXJfZGhvc3QpKTsNCiAgCQllaC0+ZXRoZXJfdHlwZSA9IGh0b25zKEVUSEVS VFlQRV9BUlApOw0KLS0tIDY2Niw2NzIgLS0tLQ0KICAJCXNhLnNhX2RhdGFb KHNpemVvZih0aC0+aXNvODgwMjVfZGhvc3QpICogMildID0gMHgxMDsNCiAg CQlzYS5zYV9kYXRhWyhzaXplb2YodGgtPmlzbzg4MDI1X2Rob3N0KSAqIDIp ICsgMV0gPSAweDQwOw0KICAJCWJyZWFrOw0KISAJY2FzZSBJRlRfRVRIRVI6 DQogIAkJZWggPSAoc3RydWN0IGV0aGVyX2hlYWRlciAqKXNhLnNhX2RhdGE7 DQogIAkJKHZvaWQpbWVtY3B5KGVoLT5ldGhlcl9kaG9zdCwgZWEtPmFycF90 aGEsIHNpemVvZihlaC0+ZXRoZXJfZGhvc3QpKTsNCiAgCQllaC0+ZXRoZXJf dHlwZSA9IGh0b25zKEVUSEVSVFlQRV9BUlApOw0K --0-2124461379-924115642=:3818-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 11:57:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from work.mzaki.nom (173.pool15.tokyo.att.ne.jp [165.76.220.188]) by hub.freebsd.org (Postfix) with ESMTP id 9565214D2F; Wed, 14 Apr 1999 11:57:28 -0700 (PDT) (envelope-from mzaki@e-mail.ne.jp) Received: from localhost (localhost [127.0.0.1]) by work.mzaki.nom (8.9.2/8.9.2) with ESMTP id DAA05453; Thu, 15 Apr 1999 03:54:47 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) To: dcs@newsguy.com Cc: logix@foobar.franken.de, freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. In-Reply-To: <3714D32A.DF778838@newsguy.com> References: <199904140620.XAA24224@freefall.freebsd.org> <37149716.582342ED@newsguy.com> <19990414164548.A14876@foobar.franken.de> <19990415021736I.mzaki@e-mail.ne.jp> <3714D32A.DF778838@newsguy.com> X-Mailer: Mew version 1.94b7 on XEmacs 21.0 (20 minutes to Nikko) X-fingerprint: BD 86 CD D9 66 FD 75 B0 A8 43 4B C4 E2 1B F5 B5 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990415035446A.mzaki@e-mail.ne.jp> Date: Thu, 15 Apr 1999 03:54:46 +0900 From: Motomichi Matsuzaki X-Dispatcher: imput version 990212(IM106) Lines: 49 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Daniel C. Sobral" Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. Date: Thu, 15 Apr 1999 02:40:58 +0900 dcs> > 2. Only Page 00 Unicode is shown (for Joliet CDs). dcs> ... dcs> > Note. dcs> > Byung's patch passes Unicode transparently. dcs> > So CJK filenames are shown if terminals do Unicodes well. dcs> dcs> Do you mean that your patch shows only page 00, but Byung's patch dcs> passes Unicode directly? My patch: * character in page 00 is converted to ASCII(+ISO-8859-1) * character in other pages is replaced by '?' Byung's patch: * character in page 00 is converted to ASCII(+ISO-8859-1) * character in other pages is passed as is For example, suppose to be a file on Joliet CD, which filename is encoded as [ 0041 0042 0043 2525 3030 3535 ] in Unicode. The kernel applied my patch shows it to userland via readdir(2) as (41)(42)(43)(3F)(3F)(3F) ... "abc???" The kernel applied Byung's patch shows it as (41)(42)(43)(25)(25)(30)(30)(35)(35) ... "abc%%0055" Byung reported, > With this patch, I was able to see long file names and > non-english characters(such as korean&chinese) so i believe it > does support unicode as long as your locale is set correctly. But with my locale 'ja_JP.EUC' (which is the major in Japan on *BSD box), these strings make no sense. To see filenames which contain Japanese characters, kernel should convert it to EUC(JP). Another possible answer is encoding to UTF-8, however, I don't know UTF-8 terminal compliant with Japanese. -- Motomichi Matsuzaki Dept. of Biological Science, Fuculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 12:11:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 28CE5152A9 for ; Wed, 14 Apr 1999 12:11:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA32003; Wed, 14 Apr 1999 12:08:20 -0700 (PDT) (envelope-from dillon) Date: Wed, 14 Apr 1999 12:08:20 -0700 (PDT) From: Matthew Dillon Message-Id: <199904141908.MAA32003@apollo.backplane.com> To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: NFS, blocks of NULLs in files References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably :with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999) :running both on server and client (except that the client's kernel is 24hrs :older than that). : :It happens during a kernel build on the client, so both the sources and :objects are being accessed via NFS. During the 'generating linker set :emulation glue for ELF' phase, a lot of the .o's turn up with blocks of :NULLs. The rest of the world builds fine, but /usr/obj is local so there is :little or no NFS writing going on in that case. : :The client is SMP but it's been doing daily builds with -j8 since that got :sorted out, and anyway it now fails in exactly the same way whether -j is :used or not. : : :-- :Bob Bishop (0118) 977 4017 international code +44 118 :rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK I've been working on this for the last few days. I should have an experiemental fix today. I'll post to current & hackers when it's ready. The problem is related to the mmap fixes which went in a few days ago. These fixes brought out yet another bug in NFS. The mmap fixes themselves are correct. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 12:59:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id AA8F614EA9 for ; Wed, 14 Apr 1999 12:59:25 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id OAA25121; Wed, 14 Apr 1999 14:55:30 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 14 Apr 1999 14:55:27 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: dcs@newsguy.com Cc: current@freebsd.org Subject: Re: swap-related problems X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14100.61923.427423.153188@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > All I want is that a program gets NULL from malloc if there is no memory : > available. I find that to be a very fundamental thing about malloc. : Do you have a solution? We don't. Make an sbrk variant which will pre-allocate backing store. setenv MALLOC_PREALLOCATE Not so hard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 13: 3:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 7854E1579F for ; Wed, 14 Apr 1999 13:03:25 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id WAA00854; Wed, 14 Apr 1999 22:01:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id WAA01894; Wed, 14 Apr 1999 22:00:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: alk@pobox.com Cc: dcs@newsguy.com, current@FreeBSD.org Subject: Re: swap-related problems In-reply-to: Your message of "Wed, 14 Apr 1999 14:55:27 CDT." <14100.61923.427423.153188@avalon.east> Date: Wed, 14 Apr 1999 22:00:59 +0200 Message-ID: <1892.924120059@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14100.61923.427423.153188@avalon.east>, Anthony Kimball writes: > >: > All I want is that a program gets NULL from malloc if there is no memory >: > available. I find that to be a very fundamental thing about malloc. > >: Do you have a solution? We don't. > >Make an sbrk variant which will pre-allocate backing store. >setenv MALLOC_PREALLOCATE > >Not so hard. 1. Demonstrate the need. 2. Implement it 3. Send patches. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 13:28:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id 1B4AC15876 for ; Wed, 14 Apr 1999 13:28:31 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id PAA25230; Wed, 14 Apr 1999 15:22:23 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 14 Apr 1999 15:22:22 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: phk@critter.freebsd.dk Cc: current@FreeBSD.org Subject: Re: swap-related problems References: <14100.61923.427423.153188@avalon.east> <1892.924120059@critter.freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14100.62842.127882.239452@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Poul-Henning Kamp on Wed, 14 April: : : 1. Demonstrate the need. Well, it's only needed if you want to be able to reliably execute ANSI C code according to spec. I personally don't care. I'd be surprised if core didn't though. I would suspect that it would be deemed worthy of someone's p2 queue, at least. : 2. Implement it : : 3. Send patches. And I certainly don't care enough to do that!-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 13:50:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id AAF6F158D9 for ; Wed, 14 Apr 1999 13:50:05 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id QAA57509; Wed, 14 Apr 1999 16:40:42 -0400 (EDT) Date: Wed, 14 Apr 1999 16:40:42 -0400 (EDT) From: Chuck Robey To: Anthony Kimball Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <14100.62842.127882.239452@avalon.east> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Anthony Kimball wrote: > Quoth Poul-Henning Kamp on Wed, 14 April: > : > : 1. Demonstrate the need. > > Well, it's only needed if you want to be able to reliably execute ANSI > C code according to spec. I personally don't care. I'd be surprised > if core didn't though. I would suspect that it would be deemed worthy > of someone's p2 queue, at least. I can't understand this. Make software that causes a major performance loss, and loses *bigtime* in memory allocation, just so the one guy to complain *at all* can not lose sleep over something that has causes no problems at all with any ANSI code in a properly sized system. The complainant could not notice a problem in any program that didn't seriously over-allocate memory in the first place. His program is far more likely to work in our present paradigm than in the one he wishes everyone to use. I don't think he understands, at all, the global effects of his requests; he has blinders on, and is looking at one program, only, in a otherwise unloaded system. This is supposed to be important enough to hit someone's work queue? No wonder *you* won't do it. > > : 2. Implement it > : > : 3. Send patches. > > And I certainly don't care enough to do that!-) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 14: 9:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id EDD32158F1 for ; Wed, 14 Apr 1999 14:08:56 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA30479; Wed, 14 Apr 1999 22:48:57 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.2/8.6.12) id WAA02242; Wed, 14 Apr 1999 22:54:29 +0200 (CEST) From: Wilko Bulte Message-Id: <199904142054.WAA02242@yedi.iaf.nl> Subject: Re: NFS, blocks of NULLs in files In-Reply-To: from Bob Bishop at "Apr 14, 1999 5:53:34 pm" To: rb@gid.co.uk (Bob Bishop) Date: Wed, 14 Apr 1999 22:54:29 +0200 (CEST) Cc: current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Bob Bishop wrote ... > I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably > with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999) > running both on server and client (except that the client's kernel is 24hrs > older than that). > > It happens during a kernel build on the client, so both the sources and > objects are being accessed via NFS. During the 'generating linker set > emulation glue for ELF' phase, a lot of the .o's turn up with blocks of > NULLs. The rest of the world builds fine, but /usr/obj is local so there is > little or no NFS writing going on in that case. I have the impression I'm seeing similar things here. I have a 3.1 NFS server holding the -current sources. I build kernels over NFS using a -current testbox. Sometimes it builds kernels alright, sometimes you get kernels that panic with 100% repeatability. Just doing a config -r and a rebuild normally fixes this. The same thing happened when the NFS server was still at 2.2.8-stable Buildworlds with a local /usr/obj seem to work just fine. Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 14:10:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id 42B21158FA; Wed, 14 Apr 1999 14:10:53 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id QAA25416; Wed, 14 Apr 1999 16:07:37 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 14 Apr 1999 16:07:36 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: chuckr@picnic.mat.net Cc: chat@FreeBSD.ORG Subject: Re: swap-related problems References: <14100.62842.127882.239452@avalon.east> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14101.711.573218.994126@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Chuck Robey on Wed, 14 April: : ... just so the one guy to : complain *at all* Someone is always the first person to recognize a defect. Until others do, they stand alone. : ...can not lose sleep over something that has causes no : problems at all with any ANSI code in a properly sized system. "properly sized system"? Smirk. Let's redirect this to chat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 14:50: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id CE5F115916 for ; Wed, 14 Apr 1999 14:49:53 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id XAA11088 for ; Wed, 14 Apr 1999 23:47:29 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma011086; Wed, 14 Apr 99 23:47:29 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id XAA26433 for ; Wed, 14 Apr 1999 23:47:28 +0200 (MET DST) Received: (qmail 54529 invoked by uid 666); 14 Apr 1999 21:47:49 -0000 Date: Wed, 14 Apr 1999 23:47:49 +0200 From: Jos Backus To: freebsd-current@freebsd.org Subject: /usr/src/UPDATING question Message-ID: <19990414234749.A42258@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While doing a ``make -DWANT_AOUT world'' I'm seeing the following: ===> libgcc_r c++ -O -pipe -march=pentium -I/usr/src/gnu/lib/libgcc_r/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc_r/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -D_PTHREADS -I/usr/src/gnu/lib/libgcc_r/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -c /usr/src/gnu/lib/libgcc_r/../../../contrib/egcs/gcc/cp/tinfo2.cc -o tinfo2.o {standard input}: Assembler messages: {standard input}:4188: Error: Unknown pseudo-op: `.section' *** Error code 1 Stop. *** Error code 1 Stop. Questions: - Is it just my (two) systems? (cvsupped today, regular make world == fine) - I don't understand the wording of the most recent paragraph: Note cc -aout has been broken since the conversion to egcs. If you have rebuilt things like XFree86 a.out libraries, you should rebuild them again or things (including netscape) will not work. If it's true that cc -aout is broken (.section in an a.out .o file? Hm.), how can one rebuild things like XFree86 a.out libraries, when make world fails? Sorry to bother y'all but apparently I'm klewl3ss today... Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 15: 0:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id F39791503D for ; Wed, 14 Apr 1999 15:00:09 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA43531; Wed, 14 Apr 1999 15:57:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA05239; Wed, 14 Apr 1999 15:57:32 -0600 (MDT) Message-Id: <199904142157.PAA05239@harmony.village.org> To: Jos Backus Subject: Re: /usr/src/UPDATING question Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 14 Apr 1999 23:47:49 +0200." <19990414234749.A42258@hal.mpn.cp.philips.com> References: <19990414234749.A42258@hal.mpn.cp.philips.com> Date: Wed, 14 Apr 1999 15:57:32 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990414234749.A42258@hal.mpn.cp.philips.com> Jos Backus writes: : - I don't understand the wording of the most recent paragraph: : : Note cc -aout has been broken since the conversion to egcs. If : you have rebuilt things like XFree86 a.out libraries, you should : rebuild them again or things (including netscape) will not work. : : If it's true that cc -aout is broken (.section in an a.out .o file? Hm.), how : can one rebuild things like XFree86 a.out libraries, when make world fails? What it means is that cc -aout has been broken since the conversion to egcs, and now it is supposedly working. Don't know about building an aout world. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 15: 6:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 6E75D14BCE for ; Wed, 14 Apr 1999 15:06:42 -0700 (PDT) (envelope-from tim@scratch.demon.co.uk) Received: from [212.228.22.156] (helo=franklin.matlink) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 10XXlb-0006Ll-0A; Wed, 14 Apr 1999 22:04:19 +0000 Received: (from tim@localhost) by franklin.matlink (8.9.3/8.9.3) id HAA22663; Wed, 14 Apr 1999 07:25:41 +0100 (BST) (envelope-from tim) Date: Wed, 14 Apr 1999 07:25:11 +0100 From: Tim Preece To: Bret Ford Cc: Tim Preece , freebsd-current@freebsd.org Subject: Re: ftp hangs on -current Message-ID: <19990414072511.A22655@franklin.matlink> Reply-To: Tim Preece Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: x-unknown X-Mailer: Balsa 0.4.9 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999 01:21:20 Bret Ford wrote: > > > > > > On Tue, 13 Apr 1999 18:34:25 Ilya Naumov wrote: > > > Hello Gianmarco, > > > > > > Thursday, April 08, 1999, 7:49:52 AM, you wrote: > > > > > > GG> "ftp" on 4.0-very-current (post egcs make world) randomly hangs during > > > GG> sessions... > > > GG> I never succeded in finishing a session lately. > > > GG> To transfer some files from my home to my isp server I had to do an "ftp" > > > GG> from the server and a "get" to them... > > > > > > GG> The ftp server works normally and fetch is ok ... > > > GG> Probably it is a fault of my system, if no other experiences it. > > > > > > you're not alone with this problem here - i have the same one. and it > > > seems that it is somehow related to natd, because ftp works quite > > > well when i disable this daemon. any ideas? > > > > Well I am also experiencing something like this with ports and sendmail connections - intermittently, unfortunatly I > am not running natd ! > > > > I am getting problems similar to those outlined above. I don't run natd, either, but I do > have a firewall enabled. (open rule) I've had to 'put' files rather than 'get' them, since my > last build/installworld. (Yesterday's -current source) > > Bret Ford I am not running any firewall but my last cvsup which is also current was the same day as yours. Tim. I'd rather boot Bill Gates than Windoze any day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 15:19: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id F3F8014E59 for ; Wed, 14 Apr 1999 15:18:53 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id AAA17178 for ; Thu, 15 Apr 1999 00:16:32 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma017174; Thu, 15 Apr 99 00:16:32 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id AAA02225 for ; Thu, 15 Apr 1999 00:16:31 +0200 (MET DST) Received: (qmail 57078 invoked by uid 666); 14 Apr 1999 22:16:49 -0000 Date: Thu, 15 Apr 1999 00:16:49 +0200 From: Jos Backus To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: /usr/src/UPDATING question Message-ID: <19990415001649.B42258@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990414234749.A42258@hal.mpn.cp.philips.com> <199904142157.PAA05239@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199904142157.PAA05239@harmony.village.org>; from Warner Losh on Wed, Apr 14, 1999 at 03:57:32PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 14, 1999 at 03:57:32PM -0600, Warner Losh wrote: > What it means is that cc -aout has been broken since the conversion to > egcs, and now it is supposedly working. I see ``supposedly'' sounds about right :) > Don't know about building an aout world. According to my system, no... I wanted to rebuild the aout bits too in an attempt to cure communicator's core creation craze, but alas. Wouldn't it be nice if the friendly folks at Netscape created an ELF version of their browser? Thanks anyway. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 15:22: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id AFE6415843 for ; Wed, 14 Apr 1999 15:21:56 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10XXwF-000Np4-00; Thu, 15 Apr 1999 00:15:19 +0200 From: Sheldon Hearn To: alk@pobox.com Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: swap-related problems In-reply-to: Your message of "Wed, 14 Apr 1999 15:22:22 EST." <14100.62842.127882.239452@avalon.east> Date: Thu, 15 Apr 1999 00:15:19 +0200 Message-ID: <91577.924128119@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999 15:22:22 EST, Anthony Kimball wrote: > : 3. Send patches. > > And I certainly don't care enough to do that!-) So, what? You're just arguing for fun? If so, then you and everyone else doing like wise can just piss the hell off. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 15:29: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id 92A1415985; Wed, 14 Apr 1999 15:28:43 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id RAA25702; Wed, 14 Apr 1999 17:25:26 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 14 Apr 1999 17:25:26 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: sheldonh@iafrica.com Cc: chat@FreeBSD.ORG Subject: Re: swap-related problems References: <14100.62842.127882.239452@avalon.east> <91577.924128119@axl.noc.iafrica.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14101.5050.590013.685243@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Sheldon Hearn on Thu, 15 April: : : > : 3. Send patches. : > : > And I certainly don't care enough to do that!-) : : So, what? You're just arguing for fun? If so, then you and everyone else : doing like wise can just piss the hell off. [redirected to chat] No, I'm trying to contribute constructively to a discussion which may affect policy in the future. One party suggested that there was an admitted problem in the current system, but that "we" didn't know how to fix it. I suggested a fix. This makes it easier for anyone who cares enough to (1) write the code, and (2) fight the mugwump politics, to implement a solution to the benefit of everyone who uses the code. Do I care about this particular problem that much? No. My concerns lie elsewhere. I do think it is important the the actual problem be recognized, and that its solvability within acceptable constraints be recognized. Otherwise, people may make bad decisions -- for example, rejecting patches offered by persons for whom this issue is more pressing. Besides, when someone makes a reasonable complaint and is derided unfairly for it, it would be craven and despicable not to co-advocate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 15:46:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id DF319157C5 for ; Wed, 14 Apr 1999 15:46:26 -0700 (PDT) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id IAA28222 for ; Thu, 15 Apr 1999 08:44:04 +1000 (EST) X-BPC-Relay-Envelope-From: andrew@lake.com.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-51-95.nsw.bigpond.net.au [24.192.51.95]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id IAA16995 for ; Thu, 15 Apr 1999 08:44:03 +1000 (EST) Received: (qmail 2078 invoked by uid 1000); 14 Apr 1999 22:37:20 -0000 From: "Andrew Reilly" Message-ID: <19990415083720.A1870@reilly.home> Date: Thu, 15 Apr 1999 08:37:20 +1000 To: alk@pobox.com, dcs@newsguy.com Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: <14100.61923.427423.153188@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <14100.61923.427423.153188@avalon.east>; from Anthony Kimball on Wed, Apr 14, 1999 at 02:55:27PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 14, 1999 at 02:55:27PM -0500, Anthony Kimball wrote: > > : > All I want is that a program gets NULL from malloc if there is no memory > : > available. I find that to be a very fundamental thing about malloc. > > : Do you have a solution? We don't. > > Make an sbrk variant which will pre-allocate backing store. > setenv MALLOC_PREALLOCATE > > Not so hard. You could do this yourself, I think, by: 1) create your own backing file of the appropriate size 2) mmap it into your address space 3) tell your own malloc() routine that that's where it should get memory from. Any problems with that? (besides not being the system standard, and the reduction of swapping efficiency caused by going through the file system). -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 15:47:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id AF4D4157C5 for ; Wed, 14 Apr 1999 15:47:13 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id SAA96731 for current@freebsd.org; Wed, 14 Apr 1999 18:44:52 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904142244.SAA96731@misha.cisco.com> Subject: Re: swap-related problems In-Reply-To: <91577.924128119@axl.noc.iafrica.com> from Sheldon Hearn at "Apr 15, 1999 00:15:19 am" To: current@freebsd.org Date: Wed, 14 Apr 1999 18:44:52 -0400 (EDT) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn once wrote: > > : 3. Send patches. > > > > And I certainly don't care enough to do that!-) > So, what? You're just arguing for fun? If so, then you and everyone > else doing like wise can just piss the hell off. I, for one, was arguing because I saw a number of people ask about this over the last years. Instead of being told "sorry, we do not comply with this part of ANSI standard for reasons such and such", this people were told how they have to be better sysadmins and what not. This time around, it took several days of a long thread for somebody to admit _the problem exists_. People are sensitive about this -- you yourself had to resort to using a notion refering to physiology AND a notion of religious nature to express your feelings... To avoid this discussion in the future, Handbook, FAQ, and malloc(3) should be updated to reflect the fact, that FreeBSD's malloc does NOT indeed to conform to ANSI/C, strictly speaking. All good arguments as to why this is good for someone's health can also go there. A TODO list can have an entry about this, because ANSI compliance is A Good Thing(TM), is not it? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 16: 8:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 4B59B15072 for ; Wed, 14 Apr 1999 16:08:29 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id QAA43660; Wed, 14 Apr 1999 16:03:28 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904142303.QAA43660@troutmask.apl.washington.edu> Subject: Re: swap-related problems In-Reply-To: <199904142244.SAA96731@misha.cisco.com> from Mikhail Teterin at "Apr 14, 1999 06:44:52 pm" To: mi@aldan.algebra.com Date: Wed, 14 Apr 1999 16:03:27 -0700 (PDT) Cc: current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > Sheldon Hearn once wrote: > > > > : 3. Send patches. > > > > > > And I certainly don't care enough to do that!-) > > > So, what? You're just arguing for fun? If so, then you and everyone > > else doing like wise can just piss the hell off. > > I, for one, was arguing because I saw a number of people ask about > this over the last years. > > Instead of being told "sorry, we do not comply with this part of > ANSI standard for reasons such and such", this people were told > how they have to be better sysadmins and what not. > > This time around, it took several days of a long thread for somebody > to admit _the problem exists_. > Then, submit your patches to fix the problem preferably with a knob to turn your patches on/off. From the discussion, I hope you're prepared to deal with the following scenario: User: I compiled malloc with -DSTRICT_ANSI. Now my system appears sluggish and I can't run as many processes because of memory/swap starvation. Mikhail: Well, malloc() conforms to the ANSI C standard. You need to buy more memory and a real big disk drive for swap space. Or, you could run fewer processes. User: But, if I compile malloc without -DSTRICT_ANSI, then everything seems to work. Mikhail: Well, that is silly because now your malloc doesn't conform to the ANSI C standard. You should not use a nonconforming OS for programming. Submit your patches to the documentation pointing out the alleged shortcomings malloc() and friends. Meanwhile, visit /usr/ports. /usr/ports/devel/libxalloc /usr/ports/devel/libmalloc /usr/ports/devel/libdlmalloc -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 16:18:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 2D71214CE4 for ; Wed, 14 Apr 1999 16:18:47 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id SAA17428; Wed, 14 Apr 1999 18:30:05 -0500 (EST) Date: Wed, 14 Apr 1999 18:30:02 -0500 (EST) From: Alfred Perlstein To: Andrew Reilly Cc: alk@pobox.com, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <19990415083720.A1870@reilly.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Apr 1999, Andrew Reilly wrote: > On Wed, Apr 14, 1999 at 02:55:27PM -0500, Anthony Kimball wrote: > > > > : > All I want is that a program gets NULL from malloc if there is no memory > > : > available. I find that to be a very fundamental thing about malloc. > > > > : Do you have a solution? We don't. > > > > Make an sbrk variant which will pre-allocate backing store. > > setenv MALLOC_PREALLOCATE > > > > Not so hard. > > You could do this yourself, I think, by: > > 1) create your own backing file of the appropriate size > 2) mmap it into your address space > 3) tell your own malloc() routine that that's where it should > get memory from. > > Any problems with that? (besides not being the system standard, > and the reduction of swapping efficiency caused by going through > the file system). actually doesn't the BSD mmap spec state that if you map anything anon without special flags and there is no backing store available that the call will fail, and that there is a way to pass a flag to tell the system to overcommit but that you are prepared to take a SIGSEGV if you do cause the system to run out of backing store on the mepped object? looking at the manpages it seems that this is either undocumented or was never completed. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 16:42:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id AE68214D79 for ; Wed, 14 Apr 1999 16:42:28 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id TAA96857 for current@freebsd.org; Wed, 14 Apr 1999 19:40:07 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904142340.TAA96857@misha.cisco.com> Subject: Re: swap-related problems In-Reply-To: <199904142303.QAA43660@troutmask.apl.washington.edu> from Steve Kargl at "Apr 14, 1999 04:03:27 pm" To: current@freebsd.org Date: Wed, 14 Apr 1999 19:40:07 -0400 (EDT) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl once wrote: > Then, submit your patches to fix the problem preferably with a knob to > turn your patches on/off. From the discussion, I hope you're prepared > to deal with the following scenario: I'll be prepared... I don't think it should be a compile time option, though. May be kernel-compile-time -- malloc isn't really at fault here, it seems... But rather a run-time. > User: I compiled malloc with -DSTRICT_ANSI. Now my system appears > sluggish and I can't run as many processes because of > memory/swap starvation. [...] > Submit your patches to the documentation pointing out the alleged > shortcomings malloc() and friends. "Alleged" :-) > Meanwhile, visit /usr/ports. > /usr/ports/devel/libxalloc > /usr/ports/devel/libmalloc > /usr/ports/devel/libdlmalloc I do not see how they can guarantee the usability of the returned memory with the current kernel. There apparently is no way of knowing at malloc time if the memory can be used. Worse then that, it may be possible to use it at malloc time, but unless your program runs and touches every page, the memory may not be available later. If we are up to discussing the possible implementations, I'd suggest that the system uses something other then SIGKILL to notify the program it's time to pay for the over-commit speed and convenience. I think, SIGBUS is appropriate, but I'm not sure. Anything a program can _catch_ and react upon, if its author chooses to. Then, one can write a safe malloc, which will install the signal handler, and touch every page in the the memory referenced by the to-be-returned pointer. If the signal handler is invoked in the progress, the to-be-returned memory must be returned back to the system and NULL should be returned to the caller. Whether or not to use this "safe" malloc can be determined by malloc options and/or the size of the request. However, my (in)ability to propose anything remotely sensible does not change the facts established in this painful thread. That our malloc does not conform to standards (for whatever reasons), and that something should be done about it. That "something" must start with documenting the flaw... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 17: 0:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id B9AAB14DB4 for ; Wed, 14 Apr 1999 17:00:50 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id TAA04480; Wed, 14 Apr 1999 19:12:32 -0500 (EST) Date: Wed, 14 Apr 1999 19:12:30 -0500 (EST) From: Alfred Perlstein To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <199904142340.TAA96857@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Mikhail Teterin wrote: > Steve Kargl once wrote: > > > /usr/ports/devel/libxalloc > > /usr/ports/devel/libmalloc > > /usr/ports/devel/libdlmalloc > > I do not see how they can guarantee the usability of the returned > memory with the current kernel. There apparently is no way of > knowing at malloc time if the memory can be used. Worse then that, > it may be possible to use it at malloc time, but unless your program > runs and touches every page, the memory may not be available later. > > If we are up to discussing the possible implementations, I'd suggest > that the system uses something other then SIGKILL to notify the > program it's time to pay for the over-commit speed and convenience. > I think, SIGBUS is appropriate, but I'm not sure. > > Anything a program can _catch_ and react upon, if its author chooses > to. Design an impelementation says a SIGSEGV should be delivered afaik, but that's only for anon mmap. the problem with that is that you then can tell if your allocator is buggy, or you have a memory problem... > Then, one can write a safe malloc, which will install the signal > handler, and touch every page in the the memory referenced by the > to-be-returned pointer. If the signal handler is invoked in the > progress, the to-be-returned memory must be returned back to the > system and NULL should be returned to the caller. > > Whether or not to use this "safe" malloc can be determined by malloc > options and/or the size of the request. > > However, my (in)ability to propose anything remotely sensible does > not change the facts established in this painful thread. That our > malloc does not conform to standards (for whatever reasons), and > that something should be done about it. That "something" must start > with documenting the flaw... It's an impelementation, NOT a flaw. there should be a sysctl to force your "standard" impelementation, this current one is great for servers, desktop boxes and shell boxes, however for embedded systems where compenents shouldn't fail being killed for using memory you "rightously allocated" or potentially causing the death of an entirly different programming running is unnaceptable. it also makes for a really big PITA to debug the reason why a totally unrelated process was killed. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 17:40:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 170CF15244 for ; Wed, 14 Apr 1999 17:40:14 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id RAA58398; Wed, 14 Apr 1999 17:37:37 -0700 (PDT) (envelope-from obrien) Message-ID: <19990414173737.A58389@nuxi.com> Date: Wed, 14 Apr 1999 17:37:37 -0700 From: "David O'Brien" To: Jos Backus , freebsd-current@FreeBSD.ORG Subject: Re: /usr/src/UPDATING question Reply-To: obrien@NUXI.com References: <19990414234749.A42258@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990414234749.A42258@hal.mpn.cp.philips.com>; from Jos Backus on Wed, Apr 14, 1999 at 11:47:49PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - I don't understand the wording of the most recent paragraph: > > Note cc -aout has been broken since the conversion to egcs. If > you have rebuilt things like XFree86 a.out libraries, you should > rebuild them again or things (including netscape) will not work. Some have gotten -aout to work. When was your last CVSup and non-a.out `make world' ? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 17:43:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id B672B14DDC for ; Wed, 14 Apr 1999 17:43:07 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id UAA09200; Wed, 14 Apr 1999 20:40:40 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA20112; Wed, 14 Apr 1999 20:40:39 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id UAA30248; Wed, 14 Apr 1999 20:40:38 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <199904150040.UAA30248@dean.pc.sas.com> Subject: Re: swap-related problems In-Reply-To: <199904142340.TAA96857@misha.cisco.com> from Mikhail Teterin at "Apr 14, 1999 7:40: 7 pm" To: mi@aldan.algebra.com Date: Wed, 14 Apr 1999 20:40:38 -0400 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I do not see how they can guarantee the usability of the returned > memory with the current kernel. There apparently is no way of > knowing at malloc time if the memory can be used. Worse then that, > it may be possible to use it at malloc time, but unless your program > runs and touches every page, the memory may not be available later. Check the man page (and the source). It looks as if "export MALLOC_OPTIONS=Z" will cause malloc to touch every page and zero it out. This may be in part what you are wanting. Also, you can compile in malloc_options = "Z" to acheive the same affect without having to always export the environment variable. Of course, when you do this, your process will (might) still be killed immediately or at some point in the future, which I think is what you are trying to avoid :( -Brian -- Brian Dean brdean@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 18:15:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id AF3DF14F44 for ; Wed, 14 Apr 1999 18:15:25 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA83676; Wed, 14 Apr 1999 21:09:03 -0400 (EDT) Date: Wed, 14 Apr 1999 21:08:57 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Poul-Henning Kamp Cc: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <771.924103059@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Poul-Henning Kamp wrote: > In message <199904141501.LAA25847@kot.ne.mediaone.net>, Mikhail Teterin writes: > >Poul-Henning Kamp once stated: > > > >=malloc() on FreeBSD returns NULL when it cannot allocate the memory > >=asked for. > > > >=If you have an example where this is not the case I would VERY > >=much like to see it. > > > >I believe, a number of examples were given, when the use of the non-NULL > >pointer returned by malloc resulted in the program being killed. > > No, the examples I have seen showed the system killing a (somewhat) > random large process in an attempt to avoid deadlock. > > I guess you can interpret it the way above if you insist on using a > very narrow application oriented focus. > > Ignoring the larger issues is not a modus operandi I subscribe to. > > Anyway, what you're asking for is really resource reservation. > > Sorry FreeBSD doesn't support resource reservation for memory. mlock()? BTW, why can't anyone explain why the old behavior WAS THAT the process would get NULL? Now it's this... > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 18:18: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id CA79E14BE3 for ; Wed, 14 Apr 1999 18:17:57 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id UAA24793; Wed, 14 Apr 1999 20:15:35 -0500 (CDT) Date: Wed, 14 Apr 1999 20:15:35 -0500 From: "Matthew D. Fuller" To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: swap-related problems Message-ID: <19990414201535.F21807@futuresouth.com> References: <55586E7391ACD211B9730000C11002761795EB@r-lmh-wi-100.corpnet.at> <199904141712.NAA95762@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199904141712.NAA95762@misha.cisco.com>; from Mikhail Teterin on Wed, Apr 14, 1999 at 01:12:00PM -0400 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 14, 1999 at 01:12:00PM -0400, a little birdie told me that Mikhail Teterin remarked > > Aha, now its clearer. May be, since we are do not conform anyway, > we can design some clever way of notifying a program rather then > SIGKILL-ing it? > > Perhaps, SIGBUS? Something, a program can catch, if it is prepared > to, and, may be, do some syscall to find out which chunk of memory > can not actually be used by it... I think you're missing a point here. (Or maybe I am, I don't know that much about it myself). The program that gets killed is NOT necessarily the program that tried to access something causing a memory overcommit; rather, the program that gets killed is the largest program around. Often, they'll probably coincide, but by no means necessarily. You'd also have to rely on somebody not writing a program that, inside the SIGBUS handler, allocates and touches more memory, causing a SIGBUS, causing more allocation, etc etc etc. Lets try not opening any more DoSen than there already are, 'K? --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 18:29:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 1749F14BEF for ; Wed, 14 Apr 1999 18:29:38 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA83861; Wed, 14 Apr 1999 21:23:39 -0400 (EDT) Date: Wed, 14 Apr 1999 21:23:39 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Poul-Henning Kamp Cc: alk@pobox.com, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <1892.924120059@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Poul-Henning Kamp wrote: > In message <14100.61923.427423.153188@avalon.east>, Anthony Kimball writes: > > > >: > All I want is that a program gets NULL from malloc if there is no memory > >: > available. I find that to be a very fundamental thing about malloc. > > > >: Do you have a solution? We don't. > > > >Make an sbrk variant which will pre-allocate backing store. > >setenv MALLOC_PREALLOCATE > > > >Not so hard. > > 1. Demonstrate the need. I'm not doing this, damnit ;) > > 2. Implement it Add another character to the malloc options there already. When something is allocated, touch the first char to be '\0'. Implementation done. > > 3. Send patches. Part of 2. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 18:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id E7FB214BEF for ; Wed, 14 Apr 1999 18:30:34 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (jbloom.ne.mediaone.net [24.128.100.196]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA04575; Wed, 14 Apr 1999 21:28:12 -0400 (EDT) Message-ID: <371540AA.BA9AED2A@acm.org> Date: Wed, 14 Apr 1999 21:28:10 -0400 From: Jim Bloom X-Mailer: Mozilla 4.51 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: <199904142340.TAA96857@misha.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A signal handler is not guaranteed to work. It must be written such that it does not require a new page of memory. Some possible problems here are the stack growing, writing on a new page in the data segment, etc. I'm not familiar enough with the VM system, but if you couldn't create a new swap page for a process, what would guarantee that the signal handler could get the pages it needs. Jim Bloom bloom@acm.org Mikhail Teterin wrote: > > If we are up to discussing the possible implementations, I'd suggest > that the system uses something other then SIGKILL to notify the > program it's time to pay for the over-commit speed and convenience. > I think, SIGBUS is appropriate, but I'm not sure. > > Anything a program can _catch_ and react upon, if its author chooses > to. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 18:30:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C18B015350 for ; Wed, 14 Apr 1999 18:30:51 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA83880; Wed, 14 Apr 1999 21:25:24 -0400 (EDT) Date: Wed, 14 Apr 1999 21:25:23 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Anthony Kimball Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <14100.62842.127882.239452@avalon.east> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Apr 1999, Anthony Kimball wrote: > Quoth Poul-Henning Kamp on Wed, 14 April: > : > : 1. Demonstrate the need. > > Well, it's only needed if you want to be able to reliably execute ANSI > C code according to spec. I personally don't care. I'd be surprised > if core didn't though. I would suspect that it would be deemed worthy > of someone's p2 queue, at least. ACTUALLY it would still break ANSI because the malloc itself would crash the program, instead of touching the memory manually. > > : 2. Implement it > : > : 3. Send patches. > > And I certainly don't care enough to do that!-) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 19: 3:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7597415187 for ; Wed, 14 Apr 1999 19:03:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA12884; Wed, 14 Apr 1999 18:58:22 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Brian Feldman Cc: Poul-Henning Kamp , alk@pobox.com, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: swap-related problems In-reply-to: Your message of "Wed, 14 Apr 1999 21:23:39 EDT." Date: Wed, 14 Apr 1999 18:58:22 -0700 Message-ID: <12882.924141502@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not doing this, damnit ;) Then can we end this stupid thread already? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 19:17:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1729314C4F for ; Wed, 14 Apr 1999 19:17:03 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40366>; Thu, 15 Apr 1999 12:01:10 +1000 Date: Thu, 15 Apr 1999 12:14:23 +1000 From: Peter Jeremy Subject: Re: swap-related problems To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Message-Id: <99Apr15.120110est.40366@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > Worse then that, >it may be possible to use it at malloc time, but unless your program >runs and touches every page, the memory may not be available later. If you run and touch every page, you are guaranteed to have the memory available, but you also increase the chances of you being the largest process when the system runs out of swap - in which case you get killed. >If we are up to discussing the possible implementations, I'd suggest >that the system uses something other then SIGKILL to notify the >program it's time to pay for the over-commit speed and convenience. >I think, SIGBUS is appropriate, but I'm not sure. I'm not sure this will gain a great deal. Currently, if the kernel runs out of swap, it kills the largest runnable process. For your proposal to work, it would need to kill the process that is requesting the space. This raises a number of issues: 1) The problem is detected in vm_pageout_scan(). There's no obvious (to me anyway) way to locate the process that is triggering the space request. 2) The current approach kills the process hogging the greatest amount of memory. This minimises the likelihood that you'll run out of swap again, quickly. 3) The process that triggered the request could potentially be in a non-runnable state. In this case, the signal would be lost (or indefinitely delayed). 4) Since you're proposing a trap-able signal, the process may chose to ignore it and attempt to continue on. 5) The process would require additional stack space to process the signal (the signal handler frame and space for system calls to free memory as a minimum). The last three issues could result in system deadlock. > That our >malloc does not conform to standards (for whatever reasons), The problem is the system, rather than malloc. I'm not sure that the ANSI C standard forbids the current system behaviour. The behaviour is quite common, so I'm sure it's not forbidden by POSIX or various other Unix specs. >that something should be done about it. This is a commonly used phrase around here. Basically, you have 3 choices: 1) Fix the problem yourself (ie submit patches that fix the problem) 2) Convince someone else that the problem is critical enough for them to fix it for you. 3) Pay someone to fix it for you (this is an extension of the previous item). > That "something" must start >with documenting the flaw... Feel free to write a PR. Including the changes you want to the documentation (in text format if you don't want to write a patch to the man page) increases the chances of the changes getting done. Having said all that, I agree that it would be useful if FreeBSD had a knob to disable overcommit - either on a system-wide, or per-process basis. I don't feel sufficiently strongly about it to actually do something about it. (From a quick look at the current code in vm_pageout_scan(), it would be fairly easy to add a per-process flag to prevent the process being a candidate for killing. ptrace(2) or setrlimit(2) seem the most obvious ways to control the flag. This would seem to allieviate the most common problem - one or two large, critical processes (eg the Xserver) getting killed, but probably has some nasty downside that I've overlooked). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 19:38: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id 060AD14D15 for ; Wed, 14 Apr 1999 19:38:03 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id VAA26554; Wed, 14 Apr 1999 21:34:59 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 14 Apr 1999 21:34:59 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: green@unixhelp.org Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: <14100.62842.127882.239452@avalon.east> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14101.20360.243064.404053@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Brian Feldman on Wed, 14 April: : : ACTUALLY it would still break ANSI because the malloc itself would crash : the program, instead of touching the memory manually. The point here is that malloc can return null when it fails to allocate. I might mention that Andrew Reilly's suggestion is the winner so far, in my mind. The solution of having libc:malloc honor a 'setenv MALLOC_MMAP_STORE /path/here' would work with shrink-wrap software, and completely bypass the concerns, real and imagined, of even the most zealous advocate of overcommit purity. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 20:14:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 559AA14D09 for ; Wed, 14 Apr 1999 20:14:45 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA38227; Wed, 14 Apr 1999 20:12:16 -0700 (PDT) (envelope-from dillon) Date: Wed, 14 Apr 1999 20:12:16 -0700 (PDT) From: Matthew Dillon Message-Id: <199904150312.UAA38227@apollo.backplane.com> To: Wilko Bulte Cc: rb@gid.co.uk (Bob Bishop), current@FreeBSD.ORG Subject: experimental patch avail (was Re: NFS, blocks of NULLs in files) References: <199904142054.WAA02242@yedi.iaf.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG WARNING!!!! --------------------------------- WARNING!!!! WARNING!!!! --------------------------------- WARNING!!!! WARNING!!!! --------------------------------- WARNING!!!! Do not use this patch unless you are willing to lose whole filesystems! WARNING!!!! --------------------------------- WARNING!!!! WARNING!!!! --------------------------------- WARNING!!!! WARNING!!!! --------------------------------- WARNING!!!! This patch is currently under test. To use it, undo any previously patches you have made and then apply. http://www.backplane.com/FreeBSD4/ The patch is rather complex. It rips out much of the piecemeal ranging code in the VFS/BIO system that had previously been added to support piecemeal reads and writes. Why? Because the crap doesn't work. We will eventually fix it all ( with a scheme that doesn't require hooks in all the VFS/BIO routines! ). For now, though, the idea is to first make NFS work properly. We will worry about optimizing it later. Since this patch modifies code that effects UFS as well as NFS, please please please do *not* run it on any machine containing data critical to you. As I said, this patch has not been tested a huge amount yet, so there are probably still bugs. It passed all my preliminary tests ( that check for various known NFS bugs ), and I was able to build the kernel. I'm building the world right now. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 21:22: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 6C55315016 for ; Wed, 14 Apr 1999 21:22:03 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA21539; Thu, 15 Apr 1999 14:19:35 +1000 Date: Thu, 15 Apr 1999 14:19:35 +1000 From: Bruce Evans Message-Id: <199904150419.OAA21539@godzilla.zeta.org.au> To: imp@harmony.village.org, Jos.Backus@nl.origin-it.com Subject: Re: /usr/src/UPDATING question Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >: If it's true that cc -aout is broken (.section in an a.out .o file? Hm.), how >: can one rebuild things like XFree86 a.out libraries, when make world fails? > >What it means is that cc -aout has been broken since the conversion to >egcs, and now it is supposedly working. Known breakage includes: * compiling with -g sometimes fails (sees to be a gas bug). * the bug just found by Joe (compiling libgcc_r produces .gnu_linkonce... sections). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 21:24:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 9A5C615016 for ; Wed, 14 Apr 1999 21:24:41 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 10XdfU-000A1H-00; Thu, 15 Apr 1999 00:22:24 -0400 To: Thomas Schuerger Cc: mi@aldan.algebra.com, jdp@polstra.com, current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: cvsup In-reply-to: Your message of "Tue, 13 Apr 1999 21:23:30 +0200." <199904131923.VAA21668@wurzelausix.cs.uni-sb.de> Date: Thu, 15 Apr 1999 00:22:23 -0400 Message-ID: <38518.924150143@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Schuerger wrote in message ID <199904131923.VAA21668@wurzelausix.cs.uni-sb.de>: > cvsup is mostly based on disk (and network) I/O, so there shouldn't > be a problem with properly updating the GUI. Someone said it is > done in a separate process, so I still wonder why the GUI is updated > so slowly on my PII/450. My bet is that when cvsup blocks on network or disk i/o, the process is blocked (since we don't have kernel support for thread scheduling), so the display update gets blocked as well... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 21:35:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7924514D01 for ; Wed, 14 Apr 1999 21:35:06 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA44290; Wed, 14 Apr 1999 22:32:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA07661; Wed, 14 Apr 1999 22:32:26 -0600 (MDT) Message-Id: <199904150432.WAA07661@harmony.village.org> To: mi@aldan.algebra.com Subject: Re: swap-related problems Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 14 Apr 1999 19:40:07 EDT." <199904142340.TAA96857@misha.cisco.com> References: <199904142340.TAA96857@misha.cisco.com> Date: Wed, 14 Apr 1999 22:32:26 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904142340.TAA96857@misha.cisco.com> Mikhail Teterin writes: : Then, one can write a safe malloc, which will install the signal : handler, and touch every page in the the memory referenced by the : to-be-returned pointer. If the signal handler is invoked in the : progress, the to-be-returned memory must be returned back to the : system and NULL should be returned to the caller. This won't work all the time. FreeBSD overcommits swap space and you may get a SIGKILL even if you've touched all the pages. FreeBSD kills processes when swap space runs out. : However, my (in)ability to propose anything remotely sensible does : not change the facts established in this painful thread. That our : malloc does not conform to standards (for whatever reasons), and : that something should be done about it. That "something" must start : with documenting the flaw... The behavior is documented: The malloc() and calloc() functions return a pointer to the allocated memory if successful; otherwise a NULL pointer is returned. What the system does when it has resource shortages is beyond the scope of the ANSI-C standard, so I don't see why you say that FreeBSD's malloc isn't standard conforming. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 21:42: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 47CAB14BE2 for ; Wed, 14 Apr 1999 21:42:05 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id AAA28222 for current@freebsd.org; Thu, 15 Apr 1999 00:39:25 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904150439.AAA28222@kot.ne.mediaone.net> Subject: Re: swap-related problems In-Reply-To: <199904150432.WAA07661@harmony.village.org> from Warner Losh at "Apr 14, 1999 10:32:26 pm" To: imp@harmony.village.org (Warner Losh) Date: Thu, 15 Apr 1999 00:38:21 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Wed, 14 Apr 1999 22:06:40 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id OAA08808; Thu, 15 Apr 1999 14:04:13 +0900 (JST) Message-ID: <371572E4.D9C64C93@newsguy.com> Date: Thu, 15 Apr 1999 14:02:28 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: alk@pobox.com Cc: current@freebsd.org Subject: Re: swap-related problems References: <14100.61923.427423.153188@avalon.east> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anthony Kimball wrote: > > : > All I want is that a program gets NULL from malloc if there is no memory > : > available. I find that to be a very fundamental thing about malloc. > > : Do you have a solution? We don't. > > Make an sbrk variant which will pre-allocate backing store. > setenv MALLOC_PREALLOCATE As soon as this application grabs all the memory, the next thing to request more memory (not a malloc!) will cause the application to be killed (largest application criteria). Change the criteria, and *another* application gets killed. Any application getting killed is a problem, you'll find very fast. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 14 22:43:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (news.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 07631151F0 for ; Wed, 14 Apr 1999 22:43:49 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40349>; Thu, 15 Apr 1999 15:27:57 +1000 Date: Thu, 15 Apr 1999 15:41:15 +1000 From: Peter Jeremy Subject: Re: swap-related problems To: mi@kot.ne.mediaone.net Cc: current@FreeBSD.ORG Message-Id: <99Apr15.152757est.40349@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: >That's my point! I advocate the use of some _other_ signal. Something >catchable. As soon as you allow a catchable signal, you create a potential deadlock situation. See my previous mail. >In case of "resource shortage" the malloc should be unsuccessful >and return NULL. This requires a change to the kernel to disable swap over-commit. malloc is behaving correctly: it calls brk/sbrk to request additional memory. The kernel verifies that the process hasn't exceeded its resource limits and the brk returns success. > Instead, right now you may still get a non-NULL >pointer, but get a SIGKILL when you try to use the rightfully >allocated memory. Actually the biggest process gets SIGKILL. This probably isn't the process that requested the memory. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 0: 7:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 81D1014C83 for ; Thu, 15 Apr 1999 00:07:21 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA06774; Thu, 15 Apr 1999 17:04:58 +1000 Date: Thu, 15 Apr 1999 17:04:58 +1000 From: Bruce Evans Message-Id: <199904150704.RAA06774@godzilla.zeta.org.au> To: green@unixhelp.org, phk@critter.freebsd.dk Subject: Re: swap-related problems Cc: current@FreeBSD.ORG, mi@kot.ne.mediaone.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Sorry FreeBSD doesn't support resource reservation for memory. > >mlock()? BTW, why can't anyone explain why the old behavior WAS THAT >the process would get NULL? Now it's this... Implementation quirks (bugs) and races. brk(2) used to fail when memory (real+swap) is running short, instead of waiting for the pagers to free some memory (it may be possible to free almost as much memory as there is real memory, e.g., by forgetting that pages backed by vnodes are in core). This tended to cause innocent processes to exit when malloc() failed. However, in simple tests where only one memory hog process is calling malloc(), it only affects the guilty process. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 1:52:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5E4D814D07 for ; Thu, 15 Apr 1999 01:52:42 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA05412; Thu, 15 Apr 1999 17:50:17 +0900 (JST) Message-ID: <37159AA4.8F513E83@newsguy.com> Date: Thu, 15 Apr 1999 16:52:04 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: alk@pobox.com, current@freebsd.org Subject: Re: swap-related problems References: <14100.61923.427423.153188@avalon.east> <371572E4.D9C64C93@newsguy.com> <14101.33255.671010.718409@avalon.east> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anthony Kimball wrote: > > Quoth Daniel C. Sobral on Thu, 15 April: > : > : As soon as this application grabs all the memory, the next thing to > : request more memory (not a malloc!) will cause the application to be > : killed (largest application criteria). Change the criteria, and > : *another* application gets killed. Any application getting killed is > : a problem, you'll find very fast. > > Let's not try to solve the unsolvable problem, just the solvable part. If > you can't tolerate anything getting killed, you can't use an > overcommit system, or you must control allocation by manual policy. What would you have killed? Why not run it in first place? Well, if you did not run it, it's memory would be taken by the memory-grabber process, and something else would get killed. So, you need something killable running just so the memory-grabber will stop at some point where there is still enough memory free to do the minimum management necessary (things like cron, inetd -- forget about X), *after* the killable processes get killed. Does that sound like taking too many turns? It is. You would have to measure how much you need, and then have a set of processes just for the sake of getting killed. So, let me asking to consider something. Why not setting a datasize memory limit for the memory-grabbing process instead? Set it to almost all memory, leaving just enough for minimum usability. Well, surprisingly (not!), FreeBSD supports that. In other words, FreeBSD already has a real, working solution. It's just that it seems not to sink in the head of some people that what they are asking for doesn't work(*), and what they have been discarding as a solution does work. (*) Yeah, a full pre-allocate solution would work too. I just don't see a point in using that solution since the memory-grabbing program would have a lot less memory to grab. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 1:57:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 466A914EA6 for ; Thu, 15 Apr 1999 01:57:57 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA05470; Thu, 15 Apr 1999 17:50:41 +0900 (JST) Message-ID: <3715A168.B193834E@newsguy.com> Date: Thu, 15 Apr 1999 17:20:56 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: alk@pobox.com Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: swap-related problems References: <14100.61923.427423.153188@avalon.east> <1892.924120059@critter.freebsd.dk> <14100.62842.127882.239452@avalon.east> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anthony Kimball wrote: > > Quoth Poul-Henning Kamp on Wed, 14 April: > : > : 1. Demonstrate the need. > > Well, it's only needed if you want to be able to reliably execute ANSI > C code according to spec. I personally don't care. I'd be surprised > if core didn't though. I would suspect that it would be deemed worthy > of someone's p2 queue, at least. FreeBSD executes ANSI C code reliably according to spec, as long as there is enough memory in the system. If there isn't, FreeBSD doesn't run reliably, much less executes any kind of code reliably. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 1:58:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id F316D14D0E for ; Thu, 15 Apr 1999 01:58:06 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA05481; Thu, 15 Apr 1999 17:50:44 +0900 (JST) Message-ID: <3715A2A0.D7EEE69D@newsguy.com> Date: Thu, 15 Apr 1999 17:26:08 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Brian Feldman Cc: Poul-Henning Kamp , Mikhail Teterin , current@FreeBSD.ORG Subject: Re: swap-related problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > > mlock()? BTW, why can't anyone explain why the old behavior WAS THAT > the process would get NULL? Now it's this... Maybe the login class was changed, and now has no limits, or a high enough limit that the resources are exhausted. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 2:32:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id AAA10158B4 for ; Thu, 15 Apr 1999 02:32:16 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id KAA09614; Thu, 15 Apr 1999 10:28:41 +0100 (BST) (envelope-from rb) Message-Id: <3.0.6.32.19990415102613.00819aa0@192.168.255.1> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 15 Apr 1999 10:26:13 +0100 To: Matthew Dillon From: Bob Bishop Subject: Re: experimental patch avail (was Re: NFS, blocks of NULLs in files) Cc: Wilko Bulte , current@FreeBSD.ORG In-Reply-To: <199904150312.UAA38227@apollo.backplane.com> References: <199904142054.WAA02242@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 20:12 14/04/99 -0700, Matthew Dillon wrote: >[dire warning] > This patch is currently under test. To use it, undo any previously patches [etc] OK, I'll try it out this evening (BST). Does this patch affect client side behaviour, server side or both (ie how many machines do I have to back up? :-) -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 3: 1: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id D551415860 for ; Thu, 15 Apr 1999 03:00:56 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id LAA26031 for ; Thu, 15 Apr 1999 11:58:34 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma026022; Thu, 15 Apr 99 11:58:34 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id LAA21899 for ; Thu, 15 Apr 1999 11:58:06 +0200 (MET DST) Received: (qmail 63039 invoked by uid 666); 15 Apr 1999 09:51:45 -0000 Date: Thu, 15 Apr 1999 11:51:45 +0200 From: Jos Backus To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: /usr/src/UPDATING question Message-ID: <19990415115145.B59089@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990414234749.A42258@hal.mpn.cp.philips.com> <19990414173737.A58389@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990414173737.A58389@nuxi.com>; from David O'Brien on Wed, Apr 14, 1999 at 05:37:37PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 14, 1999 at 05:37:37PM -0700, David O'Brien wrote: > Some have gotten -aout to work. When was your last CVSup and non-a.out > `make world' ? Yesterday around 9pm MEST. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 4:43: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 5C32F14D1F for ; Thu, 15 Apr 1999 04:42:58 -0700 (PDT) (envelope-from fanf@demon.net) Received: by noc.demon.net; id MAA28152; Thu, 15 Apr 1999 12:40:36 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma028052; Thu, 15 Apr 99 12:40:18 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10XkVE-0004kz-00; Thu, 15 Apr 1999 12:40:16 +0100 To: current@freebsd.org From: Tony Finch Subject: Re: swap-related problems In-Reply-To: <371540AA.BA9AED2A@acm.org> References: <199904142340.TAA96857@misha.cisco.com> Message-Id: Date: Thu, 15 Apr 1999 12:40:16 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bloom wrote: > >A signal handler is not guaranteed to work. It must be written such that it >does not require a new page of memory. Some possible problems here are the >stack growing, writing on a new page in the data segment, etc. man sigaltstack Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Arthur: "Oh, that sounds better, have you worked out the controls?" Ford: "No, we just stopped playing with them." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 8:26:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5DD9514F1A for ; Thu, 15 Apr 1999 08:26:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA44754; Thu, 15 Apr 1999 08:23:30 -0700 (PDT) (envelope-from dillon) Date: Thu, 15 Apr 1999 08:23:30 -0700 (PDT) From: Matthew Dillon Message-Id: <199904151523.IAA44754@apollo.backplane.com> To: Bob Bishop Cc: Wilko Bulte , current@FreeBSD.ORG Subject: Re: experimental patch avail (was Re: NFS, blocks of NULLs in files) References: <199904142054.WAA02242@yedi.iaf.nl> <3.0.6.32.19990415102613.00819aa0@192.168.255.1> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :At 20:12 14/04/99 -0700, Matthew Dillon wrote: :>[dire warning] :> This patch is currently under test. To use it, undo any previously :patches :[etc] : :OK, I'll try it out this evening (BST). Does this patch affect client side :behaviour, server side or both (ie how many machines do I have to back up? ::-) : :-- :Bob Bishop +44 118 977 4017 :rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) The client code is the most heavily effected, but since it digs into the internals of VFS/BIO, the patch will effect the entire kernel so it should only be run on boxes you can afford to lose for the moment. I'll have something better on the weekend. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 10:25:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id 2473714EB7 for ; Thu, 15 Apr 1999 10:25:48 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id MAA30026; Thu, 15 Apr 1999 12:22:33 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 15 Apr 1999 12:22:33 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: dcs@newsguy.com Cc: current@FreeBSD.ORG Subject: Re: swap-related problems References: <14100.61923.427423.153188@avalon.east> <1892.924120059@critter.freebsd.dk> <14100.62842.127882.239452@avalon.east> <3715A168.B193834E@newsguy.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14102.8184.91918.375800@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Daniel C. Sobral on Thu, 15 April: : : FreeBSD executes ANSI C code reliably according to spec, as long as : there is enough memory in the system. If there isn't, FreeBSD : doesn't run reliably, much less executes any kind of code reliably. : I understand this. I concieve the purpose of this thread as being a clear determination of the best known way to allow correctly written code to run reliably when, for reasons perhaps out of the control of the application, memory becomes overcommitted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 10:35:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 691B614FDF for ; Thu, 15 Apr 1999 10:35:45 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA47447; Thu, 15 Apr 1999 10:33:16 -0700 (PDT) (envelope-from dillon) Date: Thu, 15 Apr 1999 10:33:16 -0700 (PDT) From: Matthew Dillon Message-Id: <199904151733.KAA47447@apollo.backplane.com> To: Anthony Kimball Cc: dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: swap-related problems References: <14100.61923.427423.153188@avalon.east> <1892.924120059@critter.freebsd.dk> <14100.62842.127882.239452@avalon.east> <3715A168.B193834E@newsguy.com> <14102.8184.91918.375800@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ( Sitting in the bleachers ) Ra! Ra! Ra! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 10:46:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id B89E814C48 for ; Thu, 15 Apr 1999 10:46:36 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id NAA98408 for current@freebsd.org; Thu, 15 Apr 1999 13:44:10 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904151744.NAA98408@misha.cisco.com> Subject: swap on Irix (overcommiting, etc.) To: current@freebsd.org Date: Thu, 15 Apr 1999 13:44:10 -0400 (EDT) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Irix, each swap area has the following parameter (from swap(1M)): vswap The size the system believes the area can hold. This is always greater than or equal to pswap and maxswap. This way, an administrator can control the amount of overcommited memory (making it 0 if neccessary). It may be sufficient to have this as a centralized parameter, rather then a per swap area. They also have priorities of the swap areas (only swap here when areas with higher priorities are full), and an ability to stop paging onto a particular area. Mmmm... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 10:47: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles506.castles.com [208.214.165.70]) by hub.freebsd.org (Postfix) with ESMTP id A70D514C35 for ; Thu, 15 Apr 1999 10:46:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA02998; Thu, 15 Apr 1999 10:43:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904151743.KAA02998@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tony Finch Cc: current@freebsd.org Subject: Re: swap-related problems In-reply-to: Your message of "Thu, 15 Apr 1999 12:40:16 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Apr 1999 10:43:55 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jim Bloom wrote: > > > >A signal handler is not guaranteed to work. It must be written such that it > >does not require a new page of memory. Some possible problems here are the > >stack growing, writing on a new page in the data segment, etc. > > man sigaltstack That doesn't help; there is no guarantee that your stack or your alternate stack have been mapped. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 11: 3:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [195.224.76.132]) by hub.freebsd.org (Postfix) with ESMTP id EF4F114C35 for ; Thu, 15 Apr 1999 11:03:19 -0700 (PDT) (envelope-from fanf@chiark.greenend.org.uk) Received: from fanf by chiark.greenend.org.uk with local (Exim 2.02 #1) id 10XqRQ-0000e5-00 (Debian); Thu, 15 Apr 1999 19:00:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14102.10572.480321.581664@chiark.greenend.org.uk> Date: Thu, 15 Apr 1999 19:00:44 +0100 (BST) From: Tony Finch To: Mike Smith Cc: current@freebsd.org Subject: Re: swap-related problems In-Reply-To: <199904151743.KAA02998@dingo.cdrom.com> References: <199904151743.KAA02998@dingo.cdrom.com> X-Mailer: VM 6.47 under Emacs 19.34.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > Jim Bloom wrote: > > > > > >A signal handler is not guaranteed to work. It must be written such that it > > >does not require a new page of memory. Some possible problems here are the > > >stack growing, writing on a new page in the data segment, etc. > > > > man sigaltstack > > That doesn't help; there is no guarantee that your stack or your > alternate stack have been mapped. I assumed that the alternate stack had been forcibly allocated by touching the pages; I suppose things go pear-shaped if they have been swapped out and there's no space to swap out other pages so that the stack can be swapped in. Bummer. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 11:12:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id BDE6E1525E for ; Thu, 15 Apr 1999 11:12:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA47676; Thu, 15 Apr 1999 11:08:52 -0700 (PDT) (envelope-from dillon) Date: Thu, 15 Apr 1999 11:08:52 -0700 (PDT) From: Matthew Dillon Message-Id: <199904151808.LAA47676@apollo.backplane.com> To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: swap on Irix (overcommiting, etc.) References: <199904151744.NAA98408@misha.cisco.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Irix, each swap area has the following parameter (from swap(1M)): : : vswap The size the system believes the area can hold. This is : always greater than or equal to pswap and maxswap. : :This way, an administrator can control the amount of overcommited :memory (making it 0 if neccessary). It may be sufficient to have :this as a centralized parameter, rather then a per swap area. : :They also have priorities of the swap areas (only swap here when :areas with higher priorities are full), and an ability to stop :paging onto a particular area. Mmmm... : : -mi I think they finally got rid of vswap in later IRIX's after they fixed the core swapping code to 'overcommit'. The reality behind the virtual swap concept w/ IRIX is based on issues with the original SysV VM system. IRIX wanted to assign swap to everything, whether it needed it or not. For example, each instance of a MAP_PRIVATE map would get swap backing store assigned to it whether it needed it or not. In fact, I think even MAP_SHARED maps reserved swap under older IRIX systems. Again, fixed in newer systems. Requiring swap pre-allocation to avoid overcommits may sound like a nice idea, but it doesn't work in practice. Before IRIX's vswap came along, system administrators had to assign 10 times the amount of swap as a system actually needed to operate. On a modern system with 256MB of ram, that would come to over 2 Gigabytes of swap with the worst-case actual utilization sitting at around 200 MBytes of swap. It's A total waste of disk space. Not only that, but any system that actually had to use that much swap would pile drive right into the ground performance-wise... you would lose anyway, even if you could guarentee that no swap overcommit could occur. FreeBSD does it right - it only allocates swap when it needs to swap something out of main memory. The total available VM is essentially the amount of main memory plus the amount of swap ( non-inclusive of mmap()'d files which do not take any swap at all ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 11:26:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id E230715275 for ; Thu, 15 Apr 1999 11:26:04 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id OAA98506; Thu, 15 Apr 1999 14:22:57 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904151822.OAA98506@misha.cisco.com> Subject: Re: swap-related problems In-Reply-To: <199904151743.KAA02998@dingo.cdrom.com> from Mike Smith at "Apr 15, 1999 10:43:55 am" To: mike@smith.net.au (Mike Smith) Date: Thu, 15 Apr 1999 14:22:56 -0400 (EDT) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith once wrote: > > >A signal handler is not guaranteed to work. It must be written > > >such that it does not require a new page of memory. Some possible > > >problems here are the stack growing, writing on a new page in the > > >data segment, etc. > > > > man sigaltstack > That doesn't help; there is no guarantee that your stack or your > alternate stack have been mapped. Can I ensure the room availability for the signal handler by explicitly calling it once, _before_ doing the dangerous operation of touching every page of the freshly allocated memory? The thing itself (in the case of earlier described `safe malloc') will only change a value of a static variable and return, indicating to the malloc it should: . stop the touching . give the memory back to system . return NULL to the caller. This assumes, of course, that it is the process doing the malloc that is sent the signal, AND, that the signal is catchable. The kernel can try to remember the processes the signal went to, and send it a SIGKILL if it happens again withing a certain time -- to avoid the deadlock. Pretty horrible? Feasible? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 11:41:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 4F6F315275 for ; Thu, 15 Apr 1999 11:41:33 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id OAA98565; Thu, 15 Apr 1999 14:38:37 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904151838.OAA98565@misha.cisco.com> Subject: Re: swap on Irix (overcommiting, etc.) In-Reply-To: <199904151808.LAA47676@apollo.backplane.com> from Matthew Dillon at "Apr 15, 1999 11:08:52 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 15 Apr 1999 14:38:37 -0400 (EDT) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon once wrote: > :On Irix, each swap area has the following parameter (from swap(1M)): > : > : vswap The size the system believes the area can hold. This is > : always greater than or equal to pswap and maxswap. > : > :This way, an administrator can control the amount of overcommited > :memory (making it 0 if neccessary). It may be sufficient to have this > :as a centralized parameter, rather then a per swap area. > I think they finally got rid of vswap in later IRIX's after they > fixed the core swapping code to 'overcommit'. The reality behind > the virtual swap concept w/ IRIX is based on issues with the original [...] Mmm, that's how they use(d) it then... But can we have a way for an admin to control the amount of overcommited memory? Ranging from 0 -- no overcommitment to the entire addressable space less the phisical storage (the current situation)... And this is different from the per-user class limit. I guess, I'd settle for being able to specify the per-user class: . datasize limit in percents of the total available RAM+swap . kill-order, so the kernel will start killing with the least important users (and services running in their own sandboxes) Does not fix the non-compliance with ANSI, strictly speaking... > FreeBSD does it right - it only allocates swap when it needs to > swap something out of main memory. The total available VM is > essentially the amount of main memory plus the amount of swap > (non-inclusive of mmap()'d files which do not take any swap at > all). FreeBSD is perfect for my existing needs... > :They also have priorities of the swap areas (only swap here when > :areas with higher priorities are full), and an ability to stop > :paging onto a particular area. Mmmm... What about this two? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 11:49:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 96A2015275 for ; Thu, 15 Apr 1999 11:49:29 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA61243; Thu, 15 Apr 1999 14:44:46 -0400 (EDT) Date: Thu, 15 Apr 1999 14:44:46 -0400 (EDT) From: Chuck Robey To: mi@aldan.algebra.com Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: swap on Irix (overcommiting, etc.) In-Reply-To: <199904151838.OAA98565@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Apr 1999, Mikhail Teterin wrote: > > I think they finally got rid of vswap in later IRIX's after they > > fixed the core swapping code to 'overcommit'. The reality behind > > the virtual swap concept w/ IRIX is based on issues with the original > [...] > > Mmm, that's how they use(d) it then... But can we have a way for an > admin to control the amount of overcommited memory? Ranging from 0 -- no > overcommitment to the entire addressable space less the phisical storage > (the current situation)... And this is different from the per-user class > limit. > > I guess, I'd settle for being able to specify the per-user class: > > . datasize limit in percents of the total available RAM+swap > . kill-order, so the kernel will start killing with the least > important users (and services running in their own sandboxes) > > Does not fix the non-compliance with ANSI, strictly speaking... This is the part that gets me. You keep claiming ANSI C non-compliance, and we are compliant. If you want to claim non-compliance, then get out the spec and quote chapter and verse. There is nothing in the spec that says how the underlying OS has to treat processes on a global scale. This hasn't a darn thing to do with ANSI C compliance. If you want to argue that you don't like memory overcommit, that's valid, but claiming the non-compliance is throwing FUD. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 12:37:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 0F29614E26 for ; Thu, 15 Apr 1999 12:37:20 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id PAA98792 for current@freebsd.org; Thu, 15 Apr 1999 15:34:54 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904151934.PAA98792@misha.cisco.com> Subject: Re: swap on Irix (overcommiting, etc.) To: current@freebsd.org Date: Thu, 15 Apr 1999 15:34:54 -0400 (EDT) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey once wrote: > This is the part that gets me. You keep claiming ANSI C > non-compliance, and we are compliant. If you want to claim > non-compliance, then get out the spec and quote chapter and verse. > There is nothing in the spec that says how the underlying OS has to > treat processes on a global scale. Sorry. I'm just repeating what Ladavac Marino wrote in <55586E7391ACD211B9730000C11002761795EB@r-lmh-wi-100.corpnet.at>: LM: Please note that memory overcommit architectures are a LM: rather common optimization; FreeBSD is one of them. They LM: do, however, break the ISO/ANSI C conformance (strictly LM: speaking). Since there was no immediate (nor later) rebuttal, I assumed, that everyone quietly agreed... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 12:41:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C061C14E6E for ; Thu, 15 Apr 1999 12:41:42 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA48113; Thu, 15 Apr 1999 12:38:06 -0700 (PDT) (envelope-from dillon) Date: Thu, 15 Apr 1999 12:38:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199904151938.MAA48113@apollo.backplane.com> To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: swap on Irix (overcommiting, etc.) References: <199904151838.OAA98565@misha.cisco.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Mmm, that's how they use(d) it then... But can we have a way for an :admin to control the amount of overcommited memory? Ranging from 0 -- no :overcommitment to the entire addressable space less the phisical storage :(the current situation)... And this is different from the per-user class :limit. I think the people who keep on rooting about this 'overcommit' thing don't really understand the complexity of VM management or the total absurdity of the 'overcommit' argument. The OS *CANNOT* tell how much actual memory a process is going to use. This concept of 'overcommit' does not work in reality ... if you calculate the absolute worst-case swap required for a set of processes, the resulting number is INSANE. I will repeat that: It is an INSANE number. It is so insane that it is completely unuseable for any sort of measurement, much less any sort of requirement. Here are some simple examples: A process allocates and touches 100MB of memory. Ok, so there you have a process taking up 100MB of swappable memory. Now the process forks. Now it forks 10 times. How much real memory do these 10 processes need? The aggregate could be anything from 100MB ( all shared ) to 1GB ( all the children write to all their memory, forcing a copy-on-write for all theiir pages ). The OS can't tell in advance. This does not mean that the program might touch all of that memory... programs tend to have relatively static memory use characteristics. To assume that it might to touch all of the memory in each child is absurd. Example #2: A process mmap()'s a 100MB file MAP_PRIVATE. If the process does not write to any of the associates pages, this 100MB mapping requires *NO* swap and *NO* real memory - it is backed by the original file. If the process touches all of the pages, this mapping eats 100MB of swap+real. Now lets say you have 10 of these processes. To guarentee no overcommit you would need 1GB of swap. The actual amount of swap likely to be allocated by the system is almost certainly going to be less then 10% that figure. In many cases, less then 1% of that figure. Example #3: You run a program. It allocates nothing. How much real+swap does this program require? It could be as little as 16K and as much as the entire Data+BSS area of the program, depending on what it touches. Now combine it all together. To be blunt, the 'total VM' used by a system can run into the gigabytes while the actual real memory + swap allocation is 1/10 of that... or better. It all depends on what you are runing. The real kicker, however, is performance. What use is guarenteeing no overcommit ( and allocating gigabytes of swap space on your disks ) when the machine's performance dies before it uses up even 1/5 of that space? Just because you are guarenteeing sufficient swap doesn't mean that you are guarenteeing that the machine will remain useable. The general rule of thumb, "allocate twice as much swap as real memory", is as much related to the average machine's ability to perform as it is to the amount of swap the machine might actually need. Generally speaking, only a complete idiot focuses on guarenteeing memory without looking at the performance of the machine at the performance degradation that would occur if that much swap were actually used. ( read: machine comes to a nearly complete stop trying to page ). If some of you are wondering why some of us are saying this guarenteeing of memory is a crap argument, it's because it *IS* a crap argument. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 13:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 2E2FC15322 for ; Thu, 15 Apr 1999 13:20:29 -0700 (PDT) (envelope-from camel@avias.com) Received: from CAMEL (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id AAA51401 for ; Fri, 16 Apr 1999 00:18:06 +0400 (MSD) (envelope-from camel@avias.com) Date: Fri, 16 Apr 1999 00:18:13 +0400 From: Ilya Naumov X-Mailer: The Bat! (v1.31) UNREG Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <1512.990416@avias.com> To: Tim Preece Subject: Re[2]: ftp hangs on -current In-reply-To: <19990414072511.A22655@franklin.matlink> References: <19990414072511.A22655@franklin.matlink> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Tim, Wednesday, April 14, 1999, 10:25:11 AM, you wrote: >> I am getting problems similar to those outlined above. I don't run natd, either, but I do >> have a firewall enabled. (open rule) I've had to 'put' files rather than 'get' them, since my >> last build/installworld. (Yesterday's -current source) TP> I am not running any firewall but my last cvsup which is also current was the same day as yours. i'm still experiencing this strange problem too. developers, where are you? :) Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 15:22:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4E35214D93 for ; Thu, 15 Apr 1999 15:22:06 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA48993; Thu, 15 Apr 1999 15:19:45 -0700 (PDT) (envelope-from dillon) Date: Thu, 15 Apr 1999 15:19:45 -0700 (PDT) From: Matthew Dillon Message-Id: <199904152219.PAA48993@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Re: RE: swap-related problems References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a quick note... I've heard 'vfork' and 'fork' mentioned twice now. I think there is some confusion. fork() does not really eat that much memory if all you are doing is fork/exec. The only difference between fork and vfork from a resource point of view is around 32 KBytes of memory and a little extra cpu, and even the memory is recovered when you do the exec. Semantically, they are quite different - vfork is supposed to share the parent process's address space until it exec's whereas fork does not. But FreeBSD's updated VM model, which you can thank John Dyson for mostly, is extremely efficient even when forking whole address spaces. The differences between fork and vfork are also irrelevant in this particular discussion since the fork/exec combination is only in the 'fork' state for a very short time. The moment you exec, the address space is wiped ( except for mmap's MAP_INHERIT, which very few people ever use ). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 16:32:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id D598C14E2D for ; Thu, 15 Apr 1999 16:32:23 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id QAA14291; Thu, 15 Apr 1999 16:29:50 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id QAA03652; Thu, 15 Apr 1999 16:29:49 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA11601; Thu, 15 Apr 1999 16:29:48 -0700 (PDT) From: Don Lewis Message-Id: <199904152329.QAA11601@salsa.gv.tsc.tdk.com> Date: Thu, 15 Apr 1999 16:29:48 -0700 In-Reply-To: Peter Jeremy "Re: swap-related problems" (Apr 15, 12:14pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Peter Jeremy , mi@aldan.algebra.com Subject: Re: swap-related problems Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 15, 12:14pm, Peter Jeremy wrote: } Subject: Re: swap-related problems } Mikhail Teterin wrote: } > Worse then that, } >it may be possible to use it at malloc time, but unless your program } >runs and touches every page, the memory may not be available later. } } If you run and touch every page, you are guaranteed to have the } memory available, but you also increase the chances of you being the } largest process when the system runs out of swap - in which case you } get killed. This could also has a pretty severe runtime performance penalty. An implementation that just reserves space would not. } >If we are up to discussing the possible implementations, I'd suggest } >that the system uses something other then SIGKILL to notify the } >program it's time to pay for the over-commit speed and convenience. } >I think, SIGBUS is appropriate, but I'm not sure. } } I'm not sure this will gain a great deal. Currently, if the kernel } runs out of swap, it kills the largest runnable process. For your } proposal to work, it would need to kill the process that is requesting } the space. This raises a number of issues: } 1) The problem is detected in vm_pageout_scan(). There's no obvious } (to me anyway) way to locate the process that is triggering the } space request. } 2) The current approach kills the process hogging the greatest amount } of memory. This minimises the likelihood that you'll run out of } swap again, quickly. } 3) The process that triggered the request could potentially be in a } non-runnable state. In this case, the signal would be lost (or } indefinitely delayed). } 4) Since you're proposing a trap-able signal, the process may chose } to ignore it and attempt to continue on. } 5) The process would require additional stack space to process the } signal (the signal handler frame and space for system calls to } free memory as a minimum). } } The last three issues could result in system deadlock. Yes. On the other hand, with an implemntation where malloc() returns NULL, a carefully application could log a message and wait for more swap to become available, or checkpoint itself. } Having said all that, I agree that it would be useful if FreeBSD had a } knob to disable overcommit - either on a system-wide, or per-process } basis. I don't feel sufficiently strongly about it to actually do } something about it. (From a quick look at the current code in } vm_pageout_scan(), it would be fairly easy to add a per-process flag } to prevent the process being a candidate for killing. ptrace(2) or } setrlimit(2) seem the most obvious ways to control the flag. This } would seem to allieviate the most common problem - one or two large, } critical processes (eg the Xserver) getting killed, but probably has } some nasty downside that I've overlooked). Like if the Xserver has a memory leak, it will keep growing until most of the other processes on the machine are killed of, maybe even important ones, like the process that manipulates the control rods in the nuclear reactor ;-) Actually, that brings up a good point. It is generally considered bad practice for safety critical programs to use dynamic memory allocation since it is so hard to guarantee that there won't be a memory allocation failure. With memory overcommit, it is possible that a process that doesn't dynamically allocate memory to be killed because a fault could happen when accessing BSS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 16:57:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 98EC314A2F for ; Thu, 15 Apr 1999 16:57:24 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id QAA14648; Thu, 15 Apr 1999 16:49:36 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id QAA03806; Thu, 15 Apr 1999 16:49:35 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA11653; Thu, 15 Apr 1999 16:49:34 -0700 (PDT) From: Don Lewis Message-Id: <199904152349.QAA11653@salsa.gv.tsc.tdk.com> Date: Thu, 15 Apr 1999 16:49:33 -0700 In-Reply-To: Chuck Robey "Re: swap-related problems" (Apr 14, 4:40pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Chuck Robey , Anthony Kimball Subject: Re: swap-related problems Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 14, 4:40pm, Chuck Robey wrote: } Subject: Re: swap-related problems } On Wed, 14 Apr 1999, Anthony Kimball wrote: } > Well, it's only needed if you want to be able to reliably execute ANSI } > C code according to spec. I personally don't care. I'd be surprised } > if core didn't though. I would suspect that it would be deemed worthy } > of someone's p2 queue, at least. } } I can't understand this. Make software that causes a major performance } loss, and loses *bigtime* in memory allocation, just so the one guy to } complain *at all* can not lose sleep over something that has causes no } problems at all with any ANSI code in a properly sized system. SunOS 4 doesn't do memory overcommit. I've been running large processes for years on SunOS 4 machines and haven't noticed any performance problems due to lack of memory overcommit. You just need to configure plenty of swap. I've found the old 3x RAM rule works fine, and it's really cheap these days. This could be shaved down a bit if SunOS didn't require (swap > total VM) instead of (swap + RAM > total VM). If you want to talk about slow, there are those crufty old implementations that don't have COW fork(). If a large process forks, its entire memory space needs to be duplicated, which is *really slow* if the process was too big to fit in RAM to begin with. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 17:47:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id B33A114C36; Thu, 15 Apr 1999 17:47:47 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA29434; Fri, 16 Apr 1999 10:15:23 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA27849; Fri, 16 Apr 1999 10:15:21 +0930 (CST) Message-ID: <19990416101520.A27806@lemis.com> Date: Fri, 16 Apr 1999 10:15:20 +0930 From: Greg Lehey To: mmercer@ipass.net, FreeBSD current users Subject: Re: Kernel panic'd when using mtools command 'mdir'. References: <37167CF3.AEE13EC8@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <37167CF3.AEE13EC8@ipass.net>; from Michael E. Mercer on Thu, Apr 15, 1999 at 07:57:39PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 15 April 1999 at 19:57:39 -0400, Michael E. Mercer wrote: > Hello, > > I just recently installed freebsd 4.0 snap from 19990304. That's FreeBSD-current, and that's where you should report problems. I'm following up there. > I was able to use mtools package here... > > Then I cvsup'd 4.0 current. > made world twice..since egcs is used now... > No problems in compilation... Great... > > However, now I am trying to copy a file from the A drive. > just tried to look at the drive first... > >> mdir > > There is activity for a bit, the light comes on, then nothing.... > > I wait... > > KERNEL PANIC and REBOOT. OK, what are the details? > If I pull the disk out before I get these errors.. > >> mdir > fd0c: hard error reading fsbn 0 (No status) > plain_io: Input/output error > init A: could not read boot sector > Cannot initialize 'A:' That's reasonable. > I then put the same floppy disk in my other computer > running pre-egcs 4.0 current, and it works. > > What's wrong...I will try to send my dmesg output if really > needed...however it will take time..since I have not completely > set the new computer up. You need to look at the dump first. It sounds like you haven't read the fine print. From "The Complete FreeBSD": FreeBSD-CURRENT is the very latest version of FreeBSD, still under development. All new development work is done on this branch of the tree. FreeBSD-CURRENT is an ever-changing snapshot of the working sources for FreeBSD, including work in progress, experimental changes and transitional mechanisms that may or may not be present in the next official release of the software. Many users compile almost daily from FreeBSD-CURRENT sources, but there times when the sources are uncompilable. The problems are always resolved, but others can take their place. On occasion, keeping up with FreeBSD-CURRENT can be a full-time business. If you use -CURRENT, you should be prepared to spend a lot of time keeping the system running. You will run into problems with FreeBSD-CURRENT. When it happens, please first read the mailing list and possibly the mail archives (see http://www.FreeBSD.ORG/search.html for a search engine) and see if the problem has been reported. If it hasn't, try to investigate the problem yourself. Then send mail to FreeBSD-current describing the problem and what you have done to solve it. If you experience a panic, please don't just send a message to FreeBSD-current saying ``My kernel panics when I type foo''. Remember that you're asking somebody to use their spare time to look at the problem. Make it easy for them. Go through this procedure: 1. Update to the absolutely latest sources, unless emails have been warning against this. 2. If you have any local patches, back them out. 3. Recompile, from scratch, your kernel with ddb and with complete symbols (see above). If possible, don't strip your kernel before booting. An unstripped kernel will take up about 8 MB more memory than a stripped one, so this is not possible with very small memory systems. It's still important to build the debug kernel if you do have a small memory. You'll have to strip the version you boot, but you can still use the debug version with gdb to debug a panic dump. 4. Report all details from the panic. At an absolute minimum, give all information from show reg and trace. 5. Try to dump the system. If you don't do at least this, there isn't much chance that a mail message to FreeBSD-current will have much effect. Since writing that, I think it needs updating. You should really dump the system first, and look at the dump. The handbook tells you what to do. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 20:57:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 81AC315022 for ; Thu, 15 Apr 1999 20:57:33 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id XAA05637 for ; Thu, 15 Apr 1999 23:55:10 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA11042; Thu, 15 Apr 1999 23:55:10 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA13170 for freebsd-current@freebsd.org; Thu, 15 Apr 1999 23:55:10 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199904160355.XAA13170@bb01f39.unx.sas.com> Subject: rexec documentation/compatibility question To: freebsd-current@freebsd.org Date: Thu, 15 Apr 1999 23:55:10 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, With respect to the rexec() function: From 'man 3 rexec' on a -current system I find: SYNOPSIS int rexec(char **ahost, int inport, char *user, char *passwd, char *cmd, int *fd2p) DESCRIPTION This interface is obsoleted by rcmd(3). It is available from the compat- ibility library, libcompat. However, I don't see how rcmd() can be used to replace rexec() since rcmd() is a root/rresvport mechanism, as where rexec() is a .netrc mechanism. In looking at the rcmd() src, I don't see where any rexec() functionality has been added (/usr/src/lib/libc/net/rcmd.c). Could someone with information on how these functions relate to each other point me in the right direction? Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 22:20:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (Postfix) with ESMTP id E091114E96 for ; Thu, 15 Apr 1999 22:20:41 -0700 (PDT) (envelope-from bford@uop.cs.uop.edu) Received: from heather (user173.pop2.cwia.com [209.142.32.173]) by uop.cs.uop.edu (8.8.8/8.8.8) with SMTP id WAA09210 for ; Thu, 15 Apr 1999 22:18:17 -0700 (PDT) Message-ID: <001d01be87c8$8971d420$0100a8c0@my.domain> From: "Bret Ford" To: References: <19990414072511.A22655@franklin.matlink> <1512.990416@avias.com> Subject: Re: Re[2]: ftp hangs on -current Date: Thu, 15 Apr 1999 22:18:08 -0700 Organization: University of the Pacific 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.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Wednesday, April 14, 1999, 10:25:11 AM, you wrote: > > >> I am getting problems similar to those outlined above. I don't run natd, either, but I do > >> have a firewall enabled. (open rule) I've had to 'put' files rather than 'get' them, since my > >> last build/installworld. (Yesterday's -current source) > > TP> I am not running any firewall but my last cvsup which is also current was the same day as yours. > > i'm still experiencing this strange problem too. developers, where are you? :) > Let's continue this thread in capital letters. We might attract some attention! ;-) I CAN'T FTP OUT FROM MY -CURRENT SYSTEM. I CAN FTP IN. SOMETHING IS PROBABLY WRONG. I CAN LIST DIRECTORIES, USUALLY. 'GET' COMMANDS HANG. I AM RUNNING -CURRENT FROM MORNING APR 13. THANKS! BRET FORD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 15 23:57: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E079115162 for ; Thu, 15 Apr 1999 23:57:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA47699 for ; Fri, 16 Apr 1999 00:54:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: (from imp@localhost) by harmony.village.org (8.9.3/8.8.3) id AAA07198 for current@freebsd.org; Fri, 16 Apr 1999 00:54:32 -0600 (MDT) Date: Fri, 16 Apr 1999 00:54:32 -0600 (MDT) From: Warner Losh Message-Id: <199904160654.AAA07198@harmony.village.org> To: current@freebsd.org Subject: make aout-to-elf on -current? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does make aout-to-elf still purport to work from a 2.2.8R system to a recent (like today's) current? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 0:15:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 2501814BEA for ; Fri, 16 Apr 1999 00:15:04 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA00782; Fri, 16 Apr 1999 16:42:40 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA28721; Fri, 16 Apr 1999 16:42:38 +0930 (CST) Message-ID: <19990416164237.N27806@lemis.com> Date: Fri, 16 Apr 1999 16:42:37 +0930 From: Greg Lehey To: Warner Losh , current@FreeBSD.ORG Subject: Re: make aout-to-elf on -current? References: <199904160654.AAA07198@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904160654.AAA07198@harmony.village.org>; from Warner Losh on Fri, Apr 16, 1999 at 12:54:32AM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 16 April 1999 at 0:54:32 -0600, Warner Losh wrote: > Does make aout-to-elf still purport to work from a 2.2.8R system to > a recent (like today's) current? I spent a week trying to upgrade from 3.0-CURRENT of about August last year to 4.0-CURRENT of the beginning of April. I finally gave up going the direct way and upgraded first to 3.1-STABLE and from there to 4.0-CURRENT. I have 22 MB of make output to show for it. Most of the problems appear to have to do with the change in compiler. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 1:13:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id 4F89714DC7 for ; Fri, 16 Apr 1999 01:13:54 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 3934 invoked by uid 1001); 16 Apr 1999 08:11:30 -0000 To: Matthew Dillon Cc: current@freebsd.org Subject: Re: swap on Irix (overcommiting, etc.) References: <199904151838.OAA98565@misha.cisco.com> <199904151938.MAA48113@apollo.backplane.com.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 16 Apr 1999 11:11:13 +0300 In-Reply-To: Matthew Dillon's message of "15 Apr 1999 22:40:48 +0300" Message-ID: <86676xvvby.fsf@not.demophon.com> Lines: 7 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > To be blunt, the 'total VM' used by a system can run into the gigabytes > while the actual real memory + swap allocation is 1/10 of that... or Add another 1000% for stack autoextension... ;--) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 1:15:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 49ACA151FF for ; Fri, 16 Apr 1999 01:15:29 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id <26KYC5WD>; Fri, 16 Apr 1999 10:15:42 +0200 Message-ID: <55586E7391ACD211B9730000C11002761795EC@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Matthew Dillon' , Mikhail Teterin Cc: current@FreeBSD.ORG Subject: RE: swap on Irix (overcommiting, etc.) Date: Fri, 16 Apr 1999 10:11:47 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Matthew Dillon [SMTP:dillon@apollo.backplane.com] > Sent: Thursday, April 15, 1999 9:38 PM > To: Mikhail Teterin > Cc: current@FreeBSD.ORG > Subject: Re: swap on Irix (overcommiting, etc.) > > If some of you are wondering why some of us are saying this > guarenteeing > of memory is a crap argument, it's because it *IS* a crap > argument. > [ML] hey, I know it's a crap argument, that's why I did not raise any objections concerning memory overcommit (even though I am the one who has read the STDC document in an anal-retentive manner regarding malloc failures). One simply has to allocate sufficient swap so that the processes do not get killed before the machine swaps itself to death :) In my experience, this is about 5xRAM for a smallish desktop, 1xRAM for a database server (but do not let any badly behaved programs run on the latter machine). There is a "feature" of HPUX (and I think SINIX and Solaris as well) that they are capable of potentially swapping into a mounted filesystem. The actual filesystem swapping is very slow, and is used by the system as the last resort only--merely, swap is "reserved" there (reserved in the sense that the systems idea of free space in the filesystem is reduced by (a fraction of) the reserved amount i.e. the system keeps statistics about how much VM would have been needed if no overcommit were used, how much of the swap was really used, and how much of the filesystem swap was actually used). If the sysadmin ever sees non-zero actual filesystem swap usage, he better increases RAM/swap. Alas, I do not quite know whether this "feature" were possible in FreeBSD, or how hard would it be to implement it. It does not really solve anything, but it brings you somewhat further along. OTOH, just normal swap monitoring on FreeBSD provides you with the same information, and is practically as safe (okay, the filesystem swappers have an emergency swap area as well, which means that they can err on the low side with actual swap, but this doesn't really bring anything.) /Marino (who really did not expect this thread will explode so :) > -Matt > Matthew Dillon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 1:20:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from f77.nop.or.jp (f77.nop.or.jp [210.145.217.241]) by hub.freebsd.org (Postfix) with ESMTP id 363A014E63 for ; Fri, 16 Apr 1999 01:20:43 -0700 (PDT) (envelope-from uch@nop.or.jp) Received: from localhost (localhost [127.0.0.1]) by f77.nop.or.jp (8.9.1a/3.7W) with ESMTP id RAA00304; Fri, 16 Apr 1999 17:17:39 +0900 (JST) To: peter@netplex.com.au Cc: rwhitesel@nbase-xyplex.com, dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: newconfig/new-bus In-Reply-To: Your message of "Wed, 14 Apr 1999 03:53:16 +0800" <19990413195319.16D6A1F4F@spinner.netplex.com.au> References: <19990413195319.16D6A1F4F@spinner.netplex.com.au> X-Mailer: Mew version 1.92 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990416171739K.uch@nop.or.jp> Date: Fri, 16 Apr 1999 17:17:39 +0900 From: UCHIYAMA Yasushi X-Dispatcher: imput version 971024 Lines: 18 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | shouldn't be too hard though, but even then there are seriously non-trivial | differences in the tty, block/character devices, VM, networking, etc. Even | if the config interface was compatable it wouldn't ever be a 'drop in' | option, even with 'newconfig'. In strongly system-dependent part, even if newconfig, it is required many source change. But *BSD difference is smaller than other OSes. Except for static configuration and module dependency resolvation, I feel new-bus and newconfig have the same possibility. So new-bus seems to `re-invent the wheel'. Why not improve 4.4BSD newconfig? Except for FreeBSD, almost all the drivers are newconfig. (FreeBSD's oldconfig should die) What is merit of new-bus? Identity? current newconfig code don't support dynamic configuration. but this is not newconfig potential. Furuta and I intend to code it. --- UCHIYAMA Yasushi uch@nop.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 2:17:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id BE4F615389 for ; Fri, 16 Apr 1999 02:17:12 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA70160; Fri, 16 Apr 1999 10:18:46 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 16 Apr 1999 10:18:46 +0100 (BST) From: Doug Rabson To: UCHIYAMA Yasushi Cc: peter@netplex.com.au, rwhitesel@nbase-xyplex.com, current@FreeBSD.ORG Subject: Re: newconfig/new-bus In-Reply-To: <19990416171739K.uch@nop.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 16 Apr 1999, UCHIYAMA Yasushi wrote: > | shouldn't be too hard though, but even then there are seriously non-trivial > | differences in the tty, block/character devices, VM, networking, etc. Even > | if the config interface was compatable it wouldn't ever be a 'drop in' > | option, even with 'newconfig'. > > In strongly system-dependent part, even if newconfig, it is required > many source change. But *BSD difference is smaller than other OSes. > Except for static configuration and module dependency resolvation, I > feel new-bus and newconfig have the same possibility. So new-bus seems > to `re-invent the wheel'. Why not improve 4.4BSD newconfig? Except > for FreeBSD, almost all the drivers are newconfig. (FreeBSD's > oldconfig should die) What is merit of new-bus? Identity? > > current newconfig code don't support dynamic configuration. but this > is not newconfig potential. Furuta and I intend to code it. I'm going to re-post a reply I made to Warner Losh a while ago on the new-bus-arch list. It covers most of the reasons I have for preferring new-bus from newconfig. On Sat, 10 Apr 1999, Warner Losh wrote: > > How is New Bus different than new config that NetBSD, OpenBSD, et al > have? The Japanese hackers seem to like it and have built some things > on top of its structures. The main difference in style is that we don't rely on config(8) to build a tree of possible device attachments when the kernel is configured. The drivers in new-bus are dynamically registered with all appropriate attachment points as the driver is initialised. Since this happens via SYSINIT, drivers can be trivially loaded after the kernel has booted. A simple mechanism allows un-matched devices to be automatically probed and attached when a suitable driver is loaded. My only use of config(8) at the moment is to build the kernel makefile (which includes all statically linked drivers) and to build a list of 'probe hints' for non-pnp busses such as ISA. I would like to move the probe hints into a file which can be loaded by the bootstrap at some point. Ideally, it should be possible to build a kernel with no drivers at all and have the bootstrap load all necessary modules along with the kernel. It might be hard to make console devices loadable in this way but most other drivers wouldn't even notice the difference. The next thing which new-bus gives us over newconfig is flexibility. Because all driver functions are specified in interfaces (cf. device_if.m) instead of using structures full of function pointers, new functions can be added to interfaces and new interfaces for specific busses or classes of device can be added without having to change kernel data structures or add new ad-hoc function pointer tables. To further improve the stability and longevity of separately compiled drivers (where source might not be available), all the device data structures are opaque to the driver implementor and therefore structure and/or implementation changes do not require that all drivers are rebuilt. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 2:26:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 4020115389 for ; Fri, 16 Apr 1999 02:26:01 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id KAA25178; Fri, 16 Apr 1999 10:23:33 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA03271; Fri, 16 Apr 1999 09:49:06 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904160849.JAA03271@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Bret Ford" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Re[2]: ftp hangs on -current In-reply-to: Your message of "Thu, 15 Apr 1999 22:18:08 PDT." <001d01be87c8$8971d420$0100a8c0@my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Apr 1999 09:49:05 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > Let's continue this thread in capital letters. We might attract some attention! ;-) > > I CAN'T FTP OUT FROM MY -CURRENT SYSTEM. I CAN FTP IN. SOMETHING > IS PROBABLY WRONG. I CAN LIST DIRECTORIES, USUALLY. 'GET' COMMANDS > HANG. I AM RUNNING -CURRENT FROM MORNING APR 13. > > THANKS! Generally, if you don't get a response, it usually indicates one of three things: 1. Nobody understands the question. 2. The answer is well documented either because the question has been asked many times before or the info's in the man page/FAQ/handbook. 3. A quick check indicates that there isn't a problem. From my point of view, number 3 is my reason for not replying... I last updated yesterday. > BRET FORD -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 5:49:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 065AF1531D for ; Fri, 16 Apr 1999 05:49:32 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id QAA63057 for ; Fri, 16 Apr 1999 16:47:09 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@FreeBSD.ORG Subject: Re: Re[2]: ftp hangs on -current Date: Fri, 16 Apr 1999 16:07:50 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <199904160849.JAA03271@keep.lan.Awfulhak.org> MIME-Version: 1.0 Message-Id: <99041616470501.00565@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ÐÔ , 16 ÁÐÒ 1999, Brian Somers ÎÁÐÉÓÁÌ: > > I CAN'T FTP OUT FROM MY -CURRENT SYSTEM. I CAN FTP IN. SOMETHING > > IS PROBABLY WRONG. I CAN LIST DIRECTORIES, USUALLY. 'GET' COMMANDS > > HANG. I AM RUNNING -CURRENT FROM MORNING APR 13. > Generally, if you don't get a response, it usually indicates one of > three things: when _one_ person reports about a problem, it is usually not a bug. but when 5 men experience the same problem after cvsup, it is a reason for developers to note that fact, isn't it? > 1. Nobody understands the question. ftp sessions began to hang after one of cvsup/make world. login sequence passes ok, but when i try to get a list of files, the ftp session hangs and after several minutes it fails with error 421. in my case it depends on natd (when i disable this daemon, everything work quite well), but some people experience the same problem even without natd. > 2. The answer is well documented either because the question has been > asked many times before or the info's in the man page/FAQ/handbook. i'm in doubt :) -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 6: 4:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (Postfix) with ESMTP id 4D3BC15409 for ; Fri, 16 Apr 1999 06:04:32 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.9.3/8.9.3) with ESMTP id IAA05979; Fri, 16 Apr 1999 08:50:26 -0400 (EDT) Date: Fri, 16 Apr 1999 08:50:26 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Don Lewis Cc: Chuck Robey , Anthony Kimball , phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: swap-related problems In-Reply-To: <199904152349.QAA11653@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Apr 1999, Don Lewis wrote: > SunOS 4 doesn't do memory overcommit. I get the impression from Vahalia's _UNIX Internals_ that this is true of SunOS 5 as well. > This could be shaved down a bit if SunOS didn't require > (swap > total VM) instead of (swap + RAM > total VM). Again, from my readings it seems that Solaris has the latter policy. Does anyone know if this is true? This would seem to put paid to the idea that overcommit is the only way to go. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 6: 9:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 0018C15041 for ; Fri, 16 Apr 1999 06:09:17 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA09452; Fri, 16 Apr 1999 15:06:54 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA03087; Fri, 16 Apr 1999 15:06:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: ben@rosengart.com Cc: Don Lewis , Chuck Robey , Anthony Kimball , current@FreeBSD.ORG Subject: Re: swap-related problems In-reply-to: Your message of "Fri, 16 Apr 1999 08:50:26 EDT." Date: Fri, 16 Apr 1999 15:06:50 +0200 Message-ID: <3085.924268010@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Snob Art Gen re writes: >On Thu, 15 Apr 1999, Don Lewis wrote: > >> SunOS 4 doesn't do memory overcommit. > >I get the impression from Vahalia's _UNIX Internals_ that this is true >of SunOS 5 as well. I know from experience that solaris 2.4 overcommits. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 6: 9:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id A4DF715041 for ; Fri, 16 Apr 1999 06:09:41 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id RAA63216 for ; Fri, 16 Apr 1999 17:07:18 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@FreeBSD.ORG Subject: some news about ftp hangs Date: Fri, 16 Apr 1999 16:56:24 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99041617071702.00565@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG trying different configurations i have encountered the following 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang; 2. ncftp3 from ports DOES NOT hang; 3. netscape communicator 4 DOES NOT hang. so it seems that the problem is in native FreeBSD's ftp or a library (libedit.so.2, libtermcap.so.2 or libc.so.3). -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 6:11:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id 116FE1543B for ; Fri, 16 Apr 1999 06:11:32 -0700 (PDT) (envelope-from lowell@world.std.com) Received: from world.std.com by europe.std.com (STD1.2/BZS-8-1.0) id JAA04027; Fri, 16 Apr 1999 09:09:09 -0400 (EDT) Received: by world.std.com (TheWorld/Spike-2.0) id AA06674; Fri, 16 Apr 1999 09:09:09 -0400 To: freebsd-current@freebsd.org Subject: Re: swap on Irix (overcommiting, etc.) References: <199904151934.PAA98792@misha.cisco.com> From: Lowell Gilbert Date: 16 Apr 1999 09:09:09 -0400 In-Reply-To: Mikhail Teterin's message of Thu, 15 Apr 1999 15:34:54 -0400 (EDT) Message-Id: Lines: 28 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin writes: > Sorry. I'm just repeating what Ladavac Marino wrote in > <55586E7391ACD211B9730000C11002761795EB@r-lmh-wi-100.corpnet.at>: > > LM: Please note that memory overcommit architectures are a > LM: rather common optimization; FreeBSD is one of them. They > LM: do, however, break the ISO/ANSI C conformance (strictly > LM: speaking). > > Since there was no immediate (nor later) rebuttal, I assumed, that > everyone quietly agreed... Absolutely not. It is *definitely* okay for system conditions outside the realm of the C spec to effect the execution of "conforming" programs. Otherwise, having a system shutdown interrupt the program would be enough to make the system non-conforming. Heck, the *existence* of kill(1) and SIGKILL would be enough to make for a non-conforming C environment. The system running short on virtual memory (whether it be by having a user program touch memory it had previously allocated, or by having a new user log in, or a new sendmail daemon starting up) fits squarely into that category. How (and when) you assign backing store to virtual memory is a *very* interesting topic, but the ISO C compliance issue is a red herring, even to the most pointlessly pedantic language lawyers. Be well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 6:31:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 334C515472 for ; Fri, 16 Apr 1999 06:31:16 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA09525; Fri, 16 Apr 1999 15:28:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA03193; Fri, 16 Apr 1999 15:28:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Lowell Gilbert Cc: freebsd-current@FreeBSD.ORG Subject: Re: swap on Irix (overcommiting, etc.) In-reply-to: Your message of "16 Apr 1999 09:09:09 EDT." Date: Fri, 16 Apr 1999 15:28:49 +0200 Message-ID: <3191.924269329@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Lowell Gilbert writes: >Mikhail Teterin writes: > >> Sorry. I'm just repeating what Ladavac Marino wrote in >> <55586E7391ACD211B9730000C11002761795EB@r-lmh-wi-100.corpnet.at>: >> >> LM: Please note that memory overcommit architectures are a >> LM: rather common optimization; FreeBSD is one of them. They >> LM: do, however, break the ISO/ANSI C conformance (strictly >> LM: speaking). >> >> Since there was no immediate (nor later) rebuttal, I assumed, that >> everyone quietly agreed... > >[...] Heck, the >*existence* of kill(1) and SIGKILL would be enough to make for a >non-conforming C environment. See RFC 748 for more details. Please let this thread die now. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 7:27:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D7BF0153FD for ; Fri, 16 Apr 1999 07:27:48 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id HAA05315; Fri, 16 Apr 1999 07:22:02 -0700 (PDT) Date: Fri, 16 Apr 1999 07:22:02 -0700 (PDT) From: Julian Elischer To: Ilya Naumov Cc: current@FreeBSD.ORG Subject: Re: some news about ftp hangs In-Reply-To: <99041617071702.00565@camel.avias.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG or you've got a firewall that doesn't allow active FTP :-) On Fri, 16 Apr 1999, Ilya Naumov wrote: > > trying different configurations i have encountered the following > > 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang; > 2. ncftp3 from ports DOES NOT hang; > 3. netscape communicator 4 DOES NOT hang. > > so it seems that the problem is in native FreeBSD's ftp or a library > (libedit.so.2, libtermcap.so.2 or libc.so.3). > > -- > > sincerely, > ilya naumov (at work) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 7:35:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 1A43C153FD for ; Fri, 16 Apr 1999 07:35:37 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA16773; Fri, 16 Apr 1999 10:32:19 -0400 (EDT) (envelope-from luoqi) Date: Fri, 16 Apr 1999 10:32:19 -0400 (EDT) From: Luoqi Chen Message-Id: <199904161432.KAA16773@lor.watermarkgroup.com> To: camel@avias.com, current@FreeBSD.ORG Subject: Re: some news about ftp hangs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > trying different configurations i have encountered the following > > 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang; > 2. ncftp3 from ports DOES NOT hang; > 3. netscape communicator 4 DOES NOT hang. > > so it seems that the problem is in native FreeBSD's ftp or a library > (libedit.so.2, libtermcap.so.2 or libc.so.3). > I suspect libalias' ftp PORT command handling. > -- > > sincerely, > ilya naumov (at work) > Here's async log output from alias enabled ppp, while ftp was retransmitting the PORT command packet: Async: 7e 3d c0 00 00 9d 21 45 00 00 38 13 42 00 00 ff ^^ Async: 01 e3 a7 cf ca 49 aa d0 17 db 4e 03 03 a2 f8 00 Async: 00 00 00 45 00 00 39 a4 4e 00 00 2e 11 79 35 d0 ^^ Async: 17 db 4e cf ca 49 aa 04 00 00 35 00 25 00 00 e3 Async: 69 7e If looked like somehow the first ip frame was overwritten by a second ip frame... -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 7:35:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (Postfix) with ESMTP id 3DA16153FD for ; Fri, 16 Apr 1999 07:35:43 -0700 (PDT) (envelope-from bford@uop.cs.uop.edu) Received: from heather (user163.pop2.cwia.com [209.142.32.163]) by uop.cs.uop.edu (8.8.8/8.8.8) with SMTP id HAA14020; Fri, 16 Apr 1999 07:33:18 -0700 (PDT) Message-ID: <001901be8816$129d2860$0100a8c0@my.domain> From: "Bret Ford" To: "Current" , References: <99041617071702.00565@camel.avias.com> Subject: Re: some news about ftp hangs Date: Fri, 16 Apr 1999 07:33:15 -0700 Organization: University of the Pacific 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.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > trying different configurations i have encountered the following > > 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang; > 2. ncftp3 from ports DOES NOT hang; > 3. netscape communicator 4 DOES NOT hang. > > so it seems that the problem is in native FreeBSD's ftp or a library > (libedit.so.2, libtermcap.so.2 or libc.so.3). > Great detective work. Confirmed from here as well. PASSIVE ftp and ncftp work. Bret Ford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 7:38:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (Postfix) with ESMTP id BA64B14DC0 for ; Fri, 16 Apr 1999 07:38:47 -0700 (PDT) (envelope-from bford@uop.cs.uop.edu) Received: from heather (user163.pop2.cwia.com [209.142.32.163]) by uop.cs.uop.edu (8.8.8/8.8.8) with SMTP id HAA14034; Fri, 16 Apr 1999 07:36:23 -0700 (PDT) Message-ID: <001f01be8816$80b73160$0100a8c0@my.domain> From: "Bret Ford" To: "Current" , "Julian Elischer" References: Subject: Re: some news about ftp hangs Date: Fri, 16 Apr 1999 07:36:21 -0700 Organization: University of the Pacific 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.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My firewall is set with the open rule only---and I'm still getting the behavior described below. Bret Ford > or you've got a firewall that doesn't allow active FTP :-) > > > On Fri, 16 Apr 1999, Ilya Naumov wrote: > > > > > trying different configurations i have encountered the following > > > > 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang; > > 2. ncftp3 from ports DOES NOT hang; > > 3. netscape communicator 4 DOES NOT hang. > > > > so it seems that the problem is in native FreeBSD's ftp or a library > > (libedit.so.2, libtermcap.so.2 or libc.so.3). > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 7:51:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 255FD15107 for ; Fri, 16 Apr 1999 07:51:40 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Y9vA-0006CU-00; Fri, 16 Apr 1999 16:48:44 +0200 From: Sheldon Hearn To: "Bret Ford" Cc: freebsd-current@freebsd.org Subject: Re: Re[2]: ftp hangs on -current In-reply-to: Your message of "Thu, 15 Apr 1999 22:18:08 MST." <001d01be87c8$8971d420$0100a8c0@my.domain> Date: Fri, 16 Apr 1999 16:48:44 +0200 Message-ID: <23837.924274124@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Apr 1999 22:18:08 MST, "Bret Ford" wrote: > Let's continue this thread in capital letters. We might attract > some attention! ;-) Well done, you've attracted attention. I'm sitting here thinking you're a moron. I can ftp in and out of my machine without problems using a current that's less than a day old. I use ftp throughout the day from the box in question and haven't noticed any such problem at all. Stop whining and start being responsible about how you report the problem you're having. Send a detailed description of your environment and the problem you're experiencing to freebsd-questions@freebsd.org . Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 8:11:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 084F3152E8 for ; Fri, 16 Apr 1999 08:11:47 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10YAEs-000Djb-00; Fri, 16 Apr 1999 17:09:06 +0200 From: Sheldon Hearn To: "Bret Ford" Cc: freebsd-current@freebsd.org Subject: Re: Re[2]: ftp hangs on -current In-reply-to: Your message of "Fri, 16 Apr 1999 08:04:17 MST." <000901be881a$68786340$0100a8c0@my.domain> Date: Fri, 16 Apr 1999 17:09:06 +0200 Message-ID: <52798.924275346@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bret, I apologise for the outburst. I suppose the fact that I can't see a problem on my box doesn't mean that no problem exists, and my tone was uncalled for. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 8:13: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 9BE91152E8 for ; Fri, 16 Apr 1999 08:12:46 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA25262; Fri, 16 Apr 1999 11:10:18 -0400 (EDT) (envelope-from wollman) Date: Fri, 16 Apr 1999 11:10:18 -0400 (EDT) From: Garrett Wollman Message-Id: <199904161510.LAA25262@khavrinen.lcs.mit.edu> To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: rexec documentation/compatibility question In-Reply-To: <199904160355.XAA13170@bb01f39.unx.sas.com> References: <199904160355.XAA13170@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > DESCRIPTION > This interface is obsoleted by rcmd(3). It is available from the compat- > ibility library, libcompat. > However, I don't see how rcmd() can be used to replace rexec() > since rcmd() is a root/rresvport mechanism, as where rexec() is > a .netrc mechanism. Don't send passwords in the clear over the net. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 9: 0:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id B8691158E8 for ; Fri, 16 Apr 1999 09:00:13 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id QAA00732; Fri, 16 Apr 1999 16:57:37 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA07764; Fri, 16 Apr 1999 16:53:13 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904161553.QAA07764@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: camel@avias.com, current@FreeBSD.ORG Subject: Re: some news about ftp hangs In-reply-to: Your message of "Fri, 16 Apr 1999 10:32:19 EDT." <199904161432.KAA16773@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Apr 1999 16:53:11 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > trying different configurations i have encountered the following > > > > 1. ftp in passive mode (pftp or ftp with -p options) DOES NOT hang; > > 2. ncftp3 from ports DOES NOT hang; > > 3. netscape communicator 4 DOES NOT hang. > > > > so it seems that the problem is in native FreeBSD's ftp or a library > > (libedit.so.2, libtermcap.so.2 or libc.so.3). > > > I suspect libalias' ftp PORT command handling. Well, that hasn't changed for some time. It's not perfect in that it can't detect PORT commands that span more than one packet fragment, but this (to my knowledge) won't happen in real life as `ftp' uses the PORT command in the middle of a conversation - surrounded by expected responses from the peer, and thus making the whole PORT thing go off in one piece. > > -- > > > > sincerely, > > ilya naumov (at work) > > > Here's async log output from alias enabled ppp, while ftp was retransmitting > the PORT command packet: > > Async: 7e 3d c0 00 00 9d 21 45 00 00 38 13 42 00 00 ff > ^^ > Async: 01 e3 a7 cf ca 49 aa d0 17 db 4e 03 03 a2 f8 00 > Async: 00 00 00 45 00 00 39 a4 4e 00 00 2e 11 79 35 d0 > ^^ > Async: 17 db 4e cf ca 49 aa 04 00 00 35 00 25 00 00 e3 > Async: 69 7e > > If looked like somehow the first ip frame was overwritten by a second ip > frame... Hmm, I don't see any PORT command in there ;-/ > -lq -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 9:51: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id ADE991595E for ; Fri, 16 Apr 1999 09:50:51 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id MAA17733; Fri, 16 Apr 1999 12:46:34 -0400 (EDT) (envelope-from luoqi) Date: Fri, 16 Apr 1999 12:46:34 -0400 (EDT) From: Luoqi Chen Message-Id: <199904161646.MAA17733@lor.watermarkgroup.com> To: brian@Awfulhak.org, luoqi@watermarkgroup.com Subject: Re: some news about ftp hangs Cc: camel@avias.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Here's async log output from alias enabled ppp, while ftp was retransmitting > > the PORT command packet: > > > > Async: 7e 3d c0 00 00 9d 21 45 00 00 38 13 42 00 00 ff > > ^^ > > Async: 01 e3 a7 cf ca 49 aa d0 17 db 4e 03 03 a2 f8 00 ^^ ^^ ^^ protocol = ICMP unreachable port > > Async: 00 00 00 45 00 00 39 a4 4e 00 00 2e 11 79 35 d0 > > ^^ ^^ UDP > > Async: 17 db 4e cf ca 49 aa 04 00 00 35 00 25 00 00 e3 ^^^^^ port 53 = DNS > > Async: 69 7e > > > > If looked like somehow the first ip frame was overwritten by a second ip > > frame... > > Hmm, I don't see any PORT command in there ;-/ > Sorry, this is a legitimate ICMP packet: port unreacheable. It looks like the ftp server (ftp.freebsd.org) was making an UDP query to DNS port on the client (which happens to have a named server running, but that's just for the internal network, external ip address is served by an outside server) and the client responds with port unreacheable even though there is a named running. I'm totally confused. I'll try to find out more. By the way, if I turn off aliasing (set alias enable off), ftp works fine again. -lq > -- > Brian > > Don't _EVER_ lose your sense of humour ! > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 10: 8: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C6B021515B for ; Fri, 16 Apr 1999 10:08:03 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA17969; Sat, 17 Apr 1999 02:03:54 +0900 (JST) Message-ID: <37176D0F.904687D6@newsguy.com> Date: Sat, 17 Apr 1999 02:02:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Luoqi Chen Cc: brian@Awfulhak.org, camel@avias.com, current@FreeBSD.ORG Subject: Re: some news about ftp hangs References: <199904161646.MAA17733@lor.watermarkgroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > > Sorry, this is a legitimate ICMP packet: port unreacheable. It looks like > the ftp server (ftp.freebsd.org) was making an UDP query to DNS port on > the client (which happens to have a named server running, but that's just > for the internal network, external ip address is served by an outside server) > and the client responds with port unreacheable even though there is a named > running. I'm totally confused. I'll try to find out more. By the way, if > I turn off aliasing (set alias enable off), ftp works fine again. This might be a good time to point out that such changes were made not only to ftp but to a number of other clients. We now check the reverse address for the IP that was found, so we can decide whether log the name or the ip address (the later if the reverse does not match the original address). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 13: 4:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id E5E8815A40 for ; Fri, 16 Apr 1999 13:04:04 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id VAA00964; Fri, 16 Apr 1999 21:01:35 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA00879; Fri, 16 Apr 1999 20:03:19 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904161903.UAA00879@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Luoqi Chen , brian@Awfulhak.org, camel@avias.com, current@FreeBSD.ORG Subject: Re: some news about ftp hangs In-reply-to: Your message of "Sat, 17 Apr 1999 02:02:07 +0900." <37176D0F.904687D6@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Apr 1999 20:03:17 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen wrote: > > > > Sorry, this is a legitimate ICMP packet: port unreacheable. It looks like > > the ftp server (ftp.freebsd.org) was making an UDP query to DNS port on > > the client (which happens to have a named server running, but that's just > > for the internal network, external ip address is served by an outside server) > > and the client responds with port unreacheable even though there is a named > > running. I'm totally confused. I'll try to find out more. By the way, if > > I turn off aliasing (set alias enable off), ftp works fine again. > > This might be a good time to point out that such changes were made > not only to ftp but to a number of other clients. We now check the > reverse address for the IP that was found, so we can decide whether > log the name or the ip address (the later if the reverse does not > match the original address). Now I think I'm confused ;-} I haven't seen any changes to ftp.... I did the double lookup bit to all the stuff in libexec (including ftpd), but that shouldn't effect what's going on here. If the external NS record for Louqi's machine isn't supposed to be on that machine, then we shouldn't have seen a DNS query (maybe named is only binding to the internal IP - hence the ICMP unreachable bit). But we digress ! What's supposed to happen w/ ftp (for anyone that doesn't already know): o The client does a ``get ....''. o ftp creates a socket and bind()s it, getting a random port number back. o ftp sends a PORT command with arguments of the local IP number and the port that bind() gave back. o libalias catches this packet and tweaks it. It changes the IP to the interface IP and may change the port so some arbitrary number that fits in well with it's little world. It then makes an entry in the internal alias tables so that it'll catch the subsequent connection from the remote host, and undo the damage done from mangling the PORT command. All this happens in src/lib/libalias/alias_ftp.c o ftp sends the RETR command down the original connection and gets the data back on the new connection. The deficiency in libalias is that it can't identify PORT commands that span more than one packet fragment. In practice this has never been a problem (well, to my knowledge). On my laptop (-current from yesterday), things are just peachy. So, I don't get it. I've tested without libalias involved to other machines, and with libalias to my local machine (a ppp loopback). I haven't tested via libalias to another machine (I've only got one machine at the moment - I'm on the train!). I'll have a further poke around when I get home, but I suspect no changes ;-/ > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "Well, Windows works, using a loose definition of 'works'..." -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 13:10:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2233015A99 for ; Fri, 16 Apr 1999 13:10:16 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA49500; Fri, 16 Apr 1999 14:07:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA10692; Fri, 16 Apr 1999 14:07:46 -0600 (MDT) Message-Id: <199904162007.OAA10692@harmony.village.org> To: Greg Lehey Subject: Re: make aout-to-elf on -current? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 16 Apr 1999 16:42:37 +0930." <19990416164237.N27806@lemis.com> References: <19990416164237.N27806@lemis.com> <199904160654.AAA07198@harmony.village.org> Date: Fri, 16 Apr 1999 14:07:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990416164237.N27806@lemis.com> Greg Lehey writes: : I spent a week trying to upgrade from 3.0-CURRENT of about August last : year to 4.0-CURRENT of the beginning of April. I finally gave up : going the direct way and upgraded first to 3.1-STABLE and from there : to 4.0-CURRENT. I have 22 MB of make output to show for it. Most of : the problems appear to have to do with the change in compiler. After reading the UPDATING file, I realized just how silly a question this was :-). a.out make world is broken in -current with egcs. So, I did a cvs co -rRELENG_3 and that seems to be getting much farther than the -current one did. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 13:17: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9865015A16 for ; Fri, 16 Apr 1999 13:17:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA59951; Fri, 16 Apr 1999 13:14:42 -0700 (PDT) (envelope-from dillon) Date: Fri, 16 Apr 1999 13:14:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199904162014.NAA59951@apollo.backplane.com> To: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG Subject: NFS patch #3 avail ( but wait till the weekend if you can ) files) References: <199904142054.WAA02242@yedi.iaf.nl> <3.0.6.32.19990415102613.00819aa0@192.168.255.1> <199904151523.IAA44754@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NFS patch #3 ( for -current ) is now available. Again, I recommend waiting until the weekend before seriously trying any of these patches and not running them on any machine for which the loss of data would be a problem. http://www.backplane.com/FreeBSD4/ The current patch represents a huge amount of cleanup of the VFS/BIO code as well as hopefully fixed and re-optimized ( but not quite as optimized as the original ) NFS code. Due to the number of changes, the patch effects the entire VFS/BIO system including UFS, so again: WARNING WARNING WILL ROBINSON! Do not use it unless you are willing to lose whole filesystems! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 13:34:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0C92914E46 for ; Fri, 16 Apr 1999 13:34:11 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA29619; Sat, 17 Apr 1999 05:30:12 +0900 (JST) Message-ID: <37179AB9.2275475F@newsguy.com> Date: Sat, 17 Apr 1999 05:16:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Brian Somers Cc: Luoqi Chen , camel@avias.com, current@FreeBSD.ORG Subject: Re: some news about ftp hangs References: <199904161903.UAA00879@keep.lan.Awfulhak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > Now I think I'm confused ;-} I haven't seen any changes to ftp.... > I did the double lookup bit to all the stuff in libexec (including > ftpd), but that shouldn't effect what's going on here. If the > external NS record for Louqi's machine isn't supposed to be on that > machine, then we shouldn't have seen a DNS query (maybe named is only > binding to the internal IP - hence the ICMP unreachable bit). It looked too easy a suspect at this late at night. Sorry. The changes related to logging, and would not touch ftp, only ftpd. I was just confused by a recent problem I had with telnet client doing a reverse name lookup. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 14:32:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-19.ix.netcom.com [207.93.148.19]) by hub.freebsd.org (Postfix) with ESMTP id 8842814CA0 for ; Fri, 16 Apr 1999 14:32:13 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id OAA93936; Fri, 16 Apr 1999 14:29:50 -0700 (PDT) (envelope-from tomdean) Date: Fri, 16 Apr 1999 14:29:50 -0700 (PDT) Message-Id: <199904162129.OAA93936@ix.netcom.com> From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: /etc/rc.conf or /etc/rc.conf.local Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see the latest /etc/defaults/rc.conf will include either or both of /etc/rc.conf or /etc/rc.conf.local. I only want to have one. Which is going to stay with us the longest? tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 14:33:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 10CCC1570C for ; Fri, 16 Apr 1999 14:33:07 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 95C7B1F69 for ; Sat, 17 Apr 1999 05:30:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: HEADS UP!!!! Important instructions for -current users! Date: Sat, 17 Apr 1999 05:30:41 +0800 From: Peter Wemm Message-Id: <19990416213043.95C7B1F69@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of a few minutes ago, a minimal set of changes to bring the so-called 'new-bus' functionality to the i386 kernel in -current. This is a complete, from the ground up, change in the way the system boots and configures. For the most part, we've gone to a lot of trouble to make it work the way it used to, but there are some minor changes required to your kernel config file that make a BIG DIFFERENCE to what happens when you boot up. If you do not update the config file, you will not have a working keyboard! A brief summary of the changes you should make (see GENERIC!!): * apm and npx should attach to the nexus, not isa. * atkbd and psm should attach to the atkbdc, not isa. (critical!) I have bracketed the commit with PRE_NEWBUS and POST_NEWBUS tags. As a special warning: The APIC_IO interrupt management could be a little wonky on systems that require the special mptable fixups. If you have warnings about broken mptables, or additional interrupts being wired, hold back until it's been checked. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 14:43:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-19.ix.netcom.com [207.93.148.19]) by hub.freebsd.org (Postfix) with ESMTP id C842414D2A for ; Fri, 16 Apr 1999 14:43:35 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id OAA93965; Fri, 16 Apr 1999 14:41:12 -0700 (PDT) (envelope-from tomdean) Date: Fri, 16 Apr 1999 14:41:12 -0700 (PDT) Message-Id: <199904162141.OAA93965@ix.netcom.com> From: Thomas Dean To: freebsd-current@freebsd.org Subject: Updating ports after change to egcs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running 4.0-current of April 12. 1999. I just finished updating my ports after the change to egcs-2.91.66. I know they were OK as they were, but, I wanted to eliminate all the gcc compiled things. And, this was a good time. I had to fix a couple of applications with bad code. Everything else, all the FreeBSD-supplied parts, worked as intended. Looks like major changes can be made to FreeBSD and things settle down in a matter of a week, or so. This took a lot of work and cooperation on the part of many people. Thanks, tomdean The following ports built and installed flawlessly. XFree86-3.3.3.1/ ghostscript-5.50/ modula-3-3.6/ unzip-5.40/ arc-5.21e/ ghostview-1.5/ modula-3-lib-3.6/ xco-1.3/ autoconf-2.13/ gmake-3.77/ png-1.0.3/ xpdf-0.80/ automake-1.4/ jbigkit-1.0/ postgresql-6.4.2/ xpm-3.4k/ bzip2-0.9.0c/ jpeg-6b/ samba-2.0.3/ xscreensaver-3.08/ cvsup-16.0/ lesstif-0.87.1/ tcl-8.1.b1/ xv-3.10a/ dvi2xx-0.51a9/ lha-1.14d/ tcsh-6.08.00/ zip-2.2/ emacs-19.34b/ libtool-1.2/ tiff-3.4a/ fetchmail-5.0.0/ m4-1.4/ tk-8.1.b1/ tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 14:55:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E378C159C3 for ; Fri, 16 Apr 1999 14:55:17 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id GAA03181; Sat, 17 Apr 1999 06:52:46 +0900 (JST) Message-ID: <3717B0C2.9C61D788@newsguy.com> Date: Sat, 17 Apr 1999 06:50:58 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: /etc/rc.conf or /etc/rc.conf.local References: <199904162129.OAA93936@ix.netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > > I see the latest /etc/defaults/rc.conf will include either or both of > /etc/rc.conf or /etc/rc.conf.local. > > I only want to have one. > > Which is going to stay with us the longest? /etc/rc.conf, though rc.conf.local is not likely to go away. The former is the "do your stuff" standard file. The later is a machine-specific override when you have a standard rc.conf for many machines, and need to tweak specific parameters in a few. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 15: 9:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 10108159EB for ; Fri, 16 Apr 1999 15:08:49 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.2/8.9.0) id KAA93083 for freebsd-current@freebsd.org; Sat, 17 Apr 1999 10:06:24 +1200 (NZST) Date: Sat, 17 Apr 1999 10:06:23 +1200 From: Joe Abley To: freebsd-current@freebsd.org Subject: Consistent errors making buildworld Message-ID: <19990417100623.A93010@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been trying to make buildworld on an aged Compaq DX2 (using newly- supped CURRENT source) for about a week now, and (modulo the few egcs-looking failures early on) I am now stuck with compilation failures in doscmd. I have completely removed /usr/obj/* prior to starting, each time, and the last time I tried I also wiped /usr/src/* and re-supped. Same error (below) [note on my machine, /usr/src and /usr/obj are symlinks to /var/src and /var/obj, respectively). I have also appended /etc/make.conf to this message. Just out of interest, why is a make buildworld trying to include X headers? Machine was previously running CURRENT (supped and compiled quite a while before the egcs import). It takes about three days to make buildworld, hence my delay in reporting this... However, I see loads of other people successfully making world in -current, so I assume it must be something local. Any pointers appreciated. [last few log lines from make buildworld follows] cc -O -pipe -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/var/src/tmp/usr/include -c /var/src/usr.bin/doscmd/trap.c cc -O -pipe -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/var/src/tmp/usr/include -c /var/src/usr.bin/doscmd/tty.c /var/src/usr.bin/doscmd/tty.c:36: X11/Xlib.h: No such file or directory /var/src/usr.bin/doscmd/tty.c:37: X11/Xutil.h: No such file or directory /var/src/usr.bin/doscmd/tty.c:38: X11/keysym.h: No such file or directory /var/src/usr.bin/doscmd/tty.c:77: parse error before `*' /var/src/usr.bin/doscmd/tty.c:77: warning: data definition has no type or storage class /var/src/usr.bin/doscmd/tty.c:78: parse error before `win' /var/src/usr.bin/doscmd/tty.c:78: warning: data definition has no type or storage class /var/src/usr.bin/doscmd/tty.c:79: parse error before `*' /var/src/usr.bin/doscmd/tty.c:79: warning: data definition has no type or storage class /var/src/usr.bin/doscmd/tty.c:103: parse error before `gc' /var/src/usr.bin/doscmd/tty.c:103: warning: data definition has no type or storage class /var/src/usr.bin/doscmd/tty.c:104: parse error before `cgc' /var/src/usr.bin/doscmd/tty.c:104: warning: data definition has no type or storage class /var/src/usr.bin/doscmd/tty.c: In function `setgc': /var/src/usr.bin/doscmd/tty.c:380: `XGCValues' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:380: (Each undeclared identifier is reported only once /var/src/usr.bin/doscmd/tty.c:380: for each function it appears in.) /var/src/usr.bin/doscmd/tty.c:380: parse error before `v' /var/src/usr.bin/doscmd/tty.c:382: `v' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:393: `GCForeground' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:393: `GCBackground' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c: In function `video_update': /var/src/usr.bin/doscmd/tty.c:409: `XGCValues' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:409: parse error before `v' /var/src/usr.bin/doscmd/tty.c:484: `v' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:487: `GXxor' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:490: `GXcopy' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:492: `GCForeground' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:492: `GCFunction' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c: In function `debug_event': /var/src/usr.bin/doscmd/tty.c:737: warning: passing arg 1 of `dump_regs' from incompatible pointer type /var/src/usr.bin/doscmd/tty.c: In function `video_async_event': /var/src/usr.bin/doscmd/tty.c:986: `XEvent' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:986: parse error before `ev' /var/src/usr.bin/doscmd/tty.c:994: `ev' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c: At top level: /var/src/usr.bin/doscmd/tty.c:1126: parse error before `*' /var/src/usr.bin/doscmd/tty.c: In function `video_event': /var/src/usr.bin/doscmd/tty.c:1128: `ev' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1129: `MotionNotify' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1130: `XMotionEvent' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1130: `me' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1130: parse error before `)' /var/src/usr.bin/doscmd/tty.c:1144: `ButtonRelease' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1145: `XButtonEvent' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1145: `be' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1145: parse error before `)' /var/src/usr.bin/doscmd/tty.c:1162: `ButtonPress' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1163: parse error before `)' /var/src/usr.bin/doscmd/tty.c:1184: `NoExpose' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1186: `GraphicsExpose' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1187: `Expose' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1193: `KeyRelease' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1195: `KeySym' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1195: parse error before `ks' /var/src/usr.bin/doscmd/tty.c:1200: `ShiftMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1204: `ControlMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1209: `Mod1Mask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1214: `LockMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1218: `XKeyEvent' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1218: parse error before `)' /var/src/usr.bin/doscmd/tty.c:1219: `ks' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1220: `XK_Shift_L' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1223: `XK_Shift_R' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1226: `XK_Control_L' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1230: `XK_Control_R' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1234: `XK_Alt_L' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1238: `XK_Alt_R' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1242: `XK_Scroll_Lock' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1245: `XK_Num_Lock' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1248: `XK_Caps_Lock' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1251: `XK_Insert' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1221: warning: unreachable code at beginning of switch statement /var/src/usr.bin/doscmd/tty.c:1257: `KeyPress' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1259: parse error before `ks' /var/src/usr.bin/doscmd/tty.c:1282: parse error before `)' /var/src/usr.bin/doscmd/tty.c:1320: `XK_KP_Insert' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1326: `XK_Escape' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1330: `XK_Tab' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1331: `XK_ISO_Left_Tab' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1335: `XK_Return' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1336: `XK_KP_Enter' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1340: `XK_Print' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1344: `XK_F1' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1345: `XK_F2' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1346: `XK_F3' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1347: `XK_F4' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1348: `XK_F5' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1349: `XK_F6' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1350: `XK_F7' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1351: `XK_F8' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1352: `XK_F9' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1353: `XK_F10' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1357: `XK_KP_7' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1359: `XK_Home' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1360: `XK_KP_Home' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1363: `XK_KP_8' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1365: `XK_Up' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1366: `XK_KP_Up' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1369: `XK_KP_9' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1371: `XK_Prior' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1372: `XK_KP_Prior' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1375: `XK_KP_Subtract' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1378: `XK_KP_4' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1380: `XK_Left' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1381: `XK_KP_Left' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1384: `XK_KP_5' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1386: `XK_Begin' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1387: `XK_KP_Begin' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1390: `XK_KP_6' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1392: `XK_Right' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1393: `XK_KP_Right' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1396: `XK_KP_Add' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1399: `XK_KP_1' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1401: `XK_End' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1402: `XK_KP_End' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1405: `XK_KP_2' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1407: `XK_Down' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1408: `XK_KP_Down' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1411: `XK_KP_3' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1413: `XK_Next' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1414: `XK_KP_Next' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1417: `XK_KP_0' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1423: `XK_KP_Decimal' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1428: `XK_Delete' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1429: `XK_KP_Delete' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1433: `XK_BackSpace' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1437: `XK_F11' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1440: `XK_F12' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1445: `XK_KP_Divide' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1449: `XK_KP_Multiply' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1286: warning: unreachable code at beginning of switch statement /var/src/usr.bin/doscmd/tty.c:1142: warning: unreachable code at beginning of switch statement /var/src/usr.bin/doscmd/tty.c: In function `tty_read': /var/src/usr.bin/doscmd/tty.c:1745: warning: passing arg 1 of `fake_int' from incompatible pointer type /var/src/usr.bin/doscmd/tty.c: In function `tty_peek': /var/src/usr.bin/doscmd/tty.c:1787: warning: passing arg 1 of `fake_int' from incompatible pointer type /var/src/usr.bin/doscmd/tty.c: In function `video_init': /var/src/usr.bin/doscmd/tty.c:1963: `XSizeHints' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1963: parse error before `sh' /var/src/usr.bin/doscmd/tty.c:1964: `XGCValues' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:1965: `XColor' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2000: warning: passing arg 2 of `register_callback' from incompatible pointer type /var/src/usr.bin/doscmd/tty.c:2047: warning: assignment makes pointer from integer without a cast /var/src/usr.bin/doscmd/tty.c:2070: `ccd' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2070: `rgb' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2081: warning: assignment makes pointer from integer without a cast /var/src/usr.bin/doscmd/tty.c:2084: warning: assignment makes pointer from integer without a cast /var/src/usr.bin/doscmd/tty.c:2091: request for member `max_bounds' in something not a structure or union /var/src/usr.bin/doscmd/tty.c:2092: request for member `max_bounds' in something not a structure or union /var/src/usr.bin/doscmd/tty.c:2092: request for member `max_bounds' in something not a structure or union /var/src/usr.bin/doscmd/tty.c:2093: request for member `max_bounds' in something not a structure or union /var/src/usr.bin/doscmd/tty.c:2098: `sh' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2107: `USSize' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2107: `PMinSize' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2107: `PMaxSize' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2107: `PSize' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2116: `gcv' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2118: request for member `fid' in something not a structure or union /var/src/usr.bin/doscmd/tty.c:2120: `GCForeground' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2120: `GCBackground' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2120: `GCFont' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2126: `GXxor' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2127: `GCFunction' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2131: `ExposureMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2132: `ButtonPressMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2132: `ButtonReleaseMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2132: `PointerMotionMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2134: `KeyReleaseMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c:2134: `KeyPressMask' undeclared (first use in this function) /var/src/usr.bin/doscmd/tty.c: In function `video_bios_init': /var/src/usr.bin/doscmd/tty.c:2212: warning: passing arg 2 of `register_callback' from incompatible pointer type *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. [/etc/make.conf follows] # $Id: make.conf,v 1.73 1999/01/20 01:58:39 asami Exp $ # # This file, if present, will be read by make (see /usr/share/mk/sys.mk). # It allows you to override macro definitions to make without changing # your source tree, or anything the source tree installs. # # This file must be in valid Makefile syntax. # # You have to find the things you can put here in the Makefiles and # documentation of the source tree. # # One, and probably the most common, use could be: # CFLAGS= -O -pipe # # # Avoid compiling profiled libraries #NOPROFILE= true # # Compare before install #INSTALL=install -C # # To avoid building the default system perl #NOPERL= true # To avoid building the suid perl #NOSUIDPERL= true # # To avoid building sendmail #NO_SENDMAIL= true # # To have 'obj' symlinks created in your source directory # (they aren't needed/necessary) #OBJLINK= yes # # To compile just the kernel with special optimisations, you should use # this instead of CFLAGS (which is not applicable to kernel builds anyway): # COPTFLAGS= -O -pipe # # To compile and install the 4.4 lite libm instead of the default use: # #WANT_CSRG_LIBM= yes # # If you do not want unformatted manual pages to be compressed # when they are installed: # #NOMANCOMPRESS= true # # # If you want the "compat" shared libraries installed as part of your normal # builds, uncomment these: # #COMPAT1X= yes #COMPAT20= yes #COMPAT21= yes # # # If you do not want additional documentation (some of which are # a few hundred KB's) for ports to be installed: # #NOPORTDOCS= true # # # Default format for system documentation, depends on your printer. # Set this to "ascii" for simple printers or screen # #PRINTERDEVICE= ps # # # How long to wait for a console keypress before booting the default kernel. # This value is approximately in milliseconds. Keypresses are accepted by the # BIOS before booting from disk, making it possible to give custom boot # parameters even when this is set to 0. # #BOOTWAIT=0 #BOOTWAIT=30000 # # By default, the system will always use the keyboard/video card as system # console. However, the boot blocks may be dynamically configured to use a # serial port in addition to or instead of the keyboard/video console. # # By default we use COM1 as our serial console port *if* we're going to use # a serial port as our console at all. (0x3E8 = COM2) # #BOOT_COMCONSOLE_PORT= 0x3F8 # # The default serial console speed is 9600. Set the speed to a larger value # for better interactive response. # #BOOT_COMCONSOLE_SPEED= 115200 # # # By default, this points to /usr/X11R6 for XFree86 releases 3.0 or earlier. # If you have a XFree86 from before 3.0 that has the X distribution in # /usr/X386, you want to uncomment this. # #X11BASE= /usr/X386 # # # If you have Motif on your system, uncomment this. # #HAVE_MOTIF= yes #MOTIF_STATIC= yes # # If the default location of the Motif library (specified below) is NOT # appropriate for you, uncomment this and change it to the correct value. # If your motif is in ${X11BASE}/lib, you don't need to touch this line. # #MOTIFLIB= -L${X11BASE}/lib -lXm # # # If you are running behind a firewall, uncomment the following to leave a # hint for various make-spawned utilities that they should use passive FTP. # #FTP_PASSIVE_MODE= YES # # If you're resident in the USA, this will help various ports to determine # whether or not they should attempt to comply with the various U.S. # export regulations on certain types of software which do not apply to # anyone else in the world. # USA_RESIDENT= NO # # Next one will help ports developers to debug # #FORCE_PKG_REGISTER= YES # # # Port master sites. # # If you want your port fetches to go somewhere else than the default # (specified below) in case the distfile/patchfile was not found, # uncomment this and change it to a location nearest you. (Don't # remove the "/${DIST_SUBDIR}/" part.) # #MASTER_SITE_BACKUP?= \ # ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/ # # If you want your port fetches to check the above site first (before # the MASTER_SITES specified in the port Makefiles), uncomment the # line below. You can also change the right side to point to wherever # you want. # #MASTER_SITE_OVERRIDE?= ${MASTER_SITE_BACKUP} # # Some ports use a special variable to point to a collection of # mirrors of well-known software archives. If you have a mirror close # to you, uncomment any of the following lines and change it to that # address. (Don't remove the "/%SUBDIR%/" part.) # # Note: the right hand sides of the following lines are only for your # information. For a full list of default sites, take a look at # bsd.port.mk. # #MASTER_SITE_XCONTRIB= ftp://ftp.x.org/contrib/%SUBDIR%/ #MASTER_SITE_GNU= ftp://prep.ai.mit.edu/pub/gnu/%SUBDIR%/ #MASTER_SITE_PERL_CPAN= ftp://ftp.digital.com/pub/plan/perl/CPAN/modules/by-module/%SUBDIR%/ #MASTER_SITE_TEX_CTAN= ftp://ftp.tex.ac.uk/tex-archive/%SUBDIR%/ #MASTER_SITE_SUNSITE= ftp://sunsite.unc.edu/pub/Linux/%SUBDIR%/ #MASTER_SITE_KDE= ftp://ftp.kde.org/pub/kde/%SUBDIR%/ #MASTER_SITE_COMP_SOURCES= ftp://gatekeeper.dec.com/pub/usenet/comp.sources.%SUBDIR%/ #MASTER_SITE_GNOME= ftp://ftp.gnome.org/pub/GNOME/sources/%SUBDIR%/ # # # Kerberos IV # If you want KerberosIV (KTH eBones), define this: # #MAKE_KERBEROS4= yes # # # Kerberos5 # If you want to install Kerberos5 somewhere other than /usr/local, # define this: # #KRB5_HOME= /usr/local/krb5 # # # CVSup update flags. Edit SUPFILE settings to reflect whichever distribution # file(s) you use on your site (see /usr/share/examples/cvsup/README for more # information on CVSup and these files). To use, do "make update" in /usr/src. # #SUP_UPDATE= yes # #SUP= /usr/local/bin/cvsup #SUPFLAGS= -g -L 2 -z #SUPFILE= /usr/share/examples/cvsup/standard-supfile #SUPFILE1= /usr/share/examples/cvsup/secure-supfile #SUPFILE2= /usr/share/examples/cvsup/ports-supfile # # top(1) uses a hash table for the user names. The size of this hash # can be tuned to match the number of local users. The table size should # be a prime number approximately twice as large as the number of lines in # /etc/passwd. The default number is 20011. # #TOP_TABLE_SIZE= 101 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 16:28:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.bc.home.com (ha1.rdc1.bc.wave.home.com [24.2.10.66]) by hub.freebsd.org (Postfix) with ESMTP id 8F3C415437 for ; Fri, 16 Apr 1999 16:28:30 -0700 (PDT) (envelope-from s1ayer@home.com) Received: from home.com ([24.113.65.122]) by mail.rdc1.bc.home.com (InterMail v4.00.03 201-229-104) with ESMTP id <19990416232607.ITXP19860.mail.rdc1.bc.home.com@home.com> for ; Fri, 16 Apr 1999 16:26:07 -0700 Message-ID: <3717C74B.62158B2F@home.com> Date: Fri, 16 Apr 1999 16:27:07 -0700 From: s1ayer@home.com Organization: @Home Network Member X-Mailer: Mozilla 4.05 [en]C-AtHome0404 (Win95; U) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: cable modem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering. Does the new version of freeBSD support my SMC-Ultra EtherEZ cable modem? If it does, I will throw away Linux and convert. Thanks in advance To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 17:18:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7D49214E34 for ; Fri, 16 Apr 1999 17:18:43 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id UAA22062 for ; Fri, 16 Apr 1999 20:16:19 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Fri, 16 Apr 1999 20:16:19 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-current@freebsd.org Subject: lnc0: broke for us between 3.1 and 4.0? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We upgraded a crash machine from 3.1-RELEASE to 4.0-CURRENT from just before the EGCS switch was pulled. The machine is a Pentium 166 MMX overdrive. Prior to the upgrade, it correctly probed the Kensington KNE 2100 (something like that) with the lnc driver as being at 0x300 irq 5 drq 6. The working 3.1-RELEASE GENERIC w/a change in the config editor probe went like: lnc0 at 0x300-0x317 irq 5 drq 6 on isa lnc0: PCnet-ISA address 00:c0:f0:00:81:f4 After upgrading to -current, the probe failed as follows (when config was used on the GENERIC quote): lnc0 at 0x300-0x317 irq 5 drq 6 on isa lnc0: Memory allocated above 16Mb limit Any suggestions as to what might done to fix it? If we switch back to the old kernel, it boots fine, so presumably it was some change between 3.1-RELEASE and 4.0-CURRENT, either in the config file or the lnc driver? Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 17:52: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-185-206.res.iastate.edu (friley-185-206.res.iastate.edu [129.186.185.206]) by hub.freebsd.org (Postfix) with ESMTP id E79021528F for ; Fri, 16 Apr 1999 17:51:58 -0700 (PDT) (envelope-from cc@137.org) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by friley-185-206.res.iastate.edu (Postfix) with ESMTP id C76728C; Fri, 16 Apr 1999 18:49:33 -0600 (CST) Received: from friley-185-205.res.iastate.edu (localhost [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 9B981121; Fri, 16 Apr 1999 19:49:32 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: current@freebsd.org Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 17 Apr 1999 05:30:41 +0800." <19990416213043.95C7B1F69@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Apr 1999 19:49:32 -0500 From: Chris Csanady Message-Id: <19990417004932.9B981121@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >As of a few minutes ago, a minimal set of changes to bring the so-called >'new-bus' functionality to the i386 kernel in -current. This seems to have broken disk wiring for me. Is there some necessary change in syntax that I am not aware of? I have the following scsi related stuff in my config file.. controller ahc0 controller ncr0 controller ncr1 controller scbus0 at ahc0 controller scbus1 at ncr0 controller scbus2 at ncr1 device da0 device cd0 device pass0 disk da0 at scbus2 target 0 disk da1 at scbus2 target 1 disk da2 at scbus1 target 2 ..and when I try to build a kernel, it fails. Also, for some reason I seem to need both the ncr0 and ncr1 or config complains. These are the error messages I get: cc -c -O2 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ioconf.c ioconf.c:111: warning: `da0_count' redefined ioconf.c:100: warning: this is the location of the previous definition ioconf.c:107: redefinition of `da0_resources' ioconf.c:98: `da0_resources' previously defined here Any ideas what the problem may be? In any case, it is very nice to see new-bus being integrated. I have been awaiting loadable PCI drivers for some time. :) Great work.. Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 17:57:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from frosch.all.de (frosch.all.de [212.21.72.2]) by hub.freebsd.org (Postfix) with ESMTP id AE2CC1528F for ; Fri, 16 Apr 1999 17:57:20 -0700 (PDT) (envelope-from luthien.iceflower.in-berlin.de!wagner@bolzen.denic.net) Received: from bolzen.denic.net (root@bolzen.all.de [212.21.76.1]) by frosch.all.de (8.9.0/8.9.0) with ESMTP id CAA01141 for ; Sat, 17 Apr 1999 02:54:52 +0200 (CEST) Received: by bolzen.denic.net (Smail3.2) id ; Sat, 17 Apr 1999 02:47:21 +0200 (MET DST) Received: (from wagner@localhost) by luthien.iceflower.in-berlin.de (8.9.2/8.8.3) id CAA31420; Sat, 17 Apr 1999 02:52:56 +0200 (MET DST) Date: Sat, 17 Apr 1999 02:52:56 +0200 (MET DST) From: Olaf Wagner Message-Id: <199904170052.CAA31420@luthien.iceflower.in-berlin.de> To: freebsd-current@freebsd.org Subject: Re: cvsup In-Reply-To: User-Agent: tin/pre-1.4-19990216 ("Styrofoam") (UNIX) (FreeBSD/3.1-STABLE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > Daniel Eischen wrote: >> John Polstra wrote: >> >>> My hunch is that it's not a fairness issue. It's just the fact that >>> when you block in disk I/O, the whole process (all threads) blocks. >> >> That statement made me think that Modula-3 had it's own threading >> support because our native threads using non-blocking file I/O. > For disk I/O? Are you sure? If so then it must use the aio/lio calls > or something similar. Disk I/O calls _always_ block, even if you've > set O_NONBLOCK on the file descriptor. The SchedulerPosix interface in m3core exports the procedures IOWait() and IOAlertWait(), which can be used to wait for a single file descriptor without stopping other threads. These procedures are used in FilePosix.IntermittentRead to implement non-blocking reading. The default implementation does not count RegularFiles as intermittent readers and writers though: REVEAL Pipe.T = IntermittentFile BRANDED OBJECT END; Terminal.T = IntermittentFile BRANDED OBJECT END; RegularFile.T = RegularFile.Public BRANDED OBJECT OVERRIDES read := RegularFileRead; write := RegularFileWrite; seek := RegularFileSeek; flush := RegularFileFlush; lock := RegularFileLock; unlock := RegularFileUnlock END; So read calls on files always block until the Unix read call returns; no other threads can run. If the O_NONBLOCK flag on fds would work for disk I/O in FreeBSD, then the code from the intermittent read procedures in FilePosix could easily be used to let the scheduler run other threads while one thread is waiting for data from a file. As John Polstra pointed out, this seems not to be possible... Aio could probably be used, but there seems to be a shortage of man pages about aio calls in FreeBSD and I haven't got my Posix book at hand, so I'm not sure how difficult this would be. -- /\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ || Olaf Wagner | wagner@luthien.in-berlin.de (private) | || Cranachstrasse 7 | wagner@elego.de (business) | || D-12157 Berlin | phone: +49 30 85 60 26 70 | || Germany / Deutschland | fax: +49 30 85 60 26 71 | \///////////////////////////////////////////////////////////////// To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 18: 0:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 833AD1528F for ; Fri, 16 Apr 1999 18:00:51 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id D38BA1F69; Sat, 17 Apr 1999 08:58:26 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Csanady Cc: current@freebsd.org Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Fri, 16 Apr 1999 19:49:32 EST." <19990417004932.9B981121@friley-185-205.res.iastate.edu> Date: Sat, 17 Apr 1999 08:58:26 +0800 From: Peter Wemm Message-Id: <19990417005827.D38BA1F69@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Csanady wrote: > > >As of a few minutes ago, a minimal set of changes to bring the so-called > >'new-bus' functionality to the i386 kernel in -current. > > This seems to have broken disk wiring for me. Is there some necessary > change in syntax that I am not aware of? > > I have the following scsi related stuff in my config file.. > > controller ahc0 > controller ncr0 > controller ncr1 > > controller scbus0 at ahc0 > controller scbus1 at ncr0 > controller scbus2 at ncr1 > > device da0 > device cd0 > device pass0 > > disk da0 at scbus2 target 0 > disk da1 at scbus2 target 1 > disk da2 at scbus1 target 2 > > ..and when I try to build a kernel, it fails. Also, for some reason I > seem to need both the ncr0 and ncr1 or config complains. These are > the error messages I get: > > cc -c -O2 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extens ions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STA CK -include opt_global.h -elf ioconf.c > ioconf.c:111: warning: `da0_count' redefined > ioconf.c:100: warning: this is the location of the previous definition > ioconf.c:107: redefinition of `da0_resources' > ioconf.c:98: `da0_resources' previously defined here > > Any ideas what the problem may be? In any case, it is very nice to see > new-bus being integrated. I have been awaiting loadable PCI drivers > for some time. :) Err, perhaps it's because you've defined da0 twice? > Great work.. > > Thanks, > Chris Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 18:47:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 11A5314CF2 for ; Fri, 16 Apr 1999 18:47:52 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id VAA20876; Fri, 16 Apr 1999 21:45:29 -0400 (EDT) (envelope-from luoqi) Date: Fri, 16 Apr 1999 21:45:29 -0400 (EDT) From: Luoqi Chen Message-Id: <199904170145.VAA20876@lor.watermarkgroup.com> To: freebsd-current@FreeBSD.ORG, jabley@patho.gen.nz Subject: Re: Consistent errors making buildworld Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you have an empty /usr/X11R6/include? The Makefile assumes you have the header files if the directory /usr/X11R6/include is present and tries to build the X version of doscmd. This assumption may not be true though. I'll change the Makefile to check for /usr/X11R6/include/X11/X.h instead. By the way, X headers only take 4M disk space, you might want to consider installing them. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 19:15:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 2DD7414C2D for ; Fri, 16 Apr 1999 19:15:13 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id VAA18328; Fri, 16 Apr 1999 21:27:10 -0500 (EST) Date: Fri, 16 Apr 1999 21:27:09 -0500 (EST) From: Alfred Perlstein To: s1ayer@home.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: cable modem In-Reply-To: <3717C74B.62158B2F@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 16 Apr 1999 s1ayer@home.com wrote: > Hi, I was wondering. Does the new version of freeBSD support my > SMC-Ultra EtherEZ cable modem? If it does, I will throw away Linux and > convert. Thanks in advance > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Why not just download a kern.flp and mfsroot.flp from : ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/ /3.1-19990416-STABLE/floppies/ 'dd' (in linux) them to a disk or use: ftp://ftp.freebsd.org/pub/FreeBSD/tools/fdimage.exe in windows to make the boot disks. boot them, and see if it can detect and use your network card, FreeBSD DOES have support for many SMC type cards. enjoy, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 20: 4:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (Postfix) with ESMTP id 758AD14F48 for ; Fri, 16 Apr 1999 20:04:51 -0700 (PDT) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.3/8.9.3) id DAA20122 for current@FreeBSD.ORG; Sat, 17 Apr 1999 03:50:48 +0100 (BST) (envelope-from aw1) Date: Sat, 17 Apr 1999 03:50:48 +0100 From: Adrian Wontroba To: current@FreeBSD.ORG Subject: Re: some news about ftp hangs Message-ID: <19990417035048.A10015@titus.stade.co.uk> Reply-To: aw1@stade.co.uk References: <199904161646.MAA17733@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904161646.MAA17733@lor.watermarkgroup.com>; from Luoqi Chen on Fri, Apr 16, 1999 at 12:46:34PM -0400 X-Operating-System: FreeBSD 4.0-CURRENT Organization: Yes, I need some of that. X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 16, 1999 at 12:46:34PM -0400, Luoqi Chen wrote: > By the way, if I turn off aliasing (set alias enable off), ftp works > fine again. With a week old current cvsupped at approx 0500 GMT on 11 April I see similar behaviour - ftp seems fine with aliasing off, but often hangs with aliasing on. -- Adrian Wontroba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 20: 9: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0153114EDD for ; Fri, 16 Apr 1999 20:08:59 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id UAA70173; Fri, 16 Apr 1999 20:06:08 -0700 (PDT) (envelope-from obrien) Message-ID: <19990416200608.A70132@nuxi.com> Date: Fri, 16 Apr 1999 20:06:08 -0700 From: "David O'Brien" To: Peter Wemm , Chris Csanady Cc: current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! Reply-To: obrien@NUXI.com References: <19990417004932.9B981121@friley-185-205.res.iastate.edu> <19990417005827.D38BA1F69@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990417005827.D38BA1F69@spinner.netplex.com.au>; from Peter Wemm on Sat, Apr 17, 1999 at 08:58:26AM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > device da0 ..snip.. > > disk da0 at scbus2 target 0 > Err, perhaps it's because you've defined da0 twice? Is this a change? For pre-POST_NEWBUS When wireing down SCSI disks, the config file has both a da0 device (to get the generic SCSI disk code) and disk (to wire it down). -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 20:21:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7385414BF1 for ; Fri, 16 Apr 1999 20:21:21 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id UAA70231; Fri, 16 Apr 1999 20:18:46 -0700 (PDT) (envelope-from obrien) Message-ID: <19990416201846.B70132@nuxi.com> Date: Fri, 16 Apr 1999 20:18:46 -0700 From: "David O'Brien" To: Greg Lehey , Warner Losh , current@FreeBSD.ORG Subject: Re: make aout-to-elf on -current? Reply-To: obrien@NUXI.com References: <199904160654.AAA07198@harmony.village.org> <19990416164237.N27806@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990416164237.N27806@lemis.com>; from Greg Lehey on Fri, Apr 16, 1999 at 04:42:37PM +0930 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 16, 1999 at 04:42:37PM +0930, Greg Lehey wrote: > On Friday, 16 April 1999 at 0:54:32 -0600, Warner Losh wrote: > > Does make aout-to-elf still purport to work from a 2.2.8R system to > > a recent (like today's) current? > > I spent a week trying to upgrade from 3.0-CURRENT of about August last > year to 4.0-CURRENT of the beginning of April. I finally gave up > going the direct way and upgraded first to 3.1-STABLE and from there > to 4.0-CURRENT. I have 22 MB of make output to show for it. Most of > the problems appear to have to do with the change in compiler. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 20:26:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0328314C2D for ; Fri, 16 Apr 1999 20:26:55 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id UAA70264; Fri, 16 Apr 1999 20:24:30 -0700 (PDT) (envelope-from obrien) Message-ID: <19990416202430.C70132@nuxi.com> Date: Fri, 16 Apr 1999 20:24:30 -0700 From: "David O'Brien" To: Warner Losh , current@FreeBSD.ORG Subject: Re: make aout-to-elf on -current? Reply-To: obrien@NUXI.com References: <199904160654.AAA07198@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904160654.AAA07198@harmony.village.org>; from Warner Losh on Fri, Apr 16, 1999 at 12:54:32AM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Does make aout-to-elf still purport to work from a 2.2.8R system to a > > recent (like today's) current? > After reading the UPDATING file, I realized just how silly a question > this was :-). a.out make world is broken in -current with egcs. Please excuse my ignorance, but why does make aout-to-elf require the -CURRENT compiler to produce a.out binaries? make aout-to-elf moves a working set of a.out libraries to ---/lib/aout, so doesn't that cover the needs? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 20:41: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 4ACEC14F6B for ; Fri, 16 Apr 1999 20:40:58 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA07152; Sat, 17 Apr 1999 13:08:33 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA35050; Sat, 17 Apr 1999 13:08:32 +0930 (CST) Message-ID: <19990417130831.D27806@lemis.com> Date: Sat, 17 Apr 1999 13:08:31 +0930 From: Greg Lehey To: obrien@NUXI.com, Peter Wemm , Chris Csanady Cc: current@FreeBSD.ORG Subject: Wiring down disks under newbus (was: HEADS UP!!!! Important instructions for -current users!) References: <19990417004932.9B981121@friley-185-205.res.iastate.edu> <19990417005827.D38BA1F69@spinner.netplex.com.au> <19990416200608.A70132@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990416200608.A70132@nuxi.com>; from David O'Brien on Fri, Apr 16, 1999 at 08:06:08PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 16 April 1999 at 20:06:08 -0700, David O'Brien wrote: >>> device da0 > ..snip.. >>> disk da0 at scbus2 target 0 > >> Err, perhaps it's because you've defined da0 twice? > > Is this a change? For pre-POST_NEWBUS When wireing down SCSI disks, the > config file has both a da0 device (to get the generic SCSI disk code) and > disk (to wire it down). It doesn't have to. I have only one reference in my config: device da0 at scbus1 target 0 unit 0 So what's the difference in semantics between a 'device' entry and a 'disk' entry? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 21:25:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4539A14C45 for ; Fri, 16 Apr 1999 21:25:28 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA50498; Fri, 16 Apr 1999 22:22:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA12900; Fri, 16 Apr 1999 22:22:59 -0600 (MDT) Message-Id: <199904170422.WAA12900@harmony.village.org> To: obrien@NUXI.com Subject: Re: make aout-to-elf on -current? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 16 Apr 1999 20:24:30 PDT." <19990416202430.C70132@nuxi.com> References: <19990416202430.C70132@nuxi.com> <199904160654.AAA07198@harmony.village.org> Date: Fri, 16 Apr 1999 22:22:59 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990416202430.C70132@nuxi.com> "David O'Brien" writes: : Please excuse my ignorance, but why does make aout-to-elf require the : -CURRENT compiler to produce a.out binaries? : : make aout-to-elf moves a working set of a.out libraries to ---/lib/aout, : so doesn't that cover the needs? No. make aout-to-elf builds a.out versions of everything first, then uses them to build the elf versions. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 22: 4:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B993D1514C for ; Fri, 16 Apr 1999 22:04:41 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id WAA70579 for current@freebsd.org; Fri, 16 Apr 1999 22:02:18 -0700 (PDT) (envelope-from obrien) Message-ID: <19990416220218.A70569@nuxi.com> Date: Fri, 16 Apr 1999 22:02:18 -0700 From: "David O'Brien" To: current@freebsd.org Subject: Re: Wiring down disks under newbus (was: HEADS UP!!!! Important instructions for -current users!) Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> It doesn't have to. I have only one reference in my config: > >> > >> device da0 at scbus1 target 0 unit 0 I commented out my "device da0" and changed all my "disk"'s (16 of them across two controlers) to "devices"'s and I was able to config and build a kernel. So the distinction between "disk" and "device" isn't what I thought it was. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 22:26:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 3BAD314EFA for ; Fri, 16 Apr 1999 22:26:49 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id BAA12731 for ; Sat, 17 Apr 1999 01:24:31 -0400 (EDT) Date: Sat, 17 Apr 1999 01:24:26 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: new-bus breaks both sound drivers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Both sound drivers are broken with the new-bus code. My SB16, in the old driver, now gets recognized but sbxvi is never looked for. pcm0, the new driver, never initializes with the new code :( device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 6 #device sbmidi0 at isa? port 0x330 #device opl0 at isa? port 0x388 Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \\__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 22:31:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B091814F4A for ; Fri, 16 Apr 1999 22:31:42 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id OAA09498; Sat, 17 Apr 1999 14:29:05 +0900 (JST) Message-ID: <371819E8.3A8E0432@newsguy.com> Date: Sat, 17 Apr 1999 14:19:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Warner Losh Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: make aout-to-elf on -current? References: <19990416202430.C70132@nuxi.com> <199904160654.AAA07198@harmony.village.org> <199904170422.WAA12900@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <19990416202430.C70132@nuxi.com> "David O'Brien" writes: > : Please excuse my ignorance, but why does make aout-to-elf require the > : -CURRENT compiler to produce a.out binaries? > : > : make aout-to-elf moves a working set of a.out libraries to ---/lib/aout, > : so doesn't that cover the needs? > > No. make aout-to-elf builds a.out versions of everything first, then > uses them to build the elf versions. Correct. Older compilers would not be able to generate elf targets, so we have to update the compiler first. The system actually makes a complete world first, because of arcane reasons better left unexplained, lest one would gradually become insane. For the details, man cthulhu(9). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 22:33:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 8186B1511A for ; Fri, 16 Apr 1999 22:33:09 -0700 (PDT) (envelope-from norn@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id A7E1B1680; Fri, 16 Apr 1999 22:30:43 -0700 (PDT) Content-Length: 772 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 16 Apr 1999 22:30:43 -0800 (PDT) Reply-To: Chris Piazza From: Chris Piazza To: Brian Feldman Subject: RE: new-bus breaks both sound drivers Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Apr-99 Brian Feldman wrote: > Both sound drivers are broken with the new-bus code. My SB16, in the old > driver, now gets recognized but sbxvi is never looked for. pcm0, the new > driver, never initializes with the new code :( > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 > The pcm0 sounddriver works for me. In fact, the only problem I had with new bus was it is now pcm0 instead of pcm1 ;-). es0: at device 9.0 on pci0 pcm0: using I/O space register mapping at 0xd800 es0: interrupting at irq 4 device pcm0 I'm using it right now, actually. Of course, this is a PCI card so there could be/is a difference. --- Chris Piazza Abbotsford, BC, Canada cpiazza@home.net finger norn@norn.ca.eu.org for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 22:37:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 46ED214EFA for ; Fri, 16 Apr 1999 22:37:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id WAA70702; Fri, 16 Apr 1999 22:35:21 -0700 (PDT) (envelope-from obrien) Message-ID: <19990416223520.A70668@nuxi.com> Date: Fri, 16 Apr 1999 22:35:20 -0700 From: "David O'Brien" To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: make aout-to-elf on -current? Reply-To: obrien@NUXI.com References: <19990416202430.C70132@nuxi.com> <199904160654.AAA07198@harmony.village.org> <199904170422.WAA12900@harmony.village.org> <371819E8.3A8E0432@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <371819E8.3A8E0432@newsguy.com>; from Daniel C. Sobral on Sat, Apr 17, 1999 at 02:19:36PM +0900 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > No. make aout-to-elf builds a.out versions of everything first, then > > uses them to build the elf versions. > > Correct. Older compilers would not be able to generate elf targets, > so we have to update the compiler first. Right. But the 2.x system should build the compiler (and bootstrap libs) statically and install them in /usr/obj/..../tmp. Then the "make world" should stop dead in its tracks and use the compiler in /usr/obj/..../tmp [which itself is an a.out binary] to start a new "make world" where the output are ELF images. I've glossed over a little bit here -- I think maybe we need a /usr/src/Makefile.aout-to-elf and the upgrade path is now: make -f Makefile.aout-to-elf {,buildworld,installworld} > The system actually makes a complete world first, because of arcane > reasons better left unexplained, True.. and I bumped into the same mess in the compiler upgrade > lest one would gradually become insane. As I did in the EGCS bootstrap. ;-) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 16 22:49:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 3D4911519A for ; Fri, 16 Apr 1999 22:49:03 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.2/8.8.5) with ESMTP id MAA06066; Sat, 17 Apr 1999 12:45:58 +0700 (NSS) Date: Sat, 17 Apr 1999 12:45:58 +0700 (NSS) From: Max Khon To: Robert Watson Cc: freebsd-current@FreeBSD.ORG Subject: Re: lnc0: broke for us between 3.1 and 4.0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Fri, 16 Apr 1999, Robert Watson wrote: > We upgraded a crash machine from 3.1-RELEASE to 4.0-CURRENT from just > before the EGCS switch was pulled. The machine is a Pentium 166 MMX > overdrive. Prior to the upgrade, it correctly probed the Kensington KNE > 2100 (something like that) with the lnc driver as being at 0x300 irq 5 > drq 6. > > The working 3.1-RELEASE GENERIC w/a change in the config editor probe went > like: > > lnc0 at 0x300-0x317 irq 5 drq 6 on isa > lnc0: PCnet-ISA address 00:c0:f0:00:81:f4 > > After upgrading to -current, the probe failed as follows (when config was > used on the GENERIC quote): > > lnc0 at 0x300-0x317 irq 5 drq 6 on isa > lnc0: Memory allocated above 16Mb limit > > Any suggestions as to what might done to fix it? If we switch back to the > old kernel, it boots fine, so presumably it was some change between > 3.1-RELEASE and 4.0-CURRENT, either in the config file or the lnc driver? i had lnc (AMD PCNet) driver which uses 32-bit mode but it does not work with older (16bit) AMD PCNet cards. Maybe someone should take a look at it and merge with current lnc driver (as I do not have these cards anymore)? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 0: 8:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 849FD14D74 for ; Sat, 17 Apr 1999 00:08:45 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (async2-53.iptelecom.net.ua [212.42.68.181]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id KAA11324 for ; Sat, 17 Apr 1999 10:07:29 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37183314.F597AE6@altavista.net> Date: Sat, 17 Apr 1999 10:07:00 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Current kernel can't execute gzip'ed ELF executables! Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, If seems that 4.0-current (make world & kernel as of yesterday) can't execute ELF gzip'ed binaries with following symptoms: sh-2.02# cp /bin/sh ./ sh-2.02# gzip sh sh-2.02# ls -l total 177 -rw-r--r-- 1 root wheel 43 Apr 17 09:58 Report -r-xr-xr-x 1 root wheel 170093 Apr 17 09:58 sh.gz sh-2.02# mv sh.gz sh sh-2.02# ls -l total 177 -rw-r--r-- 1 root wheel 253 Apr 17 09:58 Report -r-xr-xr-x 1 root wheel 170093 Apr 17 09:58 sh sh-2.02# ./sh sh: ./sh: cannot execute binary file In dmesg I have: Output=32 Inflate_error=1 igz.error=8 error2=0 where=180 This misbehavior verified on two machines. Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 0:28:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id CC31B14EA1 for ; Sat, 17 Apr 1999 00:28:22 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 578211F69; Sat, 17 Apr 1999 15:25:56 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-reply-to: Your message of "Fri, 16 Apr 1999 22:30:43 PST." Date: Sat, 17 Apr 1999 15:25:56 +0800 From: Peter Wemm Message-Id: <19990417072558.578211F69@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Piazza wrote: > On 17-Apr-99 Brian Feldman wrote: > > Both sound drivers are broken with the new-bus code. My SB16, in the old > > driver, now gets recognized but sbxvi is never looked for. pcm0, the new > > driver, never initializes with the new code :( > > > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 > > > > The pcm0 sounddriver works for me. In fact, the only problem I had with new > bus was it is now pcm0 instead of pcm1 ;-). > > es0: at device 9.0 on pci0 > pcm0: using I/O space register mapping at 0xd800 > es0: interrupting at irq 4 > > device pcm0 On two different systems it works for me using pcm0.. This is an ESS clone card: Probing for PnP devices: CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0 d041] ESS1868 (rev 11) pcm1 (ESS1868 sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 on isa This is an on-board Crystal SB-like PnP device: Probing for PnP devices: CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000 0000] mss_attach 1 at 0x530 irq 5 dma 1:0 flags 0x10 pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 fl ags 0x10 on isa For what it's worth, PnP has for the most part not been changed under new-bus and is using the old mechanisms. The only significant risk is that the attach code doesn't like what I've done with the emulation of isa_device->id_id for "unit numbers". I'm sorry, you're going to need to have a bit of a look around and turning on or inserting some debug code to see what's happening. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 0:38:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 82B7D14DA8 for ; Sat, 17 Apr 1999 00:38:23 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA67808; Sat, 17 Apr 1999 00:36:00 -0700 (PDT) (envelope-from dillon) Date: Sat, 17 Apr 1999 00:36:00 -0700 (PDT) From: Matthew Dillon Message-Id: <199904170736.AAA67808@apollo.backplane.com> To: current@FreeBSD.ORG Subject: successfull SMP / current on duel P-III box. Yahhhh. I've successfully brought -current up in SMP on a duel P-III box. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have one problem, though. During the kernel boot: isa_dmainit(2, 1024) failed And, of course, any access to something that needs isa dma (e.g. floppy) panics. It's a large-memory machine (1G). I was under the impression that this was supposed to be fixed in the vm/vm_page.c commit: vm/vm_page.c revision 1.128 date: 1999/03/19 05:21:03; author: alc; state: Exp; lines: +8 -2 Construct the free queue(s) in descending order (by physical address) so that the first 16MB of physical memory is allocated last rather than first. On large-memory machines, this avoids the exhaustion of low physical memory before isa_dmainit has run. Anyone have any ideas? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 2:30:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 2524214C07 for ; Sat, 17 Apr 1999 02:30:30 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id LAA02313 for current@FreeBSD.ORG; Sat, 17 Apr 1999 11:28:06 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 4627087B6; Sat, 17 Apr 1999 11:14:00 +0200 (CEST) Date: Sat, 17 Apr 1999 11:14:00 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! Message-ID: <19990417111400.A2477@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19990417004932.9B981121@friley-185-205.res.iastate.edu> <19990417005827.D38BA1F69@spinner.netplex.com.au> <19990416200608.A70132@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990416200608.A70132@nuxi.com>; from David E . O'Brien on Fri, Apr 16, 1999 at 08:06:08PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David E . O'Brien: > Is this a change? For pre-POST_NEWBUS When wireing down SCSI disks, the > config file has both a da0 device (to get the generic SCSI disk code) and > disk (to wire it down). I've never defined da* twice in oldconfig-style config. You're not supposed to do that I think. In LINT, there is only one definition. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 4: 5:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 9A80615025 for ; Sat, 17 Apr 1999 04:05:10 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id NAA05980 for current@freebsd.org; Sat, 17 Apr 1999 13:02:47 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 2369C87B6; Sat, 17 Apr 1999 13:01:05 +0200 (CEST) Date: Sat, 17 Apr 1999 13:01:05 +0200 From: Ollivier Robert To: current@freebsd.org Subject: Re: HEADS UP!!!! Important instructions for -current users! Message-ID: <19990417130105.A3457@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <19990416213043.95C7B1F69@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990416213043.95C7B1F69@spinner.netplex.com.au>; from Peter Wemm on Sat, Apr 17, 1999 at 05:30:41AM +0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Peter Wemm: > As a special warning: The APIC_IO interrupt management could be a little > wonky on systems that require the special mptable fixups. If you have > warnings about broken mptables, or additional interrupts being wired, > hold back until it's been checked. Seems to work fine on my 2x PPro/200, Intel Providence MB, 64 MB, SMP. I've built but not yet tested the new fxp.ko module though. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #15: Sat Apr 17 12:33:10 CEST 1999 roberto@tara:/src/src/sys/compile/TARA_SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 67108864 (65536K bytes) avail memory = 62119936 (60664K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0307000. Preloaded elf module "nfs.ko" at 0xc030709c. Preloaded elf module "linux.ko" at 0xc0307138. Preloaded elf module "green_saver.ko" at 0xc03071d8. Preloaded elf module "procfs.ko" at 0xc030727c. Pentium Pro MTRR support enabled, default memory type is uncacheable npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 fxp0: at device 6.0 on pci0 fxp0: interrupting at irq 18 fxp0: Ethernet address 00:a0:c9:49:5a:ef isab0: at device 7.0 on pci0 isa0: on isab0 uhci0: at device 7.2 on pci0 uhci0: interrupting at irq 10 usb0: on uhci0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ahc0: at device 9.0 on pci0 ahc0: interrupting at irq 17 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <10 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0 at port 0x378 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 APIC_IO: routing 8254 via 8259 on pin 0 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 4: 8:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 0C91815025 for ; Sat, 17 Apr 1999 04:08:14 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id XAA23765; Sat, 17 Apr 1999 23:05:50 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id XAA11167; Sat, 17 Apr 1999 23:05:49 +1200 (NZST) (envelope-from jabley) Date: Sat, 17 Apr 1999 23:05:49 +1200 From: Joe Abley To: Luoqi Chen Cc: freebsd-current@FreeBSD.ORG Subject: Re: Consistent errors making buildworld Message-ID: <19990417230549.A11102@clear.co.nz> References: <199904170145.VAA20876@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904170145.VAA20876@lor.watermarkgroup.com>; from Luoqi Chen on Fri, Apr 16, 1999 at 09:45:29PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 16, 1999 at 09:45:29PM -0400, Luoqi Chen wrote: > Do you have an empty /usr/X11R6/include? Ah, yes I do. Thanks for that :) > The Makefile assumes you have the > header files if the directory /usr/X11R6/include is present and tries to > build the X version of doscmd. This assumption may not be true though. I'll > change the Makefile to check for /usr/X11R6/include/X11/X.h instead. By the > way, X headers only take 4M disk space, you might want to consider installing > them. Hav done. I'm a little confused as to why they weren't there already, actually, as I was certain I had compiled and installed XFree86 from the port... Ah well :) Whatever. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 4:34:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from work.mzaki.nom (3.pool6.tokyo.att.ne.jp [165.76.23.18]) by hub.freebsd.org (Postfix) with ESMTP id 2A16814D23; Sat, 17 Apr 1999 04:34:36 -0700 (PDT) (envelope-from mzaki@e-mail.ne.jp) Received: from localhost (localhost [127.0.0.1]) by work.mzaki.nom (8.9.2/8.9.2) with ESMTP id UAA00437; Sat, 17 Apr 1999 20:31:52 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) To: freebsd-gnats-submit@freebsd.org, keith@email.gcn.net.tw, dcs@newsguy.com Cc: byung@wam.umd.edu, joki@kuebart.stuttgart.netsurf.de, freebsd-current@freebsd.org Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. In-Reply-To: <19990414151257E.mzaki@e-mail.ne.jp> References: <19990414151257E.mzaki@e-mail.ne.jp> X-Mailer: Mew version 1.94b7 on XEmacs 21.0 (20 minutes to Nikko) X-fingerprint: BD 86 CD D9 66 FD 75 B0 A8 43 4B C4 E2 1B F5 B5 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990417203151E.mzaki@e-mail.ne.jp> Date: Sat, 17 Apr 1999 20:31:51 +0900 From: Motomichi Matsuzaki X-Dispatcher: imput version 990212(IM106) Lines: 83 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey! I've add UNICODE support to the Joliet patch. It contains few charsets now, but to add other charsets is very easy. Currently, iso8859-1 and euc-jp is included. Mixture of Joliet/RockRidge Extension is also available, however untested. How to use: 1. Pick up the patch from the URL. http://triaez.kaisei.org/~mzaki/joliet/joliet.unicode.patch.gz It contains huge table which provides conversion from unicode character to euc-jp, so that the gzip'ed size is 36k. So I give up to attach the patch to this mail. 2. Apply the patch to the source tree. #cd /usr/src #zcat /tmp/joliet.unicode.patch.gz|patch -p1 3. Make and install new mount_cd9660(8) #cd /usr/src/sbin/mount_cd9660 #make; make install 4. Reconfig and reinstall your kernel and reboot. 5. Tell your kernel the charset you prefer. #sysctl -w vfs.charset=iso8859-1 Currently, only 'none', 'iso8859-1' and 'euc-jp' is available. none : The filenames are assumed to have 8bit character ONLY. This is not recommended. iso8859-1 : 8bit characters. All 16bit characters (include russian, greek, chinese, etc.) are replaced with numerical ('0'-'9'). euc-jp : Japanese characters. This corresponds to the userland locale 'ja_JP.EUC'. All characters unable to express are replaced with numerical ('0'-'9'). How to use other charsets: 1. Look at the /sys/isofs. charset and encoding directories are added. For Europians, to make new charset/*.c is sufficient. For Asians (Chinese, Korean, Japanese and so on), to make new encoding/*.c is also required. charset/*.c should contains Code Conversion Table. Currently, only 'UNICODE -> local charset' conversion is needed. (in future, reverse conversion may needed for msdosfs and ntfs.) encoding/*.c should contains multibyte encoding routines. These are subset of rune(3) at /usr/src/lib/libc/locale/ At least, MSKanji is required for ja_JP.SJIS, BIG5 for zh_TW.BIG5, also UTF-8 for all UNICODE locale. 2. Add new file entries to /sys/conf/files 3. Reconfig and reinstall your kernel and reboot. More documents are now scheduled in some days at the URL http://triaez.kaisei.org/~mzaki/joliet/ -- Motomichi Matsuzaki Dept. of Biological Science, Fuculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 5:41:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id EC1A5151EB for ; Sat, 17 Apr 1999 05:41:37 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA17781; Sat, 17 Apr 1999 22:09:34 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA10605; Sat, 17 Apr 1999 22:09:34 +0930 Date: Sat, 17 Apr 1999 22:09:30 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Maxim Sobolev Cc: current@freebsd.org Subject: Re: Current kernel can't execute gzip'ed ELF executables! In-Reply-To: <37183314.F597AE6@altavista.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Maxim Sobolev wrote: > If seems that 4.0-current (make world & kernel as of yesterday) can't > execute ELF gzip'ed binaries with following symptoms: I enquired about this a few months ago (but didn't hear anything in reply). As far as I've been able to work out, the facility was never intended to work with ELF executables because no-one's updated it from using a.out executables. It's a shame since that can be quite useful on machines where disk space is tight, but I have no idea how hard it will be to get working again. Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 5:47:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B2CEE14D5F for ; Sat, 17 Apr 1999 05:47:10 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id OAA64600; Sat, 17 Apr 1999 14:44:43 +0200 (CEST) (envelope-from des) To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: Current kernel can't execute gzip'ed ELF executables! References: <37183314.F597AE6@altavista.net> From: Dag-Erling Smorgrav Date: 17 Apr 1999 14:44:42 +0200 In-Reply-To: Maxim Sobolev's message of "Sat, 17 Apr 1999 10:07:00 +0300" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev writes: > If seems that 4.0-current (make world & kernel as of yesterday) can't > execute ELF gzip'ed binaries with following symptoms: It never could, AFAIK. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 6:48: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from heaven.gigo.com (ppp.gigo.com [207.173.132.1]) by hub.freebsd.org (Postfix) with ESMTP id 24ED514CCB for ; Sat, 17 Apr 1999 06:48:05 -0700 (PDT) (envelope-from jfesler@gigo.com) Received: from heaven.gigo.com (heaven.gigo.com [207.173.133.57]) by heaven.gigo.com (Postfix) with ESMTP id 32C2C1B0; Sat, 17 Apr 1999 06:45:40 -0700 (PDT) Date: Sat, 17 Apr 1999 06:45:40 -0700 (PDT) From: To: Kris Kennaway Cc: Maxim Sobolev , current@freebsd.org Subject: Re: Current kernel can't execute gzip'ed ELF executables! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's a shame since that can be quite useful on machines where disk space is > tight, but I have no idea how hard it will be to get working again. Use "gzexe" - the old fashioned way of doing things. If anyone does actually want it fixed, on a minimum, man send-pr .. I don't see anything related posted there right now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 6:56:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-185-206.res.iastate.edu (friley-185-206.res.iastate.edu [129.186.185.206]) by hub.freebsd.org (Postfix) with ESMTP id 27F2C14EBB for ; Sat, 17 Apr 1999 06:56:27 -0700 (PDT) (envelope-from cc@137.org) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by friley-185-206.res.iastate.edu (Postfix) with ESMTP id 4F5BCA6; Sat, 17 Apr 1999 07:53:46 -0600 (CST) Received: from friley-185-205.res.iastate.edu (localhost [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id D47DBAC; Sat, 17 Apr 1999 08:53:45 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-reply-to: Your message of "Sat, 17 Apr 1999 15:25:56 +0800." <19990417072558.578211F69@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 17 Apr 1999 08:53:45 -0500 From: Chris Csanady Message-Id: <19990417135345.D47DBAC@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Chris Piazza wrote: >> On 17-Apr-99 Brian Feldman wrote: >> > Both sound drivers are broken with the new-bus code. My SB16, in the old >> > driver, now gets recognized but sbxvi is never looked for. pcm0, the new >> > driver, never initializes with the new code :( >> > >> > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 >> > >> >> The pcm0 sounddriver works for me. In fact, the only problem I had with new >> bus was it is now pcm0 instead of pcm1 ;-). >> >> es0: at device 9.0 on pci0 >> pcm0: using I/O space register mapping at 0xd800 >> es0: interrupting at irq 4 >> >> device pcm0 > >On two different systems it works for me using pcm0.. > >This is an ESS clone card: > >Probing for PnP devices: >CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: PNPb02f [0x2f b0 >d041] >ESS1868 (rev 11) >pcm1 (ESS1868 sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 on isa > >This is an on-board Crystal SB-like PnP device: > >Probing for PnP devices: >CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0xffffffff Comp ID: @@@0000 [0x00 00 >0000] >mss_attach 1 at 0x530 irq 5 dma 1:0 flags 0x10 >pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 fl >ags 0x10 on isa > >For what it's worth, PnP has for the most part not been changed under >new-bus and is using the old mechanisms. The only significant risk is that >the attach code doesn't like what I've done with the emulation of >isa_device->id_id for "unit numbers". I thought PnP was not even using new-bus yet?! I haven't used PnP in a long time, but the pcm driver is broke for me too. I have used the following successfully with just the plain isa0 for quite some time.. device pcm0 at isa? port? tty irq 5 drq 1 flags 0x10 >I'm sorry, you're going to need to have a bit of a look around and turning >on or inserting some debug code to see what's happening. Where should I start? It doesn't print out anything upon boot.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 8: 3: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 50DAC14D39 for ; Sat, 17 Apr 1999 08:03:00 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-63.camtech.net.au [203.55.243.191]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id AAA26829; Sun, 18 Apr 1999 00:28:59 +0930 (CST) Message-ID: <3718A086.17CA6F9E@camtech.net.au> Date: Sun, 18 Apr 1999 00:23:58 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Natty Rebel Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: Lastest ATA/ATAPI driver boots with kernel.debug only. References: <19990414005818.A15299@matti.ee> <199904140626.IAA07777@freebsd.dk> <19990414111731.B851@ikhala.tcimet.net> Content-Type: multipart/mixed; boundary="------------C008FDD2BEBFED14E03ADE07" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------C008FDD2BEBFED14E03ADE07 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I've found that I need to disable my secondary IDE controller with the version 5 and 6 of the new ATAPI drivers. It's probably something to do with Ultra DMA support as I have an Ultra DMA 6.48 GB IBM drive on my IDE controller 0 (master) and a Ultra DMA Mitsubishi 32 spin CD-ROM drive as slave on my second IDE controller. By the way, the IBM 6.48 GB drive is working fine in UDMA2... Lovely. Too bad my drive cant do tagged queueing. There must be a problem with the UDMA CDROMs as with my second IDE controller enabled, I never boot it just never gets to the "changing root device to" bit. dmesg attached with second controller disabled.... also old boot messages attached for ATAPI driver version 4 when I could have the controller enabled. Natty Rebel wrote: > > Hello Soren and other -current users, > I've used your new ATA/ATAPI driver flawlessly through the 4th version. > I was not able to get past the 'changing root device to wd0s1a' message > with version 5, so I just went back to the wd driver. Last nigh I tried > version 6 and ran into the same problem. I finally decided to do a little > investigating. First I found that I could do a 'ctrl-alt-del' to reboot. > I then decided to install the debug kernel doing a 'make install.debug' > in my kernel build directory. Lo! and behold! to my surprise my box > booted flawlessly. The questions I have are > > 1) Why did the debug kernel boot and not the kernel without debug symbols? > 2) What procedures/tools should I use to investigate this further? > > Of course any help/pointers are appreciated ... > > Thanxs. > > #;^) > i'khala > -- > natty rebel > harder than the rest ... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------C008FDD2BEBFED14E03ADE07 Content-Type: text/plain; charset=us-ascii; name="DMESG" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="DMESG" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Apr 16 23:03:56 CST 1999 matt@localhost:/usr/src/sys/compile/MATTE Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (463.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping=0 Features=0x183f9ff real memory = 67108864 (65536K bytes) config> pnp 1 0 bios enable avail memory = 62177280 (60720K bytes) Preloaded elf kernel "kernel" at 0xc02eb000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02eb09c. Preloaded elf module "splash_bmp.ko" at 0xc02eb0ec. Pentium Pro MTRR support enabled, default memory type is uncacheable module_register_init: module_register(splash_bmp, c02e760c, 0) error 2 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ata-pci0: rev 0x01 on pci0.7.1 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 intpm0: rev 0x02 on pci0.7.3 intpm0: I/O mapped 5000 ALLOCED IRQ 0 intr IRQ 9 enabled revision 0 intsmb0: smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 vga0: rev 0x30 int a irq 255 on pci0.11.0 ncr0: rev 0x02 int a irq 11 on pci0.13.0 Probing for devices on PCI bus 1: Probing for PnP devices: CSN 1 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100a1ec0 Comp ID: PNP0600 [0x0006d041] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <12 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 9 on isa ed0: address 00:00:e8:20:33:e8, type NE2000 (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ppc0 not found vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 joy0 at 0x201 on isa joy0: joystick sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-3 disk at ata0 as master ad0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s2a ffs_mountfs: superblock updated for soft updates ed0: device timeout --------------C008FDD2BEBFED14E03ADE07 Content-Type: text/plain; charset=us-ascii; name="DMESG.old" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="DMESG.old" Mar 28 19:25:27 localhost /kernel: Copyright (c) 1992-1999 The FreeBSD Project. Mar 28 19:25:27 localhost /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Mar 28 19:25:27 localhost /kernel: The Regents of the University of California. All rights reserved. Mar 28 19:25:27 localhost /kernel: FreeBSD 4.0-CURRENT #0: Sat Mar 27 11:42:24 CST 1999 Mar 28 19:25:27 localhost /kernel: matt@localhost:/usr/src/sys/compile/MATTE Mar 28 19:25:27 localhost /kernel: Timecounter "i8254" frequency 1193182 Hz Mar 28 19:25:27 localhost /kernel: CPU: Celeron (463.91-MHz 686-class CPU) Mar 28 19:25:27 localhost /kernel: Origin = "GenuineIntel" Id = 0x660 Stepping=0 Mar 28 19:25:27 localhost /kernel: Features=0x183f9ff Mar 28 19:25:27 localhost /kernel: real memory = 67108864 (65536K bytes) Mar 28 19:25:27 localhost /kernel: config> pnp 1 0 bios enable Mar 28 19:25:27 localhost /kernel: avail memory = 62164992 (60708K bytes) Mar 28 19:25:27 localhost /kernel: Preloaded elf kernel "kernel" at 0xc02ee000. Mar 28 19:25:27 localhost /kernel: Preloaded userconfig_script "/boot/kernel.conf" at 0xc02ee09c. Mar 28 19:25:27 localhost /kernel: Probing for devices on PCI bus 0: Mar 28 19:25:27 localhost /kernel: chip0: rev 0x03 on pci0.0.0 Mar 28 19:25:27 localhost /kernel: chip1: rev 0x03 on pci0.1.0 Mar 28 19:25:27 localhost /kernel: chip2: rev 0x02 on pci0.7.0 Mar 28 19:25:27 localhost /kernel: ata-pci0: rev 0x01 on pci0.7.1 Mar 28 19:25:27 localhost /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Mar 28 19:25:27 localhost /kernel: ata1 at 0 Mar 28 19:25:27 localhost /kernel: x0170 irq 15 on ata-pci0 Mar 28 19:25:27 localhost /kernel: uhci0: rev 0x01 int d irq 11 on pci0.7.2 Mar 28 19:25:27 localhost /kernel: usb0: USB version 1.0, chip rev. 1 Mar 28 19:25:27 localhost /kernel: intpm0: rev 0x02 on pci0.7.3 Mar 28 19:25:27 localhost /kernel: intpm0: I/O mapped 5000 ALLOCED IRQ 0 intr IRQ 9 enabled revision 0 Mar 28 19:25:27 localhost /kernel: intsmb0: Mar 28 19:25:27 localhost /kernel: smbus0: on intsmb0 Mar 28 19:25:27 localhost /kernel: smb0: on smbus0 Mar 28 19:25:27 localhost /kernel: intpm0: PM I/O mapped 4000 Mar 28 19:25:27 localhost /kernel: vga0: rev 0x30 int a irq 255 on pci0.11.0 Mar 28 19:25:27 localhost /kernel: ncr0: rev 0x02 int a irq 7 on pci0.13.0 Mar 28 19:25:27 localhost /kernel: Probing for devices on PCI bus 1: Mar 28 19:25:27 localhost /kernel: Probing for PnP devices: Mar 28 19:25:27 localhost /kernel: CSN 1 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100a1ec0 Comp ID: PNP0600 [0x0006d041] Mar 28 19:25:27 localhost /kernel: Probing for devices on the ISA bus: Mar 28 19:25:27 localhost /kernel: sc0 on isa Mar 28 19:25:27 localhost /kernel: sc0: VGA color <12 virtual consoles, flags=0x0> Mar 28 19:25:27 localhost /kernel: ed0 at 0x300-0x31f irq 9 on isa Mar 28 19:25:27 localhost /kernel: ed0: address 00:00:e8:20:33:e8, type NE2000 (16 bit) Mar 28 19:25:27 localhost /kernel: atkbdc0 at 0x60-0x6f on motherboard Mar 28 19:25:27 localhost /kernel: atkbd0 irq 1 on isa Mar 28 19:25:27 localhost /kernel: psm0 irq 12 on isa Mar 28 19:25:27 localhost /kernel: psm0: model Generic PS/2 mouse, Mar 28 19:25:27 localhost /kernel: device ID 0 Mar 28 19:25:27 localhost /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Mar 28 19:25:27 localhost /kernel: sio0: type 16550A Mar 28 19:25:27 localhost /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Mar 28 19:25:27 localhost /kernel: sio1: type 16550A Mar 28 19:25:27 localhost /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Mar 28 19:25:27 localhost /kernel: fdc0: FIFO enabled, 8 bytes threshold Mar 28 19:25:27 localhost /kernel: fd0: 1.44MB 3.5in Mar 28 19:25:27 localhost /kernel: ppc0 not found Mar 28 19:25:27 localhost /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Mar 28 19:25:27 localhost /kernel: npx0 on motherboard Mar 28 19:25:27 localhost /kernel: npx0: INT 16 interface Mar 28 19:25:27 localhost /kernel: apm0 on isa Mar 28 19:25:27 localhost /kernel: apm: found APM BIOS version 1.2 Mar 28 19:25:27 localhost /kernel: joy0 at 0x201 on isa Mar 28 19:25:27 localhost /kernel: joy0: joystick Mar 28 19:25:27 localhost /kernel: sb0 at 0x220 irq 5 drq 1 on isa Mar 28 19:25:27 localhost /kernel: snd0: Mar 28 19:25:27 localhost /kernel: sbxvi0 at drq 5 on isa Mar 28 19:25:27 localhost /kernel: snd0: Mar 28 19:25:27 localhost /kernel: sbmidi0 at 0x330 on isa Mar 28 19:25:27 localhost /kernel: snd0: Mar 28 19:25:27 localhost /kernel: opl0 at 0x388 on isa Mar 28 19:25:27 localhost /kernel: snd0: Mar 28 19:25:27 localhost /kernel: usbd_match Mar 28 19:25:27 localhost /kernel: usb0: Mar 28 19:25:27 localhost /kernel: usbd_attach Mar 28 19:25:27 localhost /kernel: usbd_new_device bus=0xc07bd000 depth=0 lowspeed=0 Mar 28 19:25:27 localhost /kernel: usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=0, protocol=0, maxpacket=64, ls=0 Mar 28 19:25:27 localhost /kernel: usbd_new_device: new dev (addr 1), dev=0xc05ae480, parent=0xc07ba0c0 Mar 28 19:25:27 localhost /kernel: uhub0 at usb0 Mar 28 19:25:27 localhost /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 28 19:25:27 localhost /kernel: usbd_set_config_index: (addr 1) attr=0x Mar 28 19:25:27 localhost /kernel: 40, selfpowered=1, power=0, powerquirk=0 Mar 28 19:25:27 localhost /kernel: usbd_set_config_index: set config 1 Mar 28 19:25:27 localhost /kernel: usbd_set_config_index: setting new config 1 Mar 28 19:25:27 localhost /kernel: uhub0: 2 ports with 2 removable, self powered Mar 28 19:25:27 localhost /kernel: usbd_init_port: adding hub port=1 status=0x0100 change=0x0000 Mar 28 19:25:27 localhost /kernel: usbd_init_port: adding hub port=2 status=0x0100 change=0x0000 Mar 28 19:25:27 localhost /kernel: ata1: unwanted interrupt Mar 28 19:25:27 localhost /kernel: ad0: ATA-3 disk at ata0 as master Mar 28 19:25:27 localhost /kernel: ad0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S Mar 28 19:25:27 localhost /kernel: ad0: 16 secs/int, 0 depth queue Mar 28 19:25:27 localhost /kernel: atapi_transfer: bad command phase Mar 28 19:25:27 localhost /kernel: acd0: CDROM drive at ata1 as slave Mar 28 19:25:27 localhost /kernel: ata1: unwanted interrupt Mar 28 19:25:27 localhost /kernel: acd0: drive speed 0KB/secacd0: supported read types: Mar 28 19:25:27 localhost /kernel: acd0: Mechanism: caddy Mar 28 19:25:27 localhost /kernel: acd0: Medium: CD-ROM unknown medium Mar 28 19:25:27 localhost /kernel: changing root device to ad0s2a --------------C008FDD2BEBFED14E03ADE07-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 8: 9:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 8D2A914D39 for ; Sat, 17 Apr 1999 08:09:32 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 0EDD21F5D; Sat, 17 Apr 1999 23:07:05 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Thyer Cc: Natty Rebel , Soren Schmidt , current@FreeBSD.ORG Subject: Re: Lastest ATA/ATAPI driver boots with kernel.debug only. In-reply-to: Your message of "Sun, 18 Apr 1999 00:23:58 +0930." <3718A086.17CA6F9E@camtech.net.au> Date: Sat, 17 Apr 1999 23:07:05 +0800 From: Peter Wemm Message-Id: <19990417150708.0EDD21F5D@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Thyer wrote: > I've found that I need to disable my secondary IDE controller with > the version 5 and 6 of the new ATAPI drivers. Just as a thought.. Is your kernel.debug leftover from an earlier build? Perhaps that's why it works and the current ones do not... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 8:53:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id BA98B1515D; Sat, 17 Apr 1999 08:53:23 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA23743; Sat, 17 Apr 1999 11:49:01 -0400 (EDT) (envelope-from luoqi) Date: Sat, 17 Apr 1999 11:49:01 -0400 (EDT) From: Luoqi Chen Message-Id: <199904171549.LAA23743@lor.watermarkgroup.com> To: dcs@newsguy.com, freebsd-gnats-submit@FreeBSD.ORG, keith@email.gcn.net.tw, mzaki@e-mail.ne.jp Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. Cc: byung@wam.umd.edu, freebsd-current@FreeBSD.ORG, joki@kuebart.stuttgart.netsurf.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hey! > > I've add UNICODE support to the Joliet patch. > > It contains few charsets now, but to add other charsets is very easy. > Currently, iso8859-1 and euc-jp is included. > > Mixture of Joliet/RockRidge Extension is also available, however untested. > Cool! I think NTFS and VFATFS could use this code too, is it possible to move the code to place like libkern/unicode? > > -- > Motomichi Matsuzaki > Dept. of Biological Science, Fuculty of Sciences, Univ. of Tokyo, Japan > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 9:55:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from devils.int.maquina.com (rcu127.rnl.ist.utl.pt [193.136.154.127]) by hub.freebsd.org (Postfix) with ESMTP id 212D315025 for ; Sat, 17 Apr 1999 09:55:23 -0700 (PDT) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.int.maquina.com (8.9.3/8.9.3) with ESMTP id RAA00354 for ; Sat, 17 Apr 1999 17:52:58 +0100 (WEST) (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.int.maquina.com: gabriel owned process doing -bs Date: Sat, 17 Apr 1999 17:52:57 +0100 (WEST) From: Jose Gabriel Marcelino X-Sender: gabriel@devils.int.maquina.com To: freebsd-current@freebsd.org Subject: boot kernel panic with the latest new-bus Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm getting kernel panics during boot with the latest kernel built today using new-bus. This broke both my custom kernel and today's GENERIC (with all the needed updates) on my machine. Booting with the old kernel works fine. From what I can see (and copied from paper) this is what happens: --- boot messages pcib1: at device 2.0 on pci0 pci1: on pcib1 ed0: at device 10.0 on pci0 ed0: interrupting at irq 9 ncr0: at device 11.0 on pci0 ncr0: interrupting at irq 10 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01f3ac1 stack pointer = 0x10:0xc02cef88 frame pointer = 0x10:0xc02cef88 code segment = base 0x0, limit 0xffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 0 () interrupt mask = trap number = 12 panic: page fault ------ also, booting a debug kernel it adds the following: "stopped at cninit_finish+0x25: movl 0x4(%edx),%eax" This machine is a K6 300, 128Mb ECC DIMM, Asus SP98AGP-X motherboard using the SiS 5591 chipset, Matrox Mystique graphics card, NCR 810 SCSI controller and an Asus 36x ATAPI CD-Rom. (I have removed Soren's ATAPI driver too, but there is no change) The following is the dmesg output from the working (older) kernel: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Fri Apr 9 10:13:51 WEST 1999 root@devils:/usr/local/src/sys/compile/DEVILS Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300002041 Hz CPU: AMD-K6tm w/ multimedia extensions (300.00-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping=0 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62382080 (60920K bytes) Preloaded elf kernel "kernel" at 0xc02c8000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 ata-pci0: rev 0xd0 int a irq 14 on pci0.0.1 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 chip1: rev 0x01 on pci0.1.0 chip2: rev 0x00 on pci0.2.0 ed1: rev 0x00 int a irq 9 on pci0.10.0 ed1: address 00:00:1c:01:9d:d9, type NE2000 (16 bit) ncr0: rev 0x01 int a irq 10 on pci0.11.0 vga0: rev 0x03 int a irq 11 on pci0.12.0 Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0 at atkbd0 psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: Winbond chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus 0 ppi0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface acd0: CDROM drive at ata0 as master acd0: drive speed 0 - 6187KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 5 seconds for SCSI devices to settle pass4 at ncr0 bus 0 target 6 lun 0 pass4: Fixed Scanner SCSI-CCS device pass4: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) da2 at ncr0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 1013MB (2074880 512 byte sectors: 64H 32S/T 1013C) changing root device to da0s1a da3 at ncr0 bus 0 target 5 lun 0 da3: Removable Direct Access SCSI-2 device da3: 3.300MB/s transfers da3: 96MB (196608 512 byte sectors: 64H 32S/T 96C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates -------- The following is my (new) config file: -------- # Devil's kernel machine "i386" cpu "I586_CPU" options "CPU_WT_ALLOC" ident DEVILS maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES options NFS #Network Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options USER_LDT options COMPAT_LINUX options "EXT2FS" options "VM86" config kernel root on da0 controller isa0 at nexus? #device pnp0 controller pci0 at nexus? #controller wdc0 at isa? port "IO_WD1" bio irq 14 #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device wcd0 #IDE CD-ROM # ATAPI subsystem #controller ata0 #device atadisk0 # ATA disk drives #device atapicd0 # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives # SCSI subsystem controller ncr0 controller scbus0 device da0 device pass0 # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? tty irq 1 device psm0 at atkbdc? tty irq 12 options KBD_INSTALL_CDEV # VGA device and console device vga0 at isa? port ? conflicts device sc0 at isa? tty options VESA # Numerical coprocessor (keep this!) device npx0 at nexus? port IO_NPX irq 13 # Serial ports device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 # Parallel port device ppc0 at isa? port? net irq 7 controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? # Ethernet devices device ed0 # Kernel options options KTRACE #kernel tracing options SYSVSHM options SYSVMSG options SYSVSEM # Pseudo devices pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn pseudo-device bpfilter 4 #Berkeley packet filter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 9:57:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS08.kng.mesh.ad.jp [133.205.214.8]) by hub.freebsd.org (Postfix) with ESMTP id 2976915025 for ; Sat, 17 Apr 1999 09:57:16 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA05159; Sat, 17 Apr 1999 14:28:18 +0900 (JST) Message-Id: <199904170528.OAA05159@chandra.eatell.msr.prug.or.jp> To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 17 Apr 1999 05:30:41 +0800." <19990416213043.95C7B1F69@spinner.netplex.com.au> Date: Sat, 17 Apr 1999 14:28:18 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As of a few minutes ago, a minimal set of changes to bring the so-called > 'new-bus' functionality to the i386 kernel in -current. Is this formal decision of core team ? I feel a huge despair, as a member of newconfig project .... -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10: 2:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 961CB14FF2 for ; Sat, 17 Apr 1999 10:02:42 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id CD3C41F0B; Sun, 18 Apr 1999 01:00:17 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Jose Gabriel Marcelino Cc: freebsd-current@freebsd.org Subject: Re: boot kernel panic with the latest new-bus In-reply-to: Your message of "Sat, 17 Apr 1999 17:52:57 +0100." Date: Sun, 18 Apr 1999 01:00:17 +0800 From: Peter Wemm Message-Id: <19990417170017.CD3C41F0B@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jose Gabriel Marcelino wrote: > > Hi, > > I'm getting kernel panics during boot with the latest > kernel built today using new-bus. > This broke both my custom kernel and today's GENERIC (with all the needed > updates) on my machine. Booting with the old kernel works fine. > > From what I can see (and copied from paper) this is what happens: [..] > ncr0: at device 11.0 on pci0 > ncr0: interrupting at irq 10 > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x4 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc01f3ac1 [..] This sounds a bit like it might be fixed by Bruce: RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v ---------------------------- revision 1.2 date: 1999/04/17 09:56:35; author: bde; state: Exp; lines: +2 -2 Allocate space for struct isa_device's, not for pointers thereto. This fixes memory corruption that caused calls to address 0 here. ---------------------------- Can you check if you have this update? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:10:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id C342F14C84 for ; Sat, 17 Apr 1999 10:10:08 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-63.camtech.net.au [203.55.243.191]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id CAA07516; Sun, 18 Apr 1999 02:42:53 +0930 (CST) Message-ID: <3718BFE7.95899006@camtech.net.au> Date: Sun, 18 Apr 1999 02:37:51 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Bret Ford Cc: freebsd-current@FreeBSD.ORG Subject: Re: ftp hangs on -current References: <19990414072511.A22655@franklin.matlink> <1512.990416@avias.com> <001d01be87c8$8971d420$0100a8c0@my.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How many of you are using RealTek network cards ? They are crap in my experience (under any OS). Bret Ford wrote: > > > > > Wednesday, April 14, 1999, 10:25:11 AM, you wrote: > > > > >> I am getting problems similar to those outlined above. I don't run natd, either, but I do > > >> have a firewall enabled. (open rule) I've had to 'put' files rather than 'get' them, since my > > >> last build/installworld. (Yesterday's -current source) > > > > TP> I am not running any firewall but my last cvsup which is also current was the same day as yours. > > > > i'm still experiencing this strange problem too. developers, where are you? :) > > > > Let's continue this thread in capital letters. We might attract some attention! ;-) > > I CAN'T FTP OUT FROM MY -CURRENT SYSTEM. I CAN FTP IN. SOMETHING > IS PROBABLY WRONG. I CAN LIST DIRECTORIES, USUALLY. 'GET' COMMANDS > HANG. I AM RUNNING -CURRENT FROM MORNING APR 13. > > THANKS! > > BRET FORD > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:10:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from einstein.fisica.ist.utl.pt (unknown [193.136.100.66]) by hub.freebsd.org (Postfix) with ESMTP id 7C01F15447 for ; Sat, 17 Apr 1999 10:10:21 -0700 (PDT) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by einstein.fisica.ist.utl.pt (8.8.8/8.8.8) with ESMTP id SAA26419; Sat, 17 Apr 1999 18:08:10 +0100 Date: Sat, 17 Apr 1999 18:08:10 +0100 (WET) From: Jose Gabriel J Marcelino X-Sender: gabriel@einstein.fisica.ist.utl.pt To: Peter Wemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: boot kernel panic with the latest new-bus In-Reply-To: <19990417170017.CD3C41F0B@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [..] > > This sounds a bit like it might be fixed by Bruce: > RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v > ---------------------------- > revision 1.2 > date: 1999/04/17 09:56:35; author: bde; state: Exp; lines: +2 -2 > Can you check if you have this update? I have just checked it and I do have it, so that's not the problem :-( Thanks anyway! Regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:10:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id DEC2315485 for ; Sat, 17 Apr 1999 10:10:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id TAA23152; Sat, 17 Apr 1999 19:08:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id TAA10368; Sat, 17 Apr 1999 19:08:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: NAKAGAWA Yoshihisa Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 17 Apr 1999 14:28:18 +0900." <199904170528.OAA05159@chandra.eatell.msr.prug.or.jp> Date: Sat, 17 Apr 1999 19:08:05 +0200 Message-ID: <10366.924368885@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904170528.OAA05159@chandra.eatell.msr.prug.or.jp>, NAKAGAWA Yoshihisa writes: >> As of a few minutes ago, a minimal set of changes to bring the so-called >> 'new-bus' functionality to the i386 kernel in -current. > >Is this formal decision of core team ? I feel a huge despair, as a >member of newconfig project .... Yes, this was a decision by the core team. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:18:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 3B20A14D82 for ; Sat, 17 Apr 1999 10:18:01 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id NAA21264; Sat, 17 Apr 1999 13:15:29 -0400 (EDT) Date: Sat, 17 Apr 1999 13:15:29 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-Reply-To: <19990417072558.578211F69@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Peter Wemm wrote: > Chris Piazza wrote: > > On 17-Apr-99 Brian Feldman wrote: > > > Both sound drivers are broken with the new-bus code. My SB16, in the old > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the new > > > driver, never initializes with the new code :( > > > > > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 > > > > > > > The pcm0 sounddriver works for me. In fact, the only problem I had with new > > bus was it is now pcm0 instead of pcm1 ;-). > > > > es0: at device 9.0 on pci0 > > pcm0: using I/O space register mapping at 0xd800 > > es0: interrupting at irq 4 > > > > device pcm0 > > On two different systems it works for me using pcm0.. > > This is an ESS clone card: > > Probing for PnP devices: > CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0 > d041] > ESS1868 (rev 11) > pcm1 (ESS1868 sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 on isa > > This is an on-board Crystal SB-like PnP device: > > Probing for PnP devices: > CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000 > 0000] > mss_attach 1 at 0x530 irq 5 dma 1:0 flags 0x10 > pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 fl > ags 0x10 on isa > > For what it's worth, PnP has for the most part not been changed under > new-bus and is using the old mechanisms. The only significant risk is that > the attach code doesn't like what I've done with the emulation of > isa_device->id_id for "unit numbers". > > I'm sorry, you're going to need to have a bit of a look around and turning > on or inserting some debug code to see what's happening. > > Cheers, > -Peter > > > Here's what's going on with the pcm code. I've got an on-board audio device that should probably eventually be supported, is PnP and detected, but not recognized by the pcm driver. However, my SB16 ALSO fails to be attached. My SB16 is a nice pre-PnP one, which used to work fine with either audio driver. I'll paste my current config and dmesg. # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.102 1998/01/11 02:16:38 jkh Exp $ machine "i386" cpu "I586_CPU" ident "CUSTOM" maxusers 128 makeoptions DEBUG="-g" options "MATH_EMULATE" #Support for x87 emulation options "INET" #InterNETworking options "FFS" #Berkeley Fast Filesystem options "FFS_ROOT" #FFS usable as root device [keep this!] options "CD9660" #ISO 9660 Filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options "UCONSOLE" #Allow users to grab the console options "FAILSAFE" #Be conservative options "USERCONFIG" #boot -c editor options "VISUAL_USERCONFIG" #visual boot -c editor options "NO_F00F_HACK" options "IPFIREWALL" options "IPFIREWALL_DEFAULT_TO_ACCEPT" options "IPFIREWALL_FORWARD" #enable xparent proxy support options "IPDIVERT" options "IPSTEALTH" options "DUMMYNET" options "DDB" options "DDB_UNATTENDED" options "VM86" options "SOFTUPDATES" options "PQ_HUGECACHE" # color for 1024k cache options "ICMP_BANDLIM" options "MSGBUF_SIZE=16384" options "VESA" options "INVARIANTS" options "INVARIANT_SUPPORT" options "CLK_USE_TSC_CALIBRATION" #options "ICMP_BANDLIM_SILENT" #options "CPU_WT_ALLOC" #options "NO_MEMORY_HOLE" config kernel root on wd0 controller pci0 at nexus? controller isa0 at nexus? controller pnp0 # Luigi's snd code. # You may also wish to enable the pnp controller with this, for pnp # sound cards. # device pcm0 device pcm1 at isa? port? tty irq 5 drq 1 flags 0x16 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 6 #device sbmidi0 at isa? port 0x330 #device opl0 at isa? port 0x388 device joy0 at isa? port "IO_GAME" #controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 #disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # for a PCI only system (most modern machines) #controller ata0 #device atadisk0 # ATA disks #device atapicd0 # ATAPI CDROM's #device atapist0 # ATAPI tapes #device atapifd0 #options "ATA_STATIC_ID" controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 #options "ATAPI" #Enable ATAPI support for IDE bus #options "ATAPI_STATIC" #Don't do it as an LKM device wcd0 #IDE CD-ROM device wfd0 options "IDE_DELAY=2000" # The keyboard controller; it controlls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at atkbdc? tty irq 1 # PS/2 mouse device psm0 at atkbdc? tty irq 12 # The video card driver. device vga0 at isa? port ? conflicts # The syscons console driver (sco color console compatible). device sc0 at isa? tty device npx0 at nexus? port "IO_NPX" irq 13 # # Laptop support (see LINT for more options) # device apm0 at nexus? conflicts # Advanced Power Management # System Management Bus! controller smbus0 controller alpm0 device smb0 at smbus? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 3 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? controller ppc0 at isa? port ? tty irq 7 drq 3 # USB support #controller uhci0 controller usb0 controller ohci0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # device ums0 device ukbd0 device ulpt0 device ucom0 device umodem0 device hid0 device ugen0 # #options USB_DEBUG #options USBVERBOSE pseudo-device loop pseudo-device ether #pseudo-device sl 4 #pseudo-device ppp 4 #pseudo-device tun 4 pseudo-device pty 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device speaker pseudo-device snp 4 pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device splash # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options "KTRACE" #kernel tracing # This provides support for System V shared memory. # options "SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)" options "SHMMAXPGS=4100" options "SYSVSHM" options "SYSVSEM" options "SYSVMSG" options "USER_LDT" #allow user-level control of i386 ldt options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Apr 17 12:01:48 EDT 1999 green@green.dyn.ez-ip.net:/usr/src/sys/compile/GREEN Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping=12 Features=0x8021bf real memory = 67108864 (65536K bytes) avail memory = 62316544 (60856K bytes) Bad DMI table checksum! Preloaded elf kernel "kernel" at 0xc02a6000. Probing for PnP devices: CSN 1 Vendor ID: CMI0001 [0x0100a90d] Serial 0x01000100 Comp ID: @@@0000 [0x00000000] npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 ohci0: at device 2.0 on pci0 ohci0: interrupting at irq 10 usb0: OHCI version 1.0, legacy support usb0: on ohci0 uhub0 at usb0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: at device 3.0 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 15.0 on pci0 joy0 at port 0x201 on isa0 joy0: joystick wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-32 wd0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-32 wd3: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 0 (atapi): , removable, iordy wfd0: medium type unknown (no disk) wdc1: interrupting at irq 15 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378 irq 7 drq 3 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 ppc0: interrupting at irq 7 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled DUMMYNET initialized (990326) -- size dn_pkt 48 changing root device to wd0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:30:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id A056015258 for ; Sat, 17 Apr 1999 10:30:15 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-63.camtech.net.au [203.55.243.191]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id DAA08893; Sun, 18 Apr 1999 03:02:55 +0930 (CST) Message-ID: <3718C49C.85785ED6@camtech.net.au> Date: Sun, 18 Apr 1999 02:57:56 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: John Polstra Cc: Thomas Schuerger , current@FreeBSD.ORG Subject: Re: cvsup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whats the posibility of having another process for the display ? Naturally this would only be forked if the DISPLAY env is set and the user didnt refuse GUI mode. John Polstra wrote: > > Thomas Schuerger wrote: > > > cvsup is mostly based on disk (and network) I/O, so there shouldn't > > be a problem with properly updating the GUI. Someone said it is > > done in a separate process, so I still wonder why the GUI is updated > > so slowly on my PII/450. > > Not a separate process -- a separate thread. It uses user-level > threads. If the process blocks in a disk I/O call, all threads stop > until the call completes. That's just the way Unix works. > > John > --- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:30:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 0309A15485 for ; Sat, 17 Apr 1999 10:30:44 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA82206; Sat, 17 Apr 1999 18:32:50 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 17 Apr 1999 18:32:50 +0100 (BST) From: Doug Rabson To: Jose Gabriel J Marcelino Cc: Peter Wemm , freebsd-current@freebsd.org Subject: Re: boot kernel panic with the latest new-bus In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Jose Gabriel J Marcelino wrote: > > > > [..] > > > > This sounds a bit like it might be fixed by Bruce: > > RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v > > ---------------------------- > > revision 1.2 > > date: 1999/04/17 09:56:35; author: bde; state: Exp; lines: +2 -2 > > > Can you check if you have this update? > > I have just checked it and I do have it, so that's not the problem :-( > > Thanks anyway! I think we aren't picking up the PCI-ISA bridge chip which means that the isa bus didn't get probed. Could you do a verbose boot (boot -v) of your *old* kernel and post the resulting dmesg. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:31: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 4B3EF15485 for ; Sat, 17 Apr 1999 10:30:57 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id NAA15165; Sat, 17 Apr 1999 13:26:18 -0400 (EDT) Date: Sat, 17 Apr 1999 13:26:18 -0400 (EDT) From: Chuck Robey To: Brian Feldman Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Brian Feldman wrote: > On Sat, 17 Apr 1999, Peter Wemm wrote: > > > Chris Piazza wrote: > > > On 17-Apr-99 Brian Feldman wrote: > > > > Both sound drivers are broken with the new-bus code. My SB16, in the old > > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the new > > > > driver, never initializes with the new code :( > > > > > > > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 [bunch of dmesg delete] [here from Peter] > > For what it's worth, PnP has for the most part not been changed under > > new-bus and is using the old mechanisms. The only significant risk is that > > the attach code doesn't like what I've done with the emulation of > > isa_device->id_id for "unit numbers". > > > > I'm sorry, you're going to need to have a bit of a look around and turning > > on or inserting some debug code to see what's happening. > > Here's what's going on with the pcm code. I've got an on-board audio device > that should probably eventually be supported, is PnP and detected, but > not recognized by the pcm driver. However, my SB16 ALSO fails to be attached. > My SB16 is a nice pre-PnP one, which used to work fine with either audio > driver. I'll paste my current config and dmesg. FWIW, using a 2 hour old kernel, my Turtle Beach Malibu PCI PnP card works just fine: [from my config file] device pcm0 at isa? port ? tty irq 15 drq 1 [from my dmesg] Probing for PnP devices: Trying Read_Port at 203 CSN 1 Vendor ID: CSC7537 [0x3775630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000 0000] PnP: override config for CSN 1 LDN 0 vend_id 0x3775630e port 0x0000 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 0 Called nullpnp_probe with tag 0x00000001, type 0x3775630e port 0x0534 0x0000 0x0220 0x0000 irq 15:0 drq 1:0 en 1 port 0x0534 0x0000 0x0220 0x0000 irq 15:0 drq 1:0 en 1 mss_attach 1 at 0x530 irq 15 dma 1:0 flags 0x10 pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 15 drq 1 f lags 0x10 on isa Notice that the line beginning "port" shows twice, which is an odditity. I use a line in my kernel.conf of: pnp 1 0 os enable port0 0x534 port2 0x220 irq0 15 drq0 1 drq1 0 I'm not saying Brian doesn't have a real problem, but I *am* saying that not all PCI PnP sound is broken. > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:38:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 6A01E15415 for ; Sat, 17 Apr 1999 10:38:27 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 95D531F58; Sun, 18 Apr 1999 01:36:01 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-reply-to: Your message of "Sat, 17 Apr 1999 13:15:29 -0400." Date: Sun, 18 Apr 1999 01:36:01 +0800 From: Peter Wemm Message-Id: <19990417173603.95D531F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > On Sat, 17 Apr 1999, Peter Wemm wrote: > > Chris Piazza wrote: > > > On 17-Apr-99 Brian Feldman wrote: > > > > Both sound drivers are broken with the new-bus code. My SB16, in the ol d > > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the ne w > > > > driver, never initializes with the new code :( > > > > > > > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 > > > > > > > > > > The pcm0 sounddriver works for me. In fact, the only problem I had with new > > > bus was it is now pcm0 instead of pcm1 ;-). > > > > > > es0: at device 9.0 on pci0 > > > pcm0: using I/O space register mapping at 0xd800 > > > es0: interrupting at irq 4 > > > > > > device pcm0 > > > > On two different systems it works for me using pcm0.. > Here's what's going on with the pcm code. I've got an on-board audio device > that should probably eventually be supported, is PnP and detected, but > not recognized by the pcm driver. However, my SB16 ALSO fails to be attached. > My SB16 is a nice pre-PnP one, which used to work fine with either audio > driver. I'll paste my current config and dmesg. [..] > # Luigi's snd code. > # You may also wish to enable the pnp controller with this, for pnp > # sound cards. > # > device pcm0 > device pcm1 at isa? port? tty irq 5 drq 1 flags 0x16 [..] Hmm, you might like to try this patch and see what happens, there is a missing old driver wrapper for the pcm stuff. As a result, it's not getting run from the isa probe. Regarding the other driver, I'm not sure what's going on there as the hooks appear to be present. Index: i386/isa/isa_compat.h =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v retrieving revision 1.1 diff -u -r1.1 isa_compat.h --- isa_compat.h 1999/04/16 21:22:23 1.1 +++ isa_compat.h 1999/04/17 17:30:34 @@ -49,6 +49,7 @@ #include "ze.h" #include "zp.h" #include "oltr.h" +#include "pcm.h" #include "pas.h" #include "sb.h" #include "sbxvi.h" @@ -117,6 +118,7 @@ extern struct isa_driver zedriver; extern struct isa_driver zpdriver; extern struct isa_driver oltrdriver; +extern struct isa_driver pcmdriver; extern struct isa_driver pasdriver; extern struct isa_driver sbdriver; extern struct isa_driver sbxvidriver; @@ -320,6 +322,9 @@ #if NOLTR > 0 { DRIVER_TYPE_MISC, &oltrdriver }, +#endif +#if NPCM > 0 + { DRIVER_TYPE_MISC, &pcmdriver }, #endif #if NPAS > 0 { DRIVER_TYPE_MISC, &pasdriver }, Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:48:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3459714C01 for ; Sat, 17 Apr 1999 10:48:48 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA12292; Sat, 17 Apr 1999 10:45:09 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: NAKAGAWA Yoshihisa Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 17 Apr 1999 14:28:18 +0900." <199904170528.OAA05159@chandra.eatell.msr.prug.or.jp> Date: Sat, 17 Apr 1999 10:45:09 -0700 Message-ID: <12290.924371109@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is this formal decision of core team ? I feel a huge despair, as a > member of newconfig project .... This was a core team decision, but I really do hope we can still figure out some way of working together on a final hybrid of the best ideas from both projects since this honestly wasn't done with the intention of making the newconfig people unhappy, please believe me. This is simply one of those unfortunate situations where two groups of developers have worked in relative isolation from one another and come up with more or less the same thing, the difference with new-bus being that we were working just that much more closely with Doug Rabson (and the others helping him) and had already used the new-bus stuff for FreeBSD/alpha. The core team did not make this decision lightly and there was considerable debate over it until we finally made the decision to take the clearest choice we could see before us and simply synchronize the FreeBSD/alpha and FreeBSD/x86 code bases. I also have to say that this has pointed out, once again, that communication is really lacking between the various groups, especially in situations where a language barrier exists. Most of us didn't even know about the newconfig project until comparatively recently, and I didn't even really know about it until I saw you guys submit a paper for the FREENIX track at USENIX. Doug's new-bus stuff, on the other hand, was a well known factor for at least a year and, as I noted, had already made it to the Alpha platform, getting it to the x86 simply being a project which was delayed by many various factors. It would, in fact, probably have gone into FreeBSD 6 months ago if everyone involved had simply had a bit more free time. However this situation came about, the core team also ultimately had to make a decision one way or another and no matter *which* alternative we picked, somebody was going to be the "loser" so it wasn't even as if we had that many good alternatives. The discussions on merging the two efforts really didn't seem to be going anywhere and the more we watched the two groups talk the more it seemed like they simply weren't going to converge on their thinking on this. I don't really like the word "loser" very much, however, and would much rather that everyone focus instead on the best route forward from here since we've made the decision, for better or for worse, and need to figure out some way for everyone's best ideas to still "win" in some way. With that in mind, I would be more than happy to take you and all the other newconfig project people out to dinner at the upcoming USENIX conference, perhaps with Satoshi serving as translator, along with Doug Rabson and any other new-bus people who'd like to come. Rather than sinking into despair, we really need to start discussing how to fix the communications problems we've had in the past since that will be addressing the *cause* rather than the symptoms of our current problem. I also truly feel that much can still be salvaged in a number of different ways if we're willing to put the well-being of FreeBSD first and foremost in our minds, and I'm more than happy to do anything I can to make that happen. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 10:53:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-4.ppp.wenet.net [206.15.85.4]) by hub.freebsd.org (Postfix) with ESMTP id 786CB14C01 for ; Sat, 17 Apr 1999 10:53:48 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id KAA00270; Sat, 17 Apr 1999 10:49:47 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sat, 17 Apr 1999 10:49:47 -0700 (PDT) From: Alex Zepeda To: Peter Wemm Cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-Reply-To: <19990417072558.578211F69@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Peter Wemm wrote: > For what it's worth, PnP has for the most part not been changed under > new-bus and is using the old mechanisms. The only significant risk is that > the attach code doesn't like what I've done with the emulation of > isa_device->id_id for "unit numbers". Well, something appears to have changed. My internal PnP modem is no longer detected. I just checked sio.c, and it appears as if the PnP id is still there. I've got: controller pnp0 device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 in my config file. Previously dmesg|grep sio would return: sio1: irq maps: 0x1 0x9 0x1 0x1 sio1: type 16550A sio1 (siopnp sn 0x00416288) at 0x3e8-0x3ef irq 3 on isa sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A apm: found APM BIOS version 1.2 Now it returns: apm: found APM BIOS version 1.2 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 > I'm sorry, you're going to need to have a bit of a look around and turning > on or inserting some debug code to see what's happening. > > Cheers, > -Peter - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 11: 4: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 113F614D63 for ; Sat, 17 Apr 1999 11:04:02 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-63.camtech.net.au [203.55.243.191]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id DAA11180; Sun, 18 Apr 1999 03:36:35 +0930 (CST) Message-ID: <3718CC80.11C1BE27@camtech.net.au> Date: Sun, 18 Apr 1999 03:31:36 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Warner Losh Cc: mi@aldan.algebra.com, current@FreeBSD.ORG Subject: Re: swap-related problems References: <199904142340.TAA96857@misha.cisco.com> <199904150432.WAA07661@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is obviously a problem when all swap is exhausted. The only solution is to allow the additional memory *use* to succeed AND to warn the sysadmin that ALL virtual memory has been exhausted. The only way to do this is to be able to allocate extra virtual memory. I'd vote for a system that would create swap files in the largest mounted read/write filesystem of type UFS or in the filesystem of my choice. There would be a systctl to set the limits on how much space to allocate. Possibly a setting for size and number of emergency swap files. When the time comes for killing processes, you should be able to specify that certain processes (by name) are "precious" and that processes owned by particular users and/or particular login classes are in the last resort or first resort for killing. I dont think it's worth trying to signal with a different signal because only FreeBSD specific programs will know what to do when signalled in such a manner. I suppose you could signal prior to killing as another layer to my dream system. Warner Losh wrote: > > In message <199904142340.TAA96857@misha.cisco.com> Mikhail Teterin writes: > : Then, one can write a safe malloc, which will install the signal > : handler, and touch every page in the the memory referenced by the > : to-be-returned pointer. If the signal handler is invoked in the > : progress, the to-be-returned memory must be returned back to the > : system and NULL should be returned to the caller. > > This won't work all the time. FreeBSD overcommits swap space and you > may get a SIGKILL even if you've touched all the pages. FreeBSD kills > processes when swap space runs out. > > : However, my (in)ability to propose anything remotely sensible does > : not change the facts established in this painful thread. That our > : malloc does not conform to standards (for whatever reasons), and > : that something should be done about it. That "something" must start > : with documenting the flaw... > > The behavior is documented: > The malloc() and calloc() functions return a pointer to the allocated > memory if successful; otherwise a NULL pointer is returned. > > What the system does when it has resource shortages is beyond the > scope of the ANSI-C standard, so I don't see why you say that > FreeBSD's malloc isn't standard conforming. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 11:12:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 08A2214D59 for ; Sat, 17 Apr 1999 11:12:24 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-63.camtech.net.au [203.55.243.191]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id DAA11759; Sun, 18 Apr 1999 03:45:13 +0930 (CST) Message-ID: <3718CE86.E7FFA6F2@camtech.net.au> Date: Sun, 18 Apr 1999 03:40:14 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Warner Losh , mi@aldan.algebra.com, current@FreeBSD.ORG Subject: Re: swap-related problems References: <199904142340.TAA96857@misha.cisco.com> <199904150432.WAA07661@harmony.village.org> <3718CC80.11C1BE27@camtech.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Replying to myself... You'd have to be able to specify the absolute maximum memory use for a process to ensure you'd still kill run-aways (These would go first! regardless of the other rules maybe). Matthew Thyer wrote: > > There is obviously a problem when all swap is exhausted. > > The only solution is to allow the additional memory *use* to succeed AND > to warn the sysadmin that ALL virtual memory has been exhausted. > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 11:16: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 3308914C4B for ; Sat, 17 Apr 1999 11:15:59 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id <2RSVNTNS>; Sat, 17 Apr 1999 19:11:44 +0100 Message-ID: From: paul@originative.co.uk To: robert+freebsd@cyrus.watson.org, freebsd-current@freebsd.org Subject: RE: lnc0: broke for us between 3.1 and 4.0? Date: Sat, 17 Apr 1999 19:11:44 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Robert Watson [mailto:robert@cyrus.watson.org] > Sent: 17 April 1999 01:16 > To: freebsd-current@freebsd.org > Subject: lnc0: broke for us between 3.1 and 4.0? > > > > We upgraded a crash machine from 3.1-RELEASE to 4.0-CURRENT from just > before the EGCS switch was pulled. The machine is a Pentium 166 MMX > overdrive. Prior to the upgrade, it correctly probed the > Kensington KNE > 2100 (something like that) with the lnc driver as being at > 0x300 irq 5 > drq 6. > > The working 3.1-RELEASE GENERIC w/a change in the config > editor probe went > like: > > lnc0 at 0x300-0x317 irq 5 drq 6 on isa > lnc0: PCnet-ISA address 00:c0:f0:00:81:f4 > > After upgrading to -current, the probe failed as follows > (when config was > used on the GENERIC quote): > > lnc0 at 0x300-0x317 irq 5 drq 6 on isa > lnc0: Memory allocated above 16Mb limit It looks like the change to allocate memory from the top rather than the bottom has broken it since on my box, at least, it's getting memory from the end of physical memory now whereas it never used to. Can someone remind what exactly that change was? Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 11:26:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 504EF14D87 for ; Sat, 17 Apr 1999 11:26:36 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA21905; Sat, 17 Apr 1999 14:24:03 -0400 (EDT) Date: Sat, 17 Apr 1999 14:24:01 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-Reply-To: <19990417173603.95D531F58@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Peter Wemm wrote: > Brian Feldman wrote: > > On Sat, 17 Apr 1999, Peter Wemm wrote: > > > Chris Piazza wrote: > > > > On 17-Apr-99 Brian Feldman wrote: > > > > > Both sound drivers are broken with the new-bus code. My SB16, in the ol > d > > > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the ne > w > > > > > driver, never initializes with the new code :( > > > > > > > > > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16 > > > > > > > > > > > > > The pcm0 sounddriver works for me. In fact, the only problem I had with > new > > > > bus was it is now pcm0 instead of pcm1 ;-). > > > > > > > > es0: at device 9.0 on pci0 > > > > pcm0: using I/O space register mapping at 0xd800 > > > > es0: interrupting at irq 4 > > > > > > > > device pcm0 > > > > > > On two different systems it works for me using pcm0.. > > > Here's what's going on with the pcm code. I've got an on-board audio device > > that should probably eventually be supported, is PnP and detected, but > > not recognized by the pcm driver. However, my SB16 ALSO fails to be attached. > > My SB16 is a nice pre-PnP one, which used to work fine with either audio > > driver. I'll paste my current config and dmesg. > > [..] > > # Luigi's snd code. > > # You may also wish to enable the pnp controller with this, for pnp > > # sound cards. > > # > > device pcm0 > > device pcm1 at isa? port? tty irq 5 drq 1 flags 0x16 > [..] > > > Hmm, you might like to try this patch and see what happens, there is > a missing old driver wrapper for the pcm stuff. As a result, it's not > getting run from the isa probe. Regarding the other driver, I'm not > sure what's going on there as the hooks appear to be present. Thank you, that did work :) Now if someone could tell me why I need to keep seeing sorry, read DMA channel unavailable let me know. This seems to be something that I do NOT need to see from sb_dsp.c :P Other than that, everything's nice and peachy. No, wait, I forgot. IPFW is _not_ being recognized in the kernel, and the module is getting loaded instead (ipfw not being initialized?). > > Index: i386/isa/isa_compat.h > =================================================================== > RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v > retrieving revision 1.1 > diff -u -r1.1 isa_compat.h > --- isa_compat.h 1999/04/16 21:22:23 1.1 > +++ isa_compat.h 1999/04/17 17:30:34 > @@ -49,6 +49,7 @@ > #include "ze.h" > #include "zp.h" > #include "oltr.h" > +#include "pcm.h" > #include "pas.h" > #include "sb.h" > #include "sbxvi.h" > @@ -117,6 +118,7 @@ > extern struct isa_driver zedriver; > extern struct isa_driver zpdriver; > extern struct isa_driver oltrdriver; > +extern struct isa_driver pcmdriver; > extern struct isa_driver pasdriver; > extern struct isa_driver sbdriver; > extern struct isa_driver sbxvidriver; > @@ -320,6 +322,9 @@ > > #if NOLTR > 0 > { DRIVER_TYPE_MISC, &oltrdriver }, > +#endif > +#if NPCM > 0 > + { DRIVER_TYPE_MISC, &pcmdriver }, > #endif > #if NPAS > 0 > { DRIVER_TYPE_MISC, &pasdriver }, > > > Cheers, > -Peter > > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 11:32: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DE7E915174 for ; Sat, 17 Apr 1999 11:32:04 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA12368; Sat, 17 Apr 1999 11:29:33 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA13256; Sat, 17 Apr 1999 11:29:33 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3718C49C.85785ED6@camtech.net.au> Date: Sat, 17 Apr 1999 11:29:33 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Matthew Thyer Subject: Re: cvsup Cc: current@FreeBSD.ORG, Thomas Schuerger Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Thyer wrote: > Whats the posibility of having another process for the display ? To be blunt, the probability is epsilon. I simply am not interested in spending time to make the silly GUI perform better when I could instead work on making the package transfer files faster. BTW, have you tried running the GUI from an X server on a different machine? Maybe the problem is that your X server isn't getting enough resources to update the screen quickly. I really don't see much of a problem with the speed of GUI updates here on my machine. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 11:44:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from devils.int.maquina.com (rcu127.rnl.ist.utl.pt [193.136.154.127]) by hub.freebsd.org (Postfix) with ESMTP id D8AC915256 for ; Sat, 17 Apr 1999 11:44:07 -0700 (PDT) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.int.maquina.com (8.9.3/8.9.3) with ESMTP id TAA00298; Sat, 17 Apr 1999 19:40:04 +0100 (WEST) (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.int.maquina.com: gabriel owned process doing -bs Date: Sat, 17 Apr 1999 19:40:04 +0100 (WEST) From: Jose Gabriel Marcelino X-Sender: gabriel@devils.int.maquina.com To: Doug Rabson Cc: Peter Wemm , freebsd-current@freebsd.org Subject: Re: boot kernel panic with the latest new-bus In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Doug Rabson wrote: > I think we aren't picking up the PCI-ISA bridge chip which means that the > isa bus didn't get probed. Could you do a verbose boot (boot -v) of your > *old* kernel and post the resulting dmesg. Ok. Here it is. This is the biggest I could get. I had some trouble to get it too (I had to turn off most of the SCSI chain and boot single mode :), how can one increase the size of the dmesg buffer btw??) 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 128M bytes Write Allocate 15-16M bytes: Disable Hardware Write Allocate Control: Enable real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002e1000 - 0x07ffdfff, 131190784 bytes (32029 pages) avail memory = 127750144 (124756K bytes) Found BIOS32 Service Directory header at 0xc00f99e0 Entry = 0xf0490 (0xc00f0490) Rev = 0 Len = 1 PCI BIOS entry at 0x4c0 DMI header at 0xc00f51c0 Version 2.0 Table at 0xf51da, 31 entries, 973 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fced0 Preloaded elf kernel "kernel.stable" at 0xc02c8000. VESA: information block 56 45 53 41 00 02 31 77 00 c0 01 00 00 00 22 00 00 01 40 00 05 01 46 77 00 c0 4d 77 00 c0 56 77 00 c0 00 01 01 01 02 01 03 01 05 01 07 01 08 01 09 01 0b 01 0c 01 10 01 11 01 12 01 13 01 14 01 VESA: 24 mode(s) found pci_open(1): mode 1 addr port (0x0cf8) is 0x80006000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=55911039) Probing for devices on PCI bus 0: found-> vendor=0x1039, dev=0x5591, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base e0000000, size 26 chip0: rev 0x02 on pci0.0.0 found-> vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=0 map[0]: type 4, range 32, base 0000e400, size 3 map[1]: type 4, range 32, base 0000e000, size 2 map[2]: type 4, range 32, base 0000d800, size 3 map[3]: type 4, range 32, base 0000d400, size 2 map[4]: type 4, range 32, base 0000d000, size 4 ata-pci0: rev 0xd0 int a irq 0 on pci0.0.1 ata-pci0: Busmastering DMA not enabled found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x1039, dev=0x0009, revid=0x00 class=ff-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x7001, revid=0x11 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[0]: type 1, range 32, base df800000, size 12 found-> vendor=0x1039, dev=0x0001, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip2: rev 0x00 on pci0.2.0 found-> vendor=0x10ec, dev=0x8029, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000b800, size 5 ed1: rev 0x00 int a irq 9 on pci0.10.0 ed1: address 00:00:1c:01:9d:d9, type NE2000 (16 bit) bpf: ed1 attached found-> vendor=0x1000, dev=0x0001, revid=0x01 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000b400, size 8 map[1]: type 1, range 32, base df000000, size 8 ncr0: rev 0x01 int a irq 10 on pci0.11.0 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver found-> vendor=0x102b, dev=0x051a, revid=0x03 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base e7000000, size 23 map[1]: type 1, range 32, base de800000, size 14 map[2]: type 1, range 32, base de000000, size 23 vga0: rev 0x03 int a irq 11 on pci0.12.0 Probing for devices on PCI bus 1: Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 No Plug-n-Play devices were found Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 90 03 3c psm: status 90 03 3c psm: status 90 03 3c psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc: parallel port found at 0x378 ppc0: 0x87 - 0x8 0x0 0xff 0x10 0x0 0x0 0x5 0x0 0x0 0x8c 0xff 0xc 0x28 0xab 0x0 0x0 0x0 0x0 0x0 0x0 0x7 0x0 0xff 0x0 0xff 0xff 0xde 0xfe 0xbe 0x3 0x25 0x43 0x0 ppc0: ECP SPP ppc0 at 0x378 irq 7 on isa ppc0: Winbond chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached ppi0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc02814a2 (1000022) VESA: Matrox Graphics Inc. VESA: Matrox VESA: MYSTIQUE VESA: 00 npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 82863771 bytes/sec bzero() bandwidth = 104723007 bytes/sec imasks: bio c0080000, tty c007129a, net c007129a BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. bpf: tun0 attached bpf: sl0 attached bpf: ppp0 attached new masks: bio c0080000, tty c007129a, net c007129a bpf: lo0 attached Linux-ELF exec handler installed Waiting 5 seconds for SCSI devices to settle ncr0: restart (scsi reset). pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 341520410988 pass0: 10.000MB/s transfers (10.000MHz, offset 8) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 341520410988 da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) Considering FFS root f/s. changing root device to da0s1a da0s1: type 0xa5, start 62, end = 2133295, size 2133234 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 11:58: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from h24-64-221-247.gv.wave.shaw.ca (24.64.221.247.bc.wave.home.com [24.64.221.247]) by hub.freebsd.org (Postfix) with ESMTP id A476B1534E for ; Sat, 17 Apr 1999 11:57:58 -0700 (PDT) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.3/8.9.2) with ESMTP id LAA00451; Sat, 17 Apr 1999 11:55:09 -0700 (PDT) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199904171855.LAA00451@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-reply-to: Your message of "Sun, 18 Apr 1999 01:36:01 +0800." <19990417173603.95D531F58@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 17 Apr 1999 11:55:08 -0700 From: Jake Burkholder Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm, you might like to try this patch and see what happens, there is > a missing old driver wrapper for the pcm stuff. As a result, it's not > getting run from the isa probe. Regarding the other driver, I'm not > sure what's going on there as the hooks appear to be present. Right on, that patch does it for me. pcm0 at port 0x220 irq 5 drq 1 flags 0x15 on isa0 pcm0: interrupting at irq 5 I've got an old SB16 Value, non-pnp. mp3s aren't playing quite right with x11amp though, little skips here and there, they work fine with the old kernel. mpg123 seems fine, as does the sound in FXTV. I'll try making the world again. IPFW works for me...but I'm loading the KLD. my panasonic cdrom is no longer probed, it uses the matcd driver. doesn't show up in dmesg at all, but it does in the visual kernel config thing. It's so old, I'm not surprised :) great work! Jake -- we are but packets in the internet of life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 11:58:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id DCA4515416 for ; Sat, 17 Apr 1999 11:58:14 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA22173; Sat, 17 Apr 1999 14:55:43 -0400 (EDT) Date: Sat, 17 Apr 1999 14:55:42 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, btw, you did break sbxvi. Look carefully at the #if which surrounds it ;) Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 12: 3:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 79E1C14C23 for ; Sat, 17 Apr 1999 12:02:23 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id LAA11461 for ; Sat, 17 Apr 1999 11:53:54 -0700 (PDT) Date: Sat, 17 Apr 1999 11:53:53 -0700 (PDT) From: Annelise Anderson To: freebsd-current@freebsd.org Subject: login Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I log in to my -current machine (April 13 sources) it takes a minute or two after the password is entered before the shell prompt comes up: FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0) login: xanne Password: []<--cursor just stays here for a while This is on a LAN; it works fine at the console (and it worked when it was 3.1). I can certainly live with this but it puzzles me. Would anyone know why this might be happening? Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 12: 3:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id AEA1915426 for ; Sat, 17 Apr 1999 12:02:51 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA82909; Sat, 17 Apr 1999 20:03:48 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 17 Apr 1999 20:03:48 +0100 (BST) From: Doug Rabson To: Jose Gabriel Marcelino Cc: Peter Wemm , freebsd-current@freebsd.org Subject: Re: boot kernel panic with the latest new-bus In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Jose Gabriel Marcelino wrote: > > > On Sat, 17 Apr 1999, Doug Rabson wrote: > > > I think we aren't picking up the PCI-ISA bridge chip which means that the > > isa bus didn't get probed. Could you do a verbose boot (boot -v) of your > > *old* kernel and post the resulting dmesg. > > Ok. Here it is. This is the biggest I could get. > > I had some trouble to get it too (I had to turn off most of the SCSI chain > and boot single mode :), how can one increase the size of the dmesg buffer > btw??) There is an option for this which is documented in LINT, MSGBUF_SIZE. Could you try this patch which should make it see your PCI-ISA bridge: Index: pcisupport.c =================================================================== RCS file: /home/ncvs/src/sys/pci/pcisupport.c,v retrieving revision 1.96 diff -u -r1.96 pcisupport.c --- pcisupport.c 1999/04/16 21:22:52 1.96 +++ pcisupport.c 1999/04/17 19:02:05 @@ -929,6 +929,10 @@ return("AcerLabs M1533 portable PCI-ISA bridge"); case 0x154310b9: return("AcerLabs M1543 desktop PCI-ISA bridge"); + + /* SiS -- vendor 0x1039 */ + case 0x00081039: + return ("SiS 85c503 PCI-ISA bridge"); } if (pci_get_class(dev) == PCIC_BRIDGE @@ -947,6 +951,7 @@ desc = isab_match(dev); if (desc) { device_set_desc_copy(dev, desc); + /* Don't bother adding more than one ISA bus */ if (!devclass_get_device(devclass_find("isa"), 0)) device_add_child(dev, "isa", -1, 0); @@ -1050,8 +1055,6 @@ return ("SiS 85c496"); case 0x04061039: return ("SiS 85c501"); - case 0x00081039: - return ("SiS 85c503"); case 0x06011039: return ("SiS 85c601"); -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 12: 3:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7C02414C7F for ; Sat, 17 Apr 1999 12:03:24 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id OAA22205; Sat, 17 Apr 1999 14:59:39 -0400 (EDT) Date: Sat, 17 Apr 1999 14:59:38 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Jake Burkholder Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-Reply-To: <199904171855.LAA00451@h24-64-221-247.gv.wave.shaw.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Jake Burkholder wrote: > > Hmm, you might like to try this patch and see what happens, there is > > a missing old driver wrapper for the pcm stuff. As a result, it's not > > getting run from the isa probe. Regarding the other driver, I'm not > > sure what's going on there as the hooks appear to be present. > > Right on, that patch does it for me. > > pcm0 at port 0x220 irq 5 drq 1 flags 0x15 on isa0 > pcm0: interrupting at irq 5 > > I've got an old SB16 Value, non-pnp. > > mp3s aren't playing quite right with x11amp though, little > skips here and there, they work fine with the old kernel. > mpg123 seems fine, as does the sound in FXTV. > I'll try making the world again. I suggest using the old VoxWare with an old SB16, like I do. I was only trying to use pcm temporarily because sbxvi is broken (fix isa_compat.h). > > IPFW works for me...but I'm loading the KLD. > I like having my ipfw rules there BEFORE anything happens, hence before rc(5). > my panasonic cdrom is no longer probed, it uses the matcd driver. > doesn't show up in dmesg at all, but it does in the visual kernel > config thing. It's so old, I'm not surprised :) > > great work! > > Jake > -- > we are but packets in the internet of life > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 12: 7: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D5F4714C7F for ; Sat, 17 Apr 1999 12:07:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA75813; Sat, 17 Apr 1999 12:04:36 -0700 (PDT) (envelope-from dillon) Date: Sat, 17 Apr 1999 12:04:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199904171904.MAA75813@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: NAKAGAWA Yoshihisa , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! References: <12290.924371109@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Is this formal decision of core team ? I feel a huge despair, as a :> member of newconfig project .... : :This was a core team decision, but I really do hope we can still :figure out some way of working together on a final hybrid of the best :ideas from both projects since this honestly wasn't done with the :... : :I also have to say that this has pointed out, once again, that :communication is really lacking between the various groups, especially :in situations where a language barrier exists. Most of us didn't even :know about the newconfig project until comparatively recently, and I :... : :I don't really like the word "loser" very much, however, and would :much rather that everyone focus instead on the best route forward from :here since we've made the decision, for better or for worse, and need :... :- Jordan I think Jordan has nailed it on the head, as usual. I would like to address the communications aspect of the problem, because I think it is fairly easy for us to solve it. Simply put, people are not using the 'hackers' mailing list enough. If you notice, whenever I'm working on something that is fairly intrusive to the code base, I post updates to hackers at fairly regular intervals ( or to current if its a patchset for a bug ). I think it is especially important to do this even if there does not appear to be a huge amount of external interest. A week or a month down the line, someone might *become* interested in doing something similar to what you are doing and they aren't going to remember the one message you posted N months ago. As an example of the obviousness of the solution, I would point to CAM. the CAM guys posted updates 'almost' regularly enough. When the time came to shoehorn it into the source tree, there was grumbling but enough people knew it was coming that CAM had no real trouble getting in. I would say that if the CAM group had posted updates more regularly then they did, there would have been even less argument and confusion. If they hadn't posted anything at all, it might not have gotten in at all. Same thing goes here. -- Point #2 : The language barrier. Language is always a barrier, but it is made much worse when people to take a guy to task for his 'bad english'. I would ask people to STOP DOING THIS. Do not harass or ridicule someone for not being fluent in english! Now, it is sorely true that someone will often post to the list a message on the order of "my machine crashed, please fix it!" without one iota of additional information -- but please, people, be polite! If you don't want to try to help the person, do not answer at all. Else allow other people to lead him through the procedure. Many of these people are trying a hellofalot harder to communicate then us fluent english speakers ( we who tend to not know any language other then english, which is quite sad! ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 12:19:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from devils.int.maquina.com (rcu127.rnl.ist.utl.pt [193.136.154.127]) by hub.freebsd.org (Postfix) with ESMTP id 8456414C23 for ; Sat, 17 Apr 1999 12:19:13 -0700 (PDT) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.int.maquina.com (8.9.3/8.9.3) with ESMTP id UAA00690; Sat, 17 Apr 1999 20:16:23 +0100 (WEST) (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.int.maquina.com: gabriel owned process doing -bs Date: Sat, 17 Apr 1999 20:16:23 +0100 (WEST) From: Jose Gabriel Marcelino X-Sender: gabriel@devils.int.maquina.com To: Doug Rabson Cc: Peter Wemm , freebsd-current@freebsd.org Subject: Re: boot kernel panic with the latest new-bus In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK! > There is an option for this which is documented in LINT, MSGBUF_SIZE. Thanks for letting me know! > Could you try this patch which should make it see your PCI-ISA bridge: Well, I'm more than pleased to say IT DID!! Everything is working now! I'm typing this using the new kernel. Thank you very much! I'm amazed :-) Great work! -- Gabriel > +++ pcisupport.c 1999/04/17 19:02:05 > Index: pcisupport.c > =================================================================== > RCS file: /home/ncvs/src/sys/pci/pcisupport.c,v > retrieving revision 1.96 > diff -u -r1.96 pcisupport.c > --- pcisupport.c 1999/04/16 21:22:52 1.96 > @@ -929,6 +929,10 @@ > return("AcerLabs M1533 portable PCI-ISA bridge"); > case 0x154310b9: > return("AcerLabs M1543 desktop PCI-ISA bridge"); > + > + /* SiS -- vendor 0x1039 */ > + case 0x00081039: > + return ("SiS 85c503 PCI-ISA bridge"); > } > > if (pci_get_class(dev) == PCIC_BRIDGE > @@ -947,6 +951,7 @@ > desc = isab_match(dev); > if (desc) { > device_set_desc_copy(dev, desc); > + > /* Don't bother adding more than one ISA bus */ > if (!devclass_get_device(devclass_find("isa"), 0)) > device_add_child(dev, "isa", -1, 0); > @@ -1050,8 +1055,6 @@ > return ("SiS 85c496"); > case 0x04061039: > return ("SiS 85c501"); > - case 0x00081039: > - return ("SiS 85c503"); > case 0x06011039: > return ("SiS 85c601"); > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 12:27:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C64CE14EA2 for ; Sat, 17 Apr 1999 12:27:56 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA22900; Sat, 17 Apr 1999 21:25:29 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904171925.VAA22900@freebsd.dk> Subject: Re: login In-Reply-To: from Annelise Anderson at "Apr 17, 1999 11:53:53 am" To: andrsn@andrsn.stanford.edu (Annelise Anderson) Date: Sat, 17 Apr 1999 21:25:29 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Annelise Anderson wrote: > When I log in to my -current machine (April 13 sources) it takes a > minute or two after the password is entered before the shell prompt > comes up: > > FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0) > > login: xanne > Password: > []<--cursor just stays here for a while > > This is on a LAN; it works fine at the console (and it worked > when it was 3.1). > > I can certainly live with this but it puzzles me. Would anyone > know why this might be happening? Sounds like a DNS timeout or something like that... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 12:35:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A784D155DF; Sat, 17 Apr 1999 12:35:36 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA06728; Sun, 18 Apr 1999 04:33:07 +0900 (JST) Message-ID: <3718E187.54571571@newsguy.com> Date: Sun, 18 Apr 1999 04:31:19 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Luoqi Chen Cc: freebsd-gnats-submit@FreeBSD.ORG, keith@email.gcn.net.tw, mzaki@e-mail.ne.jp, byung@wam.umd.edu, freebsd-current@FreeBSD.ORG, joki@kuebart.stuttgart.netsurf.de Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. References: <199904171549.LAA23743@lor.watermarkgroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > > > I've add UNICODE support to the Joliet patch. > > > > It contains few charsets now, but to add other charsets is very easy. > > Currently, iso8859-1 and euc-jp is included. > > > > Mixture of Joliet/RockRidge Extension is also available, however untested. > > > Cool! I think NTFS and VFATFS could use this code too, is it possible to > move the code to place like libkern/unicode? I'm concerned about the possible size of GENERIC with this code. Remember, it has to fit in the install floppy. (Well, not really, with loader, but I'm not the one who is getting killed because of a three-disks install.) Also, it adds a sysctl node, isn't that so? Directly under vfs, even, so it applies to all filesystems. Ideally, this should apply on a per-mount basis, and not even be in a sysctl. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 12:42:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id BAAB014FB2 for ; Sat, 17 Apr 1999 12:42:40 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id MAA11625; Sat, 17 Apr 1999 12:38:25 -0700 (PDT) Date: Sat, 17 Apr 1999 12:38:25 -0700 (PDT) From: Annelise Anderson To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: login In-Reply-To: <199904171925.VAA22900@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Soren Schmidt wrote: > It seems Annelise Anderson wrote: > > When I log in to my -current machine (April 13 sources) it takes a=20 > > minute or two after the password is entered before the shell prompt > > comes up: > >=20 > > FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0) > >=20 > > login: xanne > > Password: > > []<--cursor just stays here for a while > >=20 > > This is on a LAN; it works fine at the console (and it worked > > when it was 3.1). > >=20 > > I can certainly live with this but it puzzles me. Would anyone > > know why this might be happening? >=20 > Sounds like a DNS timeout or something like that... >=20 > -S=F8ren I think it was, thanks. I changed the order of the nameservers in resolv.conf and it no longer happens. :) =09Annelise=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 13:15:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 14677153ED for ; Sat, 17 Apr 1999 13:15:36 -0700 (PDT) (envelope-from camel@avias.com) Received: from CAMEL (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id AAA75416 for ; Sun, 18 Apr 1999 00:13:05 +0400 (MSD) (envelope-from camel@avias.com) Date: Sun, 18 Apr 1999 00:13:12 +0400 From: Ilya Naumov X-Mailer: The Bat! (v1.31) UNREG Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <19.990418@avias.com> To: Matthew Thyer Subject: Re[2]: ftp hangs on -current In-reply-To: <3718BFE7.95899006@camtech.net.au> References: <3718BFE7.95899006@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Matthew, Saturday, April 17, 1999, 9:07:51 PM, you wrote: >> I am getting problems similar to those outlined above. I don't run natd, either, but I do >> have a firewall enabled. (open rule) I've had to 'put' files rather than 'get' them, since my >> last build/installworld. (Yesterday's -current source) MT> How many of you are using RealTek network cards ? MT> They are crap in my experience (under any OS). hmm... i'm really using Realtek 8029 card. i'm in doubt that this network card is real reason of a problem with ftp, but i will try to replace it with 3Com 509 on Monday and report about results. Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 13:45:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0D34D14CA2 for ; Sat, 17 Apr 1999 13:45:26 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA09122; Sun, 18 Apr 1999 05:42:45 +0900 (JST) Message-ID: <3718EB67.950E7A4B@newsguy.com> Date: Sun, 18 Apr 1999 05:13:27 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Brian Feldman Cc: Jake Burkholder , Peter Wemm , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > > > IPFW works for me...but I'm loading the KLD. > > I like having my ipfw rules there BEFORE anything happens, hence before > rc(5). klds can be loaded by the loader. Hence, before /kernel. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 14: 4:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 5B64714CF9 for ; Sat, 17 Apr 1999 14:04:20 -0700 (PDT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id XAA21322; Sat, 17 Apr 1999 23:01:52 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id XAA01610; Sat, 17 Apr 1999 23:01:50 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199904172101.XAA01610@greenpeace.grondar.za> To: Annelise Anderson Cc: freebsd-current@freebsd.org Subject: Re: login In-Reply-To: Your message of " Sat, 17 Apr 1999 11:53:53 MST." References: Date: Sat, 17 Apr 1999 23:01:49 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Annelise Anderson wrote: > When I log in to my -current machine (April 13 sources) it takes a > minute or two after the password is entered before the shell prompt > comes up: > > FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0) > > login: xanne > Password: > []<--cursor just stays here for a while You haven't by any chance added kerberos by mistake, have you? :-) If you're not sure, send the output from "ldd /usr/libexec/rlogind". M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 15:36:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id AA69015411 for ; Sat, 17 Apr 1999 15:36:26 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA88695; Sat, 17 Apr 1999 15:33:55 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: NAKAGAWA Yoshihisa , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 17 Apr 1999 12:04:36 PDT." <199904171904.MAA75813@apollo.backplane.com> Date: Sat, 17 Apr 1999 15:33:55 -0700 Message-ID: <88666.924388435@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would ask people to STOP DOING THIS. Do not harass or ridicule someone > for not being fluent in english! Now, it is sorely true that someone wil Let me just reinforce this statement. It truly does no good at all and, speaking as a former non-speaker-of-the-native-language when I lived in Germany, I can say it's frustrating enough as it is just trying to make yourself understood in a language that's not your mother tongue, especially when you're reasonably intelligent in your own. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 15:59:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 13D3414D49; Sat, 17 Apr 1999 15:59:44 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id AAA21149; Sun, 18 Apr 1999 00:57:13 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id E9D3A3B; Sun, 18 Apr 1999 00:56:06 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id B36B21E2B; Sun, 18 Apr 1999 00:56:06 +0200 (CEST) Date: Sun, 18 Apr 1999 00:56:06 +0200 (CEST) From: Blaz Zupan To: freebsd-current@freebsd.org Cc: freebsd-isdn@freebsd.org Subject: new-bus changes break i4b Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After the latest new-bus changes in FreeBSD-current a kernel configured with ISDN support and PnP does not compile anymore. The following patch fixed the problem for me, at least the kernel compiles and runs. I don't have a PnP ISDN card (only a non-PnP one), but I do have PnP enabled in my kernel config file because my sound card needs it. The patch below is based on changes between /sys/i386/isa/sio.c and /sys/isa/sio.c and it could be completely wrong... *** /sys/i4b/layer1/i4b_isic_pnp.c.orig Sun Mar 7 17:08:16 1999 --- /sys/i4b/layer1/i4b_isic_pnp.c Sun Apr 18 00:48:46 1999 *************** *** 219,231 **** if(dev->id_driver == NULL) { dev->id_driver = &isicdriver; ! ! isa_devp = find_isadev(isa_devtab_net, &isicdriver, 0); ! ! if(isa_devp != NULL) ! { ! dev->id_id = isa_devp->id_id; ! } } if((dev->id_alive = isic_pnpprobe(dev, spci.port[1])) != 0) --- 219,225 ---- if(dev->id_driver == NULL) { dev->id_driver = &isicdriver; ! dev->id_id = isa_compat_nextid(); } if((dev->id_alive = isic_pnpprobe(dev, spci.port[1])) != 0) Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 16: 7:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id D28221500A for ; Sat, 17 Apr 1999 16:07:49 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id TAA24183; Sat, 17 Apr 1999 19:05:04 -0400 (EDT) Date: Sat, 17 Apr 1999 19:05:04 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Daniel C. Sobral" Cc: Jake Burkholder , Peter Wemm , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-Reply-To: <3718EB67.950E7A4B@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Daniel C. Sobral wrote: > Brian Feldman wrote: > > > > > IPFW works for me...but I'm loading the KLD. > > > > I like having my ipfw rules there BEFORE anything happens, hence before > > rc(5). > > klds can be loaded by the loader. Hence, before /kernel. Thanks for ruining my logic ;) But I really do hate overstuffing Makefile.inc in sys/modules so I can get the options I want. That's why for most things I use the kernel itself and not modules, really. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "Well, Windows works, using a loose definition of 'works'..." > > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ __ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 16:17:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B1F7814EE9 for ; Sat, 17 Apr 1999 16:17:47 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA54441; Sat, 17 Apr 1999 17:15:08 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA25095; Sat, 17 Apr 1999 17:15:30 -0600 (MDT) Message-Id: <199904172315.RAA25095@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: HEADS UP!!!! Important instructions for -current users! Cc: NAKAGAWA Yoshihisa , Peter Wemm , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 17 Apr 1999 10:45:09 PDT." <12290.924371109@zippy.cdrom.com> References: <12290.924371109@zippy.cdrom.com> Date: Sat, 17 Apr 1999 17:15:30 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let us not forget that much of the newconfig work can be used with newconfig shims in the newbus scheme. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 16:58:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id 3D47514EE9 for ; Sat, 17 Apr 1999 16:58:29 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.1/8.9.1) with ESMTP id BAA12947; Sun, 18 Apr 1999 01:55:58 +0200 (CEST) Message-Id: <199904172355.BAA12947@midten.fast.no> To: dillon@apollo.backplane.com Cc: current@FreeBSD.ORG Subject: Re: successfull SMP / current on duel P-III box.Yahhhh. I've successfully brought -current up in SMP on a duel P-III box. From: Tor.Egge@fast.no In-Reply-To: Your message of "Sat, 17 Apr 1999 00:36:00 -0700 (PDT)" References: <199904170736.AAA67808@apollo.backplane.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 18 Apr 1999 01:55:58 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have one problem, though. During the kernel boot: > > isa_dmainit(2, 1024) failed > > And, of course, any access to something that needs isa > dma (e.g. floppy) panics. It's a large-memory machine (1G). > I was under the impression that this was supposed to be fixed > in the vm/vm_page.c commit: [...] > Anyone have any ideas? Yes. Using a recent -current GENERIC kernel, I reproduced the problem with a machine having 512 MB memory. All physical memory below 16 MB is used. vm_page_list_find uses TAILQ_LAST when prefer_zero is set, thus pv_table occupies the physical memory below 640 KB. The remaining physical memory below 16 MB is allocated to vm_page_array and vm_page_buckets in vm_page_startup, or was reserved earlier (e.g. kernel text, data, bss). IMO, vm_page_array and vm_page_buckets should not use physical memory below 16 MB on large-memory machines. This can be achieved by modyfing the contents of phys_avail, causing the largest region to be above 16 MB. GENERIC kernel: (kgdb) print phys_avail $66 = {4096, 651264, 3624960, 536862720, 0, 0, 0, 0, 0, 0} The kernel I normally use: (kgdb) print phys_avail $1 = {4096, 651264, 3301376, 16777216, 16777216, 536608768, 0, 0, 0, 0} This works fine for machines with 512 MB and 1 GB memory. For machines with more than 2 GB memory, the size of pv_table might become a problem. Alternating between TAILQ_INSERT_HEAD and TAILQ_INSERT_TAIL in vm_page_startup might be a workaround for this second problem (causing the memory below 16 MB not already allocated by vm_page_startup to be in the middle of the page queues). - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 17: 2:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id A403B1540D for ; Sat, 17 Apr 1999 17:02:34 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id CAA24950; Sun, 18 Apr 1999 02:00:07 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.2) id BAA96006; Sun, 18 Apr 1999 01:56:59 +0200 (CEST) (envelope-from andreas) Date: Sun, 18 Apr 1999 01:56:58 +0200 From: Andreas Klemm To: Annelise Anderson Cc: Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: login Message-ID: <19990418015658.A95962@titan.klemm.gtn.com> References: <199904171925.VAA22900@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Annelise Anderson on Sat, Apr 17, 1999 at 12:38:25PM -0700 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 17, 1999 at 12:38:25PM -0700, Annelise Anderson wrote: > > I think it was, thanks. I changed the order of the nameservers > in resolv.conf and it no longer happens. :) What about setting up a caching DNS server on your machine ? You could configure forwarders. options { directory "/etc/namedb"; forwarders { aaa.bbb.ccc.ddd; }; }; in /etc/resolv.conf domain your.domain nameserver 127.0.0.1 Had to do many many (~600) DNS requests in a script and had a lame nameserver over network about 3-4 hops away. After configuring a local DNS server the script was much (!) faster. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 18:22:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id ED6D614EE9 for ; Sat, 17 Apr 1999 18:22:18 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id <2RSVNTSM>; Sun, 18 Apr 1999 02:18:03 +0100 Message-ID: From: paul@originative.co.uk To: robert+freebsd@cyrus.watson.org, freebsd-current@freebsd.org Subject: RE: lnc0: broke for us between 3.1 and 4.0? Date: Sun, 18 Apr 1999 02:18:02 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Robert Watson [mailto:robert@cyrus.watson.org] > Sent: 17 April 1999 01:16 > To: freebsd-current@freebsd.org > Subject: lnc0: broke for us between 3.1 and 4.0? > > After upgrading to -current, the probe failed as follows > (when config was > used on the GENERIC quote): > > lnc0 at 0x300-0x317 irq 5 drq 6 on isa > lnc0: Memory allocated above 16Mb limit > > Any suggestions as to what might done to fix it? If we > switch back to the > old kernel, it boots fine, so presumably it was some change between > 3.1-RELEASE and 4.0-CURRENT, either in the config file or the > lnc driver? I've just committed a fix for this. It was caused by the change to the way vm_page.c allocates memory Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 20:12:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.wwwtek.com (dns.wwwtek.com [209.153.255.2]) by hub.freebsd.org (Postfix) with ESMTP id 2ABC114BFF for ; Sat, 17 Apr 1999 20:12:34 -0700 (PDT) (envelope-from ted@stargate.org) Received: from d185d026b.rochester.rr.com (IDENT:ted@d185d026b.rochester.rr.com [24.93.2.107]) by dns.wwwtek.com (8.9.2/8.9.2) with ESMTP id XAA75963 for ; Sat, 17 Apr 1999 23:16:21 -0700 (PDT) (envelope-from ted@stargate.org) Received: from localhost (ted@localhost) by d185d026b.rochester.rr.com (8.8.7/8.8.7) with ESMTP id XAA17723 for ; Sat, 17 Apr 1999 23:05:31 -0400 Date: Sat, 17 Apr 1999 23:05:31 -0400 (EDT) From: "T.D. Brace" X-Sender: ted@d185d026b.rochester.rr.com To: freebsd-current@freebsd.org Subject: Laptop support Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone tell me if I can get freebsd 3.1 running on a compaq pressario 1675 - I'm worried about the pcmcia controller being recognized (and my xircom re-100btx working). Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 21:58:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from work.mzaki.nom (174.pool15.tokyo.att.ne.jp [165.76.220.189]) by hub.freebsd.org (Postfix) with ESMTP id 6A7C514FAB; Sat, 17 Apr 1999 21:58:44 -0700 (PDT) (envelope-from mzaki@e-mail.ne.jp) Received: from localhost (localhost [127.0.0.1]) by work.mzaki.nom (8.9.2/8.9.2) with ESMTP id NAA19054; Sun, 18 Apr 1999 13:55:59 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) To: dcs@newsguy.com Cc: luoqi@watermarkgroup.com, freebsd-gnats-submit@FreeBSD.ORG, byung@wam.umd.edu, freebsd-current@FreeBSD.ORG, joki@kuebart.stuttgart.netsurf.de Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. In-Reply-To: <3718E187.54571571@newsguy.com> References: <199904171549.LAA23743@lor.watermarkgroup.com> <3718E187.54571571@newsguy.com> X-Mailer: Mew version 1.94b7 on XEmacs 21.0 (20 minutes to Nikko) X-fingerprint: BD 86 CD D9 66 FD 75 B0 A8 43 4B C4 E2 1B F5 B5 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990418135558W.mzaki@e-mail.ne.jp> Date: Sun, 18 Apr 1999 13:55:58 +0900 From: Motomichi Matsuzaki X-Dispatcher: imput version 990212(IM106) Lines: 57 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Daniel C. Sobral" > Luoqi Chen wrote: > > > > > I've add UNICODE support to the Joliet patch. > > > > > > It contains few charsets now, but to add other charsets is very easy. > > > Currently, iso8859-1 and euc-jp is included. > > > > > Cool! I think NTFS and VFATFS could use this code too, is it possible to > > move the code to place like libkern/unicode? > > I'm concerned about the possible size of GENERIC with this code. > Remember, it has to fit in the install floppy. (Well, not really, > with loader, but I'm not the one who is getting killed because of a > three-disks install.) The UNICODE routines consist of these files. charset/charset.c mandatory iso8859-1.c recommended euc-jp.c optional <-- BIG! the object file has 53k bytes encoding/encoding.c mandatory euc.c optional The 'mandatory + recommended' object size is no more than 5 kbytes. The GENERIC kernel does not require necessarily the euc-jp support or any other charsets. I think the iso8859-1 support alone is sufficient for GENERIC. The custom kernels can have the euc-jp support through the CHARSET_EUC_JP and ENCODING_EUC kernel configure option. (They are currently defined at the top of the source files.) > Also, it adds a sysctl node, isn't that so? Directly under vfs, > even, so it applies to all filesystems. Ideally, this should apply > on a per-mount basis, and not even be in a sysctl. Yes. sysctl is not the best idea. I think the charset preferences should apply on per-process basis ideally. The operator mounts some disks. The users access the disks in their own preferred charset. The UNICODE is a multiligual codeset, so we shoud not suppose any specific charset on the disk. Therefore, a per-mount basis is not enough. If the routines can refer the users' environment 'LC_CTYPE', it is fine idea. But it can't, I suppose. -- Motomichi Matsuzaki Dept. of Biological Science, Fuculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 22:48:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 6A69E15164 for ; Sat, 17 Apr 1999 22:48:15 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id BAA02597; Sun, 18 Apr 1999 01:00:49 -0500 (EST) Date: Sun, 18 Apr 1999 01:00:47 -0500 (EST) From: Alfred Perlstein To: Motomichi Matsuzaki Cc: dcs@newsguy.com, freebsd-current@FreeBSD.ORG Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. In-Reply-To: <19990418135558W.mzaki@e-mail.ne.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Motomichi Matsuzaki wrote: > > From: "Daniel C. Sobral" > > > > I'm concerned about the possible size of GENERIC with this code. > > Remember, it has to fit in the install floppy. (Well, not really, > > with loader, but I'm not the one who is getting killed because of a > > three-disks install.) > > The UNICODE routines consist of these files. > > charset/charset.c mandatory > iso8859-1.c recommended > euc-jp.c optional <-- BIG! the object file has 53k bytes > > encoding/encoding.c mandatory > euc.c optional > > The 'mandatory + recommended' object size is no more than 5 kbytes. > The GENERIC kernel does not require necessarily > the euc-jp support or any other charsets. > I think the iso8859-1 support alone is sufficient for GENERIC. > > The custom kernels can have the euc-jp support through > the CHARSET_EUC_JP and ENCODING_EUC kernel configure option. > (They are currently defined at the top of the source files.) couldn't this be done as a KLD? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 22:55:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id C4A0F14E0C for ; Sat, 17 Apr 1999 22:55:30 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id OAA27172; Sun, 18 Apr 1999 14:52:57 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: mzaki@e-mail.ne.jp Cc: freebsd-current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. From: Tomoaki NISHIYAMA In-Reply-To: <19990418135558W.mzaki@e-mail.ne.jp> References: <199904171549.LAA23743@lor.watermarkgroup.com> <3718E187.54571571@newsguy.com> <19990418135558W.mzaki@e-mail.ne.jp> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990418145256H.tomoaki@moss.nibb.ac.jp> Date: Sun, 18 Apr 1999 14:52:56 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Motomichi Matsuzaki Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. Date: Sun, 18 Apr 1999 13:55:58 +0900 Message-ID: <19990418135558W.mzaki@e-mail.ne.jp> mzaki> If the routines can refer the users' environment 'LC_CTYPE', mzaki> it is fine idea. But it can't, I suppose. It may be possible to set the kernel behavior via a call to setlocale(3). That is, change the charset per process within setlocale routine who knows the LC_CTYPE. Another way which have larger impact on the whole system is to change the start up routine to look for LC_CTYPE and change the behavior. The last solution is to make the charset of a process inheritable to child processes. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 22:56: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-34.ppp.wenet.net [206.15.85.34]) by hub.freebsd.org (Postfix) with ESMTP id 91A6814EF3 for ; Sat, 17 Apr 1999 22:56:04 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id WAA60320 for ; Sat, 17 Apr 1999 22:53:40 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sat, 17 Apr 1999 22:53:39 -0700 (PDT) From: Alex Zepeda To: current Subject: newbus and modem(s) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm as excited as anyone to see progress, especially if it means the ability to modularize the kernel and load various drivers on demand. But, alas, it seems this whole thing was rushed horribly. The first thing I noticed was the panic I got, in atkbd_isa_intr, which has since been fixed. But once I got my system booted, I noticed that it didn't detect my PnP modem (a quick check revealed that the PnP code was #if 0'd out). So, I tried my external modem, which worked. But in the process of downloading email, I got about 5 sio overflows. I've left my box up for a few days and rebuilt world while downloading stuff, and only gotten around one or two overflows. I looked at un #ifdef'n the PnP code, but some things seem to have changed substantially. Where is there any documentation on how to un-butcher drivers or even "properly" fix them? Sure it looks like the pcm driver works and works with the PnP code but it uses the "shims". - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 17 23:46:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 33F2914CE5 for ; Sat, 17 Apr 1999 23:46:51 -0700 (PDT) (envelope-from ian@apdata.com.au) Received: from apdata.com.au (localhost [127.0.0.1]) by rose.niw.com.au (Postfix) with ESMTP id 7A164A3203 for ; Sun, 18 Apr 1999 16:14:26 +0930 (CST) Message-ID: <37197F4A.CA229E8A@apdata.com.au> Date: Sun, 18 Apr 1999 16:14:26 +0930 From: Ian West Organization: Applied Data Control X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: IPFW does not seem to work except as kld on recent builds (last day or so) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I noticed that IPFW as a built in kernel options quietly doesn't seem to work, no compile errors, but the resultant kernel passes evrything and does not appear to contain ipfw funtionality. ipfw -a l returns ipfw: getsockopt(IP_FW_GET): Protocol not available. kldload ipfw and it all works fine. Is the intention for it to longer be a available except as a kld module ? Thankyou for any feedback. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 0:12:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id EED5914C18 for ; Sun, 18 Apr 1999 00:12:43 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 26513 invoked from network); 18 Apr 1999 07:10:19 -0000 Received: from userah79.uk.uudial.com (HELO k2c.co.uk) (62.188.133.10) by smtp.dial.pipex.com with SMTP; 18 Apr 1999 07:10:19 -0000 Message-ID: <3719854D.FD6326DF@k2c.co.uk> Date: Sun, 18 Apr 1999 08:10:05 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Subject: Make World breaks in /sys/modules/fxp Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As stated. The Makefile calls for perl5, which is not available at that time. Replacing perl5 by perl solves the problem. Cheers, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 0:28:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8162314EC4 for ; Sun, 18 Apr 1999 00:28:55 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA77697; Sun, 18 Apr 1999 00:26:15 -0700 (PDT) (envelope-from dillon) Date: Sun, 18 Apr 1999 00:26:15 -0700 (PDT) From: Matthew Dillon Message-Id: <199904180726.AAA77697@apollo.backplane.com> To: Andreas Klemm Cc: Annelise Anderson , Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: login References: <199904171925.VAA22900@freebsd.dk> <19990418015658.A95962@titan.klemm.gtn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Sat, Apr 17, 1999 at 12:38:25PM -0700, Annelise Anderson wrote: :> :> I think it was, thanks. I changed the order of the nameservers :> in resolv.conf and it no longer happens. :) : :What about setting up a caching DNS server on your machine ? :You could configure forwarders. : :options { : directory "/etc/namedb"; : forwarders { : aaa.bbb.ccc.ddd; : }; :}; : :in /etc/resolv.conf : :domain your.domain :nameserver 127.0.0.1 : :Had to do many many (~600) DNS requests in a script and had :a lame nameserver over network about 3-4 hops away. : :After configuring a local DNS server the script was much (!) faster. : :-- :Andreas Klemm http://www.FreeBSD.ORG/~andreas I'm going to pass on a lesson I learned at BEST. Setting a forwarders chain sucks, because named doesn't do the right thing with it -- even if you have multiple entries, if the first one is unreachable it will create a significant delay for nearly all your DNS requests which can seriously degrade scripts and servers. The safest way to set up a reliable DNS server is very similar to what you have above, but without forwarders. * You setup a local DNS server * You install a root cache. i.e., no forwarders. No remote cache... only local caching. root.zone can be obtained from ftp.rs.internic.net as the file domain/root.zone.gz. zone "." { type hint; file "root.zone"; }; * You then secondary the domains that are most critical for your machine's proper booting and operation. For example, at BEST each of our machines secondaries the best.com domain. You need to do this sort of thing to ensure that your machine is able to boot normally into a getty even when it is disconnected from the net, so you can at least login to it from the console. This guarentees that the domains the system needs to boot are cached locally as of the time of the poweron/reboot. If not, the machine will still eventually finish booting, but it could take a long long time to get past all the myrid DNS timeouts. zone "best.com" { type slave; file "s/best.com"; masters { 209.24.149.41; 209.157.102.11; 209.24.149.42; }; }; By setting up your DNS this way, you generate a small amount of extra net traffic but you get an order of magnitude better reliability out of it. By forcing DNS to do lookups through the NS record structure, you get around problems with ( for example ) domains which have lame nameservers. The NS structure is a parallel/least-time poll. A forwarders structure runs a sequential/timeout poll. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 1:48:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 69E2114F86 for ; Sun, 18 Apr 1999 01:48:23 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id KAA21168; Sun, 18 Apr 1999 10:45:18 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sun, 18 Apr 1999 10:45:18 +0200 (CEST) From: Leif Neland To: Alex Zepeda Cc: current@freebsd.org Subject: Re: newbus and modem(s) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Alex Zepeda wrote: > I'm as excited as anyone to see progress, especially if it means the > ability to modularize the kernel and load various drivers on demand. But, > alas, it seems this whole thing was rushed horribly. > > The first thing I noticed was the panic I got, in atkbd_isa_intr, which > has since been fixed. Well, that is what you have to expect when running current. You are a betatester, and you can't expect the authors to have access to every combination of hardware. On the other hand, I have been cvsup'ing and making world every night for the last 6 months or so, and besides having to do the changes in "heads up"-messages, I haven't had any troubles. Right, make world do fail sometimes, often because I have cvsup'ed during commits, but the system has never been unbootable. I do this every night from cron cd /usr/src /usr/local/bin/cvsup -s -l /tmp/cvslock -L 2 -P - -h cvsup.dk.freebsd.org /root/ports-supfile|tee /dev/ttyv7|mail root /usr/local/bin/cvsup -s -l /tmp/cvslock -L 2 -P - -h cvsup.dk.freebsd.org /root/standard-supfile|tee /dev/ttyv7|mail root make -DNOGAMES world && cd /usr/src/sys/i386/conf && config GINA && cd /usr/src/sys/compile/GINA && make depend && make && make install && echo reboot | at +5minutes Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 1:55:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id ECE3614F86 for ; Sun, 18 Apr 1999 01:55:14 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA85884; Sun, 18 Apr 1999 09:57:51 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 18 Apr 1999 09:57:20 +0100 (BST) From: Doug Rabson To: Alex Zepeda Cc: current Subject: Re: newbus and modem(s) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, Alex Zepeda wrote: > I'm as excited as anyone to see progress, especially if it means the > ability to modularize the kernel and load various drivers on demand. But, > alas, it seems this whole thing was rushed horribly. > > The first thing I noticed was the panic I got, in atkbd_isa_intr, which > has since been fixed. > > But once I got my system booted, I noticed that it didn't detect my PnP > modem (a quick check revealed that the PnP code was #if 0'd out). So, I > tried my external modem, which worked. But in the process of downloading > email, I got about 5 sio overflows. I've left my box up for a few days > and rebuilt world while downloading stuff, and only gotten around one or > two overflows. > > I looked at un #ifdef'n the PnP code, but some things seem to have changed > substantially. Where is there any documentation on how to un-butcher > drivers or even "properly" fix them? > > Sure it looks like the pcm driver works and works with the PnP code but it > uses the "shims". I'm not sure about pnp but this patch should fix the overflows (not tested): Index: sio.c =================================================================== RCS file: /home/ncvs/src/sys/isa/sio.c,v retrieving revision 1.224 diff -u -r1.224 sio.c --- sio.c 1999/04/17 01:02:27 1.224 +++ sio.c 1999/04/18 08:53:36 @@ -349,7 +349,7 @@ static driver_t sio_driver = { driver_name, sio_methods, - DRIVER_TYPE_TTY, + DRIVER_TYPE_TTY|DRIVER_TYPE_FAST, sizeof(struct com_s), }; -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 2: 2:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6C4B014F86 for ; Sun, 18 Apr 1999 02:02:57 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA01013; Sun, 18 Apr 1999 02:00:30 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Alex Zepeda Cc: current Subject: Re: newbus and modem(s) In-reply-to: Your message of "Sat, 17 Apr 1999 22:53:39 PDT." Date: Sun, 18 Apr 1999 02:00:30 -0700 Message-ID: <1011.924426030@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm as excited as anyone to see progress, especially if it means the > ability to modularize the kernel and load various drivers on demand. But, > alas, it seems this whole thing was rushed horribly. Not at all, it's simply something which will require some time to work out the details of in -current. People forget all too often that -current is the bleeding edge and you shouldn't even bother (truly) to track it unless you're willing and able to bleed occasionally. I'm actually always happy to see this lesson driven home again when it looks like people are getting waaaaay too complacent about -current. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 2:15:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from pa.scotland.net (pa1.scotland.net [194.247.64.132]) by hub.freebsd.org (Postfix) with ESMTP id 875F41522A for ; Sun, 18 Apr 1999 02:15:52 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from [148.176.232.135] (helo=timog.prestel.co.uk) by pa.scotland.net with esmtp (Exim 1.90 #4) for current@freebsd.org id 10Yndm-0000TE-00; Sun, 18 Apr 1999 10:13:28 +0100 Received: (qmail 10738 invoked by uid 1002); 16 Apr 1999 07:35:44 -0000 Date: Fri, 16 Apr 1999 08:35:44 +0100 From: Timo Geusch To: Warner Losh Cc: current@freebsd.org Subject: Re: make aout-to-elf on -current? Message-ID: <19990416083544.A10699@timog.prestel.co.uk> References: <199904160654.AAA07198@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904160654.AAA07198@harmony.village.org>; from Warner Losh on Fri, Apr 16, 1999 at 12:54:32AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had to try this due to an unfortunate 'accident', and no, it currently does not work. The aout assembler complains about a '.section' tag in the assembly output of contrib/gcc/cp/tinfo2.cc. You have to elfify your system with a non-egcs compiler before you can move onto using egcs to make the world. Timo On Fri, Apr 16, 1999 at 12:54:32AM -0600, Warner Losh wrote: > Does make aout-to-elf still purport to work from a 2.2.8R system to > a recent (like today's) current? > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 2:57:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 1EEC61515D for ; Sun, 18 Apr 1999 02:57:51 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id LAA14901; Sun, 18 Apr 1999 11:55:18 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.2) id LAA12276; Sun, 18 Apr 1999 11:54:02 +0200 (CEST) (envelope-from andreas) Date: Sun, 18 Apr 1999 11:54:02 +0200 From: Andreas Klemm To: Matthew Dillon Cc: Andreas Klemm , Annelise Anderson , Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: login Message-ID: <19990418115402.A11762@titan.klemm.gtn.com> References: <199904171925.VAA22900@freebsd.dk> <19990418015658.A95962@titan.klemm.gtn.com> <199904180726.AAA77697@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904180726.AAA77697@apollo.backplane.com>; from Matthew Dillon on Sun, Apr 18, 1999 at 12:26:15AM -0700 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 18, 1999 at 12:26:15AM -0700, Matthew Dillon wrote: > > Setting a forwarders chain sucks, because named doesn't do the right thing > with it -- even if you have multiple entries, if the first one is > unreachable it will create a significant delay for nearly all your > DNS requests which can seriously degrade scripts and servers. Uh, didn't know that, thanks. Well, here I use only one forwarder entry as the leaf site of an ISP. I forward all DNS traffic to the DNS Server, that is located in the same segment as the NAS. Don't want to act as a secondary for the whole gtn.com. domain, because my machine often boots, so the extra traffic of the zone transfers isn't welcome ;-) > The safest way to set up a reliable DNS server is very similar to what > you have above, but without forwarders. O.k., understand that. But would do that only in my own network. If you have for example a machine in a customers network for doing some analysis task, I wouldn't setup secondaries, to be more silent in the network. > * You install a root cache. i.e., no forwarders. No remote cache... only > local caching. root.zone can be obtained from ftp.rs.internic.net as > the file domain/root.zone.gz. I run this from cron, this makes things easier on the long run: 0 18 * * 0 dig @a.root-servers.net . ns > /etc/namedb/named.root.new && mv /etc/namedb/named.root.new /etc/namedb/named.root > * You then secondary the domains that are most critical for your machine's > proper booting and operation. For example, at BEST each of our machines > secondaries the best.com domain. Good idea. Andreas //// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 4:33: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id ABE0A15094 for ; Sun, 18 Apr 1999 04:32:44 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id NAA70508; Sun, 18 Apr 1999 13:30:00 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199904181130.NAA70508@zibbi.mikom.csir.co.za> Subject: Re: HEADS UP!!!! Important instructions for -current users! In-Reply-To: <19990416213043.95C7B1F69@spinner.netplex.com.au> from Peter Wemm at "Apr 17, 1999 05:30:41 am" To: peter@netplex.com.au (Peter Wemm) Date: Sun, 18 Apr 1999 13:30:00 +0200 (SAT) Cc: current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As of a few minutes ago, a minimal set of changes to bring the so-called > 'new-bus' functionality to the i386 kernel in -current. > It looks like the stat clock isn't started after this. I have tried a SMP and UNI kernel and both behave the same. Looking with vmstat -i and systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate also have profhz and stathz as 100. A kernel of about a week ago doesn't have this problem. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 4:41:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CB8E2151CD; Sun, 18 Apr 1999 04:41:51 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA21294; Sun, 18 Apr 1999 20:39:20 +0900 (JST) Message-ID: <3719C0DF.6A8E2A29@newsguy.com> Date: Sun, 18 Apr 1999 20:24:15 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Motomichi Matsuzaki Cc: luoqi@watermarkgroup.com, freebsd-gnats-submit@FreeBSD.ORG, byung@wam.umd.edu, freebsd-current@FreeBSD.ORG, joki@kuebart.stuttgart.netsurf.de Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. References: <199904171549.LAA23743@lor.watermarkgroup.com> <3718E187.54571571@newsguy.com> <19990418135558W.mzaki@e-mail.ne.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Motomichi Matsuzaki wrote: > > The 'mandatory + recommended' object size is no more than 5 kbytes. > The GENERIC kernel does not require necessarily > the euc-jp support or any other charsets. > I think the iso8859-1 support alone is sufficient for GENERIC. > > The custom kernels can have the euc-jp support through > the CHARSET_EUC_JP and ENCODING_EUC kernel configure option. > (They are currently defined at the top of the source files.) But are they set by default to include euc-jp? Well, that's a minor point. > Yes. sysctl is not the best idea. > > I think the charset preferences should apply on per-process basis ideally. > > The operator mounts some disks. > The users access the disks in their own preferred charset. > > The UNICODE is a multiligual codeset, > so we shoud not suppose any specific charset on the disk. > Therefore, a per-mount basis is not enough. > > If the routines can refer the users' environment 'LC_CTYPE', > it is fine idea. But it can't, I suppose. Yeah, Terry Lambert has preached on this before. My point is that I can't get the patch committed with it using a sysctl node. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 4:45:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id D993215094 for ; Sun, 18 Apr 1999 04:45:46 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id DFE051F58; Sun, 18 Apr 1999 19:43:20 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay Cc: current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 18 Apr 1999 13:30:00 +0200." <199904181130.NAA70508@zibbi.mikom.csir.co.za> Date: Sun, 18 Apr 1999 19:43:20 +0800 From: Peter Wemm Message-Id: <19990418114321.DFE051F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > > As of a few minutes ago, a minimal set of changes to bring the so-called > > 'new-bus' functionality to the i386 kernel in -current. > > > > It looks like the stat clock isn't started after this. I have tried a SMP > and UNI kernel and both behave the same. Looking with vmstat -i and > systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate > also have profhz and stathz as 100. A kernel of about a week ago doesn't > have this problem. Hmm... [7:38pm]~-103# sysctl kern.clockrate kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024, stathz = 128 } And from systat: zfod Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt cow 230 total 2 2 23 59 2 141 230 30 6 16016 wire pci irq11 15636 act 2 pci irq5 1.1%Sys 1.1%Intr 0.8%User 97.0%Nice 0.0%Idl 24480 inact pci irq6 | | | | | | | | | | 3736 cache pci irq4 =>---------------------------------------------- 1400 free pci irq7 daefr 100 clk0 irq2 Namei Name-cache Dir-cache prcfr 128 rtc0 irq8 The labelling of the source column is known to be broken at the moment, there are a number of key places where the fake isa unit number is getting passed down to the lower level code. This will be fixed up shortly. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 6:17:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 64E4814F79 for ; Sun, 18 Apr 1999 06:17:43 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from giovannelli.it (modem09.masternet.it [194.184.65.19]) by kirk.giovannelli.it (8.9.3/8.9.2) with ESMTP id NAA00696 for ; Sun, 18 Apr 1999 13:15:04 GMT (envelope-from gmarco@giovannelli.it) Message-ID: <3719DAD8.90EE391C@giovannelli.it> Date: Sun, 18 Apr 1999 15:15:04 +0200 From: Gianmarco Giovannelli X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Make world fails - 990418 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 4.0-current ===> sys/modules/fdesc @ -> /usr/src/sys machine -> /usr/src/sys/i386/include sh /usr/src/sys/modules/fdesc/../../kern/vnode_if.sh /usr/src/sys/modules/fdesc/../../kern/vnode_if.src cc -nostdinc -O -pipe -DFDESC -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/fdesc -I/usr/obj/usr/src/sys/modules/fdesc/@ -I/usr/obj/usr/src/tmp/usr/include -DVFS_LKM -DVFS_KLD -c /usr/src/sys/modules/fdesc/../../miscfs/fdesc/fdesc_vfsops.c cc -nostdinc -O -pipe -DFDESC -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/fdesc -I/usr/obj/usr/src/sys/modules/fdesc/@ -I/usr/obj/usr/src/tmp/usr/include -DVFS_LKM -DVFS_KLD -c /usr/src/sys/modules/fdesc/../../miscfs/fdesc/fdesc_vnops.c /usr/src/sys/modules/fdesc/../../miscfs/fdesc/fdesc_vnops.c: In function `fdesc_open': /usr/src/sys/modules/fdesc/../../miscfs/fdesc/fdesc_vnops.c:352: warning: enumeration value `Froot' not handled in switch /usr/src/sys/modules/fdesc/../../miscfs/fdesc/fdesc_vnops.c:352: warning: enumeration value `Fdevfd' not handled in switch /usr/src/sys/modules/fdesc/../../miscfs/fdesc/fdesc_vnops.c:352: warning: enumeration value `Flink' not handled in switch gensetdefs fdesc_vfsops.o fdesc_vnops.o cc -nostdinc -O -pipe -DFDESC -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/fdesc -I/usr/obj/usr/src/sys/modules/fdesc/@ -I/usr/obj/usr/src/tmp/usr/include -DVFS_LKM -DVFS_KLD -c setdef0.c cc -nostdinc -O -pipe -DFDESC -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/fdesc -I/usr/obj/usr/src/sys/modules/fdesc/@ -I/usr/obj/usr/src/tmp/usr/include -DVFS_LKM -DVFS_KLD -c setdef1.c ld -Bshareable -o fdesc.ko setdef0.o fdesc_vfsops.o fdesc_vnops.o setdef1.o ===> sys/modules/fxp @ -> /usr/src/sys machine -> /usr/src/sys/i386/include echo "#define NFXP 1" > fxp.h echo "#define NBPFILTER 0" > bpfilter.h touch opt_bdg.h perl5 /usr/src/sys/modules/fxp/../../kern/makedevops.pl -h /usr/src/sys/modules/fxp/../../kern/device_if.m perl5: not found *** Error code 1 I cvsuped about one hour ago, but the problem was there from before... -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 6:35:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B229814C80 for ; Sun, 18 Apr 1999 06:35:19 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id OAA86658; Sun, 18 Apr 1999 14:37:42 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 18 Apr 1999 14:37:42 +0100 (BST) From: Doug Rabson To: Gianmarco Giovannelli Cc: current@freebsd.org Subject: Re: Make world fails - 990418 In-Reply-To: <3719DAD8.90EE391C@giovannelli.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Gianmarco Giovannelli wrote: > > 4.0-current > ... > perl5: not found > *** Error code 1 > > I cvsuped about one hour ago, but the problem was there from before... Fixed. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 7: 9:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8ACB314C28 for ; Sun, 18 Apr 1999 07:09:52 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA18370; Sun, 18 Apr 1999 23:07:22 +0900 (JST) Message-ID: <3719E6AC.FC43AB31@newsguy.com> Date: Sun, 18 Apr 1999 23:05:32 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Doug Rabson Cc: current Subject: Re: newbus and modem(s) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > > I'm not sure about pnp but this patch should fix the overflows (not > tested): Seems to work fine for me (I had the sio overflow problems too). > Index: sio.c > =================================================================== > RCS file: /home/ncvs/src/sys/isa/sio.c,v > retrieving revision 1.224 > diff -u -r1.224 sio.c > --- sio.c 1999/04/17 01:02:27 1.224 > +++ sio.c 1999/04/18 08:53:36 > @@ -349,7 +349,7 @@ > static driver_t sio_driver = { > driver_name, > sio_methods, > - DRIVER_TYPE_TTY, > + DRIVER_TYPE_TTY|DRIVER_TYPE_FAST, > sizeof(struct com_s), > }; -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 7:12:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS30.kng.mesh.ad.jp [133.205.214.30]) by hub.freebsd.org (Postfix) with ESMTP id E20C015260 for ; Sun, 18 Apr 1999 07:12:25 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id MAA06222; Sun, 18 Apr 1999 12:24:35 +0900 (JST) Message-Id: <199904180324.MAA06222@chandra.eatell.msr.prug.or.jp> To: Warner Losh Cc: "Jordan K. Hubbard" , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 17 Apr 1999 17:15:30 CST." <199904172315.RAA25095@harmony.village.org> Date: Sun, 18 Apr 1999 12:24:35 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Let us not forget that much of the newconfig work can be used with > newconfig shims in the newbus scheme. Probably some simple drivers for newconfig works with newconfig shims, but bus code that depends on newconfig may not work. I don't go to new-bus, this direction is disunion of BSDs. It is bad decision. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 7:20:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (Postfix) with ESMTP id B875514C13 for ; Sun, 18 Apr 1999 07:20:27 -0700 (PDT) (envelope-from w@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id QAA15511; Sun, 18 Apr 1999 16:18:02 +0200 (CEST) (envelope-from w@panke.de.freebsd.org) Received: (from w@localhost) by paula.panke.de.freebsd.org (8.9.3/8.8.8) id PAA59282; Sun, 18 Apr 1999 15:52:11 +0200 (CEST) (envelope-from w) Message-ID: <19990418155211.60645@panke.de.freebsd.org> Date: Sun, 18 Apr 1999 15:52:11 +0200 From: Wolfram Schneider To: Warner Losh , current@FreeBSD.ORG Subject: Re: make aout-to-elf on -current? References: <199904160654.AAA07198@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199904160654.AAA07198@harmony.village.org>; from Warner Losh on Fri, Apr 16, 1999 at 12:54:32AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-04-16 00:54:32 -0600, Warner Losh wrote: > Does make aout-to-elf still purport to work from a 2.2.8R system to > a recent (like today's) current? I updated my laptop 4 weeks ago from 2.2.6R to 4.0-current. There where only minor problems, see PR bin/10784 and bin/10785 -- Wolfram Schneider http://wolfram.schneider.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 7:23:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 87A5314C13 for ; Sun, 18 Apr 1999 07:23:51 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id HAA02264; Sun, 18 Apr 1999 07:20:29 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: NAKAGAWA Yoshihisa Cc: Warner Losh , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sun, 18 Apr 1999 12:24:35 +0900." <199904180324.MAA06222@chandra.eatell.msr.prug.or.jp> Date: Sun, 18 Apr 1999 07:20:29 -0700 Message-ID: <2262.924445229@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't go to new-bus, this direction is disunion of BSDs. It is > bad decision. I'm sorry that you feel this way, but I can only re-state that better communication could have prevented this in the first place and hope that you've learned your own lessons from this exercise. If you haven't, then a good opportunity for learning has simply been wasted. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 7:53:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 585CE14FC3 for ; Sun, 18 Apr 1999 07:53:40 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id QAA73581; Sun, 18 Apr 1999 16:51:02 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199904181451.QAA73581@zibbi.mikom.csir.co.za> Subject: Re: HEADS UP!!!! Important instructions for -current users! In-Reply-To: <19990418114321.DFE051F58@spinner.netplex.com.au> from Peter Wemm at "Apr 18, 1999 07:43:20 pm" To: peter@netplex.com.au (Peter Wemm) Date: Sun, 18 Apr 1999 16:51:02 +0200 (SAT) Cc: current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > John Hay wrote: > > > As of a few minutes ago, a minimal set of changes to bring the so-called > > > 'new-bus' functionality to the i386 kernel in -current. > > > > > > > It looks like the stat clock isn't started after this. I have tried a SMP > > and UNI kernel and both behave the same. Looking with vmstat -i and > > systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate > > also have profhz and stathz as 100. A kernel of about a week ago doesn't > > have this problem. > > Hmm... > > [7:38pm]~-103# sysctl kern.clockrate > kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024, > stathz = 128 } > Ok, I have found it. My kernel still had the apm line from its GENERIC days, which didn't hurt me before: device apm0 at nexus? disable flags 0x31 # Advanced Power Management It seems that the disable keyword is ignored, because the apm0 device suddenly appeared in the probe messages and that set statclock_disable to 1. I have removed apm from my kernel config file and all is well again. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 8:17:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D8C0D154E5 for ; Sun, 18 Apr 1999 08:17:36 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id QAA89989; Sun, 18 Apr 1999 16:19:33 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 18 Apr 1999 16:19:33 +0100 (BST) From: Doug Rabson To: John Hay Cc: Peter Wemm , current@freebsd.org Subject: Re: HEADS UP!!!! Important instructions for -current users! In-Reply-To: <199904181451.QAA73581@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, John Hay wrote: > > John Hay wrote: > > > > As of a few minutes ago, a minimal set of changes to bring the so-called > > > > 'new-bus' functionality to the i386 kernel in -current. > > > > > > > > > > It looks like the stat clock isn't started after this. I have tried a SMP > > > and UNI kernel and both behave the same. Looking with vmstat -i and > > > systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate > > > also have profhz and stathz as 100. A kernel of about a week ago doesn't > > > have this problem. > > > > Hmm... > > > > [7:38pm]~-103# sysctl kern.clockrate > > kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024, > > stathz = 128 } > > > > Ok, I have found it. My kernel still had the apm line from its GENERIC > days, which didn't hurt me before: > > device apm0 at nexus? disable flags 0x31 # Advanced Power Management > > It seems that the disable keyword is ignored, because the apm0 device > suddenly appeared in the probe messages and that set statclock_disable to 1. > I have removed apm from my kernel config file and all is well again. This should be fixed. I changed the apm driver to honour the disabled keyword. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 9:16:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-36.ppp.wenet.net [206.15.85.36]) by hub.freebsd.org (Postfix) with ESMTP id 2BEC214CF7 for ; Sun, 18 Apr 1999 09:16:16 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id JAA89643; Sun, 18 Apr 1999 09:13:46 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sun, 18 Apr 1999 09:13:46 -0700 (PDT) From: Alex Zepeda To: "Jordan K. Hubbard" Cc: current Subject: Re: newbus and modem(s) In-Reply-To: <1011.924426030@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Jordan K. Hubbard wrote: > > I'm as excited as anyone to see progress, especially if it means the > > ability to modularize the kernel and load various drivers on demand. But, > > alas, it seems this whole thing was rushed horribly. > > Not at all, it's simply something which will require some time to work > out the details of in -current. Which means that it perhaps should be worked out before being merged. Take for instance CAM. It didn't work perfectly, but it sure got a lot more exposure than newbus, and when it was integrated it caused very few problems. > People forget all too often that -current is the bleeding edge and you > shouldn't even bother (truly) to track it unless you're willing and > able to bleed occasionally. I'm actually always happy to see this > lesson driven home again when it looks like people are getting waaaaay > too complacent about -current. :-) Well, why not make ext2fs the default fs just to shake things up? It's one thing to expect panics and soon, but it's another thing to import code that wasn't ready. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 9:20:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-36.ppp.wenet.net [206.15.85.36]) by hub.freebsd.org (Postfix) with ESMTP id D325B14D0C for ; Sun, 18 Apr 1999 09:20:09 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id JAA89973; Sun, 18 Apr 1999 09:16:05 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sun, 18 Apr 1999 09:16:05 -0700 (PDT) From: Alex Zepeda To: Leif Neland Cc: current@FreeBSD.ORG Subject: Re: newbus and modem(s) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The first thing I noticed was the panic I got, in atkbd_isa_intr, which > > has since been fixed. > > Well, that is what you have to expect when running current. You are a > betatester, and you can't expect the authors to have access to every > combination of hardware. Well that's my point. Again, I'll point at CAM. That was available to the public for testing, and therefor required caused very little trouble (with the exception of the aic driver) when it was integrated. Hell, I'm even interested in fixing the PnP part of the sio driver, but where can I find information on newbus and PnP? The only other PnP driver I've looked at (pcm) uses the "shims". Perhaps for good reason? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 9:47:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 788F7152F7 for ; Sun, 18 Apr 1999 09:47:34 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA13134; Mon, 19 Apr 1999 01:44:53 +0900 (JST) Message-ID: <371A0B93.527905D5@newsguy.com> Date: Mon, 19 Apr 1999 01:42:59 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Alex Zepeda Cc: "Jordan K. Hubbard" , current Subject: Re: newbus and modem(s) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > > Which means that it perhaps should be worked out before being merged. Take > for instance CAM. It didn't work perfectly, but it sure got a lot more > exposure than newbus, and when it was integrated it caused very few > problems. I think CAM is a very bad example. We *still* don't have all the drivers we had, and that includes at least one reasonably requested driver. On the other hand, I don't see we losing anything with newbus, which is quite a feat given the extent of the changes. Moreover, I have seen very few problems reported. Changing the compiler to egcs seems to have produced more waves, in fact. > Well, why not make ext2fs the default fs just to shake things up? It's > one thing to expect panics and soon, but it's another thing to import code > that wasn't ready. It seems to work on my computer. Why do you say it isn't ready? A reality check seems to be in order. It would seem you are peeved because some of the very few gliches affected you. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 10: 3:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-2.ppp.wenet.net [206.15.85.2]) by hub.freebsd.org (Postfix) with ESMTP id 6722C14EAD for ; Sun, 18 Apr 1999 10:03:12 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id KAA00308; Sun, 18 Apr 1999 10:00:14 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sun, 18 Apr 1999 10:00:14 -0700 (PDT) From: Alex Zepeda To: "Daniel C. Sobral" Cc: "Jordan K. Hubbard" , current Subject: Re: newbus and modem(s) In-Reply-To: <371A0B93.527905D5@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999, Daniel C. Sobral wrote: > I think CAM is a very bad example. We *still* don't have all the > drivers we had, and that includes at least one reasonably requested > driver. Is that an offer to write the missing drivers? > On the other hand, I don't see we losing anything with newbus, which > is quite a feat given the extent of the changes. Moreover, I have > seen very few problems reported. Changing the compiler to egcs seems > to have produced more waves, in fact. Plug and Play for at least the sio driver, perhaps just pnp in general for drivers that were moved to the newbus stuff. Is there any documentation explaining what exactly was changed? Sure, egcs created problems, but at least the general public was warned that this was going to be merged soon. But the kernel worked, and C programs worked usually. > > Well, why not make ext2fs the default fs just to shake things up? It's > > one thing to expect panics and soon, but it's another thing to import code > > that wasn't ready. > > It seems to work on my computer. Why do you say it isn't ready? A > reality check seems to be in order. It would seem you are peeved > because some of the very few gliches affected you. Why would I say it wasn't ready? Because outside of core (apparently), nobody was warned/told that this was going to be committed in a few days/hours/minutes. Glitches? What about the sbxvi driver? The apm driver? Sure, I'm annoyed about one of the glitches affecting me, but I just think if this code had been aired more publically before merging, all of these problems could have been easily avoided. And then what about newconfig? To me this just adds more truth to the whole /. argument that *BSD promotes a closed development model. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 10:13:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A1E6D14DC1 for ; Sun, 18 Apr 1999 10:13:34 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00600; Sun, 18 Apr 1999 10:11:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Alex Zepeda Cc: current Subject: Re: newbus and modem(s) In-reply-to: Your message of "Sun, 18 Apr 1999 09:13:46 PDT." Date: Sun, 18 Apr 1999 10:11:08 -0700 Message-ID: <598.924455468@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Which means that it perhaps should be worked out before being merged. Take > for instance CAM. It didn't work perfectly, but it sure got a lot more > exposure than newbus, and when it was integrated it caused very few > problems. The two systems aren't equivalent so it's not really correct to make comparisons like this. In any case, -current has always been designated for developers to work on issues precisely like this one and it's simply not accurate to suggest that bleeding edge development should not be done in the -current branch. As I said before, it only points out that many people are tracking the wrong branch. If you want a smooth experience, track -stable and that's all I'm going to say on the issue. > Well, why not make ext2fs the default fs just to shake things up? It's If there were a truly practical reason to do so, you may rest assured that we would. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 10:14:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 508E714DC1 for ; Sun, 18 Apr 1999 10:14:45 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00613; Sun, 18 Apr 1999 10:12:14 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Alex Zepeda Cc: "Daniel C. Sobral" , current Subject: Re: newbus and modem(s) In-reply-to: Your message of "Sun, 18 Apr 1999 10:00:14 PDT." Date: Sun, 18 Apr 1999 10:12:14 -0700 Message-ID: <611.924455534@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And then what about newconfig? To me this just adds more truth to the > whole /. argument that *BSD promotes a closed development model. I think your perceptions are fundamentally flawed here, it's just that simple. You can argue the point all you like in -current, but it won't change that fact one iota. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 10:18:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 8DF9C14DC1 for ; Sun, 18 Apr 1999 10:18:49 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA11215 for current@freebsd.org; Sun, 18 Apr 1999 13:16:31 -0400 From: Bill Paul Message-Id: <199904181716.NAA11215@skynet.ctr.columbia.edu> Subject: Pccard support still works with newbus, right? To: current@freebsd.org Date: Sun, 18 Apr 1999 13:16:30 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1651 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently working on a driver for the Lucent WaveLAN/IEEE 802.11 PCMCIA adapter, as part of a project for the COMET lab people here at Columbia. Lucent has a PCMCIA and an "ISA" version of this adapter, however the ISA version is really just a PCMCIA card fitted into an add-in PCMCIA controller card that mounts in an ISA slot (i.e. something that lets you plug PCMCIA devices into a desktop host that doesn't have any built-in PCMCIA slots). This adapter card has a Vadem 469 chip on it which, fortunately, is supported by our current pccard code. The system I'm testing on is running 3.0-RELEASE and I'm reasonably confident my code will work with 3.1-RELEASE too. As it stands now, I can get the card probed and attached when I start pccardd, and everything seems peachy. What I need to know is if anybody has tested the pccard support in 4.0-CURRENT now that all the newbus stuff has been rolled in. If the pccard support for the x86 still works under 'emulation' using an ISA device shim, then that's fine. If not... well, then I suppoose _I'm_ the one who's going to end up testing it. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 10:47:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7378514BE5 for ; Sun, 18 Apr 1999 10:47:46 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA17449; Mon, 19 Apr 1999 02:44:54 +0900 (JST) Message-ID: <371A199F.EB92AA09@newsguy.com> Date: Mon, 19 Apr 1999 02:42:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Alex Zepeda Cc: "Jordan K. Hubbard" , current Subject: Re: newbus and modem(s) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > > On Mon, 19 Apr 1999, Daniel C. Sobral wrote: > > > I think CAM is a very bad example. We *still* don't have all the > > drivers we had, and that includes at least one reasonably requested > > driver. > > Is that an offer to write the missing drivers? Is that sidetracking the argument? :-) Alas, I found a FreeBSD driver for my card, which I don't have the heck whether it is aic-based or not, and I'll try to write a -current driver based on it. > Sure, egcs created problems, but at least the general public was warned > that this was going to be merged soon. But the kernel worked, and C > programs worked usually. I agree that a heads up a few days earlier would have been in order. I even recall a certain document might have mentioned something to this effect... Which is a different issue altogether. > Why would I say it wasn't ready? Because outside of core (apparently), > nobody was warned/told that this was going to be committed in a few > days/hours/minutes. Nobody warning is a very different issue from it not being ready. > Glitches? What about the sbxvi driver? The apm driver? Sure, I'm > annoyed about one of the glitches affecting me, but I just think if this > code had been aired more publically before merging, all of these problems > could have been easily avoided. Looks like glitches to me. And, as Jordan said, -current's purpose is airing code more publically. > And then what about newconfig? To me this just adds more truth to the > whole /. argument that *BSD promotes a closed development model. New-bus mailing list was open to subscription, the cvs repository for the code was announced, and, if I'm not mistaken, you could even cvsup it from cvsup2. It lacked a "Hey, people, new-bus *IS* going to be imported into FreeBSD at some point in the near future" message, so people who did not look further would have no doubts about it, but this is a minor point. As for the newconfig people, it *was* said to them that FreeBSD *was* going with new-bus. I suspect that, not liking this direction, they opted to proceed with their code, in the hope that working code wins against vaporware any day. Unfortunately, for them, newbus isn't vaporware. And, as Jordan said, only one of newbus and newconfig could be choosen, so there is nothing "closed" about choosing. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 10:52:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4871414F79 for ; Sun, 18 Apr 1999 10:52:45 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA90261; Sun, 18 Apr 1999 18:55:18 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 18 Apr 1999 18:55:18 +0100 (BST) From: Doug Rabson To: Bill Paul Cc: current@freebsd.org Subject: Re: Pccard support still works with newbus, right? In-Reply-To: <199904181716.NAA11215@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Bill Paul wrote: > I'm currently working on a driver for the Lucent WaveLAN/IEEE 802.11 > PCMCIA adapter, as part of a project for the COMET lab people here > at Columbia. Lucent has a PCMCIA and an "ISA" version of this adapter, > however the ISA version is really just a PCMCIA card fitted into an > add-in PCMCIA controller card that mounts in an ISA slot (i.e. something > that lets you plug PCMCIA devices into a desktop host that doesn't have > any built-in PCMCIA slots). This adapter card has a Vadem 469 chip on it > which, fortunately, is supported by our current pccard code. The system > I'm testing on is running 3.0-RELEASE and I'm reasonably confident my > code will work with 3.1-RELEASE too. As it stands now, I can get the > card probed and attached when I start pccardd, and everything seems > peachy. > > What I need to know is if anybody has tested the pccard support in > 4.0-CURRENT now that all the newbus stuff has been rolled in. If the > pccard support for the x86 still works under 'emulation' using an > ISA device shim, then that's fine. If not... well, then I suppoose > _I'm_ the one who's going to end up testing it. I think it works as well it did before but I haven't personally tested it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 10:54:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B20D314F79 for ; Sun, 18 Apr 1999 10:54:18 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00861 for ; Sun, 18 Apr 1999 10:51:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: new-bus, a success report. Date: Sun, 18 Apr 1999 10:51:53 -0700 Message-ID: <859.924457913@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since everybody's slagging new-bus right now, I thought I'd just jump in and say that as of 10 minutes ago, having made the world and a new kernel, everything's working great. NOTE: Look at GENERIC! Things have changed and you will likely need to update your old config file before everything is peachy again. I had to update my PS/2 rodent and keyboard entries, as well as the parallel port bus stuff, and it's now working wonderfully on my dual PII/450 with a fairly non-trivial set of peripherals plugged into it, including on-board PnP sound and a Hauppage bt848 card for video. My dmesg output, JFYI: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Apr 18 08:30:14 PDT 1999 jkh@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff real memory = 134217728 (131072K bytes) avail memory = 127864832 (124868K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02a5000. Pentium Pro MTRR support enabled, default memory type is uncacheable npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 devclass_alloc_unit: npx0 already exists, using next available unit number isa0: on isab0 ide_pci0: at device 7.1 on pci0 chip1: at device 7.3 on pci0 pcib2: at device 16.0 on pci0 pci2: on pcib2 fxp0: at device 17.0 on pci0 fxp0: interrupting at irq 19 fxp0: Ethernet address 00:e0:81:10:20:9e ahc0: at device 18.0 on pci0 ahc0: interrupting at irq 16 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: at device 18.1 on pci0 ahc1: interrupting at irq 16 ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs bktr0: at device 20.0 on pci0 bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 smb0: on smbus0 bktr0: interrupting at irq 17 Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner. fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: drive speed 5500KB/sec, 512KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA, packet track wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc1: interrupting at irq 15 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0 at port 0x378 irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ppc0: interrupting at irq 7 pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0 pcm0: interrupting at irq 5 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 12: 5: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 1365D14BF5 for ; Sun, 18 Apr 1999 12:05:06 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it ([194.185.55.84]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id VAA20338; Sun, 18 Apr 1999 21:04:01 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id VAA03280; Sun, 18 Apr 1999 21:01:38 +0200 (CEST) Date: Sun, 18 Apr 1999 21:01:38 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Alex Zepeda Cc: "Daniel C. Sobral" , "Jordan K. Hubbard" , current Subject: Re: newbus and modem(s) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why would I say it wasn't ready? Because outside of core (apparently), > nobody was warned/told that this was going to be committed in a few > days/hours/minutes. The USB code has been using newbus for over 4 months now. And up to now we've had only one bug to fix. The rest was feature requests. I've ported the newconfig style USB code of NetBSD to FreeBSD and I really prefer the newbus style, because it is truly dynamic. Nick FreeBSD USB project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 12:26: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 11C7E14CF3 for ; Sun, 18 Apr 1999 12:26:05 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA01769; Sun, 18 Apr 1999 13:23:16 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA25095; Sun, 18 Apr 1999 13:23:09 -0600 Date: Sun, 18 Apr 1999 13:23:09 -0600 Message-Id: <199904181923.NAA25095@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Matthew Dillon , NAKAGAWA Yoshihisa , Peter Wemm , current@FreeBSD.ORG Subject: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! ) In-Reply-To: <88666.924388435@zippy.cdrom.com> References: <199904171904.MAA75813@apollo.backplane.com> <88666.924388435@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I would ask people to STOP DOING THIS. Do not harass or ridicule >> someone for not being fluent in english! Now, it is sorely true >> that someone wil > > Let me just reinforce this statement. This is wonderful, but has this ever happened in our mailing lists? I guess I don't remember anyone *ever* ridiculing or harassing someone for not being fluent in the language. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 12:57: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from web115.yahoomail.com (web115.yahoomail.com [205.180.60.88]) by hub.freebsd.org (Postfix) with SMTP id C591414D69 for ; Sun, 18 Apr 1999 12:57:03 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990418195439.17557.rocketmail@web115.yahoomail.com> Received: from [147.226.112.101] by web115.yahoomail.com; Sun, 18 Apr 1999 12:54:39 PDT Date: Sun, 18 Apr 1999 12:54:39 -0700 (PDT) From: Valentin Shopov Subject: new-bus on ISA only machine To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On ISA only machine, w/o "controller pci0 at nexus?" in kernel config, after make depend: In file included from ../../i386/i386/nexus.c:74: ../../pci/pcivar.h:192: pci_if.h: No such file or directory In file included from ../../i386/i386/userconfig.c:132: ../../pci/pcivar.h:192: pci_if.h: No such file or directory mkdep: compile failed *** Error code 1 With "controller pci0 at nexus?" it's ok, and kernel is running fine. But I don't need PCI code into kernel on my ISA only machine. Val === Valentin Shopov 2301 West Bethel Ave., #53 Muncie, IN 47304-2112 Phone: ++1-(765)-214-0504 E-Mail: valsho@yahoo.com valsho@usa.net URL: http://www.cyberspace.org/~valentin _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13: 4: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 84A8D14E00 for ; Sun, 18 Apr 1999 13:03:30 -0700 (PDT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id WAA23512; Sun, 18 Apr 1999 22:00:53 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA33712; Sun, 18 Apr 1999 22:00:27 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199904182000.WAA33712@greenpeace.grondar.za> To: John Hay Cc: peter@netplex.com.au (Peter Wemm), current@freebsd.org Subject: Re: HEADS UP!!!! Important instructions for -current users! In-Reply-To: Your message of " Sat, 18 Apr 1999 13:30:00 +0200." <199904181130.NAA70508@zibbi.mikom.csir.co.za> References: <199904181130.NAA70508@zibbi.mikom.csir.co.za> Date: Sun, 18 Apr 1999 22:00:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > > As of a few minutes ago, a minimal set of changes to bring the so-called > > 'new-bus' functionality to the i386 kernel in -current. > > > > It looks like the stat clock isn't started after this. I have tried a SMP > and UNI kernel and both behave the same. Looking with vmstat -i and > systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate > also have profhz and stathz as 100. A kernel of about a week ago doesn't > have this problem. There are also some funny results in "systat -vmstat"; lots of interrupt names are wrong; a pnp-probed sound card is listed as "??? irq5", and everything else except "clk0 int0" and "rtc0 irq8" are listed as "pci irqNN" (with NN replaced some believable number). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13:12: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8FA7A14E00 for ; Sun, 18 Apr 1999 13:12:06 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA81952; Sun, 18 Apr 1999 13:09:35 -0700 (PDT) (envelope-from dillon) Date: Sun, 18 Apr 1999 13:09:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199904182009.NAA81952@apollo.backplane.com> To: Nate Williams Cc: "Jordan K. Hubbard" , NAKAGAWA Yoshihisa , Peter Wemm , current@FreeBSD.ORG Subject: Re: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! ) References: <199904171904.MAA75813@apollo.backplane.com> <88666.924388435@zippy.cdrom.com> <199904181923.NAA25095@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>> that someone wil :> :> Let me just reinforce this statement. : :This is wonderful, but has this ever happened in our mailing lists? I :guess I don't remember anyone *ever* ridiculing or harassing someone for :not being fluent in the language. : :Nate Oh sure, it happens quite often. I've seen people 'talk down' to other people lots of time in responding to their questions. I see it most often when the person who posted the question has trouble with the language. Sometimes you can just see how much time it took the guy to ooze-out a single sentence and it really makes me angry when all they get for their trouble is a flip answer from some bozo. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13:14:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id F2DD314E00 for ; Sun, 18 Apr 1999 13:13:42 -0700 (PDT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id WAA23537; Sun, 18 Apr 1999 22:11:12 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA33823; Sun, 18 Apr 1999 22:10:53 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199904182010.WAA33823@greenpeace.grondar.za> To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: new-bus, a success report. In-Reply-To: Your message of " Sun, 18 Apr 1999 10:51:53 MST." <859.924457913@zippy.cdrom.com> References: <859.924457913@zippy.cdrom.com> Date: Sun, 18 Apr 1999 22:10:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Since everybody's slagging new-bus right now, I thought I'd just jump > in and say that as of 10 minutes ago, having made the world and a new > kernel, everything's working great. NOTE: Look at GENERIC! Things > have changed and you will likely need to update your old config file > before everything is peachy again. I had to update my PS/2 rodent and > keyboard entries, as well as the parallel port bus stuff, and it's now > working wonderfully on my dual PII/450 with a fairly non-trivial set > of peripherals plugged into it, including on-board PnP sound and a > Hauppage bt848 card for video. My PPro/SMP (Remember that board, Jordan?) is also running it with nary a glitch. Here's my DMESG: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Apr 17 13:17:31 SAST 1999 root@greenpeace.grondar.za:/usr/src/sys/compile/GA586DX Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 67108864 (65536K bytes) avail memory = 62566400 (61100K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0284000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] mss_attach 1 at 0x530 irq 5 dma 1:0 flags 0x10 pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 fxp0: at device 6.0 on pci0 fxp0: interrupting at irq 18 fxp0: Ethernet address 00:a0:c9:49:c1:95 isab0: at device 7.0 on pci0 isa0: on isab0 ahc0: at device 9.0 on pci0 ahc0: interrupting at irq 17 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model MouseMan+, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0 at port 0x378 irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 APIC_IO: routing 8254 via 8259 on pin 0 Waiting 4 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888543 512 byte sectors: 255H 63S/T 553C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13:16:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 55B8314D04 for ; Sun, 18 Apr 1999 13:16:13 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 7EEAF1F54; Mon, 19 Apr 1999 04:13:45 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray Cc: John Hay , current@freebsd.org Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sun, 18 Apr 1999 22:00:07 +0200." <199904182000.WAA33712@greenpeace.grondar.za> Date: Mon, 19 Apr 1999 04:13:45 +0800 From: Peter Wemm Message-Id: <19990418201347.7EEAF1F54@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > John Hay wrote: > > > As of a few minutes ago, a minimal set of changes to bring the so-called > > > 'new-bus' functionality to the i386 kernel in -current. > > > > > > > It looks like the stat clock isn't started after this. I have tried a SMP > > and UNI kernel and both behave the same. Looking with vmstat -i and > > systat -vmstat, there is no sign of the stat clock. Sysctl kern.clockrate > > also have profhz and stathz as 100. A kernel of about a week ago doesn't > > have this problem. > > There are also some funny results in "systat -vmstat"; lots of > interrupt names are wrong; a pnp-probed sound card is listed as > "??? irq5", and everything else except "clk0 int0" and "rtc0 irq8" > are listed as "pci irqNN" (with NN replaced some believable number). Known bogon... In between putting out fires (here), I hope to take a further shot at cleaning up the interrupt layering shortly. I wasn't too worried about that, I didn't think the world would end if the labels fell off the irq table, so I left it out. :-] Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13:25: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 0FBFE15534 for ; Sun, 18 Apr 1999 13:23:33 -0700 (PDT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id WAA23573; Sun, 18 Apr 1999 22:21:02 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA33977; Sun, 18 Apr 1999 22:20:44 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199904182020.WAA33977@greenpeace.grondar.za> To: Peter Wemm Cc: current@freebsd.org Subject: Re: HEADS UP!!!! Important instructions for -current users! In-Reply-To: Your message of " Mon, 19 Apr 1999 04:13:45 +0800." <19990418201347.7EEAF1F54@spinner.netplex.com.au> References: <19990418201347.7EEAF1F54@spinner.netplex.com.au> Date: Sun, 18 Apr 1999 22:20:33 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > Known bogon... In between putting out fires (here), I hope to take a > further shot at cleaning up the interrupt layering shortly. ... as I saw 3 messages later. > I wasn't too worried about that, I didn't think the world would end if the > labels fell off the irq table, so I left it out. :-] No problem. No-one got hurt ;-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13:26:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 2A48714CFB for ; Sun, 18 Apr 1999 13:26:40 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from libr.scitec.kobe-u.ac.jp (cs22130.ppp.infoweb.ne.jp [202.219.4.46]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id FAA28555; Mon, 19 Apr 1999 05:15:17 +0900 (JST) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id FAA24081; Mon, 19 Apr 1999 05:20:22 +0900 (JST) From: takawata@shidahara1.planet.sci.kobe-u.ac.jp Message-Id: <199904182020.FAA24081@libr.scitec.kobe-u.ac.jp> To: Nick Hibma , freebsd-current@freebsd.org, dfr@nlsystems.com Subject: Re: newbus and modem(s) In-reply-to: Your message of "Sun, 18 Apr 1999 21:01:38 +0200." Date: Mon, 19 Apr 1999 05:20:20 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nick Hibm a wrote: >> Why would I say it wasn't ready? Because outside of core (apparently), >> nobody was warned/told that this was going to be committed in a few >> days/hours/minutes. >I've ported the newconfig style USB code of NetBSD to FreeBSD and I >really prefer the newbus style, because it is truly dynamic. Simple Question. If there were 'Closed'-Host-Controller-Interface with object-only driver, Can the vendor make the Host controller recognized without changing usb.c code? #That's what frustrated me while writing driver for smbus controller. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13:45: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.wwwtek.com (dns.wwwtek.com [209.153.255.2]) by hub.freebsd.org (Postfix) with ESMTP id 3B4E6152D4 for ; Sun, 18 Apr 1999 13:44:56 -0700 (PDT) (envelope-from ted@stargate.org) Received: from d185d026b.rochester.rr.com (IDENT:ted@d185d026b.rochester.rr.com [24.93.2.107]) by dns.wwwtek.com (8.9.2/8.9.2) with ESMTP id QAA98168 for ; Sun, 18 Apr 1999 16:48:46 -0700 (PDT) (envelope-from ted@stargate.org) Received: from localhost (ted@localhost) by d185d026b.rochester.rr.com (8.8.7/8.8.7) with ESMTP id QAA19672 for ; Sun, 18 Apr 1999 16:37:55 -0400 Date: Sun, 18 Apr 1999 16:37:55 -0400 (EDT) From: "T.D. Brace" X-Sender: ted@d185d026b.rochester.rr.com To: freebsd-current@freebsd.org Subject: compaq presario 1675 & pccard Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Has anyone been successful getting pccard services to run on this laptop? I enabled the card controller and rebuilt the kernel, enable pccard services in rc.conf, but when I run "pccardc dumpcis" I get "0 slots found". I have a feeling the pcmcia controller isn't being recognized. Can anyone point me in the right direction? Thanks. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13:47:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id DE2E615501 for ; Sun, 18 Apr 1999 13:47:34 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id WAA78724 for current@FreeBSD.ORG; Sun, 18 Apr 1999 22:45:08 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199904182045.WAA78724@zibbi.mikom.csir.co.za> Subject: newbus and isa auto irq To: current@FreeBSD.ORG Date: Sun, 18 Apr 1999 22:45:08 +0200 (SAT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I ave found one more thing that seems to be broken. I have used the irq "autodetect" feature of the ed(4) for a long time, but it seems that the newbus compatability shim is not doing the right thing with it. My kernel config file have a line like this: device ed0 at isa? port 0x280 net irq ? iomem 0xd8000 The card gets probed but you just get device timeouts and there is no mention of an irq for that device in the probe output. Booting with -c and specifying the irq there also didn't work. Rebuilding the kernel with a config file which specified the irq did work though. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 13:50:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.wwwtek.com (dns.wwwtek.com [209.153.255.2]) by hub.freebsd.org (Postfix) with ESMTP id 4AEAA14BF2 for ; Sun, 18 Apr 1999 13:50:07 -0700 (PDT) (envelope-from ted@stargate.org) Received: from d185d026b.rochester.rr.com (IDENT:ted@d185d026b.rochester.rr.com [24.93.2.107]) by dns.wwwtek.com (8.9.2/8.9.2) with ESMTP id QAA98310 for ; Sun, 18 Apr 1999 16:54:01 -0700 (PDT) (envelope-from ted@stargate.org) Received: from localhost (ted@localhost) by d185d026b.rochester.rr.com (8.8.7/8.8.7) with ESMTP id QAA19688 for ; Sun, 18 Apr 1999 16:43:11 -0400 Date: Sun, 18 Apr 1999 16:43:11 -0400 (EDT) From: "T.D. Brace" X-Sender: ted@d185d026b.rochester.rr.com To: freebsd-current@freebsd.org Subject: compaq presario 1675 & pccard (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Guess I should mention this is 3.1-RELEASE. ---------- Forwarded message ---------- Date: Sun, 18 Apr 1999 16:37:55 -0400 (EDT) From: T.D. Brace To: freebsd-current@FreeBSD.ORG Subject: compaq presario 1675 & pccard Hello, Has anyone been successful getting pccard services to run on this laptop? I enabled the card controller and rebuilt the kernel, enable pccard services in rc.conf, but when I run "pccardc dumpcis" I get "0 slots found". I have a feeling the pcmcia controller isn't being recognized. Can anyone point me in the right direction? Thanks. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 14: 2:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from poo.smooch (unknown [194.125.172.180]) by hub.freebsd.org (Postfix) with ESMTP id 55D1715180 for ; Sun, 18 Apr 1999 14:02:36 -0700 (PDT) (envelope-from blokey@indigo.ie) Received: (from plop@localhost) by poo.smooch (8.9.3/8.9.1) id WAA03557 for freebsd-current@freebsd.org; Sun, 18 Apr 1999 22:00:11 +0100 (IST) (envelope-from plop) Message-ID: <19990418220010.A3521@smooch> Date: Sun, 18 Apr 1999 22:00:10 +0100 From: Smelly Pooh To: freebsd-current@freebsd.org Subject: Parallel ZIP drive hangs machine Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running current as of April 6th and whenever I try to multi-volume tar directly to my parallel port zip drive using /dev/da0 it hangs when it gets to the end of the zip. I don't think it's a hardware problem because I've seen it happen on 2 completely separate machines. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 14: 4:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id EBC0C14F04 for ; Sun, 18 Apr 1999 14:04:08 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id QAA21574; Sun, 18 Apr 1999 16:16:50 -0500 (EST) Date: Sun, 18 Apr 1999 16:16:49 -0500 (EST) From: Alfred Perlstein To: "T.D. Brace" Cc: freebsd-current@FreeBSD.ORG Subject: Re: compaq presario 1675 & pccard (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, T.D. Brace wrote: > > Guess I should mention this is 3.1-RELEASE. > > ---------- Forwarded message ---------- > Date: Sun, 18 Apr 1999 16:37:55 -0400 (EDT) > From: T.D. Brace > To: freebsd-current@FreeBSD.ORG > Subject: compaq presario 1675 & pccard > > > Hello, > > Has anyone been successful getting pccard services to run on this laptop? > > I enabled the card controller and rebuilt the kernel, enable pccard > services in rc.conf, but when I run "pccardc dumpcis" I get "0 slots > found". > > I have a feeling the pcmcia controller isn't being recognized. Can anyone > point me in the right direction? > > Thanks. > > -Ted Wild speculation, did you enable pnp? do you have these lines in the kernel config file: # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? controller pnp0 # PnP support for ISA controller isa0 right? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 14:29:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5176814D25 for ; Sun, 18 Apr 1999 14:25:19 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id RAA19527; Sun, 18 Apr 1999 17:20:44 -0400 (EDT) Date: Sun, 18 Apr 1999 17:20:44 -0400 (EDT) From: Chuck Robey To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: new-bus, a success report. In-Reply-To: <859.924457913@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Jordan K. Hubbard wrote: > Since everybody's slagging new-bus right now, I thought I'd just jump > in and say that as of 10 minutes ago, having made the world and a new > kernel, everything's working great. NOTE: Look at GENERIC! Things > have changed and you will likely need to update your old config file > before everything is peachy again. I had to update my PS/2 rodent and > keyboard entries, as well as the parallel port bus stuff, and it's now > working wonderfully on my dual PII/450 with a fairly non-trivial set > of peripherals plugged into it, including on-board PnP sound and a > Hauppage bt848 card for video. Heck, Jordan, you weren't first. I can't understand why Alex is all upset, most especially about the sound breakage (which I don't see, my sound works fine). The sound stuff is one of the things that's likely to be helped by the fact of our bus technology on the road to becoming closer to NetBSD/OpenBSD bus technology, so we can share code. It's not done, but that's the path, and Alex would be one of those helped by it. I don't see any breakage at all, myself, but even if there is (and I know, there must be some) then it sure seems worth it. This new-bus stuff is absolutely great, and I hope Doug, Peter, and everyone else involved doesn't hear the criticism only. You guys are doing fine work. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 14:43:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id C923714CAF for ; Sun, 18 Apr 1999 14:43:00 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 4CE7B1F29; Mon, 19 Apr 1999 05:40:31 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Valentin Shopov Cc: current@freebsd.org Subject: Re: new-bus on ISA only machine In-reply-to: Your message of "Sun, 18 Apr 1999 12:54:39 MST." <19990418195439.17557.rocketmail@web115.yahoomail.com> Date: Mon, 19 Apr 1999 05:40:31 +0800 From: Peter Wemm Message-Id: <19990418214033.4CE7B1F29@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Valentin Shopov wrote: > On ISA only machine, > w/o "controller pci0 at nexus?" > in kernel config, after make depend: > > In file included from ../../i386/i386/nexus.c:74: > ../../pci/pcivar.h:192: pci_if.h: No such file or > directory > In file included from > ../../i386/i386/userconfig.c:132: > ../../pci/pcivar.h:192: pci_if.h: No such file or > directory > mkdep: compile failed > *** Error code 1 > > With "controller pci0 at nexus?" it's ok, and > kernel is running fine. But I don't need PCI code into > kernel on my ISA only machine. I've fixed one of these, and was in the middle of patching the other one when I got a little sidetracked.. I need some sleep, I'm making silly mistakes. Anyway, If you want to run without pci, you'll have to tweak the nexus.c code a little so that it adds the isa bus always (just like on PC98). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 16:25:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (unknown [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 3D15114D94 for ; Sun, 18 Apr 1999 16:25:50 -0700 (PDT) (envelope-from dispatch@blackhelicopters.org) Received: (from dispatch@localhost) by blackhelicopters.org (8.8.8/8.8.8) id TAA10642; Sun, 18 Apr 1999 19:23:04 -0400 (EDT) (envelope-from dispatch) From: Dispatcher Message-Id: <199904182323.TAA10642@blackhelicopters.org> Subject: Re: Laptop support In-Reply-To: from "T.D. Brace" at "Apr 17, 1999 11: 5:31 pm" To: ted@stargate.org (T.D. Brace) Date: Sun, 18 Apr 1999 19:23:03 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, A better place to ask this question would be over on freebsd-mobile. The whole list is nothing but portables. > > Can anyone tell me if I can get freebsd 3.1 running on a compaq > pressario 1675 - I'm worried about the pcmcia controller being > recognized (and my xircom re-100btx working). Thanks. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 16:38:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 97D2D14CB3 for ; Sun, 18 Apr 1999 16:38:40 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id TAA45222; Sun, 18 Apr 1999 19:36:06 -0400 (EDT) Date: Sun, 18 Apr 1999 19:36:04 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Alex Zepeda Cc: "Daniel C. Sobral" , "Jordan K. Hubbard" , current Subject: Re: newbus and modem(s) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Alex Zepeda wrote: > On Mon, 19 Apr 1999, Daniel C. Sobral wrote: > > > I think CAM is a very bad example. We *still* don't have all the > > drivers we had, and that includes at least one reasonably requested > > driver. > > Is that an offer to write the missing drivers? > > > On the other hand, I don't see we losing anything with newbus, which > > is quite a feat given the extent of the changes. Moreover, I have > > seen very few problems reported. Changing the compiler to egcs seems > > to have produced more waves, in fact. > > Plug and Play for at least the sio driver, perhaps just pnp in general for > drivers that were moved to the newbus stuff. > > Is there any documentation explaining what exactly was changed? > > Sure, egcs created problems, but at least the general public was warned > that this was going to be merged soon. But the kernel worked, and C > programs worked usually. > > > > Well, why not make ext2fs the default fs just to shake things up? It's > > > one thing to expect panics and soon, but it's another thing to import code > > > that wasn't ready. > > > > It seems to work on my computer. Why do you say it isn't ready? A > > reality check seems to be in order. It would seem you are peeved > > because some of the very few gliches affected you. > > Why would I say it wasn't ready? Because outside of core (apparently), > nobody was warned/told that this was going to be committed in a few > days/hours/minutes. > > Glitches? What about the sbxvi driver? The apm driver? Sure, I'm > annoyed about one of the glitches affecting me, but I just think if this > code had been aired more publically before merging, all of these problems > could have been easily avoided. I saw this and just had to note something to you. THINK what branch you are using. This is _WHERE_ things are being aired publically, and merged eventually to the STABLE branch. > > And then what about newconfig? To me this just adds more truth to the > whole /. argument that *BSD promotes a closed development model. > > - alex > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 17: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-15.ppp.wenet.net [206.15.85.15]) by hub.freebsd.org (Postfix) with ESMTP id 7ACE814E45 for ; Sun, 18 Apr 1999 17:02:21 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id QAA23426; Sun, 18 Apr 1999 16:59:38 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sun, 18 Apr 1999 16:59:38 -0700 (PDT) From: Alex Zepeda To: Brian Feldman Cc: "Daniel C. Sobral" , "Jordan K. Hubbard" , current Subject: Re: newbus and modem(s) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Brian Feldman wrote: > I saw this and just had to note something to you. THINK what branch you > are using. This is _WHERE_ things are being aired publically, and merged > eventually to the STABLE branch. Gosh, thank you, without your wonderful help and understanding, I NEVER would have been able to realize this. You are so smart. Will you commit my code which breaks a few things and causes a panic? Wouldya? Huh? Huh? Huh? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 17: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 4493E155AB for ; Sun, 18 Apr 1999 17:02:31 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id UAA45598; Sun, 18 Apr 1999 20:00:06 -0400 (EDT) Date: Sun, 18 Apr 1999 20:00:05 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Smelly Pooh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Parallel ZIP drive hangs machine In-Reply-To: <19990418220010.A3521@smooch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Smelly Pooh wrote: > I'm running current as of April 6th and whenever I try to multi-volume tar > directly to my parallel port zip drive using /dev/da0 it hangs when it gets to > the end of the zip. I don't think it's a hardware problem because I've seen > it happen on 2 completely separate machines. This is a known problem, that writes to an end of a block device will cause a lockup. I have no idea if anyone was going to fix this. Did you try using the character device, which is what you SHOULD be using anyway? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 17:44:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B0DA114C91 for ; Sun, 18 Apr 1999 17:44:26 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id UAA07799; Sun, 18 Apr 1999 20:39:40 -0400 (EDT) Date: Sun, 18 Apr 1999 20:39:39 -0400 (EDT) From: Chuck Robey To: Alex Zepeda Cc: Brian Feldman , "Daniel C. Sobral" , "Jordan K. Hubbard" , current Subject: Re: newbus and modem(s) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Alex Zepeda wrote: > On Sun, 18 Apr 1999, Brian Feldman wrote: > > > I saw this and just had to note something to you. THINK what branch you > > are using. This is _WHERE_ things are being aired publically, and merged > > eventually to the STABLE branch. > > Gosh, thank you, without your wonderful help and understanding, I NEVER > would have been able to realize this. You are so smart. Will you commit > my code which breaks a few things and causes a panic? Wouldya? Huh? Huh? > Huh? Alex, that's twice ... and enough. If you feel you have to drip sarcasm, go pick another mailing list, no one here wants to hear the sarcasm, even if they *might* agree with your points. Don't get personal, don't use sarcasm, this isn't the list for it. If you want stuff like that, the Usenet groups abound in it, go there. All you're doing here is making yourself look bad. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 18:39:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id DC92E14E8F; Sun, 18 Apr 1999 18:39:03 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA83121; Sun, 18 Apr 1999 18:36:37 -0700 (PDT) (envelope-from dillon) Date: Sun, 18 Apr 1999 18:36:37 -0700 (PDT) From: Matthew Dillon Message-Id: <199904190136.SAA83121@apollo.backplane.com> To: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: NFS patch #5 avail - need testers files) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NFS patch #5 is now available for -current. I believe I have fixed all the bugs for NFSV3 over UDP, but I need people to help test it. http://www.backplane.com/FreeBSD4/ This patch also includes general B_VMIO caching for directories ( ufs, nfs, anyone ), which DG may commit soon so if you get errors just wait a bit for me to update the patch or fix collisions yourself. To use, unapply any previous patches and start fresh. I believe this patch to be reasonably stable -- enough that it should be possible to perform meaningful testing with it. But, as always, do not run this on any box containing critical data. It has successfully passed *all* of my tests so far. Note that this is for NFSV3 UDP only, and although all the fixes apply to TCP and most of them apply to NFS V2 too, TCP probably still has other bugs. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 20: 0:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DF28314E73 for ; Sun, 18 Apr 1999 20:00:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA57231; Sun, 18 Apr 1999 20:57:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA02653; Sun, 18 Apr 1999 20:57:21 -0600 (MDT) Message-Id: <199904190257.UAA02653@harmony.village.org> To: Timo Geusch Subject: Re: make aout-to-elf on -current? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 16 Apr 1999 08:35:44 BST." <19990416083544.A10699@timog.prestel.co.uk> References: <19990416083544.A10699@timog.prestel.co.uk> <199904160654.AAA07198@harmony.village.org> Date: Sun, 18 Apr 1999 20:57:21 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990416083544.A10699@timog.prestel.co.uk> Timo Geusch writes: : You have to elfify your system with a non-egcs compiler before you can move : onto using egcs to make the world. Yes. I discovered this the hard way... I did an upgrade to 3.1-stable with a make aout-to-elf and then to -current from there. Three make worlds, but it worked... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 20:54: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1D25814DDD for ; Sun, 18 Apr 1999 20:53:41 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA57354; Sun, 18 Apr 1999 21:50:56 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA03403; Sun, 18 Apr 1999 21:50:44 -0600 (MDT) Message-Id: <199904190350.VAA03403@harmony.village.org> To: Nate Williams Subject: Re: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! ) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 18 Apr 1999 13:23:09 MDT." <199904181923.NAA25095@mt.sri.com> References: <199904181923.NAA25095@mt.sri.com> <199904171904.MAA75813@apollo.backplane.com> <88666.924388435@zippy.cdrom.com> Date: Sun, 18 Apr 1999 21:50:43 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904181923.NAA25095@mt.sri.com> Nate Williams writes: : This is wonderful, but has this ever happened in our mailing lists? I : guess I don't remember anyone *ever* ridiculing or harassing someone for : not being fluent in the language. I have seen people ask others to explain again since they didn't understand, but I cannot recall ever seeing anybody holding someone up to ridicule publically. I have deep respect for several people that have pushed through the language barrier. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 20:56:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6F1EB14DDD for ; Sun, 18 Apr 1999 20:56:41 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA57362 for ; Sun, 18 Apr 1999 21:54:00 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA03428 for ; Sun, 18 Apr 1999 21:53:47 -0600 (MDT) Message-Id: <199904190353.VAA03428@harmony.village.org> To: current@freebsd.org Subject: Re: Pccard support still works with newbus, right? In-reply-to: Your message of "Sun, 18 Apr 1999 18:55:18 BST." References: Date: Sun, 18 Apr 1999 21:53:47 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : I think it works as well it did before but I haven't personally tested it. I have personally tested my new ata-flash support as well as my 3C589D card, both with a PC-Card Vadem 365 based ISA on my PPro 200. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 20:58:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (Postfix) with ESMTP id 9E66614ECB for ; Sun, 18 Apr 1999 20:58:46 -0700 (PDT) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.3/8.9.3) id DAA01451 for current@FreeBSD.ORG; Mon, 19 Apr 1999 03:38:21 +0100 (BST) (envelope-from aw1) Date: Mon, 19 Apr 1999 03:38:21 +0100 From: Adrian Wontroba To: current@FreeBSD.ORG Subject: Re: new-bus, a success report. Message-ID: <19990419033821.A1142@titus.stade.co.uk> Reply-To: aw1@stade.co.uk References: <859.924457913@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Chuck Robey on Sun, Apr 18, 1999 at 05:20:44PM -0400 X-Operating-System: FreeBSD 4.0-CURRENT Organization: Yes, I need some of that. X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 18, 1999 at 05:20:44PM -0400, Chuck Robey wrote: > This new-bus stuff is absolutely great, and I hope Doug, Peter, and > everyone else involved doesn't hear the criticism only. You guys are > doing fine work. Hear Hear! A painless switch here too (nothing unusual about the box). -- Adrian Wontroba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 23: 5: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 11FDA150A5 for ; Sun, 18 Apr 1999 23:04:55 -0700 (PDT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id IAA24639; Mon, 19 Apr 1999 08:02:27 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id IAA78784; Mon, 19 Apr 1999 08:02:23 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199904190602.IAA78784@greenpeace.grondar.za> To: Alex Zepeda Cc: Brian Feldman , "Daniel C. Sobral" , "Jordan K. Hubbard" , current Subject: Re: newbus and modem(s) In-Reply-To: Your message of " Sun, 18 Apr 1999 16:59:38 MST." References: Date: Mon, 19 Apr 1999 08:02:22 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > On Sun, 18 Apr 1999, Brian Feldman wrote: > > > I saw this and just had to note something to you. THINK what branch you > > are using. This is _WHERE_ things are being aired publically, and merged > > eventually to the STABLE branch. > > Gosh, thank you, without your wonderful help and understanding, I NEVER > would have been able to realize this. You are so smart. Will you commit > my code which breaks a few things and causes a panic? Wouldya? Huh? Huh? > Huh? I think that what everyone is trying to say is that with CURRENT, about the best _guarantee_ you can get of a warning is "Fire in the hole!!", with just about anything else a total freebie. If you don't like that, rather run STABLE. :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 18 23:36:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from lips.lcse.umn.edu (lips.lcse.umn.edu [128.101.182.100]) by hub.freebsd.org (Postfix) with ESMTP id 00ABF14E51 for ; Sun, 18 Apr 1999 23:36:32 -0700 (PDT) (envelope-from cattelan@thebarn.com) Received: from fun.thebarn.com ([128.101.182.206]) by lips.lcse.umn.edu (8.9.2/8.9.1) with ESMTP id BAA31824 for ; Mon, 19 Apr 1999 01:34:01 -0500 (CDT) Received: (from cattelan@localhost) by fun.thebarn.com (8.9.3/8.9.2) id BAA01439 for freebsd-current@freebsd.org; Mon, 19 Apr 1999 01:33:55 -0500 (CDT) (envelope-from cattelan@thebarn.com) Message-Id: <199904190633.BAA01439@fun.thebarn.com> Date: Mon, 19 Apr 1999 01:33:54 -0500 (CDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Russell Cattelan To: freebsd-current@freebsd.org Subject: pcm sound driver crashes at boot time. X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't been able to track down exactly where this is occuring, but disabling pcm allows eliminates the crash. The build is current as of Sun 18th. The one strange thing about this box, it has two sounds cards. A build in Yamaha OPL-3 (really really crappy) and Ensoniq AudioPCI 1371 (very hacked driver, So the problem may be my fault). But I guessing it has more to do with the newbus stuff. disk1s3a:> boot -cv BIOS basemem (639K) != RTC basemem (640K), setting to BIOS value Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #7: Sun Apr 18 16:48:43 CDT 1999 cattelan@lupo.thebarn.com:/export/cyan/src/sys/compile/LUPO Calibrating clock(s) ... TSC clock: 333005093 Hz, i8254 clock: 1193009 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Xeon/Celeron (333.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00306000 - 0x03ffdfff, 63930368 bytes (15608 pages) avail memory = 62156800 (60700K bytes) Found BIOS32 Service Directory header at 0xc00fdb60 Entry = 0xfdb70 (0xc00fdb70) Rev = 0 Len = 1 PCI BIOS entry at 0xdb91 DMI header at 0xc00f6ab0 Version 0.0 Table at 0xf6b8d, 32 entries, 999 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000f7a60 Preloaded elf kernel "kernel" at 0xc02f1000. Pentium Pro MTRR support enabled, default memory type is uncacheable Math emulator present Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: YMH0802 [0x0208a865] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Called nullpnp_probe with tag 0x00000001, type 0x0208a865 Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 pci_open(1): mode 1 addr port (0x0cf8) is 0x80003b40 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71808086) pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71808086) npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard found-> vendor=0x8086, dev=0x7180, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base e0000000, size 28 found-> vendor=0x8086, dev=0x7181, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000ffa0, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=0 map[0]: type 4, range 32, base 0000ef80, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x105d, dev=0x2339, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base fd400000, size 22 map[1]: type 3, range 32, base fd000000, size 22 map[2]: type 1, range 32, base fe800000, size 22 map[3]: type 1, range 32, base fe400000, size 22 map[4]: type 1, range 32, base fe3f0000, size 16 map[5]: type 4, range 32, base 0000ec00, size 8 found-> vendor=0x10b7, dev=0x9055, revid=0x24 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 4, range 32, base 0000e480, size 7 map[1]: type 1, range 32, base fe3e6f80, size 7 found-> vendor=0x1274, dev=0x1371, revid=0x02 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 4, range 32, base 0000ef00, size 6 found-> vendor=0x9004, dev=0x7895, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000e000, size 8 map[1]: type 1, range 32, base fe3e5000, size 12 found-> vendor=0x9004, dev=0x7895, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=11 map[0]: type 4, range 32, base 0000e800, size 8 map[1]: type 1, range 32, base fe3e7000, size 12 pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 chip1: at device 7.3 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> at device 12.0 on pci0 xl0: interrupting at irq 11 xl0: Ethernet address: 00:10:4b:c7:60:93 xl0: media options word: a xl0: probing for a PHY xl0: checking address: 0 xl0: found PHY at address 0, vendor id: 0 device id: 0 xl0: PHY type: xl0: found 10baseT xl0: found 100baseTX xl0: autoneg complete, link status good (half-duplex, 10Mbps) bpf: xl0 attached es0: at device 13.0 on pci0 pcm0: using I/O space register mapping at 0xef00 es1371: codec vendor revision 0 es1371: codec features none es1371: stereo enhancement: no 3D stereo enhancement es0: interrupting at irq 11 using shared irq11. ahc0: at device 15.0 on pci0 ahc0: External SRAM bank0 ahc0: interrupting at irq 9 ahc0: Reading SEEPROM...checksum error ahc0: No SEEPROM available. ahc0: Using left over BIOS settings ahc0: aic7895 Wide Channel A, SCSI Id=7, 255 SCBs ahc0: Downloading Sequencer Program... 372 instructions downloaded ahc1: at device 15.1 on pci0 ahc1: External SRAM bank1 ahc1: interrupting at irq 11 ahc1: Reading SEEPROM...checksum error ahc1: No SEEPROM available. ahc1: Using left over BIOS settings ahc1: aic7895 Wide Channel B, SCSI Id=7, 255 SCBs ahc1: Downloading Sequencer Program... 372 instructions downloaded fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: interrupting at irq 1 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 psm0: interrupting at irq 12 vga0: on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x841 0x851 0x841 0x841 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio0: interrupting at irq 4 sio1: irq maps: 0x841 0x849 0x841 0x841 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 sio2: not probed (disabled) sio3: not probed (disabled) ppc: parallel port found at 0x378 PC873xx probe at 0x2e got unknown ID 0x0 ppc0: ECP SPP SPP ppc0 at port 0x378 irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppb0: IEEE1284 device found /NIBBLE/PS2/ECP/ECP_RLE/NIBBLE_ID/PS2_ID/ECP_ID/ECP_RLE_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: PRINTER PCL 5 Emulation, PostScript Level 2 Emulation, NPAP, PJL plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ppc0: interrupting at irq 7 mss_detect error, busy still set (0xff) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc023bf93 stack pointer = 0x10:0xc0305f24 frame pointer = 0x10:0xc0305f30 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 = 0 () interrupt mask = tty trap number = 12 panic: page fault Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 1:31:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id DE44314DB5 for ; Mon, 19 Apr 1999 01:31:49 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA91751; Mon, 19 Apr 1999 09:33:27 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 19 Apr 1999 09:33:27 +0100 (BST) From: Doug Rabson To: takawata@shidahara1.planet.sci.kobe-u.ac.jp Cc: Nick Hibma , freebsd-current@freebsd.org Subject: Re: newbus and modem(s) In-Reply-To: <199904182020.FAA24081@libr.scitec.kobe-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999 takawata@shidahara1.planet.sci.kobe-u.ac.jp wrote: > In message , Nick Hibm > a wrote: > >> Why would I say it wasn't ready? Because outside of core (apparently), > >> nobody was warned/told that this was going to be committed in a few > >> days/hours/minutes. > > >I've ported the newconfig style USB code of NetBSD to FreeBSD and I > >really prefer the newbus style, because it is truly dynamic. > > Simple Question. > If there were 'Closed'-Host-Controller-Interface with object-only driver, > Can the vendor make the Host controller recognized without changing > usb.c code? > > #That's what frustrated me while writing driver for smbus controller. It really depends on the nature of the bus. For plug-and-play style busses such as USB and PCI, the controller can decide what devices exist without the help of drivers and can then uniquely match them with the right driver. This trivially allows drivers to be added after the system is running. For 'manual' style busses, the creation of devices is generally controlled by hints. To create a new device for a new driver, it would be necessary to add the hint information for the new device and prompt the controller to add it. This isn't quite there yet but will be needed soon for dynamically adding devices (e.g. /usr/bin/joy). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 1:50:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 59C8F14F40 for ; Mon, 19 Apr 1999 01:50:42 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA91862; Mon, 19 Apr 1999 09:53:20 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 19 Apr 1999 09:53:20 +0100 (BST) From: Doug Rabson To: John Hay Cc: current@freebsd.org Subject: Re: newbus and isa auto irq In-Reply-To: <199904182045.WAA78724@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, John Hay wrote: > Hi, > > I ave found one more thing that seems to be broken. I have used the > irq "autodetect" feature of the ed(4) for a long time, but it seems > that the newbus compatability shim is not doing the right thing > with it. My kernel config file have a line like this: > > device ed0 at isa? port 0x280 net irq ? iomem 0xd8000 > > The card gets probed but you just get device timeouts and there is no > mention of an irq for that device in the probe output. Booting with > -c and specifying the irq there also didn't work. Rebuilding the kernel > with a config file which specified the irq did work though. Could you run a test kernel for me with this patch and tell me what it prints. Index: isa_compat.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v retrieving revision 1.3 diff -u -r1.3 isa_compat.c --- isa_compat.c 1999/04/19 08:42:39 1.3 +++ isa_compat.c 1999/04/19 08:52:29 @@ -171,8 +171,11 @@ isa_set_portsize(dev, portsize); if (dvp->id_iobase != isa_get_port(dev)) isa_set_port(dev, dvp->id_iobase); - if (dvp->id_irq != (1 << isa_get_irq(dev))) + if (dvp->id_irq != (1 << isa_get_irq(dev))) { +printf("isa_compat_probe: old irq=%d, new mask=%x, new irq=%d\n", + irq_get_irq(dev), dvp->id_irq, ffs(dvp->id_irq) - 1); isa_set_irq(dev, ffs(dvp->id_irq) - 1); + } if (dvp->id_drq != isa_get_drq(dev)) isa_set_drq(dev, dvp->id_drq); if (dvp->id_maddr != maddr) -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 2: 8:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 2CDF914FE3 for ; Mon, 19 Apr 1999 02:08:38 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id RAA01297; Mon, 19 Apr 1999 17:57:16 +0900 (JST) Message-Id: <199904190857.RAA01297@shidahara1.planet.sci.kobe-u.ac.jp> To: Doug Rabson , freebsd-current@freebsd.org Dcc: Subject: Re: newbus and modem(s) In-reply-to: Your message of "Mon, 19 Apr 1999 09:33:27 +0100" References: Date: Mon, 19 Apr 1999 17:57:16 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Do ug Rabson wrote: >On Mon, 19 Apr 1999 takawata@shidahara1.planet.sci.kobe-u.ac.jp wrote: >> Simple Question. >> If there were 'Closed'-Host-Controller-Interface with object-only driver, >> Can the vendor make the Host controller recognized without changing >> usb.c code? >> >> #That's what frustrated me while writing driver for smbus controller. > >It really depends on the nature of the bus. For plug-and-play style busses >such as USB and PCI, the controller can decide what devices exist without >the help of drivers and can then uniquely match them with the right >driver. This trivially allows drivers to be added after the system is >running. I don't mention on upstream driver such as 'ukbd' (I think such device can be add truly dynamic),but I mention on 'host-controller' like [ou]hci. What I ask is what shall I do if there is a downstream driver without declared DRIVER_MODULE on upstream bus.Are there any way without changing upstream bus code? Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 2:21:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 34C6214E51 for ; Mon, 19 Apr 1999 02:21:24 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id SAA29041; Mon, 19 Apr 1999 18:17:06 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: imp@harmony.village.org Cc: jkh@zippy.cdrom.com, y-nakaga@nwsl.mesh.ad.jp, peter@netplex.com.au, current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: HEADS UP!!!! Important instructions for -current users! From: Tomoaki NISHIYAMA In-Reply-To: <199904172315.RAA25095@harmony.village.org> References: <12290.924371109@zippy.cdrom.com> <199904172315.RAA25095@harmony.village.org> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990419181705X.tomoaki@moss.nibb.ac.jp> Date: Mon, 19 Apr 1999 18:17:05 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 16 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG imp> Let us not forget that much of the newconfig work can be used with imp> newconfig shims in the newbus scheme. If you are to construct a newconfig shim in the new-bus scheme, it means that you'll have two interface to device drivers. Then, you should consider, whether it is better to make a newconfig shim in the new-bus scheme than to make a new-bus shim in the newconfig scheme. By the way, how can I subscribe new-bus mailing list? It does not seem to be controlled by majordomo@freebsd.org. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 2:25:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7507014F9E for ; Mon, 19 Apr 1999 02:25:08 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA91969; Mon, 19 Apr 1999 10:27:36 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 19 Apr 1999 10:27:36 +0100 (BST) From: Doug Rabson To: Takanori Watanabe Cc: freebsd-current@freebsd.org Subject: Re: newbus and modem(s) In-Reply-To: <199904190857.RAA01297@shidahara1.planet.sci.kobe-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999, Takanori Watanabe wrote: > In message , Do > ug Rabson wrote: > >On Mon, 19 Apr 1999 takawata@shidahara1.planet.sci.kobe-u.ac.jp wrote: > >> Simple Question. > >> If there were 'Closed'-Host-Controller-Interface with object-only driver, > >> Can the vendor make the Host controller recognized without changing > >> usb.c code? > >> > >> #That's what frustrated me while writing driver for smbus controller. > > > >It really depends on the nature of the bus. For plug-and-play style busses > >such as USB and PCI, the controller can decide what devices exist without > >the help of drivers and can then uniquely match them with the right > >driver. This trivially allows drivers to be added after the system is > >running. > > I don't mention on upstream driver such as 'ukbd' > (I think such device can be add truly dynamic),but I mention on > 'host-controller' like [ou]hci. > > What I ask is what shall I do if there is a downstream driver without > declared DRIVER_MODULE on upstream bus.Are there any way without changing > upstream bus code? I don't think I understand. The DRIVER_MODULE declaration goes in the downstream driver, not the upstream bus. The bus doesn't need any knowledge of what drivers might be attached to it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 2:37:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 1402F15368 for ; Mon, 19 Apr 1999 02:37:32 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id SAA29071; Mon, 19 Apr 1999 18:34:47 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: jkh@zippy.cdrom.com Cc: y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: HEADS UP!!!! Important instructions for -current users! From: Tomoaki NISHIYAMA In-Reply-To: <2262.924445229@zippy.cdrom.com> References: <2262.924445229@zippy.cdrom.com> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990419183445N.tomoaki@moss.nibb.ac.jp> Date: Mon, 19 Apr 1999 18:34:45 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 24 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jkh> > I don't go to new-bus, this direction is disunion of BSDs. It is jkh> > bad decision. jkh> jkh> I'm sorry that you feel this way, but I can only re-state that better jkh> communication could have prevented this in the first place and hope jkh> that you've learned your own lessons from this exercise. If you jkh> haven't, then a good opportunity for learning has simply been wasted. One problem on the decision is that it was not based on a judge that new-bus is technically or philosophically superior to newconfig framework but you stated jkh> the difference with new-bus being jkh> that we were working just that much more closely with Doug Rabson (and jkh> the others helping him) and had already used the new-bus stuff for jkh> FreeBSD/alpha. Nakagawa would not be so upset if you could convince him that new-bus were superior. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 2:42:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 87CD314EF1 for ; Mon, 19 Apr 1999 02:42:13 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id LAA22652; Mon, 19 Apr 1999 11:43:32 +0200 (MET DST) Date: Mon, 19 Apr 1999 11:39:44 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: freebsd-current@freebsd.org Cc: Doug Rabson Subject: Re: newbus and modem(s) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Simple Question. > If there were 'Closed'-Host-Controller-Interface with object-only driver, > Can the vendor make the Host controller recognized without changing > usb.c code? If he exports a USB bus with the appropriate methods, he will be able to drop it in, yes. You might have noticed when installing USB support that you get a uhci0, usb0 and uhub0 device, basically all related to that one 82371AB chip that is on your motherboard. The problem currently is that, because of the porting of the NetBSD USB code, we use a mixed scheme, which makes things slightly more complicated. There is a separate method export mechanism for the UHCI/OHCI controllers. The way this is implemented currently in the NetBSD code is ugly, to say the least. > #That's what frustrated me while writing driver for smbus controller. That is more of a design issue than something caused by newbus... Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 2:44:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id D570815550 for ; Mon, 19 Apr 1999 02:44:16 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id NAA90427 for ; Mon, 19 Apr 1999 13:41:49 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@FreeBSD.ORG Subject: new kernel and IPDIVERT Date: Mon, 19 Apr 1999 13:34:55 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99041913414800.00402@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have compiled the latest kernel and encountered a problem with IPDIVERT. even with "options IPDIVERT" string in kernel config, kernel says the following: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging disabled of course, firewall rules like "add divert natd ..." do not work. everything is ok with old kernel (~5 days old). could anyone comment this? -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 2:54:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A832214DAA for ; Mon, 19 Apr 1999 02:54:29 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA04031; Mon, 19 Apr 1999 02:51:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Tomoaki NISHIYAMA Cc: y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Mon, 19 Apr 1999 18:34:45 +0900." <19990419183445N.tomoaki@moss.nibb.ac.jp> Date: Mon, 19 Apr 1999 02:51:20 -0700 Message-ID: <4029.924515480@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One problem on the decision is that it was not based > on a judge that new-bus is technically or philosophically > superior to newconfig framework but you stated I don't think they're so far apart that there's a "clear" superiority, and we certainly didn't get that impression from any of the discussions we saw between you guys and the new-bus folks. All I saw were some strong differences of opinion being expressed and a good chance that "superiority" would never be objectively determined by any of the parties involved. > Nakagawa would not be so upset if you could convince him > that new-bus were superior. Again, this appeared to be a matter of fierce argument more than anything else and I'd probably be just as inclined to try and get a Mercedes owner to agree that BMW made a "superior" car when, in fact, both vehicles provide a more than adequate ride and have a number of nice features. Given that neither system is exactly standing still, it also meant that relative superiority was a constantly changing factor and even though it might have been possible to say that newconfig was superior on one month, it would be by no means assured that this would remain a constant. What it ultimately came down to, as I said before, was choosing the group we had the best communication with and had some existing precedent, in new-bus's case that being FreeBSD/alpha. We learned a lot of painful lessons from the PAO project given the difficulties we've had with integrating that technology on an ongoing basis, and those are lessons we had no wish to learn again. Judging superiority is only partially a technical issue, and there are many other factors of equal importance when you start discussing projects of long-term significance to FreeBSD. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 3:30:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 01D3114C80 for ; Mon, 19 Apr 1999 03:30:22 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id GAA02468; Mon, 19 Apr 1999 06:27:56 -0400 (EDT) (envelope-from luoqi) Date: Mon, 19 Apr 1999 06:27:56 -0400 (EDT) From: Luoqi Chen Message-Id: <199904191027.GAA02468@lor.watermarkgroup.com> To: current@FreeBSD.ORG, jhay@mikom.csir.co.za Subject: Re: newbus and isa auto irq Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I ave found one more thing that seems to be broken. I have used the > irq "autodetect" feature of the ed(4) for a long time, but it seems > that the newbus compatability shim is not doing the right thing > with it. My kernel config file have a line like this: > > device ed0 at isa? port 0x280 net irq ? iomem 0xd8000 > > The card gets probed but you just get device timeouts and there is no > mention of an irq for that device in the probe output. Booting with > -c and specifying the irq there also didn't work. Rebuilding the kernel > with a config file which specified the irq did work though. > > John > -- > John Hay -- John.Hay@mikom.csir.co.za > I had the same problem. Here's a fix: Index: isa_compat.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v retrieving revision 1.3 diff -u -r1.3 isa_compat.c --- isa_compat.c 1999/04/19 08:42:39 1.3 +++ isa_compat.c 1999/04/19 10:07:41 @@ -131,12 +131,14 @@ } } +#define irqmask(x) ((x) < 0 ? 0 : (1 << (x))) + static int isa_compat_probe(device_t dev) { struct isa_device *dvp = device_get_softc(dev); struct isa_compat_resources res; - + bzero(&res, sizeof(res)); /* * Fill in the isa_device fields. @@ -144,7 +146,7 @@ dvp->id_id = isa_compat_nextid(); dvp->id_driver = device_get_driver(dev)->priv; dvp->id_iobase = isa_get_port(dev); - dvp->id_irq = (1 << isa_get_irq(dev)); + dvp->id_irq = irqmask(isa_get_irq(dev)); dvp->id_drq = isa_get_drq(dev); dvp->id_maddr = (void *)isa_get_maddr(dev); dvp->id_msize = isa_get_msize(dev); @@ -171,7 +173,7 @@ isa_set_portsize(dev, portsize); if (dvp->id_iobase != isa_get_port(dev)) isa_set_port(dev, dvp->id_iobase); - if (dvp->id_irq != (1 << isa_get_irq(dev))) + if (dvp->id_irq != irqmask(isa_get_irq(dev))) isa_set_irq(dev, ffs(dvp->id_irq) - 1); if (dvp->id_drq != isa_get_drq(dev)) isa_set_drq(dev, dvp->id_drq); -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 3:41:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 94CE21525D for ; Mon, 19 Apr 1999 03:41:32 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id GAA55460; Mon, 19 Apr 1999 06:38:51 -0400 (EDT) Date: Mon, 19 Apr 1999 06:38:51 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Ilya Naumov Cc: current@FreeBSD.ORG Subject: Re: new kernel and IPDIVERT In-Reply-To: <99041913414800.00402@camel.avias.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999, Ilya Naumov wrote: > > i have compiled the latest kernel and encountered a problem with IPDIVERT. even > with "options IPDIVERT" string in kernel config, kernel says the following: > > IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging disabled That's because it's loading the ipfw.ko KLD. > > of course, firewall rules like "add divert natd ..." do not work. everything is > ok with old kernel (~5 days old). could anyone comment this? I know about it, but don't know how to fix it :( However, for now, you can go over to /usr/src/sys/modules/, edit the Makefile and add what features you want to CFLAGS, and make depend all install clean && shutdown -r now. > > -- > > sincerely, > ilya naumov (at work) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 4:31:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 137F514C16 for ; Mon, 19 Apr 1999 04:31:17 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 17D6F1F5E; Mon, 19 Apr 1999 19:28:49 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Takanori Watanabe , freebsd-current@freebsd.org Subject: Re: newbus and modem(s) In-reply-to: Your message of "Mon, 19 Apr 1999 10:27:36 +0100." Date: Mon, 19 Apr 1999 19:28:48 +0800 From: Peter Wemm Message-Id: <19990419112851.17D6F1F5E@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Mon, 19 Apr 1999, Takanori Watanabe wrote: > > > In message , Do > > ug Rabson wrote: > > >On Mon, 19 Apr 1999 takawata@shidahara1.planet.sci.kobe-u.ac.jp wrote: > > >> Simple Question. > > >> If there were 'Closed'-Host-Controller-Interface with object-only driver , > > >> Can the vendor make the Host controller recognized without changing > > >> usb.c code? > > >> > > >> #That's what frustrated me while writing driver for smbus controller. > > > > > >It really depends on the nature of the bus. For plug-and-play style busses > > >such as USB and PCI, the controller can decide what devices exist without > > >the help of drivers and can then uniquely match them with the right > > >driver. This trivially allows drivers to be added after the system is > > >running. > > > > I don't mention on upstream driver such as 'ukbd' > > (I think such device can be add truly dynamic),but I mention on > > 'host-controller' like [ou]hci. > > > > What I ask is what shall I do if there is a downstream driver without > > declared DRIVER_MODULE on upstream bus.Are there any way without changing > > upstream bus code? > > I don't think I understand. The DRIVER_MODULE declaration goes in the > downstream driver, not the upstream bus. The bus doesn't need any > knowledge of what drivers might be attached to it. Well, what about the i386 nexus? It specifically creates connection points for apm, npx, eisa, isa, and pci as children. However, pci devices don't do this to attach to their parent. I am obviously missing something. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 4:33:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id DD65914C16 for ; Mon, 19 Apr 1999 04:33:12 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id E9FBD1F5E; Mon, 19 Apr 1999 19:30:45 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman Cc: Ilya Naumov , current@FreeBSD.ORG Subject: Re: new kernel and IPDIVERT In-reply-to: Your message of "Mon, 19 Apr 1999 06:38:51 -0400." Date: Mon, 19 Apr 1999 19:30:45 +0800 From: Peter Wemm Message-Id: <19990419113045.E9FBD1F5E@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > On Mon, 19 Apr 1999, Ilya Naumov wrote: > > > > > i have compiled the latest kernel and encountered a problem with IPDIVERT. even > > with "options IPDIVERT" string in kernel config, kernel says the following: > > > > IP packet filtering initialized, divert disabled, rule-based forwarding dis abled, logging disabled > > That's because it's loading the ipfw.ko KLD. > > > > > of course, firewall rules like "add divert natd ..." do not work. everythin g is > > ok with old kernel (~5 days old). could anyone comment this? > > I know about it, but don't know how to fix it :( However, for now, you can > go over to /usr/src/sys/modules/, edit the Makefile and add what features > you want to CFLAGS, and make depend all install clean && shutdown -r now. It's quite likely I broke something with the LKM cleanup.. :-( I have not yet had a chance to revisit this, but will in a few hours. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 4:54:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 030E214DC9 for ; Mon, 19 Apr 1999 04:54:47 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id NAA26982; Mon, 19 Apr 1999 13:55:42 +0200 (MET DST) Date: Mon, 19 Apr 1999 13:51:54 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Takanori Watanabe Cc: Doug Rabson , freebsd-current@FreeBSD.ORG Subject: Re: newbus and modem(s) In-Reply-To: <199904190857.RAA01297@shidahara1.planet.sci.kobe-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let me try to post an example to see whether I understood your question: Let's assume we have a motherboard with an ISA NHCI (new host controller interface) apart from the standard PCI UHCI (Universal Host Controller Interface, Intel) available in the 82371AB chipset. We boot the system, the UHCI controller is recognised by the PCI bus driver (nexus - pci), probed by the UHCI driver (pci - usb) and this will create a driver that implements a "usb" devclass. It then starts a probe for devices on the bus it represents. The "usb" class driver was compiled into the kernel and attaches to that bus. This is the uhub driver (usb - uhub). You start websurfing and find this driver for your NHCI controller (New Host Controller Interface). After download you load the driver with kldload. The ISA bus is notified of the presence of a new driver and reprobes the ISA devices that are not attached by a driver. It probes the physical NHCI device with the NHCI driver (isa - usb) (succeeds) and attaches the loaded driver to it. This will create a new bus with device class "usb". After the attach has finished, the probe_and_attach function is called and a usb class driver will probe and attach to this new bus. You now have two USB busses (the diagram contains 2 mice, 2 keyboards, 1 Zip drive, and 2 external and 2 root hubs): pci - usb - uhub - uhub - ums \ ukbd \ umass (Zip drive) \ usb - uhub - ums \ uhub - ukbd \ trackball (The '-' and '\' represent the spots where the drivers are located. The names represent the device classes). The usb class driver is able to talk to the UHCI or NHCI driver through predefined methods, like USB_DEVICE_BULK_TRANSFER, USB_DEVICE_BULK_TRANSFER_ABORT, USB_HOST_RESET, USB_HOST_SUSPEND, etc. In later releases methods can be added by using new names. What is not possible with newbus is to attach a pci - usb driver to a bus that is not called pci, but for example pci2. But this is a logical limitation as with the change of name for the bus, the interface to the bus must have changed as well. The devclass names should therefore not contain vendor, device or type specific interfaces, only generic interfaces. I hope this serves as an explanation for your question. Kind regards, Nick P.S.: Above is a wanted situation for the USB stack not the current. The current source code contains a more complicated approach due to the fact that it is converted from newconfig in NetBSD. The UHCI driver attaches to pci and creates one child for the usb bus. This could be removed. (e.g. pci - uhci - usb - uhub - ums, for a system with only a mouse attached). Second, the uhub driver is available in two device classes, usb and uhub. > I don't mention on upstream driver such as 'ukbd' > (I think such device can be add truly dynamic),but I mention on > 'host-controller' like [ou]hci. > > What I ask is what shall I do if there is a downstream driver without > declared DRIVER_MODULE on upstream bus.Are there any way without changing > upstream bus code? > > Takanori Watanabe > > Public Key > Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 5:47:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 8098614CAA for ; Mon, 19 Apr 1999 05:47:31 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 62D951F5E; Mon, 19 Apr 1999 20:45:02 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Takanori Watanabe , freebsd-current@freebsd.org Subject: Re: newbus and modem(s) In-reply-to: Your message of "Mon, 19 Apr 1999 19:28:48 +0800." <19990419112851.17D6F1F5E@spinner.netplex.com.au> Date: Mon, 19 Apr 1999 20:45:02 +0800 From: Peter Wemm Message-Id: <19990419124505.62D951F5E@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > Doug Rabson wrote: > > On Mon, 19 Apr 1999, Takanori Watanabe wrote: > > > > > In message > , Do > > > ug Rabson wrote: > > > >On Mon, 19 Apr 1999 takawata@shidahara1.planet.sci.kobe-u.ac.jp wrote: > > > >> Simple Question. > > > >> If there were 'Closed'-Host-Controller-Interface with object-only driv er > , > > > >> Can the vendor make the Host controller recognized without changing > > > >> usb.c code? > > > >> > > > >> #That's what frustrated me while writing driver for smbus controller. > > > > > > > >It really depends on the nature of the bus. For plug-and-play style buss es > > > >such as USB and PCI, the controller can decide what devices exist withou t > > > >the help of drivers and can then uniquely match them with the right > > > >driver. This trivially allows drivers to be added after the system is > > > >running. > > > > > > I don't mention on upstream driver such as 'ukbd' > > > (I think such device can be add truly dynamic),but I mention on > > > 'host-controller' like [ou]hci. > > > > > > What I ask is what shall I do if there is a downstream driver without > > > declared DRIVER_MODULE on upstream bus.Are there any way without changing > > > upstream bus code? > > > > I don't think I understand. The DRIVER_MODULE declaration goes in the > > downstream driver, not the upstream bus. The bus doesn't need any > > knowledge of what drivers might be attached to it. > > Well, what about the i386 nexus? It specifically creates connection points > for apm, npx, eisa, isa, and pci as children. > > However, pci devices don't do this to attach to their parent. I am > obviously missing something. :-) Never mind, I understand now. :-) For the benefit of the 'cc' list, and to check my understanding, let me run through it.. The parents pick up the children in one of two ways. For a 'smart' bus, like pci, usb, eisa, etc, the bus probes itself and adds an "unidentified" child (NULL name, -1 unit) with the known ID. The bus mechanism then uses this to poll the drivers to see which one(s) want to claim that ID. It knows who the children are because of the DECLARE_MODULE() statement. This means that a "smart" (or self identifying) bus doesn't need anything more to manage the relationship. On the other hand, there's isa, which is quite dumb. In this case, the bus looks up it's "hint" list and specifically adds the requested children from those hints, and using the supplied irq, port, etc values from the hints. The drivers then use that data to probe for the existance of the device. The nexus is a little bit different.. It doesn't have things to specifically look for, so it adds the children manually. It could have used the resource database to find the requested things to attach to the nexus in pretty much the same way as the isa bus does. And then there's the old isa drivers... They attach themselves to the isa parent device class on the fly, there is no DECLARE_MODULE() table for all the old isa (and perhaps PCI too) drivers. Doug, is that right so far? :-) Now what I'm curious about is how to handle the nexus and isa/eisa better so they don't need to explicitly name the children. On one hand it could look at the hints table to see all the 'at nexus?' declarations, but I think it might be better to go for a hunt to locate all the children it can find. One way to do this might be to simply add a heap of "unidentified" devices and let the bus mechanism find all the devices that are children and let them probe themselves while ignoring the fake device id's. Perhaps this could change the probe order enough so that isa and eisa won't be attached until after pci has been recursively probed. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 6: 9:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 29D2B154EA for ; Mon, 19 Apr 1999 06:09:10 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id VAA02584; Mon, 19 Apr 1999 21:57:42 +0900 (JST) Message-Id: <199904191257.VAA02584@shidahara1.planet.sci.kobe-u.ac.jp> To: Peter Wemm , current@freebsd.org, dfr@nlsystems.com Dcc: Subject: Re: newbus and modem(s) In-reply-to: Your message of "Mon, 19 Apr 1999 20:45:02 +0800" References: <19990419124505.62D951F5E@spinner.netplex.com.au> Date: Mon, 19 Apr 1999 21:57:40 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990419124505.62D951F5E@spinner.netplex.com.au>, Peter Wemm wrote: >Never mind, I understand now. :-) Ok, I think I also understand. The DRIVER_MODULE() macro is consist for static configuration to kick module initialization routine for every driver.Is it correct? But are ther more better way? Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 6:45:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 1941C15548 for ; Mon, 19 Apr 1999 06:45:12 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id JAA06265 for ; Mon, 19 Apr 1999 09:45:28 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Mon, 19 Apr 1999 09:45:28 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: error building kernel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I followed the instructions about NEXUS to rebuild my kernel, and it now it won't compile. It gets all the way through the compile, and then gives these errors. generating linker set emulation glue for ELF cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_glob al.h -elf setdef0.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_glob al.h -elf vnode_if.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_glob al.h -elf ioconf.c ioconf.c:108: warning: `psm0_count' redefined ioconf.c:68: warning: this is the location of the previous definition ioconf.c:102: redefinition of `psm0_resources' ioconf.c:64: `psm0_resources' ioconf.c:64: `psm0_resources' previously defined here ioconf.c:105: warning: excess elements in array initializer after `psm0_resource s' ioconf.c:106: warning: excess elements in array initializer after `psm0_resource s' *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 7:40:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 1354814FA0 for ; Mon, 19 Apr 1999 07:40:53 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 13FE01F5E; Mon, 19 Apr 1999 22:38:22 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: error building kernel In-reply-to: Your message of "Mon, 19 Apr 1999 09:45:28 -0400." Date: Mon, 19 Apr 1999 22:38:22 +0800 From: Peter Wemm Message-Id: <19990419143825.13FE01F5E@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > I followed the instructions about NEXUS to rebuild my kernel, and it > now it won't compile. It gets all the way through the compile, and then > gives these errors. I'll bet you've got two 'psm0' lines in the config file.. All that config is doing now is basically compiling a table of what's in your config file and saving that for the probe code to use. Yes, It should probably check for duplicates.. :-) > al.h -elf ioconf.c > ioconf.c:108: warning: `psm0_count' redefined > ioconf.c:68: warning: this is the location of the previous definition > ioconf.c:102: redefinition of `psm0_resources' > ioconf.c:64: `psm0_resources' > ioconf.c:64: `psm0_resources' previously defined here > ioconf.c:105: warning: excess elements in array initializer after > `psm0_resource > s' > ioconf.c:106: warning: excess elements in array initializer after > `psm0_resource > s' Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 9:34:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from rem.club.gagarinclub.ru (unknown [194.67.174.146]) by hub.freebsd.org (Postfix) with ESMTP id 6A5BE14FCD for ; Mon, 19 Apr 1999 09:34:35 -0700 (PDT) (envelope-from firma@gagarinclub.ru) Received: from localhost (firma@localhost) by rem.club.gagarinclub.ru (8.9.3/8.9.3) with ESMTP id UAA00723 for ; Mon, 19 Apr 1999 20:32:27 +0400 (MSD) X-Authentication-Warning: rem.club.gagarinclub.ru: firma owned process doing -bs Date: Mon, 19 Apr 1999 20:32:27 +0400 (MSD) From: REM X-Sender: firma@rem.club.gagarinclub.ru To: current@freebsd.org Subject: sysinstall crash system after cvsup at 990417 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I supped my system at 990417. Then I make world and rebuild sysinstall. The command /stand/sysinstall crash my system during probe hard disk. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x31 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0136de0 stack pointer = 0x10:0xc4a03d98 frame pointer = 0x10:0xc4a03d98 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 = 2266 (sysinstall) interrupt mask = trap number = 12 panic: page fault To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 9:44: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 97C2614D11 for ; Mon, 19 Apr 1999 09:43:56 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-65-133.atl.bellsouth.net [209.214.65.133]) by mail0.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id MAA09723; Mon, 19 Apr 1999 12:40:46 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id MAA24418; Mon, 19 Apr 1999 12:41:44 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199904191641.MAA24418@bellsouth.net> To: Alex Zepeda Cc: "Daniel C. Sobral" , "Jordan K. Hubbard" , current , wghicks@wghicks.bellsouth.net Subject: Re: newbus and modem(s) In-reply-to: Your message of "Sun, 18 Apr 1999 10:00:14 PDT." Date: Mon, 19 Apr 1999 12:41:44 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And then what about newconfig? To me this just adds more truth to the > whole /. argument that *BSD promotes a closed development model. It's a flawed argument and one that doesn't acknowledge, at least in the case of FreeBSD, the existence of publicly accessible CVS repositories along with the GNATS databases for non-committer submissions. It's a more centralized development model but not necessarily a closed one. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 9:58:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id BC30C1529F for ; Mon, 19 Apr 1999 09:58:21 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-65-133.atl.bellsouth.net [209.214.65.133]) by mail0.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id MAA19719; Mon, 19 Apr 1999 12:55:26 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id MAA24648; Mon, 19 Apr 1999 12:56:24 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199904191656.MAA24648@bellsouth.net> To: Alex Zepeda Cc: Brian Feldman , "Daniel C. Sobral" , "Jordan K. Hubbard" , current , wghicks@wghicks.bellsouth.net Subject: Re: newbus and modem(s) In-reply-to: Your message of "Sun, 18 Apr 1999 16:59:38 PDT." Date: Mon, 19 Apr 1999 12:56:24 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I saw this and just had to note something to you. THINK what branch you > > are using. This is _WHERE_ things are being aired publically, and merged > > eventually to the STABLE branch. > > Gosh, thank you, without your wonderful help and understanding, I NEVER > would have been able to realize this. You are so smart. Will you commit > my code which breaks a few things and causes a panic? Wouldya? Huh? Huh? > Huh? Don't forget that the GNATS database is a wonderful resource for acquiring patches and submitting things experimental and/or broken for consideration by others. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 10: 7: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 499EC152CA for ; Mon, 19 Apr 1999 10:07:03 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id KAA43787; Mon, 19 Apr 1999 10:02:52 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904191702.KAA43787@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: W Gerald Hicks Cc: Alex Zepeda , "Daniel C. Sobral" , "Jordan K. Hubbard" , current , wghicks@wghicks.bellsouth.net Subject: Re: newbus and modem(s) In-reply-to: Your message of "Mon, 19 Apr 1999 12:41:44 EDT." <199904191641.MAA24418@bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Apr 1999 10:02:51 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD is somewhat of a closed development enviroment what some organizations do is that they maintain their own cvs repository. CVS repository is guarded by the core members and only "certified" committers are allowed to commit code that in addition to not having a procedure or a processs to mitigate technical conflicts such as new config vs new-bus makes the develpment process at least a closed one from the perspective of the FreeBSD cvs repository. > > And then what about newconfig? To me this just adds more truth to the > > whole /. argument that *BSD promotes a closed development model. > > It's a flawed argument and one that doesn't acknowledge, at least in > the case of FreeBSD, the existence of publicly accessible CVS repositories > along with the GNATS databases for non-committer submissions. > > It's a more centralized development model but not necessarily a closed one. > > Cheers, > > Jerry Hicks > wghicks@bellsouth.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 10:14:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 529B5155CC for ; Mon, 19 Apr 1999 10:14:43 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA10465; Mon, 19 Apr 1999 11:11:53 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA28594; Mon, 19 Apr 1999 11:11:52 -0600 Date: Mon, 19 Apr 1999 11:11:52 -0600 Message-Id: <199904191711.LAA28594@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Amancio Hasty Cc: W Gerald Hicks , Alex Zepeda , "Daniel C. Sobral" , "Jordan K. Hubbard" , current , wghicks@wghicks.bellsouth.net Subject: Re: newbus and modem(s) In-Reply-To: <199904191702.KAA43787@rah.star-gate.com> References: <199904191641.MAA24418@bellsouth.net> <199904191702.KAA43787@rah.star-gate.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD is somewhat of a closed development enviroment what > some organizations do is that they maintain their own cvs repository. FreeBSD is no more closed than "linux" is, which is touted as the most open development project that exists. Joe Average person can no more commit can't commit code to the linux 'development' tree than he can to the FreeBSD tree, since there are 'developers' that maintain both trees. I know of *NO* completey open development environment, but FreeBSD's is *MUCH* more open than most, including Linux's. With the FreeBSD environment, the entire 'process' of development is more open (it is almost completely public except for some discussions that happen on the core mailing list, which I assume are less technical and more political) than any other project I'm aware of. What other project (aside from OpenBSD) gives you the ability to see the entire source code history of the tree, along with real-time discussion and development of the source code? All 'source code' control is guarded by a certain group of people in *every* project, and FreeBSD is no different. It just has different folks guarding it, who have different standards and requirements. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 10:19:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 61628152B5 for ; Mon, 19 Apr 1999 10:19:40 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id NAA05343; Mon, 19 Apr 1999 13:11:42 -0400 (EDT) Message-ID: <001e01be8a88$8f744660$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Alex Zepeda" , "W Gerald Hicks" Cc: "Brian Feldman" , "Daniel C. Sobral" , "Jordan K. Hubbard" , "current" , References: <199904191656.MAA24648@bellsouth.net> Subject: Re: newbus and modem(s) Date: Mon, 19 Apr 1999 13:17:53 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: Just wanted to say that I think the lack of a free-for-all CVS is exactly what is required to consistently move FreeBSD forward. If someone feels they would like to take a different approach, then I say by all means do so. If you can convince people to join your development effort then great!, if not, then great!. Rick Whitesel Scientist NBase-Xyplex rwhitesel@nbase-xyplex.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 ----- Original Message ----- From: W Gerald Hicks To: Alex Zepeda Cc: Brian Feldman ; Daniel C. Sobral ; Jordan K. Hubbard ; current ; Sent: Monday, April 19, 1999 12:56 PM Subject: Re: newbus and modem(s) > > I saw this and just had to note something to you. THINK what branch you > > are using. This is _WHERE_ things are being aired publically, and merged > > eventually to the STABLE branch. > > Gosh, thank you, without your wonderful help and understanding, I NEVER > would have been able to realize this. You are so smart. Will you commit > my code which breaks a few things and causes a panic? Wouldya? Huh? Huh? > Huh? Don't forget that the GNATS database is a wonderful resource for acquiring patches and submitting things experimental and/or broken for consideration by others. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 10:23:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 0A1B1155B7 for ; Mon, 19 Apr 1999 10:23:19 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10ZHfr-0003tm-00; Mon, 19 Apr 1999 19:17:35 +0200 From: Sheldon Hearn To: Tomoaki NISHIYAMA Cc: imp@harmony.village.org, jkh@zippy.cdrom.com, y-nakaga@nwsl.mesh.ad.jp, peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: Important instructions for -current users! In-reply-to: Your message of "Mon, 19 Apr 1999 18:17:05 +0900." <19990419181705X.tomoaki@moss.nibb.ac.jp> Date: Mon, 19 Apr 1999 19:17:35 +0200 Message-ID: <14989.924542255@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999 18:17:05 +0900, Tomoaki NISHIYAMA wrote: > By the way, how can I subscribe new-bus mailing list? > It does not seem to be controlled by majordomo@freebsd.org. I took "HEADS UP" out of the Subject to help the guy who maintains src/UPDATING . :-) You can subscribe to the list by mailing majordomo@bostonradio.org with no subject and the request subscribe new-bus-arch in the body of your message. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 10:27:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id AA68715577 for ; Mon, 19 Apr 1999 10:27:18 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id KAA43892; Mon, 19 Apr 1999 10:22:48 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904191722.KAA43892@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams Cc: W Gerald Hicks , Alex Zepeda , "Daniel C. Sobral" , "Jordan K. Hubbard" , current , wghicks@wghicks.bellsouth.net Subject: Re: newbus and modem(s) In-reply-to: Your message of "Mon, 19 Apr 1999 11:11:52 MDT." <199904191711.LAA28594@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Apr 1999 10:22:48 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > All 'source code' control is guarded by a certain group of people in > *every* project, and FreeBSD is no different. It just has different > folks guarding it, who have different standards and requirements. Perhaps a good step towards understanding would be if those "guarding" the process would actually state what is their standard and requirements, if they have any. It coud start by something like this: FreeBSD Development Guidelines and Motivation... It don't matter nothing has bee resolved with this issue for the last year when I highlighted this problem and I doubt that anything will come out of it this time. Time To Hack! 8) -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 10:41:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id ECB7614C8E for ; Mon, 19 Apr 1999 10:41:13 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id TAA97791; Mon, 19 Apr 1999 19:38:31 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199904191738.TAA97791@zibbi.mikom.csir.co.za> Subject: Re: newbus and isa auto irq In-Reply-To: from Doug Rabson at "Apr 19, 1999 09:53:20 am" To: dfr@nlsystems.com (Doug Rabson) Date: Mon, 19 Apr 1999 19:38:31 +0200 (SAT) Cc: current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I ave found one more thing that seems to be broken. I have used the > > irq "autodetect" feature of the ed(4) for a long time, but it seems > > that the newbus compatability shim is not doing the right thing > > with it. My kernel config file have a line like this: > > > > device ed0 at isa? port 0x280 net irq ? iomem 0xd8000 > > > > The card gets probed but you just get device timeouts and there is no > > mention of an irq for that device in the probe output. Booting with > > -c and specifying the irq there also didn't work. Rebuilding the kernel > > with a config file which specified the irq did work though. > > Could you run a test kernel for me with this patch and tell me what it > prints. > It doesn't print anything for the ed0 device. It does print 2 lines though, one for wdc0 and one for the printer port: ------- Apr 19 19:22:27 orca /kernel.doug: fdc0: FIFO enabled, 8 bytes threshold Apr 19 19:22:27 orca /kernel.doug: fd0: <1440-KB 3.5" drive> at fdc0 drive 0 Apr 19 19:22:27 orca /kernel.doug: isa_compat_probe: old irq=-1, new mask=4000, new irq=14 Apr 19 19:22:27 orca /kernel.doug: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 Apr 19 19:22:27 orca /kernel.doug: wdc0: unit 0 (wd0): Apr 19 19:22:27 orca /kernel.doug: wd0: 610MB (1249920 sectors), 1240 cyls, 16 h eads, 63 S/T, 512 B/S Apr 19 19:22:27 orca /kernel.doug: wdc0: interrupting at irq 14 ... Apr 19 19:22:28 orca /kernel.doug: isa_compat_probe: old irq=-1, new mask=80, new irq=7 Apr 19 19:22:28 orca /kernel.doug: ppc0 at port 0x378 irq 7 on isa0 Apr 19 19:22:28 orca /kernel.doug: ppc0: SMC FDC37C665GT chipset (PS2/NIBBLE) in COMPATIBLE mode Apr 19 19:22:28 orca /kernel.doug: ppb0: IEEE1284 device found Apr 19 19:22:28 orca /kernel.doug: Probing for PnP devices on ppbus0: Apr 19 19:22:28 orca /kernel.doug: lpt0: on ppbus 0 Apr 19 19:22:28 orca /kernel.doug: lpt0: Interrupt-driven port Apr 19 19:22:28 orca /kernel.doug: ppc0: interrupting at irq 7 Apr 19 19:22:28 orca /kernel.doug: ed0 at port 0x280-0x29f on isa0 Apr 19 19:22:28 orca /kernel.doug: ed0: address 00:00:c0:1d:43:db, type SMC8216/ SMC8216C (16 bit) Apr 19 19:22:28 orca /kernel.doug: Intel Pentium detected, installing workaround for F00F bug -------- > - if (dvp->id_irq != (1 << isa_get_irq(dev))) > + if (dvp->id_irq != (1 << isa_get_irq(dev))) { > +printf("isa_compat_probe: old irq=%d, new mask=%x, new irq=%d\n", > + irq_get_irq(dev), dvp->id_irq, ffs(dvp->id_irq) - 1); > isa_set_irq(dev, ffs(dvp->id_irq) - 1); > + } I assume the irq_get_irq() should be isa_get_irq(). I have tried the patch that Luoqi posted and that works for me. Although even with that the the userconfig by booting with -c don't work. It just plain ignores what you do there. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 10:49:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from 207-172-1-7.noc.erols.net (207-172-1-7.noc.erols.net [207.172.1.7]) by hub.freebsd.org (Postfix) with ESMTP id F40F114C8E for ; Mon, 19 Apr 1999 10:49:20 -0700 (PDT) (envelope-from dacoder@dcoder.com) Received: from dcoder.com (localhost [127.0.0.1]) by 207-172-1-7.noc.erols.net (8.8.7/8.8.7) with ESMTP id NAA01464; Mon, 19 Apr 1999 13:48:53 -0400 Message-ID: <371B6C85.1EC9D7FA@dcoder.com> Date: Mon, 19 Apr 1999 13:48:53 -0400 From: David Coder Organization: Erols Internet Service/RCN X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.36 i686) MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG, dacoder@dcoder.com Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 11: 0: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 89AA215311 for ; Mon, 19 Apr 1999 10:59:58 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 49D401F5E; Tue, 20 Apr 1999 01:57:30 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay Cc: dfr@nlsystems.com (Doug Rabson), current@freebsd.org Subject: Re: newbus and isa auto irq In-reply-to: Your message of "Sat, 19 Apr 1999 19:38:31 +0200." <199904191738.TAA97791@zibbi.mikom.csir.co.za> Date: Tue, 20 Apr 1999 01:57:30 +0800 From: Peter Wemm Message-Id: <19990419175732.49D401F5E@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: [..] > Apr 19 19:22:28 orca /kernel.doug: ppc0: interrupting at irq 7 > Apr 19 19:22:28 orca /kernel.doug: ed0 at port 0x280-0x29f on isa0 > Apr 19 19:22:28 orca /kernel.doug: ed0: address 00:00:c0:1d:43:db, type SMC82 16/ > SMC8216C (16 bit) > Apr 19 19:22:28 orca /kernel.doug: Intel Pentium detected, installing workaro und > for F00F bug > -------- > > > - if (dvp->id_irq != (1 << isa_get_irq(dev))) > > + if (dvp->id_irq != (1 << isa_get_irq(dev))) { > > +printf("isa_compat_probe: old irq=%d, new mask=%x, new irq=%d\n", > > + irq_get_irq(dev), dvp->id_irq, ffs(dvp->id_irq) - 1); > > isa_set_irq(dev, ffs(dvp->id_irq) - 1); > > + } > > I assume the irq_get_irq() should be isa_get_irq(). > > I have tried the patch that Luoqi posted and that works for me. Although > even with that the the userconfig by booting with -c don't work. It just > plain ignores what you do there. An additional datapoint... We have: dvp->id_maddr = (void *)isa_get_maddr(dev); [..] void *maddr; isa_compat_alloc_resources(dev, &res); if (res.memory) maddr = rman_get_virtual(res.memory); else maddr = 0; dvp->id_maddr = maddr; portsize = dvp->id_driver->probe(dvp); isa_compat_release_resources(dev, &res); if (portsize != 0) { if (portsize > 0) isa_set_portsize(dev, portsize); if (dvp->id_iobase != isa_get_port(dev)) isa_set_port(dev, dvp->id_iobase); if (dvp->id_irq != (1 << isa_get_irq(dev))) isa_set_irq(dev, ffs(dvp->id_irq) - 1); if (dvp->id_drq != isa_get_drq(dev)) isa_set_drq(dev, dvp->id_drq); if (dvp->id_maddr != maddr) isa_set_maddr(dev, (int) dvp->id_maddr - KERNBASE); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ if (dvp->id_msize != isa_get_msize(dev)) isa_set_msize(dev, dvp->id_msize); There is the problem.. isa_compat_release_resources() is clearing the hints. The only reason it works for the other devices is things like: if (dvp->id_iobase != isa_get_port(dev)) isa_set_port(dev, dvp->id_iobase); .. ie: if (id_iobase != ) reset_hint(id_iobase); .. etc. This is not happening for the maddr stuff. I suspect this would do better: if (portsize > 0) isa_set_portsize(dev, portsize); if (dvp->id_iobase >= 0) isa_set_port(dev, dvp->id_iobase); if (dvp->id_irq != 0) isa_set_irq(dev, ffs(dvp->id_irq) - 1); if (dvp->id_drq != -1) isa_set_drq(dev, dvp->id_drq); if (dvp->id_maddr != 0) isa_set_maddr(dev, (int) dvp->id_maddr - KERNBASE); if (dvp->id_msize != 0) isa_set_msize(dev, dvp->id_msize); I'm not sure about the "nothing" value for id_drq though, it might need to be 0 - but that's a valid dma channel. IMHO, isa_release_resources() clearing of the default values for the probe hints is a timebomb... I thought about adding a seperate store for the "hint" values rather than using the id_foo[0] entries, and leaving the tracked resource entries for alloc/free without risking the hints. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 11:10:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 141D514E8E for ; Mon, 19 Apr 1999 11:10:02 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA26701; Mon, 19 Apr 1999 19:59:32 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id TAA00901; Mon, 19 Apr 1999 19:58:06 +0200 (CEST) From: Wilko Bulte Message-Id: <199904191758.TAA00901@yedi.iaf.nl> Subject: Re: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! ) In-Reply-To: <199904190350.VAA03403@harmony.village.org> from Warner Losh at "Apr 18, 1999 9:50:43 pm" To: imp@harmony.village.org (Warner Losh) Date: Mon, 19 Apr 1999 19:58:05 +0200 (CEST) Cc: nate@mt.sri.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Warner Losh wrote ... > In message <199904181923.NAA25095@mt.sri.com> Nate Williams writes: > : This is wonderful, but has this ever happened in our mailing lists? I > : guess I don't remember anyone *ever* ridiculing or harassing someone for > : not being fluent in the language. > > I have seen people ask others to explain again since they didn't > understand, but I cannot recall ever seeing anybody holding someone up > to ridicule publically. I have deep respect for several people that > have pushed through the language barrier. Maybe we should decide that this is a thing to keep in mind and let it rest for now? Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 11:53:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 1E82114D6B for ; Mon, 19 Apr 1999 11:52:46 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id OAA05777; Mon, 19 Apr 1999 14:21:41 -0400 (EDT) (envelope-from luoqi) Date: Mon, 19 Apr 1999 14:21:41 -0400 (EDT) From: Luoqi Chen Message-Id: <199904191821.OAA05777@lor.watermarkgroup.com> To: jhay@mikom.csir.co.za, peter@netplex.com.au Subject: Re: newbus and isa auto irq Cc: current@FreeBSD.ORG, dfr@nlsystems.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is not happening for the maddr stuff. > I suspect this would do better: > > if (portsize > 0) > isa_set_portsize(dev, portsize); > if (dvp->id_iobase >= 0) > isa_set_port(dev, dvp->id_iobase); > if (dvp->id_irq != 0) > isa_set_irq(dev, ffs(dvp->id_irq) - 1); > if (dvp->id_drq != -1) > isa_set_drq(dev, dvp->id_drq); > if (dvp->id_maddr != 0) > isa_set_maddr(dev, > (int) dvp->id_maddr - KERNBASE); > if (dvp->id_msize != 0) > isa_set_msize(dev, dvp->id_msize); > I'm not sure about the "nothing" value for id_drq though, it might need to > be 0 - but that's a valid dma channel. > > IMHO, isa_release_resources() clearing of the default values for the probe > hints is a timebomb... I thought about adding a seperate store for the > "hint" values rather than using the id_foo[0] entries, and leaving the > tracked resource entries for alloc/free without risking the hints. > > Cheers, > -Peter > Off the topic, I think we should replace (dvp->id_maddr - KERNBASE) with kvtop(dvp->id_maddr), too much assumption about vm layout... -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 12: 8:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 34D63155EC; Mon, 19 Apr 1999 12:06:49 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id UAA15041; Mon, 19 Apr 1999 20:02:11 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA00637; Mon, 19 Apr 1999 19:15:18 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199904191815.TAA00637@keep.lan.Awfulhak.org> Date: Mon, 19 Apr 1999 19:15:18 +0100 From: Brian Somers Subject: Re: HEADS UP!!!! Important instructions for -current users! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- Blind-Carbon-Copy X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm , dfr@freebsd.org Cc: sos@FreeBSD.org Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Sat, 17 Apr 1999 05:30:41 +0800." <19990416213043.95C7B1F69@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 19 Apr 1999 19:15:18 +0100 From: Brian Somers > As of a few minutes ago, a minimal set of changes to bring the so-calle= d > 'new-bus' functionality to the i386 kernel in -current. [.....] WOW ! All of a sudden ``halt -p'' works properly on my PCG-747 VIAO = notebook ! Also, S=F8ren's ATA DMA code has started to work... awesome ! Well done Doug & associates - and S=F8ren for the ATA stuff. > Cheers, > -Peter - -- = Brian Don't _EVER_ lose your sense of humour ! ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 12:23: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id A956F14E4F for ; Mon, 19 Apr 1999 12:23:03 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA29053; Mon, 19 Apr 1999 20:39:54 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id UAA01249; Mon, 19 Apr 1999 20:12:27 +0200 (CEST) From: Wilko Bulte Message-Id: <199904191812.UAA01249@yedi.iaf.nl> Subject: Re: newbus and modem(s) In-Reply-To: <001e01be8a88$8f744660$d3e4b38c@xyplex.com> from Rick Whitesel at "Apr 19, 1999 1:17:53 pm" To: rwhitesel@nbase-xyplex.com (Rick Whitesel) Date: Mon, 19 Apr 1999 20:12:27 +0200 (CEST) Cc: garbanzo@hooked.net, wghicks@bellsouth.net, green@unixhelp.org, dcs@newsguy.com, jkh@zippy.cdrom.com, current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Rick Whitesel wrote ... > Hi: > Just wanted to say that I think the lack of a free-for-all CVS is > exactly what is required to consistently move FreeBSD forward. If someone Free-for-all as in 'everybody can do commits' ? This is a joke I hope. There already exists such a thing. It is called Linux (and even there the kernel is controlled). > feels they would like to take a different approach, then I say by all means > do so. If you can convince people to join your development effort then > great!, if not, then great!. > > Rick Whitesel > Scientist > NBase-Xyplex > rwhitesel@nbase-xyplex.com Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 12:50:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id F35C4156AF for ; Mon, 19 Apr 1999 12:50:02 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA59505; Mon, 19 Apr 1999 13:47:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA26579; Mon, 19 Apr 1999 13:47:03 -0600 (MDT) Message-Id: <199904191947.NAA26579@harmony.village.org> To: Peter Wemm Subject: Re: error building kernel Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Apr 1999 22:38:22 +0800." <19990419143825.13FE01F5E@spinner.netplex.com.au> References: <19990419143825.13FE01F5E@spinner.netplex.com.au> Date: Mon, 19 Apr 1999 13:47:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990419143825.13FE01F5E@spinner.netplex.com.au> Peter Wemm writes: : I'll bet you've got two 'psm0' lines in the config file.. I got the same error when I had two psm devices in my kernel. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 13: 3:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id D885615A53 for ; Mon, 19 Apr 1999 13:03:42 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id WAA06275 for freebsd-current@freebsd.org; Mon, 19 Apr 1999 22:01:12 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id 8A68E40; Mon, 19 Apr 1999 21:59:53 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 40C551E2B for ; Mon, 19 Apr 1999 21:59:53 +0200 (CEST) Date: Mon, 19 Apr 1999 21:59:53 +0200 (CEST) From: Blaz Zupan To: freebsd-current@freebsd.org Subject: PCI VGA card becomes ISA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that after the latest round of new-bus changes, my PCI VGA card is now recognized as a generic ISA card by the kernel. I don't see any ill effects from this, but the new-bus developers may want to know, in case it breaks something else. The VGA card is a S3 Trio64V+. Here's the dmesg output I get. I don't have an old dmesg output before the changes, but the card was recognized by its name and it was using IRQ 9. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Mon Apr 19 21:41:42 CEST 1999 blaz@gold.amis.net:/usr/home/blaz/FreeBSD/src/sys/compile/GOLD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (232.88-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 67108864 (65536K bytes) config> pnp 1 0 os enable config> pnp 1 0 port0 0x220 port1 0x530 port2 0x388 port3 0x370 config> pnp 1 0 irq0 5 drq0 1 drq1 0 config> pnp 2 0 os enable config> pnp 2 0 port0 0x280 irq0 10 avail memory = 62435328 (60972K bytes) Preloaded elf kernel "kernel" at 0xc02b6000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02b609c. Probing for PnP devices: CSN 1 Vendor ID: YMH0030 [0x3000a865] Serial 0x80860001 Comp ID: PNPb02f [0x2fb0d041] mss_attach 1 at 0x530 irq 5 dma 1:0 flags 0x10 setting up yamaha registers set yamaha master volume to max pcm1 (CS423x/Yamaha/AD1816 sn 0x80860001) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa CSN 2 Vendor ID: CPX1501 [0x0115180e] Serial 0x48ed418e Comp ID: PNP80d6 [0xd680d041] ed1: address 00:80:48:ed:41:8e, type NE2000 (16 bit) ed1 (edpnp sn 0x48ed418e) at 0x280-0x29f irq 10 on isa npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 isab0: at device 7.0 on pci0 chip1: at device 7.3 on pci0 ahc0: at device 14.0 on pci0 ahc0: interrupting at irq 14 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 isic0 at port 0xd80 irq 15 flags 0x3 on isa0 isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) isic0: interrupting at irq 15 ppc0 at port 0x378 irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 Intel Pentium detected, installing workaround for F00F bug i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached Waiting 2 seconds for SCSI devices to settle changing root device to da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15) da1: 1547MB (3170160 512 byte sectors: 255H 63S/T 197C) cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 13: 8:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from lupo.thebarn.com (lupo.lcse.umn.edu [128.101.182.105]) by hub.freebsd.org (Postfix) with ESMTP id 3853F156B1 for ; Mon, 19 Apr 1999 13:08:33 -0700 (PDT) (envelope-from cattelan@thebarn.com) Received: from thebarn.com (jizz.thebarn.com [128.101.182.205]) by lupo.thebarn.com (8.9.3/8.9.1) with ESMTP id PAA00491 for ; Mon, 19 Apr 1999 15:05:36 -0500 (CDT) Message-ID: <371B8AAA.E359696@thebarn.com> Date: Mon, 19 Apr 1999 14:57:31 -0500 From: Russell Cattelan X-Mailer: Mozilla 4.51C-SGI [en] (X11; U; IRIX 6.5 IP22) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: pcm sound driver crashes at boot time. References: <199904190633.BAA01439@fun.thebarn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Russell Cattelan wrote: > I haven't been able to track down exactly where this > is occuring, but disabling pcm allows eliminates the crash. > > The build is current as of Sun 18th. > > The one strange thing about this box, it has > two sounds cards. A build in Yamaha OPL-3 (really really crappy) > and Ensoniq AudioPCI 1371 (very hacked driver, So the problem may be my fault). > But I guessing it has more to do with the newbus stuff. > Ok I finally tracked down what was going wrong, I'm not saying I found the problem of how to fix it correctly. The cause: pcmprobe gets called after es_pci_attach (which has setup the snddev_info structure), the first thing pcmprobe does is bzero that structure. Which of course cause a page fault the next time that structure is access. (by es_intr in this case) The really Q&D fix was to just return from pcmprobe. int pcmprobe(struct isa_device * dev) { DEB(printf("pcmprobe dev:0x%x name:%s\n",dev, &(pcm_info[dev->id_unit]).name)); /* The AudioPCI probe stuff was done already */ if(!(strncmp (&(pcm_info[dev->id_unit]).name, "ES1371",strlen("ES1371")))){ return 1; } bzero(&pcm_info[dev->id_unit], sizeof(pcm_info[dev->id_unit]) ); return generic_snd_probe(dev, pcm_devslist, "pcm") ? 1 : 0 ; } -- Russell Cattelan cattelan@thebarn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 13:15:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id B013614E68 for ; Mon, 19 Apr 1999 13:15:06 -0700 (PDT) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id NAA00427 for freebsd-current@freebsd.org; Mon, 19 Apr 1999 13:10:31 -0700 (PDT) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <199904192010.NAA00427@troutmask.apl.washington.edu> Subject: modules/joy breaks make world To: freebsd-current@freebsd.org Date: Mon, 19 Apr 1999 13:10:31 -0700 (PDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI. The recent commit to move sys/sys/lkm.h to the attic breaks "make world" is sys/module/joy. 1.19 Mon Apr 19 14:19:52 1999 UTC by peter CVS Tags: HEAD Diffs to 1.18 FILE REMOVED Zap LKM option and support. Farewell old friend. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 13:19:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 5418115E4D for ; Mon, 19 Apr 1999 13:19:02 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id QAA07564; Mon, 19 Apr 1999 16:10:58 -0400 (EDT) Message-ID: <002701be8aa1$99ad6d00$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Wilko Bulte" Cc: , , , , , , References: <199904191812.UAA01249@yedi.iaf.nl> Subject: Re: newbus and modem(s) Date: Mon, 19 Apr 1999 16:17:07 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: Sorry for my lack of clarity. What I meant was that we DO need control on the cvsup updates. I am perfectly happy with the way the FreeBSD team runs the show. Rick ----- Original Message ----- From: Wilko Bulte To: Rick Whitesel Cc: ; ; ; ; ; ; Sent: Monday, April 19, 1999 2:12 PM Subject: Re: newbus and modem(s) As Rick Whitesel wrote ... > Hi: > Just wanted to say that I think the lack of a free-for-all CVS is > exactly what is required to consistently move FreeBSD forward. If someone Free-for-all as in 'everybody can do commits' ? This is a joke I hope. There already exists such a thing. It is called Linux (and even there the kernel is controlled). > feels they would like to take a different approach, then I say by all means > do so. If you can convince people to join your development effort then > great!, if not, then great!. > > Rick Whitesel > Scientist > NBase-Xyplex > rwhitesel@nbase-xyplex.com Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ http://www.freebsd.org _____ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 13:55:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 0829E15208 for ; Mon, 19 Apr 1999 13:55:12 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id NAA44061; Mon, 19 Apr 1999 13:52:43 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904192052.NAA44061@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf LINT GENERIC In-reply-to: Your message of "Mon, 19 Apr 1999 22:35:55 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Apr 1999 13:52:43 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Redirected to -current... I seem to recollect that you were having problems in handling interrupts so were are you at with this problem.. > > Unplug a few devices and you will have the opportunity to review the > devices probed in your machine (reboot). > > I've only removed the list of devices from GENERIC & LINT, not from the > conf/files and options. Hiding it basically. > > Nick > > On Mon, 19 Apr 1999, Amancio Hasty wrote: > > > Curious why is USB not ready for public consumption? > > Got a USB only system : keyboard + mouse working over here. > > > > > > > > > > > > -- > > > > Amancio Hasty > > hasty@star-gate.com > > > > > > > > -- > e-Mail: hibma@skylink.it > -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 14:13:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 198E914D11 for ; Mon, 19 Apr 1999 14:13:30 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it ([194.185.55.40]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA20764; Mon, 19 Apr 1999 23:12:25 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id XAA05307; Mon, 19 Apr 1999 23:04:28 +0200 (CEST) Date: Mon, 19 Apr 1999 23:04:28 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf LINT GENERIC In-Reply-To: <199904192052.NAA44061@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Currently we have the following: - working drivers for keyboards, mice, hubs - usable driver for USB Zip drive (Iomega, SCSI) (any coders/testers (the true combination) welcome) I am currently finishing the initial workings of the Zip driver and have been able to MSDOS format a disk and been able to read a hfs (iMac) floppy as well. But the driver panics the system when drive unplugged. Planned is: - rewrite of the uhub driver to completely follow newbus (up to now a mixed approach which fails at detach) - start working on 3COM modem support - start working on Ye-Data drive support - start working on Digi 2/4/8 serial port device support - start working on 3COM ISDN adapter support - start working on audio support and while doing this: - solidify the UHCI controller support - solidify the OHCI controller support - improve USBDI The ISDN TA, the Ye-Data drive and Digi serial port device have kindly been provided to me (have not yet arrived though) by the respective hardware vendors. Cherry has provided me with a keyboard (with internal bus powered hub). Anyone care to join? Pick up something fairly straightforward like the audio (Audiocontrol driver). Follow the specs and mail me your comments on the USBDI interface we use. A template driver is the ums mouse driver. Kind regards, Nick Hibma FreeBSD USB project n_hibma@freebsd.org http://www.etla.net/~n_hibma/usb/usb.pl http://www.usb.org/ P.S.: USBDI as in, our version of it. The people from the consortium kicked us out. On Mon, 19 Apr 1999, Amancio Hasty wrote: > > Redirected to -current... > > I seem to recollect that you were having problems in handling interrupts so > were are > you at with this problem.. > > > > > > Unplug a few devices and you will have the opportunity to review the > > devices probed in your machine (reboot). > > > > I've only removed the list of devices from GENERIC & LINT, not from the > > conf/files and options. Hiding it basically. > > > > Nick > > > > On Mon, 19 Apr 1999, Amancio Hasty wrote: > > > > > Curious why is USB not ready for public consumption? > > > Got a USB only system : keyboard + mouse working over here. > > > > > > > > > > > > > > > > > > -- > > > > > > Amancio Hasty > > > hasty@star-gate.com > > > > > > > > > > > > > -- > > e-Mail: hibma@skylink.it > > > > -- > > Amancio Hasty > hasty@star-gate.com > > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 14:24:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 5A71615208 for ; Mon, 19 Apr 1999 14:24:29 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id OAA03026; Mon, 19 Apr 1999 14:22:00 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904192122.OAA03026@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: current@FreeBSD.ORG Subject: USB Development In-reply-to: Your message of "Mon, 19 Apr 1999 23:04:28 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Apr 1999 14:22:00 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Insert your e-mail message in your web page under a section titled such as Project Status. What specifically is needed in the driver to unplug and plug a device? > > Currently we have the following: > > - working drivers for keyboards, mice, hubs > - usable driver for USB Zip drive (Iomega, SCSI) (any > coders/testers (the true combination) welcome) > > I am currently finishing the initial workings of the Zip driver and have > been able to MSDOS format a disk and been able to read a hfs (iMac) > floppy as well. But the driver panics the system when drive unplugged. > > Planned is: > > - rewrite of the uhub driver to completely follow newbus > (up to now a mixed approach which fails at detach) > - start working on 3COM modem support > - start working on Ye-Data drive support > - start working on Digi 2/4/8 serial port device support > - start working on 3COM ISDN adapter support > - start working on audio support > > and while doing this: > > - solidify the UHCI controller support > - solidify the OHCI controller support > - improve USBDI > > The ISDN TA, the Ye-Data drive and Digi serial port device have kindly > been provided to me (have not yet arrived though) by the respective > hardware vendors. Cherry has provided me with a keyboard (with internal > bus powered hub). > > Anyone care to join? Pick up something fairly straightforward like the > audio (Audiocontrol driver). Follow the specs and mail me your comments > on the USBDI interface we use. A template driver is the ums mouse > driver. > > Kind regards, > > Nick Hibma > FreeBSD USB project > n_hibma@freebsd.org > http://www.etla.net/~n_hibma/usb/usb.pl > http://www.usb.org/ > > P.S.: USBDI as in, our version of it. The people from the consortium > kicked us out. > > On Mon, 19 Apr 1999, Amancio Hasty wrote: > > > > > Redirected to -current... > > > > I seem to recollect that you were having problems in handling interrupts so > > were are > > you at with this problem.. > > > > > > > > > > Unplug a few devices and you will have the opportunity to review the > > > devices probed in your machine (reboot). > > > > > > I've only removed the list of devices from GENERIC & LINT, not from the > > > conf/files and options. Hiding it basically. > > > > > > Nick > > > > > > On Mon, 19 Apr 1999, Amancio Hasty wrote: > > > > > > > Curious why is USB not ready for public consumption? > > > > Got a USB only system : keyboard + mouse working over here. > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Amancio Hasty > > > > hasty@star-gate.com > > > > > > > > > > > > > > > > > > -- > > > e-Mail: hibma@skylink.it > > > > > > > -- > > > > Amancio Hasty > > hasty@star-gate.com > > > > > > > > -- > e-Mail: hibma@skylink.it > -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 14:33:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 886CE14F59 for ; Mon, 19 Apr 1999 14:33:24 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id RAA02712 for ; Mon, 19 Apr 1999 17:33:29 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Mon, 19 Apr 1999 17:33:28 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: x11amp 0.9beta1.1 for linux Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just in case anyone would like to know, I have gotten x11amp 0.9beta1.1 for linux working on my FreeBSD-CURRENT cvsupped as of last night. If anyone would like instructions on how I did this, please email me. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 14:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.7.39]) by hub.freebsd.org (Postfix) with SMTP id 0C56C155BC for ; Mon, 19 Apr 1999 14:34:58 -0700 (PDT) (envelope-from alexandr@mail.eecis.udel.edu) Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa05731; 19 Apr 1999 17:32 EDT To: current@freebsd.org Subject: Newbus and PCCARD Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Date: Mon, 19 Apr 1999 17:32:12 -0400 From: Jerry Alexandratos Message-ID: <199904191732.aa05731@mail.eecis.udel.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before I do a send-pr, I wanted to see if anyone else was having problems with newbus and pccardd. I've got a a 3COM/Megahertz 3CXM556 modem (sio1) and a Xircom 10/100 ethernet card (xe0). Doing a "make world" and then building a new kernel (with appropriate changes for newbus) renders the modem useless. Dmesg shows that only the xe driver is initialized. Thus, when pccardd goes to allocate resources to the modem it fails. Am I missing something, or is this something that has to be worked out in the newbus code? Thanks in advance... --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 14:37:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (Postfix) with ESMTP id 36D7F15208 for ; Mon, 19 Apr 1999 14:37:30 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: by ixion.honeywell.com (1.40.112.8/16.2) id AA025117659; Mon, 19 Apr 1999 16:34:19 -0500 Date: Mon, 19 Apr 1999 16:34:19 -0500 From: Shawn Leas To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: x11amp 0.9beta1.1 for linux Message-Id: <19990419163419.A2459@ixion.honeywell.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Kenneth Wayne Culver on Mon, Apr 19, 1999 at 05:33:28PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like that. Is it a port, or is it a linux compat thing? On Mon, Apr 19, 1999 at 05:33:28PM -0400, Kenneth Wayne Culver wrote: > just in case anyone would like to know, I have gotten x11amp 0.9beta1.1 > for linux working on my FreeBSD-CURRENT cvsupped as of last night. If > anyone would like instructions on how I did this, please email me. > > Kenneth Culver -- Shawn <=========== America Held Hostage ===========> Day 2280 for the poor and the middle class. Day 2299 for the rich and the dead. 642 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 14:45: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.eunet.ch (mail.eunet.ch [146.228.10.7]) by hub.freebsd.org (Postfix) with ESMTP id C7EA914C3E for ; Mon, 19 Apr 1999 14:45:01 -0700 (PDT) (envelope-from fjaccard@webshuttle.ch) Received: from wwwsw.webshuttle.ch (www.webshuttle.ch [146.228.6.1]) by mail.eunet.ch (8.9.1/1.34) via ESMTP id VAA12217 for ; Mon, 19 Apr 1999 21:42:34 GMT env-from (fjaccard@webshuttle.ch) Received: from uwieruowiuer (dyna-ls-47.dial.eunet.ch [193.72.6.207]) by wwwsw.webshuttle.ch (8.8.6/8.8.2) with ESMTP id XAA17749 for ; Mon, 19 Apr 1999 23:42:29 +0200 (MET DST) Message-Id: <4.2.0.32.19990419232836.00b4ef00@mail.urbanet.ch> X-Sender: fjaccard@pop.webshuttle.ch X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.32 (Beta) Date: Mon, 19 Apr 1999 23:40:34 +0200 To: current@freebsd.org From: Francois E Jaccard Subject: Problem upgrading 3.1R to 4.0-current Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have an Asus P2B-D with 2 PII/350, 128Mb Ram with FreeBSD 3.1R installed. I just added the SMP lines to the generic kernel and I am having constant reboots. I am trying to upgrade to 4.0-current and I updated my source tree tonight around 17:30 UTC but "make world" gives me errors, at different places each time it is run. I tried in single user, with the GENERIC kernel or with my SMP GENERIC (Generic with just the lines for SMP). Nothing is running on this machine. I also can't do a "config GENERIC": it gives "only isa's should be connected to nexus" for lime 129 and 134. Please help me upgrade to 4.0-current. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 14:48:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22]) by hub.freebsd.org (Postfix) with ESMTP id 2E7C114C3E for ; Mon, 19 Apr 1999 14:48:29 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-67-19.atl.bellsouth.net [209.214.67.19]) by mail2.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id RAA12695; Mon, 19 Apr 1999 17:46:02 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id RAA03765; Mon, 19 Apr 1999 17:46:31 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199904192146.RAA03765@bellsouth.net> To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: x11amp 0.9beta1.1 for linux In-reply-to: Your message of "Mon, 19 Apr 1999 17:33:28 EDT." Date: Mon, 19 Apr 1999 17:46:31 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > just in case anyone would like to know, I have gotten x11amp 0.9beta1.1 > for linux working on my FreeBSD-CURRENT cvsupped as of last night. If > anyone would like instructions on how I did this, please email me. Sure! Are you planning on updating the port? If not, I'll do the grunt work for you. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 14:54: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 7C8D414C3E for ; Mon, 19 Apr 1999 14:54:00 -0700 (PDT) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id XAA76680; Mon, 19 Apr 1999 23:51:08 +0200 (CEST) (envelope-from leif@neland.dk) Message-ID: <002101be8aae$c0b3bd20$0e00a8c0@swimsuit.internet.dk> From: "Leif Neland" To: "Kenneth Wayne Culver" , References: Subject: Re: x11amp 0.9beta1.1 for linux Date: Mon, 19 Apr 1999 23:51:05 +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.00.2314.1300 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just make a port :-) ----- Original Message ----- From: Kenneth Wayne Culver To: Sent: 19. april 1999 23:33 Subject: x11amp 0.9beta1.1 for linux > just in case anyone would like to know, I have gotten x11amp 0.9beta1.1 > for linux working on my FreeBSD-CURRENT cvsupped as of last night. If > anyone would like instructions on how I did this, please email me. > > Kenneth Culver > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 15:11:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 5C60114C3E for ; Mon, 19 Apr 1999 15:10:26 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id SAA02835 for ; Mon, 19 Apr 1999 18:10:39 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Mon, 19 Apr 1999 18:10:39 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: alright, x11amp instructions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG since I am inexperienced at creating ports, I'll just give instructions on how to get the latest linux x11amp to work. First, it won't work with voxware, only pcm or OSS. other than that, here are the instructions: Well, there isn't that much to updating the port. I guess the linux_lib port needs to be updated to include the linux versions of glib and gtk, and the x11amp port is just a straight rpm2targz of the rpms of x11amp's website. All I did was grabbed the latest linux_lib port, the x11amp 0.9 beta1.1.rpm file, and the latest gtk and glib files. I moved all the rpms to the /usr/compat/linux directory, and from there I just untarred and ungzipped them (after rpm2targz). That's all it took. I made a symlink from /usr/compat/linux/usr/X11R6/bin/x11amp to /usr/local/bin so I wouldn't have to change my path. It uses (obviously) the linux emulation because I took binary rpms for everything. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 15:13:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id E7960155EE for ; Mon, 19 Apr 1999 15:13:31 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it ([194.185.55.40]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id AAA21762; Tue, 20 Apr 1999 00:12:24 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id AAA05502; Tue, 20 Apr 1999 00:08:31 +0200 (CEST) Date: Tue, 20 Apr 1999 00:08:31 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: USB Development In-Reply-To: <199904192122.OAA03026@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999, Amancio Hasty wrote: > Insert your e-mail message in your web page under a section titled such as > Project Status. Good idea. > What specifically is needed in the driver to unplug and plug a device? attach is straightforward. detach requires: - disconnect function to handle the fact that the device does no longer respond (intr context) - detach function to delete the device and all its resources (normal context) - driver unload (detach all drivers) Currently the problem lies in the fact that free()/malloc() is called from intr context, resources are completely freed, ongoing transfers are cleaned away, etc. Nick > > > > > > Currently we have the following: > > > > - working drivers for keyboards, mice, hubs > > - usable driver for USB Zip drive (Iomega, SCSI) (any > > coders/testers (the true combination) welcome) > > > > I am currently finishing the initial workings of the Zip driver and have > > been able to MSDOS format a disk and been able to read a hfs (iMac) > > floppy as well. But the driver panics the system when drive unplugged. > > > > Planned is: > > > > - rewrite of the uhub driver to completely follow newbus > > (up to now a mixed approach which fails at detach) > > - start working on 3COM modem support > > - start working on Ye-Data drive support > > - start working on Digi 2/4/8 serial port device support > > - start working on 3COM ISDN adapter support > > - start working on audio support > > > > and while doing this: > > > > - solidify the UHCI controller support > > - solidify the OHCI controller support > > - improve USBDI > > > > The ISDN TA, the Ye-Data drive and Digi serial port device have kindly > > been provided to me (have not yet arrived though) by the respective > > hardware vendors. Cherry has provided me with a keyboard (with internal > > bus powered hub). > > > > Anyone care to join? Pick up something fairly straightforward like the > > audio (Audiocontrol driver). Follow the specs and mail me your comments > > on the USBDI interface we use. A template driver is the ums mouse > > driver. > > > > Kind regards, > > > > Nick Hibma > > FreeBSD USB project > > n_hibma@freebsd.org > > http://www.etla.net/~n_hibma/usb/usb.pl > > http://www.usb.org/ > > > > P.S.: USBDI as in, our version of it. The people from the consortium > > kicked us out. > > > > On Mon, 19 Apr 1999, Amancio Hasty wrote: > > > > > > > > Redirected to -current... > > > > > > I seem to recollect that you were having problems in handling interrupts so > > > were are > > > you at with this problem.. > > > > > > > > > > > > > > Unplug a few devices and you will have the opportunity to review the > > > > devices probed in your machine (reboot). > > > > > > > > I've only removed the list of devices from GENERIC & LINT, not from the > > > > conf/files and options. Hiding it basically. > > > > > > > > Nick > > > > > > > > On Mon, 19 Apr 1999, Amancio Hasty wrote: > > > > > > > > > Curious why is USB not ready for public consumption? > > > > > Got a USB only system : keyboard + mouse working over here. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Amancio Hasty > > > > > hasty@star-gate.com > > > > > > > > > > > > > > > > > > > > > > > -- > > > > e-Mail: hibma@skylink.it > > > > > > > > > > -- > > > > > > Amancio Hasty > > > hasty@star-gate.com > > > > > > > > > > > > > -- > > e-Mail: hibma@skylink.it > > > > -- > > Amancio Hasty > hasty@star-gate.com > > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 16: 1:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from stevenson.cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A3DC1563D; Mon, 19 Apr 1999 16:01:41 -0700 (PDT) (envelope-from richard@cogsci.ed.ac.uk) Received: from doyle.cogsci.ed.ac.uk (richard@doyle [129.215.110.29]) by stevenson.cogsci.ed.ac.uk (8.8.7/8.8.7) with SMTP id XAA25471; Mon, 19 Apr 1999 23:59:11 +0100 (BST) Date: Mon, 19 Apr 1999 23:59:11 +0100 Message-Id: <16533.199904192259@doyle.cogsci.ed.ac.uk> From: Richard Tobin Subject: RE: lnc0: broke for us between 3.1 and 4.0? To: paul@originative.co.uk, freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: paul@originative.co.uk's message of Sun, 18 Apr 1999 02:18:02 +0100 Organization: just say no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > lnc0: Memory allocated above 16Mb limit > I've just committed a fix for this. It was caused by the change to the way > vm_page.c allocates memory Is this fix going into stable? (I'm a little surprised that such a change was considered appropriate for the stable branch in the first place.) -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 16:21:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id E6EA514C59; Mon, 19 Apr 1999 16:21:06 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id <2RSVN4Z5>; Tue, 20 Apr 1999 00:16:43 +0100 Message-ID: From: paul@originative.co.uk To: richard@cogsci.ed.ac.uk, paul@originative.co.uk, freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: RE: lnc0: broke for us between 3.1 and 4.0? Date: Tue, 20 Apr 1999 00:16:37 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Richard Tobin [mailto:richard@cogsci.ed.ac.uk] > Sent: 19 April 1999 23:59 > To: paul@originative.co.uk; freebsd-current@FreeBSD.ORG; > freebsd-stable@FreeBSD.ORG > Subject: RE: lnc0: broke for us between 3.1 and 4.0? > > > > > lnc0: Memory allocated above 16Mb limit > > > I've just committed a fix for this. It was caused by the > change to the way > > vm_page.c allocates memory > > Is this fix going into stable? (I'm a little surprised that such a > change was considered appropriate for the stable branch in the first > place.) I didn't think the memory allocation change was in stable but I may merge the lnc changes back into -stable anyway since it's a cleaner way of doing things. I've got some other lnc problems to fix first though. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 17:49: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 86EB714D1A for ; Mon, 19 Apr 1999 17:48:54 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA01550; Tue, 20 Apr 1999 10:11:45 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 20 Apr 1999 10:18:47 +0930 (CST) From: "Daniel O'Connor" To: Kenneth Wayne Culver Subject: RE: alright, x11amp instructions Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Apr-99 Kenneth Wayne Culver wrote: > since I am inexperienced at creating ports, I'll just give instructions on > how to get the latest linux x11amp to work. First, it won't work with > voxware, only pcm or OSS. other than that, here are the instructions: What does it use that pcm and OSS have that Voxware doesn't? Hmm.. there is a hack to use esound with X11amp - that could alleviate the Voxware problem :) --- 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-current" in the body of the message From owner-freebsd-current Mon Apr 19 18:49:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from vanessa.eliuk.org (sec4d38.dial.uniserve.ca [204.244.165.197]) by hub.freebsd.org (Postfix) with ESMTP id 8318B155F3 for ; Mon, 19 Apr 1999 18:49:21 -0700 (PDT) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.3/8.9.3) with ESMTP id SAA01106; Mon, 19 Apr 1999 18:46:48 -0700 (PDT) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 19 Apr 1999 18:46:17 -0700 (PDT) From: "Kevin G. Eliuk" To: Blaz Zupan Cc: freebsd-current@freebsd.org Subject: Re: PCI VGA card becomes ISA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999, Blaz Zupan wrote: > I noticed that after the latest round of new-bus changes, my PCI VGA card > is now recognized as a generic ISA card by the kernel. I don't see any ill > effects from this, but the new-bus developers may want to know, in case it > breaks something else. > > The VGA card is a S3 Trio64V+. Here's the dmesg output I get. I don't have > an old dmesg output before the changes, but the card was recognized by > its name and it was using IRQ 9. > > atkbdc0: at port 0x60 on isa0 > atkbd0: on atkbdc0 > atkbd0: interrupting at irq 1 > vga0: on isa0 Same here with a "Generic S3 ViRGE" pci card. Apr 15 13:11:59 vanessa /kernel: vga0: \ rev 0x06 int a irq 0 on pci0.3.0 Apr 15 13:11:59 vanessa /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000\ msize 131072 on isa Apr 15 16:22:59 vanessa /kernel: vga0: \ rev 0x06 int a irq 0 on pci0.3.0 Apr 15 16:22:59 vanessa /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000\ msize 131072 on isa Apr 16 16:38:14 vanessa /kernel: vga0: \ rev 0x06 int a irq 0 on pci0.3.0 Apr 16 16:38:14 vanessa /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000\ msize 131072 on isa Apr 17 18:22:32 vanessa /kernel: vga0: on isa0 Apr 17 18:22:32 vanessa /kernel: fb0: vga0, vga, type:VGA (5), flags:0x700ff Apr 19 16:22:34 vanessa /kernel: vga0: on isa0 -- Regards, Kevin G. Eliuk Box 67, Granthams Landing, BC VON 1X0 (604)886-4040 Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 20: 5: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 037CA15661 for ; Mon, 19 Apr 1999 20:05:04 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id TAA15851; Mon, 19 Apr 1999 19:59:04 -0700 (PDT) Date: Mon, 19 Apr 1999 19:59:03 -0700 (PDT) From: Julian Elischer To: Tomoaki NISHIYAMA Cc: jkh@zippy.cdrom.com, y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: HEADS UP!!!! Important instructions for -current users! In-Reply-To: <19990419183445N.tomoaki@moss.nibb.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG from my understanding, the biggest difference is that New-bus is being designed to eventually delegate 'config' to a very minor role where newconfig (as it's name suggests' maintains 'config' a s a major component.. It has been a long standing goal of FreeBSD to make the system as dynamic as possible. My personal goal is to see it more dynamically configurable than NT with all it's DLLs. julian On Mon, 19 Apr 1999, Tomoaki NISHIYAMA wrote: > jkh> > I don't go to new-bus, this direction is disunion of BSDs. It is > jkh> > bad decision. > jkh> > jkh> I'm sorry that you feel this way, but I can only re-state that better > jkh> communication could have prevented this in the first place and hope > jkh> that you've learned your own lessons from this exercise. If you > jkh> haven't, then a good opportunity for learning has simply been wasted. > > One problem on the decision is that it was not based > on a judge that new-bus is technically or philosophically > superior to newconfig framework but you stated > jkh> the difference with new-bus being > jkh> that we were working just that much more closely with Doug Rabson (and > jkh> the others helping him) and had already used the new-bus stuff for > jkh> FreeBSD/alpha. > > Nakagawa would not be so upset if you could convince him > that new-bus were superior. > > -------- > Tomoaki Nishiyama > e-mail:tomoaki@biol.s.u-tokyo.ac.jp > Department of Biological Sciences, > Graduate School of Science, The University of Tokyo > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 20:41:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from pyrl.eye (ppp-233.centerplacenet.com [208.29.63.233]) by hub.freebsd.org (Postfix) with ESMTP id CEE6315335; Mon, 19 Apr 1999 20:41:15 -0700 (PDT) (envelope-from ortmann@sparc.isl.net) Received: (from ortmann@localhost) by pyrl.eye (8.9.3/8.9.1) id WAA14595; Mon, 19 Apr 1999 22:35:10 -0500 (CDT) (envelope-from ortmann) From: Daniel Ortmann Message-Id: <199904200335.WAA14595@pyrl.eye> Subject: Re: ATTENTION PLEASE: g77 in base system. In-Reply-To: <19990409112852.A14614@symbion.srrc.usda.gov> from Glenn Johnson at "Apr 9, 1999 11:28:52 am" To: gjohnson@nola.srrc.usda.gov (Glenn Johnson) Date: Mon, 19 Apr 1999 22:35:09 -0500 (CDT) Cc: reg@shale.csir.co.za, scrappy@hub.org, handy@lambic.physics.montana.edu, des@flood.ping.uio.no, obrien@NUXI.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Apr 09, 1999 at 03:52:58PM +0200, Jeremy Lea wrote: ... > Many people don't seem to understand that FreeBSD can be used for > workstations as well as servers and Fortran is *essential* on a > scientific/engineering workstation. ... Absolutely correct. Some up-and-coming IBM simulation ports require Fortran categorically. It's tough answering questions like "FreeB... what? Is that like Linux?" Without a STANDARD system Fortran compiler an operating system is unlikely to be taken seriously by ANY large engineering company. We could, however, do without "fortune". :-) -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #D E315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortmann@isl.net ortmann@us.ibm.com -- "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 20:58:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id C244B14F66 for ; Mon, 19 Apr 1999 20:58:18 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id MAA00893; Tue, 20 Apr 1999 12:55:48 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: current@FreeBSD.ORG Cc: jkh@zippy.cdrom.com, y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, julian@whistle.com Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: HEADS UP!!!! Important instructions for -current users! From: Tomoaki NISHIYAMA In-Reply-To: References: X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990420125547S.tomoaki@moss.nibb.ac.jp> Date: Tue, 20 Apr 1999 12:55:47 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 43 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Julian Elischer Subject: Re: HEADS UP!!!! Important instructions for -current users! Date: Mon, 19 Apr 1999 19:59:03 -0700 (PDT) Message-ID: julian> from my understanding, the biggest difference is that New-bus julian> is being designed to eventually delegate 'config' to a very minor role julian> where newconfig (as it's name suggests' maintains 'config' a s a major julian> component. You should not forget that newconfig is a different thing from the old config. It will remove the illness of the old config. julian> It has been a long standing goal of FreeBSD to make the system julian> as dynamic as possible. My personal goal is to see it more dynamically julian> configurable than NT with all it's DLLs. By now, newconfig people decided to continue its development until its dynamic configuration stuff works under FreeBSD, despite the decision to merge newbus into the main CVS repository You can see the implementation of dynamic configuration under newconfig, which means that you have one more chance to integrate newconfig stuff. I hope you have the flexibility to think seriously the integration of newconfig. Currently proposed schedule is on April 21 import sys4c990410 syncing and test around April 28 import PRE_NEWBUS Achievement is now announced in newconfig mailing list (newconfig@jp.freebsd.org, controlled by majordomo@jp.freebsd.org). Although most discussion are done in Japanese in newconfig-jp mailing list but any comment, suggestion, or question in English to newconfig@jp.freebsd.org will be appreciated. To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 21:49: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3B5D614C29 for ; Mon, 19 Apr 1999 21:49:07 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA08981; Mon, 19 Apr 1999 21:46:30 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Tomoaki NISHIYAMA Cc: current@FreeBSD.ORG, y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, julian@whistle.com Subject: Re: HEADS UP!!!! Important instructions for -current users! In-reply-to: Your message of "Tue, 20 Apr 1999 12:55:47 +0900." <19990420125547S.tomoaki@moss.nibb.ac.jp> Date: Mon, 19 Apr 1999 21:46:30 -0700 Message-ID: <8979.924583590@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > integrate newconfig stuff. I hope you have the flexibility > to think seriously the integration of newconfig. As long as it doesn't significantly impact the work already in progress, I think the flexibility is certainly there. > To make the communication more close, it is possible to post > the achievements and plans to hackers or current. Do you think > this appropriate? I think it's more than appropriate, it's *mandatory* if you wish to solve the communication problem. Posting regular updates on your progress on -hackers or -current (depending on applicability) is strongly encouraged. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 19 21:58:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id B0D5614C29 for ; Mon, 19 Apr 1999 21:58:46 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA21878; Tue, 20 Apr 1999 14:24:49 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA45364; Tue, 20 Apr 1999 14:24:47 +0930 (CST) Message-ID: <19990420142447.V40482@lemis.com> Date: Tue, 20 Apr 1999 14:24:47 +0930 From: Greg Lehey To: "Jordan K. Hubbard" , Tomoaki NISHIYAMA Cc: current@FreeBSD.ORG, y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, julian@whistle.com Subject: Peer review (was: HEADS UP!!!! Important instructions for -current users!) References: <19990420125547S.tomoaki@moss.nibb.ac.jp> <8979.924583590@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <8979.924583590@zippy.cdrom.com>; from Jordan K. Hubbard on Mon, Apr 19, 1999 at 09:46:30PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 19 April 1999 at 21:46:30 -0700, Jordan K. Hubbard wrote: >> integrate newconfig stuff. I hope you have the flexibility >> to think seriously the integration of newconfig. > > As long as it doesn't significantly impact the work already in > progress, I think the flexibility is certainly there. > >> To make the communication more close, it is possible to post >> the achievements and plans to hackers or current. Do you think >> this appropriate? > > I think it's more than appropriate, it's *mandatory* if you wish to > solve the communication problem. Posting regular updates on your > progress on -hackers or -current (depending on applicability) is > strongly encouraged. But as we have seen, posting on -hackers doesn't guarantee that anybody of any importance will see it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 1:13:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 308D414F46 for ; Tue, 20 Apr 1999 01:13:42 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA94478; Tue, 20 Apr 1999 09:14:32 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 09:14:32 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: Takanori Watanabe , freebsd-current@freebsd.org Subject: Re: newbus and modem(s) In-Reply-To: <19990419124505.62D951F5E@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999, Peter Wemm wrote: > > > > > > I don't think I understand. The DRIVER_MODULE declaration goes in the > > > downstream driver, not the upstream bus. The bus doesn't need any > > > knowledge of what drivers might be attached to it. > > > > Well, what about the i386 nexus? It specifically creates connection points > > for apm, npx, eisa, isa, and pci as children. > > > > However, pci devices don't do this to attach to their parent. I am > > obviously missing something. :-) > > Never mind, I understand now. :-) > > For the benefit of the 'cc' list, and to check my understanding, let me run > through it.. > > The parents pick up the children in one of two ways. For a 'smart' bus, > like pci, usb, eisa, etc, the bus probes itself and adds an "unidentified" > child (NULL name, -1 unit) with the known ID. The bus mechanism then uses > this to poll the drivers to see which one(s) want to claim that ID. It > knows who the children are because of the DECLARE_MODULE() statement. This > means that a "smart" (or self identifying) bus doesn't need anything more > to manage the relationship. > > On the other hand, there's isa, which is quite dumb. In this case, the bus > looks up it's "hint" list and specifically adds the requested children from > those hints, and using the supplied irq, port, etc values from the hints. > The drivers then use that data to probe for the existance of the device. > > The nexus is a little bit different.. It doesn't have things to > specifically look for, so it adds the children manually. It could have > used the resource database to find the requested things to attach to the > nexus in pretty much the same way as the isa bus does. > > And then there's the old isa drivers... They attach themselves to the isa > parent device class on the fly, there is no DECLARE_MODULE() table for all > the old isa (and perhaps PCI too) drivers. > > Doug, is that right so far? :-) Perfectly. > > Now what I'm curious about is how to handle the nexus and isa/eisa better > so they don't need to explicitly name the children. On one hand it could > look at the hints table to see all the 'at nexus?' declarations, but I > think it might be better to go for a hunt to locate all the children it can > find. One way to do this might be to simply add a heap of "unidentified" > devices and let the bus mechanism find all the devices that are children > and let them probe themselves while ignoring the fake device id's. Perhaps > this could change the probe order enough so that isa and eisa won't be > attached until after pci has been recursively probed. I'm not sure how this would work. At the nexus, I think it has to know what the possibly attached devices are (or at least a list of names). The NetBSD code does a simple probe (e.g. checking for pci config method or looking for the mainboard ID) before adding devices. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 1:28:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id A8D8015237 for ; Tue, 20 Apr 1999 01:28:15 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id KAA21727; Tue, 20 Apr 1999 10:29:29 +0200 (MET DST) Date: Tue, 20 Apr 1999 10:25:39 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Tomoaki NISHIYAMA Cc: current@FreeBSD.ORG, jkh@zippy.cdrom.com, y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, julian@whistle.com Subject: Re: HEADS UP!!!! Important instructions for -current users! In-Reply-To: <19990420125547S.tomoaki@moss.nibb.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To make the communication more close, it is possible to post > the achievements and plans to hackers or current. Do you think > this appropriate? Yes. Nick FreeBSD USB Project. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 1:47:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C45FE14CD4 for ; Tue, 20 Apr 1999 01:47:07 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA94897; Tue, 20 Apr 1999 09:47:58 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 09:47:58 +0100 (BST) From: Doug Rabson To: Luoqi Chen Cc: jhay@mikom.csir.co.za, peter@netplex.com.au, current@freebsd.org Subject: Re: newbus and isa auto irq In-Reply-To: <199904191821.OAA05777@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999, Luoqi Chen wrote: > > This is not happening for the maddr stuff. > > I suspect this would do better: > > > > if (portsize > 0) > > isa_set_portsize(dev, portsize); > > if (dvp->id_iobase >= 0) > > isa_set_port(dev, dvp->id_iobase); > > if (dvp->id_irq != 0) > > isa_set_irq(dev, ffs(dvp->id_irq) - 1); > > if (dvp->id_drq != -1) > > isa_set_drq(dev, dvp->id_drq); > > if (dvp->id_maddr != 0) > > isa_set_maddr(dev, > > (int) dvp->id_maddr - KERNBASE); > > if (dvp->id_msize != 0) > > isa_set_msize(dev, dvp->id_msize); > > I'm not sure about the "nothing" value for id_drq though, it might need to > > be 0 - but that's a valid dma channel. > > > > IMHO, isa_release_resources() clearing of the default values for the probe > > hints is a timebomb... I thought about adding a seperate store for the > > "hint" values rather than using the id_foo[0] entries, and leaving the > > tracked resource entries for alloc/free without risking the hints. > > > > Cheers, > > -Peter > > > Off the topic, I think we should replace (dvp->id_maddr - KERNBASE) with > kvtop(dvp->id_maddr), too much assumption about vm layout... I agree. I think your fix for the irq problem is the correct one too. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 1:48:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id A19371577A for ; Tue, 20 Apr 1999 01:48:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA94912; Tue, 20 Apr 1999 09:51:23 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 09:51:23 +0100 (BST) From: Doug Rabson To: Blaz Zupan Cc: freebsd-current@freebsd.org Subject: Re: PCI VGA card becomes ISA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Apr 1999, Blaz Zupan wrote: > I noticed that after the latest round of new-bus changes, my PCI VGA card > is now recognized as a generic ISA card by the kernel. I don't see any ill > effects from this, but the new-bus developers may want to know, in case it > breaks something else. > > The VGA card is a S3 Trio64V+. Here's the dmesg output I get. I don't have > an old dmesg output before the changes, but the card was recognized by > its name and it was using IRQ 9. I know about this. The vga probe is stubbed out in pci at the moment. The reason is that syscons requires a vga0 device on isa but pci already allocated vga0 and things go downhill from there... Its harmless and it should go away soon if we can reorganise syscons' vga driver slightly. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 1:52:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 238CB14CD4 for ; Tue, 20 Apr 1999 01:52:46 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA94916; Tue, 20 Apr 1999 09:54:40 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 09:54:40 +0100 (BST) From: Doug Rabson To: Greg Lehey Cc: "Jordan K. Hubbard" , Tomoaki NISHIYAMA , current@freebsd.org, y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, julian@whistle.com Subject: Re: Peer review (was: HEADS UP!!!! Important instructions for -current users!) In-Reply-To: <19990420142447.V40482@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Apr 1999, Greg Lehey wrote: > On Monday, 19 April 1999 at 21:46:30 -0700, Jordan K. Hubbard wrote: > >> integrate newconfig stuff. I hope you have the flexibility > >> to think seriously the integration of newconfig. > > > > As long as it doesn't significantly impact the work already in > > progress, I think the flexibility is certainly there. > > > >> To make the communication more close, it is possible to post > >> the achievements and plans to hackers or current. Do you think > >> this appropriate? > > > > I think it's more than appropriate, it's *mandatory* if you wish to > > solve the communication problem. Posting regular updates on your > > progress on -hackers or -current (depending on applicability) is > > strongly encouraged. > > But as we have seen, posting on -hackers doesn't guarantee that > anybody of any importance will see it. Possibly -current is better for ongoing development reports. I read both :-) -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 2: 2: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 0732B14F44 for ; Tue, 20 Apr 1999 02:01:58 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id LAA23460; Tue, 20 Apr 1999 11:02:55 +0200 (MET DST) Date: Tue, 20 Apr 1999 10:59:05 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Greg Lehey , "Jordan K. Hubbard" , Tomoaki NISHIYAMA , current@FreeBSD.ORG, y-nakaga@nwsl.mesh.ad.jp, imp@harmony.village.org, peter@netplex.com.au, julian@whistle.com Subject: Re: Peer review (was: HEADS UP!!!! Important instructions for -current users!) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I think it's more than appropriate, it's *mandatory* if you wish to > > > solve the communication problem. Posting regular updates on your > > > progress on -hackers or -current (depending on applicability) is > > > strongly encouraged. > > > > But as we have seen, posting on -hackers doesn't guarantee that > > anybody of any importance will see it. > > Possibly -current is better for ongoing development reports. I read both > :-) Which means that someone will crosspost it if necessary... Post and forget. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 4:51:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 203A314FE0 for ; Tue, 20 Apr 1999 04:51:20 -0700 (PDT) (envelope-from ian@apdata.com.au) Received: from apdata.com.au (localhost [127.0.0.1]) by rose.niw.com.au (Postfix) with ESMTP id 1F346A3203; Tue, 20 Apr 1999 21:18:53 +0930 (CST) Message-ID: <371C69A5.7E06D18C@apdata.com.au> Date: Tue, 20 Apr 1999 21:18:53 +0930 From: Ian West Organization: Applied Data Control X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: current@FreeBSD.ORG Subject: IPFW as built in kernel feature seems broken. References: <19990416213043.95C7B1F69@spinner.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, since rougly the time the recent changes were commited, I have been unable to compile a kernel with the IPFW funtionality build in. It still works as an KLD, but I would prefer not to run it this way. (It bothers me that if something caused it to be unloaded, or to fail to load, the machine could and would quite cheerfully pass everything.) Is this a transient thing, or is this a permanent change ? I have cvsupped and rebuilt quite a few times, the last only about 30 minutes ago, and it still appears to be the same. Thankyou for any feeback you can give me on this. On a brighter note, my machine is running fine with a fresh kernel, dual PII-350, vr0, fxp0 lan cards, bt848 video capture card and matrox millenium II agp card. No problems at all. (Other than the IPFW thing) Sorry if this has nothing to do with these changes, I did post a query a couple of days back, but there has been no response to this. Thankyou. Regards, Ian West. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 4:56:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.te.fcu.edu.tw (dns.te.fcu.edu.tw [140.134.68.79]) by hub.freebsd.org (Postfix) with ESMTP id 7EF401570D for ; Tue, 20 Apr 1999 04:53:53 -0700 (PDT) (envelope-from william@dns.te.fcu.edu.tw) Received: (from william@localhost) by dns.te.fcu.edu.tw (8.9.3/8.9.3) id TAA69628 for freebsd-current@freebsd.org; Tue, 20 Apr 1999 19:51:35 +0800 (CST) Date: Tue, 20 Apr 1999 19:51:35 +0800 From: William Liao To: freebsd-current@freebsd.org Subject: Having trouble with the new ATAPI driver Message-ID: <19990420195135.A69626@tale.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I did a CVSUP and make world at 4/15, then I decided to try the new ATAPI driver on my box. So I made some necessary changes to my kernel config and made a new kernel. But after boot, it always hangs on mounting disks. The message is: swapon: /dev/wd0s1b: Device not configured Then I tried to boot into single user mode and mount the slices manually. Unfortunately, same thing happened again when I tried to mount my /home, /var, etc. Mount replied: /dev/wd2s1e: Device not configured. Did I miss anything?... Thanks for your help. FYI, my BSD box mixes using SCSI and IDE disks, the /kernel and main system files are all on the old 1G SCSI disk. Oh yes, I forgot to comment out the old wd driver at first time, so the boot made some corrupt to the file system, will that hurt?.. (Of course, I fscked) Following is my dmesg output, kernel config, and fstab. ======= dmesg ======= Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Apr 19 15:42:08 CST 1999 root@dns.te.fcu.edu.tw:/usr/src/sys/compile/LEMON Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 100663296 (98304K bytes) avail memory = 95027200 (92800K bytes) Preloaded elf kernel "kernel.ata" at 0xc02b3000. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ata-pci0: rev 0x01 on pci0.7.1 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip2: rev 0x01 on pci0.7.3 vga0: rev 0x00 int a irq 4 on pci0.11.0 ahc0: rev 0x00 int a irq 9 on pci0.13.0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x08 int a irq 10 on pci0.15.0 fxp0: Ethernet address 00:90:27:57:c6:34 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <8 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 8250 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ata-isa1: already registered as ata0 ata1 not found at 0x1f0 ata-isa2: already registered as ata1 ata2 not found at 0x170 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 20 packets/entry ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-3 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata0: slave: settting up WDMA2 mode on PIIX3/4 chip OK ad1: ATA-? disk at ata0 as slave ad1: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=-1 ad1: 16 secs/int, 0 depth queue, DMA mode ata1: master: settting up WDMA2 mode on PIIX3/4 chip OK ad2: ATA-? disk at ata1 as master ad2: 519MB (1064448 sectors), 1056 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=-1 ad2: 8 secs/int, 0 depth queue, DMA mode afd0: rewriteable drive at ata1 as slave afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: Unknown media (0x0) Waiting 3 seconds for SCSI devices to settle changing root deviceda0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 1041MB (2131992 512 byte sectors: 255H 63S/T 132C) to da0s2a cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present ============== kernel config ============== # # LINT -- config file for checking all the sources, tries to pull in # as much of the source tree as it can. # # $Id: LINT,v 1.501 1998/11/06 20:32:22 msmith Exp $ # # NB: You probably don't want to try running a kernel built from this # file. Instead, you should start from GENERIC, and add options from # this file as required. # # # This directive is mandatory; it defines the architecture to be # configured for; in this case, the 386 family based IBM-PC and # compatibles. # machine "i386" ident LEMON maxusers 32 options FAILSAFE config kernel root on da0 #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" # aka Pentium(tm) cpu "I686_CPU" # aka Pentium Pro(tm) options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options "VM86" #options DDB #options DDB_UNATTENDED #options GDB_REMOTE_CHAT #options KTRACE #kernel tracing #options DIAGNOSTIC options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options "IPFIREWALL_VERBOSE_LIMIT=20" #limit verbosity options IPDIVERT #divert sockets options FFS #Fast filesystem options NFS #Network File System options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options NFS_ROOT #NFS usable as root device options SOFTUPDATES options QUOTA #enable disk quotas #options CODA #CODA filesystem. #pseudo-device vcoda 4 #coda minicache <-> venus comm. controller scbus0 #base SCSI code device da0 #SCSI direct access devices (aka disks) device cd0 #SCSI CD-ROMs #device pass0 #CAM passthrough driver pseudo-device pty 64 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's # Size of the kernel message buffer. Should be N * pagesize. options "MSGBUF_SIZE=40960" controller isa0 options "AUTO_EOI_1" # options "MAXMEM=(96*1024)" controller pnp0 controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 #options XSERVER # support for running an X server. device vga0 at isa? port ? conflicts device sc0 at isa? tty pseudo-device splash options MAXCONS=8 # number of virtual consoles device npx0 at isa? port IO_NPX iosiz 0x0 flags 0x0 irq 13 device apm0 at isa? disable flags 0x31 # Advanced Power Management #controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ff8004 #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x00ff8004 #disk wd2 at wdc1 drive 0 #device wfd0 controller ata0 device atadisk0 device atapifd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 controller ppbus0 device lpt0 at ppbus? device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 controller pci0 controller ahc0 options AHC_ALLOW_MEMIO options SCSI_DELAY=3000 device fxp0 #options "NSFBUFS=1024" ========== fstab ========== # Device Mountpoint FStype Options Dump Pass# /dev/wd0s1b none swap sw 0 0 /dev/wd2s1b none swap sw 0 0 /dev/wd1s1b none swap sw 0 0 /dev/da0s2a / ufs rw 1 1 /dev/wd0s1h /ftp ufs rw,noatime 1 1 /dev/wd2s1e /home ufs rw 1 1 /dev/da0s2e /usr ufs rw 1 1 /dev/wd0s1e /usr/local/news ufs rw,noatime 1 1 /dev/wd0s1g /usr/obj ufs rw 1 1 /dev/wd1s1e /usr/local/www ufs rw 0 1 1 /dev/da0s2f /usr/src ufs rw 1 1 /dev/wd0s1f /var ufs rw 1 1 /dev/wd1s1f /bak ufs rw,noatime 0 1 proc /proc procfs rw 0 0 /dev/cd0a /cdrom cd9660 ro,noauto 0 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 8:30:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3895D14F71 for ; Tue, 20 Apr 1999 08:30:54 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA62800; Tue, 20 Apr 1999 09:28:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA03027; Tue, 20 Apr 1999 09:27:56 -0600 (MDT) Message-Id: <199904201527.JAA03027@harmony.village.org> To: Tomoaki NISHIYAMA Subject: Re: HEADS UP!!!! Important instructions for -current users! Cc: current@FreeBSD.ORG, newconfig@jp.freebsd.org In-reply-to: Your message of "Tue, 20 Apr 1999 12:55:47 +0900." <19990420125547S.tomoaki@moss.nibb.ac.jp> References: <19990420125547S.tomoaki@moss.nibb.ac.jp> Date: Tue, 20 Apr 1999 09:27:56 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for the update on progress of new config, Nishiyama-san. Are snapshots of the new config work available to members outside the development team? If so, can you post a URL pointing to them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 8:31:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from chain.freebsd.os.org.za (chain.freebsd.os.org.za [196.7.74.174]) by hub.freebsd.org (Postfix) with ESMTP id AC1AC14E04 for ; Tue, 20 Apr 1999 08:30:18 -0700 (PDT) (envelope-from khetan@chain.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.9.3+3.2W/8.9.3) with ESMTP id RAA03402; Tue, 20 Apr 1999 17:26:24 +0200 (SAST) (envelope-from khetan@chain.freebsd.os.org.za) Date: Tue, 20 Apr 1999 17:26:23 +0200 (SAST) From: Khetan Gajjar Reply-To: Khetan Gajjar To: Doug Rabson Cc: freebsd-current@FreeBSD.ORG Subject: Re: PCI VGA card becomes ISA In-Reply-To: Message-ID: X-Mobile: +27 82 9907663 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Around Today, "Doug Rabson" wrote : DR> Its harmless and it should go away soon if we can reorganise syscons' vga DR> driver slightly. I'm seeing this as well, but as you've said, it's harmless. What I am "concerned" about is from sources last night, the error haveseen_isadev() called - FIXME! after the isa0 bus has been probed, and something I haven't seen before : (cd1:aha0:0:6:0): CCB 0xc51952e0 - timed out indicating a problem with my Yamaha CD-RW. Is this something serious ? As an aside, I'm trying Soren's ATA code, and it combined with the new-bus changes (neither of which I was using before) has made a dramatic difference speed-wise (or maybe it's just a placebo effect). Nice work :) Dmesg below. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Apr 20 13:00:36 SAST 1999 khetan@chain.freebsd.os.org.za:/usr/src/sys/compile/CHAIN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200455994 Hz CPU: Pentium/P54C (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 100663296 (98304K bytes) avail memory = 94699520 (92480K bytes) Preloaded elf kernel "kernel" at 0xc02d9000. ccd0-1: Concatenated disk drivers Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 ata0: at device 0.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 isab0: at device 1.0 on pci0 pcib1: at device 2.0 on pci0 pci1: on pcib1 de0: at device 11.0 on pci0 de0: interrupting at irq 5 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:f9:2f:c8 isa0: on motherboard haveseen_isadev() called - FIXME! aha0 at port 0x330-0x333 irq 11 drq 6 on isa0 aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs aha0: interrupting at irq 11 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model IntelliMouse, device ID 3 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0 at port 0x378 irq 7 on isa0 ppc0: Winbond chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ppc0: interrupting at irq 7 de0: enabling 10baseT port Intel Pentium detected, installing workaround for F00F bug ata0: master: settting up generic WDMA2 mode OK ad0: ATA-? disk at ata0 as master ad0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, DMA mode ata0: slave: settting up generic WDMA2 mode OK ad1: ATA-? disk at ata0 as slave ad1: 1039MB (2128896 sectors), 2112 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=-1 ad1: 8 secs/int, 0 depth queue, DMA mode ata1: master: settting up generic WDMA2 mode OK ad2: ATA-? disk at ata1 as master ad2: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=-1 ad2: 16 secs/int, 0 depth queue, DMA mode Waiting 15 seconds for SCSI devices to settle changing root device to wd1s1a da0 at aha0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device aha0: ahafetchtransinfo - Inquire Setup Info Failed da0: 3.300MB/s transfers da0: 516MB (1057616 512 byte sectors: 64H 32S/T 516C) da1 at aha0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 3.300MB/s transfers da1: 515MB (1056708 512 byte sectors: 64H 32S/T 515C) cd0 at aha0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [325725 x 2048 byte records] (cd1:aha0:0:6:0): CCB 0xc51952e0 - timed out (cd1:aha0:0:6:0): CCB 0xc51952e0 - timed out aha0: No longer in timeout cd1 at aha0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 8:58: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id C097414CEA for ; Tue, 20 Apr 1999 08:57:47 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id AAA02215; Wed, 21 Apr 1999 00:55:10 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: imp@harmony.village.org Cc: current@FreeBSD.ORG, newconfig@jp.freebsd.org Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: HEADS UP!!!! Important instructions for -current users! From: Tomoaki NISHIYAMA In-Reply-To: <199904201527.JAA03027@harmony.village.org> References: <19990420125547S.tomoaki@moss.nibb.ac.jp> <199904201527.JAA03027@harmony.village.org> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990421005509J.tomoaki@moss.nibb.ac.jp> Date: Wed, 21 Apr 1999 00:55:09 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 40 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Warner Losh Subject: Re: HEADS UP!!!! Important instructions for -current users! Date: Tue, 20 Apr 1999 09:27:56 -0600 Message-ID: <199904201527.JAA03027@harmony.village.org> imp> Thank you for the update on progress of new config, Nishiyama-san. imp> Are snapshots of the new config work available to members outside the imp> development team? If so, can you post a URL pointing to them. Yes, the source code is available to everyone in the world. General information is shown at http://www.jp.freebsd.org/newconfig/ Snapshots will appear at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/newconfig/snapshot/ You can also CVSup newconfig source from cvsup.jp.FreeBSD.ORG or its mirrors (cvsup[2-5].jp.FreeBSD.ORG). Example of CVSup file is: ---- begin example # Defaults that apply to all the collections *default host=cvsup.jp.freebsd.org *default base=/some/where/you/want *default prefix=/some/where/you/want/prefix *default release=cvs *default delete use-rel-suffix jp-newconfig ---- end example The test implementation code of dynamic configuration by UCHIYAMA Yasushi [newconfig-jp 1710] is at ftp://ftp.nop.or.jp/users/uch/PCMCIA/FreeBSD/ sys4c990410-newconfig990413-kld990419test2.patch.gz Note that this code is a test implementation and does not yet work completely. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 9:15:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id A188914C49 for ; Tue, 20 Apr 1999 09:15:04 -0700 (PDT) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 2205 invoked by uid 268); 20 Apr 1999 18:10:59 -0000 Message-ID: <19990420181059.2204.qmail@rucus.ru.ac.za> Subject: Re: Having trouble with the new ATAPI driver In-Reply-To: <19990420195135.A69626@tale.net> from William Liao at "Apr 20, 1999 7:51:35 pm" To: william@tale.net (William Liao) Date: Tue, 20 Apr 1999 18:10:59 +0000 (GMT) Cc: current@freebsd.org, sos@freebsd.org Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Liao writes : > > Hi, > I did a CVSUP and make world at 4/15, then I decided to try the > new ATAPI driver on my box. So I made some necessary changes to > my kernel config and made a new kernel. > But after boot, it always hangs on mounting disks. > The message is: swapon: /dev/wd0s1b: Device not configured > Then I tried to boot into single user mode and mount the slices > manually. Unfortunately, same thing happened again when I tried > to mount my /home, /var, etc. > Mount replied: /dev/wd2s1e: Device not configured. > > Did I miss anything?... Thanks for your help. I've actually seen the same symptoms, with one of my swap partitions, but it is now also giving me this with one of my file systems, on fsck, at bootup. It drops me to single user (since fsck -p fails), I run fsck -p manually, it is happy, and I go multiuser. The same happened with the swap partition in question - a second "swapon -a", and everything worked - that slice has however since become my /tmp, as I already had enough swap. I have only been getting "device not configured" errors on ad2 though. Geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 9:21:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from bryggen.bgnett.no (bryggen.bgnett.no [194.54.96.130]) by hub.freebsd.org (Postfix) with ESMTP id AD59515073 for ; Tue, 20 Apr 1999 09:21:21 -0700 (PDT) (envelope-from erikhb@bryggen.bgnett.no) Received: (from erikhb@localhost) by bryggen.bgnett.no (8.8.8/8.8.5/brage2.1) id QAA09936 for freebsd-current@freebsd.org; Tue, 20 Apr 1999 16:18:53 GMT Message-Id: <199904201618.QAA09936@bryggen.bgnett.no> Subject: Re: ATA driver for alpha In-Reply-To: from Doug Rabson at "Apr 20, 99 09:21:58 am" To: freebsd-current@freebsd.org Date: Tue, 20 Apr 1999 18:18:53 +0200 (MET DST) From: Erik Haugen Bakke X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 19 Apr 1999 erik@habatech.no wrote: > > > > > On 19-Apr-99 Doug Rabson wrote: > > > I have ported the new ATA driver to the FreeBSD/alpha. This provides > > > support for IDE disks and cdroms. The version of the driver in the tree > > > has only been tested on one old 433au machine so your mileage may vary > > >:-). For the adventurous, add these lines to your kernel config: > > > > > Hooray! > > Just one question, though... > > Will this driver support the Cypress CY82C693 controller on the AlphaPC > > 164SX boards? > > I think so. > If anyone has / will compile a boot disk with the new kernel, I would be very grateful if they could make it available for download somewhere. :) Anyone tracking -current? Regards --- Erik H. Bakke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 9:31:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 4DA6514EA6 for ; Tue, 20 Apr 1999 09:31:45 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id SAA11614 for ; Tue, 20 Apr 1999 18:33:08 +0200 (MET DST) Date: Tue, 20 Apr 1999 18:29:17 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: freebsd-current@freebsd.org Subject: Re: ATA driver for alpha (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---------- Forwarded message ---------- Date: Tue, 20 Apr 1999 18:29:04 +0200 (CEST) From: Nick Hibma To: Erik Haugen Bakke Subject: Re: ATA driver for alpha Jordan, you said nowadays one can simply compile a kernel < 1.44Mb and stick it on the disk kern.flp? People could appreciate this. I for one would like to make demo floppies to send to companies having supplied devices for USB support to show their devices at work. Nick > > > > I have ported the new ATA driver to the FreeBSD/alpha. This provides > > > > support for IDE disks and cdroms. The version of the driver in the tree > > > > has only been tested on one old 433au machine so your mileage may vary > > > >:-). For the adventurous, add these lines to your kernel config: > > > > > > > Hooray! > > > Just one question, though... > > > Will this driver support the Cypress CY82C693 controller on the AlphaPC > > > 164SX boards? > > > > I think so. > > > If anyone has / will compile a boot disk with the new kernel, > I would be very grateful if they could make it available for > download somewhere. :) > > Anyone tracking -current? > > Regards > --- > Erik H. Bakke > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 11:15: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 36FFC15061 for ; Tue, 20 Apr 1999 11:13:25 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id OAA01764 for ; Tue, 20 Apr 1999 14:13:38 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Tue, 20 Apr 1999 14:13:37 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: Build of kernel, and make world broken on my machine Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the last week, I haven't been able to get my kernel to build, or a make world to complete. I didn't have the kernel problems until recently, when the newbus stuff was done. This is my error when building the kernel. (after typing config -r MYKERNEL; make depend; make) cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ioconf.c ioconf.c:103: warning: `psm0_count' redefined ioconf.c:68: warning: this is the location of the previous definition ioconf.c:97: redefinition of `psm0_resources' ioconf.c:64: `psm0_resources' previously defined here ioconf.c:100: warning: excess elements in array initializer after `psm0_resource s' ioconf.c:101: warning: excess elements in array initializer after `psm0_resource s' *** Error code 1 Stop. culverk:/usr/src/sys/compile/MYKERNEL# make -DNOGAMES world always seems to crash when building libc but it stops at a different place each time. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 12:25:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E535E14D8F; Tue, 20 Apr 1999 12:25:23 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA25092; Wed, 21 Apr 1999 04:22:37 +0900 (JST) Message-ID: <371CD378.53956902@newsguy.com> Date: Wed, 21 Apr 1999 04:20:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Nick Hibma Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver for alpha (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > > Jordan, you said nowadays one can simply compile a kernel < 1.44Mb and > stick it on the disk kern.flp? It is possible. Even more, you can add kld modules to that disk, and then edit loader.rc to load them too, so you don't even need to compile a kernel. > People could appreciate this. I for one would like to make demo floppies > to send to companies having supplied devices for USB support to show > their devices at work. So, anyone up for creating a web page generating custom kern.klp disks, with features not found in GENERIC, using a cgi script? :-) If you limit this to adding kld modules, it would be surprisingly easy to do it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 12:41:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 36F0B14EEE for ; Tue, 20 Apr 1999 12:41:53 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA25869; Wed, 21 Apr 1999 04:39:00 +0900 (JST) Message-ID: <371CD751.652C6660@newsguy.com> Date: Wed, 21 Apr 1999 04:36:50 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: Build of kernel, and make world broken on my machine References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > > For the last week, I haven't been able to get my kernel to build, or a > make world to complete. I didn't have the kernel problems until recently, > when the newbus stuff was done. This is my error when building the kernel. > (after typing config -r MYKERNEL; make depend; make) I don't know about world, but the kernel will build much better once you remove the duplicate psm0 lines from MYKERNEL. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 12:49:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (Postfix) with SMTP id 8EC9914BD6 for ; Tue, 20 Apr 1999 12:49:23 -0700 (PDT) (envelope-from nordwick@xcf.berkeley.edu) Received: (qmail 17885 invoked by uid 27268); 20 Apr 1999 19:46:56 -0000 Date: 20 Apr 1999 19:46:56 -0000 Message-ID: <19990420194656.17884.qmail@scam.xcf.berkeley.edu> From: nordwick@xcf.berkeley.edu To: current@freebsd.org Subject: Which -current snapshot is good to install? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a box with an old 3.0-current distribution on it and want to move it to 4.0-current, but the upgrade path looks daunting, so I thought that I would just reinstall (besides, I could use the practice). I grabbed the 4.0-19990418-current/floppies files, but after a visual conf and removing unused drivers, then probbing the busses, it panics with an invalid page fault (I will report this more in depth later). So, what would be the safest snapshot to install with? thanks -jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 13: 8:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 0EB1D152FF for ; Tue, 20 Apr 1999 13:08:35 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.169]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2FAF; Tue, 20 Apr 1999 22:06:06 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id WAA00541; Tue, 20 Apr 1999 22:06:13 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 20 Apr 1999 22:06:13 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Some questions about booting with newbus Cc: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some questions I have pertaining the newbus stuff (and as a reminder to you Peter, thanks for looking into it): Am I the only one where booting with -v doesn't really do any verbose booting? Also, as talked about with Peter, -v should report unclaimed/unmatched devices, currently it doesn't... Also, I am trying to work up a driver here, but have only a list of vendor ID's for the PCI bus, anyone have a textfile with some more ID's such as the classes, etc..? Thanks, --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 13:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 26DED14F60 for ; Tue, 20 Apr 1999 13:22:07 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id A782C1F63; Wed, 21 Apr 1999 04:19:38 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Takanori Watanabe , freebsd-current@freebsd.org Subject: Re: newbus and modem(s) In-reply-to: Your message of "Tue, 20 Apr 1999 09:14:32 +0100." Date: Wed, 21 Apr 1999 04:19:38 +0800 From: Peter Wemm Message-Id: <19990420201939.A782C1F63@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Mon, 19 Apr 1999, Peter Wemm wrote: [..] > > Now what I'm curious about is how to handle the nexus and isa/eisa better > > so they don't need to explicitly name the children. On one hand it could > > look at the hints table to see all the 'at nexus?' declarations, but I > > think it might be better to go for a hunt to locate all the children it can > > find. One way to do this might be to simply add a heap of "unidentified" > > devices and let the bus mechanism find all the devices that are children > > and let them probe themselves while ignoring the fake device id's. Perhaps > > this could change the probe order enough so that isa and eisa won't be > > attached until after pci has been recursively probed. > > I'm not sure how this would work. At the nexus, I think it has to know > what the possibly attached devices are (or at least a list of names). The > NetBSD code does a simple probe (e.g. checking for pci config method or > looking for the mainboard ID) before adding devices. Thinking about this some more, the same problem is applicable to "smart" isa devices where the driver can find the card and the settings without any help. Presently it won't even get probed unless there is an 'at isa?' hint to cause the driver to be connected to isa. Presently, drivers are added to busses mostly in two ways. The first is where the bus has identification, and each identifier is added listing a device_id with an unknown driver/unit. The new-bus code will try all of the registered child drivers in turn until it finds one that matches and stops there. The isa bus on the other hand uses the hints to create a device instance that needs verification/probing. If there's no hint, the driver doesn't get a chance to probe. What I'd like would be for the busses to be able to call all the child drivers to let them look for themselves, and not stop until all are probed. For isa this would mean hint-less probing capabilities. For example, a driver could know that the hardware lives at one of 4 IO port addresses, so it could test them to see if it looks likely that there is one there. Obviously there is danger in this as calling the generic probe routines with no hints at all (ie: all zero) will cause rather bad results on most existing drivers. Perhaps there could be a specific 'identify' method for drivers that support this. ie: the probe/attach sequence would become: bus identifies what it can, ie: find device id's or look up resource hints. bus calls all child drivers to probe what has been found or hinted at bus calls all child drivers with an identify methods to see if they can find something on their own without an id or hint. This would be applicable to the nexus code as it would call all it's child driver 'identify' methods which would cause them to attach themselves to the nexus. You could then do a 'kldload eisa' and have the nexus get a notification of a new driver added, and then in doing the normal probe of the known devices (ie: none), the new eisa driver will have it's identify called which could then cause a new instance to be attached to the nexus, like what is presently hard coded. Does that make sense or am I rambling? :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 13:28:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id E6BE8151BD for ; Tue, 20 Apr 1999 13:28:08 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA96111; Tue, 20 Apr 1999 21:30:51 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 21:30:50 +0100 (BST) From: Doug Rabson To: Khetan Gajjar Cc: freebsd-current@FreeBSD.ORG Subject: Re: PCI VGA card becomes ISA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Apr 1999, Khetan Gajjar wrote: > Around Today, "Doug Rabson" wrote : > > DR> Its harmless and it should go away soon if we can reorganise syscons' vga > DR> driver slightly. > > I'm seeing this as well, but as you've said, it's harmless. > What I am "concerned" about is from sources last night, > the error > haveseen_isadev() called - FIXME! > after the isa0 bus has been probed, and something I haven't seen before : > (cd1:aha0:0:6:0): CCB 0xc51952e0 - timed out > indicating a problem with my Yamaha CD-RW. > > Is this something serious ? Its a reminder that the implementation of isa_compat is not quite complete. Not many drivers use this feature of the old isa code so we might just convert them all. > As an aside, I'm trying Soren's ATA code, and it combined with > the new-bus changes (neither of which I was using before) has made a > dramatic difference speed-wise (or maybe it's just a > placebo effect). Nice work :) I can't take credit for the ATA code. It is nice though :-) -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 13:32:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1B4311582B for ; Tue, 20 Apr 1999 13:32:00 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA96135; Tue, 20 Apr 1999 21:34:49 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 21:34:49 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: Takanori Watanabe , freebsd-current@freebsd.org Subject: Re: newbus and modem(s) In-Reply-To: <19990420201939.A782C1F63@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Peter Wemm wrote: > Doug Rabson wrote: > > On Mon, 19 Apr 1999, Peter Wemm wrote: > [..] > > > Now what I'm curious about is how to handle the nexus and isa/eisa better > > > so they don't need to explicitly name the children. On one hand it could > > > look at the hints table to see all the 'at nexus?' declarations, but I > > > think it might be better to go for a hunt to locate all the children it can > > > find. One way to do this might be to simply add a heap of "unidentified" > > > devices and let the bus mechanism find all the devices that are children > > > and let them probe themselves while ignoring the fake device id's. Perhaps > > > this could change the probe order enough so that isa and eisa won't be > > > attached until after pci has been recursively probed. > > > > I'm not sure how this would work. At the nexus, I think it has to know > > what the possibly attached devices are (or at least a list of names). The > > NetBSD code does a simple probe (e.g. checking for pci config method or > > looking for the mainboard ID) before adding devices. > > Thinking about this some more, the same problem is applicable to "smart" > isa devices where the driver can find the card and the settings without > any help. Presently it won't even get probed unless there is an 'at isa?' > hint to cause the driver to be connected to isa. > > Presently, drivers are added to busses mostly in two ways. The first is > where the bus has identification, and each identifier is added listing > a device_id with an unknown driver/unit. The new-bus code will try all > of the registered child drivers in turn until it finds one that matches > and stops there. The isa bus on the other hand uses the hints to create > a device instance that needs verification/probing. If there's no hint, > the driver doesn't get a chance to probe. > > What I'd like would be for the busses to be able to call all the child > drivers to let them look for themselves, and not stop until all are probed. > For isa this would mean hint-less probing capabilities. For example, a > driver could know that the hardware lives at one of 4 IO port addresses, so > it could test them to see if it looks likely that there is one there. > > Obviously there is danger in this as calling the generic probe routines > with no hints at all (ie: all zero) will cause rather bad results on most > existing drivers. Perhaps there could be a specific 'identify' method for > drivers that support this. > > ie: the probe/attach sequence would become: > > bus identifies what it can, ie: find device id's or look up resource hints. > bus calls all child drivers to probe what has been found or hinted at > bus calls all child drivers with an identify methods to see if they can > find something on their own without an id or hint. > > This would be applicable to the nexus code as it would call all it's child > driver 'identify' methods which would cause them to attach themselves to > the nexus. You could then do a 'kldload eisa' and have the nexus get a > notification of a new driver added, and then in doing the normal probe of > the known devices (ie: none), the new eisa driver will have it's identify > called which could then cause a new instance to be attached to the nexus, > like what is presently hard coded. > > Does that make sense or am I rambling? :-) It certainly makes sense (it would be sort of like the old eisa code where the driver digs around and finds all of the devices which it can drive). I have to figure out how this fits in with the interface system which really needs a device to hang off. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 13:56:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6911915323 for ; Tue, 20 Apr 1999 13:56:37 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA63699; Tue, 20 Apr 1999 14:53:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA05761; Tue, 20 Apr 1999 14:53:43 -0600 (MDT) Message-Id: <199904202053.OAA05761@harmony.village.org> To: Kenneth Wayne Culver Subject: Re: Build of kernel, and make world broken on my machine Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 20 Apr 1999 14:13:37 EDT." References: Date: Tue, 20 Apr 1999 14:53:43 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenneth Wayne Culver writes: : ioconf.c:103: warning: `psm0_count' redefined This is quickly becoming a FAQ. Remove the second psm0 device in your config file. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 13:56:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 83CB31525F for ; Tue, 20 Apr 1999 13:56:53 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA96224; Tue, 20 Apr 1999 22:00:01 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 22:00:01 +0100 (BST) From: Doug Rabson To: Jeroen Ruigrok/Asmodai Cc: FreeBSD Current , Peter Wemm Subject: Re: Some questions about booting with newbus In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Apr 1999, Jeroen Ruigrok/Asmodai wrote: > Some questions I have pertaining the newbus stuff (and as a reminder to you > Peter, thanks for looking into it): > > Am I the only one where booting with -v doesn't really do any verbose > booting? > > Also, as talked about with Peter, -v should report unclaimed/unmatched > devices, currently it doesn't... > > Also, I am trying to work up a driver here, but have only a list of vendor > ID's for the PCI bus, anyone have a textfile with some more ID's such as > the classes, etc..? There are a lot of class and subclass definitions in pcireg.h -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 13:59:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9B5B814EC6 for ; Tue, 20 Apr 1999 13:59:30 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA63712; Tue, 20 Apr 1999 14:56:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA05791; Tue, 20 Apr 1999 14:56:28 -0600 (MDT) Message-Id: <199904202056.OAA05791@harmony.village.org> To: Jeroen Ruigrok/Asmodai Subject: Re: Some questions about booting with newbus Cc: FreeBSD Current , Peter Wemm In-reply-to: Your message of "Tue, 20 Apr 1999 22:06:13 +0200." References: Date: Tue, 20 Apr 1999 14:56:28 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jeroen Ruigrok/Asmodai writes: : Am I the only one where booting with -v doesn't really do any verbose : booting? : Also, as talked about with Peter, -v should report unclaimed/unmatched : devices, currently it doesn't... I've seen that it does. I have a chip made by Sony that no driver claims. Likely a firewire or MPEG video chip of some flavor. : Also, I am trying to work up a driver here, but have only a list of vendor : ID's for the PCI bus, anyone have a textfile with some more ID's such as : the classes, etc..? You could look in http://www.halcyon.com/scripts/jboemler/pci/pcicode for a list of most vendors (that's how I know the chip is made by Sony) and for many cards (but none from Sony :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 14: 3:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0C7361588B for ; Tue, 20 Apr 1999 14:03:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA63732 for ; Tue, 20 Apr 1999 15:00:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA05834 for ; Tue, 20 Apr 1999 15:00:25 -0600 (MDT) Message-Id: <199904202100.PAA05834@harmony.village.org> To: current@freebsd.org Subject: Newbus in UPDATING Date: Tue, 20 Apr 1999 15:00:25 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that there has been some experience with newbus, I'd like to put together an entry for updating. So far I have the following problems: sio pnp/pccard support broken some (which ones?) sound drivers broken psm0 duplicate/duplicate devices in general keyboard/mouse attachment Anything else? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 14: 3:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 0442215A0E for ; Tue, 20 Apr 1999 14:03:32 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it ([194.185.55.56]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA18247 for ; Tue, 20 Apr 1999 23:02:24 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id WAA06911 for ; Tue, 20 Apr 1999 22:58:20 +0200 (CEST) Date: Tue, 20 Apr 1999 22:58:20 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver for alpha Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Great idea. I'll be the first one to try it with the USB support... > > People could appreciate this. I for one would like to make demo floppies > > to send to companies having supplied devices for USB support to show > > their devices at work. > > So, anyone up for creating a web page generating custom kern.klp > disks, with features not found in GENERIC, using a cgi script? :-) > > If you limit this to adding kld modules, it would be surprisingly > easy to do it. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "Well, Windows works, using a loose definition of 'works'..." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 14:10:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 8F7A1152C2 for ; Tue, 20 Apr 1999 14:10:07 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it ([194.185.55.56]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA18432; Tue, 20 Apr 1999 23:08:58 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id XAA06926; Tue, 20 Apr 1999 23:06:53 +0200 (CEST) Date: Tue, 20 Apr 1999 23:06:53 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Peter Wemm Cc: Doug Rabson , Takanori Watanabe , freebsd-current@FreeBSD.ORG Subject: Re: newbus and modem(s) In-Reply-To: <19990420201939.A782C1F63@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What about creating a second bus, isa_s, for ISA self probing? Nick On Wed, 21 Apr 1999, Peter Wemm wrote: > Doug Rabson wrote: > > On Mon, 19 Apr 1999, Peter Wemm wrote: > [..] > > > Now what I'm curious about is how to handle the nexus and isa/eisa better > > > so they don't need to explicitly name the children. On one hand it could > > > look at the hints table to see all the 'at nexus?' declarations, but I > > > think it might be better to go for a hunt to locate all the children it can > > > find. One way to do this might be to simply add a heap of "unidentified" > > > devices and let the bus mechanism find all the devices that are children > > > and let them probe themselves while ignoring the fake device id's. Perhaps > > > this could change the probe order enough so that isa and eisa won't be > > > attached until after pci has been recursively probed. > > > > I'm not sure how this would work. At the nexus, I think it has to know > > what the possibly attached devices are (or at least a list of names). The > > NetBSD code does a simple probe (e.g. checking for pci config method or > > looking for the mainboard ID) before adding devices. > > Thinking about this some more, the same problem is applicable to "smart" > isa devices where the driver can find the card and the settings without > any help. Presently it won't even get probed unless there is an 'at isa?' > hint to cause the driver to be connected to isa. > > Presently, drivers are added to busses mostly in two ways. The first is > where the bus has identification, and each identifier is added listing > a device_id with an unknown driver/unit. The new-bus code will try all > of the registered child drivers in turn until it finds one that matches > and stops there. The isa bus on the other hand uses the hints to create > a device instance that needs verification/probing. If there's no hint, > the driver doesn't get a chance to probe. > > What I'd like would be for the busses to be able to call all the child > drivers to let them look for themselves, and not stop until all are probed. > For isa this would mean hint-less probing capabilities. For example, a > driver could know that the hardware lives at one of 4 IO port addresses, so > it could test them to see if it looks likely that there is one there. > > Obviously there is danger in this as calling the generic probe routines > with no hints at all (ie: all zero) will cause rather bad results on most > existing drivers. Perhaps there could be a specific 'identify' method for > drivers that support this. > > ie: the probe/attach sequence would become: > > bus identifies what it can, ie: find device id's or look up resource hints. > bus calls all child drivers to probe what has been found or hinted at > bus calls all child drivers with an identify methods to see if they can > find something on their own without an id or hint. > > This would be applicable to the nexus code as it would call all it's child > driver 'identify' methods which would cause them to attach themselves to > the nexus. You could then do a 'kldload eisa' and have the nexus get a > notification of a new driver added, and then in doing the normal probe of > the known devices (ie: none), the new eisa driver will have it's identify > called which could then cause a new instance to be attached to the nexus, > like what is presently hard coded. > > Does that make sense or am I rambling? :-) > > Cheers, > -Peter > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 14:27:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 3A17E14BF5 for ; Tue, 20 Apr 1999 14:26:52 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA96322; Tue, 20 Apr 1999 22:29:19 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 20 Apr 1999 22:29:19 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: current@freebsd.org Subject: Re: Newbus in UPDATING In-Reply-To: <199904202100.PAA05834@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Apr 1999, Warner Losh wrote: > > Now that there has been some experience with newbus, I'd like to put > together an entry for updating. So far I have the following problems: > sio pnp/pccard support broken > some (which ones?) sound drivers broken > psm0 duplicate/duplicate devices in general > keyboard/mouse attachment > > Anything else? Machines with multiple host-pci bridges (Intel 450NX machines I think) will not probe the second bridge yet. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 14:34:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa17-30.ix.netcom.com [207.93.156.30]) by hub.freebsd.org (Postfix) with ESMTP id AA7B61527C for ; Tue, 20 Apr 1999 14:34:49 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id OAA01045; Tue, 20 Apr 1999 14:27:09 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Tue, 20 Apr 1999 14:27:09 -0700 (PDT) Message-Id: <199904202127.OAA01045@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: imp@harmony.village.org Cc: current@FreeBSD.ORG In-reply-to: <199904202100.PAA05834@harmony.village.org> (message from Warner Losh on Tue, 20 Apr 1999 15:00:25 -0600) Subject: Re: Newbus in UPDATING References: <199904202100.PAA05834@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Jose Gabriel Marcelino vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x700ff vga0: on isa0 known problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 16:37:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6108C14D4E; Tue, 20 Apr 1999 16:37:08 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA00567; Tue, 20 Apr 1999 16:34:39 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Apr 1999 16:34:39 -0700 (PDT) From: Matthew Dillon Message-Id: <199904202334.QAA00567@apollo.backplane.com> To: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: solid NFS patch #6 avail for -current - need testers files) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NFS patch #6 is now available for -current. This patch has been extensively tested with NFS and with FFS+softupdates and has not screwed up yet, so I'm reasonably confident that it will not scrap whole filesystems :-) http://www.backplane.com/FreeBSD4/ Please remember to back-out all prior patches before applying this one. Note that the memory-zeroing code ( which is committed to -current ), is *correct* and should not be disabled. This patch is for CURRENT ONLY. Do not apply to -3.x unless you like seeing computer equipment melt! The only difference between patch #5 and patch #6 is that the VMIO directory backing mods have been removed. These mods worked, but appear to have resulted in an occassional softupdates panic during 'installworld'. It is more important for us to have a rock solid implementation then majorly optimized implementation, so... The patch will probably return later on when we figure out why it is causing softupdates to panic. Please post bug reports to -current or -hackers. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 16:45: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 2F3A514EE0; Tue, 20 Apr 1999 16:45:01 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id QAA02679; Tue, 20 Apr 1999 16:42:21 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904202342.QAA02679@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Tue, 20 Apr 1999 16:34:39 PDT." <199904202334.QAA00567@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Apr 1999 16:42:21 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What does this patch fix? Tnks! Amancio -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 17:21:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id E0EAF15000 for ; Tue, 20 Apr 1999 17:21:12 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id CAA15494 for ; Wed, 21 Apr 1999 02:18:45 +0200 (CEST) Date: Wed, 21 Apr 1999 02:18:45 +0200 (CEST) From: Martin Blapp To: freebsd-current@freebsd.org Subject: ed0: device timeout Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Maybe current is not the right one to send my problem to - but I'm not subscribed on freebsd.mobile. Recently I bought a new laptop and my ed0-pccard stopped working. This happened before the newconfig stuff came in. I first thought there were some irq-related problems, but I wasn't able to figure out where the problems are. The pccard-controller is now on irq 3 (SIO1 is disabled). I also tried to put it on irq 9 or 10 with set machdep.pccard.pcic_irq, after I disabled the soundcard. That worked, but the result was the same. Is suppose that the irq's aren't as free they should be. I tried other io-settings, other irq's, the result was the same. Curious: A 2.2.8 PA0 system worked on this Laptop without problems, the card gets recognized and no timeouts appeared at all. Any help is welcome. I've no idea what my problem could be. some dmsg-output from fresh kernel: ----------------------------------- chip0: at device 0.0 on pci0 isab0: at device 1.0 on pci0 ide_pci0: at device 1.1 on pci0 uhci0: at device 1.2 on pci0 usb0: on uhci0 chip1: at device 1.3 on pci0 chip2: at device 3.0 on pci0 chip3: at device 3.1 on pci0 .... PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 Initializing PC-card drivers: ed .... Card inserted, slot 0 ed0: address 00:c0:f0:1c:b8:20, type NE2000 (16 bit) ed0: device timeout ed0: device timeout ed0: device timeout ed0: device timeout dmesg | grep irq: ----------------- uhci0: interrupting at irq 11 fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: interrupting at irq 15 atkbd0: interrupting at irq 1 psm0: interrupting at irq 12 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: interrupting at irq 4 ppc0 at port 0x378 irq 7 on isa0 ppc0: interrupting at irq 7 pcic: controller irq 3 cat /dev/sndstat : ----------------- OPL-2/OPL-3 FM at 0x388 SoundPort at 0x534 irq 5 drq 1,3 MPU-401 (UART) at 0x320 irq 9 /etc/pccard.conf : ------------------ # Generally available IO ports io 0x280 - 0x2F0 0x300 - 0x360 # Generally available IRQs (Built-in sound-card owners remove 5) irq 5 9 10 # Available memory slots memory 0xd4000 96k memory 0xc4000 32k # Kingston Ethernet card card "Kingston" "KNE-PC2" config 0x22 "ed0" 10 insert echo "Kingston card inserted" insert /etc/pccard_home ed0 remove echo "Kingston card removed" remove /sbin/ifconfig ed0 delete kernel-konfig: -------------- # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? device ed0 altern. kernel-konfig: ---------------------- controller card0 device pcic0 at card? device pcic1 at card? device ed0 at isa? port 0x340 net irq 10 iomem 0xd8000 pccardc dumpcis: ---------------- Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 3 000: 49 00 ff Attribute memory device information: Device number 1, type EEPROM, WPS = ON Speed = 250nS, Memory block size = 512b, 1 units Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 86 01 00 01 PCMCIA ID = 0x186, OEM ID = 0x100 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #5, code = 0x15 (Version 1 info), length = 21 000: 04 01 4b 69 6e 67 73 74 6f 6e 00 4b 4e 45 2d 50 010: 43 32 00 00 ff Version = 4.1, Manuf = [Kingston],card vers = [KNE-PC2] Addit. info = [] Tuple #6, code = 0x1a (Configuration map), length = 5 000: 01 23 f8 03 03 Reg len = 2, config register addr = 0x3f8, last config = 0x23 Registers: XX------ Tuple #7, code = 0x1b (Configuration entry), length = 21 000: e0 81 1d 3f 55 4d 5d 06 86 46 26 fc 24 c5 60 00 010: 03 1f 30 b8 9e Config index = 0x20(default) Interface byte = 0x81 (I/O) wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Minimum operating supply voltage: 4.5 x 1V Maximum operating supply voltage: 5.5 x 1V Continuous supply current: 1 x 100mA Max current average over 1 second: 1 x 100mA, ext = 0x46 Max current average over 10 ms: 2 x 100mA Wait scale Speed = 1.5 x 10 us Card decodes 4 address lines, 8 Bit I/O only IRQ modes: Level IRQ level = 4 Tuple #8, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 00 02 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x200 block length = 0x20 Tuple #9, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 20 02 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x220 block length = 0x20 Tuple #10, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 40 02 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x240 block length = 0x20 Tuple #11, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 60 02 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x260 block length = 0x20 Tuple #12, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 80 02 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x280 block length = 0x20 Tuple #13, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 a0 02 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x2a0 block length = 0x20 Tuple #14, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 c0 02 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x2c0 block length = 0x20 Tuple #15, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 e0 02 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x2e0 block length = 0x20 Tuple #16, code = 0x1b (Configuration entry), length = 7 000: 21 08 c5 60 20 03 1f Config index = 0x21 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x320 block length = 0x20 Tuple #17, code = 0x1b (Configuration entry), length = 7 000: 22 08 c5 60 40 03 1f Config index = 0x22 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x340 block length = 0x20 Tuple #18, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 80 03 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x380 block length = 0x20 Tuple #19, code = 0x1b (Configuration entry), length = 7 000: 20 08 c5 60 a0 03 1f Config index = 0x20 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x3a0 block length = 0x20 Tuple #20, code = 0x1b (Configuration entry), length = 7 000: 23 08 c5 60 60 03 1f Config index = 0x23 Card decodes 5 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x360 block length = 0x20 Tuple #21, code = 0xff (Terminator), length = 0 2 slots found pccardc rdmap ------------- Mem 0: flags 0x000 host 0x0 card 0000 size 0 bytes Mem 1: flags 0x000 host 0x0 card 0000 size 0 bytes Mem 2: flags 0x000 host 0x0 card 0000 size 0 bytes Mem 3: flags 0x000 host 0x0 card 0000 size 0 bytes Mem 4: flags 0x000 host 0x0 card 0000 size 0 bytes I/O 0: flags 0x015 port 0x340 size 32 bytes I/O 1: flags 0x000 port 0x 0 size 0 bytes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 18: 1:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 518F615065; Tue, 20 Apr 1999 18:01:27 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id UAA12380; Tue, 20 Apr 1999 20:14:29 -0500 (EST) Date: Tue, 20 Apr 1999 20:14:27 -0500 (EST) From: Alfred Perlstein To: Amancio Hasty Cc: Matthew Dillon , Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904202342.QAA02679@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Apr 1999, Amancio Hasty wrote: > What does this patch fix? NFS clients getting blocks of 0x00 in the cache. try to link a large object over NFS without the patches, you'll see what i mean. Matt, i'm going to test your patches now, I really appreciate the work and explanations you've given as to the problem and the solution you've devised. If anyone's gonna find a NFS bug.... :) I'm impressed with the changes you're proposing for the VM system and was wondering if these patches include the work for directory caching you've been working on. Thanks, -Alfred > > Tnks! > Amancio > > -- > > Amancio Hasty > hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 18:11:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 0468514DE1 for ; Tue, 20 Apr 1999 18:11:30 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id VAA07764; Tue, 20 Apr 1999 21:09:02 -0400 (EDT) Message-ID: <19990420210902.A6680@netmonger.net> Date: Tue, 20 Apr 1999 21:09:02 -0400 From: Christopher Masto To: current@freebsd.org Subject: New ATA driver and crash dumps Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My machine panicked today for the first time since switching to the new ATA drivers, and I noticed that I no longer have crash dumps. Is this something that is expected to be put back in soon? I know Søren's a busy guy, and I'm glad we have the results of his work. I just hope the old drivers don't get killed off until the replacement has the same functionality. Then again, wddump() is only 100 lines of code, so I should probably try to fix it myself before whining. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 18:28:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 98104150C7 for ; Tue, 20 Apr 1999 18:28:46 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id SAA26154; Tue, 20 Apr 1999 18:26:12 -0700 Date: Tue, 20 Apr 1999 18:26:11 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: new-bus, a moderate success report. In-Reply-To: <859.924457913@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To also follow the 'new-bus' success report story... I configured and built for a AMI mother board- two PCI busses... the only thing that was a gotcha was that de0 and de1 (both on separate PCI busses) got swapped in the changeover. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 18:41:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D402B1514F for ; Tue, 20 Apr 1999 18:41:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA12708; Tue, 20 Apr 1999 18:39:22 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Nick Hibma Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver for alpha (fwd) In-reply-to: Your message of "Tue, 20 Apr 1999 18:29:17 +0200." Date: Tue, 20 Apr 1999 18:39:22 -0700 Message-ID: <12706.924658762@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan, you said nowadays one can simply compile a kernel < 1.44Mb and > stick it on the disk kern.flp? Yep! You can even make one > 1.44MB and gzip it first (but remember to call it /kernel.gz or the loader won't be smart enough to un-gzip it). As long as the kernel is compiled with options MFS_ROOT and options MFS, it will know to look for the mfsroot image in memory (which the kern.flp's loader.rc will also ask for). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 19: 0:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id DC1351512E; Tue, 20 Apr 1999 19:00:07 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id LAA70229; Wed, 21 Apr 1999 11:25:51 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199904210155.LAA70229@gizmo.internode.com.au> Subject: Re: solid NFS patch #6 avail for -current - need testers To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 21 Apr 1999 11:25:51 +0930 (CST) Cc: rb@gid.co.uk, wilko@yedi.iaf.nl, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199904202334.QAA00567@apollo.backplane.com> from "Matthew Dillon" at Apr 20, 99 04:34:39 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > This patch is for CURRENT ONLY. Do not apply to -3.x unless you like > seeing computer equipment melt! Wow. I makes NFS access *that* fast?! - mark :-) ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 19: 1:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id B8B0915214 for ; Tue, 20 Apr 1999 19:01:34 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id <2RSVNV9W>; Wed, 21 Apr 1999 02:57:03 +0100 Message-ID: From: paul@originative.co.uk To: peter@netplex.com.au, dfr@nlsystems.com Cc: takawata@shidahara1.planet.sci.kobe-u.ac.jp, freebsd-current@freebsd.org Subject: RE: newbus and modem(s) Date: Wed, 21 Apr 1999 02:57:02 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Peter Wemm [mailto:peter@netplex.com.au] > Sent: 20 April 1999 21:20 > To: Doug Rabson > Cc: Takanori Watanabe; freebsd-current@freebsd.org > Subject: Re: newbus and modem(s) > > > Doug Rabson wrote: > > On Mon, 19 Apr 1999, Peter Wemm wrote: > [..] > > > Now what I'm curious about is how to handle the nexus and > isa/eisa better > > > so they don't need to explicitly name the children. On > one hand it could > > > look at the hints table to see all the 'at nexus?' > declarations, but I > > > think it might be better to go for a hunt to locate all > the children it can > > > find. One way to do this might be to simply add a heap > of "unidentified" > > > devices and let the bus mechanism find all the devices > that are children > > > and let them probe themselves while ignoring the fake > device id's. Perhaps > > > this could change the probe order enough so that isa and > eisa won't be > > > attached until after pci has been recursively probed. > > > > I'm not sure how this would work. At the nexus, I think it > has to know > > what the possibly attached devices are (or at least a list > of names). The > > NetBSD code does a simple probe (e.g. checking for pci > config method or > > looking for the mainboard ID) before adding devices. > > Thinking about this some more, the same problem is applicable > to "smart" > isa devices where the driver can find the card and the > settings without > any help. Presently it won't even get probed unless there is > an 'at isa?' > hint to cause the driver to be connected to isa. > > Presently, drivers are added to busses mostly in two ways. > The first is > where the bus has identification, and each identifier is added listing > a device_id with an unknown driver/unit. The new-bus code > will try all > of the registered child drivers in turn until it finds one > that matches > and stops there. The isa bus on the other hand uses the > hints to create > a device instance that needs verification/probing. If > there's no hint, > the driver doesn't get a chance to probe. > > What I'd like would be for the busses to be able to call all the child > drivers to let them look for themselves, and not stop until > all are probed. > For isa this would mean hint-less probing capabilities. For > example, a > driver could know that the hardware lives at one of 4 IO port > addresses, so > it could test them to see if it looks likely that there is one there. Doesn't this get in to the area we discussed some time back on the new-bus list about changing the way probing works so that instead of the pci code calling all the device drivers it just looks the device id up in a table and assigns that driver? I much prefer that direction than having all drivers called. > Obviously there is danger in this as calling the generic > probe routines > with no hints at all (ie: all zero) will cause rather bad > results on most > existing drivers. Perhaps there could be a specific > 'identify' method for > drivers that support this. > > ie: the probe/attach sequence would become: > > bus identifies what it can, ie: find device id's or look up > resource hints. > bus calls all child drivers to probe what has been found or hinted at > bus calls all child drivers with an identify methods to see > if they can > find something on their own without an id or hint. If I'm reading this right then you'd call an identify function in all available isa drivers and have them try and identify hardware? The risk here is that isa drivers/devices don't play well together and will trash you're machine if asked to probe for hardware that isn't present. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 19: 7: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8AB1214CFE; Tue, 20 Apr 1999 19:06:57 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA01245; Tue, 20 Apr 1999 19:04:26 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Apr 1999 19:04:26 -0700 (PDT) From: Matthew Dillon Message-Id: <199904210204.TAA01245@apollo.backplane.com> To: Alfred Perlstein Cc: Amancio Hasty , Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Matt, i'm going to test your patches now, I really appreciate the work :and explanations you've given as to the problem and the solution you've :devised. If anyone's gonna find a NFS bug.... :) : :I'm impressed with the changes you're proposing for the VM system :and was wondering if these patches include the work for directory :caching you've been working on. : :Thanks, :-Alfred No, we removed it temporarily while we track down a softupdates bug. Plus it's more an optimization ... not really a bug fix, so it should be separate. I didn't really propose that we do what I said in the last posting in re: to the VM system, though it is a possibility. Any changes at that level would not occur for a year or so ... not until 4.x becomes stable and 5.x becomes current. It wouldn't be worthwhile unless we could simplify some of the complexity in the existing setup, and there may be other ways to do that ( like, for example, embedding the I/O within the buffer cache routines rather then requiring that the caller issue the I/O, which encapsulates a great deal of the buffer cache's current complexity ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 19:27:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 23A861500F; Tue, 20 Apr 1999 19:27:34 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA01414; Tue, 20 Apr 1999 19:25:06 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Apr 1999 19:25:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199904210225.TAA01414@apollo.backplane.com> To: Amancio Hasty Cc: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <199904202342.QAA02679@rah.star-gate.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :What does this patch fix? : : Tnks! : Amancio : : Amancio Hasty : hasty@star-gate.com It mainly fixes interactions between mmap(), read(), and write() on NFS files. Many utilities ( such as the compiler/linker ) these days use a combination of the three and NFS was making assumptions that would leave a VM page partially uncovered - where the NFS system is storing critical data in the page but the VM system didn't know it was. The mmap-zero fixes that were committed last week brought the problem to light. As part of the fix, a bunch of things were ripped out of the buffer cache code. For example, the b_validoff/b_validend fields were ripped out because only NFS previously used them ( but don't any more ). Also pieces of the buffer cache code were rewritten in regards to dealing with the B_CACHE bit, leading to more optimal code in the critical path ( fewer scans the the b_pages array when figuring out the B_CACHE state of a struct buf ). And some other stuff. The whole thing stems from fixes made to -current over the last several months, fixes made by Luoqi, Alan, Julian, DG, and me. Luoqi concentrated on fixing up the vm_page_t valid/dirty handling and struct buf b_offset handling when dealing with small-block devices ( people may recall that this fixed, then broke, then fixed msdos floppy mounts that would occur after a ufs mount attempt, and also fixed CDROM panics ). The rest of us were working on a mmap-zeroing problem, NFS, and a mmap-garbage-after-file-EOF problem brought up by Tor. A number of vnode interlock issues came up that we fixed, a getnewbuf() supervisor stack overflow was fixed (I rewrote getnewbuf()), a bunch of low-memory handling issues were dealt with but there are still a few left. A few minor bugs in softupdates were fixed with Kirk's help. A VNOP/MMAP deadlock was fixed. Tor & DG and someone else threw in fixes for KVM exhaustion in large-memory subsystems, the ability to handle > 2G of ram, and BSDI compatibility w/ the new KVM increase. Earlier this year I tackled basic bugs in the VM system, rewrote the swapper, rewrote the VN device, and formalized and documented most of the VM system, and Alan and I began removing unused cruft. All in all, it has been a good beginning to the year. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 22:23:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 566EA1506C for ; Tue, 20 Apr 1999 22:23:49 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id WAA04008; Tue, 20 Apr 1999 22:21:14 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904210521.WAA04008@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf LINT GENERIC In-reply-to: Your message of "Mon, 19 Apr 1999 23:04:28 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Apr 1999 22:21:14 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > P.S.: USBDI as in, our version of it. The people from the consortium > kicked us out. Can you elaborate on the reason that USBDI does not FreeBSD to be involved with the consortium? Tnks P.S.: Just got a 3 COM USB modem and I am going over the USB specs right now 8) -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 20 23:50:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B318414F6B for ; Tue, 20 Apr 1999 23:50:13 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA33104; Wed, 21 Apr 1999 08:47:43 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904210647.IAA33104@freebsd.dk> Subject: Re: New ATA driver and crash dumps In-Reply-To: <19990420210902.A6680@netmonger.net> from Christopher Masto at "Apr 20, 1999 9: 9: 2 pm" To: chris@netmonger.net (Christopher Masto) Date: Wed, 21 Apr 1999 08:47:42 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Christopher Masto wrote: > My machine panicked today for the first time since switching to the > new ATA drivers, and I noticed that I no longer have crash dumps. > Is this something that is expected to be put back in soon? > > I know Søren's a busy guy, and I'm glad we have the results of his > work. I just hope the old drivers don't get killed off until the > replacement has the same functionality. > > Then again, wddump() is only 100 lines of code, so I should probably > try to fix it myself before whining. I know :), it has just not been done yet. It will be done eventually but I have other areas in the driver I want finish first. Also the old wd driver will probably not be killed off entirely, as its the only one we have that support old ST506/ESDI drives. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 0:55:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id EB4E015819 for ; Wed, 21 Apr 1999 00:55:41 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id DAA22828 for current@freebsd.org; Wed, 21 Apr 1999 03:53:13 -0400 (EDT) (envelope-from luoqi) Date: Wed, 21 Apr 1999 03:53:13 -0400 (EDT) From: Luoqi Chen Message-Id: <199904210753.DAA22828@lor.watermarkgroup.com> To: current@freebsd.org Subject: egcs bug caused ftp hang problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An egcs optimizer bug caused incorrect tcp checksum recalculation in libalias for the rewritten PORT command packet and the server subsequently discard the packet. The following piece of C code (from TcpChecksum() in alias_util.c) u_short *ptr; int sum, oddbyte; oddbyte = 0; *((u_char *) &oddbyte) = *(u_char *) ptr; sum += oddbyte; is compiled into (%esi = ptr, %ecx = sum) 0x28067038 : movb (%esi),%al 0x2806703a : addl %eax,%ecx egcs should have zeroed %eax before the movb. libalias compiled without -O works correctly. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 1: 9:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id CB7FC14C1E for ; Wed, 21 Apr 1999 01:09:21 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA97910; Wed, 21 Apr 1999 09:12:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 21 Apr 1999 09:12:24 +0100 (BST) From: Doug Rabson To: paul@originative.co.uk Cc: peter@netplex.com.au, takawata@shidahara1.planet.sci.kobe-u.ac.jp, freebsd-current@freebsd.org Subject: RE: newbus and modem(s) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999 paul@originative.co.uk wrote: > > -----Original Message----- > > From: Peter Wemm [mailto:peter@netplex.com.au] > > Sent: 20 April 1999 21:20 > > To: Doug Rabson > > Cc: Takanori Watanabe; freebsd-current@freebsd.org > > Subject: Re: newbus and modem(s) > > > > > > Doug Rabson wrote: > > > On Mon, 19 Apr 1999, Peter Wemm wrote: > > [..] > > > > Now what I'm curious about is how to handle the nexus and > > isa/eisa better > > > > so they don't need to explicitly name the children. On > > one hand it could > > > > look at the hints table to see all the 'at nexus?' > > declarations, but I > > > > think it might be better to go for a hunt to locate all > > the children it can > > > > find. One way to do this might be to simply add a heap > > of "unidentified" > > > > devices and let the bus mechanism find all the devices > > that are children > > > > and let them probe themselves while ignoring the fake > > device id's. Perhaps > > > > this could change the probe order enough so that isa and > > eisa won't be > > > > attached until after pci has been recursively probed. > > > > > > I'm not sure how this would work. At the nexus, I think it > > has to know > > > what the possibly attached devices are (or at least a list > > of names). The > > > NetBSD code does a simple probe (e.g. checking for pci > > config method or > > > looking for the mainboard ID) before adding devices. > > > > Thinking about this some more, the same problem is applicable > > to "smart" > > isa devices where the driver can find the card and the > > settings without > > any help. Presently it won't even get probed unless there is > > an 'at isa?' > > hint to cause the driver to be connected to isa. > > > > Presently, drivers are added to busses mostly in two ways. > > The first is > > where the bus has identification, and each identifier is added listing > > a device_id with an unknown driver/unit. The new-bus code > > will try all > > of the registered child drivers in turn until it finds one > > that matches > > and stops there. The isa bus on the other hand uses the > > hints to create > > a device instance that needs verification/probing. If > > there's no hint, > > the driver doesn't get a chance to probe. > > > > What I'd like would be for the busses to be able to call all the child > > drivers to let them look for themselves, and not stop until > > all are probed. > > For isa this would mean hint-less probing capabilities. For > > example, a > > driver could know that the hardware lives at one of 4 IO port > > addresses, so > > it could test them to see if it looks likely that there is one there. > > Doesn't this get in to the area we discussed some time back on the new-bus > list about changing the way probing works so that instead of the pci code > calling all the device drivers it just looks the device id up in a table and > assigns that driver? > > I much prefer that direction than having all drivers called. > > > Obviously there is danger in this as calling the generic > > probe routines > > with no hints at all (ie: all zero) will cause rather bad > > results on most > > existing drivers. Perhaps there could be a specific > > 'identify' method for > > drivers that support this. > > > > ie: the probe/attach sequence would become: > > > > bus identifies what it can, ie: find device id's or look up > > resource hints. > > bus calls all child drivers to probe what has been found or hinted at > > bus calls all child drivers with an identify methods to see > > if they can > > find something on their own without an id or hint. > > If I'm reading this right then you'd call an identify function in all > available isa drivers and have them try and identify hardware? The risk here > is that isa drivers/devices don't play well together and will trash you're > machine if asked to probe for hardware that isn't present. If we do this, possible it should be restricted to 'wildcard' style declarations in the probe hints. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 2:33:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ic.net (ic.net [152.160.8.96]) by hub.freebsd.org (Postfix) with SMTP id 213A714E81 for ; Wed, 21 Apr 1999 02:33:15 -0700 (PDT) (envelope-from rickl@ic.net) Received: (qmail 17083 invoked from network); 21 Apr 1999 09:24:20 -0000 Received: from unknown (HELO lurch.rickl.org) (152.160.108.44) by unknown with SMTP; 21 Apr 1999 09:24:20 -0000 Content-Length: 718 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 21 Apr 1999 05:28:13 -0400 (EDT) Reply-To: rickl@ic.net Organization: ic.net From: Rick Lotoczky To: freebsd-current@freebsd.org Subject: RE: ed0: device timeout Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Apr-99 Martin Blapp wrote: > > Hi, > > Recently I bought a new laptop and my ed0-pccard stopped working. This > happened before the newconfig stuff came in. I first thought there were > some irq-related problems, but I wasn't able to figure out where the > problems are. The pccard-controller is now on irq 3 (SIO1 is disabled). I > also tried to put it on irq 9 or 10 with set machdep.pccard.pcic_irq, > after I disabled the soundcard. That worked, but the result was the same. > Is suppose that the irq's aren't as free they should be. I tried other > io-settings, other irq's, the result was the same. > I had the same problem with ed0 not being recognized. I recompiled "world" and all was fine. Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 3: 5:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 6DA7814D56 for ; Wed, 21 Apr 1999 03:05:19 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id MAA00089; Wed, 21 Apr 1999 12:06:22 +0200 (MET DST) Date: Wed, 21 Apr 1999 12:02:30 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf LINT GENERIC In-Reply-To: <199904210521.WAA04008@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > P.S.: USBDI as in, our version of it. The people from the consortium > > kicked us out. > Can you elaborate on the reason that USBDI does not FreeBSD > to be involved with the consortium? Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka consortium. No company was willing to pay it for us and the consortium was not willing to waive the fee, because not-for-profit organisations still draw a certain benefit for their community, or something along those lines. All sounds a bit strange if you consider the fact that the spec will be open and free-for-all eventualy. > Tnks > P.S.: Just got a 3 COM USB modem and I am going over the USB specs right now 8) The dev/usb/umodem.c file probes it. but the attach function is not filled in at all. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 3:12:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 02EFE14D56 for ; Wed, 21 Apr 1999 03:12:22 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id DAA02084; Wed, 21 Apr 1999 03:09:48 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904211009.DAA02084@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf LINT GENERIC In-reply-to: Your message of "Wed, 21 Apr 1999 12:02:30 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Apr 1999 03:09:48 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > P.S.: USBDI as in, our version of it. The people from the consortium > > > kicked us out. > > > > Can you elaborate on the reason that USBDI does not FreeBSD > > to be involved with the consortium? > > Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka > consortium. No company was willing to pay it for us and the consortium > was not willing to waive the fee, because not-for-profit organisations > still draw a certain benefit for their community, or something along > those lines. All sounds a bit strange if you consider the fact that the > spec will be open and free-for-all eventualy. > > > > Tnks > > P.S.: Just got a 3 COM USB modem and I am going over the USB specs right now 8) > > The dev/usb/umodem.c file probes it. but the attach function is not > filled in at all. Okay, I will take a look at the umodem.c driver. Tnks! Amancio -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 8:19: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 0001915357; Wed, 21 Apr 1999 08:18:54 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id KAA03575; Wed, 21 Apr 1999 10:32:20 -0500 (EST) Date: Wed, 21 Apr 1999 10:32:19 -0500 (EST) From: Alfred Perlstein To: Matthew Dillon Cc: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904202334.QAA00567@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Apr 1999, Matthew Dillon wrote: > NFS patch #6 is now available for -current. This patch has been > extensively tested with NFS and with FFS+softupdates and has not > screwed up yet, so I'm reasonably confident that it will not > scrap whole filesystems :-) > > http://www.backplane.com/FreeBSD4/ > > Please remember to back-out all prior patches before applying this one. > Note that the memory-zeroing code ( which is committed to -current ), is > *correct* and should not be disabled. > > This patch is for CURRENT ONLY. Do not apply to -3.x unless you like > seeing computer equipment melt! > > The only difference between patch #5 and patch #6 is that the VMIO > directory backing mods have been removed. These mods worked, but > appear to have resulted in an occassional softupdates panic during > 'installworld'. It is more important for us to have a rock solid > implementation then majorly optimized implementation, so... The > patch will probably return later on when we figure out why it is > causing softupdates to panic. > > Please post bug reports to -current or -hackers. .(14:57:37)(root@thumper.reserved) /usr # mount /dev/da0s1a on / (local, soft-updates, writes: sync 598 async 27021) /dev/da0s1g on /home (local, soft-updates, writes: sync 25 async 679) /dev/da0s1f on /usr (local, soft-updates, writes: sync 738 async 42763) /dev/da0s1e on /var (local, soft-updates, writes: sync 106 async 1783) procfs on /proc (local) server:/usr/src on /usr/src server:/usr/obj on /usr/obj server:/home/ncvs on /home/ncvs /usr/src # for i in 1 2 3 4 5 6 ; do make world -j64 ; echo "$i done.." ; done >& ../build.log nfs server server:/usr/obj: not responding nfs server server:/usr/obj: is alive again .(15:00:59)(root@thumper.reserved) /usr # uptime 3:01PM up 6:55, 1 user, load averages: 1.72, 7.03, 7.34 .(15:01:47)(root@thumper.reserved) /usr # grep "^[0-9] done" build.log 1 done.. 2 done.. 3 done.. .(15:05:05)(root@thumper.reserved) /usr # .(03:33:51)(root@bright.reserved) /usr/obj # uptime 10:02AM up 14:40, 1 user, load averages: 0.18, 0.16, 0.14 yeah the clocks are not setup properly :) but otherwise i'm just gonna say HOLY SH*T you fixed NFS! :) Actually I just realized I'm not running nfsiod on the client, I just started up 8 of them (it's an SMP box). So far no problems. I'm using the default mount operations, as far as NFS server not responding messages, i have no clue, but the server is still up and i've seen that message happen when a lot of pressure is being put on an NFS server even though everything is fine. Normally i'd have client corruption and a rebooted server with both of them locked up sending out garbled RPC about now, but everything seems fine... great work! 2 questions I had: 1) you said you disabled partial writes that were causing these mmap() problems, they were causing problems because NFS had to muck with the structures directly in order to do zero copy? so if our NFS impelementation didn't do that it wouldn't be an issue probably. I know it's a good thing for speed and definetly essensial, but i'm not sure i understand NFS and the FS getting out of sync. 2) at BAFUG 2 or 3 months ago I, *cough* attempted to keep up with you an Julian talking about VM issues. :) Something you guys brought up was problems with mmap() + read()/write() no staying in sync and requireing an msync() to correctly syncronize. I really didn't understand how this could happen except recently I figured that my first question could be the answer. Does this problem only happen on NFS mounted dirs? Is it fixed? thanks again, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 9:13:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 0B40514BE5 for ; Wed, 21 Apr 1999 09:13:16 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA28330 for ; Wed, 21 Apr 1999 11:27:08 -0500 (EST) Date: Wed, 21 Apr 1999 11:27:07 -0500 (EST) From: Alfred Perlstein To: current@freebsd.org Subject: someone fixed CPU time bug, thanks. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SMP on -current would lose the WCPU and CPU times after a while in top's output, this seems to be fixed on my machine/mobo with the latest source. Asus PD2 afaik dual 400mhz. thanks guys, great work! -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 9:30:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 4F10015102 for ; Wed, 21 Apr 1999 09:30:31 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id JAA23874 for freebsd-current@freebsd.org; Wed, 21 Apr 1999 09:25:38 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904211625.JAA23874@troutmask.apl.washington.edu> Subject: Please close PR gnu/9175 To: freebsd-current@freebsd.org Date: Wed, 21 Apr 1999 09:25:38 -0700 (PDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This PR is no longer validate now that g77 has enter the base distribution. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 9:34: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 9CA5114C3E; Wed, 21 Apr 1999 09:34:06 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id LAA29863; Wed, 21 Apr 1999 11:31:05 -0500 (CDT) From: Kevin Day Message-Id: <199904211631.LAA29863@home.dragondata.com> Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester In-Reply-To: from Alfred Perlstein at "Apr 21, 1999 10:32:19 am" To: bright@rush.net (Alfred Perlstein) Date: Wed, 21 Apr 1999 11:31:05 -0500 (CDT) Cc: dillon@apollo.backplane.com, rb@gid.co.uk, wilko@yedi.iaf.nl, current@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > yeah the clocks are not setup properly :) but otherwise i'm just > gonna say HOLY SH*T you fixed NFS! :) We all owe Matt big for this. :) > I'm using the default mount operations, as far as NFS server > not responding messages, i have no clue, but the server is still > up and i've seen that message happen when a lot of pressure is > being put on an NFS server even though everything is fine. Try mounting with -d... Can I make a guess that the NFS mount is going over 100MB ethernet? I have a strong theory that the dynamic retransmit timer needs rework for low latency connections, with high variability in their performance during high traffic. (lots of collisions) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 9:55:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id E20A0153B2 for ; Wed, 21 Apr 1999 09:55:27 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA02026; Wed, 21 Apr 1999 12:09:04 -0500 (EST) Date: Wed, 21 Apr 1999 12:09:03 -0500 (EST) From: Alfred Perlstein To: Kevin Day Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester In-Reply-To: <199904211631.LAA29863@home.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Kevin Day wrote: > > yeah the clocks are not setup properly :) but otherwise i'm just > > gonna say HOLY SH*T you fixed NFS! :) > > > We all owe Matt big for this. :) > > > > I'm using the default mount operations, as far as NFS server > > not responding messages, i have no clue, but the server is still > > up and i've seen that message happen when a lot of pressure is > > being put on an NFS server even though everything is fine. > > Try mounting with -d... Can I make a guess that the NFS mount is going over > 100MB ethernet? I have a strong theory that the dynamic retransmit timer > needs rework for low latency connections, with high variability in their > performance during high traffic. (lots of collisions) Hmmm, well the client/server are both on 100mbit full duplex switched ethernet, fxp0<->fxp0 with no load other than the build going on. btw, just finished run 4 of buildworld, still kicking. I would just like to say, that unlike certain zealots of other operating systems I've always been a bit hesitant to recommend FreeBSD over solaris because of this one factor (NFS). It now seems I can't think of a single reason, (I'm much more a cluster fan than an SMP fan) SMP just doesn't buy you enough to justify putting all your eggs in one basket... Oh and the client is SMP, so i'm quite impressed on that fron as well. Oh and the newbus stuff.... "rah rah rah!" works like a charm except my USB (which i have no prepherals for anyhow). -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 9:57:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id DE73F153D2 for ; Wed, 21 Apr 1999 09:56:26 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([216.160.82.65]) by boromir.vpop.net (8.9.1/8.9.1) with ESMTP id JAA01521 for ; Wed, 21 Apr 1999 09:53:58 -0700 (PDT) Message-ID: <371E02A4.64691949@vpop.net> Date: Wed, 21 Apr 1999 09:53:56 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Great work guys! It almost seems that -current is more stable than -stable! Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:22:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from oldnews.quick.net (unknown [207.212.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 6BDD515409 for ; Wed, 21 Apr 1999 10:22:01 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id KAA13813; Wed, 21 Apr 1999 10:19:27 -0700 (PDT) Date: Wed, 21 Apr 1999 10:19:27 -0700 (PDT) From: "Steven P. Donegan" To: Alfred Perlstein Cc: Kevin Day , dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Alfred Perlstein wrote: > On Wed, 21 Apr 1999, Kevin Day wrote: > > > > > Try mounting with -d... Can I make a guess that the NFS mount is going over > > 100MB ethernet? I have a strong theory that the dynamic retransmit timer > > needs rework for low latency connections, with high variability in their > > performance during high traffic. (lots of collisions) > > Hmmm, well the client/server are both on 100mbit > full duplex switched ethernet, fxp0<->fxp0 with no load > other than the build going on. > With a full duplex setup collisions don't exist. In a switched setup the latency should be very consistent and extremely low. Something else must be wrong here. I'm very glad NFS is getting fixed - I'd really like to use FreeBSD in a frontend/backend setup with multiple round-robin DNS setup web servers with the web content on a backend NFS/RAID server. (poor man's Network Appliance equivalent :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:23: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 480D514E23; Wed, 21 Apr 1999 10:22:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA06806; Wed, 21 Apr 1999 10:20:24 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 10:20:24 -0700 (PDT) From: Matthew Dillon Message-Id: <199904211720.KAA06806@apollo.backplane.com> To: Alfred Perlstein Cc: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need testers files) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :2 questions I had: : :1) you said you disabled partial writes that were causing these :mmap() problems, they were causing problems because NFS had to :muck with the structures directly in order to do zero copy? : so if our NFS impelementation didn't do that it wouldn't be :an issue probably. I know it's a good thing for speed and definetly :essensial, but i'm not sure i understand NFS and the FS getting out :of sync. The problem w/ the partial writes has to do with cache coherency between the server, the client's VFS subsystem ( read() and write() ), and the client's VM subsystem ( mmap() ). NFS implemented the notion of unaligned valid and dirty range using struct buf's b_validoff, b_validend, b_dirtyoff, and b_dirtyend fields in order to keep track of partial writes without having to read-in the rest of the buffer. The implementation was very fragile and failed to address a number of combination situations that would occur with mmap(), read(), and write(). This in turn lead to a series of problems and, further, lead to the situation where we would fix unrelated bugs in the VM system and cause NFS to break. I finally gave up on it. What NFS does now is optimize only two write situations: (1) when a write covers the entire buffer, e.g. an 8K+ write on an 8K boundry. And (2) piecemeal writes in the write-append case. Both cases allow us to mark the buffer as essentially being fully valid without having to mess with valid and dirty ranges. We use buf->b_bcount to handle the file EOF case and resize it rather then try to use b_validoff/b_validend. Thus, b_validoff/b_validend have been completely removed. b_dirtyoff/b_dirtyend have been left intact in order to allow us to support piecemeal write RPC's. This is different from the piecemeal write optimizations we were doing before. In this case, we are able to support piecemeal writes in the middle of the file that go into *PRELOADED* buffers. That is, A read-merge-write case. The original code attempted to do piecemeal writes without the read-before resulting in the partially invalid, partially dirty buffer. Now we only allow piecemeal writes to occur in fully-valid buffers. While we could theoretically discard the dirty range and simply writeback the entire buffer when a modification is made to part of it, we keep the dirty range in order to *only* write the portion of the buffer that the explicit write() covered. This is done for cache coherency reasons. For example, take the situation where two different client machines do a seek/write to different portions of the same server-backed NFS file, where the two areas abut each other. Say one client writes 2 bytes at seek offset 10 and the second client writes 2 bytes at seek offset 12. As long as the areas are not overlapping, we want this type of operation to work properly and not scramble the data on the server even if the client's idea of the state of the date is not coherent. :2) at BAFUG 2 or 3 months ago I, *cough* attempted to keep up with you :an Julian talking about VM issues. :) Something you guys brought up :was problems with mmap() + read()/write() no staying in sync and requireing :an msync() to correctly syncronize. I really didn't understand how this :could happen except recently I figured that my first question could be :the answer. Does this problem only happen on NFS mounted dirs? Is it :fixed? : :thanks again, :-Alfred This should not be an issue any more for either UFS or NFS. If people find that it is an issue, there's a bug somewhere that needs to be addressed. This *was* an issue for NFS prior to the patch set. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:25:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5490714D35 for ; Wed, 21 Apr 1999 10:25:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA06827; Wed, 21 Apr 1999 10:22:41 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 10:22:41 -0700 (PDT) From: Matthew Dillon Message-Id: <199904211722.KAA06827@apollo.backplane.com> To: Alfred Perlstein Cc: Kevin Day , current@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I would just like to say, that unlike certain zealots of other operating :systems I've always been a bit hesitant to recommend FreeBSD over :solaris because of this one factor (NFS). : :It now seems I can't think of a single reason, (I'm much more a :cluster fan than an SMP fan) SMP just doesn't buy you enough to :justify putting all your eggs in one basket... : :-Alfred Heh. We still do not have file locking over NFS. That's a major piece. In general, though, I think FreeBSD's NFS is shaping up pretty well. It is certainly much, much better then any other OS out there except solaris. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:29:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9963A14D35 for ; Wed, 21 Apr 1999 10:29:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA06851; Wed, 21 Apr 1999 10:26:40 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 10:26:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199904211726.KAA06851@apollo.backplane.com> To: Alfred Perlstein Cc: Kevin Day , current@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> We all owe Matt big for this. :) :> :> :> > I'm using the default mount operations, as far as NFS server :> > not responding messages, i have no clue, but the server is still :> > up and i've seen that message happen when a lot of pressure is :> > being put on an NFS server even though everything is fine. :> :> Try mounting with -d... Can I make a guess that the NFS mount is going over :> 100MB ethernet? I have a strong theory that the dynamic retransmit timer :> needs rework for low latency connections, with high variability in their :> performance during high traffic. (lots of collisions) : :Hmmm, well the client/server are both on 100mbit :full duplex switched ethernet, fxp0<->fxp0 with no load :other than the build going on. : :-Alfred I think Kevin is right re: the dynamic retransmit timeout. I've noticed it occuring on my systems too -- although without the lockups. But Kevin has other problems w/ his network that could be contributing to the problems he is experiencing. :btw, just finished run 4 of buildworld, still kicking. I've gone through 4 buildworlds so far without any errors using an NFS mounted /usr/src and /usr/obj. Though, I must say, it takes about twice as long as with a FFS+softupdates /usr/obj ( two hours verses 50 minutes ). The read optimization is very good, though. Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:46:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 916DD1543B for ; Wed, 21 Apr 1999 10:46:12 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA24561; Wed, 21 Apr 1999 12:59:22 -0500 (EST) Date: Wed, 21 Apr 1999 12:59:20 -0500 (EST) From: Alfred Perlstein To: Matthew Dillon Cc: "Steven P. Donegan" , Alfred Perlstein , Kevin Day , current@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester In-Reply-To: <199904211730.KAA06870@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Matthew Dillon wrote: > : > :With a full duplex setup collisions don't exist. In a switched setup the > :latency should be very consistent and extremely low. Something else must > :be wrong here. > > I should explain this more: It isn't actually the ethernet latency > that is causing the problem, but instead it is the packet backlog that > is occuring on the interface. Even at 100BaseTX speeds. Under a heavy > NFS load, an NFS client might send several requests simultaniously or > the server might send several responses simultaniously. If each request > takes 0.5 mS to transit the network, the first request will have a > latency of 1 ms, the second will have a latency of 1.5 ms. The > third 2 ms. And so forth. When N requests are queued simultaniously, > the last request in the queue will have a much longer latency then > the first one. > > Full-duplex setups do not have collisions, but latency can occur due to > internal switch routing latencies. > Perhaps the timeout should be slightly adjusted it seems that it can cause panics, panics by users, not the kernel. :) As in... "what the heck is this?" when in reality everything is fine except a miniscule amount of latency on the interface. Some error messages should be constrained to DIAGNOSTIC so new users or people not interested in the kernel don't get nervous about freebsd. "Everything seems fine, but why am i getting errors?" -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:49: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 5F42D15858 for ; Wed, 21 Apr 1999 10:47:31 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id ECEC61F2A; Thu, 22 Apr 1999 01:45:01 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Reimer Cc: freebsd-current@freebsd.org Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Wed, 21 Apr 1999 09:53:56 MST." <371E02A4.64691949@vpop.net> Date: Thu, 22 Apr 1999 01:45:01 +0800 From: Peter Wemm Message-Id: <19990421174502.ECEC61F2A@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Reimer wrote: > Great work guys! It almost seems that -current is more stable than > -stable! > > Matt Funny you should mention it. I've heard this from a number of people over the last week.. One has even suggested using a particular known-good 4.0 snapshot in preference to a 3.1-stable for a production system...... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:49:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id ADD2615886 for ; Wed, 21 Apr 1999 10:47:55 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id NAA04155; Wed, 21 Apr 1999 13:01:43 -0500 (EST) Date: Wed, 21 Apr 1999 13:01:41 -0500 (EST) From: Alfred Perlstein To: Matthew Dillon Cc: Kevin Day , current@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester In-Reply-To: <199904211722.KAA06827@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Matthew Dillon wrote: > : > :I would just like to say, that unlike certain zealots of other operating > :systems I've always been a bit hesitant to recommend FreeBSD over > :solaris because of this one factor (NFS). > : > :It now seems I can't think of a single reason, (I'm much more a > :cluster fan than an SMP fan) SMP just doesn't buy you enough to > :justify putting all your eggs in one basket... > : > :-Alfred > > Heh. We still do not have file locking over NFS. That's a major piece. > In general, though, I think FreeBSD's NFS is shaping up pretty well. It > is certainly much, much better then any other OS out there except > solaris. File locking over a stateless filesystem is just plain icky. Supposedly someone is working on client side locking, and I definetly will take a look at it just out of interest, not that i think i have a chance of implementing it. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:52:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 7C35715420; Wed, 21 Apr 1999 10:51:20 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id NAA01767; Wed, 21 Apr 1999 13:05:01 -0500 (EST) Date: Wed, 21 Apr 1999 13:04:58 -0500 (EST) From: Alfred Perlstein To: Matthew Dillon Cc: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? , :) , WAS: Re: solid NFS patch #6 avail for -current - need testers , files) In-Reply-To: <199904211720.KAA06806@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Matthew Dillon wrote: > :2 questions I had: > : > :2) at BAFUG 2 or 3 months ago I, *cough* attempted to keep up with you > :an Julian talking about VM issues. :) Something you guys brought up > :was problems with mmap() + read()/write() no staying in sync and requireing > :an msync() to correctly syncronize. I really didn't understand how this > :could happen except recently I figured that my first question could be > :the answer. Does this problem only happen on NFS mounted dirs? Is it > :fixed? > : > :thanks again, > :-Alfred > > This should not be an issue any more for either UFS or NFS. If people > find that it is an issue, there's a bug somewhere that needs to be > addressed. This *was* an issue for NFS prior to the patch set. Ok, so is this what you and Julian were discussing about coherency issues? And it is fixed... cool. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 10:55: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 66AF5156D2; Wed, 21 Apr 1999 10:54:45 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id NAA31922; Wed, 21 Apr 1999 13:51:39 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904211751.NAA31922@misha.cisco.com> Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <19990421174502.ECEC61F2A@spinner.netplex.com.au> from Peter Wemm at "Apr 22, 1999 01:45:01 am" To: peter@netplex.com.au (Peter Wemm) Date: Wed, 21 Apr 1999 13:51:39 -0400 (EDT) Cc: current@freebsd.org, stable@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm once wrote: > > Great work guys! It almost seems that -current is more stable than > > -stable! > Funny you should mention it. I've heard this from a number of people > over the last week.. One has even suggested using a particular > known-good 4.0 snapshot in preference to a 3.1-stable for a production > system...... Speaking of, when can we expect to see this wonderfull _stability_ improvement in -stable? I'm setting up a server here, and would rather have fixed NFS code in it... Yet, jumping to -current is officially wrong... Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 11: 2:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9E1BE1583F for ; Wed, 21 Apr 1999 11:02:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA07157; Wed, 21 Apr 1999 10:59:17 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 10:59:17 -0700 (PDT) From: Matthew Dillon Message-Id: <199904211759.KAA07157@apollo.backplane.com> To: Peter Wemm Cc: Matthew Reimer , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <19990421174502.ECEC61F2A@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Reimer wrote: :> Great work guys! It almost seems that -current is more stable than :> -stable! :> :> Matt : :Funny you should mention it. I've heard this from a number of people over :the last week.. One has even suggested using a particular known-good 4.0 :snapshot in preference to a 3.1-stable for a production system...... : :Cheers, :-Peter I think that people should stick with 3.x unless there is something in -current that they really need such as the fixed NFS. current's core is very solid now and getting better, but a lot of the peripheral stuff has undergone rapid change. The new bus structure, the new compiler, the kernel build setup, configuration changes, and so forth. It's hard to keep up with it. I expect it will settle down in the next month or so. Most of the bug fixes have been backported to -stable. Getting the new VM system into -stable ( which I want to do just after the 3.2 release ) is going to require brute force, though. Unfortunately, the most recent fixes to NFS fall into that category so NFS-centric installations may need to use -current. :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 11: 6:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id 271861543B for ; Wed, 21 Apr 1999 11:06:46 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id LAA10557; Wed, 21 Apr 1999 11:03:41 -0700 (PDT) Date: Wed, 21 Apr 1999 11:03:43 -0700 (PDT) From: Tom Bartol To: Peter Wemm Cc: Matthew Reimer , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <19990421174502.ECEC61F2A@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999, Peter Wemm wrote: > Matthew Reimer wrote: > > Great work guys! It almost seems that -current is more stable than > > -stable! > > > > Matt > > Funny you should mention it. I've heard this from a number of people over > the last week.. One has even suggested using a particular known-good 4.0 > snapshot in preference to a 3.1-stable for a production system...... > > Cheers, > -Peter And on this note -- is it planned to merge or backport these patches to -stable? We make very heavy use of NFS (udp, 100mb fxp0 fullduplex). We're using FreeBSD-3.1-STABLE as NFS clients to a big Auspex NS7000 NFS file server. We're in production mode in our lab and can't risk running -current on many of our machines so we've decided to run -stable on ALL of them (except perhaps MY machine but don't tell anyone ;-) Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 11:19: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from cc01du.unity.ncsu.edu (cc01du.unity.ncsu.edu [152.1.2.49]) by hub.freebsd.org (Postfix) with ESMTP id 242EC15832 for ; Wed, 21 Apr 1999 11:15:24 -0700 (PDT) (envelope-from rdkeys@unity.ncsu.edu) Received: (from rdkeys@localhost) by cc01du.unity.ncsu.edu (8.8.4/UC02Jan97) id OAA09041; Wed, 21 Apr 1999 14:12:45 -0400 (EDT) From: rdkeys@unity.ncsu.edu Message-Id: <199904211812.OAA09041@cc01du.unity.ncsu.edu> Subject: Re: solid NFS patch #6 avail for -current - need testers files) To: peter@netplex.com.au (Peter Wemm) Date: Wed, 21 Apr 1999 14:12:45 -0400 (EDT) Cc: freebsd-current@freebsd.org In-Reply-To: <19990421174502.ECEC61F2A@spinner.netplex.com.au> from "Peter Wemm" at Apr 22, 99 01:45:01 am X-Mailer: ELM [version 2.4 PL24/POP] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Matthew Reimer wrote: > > Great work guys! It almost seems that -current is more stable than > > -stable! > > Matt > > Funny you should mention it. I've heard this from a number of people over > the last week.. One has even suggested using a particular known-good 4.0 > snapshot in preference to a 3.1-stable for a production system...... > > Cheers, > -Peter Are there any particularly good snapshots one should try? I have a couple of spare boxes on the home net that I am willing to try or crash, for the fun of it. I was using the snap from about 3 weeks back on my home web server and it seems rock solid, but I am running rather plain hardware. Bob Keys To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 12: 3: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 786CD15903 for ; Wed, 21 Apr 1999 12:01:32 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id LAA04402; Wed, 21 Apr 1999 11:58:59 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904211858.LAA04402@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Freebsd-current@FreeBSD.ORG Cc: Nick Hibma Subject: USB keyboard attach function? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Apr 1999 11:58:59 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While playing over here with the USB stuff, I rebooted the system and disconnected the USB keyboard waited till the system was fully up and re-connected the USB keyboard which resulted in the system not attaching the USB keyboard. A side note, someone fixed syscons so it no longer panics if the atkbd device is not configured . In my case, I have a USB keyboard and a USB mouse connected to the system with no atkbdc nor atbkd device . It works like a charm now 8) -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 12:13: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4791215916 for ; Wed, 21 Apr 1999 12:11:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA98909; Wed, 21 Apr 1999 20:14:18 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 21 Apr 1999 20:14:18 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: Peter Wemm , Matthew Reimer , freebsd-current@freebsd.org Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904211759.KAA07157@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Matthew Dillon wrote: > :Matthew Reimer wrote: > :> Great work guys! It almost seems that -current is more stable than > :> -stable! > :> > :> Matt > : > :Funny you should mention it. I've heard this from a number of people over > :the last week.. One has even suggested using a particular known-good 4.0 > :snapshot in preference to a 3.1-stable for a production system...... > : > :Cheers, > :-Peter > > I think that people should stick with 3.x unless there is something in > -current that they really need such as the fixed NFS. current's core is > very solid now and getting better, but a lot of the peripheral stuff > has undergone rapid change. The new bus structure, the new compiler, the > kernel build setup, configuration changes, and so forth. It's hard > to keep up with it. I expect it will settle down in the next month or so. > > Most of the bug fixes have been backported to -stable. Getting the new > VM system into -stable ( which I want to do just after the 3.2 release ) > is going to require brute force, though. Unfortunately, the most recent > fixes to NFS fall into that category so NFS-centric installations may need > to use -current. I wonder if it would be too radical to suggest that the release cycle for 4.0 be *much* shorter than the 3.0 cycle. Maintaining two branches gets worse and worse as time goes on and it just becomes a waste of programmer time. If we are reasonably careful with the 4.0 tree, I think a 4.0 release could be branched off it after 3.2 or maybe 3.3. It seems to me that merging a complex set of changes (such as the VM fixes or the new-bus work) from 4.0 to the 3.x branch would tend to produce a system which was less stable than the 'natural' environment for the software which is being merged across. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 12:33:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1525615102 for ; Wed, 21 Apr 1999 12:33:39 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA07688; Wed, 21 Apr 1999 12:31:03 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 12:31:03 -0700 (PDT) From: Matthew Dillon Message-Id: <199904211931.MAA07688@apollo.backplane.com> To: Doug Rabson Cc: Peter Wemm , Matthew Reimer , freebsd-current@freebsd.org Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I wonder if it would be too radical to suggest that the release cycle for :4.0 be *much* shorter than the 3.0 cycle. Maintaining two branches gets :worse and worse as time goes on and it just becomes a waste of programmer :time. If we are reasonably careful with the 4.0 tree, I think a 4.0 :release could be branched off it after 3.2 or maybe 3.3. : :It seems to me that merging a complex set of changes (such as the VM fixes :or the new-bus work) from 4.0 to the 3.x branch would tend to produce a :system which was less stable than the 'natural' environment for the :software which is being merged across. : :-- :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 I think the existing release schedule is pretty good. Any faster and we might as well not have two branches at all. We really need a -current branch in order to make and test radical changes, and the companies & people who use FreeBSD need a -stable branch to keep production boxes up to date without having to bet the farm. We already have the ability to shortcut certain things simply by copying them from -current to -stable wholesale after we've determined their stability under -current. The issue here really is safety. I know some of you really want some of the things in -current to be backported into -stable more quickly, but you have to be patient. We can't compromise -stable's stability by acting too quickly. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 12:40:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id E8B07153C5 for ; Wed, 21 Apr 1999 12:39:57 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id PAA06520; Wed, 21 Apr 1999 15:37:21 -0400 (EDT) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id PAA18609; Wed, 21 Apr 1999 15:37:19 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904211759.KAA07157@apollo.backplane.com> Date: Wed, 21 Apr 1999 15:37:16 -0400 (EDT) From: John Baldwin To: Matthew Dillon Subject: Re: solid NFS patch #6 avail for -current - need testers files) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Apr-99 Matthew Dillon wrote: > Most of the bug fixes have been backported to -stable. Getting the new > VM system into -stable ( which I want to do just after the 3.2 release ) > is going to require brute force, though. Unfortunately, the most recent > fixes to NFS fall into that category so NFS-centric installations may need > to use -current. > > -Matt > Matthew Dillon > I'm curious, is there any plan to backport egcs to -stable or no? Also, as a side note: good thing we went with egcs, as it was just announced that egcs is now the official gcc. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 12:40:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id AB95015807 for ; Wed, 21 Apr 1999 12:40:36 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:fBXQV8Fi4HkjD3fxVYATCl1/tpl1jtD9@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id EAA19707; Thu, 22 Apr 1999 04:37:56 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id EAA10469; Thu, 22 Apr 1999 04:41:42 +0900 (JST) Message-Id: <199904211941.EAA10469@zodiac.mech.utsunomiya-u.ac.jp> To: Amancio Hasty Cc: Freebsd-current@freebsd.org, Nick Hibma , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Wed, 21 Apr 1999 11:58:59 MST." <199904211858.LAA04402@rah.star-gate.com> References: <199904211858.LAA04402@rah.star-gate.com> Date: Thu, 22 Apr 1999 04:41:41 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >While playing over here with the USB stuff, I rebooted the system and >disconnected the USB keyboard waited till the system was fully up >and re-connected the USB keyboard which resulted in the system >not attaching the USB keyboard. You need to be running usbd. In any case, we need some more work in the usb and ukbd driver code to be able to "detach" the ukbd driver while the system is running. >A side note, someone fixed syscons so it no longer panics if >the atkbd device is not configured . In my case, I have >a USB keyboard and a USB mouse connected to the >system with no atkbdc nor atbkd device . It works like >a charm now 8) Hmm, I don't see why ukbd and syscons paniced in your system before. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 12:50: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 0C78615450 for ; Wed, 21 Apr 1999 12:47:37 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA99022; Wed, 21 Apr 1999 20:50:15 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 21 Apr 1999 20:50:15 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: Peter Wemm , Matthew Reimer , freebsd-current@freebsd.org Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904211931.MAA07688@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Matthew Dillon wrote: > :I wonder if it would be too radical to suggest that the release cycle for > :4.0 be *much* shorter than the 3.0 cycle. Maintaining two branches gets > :worse and worse as time goes on and it just becomes a waste of programmer > :time. If we are reasonably careful with the 4.0 tree, I think a 4.0 > :release could be branched off it after 3.2 or maybe 3.3. > : > :It seems to me that merging a complex set of changes (such as the VM fixes > :or the new-bus work) from 4.0 to the 3.x branch would tend to produce a > :system which was less stable than the 'natural' environment for the > :software which is being merged across. > : > :-- > :Doug Rabson Mail: dfr@nlsystems.com > :Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > I think the existing release schedule is pretty good. Any faster and > we might as well not have two branches at all. We really need a > -current branch in order to make and test radical changes, and the > companies & people who use FreeBSD need a -stable branch to keep > production boxes up to date without having to bet the farm. > > We already have the ability to shortcut certain things simply by > copying them from -current to -stable wholesale after we've determined > their stability under -current. The issue here really is safety. I > know some of you really want some of the things in -current to be > backported into -stable more quickly, but you have to be patient. We > can't compromise -stable's stability by acting too quickly. I totally agree about not wanting to compromise the stability of our release branch. However as the codebases diverge (and 3.0 diverged pretty massively from 2.2) it will get harder and harder to merge significant improvements across from the development branch without compromising the stability which we are trying to maintain. All I'm saying (I think) is that we shouldn't allow the 4.0 release cycle to stretch out to 2 years like the 3.0 cycle did (discounting 3.0 as a beta release). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 12:54: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 8828A1586E for ; Wed, 21 Apr 1999 12:53:02 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA04669; Wed, 21 Apr 1999 12:50:27 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904211950.MAA04669@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA Cc: Freebsd-current@freebsd.org, Nick Hibma Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Thu, 22 Apr 1999 04:41:41 +0900." <199904211941.EAA10469@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Apr 1999 12:50:27 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't worry quite a few fixes went into syscons so it is no longer isa centric. > > >While playing over here with the USB stuff, I rebooted the system and > >disconnected the USB keyboard waited till the system was fully up > >and re-connected the USB keyboard which resulted in the system > >not attaching the USB keyboard. > > You need to be running usbd. > > In any case, we need some more work in the usb and ukbd driver code to > be able to "detach" the ukbd driver while the system is running. > > >A side note, someone fixed syscons so it no longer panics if > >the atkbd device is not configured . In my case, I have > >a USB keyboard and a USB mouse connected to the > >system with no atkbdc nor atbkd device . It works like > >a charm now 8) > > Hmm, I don't see why ukbd and syscons paniced in your system before. > > Kazu > > -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 13:13: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9C2CA15440; Wed, 21 Apr 1999 13:12:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA08036; Wed, 21 Apr 1999 13:09:09 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 13:09:09 -0700 (PDT) From: Matthew Dillon Message-Id: <199904212009.NAA08036@apollo.backplane.com> To: Mikhail Teterin Cc: peter@netplex.com.au (Peter Wemm), current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <199904211751.NAA31922@misha.cisco.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Speaking of, when can we expect to see this wonderfull _stability_ :improvement in -stable? I'm setting up a server here, and would :rather have fixed NFS code in it... Yet, jumping to -current is :officially wrong... Thanks! : : -mi Well, you already see a lot of the pure bug fixes being backported. What you don't see in -stable are the bug fixes that also depend on the rewritten portions of the system, nor do you see the rewritten portions of the system themselves. The latest NFS patch is borderline -- it would be possible to backport in time enough for the 3.2 deadline, but it wouldn't be fun. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 13:23:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id A893D1588B for ; Wed, 21 Apr 1999 13:22:02 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id QAA26690; Wed, 21 Apr 1999 16:19:23 -0400 (EDT) Message-Id: <3.0.5.32.19990421161837.01beabf0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 21 Apr 1999 16:18:37 -0400 To: Matthew Dillon From: Mike Tancsa Subject: Re: solid NFS patch #6 avail for -current - need testers files) Cc: current@FreeBSD.ORG In-Reply-To: <199904212009.NAA08036@apollo.backplane.com> References: <199904211751.NAA31922@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:09 PM 4/21/99 -0700, Matthew Dillon wrote: >:Speaking of, when can we expect to see this wonderfull _stability_ >:improvement in -stable? I'm setting up a server here, and would >:rather have fixed NFS code in it... Yet, jumping to -current is >:officially wrong... Thanks! >: >: -mi > > Well, you already see a lot of the pure bug fixes being backported. > What you don't see in -stable are the bug fixes that also depend on the > rewritten portions of the system, nor do you see the rewritten portions > of the system themselves. The latest NFS patch is borderline -- it > would be possible to backport in time enough for the 3.2 deadline, but > it wouldn't be fun. Hi, Just wondering if these changes also have the side effect of fixing the nmap problem that crashes 3.x boxes ? i.e. as you wrote back on 3/4/99 > The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing > the file, but then it does some really weird crap when dealing with > larger files. > > It's the most idiotic code I've ever seen. The code uses a PRIVATE+RW > mmap() until it gets to odd point in the file, at which point it read()'s > additional information from the file into the mapped space ( that might > contain a previous mmap'd portion of the file ). > > So what happens is this: > > * read() call > * shared lock obtained on vnode > > ( some other process attempts to get shared lock on vnode and > succeeds... for example, a namei operation is attempted by > another grep ) > > * access MMAP'd area > * exclusive lock attempt obtained on same vnode. This blocks because > some other process has a shared lock on the vnode. > > ( the other process then attempts to get an exclusive lock on the > vnode this blocks. > > Deadlock. > > Even worse, the gnu grep does not bother munmap()'ing the space so, in > fact, the deadlock can occur between two unrelated files as well as with > the same file. This is the more likely deadlock scenario. > > The solution is more difficult. We could hack an exception for PRIVATE > mmap's... there really is no need for the vm_fault code to lock the vnode. > Howver, other situations can occur where this hack would not work. > > This is 'kinda a known problem' in FreeBSD. We really need to find a > solution to it. Other similar deadlocks can occur if you mmap() one file > and read() or write() data from it to another file, and vise versa at > the same time. > > Personally, I think the only real solution is to make vn_read() and > vn_write() lock the uio space as well as the vnode being read or > written. It would have to do it in the right order, and it would have > to deal with the situation where the uio space covers multiple vnodes. > > Alternately, vnodes need to be redesigned without these fraggin > all-encompassing locks for data R+W ops. > > -Matt > >(kgdb) back >#0 mi_switch () at ../../kern/kern_synch.c:827 >#1 0xf0151919 in tsleep (ident=0xf0a2e500, priority=0x8, wmesg=0xf0263a9c "inode", timo=0x0) > at ../../kern/kern_synch.c:443 >#2 0xf014b774 in acquire (lkp=0xf0a2e500, extflags=0x1000040, wanted=0x700) at ../../kern/kern_lock.c:145 >#3 0xf014b835 in lockmgr (lkp=0xf0a2e500, flags=0x1030041, interlkp=0xf51719b0, p=0xf5151200) > at ../../kern/kern_lock.c:209 >#4 0xf0171df0 in vop_stdlock (ap=0xf5176b94) at ../../kern/vfs_default.c:210 >#5 0xf0204b39 in ufs_vnoperate (ap=0xf5176b94) at ../../ufs/ufs/ufs_vnops.c:2309 >#6 0xf017aba4 in vn_lock (vp=0xf5171940, flags=0x1030041, p=0xf5151200) at vnode_if.h:811 >#7 0xf01747b0 in vget (vp=0xf5171940, flags=0x1020041, p=0xf5151200) at ../../kern/vfs_subr.c:1348 >#8 0xf0212f1e in vnode_pager_lock (object=0xf02af2b4) at ../../vm/vnode_pager.c:960 >#9 0xf0206a56 in vm_fault (map=0xf51497c0, vaddr=0x805d000, fault_type=0x3, fault_flags=0x8) > at ../../vm/vm_fault.c:243 >#10 0xf022aebe in trap_pfault (frame=0xf5176d14, usermode=0x0, eva=0x805d038) at ../../i386/i386/trap.c:816 >#11 0xf022ab92 in trap (frame={tf_es = 0x10, tf_ds = 0x10, tf_edi = 0x805d000, tf_esi = 0xf223e000, > tf_ebp = 0xf5176e0c, tf_isp = 0xf5176d3c, tf_ebx = 0x1060, tf_edx = 0x0, tf_ecx = 0x700, tf_eax = 0x0, > tf_trapno = 0xc, tf_err = 0x3, tf_eip = 0xf0229ce4, tf_cs = 0x8, tf_eflags = 0x10287, tf_esp = 0xffff1272, > tf_ss = 0xffff0000}) at ../../i386/i386/trap.c:437 >#12 0xf0229ce4 in fastmove_loop () >#13 0xf0229b2b in i586_copyout () >#14 0xf01fd707 in ffs_read (ap=0xf5176ef0) at ../../ufs/ufs/ufs_readwrite.c:289 >#15 0xf017a689 in vn_read (fp=0xf09dda80, uio=0xf5176f38, cred=0xf09ef480) at vnode_if.h:303 >#16 0xf015a757 in read (p=0xf5151200, uap=0xf5176f94) at ../../kern/sys_generic.c:121 >#17 0xf022b4a0 in syscall (frame={tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x0, tf_esi = 0x8000, tf_ebp = 0xefbf85c8, > tf_isp = 0xf5176fe4, tf_ebx = 0xffffffff, tf_edx = 0x8059000, tf_ecx = 0xa0000, tf_eax = 0x3, > tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x280b303c, tf_cs = 0x1f, tf_eflags = 0x206, tf_esp = 0xefbf85a0, > tf_ss = 0x2f}) at ../../i386/i386/trap.c:1100 >#18 0xf0220dcc in Xint0x80_syscall () >#19 0x804dc46 in ?? () >#20 0x804e85c in ?? () >#21 0x8048f7d in ?? () >(kgdb) > > > ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 13:30:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id CB77615835 for ; Wed, 21 Apr 1999 13:29:25 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id NAA09003 for ; Wed, 21 Apr 1999 13:26:57 -0700 (PDT) Message-ID: <371E3505.1F7B471B@seattleu.edu> Date: Wed, 21 Apr 1999 13:28:53 -0700 From: Eric Hodel X-Mailer: Mozilla 4.51 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Current@freebsd.org Subject: fxp driver and dhclient Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When running dhclient with the kernel fxp driver I get a kernel panic in ifconfig. Might be some other things I enabled in the kernel, but I haven't double-checked yet. -- Eric Hodel hodeleri@seattleu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 13:36:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4ED6315903 for ; Wed, 21 Apr 1999 13:32:23 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA08215; Wed, 21 Apr 1999 13:29:52 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 13:29:52 -0700 (PDT) From: Matthew Dillon Message-Id: <199904212029.NAA08215@apollo.backplane.com> To: Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <199904211751.NAA31922@misha.cisco.com> <3.0.5.32.19990421161837.01beabf0@staff.sentex.ca> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, :Just wondering if these changes also have the side effect of fixing the :nmap problem that crashes 3.x boxes ? i.e. as you wrote back on 3/4/99 : : :> The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing :> the file, but then it does some really weird crap when dealing with :> larger files. :> I believe this was fixed in -current. I don't know if it was backported to -stable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 13:41: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (unknown [206.29.49.3]) by hub.freebsd.org (Postfix) with ESMTP id 911CE15876 for ; Wed, 21 Apr 1999 13:40:56 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id QAA25578; Wed, 21 Apr 1999 16:39:47 -0400 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma025565; Wed, 21 Apr 99 20:38:48 GMT Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id QAA17795; Wed, 21 Apr 1999 16:37:26 -0400 (EDT) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.3/8.8.8) id QAA83999; Wed, 21 Apr 1999 16:37:28 -0400 (EDT) Date: Wed, 21 Apr 1999 16:37:28 -0400 (EDT) Message-Id: <199904212037.QAA83999@jabberwock.rstcorp.com> From: "Viren R. Shah" To: Kazutaka YOKOTA Cc: Amancio Hasty , Freebsd-current@freebsd.org, Nick Hibma Subject: Re: USB keyboard attach function? In-Reply-To: <199904211941.EAA10469@zodiac.mech.utsunomiya-u.ac.jp> References: <199904211858.LAA04402@rah.star-gate.com> <199904211941.EAA10469@zodiac.mech.utsunomiya-u.ac.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Kazu" == Kazutaka YOKOTA writes: Kazu> You need to be running usbd. Kazu> In any case, we need some more work in the usb and ukbd driver code to Kazu> be able to "detach" the ukbd driver while the system is running. Amancio and Nick helped me get my system with only a USB keyboard and USB mouse up and running. Right now I'm pretty happy with the way it is now. My only concern is that the FreeBSD bootloader does not appear to see keystrokes from the USB keyboard (which kinda makes it difficult to switch OSes on an USB only system). Kazu> Kazu [Amancio: I'm currently building world in preparation for compiling a kernel without atkbdc and atkbd, as you suggested] Viren -- Viren R. Shah "You are about as sharp as a sack of wet mice" -- Foghorn Leghorn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 13:46: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id 9B24B15835 for ; Wed, 21 Apr 1999 13:45:41 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id OAA02148 for ; Wed, 21 Apr 1999 14:43:03 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Wed, 21 Apr 1999 14:43:03 -0600 (MDT) From: Brian Handy To: freebsd-current@freebsd.org Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of upgrading to -current from 3.x-STABLE, I was just wondering -- does the new EGCS imply that things like apps2go Motif won't link properly against a 4.x-CURRENT world now? It's things like this that will hold me back, if they indeedy are a problem. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 13:53:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id BD7C715907 for ; Wed, 21 Apr 1999 13:53:14 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id QAA05130; Wed, 21 Apr 1999 16:50:42 -0400 (EDT) Message-Id: <3.0.5.32.19990421164957.00fab1f0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 21 Apr 1999 16:49:57 -0400 To: Matthew Dillon From: Mike Tancsa Subject: Re: solid NFS patch #6 avail for -current - need testers files) Cc: current@FreeBSD.ORG In-Reply-To: <199904212029.NAA08215@apollo.backplane.com> References: <199904211751.NAA31922@misha.cisco.com> <3.0.5.32.19990421161837.01beabf0@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:29 PM 4/21/99 -0700, Matthew Dillon wrote: > >:Hi, >:Just wondering if these changes also have the side effect of fixing the >:nmap problem that crashes 3.x boxes ? i.e. as you wrote back on 3/4/99 >: >: >:> The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing >:> the file, but then it does some really weird crap when dealing with >:> larger files. >:> > > I believe this was fixed in -current. I don't know if it was backported > to -stable. Unfortunately no... It can still lockup a 3.x machine. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 13:57:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id E17511592D for ; Wed, 21 Apr 1999 13:55:11 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id NAA05084; Wed, 21 Apr 1999 13:52:32 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904212052.NAA05084@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Viren R. Shah" Cc: Kazutaka YOKOTA , Freebsd-current@freebsd.org, Nick Hibma Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Wed, 21 Apr 1999 16:37:28 EDT." <199904212037.QAA83999@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Apr 1999 13:52:32 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, >is now. My only concern is that the FreeBSD bootloader does not appear If you are running -current as of at least last nite you will not have any problems with the bootloader and your USB keyboard in fact I just rebooted my test system and was able to select the kernel to boot; previously, you are right the bootloader didn't work with a USB keyboard only system. -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 14: 7:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (unknown [206.29.49.3]) by hub.freebsd.org (Postfix) with ESMTP id 1447915096 for ; Wed, 21 Apr 1999 14:03:57 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id RAA25785; Wed, 21 Apr 1999 17:02:47 -0400 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma025781; Wed, 21 Apr 99 21:02:45 GMT Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id RAA18175; Wed, 21 Apr 1999 17:01:24 -0400 (EDT) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.3/8.8.8) id RAA84753; Wed, 21 Apr 1999 17:01:25 -0400 (EDT) Date: Wed, 21 Apr 1999 17:01:25 -0400 (EDT) Message-Id: <199904212101.RAA84753@jabberwock.rstcorp.com> From: "Viren R. Shah" To: Amancio Hasty Cc: Kazutaka YOKOTA , Freebsd-current@freebsd.org, Nick Hibma Subject: Re: USB keyboard attach function? In-Reply-To: <199904212052.NAA05084@rah.star-gate.com> References: <199904212037.QAA83999@jabberwock.rstcorp.com> <199904212052.NAA05084@rah.star-gate.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Amancio" == Amancio Hasty writes: Amancio> Hi, >> is now. My only concern is that the FreeBSD bootloader does not appear Amancio> If you are running -current as of at least last nite you Amancio> will not have any problems with the bootloader and your USB Amancio> keyboard in fact I just rebooted my test system and was able Amancio> to select the kernel to boot; previously, you are right the Amancio> bootloader didn't work with a USB keyboard only system. You are right! I just rebooted after a make world and a new kernel, and it worked!!! Cool. Viren -- Viren R. Shah "You are about as sharp as a sack of wet mice" -- Foghorn Leghorn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 14:25:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id EAC13158F0 for ; Wed, 21 Apr 1999 14:24:40 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40329>; Thu, 22 Apr 1999 07:08:15 +1000 Date: Thu, 22 Apr 1999 07:22:02 +1000 From: Peter Jeremy Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) To: dillon@apollo.backplane.com Cc: current@FreeBSD.ORG Message-Id: <99Apr22.070815est.40329@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: [Partial writes] > I finally gave up on it. What NFS does now is optimize only two > write situations: ... And (2) piecemeal writes in the write-append > case. I'm nothing like an NFS expert, so I may be talking through my hat, but... I presume NFS correctly supports O_APPEND semantics for multiple clients (as seen from the server). In this case, the optimization only works when there's only one client machine (though possibly multiple processes on that machine) is using write+O_APPEND. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 14:25:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 07CC31590E; Wed, 21 Apr 1999 14:24:55 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id WAA96498; Wed, 21 Apr 1999 22:22:20 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 21 Apr 1999 22:11:55 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199904202334.QAA00567@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 21 Apr 1999 22:11:53 +0000 To: Matthew Dillon From: Bob Bishop Subject: Re: solid NFS patch #6 avail for -current - need testers files) Cc: Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 4:34 pm -0700 20/4/99, Matthew Dillon wrote: > NFS patch #6 is now available for -current.[etc] Looks real good here. Been running two servers continuously building the world with their /usr/obj cross-mounted on each other. Oh, and one of them is SMP running -j8. Great job! -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 15:59:31 1999 Delivered-To: freebsd-current@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 47507153C2; Wed, 21 Apr 1999 15:58:00 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from alphard (alphard [128.130.111.37]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id AAA24822; Thu, 22 Apr 1999 00:51:00 +0200 (MET DST) Date: Thu, 22 Apr 1999 00:51:03 +0200 (MET DST) From: Gerald Pfeifer To: Matthew Dillon Cc: Mikhail Teterin , Peter Wemm , current@freebsd.org, stable@freebsd.org Subject: NFSv3 seriously broken in 3.1 In-Reply-To: <199904212009.NAA08036@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm only subscribed to freebsd-stable, so I missed the original thread, but reading the lines below, a question arises: On Wed, 21 Apr 1999, Matthew Dillon wrote: > Well, you already see a lot of the pure bug fixes being backported. > What you don't see in -stable are the bug fixes that also depend on the > rewritten portions of the system, nor do you see the rewritten portions > of the system themselves. The latest NFS patch is borderline [...] Are you aware that NFSv3 seems to be seriously broken, at least for FreeBSD 3.1 clients connecting to a Solaris 2.6 server? Has that been fixed for current resp. stable? If not, what can I do to help getting this fixed? Symptoms are the following: We upgraded a perfectly running 2.2.7 client to 3.1, and out of a sudden NFS performed sluggish, sometimes even hanging for ten, twenty seconds, even five minutes or more. Adding the NFSv2 compatibility option to the AMD tables solved the problem. 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-current" in the body of the message From owner-freebsd-current Wed Apr 21 17:10:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa16-17.ix.netcom.com [207.93.148.145]) by hub.freebsd.org (Postfix) with ESMTP id 4B328158AA for ; Wed, 21 Apr 1999 17:09:59 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id RAA00359; Wed, 21 Apr 1999 17:07:29 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Wed, 21 Apr 1999 17:07:29 -0700 (PDT) Message-Id: <199904220007.RAA00359@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@freebsd.org Subject: new-bus Success Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running 4.0-current SMP, cvsup today and built an hour ago. Everything seems OK. Great work. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 18:22: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5A3D815896 for ; Wed, 21 Apr 1999 18:21:32 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA18942; Wed, 21 Apr 1999 18:17:40 -0700 (PDT) (envelope-from obrien) Message-ID: <19990421181740.A18926@nuxi.com> Date: Wed, 21 Apr 1999 18:17:40 -0700 From: "David O'Brien" To: John Baldwin Cc: freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) Reply-To: obrien@NUXI.com References: <199904211759.KAA07157@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from John Baldwin on Wed, Apr 21, 1999 at 03:37:16PM -0400 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm curious, is there any plan to backport egcs to -stable or no? No. > Also, as a side note: good thing we went with egcs, as it was just > announced that egcs is now the official gcc. Yep, I had some inside info that this was probably going to happen. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 18:55:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CD72C15281 for ; Wed, 21 Apr 1999 18:55:02 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA46125; Wed, 21 Apr 1999 18:52:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Peter Wemm Cc: Matthew Reimer , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Thu, 22 Apr 1999 01:45:01 +0800." <19990421174502.ECEC61F2A@spinner.netplex.com.au> Date: Wed, 21 Apr 1999 18:52:08 -0700 Message-ID: <46123.924745928@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Funny you should mention it. I've heard this from a number of people over > the last week.. One has even suggested using a particular known-good 4.0 > snapshot in preference to a 3.1-stable for a production system...... That's a little foolish since we've still not found all the egcs optimizer bugs and whatnot; didn't you guys see the one Luigi found the other day for ftpd? Now *that* had to be some obscure debugging work! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 18:59:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3A9971584F; Wed, 21 Apr 1999 18:59:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA46170; Wed, 21 Apr 1999 18:56:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: mi@aldan.algebra.com Cc: peter@netplex.com.au (Peter Wemm), current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Wed, 21 Apr 1999 13:51:39 EDT." <199904211751.NAA31922@misha.cisco.com> Date: Wed, 21 Apr 1999 18:56:24 -0700 Message-ID: <46168.924746184@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Speaking of, when can we expect to see this wonderfull _stability_ > improvement in -stable? I'm setting up a server here, and would Usually when we're sure it's not a pessimization in other ways. I think people are getting just a bit prematurely excited here, not to knock Matt's good work or anything but I think even he would be the last to jump up and down saying "NFS is fixed! It's totally perfect now!" as some younger, less wise heads are currently saying. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 19:20: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2072D153FF for ; Wed, 21 Apr 1999 19:19:51 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA46267; Wed, 21 Apr 1999 19:16:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Doug Rabson Cc: Matthew Dillon , Peter Wemm , Matthew Reimer , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Wed, 21 Apr 1999 20:14:18 BST." Date: Wed, 21 Apr 1999 19:16:08 -0700 Message-ID: <46265.924747368@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I wonder if it would be too radical to suggest that the release cycle for > 4.0 be *much* shorter than the 3.0 cycle. Maintaining two branches gets > worse and worse as time goes on and it just becomes a waste of programmer > time. If we are reasonably careful with the 4.0 tree, I think a 4.0 What's your definition of "much" in this case? I also disagree that the multi-branch model is a "waste" of programmer time since it's what keeps us able to have an experimental line of development at all. To programmers, that's pretty important. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 19:23:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BE17E151DB for ; Wed, 21 Apr 1999 19:22:21 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA46308; Wed, 21 Apr 1999 19:19:23 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: John Baldwin Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Wed, 21 Apr 1999 15:37:16 EDT." Date: Wed, 21 Apr 1999 19:19:23 -0700 Message-ID: <46306.924747563@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm curious, is there any plan to backport egcs to -stable or no? Also, as a There are no plans at this time to merge egcs over. This will only happen if time and hindsight prove egcs to be of low enough impact that it's suitable -stable material. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 19:29:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3F65F1585A for ; Wed, 21 Apr 1999 19:28:07 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA46335; Wed, 21 Apr 1999 19:24:34 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Doug Rabson Cc: Matthew Dillon , Peter Wemm , Matthew Reimer , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Wed, 21 Apr 1999 20:50:15 BST." Date: Wed, 21 Apr 1999 19:24:34 -0700 Message-ID: <46333.924747874@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > All I'm saying (I think) is that we shouldn't allow the 4.0 release cycle > to stretch out to 2 years like the 3.0 cycle did (discounting 3.0 as a > beta release). No argument there - the current schedule is 12 months for 4.0. 2 years far too long and merely the result of unforseen delays and more than a little paralysis over the issue. This caused a lot of soul-searching in core over our development practices, hopefully enough that we won't repeat that particular painful experience. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 19:58:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D28F614E14 for ; Wed, 21 Apr 1999 19:58:26 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA05780; Thu, 22 Apr 1999 12:25:26 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904212037.QAA83999@jabberwock.rstcorp.com> Date: Thu, 22 Apr 1999 12:33:40 +0930 (CST) From: "Daniel O'Connor" To: "Viren R. Shah" Subject: Re: USB keyboard attach function? Cc: Nick Hibma , Freebsd-current@FreeBSD.ORG, Amancio Hasty , Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Apr-99 Viren R. Shah wrote: > Kazu> be able to "detach" the ukbd driver while the system is running. > Amancio and Nick helped me get my system with only a USB keyboard and > USB mouse up and running. Right now I'm pretty happy with the way it > is now. My only concern is that the FreeBSD bootloader does not appear > to see keystrokes from the USB keyboard (which kinda makes it > difficult to switch OSes on an USB only system). Isn't that a BIOS problem? I know the BIOSen I have here have an option to support USB keyboards etc... --- 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-current" in the body of the message From owner-freebsd-current Wed Apr 21 20:43:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (Postfix) with ESMTP id 3F40C15555 for ; Wed, 21 Apr 1999 20:43:26 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id MAA01390 for ; Thu, 22 Apr 1999 12:40:55 +0900 (JST) To: current@FreeBSD.org Subject: newbus resource manager From: KATO Takenori X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990422124055N.kato@gneiss.eps.nagoya-u.ac.jp> Date: Thu, 22 Apr 1999 12:40:55 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can newbus resource manager manage discontinuouse I/O port? Many PC-98 devices use discontinuous I/O port like: 0x00d0, 0x10d0, 0x20d0, 0x30d0, 0x40d0, ..., 0xf0d0 Current API seems to assume contiguity and not to be able to manage such I/O port addresses. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 3.1: Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 2.2.8: Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 20:56:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from neuman.interaccess.com (neuman.interaccess.com [207.70.126.130]) by hub.freebsd.org (Postfix) with ESMTP id 32FAE15946 for ; Wed, 21 Apr 1999 20:55:04 -0700 (PDT) (envelope-from pulpitconfession@yahoo.com) Received: from bsbpub (d208.focal2.interaccess.com [207.208.137.208]) by neuman.interaccess.com (8.9.0/8.9.0) with SMTP id WAA02149; Wed, 21 Apr 1999 22:52:00 -0500 (CDT) Date: Wed, 21 Apr 1999 22:52:00 -0500 (CDT) Message-Id: <199904220352.WAA02149@neuman.interaccess.com> From: Book_Sale To: Subject: Book - "Pulpit Confessions: Exposing The Black Church" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CALL TODAY TO ORDER THIS BOOK - (800) 305-1458 [24hrs.] -------------------------------------------------- "What nobody had the nerve to tell you until now." "Real evidence of what you only suspected." "The Black Church as you've never known it before." Pulpit Confessions: Exposing The Black Church by N. Moore $16.00 ISBN: 0-9658299-2-8 _____________________________ Pulpit Confessions: Exposing The Black Church is an honest, behind the scenes look at the African-American church. The author spent a decade as a preacher and pastor in the black church and is actually betraying an unofficial code of silence by writing this book. The author began ministry in his teens and was pastoring by his early twenties. He speaks frankly about his and other ministers' odysseys from sincere, well intentioned prodigies to cynical, sinful, showman. He soon discovered that things in the church were not as they seemed. In this ground-breaking book, he describes a secular and often profane ministerial community that is often shrouded in pseudo holiness. He exposes the thoughts and motivations of both ministers and congregations and their degenerate power struggles which often turn violent. He pulls no punches when he untangles the myths, unravels the mystique and reveals the secrets of the Black Church. _____________________________ ORDERING INFORMATION **Book will be sent via COD.** **COD charges are free for a limited time*** Pulpit Confessions: Exposing The Black Church by N. Moore $16.00 ISBN: 0-9658299-2-8 $3.00 Shipping _____________________________ Order By Phone 800-305-1458 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 21: 7: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id E869E158F7 for ; Wed, 21 Apr 1999 21:06:59 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id VAA07662; Wed, 21 Apr 1999 21:04:06 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904220404.VAA07662@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" Cc: "Viren R. Shah" , Nick Hibma , Freebsd-current@FreeBSD.ORG, Kazutaka YOKOTA Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Thu, 22 Apr 1999 12:33:40 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Apr 1999 21:04:06 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem was not really a bios problem not sure what the guys did to fix the boot loader probably switch to using a dos int function to access the keyboard from the boot loader. -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 21:11:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id AFEFA158CA for ; Wed, 21 Apr 1999 21:11:01 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA06202; Thu, 22 Apr 1999 13:38:12 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904220404.VAA07662@rah.star-gate.com> Date: Thu, 22 Apr 1999 13:46:27 +0930 (CST) From: "Daniel O'Connor" To: Amancio Hasty Subject: Re: USB keyboard attach function? Cc: Kazutaka YOKOTA Cc: Kazutaka YOKOTA , Freebsd-current@FreeBSD.ORG, Nick Hibma , "Viren R. Shah" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Apr-99 Amancio Hasty wrote: > The problem was not really a bios problem not sure what the guys > did to fix the boot loader probably switch to using a dos int function > to access the keyboard from the boot loader. Hmm.. what does it do now? Just talk to the keyboard controller directly? The BIOS I have here have an option 'Port 60/64 emulation' in the USB related section... --- 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-current" in the body of the message From owner-freebsd-current Wed Apr 21 21:18: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 5E0C914EE7 for ; Wed, 21 Apr 1999 21:17:48 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id AAA21542; Thu, 22 Apr 1999 00:14:43 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904220414.AAA21542@kot.ne.mediaone.net> Subject: Re: USB keyboard attach function? In-Reply-To: <199904212037.QAA83999@jabberwock.rstcorp.com> from "Viren R. Shah" at "Apr 21, 1999 04:37:28 pm" To: hasty@rah.star-gate.com, Freebsd-current@FreeBSD.ORG Date: Thu, 22 Apr 1999 00:14:42 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Wed, 21 Apr 1999 21:25:52 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id NAA14404; Thu, 22 Apr 1999 13:23:04 +0900 (JST) Message-ID: <371E9DC6.4FD6CDEC@newsguy.com> Date: Thu, 22 Apr 1999 12:55:50 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Peter Wemm , Matthew Reimer , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <46123.924745928@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > Funny you should mention it. I've heard this from a number of people over > > the last week.. One has even suggested using a particular known-good 4.0 > > snapshot in preference to a 3.1-stable for a production system...... > > That's a little foolish since we've still not found all the egcs > optimizer bugs and whatnot; didn't you guys see the one Luigi found > the other day for ftpd? Now *that* had to be some obscure debugging > work! :-) Clearly, that goes to show Luigi must have no life... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22: 0: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 9CA7F14F95 for ; Wed, 21 Apr 1999 22:00:00 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id VAA65522; Wed, 21 Apr 1999 21:54:41 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904220454.VAA65522@troutmask.apl.washington.edu> Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <371E9DC6.4FD6CDEC@newsguy.com> from "Daniel C. Sobral" at "Apr 22, 1999 12:55:50 pm" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 21 Apr 1999 21:54:41 -0700 (PDT) Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), peter@netplex.com.au (Peter Wemm), mreimer@vpop.net (Matthew Reimer), freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel C. Sobral wrote: > "Jordan K. Hubbard" wrote: > > > > > Funny you should mention it. I've heard this from a number of people over > > > the last week.. One has even suggested using a particular known-good 4.0 > > > snapshot in preference to a 3.1-stable for a production system...... > > > > That's a little foolish since we've still not found all the egcs > > optimizer bugs and whatnot; didn't you guys see the one Luigi found > > the other day for ftpd? Now *that* had to be some obscure debugging > > work! :-) > > Clearly, that goes to show Luigi must have no life... :-) > "Luigi" is an interesting spelling of "Louqi". The bug was actually in libalias. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22: 9:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (as1-p86.tfs.net [139.146.210.86]) by hub.freebsd.org (Postfix) with ESMTP id 0159D151EC for ; Wed, 21 Apr 1999 22:08:50 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id AAA22553; Thu, 22 Apr 1999 00:06:04 -0500 (CDT) From: Jim Bryant Message-Id: <199904220506.AAA22553@argus.tfs.net> Subject: Re: Book - "Pulpit Confessions: Exposing The Black Church" In-Reply-To: <199904220352.WAA02149@neuman.interaccess.com> from Book_Sale at "Apr 21, 99 10:52:00 pm" To: pulpitconfession@yahoo.com (Book_Sale) Date: Thu, 22 Apr 1999 00:06:03 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG what is this shit? damn, i need to tell my uncle, he used to be an assemblies of god preacher, and he has enough choice words on those racists to fill a book... this shit doesn't belong here. In reply: > CALL TODAY TO ORDER THIS BOOK - (800) 305-1458 [24hrs.] > -------------------------------------------------- > "What nobody had the nerve to tell you until now." > "Real evidence of what you only suspected." > "The Black Church as you've never known it before." > > > Pulpit Confessions: > Exposing The Black Church > > by > N. Moore > > $16.00 > ISBN: 0-9658299-2-8 > _____________________________ > Pulpit Confessions: Exposing The Black Church is an honest, > behind the scenes look at the African-American church. The > author spent a decade as a preacher and pastor in the black > church and is actually betraying an unofficial code of > silence by writing this book. > [rest of racist drivel deleted] jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22:10:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3BFB41595C for ; Wed, 21 Apr 1999 22:10:00 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA46982; Wed, 21 Apr 1999 22:07:11 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Steve Kargl Cc: dcs@newsguy.com (Daniel C. Sobral), peter@netplex.com.au (Peter Wemm), mreimer@vpop.net (Matthew Reimer), freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Wed, 21 Apr 1999 21:54:41 PDT." <199904220454.VAA65522@troutmask.apl.washington.edu> Date: Wed, 21 Apr 1999 22:07:11 -0700 Message-ID: <46980.924757631@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Luigi" is an interesting spelling of "Louqi". Or even "Luoqi", as his name is actually spelled. :-) Sorry, Mr. Chen, for the transposition of you and Luigi. Temporary brain fade! :) > The bug was actually in libalias. Yes, also correct. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22:12:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8172A15222; Wed, 21 Apr 1999 22:12:17 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA10257; Wed, 21 Apr 1999 22:09:47 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 22:09:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199904220509.WAA10257@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: mi@aldan.algebra.com, peter@netplex.com.au (Peter Wemm), current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <46168.924746184@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Speaking of, when can we expect to see this wonderfull _stability_ :> improvement in -stable? I'm setting up a server here, and would : :Usually when we're sure it's not a pessimization in other ways. I :think people are getting just a bit prematurely excited here, not to :knock Matt's good work or anything but I think even he would be the :last to jump up and down saying "NFS is fixed! It's totally perfect :now!" as some younger, less wise heads are currently saying. :-) : :- Jordan NFS is definitely not fixed. NFS/TCP is still broken, the leasing stuff is still broken, and probably a bunch of other esoteric situations will cause breakage. There are still issues with stale file handles. There is no locking support ( however much NFS locking is a bad idea in general ). But it's *much* better then it was before'. The patch is certainly good enough to commit into -current. It is not commitable to -stable, though, because it depends on -current's VM & VFS/BIO system. From my point of view, NFS/VM/VFS/BIO is now sitting where it *should* have been sitting a year ago if people had been paying more attention to it. If this were a Matt Dillon project, I would be sitting at my first 'beta' release :-( and everything up to this point would have been alpha. We have a long ways to go, folks. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22:14:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 50FD9151EC for ; Wed, 21 Apr 1999 22:14:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA10273; Wed, 21 Apr 1999 22:11:39 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 22:11:39 -0700 (PDT) From: Matthew Dillon Message-Id: <199904220511.WAA10273@apollo.backplane.com> To: Steve Kargl Cc: dcs@newsguy.com (Daniel C. Sobral), jkh@zippy.cdrom.com (Jordan K. Hubbard), peter@netplex.com.au (Peter Wemm), mreimer@vpop.net (Matthew Reimer), freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <199904220454.VAA65522@troutmask.apl.washington.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > work! :-) :> :> Clearly, that goes to show Luigi must have no life... :-) :> : :"Luigi" is an interesting spelling of "Louqi". : :The bug was actually in libalias. : :-- :Steve Luoqi found a bug in the compiler's optimizer. I presume someone has/will commit a change to libalias to work around it, and hopefully Luoqi notified the EGCS people. This sort of optimizer bug is usually fairly easy to fix given demonstration code, and Luoqi presented demonstration code. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22:23: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 3067F14F65 for ; Wed, 21 Apr 1999 22:23:00 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id WAA65616; Wed, 21 Apr 1999 22:17:42 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904220517.WAA65616@troutmask.apl.washington.edu> Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904220511.WAA10273@apollo.backplane.com> from Matthew Dillon at "Apr 21, 1999 10:11:39 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 21 Apr 1999 22:17:42 -0700 (PDT) Cc: dcs@newsguy.com (Daniel C. Sobral), jkh@zippy.cdrom.com (Jordan K. Hubbard), peter@netplex.com.au (Peter Wemm), mreimer@vpop.net (Matthew Reimer), freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :> > work! :-) > :> > :> Clearly, that goes to show Luigi must have no life... :-) > :> > : > :"Luigi" is an interesting spelling of "Louqi". Whoops! Luoqi ;-) > :The bug was actually in libalias. > : > > Luoqi found a bug in the compiler's optimizer. I presume someone > has/will commit a change to libalias to work around it, and hopefully > Luoqi notified the EGCS people. This sort of optimizer bug is usually > fairly easy to fix given demonstration code, and Luoqi presented > demonstration code. > Luoqi committed a fix, but I don't remember if he fixed egcs or libalias. In his commit message, he states that he sent a bug report to the egcs people. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22:45:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (Postfix) with ESMTP id 8628C15909 for ; Wed, 21 Apr 1999 22:43:30 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id OAA01846; Thu, 22 Apr 1999 14:09:49 +1000 (EST) Date: Thu, 22 Apr 1999 14:09:49 +1000 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: Mike Tancsa Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <3.0.5.32.19990421164957.00fab1f0@staff.sentex.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >:Just wondering if these changes also have the side effect of fixing the > >:nmap problem that crashes 3.x boxes ? i.e. as you wrote back on 3/4/99 > >: > >:> The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing > >:> the file, but then it does some really weird crap when dealing with > >:> larger files. > >:> > > I believe this was fixed in -current. I don't know if it was backported > > to -stable. > > Unfortunately no... It can still lockup a 3.x machine. > This is the only thing stopping me from upgrading our production machines to 3.1-STABLE. Please, please, please backport these fixes! -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22:45:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AC21515961 for ; Wed, 21 Apr 1999 22:44:35 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id WAA19799; Wed, 21 Apr 1999 22:42:05 -0700 (PDT) (envelope-from obrien) Message-ID: <19990421224205.A19773@nuxi.com> Date: Wed, 21 Apr 1999 22:42:05 -0700 From: "David O'Brien" To: Brian Handy , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brian Handy on Wed, Apr 21, 1999 at 02:43:03PM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was just wondering -- does the new EGCS imply that things like > apps2go Motif won't link properly against a 4.x-CURRENT world now? My Apps2go Motif works just file post-EGCS. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 22:58:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id CC7FD15920 for ; Wed, 21 Apr 1999 22:58:38 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA10644; Wed, 21 Apr 1999 22:56:05 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 22:56:05 -0700 (PDT) From: Matthew Dillon Message-Id: <199904220556.WAA10644@apollo.backplane.com> To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? :) References: <99Apr22.070815est.40329@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I'm nothing like an NFS expert, so I may be talking through my hat, :but... I presume NFS correctly supports O_APPEND semantics for :multiple clients (as seen from the server). In this case, the :optimization only works when there's only one client machine (though :possibly multiple processes on that machine) is using write+O_APPEND. : :Peter I don't this was ever supported or ever will be in the multiple-client case. Maybe eventually with the leasing stuff. Otherwise, no way. The stateless nature of NFS makes it virtually impossible. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 21 23:19:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 3DBB315149 for ; Wed, 21 Apr 1999 23:19:11 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id XAA08309; Wed, 21 Apr 1999 23:16:13 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904220616.XAA08309@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mikhail Teterin Cc: Freebsd-current@FreeBSD.ORG Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Thu, 22 Apr 1999 00:14:42 EDT." <199904220414.AAA21542@kot.ne.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Apr 1999 23:16:12 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You should be able to fire up two video cards were one them can not be mapped to the vga registers -- your mileage will vary here pending upon the vga card implementation for instance the old matrox millenium had a feature to disable the vga register mapping . Can speak much about syscons I would just ignore if I had two X servers however if you are planning a dual console system I don't know if it will work your best is to ask Soren who is the original author of syscon. The mouse stuff shouldn't be too much of a problem from the X server perspective it thinks that it is talking to a serial device. Cheers, Amancio > Viren R. Shah once stated: > > =Amancio and Nick helped me get my system with only a USB keyboard and > =USB mouse up and running. Right now I'm pretty happy with the way it is > =now. My only concern is that the FreeBSD bootloader does not appear to > =see keystrokes from the USB keyboard (which kinda makes it difficult to > =switch OSes on an USB only system). > > Provided I configure two video cards not to conflict, can I use > two USB keyboard and two USB mice (or one USB and one usual of > each) and run two independent X-servers? Two instances of sc? > > Thanks! > > -mi -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 0:48:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 82CAB14DBD for ; Thu, 22 Apr 1999 00:48:19 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id JAA26415; Thu, 22 Apr 1999 09:45:37 +0200 (MET DST) Date: Thu, 22 Apr 1999 09:45:39 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Amancio Hasty Cc: Freebsd-current@FreeBSD.ORG Subject: Re: USB keyboard attach function? In-Reply-To: <199904211858.LAA04402@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While playing over here with the USB stuff, I rebooted the system and > disconnected the USB keyboard waited till the system was fully up > and re-connected the USB keyboard which resulted in the system > not attaching the USB keyboard. Did you update your rc.conf lately? It should contain the startup of the usbd daemon. > A side note, someone fixed syscons so it no longer panics if > the atkbd device is not configured . In my case, I have > a USB keyboard and a USB mouse connected to the > system with no atkbdc nor atbkd device . It works like > a charm now 8) Cool! Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 0:57:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 23888158A6 for ; Thu, 22 Apr 1999 00:57:47 -0700 (PDT) (envelope-from geoffb@gti.noc.demon.net) Received: by noc.demon.net; id IAA23702; Thu, 22 Apr 1999 08:55:18 +0100 (BST) Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma023676; Thu, 22 Apr 99 08:55:13 +0100 Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id IAA23795; Thu, 22 Apr 1999 08:55:00 +0100 (BST) Message-ID: <19990422085459.D5009@gti.noc.demon.net> Date: Thu, 22 Apr 1999 08:54:59 +0100 From: Geoff Buckingham To: Matthew Dillon , Doug Rabson Cc: Peter Wemm , Matthew Reimer , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) Reply-To: Geoff Buckingham References: <199904211931.MAA07688@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904211931.MAA07688@apollo.backplane.com>; from Matthew Dillon on Wed, Apr 21, 1999 at 12:31:03PM -0700 Organisation: Demon Internet Ltd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Previously on Wed, Apr 21, 1999 at 12:31:03PM -0700, Matthew Dillon wrote: : : I think the existing release schedule is pretty good. Any faster and : we might as well not have two branches at all. We really need a : -current branch in order to make and test radical changes, and the : companies & people who use FreeBSD need a -stable branch to keep : production boxes up to date without having to bet the farm. : : We already have the ability to shortcut certain things simply by : copying them from -current to -stable wholesale after we've determined : their stability under -current. The issue here really is safety. I : know some of you really want some of the things in -current to be : backported into -stable more quickly, but you have to be patient. We : can't compromise -stable's stability by acting too quickly. : Speaking as a heavy stable user and also a Net and OpenBSD user the big selling point I have for using FreeBSD over the other 'free' BSDs, Linux and some commercial OSs is the release structure. I believe radical alterations to this structure would be best avoided. It is only post 3.1 release that I have become confident in the RelEng3 branch as a service platform. People desperate for current functionality can wait, back port themselves or run current. I have taken all three options in the past :-) -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1: 1:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 543CD14BD3 for ; Thu, 22 Apr 1999 01:01:10 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id AAA09090; Thu, 22 Apr 1999 00:58:27 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904220758.AAA09090@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: Freebsd-current@FreeBSD.ORG Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Thu, 22 Apr 1999 09:45:39 +0200." Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-21328833960" Date: Thu, 22 Apr 1999 00:58:27 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_-21328833960 Content-Type: text/plain; charset=us-ascii > Did you update your rc.conf lately? It should contain the startup of > the usbd daemon. I know start usbd upon startup 8) > > A side note, someone fixed syscons so it no longer panics if > > the atkbd device is not configured . In my case, I have > > a USB keyboard and a USB mouse connected to the > > system with no atkbdc nor atbkd device . It works like > > a charm now 8) > > Cool! > Not quite a fix however the following patches fixes disconnect /reconnect problems with my USB mouse and the 3com USB modem . This is a bandage please don't commit is just that right if I diconnect my usb modem or usb mouse my system panics hence the following simple patch. Disconnected and reconnected my mouse several times and got no panic plus every time someone calls here the USB modem does not crash my system 8) One thing though someone ought to fix moused so that if it is talking to a usb mouse which gets disconnected and then reconnected to enable again the mouse. I managed to get back my mouse operational by sending a "HUP" signal to moused. Enjoy --==_Exmh_-21328833960 Content-Type: text/plain ; name="usb-patch"; charset=us-ascii Content-Description: usb-patch Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="usb-patch" ZGlmZiAtciAtYyB1c2IvdWdlbi5jIHVzYi5uZXcvdWdlbi5jCioqKiB1c2IvdWdlbi5jCUZy aSBBcHIgMTYgMTY6MTM6MzYgMTk5OQotLS0gdXNiLm5ldy91Z2VuLmMJV2VkIEFwciAyMSAx OToxNjo1NCAxOTk5CioqKioqKioqKioqKioqKgoqKiogOTQ3LDk1MyAqKioqCiAgCXN0cnVj dCB1Z2VuX2VuZHBvaW50ICpzY2U7CiAgCWludCByZXZlbnRzID0gMDsKICAJaW50IHM7CiEg CiAgCWlmIChzYy0+c2NfZGlzY29ubmVjdGVkKQogIAkJcmV0dXJuIChFSU8pOwogIAotLS0g OTQ3LDk1MyAtLS0tCiAgCXN0cnVjdCB1Z2VuX2VuZHBvaW50ICpzY2U7CiAgCWludCByZXZl bnRzID0gMDsKICAJaW50IHM7CiEgCWlmIChzYyA9PSBOVUxMICkgcmV0dXJuIChFSU8pOwog IAlpZiAoc2MtPnNjX2Rpc2Nvbm5lY3RlZCkKICAJCXJldHVybiAoRUlPKTsKICAKZGlmZiAt ciAtYyB1c2IvdWtiZC5jIHVzYi5uZXcvdWtiZC5jCioqKiB1c2IvdWtiZC5jCVN1biBBcHIg MTEgMTU6Mjg6MzggMTk5OQotLS0gdXNiLm5ldy91a2JkLmMJV2VkIEFwciAyMSAxOToxNToy OSAxOTk5CioqKioqKioqKioqKioqKgoqKiogMzA2LDMxMSAqKioqCi0tLSAzMDYsMzEyIC0t LS0KICB1a2JkcG9sbChkZXZfdCBkZXYsIGludCBldmVudCwgc3RydWN0IHByb2MgKnApCiAg ewogIAlVU0JfR0VUX1NDKHVrYmQsIFVLQkRVTklUKGRldiksc2MpOworIAlpZiAoc2MgPT0g TlVMTCApIHJldHVybiAwOwogIAogIAlyZXR1cm4gZ2Vua2JkcG9sbCgmc2MtPnNjX2dlbnNj LCBzYy0+c2Nfa2JkLCBldmVudCwgcCk7CiAgfQpkaWZmIC1yIC1jIHVzYi91bXMuYyB1c2Iu bmV3L3Vtcy5jCioqKiB1c2IvdW1zLmMJRnJpIEFwciAxNiAxNjoxMzo0NyAxOTk5Ci0tLSB1 c2IubmV3L3Vtcy5jCVdlZCBBcHIgMjEgMTg6NTk6MDkgMTk5OQoqKioqKioqKioqKioqKioK KioqIDY2NCw2NjkgKioqKgotLS0gNjY0LDY3MCAtLS0tCiAgCVVTQl9HRVRfU0ModW1zLCBV TVNVTklUKGRldiksIHNjKTsKICAJaW50IHJldmVudHMgPSAwOwogIAlpbnQgczsKKyAJaWYg KHNjID09IE5VTEwgKSByZXR1cm4gcmV2ZW50czsKICAKICAJcyA9IHNwbHVzYigpOwogIAlp ZiAoZXZlbnRzICYgKFBPTExJTiB8IFBPTExSRE5PUk0pKSB7CmRpZmYgLXIgLWMgdXNiL3Vz Yl9wb3J0LmggdXNiLm5ldy91c2JfcG9ydC5oCioqKiB1c2IvdXNiX3BvcnQuaAlXZWQgQXBy IDIxIDE1OjMzOjQ0IDE5OTkKLS0tIHVzYi5uZXcvdXNiX3BvcnQuaAlXZWQgQXByIDIxIDE4 OjI5OjIwIDE5OTkKKioqKioqKioqKioqKioqCioqKiAyMDIsMjA4ICoqKioKICAJCSgoZGV2 KS0+c29mdGMgPSBkZXZpY2VfZ2V0X3NvZnRjKGJkZXYpKSA6IDApCiAgCiAgLyogY29udmVy c2lvbiBmcm9tIG9uZSB0eXBlIG9mIHF1ZXVlIHRvIHRoZSBvdGhlciAqLwohICNkZWZpbmUg U0lNUExFUV9SRU1PVkVfSEVBRAlTVEFJTFFfUkVNT1ZFX0hFQUQKICAjZGVmaW5lIFNJTVBM RVFfSU5TRVJUX0hFQUQJU1RBSUxRX0lOU0VSVF9IRUFECiAgI2RlZmluZSBTSU1QTEVRX0lO U0VSVF9UQUlMCVNUQUlMUV9JTlNFUlRfVEFJTAogICNkZWZpbmUgU0lNUExFUV9ORVhUCQlT VEFJTFFfTkVYVAotLS0gMjAyLDIxNiAtLS0tCiAgCQkoKGRldiktPnNvZnRjID0gZGV2aWNl X2dldF9zb2Z0YyhiZGV2KSkgOiAwKQogIAogIC8qIGNvbnZlcnNpb24gZnJvbSBvbmUgdHlw ZSBvZiBxdWV1ZSB0byB0aGUgb3RoZXIgKi8KISAvKiAjZGVmaW5lIFNJTVBMRVFfUkVNT1ZF X0hFQUQJU1RBSUxRX1JFTU9WRV9IRUFEICovCiEgI2RlZmluZSBTSU1QTEVRX1JFTU9WRV9I RUFEKGhlYWQsIGZpZWxkKSBkbyB7CQkJCVwKISAgICAgICAgIGlmICgoaGVhZCktPnN0cWhf Zmlyc3QgIT0gTlVMTCApIHsgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgXAohIAlp ZiAoKChoZWFkKS0+c3RxaF9maXJzdCA9CQkJCQlcCiEgCSAgICAgKGhlYWQpLT5zdHFoX2Zp cnN0LT5maWVsZC5zdHFlX25leHQpID09IE5VTEwpCQlcCiEgCQkoaGVhZCktPnN0cWhfbGFz dCA9ICYoaGVhZCktPnN0cWhfZmlyc3Q7CQlcCiEgICAgICAgICAgfSAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgXAohIH0g d2hpbGUgKDApCiEgCiAgI2RlZmluZSBTSU1QTEVRX0lOU0VSVF9IRUFECVNUQUlMUV9JTlNF UlRfSEVBRAogICNkZWZpbmUgU0lNUExFUV9JTlNFUlRfVEFJTAlTVEFJTFFfSU5TRVJUX1RB SUwKICAjZGVmaW5lIFNJTVBMRVFfTkVYVAkJU1RBSUxRX05FWFQK --==_Exmh_-21328833960 Content-Type: text/plain; charset=us-ascii Amancio Hasty hasty@star-gate.com --==_Exmh_-21328833960-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1:10:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id D1A6D15920 for ; Thu, 22 Apr 1999 01:10:32 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA27485; Thu, 22 Apr 1999 10:08:00 +0200 (MET DST) Date: Thu, 22 Apr 1999 10:07:56 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Amancio Hasty Cc: FreeBSD current mailing list Subject: Re: USB keyboard attach function? In-Reply-To: <199904220758.AAA09090@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not quite a fix however the following patches fixes disconnect /reconnect > problems with my USB mouse and the 3com USB modem . This is a > bandage please don't commit is just that right if I diconnect my usb > modem or usb mouse my system panics hence the following simple patch. That looks like a proper hack. I'll have to sort out something more reliable than that :-) > Disconnected and reconnected my mouse several times and got no > panic plus every time someone calls here the USB modem does > not crash my system 8) :-) You can quitely answer the phone while your system is doing an fsck of a 18Gb disk that is 80% full... > One thing though someone ought to fix moused so that if > it is talking to a usb mouse which gets disconnected and > then reconnected to enable again the mouse. I managed > to get back my mouse operational by sending a "HUP" > signal to moused. One of the things we might to have a daemon do. Another option would be to just reconnect the mouse to the same open file descriptor, but I don't know whether this is possible. The following is no longer necessary (I think). I fixed that yesterday. diff -r -c usb/usb_port.h usb.new/usb_port.h *** usb/usb_port.h Wed Apr 21 15:33:44 1999 --- usb.new/usb_port.h Wed Apr 21 18:29:20 1999 *************** *** 202,208 **** ((dev)->softc = device_get_softc(bdev)) : 0) /* conversion from one type of queue to the other */ ! #define SIMPLEQ_REMOVE_HEAD STAILQ_REMOVE_HEAD #define SIMPLEQ_INSERT_HEAD STAILQ_INSERT_HEAD #define SIMPLEQ_INSERT_TAIL STAILQ_INSERT_TAIL #define SIMPLEQ_NEXT STAILQ_NEXT --- 202,216 ---- ((dev)->softc = device_get_softc(bdev)) : 0) /* conversion from one type of queue to the other */ ! /* #define SIMPLEQ_REMOVE_HEAD STAILQ_REMOVE_HEAD */ ! #define SIMPLEQ_REMOVE_HEAD(head, field) do { \ ! if ((head)->stqh_first != NULL ) { \ ! if (((head)->stqh_first = \ ! (head)->stqh_first->field.stqe_next) == NULL) \ ! (head)->stqh_last = &(head)->stqh_first; \ ! } \ ! } while (0) ! #define SIMPLEQ_INSERT_HEAD STAILQ_INSERT_HEAD #define SIMPLEQ_INSERT_TAIL STAILQ_INSERT_TAIL #define SIMPLEQ_NEXT STAILQ_NEXT -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1:13:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from hydrogen.fircrest.net (metriclient-3.uoregon.edu [128.223.172.3]) by hub.freebsd.org (Postfix) with ESMTP id 578E014BD3 for ; Thu, 22 Apr 1999 01:13:29 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.fircrest.net (8.9.1/8.8.7) id BAA04253; Thu, 22 Apr 1999 01:10:56 -0700 (PDT) Message-ID: <19990422011055.15112@hydrogen.nike.efn.org> Date: Thu, 22 Apr 1999 01:10:55 -0700 From: John-Mark Gurney To: current@freebsd.org Subject: buildworld as normal user... Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=wUX3Y2Cv9Ux+11Zm X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --wUX3Y2Cv9Ux+11Zm Content-Type: text/plain; charset=us-ascii well, I just completed buildworld as a normal user, and would like to recieve comments on various fixes... a) create GAMEGRP in bsd.own.mk and change games in games/Makefile.inc to use ${GAMEGRP} b) add conditional of NOFSCHG in addition to PRECIOUSLIB in bsd.lib.mk so libdes and friends try to be installed with schg flag set these are the only two that I came across... I have attached patches that I created to fix them... also attached is my dobuildworld script that I use to start the whole process... comments? I am thinking of changing NOFSCHG to NOSCHG, but I was just doing the patch real quickly... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson --wUX3Y2Cv9Ux+11Zm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="nrmlusr.patch" Index: src/share/mk/bsd.lib.mk =================================================================== RCS file: /home/ncvs/src/share/mk/bsd.lib.mk,v retrieving revision 1.86 diff -u -r1.86 bsd.lib.mk --- bsd.lib.mk 1999/03/23 03:06:25 1.86 +++ bsd.lib.mk 1999/04/22 05:47:01 @@ -262,7 +262,7 @@ beforeinstall: .endif -.if defined(PRECIOUSLIB) +.if defined(PRECIOUSLIB) && !defined(NOFSCHG) SHLINSTALLFLAGS+= -fschg .endif Index: src/share/mk/bsd.own.mk =================================================================== RCS file: /home/ncvs/src/share/mk/bsd.own.mk,v retrieving revision 1.22 diff -u -r1.22 bsd.own.mk --- bsd.own.mk 1999/04/20 14:24:52 1.22 +++ bsd.own.mk 1999/04/22 05:08:42 @@ -136,6 +136,7 @@ # Binaries BINOWN?= root BINGRP?= wheel +GAMEGRP?= games BINMODE?= 555 NOBINMODE?= 444 Index: src/games/Makefile.inc =================================================================== RCS file: /home/ncvs/src/games/Makefile.inc,v retrieving revision 1.9 diff -u -r1.9 Makefile.inc --- Makefile.inc 1998/10/18 09:48:26 1.9 +++ Makefile.inc 1999/04/22 05:08:02 @@ -1,6 +1,6 @@ # @(#)Makefile.inc 8.1 (Berkeley) 5/31/93 -BINGRP= games +BINGRP= ${GAMEGRP} BINDIR?= /usr/games .if defined(HIDEGAME) --wUX3Y2Cv9Ux+11Zm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dobuildworld #!/bin/sh -e - z=`pwd` z=`basename $z` if [ "x${z}" = "xsrc" ]; then cd .. z=`pwd` z=`basename $z` cd src if [ -f /tmp/buildworldoutput.$z ]; then mv /tmp/buildworldoutput.$z /tmp/buildworldoutput.${z}.last fi date | tee /tmp/buildworldoutput.$z chown jmg /tmp/buildworldoutput.$z time -l make BINGRP=admin BINOWN=jmg TMACOWN=jmg TMACGRP=admin SHAREOWN=jmg SHAREGRP=admin GAMEGRP=admin NOINFO= NOPROFILE= NOTCL= NOTERMCAP= NOFSCHG= $* buildworld 2>&1 | tee -a /tmp/buildworldoutput.$z echo 'NOTE: You must build share/termcap by hand!!' | tee -a /tmp/buildworldoutput.$z date | tee -a /tmp/buildworldoutput.$z else echo 'You must be in the src dir to do a buildworld' fi --wUX3Y2Cv9Ux+11Zm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1:14:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 52CDA14BD3 for ; Thu, 22 Apr 1999 01:14:22 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id KAA27649; Thu, 22 Apr 1999 10:11:43 +0200 (MET DST) Date: Thu, 22 Apr 1999 10:11:44 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Amancio Hasty Cc: "Viren R. Shah" , Kazutaka YOKOTA , Freebsd-current@freebsd.org Subject: Re: USB keyboard attach function? In-Reply-To: <199904212052.NAA05084@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am quite sure that you using the legacy USB keyboard support of your BIOS. The USB keyboard can not kick in before the PCI probes have been done. Nick On Wed, 21 Apr 1999, Amancio Hasty wrote: > Hi, > > >is now. My only concern is that the FreeBSD bootloader does not appear > > If you are running -current as of at least last nite you will not have > any problems with the bootloader and your USB keyboard in fact > I just rebooted my test system and was able to select the kernel > to boot; previously, you are right the bootloader didn't work with > a USB keyboard only system. > > > -- > > Amancio Hasty > hasty@star-gate.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1:19:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa16-17.ix.netcom.com [207.93.148.145]) by hub.freebsd.org (Postfix) with ESMTP id E606315978 for ; Thu, 22 Apr 1999 01:19:34 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id BAA01226; Thu, 22 Apr 1999 01:12:13 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Thu, 22 Apr 1999 01:12:13 -0700 (PDT) Message-Id: <199904220812.BAA01226@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: LINT Question Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I mis-directed this earlier. I am running 4.0-current SMP as of Apr 21. LINT has two versions of values for ports. One is in quotes and the other is not. For example, device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 The definition of IO_NPX and IO_COM1 have the same form in sys/isa/isareg.h, sys/i386/isa/isa.h, etc. Some time back, someone posted guidance like "if it contains letters and numbers, quote it, otherwise don't." Which form should be used for these values? LINT shows ppc0 as a device and 'man ppc' says it is a controller. I believe earlier versions of LINT had ppc as a controller. Which is correct? sio1 is not in LINT, but it is in GENERIC. Some devices like fd have both fd0 and fd1. Since two serial ports is common should LINT have sio1? Newer machines are more likely to have two serial ports than two floppy drives. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1:21:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 3FA3515973 for ; Thu, 22 Apr 1999 01:20:49 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id KAA28004; Thu, 22 Apr 1999 10:18:12 +0200 (MET DST) Date: Thu, 22 Apr 1999 10:18:13 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Mikhail Teterin Cc: hasty@rah.star-gate.com, Freebsd-current@FreeBSD.ORG Subject: Re: USB keyboard attach function? In-Reply-To: <199904220414.AAA21542@kot.ne.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've heard of no one trying, but I (we!) would love to hear whether you get this to work. There is not problem is using two keyboards at the same time, but I am not sure whether X can already handle more than one keyboard attached to a system. I don't think that you can specify the keyboard /dev/ entry int he X configuration. Try looking at the XFree pages. I remember someone asking me whether this would be possible soon in FreeBSD because they were working on support for multiple keyboards. Nick On Thu, 22 Apr 1999, Mikhail Teterin wrote: > Viren R. Shah once stated: > > =Amancio and Nick helped me get my system with only a USB keyboard and > =USB mouse up and running. Right now I'm pretty happy with the way it is > =now. My only concern is that the FreeBSD bootloader does not appear to > =see keystrokes from the USB keyboard (which kinda makes it difficult to > =switch OSes on an USB only system). > > Provided I configure two video cards not to conflict, can I use > two USB keyboard and two USB mice (or one USB and one usual of > each) and run two independent X-servers? Two instances of sc? > > Thanks! > > -mi > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1:21:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 0E64515977 for ; Thu, 22 Apr 1999 01:21:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id BAA09318; Thu, 22 Apr 1999 01:18:33 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904220818.BAA09318@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: "Viren R. Shah" , Kazutaka YOKOTA , Freebsd-current@freebsd.org Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Thu, 22 Apr 1999 10:11:44 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Apr 1999 01:18:33 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That might be the case however I and Viren R. Shah have found out that with the lastest current we can indeed talk to the bootloader which we couldn't before. The only thing which change in my computer was a cvsup update ,i.e., I did not touch my bios setting nor do I have an AT keyboard attached. > > I am quite sure that you using the legacy USB keyboard support of your > BIOS. The USB keyboard can not kick in before the PCI probes have been > done. > > Nick > > > On Wed, 21 Apr 1999, Amancio Hasty wrote: > > > Hi, > > > > >is now. My only concern is that the FreeBSD bootloader does not appear > > > > If you are running -current as of at least last nite you will not have > > any problems with the bootloader and your USB keyboard in fact > > I just rebooted my test system and was able to select the kernel > > to boot; previously, you are right the bootloader didn't work with > > a USB keyboard only system. > > > > > > -- > > > > Amancio Hasty > > hasty@star-gate.com > > > > > > > -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 8F2FB15980 for ; Thu, 22 Apr 1999 01:22:00 -0700 (PDT) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id KAA16413 for ; Thu, 22 Apr 1999 10:19:22 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id KAA17222 for ; Thu, 22 Apr 1999 10:19:23 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (IDENT:F4sM+hDOpANn7KWUKvYJdPoIyaxQAgH9@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id KAA13303 for ; Thu, 22 Apr 1999 10:19:19 +0200 (CEST) Message-Id: <199904220819.KAA13303@wurzelausix.cs.uni-sb.de> Date: Thu, 22 Apr 1999 10:19:16 +0200 (CEST) From: Alexander Leidinger Subject: _my_ world is broken To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, _my_ world breaks with: c++ -Os -march=pentium -pipe -Wall -fexpensive-optimizations -fomit-frame-pointer -funroll-loops -I/ usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -c /usr/src/gnu/lib/libgcc/../.. /../contrib/egcs/gcc/cp/exception.cc -o exception.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:33: eh-common.h: No such file or d irectory /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:89: syntax error before `;' /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:156: type specifier omitted for pa rameter /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:156: parse error before `*' /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc: In function `void * __cplus_type_ matcher(...)': /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:160: `exception_table' undeclared (first use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:160: (Each undeclared identifier i s reported only once /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:160: for each function it appears in.) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:160: `EH_LANG_C_plus_plus' undecla red (first use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:163: `match_info' undeclared (firs t use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:163: `CATCH_ALL_TYPE' undeclared ( first use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:164: `info' undeclared (first use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:168: confused by earlier errors, b ailing out *** Error code 1 My last finished world is from Apr, 7 and since then I wasn't able to build the world anymore. First I thought I have to rebuild cc as described in UPDATING, so I did: foreach i ( /usr/src/includes /usr/src/lib /usr/src/gnu/usr.bin/cc ) cd $i make clean cleandir depend make make install clean cleandir end After that I tried to make the world again, but it fails. If I change eh-common.h to ../eh-common.h it fails too, but a little bit later. What am I doing wrong? Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 1:47: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id EC5EB152DB for ; Thu, 22 Apr 1999 01:46:29 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id SAA19371; Thu, 22 Apr 1999 18:43:20 +1000 (EST) Message-ID: <19990422184319.G18359@rf900.physics.usyd.edu.au> Date: Thu, 22 Apr 1999 18:43:19 +1000 From: David Dawes To: Nick Hibma , Mikhail Teterin Cc: hasty@rah.star-gate.com, Freebsd-current@FreeBSD.ORG Subject: Re: USB keyboard attach function? References: <199904220414.AAA21542@kot.ne.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Nick Hibma on Thu, Apr 22, 1999 at 10:18:13AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 22, 1999 at 10:18:13AM +0200, Nick Hibma wrote: >I've heard of no one trying, but I (we!) would love to hear whether you >get this to work. > >There is not problem is using two keyboards at the same time, but I am >not sure whether X can already handle more than one keyboard attached to >a system. I don't think that you can specify the keyboard /dev/ entry >int he X configuration. That's correct, but we're planning to allow the Device to be specified in XFree86 4.0. >Try looking at the XFree pages. I remember someone asking me whether >this would be possible soon in FreeBSD because they were working on >support for multiple keyboards. Supporting multiple keyboards with a single X server should be relatively easy. Supporting multiple X servers on the same host will be difficult because of video hardware resource sharing/control issues, specifically for the legacy VGA resources. In our initial approach with XFree86 4.0, the X server will assume control of all of the VGA-compatible video hardware so that it can do the necessary coordination of access to the VGA resources. As Amancio implied, it should be possible to do better than that for hardware that has a PCI class/subclass that indicates no VGA core. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 2: 4:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id E4271150C8 for ; Thu, 22 Apr 1999 02:04:39 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id CAA09789; Thu, 22 Apr 1999 02:01:36 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199904220901.CAA09789@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: David Dawes Cc: Nick Hibma , Mikhail Teterin , Freebsd-current@FreeBSD.ORG Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Thu, 22 Apr 1999 18:43:19 +1000." <19990422184319.G18359@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Apr 1999 02:01:35 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi David! Just a kind reminder we can unplug and plug a usb mouse as well as a usb keyboard currently we have a small problem with moused that it does not attempt to gain access of the mouse if there is a usb disconnect / connect sequence. Regards -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 2:30:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id A33AA14C33 for ; Thu, 22 Apr 1999 02:30:39 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA07800; Thu, 22 Apr 1999 19:28:10 +1000 Date: Thu, 22 Apr 1999 19:28:10 +1000 From: Bruce Evans Message-Id: <199904220928.TAA07800@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, tomdean@ix.netcom.com Subject: Re: LINT Question Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >LINT has two versions of values for ports. One is in quotes and the >other is not. > >For example, > >device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 >device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 > >The definition of IO_NPX and IO_COM1 have the same form in >sys/isa/isareg.h, sys/i386/isa/isa.h, etc. > >Some time back, someone posted guidance like "if it contains letters >and numbers, quote it, otherwise don't." More precisely, quote if it contains multiple tokens and multiple tokens are not wanted, otherwise don't. `IO_COM1' contains 2 tokens, `IO_COM' and `1' so not quoting would give the same syntax error as `port IO_COM 1'. >Which form should be used for these values? Follow the rule. >LINT shows ppc0 as a device and 'man ppc' says it is a controller. I >believe earlier versions of LINT had ppc as a controller. Which is >correct? `controller' was correct, but it didn't matter. new-bus may change this. >sio1 is not in LINT, but it is in GENERIC. Some devices like fd have >both fd0 and fd1. Since two serial ports is common should LINT have >sio1? Newer machines are more likely to have two serial ports than >two floppy drives. LINT is not supposed to show all devices. It is for testing that all code at least compiles. It needs to show sio1 as much as it needs to show sio65535 (not). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 3:41:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5854A150B8 for ; Thu, 22 Apr 1999 03:41:07 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA08883; Thu, 22 Apr 1999 06:37:54 -0400 (EDT) Date: Thu, 22 Apr 1999 06:37:54 -0400 (EDT) From: Daniel Eischen Message-Id: <199904221037.GAA08883@pcnet1.pcnet.com> To: andyf@speednet.com.au, mike@sentex.net Subject: Re: solid NFS patch #6 avail for -current - need testers files) Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is the only thing stopping me from upgrading our production machines > to 3.1-STABLE. > > Please, please, please backport these fixes! I have to echo these feelings. NFS, as both server and client, is working without noticeable problems for us under the old 2.2-stable. I am afraid of upgrading to 3.1-stable with the reported NFS problems, and we can't get by without NFS. Some serious consideration should be given to fix the NFS problems in 3.1 - at least to make it more reliable. Perhaps there can be well announced unstable periods of -stable for things like merging non-trivial changes from -current? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 3:53:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from stevenson.cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AEEC15991 for ; Thu, 22 Apr 1999 03:52:44 -0700 (PDT) (envelope-from richard@cogsci.ed.ac.uk) Received: from doyle.cogsci.ed.ac.uk (richard@doyle [129.215.110.29]) by stevenson.cogsci.ed.ac.uk (8.8.7/8.8.7) with SMTP id LAA23290 for ; Thu, 22 Apr 1999 11:50:07 +0100 (BST) Date: Thu, 22 Apr 1999 11:50:06 +0100 Message-Id: <878.199904221050@doyle.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: solid NFS patch #6 avail for -current - need testers files) To: freebsd-current@FreeBSD.ORG In-Reply-To: Geoff Buckingham's message of Thu, 22 Apr 1999 08:54:59 +0100 Organization: just say no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > People desperate for current functionality can wait, back port themselves or > run current. I have taken all three options in the past :-) I agree. I have recently installed 3.1-STABLE on two machines, and in each case the ethernet drivers (xl and lnc) had been broken since 3.1 (both are now fixed). Stable is already not stable enough! -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 4:24:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id ABFCF15129 for ; Thu, 22 Apr 1999 04:24:11 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id HAA35014; Thu, 22 Apr 1999 07:19:36 -0400 (EDT) Date: Thu, 22 Apr 1999 07:19:36 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: Christopher Masto , current@FreeBSD.ORG Subject: Re: New ATA driver and crash dumps In-Reply-To: <199904210647.IAA33104@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Apr 1999, Soren Schmidt wrote: > It seems Christopher Masto wrote: > > My machine panicked today for the first time since switching to the > > new ATA drivers, and I noticed that I no longer have crash dumps. > > Is this something that is expected to be put back in soon? > >=20 > > I know S=F8ren's a busy guy, and I'm glad we have the results of his > > work. I just hope the old drivers don't get killed off until the > > replacement has the same functionality. > >=20 > > Then again, wddump() is only 100 lines of code, so I should probably > > try to fix it myself before whining. >=20 > I know :), it has just not been done yet. It will be done eventually > but I have other areas in the driver I want finish first. This and atapi-fd not working are the only hang-ups I have with using ATA. Heck, the benefits even outweigh that since my new UDMA2 hard drive is only supported with your wonderful new ATA drivers, not wd! The Aladdin support works great. Is there any way I can help in getting the atapi-fd driver to work with LS-120's? >=20 > Also the old wd driver will probably not be killed off entirely, as=20 > its the only one we have that support old ST506/ESDI drives. >=20 > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman _ __ ___ ____ ___ ___ ___ =20 green@unixhelp.org _ __ ___ | _ ) __| \=20 FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 4:30:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C745315119 for ; Thu, 22 Apr 1999 04:29:17 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA36407; Thu, 22 Apr 1999 13:26:43 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904221126.NAA36407@freebsd.dk> Subject: Re: New ATA driver and crash dumps In-Reply-To: from Brian Feldman at "Apr 22, 1999 7:19:36 am" To: green@unixhelp.org (Brian Feldman) Date: Thu, 22 Apr 1999 13:26:43 +0200 (CEST) Cc: chris@netmonger.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Feldman wrote: >This and atapi-fd not working are the only hang-ups I have with using ATA. >Heck, the benefits even outweigh that since my new UDMA2 hard drive is only >supported with your wonderful new ATA drivers, not wd! The Aladdin support >works great. > Is there any way I can help in getting the atapi-fd driver to work with >LS-120's? Hmm, I have a ZIP here which works, and I have reports from mike that his LS120 works too, so I'm a bit confused here. How does it not work ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 4:32:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6A75415119 for ; Thu, 22 Apr 1999 04:32:29 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id HAA35163; Thu, 22 Apr 1999 07:28:28 -0400 (EDT) Date: Thu, 22 Apr 1999 07:28:28 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: chris@netmonger.net, current@FreeBSD.ORG Subject: Re: New ATA driver and crash dumps In-Reply-To: <199904221126.NAA36407@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: >=20 > >This and atapi-fd not working are the only hang-ups I have with using AT= A. > >Heck, the benefits even outweigh that since my new UDMA2 hard drive is o= nly > >supported with your wonderful new ATA drivers, not wd! The Aladdin suppo= rt > >works great. > > Is there any way I can help in getting the atapi-fd driver to work wi= th > >LS-120's? >=20 > Hmm, I have a ZIP here which works, and I have reports from mike that > his LS120 works too, so I'm a bit confused here. > How does it not work ?? I get consistent errors reading from it (not hard errors, data errors). The md5 checksums I created on the disk using the wd driver do not match the varying checksums md5 gives me on the LS-120 with the new ATA. >=20 > -S=F8ren >=20 Brian Feldman _ __ ___ ____ ___ ___ ___ =20 green@unixhelp.org _ __ ___ | _ ) __| \=20 FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 4:40:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DE308153E3 for ; Thu, 22 Apr 1999 04:40:38 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA36443; Thu, 22 Apr 1999 13:38:04 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904221138.NAA36443@freebsd.dk> Subject: Re: New ATA driver and crash dumps In-Reply-To: from Brian Feldman at "Apr 22, 1999 7:28:28 am" To: green@unixhelp.org (Brian Feldman) Date: Thu, 22 Apr 1999 13:38:04 +0200 (CEST) Cc: chris@netmonger.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Feldman wrote: >> Hmm, I have a ZIP here which works, and I have reports from mike that >> his LS120 works too, so I'm a bit confused here. >> How does it not work ?? > >I get consistent errors reading from it (not hard errors, data errors). The >md5 checksums I created on the disk using the wd driver do not match the >varying checksums md5 gives me on the LS-120 with the new ATA. Hmm, does it still work with the old driver ?? Does it share the channel with another device ?? (ata/atapi??) It sounds like a HW problem of some sort to me.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 4:52:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (unknown [206.29.49.3]) by hub.freebsd.org (Postfix) with ESMTP id E6BB314D1D for ; Thu, 22 Apr 1999 04:52:07 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id HAA29432; Thu, 22 Apr 1999 07:50:54 -0400 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma029429; Thu, 22 Apr 99 11:50:33 GMT Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id HAA25229; Thu, 22 Apr 1999 07:49:11 -0400 (EDT) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.3/8.8.8) id HAA25805; Thu, 22 Apr 1999 07:49:11 -0400 (EDT) Date: Thu, 22 Apr 1999 07:49:11 -0400 (EDT) Message-Id: <199904221149.HAA25805@jabberwock.rstcorp.com> From: "Viren R. Shah" To: "Daniel O'Connor" Cc: Amancio Hasty , Kazutaka YOKOTA , Freebsd-current@freebsd.org, Nick Hibma Subject: Re: USB keyboard attach function? In-Reply-To: References: <199904220404.VAA07662@rah.star-gate.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Daniel" == Daniel O'Connor writes: Daniel> On 22-Apr-99 Amancio Hasty wrote: >> The problem was not really a bios problem not sure what the guys >> did to fix the boot loader probably switch to using a dos int function >> to access the keyboard from the boot loader. Daniel> Hmm.. what does it do now? Just talk to the keyboard Daniel> controller directly? The BIOS I have here have an option Daniel> 'Port 60/64 emulation' in the USB related section... From looking thru the commits over the past day, nothing that could have changed the keyboard code that early seems to have gone in. Nevertheless, as Amancio said, my USB keyboard suddenly started being seen by the FreeBSD boot manager and loader. [I had my BIOS option set to "USB keyboard support: BIOS" all the time] *shrug* Serendipity Rules. Viren -- Viren Shah | "You can't trust code that you did not totally Research Associate, RST Inc. | create yourself. (Especially code from viren@rstcorp.com | companies that employ people like me.)" http://www.rstcorp.com/~vshah | - Ken Thompson "Reflections on Trusting Trust" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 4:58:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B891A1596D for ; Thu, 22 Apr 1999 04:58:37 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA36497 for current@freebsd.org; Thu, 22 Apr 1999 13:56:07 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904221156.NAA36497@freebsd.dk> Subject: Temporary fix for PCCARD's to work... To: current@freebsd.org Date: Thu, 22 Apr 1999 13:56:07 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Below find a quick fix that makes PCCARD work again. Beware that if you have it compiled in the kernel you should remove the kldload in /etc/rc.pccard, as it will happily load the module, and screw up the whole situation... Index: i386/isa/intr_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/intr_machdep.c,v retrieving revision 1.19 diff -u -r1.19 intr_machdep.c --- intr_machdep.c 1999/04/21 07:26:27 1.19 +++ intr_machdep.c 1999/04/23 11:16:30 @@ -877,6 +877,7 @@ free(irec, M_DEVBUF); return -1; } + isareclist[intr] = irec; return 0; } Index: pccard/pccard.c =================================================================== RCS file: /home/ncvs/src/sys/pccard/pccard.c,v retrieving revision 1.73 diff -u -r1.73 pccard.c --- pccard.c 1999/03/10 15:00:54 1.73 +++ pccard.c 1999/04/23 11:18:23 @@ -527,7 +527,7 @@ if (!(mask & imask)) continue; INTRMASK(*maskp, mask); - if (register_pcic_intr(irq, 0, 0, hand, maskp, unit) == 0) { + if (register_pcic_intr(irq, unit, 0, hand, maskp, unit) == 0) { /* add this to the PCIC controller's mask */ if (pcic_imask) INTRMASK(*pcic_imask, (1 << irq)); Index: pci/pcisupport.c =================================================================== RCS file: /home/ncvs/src/sys/pci/pcisupport.c,v retrieving revision 1.100 diff -u -r1.100 pcisupport.c --- pcisupport.c 1999/04/20 11:36:36 1.100 +++ pcisupport.c 1999/04/23 11:20:40 @@ -1166,7 +1166,9 @@ if (pci_get_class(dev) == PCIC_BRIDGE && pci_get_subclass(dev) != PCIS_BRIDGE_PCI && pci_get_subclass(dev) != PCIS_BRIDGE_ISA - && pci_get_subclass(dev) != PCIS_BRIDGE_EISA) + && pci_get_subclass(dev) != PCIS_BRIDGE_EISA + && pci_get_subclass(dev) != PCIS_BRIDGE_PCMCIA + && pci_get_subclass(dev) != PCIS_BRIDGE_CARDBUS) return pci_bridge_type(dev); return NULL; -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 6: 9:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (tele.visi.com [209.98.98.17]) by hub.freebsd.org (Postfix) with ESMTP id 16B6A153E3 for ; Thu, 22 Apr 1999 06:09:34 -0700 (PDT) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 513691F846 for ; Thu, 22 Apr 1999 08:07:05 -0500 (CDT) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with SMTP id IAA19002 for ; Thu, 22 Apr 1999 08:07:05 -0500 (CDT) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Thu, 22 Apr 1999 08:07:05 -0500 (CDT) From: "Thomas T. Veldhouse" To: freebsd-current@freebsd.org Subject: PNP and CURRENT-19990421 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I CVSUP'd last night (4-21-99) to the latest and greatest. I created a completely new kernel configuration file based upon GENERIC and LINT. My problem arose when I added the support for "pnp0". I have a Yamaha sound card (pcm0) which needs PNP. When compiling the kernel, it failed with an error saying the PNP something or other was already defined (sorry, I don't have the output). The funny thing is I went in my configuration file and removed the reference to "pnp0" and recompiled. The kernel compiled just fine and the computer boots ok. However, during the boot process the kernel was doing pnp probes of the hardware. Is PNP a permanant and mandatory feature in the kernel now? If not, how do I remove it? At some point I will take a snapshot of current and put it on my old 486/ISA box (no pnp). Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 6:10:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 33098151CA for ; Thu, 22 Apr 1999 06:10:14 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id JAA08711; Thu, 22 Apr 1999 09:05:32 -0400 (EDT) Message-ID: <002101be8cc1$aa1915a0$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: Cc: "Soren Schmidt" Subject: New IDE Date: Thu, 22 Apr 1999 09:11:41 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I have been using the new IDE drivers on a ASUS P2B-DS (Dual P II with Adaptec SCSI) motherboard without any problems until yesterday afternoon. I noticed that when I booted up yesterday afternoon with the latest build that I no longer had a IDE CD-ROM. In fact dmesg shows that only one controller channel is found, e.g. ata-pci0, ata0 and ad0. I reverted to the "standard" IDE drivers and everything was fine. Anyone have any ideas what has happened? Rick Whitesel Scientist NBase-Xyplex rwhitesel@nbase-xyplex.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 6:14:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 09F6215A0F for ; Thu, 22 Apr 1999 06:13:41 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA36616; Thu, 22 Apr 1999 15:11:09 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904221311.PAA36616@freebsd.dk> Subject: Re: New IDE In-Reply-To: <002101be8cc1$aa1915a0$d3e4b38c@xyplex.com> from Rick Whitesel at "Apr 22, 1999 9:11:41 am" To: rwhitesel@nbase-xyplex.com (Rick Whitesel) Date: Thu, 22 Apr 1999 15:11:09 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Rick Whitesel wrote: > Hi: > I have been using the new IDE drivers on a ASUS P2B-DS (Dual P II > with Adaptec SCSI) motherboard without any problems until yesterday > afternoon. I noticed that when I booted up yesterday afternoon with the > latest build that I no longer had a IDE CD-ROM. In fact dmesg shows that > only one controller channel is found, e.g. ata-pci0, ata0 and ad0. I > reverted to the "standard" IDE drivers and everything was fine. Anyone have > any ideas what has happened? Be sure you have /sys/dev/ata/ata-all.c rev 1.10 or later, there was problems in the first round of Peters changes.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 6:29:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 0498F15A52 for ; Thu, 22 Apr 1999 06:29:16 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA16923; Thu, 22 Apr 1999 22:56:44 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA02671; Thu, 22 Apr 1999 22:57:13 +0930 Date: Thu, 22 Apr 1999 22:57:12 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: _my_ world is broken In-Reply-To: <199904220819.KAA13303@wurzelausix.cs.uni-sb.de> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999, Alexander Leidinger wrote: > c++ -Os -march=pentium -pipe -Wall -fexpensive-optimizations -fomit-frame-pointer -funroll-loops -I/ > usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -c /usr/src/gnu/lib/libgcc/../.. > /../contrib/egcs/gcc/cp/exception.cc -o exception.o > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:33: eh-common.h: No such file or d > irectory > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:89: syntax error before `;' unsetenv CXXFLAGS I don't know if you're supposed to be able to make world with this variable set, but it screws up several things at present. I tripped over this myself a few weeks back. Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 6:36:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 32C58151A1 for ; Thu, 22 Apr 1999 06:36:02 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id JAA09046; Thu, 22 Apr 1999 09:24:06 -0400 (EDT) Message-ID: <001001be8cc4$420ed6e0$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Soren Schmidt" Cc: References: <199904221311.PAA36616@freebsd.dk> Subject: Re: New IDE Date: Thu, 22 Apr 1999 09:30:15 -0400 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.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I am using /sys/dev/ata/ata-all.c rev 1.11. All this worked just fine with the new IDE drivers until yesterday. Rick ----- Original Message ----- From: Soren Schmidt To: Rick Whitesel Cc: Sent: Thursday, April 22, 1999 9:11 AM Subject: Re: New IDE It seems Rick Whitesel wrote: > Hi: > I have been using the new IDE drivers on a ASUS P2B-DS (Dual P II > with Adaptec SCSI) motherboard without any problems until yesterday > afternoon. I noticed that when I booted up yesterday afternoon with the > latest build that I no longer had a IDE CD-ROM. In fact dmesg shows that > only one controller channel is found, e.g. ata-pci0, ata0 and ad0. I > reverted to the "standard" IDE drivers and everything was fine. Anyone have > any ideas what has happened? Be sure you have /sys/dev/ata/ata-all.c rev 1.10 or later, there was problems in the first round of Peters changes.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 6:38: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 2660315A07 for ; Thu, 22 Apr 1999 06:37:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.41.238]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA21421 for ; Thu, 22 Apr 1999 15:35:21 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA05047 for ; Thu, 22 Apr 1999 15:35:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: nice little kernel task for somebody From: Poul-Henning Kamp Date: Thu, 22 Apr 1999 15:35:11 +0200 Message-ID: <5045.924788111@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a thing I've missed a couple of times: I'd like to be able to see the limits for a process in /proc. Any takers ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 6:48:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2F76D15A13 for ; Thu, 22 Apr 1999 06:48:20 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA36709; Thu, 22 Apr 1999 15:45:48 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904221345.PAA36709@freebsd.dk> Subject: Re: New IDE In-Reply-To: <001001be8cc4$420ed6e0$d3e4b38c@xyplex.com> from Rick Whitesel at "Apr 22, 1999 9:30:15 am" To: rwhitesel@nbase-xyplex.com (Rick Whitesel) Date: Thu, 22 Apr 1999 15:45:47 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Rick Whitesel wrote: > Hi: > I am using /sys/dev/ata/ata-all.c rev 1.11. All this worked just fine > with the new IDE drivers until yesterday. Hmm, wierd, I see no problems here.. Try do a config -r configfile, make depend, make and see if the problem is still there... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 7: 0:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (Postfix) with ESMTP id 2EF6A14C19 for ; Thu, 22 Apr 1999 07:00:38 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id XAA02867; Thu, 22 Apr 1999 23:57:50 +1000 (EST) Date: Thu, 22 Apr 1999 23:57:50 +1000 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: Daniel Eischen Cc: current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904221037.GAA08883@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999, Daniel Eischen wrote: > I have to echo these feelings. NFS, as both server and client, is > working without noticeable problems for us under the old 2.2-stable. > I am afraid of upgrading to 3.1-stable with the reported NFS problems, > and we can't get by without NFS. I was refering to the find/grep problem - I tried to start a thread in stable@freebsd.org... > Dan Eischen > eischen@vigrid.com > > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 7:12: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id C8D6414DC0 for ; Thu, 22 Apr 1999 07:12:01 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id KAA09632; Thu, 22 Apr 1999 10:00:06 -0400 (EDT) Message-ID: <002901be8cc9$48dcd620$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Soren Schmidt" Cc: References: <199904221345.PAA36709@freebsd.dk> Subject: Re: New IDE Date: Thu, 22 Apr 1999 10:06:14 -0400 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.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: No change. I forget to mention that there is an ATM card in the system. I am going to build a version that does not support the ATM card or the SCSI. I will let you know what happens. Rick ----- Original Message ----- From: Soren Schmidt To: Rick Whitesel Cc: Sent: Thursday, April 22, 1999 9:45 AM Subject: Re: New IDE It seems Rick Whitesel wrote: > Hi: > I am using /sys/dev/ata/ata-all.c rev 1.11. All this worked just fine > with the new IDE drivers until yesterday. Hmm, wierd, I see no problems here.. Try do a config -r configfile, make depend, make and see if the problem is still there... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 7:29: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3121415A74 for ; Thu, 22 Apr 1999 07:29:06 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA14067; Thu, 22 Apr 1999 23:26:10 +0900 (JST) Message-ID: <371F30F1.5DA29577@newsguy.com> Date: Thu, 22 Apr 1999 23:23:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Steve Kargl Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <199904220454.VAA65522@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl wrote: > > > > That's a little foolish since we've still not found all the egcs > > > optimizer bugs and whatnot; didn't you guys see the one Luigi found > > > the other day for ftpd? Now *that* had to be some obscure debugging > > > work! :-) > > > > Clearly, that goes to show Luigi must have no life... :-) > > > > "Luigi" is an interesting spelling of "Louqi". To my defense, I thought it was Louqi, but since I have been making a lot of mistaken comments lately, I decided to trust what Jordan has said... I just wish april would go away, very, very fast... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 7:59:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id E3DC614C0C for ; Thu, 22 Apr 1999 07:59:23 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA04821; Thu, 22 Apr 1999 10:56:20 -0400 (EDT) (envelope-from luoqi) Date: Thu, 22 Apr 1999 10:56:20 -0400 (EDT) From: Luoqi Chen Message-Id: <199904221456.KAA04821@lor.watermarkgroup.com> To: dcs@newsguy.com, sgk@troutmask.apl.washington.edu Subject: Re: solid NFS patch #6 avail for -current - need testers files) Cc: freebsd-current@FreeBSD.ORG, jkh@zippy.cdrom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Steve Kargl wrote: > > > > > > That's a little foolish since we've still not found all the egcs > > > > optimizer bugs and whatnot; didn't you guys see the one Luigi found > > > > the other day for ftpd? Now *that* had to be some obscure debugging > > > > work! :-) > > > > > > Clearly, that goes to show Luigi must have no life... :-) > > > > > > > "Luigi" is an interesting spelling of "Louqi". > > To my defense, I thought it was Louqi, but since I have been making > a lot of mistaken comments lately, I decided to trust what Jordan > has said... > I thought you guys had better things to do other than arguing about how to spell my name. None of them is correct anyway, it is not even in alphabets... > I just wish april would go away, very, very fast... > Here's a challenge to help you get by the rest of the days, figure out how to write my name, in its original form I was given at birth :-) > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "Well, Windows works, using a loose definition of 'works'..." > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 8:29:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40]) by hub.freebsd.org (Postfix) with ESMTP id 3278B14D64 for ; Thu, 22 Apr 1999 08:29:50 -0700 (PDT) (envelope-from glenn@nola.srrc.usda.gov) Received: from symbion.srrc.usda.gov (localhost [127.0.0.1]) by symbion.srrc.usda.gov (8.9.3/8.9.3) with ESMTP id KAA84938; Thu, 22 Apr 1999 10:26:53 -0500 (CDT) (envelope-from glenn@symbion.srrc.usda.gov) Message-Id: <199904221526.KAA84938@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.3 2/24/98 To: Kris Kennaway Cc: Alexander Leidinger , current@FreeBSD.ORG Subject: Re: _my_ world is broken In-Reply-To: Message from Kris Kennaway of "Thu, 22 Apr 1999 22:57:12 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Apr 1999 10:26:53 -0500 From: Glenn Johnson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, 22 Apr 1999, Alexander Leidinger wrote: > > >unsetenv CXXFLAGS > >I don't know if you're supposed to be able to make world with this >variable set, but it screws up several things at present. I tripped >over this myself a few weeks back. > >Kris > Look in /usr/share/mk/sys.mk and you will find: CXXFLAGS ?= ${CXXINCLUDES} ${CFLAGS} So if you want your CFLAGS used for CXX you do nothing. If you need to set some specific CXXFLAGS that you don't want set in CFLAGS then you need to make sure that you also have ${CXXINCLUDES} listed on your CXXFLAGS line. -- Glenn Johnson Technician USDA, ARS, SRRC New Orleans, LA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 8:34:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A44C314D95; Thu, 22 Apr 1999 08:34:09 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10aLQ8-0007kH-00; Thu, 22 Apr 1999 17:29:44 +0200 From: Sheldon Hearn To: Gerald Pfeifer Cc: Matthew Dillon , Mikhail Teterin , Peter Wemm , current@freebsd.org, stable@freebsd.org Subject: Re: NFSv3 seriously broken in 3.1 In-reply-to: Your message of "Thu, 22 Apr 1999 00:51:03 +0200." Date: Thu, 22 Apr 1999 17:29:44 +0200 Message-ID: <29776.924794984@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999 00:51:03 +0200, Gerald Pfeifer wrote: > Symptoms are the following: We upgraded a perfectly running 2.2.7 client > to 3.1, and out of a sudden NFS performed sluggish, sometimes even hanging > for ten, twenty seconds, even five minutes or more. > > Adding the NFSv2 compatibility option to the AMD tables solved the > problem. CURRENT has been giving me similar problems that weren't (as) obvious in 2.2-STABLE . I've found two client-side work-arounds to improve the situation: 1) Use ``opts:=vers=2,soft,intr'' in /etc/amd.map (see the AMD info page for more details). 2) Don't use AMD. Use direct mounts out of /etc/fstab, eg: src.noc:/a/ncvs /home/ncvs nfs soft,intr 0 0 This causes an apparent hang during FreeBSD boot if the server is unavailable (eg: network fault). Otherwise, all I can suggest is patience. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 8:40:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 5998515176 for ; Thu, 22 Apr 1999 08:40:38 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id LAA11279; Thu, 22 Apr 1999 11:28:08 -0400 (EDT) Message-ID: <001501be8cd5$950f8ea0$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Soren Schmidt" , "Christopher Masto" Cc: References: <199904210647.IAA33104@freebsd.dk> Subject: Re: New ATA driver and crash dumps Date: Thu, 22 Apr 1999 11:34:16 -0400 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.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I built a version that removed the SCSI and ATM support with no change. Something has changed such that only one channel of the PCI IDE controller is reported. I will continue my investigation. Rick ----- Original Message ----- From: Soren Schmidt To: Christopher Masto Cc: Sent: Wednesday, April 21, 1999 2:47 AM Subject: Re: New ATA driver and crash dumps It seems Christopher Masto wrote: > My machine panicked today for the first time since switching to the > new ATA drivers, and I noticed that I no longer have crash dumps. > Is this something that is expected to be put back in soon? > > I know Søren's a busy guy, and I'm glad we have the results of his > work. I just hope the old drivers don't get killed off until the > replacement has the same functionality. > > Then again, wddump() is only 100 lines of code, so I should probably > try to fix it myself before whining. I know :), it has just not been done yet. It will be done eventually but I have other areas in the driver I want finish first. Also the old wd driver will probably not be killed off entirely, as its the only one we have that support old ST506/ESDI drives. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 9:13:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiwi.datasys.net (kiwi.hefty.org [209.119.145.2]) by hub.freebsd.org (Postfix) with ESMTP id AEF101539E for ; Thu, 22 Apr 1999 09:13:26 -0700 (PDT) (envelope-from ayan@kiwi.datasys.net) Received: (from ayan@localhost) by kiwi.datasys.net (8.9.3/8.9.3) id MAA00841 for freebsd-current@freebsd.org; Thu, 22 Apr 1999 12:10:56 -0400 (EDT) (envelope-from ayan) Date: Thu, 22 Apr 1999 12:10:56 -0400 (EDT) From: Ayan George Message-Id: <199904221610.MAA00841@kiwi.datasys.net> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: freebsd-current@freebsd.org Subject: Boot error Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, Ever since installing 4.0-CURRENT, I've gotten the following message when I boot FreeBSD: Disk error 0x1 (lba=0x12007f) No /boot/loader >> FreeBSD/i386 BOOT Default: 0:wd(0,a)kernel boot: If I type: wd(0,a)/boot/loader at the boot prompt, it claims it cant find the file but I know it exists. I can load the kernel from the boot prompt however. I've tried rebuilding /boot/loader from newer source to no avail. There is obviously something I'm overlooking. Has anyone else seen this problem and know how to fix it? -Ayan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 9:17:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.is.co.za (apollo.is.co.za [196.4.160.2]) by hub.freebsd.org (Postfix) with ESMTP id 59469151B8 for ; Thu, 22 Apr 1999 09:17:18 -0700 (PDT) (envelope-from geoff@hangdog.is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by apollo.is.co.za (8.8.6/8.7.5/IShub#2) with ESMTP id SAA05406 for ; Thu, 22 Apr 1999 18:14:48 +0200 (GMT) Received: from hangdog.is.co.za (hangdog.is.co.za [196.23.0.108]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id SAA28783 for ; Thu, 22 Apr 1999 18:14:47 +0200 (GMT) Received: (from geoff@localhost) by hangdog.is.co.za (8.9.3/8.9.2) id SAA00933 for current@freebsd.org; Thu, 22 Apr 1999 18:14:46 +0200 (SAST) (envelope-from geoff) From: Geoff Rehmet Message-Id: <199904221614.SAA00933@hangdog.is.co.za> Subject: newbus - kernel compile failure (old + new PCI drivers) To: current@freebsd.org Date: Thu, 22 Apr 1999 18:14:46 +0200 (SAST) Reply-To: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since the newbus changes, I have had kernel compile failures, due to the fact that I don't have any old style PCI drivers configured on my system. By #ifdef'ing out the code that wraperises the old driver code. Diffs are as follows (this requires defining "NOOLDPCIDRIVERS"). Obviously, this code should eventually all disappear, but is there a more elegant way of doing things at the moment? Are these changes worth committing? *** pci.c.orig Mon Apr 19 08:21:08 1999 --- pci.c Wed Apr 21 23:41:33 1999 *************** *** 846,851 **** --- 846,852 ---- #include "pci_if.h" + #if !defined(NOOLDPCIDRIVERS) /* * A simple driver to wrap the old pci driver mechanism for back-compat. */ *************** *** 921,928 **** --- 922,932 ---- { 0, 0 } }; + #endif + static devclass_t pci_devclass; + #if !defined(NOOLDPCIDRIVERS) /* * Create a new style driver around each old pci driver. */ *************** *** 946,951 **** --- 950,956 ---- devclass_add_driver(pci_devclass, driver); } } + #endif /* * New style pci driver. Parent device is either a pci-host-bridge or a *************** *** 1330,1336 **** --- 1335,1343 ---- { switch (what) { case MOD_LOAD: + #if !defined(NOOLDPCIDRIVERS) pci_wrap_old_drivers(); + #endif break; case MOD_UNLOAD: *** userconfig.c.orig Wed Apr 21 23:45:28 1999 --- userconfig.c Wed Apr 21 23:41:22 1999 *************** *** 570,575 **** --- 570,576 ---- insdev(&scratch,ap[i].id_enabled?active:inactive); } #if NPCI > 0 + #if !defined(NOOLDPCIDRIVERS) for (i = 0; i < pcidevice_set.ls_length; i++) { if (pcidevice_set.ls_items[i]) *************** *** 595,600 **** --- 596,602 ---- } } } + #endif #endif /* NPCI > 0 */ } -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 9:32:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 330FF1539E for ; Thu, 22 Apr 1999 09:32:30 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA09495; Thu, 22 Apr 1999 12:29:56 -0400 (EDT) (envelope-from wollman) Date: Thu, 22 Apr 1999 12:29:56 -0400 (EDT) From: Garrett Wollman Message-Id: <199904221629.MAA09495@khavrinen.lcs.mit.edu> To: KATO Takenori Cc: current@FreeBSD.ORG Subject: newbus resource manager In-Reply-To: <19990422124055N.kato@gneiss.eps.nagoya-u.ac.jp> References: <19990422124055N.kato@gneiss.eps.nagoya-u.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Can newbus resource manager manage discontinuouse I/O port? > Many PC-98 devices use discontinuous I/O port like: > 0x00d0, 0x10d0, 0x20d0, 0x30d0, 0x40d0, ..., 0xf0d0 > Current API seems to assume contiguity and not to be able to manage > such I/O port addresses. Each one of these is a single port, so it needs to be reserved individually. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 9:35:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id B0778152AD; Thu, 22 Apr 1999 09:35:31 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 22 Apr 99 17:32:41 +0100 (BST) To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: nice little kernel task for somebody In-reply-to: Your message of "Thu, 22 Apr 1999 15:35:11 +0200." <5045.924788111@critter.freebsd.dk> X-Request-Do: Date: Thu, 22 Apr 1999 17:32:40 +0100 From: David Malone Message-ID: <9904221732.aa19138@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here's a thing I've missed a couple of times: I'd like to be > able to see the limits for a process in /proc. I'd like to be able to open processes file discriptors too (so you can still get files back if all the filsystem references to it have gone, but a process still has it open). I might have a go at doing both - if it isn't too Linuxesque. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 10:48: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 95B7B15AFD for ; Thu, 22 Apr 1999 10:48:00 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA14474; Fri, 23 Apr 1999 02:45:21 +0900 (JST) Message-ID: <371F5DA2.A9B7C948@newsguy.com> Date: Fri, 23 Apr 1999 02:34:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Ayan George Cc: freebsd-current@FreeBSD.ORG Subject: Re: Boot error References: <199904221610.MAA00841@kiwi.datasys.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ayan George wrote: > > Ever since installing 4.0-CURRENT, I've gotten the following What were you running before? How did you make the upgrade? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 12: 8:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7DE3F14D1E for ; Thu, 22 Apr 1999 12:06:47 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA49682 for ; Thu, 22 Apr 1999 12:04:11 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Prev-Resent: Thu, 22 Apr 1999 12:04:11 -0700 Prev-Resent: "current@freebsd.org " Received: from mta2-rme.xtra.co.nz (mta.xtra.co.nz [203.96.92.3]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id GAA48907 for ; Thu, 22 Apr 1999 06:43:26 -0700 (PDT) (envelope-from junkmale@pop3.xtra.co.nz) Received: from wocker ([210.55.152.128]) by mta2-rme.xtra.co.nz (InterMail v04.00.02.07 201-227-108) with SMTP id <19990422134449.KADL6531620.mta2-rme@wocker> for ; Fri, 23 Apr 1999 01:44:49 +1200 From: "Dan Langille" Organization: The FreeBSD Diary To: jkh@zippy.cdrom.com Date: Fri, 23 Apr 1999 01:42:56 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: ncr scsi doesn't boot Reply-To: junkmale@xtra.co.nz X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990422134449.KADL6531620.mta2-rme@wocker> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's what it is under 2.2.8: Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 ncr0 rev 1 int a irq 11 on pci0:1:0 The following snapshots fail to find it: 3.1-19990421-STABLE no disks found, no PCI probes done 4.0-19990418-CURRENT gets to visual configuration but no PCI probing. 4.0-19990420-CURRENT gets to visual configuration but no PCI probing. 4.0-19990421-CURRENT after visual configuration, it stops at "rootfs is 2880 bytes compiled in MFS". No PCI probes at all. Doesn't get to visual configuration At that point, I gave up. cheers. btw: this is the new NZ mirror I'm trying to set up. Mind you, we can always run it on 2.2.8. But I'd prefer 3.1. -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 12:11:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 4F6B314BE4 for ; Thu, 22 Apr 1999 12:11:20 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 61424 invoked by uid 1001); 22 Apr 1999 19:08:50 +0000 (GMT) To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: 3.1-STABLE is currently broken From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 22 Apr 1999 21:08:50 +0200 Message-ID: <61422.924808130@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... because usr.bin/colldef/data/de_DE.DIS_8859-15.src has been updated: # $Id: de_DE.DIS_8859-15.src,v 1.3.2.1 1999/04/22 08:34:03 foxfair Exp $ without the corresponding update to scan.l and parse.y in the colldef source. End result: ===> usr.bin/colldef/data colldef -I /usr/src/usr.bin/colldef/data -o de_DE.DIS_8859-15.out /usr/src/usr.bin /colldef/data/de_DE.DIS_8859-15.src colldef: syntax error near line 6 *** Error code 69 Stop. *** Error code 1 This is from a 3.1-RELEASE box, attemtping a buildworld to 3.1-STABLE. Using usr.bin/colldef/data/{scan.l,parse.y} from -CURRENT and generating colldef from these seems to fix the problem. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 12:25:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 72FB914D96; Thu, 22 Apr 1999 12:25:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA16505; Thu, 22 Apr 1999 12:22:32 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Apr 1999 12:22:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199904221922.MAA16505@apollo.backplane.com> To: Gerald Pfeifer Cc: Mikhail Teterin , Peter Wemm , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: NFSv3 seriously broken in 3.1 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Symptoms are the following: We upgraded a perfectly running 2.2.7 client :to 3.1, and out of a sudden NFS performed sluggish, sometimes even hanging :for ten, twenty seconds, even five minutes or more. : :Adding the NFSv2 compatibility option to the AMD tables solved the :problem. : :Gerald :-- :Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ It's really hard to say. It kinda sounds like it is trying to use a tcp connection. Make sure AMD is compiled/configured to use UDP with NFSV3, not TCP. AMD defaults to tcp. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 13:15:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 7206E159A0 for ; Thu, 22 Apr 1999 13:15:36 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id QAA15214 for ; Thu, 22 Apr 1999 16:10:53 -0400 (EDT) Message-ID: <000701be8cfd$188f1f80$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: Subject: New IDE drivers problem Date: Thu, 22 Apr 1999 16:17:06 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: As I had stated earlier, the new IDE drivers broke on me yesterday. I have done some investigation and discovered that the ATA driver no longer believes I have any devices on ata1 (I think!). I have included the dmesg text. Any help in solving the problem would be greatly appreciated. Rick Whitesel Scientist NBase-Xyplex rwhitesel@nbase-xyplex.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Thu Apr 22 16:05:29 EDT 1999 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 258252800 (252200K bytes) Programming 24 pins in IOAPIC #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 0xc031b000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 4.0 on pci0 ata-pci0: at device 4.1 on pci0 ata-pci0: type=71118086 class=01 subclass=01 cmd=02800005 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=03 status0=a5 status1=50 ata1: mask=03 status0=50 status1=50 ata1: devices = 0x0 chip2: at device 4.3 on pci0 ahc0: at device 6.0 on pci0 ahc0: interrupting at irq 19 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: at device 9.0 on pci0 fxp0: interrupting at irq 19 fxp0: Ethernet address 00:a0:c9:b7:be:e9 fxp1: at device 10.0 on pci0 fxp1: interrupting at irq 18 fxp1: Ethernet address 00:a0:c9:b7:bf:5f hea0: at device 11.0 on pci0 hea0: interrupting at irq 17 isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 sio2: not probed (disabled) sio3: not probed (disabled) 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/9 bytes threshold ppc0: interrupting at irq 7 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 ds0 XXX: driver didn't set ifq_maxlen SMP: AP CPU #1 Launched! ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) changing root device to wd0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 13:22:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1D11314BEA; Thu, 22 Apr 1999 13:22:12 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA24567; Thu, 22 Apr 1999 13:19:28 -0700 (PDT) (envelope-from obrien) Message-ID: <19990422131928.A24556@nuxi.com> Date: Thu, 22 Apr 1999 13:19:28 -0700 From: "David O'Brien" To: Matthew Dillon , Gerald Pfeifer Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: NFSv3 seriously broken in 3.1 Reply-To: obrien@NUXI.com References: <199904221922.MAA16505@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904221922.MAA16505@apollo.backplane.com>; from Matthew Dillon on Thu, Apr 22, 1999 at 12:22:32PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Make sure AMD is compiled/configured to use UDP with NFSV3, not TCP. > AMD defaults to tcp. I made a commit to -STABLE a few weeks ago (but not -CURRENT) that should have made v3/udp the default. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 13:26:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 0F8DC14EBA; Thu, 22 Apr 1999 13:26:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA16923; Thu, 22 Apr 1999 13:23:56 -0700 (PDT) (envelope-from dillon) Date: Thu, 22 Apr 1999 13:23:56 -0700 (PDT) From: Matthew Dillon Message-Id: <199904222023.NAA16923@apollo.backplane.com> To: "David O'Brien" Cc: Gerald Pfeifer , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: NFSv3 seriously broken in 3.1 References: <199904221922.MAA16505@apollo.backplane.com> <19990422131928.A24556@nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Make sure AMD is compiled/configured to use UDP with NFSV3, not TCP. :> AMD defaults to tcp. : :I made a commit to -STABLE a few weeks ago (but not -CURRENT) that should :have made v3/udp the default. : :-- :-- David (obrien@NUXI.com -or- obrien@FreeBSD.org) Ah, cool. I'll bet the author was using the 3.1 CD's Fixing TCP is on the list, but probably won't happen for a while ( though if other people want to take a crack at it I'll accept patches ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 13:38:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 5672B14EBA for ; Thu, 22 Apr 1999 13:38:23 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id QAA00295 for ; Thu, 22 Apr 1999 16:38:40 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Thu, 22 Apr 1999 16:38:40 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: pcm broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For some reason, when I rebuilt the kernel after a cvsup this morning, sound will no longer work. It gives this kernel warning when I try to play sound: timeout flushing dbuf_out, chan 1 cnt 0xff00 flags 0x000000c1 sound worked fine yesterday, before I cvsupped. Thanks. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 14: 7:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (196-7-192-117.iafrica.com [196.7.192.117]) by hub.freebsd.org (Postfix) with ESMTP id 91E8915A36 for ; Thu, 22 Apr 1999 14:07:38 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA19051; Thu, 22 Apr 1999 23:03:24 +0200 (SAT) From: Robert Nordier Message-Id: <199904222103.XAA19051@ceia.nordier.com> Subject: Re: Boot error In-Reply-To: <199904221610.MAA00841@kiwi.datasys.net> from Ayan George at "Apr 22, 99 12:10:56 pm" To: ayan@kiwi.datasys.net (Ayan George) Date: Thu, 22 Apr 1999 23:03:22 +0200 (SAT) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ayan George wrote: > Ever since installing 4.0-CURRENT, I've gotten the following > message when I boot FreeBSD: > > Disk error 0x1 (lba=0x12007f) > No /boot/loader > > >> FreeBSD/i386 BOOT > Default: 0:wd(0,a)kernel > > boot: > > > If I type: > > wd(0,a)/boot/loader > > at the boot prompt, it claims it cant find the file but I know it > exists. > > I can load the kernel from the boot prompt however. I've tried > rebuilding /boot/loader from newer source to no avail. > > There is obviously something I'm overlooking. Has anyone else seen > this problem and know how to fix it? > > -Ayan Disk error 0x1 means "invalid argument". The most likely cause is that your / filesystem spans cylinder 1023 and /boot/loader is inaccessible for this reason. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 16:13:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from sagan.askjeeves.com (sagan.askjeeves.com [204.71.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D9CD15A03 for ; Thu, 22 Apr 1999 16:13:23 -0700 (PDT) (envelope-from jnordwick@Ask.com) Received: by sagan.askjeeves.com with Internet Mail Service (5.5.2448.0) id ; Thu, 22 Apr 1999 16:11:13 -0700 Message-ID: <959045D7661AD211BA5200A0C983766A7384B8@sagan.askjeeves.com> From: Jason Nordwick To: "'current@freebsd.org'" Subject: IMPT HELP: maxproc at 128 Date: Thu, 22 Apr 1999 16:11:11 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /etc/login.conf has a default entry of unlimited for maxproc. I need more processes to be run (in the kernel config the MAXUSER is 256). please help, jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 19:50:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 7B3CD1521B for ; Thu, 22 Apr 1999 19:50:29 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id WAA00298 for ; Thu, 22 Apr 1999 22:50:46 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Thu, 22 Apr 1999 22:50:46 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: Re: pcm broken In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For some reason, when I rebuilt the kernel after a cvsup this morning, sound will no longer work. It gives this kernel warning when I try to play sound: timeout flushing dbuf_out, chan 1 cnt 0xff00 flags 0x000000c1 sound worked fine yesterday, before I cvsupped. Can anyone give me an idea as to what happened here? Any help would be appreciated. Thanks. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 20: 2:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id CC16F14F00 for ; Thu, 22 Apr 1999 20:02:45 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA49665; Thu, 22 Apr 1999 22:58:19 -0400 (EDT) Date: Thu, 22 Apr 1999 22:58:19 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: chris@netmonger.net, current@FreeBSD.ORG Subject: Re: New ATA driver and crash dumps In-Reply-To: <199904221138.NAA36443@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > >> Hmm, I have a ZIP here which works, and I have reports from mike that > >> his LS120 works too, so I'm a bit confused here. > >> How does it not work ?? > > > >I get consistent errors reading from it (not hard errors, data errors). = The > >md5 checksums I created on the disk using the wd driver do not match the > >varying checksums md5 gives me on the LS-120 with the new ATA. >=20 > Hmm, does it still work with the old driver ?? Yep, flawlessly. > Does it share the channel with another device ?? (ata/atapi??) ata0: master: settting up UDMA2 mode on Aladdin chip OK ad0: ATA-4 disk at ata0 as master ad0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=3D4, dmamode=3D2, udmamode=3D2 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: slave: settting up WDMA2 mode on Aladdin chip OK ad3: ATA-? disk at ata1 as slave=20 ad3: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad3: piomode=3D4, dmamode=3D2, udmamode=3D-1 ad3: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata0 as slave=20 acd0: drive speed 2067KB/sec, 128KB cache acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked afd0: rewriteable drive at ata1 as mas= ter afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S afd0: Unknown media (0x0) > It sounds like a HW problem of some sort to me.. >=20 Or one that's exacerbated by the new drivers. > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman _ __ ___ ____ ___ ___ ___ =20 green@unixhelp.org _ __ ___ | _ ) __| \=20 FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 20:17:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id DF01714DA5 for ; Thu, 22 Apr 1999 20:17:27 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA49944; Thu, 22 Apr 1999 23:15:00 -0400 (EDT) Date: Thu, 22 Apr 1999 23:15:00 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Luoqi Chen Cc: dcs@newsguy.com, sgk@troutmask.apl.washington.edu, freebsd-current@FreeBSD.ORG, jkh@zippy.cdrom.com Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904221456.KAA04821@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999, Luoqi Chen wrote: > > Steve Kargl wrote: > > > > > > > > That's a little foolish since we've still not found all the egcs > > > > > optimizer bugs and whatnot; didn't you guys see the one Luigi found > > > > > the other day for ftpd? Now *that* had to be some obscure debugging > > > > > work! :-) > > > > > > > > Clearly, that goes to show Luigi must have no life... :-) > > > > > > > > > > "Luigi" is an interesting spelling of "Louqi". > > > > To my defense, I thought it was Louqi, but since I have been making > > a lot of mistaken comments lately, I decided to trust what Jordan > > has said... > > > I thought you guys had better things to do other than arguing about how > to spell my name. None of them is correct anyway, it is not even in > alphabets... > > > I just wish april would go away, very, very fast... > > > Here's a challenge to help you get by the rest of the days, figure out > how to write my name, in its original form I was given at birth :-) Hmm... is it cheating to use Hiragana? (^_^) > > > -- > > Daniel C. Sobral (8-DCS) > > dcs@newsguy.com > > dcs@freebsd.org > > > > "Well, Windows works, using a loose definition of 'works'..." > > > > -lq > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 20:23: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id 2F37514BFE for ; Thu, 22 Apr 1999 20:22:52 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id NAA21980; Fri, 23 Apr 1999 13:20:10 +1000 (EST) Message-ID: <19990423132010.D21645@rf900.physics.usyd.edu.au> Date: Fri, 23 Apr 1999 13:20:10 +1000 From: David Dawes To: Amancio Hasty Cc: Freebsd-current@FreeBSD.ORG Subject: Re: USB keyboard attach function? References: <19990422184319.G18359@rf900.physics.usyd.edu.au> <199904220901.CAA09789@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904220901.CAA09789@rah.star-gate.com>; from Amancio Hasty on Thu, Apr 22, 1999 at 02:01:35AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 22, 1999 at 02:01:35AM -0700, Amancio Hasty wrote: >Just a kind reminder we can unplug and plug a usb mouse as >well as a usb keyboard currently we have a small problem with >moused that it does not attempt to gain access of the mouse if there >is a usb disconnect / connect sequence. I'll let you OS guys sort that out with moused first :-). We have an X server extension that allows a pointer device to be reopened (and reconfigured) This was intended mainly for use by configuration tools, but it could be used by some daemon to tell the X server to reopen the mouse, and maybe change its parameters. It might turn out that it is easier to handle this solely within moused, and just configure the X server to use moused. We'll keep this sort of thing in mind as we rework the input device handling for XFree86 4.0. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 21:25:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprtp.nortel.com (smtprtp.NortelNetworks.com [192.122.117.66]) by hub.freebsd.org (Postfix) with ESMTP id CA92414C59 for ; Thu, 22 Apr 1999 21:25:48 -0700 (PDT) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtprtp.nortel.com; Fri, 23 Apr 1999 00:21:44 -0400 Received: from hcarp00g.ca.nortel.com by zcars01t; Fri, 23 Apr 1999 00:21:25 -0400 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id AAA01156; Fri, 23 Apr 1999 00:21:38 -0400 (EDT) Date: Fri, 23 Apr 1999 00:21:38 -0400 (EDT) From: "Andrew Atrens" Reply-To: "Andrew Atrens" To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: pcm broken In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ken, I can't offer you any help, just moral support :P - mine just broke too. Same message. Andrew. On Thu, 22 Apr 1999, Kenneth Wayne Culver wrote: > Date: Thu, 22 Apr 1999 22:50:46 -0400 (EDT) > From: Kenneth Wayne Culver > To: freebsd-current@freebsd.org > Subject: Re: pcm broken > > For some reason, when I rebuilt the kernel after a cvsup this morning, > sound will no longer work. It gives this kernel warning when I try to play > sound: > > timeout flushing dbuf_out, chan 1 cnt 0xff00 flags 0x000000c1 > > sound worked fine yesterday, before I cvsupped. > > Can anyone give me an idea as to what happened here? Any help would be > appreciated. > > Thanks. > > Kenneth Culver > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 23: 6: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id BFD9D15138 for ; Thu, 22 Apr 1999 23:05:55 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA09482 for ; Fri, 23 Apr 1999 15:33:25 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA96610 for FreeBSD-current@FreeBSD.ORG; Fri, 23 Apr 1999 15:33:24 +0930 (CST) Date: Fri, 23 Apr 1999 15:33:23 +0930 From: Greg Lehey To: FreeBSD current users Subject: Problems with symbol sequences in recent kernels Message-ID: <19990423153323.P91260@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just had a strange experience. I have some gdb macros which I use for debugging Vinum. One, ps, gives me a ps-like listing: (kgdb) ps Check your .gdbinit, it contains a y command pid proc addr uid ppid pgrp flag stat comm wchan 1544 c68a5100 c6df3000 0 1534 1544 004006 2 Vinum 1534 c68a57e0 c6ddb000 0 1524 1534 004086 3 bash wait c68a57e0 1524 c68a5c00 c6dc9000 1004 1516 1524 004086 3 bash wait c68a5c00 Another macro helps me load symbols from a kld: Without: (kgdb) bt #0 Debugger (msg=0xc11696a0 "vinum debug") at ../../i386/i386/db_interface.c:318 #1 0xc1163585 in ?? () #2 0xc01826ea in spec_ioctl (ap=0xc6df4e1c) at ../../miscfs/specfs/spec_vnops.c:440 With: (kgdb) bt #0 Debugger (msg=0xc11696a0 "vinum debug") at ../../i386/i386/db_interface.c:318 #1 0xc1163585 in vinumioctl (dev=0x40001901, cmd=0xc008464b, data=0xc6df4ee0 "", flag=0x3, p=0xc68a5100) at /src/PANIC/src/sys/modules/Vinum/../../dev/Vinum/vinumioctl.c:96 #2 0xc01826ea in spec_ioctl (ap=0xc6df4e1c) at ../../miscfs/specfs/spec_vnops.c:440 This has worked quite nicely for some time. Since yesterday, after building a kernel with newbus support, I get strange messages if I read in the Vinum symbols before reading in the kernel symbols: (kgdb) bt #0 Debugger (msg=0xc11696a0 "vinum debug") at ../../i386/i386/db_interface.c:318 #1 0xc1163585 in vinumioctl (dev=0x40001901, cmd=0xc008464b, data=0xc6df4ee0 "", flag=0x3, p=0xc68a5100) at /src/PANIC/src/sys/modules/Vinum/../../dev/Vinum/vinumioctl.c:96 During symbol reading, "repeated" header file opt_global.h not previously seen, at symtab pos 23. During symbol reading, Invalid symbol data: type number (2,2) out of range at symtab pos 25.. #2 0xc01826ea in spec_ioctl (ap=0xc6df4e1c) at ../../miscfs/specfs/spec_vnops.c:440 The following stack frames also look strange: #5 0xc017ccdd in vn_ioctl (fp=, com=, data=, p=) at vnode_if.h:395 #6 0xc015c5f7 in ioctl (p=0xc68a5100, uap=0xc6df4f94) at ../../kern/sys_generic.c:564 #7 0xc021e916 in syscall (frame=) at ../../i386/i386/trap.c:1071 I debugged gdb and found that it was finding these references (opt_global.h) in cd9660_rrip.o, which it read after reading the Vinum kld symbols. If I can convince it to read the kernel symbols first, I don't have any trouble. I don't think that it's anything to do with that particular file; there must be about 30 files in a typical kernel build which refer to this symbol. If I don't get any response on the list, I'll put in a PR, but I thought there's a good chance that somebody will recognize this problem and be able to fix it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 23:49: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2883114E65 for ; Thu, 22 Apr 1999 23:49:05 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id PAA02913; Fri, 23 Apr 1999 15:46:23 +0900 (JST) Message-ID: <37200AF7.4BF4607A@newsguy.com> Date: Fri, 23 Apr 1999 14:53:59 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Brian Feldman Cc: Luoqi Chen , sgk@troutmask.apl.washington.edu, freebsd-current@FreeBSD.ORG, jkh@zippy.cdrom.com Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > > > > I just wish april would go away, very, very fast... > > > > > Here's a challenge to help you get by the rest of the days, figure out > > how to write my name, in its original form I was given at birth :-) > > Hmm... is it cheating to use Hiragana? (^_^) Being a chinese name (I think -- not a japanese one, for sure), I don't think it will help. Besides, you can't spell an L in hiragana. :-) My own take is (japanese characters -- sorry, no chinese input) $BDD(B for Chen. For Luoqi, japanese shift-jis/euc-jp just won't do. Well, I cheated, anyway... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 22 23:59:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 82DF514E65 for ; Thu, 22 Apr 1999 23:59:16 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA71685 for ; Fri, 23 Apr 1999 00:56:23 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA05028 for ; Fri, 23 Apr 1999 00:56:19 -0600 (MDT) Message-Id: <199904230656.AAA05028@harmony.village.org> To: current@freebsd.org Subject: Cross patches Date: Fri, 23 Apr 1999 00:56:19 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had a bunch of requests for what I'm using to cross build. I've put up the cross compilation development patches that I have done so far at http://www.village.org/villagers/imp/freebsd-cross-1.patch.gz for anybody to give a test spin. There are no directions, but if you do a make buildworld TARGET=i386 TARGET_ARCH=i386 on an alpha, you should get a complete i386 world that can be installed on a i386 machine. It is critically important that you include both the TARGET and TARGET_ARCH on the command line, otherwise this won't work. They patch the two files that I needed to patch to get the cross building stuff working. However, note that so far I've not gotten past building the libraries on mips, due to kernel include files I've not written/imported yet, so I don't know how far it will make it. I release these patches in the hopes they are useful. I don't know if this is the direction that FreeBSD wants to take wrt cross building binaries or not. It is certainly a good learning experience. I also don't know if our tools are up to the task of generating working alpha code on a i386 box. I got all kinds of warnings when I tried to do that which lead me to believe that the answer was no (things like shifts > 32 bits). Please let me know what you think of these patches. If you have updates to them, please let me know. I'd have to characterize them as a "rapid prototyping learning experience" at the moment. However, every time I tried to do something more elegant I ran into boatloads of problems. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 0:19: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from dslab7.cs.uit.no (dslab7.cs.UiT.No [129.242.16.27]) by hub.freebsd.org (Postfix) with ESMTP id 2914914F38 for ; Fri, 23 Apr 1999 00:19:05 -0700 (PDT) (envelope-from frodef@dslab7.cs.uit.no) Received: (from frodef@localhost) by dslab7.cs.uit.no (8.9.2/8.9.1) id JAA06708; Fri, 23 Apr 1999 09:15:52 +0200 (CEST) (envelope-from frodef) To: freebsd-current@freebsd.org Subject: Re: lnc0: broke for us between 3.1 and 4.0? References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Frode Vatvedt Fjeld Date: 23 Apr 1999 09:15:52 +0200 In-Reply-To: paul@originative.co.uk's message of "Tue, 20 Apr 1999 00:16:37 +0100" Message-ID: <2h3e1rbydz.fsf@dslab7.cs.uit.no> Lines: 22 User-Agent: Gnus/5.07008 (Pterodactyl Gnus v0.80) Emacs/20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG paul@originative.co.uk writes: > > From: Richard Tobin [mailto:richard@cogsci.ed.ac.uk] > > Is this fix going into stable? (I'm a little surprised that such a > > change was considered appropriate for the stable branch in the first > > place.) > > I didn't think the memory allocation change was in stable but I may merge > the lnc changes back into -stable anyway since it's a cleaner way of doing > things. > > I've got some other lnc problems to fix first though. Will this take very long? Because my "stable" source tree has not produced a working kernel for me for several weeks because of this. And does this all mean that if I want my kernel source tree to be consistent more often than not (and any errors be fixed as soon as possible), I'd be better off switching from -stable to -current? -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 0:26:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 168C01517D for ; Fri, 23 Apr 1999 00:26:19 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id JAA29735; Fri, 23 Apr 1999 09:23:47 +0200 (MET DST) Date: Fri, 23 Apr 1999 09:23:46 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Frode Vatvedt Fjeld Cc: freebsd-current@FreeBSD.ORG Subject: Re: lnc0: broke for us between 3.1 and 4.0? In-Reply-To: <2h3e1rbydz.fsf@dslab7.cs.uit.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And does this all mean that if I want my kernel source tree to be > consistent more often than not (and any errors be fixed as soon as > possible), I'd be better off switching from -stable to -current? Yes and no. Stable will give you a broken tree less often. But people in Current have a habit of fixing things first in Current :-) The ideal combination: Running stable and keeping track of current, backporting whatever you think is of use to you. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 2:19:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 50D8615A42 for ; Fri, 23 Apr 1999 02:19:16 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 14105 invoked by uid 1008); 23 Apr 1999 09:16:33 -0000 Message-ID: <19990423091633.14103.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: freebsd-current@freebsd.org Cc: phk@freebsd.org Subject: Re: nice little kernel task for somebody In-reply-to: Your message of "Thu, 22 Apr 1999 17:32:40 +0100." <9904221732.aa19138@salmon.maths.tcd.ie> Date: Fri, 23 Apr 1999 17:16:33 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone writes: >> Here's a thing I've missed a couple of times: I'd like to be >> able to see the limits for a process in /proc. > >I'd like to be able to open processes file discriptors too (so >you can still get files back if all the filsystem references to >it have gone, but a process still has it open). I might have a >go at doing both - if it isn't too Linuxesque. I don't know about that one, but the first one sounds easish. Since I've been messing around with procfs quite a bit lately, I'll spend some time later today poking around and produce a patch against -current . Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 3:16:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 26CCC14D31 for ; Fri, 23 Apr 1999 03:16:52 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 14357 invoked by uid 1008); 23 Apr 1999 10:14:18 -0000 Message-ID: <19990423101418.14355.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: freebsd-current@freebsd.org Subject: kernel build from a non-/usr/src/sys directory failing? Date: Fri, 23 Apr 1999 18:14:17 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just went to config a kernel on a -current system supped yesterday, with the source sitting in my home directory,and suddenly .. adrian@java:/usr/home/adrian/work/procfs/sys/compile/JAVA$ make depend make: don't know how to make ../../../include/stddef.h. Stop adrian@java:/usr/home/adrian/work/procfs/sys/compile/JAVA$ Now, I could swear to god this used to work.. any ideas? Adrian -- Adrian Chadd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 3:26:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 7776C15139 for ; Fri, 23 Apr 1999 03:26:18 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 14411 invoked by uid 1008); 23 Apr 1999 10:23:47 -0000 Message-ID: <19990423102347.14409.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Mikhail Teterin Cc: freebsd-current@freebsd.org Subject: Re: kernel build from a non-/usr/src/sys directory failing? In-reply-to: Your message of "Fri, 23 Apr 1999 06:19:12 -0400." <199904231019.GAA25250@kot.ne.mediaone.net> Date: Fri, 23 Apr 1999 18:23:47 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin writes: >adrian@FreeBSD.ORG once stated: > >=I just went to config a kernel on a -current system supped yesterday, >=with the source sitting in my home directory,and suddenly .. >= >=adrian@java:/usr/home/adrian/work/procfs/sys/compile/JAVA$ make depend >=make: don't know how to make ../../../include/stddef.h. Stop >=adrian@java:/usr/home/adrian/work/procfs/sys/compile/JAVA$ >= >=Now, I could swear to god this used to work.. any ideas? > >Look for stale .depend file(s)... > > -mi Ignore my temporary insanity ladies and gentlemen, suffice to say the coffee machine is percolating as we speak. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 5: 0:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 87FDA15235 for ; Fri, 23 Apr 1999 05:00:30 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id HAA20926 for ; Fri, 23 Apr 1999 07:55:47 -0400 (EDT) Message-ID: <003801be8d81$19342d20$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: Subject: New IDE Drivers Date: Fri, 23 Apr 1999 08:02:01 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I believe the problems I started having with the new IDE drivers may be related to the bugs in the SMP IRQ handler described by Roger Hardiman. I am going to wait until Roger fixes the bug to see if my IDE problem disappears. I tried the latest drivers on a non SMP motherboard and they work fine! Rick Whitesel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 5:10: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.51]) by hub.freebsd.org (Postfix) with ESMTP id D1903151B1; Fri, 23 Apr 1999 05:09:31 -0700 (PDT) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id MAA78614; Fri, 23 Apr 1999 12:05:50 GMT (envelope-from zach) Date: Fri, 23 Apr 1999 07:05:49 -0500 From: Zach Heilig To: adrian@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: nice little kernel task for somebody Message-ID: <19990423070549.A78489@k6n1.znh.org> References: <9904221732.aa19138@salmon.maths.tcd.ie> <19990423091633.14103.qmail@ewok.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990423091633.14103.qmail@ewok.creative.net.au>; from adrian@freebsd.org on Fri, Apr 23, 1999 at 05:16:33PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 23, 1999 at 05:16:33PM +0800, adrian@freebsd.org wrote: > I don't know about that one, but the first one sounds easish. > Since I've been messing around with procfs quite a bit lately, > I'll spend some time later today poking around and produce a patch > against -current . I don't know how to do this, but I did notice this much: (the binary does remain accessible even after it's removed, as long as it doesn't exit). #include #include #include #include int main(int argc, char **argv) { int id; char cmd[128]; unlink(argv[0]); id = getpid(); printf("pid == %d\n", id); sprintf(cmd, "ls -l /proc/%d", id); system(cmd); exit(0); } $ cc foo.c $ ./a.out pid == 78597 total 4 -r--r--r-- 1 zach wheel 0 Apr 23 07:00 cmdline --w------- 1 zach wheel 0 Apr 23 07:00 ctl -r--r--r-- 1 zach wheel 76 Apr 23 07:00 etype -rwxrwxr-x 0 zach wheel 3637 Apr 23 07:00 file -rw------- 1 zach wheel 176 Apr 23 07:00 fpregs -r--r--r-- 1 zach wheel 76 Apr 23 07:00 map -rw-r----- 1 zach kmem 0 Apr 23 07:00 mem --w------- 1 zach wheel 0 Apr 23 07:00 note --w------- 1 zach wheel 0 Apr 23 07:00 notepg -rw------- 1 zach wheel 76 Apr 23 07:00 regs -r--r--r-- 1 zach wheel 0 Apr 23 07:00 status $ [note the '0' links for the binary] -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 5:33:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 87342150D0 for ; Fri, 23 Apr 1999 05:33:41 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 14694 invoked by uid 1008); 23 Apr 1999 12:31:08 -0000 Message-ID: <19990423123108.14692.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Zach Heilig Cc: freebsd-current@freebsd.org Subject: Re: nice little kernel task for somebody In-reply-to: Your message of "Fri, 23 Apr 1999 07:05:49 EST." <19990423070549.A78489@k6n1.znh.org> Date: Fri, 23 Apr 1999 20:31:07 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zach Heilig writes: >On Fri, Apr 23, 1999 at 05:16:33PM +0800, adrian@freebsd.org wrote: >> I don't know about that one, but the first one sounds easish. >> Since I've been messing around with procfs quite a bit lately, >> I'll spend some time later today poking around and produce a patch >> against -current . > >I don't know how to do this, but I did notice this much: (the binary does >remain accessible even after it's removed, as long as it doesn't exit). > >#include >#include >#include >#include > >int main(int argc, char **argv) { > int id; > char cmd[128]; > unlink(argv[0]); > id = getpid(); > printf("pid == %d\n", id); > sprintf(cmd, "ls -l /proc/%d", id); > system(cmd); > exit(0); >} > >$ cc foo.c >$ ./a.out >pid == 78597 >total 4 >-r--r--r-- 1 zach wheel 0 Apr 23 07:00 cmdline >--w------- 1 zach wheel 0 Apr 23 07:00 ctl >-r--r--r-- 1 zach wheel 76 Apr 23 07:00 etype >-rwxrwxr-x 0 zach wheel 3637 Apr 23 07:00 file >-rw------- 1 zach wheel 176 Apr 23 07:00 fpregs >-r--r--r-- 1 zach wheel 76 Apr 23 07:00 map >-rw-r----- 1 zach kmem 0 Apr 23 07:00 mem >--w------- 1 zach wheel 0 Apr 23 07:00 note >--w------- 1 zach wheel 0 Apr 23 07:00 notepg >-rw------- 1 zach wheel 76 Apr 23 07:00 regs >-r--r--r-- 1 zach wheel 0 Apr 23 07:00 status >$ > >[note the '0' links for the binary] > Which is right though, isn't it? I've finished the patch. I'll test it a little more when I get back home tonight, and then send the URL to -current for people to poke around with. phk - I hope you didn't also want the process limits to be modifyable the same way just yet :-) (but it'd be nice however... maybe later.) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 5:37:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 91AD615094; Fri, 23 Apr 1999 05:37:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id OAA25840; Fri, 23 Apr 1999 14:34:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id OAA02560; Fri, 23 Apr 1999 14:34:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: adrian@FreeBSD.ORG Cc: Zach Heilig , freebsd-current@FreeBSD.ORG Subject: Re: nice little kernel task for somebody In-reply-to: Your message of "Fri, 23 Apr 1999 20:31:07 +0800." <19990423123108.14692.qmail@ewok.creative.net.au> Date: Fri, 23 Apr 1999 14:34:50 +0200 Message-ID: <2558.924870890@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990423123108.14692.qmail@ewok.creative.net.au>, adrian@FreeBSD.OR G writes: >I've finished the patch. I'll test it a little more when I get back >home tonight, and then send the URL to -current for people to poke >around with. > Cool! >phk - I hope you didn't also want the process limits to be modifyable >the same way just yet :-) (but it'd be nice however... maybe later.) No, I just want a way to figure out what login.conf have done to various processes... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 5:47:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id E44AA14D4D; Fri, 23 Apr 1999 05:47:34 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Fri, 23 Apr 1999 13:44:33 +0100 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id JKMQ3M54; Fri, 23 Apr 1999 13:37:46 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10afNZ-000DVP-00; Fri, 23 Apr 1999 13:48:25 +0100 To: Poul-Henning Kamp Cc: adrian@FreeBSD.ORG, Zach Heilig , freebsd-current@FreeBSD.ORG Subject: Re: nice little kernel task for somebody X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: Poul-Henning Kamp's message of "Fri, 23 Apr 1999 14:34:50 +0200" <2558.924870890@critter.freebsd.dk> Date: Fri, 23 Apr 1999 13:48:25 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 April 1999, Poul-Henning Kamp proclaimed: > No, I just want a way to figure out what login.conf have done to > various processes... What we really need are some tools similiar to solaris' /usr/proc/bin stuff. http://www.sunworld.com/swol-04-1999/swol-04-supersys.html Sadly, the ability to do this lies well outside my meagre coding knowledge. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Value of 2 may go down as well as up" -- FORTRAN programmers manual -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 6:26:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 44D8715278 for ; Fri, 23 Apr 1999 06:26:41 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA00657; Fri, 23 Apr 1999 13:10:31 +0200 From: Luigi Rizzo Message-Id: <199904231110.NAA00657@labinfo.iet.unipi.it> Subject: does login.conf limitations work ? To: current@freebsd.org Date: Fri, 23 Apr 1999 13:10:30 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 910 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i was wondering if the limitations that are supposed to be enforced via the login.conf mechanism do really work... In particular, i have tried (on 3.1 something, but don't think that current is much different in this respect) to enforce the daily etc. login times but the system seems to ignore them. I think /etc/login.conf is properly parsed, because if i assign a user to a class that is not defined in login.conf i get complaints, but other than that i am unable to limit login time... Any hints ? cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 6:55: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 40EC11544D for ; Fri, 23 Apr 1999 06:54:59 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 14957 invoked by uid 1008); 23 Apr 1999 13:45:07 -0000 Message-ID: <19990423134507.14955.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Dom Mitchell Cc: freebsd-current@freebsd.org Subject: Re: nice little kernel task for somebody In-reply-to: Your message of "Fri, 23 Apr 1999 13:48:25 +0100." Date: Fri, 23 Apr 1999 21:45:06 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell writes: >On 23 April 1999, Poul-Henning Kamp proclaimed: >> No, I just want a way to figure out what login.conf have done to >> various processes... > >What we really need are some tools similiar to solaris' /usr/proc/bin >stuff. http://www.sunworld.com/swol-04-1999/swol-04-supersys.html >Sadly, the ability to do this lies well outside my meagre coding >knowledge. A few of those utilities are avaliable right now (hell, I even wrote a pstree command to get a process tree listing a few months ago when I started messing about with procfs, but its rather crude atm), along with pcred, pflags, pgrep, plimit with what I've just written, and with a little magic, pmap, ptime, and the rest of them. But we'd need to extend our procfs just a little bit to work real magic (like say, proc-ps / proc-top), and I'm not prepared to start messing around with it in a big way, but if people are interested in a bunch of utilities like the sun /usr/proc/bin/ utilities, I might go ahead and write some. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 7:37:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 2575C15362; Fri, 23 Apr 1999 07:37:08 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Fri, 23 Apr 1999 15:34:01 +0100 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id JKMQ3M7N; Fri, 23 Apr 1999 15:27:14 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10ah5V-000Da6-00; Fri, 23 Apr 1999 15:37:53 +0100 To: adrian@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: nice little kernel task for somebody X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: adrian@freebsd.org's message of "Fri, 23 Apr 1999 21:45:06 +0800" <19990423134507.14955.qmail@ewok.creative.net.au> Date: Fri, 23 Apr 1999 15:37:52 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 April 1999, adrian@freebsd.org proclaimed: > Dom Mitchell writes: > >What we really need are some tools similiar to solaris' /usr/proc/bin > >stuff. http://www.sunworld.com/swol-04-1999/swol-04-supersys.html > >Sadly, the ability to do this lies well outside my meagre coding > >knowledge. > > A few of those utilities are avaliable right now (hell, I even wrote > a pstree command to get a process tree listing a few months ago when > I started messing about with procfs, but its rather crude atm), along > with pcred, pflags, pgrep, plimit with what I've just written, > and with a little magic, pmap, ptime, and the rest of them. I actually find these little tools to be very useful indeed. They make investigating rogue daemons and suchlike far easier. And pmap is wonderful for working out how much memory something is really taking up, in detail. > But we'd need to extend our procfs just a little bit to work real > magic (like say, proc-ps / proc-top), and I'm not prepared to > start messing around with it in a big way, but if people are interested > in a bunch of utilities like the sun /usr/proc/bin/ utilities, > I might go ahead and write some. Well, I'd certainly be very grateful! Sign me up for testing your patches... As for making ps totally proc aware, I'm not totally sure that's the way to go. I shall have to have a look through the archives though; I've a feeling that this has been discussed before... -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Value of 2 may go down as well as up" -- FORTRAN programmers manual -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 7:47:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 61A8914D46 for ; Fri, 23 Apr 1999 07:47:52 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 15116 invoked by uid 1008); 23 Apr 1999 14:45:20 -0000 Message-ID: <19990423144520.15114.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Dom Mitchell Cc: freebsd-current@freebsd.org Subject: Re: nice little kernel task for somebody In-reply-to: Your message of "Fri, 23 Apr 1999 15:37:52 +0100." Date: Fri, 23 Apr 1999 22:45:19 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell writes: >On 23 April 1999, adrian@freebsd.org proclaimed: >> Dom Mitchell writes: >> >What we really need are some tools similiar to solaris' /usr/proc/bin >> >stuff. http://www.sunworld.com/swol-04-1999/swol-04-supersys.html >> >Sadly, the ability to do this lies well outside my meagre coding >> >knowledge. >> >> A few of those utilities are avaliable right now (hell, I even wrote >> a pstree command to get a process tree listing a few months ago when >> I started messing about with procfs, but its rather crude atm), along >> with pcred, pflags, pgrep, plimit with what I've just written, >> and with a little magic, pmap, ptime, and the rest of them. > >I actually find these little tools to be very useful indeed. They make >investigating rogue daemons and suchlike far easier. And pmap is >wonderful for working out how much memory something is really taking up, >in detail. > >> But we'd need to extend our procfs just a little bit to work real >> magic (like say, proc-ps / proc-top), and I'm not prepared to >> start messing around with it in a big way, but if people are interested >> in a bunch of utilities like the sun /usr/proc/bin/ utilities, >> I might go ahead and write some. > >Well, I'd certainly be very grateful! Sign me up for testing your >patches... > >As for making ps totally proc aware, I'm not totally sure that's the way >to go. I shall have to have a look through the archives though; I've a >feeling that this has been discussed before... Yup - it'd mean keeping two sets of utilities, one for procfs/sysctl interfaces, and one for kvm interfaces for coredumps. I meant that if we wanted a procfs that gave us the -flexibility- to extract stuff out of the struct proc * without kvm_getprocs() ... Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 8:15:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 511971548E for ; Fri, 23 Apr 1999 08:15:13 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA19096; Sat, 24 Apr 1999 00:12:19 +0900 (JST) Message-ID: <37208D59.4A8670E8@newsguy.com> Date: Sat, 24 Apr 1999 00:10:17 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Greg Lehey Cc: FreeBSD current users Subject: Re: Problems with symbol sequences in recent kernels References: <19990423153323.P91260@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > This has worked quite nicely for some time. Since yesterday, after > building a kernel with newbus support, I get strange messages if I > read in the Vinum symbols before reading in the kernel symbols: ... > I debugged gdb and found that it was finding these references > (opt_global.h) in cd9660_rrip.o, which it read after reading the Vinum > kld symbols. If I can convince it to read the kernel symbols first, I > don't have any trouble. I don't think that it's anything to do with > that particular file; there must be about 30 files in a typical kernel > build which refer to this symbol. > > If I don't get any response on the list, I'll put in a PR, but I > thought there's a good chance that somebody will recognize this > problem and be able to fix it. Well, I don't recognize the problem, but I committed changes to cd9660_rrip.c after newbus got in. Could you try a kernel from before my changes got in? Just for the files I changed would be enough. This commit added Joliet Extensions support for cd9660, and affected cd9660 fs and mount_cd9660. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 9:23:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7DB9B14D80; Fri, 23 Apr 1999 09:23:16 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA01082; Sat, 24 Apr 1999 01:20:35 +0900 (JST) Message-ID: <3720973B.B24B2FEE@newsguy.com> Date: Sat, 24 Apr 1999 00:52:27 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Dom Mitchell Cc: adrian@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: nice little kernel task for somebody References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell wrote: > > As for making ps totally proc aware, I'm not totally sure that's the way > to go. I shall have to have a look through the archives though; I've a > feeling that this has been discussed before... DCS, The Archive Man, comes to your help. If you make ps procfs dependent, you won't be able to use it on core dumps. That's different from making procfs complete enough to support a ps. Against that there is a general Linuxism/Kitchen-Sink feeling. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 9:40: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 84CC014D38 for ; Fri, 23 Apr 1999 09:40:02 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id SAA39329; Fri, 23 Apr 1999 18:37:19 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904231637.SAA39329@freebsd.dk> Subject: Re: New IDE Drivers In-Reply-To: <003801be8d81$19342d20$d3e4b38c@xyplex.com> from Rick Whitesel at "Apr 23, 1999 8: 2: 1 am" To: rwhitesel@nbase-xyplex.com (Rick Whitesel) Date: Fri, 23 Apr 1999 18:37:18 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Rick Whitesel wrote: > Hi: > I believe the problems I started having with the new IDE drivers may > be related to the bugs in the SMP IRQ handler described by Roger Hardiman. I > am going to wait until Roger fixes the bug to see if my IDE problem > disappears. I tried the latest drivers on a non SMP motherboard and they > work fine! Hmm, I run them/develop them on a SMP system, and they still works for me, but I might have some local changes that affects this too.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 9:40:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp4.mindspring.com (smtp4.mindspring.com [207.69.200.64]) by hub.freebsd.org (Postfix) with ESMTP id DFA75154D3 for ; Fri, 23 Apr 1999 09:40:07 -0700 (PDT) (envelope-from stevensl@mindspring.net) Received: from freelove.mindspring.net (freelove.mindspring.net [207.69.192.92]) by smtp4.mindspring.com (8.8.5/8.8.5) with ESMTP id MAA04555 for ; Fri, 23 Apr 1999 12:37:36 -0400 (EDT) Date: Fri, 23 Apr 1999 12:39:45 -0400 (EDT) From: steven To: freebsd-current@FreeBSD.ORG Subject: Colldef fails to make Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Currently running 3.0-Current on my dual ppro machine. I cvsup'd this version back in mid Jan and thought it was time to try again. At first i went to 4.x-Current, during buildworld colldef fails giving dont know how to make de_DE.ISO_8859-15 (i think.. doing from memory) so i tried the latest 3.x-Current and now i get syntax error's and error 69 when in build world. Someone posted make includes seemed to help them along so i tried that and it still barfs.. i think its something wrong with my system so i'm prepping for a clean install but was wondering if anyone else has seen this error? Steven S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 11:17:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from jason02.u.washington.edu (jason02.u.washington.edu [140.142.76.8]) by hub.freebsd.org (Postfix) with ESMTP id 4D4A214EAD for ; Fri, 23 Apr 1999 11:17:33 -0700 (PDT) (envelope-from jcwells@u.washington.edu) Received: from saul10.u.washington.edu (root@saul10.u.washington.edu [140.142.13.73]) by jason02.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA34632; Fri, 23 Apr 1999 11:14:55 -0700 Received: from s8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul10.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA10269; Fri, 23 Apr 1999 11:14:54 -0700 (PDT) Date: Fri, 23 Apr 1999 11:14:00 -0700 (PDT) From: "Jason C. Wells" X-Sender: jcw@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: steven Cc: freebsd-current@FreeBSD.ORG Subject: Re: Colldef fails to make In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Apr 1999, steven wrote: >At first i went to 4.x-Current, during buildworld colldef fails >giving dont know how to make de_DE.ISO_8859-15 (i think.. doing from >memory) > >so i tried the latest 3.x-Current and now i get syntax error's and error >69 when in build world. Someone posted make includes seemed to help >them along so i tried that and it still barfs.. I had colldef problems yesterday using stable. They were fixed by the evening. Perhaps this fix is in current too. I would try again today. Catchya Later, | Give me UNIX or give me a typewriter. Jason Wells | http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 11:23:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (Postfix) with ESMTP id 0947714EAD for ; Fri, 23 Apr 1999 11:23:30 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id LAA15437; Fri, 23 Apr 1999 11:21:00 -0700 (PDT) (envelope-from sef) Date: Fri, 23 Apr 1999 11:21:00 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199904231821.LAA15437@kithrup.com> To: current@freebsd.org Subject: Re: nice little kernel task for somebody In-Reply-To: <19990423091633.14103.qmail.kithrup.freebsd.current@ewok.creative.net.au> References: Your message of "Thu, 22 Apr 1999 17:32:40 +0100." <9904221732.aa19138@salmon.maths.tcd.ie> Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Here's a thing I've missed a couple of times: I'd like to be >> able to see the limits for a process in /proc. At some point, I want to add an ioctl to get various process information (well, multiple ioctl's, I think); SysVr4 has a bunch, and that's what I'd model it on. >I'd like to be able to open processes file discriptors too (so >you can still get files back if all the filsystem references to >it have gone, but a process still has it open). I might have a >go at doing both - if it isn't too Linuxesque. Ugh. I don't particularly like that one. It's fairly rare, and very invasive, and gives me the willies. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 12:13:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dnvrpop1.dnvr.uswest.net (dnvrpop1.dnvr.uswest.net [206.196.128.3]) by hub.freebsd.org (Postfix) with SMTP id 940BF151AF for ; Fri, 23 Apr 1999 12:12:55 -0700 (PDT) (envelope-from dchang@uswest.net) Received: (qmail 8881 invoked by alias); 23 Apr 1999 19:10:23 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 8816 invoked by uid 0); 23 Apr 1999 19:10:21 -0000 Received: from mdsl206.dnvr.uswest.net (HELO Amber.XtremeDev.com) (209.181.71.206) by dnvrpop1.dnvr.uswest.net with SMTP; 23 Apr 1999 19:10:21 -0000 From: Dave Reply-To: dchang@uswest.net To: current@FreeBSD.ORG Subject: Code Crusader 2.0.x on FreeBSD Date: Fri, 23 Apr 1999 13:08:26 -0600 X-Mailer: KMail [version 1.0.17] Content-Type: Multipart/Mixed; boundary="Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ" MIME-Version: 1.0 Message-Id: <99042313102100.01435@Amber.XtremeDev.com> X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ Content-Type: text/plain Content-Transfer-Encoding: 8bit Trying to see what the success rate is with everyone who's able to get Code Crusader 2.0.x to compile on FreeBSD either on -stable or -current. I have had no luck with getting it to compile on -stable (nor -current right now). ACE compiles successfully with config-freebsd-pthread.h and platform_freebsd_pthread.GNU, makemake compiles as well, but when it got to compiling JX core and libraries and rest (including Code Crusader) it core dumps. I modified the Makefile at the root JX dir so gmake freebsd would link in config-freebsd-pthread.h and platform_freebsd_pthread.GNU, and changed the line in ACE_JX_-1.1.22/include/make/sys/FreeBSD_g++ from: J_ACE_LIBS := -L${JX_ROOT}/lib -lACE-${ACE_LIB_VERSION} to: J_ACE_LIBS := -L${JX_ROOT}/lib -lACE-${ACE_LIB_VERSION} -pthread as per man pthread's directions to pull in libc_r.a. Does anyone have any success stories they would like to share? Or suggestions on how to cure the core dumps? I've tried the config-freebsd4.h and platform_freebsd4.GNU files from http://www.Pinyon.ORG/ace/ as well as the same files [34] from Ian West who posted his suggestions on Sat, 27 Mar 1999 23:46:14. Same core dumps on making make. Attached is the log of the make process after above modifications. Dave --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ Content-Type: text/plain; name="JX_freebsd4.log" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="JX_freebsd4.log" gmake[1]: Entering directory `/usr/home/dave/temp/JX-1.1.22/lib' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/ACE' gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers/ace' test -d .shobj || mkdir .shobj eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Basic_Types.o Basic_Types.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/OS.o OS.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Sched_Params.o Sched_Params.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/ACE.o ACE.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Active_Map_Manager.o Active_Map_Manager.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Arg_Shifter.o Arg_Shifter.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/ARGV.o ARGV.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Containers.o Containers.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Dirent.o Dirent.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Dynamic.o Dynamic.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Filecache.o Filecache.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Functor.o Functor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Get_Opt.o Get_Opt.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Hash_Map_Manager.o Hash_Map_Manager.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/High_Res_Timer.o High_Res_Timer.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Method_Request.o Method_Request.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Object_Manager.o Object_Manager.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Profile_Timer.o Profile_Timer.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Registry.o Registry.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SString.o SString.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Stats.o Stats.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/System_Time.o System_Time.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Time_Request_Reply.o Time_Request_Reply.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Timeprobe.o Timeprobe.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Timer_Hash.o Timer_Hash.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Timer_Heap.o Timer_Heap.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Timer_List.o Timer_List.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Timer_Queue.o Timer_Queue.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Timer_Wheel.o Timer_Wheel.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Dump.o Dump.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Log_Msg.o Log_Msg.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Log_Record.o Log_Record.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Trace.o Trace.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Activation_Queue.o Activation_Queue.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Process.o Process.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Process_Manager.o Process_Manager.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Synch.o Synch.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Synch_Options.o Synch_Options.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Thread.o Thread.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Thread_Manager.o Thread_Manager.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Token.o Token.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Event_Handler.o Event_Handler.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Handle_Set.o Handle_Set.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/POSIX_Proactor.o POSIX_Proactor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Priority_Reactor.o Priority_Reactor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Proactor.o Proactor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Reactor.o Reactor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Select_Reactor.o Select_Reactor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Select_Reactor_Base.o Select_Reactor_Base.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/WFMO_Reactor.o WFMO_Reactor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Asynch_IO.o Asynch_IO.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Asynch_IO_Impl.o Asynch_IO_Impl.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/POSIX_Asynch_IO.o POSIX_Asynch_IO.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Strategies.o Strategies.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/IPC_SAP.o IPC_SAP.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/LSOCK.o LSOCK.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/LSOCK_Acceptor.o LSOCK_Acceptor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/LSOCK_CODgram.o LSOCK_CODgram.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/LSOCK_Connector.o LSOCK_Connector.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/LSOCK_Dgram.o LSOCK_Dgram.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/LSOCK_Stream.o LSOCK_Stream.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK.o SOCK.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK_Acceptor.o SOCK_Acceptor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK_CODgram.o SOCK_CODgram.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK_Connector.o SOCK_Connector.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK_Dgram.o SOCK_Dgram.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK_Dgram_Bcast.o SOCK_Dgram_Bcast.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK_Dgram_Mcast.o SOCK_Dgram_Mcast.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK_IO.o SOCK_IO.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SOCK_Stream.o SOCK_Stream.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Addr.o Addr.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/DEV.o DEV.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/DEV_Addr.o DEV_Addr.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/DEV_Connector.o DEV_Connector.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/DEV_IO.o DEV_IO.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FIFO.o FIFO.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FIFO_Recv.o FIFO_Recv.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FIFO_Recv_Msg.o FIFO_Recv_Msg.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FIFO_Send.o FIFO_Send.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FIFO_Send_Msg.o FIFO_Send_Msg.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FILE_Addr.o FILE_Addr.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FILE.o FILE.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FILE_Connector.o FILE_Connector.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/FILE_IO.o FILE_IO.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/INET_Addr.o INET_Addr.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/IO_SAP.o IO_SAP.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/IOStream.o IOStream.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Pipe.o Pipe.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Signal.o Signal.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SPIPE_Addr.o SPIPE_Addr.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SPIPE.o SPIPE.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SPIPE_Acceptor.o SPIPE_Acceptor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SPIPE_Connector.o SPIPE_Connector.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SPIPE_Stream.o SPIPE_Stream.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SV_Message.o SV_Message.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SV_Message_Queue.o SV_Message_Queue.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SV_Semaphore_Complex.o SV_Semaphore_Complex.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SV_Semaphore_Simple.o SV_Semaphore_Simple.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/SV_Shared_Memory.o SV_Shared_Memory.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/TLI.o TLI.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/TLI_Acceptor.o TLI_Acceptor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/TLI_Connector.o TLI_Connector.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/TLI_Stream.o TLI_Stream.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/TTY_IO.o TTY_IO.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/UNIX_Addr.o UNIX_Addr.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/UPIPE_Acceptor.o UPIPE_Acceptor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/UPIPE_Connector.o UPIPE_Connector.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/UPIPE_Stream.o UPIPE_Stream.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/DLL.o DLL.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Parse_Node.o Parse_Node.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Service_Config.o Service_Config.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Service_Manager.o Service_Manager.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Service_Object.o Service_Object.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Service_Repository.o Service_Repository.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Service_Types.o Service_Types.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Shared_Object.o Shared_Object.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Svc_Conf_l.o Svc_Conf_l.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Svc_Conf_y.o Svc_Conf_y.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/CDR_Stream.o CDR_Stream.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Message_Block.o Message_Block.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Message_Queue.o Message_Queue.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Task.o Task.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Malloc.o Malloc.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Mem_Map.o Mem_Map.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Memory_Pool.o Memory_Pool.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Obstack.o Obstack.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Read_Buffer.o Read_Buffer.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Shared_Memory.o Shared_Memory.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Shared_Memory_MM.o Shared_Memory_MM.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Shared_Memory_SV.o Shared_Memory_SV.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Local_Tokens.o Local_Tokens.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Remote_Tokens.o Remote_Tokens.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Token_Collection.o Token_Collection.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Token_Invariants.o Token_Invariants.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Token_Manager.o Token_Manager.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Token_Request_Reply.o Token_Request_Reply.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/CORBA_Handler.o CORBA_Handler.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/CORBA_Ref.o CORBA_Ref.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Local_Name_Space.o Local_Name_Space.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Msg_WFMO_Reactor.o Msg_WFMO_Reactor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Name_Proxy.o Name_Proxy.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Name_Request_Reply.o Name_Request_Reply.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Name_Space.o Name_Space.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Naming_Context.o Naming_Context.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Registry_Name_Space.o Registry_Name_Space.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/Remote_Name_Space.o Remote_Name_Space.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/TP_Reactor.o TP_Reactor.cpp eg++ -Wall -O -fno-exceptions -D__ACE_INLINE__ -frepo -DACE_HAS_GNU_REPO -I. -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c -fpic -o .shobj/XtReactor.o XtReactor.cpp eg++ -shared -o libACE.so .shobj/Basic_Types.o .shobj/OS.o .shobj/Sched_Params.o .shobj/ACE.o .shobj/Active_Map_Manager.o .shobj/Arg_Shifter.o .shobj/ARGV.o .shobj/Containers.o .shobj/Dirent.o .shobj/Dynamic.o .shobj/Filecache.o .shobj/Functor.o .shobj/Get_Opt.o .shobj/Hash_Map_Manager.o .shobj/High_Res_Timer.o .shobj/Method_Request.o .shobj/Object_Manager.o .shobj/Profile_Timer.o .shobj/Registry.o .shobj/SString.o .shobj/Stats.o .shobj/System_Time.o .shobj/Time_Request_Reply.o .shobj/Timeprobe.o .shobj/Timer_Hash.o .shobj/Timer_Heap.o .shobj/Timer_List.o .shobj/Timer_Queue.o .shobj/Timer_Wheel.o .shobj/Dump.o .shobj/Log_Msg.o .shobj/Log_Record.o .shobj/Trace.o .shobj/Activation_Queue.o .shobj/Process.o .shobj/Process_Manager.o .shobj/Synch.o .shobj/Synch_Options.o .shobj/Thread.o .shobj/Thread_Manager.o .shobj/Token.o .shobj/Event_Handler.o .shobj/Handle_Set.o .shobj/POSIX_Proactor.o .shobj/Priority_Reactor.o .shobj/Proactor.o .shobj/Reactor.o .shobj/Select_Reactor.o .shobj/Select_Reactor_Base.o .shobj/WFMO_Reactor.o .shobj/Asynch_IO.o .shobj/Asynch_IO_Impl.o .shobj/POSIX_Asynch_IO.o .shobj/Strategies.o .shobj/IPC_SAP.o .shobj/LSOCK.o .shobj/LSOCK_Acceptor.o .shobj/LSOCK_CODgram.o .shobj/LSOCK_Connector.o .shobj/LSOCK_Dgram.o .shobj/LSOCK_Stream.o .shobj/SOCK.o .shobj/SOCK_Acceptor.o .shobj/SOCK_CODgram.o .shobj/SOCK_Connector.o .shobj/SOCK_Dgram.o .shobj/SOCK_Dgram_Bcast.o .shobj/SOCK_Dgram_Mcast.o .shobj/SOCK_IO.o .shobj/SOCK_Stream.o .shobj/Addr.o .shobj/DEV.o .shobj/DEV_Addr.o .shobj/DEV_Connector.o .shobj/DEV_IO.o .shobj/FIFO.o .shobj/FIFO_Recv.o .shobj/FIFO_Recv_Msg.o .shobj/FIFO_Send.o .shobj/FIFO_Send_Msg.o .shobj/FILE_Addr.o .shobj/FILE.o .shobj/FILE_Connector.o .shobj/FILE_IO.o .shobj/INET_Addr.o .shobj/IO_SAP.o .shobj/IOStream.o .shobj/Pipe.o .shobj/Signal.o .shobj/SPIPE_Addr.o .shobj/SPIPE.o .shobj/SPIPE_Acceptor.o .shobj/SPIPE_Connector.o .shobj/SPIPE_Stream.o .shobj/SV_Message.o .shobj/SV_Message_Queue.o .shobj/SV_Semaphore_Complex.o .shobj/SV_Semaphore_Simple.o .shobj/SV_Shared_Memory.o .shobj/TLI.o .shobj/TLI_Acceptor.o .shobj/TLI_Connector.o .shobj/TLI_Stream.o .shobj/TTY_IO.o .shobj/UNIX_Addr.o .shobj/UPIPE_Acceptor.o .shobj/UPIPE_Connector.o .shobj/UPIPE_Stream.o .shobj/DLL.o .shobj/Parse_Node.o .shobj/Service_Config.o .shobj/Service_Manager.o .shobj/Service_Object.o .shobj/Service_Repository.o .shobj/Service_Types.o .shobj/Shared_Object.o .shobj/Svc_Conf_l.o .shobj/Svc_Conf_y.o .shobj/CDR_Stream.o .shobj/Message_Block.o .shobj/Message_Queue.o .shobj/Task.o .shobj/Malloc.o .shobj/Mem_Map.o .shobj/Memory_Pool.o .shobj/Obstack.o .shobj/Read_Buffer.o .shobj/Shared_Memory.o .shobj/Shared_Memory_MM.o .shobj/Shared_Memory_SV.o .shobj/Local_Tokens.o .shobj/Remote_Tokens.o .shobj/Token_Collection.o .shobj/Token_Invariants.o .shobj/Token_Manager.o .shobj/Token_Request_Reply.o .shobj/CORBA_Handler.o .shobj/CORBA_Ref.o .shobj/Local_Name_Space.o .shobj/Msg_WFMO_Reactor.o .shobj/Name_Proxy.o .shobj/Name_Request_Reply.o .shobj/Name_Space.o .shobj/Naming_Context.o .shobj/Registry_Name_Space.o .shobj/Remote_Name_Space.o .shobj/TP_Reactor.o .shobj/XtReactor.o -Wl,-rpath /usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers/ace -L/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers/ace -L./ -llthread chmod a+rx libACE.so gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers/ace' gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/ACE' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/misc/regex' sh ./mkh -p regcomp.c >regcomp.ih gcc -I. -DREDEBUG -c regcomp.c -o regcomp.o sh ./mkh -p engine.c >engine.ih gcc -I. -DREDEBUG -c regexec.c -o regexec.o sh ./mkh -p regerror.c >regerror.ih gcc -I. -DREDEBUG -c regerror.c -o regerror.o gcc -I. -DREDEBUG -c regfree.c -o regfree.o gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/misc/regex' g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c makemake.cc -o makemake.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JBroadcaster.cc -o ../../include/jcore/JBroadcaster.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JCollection.cc -o ../../include/jcore/JCollection.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JContainer.cc -o ../../include/jcore/JContainer.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JProbDistr.cc -o ../../include/jcore/JProbDistr.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JOrderedSetT.cc -o ../../include/jcore/JOrderedSetT.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JOrderedSetUtil.cc -o ../../include/jcore/JOrderedSetUtil.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JString.cc -o ../../include/jcore/JString.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JSubstitute.cc -o ../../include/jcore/JSubstitute.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jCommandLine.cc -o ../../include/jcore/jCommandLine.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jStreamUtil.cc -o ../../include/jcore/jStreamUtil.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jStreamUtil_UNIX.cc -o ../../include/jcore/jStreamUtil_UNIX.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jFStreamUtil.cc -o ../../include/jcore/jFStreamUtil.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jFStreamUtil_UNIX.cc -o ../../include/jcore/jFStreamUtil_UNIX.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jFileUtil.cc -o ../../include/jcore/jFileUtil.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jFileUtil_UNIX.cc -o ../../include/jcore/jFileUtil_UNIX.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jDirUtil_UNIX.cc -o ../../include/jcore/jDirUtil_UNIX.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jUNIXUtil.cc -o ../../include/jcore/jUNIXUtil.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JError.cc -o ../../include/jcore/JError.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JStdError.cc -o ../../include/jcore/JStdError.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JRTTIBase.cc -o ../../include/jcore/JRTTIBase.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JProgressDisplay.cc -o ../../include/jcore/JProgressDisplay.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jMemory.cc -o ../../include/jcore/jMemory.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jMath.cc -o ../../include/jcore/jMath.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jAssert.cc -o ../../include/jcore/jAssert.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JAssertBase.cc -o ../../include/jcore/JAssertBase.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jGlobals.cc -o ../../include/jcore/jGlobals.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JUserNotification.cc -o ../../include/jcore/JUserNotification.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JTextUserNotification.cc -o ../../include/jcore/JTextUserNotification.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JChooseSaveFile.cc -o ../../include/jcore/JChooseSaveFile.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JTextChooseSaveFile.cc -o ../../include/jcore/JTextChooseSaveFile.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JCreateProgressDisplay.cc -o ../../include/jcore/JCreateProgressDisplay.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JCreateTextPG.cc -o ../../include/jcore/JCreateTextPG.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JTextProgressDisplay.cc -o ../../include/jcore/JTextProgressDisplay.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JLatentPG.cc -o ../../include/jcore/JLatentPG.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JProcess.cc -o ../../include/jcore/JProcess.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JProcessError.cc -o ../../include/jcore/JProcessError.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JThisProcess.cc -o ../../include/jcore/JThisProcess.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jProcessUtil.cc -o ../../include/jcore/jProcessUtil.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jSignal.cc -o ../../include/jcore/jSignal.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JInPipeStream.cc -o ../../include/jcore/JInPipeStream.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JUNIXDirInfo.cc -o ../../include/jcore/JUNIXDirInfo.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JUNIXDirEntry.cc -o ../../include/jcore/JUNIXDirEntry.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/Templates-JString.cc -o ../../include/jcore/Templates-JString.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/Templates-int.cc -o ../../include/jcore/Templates-int.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/Templates-long.cc -o ../../include/jcore/Templates-long.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/Templates-longlong.cc -o ../../include/jcore/Templates-longlong.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/Templates-double.cc -o ../../include/jcore/Templates-double.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JPtrArray-JString.cc -o ../../include/jcore/JPtrArray-JString.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JRegex.cc -o ../../include/jcore/JRegex.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JInterpolate.cc -o ../../include/jcore/JInterpolate.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jHashFunctions.cc -o ../../include/jcore/jHashFunctions.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/jNew.cc -o ../../include/jcore/jNew.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JMemoryManager.cc -o ../../include/jcore/JMemoryManager.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JMMTable.cc -o ../../include/jcore/JMMTable.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JMMArrayTable.cc -o ../../include/jcore/JMMArrayTable.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JMMHashTable.cc -o ../../include/jcore/JMMHashTable.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JMMMonitor.cc -o ../../include/jcore/JMMMonitor.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JMMErrorPrinter.cc -o ../../include/jcore/JMMErrorPrinter.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JMMRecord.cc -o ../../include/jcore/JMMRecord.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JArray-JMMRecord.cc -o ../../include/jcore/JArray-JMMRecord.o g++ -Wall -Wno-unused -fno-implicit-templates -O0 -D_J_UNIX -D_J_ARRAY_NEW_OVERRIDABLE -Werror -DJ_MAKE_BINARY_NAME=\"gmake\" -I- -I. -I../../include/jcore -I/usr/home/dave/temp/JX-1.1.22/ACE/ACE_wrappers -c ../../include/jcore/JHashTable-JMMRecord.cc -o ../../include/jcore/JHashTable-JMMRecord.o g++ -o makemake makemake.o ../../include/jcore/JBroadcaster.o ../../include/jcore/JCollection.o ../../include/jcore/JContainer.o ../../include/jcore/JProbDistr.o ../../include/jcore/JOrderedSetT.o ../../include/jcore/JOrderedSetUtil.o ../../include/jcore/JString.o ../../include/jcore/JSubstitute.o ../../include/jcore/jCommandLine.o ../../include/jcore/jStreamUtil.o ../../include/jcore/jStreamUtil_UNIX.o ../../include/jcore/jFStreamUtil.o ../../include/jcore/jFStreamUtil_UNIX.o ../../include/jcore/jFileUtil.o ../../include/jcore/jFileUtil_UNIX.o ../../include/jcore/jDirUtil_UNIX.o ../../include/jcore/jUNIXUtil.o ../../include/jcore/JError.o ../../include/jcore/JStdError.o ../../include/jcore/JRTTIBase.o ../../include/jcore/JProgressDisplay.o ../../include/jcore/jMemory.o ../../include/jcore/jMath.o ../../include/jcore/jAssert.o ../../include/jcore/JAssertBase.o ../../include/jcore/jGlobals.o ../../include/jcore/JUserNotification.o ../../include/jcore/JTextUserNotification.o ../../include/jcore/JChooseSaveFile.o ../../include/jcore/JTextChooseSaveFile.o ../../include/jcore/JCreateProgressDisplay.o ../../include/jcore/JCreateTextPG.o ../../include/jcore/JTextProgressDisplay.o ../../include/jcore/JLatentPG.o ../../include/jcore/JProcess.o ../../include/jcore/JProcessError.o ../../include/jcore/JThisProcess.o ../../include/jcore/jProcessUtil.o ../../include/jcore/jSignal.o ../../include/jcore/JInPipeStream.o ../../include/jcore/JUNIXDirInfo.o ../../include/jcore/JUNIXDirEntry.o ../../include/jcore/Templates-JString.o ../../include/jcore/Templates-int.o ../../include/jcore/Templates-long.o ../../include/jcore/Templates-longlong.o ../../include/jcore/Templates-double.o ../../include/jcore/JPtrArray-JString.o ../../include/jcore/JRegex.o ../../include/jcore/JInterpolate.o ../../include/jcore/jHashFunctions.o ../../include/jcore/jNew.o ../../include/jcore/JMemoryManager.o ../../include/jcore/JMMTable.o ../../include/jcore/JMMArrayTable.o ../../include/jcore/JMMHashTable.o ../../include/jcore/JMMMonitor.o ../../include/jcore/JMMErrorPrinter.o ../../include/jcore/JMMRecord.o ../../include/jcore/JArray-JMMRecord.o ../../include/jcore/JHashTable-JMMRecord.o ../../misc/regex/regcomp.o ../../misc/regex/regexec.o ../../misc/regex/regerror.o ../../misc/regex/regfree.o -L../../lib -lACE-4_6 -pthread -lstdc++ -lm -lc /usr/lib/libc_r.so: warning: this program uses gets(), which is unsafe. /usr/lib/libc_r.so: WARNING! setkey(3) not present in the system! /usr/lib/libc_r.so: WARNING! des_setkey(3) not present in the system! /usr/lib/libc_r.so: WARNING! encrypt(3) not present in the system! /usr/lib/libc_r.so: WARNING! des_cipher(3) not present in the system! /usr/lib/libc_r.so: warning: this program uses f_prealloc(), which is stupid. makemake successfully installed gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/lib' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/libjcore' gmake[3]: *** No rule to make target `Makefiles'. Stop. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/libjcore' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/libjx' gmake[3]: *** No rule to make target `Makefiles'. Stop. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/libjx' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/lib/util/ace' gmake[3]: Nothing to be done for `Makefiles'. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib/util/ace' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/lib/util/autodoc' gmake[3]: *** No rule to make target `Makefiles'. Stop. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib/util/autodoc' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/programs/code_crusader' gmake[3]: *** No rule to make target `Makefiles'. Stop. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/code_crusader' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/programs/jxlayout' gmake[3]: *** No rule to make target `Makefiles'. Stop. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/jxlayout' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' gmake[3]: *** No rule to make target `Makefiles'. Stop. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/ACE/test' gmake[3]: *** No rule to make target `Makefiles'. Stop. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/ACE/test' Segmentation fault - core dumped gmake[3]: Entering directory `/usr/home/dave/temp/JX-1.1.22/tutorial' gmake[3]: *** No rule to make target `Makefiles'. Stop. gmake[3]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/tutorial' gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/libjcore' gmake[2]: *** No targets. Stop. gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/libjcore' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/libjx' gmake[2]: *** No targets. Stop. gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/libjx' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/lib/util/ace' gmake[2]: Nothing to be done for `jxinstall'. gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib/util/ace' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/lib/util/autodoc' gmake[2]: *** No rule to make target `jxinstall'. Stop. gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib/util/autodoc' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/programs/code_crusader' gmake[2]: *** No rule to make target `jxinstall'. Stop. gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/code_crusader' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/programs/jxlayout' gmake[2]: *** No rule to make target `jxinstall'. Stop. gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/jxlayout' gmake[2]: Entering directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' gmake[2]: *** No rule to make target `jxinstall'. Stop. gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' gmake[1]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib' --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 12:46:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.22]) by hub.freebsd.org (Postfix) with ESMTP id A834214D6D for ; Fri, 23 Apr 1999 12:46:10 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id OAA09568; Fri, 23 Apr 1999 14:41:53 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 23 Apr 1999 14:41:52 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: dcs@newsguy.com Cc: current@freebsd.org Subject: Re: nice little kernel task for somebody X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14112.52429.575986.913523@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : Against that there is a general Linuxism/Kitchen-Sink feeling. : Think of this case as a plan9-ism. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 13:22:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5E00A14D98 for ; Fri, 23 Apr 1999 13:22:31 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA19075; Sat, 24 Apr 1999 05:19:52 +0900 (JST) Message-ID: <3720D54C.70CDDF13@newsguy.com> Date: Sat, 24 Apr 1999 05:17:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: alk@pobox.com Cc: current@freebsd.org Subject: Re: nice little kernel task for somebody References: <14112.52429.575986.913523@avalon.east> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anthony Kimball wrote: > > : Against that there is a general Linuxism/Kitchen-Sink feeling. > > Think of this case as a plan9-ism. I think nothing of it... My opinions wouldn't matter a tiny little bit. :-) Still, after reading the Samba reply to the Microsoft, err, Mindcraft NTvsLinus benchmark, and the comments on tuning through /proc, I have to say I'd feel disgusted to have something like that on FreeBSD. It gave a whole new meaning to the word "arcane". Still, I'm against process privacy. We ought to be able to know anything about how a process is using *our* (the system's) resources. At least until we get proper compartimentalized security, which a number of people few is very un-Unix-like. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 13:23: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id D9C8F15477 for ; Fri, 23 Apr 1999 13:22:59 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 1BDF41F5B; Sat, 24 Apr 1999 04:20:26 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Sean Eric Fagan Cc: current@freebsd.org Subject: Re: nice little kernel task for somebody In-reply-to: Your message of "Fri, 23 Apr 1999 11:21:00 MST." <199904231821.LAA15437@kithrup.com> Date: Sat, 24 Apr 1999 04:20:26 +0800 From: Peter Wemm Message-Id: <19990423202028.1BDF41F5B@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Eric Fagan wrote: > >> Here's a thing I've missed a couple of times: I'd like to be > >> able to see the limits for a process in /proc. > > At some point, I want to add an ioctl to get various process information > (well, multiple ioctl's, I think); SysVr4 has a bunch, and that's what I'd > model it on. We've already got a good chunk of that code for ELF coredump support. They are the same data structures... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 13:48: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (Postfix) with ESMTP id 8FED81550C for ; Fri, 23 Apr 1999 13:48:03 -0700 (PDT) (envelope-from plm@smtp1.xs4all.nl) Received: from localhost. (dc2-isdn1998.dial.xs4all.nl [194.109.155.206]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id WAA25714 for ; Fri, 23 Apr 1999 22:45:29 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id WAA00567; Fri, 23 Apr 1999 22:45:29 +0200 (MET DST) (envelope-from plm) To: freebsd-current@freebsd.org Subject: suspend mode broken since one week ago From: Peter Mutsaers Date: 23 Apr 1999 22:22:51 +0200 Message-ID: <87so9r3x44.fsf@muon.xs4all.nl> X-Mailer: Gnus v5.6.45/Emacs 20.3 Lines: 22 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I rebuilt my kernel just after the new config stuff (nexus). Since then (but I'm not 100% sure it is related to this) my desktop computer doesn't suspend anymore. Before that, I could suspend it either by: - pressing the suspend button - zzz command (apm -z) - wait until BIOS-set time for suspend mode passes Now it won't suspend in any way anymore (which is irritating since my computer is in the living room; it must be quiet but I don't want it to reboot all the time). Is this a bug that I should report through send-pr, is it already known as a bug or is this an intentional change in behaviour? -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+------------------ Running FreeBSD-current UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 15:25:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles539.castles.com [208.214.165.103]) by hub.freebsd.org (Postfix) with ESMTP id DB7C714CA4 for ; Fri, 23 Apr 1999 15:25:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id IAA00751; Fri, 23 Apr 1999 08:55:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904231555.IAA00751@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman Cc: Soren Schmidt , Christopher Masto , current@FreeBSD.ORG Subject: Re: New ATA driver and crash dumps In-reply-to: Your message of "Thu, 22 Apr 1999 07:19:36 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 23 Apr 1999 08:55:44 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any way I can help in getting the atapi-fd driver to work w= ith > LS-120's? Unless it was just recently broken, it works fine (I have one). -- = \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 15:25:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles539.castles.com [208.214.165.103]) by hub.freebsd.org (Postfix) with ESMTP id 89DD815483 for ; Fri, 23 Apr 1999 15:25:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id IAA00674; Fri, 23 Apr 1999 08:40:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904231540.IAA00674@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty Cc: "Daniel O'Connor" , "Viren R. Shah" , Nick Hibma , Freebsd-current@FreeBSD.ORG, Kazutaka YOKOTA Subject: Re: USB keyboard attach function? In-reply-to: Your message of "Wed, 21 Apr 1999 21:04:06 PDT." <199904220404.VAA07662@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Apr 1999 08:40:21 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem was not really a bios problem not sure what the guys > did to fix the boot loader probably switch to using a dos int function > to access the keyboard from the boot loader. I haven't seen anything (being disconnected), but I thought I should just slap you for being so stupid as to think that DOS had anything to do with the loader. The loader's keyboard interface code uses the BIOS, like it always has. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 15:26:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles539.castles.com [208.214.165.103]) by hub.freebsd.org (Postfix) with ESMTP id 86F221556D for ; Fri, 23 Apr 1999 15:25:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id HAA00330; Fri, 23 Apr 1999 07:32:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904231432.HAA00330@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf LINT GENERIC In-reply-to: Your message of "Wed, 21 Apr 1999 12:02:30 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Apr 1999 07:32:00 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > P.S.: USBDI as in, our version of it. The people from the consortium > > > kicked us out. > > > Can you elaborate on the reason that USBDI does not FreeBSD > > to be involved with the consortium? > > Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka > consortium. No company was willing to pay it for us and the consortium > was not willing to waive the fee, because not-for-profit organisations > still draw a certain benefit for their community, or something along > those lines. All sounds a bit strange if you consider the fact that the > spec will be open and free-for-all eventualy. Actually, there are a combination of issues. The cost involved in being a member is one issue, another is that to remain a "member in good standing" you have to attend at least one meeting every three months (ie. travel to/around the USA), and the third is that you need to be able to negotiate and sign legal agreements on behalf of your organisation. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 15:56: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-185-206.res.iastate.edu (friley-185-206.res.iastate.edu [129.186.185.206]) by hub.freebsd.org (Postfix) with ESMTP id 9EB7514D04 for ; Fri, 23 Apr 1999 15:56:03 -0700 (PDT) (envelope-from cc@137.org) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by friley-185-206.res.iastate.edu (Postfix) with ESMTP id CB6FBC5; Fri, 23 Apr 1999 16:53:13 -0600 (CST) Received: from friley-185-205.res.iastate.edu (localhost [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id CE347109; Fri, 23 Apr 1999 17:53:13 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Jake Burkholder Cc: Peter Wemm , Brian Feldman , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-reply-to: Your message of "Sat, 17 Apr 1999 11:55:08 PDT." <199904171855.LAA00451@h24-64-221-247.gv.wave.shaw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Apr 1999 17:53:13 -0500 From: Chris Csanady Message-Id: <19990423225313.CE347109@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Hmm, you might like to try this patch and see what happens, there is >> a missing old driver wrapper for the pcm stuff. As a result, it's not >> getting run from the isa probe. Regarding the other driver, I'm not >> sure what's going on there as the hooks appear to be present. > >Right on, that patch does it for me. > >pcm0 at port 0x220 irq 5 drq 1 flags 0x15 on isa0 >pcm0: interrupting at irq 5 > >I've got an old SB16 Value, non-pnp. > >mp3s aren't playing quite right with x11amp though, little >skips here and there, they work fine with the old kernel. >mpg123 seems fine, as does the sound in FXTV. >I'll try making the world again. Was there ever any resolution/further inspection of this? x11amp behaves similarly for me. Actually, under considerable load, it is *really* bad. Have there been any notable scheduling changes recently? I remember people were seeing overflows on their serial ports after the new-bus integration since the driver was no longer using fast interrupts or something. Could there be something similar with the pcm driver? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 17:13:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 3417D14CE2 for ; Fri, 23 Apr 1999 17:13:17 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id UAA68905; Fri, 23 Apr 1999 20:09:05 -0400 (EDT) Date: Fri, 23 Apr 1999 20:09:05 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith Cc: Soren Schmidt , Christopher Masto , current@FreeBSD.ORG Subject: Re: New ATA driver and crash dumps In-Reply-To: <199904231555.IAA00751@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Apr 1999, Mike Smith wrote: > > Is there any way I can help in getting the atapi-fd driver to work with > > LS-120's? > > Unless it was just recently broken, it works fine (I have one). ATA has never worked with my LS-120. It's a Digital Research/Mitsubishi, and I just can't get it to work right. I get garbled data, that's just it. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 17:17:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from io.dyn.ez-ip.net (h24-66-174-118.xx.wave.shaw.ca [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id 61A1C14CE2 for ; Fri, 23 Apr 1999 17:17:19 -0700 (PDT) (envelope-from jake@io.dyn.ez-ip.net) Received: from io.dyn.ez-ip.net (jake@localhost [127.0.0.1]) by io.dyn.ez-ip.net (8.9.3/8.9.2) with ESMTP id RAA18144 for ; Fri, 23 Apr 1999 17:14:56 -0700 (PDT) (envelope-from jake@io.dyn.ez-ip.net) Message-Id: <199904240014.RAA18144@io.dyn.ez-ip.net> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: new-bus, pcm, and matcd (was Re: new-bus breaks both sound drivers) In-reply-to: Your message of "Fri, 23 Apr 1999 17:53:13 CDT." <19990423225313.CE347109@friley-185-205.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Apr 1999 17:14:54 -0700 From: Jake Burkholder Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >mp3s aren't playing quite right with x11amp though, little > >skips here and there, they work fine with the old kernel. > >mpg123 seems fine, as does the sound in FXTV. > >I'll try making the world again. > > Was there ever any resolution/further inspection of this? Not as far I know; its still happening here. cmp3 (mpg123) also skips in the same way, but its much less noticeable. I've been updating and recompiling almost daily. also, is it known that the matcd driver is now non-functional? It doesn't get probed at all, but it does show up in the visual kernel config screen. Its a 2x cdrom drive that plugs into my sb16; proprietary interface, not IDE. > grep matcd /sys/i386/conf/JAKE controller matcd0 at isa? port 0x230 bio > dmesg | grep matcd > Thank you. Jake -- we are but packets in the internet of life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 18:46:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from dnvrpop1.dnvr.uswest.net (dnvrpop1.dnvr.uswest.net [206.196.128.3]) by hub.freebsd.org (Postfix) with SMTP id 5F53214E00 for ; Fri, 23 Apr 1999 18:46:39 -0700 (PDT) (envelope-from dchang@uswest.net) Received: (qmail 3222 invoked by alias); 24 Apr 1999 01:44:06 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 3194 invoked by uid 0); 24 Apr 1999 01:44:05 -0000 Received: from mdsl206.dnvr.uswest.net (HELO Amber.XtremeDev.com) (209.181.71.206) by dnvrpop1.dnvr.uswest.net with SMTP; 24 Apr 1999 01:44:05 -0000 From: Dave Reply-To: dchang@uswest.net To: "Russell L. Carter" Subject: Re: Code Crusader 2.0.x on FreeBSD Date: Fri, 23 Apr 1999 19:32:19 -0600 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <199904231953.MAA37124@vip.consys.com> Cc: current@FreeBSD.ORG MIME-Version: 1.0 Message-Id: <99042319440600.03051@Amber.XtremeDev.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, I missed that. I took -lc out, but now I get this: g++ -o makemake makemake.o ../../include/jcore/JBroadcaster.o ../../include/jcore/JCollectio n.o ../../include/jcore/JContainer.o ../../include/jcore/JProbDistr.o ../../include/jcore/JOr deredSetT.o ../../include/jcore/JOrderedSetUtil.o ../../include/jcore/JString.o ../../include /jcore/JSubstitute.o ../../include/jcore/jCommandLine.o ../../include/jcore/jStreamUtil.o ../ ../include/jcore/jStreamUtil_UNIX.o ../../include/jcore/jFStreamUtil.o ../../include/jcore/jF StreamUtil_UNIX.o ../../include/jcore/jFileUtil.o ../../include/jcore/jFileUtil_UNIX.o ../../ include/jcore/jDirUtil_UNIX.o ../../include/jcore/jUNIXUtil.o ../../include/jcore/JError.o .. /../include/jcore/JStdError.o ../../include/jcore/JRTTIBase.o ../../include/jcore/JProgressDi splay.o ../../include/jcore/jMemory.o ../../include/jcore/jMath.o ../../include/jcore/jAssert .o ../../include/jcore/JAssertBase.o ../../include/jcore/jGlobals.o ../../include/jcore/JUser Notification.o ../../include/jcore/JTextUserNotification.o ../../include/jcore/JChooseSaveFil e.o ../../include/jcore/JTextChooseSaveFile.o ../../include/jcore/JCreateProgressDisplay.o .. /../include/jcore/JCreateTextPG.o ../../include/jcore/JTextProgressDisplay.o ../../include/jc ore/JLatentPG.o ../../include/jcore/JProcess.o ../../include/jcore/JProcessError.o ../../incl ude/jcore/JThisProcess.o ../../include/jcore/jProcessUtil.o ../../include/jcore/jSignal.o ../ ../include/jcore/JInPipeStream.o ../../include/jcore/JUNIXDirInfo.o ../../include/jcore/JUNIX DirEntry.o ../../include/jcore/Templates-JString.o ../../include/jcore/Templates-int.o ../../ include/jcore/Templates-long.o ../../include/jcore/Templates-longlong.o ../../include/jcore/T emplates-double.o ../../include/jcore/JPtrArray-JString.o ../../include/jcore/JRegex.o ../../ include/jcore/JInterpolate.o ../../include/jcore/jHashFunctions.o ../../include/jcore/jNew.o ../../include/jcore/JMemoryManager.o ../../include/jcore/JMMTable.o ../../include/jcore/JMMAr rayTable.o ../../include/jcore/JMMHashTable.o ../../include/jcore/JMMMonitor.o ../../include/ jcore/JMMErrorPrinter.o ../../include/jcore/JMMRecord.o ../../include/jcore/JArray-JMMRecord. o ../../include/jcore/JHashTable-JMMRecord.o ../../misc/regex/regcomp.o ../../misc/regex/rege xec.o ../../misc/regex/regerror.o ../../misc/regex/regfree.o -L../../lib -lACE-4_6 -pthread -lstdc++ -lm -pthread /usr/local/lib/liblthread.so.0: undefined reference to `_sigsuspend' /usr/local/lib/liblthread.so.0: undefined reference to `_nanosleep' /usr/local/lib/liblthread.so.0: undefined reference to `_fork' /usr/local/lib/liblthread.so.0: undefined reference to `_sched_yield' /usr/local/lib/liblthread.so.0: undefined reference to `_write' /usr/local/lib/liblthread.so.0: undefined reference to `_close' gmake[2]: *** [makemake] Error 1 gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' gmake[1]: *** [install] Error 2 gmake[1]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib' gmake: *** [freebsd] Error 2 A search on freebsd.org/search made references that sigsuspend was removed from libc? Stranger and stranger.. On Fri, 23 Apr 1999, you wrote: > Why is it still linking with libc? > > Russell > > |g++ -o makemake makemake.o ../../include/jcore/JBroadcaster.o ../../include/jcore/JCollection.o ../../include/jcore/JContainer.o ../../include/jcore/JProbDistr.o ../../include/jcore/JOrderedSetT.o ../../include/jcore/JOrderedSetUtil.o ../../include/jcore/JString.o ../../include/jcore/JSubstitute.o ../../include/jcore/jCommandLine.o ../../include/jcore/jStreamUtil.o ../../include/jcore/jStreamUtil_UNIX.o ../../include/jcore/jFStreamUtil.o ../../include/jcore/jFStreamUtil_UNIX.o ../../include/jcore/jFileUtil.o ../../include/jcore/jFileUtil_UNIX.o ../../include/jcore/jDirUtil_UNIX.o ../../include/jcore/jUNIXUtil.o ../../include/jcore/JError.o ../../include/jcore/JStdError.o ../../include/jcore/JRTTIBase.o ../../include/jcore/JProgressDisplay.o ../../include/jcore/jMemory.o ../../include/jcore/jMath.o ../../include/jcore/jAssert.o ../../include/jcore/JAssertBase.o ../../include/jcore/jGlobals.o ../../include/jcore/JUserNotification.o ../../include/jcore/JTextUserNotification.o .! > ./../include/jcore/JChooseSaveFil|e.o ../../include/jcore/JTextChooseSaveFile.o ../../include/jcore/JCreateProgressDisplay.o ../../include/jcore/JCreateTextPG.o ../../include/jcore/JTextProgressDisplay.o ../../include/jcore/JLatentPG.o ../../include/jcore/JProcess.o ../../include/jcore/JProcessError.o ../../include/jcore/JThisProcess.o ../../include/jcore/jProcessUtil.o ../../include/jcore/jSignal.o ../../include/jcore/JInPipeStream.o ../../include/jcore/JUNIXDirInfo.o ../../include/jcore/JUNIXDirEntry.o ../../include/jcore/Templates-JString.o ../../include/jcore/Templates-int.o ../../include/jcore/Templates-long.o ../../include/jcore/Templates-longlong.o ../../include/jcore/Templates-double.o ../../include/jcore/JPtrArray-JString.o ../../include/jcore/JRegex.o ../../include/jcore/JInterpolate.o ../../include/jcore/jHashFunctions.o ../../include/jcore/jNew.o ../../include/jcore/JMemoryManager.o ../../include/jcore/JMMTable.o ../../include/jcore/JMMArrayTable.o ../../include/j! > ccore/JMMHashTable.o ../../include/jcore/JMMMonitor.o ../../include/|jcore/JMMErrorPrinter.o ../../include/jcore/JMMRecord.o ../../include/jcore/JArray-JMMRecord.o ../../include/jcore/JHashTable-JMMRecord.o ../../misc/regex/regcomp.o ../../misc/regex/regexec.o ../../misc/regex/regerror.o ../../misc/regex/regfree.o -L../../lib -lACE-4_6 -pthread -lstdc++ -lm -lc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 21:34:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id A2C4E14DC1 for ; Fri, 23 Apr 1999 21:34:44 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA16137; Sat, 24 Apr 1999 14:02:12 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA09371; Sat, 24 Apr 1999 14:02:11 +0930 (CST) Date: Sat, 24 Apr 1999 14:02:10 +0930 From: Greg Lehey To: "Daniel C. Sobral" Cc: FreeBSD current users Subject: Re: Problems with symbol sequences in recent kernels Message-ID: <19990424140210.N97757@freebie.lemis.com> References: <19990423153323.P91260@freebie.lemis.com> <37208D59.4A8670E8@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37208D59.4A8670E8@newsguy.com>; from Daniel C. Sobral on Sat, Apr 24, 1999 at 12:10:17AM +0900 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 24 April 1999 at 0:10:17 +0900, Daniel C. Sobral wrote: > Greg Lehey wrote: >> >> This has worked quite nicely for some time. Since yesterday, after >> building a kernel with newbus support, I get strange messages if I >> read in the Vinum symbols before reading in the kernel symbols: > > ... > >> I debugged gdb and found that it was finding these references >> (opt_global.h) in cd9660_rrip.o, which it read after reading the Vinum >> kld symbols. If I can convince it to read the kernel symbols first, I >> don't have any trouble. I don't think that it's anything to do with >> that particular file; there must be about 30 files in a typical kernel >> build which refer to this symbol. >> >> If I don't get any response on the list, I'll put in a PR, but I >> thought there's a good chance that somebody will recognize this >> problem and be able to fix it. > > Well, I don't recognize the problem, but I committed changes to > cd9660_rrip.c after newbus got in. Could you try a kernel from > before my changes got in? Just for the files I changed would be > enough. As I mentioned, I didn't think that it has anything to do with the cd code. I've built a kernel with the old version of cd9660, and it has the same problem. Since nobody else has replied, I'll put in the promised PR. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 22:25:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from psf.Pinyon.ORG (ip-17-116.prc.primenet.com [207.218.17.116]) by hub.freebsd.org (Postfix) with ESMTP id 7DEB514DFA for ; Fri, 23 Apr 1999 22:25:42 -0700 (PDT) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.3/8.9.2) with ESMTP id WAA97673 for ; Fri, 23 Apr 1999 22:19:41 -0700 (MST) (envelope-from rcarter@psf.Pinyon.ORG) Message-Id: <199904240519.WAA97673@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.3 To: current@freebsd.org Subject: Re: Code Crusader 2.0.x on FreeBSD In-Reply-To: Your message of "Fri, 23 Apr 1999 19:32:19 CST." <99042319440600.03051@Amber.XtremeDev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Apr 1999 22:19:41 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %Hmm, I missed that. I took -lc out, but now I get this: % [...] %/usr/local/lib/liblthread.so.0: undefined reference to `_sigsuspend' %/usr/local/lib/liblthread.so.0: undefined reference to `_nanosleep' %/usr/local/lib/liblthread.so.0: undefined reference to `_fork' %/usr/local/lib/liblthread.so.0: undefined reference to `_sched_yield' %/usr/local/lib/liblthread.so.0: undefined reference to `_write' %/usr/local/lib/liblthread.so.0: undefined reference to `_close' %gmake[2]: *** [makemake] Error 1 %gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' %gmake[1]: *** [install] Error 2 %gmake[1]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib' %gmake: *** [freebsd] Error 2 % %A search on freebsd.org/search made references that sigsuspend was removed from %libc? Stranger and stranger.. because liblthread is linuxthreads, and you really want what the original ACE configuration probably specified, given the time frame, which is libc_r threads. I am converging in on getting a performance analysis done of libc_r and linuxthreads on ACE and TAO (!!) nailed down, so I don't have time to build this stuff though it looks very interesting. Please do not use any of my config files at www.pinyon.org/ace for this sort of thing. Switching amongst the thread libs is a real mess right now but I have got most of it automated. Still some glitches though. I will say for those interested that the sched.diff patch on Richard Seaman's page works as advertised, and I am just drooling at the prospect of running the full set of "real-time" priority tests on the set of described in several papers on Douglas Schmidt's site. Way cool, everybody who has worked on threads or scheduling! Thanks! Cheers, Russell % % %On Fri, 23 Apr 1999, you wrote: %> Why is it still linking with libc? %> %> Russell %> %> |g++ -o makemake makemake.o ../../include/jcore/JBroadcaster.o ../../include/jcore/JCollection.o ../../include/jcore/JContainer.o ../../include/jcore/JProbDistr.o ../../include/jcore/JOrderedSetT.o ../../include/jcore/JOrderedSetUtil.o ../../include/jcore/JString.o ../../include/jcore/JSubstitute.o ../../include/jcore/jCommandLine.o ../../include/jcore/jStreamUtil.o ../../include/jcore/jStreamUtil_UNIX.o ../../include/jcore/jFStreamUtil.o ../../include/jcore/jFStreamUtil_UNIX.o ../../include/jcore/jFileUtil.o ../../include/jcore/jFileUtil_UNIX.o ../../include/jcore/jDirUtil_UNIX.o ../../include/jcore/jUNIXUtil.o ../../include/jcore/JError.o ../../include/jcore/JStdError.o ../../include/jcore/JRTTIBase.o ../../include/jcore/JProgressDisplay.o ../../include/jcore/jMemory.o ../../include/jcore/jMath.o ../../include/jcore/jAssert.o ../../include/jcore/JAssertBase.o ../../include/jcore/jGlobals.o ../../include/jcore/JUserNotification.o ../../include/jcore/JTextUserNotificatio! n.o .! %> ./../include/jcore/JChooseSaveFil|e.o ../../include/jcore/JTextChooseSaveFile.o ../../include/jcore/JCreateProgressDisplay.o ../../include/jcore/JCreateTextPG.o ../../include/jcore/JTextProgressDisplay.o ../../include/jcore/JLatentPG.o ../../include/jcore/JProcess.o ../../include/jcore/JProcessError.o ../../include/jcore/JThisProcess.o ../../include/jcore/jProcessUtil.o ../../include/jcore/jSignal.o ../../include/jcore/JInPipeStream.o ../../include/jcore/JUNIXDirInfo.o ../../include/jcore/JUNIXDirEntry.o ../../include/jcore/Templates-JString.o ../../include/jcore/Templates-int.o ../../include/jcore/Templates-long.o ../../include/jcore/Templates-longlong.o ../../include/jcore/Templates-double.o ../../include/jcore/JPtrArray-JString.o ../../include/jcore/JRegex.o ../../include/jcore/JInterpolate.o ../../include/jcore/jHashFunctions.o ../../include/jcore/jNew.o ../../include/jcore/JMemoryManager.o ../../include/jcore/JMMTable.o ../../include/jcore/JMMArrayTable.o ../../inclu! de/j! %> ccore/JMMHashTable.o ../../include/jcore/JMMMonitor.o ../../include/|jcore/JMMErrorPrinter.o ../../include/jcore/JMMRecord.o ../../include/jcore/JArray-JMMRecord.o ../../include/jcore/JHashTable-JMMRecord.o ../../misc/regex/regcomp.o ../../misc/regex/regexec.o ../../misc/regex/regerror.o ../../misc/regex/regfree.o -L../../lib -lACE-4_6 -pthread -lstdc++ -lm -lc % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 23 22:31:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C439F14DFA for ; Fri, 23 Apr 1999 22:31:33 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA74896; Fri, 23 Apr 1999 23:28:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA10300; Fri, 23 Apr 1999 23:28:46 -0600 (MDT) Message-Id: <199904240528.XAA10300@harmony.village.org> To: Peter Mutsaers Subject: Re: suspend mode broken since one week ago Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "23 Apr 1999 22:22:51 +0200." <87so9r3x44.fsf@muon.xs4all.nl> References: <87so9r3x44.fsf@muon.xs4all.nl> Date: Fri, 23 Apr 1999 23:28:45 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <87so9r3x44.fsf@muon.xs4all.nl> Peter Mutsaers writes: : Is this a bug that I should report through send-pr, is it already : known as a bug or is this an intentional change in behaviour? This is a known bug. I thought I kludged around it in apm.c in the timeframe that you mentioned. Do you have $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ or newer? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 0:20:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A7E4C14D68 for ; Sat, 24 Apr 1999 00:20:30 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA75103 for ; Sat, 24 Apr 1999 01:17:35 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA10749 for ; Sat, 24 Apr 1999 01:17:44 -0600 (MDT) Message-Id: <199904240717.BAA10749@harmony.village.org> To: current@freebsd.org Subject: Boatload of patche... Date: Sat, 24 Apr 1999 01:17:43 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a boatload of patches I'd like to have reviewed. They are fixes for most of the current batch of compiler warnings in make buildworld. Any takers? I did fine one bug, I think. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 1:12:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from dnvrpop1.dnvr.uswest.net (dnvrpop1.dnvr.uswest.net [206.196.128.3]) by hub.freebsd.org (Postfix) with SMTP id 4738814F0F for ; Sat, 24 Apr 1999 01:12:29 -0700 (PDT) (envelope-from dchang@uswest.net) Received: (qmail 23887 invoked by alias); 24 Apr 1999 08:09:57 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 23879 invoked by uid 0); 24 Apr 1999 08:09:57 -0000 Received: from mdsl206.dnvr.uswest.net (HELO Amber.XtremeDev.com) (209.181.71.206) by dnvrpop1.dnvr.uswest.net with SMTP; 24 Apr 1999 08:09:57 -0000 From: Dave Reply-To: dchang@uswest.net To: current@FreeBSD.ORG Subject: Re: Code Crusader 2.0.x on FreeBSD Date: Fri, 23 Apr 1999 23:43:13 -0600 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <199904240519.WAA97673@psf.Pinyon.ORG> MIME-Version: 1.0 Message-Id: <99042402095800.04561@Amber.XtremeDev.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Replying to both Scott Michel and Russell L. Carter: Scott. According to man pthread, libc_r is pulled in automatically by the -pthread switch. From man pthread : A FreeBSD specific option has been added to gcc to make linking threaded processes simple. gcc -pthread links a threaded process against libc_r instead of libc. But I tried it anyways, and was presented with the same result. lc_r -lstdc++ -lm -lc_r -pthread /usr/local/lib/liblthread.so.0: undefined reference to `_sigsuspend' /usr/local/lib/liblthread.so.0: undefined reference to `_nanosleep' /usr/local/lib/liblthread.so.0: undefined reference to `_fork' /usr/local/lib/liblthread.so.0: undefined reference to `_sched_yield' /usr/local/lib/liblthread.so.0: undefined reference to `_write' /usr/local/lib/liblthread.so.0: undefined reference to `_close' gmake[2]: *** [makemake] Error 1 gmake[2]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/programs/makemake' gmake[1]: *** [install] Error 2 gmake[1]: Leaving directory `/usr/home/dave/temp/JX-1.1.22/lib' gmake: *** [freebsd] Error 2 On Fri, 23 Apr 1999, Scott Michel wrote: >Try adding "-lc_r" after "-lpthread". Russel. Ok, I understand, I will use the config files that came with ACE. ACE comes with a config-freebsd.h and config-freebsd-pthread.h (the same for platform_freebsd.GNU and platform_freebsd_pthread.GNU), and the only one that would get the ACE library to compile are the [-_]pthread files. And the results are good, I'm not getting core dumps anymore, and things are actually compiling, except for code crusader itself. But it seems to be more of a problem with make.header making references to jtree_constants and jtree dirs that doesn't exist. But this is outside the problems with the threads. Thank you for your help, everyone. This thing looks like it just might work. Now to have a few words with the author about the jtree references... On Fri, 23 Apr 1999, Russell L. Carter wrote: > [...] > because liblthread is linuxthreads, and you really want what the > original ACE configuration probably specified, given the time frame, > which is libc_r threads. > > I am converging in on getting a performance analysis done of libc_r > and linuxthreads on ACE and TAO (!!) nailed down, > so I don't have time to build this stuff though > it looks very interesting. Please do not use any of my config files > at www.pinyon.org/ace for this sort of thing. > > Switching amongst the thread libs is a real mess right now but I have > got most of it automated. Still some glitches though. > > I will say for those interested that the sched.diff patch on > Richard Seaman's page works as advertised, and I am just drooling > at the prospect of running the full set of "real-time" priority tests on > the set of described in several papers on Douglas Schmidt's site. > > Way cool, everybody > who has worked on threads or scheduling! Thanks! > > Cheers, > Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 2:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 376F814E6C for ; Sat, 24 Apr 1999 02:35:09 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 5A29A18C6; Sat, 24 Apr 1999 11:35:22 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 571C349C2; Sat, 24 Apr 1999 11:35:22 +0200 (CEST) Date: Sat, 24 Apr 1999 11:35:21 +0200 (CEST) From: Andrzej Bialecki To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? In-Reply-To: <199904231110.NAA00657@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Apr 1999, Luigi Rizzo wrote: > Hi, > > i was wondering if the limitations that are supposed to be enforced via > the login.conf mechanism do really work... > > In particular, i have tried (on 3.1 something, but don't think that > current is much different in this respect) to enforce the daily etc. > login times but the system seems to ignore them. > > I think /etc/login.conf is properly parsed, because if i assign a user > to a class that is not defined in login.conf i get complaints, but > other than that i am unable to limit login time... > > Any hints ? That's also my impression. I glipmsed the whole source tree and I couldn't find any place where the limits are enforced. BTW. what entity should enforce login time limits? Kernel? Some user-space daemon? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 5: 2:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (Postfix) with ESMTP id 938E414CBF for ; Sat, 24 Apr 1999 05:02:07 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id VAA00666 for ; Sat, 24 Apr 1999 21:02:07 +0900 (JST) To: current@FreeBSD.org Subject: singed short to unsigned long conversion problem in isa.c From: KATO Takenori X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990424210206R.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 24 Apr 1999 21:02:06 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 39 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The type of the member id_port in isa_device structure is signed short and a value is converted int unsigned long to allocate I/O port resource via bus_alloc_resources. If an I/O port >= 0x8000, conversion from signed short to unsigned long causes unexpected result and nexus_alloc_resouce cannot allocate resouce. Fix is: ---------- BEGIN ---------- *** isa.c.orig Sat Apr 24 20:55:32 1999 --- isa.c Sat Apr 24 20:55:24 1999 *************** *** 75,81 **** * The structure used to attach devices to the isa bus. */ struct isa_device { ! short id_port[ISA_NPORT_IVARS]; u_short id_portsize[ISA_NPORT_IVARS]; vm_offset_t id_maddr[ISA_NMEM_IVARS]; vm_size_t id_msize[ISA_NMEM_IVARS]; --- 75,81 ---- * The structure used to attach devices to the isa bus. */ struct isa_device { ! u_short id_port[ISA_NPORT_IVARS]; u_short id_portsize[ISA_NPORT_IVARS]; vm_offset_t id_maddr[ISA_NMEM_IVARS]; vm_size_t id_msize[ISA_NMEM_IVARS]; ---------- END ---------- If this should not be in sys/i386/isa, I will copy this file into sys/pc98/pc98. Comment please. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 3.1: Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 2.2.8: Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 6:40:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from wanadoo.fr (smtp-out-004.wanadoo.fr [193.252.19.87]) by hub.freebsd.org (Postfix) with ESMTP id 2ADC814FC6 for ; Sat, 24 Apr 1999 06:40:15 -0700 (PDT) (envelope-from stephane@wanadoo.fr) Received: from bdijon1-2-144.abo.wanadoo.fr [193.250.195.144] by wanadoo.fr for Paris Sat, 24 Apr 1999 15:40:02 +0200 (MET DST) Received: (from stephane@localhost) by sequoia.mondomaineamoi.megalo (8.9.3/8.9.1) id PAA01205; Sat, 24 Apr 1999 15:37:50 +0200 (CEST) (envelope-from stephane) Date: Sat, 24 Apr 1999 15:37:50 +0200 (CEST) Message-Id: <199904241337.PAA01205@sequoia.mondomaineamoi.megalo> From: Stephane Legrand MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrzej Bialecki Cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? In-Reply-To: References: <199904231110.NAA00657@labinfo.iet.unipi.it> X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > > Hi, > > > > i was wondering if the limitations that are supposed to be enforced via > > the login.conf mechanism do really work... > > > > In particular, i have tried (on 3.1 something, but don't think that > > current is much different in this respect) to enforce the daily etc. > > login times but the system seems to ignore them. > > > > I think /etc/login.conf is properly parsed, because if i assign a user > > to a class that is not defined in login.conf i get complaints, but > > other than that i am unable to limit login time... > > > > Any hints ? > > That's also my impression. I glipmsed the whole source tree and I couldn't > find any place where the limits are enforced. BTW. what entity should > enforce login time limits? Kernel? Some user-space daemon? > To report a login.conf success, i've used on a 2.2.8 system the "cputime" ressource limit. I set it to zero and that worked very well. So may be only some limits are implemented ? Stephane Legrand. -- Stephane.Legrand@wanadoo.fr : http://perso.wanadoo.fr/stephane.legrand/ FreeBSD Francophone : http://www.freebsd-fr.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 6:57:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailin.hkstar.com (cygnus.hkstar.com [202.82.3.13]) by hub.freebsd.org (Postfix) with ESMTP id 0137714C16 for ; Sat, 24 Apr 1999 06:57:45 -0700 (PDT) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by mailin.hkstar.com (8.8.8/8.8.5) with ESMTP id VAA22012 for ; Sat, 24 Apr 1999 21:57:44 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id VAA19929 for freebsd-current@freebsd.org; Sat, 24 Apr 1999 21:57:42 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199904241357.VAA19929@b1.hkstar.com> Subject: make world error with source upto src-cur.3843 To: freebsd-current@freebsd.org Date: Sat, 24 Apr 1999 21:57:41 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Is there anyone know how to fix the problem. I cannot make world with source src-cur.3843 and the error is as followings. Thanks. Clarence ======= Error ======= cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: `GPLUSPLUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: initializer element for `include_defaults_array[0].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: `OLD_GPLUSPLUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: initializer element for `include_defaults_array[1].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: `GCC_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: initializer element for `include_defaults_array[2].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c: In function `main': /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: `GCC_INCLUDE_DIR' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: for each function it appears in.) *** Error code 1 Stop. ======= Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 7:24:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5702D14E75 for ; Sat, 24 Apr 1999 07:24:10 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA29479; Sat, 24 Apr 1999 15:30:26 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 24 Apr 1999 15:30:26 +0100 (BST) From: Doug Rabson To: KATO Takenori Cc: current@freebsd.org Subject: Re: singed short to unsigned long conversion problem in isa.c In-Reply-To: <19990424210206R.kato@gneiss.eps.nagoya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Apr 1999, KATO Takenori wrote: > The type of the member id_port in isa_device structure is signed short > and a value is converted int unsigned long to allocate I/O port > resource via bus_alloc_resources. If an I/O port >= 0x8000, > conversion from signed short to unsigned long causes unexpected result > and nexus_alloc_resouce cannot allocate resouce. > > Fix is: > > ---------- BEGIN ---------- > *** isa.c.orig Sat Apr 24 20:55:32 1999 > --- isa.c Sat Apr 24 20:55:24 1999 > *************** > *** 75,81 **** > * The structure used to attach devices to the isa bus. > */ > struct isa_device { > ! short id_port[ISA_NPORT_IVARS]; > u_short id_portsize[ISA_NPORT_IVARS]; > vm_offset_t id_maddr[ISA_NMEM_IVARS]; > vm_size_t id_msize[ISA_NMEM_IVARS]; > --- 75,81 ---- > * The structure used to attach devices to the isa bus. > */ > struct isa_device { > ! u_short id_port[ISA_NPORT_IVARS]; > u_short id_portsize[ISA_NPORT_IVARS]; > vm_offset_t id_maddr[ISA_NMEM_IVARS]; > vm_size_t id_msize[ISA_NMEM_IVARS]; > ---------- END ---------- > > If this should not be in sys/i386/isa, I will copy this file into > sys/pc98/pc98. Comment please. It needs to be signed since the value -1 is used to indicate no port resources. Perhaps it would be better to change it to 'int' instead of 'u_short'. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 7:39: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 34AD514CB9 for ; Sat, 24 Apr 1999 07:39:07 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id F286C18C6; Sat, 24 Apr 1999 16:39:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id ED2AA49BD; Sat, 24 Apr 1999 16:39:20 +0200 (CEST) Date: Sat, 24 Apr 1999 16:39:20 +0200 (CEST) From: Andrzej Bialecki To: Stephane Legrand Cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? In-Reply-To: <199904241337.PAA01205@sequoia.mondomaineamoi.megalo> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Apr 1999, Stephane Legrand wrote: > > That's also my impression. I glipmsed the whole source tree and I couldn't > > find any place where the limits are enforced. BTW. what entity should > > enforce login time limits? Kernel? Some user-space daemon? > > > > To report a login.conf success, i've used on a 2.2.8 system the > "cputime" ressource limit. I set it to zero and that worked very > well. So may be only some limits are implemented ? You're right, this part works. However, I was talking about login time (which is how long can user be logged on to the system), which isn't checked anywhere. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 8: 0:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 8114214FB5; Sat, 24 Apr 1999 08:00:22 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 699F518C6; Sat, 24 Apr 1999 17:00:35 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 624FB49BD; Sat, 24 Apr 1999 17:00:35 +0200 (CEST) Date: Sat, 24 Apr 1999 17:00:31 +0200 (CEST) From: Andrzej Bialecki To: sos@freebsd.org Cc: freebsd-current@freebsd.org Subject: New ATA hangs my machine Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1217266395-924966031=:25684" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1217266395-924966031=:25684 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I'd love to play with the new IDE drivers, especially that I got an LS-120 drive, but... I can't mount my filesystems with it. I'm using today's sources (kernel config file attached), and it fsck's them just ok, and then just hangs. Keyboard works, though. If I boot with -v, it reports: ad0: invalid primary partition table: no magic and of course it just sits there... The issue is, however, that old kernel booted just fine. I attached relevant parts of dmesg with old drivers, and disklabel and fdisk output. Any clues? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- --0-1217266395-924966031=:25684 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dm.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dm.out" cGNpMDogPFBDSSBidXM+IG9uIHBjaWIwDQpjaGlwMDogPEludGVsIDgyNDM5 PiBhdCBkZXZpY2UgMC4wIG9uIHBjaTANCmlzYWIwOiA8SW50ZWwgODIzNzFT QiBQQ0kgdG8gSVNBIGJyaWRnZT4gYXQgZGV2aWNlIDcuMCBvbiBwY2kwDQpp c2EwOiA8SVNBIGJ1cz4gb24gaXNhYjANCmlkZV9wY2kwOiA8SW50ZWwgUElJ WDMgQnVzLW1hc3RlciBJREUgY29udHJvbGxlcj4gYXQgZGV2aWNlIDcuMSBv biBwY2kwDQppbnRlbF9waWl4X3N0YXR1czogcHJpbWFyeSBtYXN0ZXIgc2Ft cGxlID0gMywgbWFzdGVyIHJlY292ZXJ5ID0gMQ0KaW50ZWxfcGlpeF9zdGF0 dXM6IHByaW1hcnkgbWFzdGVyIGZhc3RETUFvbmx5IGRpc2FibGVkLCBwcmUv cG9zdCBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBJT1JEWSBzYW1w bGluZyBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBmYXN0IFBJTyBl bmFibGVkDQppbnRlbF9waWl4X3N0YXR1czogcHJpbWFyeSBzbGF2ZSBzYW1w bGUgPSAzLCBzbGF2ZSByZWNvdmVyeSA9IDENCmludGVsX3BpaXhfc3RhdHVz OiBwcmltYXJ5IHNsYXZlIGZhc3RETUFvbmx5IGRpc2FibGVkLCBwcmUvcG9z dCBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBJT1JEWSBzYW1wbGlu ZyBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBmYXN0IFBJTyBlbmFi bGVkDQppZGVfcGNpOiBidXNtYXN0ZXIgMCBzdGF0dXM6IDA0IGZyb20gcG9y dDogMDAwMDkwMDINCmludGVsX3BpaXhfc3RhdHVzOiBzZWNvbmRhcnkgbWFz dGVyIHNhbXBsZSA9IDMsIG1hc3RlciByZWNvdmVyeSA9IDENCmludGVsX3Bp aXhfc3RhdHVzOiBzZWNvbmRhcnkgbWFzdGVyIGZhc3RETUFvbmx5IGRpc2Fi bGVkLCBwcmUvcG9zdCBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBJ T1JEWSBzYW1wbGluZyBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBm YXN0IFBJTyBlbmFibGVkDQppbnRlbF9waWl4X3N0YXR1czogc2Vjb25kYXJ5 IHNsYXZlIHNhbXBsZSA9IDMsIHNsYXZlIHJlY292ZXJ5ID0gMQ0KaW50ZWxf cGlpeF9zdGF0dXM6IHNlY29uZGFyeSBzbGF2ZSBmYXN0RE1Bb25seSBkaXNh YmxlZCwgcHJlL3Bvc3QgZW5hYmxlZCwNCmludGVsX3BpaXhfc3RhdHVzOiAg SU9SRFkgc2FtcGxpbmcgZW5hYmxlZCwNCmludGVsX3BpaXhfc3RhdHVzOiAg ZmFzdCBQSU8gZW5hYmxlZA0KaWRlX3BjaTogYnVzbWFzdGVyIDEgc3RhdHVz OiAwNCBmcm9tIHBvcnQ6IDAwMDA5MDBhDQpmZGMwOiBpbnRlcnJ1cHRpbmcg YXQgaXJxIDYNCmZkYzA6IDxORUMgNzIwNjVCIG9yIGNsb25lPiBhdCBwb3J0 IDB4M2YwLTB4M2Y3IGlycSA2IGRycSAyIG9uIGlzYTANCmZkYzA6IEZJRk8g ZW5hYmxlZCwgOCBieXRlcyB0aHJlc2hvbGQNCmZkMDogPDE0NDAtS0IgMy41 IiBkcml2ZT4gYXQgZmRjMCBkcml2ZSAwDQp3ZGMwIGF0IHBvcnQgMHgxZjAt MHgxZjcgaXJxIDE0IGZsYWdzIDB4YTBmZmEwZmYgb24gaXNhMA0KaW50ZWxf cGlpeF9kbWFpbml0OiBzZXR0aW5nIG11bHRpd29yZCBETUEgbW9kZSAyDQp3 ZDA6IHdkc2V0bW9kZSgpIHNldHRpbmcgdHJhbnNmZXIgbW9kZSB0byAyMg0K aW50ZWxfcGlpeF9zdGF0dXM6IHByaW1hcnkgbWFzdGVyIHNhbXBsZSA9IDMs IG1hc3RlciByZWNvdmVyeSA9IDENCmludGVsX3BpaXhfc3RhdHVzOiBwcmlt YXJ5IG1hc3RlciBmYXN0RE1Bb25seSBkaXNhYmxlZCwgcHJlL3Bvc3QgZW5h YmxlZCwNCmludGVsX3BpaXhfc3RhdHVzOiAgSU9SRFkgc2FtcGxpbmcgZW5h YmxlZCwNCmludGVsX3BpaXhfc3RhdHVzOiAgZmFzdCBQSU8gZW5hYmxlZA0K d2RjMDogdW5pdCAwICh3ZDApOiA8V0RDIEFDMjI1MDBMPiwgRE1BLCAzMi1i aXQsIG11bHRpLWJsb2NrLTE2DQp3ZDA6IDI0NDFNQiAoNDk5OTY4MCBzZWN0 b3JzKSwgNDk2MCBjeWxzLCAxNiBoZWFkcywgNjMgUy9ULCA1MTIgQi9TDQp3 ZDA6IEFUQSBJTlFVSVJFIHZhbGlkID0gMDAwMywgZG1hbXdvcmQgPSAwNDA3 LCBhcGlvID0gMDAwMywgdWRtYSA9IDAwMDANCmludGVsX3BpaXhfZG1haW5p dDogc2V0dGluZyBtdWx0aXdvcmQgRE1BIG1vZGUgMg0Kd2QxOiB3ZHNldG1v ZGUoKSBzZXR0aW5nIHRyYW5zZmVyIG1vZGUgdG8gMjINCmludGVsX3BpaXhf c3RhdHVzOiBwcmltYXJ5IHNsYXZlIHNhbXBsZSA9IDMsIHNsYXZlIHJlY292 ZXJ5ID0gMQ0KaW50ZWxfcGlpeF9zdGF0dXM6IHByaW1hcnkgc2xhdmUgZmFz dERNQW9ubHkgZGlzYWJsZWQsIHByZS9wb3N0IGVuYWJsZWQsDQppbnRlbF9w aWl4X3N0YXR1czogIElPUkRZIHNhbXBsaW5nIGVuYWJsZWQsDQppbnRlbF9w aWl4X3N0YXR1czogIGZhc3QgUElPIGVuYWJsZWQNCndkYzA6IHVuaXQgMSAo d2QxKTogPFFVQU5UVU0gRklSRUJBTEwgU1Q0LjNBPiwgRE1BLCAzMi1iaXQs IG11bHRpLWJsb2NrLTE2DQp3ZDE6IDQxMTBNQiAoODQxODgxNiBzZWN0b3Jz KSwgMTQ4NDggY3lscywgOSBoZWFkcywgNjMgUy9ULCA1MTIgQi9TDQp3ZDE6 IEFUQSBJTlFVSVJFIHZhbGlkID0gMDAwNywgZG1hbXdvcmQgPSAwNDA3LCBh cGlvID0gMDAwMywgdWRtYSA9IDAwMDcNCndkYzA6IGludGVycnVwdGluZyBh dCBpcnEgMTQNCndkYzEgYXQgcG9ydCAweDE3MC0weDE3NyBpcnEgMTUgZmxh Z3MgMHg4MGZmODBmZiBvbiBpc2EwDQp3ZGMxOiB1bml0IDAgKGF0YXBpKTog PExTLTEyMCBWRVI0ICAgMDYgICAgICAgICAgICAgIFVIRCBGbG9wcHkvMDQy ME00MTQ+LCByZW1vdmFibGUsIGRtYSwgaW9yZHkNCndkYzE6IEFUQVBJIEZs b3BwaWVzIG5vdCBjb25maWd1cmVkDQp3ZGMxOiB1bml0IDEgKGF0YXBpKTog PENSRC04MzIwQi8xLjIyPiwgcmVtb3ZhYmxlLCBhY2NlbCwgZG1hLCBpb3Jk aXMNCndjZDA6IGRyaXZlIHNwZWVkIDE3MSAtIDU1MDBLQi9zZWMsIDEyOEtC IGNhY2hlDQp3Y2QwOiBzdXBwb3J0ZWQgcmVhZCB0eXBlczogQ0QtUiwgQ0Qt UlcsIENELURBLCBwYWNrZXQgdHJhY2sNCndjZDA6IEF1ZGlvOiBwbGF5LCAy NTUgdm9sdW1lIGxldmVscw0Kd2NkMDogTWVjaGFuaXNtOiBlamVjdGFibGUg dHJheQ0Kd2NkMDogTWVkaXVtOiBuby9ibGFuayBkaXNjIGluc2lkZSwgdW5s b2NrZWQsIGxvY2sgcHJvdGVjdGVkDQp3ZGMxOiBpbnRlcnJ1cHRpbmcgYXQg aXJxIDE1DQphdGtiZGMwOiA8a2V5Ym9hcmQgY29udHJvbGxlciAoaTgwNDIp PiBhdCBwb3J0IDB4NjAgb24gaXNhMA0KYXRrYmQwOiA8QVQgS2V5Ym9hcmQ+ IG9uIGF0a2JkYzANCmF0a2JkOiB0aGUgY3VycmVudCBrYmQgY29udHJvbGxl ciBjb21tYW5kIGJ5dGUgMDA2NQ0KYXRrYmQ6IGtleWJvYXJkIElEIDB4NDFh YiAoMikNCmtiZGM6IFJFU0VUX0tCRCByZXR1cm4gY29kZTowMGZhDQprYmRj OiBSRVNFVF9LQkQgc3RhdHVzOjAwYWENCmtiZDA6IGF0a2JkMCwgQVQgMTAx LzEwMiAoMiksIGNvbmZpZzoweDAsIGZsYWdzOjB4M2QwMDAwDQphdGtiZDA6 IGludGVycnVwdGluZyBhdCBpcnEgMQ0KcHNtMDogY3VycmVudCBjb21tYW5k IGJ5dGU6MDA2NQ0Ka2JkYzogVEVTVF9BVVhfUE9SVCBzdGF0dXM6MDAwMA0K a2JkYzogUkVTRVRfQVVYIHJldHVybiBjb2RlOjAwZmUNCmtiZGM6IFJFU0VU X0FVWCByZXR1cm4gY29kZTowMGZlDQprYmRjOiBSRVNFVF9BVVggcmV0dXJu IGNvZGU6MDBmZQ0Ka2JkYzogRElBR05PU0Ugc3RhdHVzOjAwNTUNCmtiZGM6 IFRFU1RfS0JEX1BPUlQgc3RhdHVzOjAwMDANCnBzbTA6IGZhaWxlZCB0byBy ZXNldCB0aGUgYXV4IGRldmljZS4NCnZnYTA6IDxHZW5lcmljIElTQSBWR0E+ IG9uIGlzYTANClsuLi5dDQpCSU9TIEdlb21ldHJpZXM6DQogMDowMDAwMDAw MCAwLi4wPTEgY3lsaW5kZXJzLCAwLi4wPTEgaGVhZHMsIDEuLjA9MCBzZWN0 b3JzDQogMTowMDAwMDAwMCAwLi4wPTEgY3lsaW5kZXJzLCAwLi4wPTEgaGVh ZHMsIDEuLjA9MCBzZWN0b3JzDQogMjowMDAwMDAwMCAwLi4wPTEgY3lsaW5k ZXJzLCAwLi4wPTEgaGVhZHMsIDEuLjA9MCBzZWN0b3JzDQogMzowMDAwMDAw MCAwLi4wPTEgY3lsaW5kZXJzLCAwLi4wPTEgaGVhZHMsIDEuLjA9MCBzZWN0 b3JzDQogNDowMDAwMDAwMCAwLi4wPTEgY3lsaW5kZXJzLCAwLi4wPTEgaGVh ZHMsIDEuLjA9MCBzZWN0b3JzDQogNTowMDAwMDAwMCAwLi4wPTEgY3lsaW5k ZXJzLCAwLi4wPTEgaGVhZHMsIDEuLjA9MCBzZWN0b3JzDQogNjowMDAwMDAw MCAwLi4wPTEgY3lsaW5kZXJzLCAwLi4wPTEgaGVhZHMsIDEuLjA9MCBzZWN0 b3JzDQogNzowMDAwMDAwMCAwLi4wPTEgY3lsaW5kZXJzLCAwLi4wPTEgaGVh ZHMsIDEuLjA9MCBzZWN0b3JzDQogMCBhY2NvdW50ZWQgZm9yDQpEZXZpY2Ug Y29uZmlndXJhdGlvbiBmaW5pc2hlZC4NCkNvbnNpZGVyaW5nIEZGUyByb290 IGYvcy4NCmNoYW5naW5nIHJvb3QgZGV2aWNlIHRvIHdkMXMxYQ0Kd2QxczE6 IHR5cGUgMHhhNSwgc3RhcnQgNjMsIGVuZCA9IDYyOTE0MzEsIHNpemUgNjI5 MTM2OSANCndkMXMxOiBDL0gvUyBlbmQgMzkxLzE1OC82MyAoMzkyNjY2Mykg IT0gZW5kIDYyOTE0MzE6IGludmFsaWQNCndkMXMyOiB0eXBlIDB4YTUsIHN0 YXJ0IDYyOTE0MzIsIGVuZCA9IDg0MTg4MTUsIHNpemUgMjEyNzM4NCANCndk MXMyOiBDL0gvUyBzdGFydCAzOTEvMTU5LzEgKDM5MjY2NjQpICE9IHN0YXJ0 IDYyOTE0MzI6IGludmFsaWQNCndkMXMyOiBDL0gvUyBlbmQgNTI0LzExLzYz ICg1MjQ5NjYzKSAhPSBlbmQgODQxODgxNTogaW52YWxpZA0Kd2QwczE6IHR5 cGUgMHg2LCBzdGFydCA2MywgZW5kID0gMTAyNDEyNywgc2l6ZSAxMDI0MDY1 IDogT0sNCndkMHMyOiB0eXBlIDB4YTUsIHN0YXJ0IDEwMjQxMjgsIGVuZCA9 IDMwNjQzMTksIHNpemUgMjA0MDE5MiA6IE9LDQp3ZDBzMzogdHlwZSAweDYz LCBzdGFydCAzMDY0MzIwLCBlbmQgPSA0MDc5ODc5LCBzaXplIDEwMTU1NjAg OiBPSw0Kd2QwczQ6IHR5cGUgMHhhNSwgc3RhcnQgNDA4MDM4NCwgZW5kID0g NDk5OTY3OSwgc2l6ZSA5MTkyOTYgOiBPSw0KZmZzX21vdW50ZnM6IHN1cGVy YmxvY2sgdXBkYXRlZCBmb3Igc29mdCB1cGRhdGVzDQpmZnNfbW91bnRmczog c3VwZXJibG9jayB1cGRhdGVkIGZvciBzb2Z0IHVwZGF0ZXMNCmZmc19tb3Vu dGZzOiBzdXBlcmJsb2NrIHVwZGF0ZWQgZm9yIHNvZnQgdXBkYXRlcw0Kd2Qw czE6IHR5cGUgMHg2LCBzdGFydCA2MywgZW5kID0gMTAyNDEyNywgc2l6ZSAx MDI0MDY1IDogT0sNCndkMHMyOiB0eXBlIDB4YTUsIHN0YXJ0IDEwMjQxMjgs IGVuZCA9IDMwNjQzMTksIHNpemUgMjA0MDE5MiA6IE9LDQp3ZDBzMzogdHlw ZSAweDYzLCBzdGFydCAzMDY0MzIwLCBlbmQgPSA0MDc5ODc5LCBzaXplIDEw MTU1NjAgOiBPSw0Kd2QwczQ6IHR5cGUgMHhhNSwgc3RhcnQgNDA4MDM4NCwg ZW5kID0gNDk5OTY3OSwgc2l6ZSA5MTkyOTYgOiBPSw0KZmZzX21vdW50ZnM6 IHN1cGVyYmxvY2sgdXBkYXRlZCBmb3Igc29mdCB1cGRhdGVzDQpzcGxhc2g6 IGltYWdlIGRlY29kZXIgZm91bmQ6IHdhcnBfc2F2ZXINCg== --0-1217266395-924966031=:25684 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="fdisk.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="fdisk.out" KioqKioqKiBXb3JraW5nIG9uIGRldmljZSAvZGV2L3J3ZDEgKioqKioqKg0K cGFyYW1ldGVycyBleHRyYWN0ZWQgZnJvbSBpbi1jb3JlIGRpc2tsYWJlbCBh cmU6DQpjeWxpbmRlcnM9ODQwIGhlYWRzPTE1OSBzZWN0b3JzL3RyYWNrPTYz ICgxMDAxNyBibGtzL2N5bCkNCg0KcGFyYW1ldGVycyB0byBiZSB1c2VkIGZv ciBCSU9TIGNhbGN1bGF0aW9ucyBhcmU6DQpjeWxpbmRlcnM9ODQwIGhlYWRz PTE1OSBzZWN0b3JzL3RyYWNrPTYzICgxMDAxNyBibGtzL2N5bCkNCg0KTWVk aWEgc2VjdG9yIHNpemUgaXMgNTEyDQpXYXJuaW5nOiBCSU9TIHNlY3RvciBu dW1iZXJpbmcgc3RhcnRzIHdpdGggc2VjdG9yIDENCkluZm9ybWF0aW9uIGZy b20gRE9TIGJvb3RibG9jayBpczoNClRoZSBkYXRhIGZvciBwYXJ0aXRpb24g MSBpczoNCnN5c2lkIDE2NSwoRnJlZUJTRC9OZXRCU0QvMzg2QlNEKQ0KICAg IHN0YXJ0IDYzLCBzaXplIDYyOTEzNjkgKDMwNzEgTWVnKSwgZmxhZyA4MCAo YWN0aXZlKQ0KCWJlZzogY3lsIDAvIHNlY3RvciAxLyBoZWFkIDE7DQoJZW5k OiBjeWwgMzkxLyBzZWN0b3IgNjMvIGhlYWQgMTU4DQpUaGUgZGF0YSBmb3Ig cGFydGl0aW9uIDIgaXM6DQpzeXNpZCAxNjUsKEZyZWVCU0QvTmV0QlNELzM4 NkJTRCkNCiAgICBzdGFydCA2MjkxNDMyLCBzaXplIDIxMjczODQgKDEwMzgg TWVnKSwgZmxhZyAwDQoJYmVnOiBjeWwgMzkxLyBzZWN0b3IgMS8gaGVhZCAx NTk7DQoJZW5kOiBjeWwgNTI0LyBzZWN0b3IgNjMvIGhlYWQgMTENClRoZSBk YXRhIGZvciBwYXJ0aXRpb24gMyBpczoNCjxVTlVTRUQ+DQpUaGUgZGF0YSBm b3IgcGFydGl0aW9uIDQgaXM6DQo8VU5VU0VEPg0K --0-1217266395-924966031=:25684 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="label.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="label.out" IyAvZGV2L3J3ZDFjOg0KdHlwZTogRVNESQ0KZGlzazogd2QxczENCmxhYmVs OiANCmZsYWdzOg0KYnl0ZXMvc2VjdG9yOiA1MTINCnNlY3RvcnMvdHJhY2s6 IDYzDQp0cmFja3MvY3lsaW5kZXI6IDkNCnNlY3RvcnMvY3lsaW5kZXI6IDU2 Nw0KY3lsaW5kZXJzOiAxMTA5NQ0Kc2VjdG9ycy91bml0OiA2MjkxMzY5DQpy cG06IDM2MDANCmludGVybGVhdmU6IDENCnRyYWNrc2tldzogMA0KY3lsaW5k ZXJza2V3OiAwDQpoZWFkc3dpdGNoOiAwCQkjIG1pbGxpc2Vjb25kcw0KdHJh Y2stdG8tdHJhY2sgc2VlazogMAkjIG1pbGxpc2Vjb25kcw0KZHJpdmVkYXRh OiAwIA0KDQo4IHBhcnRpdGlvbnM6DQojICAgICAgICBzaXplICAgb2Zmc2V0 ICAgIGZzdHlwZSAgIFtmc2l6ZSBic2l6ZSBicHMvY3BnXQ0KICBhOiAgICA4 MTkyMCAgICAgICAgMCAgICA0LjJCU0QgICAgICAgIDAgICAgIDAgICAgIDAg CSMgKEN5bC4gICAgMCAtIDE0NCopDQogIGI6ICAgMjYyMTQ0ICAgIDgxOTIw ICAgICAgc3dhcCAgICAgICAgICAgICAgICAgICAgCSMgKEN5bC4gIDE0NCot IDYwNiopDQogIGM6ICA2MjkxMzY5ICAgICAgICAwICAgIHVudXNlZCAgICAg ICAgMCAgICAgMCAgICAgICAJIyAoQ3lsLiAgICAwIC0gMTEwOTUqKQ0KICBl OiAgIDE2Mzg0MCAgIDM0NDA2NCAgICA0LjJCU0QgICAgICAgIDAgICAgIDAg ICAgIDAgCSMgKEN5bC4gIDYwNiotIDg5NSopDQogIGY6ICA1NzgzNDY1ICAg NTA3OTA0ICAgIDQuMkJTRCAgICAgICAgMCAgICAgMCAgICAgMCAJIyAoQ3ls LiAgODk1Ki0gMTEwOTUqKQ0K --0-1217266395-924966031=:25684 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=TUNE Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=TUNE Iw0KIyBHRU5FUklDIC0tIEdlbmVyaWMgbWFjaGluZSB3aXRoIFdEL0FIeC9O Q1IvQlR4IGZhbWlseSBkaXNrcw0KIw0KIyBGb3IgbW9yZSBpbmZvcm1hdGlv biByZWFkIHRoZSBoYW5kYm9vayBwYXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlv biAtPiANCiMgQ29uZmlndXJpbmcgdGhlIEZyZWVCU0QgS2VybmVsIC0+IFRo ZSBDb25maWd1cmF0aW9uIEZpbGUuIA0KIyBUaGUgaGFuZGJvb2sgaXMgYXZh aWxhYmxlIGluIC91c3Ivc2hhcmUvZG9jL2hhbmRib29rIG9yIG9ubGluZSBh cw0KIyBsYXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdp ZGUgV2ViIHNlcnZlciANCiMgPFVSTDpodHRwOi8vd3d3LkZyZWVCU0QuT1JH Lz4NCiMNCiMgQW4gZXhoYXVzdGl2ZSBsaXN0IG9mIG9wdGlvbnMgYW5kIG1v cmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSANCiMgZGV2aWNlIGxp bmVzIGlzIHByZXNlbnQgaW4gdGhlIC4vTElOVCBjb25maWd1cmF0aW9uIGZp bGUuIElmIHlvdSBhcmUgDQojIGluIGRvdWJ0IGFzIHRvIHRoZSBwdXJwb3Nl IG9yIG5lY2Vzc2l0eSBvZiBhIGxpbmUsIGNoZWNrIGZpcnN0IGluIExJTlQu DQojDQojCSRJZDogR0VORVJJQyx2IDEuODggMTk5Ny8wMy8xMyAxOTowMzo1 OCBiZGUgRXhwICQNCg0KbWFjaGluZQkJImkzODYiDQojY3B1CQkiSTQ4Nl9D UFUiDQpjcHUJCSJJNTg2X0NQVSINCmlkZW50CQlUVU5FDQptYXh1c2Vycwkz MA0KDQpvcHRpb25zCQlJTkVUCQkJI0ludGVyTkVUd29ya2luZw0Kb3B0aW9u cwkJRkZTCQkJI0JlcmtlbGV5IEZhc3QgRmlsZXN5c3RlbQ0Kb3B0aW9ucwkJ TVNET1NGUwkJCSNNU0RPUyBGaWxlc3lzdGVtDQpvcHRpb25zCQkiQ0Q5NjYw IgkJI0lTTyA5NjYwIEZpbGVzeXN0ZW0NCm9wdGlvbnMJCVBST0NGUwkJCSNQ cm9jZXNzIGZpbGVzeXN0ZW0NCm9wdGlvbnMJCU1GUw0Kb3B0aW9ucwkJIkNP TVBBVF80MyIJCSNDb21wYXRpYmxlIHdpdGggQlNEIDQuMyBbS0VFUCBUSElT IV0NCm9wdGlvbnMJCVVDT05TT0xFCQkjQWxsb3cgdXNlcnMgdG8gZ3JhYiB0 aGUgY29uc29sZQ0Kb3B0aW9ucwkJVVNFUkNPTkZJRwkJI2Jvb3QgLWMgZWRp dG9yDQpvcHRpb25zCQlWSVNVQUxfVVNFUkNPTkZJRwkjdmlzdWFsIGJvb3Qg LWMgZWRpdG9yDQojb3B0aW9ucwkJQ0xLX1VTRV9UU0NfQ0FMSUJSQVRJT04N CiNvcHRpb25zCQlVU0VSX0xEVA0Kb3B0aW9ucwkJU1lTVlNITQ0Kb3B0aW9u cwkJU1lTVlNFTQ0Kb3B0aW9ucwkJU1lTVk1TRw0Kb3B0aW9ucwkJS1RSQUNF DQpvcHRpb25zCQlEREINCm9wdGlvbnMJCSJBVVRPX0VPSV8xIg0Kb3B0aW9u cwkJIkFVVE9fRU9JXzIiDQpvcHRpb25zCQkiVk04NiINCm9wdGlvbnMJCVNP RlRVUERBVEVTDQoNCmNvbmZpZwkJa2VybmVsCXJvb3Qgb24gd2QwICNzd2Fw IG9uIGdlbmVyaWMNCg0KY29udHJvbGxlcglpc2EwIGF0IG5leHVzPw0KY29u dHJvbGxlcglwY2kwIGF0IG5leHVzPw0KDQpjb250cm9sbGVyCWZkYzAJYXQg aXNhPyBwb3J0ICJJT19GRDEiIGJpbyBpcnEgNiBkcnEgMg0KZGlzawkJZmQw CWF0IGZkYzAgZHJpdmUgMA0KDQojY29udHJvbGxlcgl3ZGMwCWF0IGlzYT8g cG9ydCAiSU9fV0QxIiBiaW8gaXJxIDE0IGZsYWdzIDB4YTBmZmEwZmYNCiNk aXNrCQl3ZDAJYXQgd2RjMCBkcml2ZSAwDQojZGlzawkJd2QxCWF0IHdkYzAg ZHJpdmUgMQ0KDQojY29udHJvbGxlcgl3ZGMxCWF0IGlzYT8gcG9ydCAiSU9f V0QyIiBiaW8gaXJxIDE1IGZsYWdzIDB4ODBmZjgwZmYNCiNkaXNrCQl3ZDIJ YXQgd2RjMSBkcml2ZSAwDQojZGlzawkJd2QzCWF0IHdkYzEgZHJpdmUgMQ0K DQojZGV2aWNlCQl3Y2QwCSNJREUgQ0QtUk9NDQoNCmNvbnRyb2xsZXIgYXRh MA0KZGV2aWNlCQlhdGFkaXNrMA0KZGV2aWNlCQlhdGFwaWNkMA0KZGV2aWNl CQlhdGFwaWZkMA0KDQoNCiMgYXRrYmRjMCBjb250cm9sbHMgYm90aCB0aGUg a2V5Ym9hcmQgYW5kIHRoZSBQUy8yIG1vdXNlDQpjb250cm9sbGVyCWF0a2Jk YzAJYXQgaXNhPyBwb3J0IElPX0tCRCB0dHkNCmRldmljZQkJYXRrYmQwCWF0 IGF0a2JkYz8gdHR5IGlycSAxDQpkZXZpY2UJCXBzbTAJYXQgYXRrYmRjPyB0 dHkgaXJxIDEyDQoNCmRldmljZQkJdmdhMAlhdCBpc2E/IHBvcnQgPyBjb25m bGljdHMNCg0KIyBzcGxhc2ggc2NyZWVuL3NjcmVlbiBzYXZlcg0KcHNldWRv LWRldmljZQlzcGxhc2gNCg0KIyBzeXNjb25zIGlzIHRoZSBkZWZhdWx0IGNv bnNvbGUgZHJpdmVyLCByZXNlbWJsaW5nIGFuIFNDTyBjb25zb2xlDQpkZXZp Y2UJCXNjMAlhdCBpc2E/IHR0eQ0KZGV2aWNlCQlucHgwCWF0IG5leHVzPyBw b3J0ICJJT19OUFgiIGlycSAxMw0KDQpkZXZpY2UJCXNpbzAJYXQgaXNhPyBw b3J0ICJJT19DT00xIiB0dHkgaXJxIDQNCmRldmljZQkJc2lvMQlhdCBpc2E/ IHBvcnQgIklPX0NPTTIiIHR0eSBpcnEgMw0KZGV2aWNlCQlzaW8yCWF0IGlz YT8gcG9ydCAiSU9fQ09NMyIgdHR5IGlycSA5DQoNCmNvbnRyb2xsZXIgcG5w MA0KY29udHJvbGxlciBzbmQwDQpkZXZpY2UgZ3VzMCBhdCBpc2E/DQojZGV2 aWNlIHBjbTAgYXQgaXNhPyBwb3J0ID8gdHR5IGlycSAxMCBkcnEgMSBmbGFn cyAweDAgdmVjdG9yIHBjbWludHINCg0KY29udHJvbGxlciBwcGJ1czANCmRl dmljZSBscHQwIGF0IHBwYnVzPw0KZGV2aWNlIHBwaTAgYXQgcHBidXM/DQoN CmNvbnRyb2xsZXIgcHBjMCBhdCBpc2E/IHBvcnQgPyBpcnEgNw0KDQpkZXZp Y2UgZWQwIGF0IGlzYT8gcG9ydCAweDI4MCBpcnEgMTAgdmVjdG9yIGVkaW50 cg0KDQpwc2V1ZG8tZGV2aWNlCWxvb3ANCnBzZXVkby1kZXZpY2UJZXRoZXIN CnBzZXVkby1kZXZpY2UJYnBmaWx0ZXIJNA0KcHNldWRvLWRldmljZQlzcGVh a2VyDQpwc2V1ZG8tZGV2aWNlCXZuCTQNCnBzZXVkby1kZXZpY2UJc25wCTIN CnBzZXVkby1kZXZpY2UJdHVuCTQNCnBzZXVkby1kZXZpY2UJcHR5CTE2DQpw c2V1ZG8tZGV2aWNlCWd6aXAJCSMgRXhlYyBnemlwcGVkIGEub3V0J3MNCg== --0-1217266395-924966031=:25684-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 8:10: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 1456714F0B for ; Sat, 24 Apr 1999 08:09:57 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA84737; Sat, 24 Apr 1999 11:09:51 -0400 (EDT) Date: Sat, 24 Apr 1999 11:09:51 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Stephane Legrand Cc: Andrzej Bialecki , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? In-Reply-To: <199904241337.PAA01205@sequoia.mondomaineamoi.megalo> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Apr 1999, Stephane Legrand wrote: > Andrzej Bialecki writes: > > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > > > > Hi, > > > > > > i was wondering if the limitations that are supposed to be enforced via > > > the login.conf mechanism do really work... > > > > > > In particular, i have tried (on 3.1 something, but don't think that > > > current is much different in this respect) to enforce the daily etc. > > > login times but the system seems to ignore them. > > > > > > I think /etc/login.conf is properly parsed, because if i assign a user > > > to a class that is not defined in login.conf i get complaints, but > > > other than that i am unable to limit login time... > > > > > > Any hints ? > > > > That's also my impression. I glipmsed the whole source tree and I couldn't > > find any place where the limits are enforced. BTW. what entity should > > enforce login time limits? Kernel? Some user-space daemon? > > > > To report a login.conf success, i've used on a 2.2.8 system the > "cputime" ressource limit. I set it to zero and that worked very > well. So may be only some limits are implemented ? > If you'd like to see where the ones which are implemented are implemented, look at the process context-switch routines in the kernel. Not having checked, but guessing, I bet login reads login.conf as a db and uses the values to set rlimits, which is where they would be set. > Stephane Legrand. > > -- > Stephane.Legrand@wanadoo.fr : http://perso.wanadoo.fr/stephane.legrand/ > FreeBSD Francophone : http://www.freebsd-fr.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 8:12: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 9826714F0B; Sat, 24 Apr 1999 08:11:59 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id LAA84820; Sat, 24 Apr 1999 11:11:59 -0400 (EDT) Date: Sat, 24 Apr 1999 11:11:58 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Andrzej Bialecki Cc: sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: New ATA hangs my machine In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Apr 1999, Andrzej Bialecki wrote: > Hi, > > I'd love to play with the new IDE drivers, especially that I got an LS-120 Note that wfd is here for those drives.. I'm currently in a sticky situation: wd: works with all drives, does no manner of DMA on my 6.4G Medalist ATA: works with all but LS-120 (for me), does UDMA2 great on my Medalist, but has no dump routine > drive, but... I can't mount my filesystems with it. I'm using today's > sources (kernel config file attached), and it fsck's them just ok, and > then just hangs. Keyboard works, though. If I boot with -v, it reports: > > ad0: invalid primary partition table: no magic > > and of course it just sits there... > > The issue is, however, that old kernel booted just fine. I attached > relevant parts of dmesg with old drivers, and disklabel and fdisk output. > > Any clues? LBA? > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 8:20:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 1E14D14F74 for ; Sat, 24 Apr 1999 08:20:32 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id KAA07558; Sat, 24 Apr 1999 10:16:44 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Sat, 24 Apr 1999 10:16:44 +0000 (GMT) From: eagle To: Brian Feldman Cc: Stephane Legrand , Andrzej Bialecki , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Apr 1999, Brian Feldman wrote: > On Sat, 24 Apr 1999, Stephane Legrand wrote: > > > Andrzej Bialecki writes: > > > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > > > > > > Hi, > > > > > > > > i was wondering if the limitations that are supposed to be enforced via > > > > the login.conf mechanism do really work... > > > > > > > > In particular, i have tried (on 3.1 something, but don't think that > > > > current is much different in this respect) to enforce the daily etc. > > > > login times but the system seems to ignore them. > > > > > > > > I think /etc/login.conf is properly parsed, because if i assign a user > > > > to a class that is not defined in login.conf i get complaints, but > > > > other than that i am unable to limit login time... > > > > > > > > Any hints ? > > > > > > That's also my impression. I glipmsed the whole source tree and I couldn't > > > find any place where the limits are enforced. BTW. what entity should > > > enforce login time limits? Kernel? Some user-space daemon? > > > > > > > To report a login.conf success, i've used on a 2.2.8 system the > > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? > > > > If you'd like to see where the ones which are implemented are implemented, look at the process > context-switch routines in the kernel. Not having checked, but guessing, I bet login reads > login.conf as a db and uses the values to set rlimits, which is where they would be set. > > > Stephane Legrand. > > > > -- > > Stephane.Legrand@wanadoo.fr : http://perso.wanadoo.fr/stephane.legrand/ > > FreeBSD Francophone : http://www.freebsd-fr.org/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > Some of it works, and some doesn't some is implemented in login, other parts are in init.. rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 8:37:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (Postfix) with ESMTP id 2C4AC14F74 for ; Sat, 24 Apr 1999 08:37:12 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id AAA00882; Sun, 25 Apr 1999 00:36:53 +0900 (JST) To: dfr@nlsystems.com, peter@netplex.com.au Cc: current@freebsd.org Subject: Re: singed short to unsigned long conversion problem in isa.c From: KATO Takenori In-Reply-To: Your message of "Sat, 24 Apr 1999 15:30:26 +0100 (BST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990425003653V.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sun, 25 Apr 1999 00:36:53 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 18 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > It needs to be signed since the value -1 is used to indicate no port > resources. Perhaps it would be better to change it to 'int' instead of > 'u_short'. Oops, I didn't realize this case. The assumption that an I/O port address is lower than 0x8000 is OK for IBM-PC's ISA-bus, but PC98 can use hiher addresses for ISA-bus like bus. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 3.1: Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 2.2.8: Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 8:43:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 2C64614F74 for ; Sat, 24 Apr 1999 08:43:21 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA02593; Sat, 24 Apr 1999 15:29:34 +0200 From: Luigi Rizzo Message-Id: <199904241329.PAA02593@labinfo.iet.unipi.it> Subject: Re: does login.conf limitations work ? To: abial@webgiro.com (Andrzej Bialecki) Date: Sat, 24 Apr 1999 15:29:33 +0200 (MET DST) Cc: Stephane.Legrand@wanadoo.fr, current@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Apr 24, 99 04:39:01 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 748 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? > > You're right, this part works. However, I was talking about login time > (which is how long can user be logged on to the system), which isn't > checked anywhere. too bad... this is something isp's would love to have! cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 8:52:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 223E714CB9 for ; Sat, 24 Apr 1999 08:52:27 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id LAA02338 for ; Sat, 24 Apr 1999 11:52:27 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Sat, 24 Apr 1999 11:52:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: current@FreeBSD.org Subject: Re: singed short to unsigned long conversion problem in isa.c In-Reply-To: <19990424210206R.kato@gneiss.eps.nagoya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Singed shorts are often the result of sitting on a stove during the summer. We also recently saw a "hanging root device to..." in a boot on one of our machines. :-) Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 9: 8:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 23F0515368 for ; Sat, 24 Apr 1999 09:08:17 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA17473; Sun, 25 Apr 1999 01:07:57 +0900 (JST) Message-ID: <3721E5EA.672014EB@newsguy.com> Date: Sun, 25 Apr 1999 00:40:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Andrzej Bialecki Cc: Stephane Legrand , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > On Sat, 24 Apr 1999, Stephane Legrand wrote: > > > > That's also my impression. I glipmsed the whole source tree and I couldn't > > > find any place where the limits are enforced. BTW. what entity should > > > enforce login time limits? Kernel? Some user-space daemon? > > > > To report a login.conf success, i've used on a 2.2.8 system the > > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? > > You're right, this part works. However, I was talking about login time > (which is how long can user be logged on to the system), which isn't > checked anywhere. It isn't. Login.conf, just like, now, pam, is one of those cases of a wonderful clean, orthogonal solution which is only partially implemented. I personally think login time should be enforced through tty revocation. The main problem is that no solution exists which will do the right thing regarding processes to kill for all processes. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 10:56:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2F99C15168 for ; Sat, 24 Apr 1999 10:56:24 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA29767; Sat, 24 Apr 1999 19:02:16 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 24 Apr 1999 19:02:15 +0100 (BST) From: Doug Rabson To: KATO Takenori Cc: peter@netplex.com.au, current@freebsd.org Subject: Re: singed short to unsigned long conversion problem in isa.c In-Reply-To: <19990425003653V.kato@gneiss.eps.nagoya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Apr 1999, KATO Takenori wrote: > Doug Rabson wrote: > > > It needs to be signed since the value -1 is used to indicate no port > > resources. Perhaps it would be better to change it to 'int' instead of > > 'u_short'. > > Oops, I didn't realize this case. > > The assumption that an I/O port address is lower than 0x8000 is OK for > IBM-PC's ISA-bus, but PC98 can use hiher addresses for ISA-bus like > bus. I understand. I think the best thing is to store the port address as an int. I don't think there is a need to fork the file into a pc98 version. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 12: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles555.castles.com [208.214.165.119]) by hub.freebsd.org (Postfix) with ESMTP id 1BBC114BE0 for ; Sat, 24 Apr 1999 12:02:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA10270; Sat, 24 Apr 1999 11:53:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904241853.LAA10270@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Watson Cc: current@FreeBSD.org Subject: Re: singed short to unsigned long conversion problem in isa.c In-reply-to: Your message of "Sat, 24 Apr 1999 11:52:26 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Apr 1999 11:53:36 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Singed shorts are often the result of sitting on a stove during the > summer. > > We also recently saw a "hanging root device to..." in a boot on one of our > machines. You'll see the 'c' up above all of the SCSI device probe messages. Not sure how we go about making that one tidy. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 12: 9: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 2646E14BE0 for ; Sat, 24 Apr 1999 12:09:02 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id D3A791F58 for ; Sun, 25 Apr 1999 03:08:59 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Heads up! config(8) changes.. Date: Sun, 25 Apr 1999 03:08:59 +0800 From: Peter Wemm Message-Id: <19990424190901.D3A791F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This shouldn't cause much in the way of trouble, but it will complain about old lint in your config files. That includes 'net/tty/bio/cam' mask indicators, and 'vector xxxintr' as well as some of the wierder workarounds for the poor 'options' parsing. So: things like: device sio1 at isa? tty port "IO_COM2" tty irq 3 become: device sio1 at isa? port IO_COM2 irq3 options "VM86" -> options VM86 options "_KPOSIX_FOO=12345L" -> options _KPOSIX_FOO=12345L etc. These are warnings about things that have been silently ignored for a while, or I've just (hopefully) fixed. However, I don't know lex/yacc too well, so I could well have stuffed something up. If there isn't too much trouble (ha ha! I should know better than to touch config), I'll commit a set of cleaned up GENERIC / LINT files. You do not need to build a new config(8), the version numbers have not been bumped (and don't need to). Cheers, -Peter ------- Forwarded Message peter 1999/04/24 11:59:20 PDT Modified files: usr.sbin/config config.h config.y lang.l main.c mkioconf.c mkmakefile.c mkoptions.c mkswapconf.c Log: More cleanups, tweaks and features. - make this work: options FOO123=456 *without quotes* - grumble (but accept) vector xxxintr, and tty/net/bio/cam flags. - complain if a device is specified twice (eg: 2 x psm0) - don't require quotes around: port IO_COM2 - recognize negative numbers. (ie: options CAM_DEBUG_UNIT=-1) - GC some more unused stuff (we don't have composite disks from config(8)). - various other nits (snprintf paranoia etc) Revision Changes Path 1.24 +2 -12 src/usr.sbin/config/config.h 1.30 +58 -181 src/usr.sbin/config/config.y 1.19 +7 -7 src/usr.sbin/config/lang.l 1.32 +2 -2 src/usr.sbin/config/main.c 1.54 +4 -4 src/usr.sbin/config/mkioconf.c 1.41 +4 -4 src/usr.sbin/config/mkmakefile.c 1.11 +2 -2 src/usr.sbin/config/mkoptions.c 1.19 +6 -6 src/usr.sbin/config/mkswapconf.c ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 12:37:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw1adm.rcsntx.swbell.net (mail-gw1.rcsntx.swbell.net [151.164.30.51]) by hub.freebsd.org (Postfix) with ESMTP id EFD9B14C89 for ; Sat, 24 Apr 1999 12:37:35 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-12-81.hstntx.swbell.net [207.193.12.81]) by mail-gw1adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id OAA05080; Sat, 24 Apr 1999 14:37:26 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id OAA14117; Sat, 24 Apr 1999 14:38:04 -0500 (CDT) (envelope-from chris) Date: Sat, 24 Apr 1999 14:38:02 -0500 From: Chris Costello To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: Heads up! config(8) changes.. Message-ID: <19990424143801.B11941@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990424190901.D3A791F58@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="QKdGvSO+nmPlgiQ/"; micalg=pgp-md5; protocol="application/pgp-signature" User-Agent: Mutt/0.96.1i In-Reply-To: <19990424190901.D3A791F58@spinner.netplex.com.au>; from Peter Wemm on Sun, Apr 25, 1999 at 03:08:59AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --QKdGvSO+nmPlgiQ/ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Sat, Apr 24, 1999, Peter Wemm wrote: > This shouldn't cause much in the way of trouble, but it will complain > about old lint in your config files. That includes 'net/tty/bio/cam' > mask indicators, and 'vector xxxintr' as well as some of the wierder > workarounds for the poor 'options' parsing. >=20 > So: things like: > device sio1 at isa? tty port "IO_COM2" tty irq 3 > become: > device sio1 at isa? port IO_COM2 irq3 >=20 > options "VM86" -> options VM86 > options "_KPOSIX_FOO=3D12345L" -> options _KPOSIX_FOO=3D12345L > etc. Excellent! Why wasn't this done before? --=20 Chris Costello And on the seventh day, He exited from append mode. --QKdGvSO+nmPlgiQ/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNyIdmbfyXY/Dmk2NAQFB6gL/XCFzF9iPjlNJwvbjJx0jWAR7pBCRwaMQ mdrgUvlegtbnALGXiZNFMgIp1IcPZvv4W/ivyKP3+m4M1MXRmYrdAoERyV1Fdtst pLlsM2ICazh6moDHVnV0jWqA3DPq2z3J =Gw0U -----END PGP SIGNATURE----- --QKdGvSO+nmPlgiQ/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 12:40:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 64E5314E4E for ; Sat, 24 Apr 1999 12:40:26 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id A6C111F58; Sun, 25 Apr 1999 03:40:21 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: chris@calldei.com Cc: current@FreeBSD.ORG Subject: Re: Heads up! config(8) changes.. In-reply-to: Your message of "Sat, 24 Apr 1999 14:38:02 EST." <19990424143801.B11941@holly.dyndns.org> Date: Sun, 25 Apr 1999 03:40:21 +0800 From: Peter Wemm Message-Id: <19990424194023.A6C111F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > On Sat, Apr 24, 1999, Peter Wemm wrote: > > This shouldn't cause much in the way of trouble, but it will complain > > about old lint in your config files. That includes 'net/tty/bio/cam' > > mask indicators, and 'vector xxxintr' as well as some of the wierder > > workarounds for the poor 'options' parsing. > > > > So: things like: > > device sio1 at isa? tty port "IO_COM2" tty irq 3 > > become: > > device sio1 at isa? port IO_COM2 irq3 > > > > options "VM86" -> options VM86 > > options "_KPOSIX_FOO=12345L" -> options _KPOSIX_FOO=12345L > > etc. > > Excellent! Why wasn't this done before? Probably because the code was a nightmare.. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 15:53: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 58B94152DF for ; Sat, 24 Apr 1999 15:52:54 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id PAA29147; Sat, 24 Apr 1999 15:52:53 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA06937; Sat, 24 Apr 1999 15:52:53 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 24 Apr 1999 15:52:53 -0700 (PDT) Message-Id: <199904242252.PAA06937@vashon.polstra.com> To: abial@webgiro.com Subject: Re: does login.conf limitations work ? In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Andrzej Bialecki wrote: > On Fri, 23 Apr 1999, Luigi Rizzo wrote: > > That's also my impression. I glipmsed the whole source tree and I couldn't > find any place where the limits are enforced. BTW. what entity should > enforce login time limits? Kernel? Some user-space daemon? Pre-PAM, it would have been done in login itself, I believe. That's where other things such as password expiration are checked. With PAM, it should go into the "account management" modules. Somebody has submitted such a module to me, and they're currently making some post-review revisions I requested. After that I will commit it. Note, it doesn't handle login time restrictions either -- it does only what login does now. However, once the module exists, we'll at least have a place to put the changes into. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 16:22:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-185-206.res.iastate.edu (friley-185-206.res.iastate.edu [129.186.185.206]) by hub.freebsd.org (Postfix) with ESMTP id D17FA14D61 for ; Sat, 24 Apr 1999 16:22:19 -0700 (PDT) (envelope-from cc@137.org) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by friley-185-206.res.iastate.edu (Postfix) with ESMTP id D9FAC38; Sat, 24 Apr 1999 17:22:18 -0600 (CST) Received: from friley-185-205.res.iastate.edu (localhost [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 42DA0109; Sat, 24 Apr 1999 18:22:18 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Jake Burkholder Cc: current@FreeBSD.ORG Subject: Re: new-bus, pcm, and matcd (was Re: new-bus breaks both sound drivers) In-reply-to: Your message of "Fri, 23 Apr 1999 17:14:54 PDT." <199904240014.RAA18144@io.dyn.ez-ip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Apr 1999 18:22:18 -0500 From: Chris Csanady Message-Id: <19990424232218.42DA0109@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >mp3s aren't playing quite right with x11amp though, little >> >skips here and there, they work fine with the old kernel. >> >mpg123 seems fine, as does the sound in FXTV. >> >I'll try making the world again. >> >> Was there ever any resolution/further inspection of this? > >Not as far I know; its still happening here. cmp3 (mpg123) also skips >in the same way, but its much less noticeable. >I've been updating and recompiling almost daily. Ugh. This also has the same effect on captured audio using fxtv. It seems that everything audio related is messed up now. (Or perhaps real time?) I will try to find the exact day where things broke I guses. I don't have much time right now though.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 16:24:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 859F414D61 for ; Sat, 24 Apr 1999 16:24:19 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id TAA02445 for current@freebsd.org; Sat, 24 Apr 1999 19:23:39 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904242323.TAA02445@kot.ne.mediaone.net> Subject: Re: does login.conf limitations work ? In-Reply-To: <199904241329.PAA02593@labinfo.iet.unipi.it> from Luigi Rizzo at "Apr 24, 1999 03:29:33 pm" To: current@freebsd.org Date: Sat, 24 Apr 1999 19:23:39 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" > "cputime" ressource limit. I set it to zero and that worked very => > well. So may be only some limits are implemented ? => => You're right, this part works. However, I was talking about login time => (which is how long can user be logged on to the system), which isn't => checked anywhere. = =too bad... this is something isp's would love to have! idled from ports? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 16:27:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 97BBB14D61 for ; Sat, 24 Apr 1999 16:27:37 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id TAA02475 for current@freebsd.org; Sat, 24 Apr 1999 19:26:57 -0400 (EDT) From: Mikhail Teterin Message-Id: <199904242326.TAA02475@kot.ne.mediaone.net> Subject: Re: singed short to unsigned long conversion problem in isa.c In-Reply-To: from Doug Rabson at "Apr 24, 1999 03:30:26 pm" To: current@freebsd.org Date: Sat, 24 Apr 1999 19:26:56 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" If this should not be in sys/i386/isa, I will copy this file into => sys/pc98/pc98. Comment please. = =It needs to be signed since the value -1 is used to indicate no port =resources. Perhaps it would be better to change it to 'int' instead of ='u_short'. Uff, waisting additional 24 physical bits for one bit of information... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 18:52:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 4E81314D53 for ; Sat, 24 Apr 1999 18:52:39 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id VAA00295 for ; Sat, 24 Apr 1999 21:55:30 -0400 (EDT) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Sat, 24 Apr 1999 21:55:30 -0400 (EDT) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: sound still broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just wondering when and if sound was going to be fixed anytime soon, I'm still getting the same error as the last time I mailed. I just cvsupped about an hour ago, so I'm pretty up to date. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 24 23:23:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E98A614DC1 for ; Sat, 24 Apr 1999 23:23:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA33729; Sat, 24 Apr 1999 23:23:49 -0700 (PDT) (envelope-from dillon) Date: Sat, 24 Apr 1999 23:23:49 -0700 (PDT) From: Matthew Dillon Message-Id: <199904250623.XAA33729@apollo.backplane.com> To: Doug Rabson Cc: KATO Takenori , peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: singed short to unsigned long conversion problem in isa.c References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> The assumption that an I/O port address is lower than 0x8000 is OK for :> IBM-PC's ISA-bus, but PC98 can use hiher addresses for ISA-bus like :> bus. : :I understand. I think the best thing is to store the port address as an :int. I don't think there is a need to fork the file into a pc98 version. : :-- :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 I would recommend making it an unsigned short, and representing the -1 case with a '#define BAD_PORT ((unsigned short)-1)'. All representations and tests for this special case would be required to use the #define rather then a constant. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 1:40:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 5C76514F3A for ; Sun, 25 Apr 1999 01:40:11 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id DAA26461 for ; Sun, 25 Apr 1999 03:57:40 -0500 (EST) Date: Sun, 25 Apr 1999 03:57:36 -0500 (EST) From: Alfred Perlstein To: current@freebsd.org Subject: quotas are broken? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone using quotas on -current or -stable on SMP machines and has it working? Several of my friends are experiancing weird stuff with them enabled, either total lockups, or slowdowns so bad that the machine becomes unsuable quite quickly. The problems are supposedly quite easy to trigger, especially on SMP boxes. This is preventing deployment of FreeBSD in several critical areas for a number of my friends in the ISP business. any help would be appreciated, and i apologize for not having more information available about what triggers it, but again it's supposedly very easy to trigger. http://www.freebsd.org/cgi/query-pr.cgi?pr=11004 thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 2:11:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id E85B414C85 for ; Sun, 25 Apr 1999 02:11:45 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 7091D164 for ; Sun, 25 Apr 1999 09:11:43 +0000 (GMT) Date: Sun, 25 Apr 1999 13:11:43 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.org Subject: night make buildworld failed... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Night make buildworld failed: ===> sys/modules/fxp @ -> /usr/src/sys machine -> /usr/src/sys/i386/include echo "#define NFXP 1" > fxp.h echo "#define NBPFILTER 0" > bpfilter.h touch opt_bdg.h perl /usr/src/sys/modules/fxp/../../kern/makedevops.pl -h /usr/src/sys/modules/fxp/../../kern/device_if.m perl: not found *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Rgdz, Osokin Sergey aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 2:41:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 3190714D53 for ; Sun, 25 Apr 1999 02:41:25 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 22631 invoked by uid 1008); 25 Apr 1999 09:41:22 -0000 Message-ID: <19990425094122.22629.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: freebsd-current@freebsd.org Subject: procfs-rlimit patch Date: Sun, 25 Apr 1999 17:41:22 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the delay on this one. http://www.freebsd.org/~adrian/procfs-rlimit/ Thats a patch against -current as of a few days ago, and a README. Any suggestions / improvements are welcome. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 3:21:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id D7BBC14BDC; Sun, 25 Apr 1999 03:21:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA08742; Sun, 25 Apr 1999 12:21:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id MAA11598; Sun, 25 Apr 1999 12:21:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: adrian@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: procfs-rlimit patch In-reply-to: Your message of "Sun, 25 Apr 1999 17:41:22 +0800." <19990425094122.22629.qmail@ewok.creative.net.au> Date: Sun, 25 Apr 1999 12:21:03 +0200 Message-ID: <11596.925035663@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990425094122.22629.qmail@ewok.creative.net.au>, adrian@FreeBSD.OR G writes: > >Sorry for the delay on this one. > >http://www.freebsd.org/~adrian/procfs-rlimit/ > >Thats a patch against -current as of a few days ago, >and a README. > >Any suggestions / improvements are welcome. I think we need the names in there, something like: cputime -1 -1 filesize -1 -1 ... Mode 0444 is fine with me. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 3:55:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 54CEF14E08 for ; Sun, 25 Apr 1999 03:55:53 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA06632; Sun, 25 Apr 1999 20:55:51 +1000 Date: Sun, 25 Apr 1999 20:55:51 +1000 From: Bruce Evans Message-Id: <199904251055.UAA06632@godzilla.zeta.org.au> To: current@FreeBSD.ORG, osa@etrust.ru Subject: Re: night make buildworld failed... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Night make buildworld failed: > >===> sys/modules/fxp >@ -> /usr/src/sys >machine -> /usr/src/sys/i386/include >echo "#define NFXP 1" > fxp.h >echo "#define NBPFILTER 0" > bpfilter.h >touch opt_bdg.h >perl /usr/src/sys/modules/fxp/../../kern/makedevops.pl -h /usr/src/sys/modules/fxp/../../kern/device_if.m >perl: not found >*** Error code 1 This is probably caused by using the NOPERL option. Don't use it. It shouldn't exist, since perl is not optional. It is used by `make world' for at least building fxp and updating the man page indexes. The latter uses the wrong version of perl (/usr/bin/perl) so it fails when DESTDIR is set and perl is not already installed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 4:43:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 7AC9914D03 for ; Sun, 25 Apr 1999 04:43:37 -0700 (PDT) (envelope-from gjvc@extremis.demon.co.uk) Received: from [194.222.242.30] (helo=extremis.demon.co.uk) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 10bNJl-000FJo-0B for freebsd-current@freebsd.org; Sun, 25 Apr 1999 11:43:31 +0000 Received: (from gjvc@localhost) by extremis.demon.co.uk (8.9.3/8.9.1) id MAA00992 for freebsd-current@freebsd.org; Sun, 25 Apr 1999 12:43:14 GMT (envelope-from gjvc) Date: Sun, 25 Apr 1999 12:43:14 +0000 From: "[gjvc]" To: freebsd-current@freebsd.org Subject: VESA screenmodes Message-ID: <19990425124314.A976@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello -CURRENTers, I CVSup every night, and a couple of days ago my 'vidcontrol VESA_132x60' line in my /etc/rc.local stopped working. The VESA-related lines in my config file are: #### VIDEO CONTROLLER device vga0 at isa? port? conflicts options VGA_ALT_SEQACCESS # options "VESA" # VESA BIOS support options "VM86" # Required by the vga0 driver What's going on? -- [gjvc] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 9:49:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 04E5714C2E for ; Sun, 25 Apr 1999 09:49:28 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 23276 invoked by uid 1008); 25 Apr 1999 16:49:02 -0000 Message-ID: <19990425164902.23274.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Poul-Henning Kamp Cc: freebsd-current@freebsd.org Subject: Re: procfs-rlimit patch In-reply-to: Your message of "Sun, 25 Apr 1999 12:21:03 +0200." <11596.925035663@critter.freebsd.dk> Date: Mon, 26 Apr 1999 00:49:02 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: >In message <19990425094122.22629.qmail@ewok.creative.net.au>, adrian@FreeBSD.OR >G writes: >> >>Sorry for the delay on this one. >> >>http://www.freebsd.org/~adrian/procfs-rlimit/ >> >>Thats a patch against -current as of a few days ago, >>and a README. >> >>Any suggestions / improvements are welcome. > >I think we need the names in there, something like: > > cputime -1 -1 > filesize -1 -1 > ... > >Mode 0444 is fine with me. > Which means that we need an array in sys/resource.h containing the names - something I wanted to double check before I did it. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 10: 7:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id DE10814BDD; Sun, 25 Apr 1999 10:07:18 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id TAA10452; Sun, 25 Apr 1999 19:07:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id TAA12607; Sun, 25 Apr 1999 19:07:13 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: adrian@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: procfs-rlimit patch In-reply-to: Your message of "Mon, 26 Apr 1999 00:49:02 +0800." <19990425164902.23274.qmail@ewok.creative.net.au> Date: Sun, 25 Apr 1999 19:07:12 +0200 Message-ID: <12605.925060032@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990425164902.23274.qmail@ewok.creative.net.au>, adrian@FreeBSD.OR G writes: >Poul-Henning Kamp writes: >>In message <19990425094122.22629.qmail@ewok.creative.net.au>, adrian@FreeBSD.OR >>G writes: >>> >>>Sorry for the delay on this one. >>> >>>http://www.freebsd.org/~adrian/procfs-rlimit/ >>> >>>Thats a patch against -current as of a few days ago, >>>and a README. >>> >>>Any suggestions / improvements are welcome. >> >>I think we need the names in there, something like: >> >> cputime -1 -1 >> filesize -1 -1 >> ... >> >>Mode 0444 is fine with me. >> > >Which means that we need an array in sys/resource.h containing the >names - something I wanted to double check before I did it. And we should change all other users to use it too :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 10:35:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from io.dyn.ez-ip.net (h24-66-174-118.xx.wave.shaw.ca [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id 0318614C0F for ; Sun, 25 Apr 1999 10:35:08 -0700 (PDT) (envelope-from jake@io.dyn.ez-ip.net) Received: from io.dyn.ez-ip.net (jake@localhost [127.0.0.1]) by io.dyn.ez-ip.net (8.9.3/8.9.2) with ESMTP id KAA00614 for ; Sun, 25 Apr 1999 10:16:09 -0700 (PDT) (envelope-from jake@io.dyn.ez-ip.net) Message-Id: <199904251716.KAA00614@io.dyn.ez-ip.net> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: config nit Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Apr 1999 10:16:09 -0700 From: Jake Burkholder Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just noticed that after all the dequote stuff went into config (great work!) options NO_F00F_HACK still needs quotes. Its interpreted as NO_F0F_HACK without them; to be expected I guess. This should probably be reflected in LINT. Thanks, Jake -- we are but packets in the internet of life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 10:55:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id CE6E2155E4 for ; Sun, 25 Apr 1999 10:55:03 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA31820; Mon, 26 Apr 1999 03:54:58 +1000 Date: Mon, 26 Apr 1999 03:54:58 +1000 From: Bruce Evans Message-Id: <199904251754.DAA31820@godzilla.zeta.org.au> To: current@FreeBSD.ORG, jake@checker.org Subject: Re: config nit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi, I just noticed that after all the dequote stuff went into config >(great work!) options NO_F00F_HACK still needs quotes. Its interpreted >as NO_F0F_HACK without them; to be expected I guess. It also translates unsigned hex to signed decimal, so N0xF00F_HACK becomes N61455_HACK, and it prints the translated version in the warning message about unknown options. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 11: 1:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 070EB150F8 for ; Sun, 25 Apr 1999 11:01:09 -0700 (PDT) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (mars.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.8.8/8.8.7/8.7.7) with ESMTP id UAA848444 for ; Sun, 25 Apr 1999 20:01:08 +0200 (CST) Received: from vodix.cs.uni-sb.de (maxtnt-167.telip.uni-sb.de [134.96.71.38]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id UAA01276 for ; Sun, 25 Apr 1999 20:01:07 +0200 (CST) Received: from Vodix.CS.Uni-SB.de (localhost.net.local [127.0.0.1]) by vodix.cs.uni-sb.de (8.9.3/8.9.3) with ESMTP id UAA44385 for ; Sun, 25 Apr 1999 20:00:54 +0200 (CEST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199904251800.UAA44385@vodix.cs.uni-sb.de> Date: Sun, 25 Apr 1999 20:00:53 +0200 (CEST) From: A.Leidinger@Wurzelausix.CS.Uni-SB.de Subject: config & NO_F00F_HACK To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, # ident LINT LINT: $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ with: option NO_F00F_HACK # config WORK WORK:15: unknown option "NO_F0F_HACK" with: option "NO_F00F_HACK" # config WORK Don't forget to do a ``make depend'' Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 11:29:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (Postfix) with ESMTP id 6E84D14EFF; Sun, 25 Apr 1999 11:29:23 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.webwizard.net.mx (8.9.3/8.9.3) with ESMTP id NAA49164; Sun, 25 Apr 1999 13:29:16 -0500 (CDT) (envelope-from eculp@MexComUSA.net) Message-ID: <37235EF6.A74D6974@MexComUSA.net> Date: Sun, 25 Apr 1999 11:29:11 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Cc: freebsd-mobile@FreeBSD.ORG Subject: Network problem with Laptop/Current. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I try to configure my D-Link de-660 pcmcia card with a kernel from sources from the last 5 days or so, I get the following: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 5 Card inserted, slot 2 Card inserted, slot 3 ed0: address 00:80:c8:8c:03:8d, type NE2000 (16 bit) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01ac150 stack pointer = 0x10:0xc60f0d58 frame pointer = 0x10:0xc60f0d60 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 = 424 (ifconfig) interrupt mask = net tty trap number = 12 panic: page fault syncing disks... 8 4 done Automatic reboot in 15 seconds - press a key on the console to abort With a kernel from April 20 everything works except my pcmcia Viking Modem which hasn't worked since last weekend. Is anyone else else having this problem? Could I be doing something wrong? Thanks, ed (This is a generic AMS K6-300 .) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 11:36:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 25A3514EFF; Sun, 25 Apr 1999 11:36:09 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA46007; Sun, 25 Apr 1999 20:35:49 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904251835.UAA46007@freebsd.dk> Subject: Re: Network problem with Laptop/Current. In-Reply-To: <37235EF6.A74D6974@MexComUSA.net> from Edwin Culp at "Apr 25, 1999 11:29:11 am" To: eculp@MexComUSA.net (Edwin Culp) Date: Sun, 25 Apr 1999 20:35:49 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Edwin Culp wrote: > When I try to configure my D-Link de-660 pcmcia card with a kernel from > sources from the last 5 days or so, I get the following: > > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) > pcic: controller irq 5 > Card inserted, slot 2 > Card inserted, slot 3 > ed0: address 00:80:c8:8c:03:8d, type NE2000 (16 bit) Try the patch I posted a couble of days ago, that does it for me... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 11:59:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (Postfix) with ESMTP id 9D98514EFF for ; Sun, 25 Apr 1999 11:59:24 -0700 (PDT) (envelope-from plm@smtp3.xs4all.nl) Received: from localhost. (dc2-isdn135.dial.xs4all.nl [194.109.148.135]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id UAA02478; Sun, 25 Apr 1999 20:59:23 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id UAA00299; Sun, 25 Apr 1999 20:59:22 +0200 (MET DST) (envelope-from plm) From: Peter Mutsaers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14115.26121.474045.508934@muon.xs4all.nl> Date: Sun, 25 Apr 1999 20:59:21 +0200 (MET DST) To: Warner Losh Cc: Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: suspend mode broken since one week ago In-Reply-To: <199904240528.XAA10300@harmony.village.org> References: <87so9r3x44.fsf@muon.xs4all.nl> <199904240528.XAA10300@harmony.village.org> X-Mailer: VM 6.65 under Emacs 20.3.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "WL" == Warner Losh writes: WL> In message <87so9r3x44.fsf@muon.xs4all.nl> Peter Mutsaers writes: WL> : Is this a bug that I should report through send-pr, is it already WL> : known as a bug or is this an intentional change in behaviour? WL> This is a known bug. I thought I kludged around it in apm.c in the WL> timeframe that you mentioned. Do you have WL> $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ WL> or newer? Today I did a cvsup which upgraded apm.c from 1.79 to 1.80. Now after a reboot when X starts, the screen gets garbled and crashes after a while. When I press the suspend button and resume from suspend, the system reboots. I don't know if apm.c is causing this (probably the screen corruption and crash has another cause). -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+------------------ Running FreeBSD-current UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 13:54:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-31.ppp.wenet.net [206.15.85.31]) by hub.freebsd.org (Postfix) with ESMTP id 22A9914D15 for ; Sun, 25 Apr 1999 13:54:46 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id NAA00615; Sun, 25 Apr 1999 13:54:30 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sun, 25 Apr 1999 13:54:30 -0700 (PDT) From: Alex Zepeda To: Chris Csanady Cc: Jake Burkholder , current@FreeBSD.ORG Subject: Re: new-bus, pcm, and matcd (was Re: new-bus breaks both sound drivers) In-Reply-To: <19990424232218.42DA0109@friley-185-205.res.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Apr 1999, Chris Csanady wrote: > Ugh. This also has the same effect on captured audio using fxtv. It seems > that everything audio related is messed up now. (Or perhaps real time?) > > I will try to find the exact day where things broke I guses. I don't have > much time right now though.. FWIW, I can still play audio CDs... perhaps its time to shake the dust off some CDs? ;) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 15:27: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw3adm.rcsntx.swbell.net (mail-gw3.rcsntx.swbell.net [151.164.30.53]) by hub.freebsd.org (Postfix) with ESMTP id B70AE14F25 for ; Sun, 25 Apr 1999 15:26:24 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-14-197.hstntx.swbell.net [207.193.14.197]) by mail-gw3adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id RAA06531; Sun, 25 Apr 1999 17:26:17 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA00649; Sun, 25 Apr 1999 17:27:04 -0500 (CDT) (envelope-from chris) Date: Sun, 25 Apr 1999 17:26:59 -0500 From: Chris Costello To: A.Leidinger@Wurzelausix.CS.Uni-SB.de Cc: current@FreeBSD.ORG Subject: Re: config & NO_F00F_HACK Message-ID: <19990425172657.A422@holly.dyndns.org> Reply-To: chris@calldei.com References: <199904251800.UAA44385@vodix.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: multipart/signed; boundary=sm4nu43k4a2Rpi4c; micalg=pgp-md5; protocol="application/pgp-signature" User-Agent: Mutt/0.96.1i In-Reply-To: <199904251800.UAA44385@vodix.cs.uni-sb.de>; from A.Leidinger@Wurzelausix.CS.Uni-SB.de on Sun, Apr 25, 1999 at 08:00:53PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Sun, Apr 25, 1999, A.Leidinger@Wurzelausix.CS.Uni-SB.de wrote: > Hi, >=20 > # ident LINT > LINT: > $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ >=20 > with: > option NO_F00F_HACK >=20 > # config WORK > WORK:15: unknown option "NO_F0F_HACK" ^^^^^^^^^^^^^ You made a typo. --=20 Chris Costello Make sure all variables are initialized before use. --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNyOWsbfyXY/Dmk2NAQHlwQL+KSQ8LwvNwQYEqOKpMufNOQO7Y4ByrR6i eAyljtaLZoKXmFCHr+iww4/V3vHBsYZs/DHzxx31wNfcr/mgQGYBuzGBOGS2Stsa 0wByP3etK9/0HNL8nYdWe6IH2fvG0QCY =E+27 -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 17:51:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id E45C914D12; Sun, 25 Apr 1999 17:51:47 -0700 (PDT) (envelope-from ctapang@aracnet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by mail4.aracnet.com (8.9.1/8.9.0) with SMTP id RAA14895; Sun, 25 Apr 1999 17:51:28 -0700 Message-ID: <01e701be8f7f$3ad97160$0d787880@apex.tapang> From: "Carlos C. Tapang" To: , Subject: Encanto Networks chooses FreeBSD over Linux Date: Sun, 25 Apr 1999 17:53:41 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just came across an interesting article in Investor's Business Daily (April 26th issue) in the Computers and Technology section. The title is "Windows Foes Pose A Threat: Ex-Novell CEO". In it Bob Frankenberg cites the reason why his company chose FreeBSD over Linux: they did a very careful evaluation and "found that there was a 2-1 or 3-1 improvement over Linux". "... A lot of work had been done to maximize transaction-processing performance." But "Linux, on the other hand, performs better for individual use" because of "better network performance". Hmm, are we finally getting good press coverage? I am sure this did not happen by accident. There must be an effort going on to get this kind of press coverage. Good job, guys. Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 18:17: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (Postfix) with ESMTP id 81A5514D4F for ; Sun, 25 Apr 1999 18:17:02 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: by ixion.honeywell.com (1.40.112.8/16.2) id AA167749407; Sun, 25 Apr 1999 20:16:47 -0500 Date: Sun, 25 Apr 1999 20:16:46 -0500 From: Shawn Leas To: current@freebsd.org Subject: -current compile failure (cvsup'ed today) Message-Id: <19990425201646.A16398@ixion.honeywell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just cvsup'ed today at around 4:00pm and I got this when building world. bison -y -d -o bc.c /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y conflicts: 1 shift/reduce cc -L/opt/gnome/lib -I/opt/gnome/include -L/usr/local/lib -I/usr/local/include -I. -I/usr/src/gnu/usr.bin/bc -I/usr/src/gnu/usr.bin/bc/../../../contrib/bc/h -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -c bc.c /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y: In function `yyparse': /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: `interactive' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: for each function it appears in.) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: `quiet' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:170: `break_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:174: `genstr' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:181: `continue_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:200: `next_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:244: `if_label' undeclared (first use in this function) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- Shawn <=========== America Held Hostage ===========> Day 2286 for the poor and the middle class. Day 2305 for the rich and the dead. 636 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 19: 7:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 4494614C35; Sun, 25 Apr 1999 19:07:46 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id CAA16297; Mon, 26 Apr 1999 02:05:28 GMT Message-Id: <199904260205.CAA16297@chandra.eatell.msr.prug.or.jp> To: Edwin Culp Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. In-reply-to: Your message of "Sun, 25 Apr 1999 11:29:11 MST." <37235EF6.A74D6974@MexComUSA.net> Date: Mon, 26 Apr 1999 11:05:27 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) It is probably TI CardBus controller, -current code not support it correctly. You should be use PAO. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 20:30:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from intrepid.leaky.com (cx74391-a.fed1.sdca.home.com [24.0.162.8]) by hub.freebsd.org (Postfix) with ESMTP id 01F3414C2D for ; Sun, 25 Apr 1999 20:30:42 -0700 (PDT) (envelope-from gshaffer@leaky.com) Received: (from admin@localhost) by intrepid.leaky.com (8.9.3/8.8.5) id UAA00978; Sun, 25 Apr 1999 20:28:47 -0700 (PDT) X-Authentication-Warning: intrepid.leaky.com: admin set sender to using -f Received: from aegis.leaky.com(199.184.74.2) by intrepid.leaky.com via smap (V2.1) id xma000973; Sun, 25 Apr 99 20:28:22 -0700 From: "Greg Shaffer" To: Cc: Subject: Fatal Trap 12 Date: Sun, 25 Apr 1999 20:31:28 -0700 Message-ID: <000101be8f95$45256410$024ab8c7@aegis.leaky.com> 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 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I updated my source tree, successfully did a make buildworld and installworld. Rebuilt the kernel. Upon reboot I encountered the following trap. Fatal Trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0xbfc00000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01dc935 stack pointer = 0x10:0xc0295ed8 frame pointer = 0x10:0xc0295ed8 code segment = base 0x0 limit 0xfffff type 0x1b = DPL 0, page 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 0 () interrupt mask = net tty bio cam <- SMP:XXX trap number = 12 mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 When it dropped into ddb I got the following: stopped at kvtop+0x2d: movl PTmap(,%eax,4),%edx At trace in ddb provides the following: kvtop(0) at kvtop+0x2d isa_compat_probe(...) at isa_compat_probe+0x297 DEVICE_PROBE(...) at DEVICE_PROBE+0x25 device_probe_child(...) at device_probe_child+0x4a device_probe_and_attach(...) at device_probe_and_attach+0x25 bus_generic_attach(...) at bus_generic_attach+0x16 configure(0) at configure+0x46 main at main+0x83 begin at begin+0x55 This is an dual 233MMX system with hardware I have been using for several years without any problems. The last kernel I built was on 4 April. Everything worked fine. Also, the GENERIC kernel does works. I have looked through my config file and compared it against GENERIC and nothing seems to be out of wack. The fault occured right after probing the ppbus. I thought that might be the problem, but commenting out the ppbus stuff does not prevent it from faulting. Any suggenstions would be appriciated. Thanks Greg Shaffer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 25 23:43:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E81FA14CF1; Sun, 25 Apr 1999 23:43:51 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA47125; Mon, 26 Apr 1999 08:43:33 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904260643.IAA47125@freebsd.dk> Subject: Re: Network problem with Laptop/Current. In-Reply-To: <199904260205.CAA16297@chandra.eatell.msr.prug.or.jp> from NAKAGAWA Yoshihisa at "Apr 26, 1999 11: 5:27 am" To: y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa) Date: Mon, 26 Apr 1999 08:43:33 +0200 (CEST) Cc: eculp@MexComUSA.net, freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems NAKAGAWA Yoshihisa wrote: > > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) > > It is probably TI CardBus controller, -current code not support it > correctly. You should be use PAO. It works fine with both 3.1 and 4.0-current, the reason it fails now is because the pcic/pccard stuff has not been moved to new-bus yet. The patches (well 3 oneliners) fixes this for the time being, until somebody has the time to convert the driver to new-bus. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 0:31:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B6C581505A; Mon, 26 Apr 1999 00:31:48 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA82391; Mon, 26 Apr 1999 01:31:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA08814; Mon, 26 Apr 1999 01:31:25 -0600 (MDT) Message-Id: <199904260731.BAA08814@harmony.village.org> To: Edwin Culp Subject: Re: Network problem with Laptop/Current. Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 25 Apr 1999 11:29:11 PDT." <37235EF6.A74D6974@MexComUSA.net> References: <37235EF6.A74D6974@MexComUSA.net> Date: Mon, 26 Apr 1999 01:31:25 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37235EF6.A74D6974@MexComUSA.net> Edwin Culp writes: : With a kernel from April 20 everything works except my pcmcia Viking : Modem which hasn't worked since last weekend. Is anyone else else : having this problem? Could I be doing something wrong? I'm painfully aware of this problem. I see variations on this theme many times. I'm about 2/3 through reworking pcic/pccard to work with the newer, much nicer newbus functions for allocating resources and such. This should be hitting the tree in the early part of this week. Until then, use the April 20th kernel. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 0:37:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B29C5150B2; Mon, 26 Apr 1999 00:37:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA82408; Mon, 26 Apr 1999 01:36:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA08858; Mon, 26 Apr 1999 01:37:01 -0600 (MDT) Message-Id: <199904260737.BAA08858@harmony.village.org> To: Soren Schmidt Subject: Re: Network problem with Laptop/Current. Cc: y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa), eculp@MexComUSA.net, freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 26 Apr 1999 08:43:33 +0200." <199904260643.IAA47125@freebsd.dk> References: <199904260643.IAA47125@freebsd.dk> Date: Mon, 26 Apr 1999 01:37:01 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904260643.IAA47125@freebsd.dk> Soren Schmidt writes: : It works fine with both 3.1 and 4.0-current, the reason it fails now : is because the pcic/pccard stuff has not been moved to new-bus yet. : The patches (well 3 oneliners) fixes this for the time being, until : somebody has the time to convert the driver to new-bus. The three oneliners kinda sorta fix it for the time being. Not all laptops are fixed by it (I know my vaio has me using the zp driver because of random panics when I unplug the card). However, if they work for you, more power to you. Rest assured that I'm working on the pcic/pccard stuff right now and should have stage one of newbusification done early this week. Phase one is where minimal cahnges are done to get rid of unstable interrupt hacking that it is doing which used to be right, but now is bogus. Phase two will be much more radical, hopefully obviating the need for pccardd in most cases. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 1:19: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7471514A2F; Mon, 26 Apr 1999 01:18:55 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA47281; Mon, 26 Apr 1999 10:18:33 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904260818.KAA47281@freebsd.dk> Subject: Re: Network problem with Laptop/Current. In-Reply-To: <199904260737.BAA08858@harmony.village.org> from Warner Losh at "Apr 26, 1999 1:37: 1 am" To: imp@harmony.village.org (Warner Losh) Date: Mon, 26 Apr 1999 10:18:33 +0200 (CEST) Cc: y-nakaga@nwsl.mesh.ad.jp, eculp@MexComUSA.net, freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Warner Losh wrote: > In message <199904260643.IAA47125@freebsd.dk> Soren Schmidt writes: > : It works fine with both 3.1 and 4.0-current, the reason it fails now > : is because the pcic/pccard stuff has not been moved to new-bus yet. > : The patches (well 3 oneliners) fixes this for the time being, until > : somebody has the time to convert the driver to new-bus. > > The three oneliners kinda sorta fix it for the time being. Not all > laptops are fixed by it (I know my vaio has me using the zp driver > because of random panics when I unplug the card). However, if they > work for you, more power to you. > > Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. Cool!, let me know if there is something I can test for you!! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 1:28:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 3F8FC14FDF for ; Mon, 26 Apr 1999 01:28:48 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 40A571F5C; Mon, 26 Apr 1999 16:28:42 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: chris@calldei.com Cc: A.Leidinger@Wurzelausix.CS.Uni-SB.de, current@FreeBSD.ORG Subject: Re: config & NO_F00F_HACK In-reply-to: Your message of "Sun, 25 Apr 1999 17:26:59 EST." <19990425172657.A422@holly.dyndns.org> Date: Mon, 26 Apr 1999 16:28:42 +0800 From: Peter Wemm Message-Id: <19990426082847.40A571F5C@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > On Sun, Apr 25, 1999, A.Leidinger@Wurzelausix.CS.Uni-SB.de wrote: > > Hi, > >=20 > > # ident LINT > > LINT: > > $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ > >=20 > > with: > > option NO_F00F_HACK > >=20 > > # config WORK > > WORK:15: unknown option "NO_F0F_HACK" > ^^^^^^^^^^^^^ > > You made a typo. No, it is a parsing/stringification botch. It's parsed like this: ID: NO_F NUMBER: 00 (octal 0) ID: F_HACK Of course, an atoi of "00" and then a sprintf("%d") results in a single "0". I've fixed this here and will commit it shortly, but I'm a bit nervous about the scope of the change required to prevent this information loss. :-/ I don't know enough lex/yacc to do context-sensitive tokenization. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 1:46:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 579781504E for ; Mon, 26 Apr 1999 01:46:27 -0700 (PDT) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id KAA00824; Mon, 26 Apr 1999 10:46:03 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id KAA23113; Mon, 26 Apr 1999 10:46:02 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (IDENT:EGN4Q5uG9DYYo9LRHU+JZhfXJmvQcONz@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id KAA11929; Mon, 26 Apr 1999 10:45:58 +0200 (CEST) Message-Id: <199904260845.KAA11929@wurzelausix.cs.uni-sb.de> Date: Mon, 26 Apr 1999 10:45:56 +0200 (CEST) From: Alexander Leidinger Subject: Re: config & NO_F00F_HACK To: peter@netplex.com.au Cc: current@FreeBSD.ORG In-Reply-To: <19990426082847.40A571F5C@spinner.netplex.com.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Apr, Peter Wemm wrote: > I've fixed this here and will commit it shortly, but I'm a bit nervous about > the scope of the change required to prevent this information loss. :-/ I > don't know enough lex/yacc to do context-sensitive tokenization. What about pseudo-device "i4bq921" at the moment I have to quote. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 2:38: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 5BA3914BE2 for ; Mon, 26 Apr 1999 02:37:55 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id D52B31F5C; Mon, 26 Apr 1999 17:37:51 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: config & NO_F00F_HACK In-reply-to: Your message of "Mon, 26 Apr 1999 10:45:56 +0200." <199904260845.KAA11929@wurzelausix.cs.uni-sb.de> Date: Mon, 26 Apr 1999 17:37:51 +0800 From: Peter Wemm Message-Id: <19990426093753.D52B31F5C@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger wrote: > On 26 Apr, Peter Wemm wrote: > > > I've fixed this here and will commit it shortly, but I'm a bit nervous abou t > > the scope of the change required to prevent this information loss. :-/ I > > don't know enough lex/yacc to do context-sensitive tokenization. > > What about > pseudo-device "i4bq921" > at the moment I have to quote. I don't think anything much can be done about that.. The tokenizer essentially ignores whitespace, so these are the same: pseudo-device snp 4 pseudo-device snp4 Without the quotes, your example above is parsed something like this: pseudo-device i 4 bq 921 Ie: a request for 4 units of the i device and 921 units of the bq device, which do not exist, or it will be a syntax error. Unfortunately, you can't use "options i4bq921" since there is: #if NI4BQ921 > 0 and... conf/files:i4b/layer2/i4b_l2fsm.c optional i4bq921 That 'N' prefix is for the unit count. Sigh... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 2:44:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id A26F614BE2 for ; Mon, 26 Apr 1999 02:44:18 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id LAA28244 for ; Mon, 26 Apr 1999 11:44:14 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma028242; Mon, 26 Apr 99 11:44:14 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id LAA09291 for ; Mon, 26 Apr 1999 11:43:40 +0200 (MET DST) Received: (qmail 30622 invoked by uid 666); 26 Apr 1999 09:44:01 -0000 Date: Mon, 26 Apr 1999 11:44:01 +0200 From: Jos Backus To: Peter Wemm Cc: Alexander Leidinger , current@FreeBSD.ORG Subject: Re: config & NO_F00F_HACK Message-ID: <19990426114401.C73238@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <199904260845.KAA11929@wurzelausix.cs.uni-sb.de> <19990426093753.D52B31F5C@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990426093753.D52B31F5C@spinner.netplex.com.au>; from Peter Wemm on Mon, Apr 26, 1999 at 05:37:51PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 26, 1999 at 05:37:51PM +0800, Peter Wemm wrote: [parsing hell elided] > Sigh... Maybe config should be rewritten in perl :-) Ducking, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 4:50:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 15EEB15101 for ; Mon, 26 Apr 1999 04:50:41 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id HAA12979; Mon, 26 Apr 1999 07:49:46 -0400 (EDT) (envelope-from luoqi) Date: Mon, 26 Apr 1999 07:49:46 -0400 (EDT) From: Luoqi Chen Message-Id: <199904261149.HAA12979@lor.watermarkgroup.com> To: chris@calldei.com, peter@netplex.com.au Subject: Re: config & NO_F00F_HACK Cc: A.Leidinger@Wurzelausix.CS.Uni-SB.de, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Sun, Apr 25, 1999, A.Leidinger@Wurzelausix.CS.Uni-SB.de wrote: > > > Hi, > > >=20 > > > # ident LINT > > > LINT: > > > $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ > > >=20 > > > with: > > > option NO_F00F_HACK > > >=20 > > > # config WORK > > > WORK:15: unknown option "NO_F0F_HACK" > > ^^^^^^^^^^^^^ > > > > You made a typo. > > No, it is a parsing/stringification botch. It's parsed like this: > > ID: NO_F > NUMBER: 00 (octal 0) > ID: F_HACK > > Of course, an atoi of "00" and then a sprintf("%d") results in a single "0". > > I've fixed this here and will commit it shortly, but I'm a bit nervous about > the scope of the change required to prevent this information loss. :-/ I > don't know enough lex/yacc to do context-sensitive tokenization. > This should be fairly simple, please try this, Index: lang.l =================================================================== RCS file: /home/ncvs/src/usr.sbin/config/lang.l,v retrieving revision 1.19 diff -u -r1.19 lang.l --- lang.l 1999/04/24 18:59:19 1.19 +++ lang.l 1999/04/26 11:47:35 @@ -105,11 +105,14 @@ int hex __P((char *)); %} -WORD [-A-Za-z_][-A-Za-z_]* +WORD [A-Za-z_][-A-Za-z_]* +ALNUM [A-Za-z_][-A-Za-z_0-9]* +%s NONUM %% -{WORD} { +{WORD} { int i; + BEGIN(0); if ((i = kw_lookup(yytext)) == -1) { yylval.str = strdup(yytext); @@ -118,6 +121,22 @@ } tprintf("(%s) ", yytext); return i; + } +{WORD} { + int i; + + if ((i = kw_lookup(yytext)) == -1) + REJECT + if (i == CONTROLLER || i == DEVICE || i == DISK || + i == PSEUDO_DEVICE || i == AT || i == ON) + BEGIN(NONUM); + tprintf("(%s) ", yytext); + return i; + } +{ALNUM} { + yylval.str = strdup(yytext); + tprintf("id(%s) ", yytext); + return ID; } \\\"[^"]+\\\" { yytext[strlen(yytext)-2] = '"'; > Cheers, > -Peter > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 5:14:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 6FE8014C21 for ; Mon, 26 Apr 1999 05:14:31 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id AC3F61F58; Mon, 26 Apr 1999 20:14:27 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: chris@calldei.com, A.Leidinger@Wurzelausix.CS.Uni-SB.de, current@FreeBSD.ORG Subject: Re: config & NO_F00F_HACK In-reply-to: Your message of "Mon, 26 Apr 1999 07:49:46 -0400." <199904261149.HAA12979@lor.watermarkgroup.com> Date: Mon, 26 Apr 1999 20:14:27 +0800 From: Peter Wemm Message-Id: <19990426121429.AC3F61F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > > > On Sun, Apr 25, 1999, A.Leidinger@Wurzelausix.CS.Uni-SB.de wrote: > > > > Hi, > > > >=20 > > > > # ident LINT > > > > LINT: > > > > $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ > > > >=20 > > > > with: > > > > option NO_F00F_HACK > > > >=20 > > > > # config WORK > > > > WORK:15: unknown option "NO_F0F_HACK" > > > ^^^^^^^^^^^^^ > > > > > > You made a typo. > > > > No, it is a parsing/stringification botch. It's parsed like this: > > > > ID: NO_F > > NUMBER: 00 (octal 0) > > ID: F_HACK > > > > Of course, an atoi of "00" and then a sprintf("%d") results in a single "0" . > > > > I've fixed this here and will commit it shortly, but I'm a bit nervous abou t > > the scope of the change required to prevent this information loss. :-/ I > > don't know enough lex/yacc to do context-sensitive tokenization. > > > This should be fairly simple, please try this, It works here fine, but I can't pretend that I understand it. :-) Will you commit it? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 8: 2: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A4B6D1503E for ; Mon, 26 Apr 1999 08:02:02 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA17123; Tue, 27 Apr 1999 00:01:37 +0900 (JST) Message-ID: <37247F56.27C734BE@newsguy.com> Date: Mon, 26 Apr 1999 23:59:34 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Jos Backus Cc: Peter Wemm , Alexander Leidinger , current@FreeBSD.ORG Subject: Re: config & NO_F00F_HACK References: <199904260845.KAA11929@wurzelausix.cs.uni-sb.de> <19990426093753.D52B31F5C@spinner.netplex.com.au> <19990426114401.C73238@hal.mpn.cp.philips.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jos Backus wrote: > > On Mon, Apr 26, 1999 at 05:37:51PM +0800, Peter Wemm wrote: > [parsing hell elided] > > Sigh... > > Maybe config should be rewritten in perl :-) If it properly respected spaces, it would have been enough. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 8:42:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from pc16s121r4.jancomulti.com (pc16s121r4.jancomulti.com [195.139.121.16]) by hub.freebsd.org (Postfix) with ESMTP id 406C71527C; Mon, 26 Apr 1999 08:42:13 -0700 (PDT) (envelope-from pms@jancomulti.com) Received: from jancomulti.com (localhost [127.0.0.1]) by pc16s121r4.jancomulti.com (8.8.8/8.8.8) with ESMTP id QAA00345; Mon, 26 Apr 1999 16:39:50 +0200 (CEST) (envelope-from pms@jancomulti.com) Message-ID: <37247AB5.467BDB2D@jancomulti.com> Date: Mon, 26 Apr 1999 16:39:49 +0200 From: "Pål Sommerhein" X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) MIME-Version: 1.0 To: "Carlos C. Tapang" Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Encanto Networks chooses FreeBSD over Linux References: <01e701be8f7f$3ad97160$0d787880@apex.tapang> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Carlos C. Tapang wrote: > > Just came across an interesting article in Investor's Business Daily (April > 26th issue) in the Computers and Technology section. The title is "Windows > Foes Pose A Threat: Ex-Novell CEO". In it Bob Frankenberg cites the reason > why his company chose FreeBSD over Linux: they did a very careful evaluation > and "found that there was a 2-1 or 3-1 improvement over Linux". "... A lot > of work had been done to maximize transaction-processing performance." > But "Linux, on the other hand, performs better for individual use" because > of "better network performance". The last sentence above says that "Linux performs better for individual use _because_of_better_network_performance." This is not what the article conveyed. The correct interpretation is rather that Encanto Networks Inc. chose FreeBSD because the company needed better network performance, *not* better desktop performance. A quote from the article follows: We did a very careful evaluation. The reason we went with FreeBSD is that a lot of work had been done to maximize transaction-processing performance. This can improve the speed of accessing Web pages. We found there was a 2- 1 or 3-1 improvement over Linux. Linux, on the other hand, performs better for individual use. In general, if I'm a user of a desktop computer - instead of a network user - I'll get a faster response time on Linux than FreeBSD. We needed better network performance. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [referring to an asset of FreeBSD] Paal Sommerhein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 9: 7: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 6B2D21520A; Mon, 26 Apr 1999 09:07:05 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA27540; Mon, 26 Apr 1999 10:05:09 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA29804; Mon, 26 Apr 1999 10:05:04 -0600 Date: Mon, 26 Apr 1999 10:05:04 -0600 Message-Id: <199904261605.KAA29804@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Soren Schmidt , y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa), eculp@MexComUSA.net, freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. In-Reply-To: <199904260737.BAA08858@harmony.village.org> References: <199904260643.IAA47125@freebsd.dk> <199904260737.BAA08858@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. Go Warner Go! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 9:51:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcayk.ukc.ac.uk (pcayk.ukc.ac.uk [129.12.41.131]) by hub.freebsd.org (Postfix) with ESMTP id 26DC6150C2; Mon, 26 Apr 1999 09:51:19 -0700 (PDT) (envelope-from ayk1 @ukc.ac.uk) Received: from ukc.ac.uk (localhost [127.0.0.1]) by pcayk.ukc.ac.uk (8.9.2/8.9.2) with ESMTP id RAA89313; Mon, 26 Apr 1999 17:53:47 +0100 (BST) (envelope-from "ayk1 "@ukc.ac.uk) Message-Id: <199904261653.RAA89313@pcayk.ukc.ac.uk> Date: Mon, 26 Apr 1999 17:53:47 +0100 From: Dean Lombardo <"ayk1 "@ukc.ac.uk> Organization: University of Kent at Canterbury, UK X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: file disappeared? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The subject says it all: I removed a file, but according to df, it's still there! pcayk:~/tmp$ df -k . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1f 7621844 6975669 36428 99% /usr pcayk:~/tmp$ ls -l -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso pcayk:~/tmp$ rm bigcdimage.iso pcayk:~/tmp$ df -k . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1f 7621844 6975669 36428 99% /usr How on earth did that happen?!!! So I decided to run fsck, with -p at first: pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f /dev/rwd0s1f: UNREF FILE I=1111053 OWNER=ayk1 MODE=100644 /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, 163307 blocks, 0.5% fragmentation) OK - the file's there - time to salvage it. pcayk:/usr/home/ayk1# fsck -f /dev/wd0s1f ** /dev/rwd0s1f ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y 176217 files, 6275839 used, 1346005 free (39581 frags, 163303 blocks, 0.5% fragmentation) ***** FILE SYSTEM MARKED CLEAN ***** ***** FILE SYSTEM WAS MODIFIED ***** pcayk:/usr/home/ayk1# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 63503 32799 25624 56% / /dev/wd0s1f 7621844 6975664 36433 99% /usr /dev/wd0s1e 63503 11211 47212 19% /var /dev/wd2s1e 8002964 7346107 16620 100% /usr/local/mp3-archive procfs 4 4 0 100% /proc Arrgghhh - now I've done it! Any suggestions on how to deal with this? Thanks, Alex pcayk:~/tmp$ uname -a FreeBSD pcayk.ukc.ac.uk 3.1-STABLE FreeBSD 3.1-STABLE #0: Sun Apr 4 15:58:45 BST 1999 ayk1@pcayk.ukc.ac.uk:/usr/src/sys/compile/SHAKA i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 10:10: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcayk.ukc.ac.uk (pcayk.ukc.ac.uk [129.12.41.131]) by hub.freebsd.org (Postfix) with ESMTP id AF2D514F48; Mon, 26 Apr 1999 10:09:52 -0700 (PDT) (envelope-from dlombardo@excite.com) Received: from excite.com (xtsw12c.ukc.ac.uk [129.12.41.85]) by pcayk.ukc.ac.uk (8.9.2/8.9.2) with ESMTP id SAA89332; Mon, 26 Apr 1999 18:12:22 +0100 (BST) (envelope-from dlombardo@excite.com) Message-ID: <37249EE8.85E9133F@excite.com> Date: Mon, 26 Apr 1999 18:14:16 +0100 From: Dean Lombardo Organization: University of Kent at Canterbury X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: file disappeared? References: <199904261653.RAA89313@pcayk.ukc.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dean Lombardo didn't write: > > The subject says it all: I removed a file, but according to df, it's > still there! (snipped) > Thanks, > > Alex Sorry about the name mixup - I accidentally left Netscape open on a friend's box... Anyway, email ayk1@ukc.ac.uk, not me! Dean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 10:51:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 2011914C38 for ; Mon, 26 Apr 1999 10:51:11 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA25933; Mon, 26 Apr 1999 10:51:07 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 26 Apr 1999 10:51:06 -0700 (PDT) From: Doug White To: ayk1@ukc.ac.uk Cc: freebsd-current@FreeBSD.ORG Subject: Re: file disappeared? In-Reply-To: <199904261653.RAA89313@pcayk.ukc.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Apr 1999, Dean Lombardo wrote: > The subject says it all: I removed a file, but according to df, it's > still there! > > pcayk:~/tmp$ df -k . > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > pcayk:~/tmp$ ls -l > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > pcayk:~/tmp$ rm bigcdimage.iso > > pcayk:~/tmp$ df -k . > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > How on earth did that happen?!!! Are you running soft updates? It takes ~30s for changes to take effect if you are. I noticed this myself last week. > So I decided to run fsck, with -p at first: > > > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f > /dev/rwd0s1f: UNREF FILE I=1111053 OWNER=ayk1 MODE=100644 > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, > 163307 blocks, 0.5% fragmentation) I assume this was in single user mode, otherwise you made a gigantic mess. :-) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 11:44:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.ukc.ac.uk (mercury.ukc.ac.uk [129.12.21.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A22D14C27 for ; Mon, 26 Apr 1999 11:44:21 -0700 (PDT) (envelope-from ayk1@ukc.ac.uk) Received: from ash.ukc.ac.uk ([129.12.3.224]) by mercury.ukc.ac.uk with smtp (Exim 2.12 #1) id 10bqKh-0000JW-00; Mon, 26 Apr 1999 19:42:19 +0100 Received: from localhost by ash.ukc.ac.uk (SMI-8.6/UKC-2.14) id TAA18822; Mon, 26 Apr 1999 19:44:17 +0100 Date: Mon, 26 Apr 1999 19:44:17 +0100 (BST) From: Alex To: Doug White Cc: freebsd-current@FreeBSD.ORG Subject: Re: file disappeared? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for a quick response. > > pcayk:~/tmp$ df -k . > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > > pcayk:~/tmp$ ls -l > > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > > > pcayk:~/tmp$ rm bigcdimage.iso > > > > pcayk:~/tmp$ df -k . > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > > How on earth did that happen?!!! > > Are you running soft updates? It takes ~30s for changes to take effect if > you are. I noticed this myself last week. I believe not - doesn't that involve adding a "SOFTUPDATES" option to the kernel? I don't have that in my kernel; therefore, disc access should be synchronous by default, right? And it had definitely been longer than 30s before I decided to run fsck (or before the first run completed). What does it all mean? That I have a file occupying 700+ Mb on my hard drive that I can't get rid of? :-( By the way, rm returned almost instantaneously - normally it takes a few seconds to remove such a huge file (that was the reason I even noticed the problem in the first place.) If this is a bug, I would be glad to help, but this kind of error is hard to reproduce... Perhaps someone with an in-depth knowledge of ufs can tell me what really happened (and what exactly did fsck do to my drive, just to make things worse.) > > So I decided to run fsck, with -p at first: > > > > > > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f > > /dev/rwd0s1f: UNREF FILE I=1111053 OWNER=ayk1 MODE=100644 > > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) > > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, > > 163307 blocks, 0.5% fragmentation) > > I assume this was in single user mode, otherwise you made a gigantic mess. > :-) I did, didn't I? Alex --- A mathematician is a machine for converting coffee into theorems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 11:49:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 8BF16155EE for ; Mon, 26 Apr 1999 11:49:01 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id LAA82506; Mon, 26 Apr 1999 11:46:15 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904261846.LAA82506@troutmask.apl.washington.edu> Subject: Re: file disappeared? In-Reply-To: from Doug White at "Apr 26, 1999 10:51:06 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Mon, 26 Apr 1999 11:46:15 -0700 (PDT) Cc: ayk1@ukc.ac.uk, freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > On Mon, 26 Apr 1999, Dean Lombardo wrote: > > > So I decided to run fsck, with -p at first: > > > > > > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f > > /dev/rwd0s1f: UNREF FILE I=1111053 OWNER=ayk1 MODE=100644 > > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) > > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, > > 163307 blocks, 0.5% fragmentation) > > I assume this was in single user mode, otherwise you made a gigantic mess. > :-) > Doesn't the file system just need to be unmounted? Qualifier: I'm not a file system hacker. Can VFS_STATFS return a value that indicates whether a file system is mounted? If so, it would seem logical to have fsck check the status. status = VFS_STATFS(mp, sbp, p); if (status & MOUNTED) perror("file system mounted"); -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 11:51:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from users.anet-stl.com (users.anet-stl.com [209.83.128.16]) by hub.freebsd.org (Postfix) with ESMTP id 779CE15277 for ; Mon, 26 Apr 1999 11:51:40 -0700 (PDT) (envelope-from doogie@anet-stl.com) Received: from rhea (rhea.accessus.net [207.206.169.52]) by users.anet-stl.com (8.8.8/8.8.5) with SMTP id NAA08474; Mon, 26 Apr 1999 13:51:32 -0500 (CDT) From: "Jason Young" To: "Alex" , "Doug White" Cc: Subject: RE: file disappeared? Date: Mon, 26 Apr 1999 13:51:31 -0500 Message-ID: <001001be9015$ccd0c6e0$34a9cecf@anetstl.com> 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 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 In-Reply-To: Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A file's storage isn't freed until its last reference is removed. An open file descriptor is a reference. Do you perhaps have a hung CD burner process or something similar running? If there is something holding that file open, a reboot would almost certainly clear the space. Jason Young ANET Chief Network Engineer > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Alex > Sent: Monday, April 26, 1999 1:44 PM > To: Doug White > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: file disappeared? > > > > Thank you for a quick response. > > > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > > > > pcayk:~/tmp$ ls -l > > > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > > > > > pcayk:~/tmp$ rm bigcdimage.iso > > > > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > > > > How on earth did that happen?!!! > > > > Are you running soft updates? It takes ~30s for changes to > take effect if > > you are. I noticed this myself last week. > > > > I believe not - doesn't that involve adding a "SOFTUPDATES" option to the > kernel? I don't have that in my kernel; therefore, disc access should be > synchronous by default, right? And it had definitely been longer than 30s > before I decided to run fsck (or before the first run completed). > > What does it all mean? That I have a file occupying 700+ Mb on my hard > drive that I can't get rid of? :-( > > By the way, rm returned almost instantaneously - normally it takes a few > seconds to remove such a huge file (that was the reason I even noticed the > problem in the first place.) If this is a bug, I would be glad to help, > but this kind of error is hard to reproduce... > > Perhaps someone with an in-depth knowledge of ufs can tell me what really > happened (and what exactly did fsck do to my drive, just to make things > worse.) > > > > > So I decided to run fsck, with -p at first: > > > > > > > > > pcayk:/usr/home/ayk1# fsck -p -f /dev/wd0s1f > > > /dev/rwd0s1f: UNREF FILE I=1111053 OWNER=ayk1 MODE=100644 > > > /dev/rwd0s1f: SIZE=716247040 MTIME=Apr 22 20:36 1999 (CLEARED) > > > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > > > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > > > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > > > /dev/rwd0s1f: 176217 files, 6275813 used, 1346031 free (39575 frags, > > > 163307 blocks, 0.5% fragmentation) > > > > I assume this was in single user mode, otherwise you made a > gigantic mess. > > :-) > > > I did, didn't I? > > Alex > > --- > A mathematician is a machine for converting coffee into theorems. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 11:59: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (node35.unassigned245.tfs.net [139.146.245.35]) by hub.freebsd.org (Postfix) with ESMTP id 2679114C25 for ; Mon, 26 Apr 1999 11:58:53 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id NAA21791; Mon, 26 Apr 1999 13:58:45 -0500 (CDT) From: Jim Bryant Message-Id: <199904261858.NAA21791@argus.tfs.net> Subject: Re: file disappeared? In-Reply-To: <199904261846.LAA82506@troutmask.apl.washington.edu> from Steve Kargl at "Apr 26, 99 11:46:15 am" To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Mon, 26 Apr 1999 13:58:44 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > Can VFS_STATFS return a value that indicates whether a file system > is mounted? If so, it would seem logical to have fsck check the status. > > status = VFS_STATFS(mp, sbp, p); > if (status & MOUNTED) > perror("file system mounted"); I am saying this without having looked at the code first, but I believe that it is already impossible to umount a filesystem with any OPEN files on it: "filesystem in use". Assuming that all of the buffers are flushed upon close, the only thing you really should get is a clean flag problem, as would happen in a crash on a filesystem with no open files. It looks more like he crashed to me, but then something could be munged up in the code. is softupdates on? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 12: 4:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id DB43F153B3 for ; Mon, 26 Apr 1999 12:04:31 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id MAA04669; Mon, 26 Apr 1999 12:03:57 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA16060; Mon, 26 Apr 1999 12:03:55 -0700 Received: from softweyr.com (dyn5.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA11247; Mon, 26 Apr 99 12:03:53 PDT Message-Id: <3724B897.F98426E4@softweyr.com> Date: Mon, 26 Apr 1999 13:03:51 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: ayk1@ukc.ac.uk Cc: freebsd-current@FreeBSD.ORG Subject: Re: file disappeared? References: <199904261653.RAA89313@pcayk.ukc.ac.uk> <37249EE8.85E9133F@excite.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dean Lombardo wrote: > > Dean Lombardo didn't write: > > > > > The subject says it all: I removed a file, but according to df, it's > > still there! Some running process still has the file open. As soon as that process exits, the space will be freed. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 12: 6:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.ukc.ac.uk (mercury.ukc.ac.uk [129.12.21.10]) by hub.freebsd.org (Postfix) with ESMTP id 6F98D154F1 for ; Mon, 26 Apr 1999 12:06:01 -0700 (PDT) (envelope-from ayk1@ukc.ac.uk) Received: from ash.ukc.ac.uk ([129.12.3.224]) by mercury.ukc.ac.uk with smtp (Exim 2.12 #1) id 10bqfg-0000fc-00; Mon, 26 Apr 1999 20:04:00 +0100 Received: from localhost by ash.ukc.ac.uk (SMI-8.6/UKC-2.14) id UAA19159; Mon, 26 Apr 1999 20:05:59 +0100 Date: Mon, 26 Apr 1999 20:05:59 +0100 (BST) From: Alex To: Jason Young Cc: Doug White , freebsd-current@FreeBSD.ORG Subject: RE: file disappeared? In-Reply-To: <001001be9015$ccd0c6e0$34a9cecf@anetstl.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A file's storage isn't freed until its last reference is removed. An open > file descriptor is a reference. Do you perhaps have a hung CD burner process > or something similar running? Nothing like that - I used a CD burner on another machine, and then ftp'ed the image to my home dir in case I needed more copies. After a few days, I decided that I didn't need it after all, and deleted it... or did I? The question is how badly did I screw things up by running fsck? It still reports pcayk:/etc# fsck -p -f /dev/wd0s1f /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/rwd0s1f: 176225 files, 6278980 used, 1342864 free (39576 frags, 162911 blocks, 0.5% fragmentation) (I think with -p it doesn't actually salvage anything, just checks the disk). Worth a reboot? Alex --- A mathematician is a machine for converting coffee into theorems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 12: 7:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id AF59B15395 for ; Mon, 26 Apr 1999 12:07:07 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id OAA13739; Mon, 26 Apr 1999 14:24:41 -0500 (EST) Date: Mon, 26 Apr 1999 14:24:40 -0500 (EST) From: Alfred Perlstein To: Jim Bryant Cc: Steve Kargl , freebsd-current@FreeBSD.ORG Subject: Re: file disappeared? In-Reply-To: <199904261858.NAA21791@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Apr 1999, Jim Bryant wrote: > In reply: > > Can VFS_STATFS return a value that indicates whether a file system > > is mounted? If so, it would seem logical to have fsck check the status. > > > > status = VFS_STATFS(mp, sbp, p); > > if (status & MOUNTED) > > perror("file system mounted"); > > I am saying this without having looked at the code first, but I > believe that it is already impossible to umount a filesystem with any > OPEN files on it: "filesystem in use". umount -f will force a dismount and make all open references go to deadfs afaik. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 12:18:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 7132514A09 for ; Mon, 26 Apr 1999 12:18:02 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id MAA82637; Mon, 26 Apr 1999 12:15:21 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904261915.MAA82637@troutmask.apl.washington.edu> Subject: Re: file disappeared? In-Reply-To: <199904261858.NAA21791@argus.tfs.net> from Jim Bryant at "Apr 26, 1999 01:58:44 pm" To: jbryant@unix.tfs.net Date: Mon, 26 Apr 1999 12:15:21 -0700 (PDT) Cc: freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bryant wrote: > In reply: > > Can VFS_STATFS return a value that indicates whether a file system > > is mounted? If so, it would seem logical to have fsck check the status. > > > > status = VFS_STATFS(mp, sbp, p); > > if (status & MOUNTED) > > perror("file system mounted"); > > I am saying this without having looked at the code first, but I > believe that it is already impossible to umount a filesystem with any > OPEN files on it: "filesystem in use". Assuming that all of the > buffers are flushed upon close, the only thing you really should get > is a clean flag problem, as would happen in a crash on a filesystem > with no open files. > I wasn't clear in my response. Running "fsck -p" on a mounted file system can supposedly lead to Bad Things. It seems that fsck should determine if the file systm is mounted before it can to some damage. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 12:21: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.ukc.ac.uk (mercury.ukc.ac.uk [129.12.21.10]) by hub.freebsd.org (Postfix) with ESMTP id A602914E1C for ; Mon, 26 Apr 1999 12:20:59 -0700 (PDT) (envelope-from ayk1@ukc.ac.uk) Received: from ash.ukc.ac.uk ([129.12.3.224]) by mercury.ukc.ac.uk with smtp (Exim 2.12 #1) id 10bquC-0000sM-00; Mon, 26 Apr 1999 20:19:00 +0100 Received: from localhost by ash.ukc.ac.uk (SMI-8.6/UKC-2.14) id UAA19543; Mon, 26 Apr 1999 20:20:58 +0100 Date: Mon, 26 Apr 1999 20:20:58 +0100 (BST) From: Alex Reply-To: Alex To: Wes Peters Cc: freebsd-current@FreeBSD.ORG Subject: Re: file disappeared? In-Reply-To: <3724B897.F98426E4@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The subject says it all: I removed a file, but according to df, it's > > > still there! > > Some running process still has the file open. As soon as that process > exits, the space will be freed. Of course... stupid me! I used vnconfig to mount the image and then unmounted it, but forgot to do a vnconfig -u... Of course, it's a bit too late now - just got a kernel panic trying to do so (not entirely unexpected - anyone want a core dump... :-) vnconfig was a one-off thing and not a running process, therefore difficult to detect. Many thanks to everyone who responded, and I do apologise for wasting your time. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 12:22: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B727C14BEC for ; Mon, 26 Apr 1999 12:22:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA47498; Mon, 26 Apr 1999 12:21:52 -0700 (PDT) (envelope-from dillon) Date: Mon, 26 Apr 1999 12:21:52 -0700 (PDT) From: Matthew Dillon Message-Id: <199904261921.MAA47498@apollo.backplane.com> To: Alex Cc: Jason Young , Doug White , freebsd-current@FreeBSD.ORG Subject: Re: RE: file disappeared? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Nothing like that - I used a CD burner on another machine, and then ftp'ed :the image to my home dir in case I needed more copies. After a few days, :I decided that I didn't need it after all, and deleted it... or did I? : :The question is how badly did I screw things up by running fsck? : :It still reports : :pcayk:/etc# fsck -p -f /dev/wd0s1f :/dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) :/dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) :/dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) :/dev/rwd0s1f: 176225 files, 6278980 used, 1342864 free (39576 frags, :162911 blocks, 0.5% fragmentation) : :(I think with -p it doesn't actually salvage anything, just checks the :disk). : :Worth a reboot? : :Alex Good god. Alex. NEVER RUN FSCK OUTSIDE OF SINGLE-USER MODE. Also, never 'guess' what an option is supposed to do. Read the man page. In this case, you guessed wrong. -p does salvage things. Reboot, get into the boot prompt, type 'boot -s' ( if a newer boot prompt ) or simply '-s' if an older boot prompt. When you get into SINGLE user mode, type 'fsck'. Do not specify any other options. The fsck run in normal boot will not properly clean up the mess, because the filesystem will probably be marked valid when it isn't. Then reboot again. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 12:25:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (node35.unassigned245.tfs.net [139.146.245.35]) by hub.freebsd.org (Postfix) with ESMTP id B64B514E1C for ; Mon, 26 Apr 1999 12:25:38 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id OAA26384; Mon, 26 Apr 1999 14:25:30 -0500 (CDT) From: Jim Bryant Message-Id: <199904261925.OAA26384@argus.tfs.net> Subject: Re: file disappeared? In-Reply-To: from Alfred Perlstein at "Apr 26, 99 02:24:40 pm" To: bright@rush.net (Alfred Perlstein) Date: Mon, 26 Apr 1999 14:25:29 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > On Mon, 26 Apr 1999, Jim Bryant wrote: > > > In reply: > > > Can VFS_STATFS return a value that indicates whether a file system > > > is mounted? If so, it would seem logical to have fsck check the status. > > > > > > status = VFS_STATFS(mp, sbp, p); > > > if (status & MOUNTED) > > > perror("file system mounted"); > > > > I am saying this without having looked at the code first, but I > > believe that it is already impossible to umount a filesystem with any > > OPEN files on it: "filesystem in use". > > umount -f > > will force a dismount and make all open references go to deadfs afaik. > > -Alfred I stand corrected. I must of misinterpreted the -f to mean -f[orget-this-option!], in a moment of self-preservation. As I recall -f is a last resort. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 12:28:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from users.anet-stl.com (users.anet-stl.com [209.83.128.16]) by hub.freebsd.org (Postfix) with ESMTP id 0AAFC15328 for ; Mon, 26 Apr 1999 12:28:10 -0700 (PDT) (envelope-from doogie@anet-stl.com) Received: from rhea (rhea.accessus.net [207.206.169.52]) by users.anet-stl.com (8.8.8/8.8.5) with SMTP id OAA17726; Mon, 26 Apr 1999 14:27:50 -0500 (CDT) From: "Jason Young" To: "Alex" Cc: "Doug White" , Subject: RE: file disappeared? Date: Mon, 26 Apr 1999 14:27:50 -0500 Message-ID: <001601be901a$df816060$34a9cecf@anetstl.com> 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 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 In-Reply-To: Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fscking a live system is a Bad Idea(tm) and should be avoided. Reboot into single-user and fsck it manually (while unmounted). Jason Young ANET Chief Network Engineer > -----Original Message----- > From: Alex [mailto:ayk1@ukc.ac.uk] > Sent: Monday, April 26, 1999 2:06 PM > To: Jason Young > Cc: Doug White; freebsd-current@FreeBSD.ORG > Subject: RE: file disappeared? > > > > > A file's storage isn't freed until its last reference is > removed. An open > > file descriptor is a reference. Do you perhaps have a hung CD > burner process > > or something similar running? > > > Nothing like that - I used a CD burner on another machine, and then ftp'ed > the image to my home dir in case I needed more copies. After a few days, > I decided that I didn't need it after all, and deleted it... or did I? > > The question is how badly did I screw things up by running fsck? > > It still reports > > pcayk:/etc# fsck -p -f /dev/wd0s1f > /dev/rwd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > /dev/rwd0s1f: SUMMARY INFORMATION BAD (SALVAGED) > /dev/rwd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) > /dev/rwd0s1f: 176225 files, 6278980 used, 1342864 free (39576 frags, > 162911 blocks, 0.5% fragmentation) > > (I think with -p it doesn't actually salvage anything, just checks the > disk). > > Worth a reboot? > > Alex > > --- > A mathematician is a machine for converting coffee into theorems. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 13:21:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 7E0E6153D8 for ; Mon, 26 Apr 1999 13:21:06 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id NAA28551; Mon, 26 Apr 1999 13:21:02 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 26 Apr 1999 13:21:00 -0700 (PDT) From: Doug White To: Alex Cc: freebsd-current@FreeBSD.ORG Subject: Re: file disappeared? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Apr 1999, Alex wrote: > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > > > > pcayk:~/tmp$ ls -l > > > -rw-r--r-- 1 ayk1 users 716247040 Apr 22 1999 bigcdimage.iso > > > > > > pcayk:~/tmp$ rm bigcdimage.iso > > > > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > > > > How on earth did that happen?!!! > > > > Are you running soft updates? It takes ~30s for changes to take effect if > > you are. I noticed this myself last week. > > I believe not - doesn't that involve adding a "SOFTUPDATES" option to the > kernel? I don't have that in my kernel; therefore, disc access should be > synchronous by default, right? And it had definitely been longer than 30s > before I decided to run fsck (or before the first run completed). If you're running default disk access then I'm guessing some program still has the file open. Perhaps 'cdrecord' hung? > > I assume this was in single user mode, otherwise you made a gigantic mess. > > :-) > > I did, didn't I? For the future, running fsck in multiuser mode is a no-no. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 13:28:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 3583814C28 for ; Mon, 26 Apr 1999 13:28:39 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id QAA15617 for current@freebsd.org; Mon, 26 Apr 1999 16:28:39 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199904262028.QAA15617@misha.cisco.com> Subject: Re: file disappeared? In-Reply-To: from Doug White at "Apr 26, 1999 01:21:00 pm" To: current@freebsd.org Date: Mon, 26 Apr 1999 16:28:38 -0400 (EDT) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White once wrote: > > > I assume this was in single user mode, otherwise you made a gigantic mess. > > > :-) > > > > I did, didn't I? > > For the future, running fsck in multiuser mode is a no-no. Not "in multiuser mode" but "on a mounted filesystem", is it? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 13:49:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 1FDA91539C; Mon, 26 Apr 1999 13:49:37 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id NAA48042; Mon, 26 Apr 1999 13:49:22 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <3724D154.D09BFEE8@MexComUSA.net> Date: Mon, 26 Apr 1999 13:49:24 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: NAKAGAWA Yoshihisa Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. References: <199904260205.CAA16297@chandra.eatell.msr.prug.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NAKAGAWA Yoshihisa wrote: > > PC-Card VLSI 82C146 (5 mem & 2 I/O windows) > > It is probably TI CardBus controller, -current code not support it > correctly. You should be use PAO. > I cannot use paq with current and it has been working fine for sometime. The newbus seems to have killed it. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 13:50:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 1C2E815397; Mon, 26 Apr 1999 13:50:29 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id NAA48037; Mon, 26 Apr 1999 13:46:13 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <3724D097.E781FB25@MexComUSA.net> Date: Mon, 26 Apr 1999 13:46:15 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Soren Schmidt , NAKAGAWA Yoshihisa , freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. References: <199904260643.IAA47125@freebsd.dk> <199904260737.BAA08858@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <199904260643.IAA47125@freebsd.dk> Soren Schmidt writes: > : It works fine with both 3.1 and 4.0-current, the reason it fails now > : is because the pcic/pccard stuff has not been moved to new-bus yet. > : The patches (well 3 oneliners) fixes this for the time being, until > : somebody has the time to convert the driver to new-bus. > > The three oneliners kinda sorta fix it for the time being. Not all > laptops are fixed by it (I know my vaio has me using the zp driver > because of random panics when I unplug the card). However, if they > work for you, more power to you. > > Rest assured that I'm working on the pcic/pccard stuff right now > and should have stage one of newbusification done early this week. > Phase one is where minimal cahnges are done to get rid of unstable > interrupt hacking that it is doing which used to be right, but now is > bogus. Phase two will be much more radical, hopefully obviating the > need for pccardd in most cases. > > Warner I'll be glad to test with a generic k6-2 running current, if it will help. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 13:59:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 6B7B0153DD for ; Mon, 26 Apr 1999 13:59:18 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA00301 for freebsd-current@freebsd.org; Mon, 26 Apr 1999 22:59:16 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id BBC4A8855; Mon, 26 Apr 1999 20:41:33 +0200 (CEST) Date: Mon, 26 Apr 1999 20:41:33 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: file disappeared? Message-ID: <19990426204133.A56100@keltia.freenix.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <199904261653.RAA89313@pcayk.ukc.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <199904261653.RAA89313@pcayk.ukc.ac.uk>; from Dean Lombardo on Mon, Apr 26, 1999 at 05:53:47PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Dean Lombardo: > How on earth did that happen?!!! Are you using softupdates ? If yes, there is a 30s window where the space is still taken and not given back to the system. > So I decided to run fsck, with -p at first: Never run fsck on a live filesystem, you could screw up yourself big time. > Any suggestions on how to deal with this? Either do a lot of sync or just wait 30s. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 15:14:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 8155A1543F for ; Mon, 26 Apr 1999 15:14:38 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA23390; Mon, 26 Apr 1999 15:14:32 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 26 Apr 1999 15:14:32 -0700 (PDT) From: Doug White To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: file disappeared? In-Reply-To: <199904262028.QAA15617@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Apr 1999, Mikhail Teterin wrote: > Doug White once wrote: > > > > > I assume this was in single user mode, otherwise you made a gigantic mess. > > > > :-) > > > > > > I did, didn't I? > > > > For the future, running fsck in multiuser mode is a no-no. > > Not "in multiuser mode" but "on a mounted filesystem", is it? Actually, I believe you're correct. I apologize for the goof. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 16:40:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id 949AD1539B for ; Mon, 26 Apr 1999 16:40:13 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id QAA23858 for ; Mon, 26 Apr 1999 16:40:05 -0700 (PDT) Message-ID: <3724F9D2.2AE86206@seattleu.edu> Date: Mon, 26 Apr 1999 16:42:10 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Current@FreeBSD.ORG Subject: Re: fxp driver and dhclient References: <371E3505.1F7B471B@seattleu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Hodel wrote: > > When running dhclient with the kernel fxp driver I get a kernel panic in > ifconfig. Might be some other things I enabled in the kernel, but I haven't > double-checked yet. I got it all straightened out, something in the config file was messing up, but I accidentally deleted it before I could figure out what. -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 17: 7:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id B53661539B for ; Mon, 26 Apr 1999 17:07:17 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id JAA01079; Tue, 27 Apr 1999 09:35:58 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199904270005.JAA01079@gizmo.internode.com.au> Subject: Re: file disappeared? To: ayk1@ukc.ac.uk (Alex) Date: Tue, 27 Apr 1999 09:35:58 +0930 (CST) Cc: dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG In-Reply-To: from "Alex" at Apr 26, 99 07:44:17 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex wrote: > > > pcayk:~/tmp$ rm bigcdimage.iso > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > > /dev/wd0s1f 7621844 6975669 36428 99% /usr > > > How on earth did that happen?!!! > > > > Are you running soft updates? It takes ~30s for changes to take effect if > > you are. I noticed this myself last week. > > I believe not - doesn't that involve adding a "SOFTUPDATES" option to the > kernel? I don't have that in my kernel; therefore, disc access should be > synchronous by default, right? And it had definitely been longer than 30s > before I decided to run fsck (or before the first run completed). Ok, something has the file open then - storage is not freed until the last reference to the file disappears. This is so that you can rm a file on a multitasking system without making processes that might be using the file at the time fall over and die (for a similar effect, try "rm /var/log/messages" -- You'll note that storage for the file isn't freed until you kill syslogd; in fact, if you generage log messages the file will "grow" and consume more space even though it doesn't have a directory entry. An application might have the file open; Alternatively, since it's a disk image which I presume you've been testing, you could have it attached to a vn device; if that's the case, something like "vnconfig -u /dev/vn0" will detach it, close the last reference to the file, and free the associated storage. Finally, it's possible that there was a hard link to the file. Given that fsck bitched about it being an unref'ed file that's probably unlikely, but the fact stil remains that hardlinks are a legitimate reason for storage to remain allocated after you've deleted something: Once again, the file isn't really deleted until the last reference to it disappears. > Perhaps someone with an in-depth knowledge of ufs can tell me what really > happened (and what exactly did fsck do to my drive, just to make things > worse.) No need for an in-depth knowledge of UFS; this is standard UNIX behaviour, regardless of the underlying filesystem. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 17: 9:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 58BFB1539B for ; Mon, 26 Apr 1999 17:09:26 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id JAA01090; Tue, 27 Apr 1999 09:37:42 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199904270007.JAA01090@gizmo.internode.com.au> Subject: Re: file disappeared? To: ayk1@ukc.ac.uk (Alex) Date: Tue, 27 Apr 1999 09:37:42 +0930 (CST) Cc: doogie@anet-stl.com, dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG In-Reply-To: from "Alex" at Apr 26, 99 08:05:59 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex wrote: > The question is how badly did I screw things up by running fsck? > (I think with -p it doesn't actually salvage anything, just checks the > disk). > Worth a reboot? Definitely: -p *does* salvage things. Boot to single user and run fsck manually to make sure everything's ok. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 17:45:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (Postfix) with ESMTP id CF976153D1 for ; Mon, 26 Apr 1999 17:45:04 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: by ixion.honeywell.com (1.40.112.8/16.2) id AA254793904; Mon, 26 Apr 1999 19:45:04 -0500 Date: Mon, 26 Apr 1999 19:45:03 -0500 From: Shawn Leas To: current@freebsd.org Subject: Kant Kompile Current today Message-Id: <19990426194503.A24564@ixion.honeywell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=h31gzZEtNLTqOjlF X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii uname -a: FreeBSD cerebro.mn26.integris-ds.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Apr 20 23:50:52 CDT 1999 sleas@cerebro.mn26.integris-ds.com:/usr/src/sys/compile/MYCONFIG i386 cvsup'ed a couple minutes ago gives me this. (I attatched a gzip'ed copy of the build log too) ===> doc /usr/obj/usr/src/gnu/usr.bin/awk/doc created for /usr/src/gnu/usr.bin/awk/doc cd /usr/src/gnu/usr.bin/bc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -D_BUILD_TOOLS cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -D_BUILD_TOOLS all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -D_BUILD_TOOLS -B install cleandir obj rm -f .depend /usr/obj/usr/src/gnu/usr.bin/bc/GPATH /usr/obj/usr/src/gnu/usr.bin/bc/GRTAGS /usr/obj/usr/src/gnu/usr.bin/bc/GSYMS /usr/obj/usr/src/gnu/usr.bin/bc/GTAGS bison -y -d -o bc.c /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y conflicts: 1 shift/reduce cc -L/opt/gnome/lib -I/opt/gnome/include -L/usr/local/lib -I/usr/local/include -I. -I/usr/src/gnu/usr.bin/bc -I/usr/src/gnu/usr.bin/bc/../../../contrib/bc/h -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -c bc.c /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y: In function `yyparse': /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: `interactive' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: for each function it appears in.) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: `quiet' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:170: `break_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:174: `genstr' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:181: `continue_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:200: `next_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:244: `if_label' undeclared (first use in this function) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- Shawn <=========== America Held Hostage ===========> Day 2287 for the poor and the middle class. Day 2306 for the rich and the dead. 635 days remaining in the Raw Deal. <============================================> --h31gzZEtNLTqOjlF Content-Type: application/x-gunzip Content-Disposition: attachment; filename="build.log.gz" Content-Transfer-Encoding: base64 H4sICEkIJTcCA2J1aWxkLmxvZwDtvW134za2Jvrdv4KTMzM5p9OyY5crSTtTtZZjuyqeU2XX sivdyZ2eUVMkJDHmW0jKsnPn/veLd4KyRIJ6s+h6slIWNgmC2A82nr0JgkCvt8p/e2/fvnVu yGAShH4Qj5xBkhR5kbmpEwaDzM0Cku/1VruD5zsHkzw7yDPvR+fT6eef33AxGfyuDh8UUXqQ D4L4ZO4Znl54tvYyfjJJi4NRnEREiGVRZSpMPDd8Imvx18PDm++EmFGAREqffXqV89Pl7fVV //by46cPF28WKzV2M3IQBblHL8qTeD8PojQkjnN2/fHT5YeLm/5iuPj9ggF5IF6t+o7z/uys f/HrxVn/083Fu8tfa4s7qTt54DgfzvsfLn+6Ob35rblqNLdt1trbOlfXF79+vjk9v/h0cXX+ pnCc65/+57vrm4+nn9vgIwWnDqyDyL0jzvnF7efzy5u55Tq9ofORZhoGIdkPYu+w7DG9sscY Js+B8/LJQfDqh+96JBz+6FhUoXf+j+ubD+f09+r68urdNU98PL3iv58uz8TvzfU7aiU8ffvz 6c3FueOFxI19kpLY3+h93DDcaPm9n5wgzgt6G6lSkDn0RntZxBpgX2j49P6zWB+8ZwZik+/m 8+n7W8cm5+1vH29t8rEC9zzP6X0wCIiZc+/SOEBNKJz4hOUqGUTmKg/oXLRkp/cPBktveEdI 2gviMIhJbziJvSJI4lxdN69VdCneYus88LLicJ/WOnF4KummCgMyCmKthpA6qgo1dK0ISws1 5tZ6biWba9BYhWD/VlYgeI7bx/r2u9uI5+/Pbj4zTWhFR6LnNHYyrsowDejfc86FL6Kb3Sbd 12u2z1GdlDsSTcyiQKc3cqZjQuixyDk+PnYcs90XxVCSVS2Lk8zVWKRiOMtiOY80FirYxrLI wKLAwL44G6VtFR7ZtMtomYa5tWyZ23ZNc2vVNqzQxjiEFkncgvjOMMkW2/yTgJX+K0gWeW6K cHWz4WqJdF2wauaqC1XNfIsDVTPXRsLU87OP/Svx8/6z+P1J/JyrK57WZRniNjSRv4K3lZC8 DNVGSZFIxXjyhaiVTopcqsWTL0UtN4uUWiz5QtRK8pQQGRcpIdnTI4eU/mLfzXzV9+QA4uNe 5sZMk7Kofbd0hmcLnWFTPx/XELpUx8rnVipW63f3ap2yLIb+0GJ6bx2bzAKMBo5e7MLLPBUH Poon6nRGRuQBLnxzLnwW60VO/Gm+RW78ac75jvxpPu7K37x589bxE2/tnHO58M4Uxp9P/37R v/18c3n1vv/zm0N65Pbz+Vn/54vT84ubW37g6rr/6fr28tc+G9w+/cyOteOjJwrzv4KPRHIe G9GrRCWf0pE6RbugRq0NMS2okAUxHehbj605qqxtPUlpVXRCmLC4uCAPwV6jLc2nnNlc5R2a jZPmsiv0gNvuIjZzffawD0LbEqEJuK04TWW1ojWV2YLZVNYquanEwTjIi4T2an1AXbEt/hN3 azh9sL8v//eSuMhmrxX0eXZ99e6S0ieVbz7o12x/p/x5eX315uuvjvaPvvp6JdK0qIzGT/Gq lBLguRye90E/SnwJpxKA5pJoDidxpJ7xZRpYLonlHXmk+MkHcCUAzSXRpE/6JJZgyjSwXBLL nLiZNxZYyjSwXNafh0XxKJ05TwLJJZH0EjY5q5CuXEvAc0k86ROOHE3kKeC4JI6BSZcB+HI1 NP0gT0NXMqYSgOaynjwYxW4owyIlAM0l0ZwUQSig5CnguOyTTxBKHHkKOC5rj7EvX0vzFHBc EsfI9TIJpEgCyWVjoTidFDIS4kkguezTjhuGA9e7k087SgKeS+LJXtQHNPwp5ydxCXguiWes osoYEeXyKD5EtGMnnkBSCUBzSTTly0iBphKA5gpokofUVaNEhgxMV8CUf7qoEeUS8FwBT3P4 zZCB6bJjRmOiHs9FEkguG3MGoZp5IJLzJsjpqj+dIKdnf7itZt4sPYeu1fwUm2l226mSN6Y4 kmG+Q1VSr/N3p0YqHNqdGokusVx9GuZqlh2n5VzNml61OK+Y0acA5jM8n16uJoHKilnMA5W0 0Dxrs7GCVjP8jAus73lQD5n1fVsre1Cdavj06zkPc1Q3/t2c1/DFnNf4rZzX8JWcJ+edZqk3 IjGnobH4LPgxLSh1NDNH6uX33oHI//CknMe0RSE088NemgVxMXS+/jcVIHx1+9vt/virf8Y3 NHF2+uHDvzOz/I9/xl87b3l3379t+cX+OQ1Xzvo3Z7dsFv9vt6V0+RSe8qJ+//yny6vPFzfv Ts8u+p9uLv9++pm1tZjz//Hy9vPpf17MLYPSM//l1WBF/XRz/Z8XV/3zC1aD3z5ZhUnz6vbq h+8YUwsQ1GxWGgNZYDjNgoJIEHn6i0dRosBgFEkrHBPagSWMLPnFoyhAYCDylBWGXpjkyhZ5 +otHUaLAmZgn7fq0GxTHqk+zNPq0QIH3aZ60wpGGPHcSRpb84lEUIDAQecoKw0lsoCiELx5H BYOYT2CPpTemYaPiR5YGPwoUOD/ypBWOQxPIIZBkSA4NKIctsIzu4kQF4Tz9xSMpUeBzXHjS sm9HGkeeRt8WKIi+HdnjmExjjSNNA0eBgsCRJa1wHJFimOeFW0gstfzF42kgwdfA06Itrmng l6BSAYhKGCScLG3ne5JJrOyTp+F7BArc9/CkZYxuIiklROmxgaYSrPDMSTHRfVwIXzyaCgbx pSNP2/LlxORLYOlpGCRftsGSVMAkQNMrcZBwEms8M+LdR/lIv4LgEt5CKBzEiwghWPJm7Jd4 SgnMqXAQ1CkEa/scZklkGCgTYaEaCGWiXLLC1PU8kqpQSQhfPJ4KBoamTFs/CxGSxW5EjAci eQR+ycRCPRqpA7b45ol3V8VXHQG+JhYSX33Amgvy3OCCPAcXSBgUF+S57bjdMHRHuR654xLG 7hQOYvROCLbvOExAh0BUv+cwIB22wjR/jD0VnNIkIlMOAg9LWcoKQ/YdusSQf5L+pWMoQDC+ 0LeMm6qDyBhF9kocVKxkPY7sT1KJJU198ThyDPiaMJPUflxpVBlXGsEeSxzUuNLI1h7TLBkG iiWF8MWjqWDgqw6KtJ2/KTLXU48/QoDPkTBwryPSdvFPMHL51lMqCFIyIqESCbn+kxRt+bNC n2BPT8MgydOaO+kzpzE6h7E5AYJ8Gi/s+3lY5IXr3Rk9XR5BXzexUL1dHbDCN0i8Qrl3nv7i MZUo8NWMeNLy/cZ9ckf02w0m4N2GhEG82eBpy7GNyJioLSX0dYWDGOSI7Odqy08m74zv04Co /EathFRLVpiyXc3vVX8XwhePp4KBoSnTdnO+IjfXn2WwNOZ7CRT4bC+etHxvwT6O168tmIC3 FhIG8dKCp+3mcxoD7BFG2Nl8znKIPbIfY793/ftAf0kppS8eS40D359GCnZ2yfdfUYYpNmP5 4i1TwsBNU+1PY4NlmiUF0c/oSgSeGgiOqJLsMK309wj9XSBq9veoVX+np5JM4ykk4Klw4HhK wXp8M0smaW4McXIZo5wlEmqgU4i23xlUcM2Ba/m1gYlr3g5X9vJ4lKXG+3UqwVYVDur9OhNs 7TQdmR/EpHjD4ZU4SAtNrd9x0MxBEUQkKxEVMjAtkZCoStEO16mbli83uQBEJQwcTpG25dCK jY5goyWPmjY6amejNLtfuIOQ5MGfxqzu8hjwraIhMTYO2c4JOyonhR1hVhgHQU4LO7Kdgxzr 95w8jdnHAgUx9Ti2fc+Zk7AcMREC/JKEQbj50HqsZGiMMQ8xxsxsshxjHtqPMbOANQuSLCge jbheHoF1mlio+F4dsMM38e6I7vNcAKoSBg6oSNu9o0viuCRQKeEtncJBbPIrBOvxkWrfH6Hv V8ZJKn1/1Lbvs12CJbB8w+AvHVEBgrF/sp1/YhSRpGXcpA6ARw0opHNSsuW6qHmhVzsWAtZG lTCI1VF52pZL2dN/MvRdg0z1IbBpBQxJp+URW4yzSe6OjPESIQPdEgkJrRTbrC9QcuwIHDuz uoDm2FFLjmUzI++NyaP3mDkqUFDTRu9b7G9wb25wACQVDHqLg3vrmGrWV+XwVZW4asZX5a19 1dBcwHaIFWzlmg16CdthizVsh+aiykOsqiyx1MsqD1usq0wtOSOVVS0zrB4o+nxGzJUtM/v1 A3nuURVTzIzwDCA0piP7NRmN5a6EgMiJlItcybQdf9IKqW9EeBrsKVDg5MmTlnskDINhojdJ YAJmk0oYxDYJPG29RmiRGEuEFsBSwaAWCC1ssRxPCr+MNpUIPDUQYmtmKbV4b5e6en+Z8gBw NaAo3+Fx2ZJHy217eBoseqc37RFJuxgpKnHkaURIkcZRJO2+oWXP9mryvRDwFa2EgX9GK9J2 67b4v7PcaukWIWH1FoUDX8BFCtbvP80nyxzPlRoG9c7T9pnyj0lSuOWSLUr84vEsgWCIaskK 03iY5/dqIp4Qvng8FQwMTZm26+uFWwz1R2BcQF+XMPC+LtKW80NNMIdAU84RNeActsGTbY82 NvaQG+PNsEBB7R03tl2fKXczb6zXZ+ISernCQazPJAS7ZyA+J089BHEBT0ESBv4YJNKWsWZE sdexJhNgmRIGEWvytOUaOKMSSyFglEPCIJbBGVljmY9NuxzDLvnYpmGXY3u7jIu0X31GN44g cjex4OG7ccB6LQfzeR3vgT0Ng1rCocV79eprdbxVF2hWXqqTVnhWpn5g5ofE05z40WLeR7mt NnbUls/q5ZN6i+d08ykdz+gljEN7HEMDxxA4si85ShxDexxTtxh7STxUu3ZIEft2aCD4zh1K suvjM6AOgarq61VYh+1wZZ95hEEUGJ9tCBljcyUS6nsYIVrP5zRxzYGrMaPTwDVvhytbviXI SFxkATHWECyPwW6raKg1b8pDVjj3+/ljTiuoXnRq+YvH10CCYVuKLXAtqrDi/bEBRAmq7fvj yJibHGFuMhslLecmRy3mJk9iE0khAUuFg1ze2h7PSeyTkBRqkFSJmBemgeAzw5Rk9xxQmWg3 xEw78QxgTrUbtplrN6qsxzrCeqzl+rbm/rH2+3UmOmRiSTzzJypQ4im7NZoYxfbl2g5qpSbz GNZrqqLBV22qHGqBcz4H5xw4GzjnT3HO2+PMBhC04zIPAeUKGBVjzmz9WOzGSR4SolZq1zLe R5dI8LfRWrTd/2JMMj2MpUQ8FWgg5BYYQrLb8zOn9DEpoy4tY+/PEgm+/6cW7d5fmetlhFgv g7/BMtbLCFusl8GGDElcmEOsTMSTgQZCDaxyydY+yzVIQqxBIu1Tr0EStliDJCbFIPf7lS5f OQa/X0WD+/7KITubrYy3hBhvEVZrjreEbcZbZBOY21uah2C1FTAMo22x52VszGOJMY+FoVrO Y4nt57HE5sSqGDOr5Hd5JZQt5lbF5uSqGLOrOJbG9Kq4xfwqGiTE5EE/kgoJT6QKB/5AKgVb PA3jlBLwVDhIPFvZ57BqoENYqEB0WDHRYSsbHZZL4UsJiCocFKDWa+LfhX6YuApPKX3xeGoc GJ5KsMWTTQ0wERUyMC2RkKhK0RZXo99LCZiGRr9Xgi2ehmuSEvAMjdhJCbZ4GrGTlIBnaMRO SrDv71lelAOlxhHgamKh+748YL1PgzndB2tBeRoGtTeD7fsmN0j6GSkmmRqALg9gtTIDCr5g WSlbY5tP8pRo328cAbomFgpedcAaX8+NPRIa8IoDQNeAQoErZWtsSZYlmQEtl4FsiYQCVogt +Nb1K2yLJywDiJJp3RY8wPd9MUDlMlAtkVCwCtFyX7ykz/Z+0+tKlQfw9tSAQuyRp2XLb6ho lOZNff0NlRDxDZUGQnxDJSW771W9MfHZtNbUzdxIfbRaOYgvV2fg4J+vVo+1wHo0D+sRsDax Hs3BerQE1myFX5aYhCSbtW19ApjPgaRi4+XxdnY+H/sRsJ9j73OxHy2J/WNAQr8COj8CtE0s SpjFgXa23Vf7efcj92HWvisngfoCWCp2Xj23dFsEcU1bBBifWwTLorYI4jZtkWX8cpqbZPdu WGmKmXNoifmolA0xe8pyP5LM9fSX51zAd+cSBrEfCU9b7zM2DEJi7DTGRFiuBkLtNsYl6/em j5Hx2vQRzzwKBvXS9LH+GefT7cUv59f/zsghTEZB/FeV4KiygRF1ACMjJRJ8aESLtfgqgMlD UPyV/dHAMgGgChQ4oDyZcEA+GIDQ/AsQ+mAgJHO9FMg8Z3HB/uBgUGSE0L99L0xysu8x/LQE CNtBmMT3JYJMAICtAPTJYDLSCAoJELaEkK9eVGIoFzMCiC1ApA5ZI8jSgK8VfElKYo0fFwBg OwDvSTYMk2kJojoAIFsBmbqjkgu5AADbATgpmZClAV8r+HLC9/1SCEoRILYE8Q8DwT8AX0v4 0jAoO7GQAGErCCdFEOYaQiEBQhsI+f8COfoLzGwwG7v5mP8RuPEUkGuFXH8QjO7IYwmgOgAc W+I4GZogToZAsCWCw0nsGRByERi2wzBMRkcGhlwEhu0wLB+FSxEY2mNoPsqN8SDXFr/YH0QC PJ4CcjbIRWmShOKvwE4kAZ4NeBnx4oT9NV9tliJAbAei+WLJkAFjOxj1qyUlAMB2AJYvl7QE CNtBqAf1lQAA2wFoxoKGDBjbwviHiSFG9tsCaIxLlyJAbATRS6LULXrHrw68jLiSDEUS6LVA j8Yv4yQvAl8gWIpAsR2K0xLBKdBrhd5dEIapnDQo08CvBX55tQ/n6MNLopiOslRjyAUg2A7B bGRYYTaCDbZHcGIiOAGCLREMRkKQGGoRKDaiOCLxQT9zY//4B4GeEoCdHXZ5GsRiN8diIqfM zBwDklZIuqGbyXdNIgnc7HDLvGPWZxMFXikDQTsE85xk0nnINJCzQo5vsSrHYeSW9sDNDrec +EGmoRMS0LNDL2GbJinwpADs7LDLHlM9csqSwM0Ot4JkkXpKUwKws8LOd0mUyLe/Mg3k7JAj 97EbyekbSgB2dtgF+V3oDoicg1WKwM8Ov3DoqU7Lk8DNDjdzNMXHaEob7IiJHQF27bDLFG6I hu0xC/NCw8bSQM4OuQciv4/hKaBmhdowjtxCTUFTArCzwy4vXDnALpLAzQ63IpFDdDwF1CxR yxVomJtnidmIFIMkKfj6nWpelD4ADK0xzIM/DQC5BPRs0fPcVGPH0kDOGjljOqOH+YwtkPOT yA3icqSuegg42uI4ykhcaAiFBPTs0UsmKdsCy0BQHQGKtiiyabSVnqwPAENbDNnO7O79SEOo ZCBojyBbWLzETywzDvTs0IviIoiHicZPyUDQFsF41hnH8MdtMaTXD5MscksQyyNA0RrFPCOh 7xalQy6PAEVbFNm6QZVhBX0AGNpjmOcGfjnGBVtgNzWdiZCAni16RfFowidF4GeL3yQnWT4m YaghLI8ARVsU74f54LHyaFweAYotUDT7shSBnx1+YSJfAfMUULNCLYgDMRQowxdDBoJ2COYu dboSPZEGclbI/W7O6PsdM/raYBd6STxS2CkB2Nlhl3h3cg1skQRudriZ/TVEf22DXWRiFwG7 VtjlI69Qy+WKNJCzRU6vTirTQM4Wucy718ixNJCzRS6PfY0cSwM5K+TiwJPjJzwF1OxQK6e1 xJjP0gI3MyKJEZG0wq5I2UrfRaAGPM0DwNAKQ7bOt17mQgnAzgq71J2o7Q9EErjZ4VYuNZ9i nfkWuOXBKHblI5gSgJ0ddlPP9caqt0oB2Flhl7mB3uaFJ4GbHW7E9bVvVQKws8RuGsQmekoE flb45Z5bxnVKAHZ22BGiH8lkGsjZIndXWp0UgJ0ldhFbKS8YKfSUCPys8VPvJ2QayNkip99P yDSQs0Uu0XsTsCRws8TtyRe5Ob7IXQrH6teQOb6GXALD36NUr81VisDPFr8o8Uv74wKws8Nu rD8+E0ngZotbGeuNEeu1Qs4vLc6HxdnjVsbIY8TILZALRkFcUIc6Scvtf8ojQNEWxXKGhRKA nS12+rUZ3pq1RI5GdIn6LKUUgZ8dfiEhanyAJ4GbHW7mrKgcs6JaYVdkQWw6i1IGgnYIPuZs 6F3CJwVgZ42dfjITaSDXAjnz++3KEaBoi2KYjDR+LA3krJArSBjqd7dKAHaW2GVRkOQKOyEA Ozvs9PRtzNtuh1pewgZra4Hbn0lsWByXgJ4deoURnigB2NliR8ORQmPHBWBnhd3E2Hp6gr2n 2yBX9tcJemsb3O6DXOHGksDNDjdjyHOCMc82yJWB8ASRsD1u925IyxfAyTSQs0NOMRz4zRqz qRvIEI6ngJo1aq9K2F4BN3vcUrWnuRIEdnOhejnIzKvbqx++q4eM5eC49cUszv1bhpsSgFsj btx9ugI2mQZqjagN3UEuMOMpcFsjt5XQZeRBPi2IJMCzBy+Ih2yhWLXqqZIAYQsI80C96BdJ gGcPXujrziuS8BWNmEWJPxS+gqeAWCNiZiiHSM4aNT5VswROiyC45ievKIn5H7mQPUsBNjvY Ii+ZqM0TZBrQNUInCj5w4zwQ0PEUgLMFbhCMXgvgeArA2QLnJWGod25TAuBrA58XpSV8Hjxs C/jIRL63YQnAZgvbMJuoCUwiCehsoQtyr3hMiXriFwLgs4WPbXFyX+52gtXYW0DHfwz8Shkg 2oIYDUrqk2mAZw1efufGvwdqTwAhAD5b+CgWrpepSf5aAoD2AKquG2PKdRvgSs4D47UGrgz3 tAQAbQHMSRHE924Y+KUNzhwDmC3AFCmNoxQBYQsImdHNwGgcApS2UBbuQEEokoDOGrokTKZE fSkrBcBnD98kTUv4hAD4bOGbFMMj9ZkATQG4RuBo2Hfg+n525OZeoF6wlTIQtEOQgXXEcJMI ljIQtEJw4Obku2P5nlKkgZwVcqQYk6xf2p4hA0ErBEdiYejBox/LEazKEaDYDsVxMQPiGPNc 2mIYB7OWGOM7tJYoxm7kKlKsHgKOtjjSnyot6gPAsBWGBikqGQi2QtCkRH0AGLbAcIYQyyNA 0RbFNEuKRCMoJKDXCj0SF1UACeZBt8WwXLimcgQo2qKYk+zeXE60egg4tsMxTbJiBkd+CDi2 wdEkRiUDQSsExyTLEhnZyDSQs0IuoH+MwcNSBH72+IWxmwwNAIUMBO0RjNw7MmOF+hBwtMeR /yvUvpvVQ8CxHY5pob5yrR4Cjq1wdKsYusCvHX4VzyJkINgKwWmS3VUx5EeAYgsUi6TSj5kI /Frhl1bxgz9ug9+ML4YftscvDOK7MrTWEtCzQi9y0/798f138sswJQE9K/Ti3BhbUAKws8Wu HJ9WArCzxo59ilOU6AkR+FnjpyM+JQA7W+xSN8vLjiskoGeNXmZ2XCEBPVv0CrXDpEwDOUvk aGhnxipKBH5W+GVeJJdi5ymgZoca8eSSJzwF1CxRy/teopYW0xLQs0bPd9WwvJaAnj16ZDAZ GfBxEfhZ48eWYi/h4xLQs0YvuvtjQrLHEkB1ABi2wHCS+nptz8oRoGiN4owdwgpb4peT2C/h 4xLQs0Zvtgej/7ZBsLQ9w+6wa8CCXQP4HNMiiUOxY4BIAjMrzPISsxyYNWMWF8lY2plIAjMr zPISM3wXaOMFwvzAcwsvTNS7Ci0BPVv02KcaGjwuADtb7JKUxBo7LgA7K+yifEQRU2sV8zSQ a0Tuj4nrH3hR6gdyiTCZBnR20PnBvR/IjYplGtDZQRclvoZOpgGdHXR/UFPLSCSwUwLAswNv YtLdBHzXDjyT8CZgvHbgmZQ3AefZgpeREXlgf8332yO83m6JnvE5uJaAXwv8HohXwscEoGeP 3jAj+r2EEIBeI3p54QfJQX9Ib3DXz4vJQCBoHgCKlii6OZ81O1SLEUsJ+Fni54UZ9RlylECk gZ0ldkNjQHmI4eR22PnlmKhMAztb7Ij6UJ6ngJs1bmWsPESk3A67YTjJxxI7kQZ2ttiNSCGf MUQSyLVALoxL6EJ4iVbYpWqfSiUAvRboGdgBOXvkgpDEcuFgmQZ21tjF/jBV2PE0sLPFLnRH qsfyJJCzRc54FMOTWCvkzMGnIcae2qI3yUZq/ESkgZ09dvqZgieBXAvk8hI5+Al75DLiyi8p RBLI2SNn+FgpAD1b9HLPjZWTFWlgZ40dIXcKOpYEcvbIGeMnOcZP2qFXkFCuziOSQM4WuUls +AopAD1b9O6nWaC+lVUC0LNFb+qGylvwJJCzRs4wO1hdK+zK12N4O9YWt7Fb7nLIBaBnj165 yyYiuza4TTVuU+Bmixvb5GcwGarVtYUA9GzRuyuI+kxApoGdJXapMe8pxbyndtgZL3jwfqcl dvoVBd5QtMVNx3VKAHr26OUaOsR1bXCbatwQ11njlpFhoIY6ZRrYWWMXJff6AzKeBnbW2E2D clFFngZ2ttjRR1eJHEsBN0vcjBexeA/bDjlS6Id/mQZ2rbAbksyEj4lA0B7Be9P87mF/bdCL zVEALQE/W/wq8AG9luiZThdetx127K+EjieBnCVybIQ9duViZEoAerboRSn79EmiJwWgZ49e aXqwvFbYTeJyNoVMAztL7O6ri8ncYzWZ1ghWPoi6xxdRrfEzgr17zHVviV7F+GB7LdEzTQ+W 1xK7yhDBPcYI2iNYBRD4tcWv0n3Rf1uhN9WDo1OMjLbBLSfFRM7Kk2lgZ4MdO5YXWZGonclE GuDZgFcEFAc399ivWvdTCMDPGj8/GA5LALUEBK0R5DcoISxFYGiNIeU9wwq1BATbIJhWEEyB YDsE2R9+EznirEVg2Igh35Ywf8x5oj8iRT9IUpLJwfvZgwB0CUBDv5hBkx0BlC2hzOfZZg7b XAnQqm3msM3loLyPfvjOwJGLALHZgVP8hkU2iT29O3opAj8r/MJyfaAQ6wPZ4xZFrvoalaWA mhVqabmCXIoV5FrgZqwukmJ1kRbIVd0DvEM79Pp949NxJQjs5kL1cpCZVzcam1lGddf3wyS7 279lsMk0UGtEbaAgGwAvG7w80R85ZB76piVqbI/HQoAmksCsEbOSzcBldoilQUoEYjwFxJoR KzLXU5iJNFBrRC0jgySRdCbTQK0ZtZLQMjCaHWa5Ds9yxGd2iJEiTEZBLFFTEpBrRi4YpST2 g3gksStloGeFXpZ4kZvflfCpA8DPBr+MFJMs1uhJEdjZYJdPctZZNXhKBnrN6D3m9N6hhE4K GKtsHKvMUu/AnRTjvk/k2m9aAnr26MVJTAz4uAj87PEzJiRrEfjZ4zeJgwcDPy4CP2v8KN31 aZxXlBDqI0DRGkVmdTMwloeAoxWOgyD2M5Lfp0kmYawcAYpWKHphXPRHJCZZIFd0qBwBivYo mkugmweAoT2GmTs1AGQS0LNHLw+iVK0IZB4AhvYYFl5qAMgkoGeP3sQ30WMS0GuBnn42KUXg Z4df9pgWfS8MSCyjwcoRoGiFInuW47jJL3a1CPys8cuToQEfl4CeFXrsu7Po0fXZQ1y5bZpx CDja4phOBmHg3ZFHDWN5BCjaokh/tDspReDXAr9ydMaQgaAVgrSz9vnbOY6floCeNXpsPLX/ 4GclgvoIULRCMSZF7Ko3TkoAdm2wyyrgwfIs0UsjN+2z52D5SZoWgZ89ftTp0p/cgFAdAYqt UCzjmMoRoGiPYvm+sxSBXzv8jmYAPAKCLRDMItMAmQT0rNCj//izR5SP5JZ2xgFgaI9hEkVJ 7LuFa8BYHgOS1kj6hTsISR78SUokjWNA0hrJ0i1rCejZoueXD8daAnp26JUzWTPMYrXHLb+X E7VYApjZYtZnkyw1cEICeq3QK798qBwBiu1QLGd5VA8BR2sc9TRBJQA7e+wmsYHdJAZ29tiZ EywNGQhaI6inVyoB2FljpydXKgHY2WNXcbrS39KTIxI7vTOnF5pTBvk7p6b7sqJpWWLm4f4D mkI0RQXDKqYVwI2T4gU98F4Bbz3HoRRBDo3kQGE60MgBszaY9d0scx81clIEftb4DcPELUr8 hAj8rPGLSFSixwRgZ41dRrwSOyYAuxbYDUlGYo+YCKpDwNEaR765Y4mhEIGfPX7BnyQZGgAK GQg2IviYMgAfU43dYzrn0eQxbflcQkvBQ4kEX4NXAgnDtDHMx5SmFG4siQXN6hc0E9vcuoNc rGfGEoDMBjI/uBeQsQQgs4Es1GYWws6sQdOGFsLSLEDLgnh0MPCiVG5TwVIAzQ60JH1UqLEk YLOC7U+SJRI2ngRsNrANh9IXsAQgs4EsiH3yIEATScBmA1tEIm8st+CRaQBnC5zyozIN4GyB U65UpgGcJXBRck80clwAdJbQ5aTQyLE0gLMBLjPcaga/ag8c/fFcaXEyDeBsgVMBiUwDOFvg VEAi0wDOFjgVkMg0gLMELiSxBo6lAZwlcLHZV2N01hbQVfwDHIQ9dFN3IHFjKbwzbd5BXL0A 1OuziCSgs4auIA+Bwk6kAZ49eGoODk8BuBbABRq4AMC1AS7UwGExSHvgBjlxaSgit4qRAuCz hY+t9pOoLWJEGuDZgld6WPjXVsCNSEHie72AMEsDvBbgJWm5+nKCdfzbgZdPBiZ+UgSEthCO iZvm+rlMSwDQFsDI8LkRfG5L8Eg2kh/piCSgs4UunZReV6YBni14f5SU9wf4rhV0mesHDyV8 pQgI7SGMfYUeTQG4NsAlUQldgi+KW4BHeHQih0K1BADbAJi6aoFCLQFAWwBzY6Agx0BBS/CK bOzmanVMKQC+FvDpQXmZBnitwPvDAO8PgNcOvIlpehPYXlv4TOObwPpawPeYF2oVHpkGeBbg 6W8s2DxGT31kUU5qBHzN8PEJ2zlhs/I8PYFbyACxDYhJWLoPLgC+NvDlaVzCxwTA1wI+f1J2 X5YGeC3AI1mWZBo+IQHAFgBGiU80flwAfC3giz21gKUSAF8r+FT0pwTA1wK+dJDdafi4APha wJeT0vOyNMBrA54R9CHmawteUQYtLA3wWoBXJHfGaBU4rxV4D8Ms0uhxIdkbTILQp+fpITf2 3cx3PIdelrnZ417mxgwnVsq+uxfENEsYyuVBsyQpnN7ImY4Jocci5/j42HFk3sVrhtLze09O qio7XkbcgvjOMMmeKrTn+U8PstX+f3QW328QxAeRe8dw/cf1zYdz+nt1fXn17ponPp5e8d9P l2fi9+b63eWHC56+/fn05uLc8UJCcSEpif2N3ociu9Hyez85qgGFSkHm0BvtZZHTGzr7QkNn YdMwnA/efzr9/HNTnpvPp+9vnaZct799vG3Kwwpae/e+nH8z0VkiX/X/27Oyy7ftebxAsUtH uSXFBphqW6qoAg8i/7WajMlS88gj55fMYRBxogWNqAtacolxUmtAC+m9rVSi1vLqaYjlmEtF ExpH5uCizXMRB7qJjGSmJjaS2erpSGbaBB+x0OHsl5vbi9syaLicX4Fl+7Covev7g8dC7V+p paTLCqmP2USy06rE+qlACd1VZ5DIncZYortqMGpSm0rxZJdVoQ9LA7XNuZY6rhBRc4601GGF sn460fEiT3dYmSJz1f4wMt1hZSZZv5wcqKVOK5SrOECmu6uMT0IVBYhkp1UhBQljrY2QOq3Q NCjVYenuKkMyN5eUJpLdVWU4CcPYjaQ2WuquQiNSKBIQyU6rop8EZLq7ygR+P58MaL+X3saQ u6xUqN5BiGSHVYmDIvektSmhy+rkigZEstOqkKxQsYCWuqtQmMSj0udoqbsK8ZXNxVh4ucZ5 JxW510GaSHZXlZhMtS4y3V1lqFVlodphWgndVmeaBQUpFRJid1VKsyAupnKVCJHurjJsyMkb qwFPLXW4dUx9uq9ORoYZyfX30ULorjq558ay64hkl1XJym9IRLrDypCiIHqWkBQ6rA6bl5BM 9DRtKXVXoSKZeOMkdOXk1VLsuEo6btNShxUyGaHoPCUUeaGsjaU6rEgho2mW6K4ak9grMmld Mj13Gqe41Zy5nOKdjzET62zhTKz6V0hjp3FzePtZo7JWS04dFcrWTtziWebN3CJ+gDmkm5+3 xWBumLUlsjTM2RKZamdsiSx8vlY+ntveHIgwyKk1Lshwz5Znf+vQn/HyhZDI9XJejkitUJSX RFES87Jk0qaw4ZhroG6vL6WlDL3YrkJDr74Mz6KMQR3KtdA1gTEmYWqlxsDbaBVsUCAOewol bIE6fTlhVK7uJPCUBTpjehH9uSPMb0U85nNSN+PvIdMsifgEY0p5Pv9Rz4d6mfc8GNG/MpwX zk8aNatWGMS0nPVPSt6f4/bY/SjN27m9snL8ZauSkh2s6tzmLpI7Egd/kkwFtErsjAbM7pJM BktKmBdj8Fs9jTDY4RYzvUX25Rw/r0Gd22cZnjj9KJ/E8Pib9fgM4zp3L87X+XqRY7GjF+c3 8pXIef/y4uKi/+Hyp49MOL05+7l/eXV+eXNx9vlN8OqH7/vL9C9eYSaQvusl8qW4TCfd1GFo KjHsqhZjU4txZ7WoNMa4m62Rq4Egme6oDkNTiW62BHXyR1oLLnRVi2FFjc62xthUY9xZLSqt 0U2WMl1GVz1GxWF01l+Qh1TpwJLd1GBoqNDJVhhGia904OmO6jA0lehkS4zcKHKVFkLoqhb9 rKJHP+usJsOKIt21q+FMkwy72Sbjx1R9CqmErmoxrKjRScv6/VulA011sv7DUoFutsChVuCw m/UvW+Cwmy2gxzx+j7tZ/7IFujnaEVYCp7CzkVM4EzqFHY6dwmrwFHY3egpnw6ewy/FTmIy0 HjTZTQ0OvzV0OPy2s1oMK2oMO6qHqUUndUiTqVKBJbupwdBQoZOtkJGonwaJfm2h5Q7rMpxV pqst4waxTzJDG3mgy9oMn6jTydbJ6e0GShUhdFWLYUWNbrZGUL7q4+mO6jA0lehmS/yR6YFC nu6oDkNTiQ62xIgU/fG0PwwTteNG5Ujn9Lnr6+lfItlNDYaGCsMu6lCNF+86HC/ezcaLd12O F+/6ehqYSHZTg6GhQjdbQU701noouYO60KorNViymxoMDRU6aFE5nw6p9tmWQle1GFbU6GZr 6E4h0x3VYWgq0cmW8AbqSUOmO6rD0FSimy1BglArwdId1WFoKtHNlkjSxzwYaYbScod1Gc4q 09GWyUs98o5qYDRF3slW0MPPItlNDUwVuqnDQxodaiW40FUthhU1OtkaQ3dQdmwhdFELthgv 0WoIqbN6DKuKdLNFwkTvNS6FrmoxrKjRzdbIyq9mtNRBPYIwGQ2UGkLoqhbDihrdbI08NoYS pNRBPULf7B1S6qIewaB/T7I8SPQjoHmoixolo8NU68KFrmoxrKgx7KgeA0OLQVd1MJuim8wb ucWYZDq+UmIXNUn88pFWCB3UIiYPhTssiG6R8kCXtRk+UaeTrcOWmlea8HRHdRiaSnSyJfgc Qx2cSKmzegyrinSzRYJRPHIjrYkUO6pJMAw8N/ZNbdShbms0nKNSR+2t7P5B3FENjNboZq83 pjF0dBaDOYmhq3MYyiWqZLqjOpgN0cV5PVNjdclpR1eXnJqrS067urrk1FxdctrV1SWnldUl p51dXXJqrC457ejqklNzdclpV1eXnJqrS067urrktLK65LSzq0tOzdUlp11dXXJaWV1y2tnV Jad9zx1o783THdVhaCrRzZYwnHdXfXfFdXfWc/sZiZQSPN1RHYamEp1sCb3i6rSbK65OjRVX px1dcXVqrLg67eiKq1NzxdVpV1dcnZorrk67uuLqtLri6rS7K65OKyuuTju74up0ZsXVaYdX XJ2aK65Ou7ri6rSy4uq0syuuTvWKq9NOrrg6LVdcnXZzxdWpXnF12skVV6fliqvTbq64OtUr rk47ueLqtFxxddrNFVenlRVXp51dcXU6s+LqtMMrrk6rK65Ou7vi6nR2xdVpl1dcnZYrrk67 ueLq1FxxddrVFVenlRVXp51dcXVqrLg67eiKq9NyxdVpN1dcnRorrk47uuLqdHZdz2mX1/Wc PlnXc9rpdT2n5rqe066u6zmtrOs57ey6nlNjXc9pR9f1nJrrek67uq7n1FjXc9rRdT2n5rqe 066u6zntP+qg8PHbbtZ/WCrQzRbQY1GPh92sf9kC3RyLetRjUY9xN+tftoAYi0rn5GV3Uhuf 3zr8vkriKs/VcIMKMY0qtWAamAca9GDTB0s9uPTseog6GXrIOY51evC5d6UiQnx2TWStDFXU HMEaXdh8BK0JF55bD1GjUgs5Y6JGB/4yXyshpOfWQtapVEPNOKjRg41TaTW48NxaiBqVSsiR tHodDr+taMHEHdCD16qiiRhPq9GlfC7X+hiHnlsns3alXpWxhBrdxJOt1kuKz62TqlWpj34C r9OFPY6UqnDp2TURdTIUkc9MC/WQy8lKPZT0vHroOik9yjVva/TgS4BqPYT03HrIOpV6qHVK 6/RQi2eWuugjz65PWTdDJ2O1z1q9clOlfBe0yWcUyRt0kAu8aTWU/Nya6HqVypRr0dXpw9dH K9UR4rNrI2tlKKPWcavRRazKpXWR4nPrompV6qJXD6vRparKbmjyRBELPfiiF1oPIT23HrJO pR5qZY4aPeSCEVoTJT+3LrpepTbl2hZ1+hjrE5RKmQefXbNKDQ31qisr1OpoNliwC60VzDRV 0NROldBsJyKz2cBMxGWDSRD6QTxy1L4jTuRQXTI3e9zL3JgNedF/0b67F8Q0Sxg6vTNWSJYk hdMbOdMxIfRY5BwfHy8YvWJLTe2PHaepsuUdvIV3cGRtFhdGz+89Oanq43gZcQviO8Mke1rb Pc+vHmT38n+sqfkgiKl6d6y5/nF98+Gc/l5dX169u+aJj6dX/PfT5Zn4vbl+d/nhgqdvfz69 uTh3vJBQ2ElK4s3eh8K60fJ7Pzmq9YRKQebQG+1lkdMbOvtCQ2duu3CQD95/Ov38c22Gm8+n 72+d2iy3v328rc3AitjLafv3iPN1fhD5v9J/Rwejr+WBj+e/0n/8wJzLafb9V85bh16y/2rP c4v5mY72WVydBaNx4bxVuWdvejx70+PGmx7X3fR49qbHc276evamrxtv+rrupq9nb8pzr3ls /fLpranlUbs77J/eMm68+PCO/r35eH743bfmofYD7roFPTHYzlPJS9DoWGt0/EI0eq01es00 +nfijRPn63/zCX18Is6Hi6v3lE8Ov/ua0t4qHX4c7nv/Ifo8S3YMOVlracvjsCVQbUiqBOq4 k0Adl0AdtwaqDbGWQL3uJFCvS6Bej8OXQCZZ5NOSJJ8oYZEBHH371ACyICW0nIoN3Fx+uhA1 ZMflifJgfzZDvbGIWnXQXsqKl+C+DKvJx66yGZFsYzH0iqq50Ir2yyNM6utjDbbB7t5By1DV VgC+GKs4LK3icHWrOKyaxaGwi0NLwzjspmEcGoZxqA3DfvBkgxVc0O7Bqx++Y+0nhlhYoiN1 FpQsqi3Tc0eF/HnDQv4S40LlY3KrMaGWpR9vtPTXGyxdBBMbvAEzzrUOx/lLjccJC184IMdP zxuRmxRBiDG5jY/JMZgbRuVEloZxOZGpdmROZOFjc+v2VP/gBnz+4fKns/7t2dntHJpld19w +GB/n/2fP+ZLBgS8kDAZqSURRTJ5uWr2i+LRUJWLL1bdZFJoXVn6xSo6pXm1plx4maqmynjT F2u2OSnSLPGKoAjV5ofmkZdMTZ6bmtTExBetbujmeUVhfuAlq+xOirGpMZdftLcNIlJpY3Hg Jauc3Jn6UullKtvPiTfJSD91lUlXjrxMpScTL6XVki2spRcabGRJSjIdcSjpZSpbMvML5uSM uOE4yYvYjWRsVTkyb1iN1+npwBo7vNzQmmBKWcKGxpBmYqp1jiUJxZcbTeJY1o0nsQzzRpT+ xHDSxoeT/mwYS/qzcSDpz4ZRpD83NIS0FB/8eeD6Icleyf0XlJDsSu28JEozop4PtLQ79cs8 hZ1I7kzNRn8GiagYT+1MvSYxb0UZOklhZ2rnk2FIeVnUTgk7U7siI+oxSiR3pmZ/cofIayaS O1OzIDZaVAm7VLtB+SShpV2qn2F0Wtql+nmJb9RPSLtUv7JnKGGXajd080LXjgvzwv8/58T+ fy4X+FOu8JJ4uKmYnxZP/6411v9z2UD/z9oo/89KiE9/91noG5IHdhKR/uYi/RmoFwX8T7It ivufZJwf/j/JtgNPAbN1YpMZXP0SWArJ7lXy8XGa6bckWpzHXGE8h7rC2OSuhu7PMrfs/8ZJ 9o+NFPTeOo3ZWK2aMg1XKmwGyvn8NJOpQlOjeKLPpyTjjcx+wVeb46tFmC8irsX5FzHY4ivm U9ni/JzTaJ/r5cNmo5GjmeJ/GhQUGbVdduI1k4bBqD/ev/3Z0el8bF+0uIhe3iPhcJ/NIJTl sFLycaXQi4cic72C8YbMM3b+fRoUY+fezQJ3EBInnwzyIiho+JbE+X9sgRAXKWYODLfHtS31 LtFy7K98VcBSCbBajNXoXo7Q3AOnOpyK5E4+wPMUsGrof49lB3wEWnVoJTKITFLgVIdTRkZs pFa9LRQCEKtBzJ8ouHgKWNVgVQ6RbW18rLNYRXL7l2gEnOpwGjwWJJvIoQwlALEaxMYyGh0j Gq3FyZU4ucCpPmZQvQ89rylmT/tjtSmqTAOvGrxy2QNz9MAGu1I2BZxq7clLUvWVCU8CrXq2 8opQsxVLA696vPLHXOPF0sCr7sk5UaMyPAWsarFSs/x4CljVj2GRB+LpMSwuALG6cXeXLVws Bt5duYYx0FrYF8lAzRsdAKna8b44uCdZ7qpBPy0Ctbq3hWEycEMZSCgBiDW8C1P+UabnzRHi ujydJcTfX9vPExLZW84UWgjt3Jk5i3Lv7fVW+m/v7du3zg3RyBRJEuZOTIhPa1AkDj8hEQpI vurdjAlFPzpsDsubuaDlVM2ThXAuPlt7GT9Z9g0ulkWVKdEpZmUt/np4ePOdEJlFiJQ++/Qq 56fL2+ur/u3lx08fLt4sVmrsZuQgCnKPXpQn8X4eRGlIHOfs+uOnyw8XN/3FcEkbY1FNrfqO 8/7srH/x68VZ/9PNxbvLX2uLO6mdaOY4H87Z0u83pze/NVeN5rbNWntb5+r64tfPN6fnF58u rs7fFI5z/dP/fHd98/H0cxt8pGAx4ev84vbz+eXN3HLZ1K2PNNMwCMk+5a1D1k96vActnDk3 op12+CNmzLWYMbeG28wtftmJeLwJbWbgyYw2U+9k1uY5dzIjn2z35s2bt/Thz9vAXqE/n/79 gnaom9OP/Z/ZN8vX/bPTDzTxnipNqej28+nny9vPl2dUr1WcudDmiQsXh1lmqgKbdrf/knUM CpK5RZK9aCXF3PIXrCBLEK940TrekccwyF+2jkzBOPHJi1byIaJ+NfFetI5jNx8XbAb3i9Zy QKNNN8vcxxetJX0i9sMgftlNmRc+yV52FMDG+mg896J1HJGCatEFFZ0efb4qAjGoyOrvqHA7 cXRQmjjiS0BHBTiJo8IA9gGedJaJo1xK4pTEmzglPfGVhkQnThxp6omjDIJWQMCWOE75XGOO v+Vzh+Bev35NdRWVr3tILMvUiebHrOaROJ6tTZEHNJtlsQf8yW7BMELoYwyhy2MIoW8zgBD6 dqMHoW8zdBD6G/3w+OntFp8p+VOOxB1kRej33GRSLHUR3yfAsblU8TUZefnBiCFxfnnVf3/G bOj8gjb2+w8X/bNPH365Zf/owXc3Fxc/3Z73T69/+bya56DVCP2NbnUB+Ovhzx+jQRKiCZ6z BwQD4P+M+NdokI/ROM/bOFM3i4N4lKMRdrSHTNI0yQo0zzM2T5ahezwn/g+DoEAL7ChB8e3S Ijxk7ETzzFbjwEvDSd7zSYT22XT7mEObbP6azwYdxdMfXzaMiWPxq4Muekj698RhXiZxBNex bYTpn7L12Bil7dBk6DtNU5IOGHp7DUM3zYOGoT93VcEipxphsLBrg4WV5mtap1BmalqlUGar X6NQZtrEQKGz7PJ/ok787/qpszWf8HqIv62oQFxX+5aivlXq1+zjWRa+MHBzcECXXxi4uc0L A5bL5oUBy9f8woDl4jwwSX2Xr5FXuNmo56WT/fH+/n55mBbQozYZucXMCbaxyMwhXgSJ78Xh tb8jvbq+6v90c/2fF1d92jbnLHrg7X25QMOmjx7KHHPQEUsGUnI4v/5w3n9/yu52e/n+829v 7pOAbY1MsizJ3rh5f+hSo2IZb3/5qX978f7jxdXn/umHy/dXb47XGoDqWh0UXo9FZJt4EQ2Q FchukQx7ASEEMG8EZpetYwBkN4FsDmA3AyyjhBGJSRZ4gHgjEA8CeiDqeUn6CIQ35d58QLsR aMlDmgHajUA7DBNKCvFmvlAAvhJfkO7m4GVuLZqEMOANIZy5I8S9m8GWTfsGtJuBljz07t1w glGGzeAbxOmk6PHP+AHw5gDOvWwyAMIbQZh9iRPEI6C7EXQjkufuiCB02Ay8ySAvXLYTKtDd BLqTAu5towizLxsB7UagZbuvETyzbQpdPiUO6G4G3Q1+7Q50D6ZZUMChbQbbDa4PA3QPHmi8 AHg3PTWHTUpjM6uB8vIom9NeaR3VlDIq6HlPNM32GKGn1WE19yFxzPf0icPfKScOf/+ZOOW7 OpXmmcx3IFTi4/ViSRH2o8dBE8cYs1OCGF8Sq5KwsZDE0c/tiaOeMWnKeB4Sq5Lwqf8izlSf CeSVxUmErzEXOdF9OHG0obWZDEzRXMN3AbSUxu8C3MWLkfKFZjEvuMvzgnkT2kwNlhltZgfL rM0ThGVGYzFSSkAbXJb09vP5Wf/ni9Pzi5vbN4f0AF8Q6fbzzeXV+/7P5pHzD5c/mUdOP3y4 PjulsnHRxc3N9Q3P8usn1iJv/vlV3UrM//xK5zxcmHXsBtkjzbmSDxOwPvlcShz+cPPtPqDd CLSc0N3NPFQA3/jAC5N8kgHeTcFL48Qw8DbydTYApod9GtbeE8C7IXhZQA5wNwTuiLAPrwDv puDN3AjYbgbb0A0zYLshbMkDoN0MtJva8QDYxgfxJAw3tbQ78I3llBGguxl004zvrQlwNwEu G88niBc2hq4/8UC7G0I3f4wKdwB0N4Pu1M3oXcMQ+G4G3w1OdwK88Qb3FQG6Ct1DwNtqTgi/ 3GGvJBNHvz1LHPWih8/5kO8k2N7oYvg8ccRIL9/zhQ9K0hQbP0scPtRDf8hDue+MftZTMzfY XjQ8ghaTN0jGEzwu4bM3mAvlyzoKtp+7yYxq7nK7GfbmOie+0yPOVwf/59/YRjUHTv5/uYb/ dy5s/5cC9j/qTI2VOXeLanG6ss3vW0eKh+23vxGtYLH9DdPRYk9rVZOaqQ4LrM2m9FUB48Zq VbXZTX+Y+mJqRamh5eY9AuLGuTY8m3E3i9kTLJ9lwQfV6RU2hdvsNqSzLpwn5HmYJLRzk4S4 HXheX+w33WLKEFuJWF5mM3Gokt1m+lDlguZJRJXs5VQieoxyfHu96EX2WvHM9jrx7LYa8cwV ffzsvr0+9CJ7fXhme314dlt9eGZDnzRtq0ya2mrCctqqwfLa6cBymg1y2Lo1Dq2b4rBFOxxa N8JhVYHW9beufovaW1d+BvyWEx2F/uysdRPwzPatwLPbNgTPXNGHLQ/eXiF2lb1GIre9SiK/ rU4it6HUN9+0Veibb2yVYTltFWF57ZRgOSsK0EeNor0S7Cp7RURue2VEfluFRG5jjq2KZ4ff f99SM3qFpVY8p6VGPK+VNjxnqQkVD9trcGivwmEbHQ7tlTic0UI3iQ7HxP6hvdTp/U4f1QPn kD0G0SeiHn0eeu/0rpwg72ckJ9k98fvTJKPPnXeHf3311//qOI1B0rwHpHKPiV5KH3zJvqgA rVGPp/bHewd/cWhwmolFmIOI0Co4h387OTw+OfrO+csBO09bYNHZqkJalzmKfM00Of7r93/9 r1+vrEx6MHp4ULrwj0BW1aN8xA+GtJG9/3rw14P/wyxPiT59qlcZhCgkkUdmWE8bBTFvICE8 7olnzJ5fHmIoK0E5+zK/qYqpx4wSWi1Tj1LXNarCCn2qjXmUKWTI3l7lJCvdpY9QznffO/k4 GBbydZMxiiRBqNyJeOPE+frf1PjUV+6kSHpi5fGvvmYI8++nqOXMZuS75TxE4psmnrcm82yp 41bFzuaWQ2je2M2cv7CPnYIwGPQzd/q//rfzxvl/HXo/tg9LxP7++NVfna9IOHT+ixavfvnw wfn/fmT1UBc3FB25hTcmeeUW0cw9InYT9qd6C+t7kIcic2nZX3214LISI9qzQzce9dSG0wJT LT3JP5yTvS6/Kj9PiadKl+lFZZdZ6X9vF2d/2rxOUW8LZs5oUaZhRsgg95VqizMyMkyyqJJx 7bsJ7S/6HtGWGVa9Xn31WH61eHX6+fLvF2ok/Oz66t3le74N+vnFu9NfPnzufz69eX/xuf/3 i5vby+urN//8ipXVO9r/2+H+d9/xcfCZnB9Pz36+vGIj6AzY3iS+i5Np3JMtwa64tB65YCrI tKXqLbMvRoqR4WpvRqxvNSIxZRG+Us9lzIfxHVm27wyzJOLWeHL01z1n9j9+dh0WcVDtfyfH rxbdTXPupipUonFydHiytz7tNBecvPrbidqg6sT51+0/Lj+f/UzN9z8vbvvUhr9m7z3IMIiJ v5675/fZMb3ra/OuxZiGUPT/Ykwc/oaHUq6TDLmcZuQ+SCa5w2sRsFMbgeH4WxMG9sl1f1tY fPf9ClgwHlRvy8DP4OcWr1YVuejEfrK3rymHhRIUhp44gwAABra1AID+nxUhIoAZOE6OjhAC IARACACGXmMIINilTKkgoDzODo4dTcoIBGBmWwoE3KLIEAZUwDg5eoUgAEHA3CAArAxW3jQr d+XBbNOEjCcykDHIGGT8rGRc7moBQtZYnBwdg5RByiBlkPKzkPIgKCI3BScbUGDyAigZby5A zet9c8EGRNUv+0CbvbswFuGX5CNfZ/DM6+t7nFoj33nLPsiMe7wKmCMBO97eJMnE50vZ4t2I gcbJ0WvEGYgzEGeAn9c5SZKRi040Rhoi+8ZCDVEJxBqw5S3GGtyBI9iowoGpGIg2EG2Aodcd bXCIS55pjjf4BRsMOOSXp4g4YM9bijiGoTvC6MYMGhjdQLyBeAP8vN54g5OLTjRGGyL7xoIN UQnEGrDlrX5kIvZEQLRRwePkbz8g3kC8gYl04Obn+tTEjV18blLBAp+cgJRByiDl5yJlvi9K D18BPkEDxAxixugcCHr9c5zpw7iR1CN0KiSUe1X1muc/s4I2OgV6M1tLwtIRiiwYqyJRUGDg rgIG4hDEIYhDwM7rjUMYt6jfxneEPPPGAg3J+YgyYMfbijLYrhMeAo0neCDWQKyBWAMcveZY Q9CLkWyOOOQlmws6tAtA3AGb3lLckaSMUBF2zMCBqANRB6IOMPR6ow7BLmWqMeaQF2ws5NDs j4gD9rytiGNSpBNEHLNwnPwNX3oj4kDEAYZea8TB2aVMNUcc4oLNRRyK/RFxwJ63FHGkhKSI NypgYHwD0QaiDbDzeqMNxi3qtzHS4Jk3FmdIzkeUATveUpSRES/BAnYzaJwc/w1xBuIMxBng 5zXGGZxcdKIx0hDZNxZqKOJ/8+bNW4eWFsTF+uOOmtrT+61g0U1Xd8eepSZ25vkk87msy9Xp x3YVaRdLNMPd85IoSuJ9buxaShbEFe1xOVg6FLE0FftAZInKrxS6tAC/aTuhVlisOWyxvfeG g5YlIVhfyNISh91a+wCE/sUQepq5o8hVhC4lEPp2CF2BD0IHoYPQQehrIHQ3DEnWy917Ijnd OABa3wqtm00AZgezg9nB7Oth9rzk9BxsvjU2z8Hj4HHwOHh8LTyeRDS3is6lAC7fCpcr6E++ /x5sDjYHm4PNV2bz+J5khWJzIYDNt8PmEvqmfcHA5mBzsDnY3ALuXMXlOWLyLbF4Tpq/+AGD g8HB4GDwZrj9wUMykeG4TIPHt8HjCviT778FlYPKQeWg8lWpnNrcsCRzJYHOt0LnGnzE5iB0 EDoIfXVCZxsXiL3iGKFrCYS+DUIvwT95hZefIHQQOgh9ZUJ/SMNkKulcpEHmWyFzCTxic1A5 qBxUvhYqj4ivqZylQeVbonIO/MnRK1A5qBxUDipfncozTeQZaHxbNJ4hHgeJg8RB4usgcWpC rhwoF0nQ+DZoXMJ+cowhcvA4eBw8vjKP6wHyIYbHt8biYnD88BDf7IPFweJg8ZVZPAn9Hj2a y8mIhgxG3wqjGw1wcozPPUHroHXQ+sq0Pok9ZkKS1JUESt8KpWvwT44Rp4PQQegg9FUJfUSK dCpnscg0yHwbZK6AP8EkFjA5mBxMvjKTh8lAvQCVaTD5VphcAo+pLKByUDmoXFC5yT98X0G3 KLLCHQiCrhx5kTTdjn8Xo3VyDFIFqYJUQarzSJV9o20wKhdBp4twApeCS8Gl4NIFXPpQZK5X oVN5BIxagxZIFaQKUgWpzifVJGWGYXCqPABKXYwVGBWMCkYFoy5g1EmRTiqMKg6AURdjBUYF o4JRwajzGTUlJDX4lItg00U4gUvBpeBScOl8Ls2Il4wMMhUy2HQhUqBT0CnoFHS68vxXmoGM Mrcgin2ViFmw25gFa8CPhTnB6eB0cPrqnP77JJIjEzwFJt8GkwvQT14jMAeJg8RB4quSOG/4 nhvSX8Hl5gFQ+jYovdIEJ9/hOzUwO5gdzL46syepovQE4fm2uJyBji0JQeIgcZD46iSeDPLC 9e4EjysBVL4NKtfQnxxhsAVsDjYHm6/M5mnhDnJJ5iINLt8Kl0vgsQoQqBxUDipfncrTjGbp ZYVc060UQejbIHQDfnA6OB2cDk5fF6cX9I4mqXMZrL49VhcNAFoHrYPWQeur03pG1MrLPAUq 3waVC9Ax2RwkDhIHia+DxPWnmy/4q80dpHHxHSiCcfA4eBw8vgYeH/WMKS2lCD7fDp9r+E8O v/sWpA5SB6mD1FcndS9081xzupBA6VuidAn+ydF3IHQQOggdhL4yoYeJ6ys652mQ+XbIXAB/ 8jfE5qByUDmofD1Ufmhy+SHIfItkfojhc7A52Bxsvh42TzL9GpQlweTbYXIO+8nh4Q8gchA5 iBxEviqRqy+H8M3Q1kgcXwuBwcHgYPC1MbgbuyWLcwFMviUmF9CDzcHmYHOw+epsnvuDRG1c KdPg8m1wuQKe1hlUDioHlYPKV6XyIlJEzlKg8a3QOAf95BVmIILEQeIg8dVJPMl6oftYBuXG AVD6dijdaAKMtIDZwexg9nUw+yQNfEXqPA0+3w6fC+BPjl+DykHloHJQ+YpUXiRpSO4Flcs0 qHwbVK6AxxefoHJQOah8DVSuV73Ferfbo3Gx0i0GzUHiIHGQ+MokPomzJJQzEmUaRL4NIlfA nxwe/w1cDi4Hl4PLV+Tyezdz80hwuUyDy7fB5Qr4kyNQOagcVA4qX5nKSZZTC5JcLoUEBgWD WhLuBy8ZDvXMKC0hPthGfFCCf3L0PSIERAiIEEDoKxK6GwauXD1ZJEHl26ByCTvmtoLHwePg 8dV5fBAUkZsKIpdpMPk2mFwBf3J0CCoHlYPKQeUrUrlPbW54pAdZShGEvg1CN+DHixhwOjgd nL4GTn+Mezk9FMsllA0ZrL4VVjcaAKE6aB20DlpfndbJg0dSGafLNOh8G3SugKekCy4Hl4PL weWrcjn9ld+h8RR4fBs8LkA/OTzGe1CwOFgcLM5Y3KSfEYn1hiUy/SKZuR3lzkPo5BgUCgoF hYJCVwyE0yxh7Co4VwkIh7cRDmvosSY92BxsDjZfx76toyi5J2rnViGAzbezd6uEHoulgc3B 5mDztazNkLmPem0GlgaXb2ltBg48vtgBlYPKQeWrU7nZCzgfclLnKVD6Nij9aQOA3EHuIHeQ +xq2GvHGRO00wpOg9K1sNCJgPzk8+hZEDiLXOAwmQejTK528cGPfzXxHVMChXJ252eNe5saM tuk/cWLf3Xvz5s1bls3P7rfqCOj9VnAETVd3xxFITewcwZPM559uLt5d/krrwHLyWl5e9d+f na1O/s0Qj5MkJ72CRPKDfPPACo5gRsnlHYGlkazVEcxWfiVH0K4JmobfW8GxZm9ge+8Ne4Ml IVifN2iJQ2fCerB519k8GdCgwbsTTK4EsPg2WFxDf3J0DAYHg4PBweBLQEwtaBg8qPmMPA3+ 3gZ/K+BPvkMADvoGfYO+l2IR8kC8SaEmpCsJFL4VCtfgN605DhIHiYPEQeKtdiKZ+2KGFjb/ xQw9oV/MpOkWLTBNlza/hku7YntCDRvDm835xOqcVc2tEVLPS/e9ZcODav2XjQ3smn2NgcFM tVeICuzgrV9ErY36a40FLG+80UBgOeXXFQW0Q2C11+pBTjPwN5zkgb3rXL5S7PpHMPrLZnRh JSDmTREz70QnRz+AmL9wYgaPIjKufaEKDt4QB1u+sgYNg4ZBw18qDav3omDhDbGw3YtnkDBI GCT8pZKwfiMBC3nBFuL0aDxeBOIzjDR1+OC1HK80pvPqeWHluynHUZ8AHW7zXefh8i86D1/G W85D61ec1ZzOEsvLer3UzdgS1EtPJjlcy0ySw21PIzlsGYopoB5PXtfO5Tt8rjkghzswAeTw WWd/HL7EqR+gw03T4fIA9tzJQy+Ihwnoc/kpeC1AbvgKBtQL6gX1fiHU6yVRxB9eQbybIl4F ccN2kaBd0C5o94uh3fieZAV4d6O8KzFu+OIExAviBfF+IcTrEy8E626QdQXAJ0d/A+WCckG5 oNxeUJDMLfBubJOsqzFuWKMOxAviBfF+IcQbuvEIrLtB1hUAN6z2D8oF5YJyvxTKJQ9g3E0y LsMXL9JAuCBcEC4jhDRzR5ELzt0g5yqIQbugXdAuaJdxQvGYklW+/wftWkN88gq0C9oF7b4M 2q18R+gd6u+hqFTO0GeCnDUqkmIiE0vz1+ssod74sDQfh+QJ8sB/ZcjGkpJGEqcFu7Et1eZs YbZNM1zeCl+GEVrb4Jo9fz169N8KPn8tLn/bHn9tDt8C2ZNXtR/mPJen3wFH/6x+/iW6efDr xvi16uId1rOtvK+8E1sC++ky1d4hvXarcSCr6/KhYNPV3YkGpSZ2AeEymesWgfvdW2o5Anbh 6isSzCiz/FO6pTGs9UF9tvLNrtsA7fHk1avah+5WGq35udv23ht+9F4SgvU9fbfEoTMP4CDe bhHvqjcSbO16Bbh6HeOqbTE/OT4E1YPqQfWg+o1S/XqWuQHPLwV405I3IHmQPEgeJL86ya++ oA4ofgm4myangeBB8CB4EPw6CH7lpXvA8Mvg3bSMDygeFA+KB8WvTvGrLhIEfm8NdtOCQSB3 kDvIHeS+OrmvYTki8PsyeDctTQSKB8WD4kHxq1P8iqtwgN7bYo3Rd1A7qB3UvnlqX329D7D7 EnCD4EHwIHgQ/OYJfvWVRUDwS8DdtMoICB4ED4IHwc8uYEKzmh9OJo7+sGa1FU1WXMikRGfB WiaHaTjJ9wZBTrtBz68jUZaxwcDSA/nZKANFfXa7riLZOTeIc+foOycfB8PigJLFxCPsxDAM vCJ33Nh3jo8ccfzJ6f29UUZS5+v/82+CY/4Xbej//Zfffrv4+Onzb1+r+jpv34rUeKt9vxGK FS/vTu9Xqtj16OVy1xkcLWHfOsZb+dvy2fovH6XZmsBaw7Qn1V8pTmvDB01fpreDY82RmvXN NxyqLQvC+mK1tkh0JlgDYXeSsFdlH2ofIfh+m3wvEG+aNAG6B92D7kH366b70M1z8P1W+V5A fnL0GoQPwgfhg/C3Svj3Beh+q3R/zz9p/AFkD7IH2YPst0n2q37fCLZfDvGTV9+C7kH3oHvQ /bbp/gh8v22+PwLhg/BB+CD8rRM+ybJhDMLfJuFLyE+OjkD4IHwQPgh/y4SfZCD8LRM+gxyE D8IH4YPwt034Dx5J8cZ2u4wvMccMHVA+KB+Uv3XKTxHib5nwUx7h44Mr0D3oHnS/VbofZgGJ fRD+NglfYd602hUoH5QPygflr5nymamB8LdJ+ALxps1BQfege9A96H7NdL/iKuVg+6UAxydX IHuQPch+y2QfkWKcYDhnq3yvMMeSaaB8UD4of8uUj/k5W14gEwsqgOpB9aD656B6Cg7Yfrts zyHH7BwQPggfhL9lws9ImoDvt8n3AnHE96B70D3oftt0XxQB6H6rdM8RR3QPugfdg+63TPc5 cTNvDMLfJuErzPF1LSgflA/K3zrlR25cBB42Pdky62vYT46+B/GD+EH8IP6tEj8lOFD+Nimf AY6BHZA9yB5kv22yT8kUbL9VtueIYxdb0D3oHnS/ZbrHrMxt072alIlFkUH3oHvQ/Xbp/jEl 3h0If6uELzE/eQXKB+WD8kH5z0D52NzwGTj/CAsrgPRB+iD9rZP+Q0aGYPxtMr5AHC9tQfeg e9B9G7p3enlBjYg2TeLIwp3UzXKyT2U3DNlP6OY5+70v6F+2c7b8OaK/Yl9V/ptk7FdswsQS KZPlku2Jw5fyTRy2xmPiyJW/EodnFUsFJA7/hJT+sE+LEkdOOGcJNQeRpimP0r/spWXiyMvk EIdKsFpxPkyclmwdxAWzfJHad/fevHnz1vG++WaLneibb5buQA2XdqXzCDVsusJszvMPp1fv +7efLs4u312e9c9vqHY3qwc9TbjSf8sHO1Udlg107Jp+jUHOTLVXCHCs0D15VbcAeBvt1xrU WN54owHNcsqvK5hph0BHAhlwcOc4mD4Cjb75hoYFoOLNUbEJcv0OPGBkMDIYufOMXHk2/OYb h8ViiaM4wObxSlfGz+7loxVNGY9WlKiLrRoSu+EKxtR4eXcMSqliZ1RPc59/PL28oj+XV/33 Z2c0sVCBNbh/C9zZg3zPJxGNAGBQMKiVDWpEimSVJaKfqrh8TGlrJWuNK59Uf6XY0h7wpqf9 dmCsOb60vvmGY8xlQVhfnNkWic7EmmD0F83oh6D0LVP6YdMWjuD0L5HTiTdOnK+CuHAeHh77 k7zvT6Lo8cevnLe04/eoICP5W6eU+TVfH/zlH6c3V5dX70+cz+ymoi/njjspkog9sbph+OiM SEwytyD+f/nLwdfO20nskyz3kox9chQMnVFGUqdv3lrfJ3feOgc+uT+IJ2Ho/Mg0iB2nrC/V JiWxn/fLMp03ziGreuU2P9KLwpw0X/rtvEuHwV4WOb1hqX5ZQThEOETuECtWDaOAUcyO2rH7 OeXgSOLIxyyVOKQpw4gSxxGDc37iicTw+++3Z1j0ZssaVdOlHTEoqYaFMT3JuZmXb424rjIB YkaHJcNpy6ZfXyg9W+3lw2g7dGuHRFppv87Q2fbGmwybl1R+TSFzSwS6MQQCDu4eBw8PRt9/ v9L8BzBxC4xPjr8HH4OPwcfg40VccU+fqKiZbPOpHIbyPIZiPnHTctU8GeksEkeZgsWMmbJa c2fM0NOHW7WnwxUM6vCFWNShvUm1zVpDIGv5YtPiPgfMoa0SNR6uJ2w83HrceLi+wLERZFn6 7ydHrzdRfJolv7MQ8ttNFC4MpHbNsHbtt+aY93AXgt7D5416D19k2Avv8+K9D2cueB94n3oD gfeB91HeRz1swQvBC819BKfGwv+wpQUYeyR7+zyIXYmH8iLrHRb7tBxHJn9XifG6yj8qyz9S 5R+tsfxhosunyd9VYm3lB2X5gSo/WGP58R+6fJr8XSXWVn6S6vJp8neVWF/5Zfsmqn0T1r4I qkFnawyqB66PmBoxdb19sPAXITVCavge+J51+p6ggO+B76m3j9qFieF74Hvge+B7luCWEM89 8D0N9nHy6gf4Hvge+B74nnX6Hi+J4Hvge+rt4+QH+B74Hvge+J61+h7fLVw4HzifBgPBqBu8 D7wPvM+avQ/5YxLcw/3A/TRZyMmr1/A/8D/wP/A/a/U/bKcxuB+4n3oDwdMPvA+8D7zPmr3P KEwGbgj/A//TaCJ4/oEHggeCB1qzBwqiNAw8eCB4oEYTwTMQPBA8EDzQuj1QPEzgf+B/Ggzk 5NV38D7wPvA+8D7r9T70SAz/A//TaCK129DBA8EDwQPBA7Wnl9AdwP3A/dTbB55+4Hvge+B7 1u17yAN8D3xPvX1g+WT4Hvge+J41+57IDalBwP3A/TSaCGYewAPBA8EDrdkDxW5E4H/gfxoM BN4H3gfeB95n3ZuXuVkO9wP302ghGH+D/4H/gf9Zs/+hl8H7wPvU28fJq0P4Hvge+B74nrX6 HmzzA9dTbx4nf8Nsa3geeB54njV7Hix2DdfTYB9Yawe+B74Hvmftvgdf+sD3NNjHyd++he+B 74Hvge9Zr+/B2x74ngb7OPnub/A98D3wPfA96/U92FkbvqfBPjDmBt8D3wPfs3bfgznW8D0N 9nFyjJ214Xvge+B71ux7kswdwf3A/TSaCJ5+4IHggeCB1u6BUrgfuJ96+zh5hZnW8D3wPfA9 a/Y92FgbvqfBPrC2DnwPfA98z9p9Tw7fA99Tbx947oHvge+B71m778HiBvA9DfaB5x74Hvge +J61+54JfA98T719nBxhLzn4Hvge+J41+557+B74nnr7wHMPfA98D3zP2n3PFL4HvqfePvC+ B74Hvge+Z92+5zEaJCHcD9xPo4lgJx94IHggeKA1e6DCzUYEkw7ggZpN5OR77OcDDwQPBA+0 Xg+U4DtTuJ8G+8C7H/ge+B74nnX7nscUS7zB+TQZCMbe4H3gfeB91ux97kmWU7OiDgiGBcNa o2FNxyRDXIO4ptFCTl4hsEFgg8AG/qfqf5xeXlCjoa2ROKxgZ+D6+4kzCAr2N2RpL4noX98t XPpD/pgE9+z3Ic3ozyhMBm5IE0GUhoHHEvEw4T+0SjFNhO6A/SUP9G/khtR8aCJ2I0J/UjfL +S8jwMSh9WN/C/7H5X8H/K847PO/hP/l66GyRMr/Zvxvzv+Kyyf87z3/O2V/xeSKxJHvuGgi Ydfyx77EUQFa4gi+TJw2Pogqy7qISO27e2/evHnL0PQTT6RVq2qJ5tNpP7uX6TTdC2Kqehiy uKCXs0bJkqRweiNWL0IPR87r169p09K8zsLGpXUhD0Tf+9C+VO/QutQWhS4uk2K5V3dSEMXb 2gJoC2hNaZY2ytLs9iim4SQvCz+bW/Lx8bGz0F3LMhqYLWV984A8eCTlZL6O0mIyXVc5++O1 lMT6HaMKx2miqIPRN9+0aVNWBdtGbVPyN9+sYsb06kYzprWpzXB2ZlWGUo0+EBRt1GP561Xk JWtSowRnXTzNa1E0o9Q2RdqS1XJUrNlTEZ5JMhVS0MZUgf4pWqWSi6vV5HZ0gOBlxC3Yk16S OU2ZK8pa3IFmsy1/Fj6L0mk229IrDdJYNPWJVuWajdtc30PLypaG0lymZZEVk7OoKfNnlpV9 YsQWxXNqtSy/2jEaC6f8aFXwbCezKJjzmmXh1Y7bVDjNY1VwhQQs4kqrQquEYhOt2hZbpSeL km1xkCV6fjUH5Wr2j0YHP9Z7t8i9o4+c5/RJ+8M5/b26vrx6d80TH0+v+O+nyzPxe3P97vLD BU/f/nx6c3HueCFxY5+kJPZ/dDZ4H+q7Nlp+7ydHusg13GZu8QKpIHMYR2SR0xs6+wK4+Q9F ZfsdvP90+vnn5lw3n0/f3zrN+W5/+3jbnIsVtke8ceJ8/W/qufZ/VMca337tUM6Qg4RP8tJs elSH5Vyc9atqsV+xYov6zGbOaFEmlz628jx1mXQdmzKmJKPdMKpkZM9RGx37MVqkedym/aV8 SKM31M9FNDQ8v7zqv2dBscUw+/mHfjQJ8+AViyhlkj7lt9dAZDhcOObOh9BfWY3ktkDMfuhc j4Qfrq8OWuenG9C01mHl0eM2d1z7qPEK6q4yWryEziuPEn/ZZDHxg3vFFjINugBdgC5AF/Po wmALkAXIAmQBsqiJLaLE17GFSIMuQBegC9DF3HGLki1AFiALkAXIYjFZhPk4U2wh06AL0AXo AnQxjy5cgy5c0AXoAnQBuqili9CgC7xEBV2ALkAXNW9F/KF+K0KTIAuQBcgCZLFgepYiC5EE WYAsQBYgi3lkEZORPzziZCGSIAuQBcgCZDF31ML3VWQhkiALkAXIAmQxjyzyyUCRhUiCLEAW IAuQxTyyGAYP/jAPOFvINOgCdAG6AF0soIvcoIscdAG6AF2ALhbRRZi4RR74Q0EYSgJlgDJA GaCMGsrIK5SRgzJAGaAMUMZcyiiySez5w1y+Ti1FkAZIA6QB0phHGuShILGfD9UkDEMGbYA2 QBugjQUzMfJyJkaOl6sgC5AFyGLhHM+8nOOJBxKQBcgCZLF42lZeTttCZAGyAFmALGpWAi8/ NQNZgCxAFiCLmqV9y4/YQRYgC5AFyGLRe5E/9BuRP/AuBFQBqgBVLBzeLL9gB1WAKkAVoIoF VDEqFFXwFKgCVAGqAFXMpQodVYwQVYAqQBWgioVbBeioIkRUAaoAVYAqFlKFjipCRBWgClAF qGLxG5BcvwHBnE1QBagCVLHwDUg5vxtUAaoAVYAqFr4ByfUbEFAFqAJUAapY+AZEUwWiClAF qAJUsfgNSK7fgIAqQBWgClDFwjcgmioQVYAqQBWgirqNDINyI8OVtkg+2lmyKDbHFkeMLV6B LcAWX8geyUG5RzLYAmwBtgBbLIotEl/HFjwJtgBbgC3AFnPZYmIEFxNEF+AL8AX4oo4vjPBi gvgCfAG+AF/Ur9DrB3qFXpoEW4AtwBZgi/mvUPNxpqILmQZfgC/AF+CL+ZuF5GP9IlWmwRfg C/AF+GIRX2QGXyC+AF+AL8AXi/dKHuZq9EIkwRZgC7AF2GLhu9T+tE954l6/T5UyeAO8Ad4A byzkDf4q9VjThhDBGmANsAZYYy5reFGqnk1EEmwBtgBbgC3mxxgGXUzAF+AL8AX4om7kM0zc wg/8oRj8VBI4A5wBzgBn1HFGXuGMHJwBzgBngDMWcEbwMIlzf5gHgjS0CNYAa4A1wBo1rJFX WSMHa4A1wBpgjaZYw6/GGj5YA6wB1gBrLGQNkzLAF+AL8AX4ovHZxK8+m4A1wBpgDbDGYtYw KQN8Ab4AX4Av6vjiweCLB/AF+AJ8Ab6ofyp5qD6VgDXAGmANsEbTjK6HyoyuB8zoAmeAM8AZ 9ZFGXo00MDcDrAHWAGssZo3CeDgp8GQCvgBfgC/qo4yiOp4B1gBrgDXAGk3jGUVlPKPAeAY4 A5wBzpjPGX1aSn/gRSnnDC2BM8AZ4AxwxlzOuHczNxvlnDFkGnwBvgBfgC/mxxj+JIoeRYDB k2ALsAXYAmwxly1ImgWxHMOQafAF+AJ8Ab6YyxeDAaeKwQAsAZYAS4Al5rJEPi5cQRQ8Ba4A V4ArwBXz9x4IiZv1PdejCPENCEoZvAHeAG+AN+byRpG5UZqEtCk4bZQiWAOsAdYAa8x/OxK5 QSxejrAUuAJcAa4AV8x/N/IQFOLFCE2AKcAUYAowxfwxjCLJxAwtngJXgCvAFeCK+VHFWMQU Y7AEWAIsAZaYyxLpJBPjmiwBpgBTgCnmM8U333CqaOxVByOW80tllGXqmrLLnV6c5IVPUww+ SkxJ2o/JlFOTSC5FTrRweunhvuehBZ+nBePCaMO4QCt2rxXvjY54v1pPPEIbPl8bll3xftW+ iHZ8pnb0SUgKotpRSGjHTrZj2R25gFbsIKvSltOcStNow262oeEZ19MXv+BBJW8J6IaZG5F9 jzWCSCZf0mCS1P7k1TGGkr6UoSQw/DYY3luOxosgHib7HucjkU7Qat1otSOz2Y7Qbh1oNzai JBqNjy2hxXa+xXStZbuVcrI3mAQhLX7k5IUb+27mO0xbWmrmZo97mRuzBhA32Xf3gphmC0P+ 0JM4WZLQQHzkTMeEPVdFzvHxMQ2rVG5nIS40x96Tk1WNHC8jbsHiyCRbpPWe55en6O/+IIgP 3OzHxTdmGSL3jr1LpUHHh3P6e3V9efXumic+nl7x30+XZ+L35vrd5YcLnr79+fTm4txhX6HF PklJ7P/obPA+FOSNlt/7yZFtuYbbzC1eIBVkDi14L4to53H2BXBP71e23cH7T6eff67PcfP5 9P2tU5/n9rePt/U5WCEbfPArb+X0/sG6jNP2acyorJsy3Pa9ztQ361JdvXFwT7pTYcbwJC5y WuP60ycOeyifxB5/wvmXOvH1SdN1P1Sezv6b97XzGJDQz50kDh+d0M0L58jxg1FQ5OzB6ZFQ vYLYySlG/IkqJHlXwJQj8p1pfPJQZK5XdKfCUZB7Hapt0iUm4Otydae6GUlD19tFfJ0eDYWK gAe19Erpblma/xEOInE0RSaOfpOnOmTicEunPwnPK9qGxshS6cRxKtFzPjeAfv36Na2xm9WG zuSBeAduMin2agKc+fFzeX5u7EziewTPXQ2eaeM1Rc88S1P4zDPVx888y0YC6NVIhtWL/tsA wyzHJbQu7F+rzs+uqbOpvbpWqe/1NMPcbh+SB6Y6un5Xu75swKbur7M1UYDOWE8DOtsGn6Xb UoCqE/3HP+Tn/VAJye5V8vFxmrmprqYU543LhfGcYbkwbjEqxzK3HJQzTrJ/IS2g99ZpzMZq 1ZRpuFJhM1DWE5/MNJf8oru+F/k5yK+r5CcbsIn8dLYm8tMZ68lPZ+Pk9+gyZllsXgf0EeFx z0udx3228KHnbOYZfn/es5CqgnhBIHtVLt9gfPzP/tnH89vlYy5Vuvx9YVol4m3PC9NqUgRh R3Xi/YbyudOjTi6s6W+R3y+ovwqdt45Kd1PhzlbefBKSpapf+kSkelbiCGtMHD6KotSlj0y9 MLR+alLlL/fkpK6uDSJkprlBRBwhfuhq/BBHTaEDy9EUNbA89QEDy7GJB6WlvQGtUBytn1da c0Mc0f9bjZHE0aoDpLSE2s4eR3P7uXjwQl/val8X7dfU31Wupj6v8tX3e5VrSxMO5NjAwjPM q7vZ8qxhlrLVl+dbUowPvLwkhbb2BnZL+oifl6RRkUy8cecUMl24LLd8VSp6kX4pKtsscYSq bXy9LHpFfy9LqfX5Is9cv58XWZDC7XfV7fPma/L6MlOT05fZ6n2+zLRT4b6oE/+7A0E/r4f4 y+nAS52elJ3IfRyQPk+nxN+be7DhnQfnjuoldhQiANqrb9l6HhElmDTCpi2rs/QfH/AAm+wc m7x58+Yte09GzSErHpvIZV6jHuirF7FN01WL6Kfpuvl81HQVJyil9mDoL6szvbStwvySttry i9qpyi+p6JmkXuKTfFld5eVt9dWXtdVZX9hOb31ZtY1ljqUbWqXbtra+rnWT6ytbtru+rgTA 9f3siO0FspT6+upWyhtXtVLduK6F4sZVhtrZcvpm7RTN2mqYtVMtq+iUq98DN++zz4uX01Ff 3k5X47J2OhsXttHduMzoz0vydUuubs3TLTm6ws9xtJROiwfxF2ZvpdPi4f2F2UudaHYvSZcL KOS1rbTT17RSUV/VQk99TUVZfxKlyyrLrm2rrLimrbLiqnbKimtKZeWQwTK61g9F117SStP6 QeraS0o98+DP5Xwmu7CVjuKCVhqKS1roJy4wtKMPbPFouZhIXttOR3VNOzXVVW00VddUlU2X VjVtrWi6hJppayUrvdJPvNlnuXUPrZ7331/90r+9/uXmjD5SXvZmZ1PUP3jZ55RzMNhDDPP+ 7S588lG4zrbk/NVVbllmc7PR/b781oamEjTODjXOwM1JrFd30hIaaZcayRsnSU56BYnkzHHz AJpqp5oqiT23kK0k0mignWqgNJzkPZ9Eso20iGbapWYa+pFbsLfkfNFBKaCJdqqJYrOJYjTR 7jXRiBQUd9FCMo0G2r0GOjRb6BBNtGtNlE3iIlDPSIaMhtqlhhqTB9FCLIGm2alQIUzcYphk kXo0Mg+gqXapqejd3JDiKdpJS2ik3WqkvHC9O9VGQkAT7VIT5anrkVy0kEyjgXaqgYqMZFmS 7av5qUJCI+1YI+XBKHZD3UpSRDPtUjM9uAV5CGRspwQ00U41kdFAaJ7da57IiLqVgCbaqSai 3sefyDewSkAT7VoTGUHdA6K6nWymIM7/mMjhVJmetwKehOrpKnjixL5b+ZQlJ77TI05+cHV1 8OroYORYfSpSW2OWgYTDh4de4WYjUuyPnbcOPfDqSB8Qtx2u6WasVPEeLSf+msqUW6LRJK18 eYPxzvSINqbNtLAssn2/aYSzVPX84t3pLx8+9/9+cfb5+uYNvbLP7YLP2e/fEwrt+c+nf7/o zztzuZaGpXe4vfhA798/vTn7+fIzTf1yc3H75ivnv7Ob8tuxD7S/KjPS2urz1Up9tS4isDPJ dCL28pNTMKSUwCRhks9kkoLVS6M0ZJglzPJZzdKwSBgjjPE5jTEM4jttjlyAQcIgn8sg9XJk 4uMSuRgRDBIG+YwGOcnUa18twSRhks9lkvSf/LaLJmCIMMRnM8QgdrNHaYsiDXOEOT7bGKTr jWXkKJIwRhjjsxljMhyOSKw+GxUCDBIG+XwGmZFhECqCVBJMEib5jKOPeuQRhghDfDZDrHzH tGufMMEcvzRzHLu5/Aafp2CKMMXnMsVAf4Ib7NY3uDDFL84UY/W1A0/BFGGKz2WKIp/e8hvv YWCOz2uO8R3JlDnyNMwR5vhc5piktEQ5YUKmYY4wx+cyx4zorzBFEsYIY3wuY8yJxzZNl2sf SAEGCYN8NoPMiCRHnoIpwhSfzRQLd9DLHyO1xJIWYZQwyuc0SsMgYYwwxmc0xpIcwYswxec0 RbFahrRGJcAgYZDPZpDkTr+rlmmYI8zxuczRn7rZUH7nL9PzFkRiSj5dDYm9UHSf7Ha9K8Ys 69Mi6xKGalxpY6zMPvprLXs5LRvMeT0G2Kb+HPCeH0hPraUE5gRzWsKcqO30BhM5b1sJMCYY 05LG5OY5iQbqsxTzwDx3qRR/6jLlGXMFQXm3vUeXWacvvt9P3SxnN2v28ipdj1y5t70o+XEv JA9Or3A2cAda8n7ovHVEytud6Fam2+RdJna1wqvU5vPpzfuLz2/++RV3epP4Lk6mcW+YETLI fRob/pOFjX+/uLm9vL6iuY72/7Z/+M+v1leTZWFZRz+VJiJsPtytZyFYy+5Zi6JFgyNhMbCY FR6S2zq3XK3DLZKwPljf1qxvMPGSSG4fLNOwP9jf1uzPJ4PJSD4B8SSsD9a3Netj60BE9OFZ fv+sJNggbHBrNhgQonaPYCnYHmxva7aX+Wx9JvmFgEjD/mB/W7Q/fzBS5seSsD5Y39asb5cn uML6Xrr1TTPD/pQAC4QFbs0C70mW6y/ylDB3qpZSes58LXlKvX12fT87CoOY7IYh6+rY52xr xJULrfcotK+HrcFZ1kOX56zF6lretcy/Ky/xYSGrWYjTozRRBOL9lcaybOaE5vgwW9GwTH7Q YLLD7K88ovYWDUVC0ku2I1aTWWRpbSfZmgwka20Z2Zq8XmNBtIHXRDyZ9fvVnaEaGE1XjCZO ip4IcmA8X4jxVBxZRv+nrsswgzX7sVz9Hrg5nyG7I1am69Miq4S+leHNXrwGG7QvcuTmay5O bky9xlLnPsauiQXbqeam6c6QIMwT5jlrnjmsE9a5s9ZZJMPeiMQkCzzYKex0V+1UqCbMVcxI ga3CVnfTVgcBLSXqeUn6CDOFme4wpfqwT9jnrtonEXP/YKAw0B010Ic0g33CPnfVPodhgjgU ZtoRM71L4ryAncJOd9xOo0kIM4WZ7q6ZZu4Ir5xgoDtroGIPXdgn7HM37TOI00nRYx/bw0ph pbttpbmXTQYwU5jprpppGORFEI9gojDR3TXRgmRuCBOFie6qiUaulyUwUBjozhooyXN3RDDu BBvdWRtNJgUe7GGmu26mGXExLQ/2ubP2mWO8Cda5u9Yp1qyCgcJAd9RAJ4Oc4AU9THSHTfQx GiQhTBQmurMmOs2CAk/xMNCdNVCfpASf18FCd/jrpTG1QRgoDHTHl3ygt+yREB+CwlJ33VIL r8cugaXCUtdlqZVFH3OHLXXHEuyPuXCTFMUGTY65/kji8GUeEkd8TU9/2UfLiWN+G6ol8Qme FvmXTlTiH5QkDp+3nzjG9GgliFmoiaMm+7GUmFOVOGLqCv1VMwQSx3wRmzj8fVfi5KwAucmA owbJaEqORbAtCNgjH9uGj0fWVBMewNDipINIHNUB1VqYc5e8nLvqpXlKb+EeypTct9zfI944 cb6iEFLlYnqgTyhEtHmSuP8wJFm/eEwJPxwOuV2U53/8ymElMLnHUNofy8L+zSdDtiD1xcdf Ppx+phbS/3B5+9lx/vvcYv7qfEsLmi3J2EU99EeZGzVvou7X9wJ6Xpb0uEfie+fD5U/9T6ef f37zlWCnYEDtNx+vfhdqwNR4grTI99dQnLOwPzFqdRZsydD6uKMaxvnqqzK9IPeObJhhu+OF b1NU2200fNvdM84v3p3+8uFzX/cGypcKYL5zhtX2GrdnN5efPp9f3tB8dRbhu4Vrs/dGs93Z Rh1EKbMrMQLsYifsYg1s7WVkCKuCVa3Zqookg1XBqtZrVSx4hVXBqtZsVQ8pjApGtV6j2qXZ 4rCqnbAqNcYCo4BRrJNqQpd/Jx2SB6dXOGspkTzsh3zgkaVgsDBYk8VgE7CJtZNY5AYxrApW tWarCnIPVgWrWq9V3ROMbcKo1mxUOzUzHWb1QsyKPOQTjG7CqtZqVVEWwKRgUvPmGtJryrkq TOTTC3iCvRFO5Aw0kXhI+a+czyeHR1mCj2glcqiB/fKnQ55gAT1LsBiM/arZfZLpEocZp7mn td2+1XG0G/YcRxZZ2tqpuGL12bXlnW03MW+6sy5oPdxlezuacVcIDA1uySwUqDha82719N5s IvNuWIKsjG2+tjZhXLa6YczUwdY6rOqwZk5odU+Ve1fYATaxAzYRJwXloSxIYRVdtgrTmSgE VXen7kU38tpdjD+J0p0xHFYZ23xLGI66bC2GY9ahheE012H9dGJ/T5V7h8gENvHcNpFm/mAE i+iyRcy4F46g6uqJIxrY0rU8+ZCwrdPJ3JjKu2FNoi6W2draUnnV6qZUrYGtJdnUYL2FDdc1 0tum6gfuzrzyhEG9CIMK8p7ID7v6wu3K9JyyEVw2uF9ayHofyfLgT7IbJsdqYpWprbmpa1Y3 NvPuttbRfPc1B9v2N+RZd4Vx0Pyt+YFDxttwzZxAKxiP8h2xC1EZ23ytraO8bA0GUq2DtY3Y 1GHdLNHmnir3znAFbGJV6pAIqoZdP4Gku2MqqV2uZcwkXZ+RpMuYSLp10ki7+fIQdvBMdkAf XHbqfSEMYXmPkRrvCHW7rs11eKm8SeQ+Dkifp1Pi7809yP2Mn3hyWTlVmhbpjXS6ugJdWU1x wPX97CgMYrIXxFTdMGT238v5A3iSFE5v5EzHhNDDkfP69WuKnL6idqk08kC8A7Z2mbhLZl98 1qZcpYVeR9H+PnmL+4S+dbkNS8jpcs3y5hR2fHzMypIr2x3oiZQPcw8O4rmH5x/N5h7N5x6d OE2zSw/0ZXr6pC1UcdSiCdQELdvC1Xv9Vnfg7+db3IG/2rG/g3wZY3sDOQJmXz4fzrItnT8/ tyhbPhZbFy9j7HZ3SJv6BS+8yoZWtxDuoSROSre9tMHR03xN/ozXla07KZN73jhKfMf95kEf WSNFKy5dxH2Kq1RHrHScio2b5liaTqWhjTZZ5G6eAD9/crl2dl5G3II22DDJHMtrKnhZ3485 2lY3m9ca1ndTr2Zb3XFhm9srqYKMdpousC2725bO3/6mT+3X8l5Zm5ss7hWWdyuXum5x16d9 z7L5Wtln2aPtSqeO1b70WZ6wu4Vyr/b3mctD1jfjnrbVzZ7wnN29pNO1v9UTFrW7D3e/9nd5 ys+Wt5FuuMWdnvK//a3SljcyfIvdTWjOFrfgnt4vM6kME/p8x+j3x8WxA8sWuXfsQfsf1zcf zunv1fXl1btrnvh4esV/P12eid+b63eXHy54+vbn05uLc8cLiRuLlcZ/dDZ4HxpjbLT83k8q lFnDbeYWL5AKMsYKe1nk9IbOvgDu6f1mW/DgPVtU3CbfzefT97eOTc7b3z7e2uRjBa57WKf1 ENWTaqnE+oecWo+aqKroBBsusX6C0FfXGd1eYzvNp4vZXHNpghZLL4rcAjzRVZ7QTdhEFEbG JqYwstZThZFxE1zR+wfrRkszRlk7ndrAMLV9HWemzYoalalW3FFe3448TDMtn3V6b+sNWt+t ocBsbSXl6yrJ++abYRAW6ypu5A/WVRT7Tn89JbEPa9dTkv7cam3Fien16ylOTVtcT2liStKa ylJTFtZX3EqoPaHA+iChLGmvt9J/e2/fvnVuyGAShD4FhPlkJynGJHOKJAlzJybEp5UoEodn cegptjuMM02y0F/13kaE86PDt+KZC19ONT5ZCOzis7WX8ZOlD+FiWVSZEs5jVtbir4eHN98J kRG/SOmzT69yfrq8vb7q315+/PTh4s1ipcZuRg7YghL0ojyJ9/MgSkPqkc6uP36icchNfzFc xjhzrfqO8/7srH/x68VZ/9PNxbvLX2uLO6k7eeA4H877Hy5/ujm9+a25ao5jnbX2ts7V9cWv n29Ozy8+XVydvykc5/qn//nu+ubj6ec2+EjBIkQ8v7jlS5zMy8mCv480E18xhEYQh6LH9Hg/ qgTz3MttNoTvnfd/+uWStsnn6+sPt1uL6Gduu/EAv3q7Mt5vFZjL5lgUjuvTi4JwnWF+6K1P by7g7v1D+ozWkbeqnLe5SLtd5cyQ22NesGWY7S0KsOcG11L9+b5WnnzaddkLNXTeHeq8rEFq u6/IUNuBRZaaLiwy7Gwn5tXjf3ewI/NX0KJyrTozv65ldxb3Wtih2emnXTpFf96h/pzWdua0 oSentd043VAfPv/7x/7pFcPg3Tsanp+dnv180b/97ers55vrq8v/hwG0jm6e0v83MXVzW7Xn b8E6o0CFxFL6P6UvoUErGkvbclhaQ2DpE/byaU7w1+7wF2uPOgYT5+s4TORYzGLi/K7GIrx2 7M9uRCJzqxeTYsdreO9mj7sXyrGq8T9sWSqJYeLwurKJ5yFjR2ti5IW1o0Z+yUJyZGef0iMe 1naJHGuf1PyGxzS/9hnN3+EHNFo3N9vIJ5vrqZyXxPc7Xbl+4Q52toI+e+qed/DEuYyd4ST2 iiCJnX/5fj+Ivz6Zn/Xo9eGJM3WzOIhHJ04+GY1IXjjkIQ0DLyicQeZ6JGevYtz7JPAdNxoE o0kyyZ1/kTAnX+8oNBva5mY9lUuTPGAts4OOljZwxr8E5j1T/PA+wM6xtcTFauNagzZPJH7b URW/ZkjFfzqeQrxxAqe7O06XtUed2xXn6xyvyLHY9Yrzu+p8ee3Yn93r56xW/E+rDsyvateF +SULOzE7+7QbP6QZuvEOdWPaHrXdmJ+v7cY8R0035ud5N350aU/hFkqP7XtPLYP/2X/ckf4u arlzvZvWSlStVe9mV7Xs3eySxb2bnn3Su8dJXsRuhKHDHerhqk3qenmZp66nl7kW9/Yyz646 bl1Dldi9Lq5qphOturq+ul1315ct7PIqx5NuH8bo8LvT4cO4rquzs3WdnJ1f3L3Z2V3t2CH7 f/c6cxjT/1t1YHpFu65LL1jYacP4aXfN0V13qLvmtd01b+iueW13zXe4u+YH3ka2hVhP3VgH 7g9Dd1fH19kn87tbtTQL4mJ2/Lo8PjOEzY8WQURmh7GNK46O/2aMZP/rv3lfO48BCf3cSeLw 0QndvHCOHD8YBQU9NHQeiZvRPunkFAOH60jyHQWLveDcQb+VOx7fy8HoCewo392BtYmYt9LO s+VtPVte49meToGP7ijxwrntjnPjDVLn32SGOhcnsyz2cjLDrjo6UT3+d/d6Oa+W+NuqJ4vr 2nVmcc3C/sxPP+3S9+jPO9Sf72s7831DT76v7cb3O9yH7+n/O9h77+n/S8ySote17Lr3Nf32 /kmnzSJ02t3ptFlU12nZ2bpOy84v7rTs7K52Wlq3LNrNR6RM7DS9e4+Zlc1pIvr/7AOAfYiQ RS1JJosWk0wWPSGZguT44HWHaIa1Rx3RiPN1VCNyLCYbcX5X6YbXjv3ZTcrh1UtSkrlFku0g 27D68T+UZMpqtiEcXoI95cgTB/9r4SIbCra9hda4mLD4dSZljdyI5AeeS3IXQxQ7Qltmmyyi rmqeRfRVzTWfwqp5dmixrErFxI85djv39Mn35nhsRopJFjvFY0rY4Ou/IjeIv3aCnO0z7vwr iIuvd2TNLVF9+SOenKIFy3FztTW7zEcjS4rDV2xp7IWVENl5vsVEVr2VqmR9mXu19rVg/VAj xxxyonmLSUzY0kNsyRGw1C6x1Ezj1NPVk8z1vPUkex2BPcm8c0w2W0P5+5TTFmY8OXz1Qxfp TSqgfuvDpxnWUdcuRzszUNbxz0zWKhEZKxy70ztQ0I5QULVZFpLPbLaFtDObcQHhzGbjVFPu b7HmPjecxHkwionf88ZsHcvLRRWpOfV0Jw2e//zn079f9M+ur95dvu//TOX3p//4T/pzfvGO Lyv2z6/2//nVant3Lbr5gZtlLvvuN4ypinnbi6d3+48O/cu+E3rc40vHOb1HPo1bHvXK0/TK YRh4RX7iON8dOfk4GBYHGfEnHvlyW0vBBHu1Mzm2yF0RxADMFjBy74ZAyxatIZs2BLhs4RrR Pxv64PaFIhYkwMoWK/YkBbSs0cpHAMsWrHgj+4O8VLQyYGWN1T3J8s2s8PBCAfOHLsCyDrhI QSEBXu3wOvxiATPHf1nZYrhHj86IbRbY83Ti8AfFxBFPQImjQ/vECdhiETwYoz80ykicWGxl lfHF2CThJQ7ryfRCYaIqcShepFHNMzIiD/ydmh6ks96rmla9dh+b6gatjbvpsfIaN9GjmeyL s9uXT2ZcOKo98DCovXuD2gPPZkyb5bIZ0mb5mke0WS4+oK0HVXs+6yADb99bZDtzNmr2xP8z o6+Hmx18vdxfxHkDb/GZubUfP2FDWz/BgNpbAqiZz88eH1M3yysfn7Uo6/DbH074O0CSubTA e/K1M6FdzgtdCr3z78MgywtnkhP2MVoxDnJ94/9Y/nb/fuF6Y/M2gU/iIqC8nrG3khlJk4yR FP80Lok9svytGM8RdjeNV1A4bpoSChlVaX8FLf71xyQgxYbh+v5beqMBJe27fugOSLjp2x3T 240IZaNsw3f64ZDeiZ0I4gnZhm5H3zIoY/JQbOVuxwzJYNj2Xn/5y1+ciyyjVsv3xTzc27ul Icr+xo///0piu3w3HQ0A --h31gzZEtNLTqOjlF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 18:17:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 1D3611523F for ; Mon, 26 Apr 1999 18:17:21 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id VAA19598; Mon, 26 Apr 1999 21:16:37 -0400 (EDT) (envelope-from luoqi) Date: Mon, 26 Apr 1999 21:16:37 -0400 (EDT) From: Luoqi Chen Message-Id: <199904270116.VAA19598@lor.watermarkgroup.com> To: peter@netplex.com.au Subject: Re: config & NO_F00F_HACK Cc: A.Leidinger@Wurzelausix.CS.Uni-SB.de, chris@calldei.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It works here fine, but I can't pretend that I understand it. :-) Will you > commit it? > > Cheers, > -Peter > There's some problems with one I posted (e.g. can't deal with cases where a keyword is followed immediately by a number like irq1), I'll commit a better one. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 18:50:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (sj-dsl-9-161-065.dspeed.net [209.249.161.65]) by hub.freebsd.org (Postfix) with ESMTP id 96E5215041; Mon, 26 Apr 1999 18:50:02 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id SAA49440; Mon, 26 Apr 1999 18:49:54 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <372517C7.B7527A68@MexComUSA.net> Date: Mon, 26 Apr 1999 18:49:59 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Network problem with Laptop/Current. References: <37235EF6.A74D6974@MexComUSA.net> <199904260731.BAA08814@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <37235EF6.A74D6974@MexComUSA.net> Edwin Culp writes: > : With a kernel from April 20 everything works except my pcmcia Viking > : Modem which hasn't worked since last weekend. Is anyone else else > : having this problem? Could I be doing something wrong? > > I'm painfully aware of this problem. I see variations on this theme > many times. I'm about 2/3 through reworking pcic/pccard to work with > the newer, much nicer newbus functions for allocating resources and > such. This should be hitting the tree in the early part of this > week. Until then, use the April 20th kernel. > > Warner Thank you, that is what I'm doing:-) ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 19:13: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from spook.navinet.net (spook.navinet.net [216.67.14.69]) by hub.freebsd.org (Postfix) with ESMTP id 018D714BF2 for ; Mon, 26 Apr 1999 19:12:47 -0700 (PDT) (envelope-from forrie@forrie.com) Received: from boom (forrie.ne.mediaone.net [24.128.73.234]) by spook.navinet.net (8.9.3/8.9.3) with SMTP id WAA49534 for ; Mon, 26 Apr 1999 22:13:13 -0400 (EDT) Message-Id: <4.1.19990426221303.00924da0@216.67.14.69> X-Sender: forrie@216.67.14.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 26 Apr 1999 22:14:34 -0400 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Floppies and laptops Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I realize there are only so many drivers you can crunch on a floppy... with that in mind, and with the advent of many laptops comnig about that people would like to net-install, would it not be more practical to provide an alternate mfsroot that would be more apt to find your PCMCIA card? Would be a really handy tool/option to have. -F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 20:32:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id 66EC414E0D; Mon, 26 Apr 1999 20:32:53 -0700 (PDT) (envelope-from ctapang@aracnet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by mail4.aracnet.com (8.9.1/8.9.0) with SMTP id UAA25951; Mon, 26 Apr 1999 20:32:28 -0700 Message-ID: <00f401be905e$e55f34a0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: "=?iso-8859-1?Q?P=E5l_Sommerhein?=" Cc: , Subject: Re: Encanto Networks chooses FreeBSD over Linux Date: Mon, 26 Apr 1999 20:34:42 -0700 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.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the correction. I misread it. Yes, Mr. Frankenberg does say in effect that FreeBSD has better network performance than Linux, and that Linux is only good for desktop use. Carlos C. Tapang http://www.genericwindows.com -----Original Message----- From: Pål Sommerhein To: Carlos C. Tapang Cc: freebsd-current@freebsd.org ; freebsd-stable@freebsd.org Date: Monday, April 26, 1999 8:41 AM Subject: Re: Encanto Networks chooses FreeBSD over Linux >Carlos C. Tapang wrote: >> >> Just came across an interesting article in Investor's Business Daily (April >> 26th issue) in the Computers and Technology section. The title is "Windows >> Foes Pose A Threat: Ex-Novell CEO". In it Bob Frankenberg cites the reason >> why his company chose FreeBSD over Linux: they did a very careful evaluation >> and "found that there was a 2-1 or 3-1 improvement over Linux". "... A lot >> of work had been done to maximize transaction-processing performance." >> But "Linux, on the other hand, performs better for individual use" because >> of "better network performance". > >The last sentence above says that "Linux performs better for individual use >_because_of_better_network_performance." This is not what the article >conveyed. The correct interpretation is rather that Encanto Networks Inc. >chose FreeBSD because the company needed better network performance, *not* >better desktop performance. A quote from the article follows: > > We did a very careful evaluation. The reason > we went with FreeBSD is that a lot of work had > been done to maximize transaction-processing > performance. This can improve the speed of > accessing Web pages. We found there was a > 2- 1 or 3-1 improvement over Linux. > > Linux, on the other hand, performs better for > individual use. In general, if I'm a user of a > desktop computer - instead of a network user > - I'll get a faster response time on Linux than > FreeBSD. We needed better network performance. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [referring to an asset of FreeBSD] > > >Paal Sommerhein > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 23:24:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-32.ppp.wenet.net [206.15.85.32]) by hub.freebsd.org (Postfix) with ESMTP id F237114F65 for ; Mon, 26 Apr 1999 23:24:23 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id XAA00804; Mon, 26 Apr 1999 23:24:13 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Mon, 26 Apr 1999 23:24:13 -0700 (PDT) From: Alex Zepeda To: Warner Losh Cc: Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: suspend mode broken since one week ago In-Reply-To: <199904240528.XAA10300@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Apr 1999, Warner Losh wrote: > In message <87so9r3x44.fsf@muon.xs4all.nl> Peter Mutsaers writes: > : Is this a bug that I should report through send-pr, is it already > : known as a bug or is this an intentional change in behaviour? > > This is a known bug. I thought I kludged around it in apm.c in the > timeframe that you mentioned. Do you have > $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ > or newer? Yup. * $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ and zzz (and apm -z) don't do much. If we had ACPI support, I'd try hitting the power button.... - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 23:25:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from intrepid.leaky.com (cx74391-a.fed1.sdca.home.com [24.0.162.8]) by hub.freebsd.org (Postfix) with ESMTP id C899114F65 for ; Mon, 26 Apr 1999 23:25:34 -0700 (PDT) (envelope-from gshaffer@leaky.com) Received: (from admin@localhost) by intrepid.leaky.com (8.9.3/8.8.5) id XAA00381; Mon, 26 Apr 1999 23:23:07 -0700 (PDT) X-Authentication-Warning: intrepid.leaky.com: admin set sender to using -f Received: from aegis.leaky.com(199.184.74.2) by intrepid.leaky.com via smap (V2.1) id xma000379; Mon, 26 Apr 99 23:22:44 -0700 From: "Greg Shaffer" To: "Warner Losh" Cc: , Subject: RE: Fatal Trap 12 Date: Mon, 26 Apr 1999 23:25:49 -0700 Message-ID: <000001be9076$cab087e0$024ab8c7@aegis.leaky.com> 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 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <199904260733.BAA08842@harmony.village.org> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner, Thanks for the pointer! The only card I have that specifies a memory address is ed0 at 0xd8000. I removed the memory address in my config file, rebuilt the kernel and everything seems to works fine now. This is a older NE2000 clone card with jumpers for irq and memory address. I have been using this card for years without a problem or complaint. Why would it cause problems now? Thanks again. Greg Shaffer > -----Original Message----- > From: Warner Losh [mailto:imp@harmony.village.org] > Sent: Monday, April 26, 1999 12:34 AM > To: Greg Shaffer > Subject: Re: Fatal Trap 12 > > > In message <000101be8f95$45256410$024ab8c7@aegis.leaky.com> "Greg > Shaffer" writes: > : At trace in ddb provides the following: > : kvtop(0) at kvtop+0x2d > : isa_compat_probe(...) at isa_compat_probe+0x297 > : DEVICE_PROBE(...) at DEVICE_PROBE+0x25 > > Hmmm. Looks like somebody is trying to use location zero... I've > seen this when I had a bogus mem address for a card. > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 26 23:55:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 38CAB150D3; Mon, 26 Apr 1999 23:55:34 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA63454; Mon, 26 Apr 1999 23:55:03 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: wollman@freebsd.org Cc: current@freebsd.org Subject: Our routed - Vern says it's old and buggy. Date: Mon, 26 Apr 1999 23:55:03 -0700 Message-ID: <63452.925196103@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do we have any plans to update it to his latest offering? I believe NetBSD's already done so and would be a good source for the bits if we need them. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 0:18:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id BEC6D15109 for ; Tue, 27 Apr 1999 00:18:52 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 535991F58; Tue, 27 Apr 1999 15:18:49 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Greg Shaffer" Cc: "Warner Losh" , current@freebsd.org Subject: Re: Fatal Trap 12 In-reply-to: Your message of "Mon, 26 Apr 1999 23:25:49 MST." <000001be9076$cab087e0$024ab8c7@aegis.leaky.com> Date: Tue, 27 Apr 1999 15:18:49 +0800 From: Peter Wemm Message-Id: <19990427071851.535991F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Greg Shaffer" wrote: > Warner, > > Thanks for the pointer! The only card I have that specifies a memory address > is ed0 at 0xd8000. I removed the memory address in my config file, rebuilt > the kernel and everything seems to works fine now. This is a older NE2000 > clone card with jumpers for irq and memory address. I have been using this > card for years without a problem or complaint. Why would it cause problems > now? I've hopefully fixed this mistake now.. The problem was a side effect of the card being given a memory address and the driver turning it off because there isn't memory (ie: an ne2000). Removing the specification entirely would fix it, or updating to the latest isa_compat.c should also fix it. Why now? If you'd been reading the commit messages, you'd know the configuration system has had major changes committed... > Thanks again. > Greg Shaffer > > > -----Original Message----- > > From: Warner Losh [mailto:imp@harmony.village.org] > > Sent: Monday, April 26, 1999 12:34 AM > > To: Greg Shaffer > > Subject: Re: Fatal Trap 12 > > > > > > In message <000101be8f95$45256410$024ab8c7@aegis.leaky.com> "Greg > > Shaffer" writes: > > : At trace in ddb provides the following: > > : kvtop(0) at kvtop+0x2d > > : isa_compat_probe(...) at isa_compat_probe+0x297 > > : DEVICE_PROBE(...) at DEVICE_PROBE+0x25 > > > > Hmmm. Looks like somebody is trying to use location zero... I've > > seen this when I had a bogus mem address for a card. > > > > Warner Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 1: 0: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9C5D014FC4 for ; Tue, 27 Apr 1999 01:00:02 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA37538; Tue, 27 Apr 1999 09:00:04 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 27 Apr 1999 09:00:03 +0100 (BST) From: Doug Rabson To: Alex Zepeda Cc: Warner Losh , Peter Mutsaers , freebsd-current@freebsd.org Subject: Re: suspend mode broken since one week ago In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Apr 1999, Alex Zepeda wrote: > On Fri, 23 Apr 1999, Warner Losh wrote: > > > In message <87so9r3x44.fsf@muon.xs4all.nl> Peter Mutsaers writes: > > : Is this a bug that I should report through send-pr, is it already > > : known as a bug or is this an intentional change in behaviour? > > > > This is a known bug. I thought I kludged around it in apm.c in the > > timeframe that you mentioned. Do you have > > $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ > > or newer? > > Yup. > > * $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ > > and zzz (and apm -z) don't do much. If we had ACPI support, I'd try > hitting the power button.... I have the ACPI spec and I'm starting to get to grips with it. Initially, I will be trying to use the static device configuration tables but power management, docking and all that other good stuff should come eventually. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 1: 9:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id A53461502E for ; Tue, 27 Apr 1999 01:09:25 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id RAA13631; Tue, 27 Apr 1999 17:00:25 +0900 (JST) Message-Id: <199904270800.RAA13631@shidahara1.planet.sci.kobe-u.ac.jp> To: Doug Rabson Cc: current@freebsd.org Subject: Re: suspend mode broken since one week ago In-reply-to: Your message of "Tue, 27 Apr 1999 09:00:03 +0100" References: Date: Tue, 27 Apr 1999 17:00:24 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Do ug Rabson wrote: >I have the ACPI spec and I'm starting to get to grips with it. Initially, >I will be trying to use the static device configuration tables but power >management, docking and all that other good stuff should come eventually. Don't you try my code? I put it at http://www.planet.sci.kobe-u.ac.jp/~takawata/acpi/acpi-19990427.tar.gz . Currentry what it can do is not so different from my previous code, but I'll write a code to show ACPI name space tree in a few days. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 1:34:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1110514D89 for ; Tue, 27 Apr 1999 01:34:45 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA37605; Tue, 27 Apr 1999 09:34:53 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 27 Apr 1999 09:34:53 +0100 (BST) From: Doug Rabson To: Takanori Watanabe Cc: current@freebsd.org Subject: Re: suspend mode broken since one week ago In-Reply-To: <199904270800.RAA13631@shidahara1.planet.sci.kobe-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Apr 1999, Takanori Watanabe wrote: > In message , Do > ug Rabson wrote: > >I have the ACPI spec and I'm starting to get to grips with it. Initially, > >I will be trying to use the static device configuration tables but power > >management, docking and all that other good stuff should come eventually. > > Don't you try my code? > I put it at > http://www.planet.sci.kobe-u.ac.jp/~takawata/acpi/acpi-19990427.tar.gz > . > Currentry what it can do is not so different from my previous code, > but I'll write a code to show ACPI name space tree in a few days. I'll take a look, thanks! My test program currently manages to display most of the ASL code for my Toshiba laptop. We should compare notes; I'll put my test program up on freefall this evening after I have played with it some more. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 2: 8:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.unilat.com (mail.unilat.com [206.132.217.5]) by hub.freebsd.org (Postfix) with ESMTP id D4E8114ED9; Tue, 27 Apr 1999 02:08:06 -0700 (PDT) (envelope-from rhaas@unilat.com) Received: from unilate.com [38.27.175.93] by mail.unilat.com (SMTPD32-5.01) id AF0917B012A; Tue, 27 Apr 1999 02:10:33 PDT From: rhaas@unilat.com To: rhaas@unilat.com Subject: Attention: Coupon fraud alert! Message-Id: <199904270210.SM00153@unilate.com> Date: Tue, 27 Apr 1999 02:12:19 PDT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please forward this article. Texas Textbooks Coupon Fraud "On or Off the Drag" by Richard Haas Texas Textbooks, Inc. may have conspired to commit coupon fraud against 7-UP/Dr. Pepper. Sources claim that the President of Texas Textbooks, Inc., Morris Woods, instructed managers to have his employees separate coupons and candies from Buy Back Promotional Packages, that were put together by Market Source, Inc., and www.taponline.com. Within the Buy Back Promotional Packages were various candies, gum, and a coupon for a free 20 oz. 7-UP, as well as other advertisements and promotions from various companies, such as Chevy, University Subscription Service, Citibank, American Airlines, TIME magazine, Student Financial Services, BMG Music Service, and Sprint. According to sources, the 7-UP coupons and candied were separated and put into boxes, while the rest of the packages were thrown into the dumpster behind Texas Textbooks. These Buy Back Promotional Packages were supposed to have been given to students during the Fall Buy Back season during finals week in December, 1998. The marketing company behind the packages, Market Source, Inc. was notified about the problem in early January, 1999, but refused to do anything about it. Woods, when telephone regarding the alleged coupon fraud against 7-UP/Dr.Pepper, denied having any knowledge of the incident, and hung up the the telephone on a reporter. Several former employees claimed that they were threatened with being fired when they refused to participate in the separation of the items. "Committing a possible felony is not worth five dollars an hour," said a former employee. Seven Up/Dr. Pepper, University Subscription Service, Sprint, Chevrolet Motor Company, and the Coupon Information Center (CIC) have also been notified of these activities. Fraud is a crime punishable under both state and federal laws. Under Federal Law, a person convicted of mail fraud can be sentenced up to five years in prison and a fine of up to $250,000 for each count of the indictment. In cases where the proceeds of the fraud are not reported for Federal Income Tax purposes, conviction of tax evasion is punishable by up to 20 years imprisonment and up to a million dollar fine for each count. Photos available at: http://www.geocities.com/ResearchTriangle/Node/8879/fraud.htm If you would like to express your concern about this, please contact: Morris Woods President, Texas Textbooks, Inc. 1514 Parker Ln Austin, TX 78741-2563 (512) 462-2149 gsdesign@studybreaks.com Texas Textbooks 2410B E. Riverside Drive Austin, TX 78741 (512) 443-1257 Texas Textbooks 2338 Guadalupe Austin, TX 78705 (512) 478-9833 Bonnie O'Neill-Totin boneill@marketsource.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 4:17:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 3282414BD6 for ; Tue, 27 Apr 1999 04:17:06 -0700 (PDT) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (vallo@myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id OAA14347 for ; Tue, 27 Apr 1999 14:16:59 +0300 (EET DST) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.3/8.9.3) id OAA04064 for freebsd-current@freebsd.org; Tue, 27 Apr 1999 14:17:02 +0300 (EEST) (envelope-from vallo) Date: Tue, 27 Apr 1999 14:17:02 +0300 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: Sound doesn't work after recent upgrade Message-ID: <19990427141702.A3995@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! Something changed between Apr.21 and Apr.27 so that my onboard Vibra16X get probed but I doesn't get sound. No error messages, nothing, different players show that all is okay and play "silently". Catting something to /dev/audio or /dev/dsp(W) causes noise for about 1 second then silence. My soundcard worked well after initial new-bus changes. The motherboard is Tyan Thunder 100 DLUAN with onboard sound. Sound is not essential but it's annoying. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Apr 27 13:15:18 EEST 1999 root@myhakas.matti.ee:/usr/src/sys/compile/Myhakas_SMP Timecounter "i8254" frequency 1193061 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff real memory = 134217728 (131072K bytes) config> q avail memory = 127279104 (124296K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc031d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031d09c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x13 on isa npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: at device 7.2 on pci0 uhci0: could not map ports device_probe_and_attach: uhci0 attach returned 6 chip2: at device 7.3 on pci0 pcib1: at device 16.0 on pci0 pci2: on pcib1 fxp0: at device 17.0 on pci0 fxp0: interrupting at irq 19 fxp0: Ethernet address 00:e0:81:10:18:e0 ahc0: at device 18.0 on pci0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: interrupting at irq 16 ahc1: at device 18.1 on pci0 ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc1: interrupting at irq 16 ncr0: at device 19.0 on pci0 ncr0: interrupting at irq 16 fxp1: at device 20.0 on pci0 fxp1: interrupting at irq 17 fxp1: Ethernet address 00:90:27:45:26:03 isa0: on motherboard atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <8 virtual consoles, flags=0x0> fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 BRIDGE 981214, have 3 interfaces -- index 1 fxp0 type 6 phy 0 addrl 6 addr 00.e0.81.10.18.e0 -- index 2 fxp1 type 6 phy 0 addrl 6 addr 00.90.27.45.26.03 SMP: AP CPU #1 Launched! ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 2445MB (5008500 sectors), 5300 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode Waiting 4 seconds for SCSI devices to settle changing root device to da0s1a da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ahc1 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) cd0 at ncr0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 4:25:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from doc.dcoder.com (doc.dcoder.com [207.96.1.117]) by hub.freebsd.org (Postfix) with ESMTP id 5E5211517F for ; Tue, 27 Apr 1999 04:25:31 -0700 (PDT) (envelope-from dacoder@dcoder.com) Received: from doc.dcoder.com (doc.dcoder.com [207.96.1.117]) by doc.dcoder.com (8.9.1/8.9.1) with SMTP id HAA07946; Tue, 27 Apr 1999 07:24:48 -0400 (EDT) (envelope-from dacoder@dcoder.com) Date: Tue, 27 Apr 1999 07:24:48 -0400 (EDT) From: David Coder Reply-To: David Coder To: Mark Newton Cc: Alex , doogie@anet-stl.com, dwhite@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG Subject: Re: file disappeared? In-Reply-To: <199904270007.JAA01090@gizmo.internode.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And next time you have a big file you want to get rid of, cp /dev/null foo, then rm foo. dc -------------------------- David Coder NOC Op Erols Internet Service/RCN On Tue, 27 Apr 1999, Mark Newton wrote: :Date: Tue, 27 Apr 1999 09:37:42 +0930 (CST) :From: Mark Newton :To: Alex :Cc: doogie@anet-stl.com, dwhite@resnet.uoregon.edu, : freebsd-current@FreeBSD.ORG :Subject: Re: file disappeared? : :Alex wrote: : : > The question is how badly did I screw things up by running fsck? : > (I think with -p it doesn't actually salvage anything, just checks the : > disk). : > Worth a reboot? : :Definitely: -p *does* salvage things. Boot to single user and run :fsck manually to make sure everything's ok. : : - mark : :---- :Mark Newton Email: newton@internode.com.au (W) :Network Engineer Email: newton@atdot.dotat.org (H) :Internode Systems Pty Ltd Desk: +61-8-82232999 :"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 6:52:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E228314C25 for ; Tue, 27 Apr 1999 06:52:41 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id HAA86340; Tue, 27 Apr 1999 07:52:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id HAA17555; Tue, 27 Apr 1999 07:52:35 -0600 (MDT) Message-Id: <199904271352.HAA17555@harmony.village.org> To: Doug Rabson Subject: Re: suspend mode broken since one week ago Cc: Alex Zepeda , Peter Mutsaers , freebsd-current@freebsd.org In-reply-to: Your message of "Tue, 27 Apr 1999 09:00:03 BST." References: Date: Tue, 27 Apr 1999 07:52:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : I have the ACPI spec and I'm starting to get to grips with it. Initially, : I will be trying to use the static device configuration tables but power : management, docking and all that other good stuff should come eventually. One problem that I've had in trying to use the acpi spec to implement something is that the acpi tables on my laptop get overwritten early in the boot process on my Vaio. The driver would have to copy the tables. By "early" I mean before the login prompt. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 6:53:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E2DBA15608 for ; Tue, 27 Apr 1999 06:53:10 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id HAA86344; Tue, 27 Apr 1999 07:52:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id HAA17568; Tue, 27 Apr 1999 07:53:06 -0600 (MDT) Message-Id: <199904271353.HAA17568@harmony.village.org> To: Alex Zepeda Subject: Re: suspend mode broken since one week ago Cc: Peter Mutsaers , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 26 Apr 1999 23:24:13 PDT." References: Date: Tue, 27 Apr 1999 07:53:06 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Alex Zepeda writes: : and zzz (and apm -z) don't do much. If we had ACPI support, I'd try : hitting the power button.... I've been suspending my machine fairly well with this patch. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 7: 5:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 65792153E3 for ; Tue, 27 Apr 1999 07:05:09 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id WAA15353; Tue, 27 Apr 1999 22:56:02 +0900 (JST) Message-Id: <199904271356.WAA15353@shidahara1.planet.sci.kobe-u.ac.jp> To: Warner Losh , jlemon@americantv.com Cc: current@freebsd.org, dfr@nlsystems.com Subject: Re: suspend mode broken since one week ago In-reply-to: Your message of "Tue, 27 Apr 1999 07:52:35 CST" References: <199904271352.HAA17555@harmony.village.org> Date: Tue, 27 Apr 1999 22:56:01 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904271352.HAA17555@harmony.village.org>, Warner Losh $B$5$s$$$o$/(B: >In message Do >ug Rabson writes: >: I have the ACPI spec and I'm starting to get to grips with it. Initially, >: I will be trying to use the static device configuration tables but power >: management, docking and all that other good stuff should come eventually. > >One problem that I've had in trying to use the acpi spec to implement >something is that the acpi tables on my laptop get overwritten early >in the boot process on my Vaio. The driver would have to copy the >tables. Use options "VM86" . vm86.c:initial_bioscalls() imprements ACPI Spec section 15. Mr. Jonathan, your code works in my machine now. Now it use Int15h:E820H call. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 7:16: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 044DE14E34 for ; Tue, 27 Apr 1999 07:16:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA86414; Tue, 27 Apr 1999 08:13:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA17741; Tue, 27 Apr 1999 08:14:15 -0600 (MDT) Message-Id: <199904271414.IAA17741@harmony.village.org> To: Takanori Watanabe Subject: Re: suspend mode broken since one week ago Cc: jlemon@americantv.com, current@freebsd.org, dfr@nlsystems.com In-reply-to: Your message of "Tue, 27 Apr 1999 22:56:01 +0900." <199904271356.WAA15353@shidahara1.planet.sci.kobe-u.ac.jp> References: <199904271356.WAA15353@shidahara1.planet.sci.kobe-u.ac.jp> <199904271352.HAA17555@harmony.village.org> Date: Tue, 27 Apr 1999 08:14:14 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904271356.WAA15353@shidahara1.planet.sci.kobe-u.ac.jp> Takanori Watanabe writes: : options "VM86" : vm86.c:initial_bioscalls() imprements ACPI Spec section 15. Yea!!! The acpi info program that was posted here (or at least talked about here) recently now works! Yippie! Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 7:20: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7010D14E34 for ; Tue, 27 Apr 1999 07:20:00 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA86424; Tue, 27 Apr 1999 08:19:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA17797; Tue, 27 Apr 1999 08:19:55 -0600 (MDT) Message-Id: <199904271419.IAA17797@harmony.village.org> To: Forrest Aldrich Subject: Re: Floppies and laptops Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 26 Apr 1999 22:14:34 EDT." <4.1.19990426221303.00924da0@216.67.14.69> References: <4.1.19990426221303.00924da0@216.67.14.69> Date: Tue, 27 Apr 1999 08:19:55 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.1.19990426221303.00924da0@216.67.14.69> Forrest Aldrich writes: : mfsroot that would be more apt to find your PCMCIA card? Would be a really : handy tool/option to have. More generally, it would be nice to have support for pccards on the boot disk. There is work in progress to make this happen. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 7:31:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id A0C7015558 for ; Tue, 27 Apr 1999 07:31:05 -0700 (PDT) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999031900) with ESMTP id QAA08564; Tue, 27 Apr 1999 16:31:00 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id QAA09840; Tue, 27 Apr 1999 16:30:59 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (IDENT:TMw68QlgLVd1oBgqBJZ6KEC/NXo71Cq3@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id QAA22904; Tue, 27 Apr 1999 16:30:55 +0200 (CEST) Message-Id: <199904271430.QAA22904@wurzelausix.cs.uni-sb.de> Date: Tue, 27 Apr 1999 16:30:52 +0200 (CEST) From: Alexander Leidinger Subject: Re: Sound doesn't work after recent upgrade To: vallo@matti.ee Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19990427141702.A3995@myhakas.matti.ee> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27 Apr, Vallo Kallaste wrote: > Something changed between Apr.21 and Apr.27 so that my onboard > Vibra16X get probed but I doesn't get sound. No error messages, > nothing, different players show that all is okay and play > "silently". Catting something to /dev/audio or /dev/dsp(W) causes > noise for about 1 second then silence. My soundcard worked well "Me too" for my Vibra16?-Card. But only for pcm. The in-kernel Voxware driver works. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 7:36:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 9D283155A6 for ; Tue, 27 Apr 1999 07:36:40 -0700 (PDT) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (vallo@myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id RAA22979; Tue, 27 Apr 1999 17:36:33 +0300 (EET DST) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.3/8.9.3) id RAA05274; Tue, 27 Apr 1999 17:36:35 +0300 (EEST) (envelope-from vallo) Date: Tue, 27 Apr 1999 17:36:35 +0300 From: Vallo Kallaste To: Alexander Leidinger Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sound doesn't work after recent upgrade Message-ID: <19990427173635.A5239@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19990427141702.A3995@myhakas.matti.ee> <199904271430.QAA22904@wurzelausix.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904271430.QAA22904@wurzelausix.cs.uni-sb.de>; from Alexander Leidinger on Tue, Apr 27, 1999 at 04:30:52PM +0200 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 27, 1999 at 04:30:52PM +0200, Alexander Leidinger wrote: > > "silently". Catting something to /dev/audio or /dev/dsp(W) causes > > noise for about 1 second then silence. My soundcard worked well > > "Me too" for my Vibra16?-Card. But only for pcm. The in-kernel Voxware > driver works. Uh.. I forgot to mention that I use Luigi's pcm driver. Sorry. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:12:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 8C9AD155C7 for ; Tue, 27 Apr 1999 08:12:32 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (AS12.d-up.ACN-KV-ASC1.ukrpack.net [212.1.80.204]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id SAA15329 for ; Tue, 27 Apr 1999 18:12:47 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id SAA19412 for ; Tue, 27 Apr 1999 18:12:23 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3725D38C.2153F5B8@altavista.net> Date: Tue, 27 Apr 1999 18:11:08 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Confusing location of md5 program Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody can explain why md5 located in /sbin directory? As far as I know in /sbin only program which intended for super-user (like mount(8)) or have some features only for super-user (like ping(8)) are located. md5 in my opinion doesn't fall into any of this categories. Furthermore,  corresponding man page (md5(1)) states "FreeBSD General Commands Manual"... Sincerely, Maxim     To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:19:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 2F1B214C0C; Tue, 27 Apr 1999 08:19:08 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA05974; Tue, 27 Apr 1999 11:18:38 -0400 (EDT) (envelope-from wollman) Date: Tue, 27 Apr 1999 11:18:38 -0400 (EDT) From: Garrett Wollman Message-Id: <199904271518.LAA05974@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: wollman@freebsd.org, current@freebsd.org Subject: Our routed - Vern says it's old and buggy. In-Reply-To: <63452.925196103@zippy.cdrom.com> References: <63452.925196103@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Do we have any plans to update it to his latest offering? I believe > NetBSD's already done so and would be a good source for the bits if we > need them. I have asked someone to do so several times in the past when Vern has mailed me about new versions, but nobody has stood up to the plate. My environment here is all OSPF now, so I can't properly test it. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:25:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 2BD1014F4C for ; Tue, 27 Apr 1999 08:25:02 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id KAA18083; Tue, 27 Apr 1999 10:40:43 -0500 (EST) Date: Tue, 27 Apr 1999 10:40:41 -0500 (EST) From: Alfred Perlstein To: Warner Losh Cc: Doug Rabson , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: suspend mode broken since one week ago In-Reply-To: <199904271352.HAA17555@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Apr 1999, Warner Losh wrote: > In message Doug Rabson writes: > : I have the ACPI spec and I'm starting to get to grips with it. Initially, > : I will be trying to use the static device configuration tables but power > : management, docking and all that other good stuff should come eventually. > > One problem that I've had in trying to use the acpi spec to implement > something is that the acpi tables on my laptop get overwritten early > in the boot process on my Vaio. The driver would have to copy the > tables. > > By "early" I mean before the login prompt. Small "nit" with APM type stuff, when i close the laptop pccardd seems to deallocate my netcard. Is this really nessesary? It comes back sometimes when i open it again, but not always... -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:28:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A394615107 for ; Tue, 27 Apr 1999 08:28:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA86530; Tue, 27 Apr 1999 09:28:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA00358; Tue, 27 Apr 1999 09:27:51 -0600 (MDT) Message-Id: <199904271527.JAA00358@harmony.village.org> To: Alfred Perlstein Subject: Re: suspend mode broken since one week ago Cc: Doug Rabson , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Apr 1999 10:40:41 CDT." References: Date: Tue, 27 Apr 1999 09:27:51 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Alfred Perlstein writes: : Small "nit" with APM type stuff, when i close the laptop pccardd seems : to deallocate my netcard. Is this really nessesary? It comes back : sometimes when i open it again, but not always... Hmmm. In theory if the lid closing is shutting down the laptop into one of its less power used states, then the pcmcia cards are deactivated (sometimes by the bios itself). In theory, if that happens, it should reactivate them when it comes back... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:28:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 2BF1714F4C for ; Tue, 27 Apr 1999 08:28:01 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA22482; Tue, 27 Apr 1999 17:28:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA20046; Tue, 27 Apr 1999 17:27:52 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: sobomax@altavista.net Cc: current@FreeBSD.ORG Subject: Re: Confusing location of md5 program In-reply-to: Your message of "Tue, 27 Apr 1999 18:11:08 +0300." <3725D38C.2153F5B8@altavista.net> Date: Tue, 27 Apr 1999 17:27:52 +0200 Message-ID: <20044.925226872@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3725D38C.2153F5B8@altavista.net>, Maxim Sobolev writes: >Does anybody can explain why md5 located in /sbin directory? As far as I >know in /sbin only program which intended for super-user (like mount(8)) >or have some features only for super-user (like ping(8)) are located. It's there so that you have it if you're trying to figure out what binaries an intruder has messed with. This may be a bad argument. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7892215107 for ; Tue, 27 Apr 1999 08:30:32 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA86547; Tue, 27 Apr 1999 09:30:01 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA00424; Tue, 27 Apr 1999 09:29:49 -0600 (MDT) Message-Id: <199904271529.JAA00424@harmony.village.org> To: sobomax@altavista.net Subject: Re: Confusing location of md5 program Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Apr 1999 18:11:08 +0300." <3725D38C.2153F5B8@altavista.net> References: <3725D38C.2153F5B8@altavista.net> Date: Tue, 27 Apr 1999 09:29:48 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3725D38C.2153F5B8@altavista.net> Maxim Sobolev writes: : Does anybody can explain why md5 located in /sbin directory? As far as I : know in /sbin only program which intended for super-user (like mount(8)) : or have some features only for super-user (like ping(8)) are located. : md5 in my opinion doesn't fall into any of this categories. : Furthermore,  corresponding man page (md5(1)) states "FreeBSD General : Commands Manual"... At a guess, it is there to ensure that when you boot single user, and have only /, you can still verify the integrety of other files... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:37:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 01A1215614 for ; Tue, 27 Apr 1999 08:37:14 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA08277; Tue, 27 Apr 1999 09:35:06 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA04266; Tue, 27 Apr 1999 09:35:06 -0600 Date: Tue, 27 Apr 1999 09:35:06 -0600 Message-Id: <199904271535.JAA04266@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Alfred Perlstein Cc: Warner Losh , Doug Rabson , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: suspend mode broken since one week ago In-Reply-To: References: <199904271352.HAA17555@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Small "nit" with APM type stuff, when i close the laptop pccardd seems > to deallocate my netcard. Is this really nessesary? Yes, it is. This is what Win95 does as well, and because of lots of weird problems (not the least of which being certain cards that don't restore their settings when resumed), suspend/resume requires that we 'emulate' a removal and re-insertion. > It comes back sometimes when i open it again, but not always... The above is related to a bug in pccardd that doesn't properly 'free' resources, or recognize that the card being 're-inserted' is the same one that it knew about before. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:41:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id B29D015614 for ; Tue, 27 Apr 1999 08:39:52 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (async3-44.iptelecom.net.ua [212.42.68.235]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id SAA16920; Tue, 27 Apr 1999 18:40:09 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id SAA19524; Tue, 27 Apr 1999 18:39:19 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3725DA26.4BAB3A2B@altavista.net> Date: Tue, 27 Apr 1999 18:39:18 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Confusing location of md5 program References: <3725D38C.2153F5B8@altavista.net> <199904271529.JAA00424@harmony.village.org> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At a guess, it is there to ensure that when you boot single user, and > have only /, you can still verify the integrety of other files... Why not to put it in /bin?   Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 8:55: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from voyage.coolfitch.ie (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id C4CD714E13 for ; Tue, 27 Apr 1999 08:54:53 -0700 (PDT) (envelope-from steveo@iol.ie) Received: from voyage.coolfitch.ie (localhost [127.0.0.1]) by voyage.coolfitch.ie (8.9.3/8.9.2) with ESMTP id QAA12443; Tue, 27 Apr 1999 16:47:53 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3725DA26.4BAB3A2B@altavista.net> Date: Tue, 27 Apr 1999 16:47:53 +0100 (IST) From: "Steve O'Hara-Smith" To: Maxim Sobolev Subject: Re: Confusing location of md5 program Cc: current@FreeBSD.ORG, Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Apr-99 Maxim Sobolev wrote: >> At a guess, it is there to ensure that when you boot single user, >> and >> have only /, you can still verify the integrety of other files... > > Why not to put it in /bin? I had always understood that sbin meant static binaries (ie: those that could be used even when /lib is hosed) and should contain the vital binaries for such situations. I have just failed to locate the documentation that has left me believing this so could somebody confirm (or deny) ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 9: 4: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 3D2BA15553 for ; Tue, 27 Apr 1999 09:03:58 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id MAA18063 for current@freebsd.org; Tue, 27 Apr 1999 12:03:57 -0400 (EDT) (envelope-from mi) Message-Id: <199904271603.MAA18063@misha.cisco.com> Subject: Re: Confusing location of md5 program In-Reply-To: from "Steve O'Hara-Smith" at "Apr 27, 1999 04:47:53 pm" To: current@freebsd.org Date: Tue, 27 Apr 1999 12:03:57 -0400 (EDT) Reply-To: mi@aldan.algebra.com From: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve O'Hara-Smith once wrote: > On 27-Apr-99 Maxim Sobolev wrote: > >> At a guess, it is there to ensure that when you boot single user, > >> and have only /, you can still verify the integrety of other > >> files... > > > > Why not to put it in /bin? > > I had always understood that sbin meant static binaries (ie: > those that could be used even when /lib is hosed) and should contain > the vital binaries for such situations. I have just failed to locate > the documentation that has left me believing this so could somebody > confirm (or deny) ? There is no /lib on FreeBSD and none of the /bin/* (except for rmail) is dynamicly linked. Both of this things are quite easy to find out without any documentation, BTW :-) -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 9: 7: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BDDFB15553 for ; Tue, 27 Apr 1999 09:06:58 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA86636; Tue, 27 Apr 1999 10:06:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA00754; Tue, 27 Apr 1999 10:06:15 -0600 (MDT) Message-Id: <199904271606.KAA00754@harmony.village.org> To: "Steve O'Hara-Smith" Subject: Re: Confusing location of md5 program Cc: Maxim Sobolev , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Apr 1999 16:47:53 BST." References: Date: Tue, 27 Apr 1999 10:06:15 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Steve O'Hara-Smith" writes: : I had always understood that sbin meant static binaries (ie: : those that could be used even when /lib is hosed) and should contain : the vital binaries for such situations. I have just failed to locate : the documentation that has left me believing this so could somebody : confirm (or deny) ? /sbin is for "System binaries", which are traditionally linked static. since both system and static begin with 's' there has been much confusion over what, exactly, sbin means. The first part of this is in hier(7). Don't know why md5 is in /sbin vs /bin or /usr/sbin, to be honest. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 9:29:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from voyage.coolfitch.ie (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 931A915648 for ; Tue, 27 Apr 1999 09:29:39 -0700 (PDT) (envelope-from steveo@iol.ie) Received: from voyage.coolfitch.ie (localhost [127.0.0.1]) by voyage.coolfitch.ie (8.9.3/8.9.2) with ESMTP id RAA12508; Tue, 27 Apr 1999 17:23:09 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904271603.MAA18063@misha.cisco.com> Date: Tue, 27 Apr 1999 17:23:08 +0100 (IST) From: "Steve O'Hara-Smith" To: mi@aldan.algebra.com Subject: Re: Confusing location of md5 program Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Apr-99 mi@aldan.algebra.com wrote: > Steve O'Hara-Smith once wrote: > >> On 27-Apr-99 Maxim Sobolev wrote: > There is no /lib on FreeBSD and none of the /bin/* (except for rmail) > is My typo for /lib read /usr/lib, however Warner has shown that (at least for FreeBSD) sbin means System Binaries and is not related to static/dynamic. ---------------------------------- E-Mail: Steve O'Hara-Smith Date: 27-Apr-99 Time: 17:20:14 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 10:15:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw1adm.rcsntx.swbell.net (mail-gw1.rcsntx.swbell.net [151.164.30.51]) by hub.freebsd.org (Postfix) with ESMTP id DE7C91547D for ; Tue, 27 Apr 1999 10:15:55 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-13-53.hstntx.swbell.net [207.193.13.53]) by mail-gw1adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id MAA21282; Tue, 27 Apr 1999 12:15:43 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id MAA11239; Tue, 27 Apr 1999 12:16:22 -0500 (CDT) (envelope-from chris) Date: Tue, 27 Apr 1999 12:16:21 -0500 From: Chris Costello To: Warner Losh Cc: "Steve O'Hara-Smith" , Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Confusing location of md5 program Message-ID: <19990427121619.B9324@holly.dyndns.org> Reply-To: chris@calldei.com References: <199904271606.KAA00754@harmony.village.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="J/dobhs11T7y2rNN"; micalg=pgp-md5; protocol="application/pgp-signature" User-Agent: Mutt/0.96.1i In-Reply-To: <199904271606.KAA00754@harmony.village.org>; from Warner Losh on Tue, Apr 27, 1999 at 10:06:15AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Tue, Apr 27, 1999, Warner Losh wrote: > In message "Steve O'Hara-Smith" write= s: > : I had always understood that sbin meant static binaries (ie: > : those that could be used even when /lib is hosed) and should contain > : the vital binaries for such situations. I have just failed to locate > : the documentation that has left me believing this so could somebody > : confirm (or deny) ? >=20 > /sbin is for "System binaries", which are traditionally linked static. > since both system and static begin with 's' there has been much > confusion over what, exactly, sbin means. The first part of this is > in hier(7). My god, that man page is horrible! I'll fix it up. >=20 > Don't know why md5 is in /sbin vs /bin or /usr/sbin, to be honest. >=20 > Warner >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 --=20 Chris Costello How was Thomas J. Watson buried? 9 edge down. --J/dobhs11T7y2rNN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNyXw4rfyXY/Dmk2NAQFzpgL/V+Y65QHDauCEtyGumA+005L9NVGnBFro s2UQhnF0E75kV3pLk7+pSJsArl7cXYAVrxjWBTDW+C5swM+NypztrcNLissx+oot cr494FqreGevKh8YPpWv2fr9hYVx10cJ =+NH5 -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 12:21:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 90BBC1547D for ; Tue, 27 Apr 1999 12:21:25 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id MAA14270; Tue, 27 Apr 1999 12:21:24 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA05271; Tue, 27 Apr 1999 12:21:24 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 27 Apr 1999 12:21:24 -0700 (PDT) Message-Id: <199904271921.MAA05271@vashon.polstra.com> To: imp@harmony.village.org Subject: Re: Floppies and laptops In-Reply-To: <199904271419.IAA17797@harmony.village.org> References: <4.1.19990426221303.00924da0@216.67.14.69> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904271419.IAA17797@harmony.village.org>, Warner Losh wrote: > > More generally, it would be nice to have support for pccards on the > boot disk. There is work in progress to make this happen. Yesssss! We need this. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 12:32:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from charon.khoral.com (charon.khoral.com [209.75.155.97]) by hub.freebsd.org (Postfix) with SMTP id 36C0C14D6A for ; Tue, 27 Apr 1999 12:32:25 -0700 (PDT) (envelope-from steve@khoral.com) Received: from zen.alb.khoral.com by charon.khoral.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 27 Apr 1999 19:32:24 UT Received: from khoral.com Tue, 27 Apr 1999 13:32:23 -0600 (MDT) Date: Tue, 27 Apr 1999 13:32:23 -0600 (MDT) From: Steve Jorgensen Message-Id: <199904271932.NAA01643@zen.alb.khoral.com> To: freebsd-current@freebsd.org Subject: XFree86 and egcs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'ed and installed yesterday morning it's the third cvsup I've done since egcs went in, so I know it's working ok. Anyway, I decided to update my XFree86 installation, and found that the port no longer works. As it compiles all binaries created report tons of missing symbols from the various X library. The wierd thing is that it still installs most of the X binaries anyway, and they work fine, but it dies when it gets to installing the X server itself. I'm running a P-233 MMX with 64meg, a Adaptec 2940, scsi disks and cd, and a 4meg ATI mach64 graphics card. Any ideas what the problem is? Have I missed something? Steve -- ----------------------------------------------------------- Steven Jorgensen steve@khoral.com steve@haunt.com ------------------------------+---------------------------- Khoral Research Inc. | PHONE: (505) 837-6500 6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842 Albuquerque, NM 87110 | URL: http://www.khoral.com/ ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 13:18:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6CC0E15174; Tue, 27 Apr 1999 13:18:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA00464; Tue, 27 Apr 1999 13:18:21 -0700 (PDT) (envelope-from dillon) Date: Tue, 27 Apr 1999 13:18:21 -0700 (PDT) From: Matthew Dillon Message-Id: <199904272018.NAA00464@apollo.backplane.com> To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: NFS Patch #8 for current available - new TCP fixes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (fanfair!) NFS Patch #8 for -current is now available. This patch fixes serious bugs w/ NFS/TCP. Probably not *all* the failure conditions, but hopefully most of them. http://www.backplane.com/FreeBSD4/ NFS attempts to realign packet buffers and trods all over the underlying mbufs. For TCP connections, several RPC's may be present in an mbuf chain. The realignment of one of them may destroy the others. This does not occur with UDP because each UDP packet contains only a single rpc. Packet buffers may be unaligned for a number of reasons. The main reason is due to the 14 byte MAC header on the ethernet frame. This causes the remainder of the packet - the ip payload - to NOT be 4-byte aligned. Many ethernet drivers fudge the packet buffer in order to cause the IP payload to be aligned. Some do not. The ones that do not cause the NFS code to realign the packet and it is the nfs_realign() procedure that is broken. So the combination of having the wrong ethernet card in the server and trying to use NFS/TCP would cause some people to have lots of problems while other people might not have any problems. Neither the 'de' nor the 'xl' ethernet drivers align the packet. The 'xl' driver conditionally aligns it for the alpha. Part of the patch fixes the 'xl' driver to unconditionally align the packet buffer in order to improve NFS performance. I could not do the same for the 'de' driver because I am unsure if the dec chipset can handle an unaligned start address. The patch also fixes the nfs_realign() code so it will work properly with unaligned packets. The patch has also been updated to patch against the latest -current. As usual, any and all feedback will be appreciated. There are still NFS issues to be resolved, including a number related to AMD ( automountdaemon). Depending on how my testing works, further TCP patches may be in the wings. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 14:38: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 90013153F3 for ; Tue, 27 Apr 1999 14:37:58 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id XAA24513 for ; Tue, 27 Apr 1999 23:37:57 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma024511; Tue, 27 Apr 99 23:37:57 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id XAA01323 for ; Tue, 27 Apr 1999 23:37:57 +0200 (MET DST) Received: (qmail 66152 invoked by uid 666); 27 Apr 1999 21:38:18 -0000 Date: Tue, 27 Apr 1999 23:38:18 +0200 From: Jos Backus To: current@freebsd.org Subject: -current's routing code... Message-ID: <19990427233818.A66120@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <4.1.19990426221303.00924da0@216.67.14.69> <199904271419.IAA17797@harmony.village.org> <199904271921.MAA05271@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199904271921.MAA05271@vashon.polstra.com>; from John Polstra on Tue, Apr 27, 1999 at 12:21:24PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I really don't want to whine or anything (apologies in advance), but maybe somebody would be so kind as to apply Luoqi's patch to fix the SYSINIT(?) order so ``route add default'' works again? Thank You :-) Jos -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 14:42:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id C94B515438; Tue, 27 Apr 1999 14:42:27 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id RAA95381; Tue, 27 Apr 1999 17:39:39 -0400 (EDT) Date: Tue, 27 Apr 1999 17:39:39 -0400 (EDT) From: Chuck Robey To: Garrett Wollman Cc: "Jordan K. Hubbard" , wollman@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <199904271518.LAA05974@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Apr 1999, Garrett Wollman wrote: > < said: > > > Do we have any plans to update it to his latest offering? I believe > > NetBSD's already done so and would be a good source for the bits if we > > need them. > > I have asked someone to do so several times in the past when Vern has > mailed me about new versions, but nobody has stood up to the plate. > My environment here is all OSPF now, so I can't properly test it. Finally learned enough about routing to understand this. Which router program does OSPF? Gated? Since OSPF seems to have a lot of good features, and it's hardly new, why isn't a router using OSPF installed with FreeBSD? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 14:49:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 66A2A14C1E for ; Tue, 27 Apr 1999 14:49:32 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id OAA52175; Tue, 27 Apr 1999 14:48:56 -0700 (PDT) Date: Tue, 27 Apr 1999 14:48:56 -0700 (PDT) From: David Wolfskill Message-Id: <199904272148.OAA52175@pau-amma.whistle.com> To: chuckr@picnic.mat.net Subject: Re: Our routed - Vern says it's old and buggy. Cc: current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 27 Apr 1999 17:39:39 -0400 (EDT) >From: Chuck Robey >Finally learned enough about routing to understand this. Which router >program does OSPF? Gated? As I recall from about '93 or so, yes. >Since OSPF seems to have a lot of good features, and it's hardly new, >why isn't a router using OSPF installed with FreeBSD? Sorry; that's in the realms of psychology, sociology, and/or metaphysics, and as such, is outside any areas where I'm qualified to comment. :-) Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 14:50:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 4E76D14C1E for ; Tue, 27 Apr 1999 14:50:11 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 47567 invoked by uid 1001); 27 Apr 1999 21:50:08 +0000 (GMT) To: chuckr@picnic.mat.net Cc: wollman@khavrinen.lcs.mit.edu, jkh@zippy.cdrom.com, wollman@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 27 Apr 1999 17:39:39 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 27 Apr 1999 23:50:08 +0200 Message-ID: <47565.925249808@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Finally learned enough about routing to understand this. Which router > program does OSPF? Gated? Yes. > Since OSPF seems to have a lot of good features, and it's hardly new, > why isn't a router using OSPF installed with FreeBSD? Probably because: - OSPF *is* more complex, and you need to learn more to configure it properly. - OSPF is arguably overkill for small networks. - OSPF can't be used in 'listen-only' mode like 'routed -q'. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 14:51:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from adsl-216-102-91-184.dsl.snfc21.pacbell.net (adsl-216-102-91-184.dsl.snfc21.pacbell.net [216.102.91.184]) by hub.freebsd.org (Postfix) with ESMTP id 19ED314C1E for ; Tue, 27 Apr 1999 14:51:33 -0700 (PDT) (envelope-from cwsung@Sung.org) Received: from win95.sung.org (win95.sung.org [192.168.255.2]) by adsl-216-102-91-184.dsl.snfc21.pacbell.net (8.9.3/8.9.1) with ESMTP id OAA17531; Tue, 27 Apr 1999 14:51:29 -0700 (PDT) (envelope-from cwsung@Sung.org) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) In-Reply-To: <199904271932.NAA01643@zen.alb.khoral.com> Date: Tue, 27 Apr 1999 14:51:28 -0700 (PDT) Organization: Christian Sung & Associates From: Christian Sung To: Steve Jorgensen Subject: RE: XFree86 and egcs Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm seeing the same problem on two different machines, one running -current and the other 2.2.8-STABLE! -christian On 27-Apr-99 Steve Jorgensen wrote: > I cvsup'ed and installed yesterday morning it's the third > cvsup I've done since egcs went in, so I know it's working > ok. Anyway, I decided to update my XFree86 installation, > and found that the port no longer works. As it compiles > all binaries created report tons of missing symbols > from the various X library. The wierd thing is that it > still installs most of the X binaries anyway, and they work > fine, but it dies when it gets to installing the X server > itself. > > I'm running a P-233 MMX with 64meg, a Adaptec 2940, scsi > disks and cd, and a 4meg ATI mach64 graphics card. > > Any ideas what the problem is? Have I missed something? > > Steve > -- > ----------------------------------------------------------- > Steven Jorgensen steve@khoral.com steve@haunt.com > ------------------------------+---------------------------- > Khoral Research Inc. | PHONE: (505) 837-6500 > 6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842 > Albuquerque, NM 87110 | URL: http://www.khoral.com/ > ----------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --- Christian W. Sung _ __ ___ ___ ___ cwsung@Sung.org _ __ ___ | _ ) __| \ http://www.Sung.org _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ =============================================================== PGP Key Fingerprint: F6E2 0372 F765 28B6 6D34 7DF4 A928 A7AF 59A0 04CD =============================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 15:11:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id F3B0D14D35 for ; Tue, 27 Apr 1999 15:11:51 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id SAA07565; Tue, 27 Apr 1999 18:11:30 -0400 (EDT) (envelope-from wollman) Date: Tue, 27 Apr 1999 18:11:30 -0400 (EDT) From: Garrett Wollman Message-Id: <199904272211.SAA07565@khavrinen.lcs.mit.edu> To: sthaug@nethelp.no Cc: current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <47565.925249808@verdi.nethelp.no> References: <47565.925249808@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG <> Finally learned enough about routing to understand this. Which router >> program does OSPF? Gated? > Yes. >> Since OSPF seems to have a lot of good features, and it's hardly new, >> why isn't a router using OSPF installed with FreeBSD? > Probably because: [three good reasons deleted] Most importantly: - Recent values of GateD are distributed under a very unfriendly license. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 15:24:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C17C915056 for ; Tue, 27 Apr 1999 15:24:07 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA38950; Tue, 27 Apr 1999 23:24:13 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 27 Apr 1999 23:24:13 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: Alex Zepeda , Peter Mutsaers , freebsd-current@freebsd.org Subject: Re: suspend mode broken since one week ago In-Reply-To: <199904271352.HAA17555@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Apr 1999, Warner Losh wrote: > In message Doug Rabson writes: > : I have the ACPI spec and I'm starting to get to grips with it. Initially, > : I will be trying to use the static device configuration tables but power > : management, docking and all that other good stuff should come eventually. > > One problem that I've had in trying to use the acpi spec to implement > something is that the acpi tables on my laptop get overwritten early > in the boot process on my Vaio. The driver would have to copy the > tables. > > By "early" I mean before the login prompt. I had a problem with that. I had to tweak machdep.c to believe the bios version of extmem so that the ACPI area wasn't overwritten. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 15:42:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9443314D35 for ; Tue, 27 Apr 1999 15:42:23 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id PAA15077; Tue, 27 Apr 1999 15:42:22 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA05788; Tue, 27 Apr 1999 15:42:21 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 27 Apr 1999 15:42:21 -0700 (PDT) Message-Id: <199904272242.PAA05788@vashon.polstra.com> To: steve@khoral.com Subject: Re: XFree86 and egcs In-Reply-To: <199904271932.NAA01643@zen.alb.khoral.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904271932.NAA01643@zen.alb.khoral.com>, Steve Jorgensen wrote: > I cvsup'ed and installed yesterday morning it's the third > cvsup I've done since egcs went in, so I know it's working > ok. Anyway, I decided to update my XFree86 installation, > and found that the port no longer works. As it compiles > all binaries created report tons of missing symbols > from the various X library. The wierd thing is that it > still installs most of the X binaries anyway, and they work > fine, but it dies when it gets to installing the X server > itself. Thanks for the report, but saying that it gets "tons of missing symbols" and that it "dies" when installing the server really isn't helpful to those who might be able to fix the problem. Which symbols? Let's see the error messages. How does it "die"? Let's see the error messages. Nobody can help without that. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 16: 3:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 9F16E1528F for ; Tue, 27 Apr 1999 16:03:31 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id F23B34CE02; Tue, 27 Apr 1999 19:03:30 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id TAA10150; Tue, 27 Apr 1999 19:03:29 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.7/8.8.5) id TAA04326; Tue, 27 Apr 1999 19:03:28 -0400 (EDT) Message-Id: <199904272303.TAA04326@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: peter@netplex.com.au Subject: Re: Heads up! config(8) changes.. Cc: current@freebsd.org Date: Tue, 27 Apr 1999 16:03:28 -0700 Versions: dmail (solaris) 2.2c/makemail 2.8t Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - complain if a device is specified twice (eg: 2 x psm0) Does this work for pseudo-devices also (i.e. can bin/9931 get closed)? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 16:10:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id F2EE9156A4 for ; Tue, 27 Apr 1999 16:10:38 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA11678; Tue, 27 Apr 1999 17:10:26 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA06057; Tue, 27 Apr 1999 17:10:25 -0600 Date: Tue, 27 Apr 1999 17:10:25 -0600 Message-Id: <199904272310.RAA06057@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Doug Rabson Cc: Warner Losh , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: suspend mode broken since one week ago In-Reply-To: References: <199904271352.HAA17555@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : I have the ACPI spec and I'm starting to get to grips with it. Initially, > > : I will be trying to use the static device configuration tables but power > > : management, docking and all that other good stuff should come eventually. > > > > One problem that I've had in trying to use the acpi spec to implement > > something is that the acpi tables on my laptop get overwritten early > > in the boot process on my Vaio. The driver would have to copy the > > tables. > > > > By "early" I mean before the login prompt. > > I had a problem with that. I had to tweak machdep.c to believe the bios > version of extmem so that the ACPI area wasn't overwritten. Ahh, this is a very common problem on many new laptops. Most notably, the entire IBM ThinkPad line has this problem. Someone submitted a patch that checked to see if the BIOS returned a value > 64M, and if so to 'accept' it's value for the memory, since it's more likely to be correct. I'd like to apply it to -current, but I'm not sure of the political ramifications.... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 16:27:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 8E40315036 for ; Tue, 27 Apr 1999 16:27:19 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA95694; Tue, 27 Apr 1999 19:24:32 -0400 (EDT) Date: Tue, 27 Apr 1999 19:24:32 -0400 (EDT) From: Chuck Robey To: Garrett Wollman Cc: sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <199904272211.SAA07565@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Apr 1999, Garrett Wollman wrote: > < > >> Finally learned enough about routing to understand this. Which router > >> program does OSPF? Gated? > > > Yes. > > >> Since OSPF seems to have a lot of good features, and it's hardly new, > >> why isn't a router using OSPF installed with FreeBSD? > > > Probably because: > > [three good reasons deleted] > > Most importantly: > > - Recent values of GateD are distributed under a very unfriendly > license. Must be more to it, then. The basic idea of what the OSPF router program should do, it doesn't sound like a huge problem to do, and the actual specs are pretty well laid out and public, right? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 16:41:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 37CBC156E9 for ; Tue, 27 Apr 1999 16:41:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA01360; Tue, 27 Apr 1999 16:41:14 -0700 (PDT) (envelope-from dillon) Date: Tue, 27 Apr 1999 16:41:14 -0700 (PDT) From: Matthew Dillon Message-Id: <199904272341.QAA01360@apollo.backplane.com> To: Chuck Robey Cc: Garrett Wollman , sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> - Recent values of GateD are distributed under a very unfriendly :> license. : :Must be more to it, then. The basic idea of what the OSPF router :program should do, it doesn't sound like a huge problem to do, and the :actual specs are pretty well laid out and public, right? : :----------------------------+----------------------------------------------- :Chuck Robey | Interests include any kind of voice or data Given the choice between OSPF and RIP1/2, OSPF is far superior even on 'simple' networks. It is effectively an open protocol, like BGP. GateD is *very* unfriendly. It is user-unfriendly and it is OSS-unfriendly. It is not something I would like to see in the base distribution ( nor something I think we could put in the base distribution ). Also, the older, more OSS friendly versions of gated have too many bugs to be useable as a base. The OSPF implementation in it wasn't really fixed until late last year. For a knowledgeable programmer, building an OSPF router is not too hard to do, especially on modern UNIX systems like FreeBSD and Linux which have route monitoring sockets and fine control over the kernel routing tables. It would be a very cool thing to add. About a man-month worth of programming & debugging. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 16:49:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id B0AD7156D5; Tue, 27 Apr 1999 16:49:45 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id TAA28969; Tue, 27 Apr 1999 19:49:44 -0400 (EDT) (envelope-from luoqi) Date: Tue, 27 Apr 1999 19:49:44 -0400 (EDT) From: Luoqi Chen Message-Id: <199904272349.TAA28969@lor.watermarkgroup.com> To: current@freebsd.org, smp@freebsd.org Subject: HEADS UP! to commit SMP vmspace sharing patches Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm about to commit the SMP vmspace sharing patch (the %fs approach). All kernel modules will need to be recompiled. Recompilation is not neccessary for user land applications including ps, libkvm and friends. In this %fs approach, per-processor private pages are no longer mapped at identical virtual address for each cpu, instead a new segment descriptor (%fs) is setup to access per-cpu global variables like curproc. As a result the %fs register needs to be saved and restored at the kernel boundary, this would impose a small penalty (cpu model dependent) for each syscall and interrupt. UP kernel will also be affected as efforts were made to ensure portability of kernel modules between UP and SMP architectures. Fast vfork is now possible for SMP and is turned on as default. We're also able to get rid of vmspace juggling kludges in aio code, aio should now work correctly on SMP. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 17: 5:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 4AE0E154BB for ; Tue, 27 Apr 1999 17:05:42 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA09469; Wed, 28 Apr 1999 09:35:39 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA05800; Wed, 28 Apr 1999 09:36:10 +0930 Date: Wed, 28 Apr 1999 09:36:09 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Garrett Wollman Cc: sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <199904272211.SAA07565@khavrinen.lcs.mit.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Apr 1999, Garrett Wollman wrote: > Most importantly: > > - Recent values of GateD are distributed under a very unfriendly > license. There's also zebra, in ports (as someone pointed out on -net the other day), which seems to be GPL'ed. I haven't tried either of the two except to poke around briefly in the code.. Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 17:51:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (unknown [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id 9463314CF9 for ; Tue, 27 Apr 1999 17:51:37 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id IAA04751 for ; Wed, 28 Apr 1999 08:51:02 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id IAA17879 for ; Wed, 28 Apr 1999 08:51:31 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id IAA09151; Wed, 28 Apr 1999 08:51:31 +0800 Message-Id: <199904280051.IAA09151@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: New kernels won't boot Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Apr 1999 08:51:30 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my machine, a kernel newer than one built on the 22nd will not complete booting, panicing about not being able to mount root. Another machine with a very similar config is fine. The main difference is that the faulty machine has its FreeBSD partition in an odd spot on the disk. Below is the dmesg output, the fdisk output and the config file. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Apr 22 00:37:32 WST 1999 toor@bloop.craftncomp.com:/usr/src/sys/compile/bleep Timecounter "i8254" frequency 1193182 Hz CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) Origin = "AuthenticAMD" Id = 0x484 Stepping=4 Features=0x1 real memory = 16777216 (16384K bytes) avail memory = 13750272 (13428K bytes) Preloaded elf kernel "kernel.good" at 0xc02c4000. Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 de0: at device 4.0 on pci0 de0: interrupting at irq 11 de0: SMC 9332DST 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:a6:59:dc de0: enabling 10baseT port isa0: on motherboard atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> ata1 at irq 14 on isa0 ata1: interrupting at irq 14 fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> at fdc0 drive 0 mse0 at port 0x23c irq 5 on isa0 mse0: interrupting at irq 5 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 ed0: address 00:00:c0:d2:b2:72, type SMC8216T (16 bit) ed0: interrupting at irq 10 ppc0 at port 0x378 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 ppc0: interrupting at irq 7 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled ds0 XXX: driver didn't set ifq_maxlen ad0: ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, PIO mode changing root device to wd0s4a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=1042 heads=128 sectors/track=63 (8064 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1042 heads=128 sectors/track=63 (8064 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 201600, size 7999488 (3906 Meg), flag 80 (active) beg: cyl 25/ sector 1/ head 0; end: cyl 1016/ sector 63/ head 127 machine "i386" ident BLEEP maxusers 10 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on ad0 dumps on ad0 cpu "I486_CPU" cpu "I586_CPU" # aka Pentium(tm) cpu "I686_CPU" # aka Pentium Pro(tm) options "COMPAT_43" options USER_LDT #allow user-level control of i386 ldt options SYSVSHM options SYSVSEM options SYSVMSG options "VM86" options DDB options KTRACE #kernel tracing options UCONSOLE options USERCONFIG #boot -c editor options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 2 #Tunnel driver (ppp(8), nos-tun(8)) options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_FORWARD #enable transparent proxy support options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options "ICMP_BANDLIM" options FFS #Fast filesystem options MFS #Memory File System options NFS #Network File System options FDESC #File descriptor filesystem options KERNFS #Kernel filesystem options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options SOFTUPDATES options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker options "MSGBUF_SIZE=40960" controller isa0 controller pnp0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? tty irq 1 device vga0 at isa? port ? conflicts options VESA # needs VM86 defined too!! options XSERVER # support for running an X server. device sc0 at isa? tty options MAXCONS=16 # number of virtual consoles device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller ata0 controller ata1 at isa? port "IO_WD1" bio irq 14 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 device mse0 at isa? port 0x23c tty irq 5 device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" tty flags 0x10 irq 3 device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 controller pci0 device de0 device rl0 controller ppbus0 device lpt0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? device ppc0 at isa? port? tty irq 7 ------- End of Forwarded Message -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 19: 8: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from eterna.binary.net (eterna.binary.net [12.13.84.6]) by hub.freebsd.org (Postfix) with ESMTP id 364ED14BD0 for ; Tue, 27 Apr 1999 19:07:55 -0700 (PDT) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id VAA59662; Tue, 27 Apr 1999 21:07:54 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id VAA07396; Tue, 27 Apr 1999 21:07:42 -0500 (CDT) Date: Tue, 27 Apr 1999 22:07:42 -0400 From: Nathan Dorfman To: Andrzej Bialecki Cc: Stephane Legrand , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? Message-ID: <19990427220742.A4971@rtfm.net> References: <199904241337.PAA01205@sequoia.mondomaineamoi.megalo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Andrzej Bialecki on Sat, Apr 24, 1999 at 04:39:20PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 24, 1999 at 04:39:20PM +0200, Andrzej Bialecki wrote: > On Sat, 24 Apr 1999, Stephane Legrand wrote: > > > > That's also my impression. I glipmsed the whole source tree and I couldn't > > > find any place where the limits are enforced. BTW. what entity should > > > enforce login time limits? Kernel? Some user-space daemon? > > > > > > > To report a login.conf success, i've used on a 2.2.8 system the > > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? cputime is just a plain old process rlimit. Implementing it should be as easy as calling setrlimit(). On the other hand, login time is a different story. Generally I've found that most of the stuff in login.conf, at least that which does things like setting rlimits, environment, and modifying some login behavior (motd, nologin, mail check, etc.) works. -- Nathan Dorfman The statements and opinions in my Unix Admin @ Frontline Communications public posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 19:46:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (Postfix) with ESMTP id EB64414E83 for ; Tue, 27 Apr 1999 19:46:06 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id OAA23043; Wed, 28 Apr 1999 14:45:59 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id OAA66259; Wed, 28 Apr 1999 14:45:50 +1200 (NZST) (envelope-from jabley) Date: Wed, 28 Apr 1999 14:45:50 +1200 From: Joe Abley To: Kris Kennaway Cc: Garrett Wollman , sthaug@nethelp.no, current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: Our routed - Vern says it's old and buggy. Message-ID: <19990428144550.A66083@clear.co.nz> References: <199904272211.SAA07565@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kris Kennaway on Wed, Apr 28, 1999 at 09:36:09AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 09:36:09AM +0930, Kris Kennaway wrote: > On Tue, 27 Apr 1999, Garrett Wollman wrote: > > > Most importantly: > > > > - Recent values of GateD are distributed under a very unfriendly > > license. And the last "free" version is hideous in the extreme. > There's also zebra, in ports (as someone pointed out on -net the other day), > which seems to be GPL'ed. I haven't tried either of the two except to poke > around briefly in the code.. It's also probably worth mentioning that Zebra is being developed in an extremely active and proactive fashion, and the principal developers are extremely open to contributed feedback and code. Zebra's BGP seems pretty good and stable right now; the OSPF work has apparently received a lot of attention recently, although I haven't tried it. One of the nice things about zebra is the way that each routing protocol is neatly compartmentalised into a separate daemon. This makes it simple and easy to maintain individual protocols (or add new ones) without jeopardising others. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 20:17:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id EC33215486 for ; Tue, 27 Apr 1999 20:17:08 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id XAA08344; Tue, 27 Apr 1999 23:17:04 -0400 (EDT) Message-ID: <19990427231704.A8077@netmonger.net> Date: Tue, 27 Apr 1999 23:17:04 -0400 From: Christopher Masto To: current@freebsd.org Subject: Re: Our routed - Vern says it's old and buggy. References: <199904272211.SAA07565@khavrinen.lcs.mit.edu> <19990428144550.A66083@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19990428144550.A66083@clear.co.nz>; from Joe Abley on Wed, Apr 28, 1999 at 02:45:50PM +1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 02:45:50PM +1200, Joe Abley wrote: > It's also probably worth mentioning that Zebra is being developed > in an extremely active and proactive fashion, and the principal developers > are extremely open to contributed feedback and code. And it says right on their information page, > Currently we are developing zebra under: > > GNU/Linux 2.0.X > GNU/Linux 2.2.X > FreeBSD 2.2.8 > FreeBSD 3.X > FreeBSD 4.X > [...] > > IPv6 support is for. > > FreeBSD with INRIA > FreeBSD with KAME > GNU/Linux with IPv6 > GNU/Hurd with pfinet6 (under development) This seems like a very good thing. I have not tried Zebra, but unless there is something horribly wrong with it, I think it makes more sense to help them than to fall prey to Not Invented Here and do our own OSPF. Hopefully nobody will start a fight over the license. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 21:12:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.16]) by hub.freebsd.org (Postfix) with ESMTP id C6F7814E34 for ; Tue, 27 Apr 1999 21:12:13 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id XAA00744; Tue, 27 Apr 1999 23:12:03 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 27 Apr 1999 23:12:01 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@freebsd.org Subject: psm stopped working X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14118.35262.346147.472131@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Somewhere between April 12 and April 24 my PS/2 mouse stopped being detected by newer kernels. 773 Apr 24 23:38:03 avalon /kernel: psm0 at 0x60-0x64 irq 12 on motherboard 774 Apr 24 23:38:03 avalon /kernel: psm0: model Generic PS/2 mouse, device ID 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 21:23:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1082514E34 for ; Tue, 27 Apr 1999 21:23:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA88130; Tue, 27 Apr 1999 22:23:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA04592; Tue, 27 Apr 1999 22:22:58 -0600 (MDT) Message-Id: <199904280422.WAA04592@harmony.village.org> To: Nate Williams Subject: Re: suspend mode broken since one week ago Cc: Doug Rabson , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Apr 1999 17:10:25 MDT." <199904272310.RAA06057@mt.sri.com> References: <199904272310.RAA06057@mt.sri.com> <199904271352.HAA17555@harmony.village.org> Date: Tue, 27 Apr 1999 22:22:58 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904272310.RAA06057@mt.sri.com> Nate Williams writes: : Someone submitted a patch that checked to see if the BIOS returned a : value > 64M, and if so to 'accept' it's value for the memory, since it's : more likely to be correct. I'd like to apply it to -current, but I'm : not sure of the political ramifications.... I think that it would be OK to do this, especially if you were able to sanity check the numbers against something else... If it isn't possible to do a sanity check, then I'd still be tempted to commit it, making it an option if it causes problems for a significant number (> 1%) of people. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 21:36:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B792F15453 for ; Tue, 27 Apr 1999 21:36:19 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA88160; Tue, 27 Apr 1999 22:35:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA04679; Tue, 27 Apr 1999 22:35:43 -0600 (MDT) Message-Id: <199904280435.WAA04679@harmony.village.org> To: John Polstra Subject: Re: Floppies and laptops Cc: current@freebsd.org In-reply-to: Your message of "Tue, 27 Apr 1999 12:21:24 PDT." <199904271921.MAA05271@vashon.polstra.com> References: <199904271921.MAA05271@vashon.polstra.com> <4.1.19990426221303.00924da0@216.67.14.69> Date: Tue, 27 Apr 1999 22:35:43 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904271921.MAA05271@vashon.polstra.com> John Polstra writes: : Yesssss! We need this. I have the sysinstall patches from the PAO people. Plus I've started working on an all kernel design for what pccardd is now doing. This should obviate the need for pccardd on the floppies. There may be more hacking to sysinstall needed to get it to rescan devices, since it would be nice to be able to plug in devices at anytime, just just right after you booted the floppy. However, this is long term stuff. The short term plans I have are getting the pcic stuff working in the newbus framework, as well as including the initial patches from PAO to pccardd and sysinstall to at least give the snaps something that is easier to install on laptops. I had to jump through too many to get my machine up and running. Once I get the pccard stuff working, I may go after cardbus. Geeze, all of this so I can get the pccard support working in Soren's new driver so I can read/write compact flash cards on my FreeBSD machine so I can put them into a WinCE palmtop I have.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 22:24:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 74B8714DA5 for ; Tue, 27 Apr 1999 22:24:09 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA88250; Tue, 27 Apr 1999 23:23:37 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA05071; Tue, 27 Apr 1999 23:23:32 -0600 (MDT) Message-Id: <199904280523.XAA05071@harmony.village.org> To: alk@pobox.com Subject: Re: psm stopped working Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Apr 1999 23:12:01 CDT." <14118.35262.346147.472131@avalon.east> References: <14118.35262.346147.472131@avalon.east> Date: Tue, 27 Apr 1999 23:23:32 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14118.35262.346147.472131@avalon.east> Anthony Kimball writes: : Somewhere between April 12 and April 24 my PS/2 mouse stopped being : detected by newer kernels. : 773 Apr 24 23:38:03 avalon /kernel: psm0 at 0x60-0x64 irq 12 on motherboard : 774 Apr 24 23:38:03 avalon /kernel: psm0: model Generic PS/2 mouse, device ID 0 Read UPDATING :-). To be more helpful, you need to connect the psm device to the atkbdc controller. See the new GENERIC file for details. There is anti foot shooting code for the keyboard, but not the mouse. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 22:37: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 95DA014C3B; Tue, 27 Apr 1999 22:37:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id HAA25819; Wed, 28 Apr 1999 07:36:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id HAA22150; Wed, 28 Apr 1999 07:36:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Luoqi Chen Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: HEADS UP! to commit SMP vmspace sharing patches In-reply-to: Your message of "Tue, 27 Apr 1999 19:49:44 EDT." <199904272349.TAA28969@lor.watermarkgroup.com> Date: Wed, 28 Apr 1999 07:36:48 +0200 Message-ID: <22148.925277808@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904272349.TAA28969@lor.watermarkgroup.com>, Luoqi Chen writes: >I'm about to commit the SMP vmspace sharing patch (the %fs approach). All >kernel modules will need to be recompiled. Recompilation is not neccessary >for user land applications including ps, libkvm and friends. > >In this %fs approach, per-processor private pages are no longer mapped at >identical virtual address for each cpu, instead a new segment descriptor (%fs) >is setup to access per-cpu global variables like curproc. How is this accessed from C sources ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 22:45:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0601514C3B for ; Tue, 27 Apr 1999 22:45:13 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA68498; Tue, 27 Apr 1999 22:44:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Chuck Robey Cc: Garrett Wollman , sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-reply-to: Your message of "Tue, 27 Apr 1999 19:24:32 EDT." Date: Tue, 27 Apr 1999 22:44:24 -0700 Message-ID: <68496.925278264@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Um, can we get back to the subject at hand PLEASE? Who among you is going to import the new routed? Garrett doesn't have testing facilities for RIP, so it has to be someone else. Since Chuck also appears to have boundless energy for this topic, might he be willing? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 23:16: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 57FF814F41 for ; Tue, 27 Apr 1999 23:15:46 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA22312; Wed, 28 Apr 1999 08:15:42 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id IAA10695; Wed, 28 Apr 1999 08:15:35 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904280615.IAA10695@greenpeace.grondar.za> To: "Jordan K. Hubbard" Cc: Chuck Robey , Garrett Wollman , sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: Your message of " Tue, 27 Apr 1999 22:44:24 MST." <68496.925278264@zippy.cdrom.com> References: <68496.925278264@zippy.cdrom.com> Date: Wed, 28 Apr 1999 08:15:33 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Um, can we get back to the subject at hand PLEASE? Who among you is > going to import the new routed? Garrett doesn't have testing > facilities for RIP, so it has to be someone else. Since Chuck also > appears to have boundless energy for this topic, might he be willing? :-) I could do it? :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 27 23:33:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BF1E615184 for ; Tue, 27 Apr 1999 23:33:27 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA68805; Tue, 27 Apr 1999 23:31:15 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Mark Murray Cc: Chuck Robey , Garrett Wollman , sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-reply-to: Your message of "Wed, 28 Apr 1999 08:15:33 +0200." <199904280615.IAA10695@greenpeace.grondar.za> Date: Tue, 27 Apr 1999 23:31:15 -0700 Message-ID: <68803.925281075@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sold, to the man in the long black coat! :) > "Jordan K. Hubbard" wrote: > > Um, can we get back to the subject at hand PLEASE? Who among you is > > going to import the new routed? Garrett doesn't have testing > > facilities for RIP, so it has to be someone else. Since Chuck also > > appears to have boundless energy for this topic, might he be willing? :-) > > I could do it? :-) > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 1: 4:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5C4F5155FF for ; Wed, 28 Apr 1999 01:04:13 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA40247; Wed, 28 Apr 1999 09:04:31 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 28 Apr 1999 09:04:31 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: Nate Williams , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: suspend mode broken since one week ago In-Reply-To: <199904280422.WAA04592@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Apr 1999, Warner Losh wrote: > In message <199904272310.RAA06057@mt.sri.com> Nate Williams writes: > : Someone submitted a patch that checked to see if the BIOS returned a > : value > 64M, and if so to 'accept' it's value for the memory, since it's > : more likely to be correct. I'd like to apply it to -current, but I'm > : not sure of the political ramifications.... > > I think that it would be OK to do this, especially if you were able to > sanity check the numbers against something else... If it isn't > possible to do a sanity check, then I'd still be tempted to commit it, > making it an option if it causes problems for a significant number (> > 1%) of people. My patch looks like this: Index: machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.330 diff -u -r1.330 machdep.c --- machdep.c 1999/04/19 14:14:12 1.330 +++ machdep.c 1999/04/26 13:20:30 @@ -1403,8 +1403,9 @@ } } if (bootinfo.bi_extmem != biosextmem) - printf("BIOS extmem (%uK) != RTC extmem (%uK)\n", + printf("BIOS extmem (%uK) != RTC extmem (%uK), setting to BIOS value\n", bootinfo.bi_extmem, biosextmem); + biosextmem = bootinfo.bi_extmem; } #ifdef SMP -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 2:12:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id D5F3814E61 for ; Wed, 28 Apr 1999 02:12:32 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 6961 invoked by uid 1001); 28 Apr 1999 09:12:30 -0000 Date: 28 Apr 1999 09:12:30 -0000 Message-ID: <19990428091230.6958.qmail@ns.oeno.com> From: Ville-Pertti Keinonen To: current@freebsd.org Subject: Patch affecting vnode identification and name cache - please test Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This small patch doesn't fix any major bugs (mostly the XXX in the comment before cache_purge in kern/vfs_cache.c), but should be a step towards allowing a dynamically sized vnode cache to be used. This is done by eliminating the reliance on a vnode pointer/v_id pair as a unique identification for an arbitrary vnode over arbitrary periods of time and without holding references. It needs to be tested for reliability (in particular, look for leaks in free vnodes). You can get the unified diffs against -current (kern/vfs_cache.c 1.39, kern/vfs_subr.c 1.189) from http://www.hut.fi/~will/freebsd_v_id.diff Please send success/failure reports. Comments on the approach are also welcome, I've only discussed this with phk so far. The following things are changed: - A reference is held by v_dd to prevent the referenced vnode from being reused (this is currently prevented in most cases because of the v_cache_src link, so it doesn't make behavior worse, only more deterministic). - The v_id is used as a version number, rather than a (supposedly) unique identifier, and incremented locally. This should make the probability of wrapping during the uses of v_id other than v_ddid insignificant (it would have to occur during a single wait for a lock on the vnode). - The vnode pointer is used in NCHHASH rather than v_id, which is no longer globally unique, even most of the time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 3: 3:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id E539214FF8 for ; Wed, 28 Apr 1999 03:03:37 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (postfix@myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id NAA08997 for ; Wed, 28 Apr 1999 13:03:23 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 4A9061F44; Wed, 28 Apr 1999 13:03:24 +0300 (EEST) Date: Wed, 28 Apr 1999 13:02:09 +0300 From: Vallo Kallaste To: freebsd-ports@freebsd.org Subject: blackbox doesn't work after recent changes in current Message-ID: <19990428130209.A2030@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! Blackbox doesn't work after recent changes in current, it complains: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "__vt_7filebuf" Unfortunately it doesn't compile also, autoconf(?) complains about C++ compilator and thinks that it cannot generate executables. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 4:34:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ambra.transint.is (ambra.transint.is [194.144.127.11]) by hub.freebsd.org (Postfix) with ESMTP id AD658156B8 for ; Wed, 28 Apr 1999 04:34:54 -0700 (PDT) (envelope-from bjornr@transint.is) Received: by ambra.transint.is (Postfix, from userid 1000) id 8C3E7158; Wed, 28 Apr 1999 11:31:07 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by ambra.transint.is (Postfix) with ESMTP id 28936117 for ; Wed, 28 Apr 1999 11:31:07 +0000 (GMT) Date: Wed, 28 Apr 1999 11:31:06 +0000 (GMT) From: Bjorn Robertsson To: freebsd-current@FreeBSD.ORG Subject: Re: Confirmation for subscribe freebsd-current In-Reply-To: <19990428113224.AE352156B8@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 9b0472d2 subscribe freebsd-current bjornr@transint.is To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 4:37:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82]) by hub.freebsd.org (Postfix) with ESMTP id A44DC1522F for ; Wed, 28 Apr 1999 04:37:21 -0700 (PDT) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.2/8.9.2) with ESMTP id NAA49344; Wed, 28 Apr 1999 13:37:18 +0200 (CEST) (envelope-from tseidmann@simultan.ch) Message-ID: <3726F2EB.2B4A6AA5@simultan.ch> Date: Wed, 28 Apr 1999 13:37:15 +0200 From: Thomas Seidmann X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth Subject: New ATA drivers problem? (Was: New kernels won't boot) References: <199904280051.IAA09151@ariadne.tensor.pgs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, In the great new ATA device driver framework (thanks Soren) there seems to be a problem reported before by Stephen: Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > On my machine, a kernel newer than one built on the 22nd will not complete > booting, panicing about not being able to mount root. Another machine with a > very similar config is fine. The main difference is that the faulty machine > has its FreeBSD partition in an odd spot on the disk. Below is the dmesg > output, the fdisk output and the config file. [stuff deleted] I have three hosts with -current, all with the new ATA in function. Booting the same kernel produces different results on all of them wrt root file system mounting: - one reports 'changing root device to wd0s3a' - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and continues flawlessly - one reports 'changing root device to wd0s3a' followed by 'changing root device to wd0a' and panics with 'cannot mount root file system (2), err 22' All motherboards are equipped with the PIIX4 IDE controller. If I need to supply the dmesg output and/or configuration, please let me know. All three hosts have FreeBSD on the first disk (on different disk locations, though). Regards, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 4:44: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 24370156D0 for ; Wed, 28 Apr 1999 04:44:03 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA02577; Wed, 28 Apr 1999 13:43:54 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904281143.NAA02577@freebsd.dk> Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: <3726F2EB.2B4A6AA5@simultan.ch> from Thomas Seidmann at "Apr 28, 1999 1:37:15 pm" To: tseidmann@SIMULTAN.CH (Thomas Seidmann) Date: Wed, 28 Apr 1999 13:43:54 +0200 (CEST) Cc: current@FreeBSD.ORG, shocking@prth.pgs.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > I have three hosts with -current, all with the new ATA in function. > Booting the same kernel produces different results on all of them wrt > root file system mounting: > > - one reports 'changing root device to wd0s3a' > - one reports 'changing root device to wd0s3a' followed by 'changing > root device to wd0a' and continues flawlessly > - one reports 'changing root device to wd0s3a' followed by 'changing > root device to wd0a' and panics with 'cannot mount root file system (2), > err 22' > > All motherboards are equipped with the PIIX4 IDE controller. If I need > to supply the dmesg output and/or configuration, please let me know. All > three hosts have FreeBSD on the first disk (on different disk locations, > though). Hmm, could you mail me the output of fdisk & disklabel from those tree machines, with indication of how they behave ?? I'm unable to reproduce those errors here, but this might bring the details I need to figure it out... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 4:44:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id D298E156D0 for ; Wed, 28 Apr 1999 04:44:41 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id HAA18116; Wed, 28 Apr 1999 07:41:56 -0400 (EDT) Date: Wed, 28 Apr 1999 07:41:55 -0400 (EDT) From: Chuck Robey To: "Jordan K. Hubbard" Cc: Garrett Wollman , sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <68496.925278264@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Apr 1999, Jordan K. Hubbard wrote: > Um, can we get back to the subject at hand PLEASE? Who among you is > going to import the new routed? Garrett doesn't have testing > facilities for RIP, so it has to be someone else. Since Chuck also > appears to have boundless energy for this topic, might he be willing? :-) It's likely I'll have time this weekend. Anyone got a URL? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 5: 5: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B333C151F3 for ; Wed, 28 Apr 1999 05:05:03 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id FAA67494 for ; Wed, 28 Apr 1999 05:00:14 -0700 (PDT) Date: Wed, 28 Apr 1999 05:00:14 -0700 (PDT) From: Julian Elischer To: current@freebsd.org Subject: vmstat -m very confused. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it just me, or is vmstat -m getting very confused in the last few days? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 5:11:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82]) by hub.freebsd.org (Postfix) with ESMTP id 6447D1537C for ; Wed, 28 Apr 1999 05:11:36 -0700 (PDT) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.2/8.9.2) with ESMTP id OAA50636; Wed, 28 Apr 1999 14:10:02 +0200 (CEST) (envelope-from tseidmann@simultan.ch) Message-ID: <3726FA96.8486A6D5@simultan.ch> Date: Wed, 28 Apr 1999 14:09:58 +0200 From: Thomas Seidmann X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) References: <199904281143.NAA02577@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > Hmm, could you mail me the output of fdisk & disklabel from those tree > machines, with indication of how they behave ?? > > I'm unable to reproduce those errors here, but this might bring the > details I need to figure it out... Certainly. First the working machine (reports solely 'changing root device to wd0s3a' and continues): ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=970 heads=128 sectors/track=63 (8064 blks/cyl) parameters to be used for BIOS calculations are: cylinders=970 heads=128 sectors/track=63 (8064 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 63, size 1048257 (511 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 129/ sector 63/ head 127 The data for partition 2 is: sysid 7,(OS/2 HPFS, NTFS, QNX or Advanced UNIX) start 1048320, size 3386880 (1653 Meg), flag 0 beg: cyl 130/ sector 1/ head 0; end: cyl 549/ sector 63/ head 127 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4435200, size 3386880 (1653 Meg), flag 0 beg: cyl 550/ sector 1/ head 0; end: cyl 969/ sector 63/ head 127 The data for partition 4 is: # /dev/rwd0s3c: type: ESDI disk: Maxtor 84000A6 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 128 sectors/cylinder: 8064 cylinders: 420 sectors/unit: 3386880 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 64512 0 4.2BSD 0 0 0 # (Cyl. 0 - 7) b: 266112 64512 swap # (Cyl. 8 - 40) c: 3386880 0 unused 0 0 # (Cyl. 0 - 419) e: 64512 330624 4.2BSD 0 0 0 # (Cyl. 41 - 48) f: 2991744 395136 4.2BSD 0 0 0 # (Cyl. 49 - 419) Now the one which panics: ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=790 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=790 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 63, size 208782 (101 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 12/ sector 63/ head 254 The data for partition 2 is: sysid 5,(Extended DOS) start 208845, size 8193150 (4000 Meg), flag 0 beg: cyl 13/ sector 1/ head 0; end: cyl 522/ sector 63/ head 254 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 8401995, size 4289355 (2094 Meg), flag 0 beg: cyl 523/ sector 1/ head 0; end: cyl 789/ sector 63/ head 254 The data for partition 4 is: # /dev/rwd0s3a: type: ESDI disk: wd0s3 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 267 sectors/unit: 4289355 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 64260 0 4.2BSD 0 0 0 # (Cyl. 0 - 3) b: 546210 64260 swap # (Cyl. 4 - 37) c: 4289355 0 unused 0 0 # (Cyl. 0 - 266) e: 64260 610470 4.2BSD 0 0 0 # (Cyl. 38 - 41) f: 3614625 674730 4.2BSD 0 0 0 # (Cyl. 42 - 266) The third one is unfortunately at home, I'll have access to it after approx 6.00PM CEST. Thank you, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 5:29:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.aa.net [206.125.75.16]) by hub.freebsd.org (Postfix) with ESMTP id A014014DC4 for ; Wed, 28 Apr 1999 05:29:49 -0700 (PDT) (envelope-from dennis.glatting@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id FAA63594; Wed, 28 Apr 1999 05:27:25 -0700 (PDT) Date: Wed, 28 Apr 1999 05:27:25 -0700 (PDT) From: Dennis Glatting To: Matthew Dillon Cc: Chuck Robey , Garrett Wollman , sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <199904272341.QAA01360@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > GateD is *very* unfriendly. It is user-unfriendly and it is > OSS-unfriendly. ... > ... Also, the older, more OSS friendly versions of gated have too > many bugs to be useable as a base. The OSPF implementation in it > wasn't really fixed until late last year. > I can vouch for that... again, and again, and again... :) -dpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 6:27:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id D15AE14C08; Wed, 28 Apr 1999 06:27:07 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA29467; Wed, 28 Apr 1999 09:27:06 -0400 From: Bill Paul Message-Id: <199904281327.JAA29467@skynet.ctr.columbia.edu> Subject: Re: NFS Patch #8 for current available - new TCP fixes To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 28 Apr 1999 09:27:05 -0400 (EDT) Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199904272018.NAA00464@apollo.backplane.com> from "Matthew Dillon" at Apr 27, 99 01:18:21 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2310 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > (fanfair!) (Darth Vader's imperial march theme) > NFS Patch #8 for -current is now available. This patch fixes serious bugs > w/ NFS/TCP. Probably not *all* the failure conditions, but hopefully > most of them. [...] > Neither the 'de' nor the 'xl' ethernet drivers align the packet. The 'xl' > driver conditionally aligns it for the alpha. Part of the patch fixes > the 'xl' driver to unconditionally align the packet buffer in order to > improve NFS performance. I could not do the same for the 'de' driver > because I am unsure if the dec chipset can handle an unaligned start > address. From what I can tell, the DEC parts make you specify an RX DMA buffer address that is longword aligned. There are actually not that many devices where you're allowed to use arbitrary byte-aligned addresses for receive buffers (the 3Com XL and Intel 'speedo' chips let you do it, as well as the ThunderLAN, and the Alteon Tigon NIC; I _think_ the AMD PCnet/LANCE devices let you do it, but that's about it). For parts that don't support arbitrary alignment, you have to copy. Now, in some of the drivers that I ported to the alpha, I only copied the first small section of the packet in order to get the IP header aligned (since failing to do this causes an unaligned access trap in the IP code). This is faster than copying the entire packet to fix the alignment, but I'm not sure what effect it has on NFS. That said, although I haven't looked too closely at the de driver (it scares me -- a lot), it should have some sort of gimmick to fix the packet alignment otherwise it wouldn't work on the alpha. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 7:15:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 24A25154F7 for ; Wed, 28 Apr 1999 07:15:12 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA18310; Wed, 28 Apr 1999 08:14:59 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA08646; Wed, 28 Apr 1999 08:14:58 -0600 Date: Wed, 28 Apr 1999 08:14:58 -0600 Message-Id: <199904281414.IAA08646@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Doug Rabson Cc: Warner Losh , Nate Williams , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: suspend mode broken since one week ago In-Reply-To: References: <199904280422.WAA04592@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : Someone submitted a patch that checked to see if the BIOS returned a > > : value > 64M, and if so to 'accept' it's value for the memory, since it's > > : more likely to be correct. I'd like to apply it to -current, but I'm > > : not sure of the political ramifications.... > > > > I think that it would be OK to do this, especially if you were able to > > sanity check the numbers against something else... If it isn't > > possible to do a sanity check, then I'd still be tempted to commit it, > > making it an option if it causes problems for a significant number (> > > 1%) of people. > > My patch looks like this: > > Index: machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v > retrieving revision 1.330 > diff -u -r1.330 machdep.c > --- machdep.c 1999/04/19 14:14:12 1.330 > +++ machdep.c 1999/04/26 13:20:30 > @@ -1403,8 +1403,9 @@ > } > } > if (bootinfo.bi_extmem != biosextmem) > - printf("BIOS extmem (%uK) != RTC extmem (%uK)\n", > + printf("BIOS extmem (%uK) != RTC extmem (%uK), setting to BIOS value\n", > bootinfo.bi_extmem, biosextmem); > + biosextmem = bootinfo.bi_extmem; > } > > #ifdef SMP > I don't think this is complete, because I think (don't know) that many older BIOS's only reported up to 64M of memory, so if you had more than 64M in the box it didn't report it. However, I can't verify this since I don't have any machines with > 64M of memory. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 8: 5:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id B540C153CB; Wed, 28 Apr 1999 08:05:21 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Wed, 28 Apr 1999 16:03:04 +0100 Message-ID: From: paul@originative.co.uk To: wpaul@skynet.ctr.columbia.edu, dillon@apollo.backplane.com Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: NFS Patch #8 for current available - new TCP fixes Date: Wed, 28 Apr 1999 16:03:02 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Bill Paul [mailto:wpaul@skynet.ctr.columbia.edu] > Sent: 28 April 1999 14:27 > To: dillon@apollo.backplane.com > Cc: hackers@FreeBSD.ORG; current@FreeBSD.ORG > Subject: Re: NFS Patch #8 for current available - new TCP fixes > > > Of all the gin joints in all the towns in all the world, > Matthew Dillon > had to walk into mine and say: > > > (fanfair!) > > (Darth Vader's imperial march theme) > > > NFS Patch #8 for -current is now available. This patch > fixes serious bugs > > w/ NFS/TCP. Probably not *all* the failure conditions, > but hopefully > > most of them. > [...] > > > Neither the 'de' nor the 'xl' ethernet drivers align > the packet. The 'xl' > > driver conditionally aligns it for the alpha. Part of > the patch fixes > > the 'xl' driver to unconditionally align the packet > buffer in order to > > improve NFS performance. I could not do the same for > the 'de' driver > > because I am unsure if the dec chipset can handle an > unaligned start > > address. > > From what I can tell, the DEC parts make you specify an RX DMA buffer > address that is longword aligned. There are actually not that > many devices > where you're allowed to use arbitrary byte-aligned addresses > for receive > buffers (the 3Com XL and Intel 'speedo' chips let you do it, > as well as the > ThunderLAN, and the Alteon Tigon NIC; I _think_ the AMD PCnet/LANCE > devices let you do it, but that's about it). The Lance requires longword alignement, the PCnet requires 16 byte alignement if you put it in 32 bit mode, otherwise it's the same as the lance. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 8:20:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from atdot.dotat.org (atdot.dotat.org [150.101.89.3]) by hub.freebsd.org (Postfix) with ESMTP id 32540151E0 for ; Wed, 28 Apr 1999 08:20:11 -0700 (PDT) (envelope-from newton@atdot.dotat.org) Received: (from newton@localhost) by atdot.dotat.org (8.9.2/8.7) id AAA35436 for current@freebsd.org; Thu, 29 Apr 1999 00:48:58 +0930 (CST) Date: Thu, 29 Apr 1999 00:48:58 +0930 (CST) From: Mark Newton Message-Id: <199904281518.AAA35436@atdot.dotat.org> To: current@freebsd.org Subject: cvsup.au.freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know what has happened to cvsup.au.freebsd.org? - mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 8:32:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 6A1E614EA2 for ; Wed, 28 Apr 1999 08:32:29 -0700 (PDT) (envelope-from erik@habatech.no) Received: from freebsd.habatech.no ([62.92.133.2]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id RAA01743 for ; Wed, 28 Apr 1999 17:32:26 +0200 (CEST) (envelope-from erik@habatech.no) From: erik@habatech.no Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 28 Apr 1999 17:38:45 +0200 (CEST) To: freebsd-current@FreeBSD.org Subject: Problems with ahc (2940U2W) and USB Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the current sources, there seems to be a problem with the Adaptec 2940U2W driver when using USB. Whenever I try to boot a kernel with the USB driver, the boot process gets to the "Waiting 15 seconds for SCSI devices to settle" and stops. If I compile a kernel with an nearly identical config, only the USB driver has been commented out, it boots all right. My computer has a Spacewalker 661 mainboard, which is a 440BX based card. The SCSI controller is an Adaptec 2940U2W. Kernels compiled before the integration of new-bus works fine. Now, this is not a critical situation for me, as I have no USB devices, but I thought someone else would want this information. Anyone else experiencing this? -- --------------------------------+---------------------------------------+ Erik H. Bakke, Habatech AS | To be or not to be... | E-Mail: erik@habatech.no | Is simply a question of binary logic. | This message was sent by XFMail | | --------------------------------+---------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 8:36:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id 9FB1815442 for ; Wed, 28 Apr 1999 08:36:11 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id BAA12550; Thu, 29 Apr 1999 01:36:04 +1000 (EST) Message-ID: <19990429013604.H21534@rf900.physics.usyd.edu.au> Date: Thu, 29 Apr 1999 01:36:04 +1000 From: David Dawes To: Mark Newton , current@FreeBSD.ORG Subject: Re: cvsup.au.freebsd.org References: <199904281518.AAA35436@atdot.dotat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904281518.AAA35436@atdot.dotat.org>; from Mark Newton on Thu, Apr 29, 1999 at 12:48:58AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 29, 1999 at 12:48:58AM +0930, Mark Newton wrote: > >Does anyone know what has happened to cvsup.au.freebsd.org? I think a disk has died. I'm on leave for a couple of weeks, and haven't had a chance to go into work to check up on it properly. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 8:42:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from phobos.walker.dom (pme-04.ior.com [204.212.113.4]) by hub.freebsd.org (Postfix) with ESMTP id 7F02615706 for ; Wed, 28 Apr 1999 08:42:39 -0700 (PDT) (envelope-from kew@timesink.spk.wa.us) Received: from timesink.spk.wa.us (localhost.walker.dom [127.0.0.1]) by phobos.walker.dom (8.9.3/8.9.3) with ESMTP id IAA62810 for ; Wed, 28 Apr 1999 08:41:53 -0700 (PDT) (envelope-from kew@timesink.spk.wa.us) Message-ID: <37272C41.6F889B3E@timesink.spk.wa.us> Date: Wed, 28 Apr 1999 08:41:53 -0700 From: Keith Walker X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Progs linked against libstdc++ dead... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aagh! As of last-night's current (Tuesday), *NO* C++ program that links against libstdc++ works now. All of them come up with this error, and recompilation doesn't help :-( On my machine, this killed the entire KDE system. All of those programs come up with the error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "__vt_7filebuf" which kinda refects the error I get when trying to recompile one of my programs that also failed. Here's the final link in verbose on my CM11A daemon: ---------------- c++ -O -pipe -Os -I/usr/local/include -DLATITUDE="47.7329" -DLONGITUDE="-117.5138" -o xtend++ main.o x10.o attime.o tlexer.o altss.o atparse.o solar.o atmgr.o macmgr.o program.o SysLog.o timerep.o -ll -v Using builtin specs. gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) /usr/libexec/elf/ld -m elf_i386 -dynamic-linker /usr/libexec/ld-elf.so.1 -o xtend++ /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o -L/usr/libdata/gcc -L/usr/libexec/elf -L/usr/libexec main.o x10.o attime.o tlexer.o altss.o atparse.o solar.o atmgr.o macmgr.o program.o SysLog.o timerep.o -ll -lstdc++ -lm /usr/lib/libgcc.a -lc /usr/lib/libgcc.a /usr/lib/crtend.o /usr/lib/crtn.o /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' *** Error code 1 ---------------- -- Keith Walker, Spokane, WA FreeBSD 4.0-CURRENT (ASUS) #35: Mon Apr 19 20:48:32 PDT 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 8:55: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by hub.freebsd.org (Postfix) with ESMTP id E869A15727 for ; Wed, 28 Apr 1999 08:55:06 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id JAA01524; Wed, 28 Apr 1999 09:58:56 -0700 (PDT) Date: Wed, 28 Apr 1999 09:58:56 -0700 (PDT) From: Jim Shankland Message-Id: <199904281658.JAA01524@biggusdiskus.flyingfox.com> To: dillon@apollo.backplane.com Subject: Re: Our routed - Vern says it's old and buggy. Cc: current@FreeBSD.ORG In-Reply-To: <199904272341.QAA01360@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > Given the choice between OSPF and RIP1/2, OSPF is far superior > even on 'simple' networks. It is effectively an open protocol, > like BGP. Matt, can you clarify what you mean by "open" here? I know it's what the "O" in OSPF stands for, but in what way are OSPF and BGP more open than RIP? Jim Shankland NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 8:56: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id AC8E515720 for ; Wed, 28 Apr 1999 08:56:02 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id LAA06063; Wed, 28 Apr 1999 11:53:43 -0400 (EDT) Message-ID: <002f01be9190$2e22bfe0$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: , References: Subject: Re: Problems with ahc (2940U2W) and USB Date: Wed, 28 Apr 1999 12:00:04 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I am seeing the same thing on a ASUS P2B with a Adaptec 2940?? controller. Rick ----- Original Message ----- From: To: Sent: Wednesday, April 28, 1999 11:38 AM Subject: Problems with ahc (2940U2W) and USB With the current sources, there seems to be a problem with the Adaptec 2940U2W driver when using USB. Whenever I try to boot a kernel with the USB driver, the boot process gets to the "Waiting 15 seconds for SCSI devices to settle" and stops. If I compile a kernel with an nearly identical config, only the USB driver has been commented out, it boots all right. My computer has a Spacewalker 661 mainboard, which is a 440BX based card. The SCSI controller is an Adaptec 2940U2W. Kernels compiled before the integration of new-bus works fine. Now, this is not a critical situation for me, as I have no USB devices, but I thought someone else would want this information. Anyone else experiencing this? -- --------------------------------+---------------------------------------+ Erik H. Bakke, Habatech AS | To be or not to be... | E-Mail: erik@habatech.no | Is simply a question of binary logic. | This message was sent by XFMail | | --------------------------------+---------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 9: 2:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-03.ix.netcom.com [207.93.148.3]) by hub.freebsd.org (Postfix) with ESMTP id D1FFB15752 for ; Wed, 28 Apr 1999 09:02:19 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id JAA17273; Wed, 28 Apr 1999 09:02:08 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Wed, 28 Apr 1999 09:02:08 -0700 (PDT) Message-Id: <199904281602.JAA17273@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: current@FreeBSD.ORG Subject: Time Driftine Really Fast References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running 4.0-current SMP of Apr 21 16:51:36 1999. Time appears to be drifting very fast, ~300 sec in 8 hours. dmesg and config attached at the end. I am using CLK_USE_I8254_CALIBRATION. On 27 Apr at about 2000, the system appeared to freeze for several seconds, while lightly loaded, one user, using emacs to edit a small (10k?) text file. 27 Apr 08:02:47 ntpdate: adjust time server 192.5.41.40 offset 0.268785 27 Apr 23:54:17 ntpdate: step time server 192.5.41.40 offset 564.832098 27 Apr 23:54:24 ntpdate: adjust time server 192.5.41.40 offset 0.092320 27 Apr 23:54:46 ntpdate: adjust time server 192.5.41.40 offset 0.269666 27 Apr 23:55:41 ntpdate: step time server 192.5.41.40 offset 0.807377 28 Apr 08:39:52 ntpdate: step time server 192.5.41.40 offset 310.876164 28 Apr 08:40:25 ntpdate: adjust time server 192.5.41.40 offset 0.327690 28 Apr 08:48:28 ntpdate: step time server 192.5.41.40 offset 4.873418 From /var/log/messages: Apr 16 23:10:46 celebris /kernel: Timecounter "i8254" frequency 1193024 Hz Apr 19 12:51:55 celebris /kernel: Timecounter "i8254" frequency 1193032 Hz Apr 20 07:23:17 celebris /kernel: Timecounter "i8254" frequency 1193036 Hz Apr 20 09:02:17 celebris /kernel: Timecounter "i8254" frequency 1193040 Hz From dmesg: Timecounter "i8254" frequency 1204957 Hz From sysctl: kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, \ profhz = 1024, stathz = 128 } machdep.adjkerntz: 0 machdep.wall_cmos_clock: 0 machdep.i8254_freq: 1204957 machdep.tsc_freq: 118502921 tomdean === dmesg ========================== irtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: PC87334 chipset (PS2/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed Apr 21 16:51:36 PDT 1999 tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1204957 Hz CPU: Pentium/P54C (586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 94953472 (92728K bytes) Programming 16 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02bf000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 ncr0: at device 1.0 on pci0 ncr0: interrupting at irq 11 isab0: at device 2.0 on pci0 de0: at device 8.0 on pci0 de0: interrupting at irq 10 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0 at port 0x378 irq 7 on isa0 ppc0: PC87334 chipset (PS2/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) changing root device to da1s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: cd present [322265 x 2048 byte records] cd9660: RockRidge Extension pid 11732 (as6811), uid 1001: exited on signal 11 (core dumped) pid 13990 (netscape), uid 1001: exited on signal 4 (core dumped) pid 14045 (netscape), uid 1001: exited on signal 11 (core dumped) pid 14050 (netscape), uid 1001: exited on signal 11 (core dumped) ==== config =================== # # CELEBRIS # # 970807 tomdean # # derived from $Id: GENERIC,v 1.91 1997/06/06 12:24:43 jkh Exp $ machine "i386" cpu "I586_CPU" ident CELEBRIS maxusers 50 ################################################################## # # options from mptable # #MPTable, version 2.0.11 # #-------------------------------------------------------------------------- # #MP Floating Pointer Structure: # # #location: EBDA # physical address: 0x0009fc30 # signature: '_MP_' # length: 16 bytes # version: 1.1 # checksum: 0x55 # mode: Virtual Wire # #-------------------------------------------------------------------------- # # MP default config type: 5 # # bus: ISA+PCI, APIC: Integrated # #-------------------------------------------------------------------------- # # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Lets always enable the kernel debugger for SMP. options DDB ################################################################## options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options SYSVSHM # for X11 options SYSVSEM # for X11 options SYSVMSG # for X11 #options PSM_CHECKSYNC # resync when switch console modes config kernel root on da1 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 # # FDC_DEBUG enables floppy debugging. Since the debug output is huge, you # gotta turn it actually on by setting the variable fd_debug with DDB, # however. options FDC_DEBUG options FDC_PRINT_BOGUS_CHIPTYPE disk fd0 at fdc0 drive 0 #tape ft0 at fdc0 drive 2 controller ncr0 controller scbus0 device da0 # SCSI Direct Access Device device sa0 # SCSI Tape device cd0 #Only need one of these, the code dynamically grows # The keyboard controller; it controlls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at atkbdc? tty irq 1 # `flags' for atkbd: # 0x01 Force detection of keyboard, else we always assume a keyboard # 0x02 Don't reset keyboard, useful for some newer ThinkPads # 0x04 Old-style (XT) keyboard support, useful for older ThinkPads device psm0 at atkbdc? tty irq 12 # The video card driver. device vga0 at isa? port ? conflicts # Splash screen at start up! Screen savers require this too. pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 # Parallel-Port Bus # nlpt Parallel Printer controller ppbus0 device lpt0 at ppbus? controller ppc0 at isa? port ? tty irq 7 device de0 # DEC DC21040 Ethernet Adapter pseudo-device loop pseudo-device ether pseudo-device tun 1 pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # use the calibrated value of the I8254 frequency # keep this to use with ~tomdean/bin/timecounter.pl options "CLK_USE_I8254_CALIBRATION" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 9:25:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id EEE7D14E94; Wed, 28 Apr 1999 09:25:29 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id MAA05043; Wed, 28 Apr 1999 12:25:28 -0400 (EDT) (envelope-from luoqi) Date: Wed, 28 Apr 1999 12:25:28 -0400 (EDT) From: Luoqi Chen Message-Id: <199904281625.MAA05043@lor.watermarkgroup.com> To: luoqi@watermarkgroup.com, phk@critter.freebsd.dk Subject: Re: HEADS UP! to commit SMP vmspace sharing patches Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199904272349.TAA28969@lor.watermarkgroup.com>, Luoqi Chen writes: > >I'm about to commit the SMP vmspace sharing patch (the %fs approach). All > >kernel modules will need to be recompiled. Recompilation is not neccessary > >for user land applications including ps, libkvm and friends. > > > >In this %fs approach, per-processor private pages are no longer mapped at > >identical virtual address for each cpu, instead a new segment descriptor (%fs) > >is setup to access per-cpu global variables like curproc. > > How is this accessed from C sources ? > curproc is now a macro defined as an inline asm function. > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 9:27:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 694CC14E94 for ; Wed, 28 Apr 1999 09:27:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id SAA28286; Wed, 28 Apr 1999 18:26:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id SAA24047; Wed, 28 Apr 1999 18:26:47 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Thomas Dean Cc: current@FreeBSD.ORG Subject: Re: Time Driftine Really Fast In-reply-to: Your message of "Wed, 28 Apr 1999 09:02:08 PDT." <199904281602.JAA17273@ix.netcom.com> Date: Wed, 28 Apr 1999 18:26:47 +0200 Message-ID: <24045.925316807@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904281602.JAA17273@ix.netcom.com>, Thomas Dean writes: >I am running 4.0-current SMP of Apr 21 16:51:36 1999. > >Time appears to be drifting very fast, ~300 sec in 8 hours. dmesg and config >attached at the end. I am using CLK_USE_I8254_CALIBRATION. Try to remove that option, if your RTC is at large it is a Really Bad Idea to use CLK_USE_I8254_CALIBRATION. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 9:31:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 7DD5F15752 for ; Wed, 28 Apr 1999 09:28:48 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id SAA28297 for ; Wed, 28 Apr 1999 18:28:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id SAA24071 for ; Wed, 28 Apr 1999 18:28:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: worldstone improvement... Date: Wed, 28 Apr 1999 18:28:35 +0200 Message-ID: <24069.925316915@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My 2 x 233MHz PPro has improved make world time by about 100 seconds out of 5000s = 2 % Not bad... Poul-Henning To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 9:44:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id E9FF014C04 for ; Wed, 28 Apr 1999 09:44:13 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id JAA97395; Wed, 28 Apr 1999 09:38:08 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904281638.JAA97395@troutmask.apl.washington.edu> Subject: Re: worldstone improvement... In-Reply-To: <24069.925316915@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 28, 1999 06:28:35 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Wed, 28 Apr 1999 09:38:08 -0700 (PDT) Cc: current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > My 2 x 233MHz PPro has improved make world time by about 100 seconds > out of 5000s = 2 % > > Not bad... > > Poul-Henning > I assume your "benchmarking" the recent changes Luoqi made to SMP? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 9:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from neunacht.netgsi.com (neunacht.netgsi.com [192.55.203.174]) by hub.freebsd.org (Postfix) with ESMTP id 6C11C14D59 for ; Wed, 28 Apr 1999 09:54:22 -0700 (PDT) (envelope-from cjohnson@neunacht.netgsi.com) Received: (from cjohnson@localhost) by neunacht.netgsi.com (8.9.2/8.9.2) id MAA37459; Wed, 28 Apr 1999 12:54:08 -0400 (EDT) (envelope-from cjohnson) From: "Christopher T. Johnson" Message-Id: <199904281654.MAA37459@neunacht.netgsi.com> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904130114.JAA21725@ariadne.tensor.pgs.com> from Stephen Hocking-Senior Programmer PGS Tensor Perth at "Apr 13, 99 09:14:18 am" To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Date: Wed, 28 Apr 1999 12:54:08 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some extra information on tape problems: FreeBSD neunacht.netgsi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Apr 22 16:50:33 EDT 1999 root@:/m/src/sys/compile/NEUNACHT i386 This is SMP machine with scsi only. The tape drive is an EXABYTE-8200. When doing tape IO that lasts for an extend period of time the tape drive will show an amber light. This normally means SCSI activity. At that point any reads or writes to the device happen at 1.4Mbytes/second when the max I know that this drive will do is 0.24 Mbytes/second. We've replaced the tape drive. We've tested with different tapes. It LOOKS like the drive is detecting some sort of error and then going into "toss data mode". This has cost me lots and lots of backups and is very distressing. One interesting data point. When I issue an mt erase command it runs for a fairly long time. It should runn for just over 2 hours. It gets about 3/4s of the way and stops. Again with the orange light. The interesting data point is that four tapes have all stopped at almost the same point. (Visual inspection of amount of media left on the reels.) Any help would be very nice. Thank you, Chris > When the tape hangs with an unkillable process, its relevant PS flags are > "physstrat" and "DL+". It doesn't hang forever, just a very long time, like > someone's confused milliseconds with microseconds, or some such. > > > Also, when writing to the 2nd tape in a CPIO archive, it doesn't actually > write to the tape. systat -vmstat records lots of stuff going to the tape > device (a SCSI QIC-525 in this case) very quickly - way beyond the speed it > can actually do but there's no actual activity. Dump on the otherhand seems > fine. > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 10: 0:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from bug.us.dell.com (bug.us.dell.com [143.166.12.35]) by hub.freebsd.org (Postfix) with ESMTP id A50201522A for ; Wed, 28 Apr 1999 10:00:32 -0700 (PDT) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bug.us.dell.com (8.8.8/8.8.8) with SMTP id LAA03046; Wed, 28 Apr 1999 11:58:07 -0500 (CDT) (envelope-from tony@dell.com) Message-Id: <3.0.6.32.19990428115805.03c08a50@bug.us.dell.com> X-Sender: tony@bug.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 28 Apr 1999 11:58:05 -0500 To: Nate Williams , Doug Rabson From: Tony Overfield Subject: RTC extmem - was: Re: suspend mode broken since one week ago Cc: Warner Losh , Nate Williams , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG In-Reply-To: <199904281414.IAA08646@mt.sri.com> References: <199904280422.WAA04592@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>[regarding RTC vs. BIOS selection algorithm] >I don't think this is complete, because I think (don't know) that many >older BIOS's only reported up to 64M of memory, so if you had more than >64M in the box it didn't report it. The RTC extmem cannot "report" >64 MB either. In fact, the RTC extmem is unreliable for many >64 MB systems. The only time reading the RTC extmem was helpful was when the BIOS reported less than 64 MB and the RTC extmem "reported" more than the BIOS, but still less than or equal to 64 MB. The exception to this is the case where the BIOS is trying to hide something from the operating system, such as the ACPI tables. Again, using the BIOS value is the right choice. Reading the RTC extmem value is only useful for systems that meet all of these requirements: 1. They do not support either of the newer BIOS memory functions, int 0x15 - 0xe820 or 0xe801. 2. They have an int 0x15 - 0x8800 function that is artificially limited to a value below 64 MB. 3. They do not have a BIOS that is trying to hide something important from the operating system. The number of systems for which this happens is becoming vanishingly small, IMO. (Yes, I do know which ones they were.) Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 10: 1:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-03.ix.netcom.com [207.93.148.3]) by hub.freebsd.org (Postfix) with ESMTP id D159E1540F for ; Wed, 28 Apr 1999 10:01:30 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id JAA17394; Wed, 28 Apr 1999 09:55:16 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Wed, 28 Apr 1999 09:55:16 -0700 (PDT) Message-Id: <199904281655.JAA17394@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: phk@critter.freebsd.dk Cc: current@FreeBSD.ORG In-reply-to: <24045.925316807@critter.freebsd.dk> (message from Poul-Henning Kamp on Wed, 28 Apr 1999 18:26:47 +0200) Subject: Re: Time Driftine Really Fast References: <24045.925316807@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We had this discussion last September, along with Mike Smith. We discussed using the calibration stuff in config, and not to use CLK_CALIBRATION_LOOP. It was noted the 8254 was unstable and TSC could not be used to improve it. As a result of the conversation, I wound up with CLK_USE_I8254_CALIBRATION. The drift of the clock started lately, within the past month. My config entry dates to last September. I will stop using the 8254. Thanks, tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 10:19:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 48AD615719 for ; Wed, 28 Apr 1999 10:19:26 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id KAA19155; Wed, 28 Apr 1999 10:16:06 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id KAA01008; Wed, 28 Apr 1999 10:19:25 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id KAA10145; Wed, 28 Apr 1999 10:16:28 -0700 To: phk@critter.freebsd.dk Cc: current@FreeBSD.ORG Subject: Re: worldstone improvement... In-Reply-To: Your message of "Wed, 28 Apr 1999 18:28:35 +0200" <24069.925316915@critter.freebsd.dk> References: <24069.925316915@critter.freebsd.dk> X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990428101628C.thomma@baynetworks.com> Date: Wed, 28 Apr 1999 10:16:28 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 9 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My 2 x 233MHz PPro has improved make world time by about 100 seconds > out of 5000s = 2 % My dual 200MHz PPro worldstone also improved almost 3 minutes (173 seconds) after Luoqi's SMP change. I think it's good improvement. Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11: 0:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 0A5C914D80; Wed, 28 Apr 1999 11:00:41 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA28701; Wed, 28 Apr 1999 20:00:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA24331; Wed, 28 Apr 1999 20:00:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Luoqi Chen Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: HEADS UP! to commit SMP vmspace sharing patches In-reply-to: Your message of "Wed, 28 Apr 1999 12:25:28 EDT." <199904281625.MAA05043@lor.watermarkgroup.com> Date: Wed, 28 Apr 1999 20:00:26 +0200 Message-ID: <24329.925322426@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904281625.MAA05043@lor.watermarkgroup.com>, Luoqi Chen writes: >> >In this %fs approach, per-processor private pages are no longer mapped at >> >identical virtual address for each cpu, instead a new segment descriptor (%fs) >> >is setup to access per-cpu global variables like curproc. >> >> How is this accessed from C sources ? >> >curproc is now a macro defined as an inline asm function. Not that I really miss far pointers, but right now we could use one... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11: 6:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7D01214E65 for ; Wed, 28 Apr 1999 11:06:18 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA07782; Wed, 28 Apr 1999 11:06:09 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 11:06:09 -0700 (PDT) From: Matthew Dillon Message-Id: <199904281806.LAA07782@apollo.backplane.com> To: "Christopher T. Johnson" Cc: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth), current@FreeBSD.ORG Subject: Re: Further on tape & CAM problems References: <199904281654.MAA37459@neunacht.netgsi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The amber LED on exabytes typically means 'drive needs cleaning'. Exabyte drives should be cleaned once or twice a week depending on how heavily you use them. If an exabyte drive is not cleaned on a regular basis, the transfer rate will drop steadily as the drive is forced to rewrite sectors on the tape. Additionally, the larger gaps produced by the rewrites will result in much less storage per tape. I dunno about the 8200. The mamoth exabytes can do 3 MBytes/sec. Any exabyte drive should transfer up to its rating. If it transfers more slowly, it is either damaged or in need of cleaning. When purchasing cleaning tapes, be sure to purchase the correct cleaning tapes for the type of drive you have. Exabytes tend to be fairly sensitive and putting in the wrong sort of cleaning tape can damage the head. -Matt Matthew Dillon :Some extra information on tape problems: : :FreeBSD neunacht.netgsi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Apr 22 :16:50:33 EDT 1999 root@:/m/src/sys/compile/NEUNACHT i386 : :This is SMP machine with scsi only. : :The tape drive is an EXABYTE-8200. : :When doing tape IO that lasts for an extend period of time the tape drive :will show an amber light. This normally means SCSI activity. At that :point any reads or writes to the device happen at 1.4Mbytes/second when :the max I know that this drive will do is 0.24 Mbytes/second. : :We've replaced the tape drive. We've tested with different tapes. : :It LOOKS like the drive is detecting some sort of error and then going :into "toss data mode". This has cost me lots and lots of backups and :is very distressing. : :One interesting data point. When I issue an mt erase command it runs for :a fairly long time. It should runn for just over 2 hours. It gets about :3/4s of the way and stops. Again with the orange light. The interesting :data point is that four tapes have all stopped at almost the same point. :(Visual inspection of amount of media left on the reels.) : :Any help would be very nice. : : Thank you, : Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11: 8:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id AAF09151D1; Wed, 28 Apr 1999 11:08:14 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA19247; Wed, 28 Apr 1999 14:02:01 -0400 (EDT) Date: Wed, 28 Apr 1999 14:02:01 -0400 (EDT) From: Chuck Robey To: Poul-Henning Kamp Cc: Luoqi Chen , current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: HEADS UP! to commit SMP vmspace sharing patches In-Reply-To: <24329.925322426@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Poul-Henning Kamp wrote: > In message <199904281625.MAA05043@lor.watermarkgroup.com>, Luoqi Chen writes: > > >> >In this %fs approach, per-processor private pages are no longer mapped at > >> >identical virtual address for each cpu, instead a new segment descriptor (%fs) > >> >is setup to access per-cpu global variables like curproc. > >> > >> How is this accessed from C sources ? > >> > >curproc is now a macro defined as an inline asm function. > > Not that I really miss far pointers, but right now we could use one... No profanity on this list (and Poul, far-pointers were very definitely profane!) Go wash out your mouth! ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:12:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id D7F6715012 for ; Wed, 28 Apr 1999 11:12:35 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id UAA22882 for ; Wed, 28 Apr 1999 20:12:33 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma022880; Wed, 28 Apr 99 20:12:33 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id UAA04898 for ; Wed, 28 Apr 1999 20:12:32 +0200 (MET DST) Received: (qmail 14461 invoked by uid 666); 28 Apr 1999 18:12:54 -0000 Date: Wed, 28 Apr 1999 20:12:54 +0200 From: Jos Backus To: current@freebsd.org Subject: Re: -current's routing code... Message-ID: <19990428201254.A14332@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <4.1.19990426221303.00924da0@216.67.14.69> <199904271419.IAA17797@harmony.village.org> <199904271921.MAA05271@vashon.polstra.com> <19990427233818.A66120@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990427233818.A66120@hal.mpn.cp.philips.com>; from Jos Backus on Tue, Apr 27, 1999 at 11:38:18PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fwiw: The patch below unbreaks -current for me. [Luoqi Chen's message <199904270645.CAA21642@lor.watermarkgroup.com> below] This broke routing, part of the route domain init needs to be done after all domains are attached. It happened that the new kernel I just made listed routedomain before inetdomain... -lq Index: route.c =================================================================== RCS file: /home/ncvs/src/sys/net/route.c,v retrieving revision 1.51 diff -u -r1.51 route.c --- route.c 1999/01/27 22:42:14 1.51 +++ route.c 1999/04/27 06:22:50 @@ -43,6 +43,7 @@ #include #include #include +#include #include #include @@ -77,7 +78,9 @@ route_init() { rn_init(); /* initialize all zeroes, all ones, mask table */ +#if 0 rtable_init((void **)rt_tables); +#endif } /* @@ -1062,3 +1065,5 @@ } return (error); } + +SYSINIT(rtable, SI_SUB_PROTO_DOMAIN, SI_ORDER_ANY, rtable_init, rt_tables); -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:16:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7B70A1521D for ; Wed, 28 Apr 1999 11:16:02 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA03288; Wed, 28 Apr 1999 20:15:55 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904281815.UAA03288@freebsd.dk> Subject: Re: worldstone improvement... In-Reply-To: <19990428101628C.thomma@baynetworks.com> from Tamiji Homma at "Apr 28, 1999 10:16:28 am" To: thomma@baynetworks.com (Tamiji Homma) Date: Wed, 28 Apr 1999 20:15:55 +0200 (CEST) Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Tamiji Homma wrote: > > My 2 x 233MHz PPro has improved make world time by about 100 seconds > > out of 5000s = 2 % > > My dual 200MHz PPro worldstone also improved almost 3 minutes > (173 seconds) after Luoqi's SMP change. Yep, I see the same here, good job!! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:19:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B98A71521D; Wed, 28 Apr 1999 11:19:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA07937; Wed, 28 Apr 1999 11:19:17 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 11:19:17 -0700 (PDT) From: Matthew Dillon Message-Id: <199904281819.LAA07937@apollo.backplane.com> To: Chuck Robey Cc: Poul-Henning Kamp , Luoqi Chen , current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: HEADS UP! to commit SMP vmspace sharing patches References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know this is a little late ... but I don't suppose there might be a way to lock a TLB entry in place? That would solve the problem too. Baring that, %fs is the way to go. I am happily compiling up a new SMP kernel as we speak :-). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:26:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.digitalselect.net (mail.digitalselect.net [216.181.1.6]) by hub.freebsd.org (Postfix) with ESMTP id 9F02515481 for ; Wed, 28 Apr 1999 11:26:22 -0700 (PDT) (envelope-from adhir@forumone.com) Received: from digitalselect ([216.181.56.84]) by mail.digitalselect.net (8.8.7/8.8.7) with SMTP id OAA23758; Wed, 28 Apr 1999 14:25:41 -0400 Reply-To: From: "Alok K. Dhir" To: "Tamiji Homma" , Cc: Subject: RE: worldstone improvement... Date: Wed, 28 Apr 1999 14:26:39 -0400 Message-ID: <003001be91a4$a8095300$5438b5d8@net> 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 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <19990428101628C.thomma@baynetworks.com> Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are these changes going to be committed to -stable? Tx > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Tamiji Homma > Sent: Wednesday, April 28, 1999 1:16 PM > To: phk@critter.freebsd.dk > Cc: current@FreeBSD.ORG > Subject: Re: worldstone improvement... > > > > My 2 x 233MHz PPro has improved make world time by about 100 seconds > > out of 5000s = 2 % > > My dual 200MHz PPro worldstone also improved almost 3 minutes > (173 seconds) after Luoqi's SMP change. > > I think it's good improvement. > > Tammy > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:26:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from neunacht.netgsi.com (neunacht.netgsi.com [192.55.203.174]) by hub.freebsd.org (Postfix) with ESMTP id 3813A14EE9 for ; Wed, 28 Apr 1999 11:26:49 -0700 (PDT) (envelope-from cjohnson@neunacht.netgsi.com) Received: (from cjohnson@localhost) by neunacht.netgsi.com (8.9.2/8.9.2) id OAA37667; Wed, 28 Apr 1999 14:26:24 -0400 (EDT) (envelope-from cjohnson) From: "Christopher T. Johnson" Message-Id: <199904281826.OAA37667@neunacht.netgsi.com> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904281806.LAA07782@apollo.backplane.com> from Matthew Dillon at "Apr 28, 99 11:06:09 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 28 Apr 1999 14:26:24 -0400 (EDT) Cc: shocking@prth.pgs.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew, Thanks I should have been more clear. The amber LED on 8205s and 8505s and any of the half hight drives blink when they need cleaning. This is the original 8200 full hight drives. They have no cleaning indicator. The drive is cleaned every monday before the amflush. We use exabyte 8mm cleaning cartridges as specified for the 8200. When the problem first occured I immedieatly used the cleaning cart and that did not solve the problem of the amber light. REGARDLESS! The drive is reporting an error condition and that error is NOT getting back to user land. I've verified the problem with amdump amflush and dd. In ALL cases once the amber light goes on solid systat -vmstat shows a solid 1.4MB/second data transfer into never never land. Thanks, Chris P.S. This is not the only reply suggesting head cleaning. I should have mentiond that. I did mention that I replaced the drive rather than suspect our drivers. *GRIN* > The amber LED on exabytes typically means 'drive needs cleaning'. Exabyte > drives should be cleaned once or twice a week depending on how heavily > you use them. If an exabyte drive is not cleaned on a regular basis, the > transfer rate will drop steadily as the drive is forced to rewrite sectors > on the tape. Additionally, the larger gaps produced by the rewrites will > result in much less storage per tape. > > I dunno about the 8200. The mamoth exabytes can do 3 MBytes/sec. Any > exabyte drive should transfer up to its rating. If it transfers more > slowly, it is either damaged or in need of cleaning. > > When purchasing cleaning tapes, be sure to purchase the correct cleaning > tapes for the type of drive you have. Exabytes tend to be fairly sensitive > and putting in the wrong sort of cleaning tape can damage the head. > > -Matt > Matthew Dillon > > > :Some extra information on tape problems: > : > :FreeBSD neunacht.netgsi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Apr 22 > :16:50:33 EDT 1999 root@:/m/src/sys/compile/NEUNACHT i386 > : > :This is SMP machine with scsi only. > : > :The tape drive is an EXABYTE-8200. > : > :When doing tape IO that lasts for an extend period of time the tape drive > :will show an amber light. This normally means SCSI activity. At that > :point any reads or writes to the device happen at 1.4Mbytes/second when > :the max I know that this drive will do is 0.24 Mbytes/second. > : > :We've replaced the tape drive. We've tested with different tapes. > : > :It LOOKS like the drive is detecting some sort of error and then going > :into "toss data mode". This has cost me lots and lots of backups and > :is very distressing. > : > :One interesting data point. When I issue an mt erase command it runs for > :a fairly long time. It should runn for just over 2 hours. It gets about > :3/4s of the way and stops. Again with the orange light. The interesting > :data point is that four tapes have all stopped at almost the same point. > :(Visual inspection of amount of media left on the reels.) > : > :Any help would be very nice. > : > : Thank you, > : Chris > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:28:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A880014E99 for ; Wed, 28 Apr 1999 11:28:39 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA07993; Wed, 28 Apr 1999 11:28:38 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 11:28:38 -0700 (PDT) From: Matthew Dillon Message-Id: <199904281828.LAA07993@apollo.backplane.com> To: Jim Shankland Cc: current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. References: <199904281658.JAA01524@biggusdiskus.flyingfox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon writes: : :> Given the choice between OSPF and RIP1/2, OSPF is far superior :> even on 'simple' networks. It is effectively an open protocol, :> like BGP. : :Matt, can you clarify what you mean by "open" here? I know it's :what the "O" in OSPF stands for, but in what way are OSPF and :BGP more open than RIP? : :Jim Shankland :NLynx Systems, Inc. You can download the protocol spec without putting forth cash. I haven't looked at it for a long time so I don't have a URL handy. OSPF has been around for a long time. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:33:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 663F015782 for ; Wed, 28 Apr 1999 11:33:17 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA41250; Wed, 28 Apr 1999 19:33:18 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 28 Apr 1999 19:33:18 +0100 (BST) From: Doug Rabson To: Nate Williams Cc: Warner Losh , Alex Zepeda , Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: suspend mode broken since one week ago In-Reply-To: <199904281414.IAA08646@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Nate Williams wrote: > > > : Someone submitted a patch that checked to see if the BIOS returned a > > > : value > 64M, and if so to 'accept' it's value for the memory, since it's > > > : more likely to be correct. I'd like to apply it to -current, but I'm > > > : not sure of the political ramifications.... > > > > > > I think that it would be OK to do this, especially if you were able to > > > sanity check the numbers against something else... If it isn't > > > possible to do a sanity check, then I'd still be tempted to commit it, > > > making it an option if it causes problems for a significant number (> > > > 1%) of people. > > > > My patch looks like this: > > > > Index: machdep.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v > > retrieving revision 1.330 > > diff -u -r1.330 machdep.c > > --- machdep.c 1999/04/19 14:14:12 1.330 > > +++ machdep.c 1999/04/26 13:20:30 > > @@ -1403,8 +1403,9 @@ > > } > > } > > if (bootinfo.bi_extmem != biosextmem) > > - printf("BIOS extmem (%uK) != RTC extmem (%uK)\n", > > + printf("BIOS extmem (%uK) != RTC extmem (%uK), setting to BIOS value\n", > > bootinfo.bi_extmem, biosextmem); > > + biosextmem = bootinfo.bi_extmem; > > } > > > > #ifdef SMP > > > > I don't think this is complete, because I think (don't know) that many > older BIOS's only reported up to 64M of memory, so if you had more than > 64M in the box it didn't report it. > > However, I can't verify this since I don't have any machines with > 64M > of memory. I wasn't intending to commit the patch since I don't really understand all the compatibility problems. I just wanted to be able to read the ACPI tables on my laptop... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:35:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from krabi.mbp.ee (krabi.mbp.ee [194.204.12.83]) by hub.freebsd.org (Postfix) with ESMTP id DB03815886 for ; Wed, 28 Apr 1999 11:35:37 -0700 (PDT) (envelope-from mauri@krabi.mbp.ee) Received: from localhost (mauri@localhost) by krabi.mbp.ee (8.9.3/8.9.3) with ESMTP id VAA00806 for ; Wed, 28 Apr 1999 21:35:36 +0300 (EEST) (envelope-from mauri@krabi.mbp.ee) Date: Wed, 28 Apr 1999 21:35:36 +0300 (EEST) From: Lauri Laupmaa To: current@freebsd.org Subject: new clock good for unix (FreeBSD) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Just wondering if the new swatch clock has its way into the date command... _____________ Lauri Laupmaa ...speaking for myself only... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:37:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 7E36E1571B for ; Wed, 28 Apr 1999 11:37:39 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA19411; Wed, 28 Apr 1999 14:34:51 -0400 (EDT) Date: Wed, 28 Apr 1999 14:34:51 -0400 (EDT) From: Chuck Robey To: Matthew Dillon Cc: Jim Shankland , current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <199904281828.LAA07993@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Matthew Dillon wrote: > > :Matthew Dillon writes: > : > :> Given the choice between OSPF and RIP1/2, OSPF is far superior > :> even on 'simple' networks. It is effectively an open protocol, > :> like BGP. > : > :Matt, can you clarify what you mean by "open" here? I know it's > :what the "O" in OSPF stands for, but in what way are OSPF and > :BGP more open than RIP? > : > :Jim Shankland > :NLynx Systems, Inc. > > You can download the protocol spec without putting forth cash. > I haven't looked at it for a long time so I don't have a URL handy. And you didn't know that the RIP spec is even older, and was publicly available via an RFC (the same as OSPF?) I can't quite figure why they stuck the word "open" in there, because it couldn't possibly be more open than RIP. > > OSPF has been around for a long time. But RIP is older, and was the first routing scheme. > > -Matt > Matthew Dillon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:41:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D2B2C15481; Wed, 28 Apr 1999 11:41:09 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA41287; Wed, 28 Apr 1999 19:41:25 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 28 Apr 1999 19:41:25 +0100 (BST) From: Doug Rabson To: Bill Paul Cc: Matthew Dillon , hackers@freebsd.org, current@freebsd.org Subject: Re: NFS Patch #8 for current available - new TCP fixes In-Reply-To: <199904281327.JAA29467@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Matthew Dillon > had to walk into mine and say: > > > (fanfair!) > > (Darth Vader's imperial march theme) > > > NFS Patch #8 for -current is now available. This patch fixes serious bugs > > w/ NFS/TCP. Probably not *all* the failure conditions, but hopefully > > most of them. > [...] > > > Neither the 'de' nor the 'xl' ethernet drivers align the packet. The 'xl' > > driver conditionally aligns it for the alpha. Part of the patch fixes > > the 'xl' driver to unconditionally align the packet buffer in order to > > improve NFS performance. I could not do the same for the 'de' driver > > because I am unsure if the dec chipset can handle an unaligned start > > address. > > >From what I can tell, the DEC parts make you specify an RX DMA buffer > address that is longword aligned. There are actually not that many devices > where you're allowed to use arbitrary byte-aligned addresses for receive > buffers (the 3Com XL and Intel 'speedo' chips let you do it, as well as the > ThunderLAN, and the Alteon Tigon NIC; I _think_ the AMD PCnet/LANCE > devices let you do it, but that's about it). > > For parts that don't support arbitrary alignment, you have to copy. > Now, in some of the drivers that I ported to the alpha, I only copied > the first small section of the packet in order to get the IP header > aligned (since failing to do this causes an unaligned access trap in > the IP code). This is faster than copying the entire packet to fix > the alignment, but I'm not sure what effect it has on NFS. > > That said, although I haven't looked too closely at the de driver (it > scares me -- a lot), it should have some sort of gimmick to fix the > packet alignment otherwise it wouldn't work on the alpha. The de driver copies the entire packet. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:42:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 09412157E8 for ; Wed, 28 Apr 1999 11:42:16 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA01922 for ; Wed, 28 Apr 1999 11:42:15 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 28 Apr 1999 11:42:14 -0700 (PDT) From: Doug White To: current@freebsd.org Subject: /usr/share/examples/atapi scripts wrong Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ... The burn* scripts in /usr/share/examples/atapi try to use wormcontrol for some reason, which obviously doesn't work. Should we just dump them, or does someone have one that uses mkisofs/cdrecord that would be appropriate? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 11:55:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4001014D36 for ; Wed, 28 Apr 1999 11:55:44 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA03456; Wed, 28 Apr 1999 20:55:23 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904281855.UAA03456@freebsd.dk> Subject: Re: /usr/share/examples/atapi scripts wrong In-Reply-To: from Doug White at "Apr 28, 1999 11:42:14 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Wed, 28 Apr 1999 20:55:23 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Doug White wrote: > Hello ... > > The burn* scripts in /usr/share/examples/atapi try to use wormcontrol for > some reason, which obviously doesn't work. Should we just dump them, or > does someone have one that uses mkisofs/cdrecord that would be > appropriate? What planet are you from ?? They work for ATAPI drives, and have been since they were introduced, all the time using wormcontrol.. Our SCSI system (CAM) dont support wormdevices (the old did), but that is something totally unrelated to /usr/share/examples/atapi. ^^^^^ Or you where just kidding ?? :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12: 9:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 160B51507F for ; Wed, 28 Apr 1999 12:09:55 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA08470; Wed, 28 Apr 1999 12:09:44 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 12:09:44 -0700 (PDT) From: Matthew Dillon Message-Id: <199904281909.MAA08470@apollo.backplane.com> To: Chuck Robey Cc: Jim Shankland , current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :couldn't possibly be more open than RIP. : :> :> OSPF has been around for a long time. : :But RIP is older, and was the first routing scheme. Which means.... nothing. RIP was designed for a time when networks were simple. It has no multipath capabilities, it can *barely* handle subnet masks, and it figures out when a route is dead by letting packets loop until their TTL runs out. Also, propogation of state loads the network in a non linear fashion and breaks down when you have a lot of nodes. It works, but it isn't fun. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:12:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 62FC2154A9 for ; Wed, 28 Apr 1999 12:12:31 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 67010 invoked by uid 1001); 28 Apr 1999 19:12:30 +0000 (GMT) To: chuckr@picnic.mat.net Cc: current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 28 Apr 1999 14:34:51 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 28 Apr 1999 21:12:29 +0200 Message-ID: <67008.925326749@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I can't quite figure why they stuck the word "open" in there, because it > couldn't possibly be more open than RIP. Probably because it was (at the time) in heavy "competition" with the OSI IS-IS routing protocol. Those standards were *not* openly available. (I believe they are now.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:14: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 11EB91578E for ; Wed, 28 Apr 1999 12:14:06 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA08534; Wed, 28 Apr 1999 12:14:03 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 12:14:03 -0700 (PDT) From: Matthew Dillon Message-Id: <199904281914.MAA08534@apollo.backplane.com> To: sthaug@nethelp.no Cc: chuckr@picnic.mat.net, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. References: <67008.925326749@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I can't quite figure why they stuck the word "open" in there, because it :> couldn't possibly be more open than RIP. : :Probably because it was (at the time) in heavy "competition" with the OSI :IS-IS routing protocol. Those standards were *not* openly available. (I :believe they are now.) : :Steinar Haug, Nethelp consulting, sthaug@nethelp.no I consider ISIS dead these days, though I'm sure there are people who still swear by it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:14:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by hub.freebsd.org (Postfix) with ESMTP id 9DB9F15764 for ; Wed, 28 Apr 1999 12:14:42 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id NAA02091; Wed, 28 Apr 1999 13:18:34 -0700 (PDT) Date: Wed, 28 Apr 1999 13:18:34 -0700 (PDT) From: Jim Shankland Message-Id: <199904282018.NAA02091@biggusdiskus.flyingfox.com> To: dillon@apollo.backplane.com Subject: Re: Our routed - Vern says it's old and buggy. Cc: current@freebsd.org In-Reply-To: <199904281828.LAA07993@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Umm ... OK, I thought you were saying that OSPF and BGP are "open", whereas RIP v1 and v2 are not. In that context, I wasn't sure what you meant by "open". If "open" means freely downloadable spec, then presumably all of the above are open. So never mind :-). Jim Shankland NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:17:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.t.dk (freesbee.t.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with SMTP id 98BF614EC4 for ; Wed, 28 Apr 1999 12:17:42 -0700 (PDT) (envelope-from jesper@freesbee.t.dk) Received: (qmail 11005 invoked by uid 1001); 28 Apr 1999 19:17:41 -0000 Date: Wed, 28 Apr 1999 21:17:41 +0200 From: Jesper Skriver To: Matthew Dillon Cc: sthaug@nethelp.no, chuckr@picnic.mat.net, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. Message-ID: <19990428211741.A10891@skriver.dk> References: <67008.925326749@verdi.nethelp.no> <199904281914.MAA08534@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199904281914.MAA08534@apollo.backplane.com>; from Matthew Dillon on Wed, Apr 28, 1999 at 12:14:03PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 12:14:03PM -0700, Matthew Dillon wrote: > > :Probably because it was (at the time) in heavy "competition" with the OSI > :IS-IS routing protocol. Those standards were *not* openly available. (I > :believe they are now.) > : > :Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > I consider ISIS dead these days, though I'm sure there are people who > still swear by it. Yes, it has some very nice features over OSPF, like the ability to have hundreds of routers in the "backbone area", a serious problem with OSPF when you have a rapid growing network, and it's impossible to know exactly where you need to grow new areas in 2 years time ... Yes, we run I-ISIS, and is very happy with it ... /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) 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-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:19:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id AC53A157A5 for ; Wed, 28 Apr 1999 12:19:13 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id VAA29191; Wed, 28 Apr 1999 21:19:09 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA24842; Wed, 28 Apr 1999 21:18:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: sthaug@nethelp.no, chuckr@picnic.mat.net, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-reply-to: Your message of "Wed, 28 Apr 1999 12:14:03 PDT." <199904281914.MAA08534@apollo.backplane.com> Date: Wed, 28 Apr 1999 21:18:58 +0200 Message-ID: <24840.925327138@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904281914.MAA08534@apollo.backplane.com>, Matthew Dillon writes: > >:> I can't quite figure why they stuck the word "open" in there, because it >:> couldn't possibly be more open than RIP. >: >:Probably because it was (at the time) in heavy "competition" with the OSI >:IS-IS routing protocol. Those standards were *not* openly available. (I >:believe they are now.) >: >:Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > I consider ISIS dead these days, though I'm sure there are people who > still swear by it. He, the Danish telecom is spending several millions DKR right now on a study for the future strategy of their CMIP based network management, so I'm sure somebody is running IS-IS somewhere too :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:22:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id C1EA81552E for ; Wed, 28 Apr 1999 12:22:11 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 67283 invoked by uid 1001); 28 Apr 1999 19:22:11 +0000 (GMT) To: dillon@apollo.backplane.com Cc: current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 28 Apr 1999 12:14:03 -0700 (PDT)" References: <199904281914.MAA08534@apollo.backplane.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 28 Apr 1999 21:22:11 +0200 Message-ID: <67281.925327331@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I consider ISIS dead these days, though I'm sure there are people who > still swear by it. As far as I know, there is *active* development of IS-IS these days, see for instance: "IS-IS Optimized Multipath (ISIS-OMP)", Tony Li, Curtis Villamizar, 02/23/1999, "IS-IS extensions for Traffic Engineering", Tony Li, Henk Smit, 02/02/1999, "L1/L2 Optimal IS-IS Routing", Antoni Przygienda, Ajay Patel, 02/19/1999, "Domain-wide Prefix Distribution with Multi-Level IS-IS", Tony Li, 02/26/1999, Tony Li (Juniper, ex Cisco) is the head of this particular working group. Also, it's used by some rather big backbone providers. PS: No, this is not meant to start a flame war/discussion about the merits and demerits of various routing protocols. We use OSPF as an IGP ourselves. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:27:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 977B614C45 for ; Wed, 28 Apr 1999 12:27:22 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id OAA78175; Wed, 28 Apr 1999 14:24:15 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 28 Apr 1999 14:24:14 -0500 (CDT) From: Chris Dillon To: sthaug@nethelp.no Cc: chuckr@picnic.mat.net, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <67008.925326749@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999 sthaug@nethelp.no wrote: > > I can't quite figure why they stuck the word "open" in there, because it > > couldn't possibly be more open than RIP. > > Probably because it was (at the time) in heavy "competition" with the OSI > IS-IS routing protocol. Those standards were *not* openly available. (I > believe they are now.) Someone correct me if I'm wrong, but OSPF stands for Open Shortest Path First, and thus "Open" in this context would have nothing to do with how "free" it is. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:36:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id CF78B14EDE for ; Wed, 28 Apr 1999 12:36:08 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA13620; Wed, 28 Apr 1999 21:12:23 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id UAA01026; Wed, 28 Apr 1999 20:45:36 +0200 (CEST) From: Wilko Bulte Message-Id: <199904281845.UAA01026@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904281654.MAA37459@neunacht.netgsi.com> from "Christopher T. Johnson" at "Apr 28, 1999 12:54: 8 pm" To: cjohnson@neunacht.netgsi.com (Christopher T. Johnson) Date: Wed, 28 Apr 1999 20:45:36 +0200 (CEST) Cc: shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Christopher T. Johnson wrote ... > Some extra information on tape problems: > > FreeBSD neunacht.netgsi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Apr 22 > 16:50:33 EDT 1999 root@:/m/src/sys/compile/NEUNACHT i386 > > This is SMP machine with scsi only. > > The tape drive is an EXABYTE-8200. > > When doing tape IO that lasts for an extend period of time the tape drive > will show an amber light. This normally means SCSI activity. At that > point any reads or writes to the device happen at 1.4Mbytes/second when > the max I know that this drive will do is 0.24 Mbytes/second. The drive is speced for 270 kb/sec max IRRC. > We've replaced the tape drive. We've tested with different tapes. > > It LOOKS like the drive is detecting some sort of error and then going > into "toss data mode". This has cost me lots and lots of backups and > is very distressing. Exabyte is not particularly famous for stable firmware. I have a 8200 here and a 4.0-current testbox. No SMP though, a lowly P100 machine. I'll give it a try and report later today. > One interesting data point. When I issue an mt erase command it runs for > a fairly long time. It should runn for just over 2 hours. It gets about > 3/4s of the way and stops. Again with the orange light. The interesting > data point is that four tapes have all stopped at almost the same point. > (Visual inspection of amount of media left on the reels.) I can also try that, but it'll probably take until tomorrow. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:36:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id D780E15163 for ; Wed, 28 Apr 1999 12:36:02 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id UAA24419; Wed, 28 Apr 1999 20:35:55 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 28 Apr 1999 20:26:24 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 28 Apr 1999 20:26:24 +0000 To: Doug White From: Bob Bishop Subject: Re: /usr/share/examples/atapi scripts wrong Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 11:42 am -0700 28/4/99, Doug White wrote: > >The burn* scripts in /usr/share/examples/atapi try to use wormcontrol for >some reason, which obviously doesn't work.[etc] Er, I think it does. It's SCSI/CAM which has lost the worm device, not ATAPI. See also misc/10351. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:41:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 0960614EDE for ; Wed, 28 Apr 1999 12:41:11 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id VAA29867 for freebsd-current@freebsd.org; Wed, 28 Apr 1999 21:41:04 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id A317440; Wed, 28 Apr 1999 21:39:48 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 7FEA81E19 for ; Wed, 28 Apr 1999 21:39:48 +0200 (CEST) Date: Wed, 28 Apr 1999 21:39:48 +0200 (CEST) From: Blaz Zupan To: freebsd-current@freebsd.org Subject: Broken Linux emulation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After doing a make world today and compiling a new kernel, the Linux netscape 4.51 does not work anymore. It immediately core dumps: /home/blaz> netscape Illegal instruction (core dumped) /home/blaz> gdb /usr/local/netscape-4.51/communicator-4.51.bin communicator-4.5. core GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... warning: core file may not match specified executable file. Core was generated by `communicator-4.5'. Program terminated with signal 4, Illegal instruction. /usr/X11R6/lib/libXt.so.6.0: No such file or directory. #0 0x836fefd in XP_ListNextEncodingType () (gdb) bt #0 0x836fefd in XP_ListNextEncodingType () #1 0x8370327 in NET_RegisterContentTypeConverter () #2 0x866fa3f in NF_RegisterConverters () #3 0x866be2a in NF_FontBrokerInitialize () #4 0x823e695 in fe_ComputeFontSizeTable () #5 0x823e965 in fe_InitFonts () #6 0x826d32c in main () #7 0x8231edb in ___crt_dummy__ () (gdb) Before anybody asks why I use the Linux netscape binary, there is no Flash and Acrobat plugin for the FreeBSD version. I also noticed the problem reported by others which C++ programs: /home/blaz> /usr/local/etc/rc.d/xfstt.sh /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "__vt_7filebuf" Blaz Zupan, blaz@amis.net, http://www.herbie.amis.net Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:49: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 6DFD414EDE for ; Wed, 28 Apr 1999 12:49:01 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA21208; Wed, 28 Apr 1999 13:48:17 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA10488; Wed, 28 Apr 1999 13:48:16 -0600 Date: Wed, 28 Apr 1999 13:48:16 -0600 Message-Id: <199904281948.NAA10488@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: sthaug@nethelp.no, chuckr@picnic.mat.net, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <199904281914.MAA08534@apollo.backplane.com> References: <67008.925326749@verdi.nethelp.no> <199904281914.MAA08534@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> I can't quite figure why they stuck the word "open" in there, because it > :> couldn't possibly be more open than RIP. > : > :Probably because it was (at the time) in heavy "competition" with the OSI > :IS-IS routing protocol. Those standards were *not* openly available. (I > :believe they are now.) > : > :Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > I consider ISIS dead these days, though I'm sure there are people who > still swear by it. And some who swear *at* it still. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 12:59:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 40CF0154CB for ; Wed, 28 Apr 1999 12:59:20 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id VAA03001 for freebsd-current@FreeBSD.ORG; Wed, 28 Apr 1999 21:59:18 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id 7181340; Wed, 28 Apr 1999 21:55:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 38B021E1A for ; Wed, 28 Apr 1999 21:55:41 +0200 (CEST) Date: Wed, 28 Apr 1999 21:55:41 +0200 (CEST) From: Blaz Zupan To: freebsd-current@FreeBSD.ORG Subject: Re: Broken Linux emulation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Blaz Zupan wrote: > After doing a make world today and compiling a new kernel, the Linux > netscape 4.51 does not work anymore. It immediately core dumps: Sigh. Ignore my mail. I failed to follow the first rule of posting: think before you post. I cvsupped between make world and making kernel, so my /modules and kernel got out of sync. Recompiling modules fixed the problem. Sorry again for the wasted bandwidth. Blaz Zupan, blaz@amis.net, http://www.herbie.amis.net Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 13:15:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id E7B351577D; Wed, 28 Apr 1999 13:15:01 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id PAA24466; Wed, 28 Apr 1999 15:14:54 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id PAA15451; Wed, 28 Apr 1999 15:14:54 -0500 (CDT) Date: Wed, 28 Apr 1999 15:14:54 -0500 From: Alan Cox To: Matthew Dillon Cc: Chuck Robey , Poul-Henning Kamp , Luoqi Chen , current@freebsd.org, smp@freebsd.org Subject: Re: HEADS UP! to commit SMP vmspace sharing patches Message-ID: <19990428151454.O1121@nonpc.cs.rice.edu> References: <199904281819.LAA07937@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199904281819.LAA07937@apollo.backplane.com>; from Matthew Dillon on Wed, Apr 28, 1999 at 11:19:17AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 11:19:17AM -0700, Matthew Dillon wrote: > I know this is a little late ... but I don't suppose there might be a > way to lock a TLB entry in place? That would solve the problem too. > Baring that, %fs is the way to go. > Unfortunately, on the x86, the answer is "No." The only serious alternative was to put the commonly used per processor variables and a pointer to the less commonly used ones at the base of each process's/thread's kernel stack, i.e., the upages, where you could mask off bits from the stack pointer to arrive at the correct address. You'd then have to "refresh" most of these variables on a context switch (in case the process migrated). Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 13:18:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1453315796 for ; Wed, 28 Apr 1999 13:18:54 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA15382; Wed, 28 Apr 1999 21:50:01 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id VAA01921; Wed, 28 Apr 1999 21:38:45 +0200 (CEST) From: Wilko Bulte Message-Id: <199904281938.VAA01921@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904281826.OAA37667@neunacht.netgsi.com> from "Christopher T. Johnson" at "Apr 28, 1999 2:26:24 pm" To: cjohnson@neunacht.netgsi.com (Christopher T. Johnson) Date: Wed, 28 Apr 1999 21:38:45 +0200 (CEST) Cc: dillon@apollo.backplane.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Christopher T. Johnson wrote ... > REGARDLESS! > The drive is reporting an error condition and that error is NOT > getting back to user land. I've verified the problem with amdump Oh? Where/what is the error, does the console tell you? > amflush and dd. In ALL cases once the amber light goes on solid > systat -vmstat shows a solid 1.4MB/second data transfer into > never never land. That sounds like a bug. But it could be CAM not understanding that the 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte lockup.. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 13:19:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 382471576F for ; Wed, 28 Apr 1999 13:18:54 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA15379; Wed, 28 Apr 1999 21:49:59 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id VAA01869; Wed, 28 Apr 1999 21:32:34 +0200 (CEST) From: Wilko Bulte Message-Id: <199904281932.VAA01869@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904281806.LAA07782@apollo.backplane.com> from Matthew Dillon at "Apr 28, 1999 11: 6: 9 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 28 Apr 1999 21:32:34 +0200 (CEST) Cc: cjohnson@neunacht.netgsi.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Matthew Dillon wrote ... > The amber LED on exabytes typically means 'drive needs cleaning'. Exabyte > drives should be cleaned once or twice a week depending on how heavily > you use them. If an exabyte drive is not cleaned on a regular basis, the > transfer rate will drop steadily as the drive is forced to rewrite sectors > on the tape. Additionally, the larger gaps produced by the rewrites will > result in much less storage per tape. Very true. But a 8200 only has a green and an amber LED. Amber is SCSI activity on this model. > I dunno about the 8200. The mamoth exabytes can do 3 MBytes/sec. Any > exabyte drive should transfer up to its rating. If it transfers more > slowly, it is either damaged or in need of cleaning. The 8200 is Mark I and is dog slow compared to the later models. > When purchasing cleaning tapes, be sure to purchase the correct cleaning > tapes for the type of drive you have. Exabytes tend to be fairly sensitive > and putting in the wrong sort of cleaning tape can damage the head. Yep, stay away from the Video8 cleaning cartridges. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 13:26:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from charon.khoral.com (charon.khoral.com [209.75.155.97]) by hub.freebsd.org (Postfix) with SMTP id 8F88E15947 for ; Wed, 28 Apr 1999 13:26:47 -0700 (PDT) (envelope-from steve@khoral.com) Received: from zen.alb.khoral.com by charon.khoral.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 28 Apr 1999 20:26:47 UT Received: from khoral.com Wed, 28 Apr 1999 14:26:46 -0600 (MDT) Date: Wed, 28 Apr 1999 14:26:46 -0600 (MDT) From: Steve Jorgensen Message-Id: <199904282026.OAA13313@zen.alb.khoral.com> To: John Polstra , current@freebsd.org Subject: Re: XFree86 and egcs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <199904271932.NAA01643@zen.alb.khoral.com>, > Steve Jorgensen wrote: > > I cvsup'ed and installed yesterday morning it's the third > > cvsup I've done since egcs went in, so I know it's working > > ok. Anyway, I decided to update my XFree86 installation, > > and found that the port no longer works. As it compiles > > all binaries created report tons of missing symbols > > from the various X library. The wierd thing is that it > > still installs most of the X binaries anyway, and they work > > fine, but it dies when it gets to installing the X server > > itself. > Thanks for the report, but saying that it gets "tons of missing > symbols" and that it "dies" when installing the server really isn't > helpful to those who might be able to fix the problem. Which symbols? > Let's see the error messages. How does it "die"? Let's see the error > messages. Nobody can help without that. Ok, well in the interest of not sending large compile output to the news group, I've put an error log on my webserver with all the info in it: http://www.haunt.com/~steve/error.html As you will be able to see from the log, the only non-standard response to the build was I said YES to creating the a.out compat libraries. After the initial config section, I deleted the lines of the make output until the first error occurrs. Then all lines are included until the make finally fails. Let me know how if you need any other information. I'm more than willing to try different config for compile, and patches to my OS to help debug it. Steve PS: I'm on a slow (modem) link to the net, so be gentle to my webserver.. :) ----------------------------------------------------------- Steven Jorgensen steve@khoral.com steve@haunt.com ------------------------------+---------------------------- Khoral Research Inc. | PHONE: (505) 837-6500 6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842 Albuquerque, NM 87110 | URL: http://www.khoral.com/ ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 13:45:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from neunacht.netgsi.com (neunacht.netgsi.com [192.55.203.174]) by hub.freebsd.org (Postfix) with ESMTP id D7AB8151A8 for ; Wed, 28 Apr 1999 13:45:38 -0700 (PDT) (envelope-from cjohnson@neunacht.netgsi.com) Received: (from cjohnson@localhost) by neunacht.netgsi.com (8.9.2/8.9.2) id QAA38050; Wed, 28 Apr 1999 16:45:17 -0400 (EDT) (envelope-from cjohnson) From: "Christopher T. Johnson" Message-Id: <199904282045.QAA38050@neunacht.netgsi.com> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904281938.VAA01921@yedi.iaf.nl> from Wilko Bulte at "Apr 28, 99 09:38:45 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 28 Apr 1999 16:45:17 -0400 (EDT) Cc: dillon@apollo.backplane.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As Christopher T. Johnson wrote ... > > > REGARDLESS! > > The drive is reporting an error condition and that error is NOT > > getting back to user land. I've verified the problem with amdump > > Oh? Where/what is the error, does the console tell you? Sorry, no error reported, just the lights. Amber light, no green solid. Either the kernel has the device "active" OR it is an error indicator. Exabyte is known for doing that. > > > amflush and dd. In ALL cases once the amber light goes on solid > > systat -vmstat shows a solid 1.4MB/second data transfer into > > never never land. > > That sounds like a bug. But it could be CAM not understanding that the > 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte > lockup.. Yep, been there done that. But these drives have been rock solid. It is not the case of putting in a new, unknown drive and finding out that it is a little strange. It is the case where I have a hardware configuration that has been stable that suddenly isn't. The original change is the upgrade to 4.0-CURRENT. After that drive "failed" I took our back up drive and put it into production and got exactly the same failure mode. Here is the sequence that I just did: Old working tape. mt erase & 1hr 30minutes or so later Drive makes sounds of tape stopping. Amber light comes on mt erase reports done (no errors) mt rewind mt: /dev/nrsa0: Device busy push button on face plate amber light goes out, tape noises. Green light comes on. mt rewind tape is ejected at the same place as all the other failures. push tape back into drive Drive is ejected. manually rewind tape (Yeah Yeah, I know don't do it but the exabyte ejects the tape each time it is reinserted until I have it mostly rewound) repeat with new tapes old tapes and almost new tapes.... Same thing Chris > > Groeten / Cheers, > > | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 13:56:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 672C4151A8 for ; Wed, 28 Apr 1999 13:56:36 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA26498; Wed, 28 Apr 1999 13:55:12 -0700 Date: Wed, 28 Apr 1999 13:55:11 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Christopher T. Johnson" Cc: Wilko Bulte , dillon@apollo.backplane.com, shocking@prth.pgs.com, current@FreeBSD.ORG Subject: Re: Further on tape & CAM problems In-Reply-To: <199904282045.QAA38050@neunacht.netgsi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > That sounds like a bug. But it could be CAM not understanding that the > > 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte > > lockup.. > > Yep, been there done that. But these drives have been rock solid. It is > not the case of putting in a new, unknown drive and finding out that > it is a little strange. It is the case where I have a hardware configuration > that has been stable that suddenly isn't. > > The original change is the upgrade to 4.0-CURRENT. After that drive > "failed" I took our back up drive and put it into production and got exactly > the same failure mode. > > Here is the sequence that I just did: > Old working tape. > mt erase & > 1hr 30minutes or so later > Drive makes sounds of tape stopping. > Amber light comes on > mt erase reports done (no errors) > mt rewind > mt: /dev/nrsa0: Device busy > push button on face plate > amber light goes out, tape noises. > Green light comes on. > mt rewind > tape is ejected at the same place as all the other failures. > push tape back into drive > Drive is ejected. > manually rewind tape (Yeah Yeah, I know don't do it but the exabyte > ejects the tape each time it is reinserted until I have > it mostly rewound) > repeat with new tapes old tapes and almost new tapes.... Same thing > Chris I'm sorry- I missed the front end of this. I've had pretty good luck with getting the 8200 to work. What f/w level are you at for the 8200? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 14: 4:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 73FD414F7B for ; Wed, 28 Apr 1999 14:04:15 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id RAA11123; Wed, 28 Apr 1999 17:03:58 -0400 (EDT) (envelope-from wollman) Date: Wed, 28 Apr 1999 17:03:58 -0400 (EDT) From: Garrett Wollman Message-Id: <199904282103.RAA11123@khavrinen.lcs.mit.edu> To: Chuck Robey Cc: Matthew Dillon , Jim Shankland , current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: References: <199904281828.LAA07993@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I can't quite figure why they stuck the word "open" in there, because it > couldn't possibly be more open than RIP. Because a previous link-state (aka shortest-path-first) routing protocol had been deployed which was not. > But RIP is older, and was the first routing scheme. Um, no. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 14:36:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (as1-p8.tfs.net [139.146.210.8]) by hub.freebsd.org (Postfix) with ESMTP id 426DB15505 for ; Wed, 28 Apr 1999 14:36:17 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id QAA37205; Wed, 28 Apr 1999 16:34:58 -0500 (CDT) From: Jim Bryant Message-Id: <199904282134.QAA37205@argus.tfs.net> Subject: Re: new clock good for unix (FreeBSD) In-Reply-To: from Lauri Laupmaa at "Apr 28, 99 09:35:36 pm" To: mauri@krabi.mbp.ee (Lauri Laupmaa) Date: Wed, 28 Apr 1999 16:34:56 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > Hi > > Just wondering if the new swatch clock has its way into the date command... I'd rather that it wouldn't. Swatch is pulling a marketing stunt, plain and simple. Something to toss in the closet with the pet rock a year from now. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 14:49: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 0BDDD15520; Wed, 28 Apr 1999 14:48:58 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA09354; Wed, 28 Apr 1999 14:48:56 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 14:48:56 -0700 (PDT) From: Matthew Dillon Message-Id: <199904282148.OAA09354@apollo.backplane.com> To: Alan Cox Cc: Chuck Robey , Poul-Henning Kamp , Luoqi Chen , current@freebsd.org, smp@freebsd.org Subject: Re: HEADS UP! to commit SMP vmspace sharing patches References: <199904281819.LAA07937@apollo.backplane.com> <19990428151454.O1121@nonpc.cs.rice.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Wed, Apr 28, 1999 at 11:19:17AM -0700, Matthew Dillon wrote: :> I know this is a little late ... but I don't suppose there might be a :> way to lock a TLB entry in place? That would solve the problem too. :> Baring that, %fs is the way to go. :> : :Unfortunately, on the x86, the answer is "No." The only serious :alternative was to put the commonly used per processor variables :and a pointer to the less commonly used ones at the base of each :process's/thread's kernel stack, i.e., the upages, where you could :mask off bits from the stack pointer to arrive at the correct address. :You'd then have to "refresh" most of these variables on a context switch :(in case the process migrated). : : Alan Too bad. There might be less confusion with %fs if we simply use it as a 'cpu number' index and then make all the cpu-dependant variables standard arrays. i.e. instead if 'struct proc *curproc' we would have 'struct proc *curproc[NCPU];'. The assembly macro would simply retrieive the current cpu number from %fs, so: curproc[MYCPU] = ... This would be much less confusing then trying to encapsulate the concept of 'curproc', and we could do away with cpu-specific VM areas entirely. Sure, it would eat a few more cycles, but I don't think it would effect performance. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 14:52:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id CE09E14C86 for ; Wed, 28 Apr 1999 14:52:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA01594; Wed, 28 Apr 1999 14:52:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904282152.OAA01594@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: erik@habatech.no Cc: freebsd-current@FreeBSD.org Subject: Re: Problems with ahc (2940U2W) and USB In-reply-to: Your message of "Wed, 28 Apr 1999 17:38:45 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Apr 1999 14:52:00 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With the current sources, there seems to be a problem with the Adaptec > 2940U2W driver when using USB. This isn't likely to be related to the 2940 per se. Check your BIOS settings related to USB; make sure you have it properly turned on and have an interrupt allocated to the USB port. Try turning it off, etc. Can we have some more verbose boot messages? Specifically, interrupt details for the USB port as well as the 2940. > Whenever I try to boot a kernel with the USB driver, the boot process > gets to the "Waiting 15 seconds for SCSI devices to settle" and stops. > If I compile a kernel with an nearly identical config, only the USB > driver has been commented out, it boots all right. > > My computer has a Spacewalker 661 mainboard, which is a 440BX based card. > The SCSI controller is an Adaptec 2940U2W. > > Kernels compiled before the integration of new-bus works fine. > > Now, this is not a critical situation for me, as I have no USB devices, > but I thought someone else would want this information. > > Anyone else experiencing this? > > -- > --------------------------------+---------------------------------------+ > Erik H. Bakke, Habatech AS | To be or not to be... | > E-Mail: erik@habatech.no | Is simply a question of binary logic. | > This message was sent by XFMail | | > --------------------------------+---------------------------------------+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 14:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B67B114C86 for ; Wed, 28 Apr 1999 14:54:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA26755; Wed, 28 Apr 1999 14:54:07 -0700 Date: Wed, 28 Apr 1999 14:54:07 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Christopher T. Johnson" Cc: freebsd-current@freebsd.org Subject: Re: Further on tape & CAM problems In-Reply-To: <199904282144.RAA38142@neunacht.netgsi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > I'm sorry- I missed the front end of this. I've had pretty good luck with > > getting the 8200 to work. What f/w level are you at for the 8200? > > > > -matt > > Matt, it isn't a tape drive problem. Nor is it directly and exabyte problem. > It is a problem where an error from the tape drive is not being handled > well at the kernel interface. It is as if the kernel is sending a block > to the drive, the drive is giving or holding and error state, the kernel > sees the drive drop the block but instead of reporting an error back to > user land, it reports "ok". User land then proceeds to dump tons of > bytes down the pipe with out really writing it to tape. > Yes, but I'd like to know what error condition is inducing the driver and/or CAM issues. Has anyone tried a CAMDEBUG kernel and camcontrol tracing on? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 14:56:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9243415520 for ; Wed, 28 Apr 1999 14:56:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA09487; Wed, 28 Apr 1999 14:56:28 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 14:56:28 -0700 (PDT) From: Matthew Dillon Message-Id: <199904282156.OAA09487@apollo.backplane.com> To: Jim Shankland Cc: current@freebsd.org Subject: Re: Our routed - Vern says it's old and buggy. References: <199904282018.NAA02091@biggusdiskus.flyingfox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Umm ... OK, I thought you were saying that OSPF and BGP are "open", :whereas RIP v1 and v2 are not. In that context, I wasn't sure what :you meant by "open". If "open" means freely downloadable spec, then :presumably all of the above are open. So never mind :-). : :Jim Shankland :NLynx Systems, Inc. Huh? Where'd you get that idea? RIP is open. It just isn't particularly well suited to today's networks. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 15: 3:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from psycho.h4x0rz.za.org (psycho.h4x0rz.za.org [206.49.228.8]) by hub.freebsd.org (Postfix) with ESMTP id 1E03015793 for ; Wed, 28 Apr 1999 15:03:26 -0700 (PDT) (envelope-from andrew@psycho.h4x0rz.za.org) Received: from localhost (andrew@localhost) by psycho.h4x0rz.za.org (8.9.3/8.9.2) with ESMTP id XAA06051 for ; Wed, 28 Apr 1999 23:17:31 +0200 (SAST) (envelope-from andrew@psycho.h4x0rz.za.org) Date: Wed, 28 Apr 1999 23:17:30 +0200 (SAST) From: vortexia To: current@freebsd.org Subject: PCM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsupped from 3.1-RELEASE today to 4.0-CURRENT and since then PCM sound has been screwed. Im using a crystal sound card, anyone having similar problems? Cheers Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 15: 4:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AF58A154A6; Wed, 28 Apr 1999 15:04:16 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA09667; Wed, 28 Apr 1999 15:04:04 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 15:04:04 -0700 (PDT) From: Matthew Dillon Message-Id: <199904282204.PAA09667@apollo.backplane.com> To: Bill Paul Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: NFS Patch #8 for current available - new TCP fixes References: <199904281327.JAA29467@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :For parts that don't support arbitrary alignment, you have to copy. :Now, in some of the drivers that I ported to the alpha, I only copied :the first small section of the packet in order to get the IP header :aligned (since failing to do this causes an unaligned access trap in :the IP code). This is faster than copying the entire packet to fix :the alignment, but I'm not sure what effect it has on NFS. : :-Bill : :-- :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu What will happen is that NFS will realign the unaligned mbufs, which requires a copy. NFS previously copied in-place, but my patch rewrites that code to copy to a new buffer ( because copying in-place breaks NFS/TCP ). We could avoid realigning the mbufs by changing the various NFS 32 bit read/write macros to operate in 16 bit chunks. This might be the best solution ultimately. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 15:25:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from gina.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 2949314BC9 for ; Wed, 28 Apr 1999 15:25:13 -0700 (PDT) (envelope-from root@neland.dk) Received: from gina (gina [192.168.0.14]) by gina.neland.dk (8.9.3/8.9.3) with ESMTP id AAA00356 for ; Thu, 29 Apr 1999 00:25:22 +0200 (CEST) (envelope-from root@neland.dk) Date: Thu, 29 Apr 1999 00:25:22 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: Still no sound Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get "no pcm devices configured"; this happened after cvsupping a week or so. (I cvsup every night). The soundcard gets probed as a AudioPCI ESS1370 dmesg: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #2: Tue Apr 27 02:02:50 CEST 1999 root@gina.neland.dk:/usr/src/sys/compile/GINA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff real memory = 67043328 (65472K bytes) avail memory = 62328832 (60868K bytes) Preloaded elf kernel "kernel" at 0xc02c4000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: TCM5098 [0x98506d50] Serial 0x0809c8d9 Comp ID: PNP80f7 [0xf780d041] npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 4.0 on pci0 ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 chip2: at device 4.3 on pci0 >es0: at device 10.0 on pci0 >pcm0: using I/O space register mapping at 0xd000 >es0: interrupting at irq 10 eisa0: on motherboard isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 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/9 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ppc0: interrupting at irq 7 1 3C5x9 board(s) on ISA found at 0x300 ep0 at port 0x300-0x30f irq 11 on isa0 ep0: utp/bnc[*UTP*] address 00:60:08:09:c8:d9 ep0: interrupting at irq 11 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver ep0 XXX: driver didn't set ifq_maxlen ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 6197MB (12692295 sectors), 13431 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates no pcm units configured\^Hno pcm units configured\^Hno pcm units configured\^H Config: machine i386 cpu I686_CPU ident "GINA" maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0s3a options DDB controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x31 # Advanced Power Management device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device ep0 at isa? port 0x300 irq 11 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's options KTRACE #kernel tracing options SYSVSHM options SYSVMSG options SYSVSEM pseudo-device bpfilter 4 #Berkeley packet filter device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 device pca0 at isa? port IO_TIMER1 controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives options SOFTUPDATES To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 15:27:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from gina.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id CFF1D14BC9 for ; Wed, 28 Apr 1999 15:27:38 -0700 (PDT) (envelope-from root@neland.dk) Received: from gina (gina [192.168.0.14]) by gina.neland.dk (8.9.3/8.9.3) with ESMTP id AAA00363 for ; Thu, 29 Apr 1999 00:27:45 +0200 (CEST) (envelope-from root@neland.dk) Date: Thu, 29 Apr 1999 00:27:45 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: ep0 *UTP* Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Btw, why does boot write [*UTP*] ? The card is working nicely with bnc. ep0 at port 0x300-0x30f irq 11 on isa0 ep0: utp/bnc[*UTP*] address 00:60:08:09:c8:d9 ep0: interrupting at irq 11 device ep0 at isa? port 0x300 irq 11 Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 15:31:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5B89A14BC9 for ; Wed, 28 Apr 1999 15:31:47 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id SAA20276; Wed, 28 Apr 1999 18:28:47 -0400 (EDT) Date: Wed, 28 Apr 1999 18:28:47 -0400 (EDT) From: Chuck Robey To: Garrett Wollman Cc: Matthew Dillon , Jim Shankland , current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <199904282103.RAA11123@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Garrett Wollman wrote: > < said: > > > > I can't quite figure why they stuck the word "open" in there, because it > > couldn't possibly be more open than RIP. > > Because a previous link-state (aka shortest-path-first) routing > protocol had been deployed which was not. > > > But RIP is older, and was the first routing scheme. > > Um, no. I don't know which was invented first, but I have a stack of books here that all aver that RIP was used on arpanet long before OSPF. The date on the rfc seems to back me up. Which one should I quote? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 15:35:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8AF5414BC9 for ; Wed, 28 Apr 1999 15:35:39 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA23923; Thu, 29 Apr 1999 00:31:29 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id AAA01580; Thu, 29 Apr 1999 00:16:41 +0200 (CEST) From: Wilko Bulte Message-Id: <199904282216.AAA01580@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904282045.QAA38050@neunacht.netgsi.com> from "Christopher T. Johnson" at "Apr 28, 1999 4:45:17 pm" To: cjohnson@neunacht.netgsi.com (Christopher T. Johnson) Date: Thu, 29 Apr 1999 00:16:41 +0200 (CEST) Cc: dillon@apollo.backplane.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Christopher T. Johnson wrote ... > > As Christopher T. Johnson wrote ... > > > > > REGARDLESS! > > > The drive is reporting an error condition and that error is NOT > > > getting back to user land. I've verified the problem with amdump > > > > Oh? Where/what is the error, does the console tell you? > > Sorry, no error reported, just the lights. Amber light, no green solid. > Either the kernel has the device "active" OR it is an error indicator. > Exabyte is known for doing that. In my experience it was always the drive, but YMMV. > > > amflush and dd. In ALL cases once the amber light goes on solid > > > systat -vmstat shows a solid 1.4MB/second data transfer into > > > never never land. > > > > That sounds like a bug. But it could be CAM not understanding that the > > 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte > > lockup.. > > Yep, been there done that. But these drives have been rock solid. It is > not the case of putting in a new, unknown drive and finding out that > it is a little strange. It is the case where I have a hardware configuration > that has been stable that suddenly isn't. CAM might trigger different code paths in the firmware. Or different timing. Or.. > The original change is the upgrade to 4.0-CURRENT. After that drive > "failed" I took our back up drive and put it into production and got exactly > the same failure mode. > > Here is the sequence that I just did: > Old working tape. > mt erase & > 1hr 30minutes or so later > Drive makes sounds of tape stopping. I also tried that in the meantime (it said *click* just a minute ago ;-) and I did not experience any problem with the erase operation. > Amber light comes on Nope, after the tape motion stops I have the green one on again. > mt erase reports done (no errors) > mt rewind > mt: /dev/nrsa0: Device busy p100#mt -f /dev/rst0 rewind p100# My P100 testbox uses a NCR810 to drive the 8200. Any chance you can try an 8200 with different f/w ? I'll also try a 'dump' again with more data, my previous test was 300Mb. Maybe that is not enough (I doubt it, but still..) Will post results when it's finished writing. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 15:39:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0995F14CD3 for ; Wed, 28 Apr 1999 15:39:09 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id PAA77062; Wed, 28 Apr 1999 15:39:08 -0700 (PDT) (envelope-from obrien) Message-ID: <19990428153908.A76974@nuxi.com> Date: Wed, 28 Apr 1999 15:39:08 -0700 From: "David O'Brien" To: Keith Walker , freebsd-current@FreeBSD.ORG Subject: Re: Progs linked against libstdc++ dead... Reply-To: obrien@NUXI.com References: <37272C41.6F889B3E@timesink.spk.wa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <37272C41.6F889B3E@timesink.spk.wa.us>; from Keith Walker on Wed, Apr 28, 1999 at 08:41:53AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Aagh! As of last-night's current (Tuesday), *NO* C++ program that > links against libstdc++ works now. All of them come up with this > error, and recompilation doesn't help :-( You have done a *FULL* CVSup and `make world'? You have then recopiled any C++ libs from ports or private sources? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 15:58:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from axle.cs.ucla.edu (Axle.CS.UCLA.EDU [131.179.192.135]) by hub.freebsd.org (Postfix) with ESMTP id 7CF3714EC4 for ; Wed, 28 Apr 1999 15:58:37 -0700 (PDT) (envelope-from scottm@axle.cs.ucla.edu) Received: from axle.cs.ucla.edu (localhost [127.0.0.1]) by axle.cs.ucla.edu (8.9.3/8.9.3) with ESMTP id PAA22086; Wed, 28 Apr 1999 15:58:27 -0700 (PDT) (envelope-from scottm@axle.cs.ucla.edu) Message-Id: <199904282258.PAA22086@axle.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no Cc: current@freebsd.org Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: Your message of "Wed, 28 Apr 1999 21:12:29 +0200." <67008.925326749@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Apr 1999 15:58:27 -0700 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Open" (according to Lenny Kleinrock) meant "available"; thus OSPF was supposed to mean "Available, shortest path first." But, then again, these meanings get changed with time. "Open" is now a codeword for GNU/GPL/intellectual rights unencumbtered software. For OSPF, it was simply a description of an algorithm. The reason for OSPF and link state protocols in the first place was to correct problems that evovled from distance vector protocols, such as "counting to infinity" and to speed convergence when topologies change. Distance vector protocols are easy to implement and easy to understand and easy to configure (i.e. just turn it on.) While link-state doesn't have to be difficult and should be easy to turn on and route, the history of gated has caused a certain mental inertia and prejudice to using them. Heck, even my ex-advisor grimaces with fear when you mention "link-state" in her presence. -scooter > > I can't quite figure why they stuck the word "open" in there, because it > > couldn't possibly be more open than RIP. > > Probably because it was (at the time) in heavy "competition" with the OSI > IS-IS routing protocol. Those standards were *not* openly available. (I > believe they are now.) > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 16: 0:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 74C4D14EC4; Wed, 28 Apr 1999 16:00:22 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id SAA29228; Wed, 28 Apr 1999 18:00:21 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id SAA15816; Wed, 28 Apr 1999 18:00:21 -0500 (CDT) Date: Wed, 28 Apr 1999 18:00:20 -0500 From: Alan Cox To: Matthew Dillon Cc: Chuck Robey , Poul-Henning Kamp , Luoqi Chen , current@freebsd.org, smp@freebsd.org Subject: Re: HEADS UP! to commit SMP vmspace sharing patches Message-ID: <19990428180020.P1121@nonpc.cs.rice.edu> References: <199904281819.LAA07937@apollo.backplane.com> <19990428151454.O1121@nonpc.cs.rice.edu> <199904282148.OAA09354@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199904282148.OAA09354@apollo.backplane.com>; from Matthew Dillon on Wed, Apr 28, 1999 at 02:48:56PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 02:48:56PM -0700, Matthew Dillon wrote: > > ... > > There might be less confusion with %fs if we simply use it as a > 'cpu number' index and then make all the cpu-dependant variables > standard arrays. i.e. instead if 'struct proc *curproc' we would > have 'struct proc *curproc[NCPU];'. The assembly macro would > simply retrieive the current cpu number from %fs, so: > > curproc[MYCPU] = ... > > This would be much less confusing then trying to encapsulate the concept > of 'curproc', and we could do away with cpu-specific VM areas entirely. > > Sure, it would eat a few more cycles, but I don't think it would effect > performance. > I don't think the current approach with %fs is that confusing. :-) You can view it as an optimization of struct "per processor data" { struct proc *curproc; ... } ppd[NCPUS]; some_func() { ... ppd[MYCPU]->curproc In some sense, the "ppd[MYCPU]" is precomputed in %fs. Also, I would discourage a "per-variable" approach like struct proc *curproc[NCPU]; This will lead to unnecessary cache coherence traffic (due to false sharing). For example, when processor 0 updates curproc[0] it will cause the invalidation of the cache line containing curproc on processor 1, and vice versa when processor 1 updates curproc[1]. Instead, it's better to aggregate each processor's per-processor data like our current code does. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 16: 4: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 76AE114D98 for ; Wed, 28 Apr 1999 16:03:54 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id LAA06434; Thu, 29 Apr 1999 11:03:52 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id LAA82012; Thu, 29 Apr 1999 11:03:44 +1200 (NZST) (envelope-from jabley) Date: Thu, 29 Apr 1999 11:03:44 +1200 From: Joe Abley To: Chuck Robey Cc: Matthew Dillon , Jim Shankland , current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: Our routed - Vern says it's old and buggy. Message-ID: <19990429110344.A81921@clear.co.nz> References: <199904281828.LAA07993@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Chuck Robey on Wed, Apr 28, 1999 at 02:34:51PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 02:34:51PM -0400, Chuck Robey wrote: > And you didn't know that the RIP spec is even older, and was publicly > available via an RFC (the same as OSPF?) But, of course, RIP sucks in many well-known ways. > I can't quite figure why they stuck the word "open" in there, because it > couldn't possibly be more open than RIP. I thought the "open" referred to the algorithm -- i.e. "shortest open path first" would be a synonym. I have no reason to think this, though. I could well be wrong, and probably am. > > OSPF has been around for a long time. > > But RIP is older, and was the first routing scheme. X.25 is older than IP, which clearly makes it better in all circumstances. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 16:45: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 48B1E14CEE; Wed, 28 Apr 1999 16:44:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA10391; Wed, 28 Apr 1999 16:44:52 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 16:44:52 -0700 (PDT) From: Matthew Dillon Message-Id: <199904282344.QAA10391@apollo.backplane.com> To: Alan Cox Cc: Chuck Robey , Poul-Henning Kamp , Luoqi Chen , current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: HEADS UP! to commit SMP vmspace sharing patches References: <199904281819.LAA07937@apollo.backplane.com> <19990428151454.O1121@nonpc.cs.rice.edu> <199904282148.OAA09354@apollo.backplane.com> <19990428180020.P1121@nonpc.cs.rice.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I don't think the current approach with %fs is that confusing. :-) You :can view it as an optimization of : : struct "per processor data" { : struct proc *curproc; : ... : } ppd[NCPUS]; : : some_func() : { : ... ppd[MYCPU]->curproc : :In some sense, the "ppd[MYCPU]" is precomputed in %fs. : :Also, I would discourage a "per-variable" approach like : : struct proc *curproc[NCPU]; : :This will lead to unnecessary cache coherence traffic (due to false :sharing). For example, when processor 0 updates curproc[0] it will :cause the invalidation of the cache line containing curproc on processor 1, :and vice versa when processor 1 updates curproc[1]. Instead, it's better :to aggregate each processor's per-processor data like our current :code does. : :Alan Quite true. But, in that case, the equivalent of struct perprocess { struct process *curproc; ... } perproc[NCPU]; While it is true that you then have to draw out the access: perproc[MYCPU].curproc Or perhaps ( even better ): MYCPU->curproc It would make the code much more readable then trying to 'hide' the fact that curproc ( and other variables ) are actually segmented. We have to keep in mind the fact that SMP is only just now gaining momentum, and I think a considerable amount of additional data and structure is going to be added to the per-cpu structures in the next few years as we begin to parallelize kernel operations. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 17:52: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id E6AEB14CC5 for ; Wed, 28 Apr 1999 17:51:57 -0700 (PDT) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id RAA31141; Wed, 28 Apr 1999 17:51:53 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.2.0.32.19990428172830.00a49360@216.101.162.50> X-Sender: null@216.101.162.50 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.32 (Beta) Date: Wed, 28 Apr 1999 17:51:52 -0700 To: obrien@NUXI.com, Keith Walker , freebsd-current@FreeBSD.ORG From: Manfred Antar Subject: Re: Progs linked against libstdc++ dead... In-Reply-To: <19990428153908.A76974@nuxi.com> References: <37272C41.6F889B3E@timesink.spk.wa.us> <37272C41.6F889B3E@timesink.spk.wa.us> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:39 PM 4/28/99 -0700, David O'Brien wrote: >> Aagh! As of last-night's current (Tuesday), *NO* C++ program that >> links against libstdc++ works now. All of them come up with this >> error, and recompilation doesn't help :-( > >You have done a *FULL* CVSup and `make world'? You have then recopiled >any C++ libs from ports or private sources? This same thing happened here libstdc++ from Monday was fine There were some header files changed in the contrib/egcs directory I don't remember which something-freebsd.h and I think this might have caused it. Even when trying to compile a new program Example: (xtide-2.1.2)503}make rm -f xtide g++ -o xtide -O2 -L/usr/X11R6/lib xtide.o xxerrors.o xxContext.o xxTitleScre en.o xxGlobe.o xxLocationList.o xxXTideRoot.o xxTideContext.o xxDisclaimer.o x xTextMode.o xxDrawable.o xxErrorBox.o xxHelpBox.o xxFilename.o xxMarkLevel.o xx ApplicationDefaults.o xxGraphMode.o xxPixmapGraph.o xxAspect.o xxClock.o xxWind ow.o xxTimestamp.o xxMultiChoice.o xxHorizDialog.o xxUnsignedChooser.o Dstr.o H armonicsPath.o PredictionValue.o Amplitude.o Angle.o Speed.o Timestamp.o Interv al.o Year.o Constituent.o TabulatedConstituent.o Coordinates.o HarmonicsFile.o StationRef.o StationIndex.o ConstantSet.o TideContext.o Offsets.o ConstituentS et.o ConstantSetWrapper.o Station.o xml_l.o xml_y.o xmlstruct.o ReferenceStatio n.o SubordinateStation.o skycal.o Colors.o Graph.o RGBGraph.o UserDefaults.o C onfigDefaults.o Settings.o CommandLineSettings.o TTYGraph.o Calendar.o Banner.o NullableAngle.o -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11 -lXpm -lxpg4 -lpng -lz -lm -Wl,-rpath,/usr/X11R6/lib -L/usr/local/lib /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' *** Error code 1 I just did a cvsup and noticed that there was another change to the contrib/egcs tree I'm starting a make world now. Meanwhile I have a backup of the libstdc++ files. Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 18: 3:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id DB96E14EB2 for ; Wed, 28 Apr 1999 18:03:48 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (jbloom.ne.mediaone.net [24.128.100.196]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA01246; Wed, 28 Apr 1999 21:03:37 -0400 (EDT) Message-ID: <3727AFE8.168D7178@acm.org> Date: Wed, 28 Apr 1999 21:03:36 -0400 From: Jim Bloom X-Mailer: Mozilla 4.51 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rick Whitesel Cc: erik@habatech.no, freebsd-current@FreeBSD.ORG Subject: Re: Problems with ahc (2940U2W) and USB References: <002f01be9190$2e22bfe0$d3e4b38c@xyplex.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Add me to the list of people seeing this problem. I have an ASUS P2B-S with onboard Adaptec 7890. I have been seeing the problem on and off since December of last year. One time it boots and the next time it doesn't. Once the disk is hung, the reset switch or power cycling are the only ways to unfreeze it. I have seen this problem mentioned on both freebsd-current and freebsd-scsi several times without a solution. I don't recall a link to USB being mentioned before. I'll try to post my dmesg output later this tonight. Jim Bloom bloom@acm.org Rick Whitesel wrote: > > Hi: > I am seeing the same thing on a ASUS P2B with a Adaptec 2940?? > controller. > > Rick > > ----- Original Message ----- > From: > To: > Sent: Wednesday, April 28, 1999 11:38 AM > Subject: Problems with ahc (2940U2W) and USB > > With the current sources, there seems to be a problem with the Adaptec > 2940U2W driver when using USB. > > Whenever I try to boot a kernel with the USB driver, the boot process > gets to the "Waiting 15 seconds for SCSI devices to settle" and stops. > If I compile a kernel with an nearly identical config, only the USB > driver has been commented out, it boots all right. > > My computer has a Spacewalker 661 mainboard, which is a 440BX based card. > The SCSI controller is an Adaptec 2940U2W. > > Kernels compiled before the integration of new-bus works fine. > > Now, this is not a critical situation for me, as I have no USB devices, > but I thought someone else would want this information. > > Anyone else experiencing this? > > -- > --------------------------------+---------------------------------------+ > Erik H. Bakke, Habatech AS | To be or not to be... | > E-Mail: erik@habatech.no | Is simply a question of binary logic. | > This message was sent by XFMail | | > --------------------------------+---------------------------------------+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 18:18:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from qix.jmz.org (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id 868A214D94 for ; Wed, 28 Apr 1999 18:18:27 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.2) id DAA77398; Thu, 29 Apr 1999 03:19:37 +0200 (MET DST) (envelope-from jmz@FreeBSD.ORG) Date: Thu, 29 Apr 1999 03:19:37 +0200 (MET DST) Message-Id: <199904290119.DAA77398@qix.jmz.org> X-Authentication-Warning: qix.jmz.org: jmz set sender to jmz@FreeBSD.ORG using -f From: Jean-Marc Zucconi To: current@FreeBSD.ORG Subject: make world failure X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just encountered this: ===> gnu/usr.bin/cc/doc makeinfo -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/cp --no-split -I /u3/src/gnu/usr.bin/cc/doc -I /u3/src/gnu/usr.bin/cc/doc /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/gcc.texi -o gcc.info /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:434: Next reference to nonexistent node `Invoking G++'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/gcc.texi:2085: Cross reference to nonexistent node `Warning Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/gcc.texi:1619: Cross reference to nonexistent node `Optimize Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/extend.texi:2236: Cross reference to nonexistent node `C++ Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:431: Menu reference to nonexistent node `Target Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:429: Menu reference to nonexistent node `Directory Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:428: Menu reference to nonexistent node `Link Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:427: Menu reference to nonexistent node `Assembler Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:425: Menu reference to nonexistent node `Preprocessor Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:424: Menu reference to nonexistent node `Optimize Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:423: Menu reference to nonexistent node `Debugging Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:422: Menu reference to nonexistent node `Warning Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:421: Menu reference to nonexistent node `C++ Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:420: Menu reference to nonexistent node `C Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:401: Cross reference to nonexistent node `Code Gen Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:208: Cross reference to nonexistent node `Submodel Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:202: Cross reference to nonexistent node `Target Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:195: Cross reference to nonexistent node `Directory Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:185: Cross reference to nonexistent node `Link Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:179: Cross reference to nonexistent node `Assembler Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:166: Cross reference to nonexistent node `Preprocessor Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:147: Cross reference to nonexistent node `Optimize Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:136: Cross reference to nonexistent node `Debugging Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:115: Cross reference to nonexistent node `Warning Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:103: Cross reference to nonexistent node `C++ Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:94: Cross reference to nonexistent node `C Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:77: Menu reference to nonexistent node `Running Protoize'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:76: Menu reference to nonexistent node `Environment Variables'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:74: Menu reference to nonexistent node `Code Gen Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:72: Menu reference to nonexistent node `Submodel Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:71: Menu reference to nonexistent node `Target Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:69: Menu reference to nonexistent node `Directory Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:68: Menu reference to nonexistent node `Link Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:67: Menu reference to nonexistent node `Assembler Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:65: Menu reference to nonexistent node `Preprocessor Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:64: Menu reference to nonexistent node `Optimize Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:63: Menu reference to nonexistent node `Debugging Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:62: Menu reference to nonexistent node `Warning Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:61: Menu reference to nonexistent node `C++ Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:60: Menu reference to nonexistent node `C Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:59: Menu reference to nonexistent node `Invoking G++'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:30: Cross reference to nonexistent node `Invoking G++'. makeinfo: Removing output file `gcc.info' due to errors; use --force to preserve. Making info file `gcc.info' from `/u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/gcc.texi'. *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 18:35:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from valhalla.daily.umn.edu (valhalla.daily.umn.edu [128.101.178.6]) by hub.freebsd.org (Postfix) with ESMTP id 9706115794 for ; Wed, 28 Apr 1999 18:35:30 -0700 (PDT) (envelope-from yhuerta@valhalla.daily.umn.edu) Received: from localhost (yhuerta@localhost) by valhalla.daily.umn.edu (8.8.7/8.8.7) with SMTP id UAA17603 for ; Wed, 28 Apr 1999 20:35:29 -0500 (CDT) (envelope-from yhuerta@valhalla.daily.umn.edu) Date: Wed, 28 Apr 1999 20:35:29 -0500 (CDT) From: Yectli Huerta To: freebsd-current@FreeBSD.ORG Subject: unsubscribe In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 18:46:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 673161548B; Wed, 28 Apr 1999 18:46:42 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA77882; Wed, 28 Apr 1999 18:46:42 -0700 (PDT) (envelope-from obrien) Message-ID: <19990428184642.A77865@nuxi.com> Date: Wed, 28 Apr 1999 18:46:42 -0700 From: "David O'Brien" To: Jean-Marc Zucconi , current@FreeBSD.ORG Subject: Re: make world failure Reply-To: obrien@NUXI.com References: <199904290119.DAA77398@qix.jmz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904290119.DAA77398@qix.jmz.org>; from Jean-Marc Zucconi on Thu, Apr 29, 1999 at 03:19:37AM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 29, 1999 at 03:19:37AM +0200, Jean-Marc Zucconi wrote: > I just encountered this: > > ===> gnu/usr.bin/cc/doc > makeinfo -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/cp --no-split -I /u3/src/gnu/usr.bin/cc/doc -I /u3/src/gnu/usr.bin/cc/doc /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/gcc.texi -o gcc.info As latest egcs committer, info docs are out of my forte. Hopefully someone knowledgeable about them can help you out. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 18:54:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4740B1548B for ; Wed, 28 Apr 1999 18:54:29 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA77942; Wed, 28 Apr 1999 18:54:27 -0700 (PDT) (envelope-from obrien) Message-ID: <19990428185427.B77865@nuxi.com> Date: Wed, 28 Apr 1999 18:54:27 -0700 From: "David O'Brien" To: Keith Walker , freebsd-current@FreeBSD.ORG Subject: Re: Progs linked against libstdc++ dead... Reply-To: obrien@NUXI.com References: <37272C41.6F889B3E@timesink.spk.wa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <37272C41.6F889B3E@timesink.spk.wa.us>; from Keith Walker on Wed, Apr 28, 1999 at 08:41:53AM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined > symbol "__vt_7filebuf" I'm rather tied up until Sunday. So it will be few days unti I can really take a look at this. Until then, patches gladly accepted. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 18:59:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id C5CE014CF8 for ; Wed, 28 Apr 1999 18:59:27 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA00953; Wed, 28 Apr 1999 20:59:22 -0500 (CDT) Date: Wed, 28 Apr 1999 20:59:22 -0500 (CDT) From: Steve Price To: obrien@NUXI.com Cc: Keith Walker , freebsd-current@FreeBSD.ORG Subject: Re: Progs linked against libstdc++ dead... In-Reply-To: <19990428185427.B77865@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, David O'Brien wrote: # > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined # > symbol "__vt_7filebuf" # # I'm rather tied up until Sunday. So it will be few days unti I can # really take a look at this. Until then, patches gladly accepted. Remember you asked. :-) Index: freebsd.h =================================================================== RCS file: /home/ncvs/src/contrib/egcs/gcc/config/freebsd.h,v retrieving revision 1.9 retrieving revision 1.8 diff -u -r1.9 -r1.8 --- freebsd.h 1999/04/27 15:43:56 1.9 +++ freebsd.h 1999/04/22 17:45:01 1.8 @@ -89,10 +89,9 @@ libraries compiled with the native cc. */ #undef NO_DOLLAR_IN_LABEL -/* Wait until EGCS 1.2 to use more efficient ``thunks'' to implement - C++ vtables. */ +/* Use more efficient ``thunks'' to implement C++ vtables. */ #undef DEFAULT_VTABLE_THUNKS -#define DEFAULT_VTABLE_THUNKS 0 +#define DEFAULT_VTABLE_THUNKS 1 /* Miscellaneous parameters. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 19: 0:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id E1D5E15422 for ; Wed, 28 Apr 1999 19:00:20 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA92780; Wed, 28 Apr 1999 21:58:48 -0400 (EDT) Date: Wed, 28 Apr 1999 21:58:48 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: Thomas Seidmann , current@FreeBSD.ORG, shocking@prth.pgs.com Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: <199904281143.NAA02577@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Soren Schmidt wrote: > > Hi, > > I have three hosts with -current, all with the new ATA in function. > > Booting the same kernel produces different results on all of them wrt > > root file system mounting: > >=20 > > - one reports 'changing root device to wd0s3a' > > - one reports 'changing root device to wd0s3a' followed by 'changing > > root device to wd0a' and continues flawlessly > > - one reports 'changing root device to wd0s3a' followed by 'changing > > root device to wd0a' and panics with 'cannot mount root file system (2)= , > > err 22' > >=20 > > All motherboards are equipped with the PIIX4 IDE controller. If I need > > to supply the dmesg output and/or configuration, please let me know. Al= l > > three hosts have FreeBSD on the first disk (on different disk locations= , > > though). >=20 > Hmm, could you mail me the output of fdisk & disklabel from those tree > machines, with indication of how they behave ?? >=20 > I'm unable to reproduce those errors here, but this might bring the > details I need to figure it out... >=20 > -S=F8ren Ever going to help with my atapi-fd problems? I found examples of the corruptions, including lots of NULLs... >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman _ __ ___ ____ ___ ___ ___ =20 green@unixhelp.org _ __ ___ | _ ) __| \=20 FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 19:44:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.ne.mediaone.net (jbloom.ne.mediaone.net [24.128.100.196]) by hub.freebsd.org (Postfix) with ESMTP id 4ED1614FA3 for ; Wed, 28 Apr 1999 19:44:06 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by jbloom.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id WAA00365 for ; Wed, 28 Apr 1999 22:44:04 -0400 (EDT) (envelope-from bloom@acm.org) Message-ID: <3727C774.5167350D@acm.org> Date: Wed, 28 Apr 1999 22:44:04 -0400 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Hang during boot with ahc (2940U2W) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the dmesg output from a boot -v on my machine. I don't believe that I have ever had the USB ports configured in my kernel. They do have an IRQ allocated in the BIOS though. Jim Bloom bloom@acm.org Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #19: Sat Apr 10 14:19:12 EDT 1999 bloom@jbloom.ne.mediaone.net:/usr/src/sys/compile/JMB Calibrating clock(s) ... TSC clock: 400903902 Hz, i8254 clock: 1193167 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0032d000 - 0x07ffbfff, 130871296 bytes (31951 pages) config> pnp 1 0 os enable irq0 5 drq0 1 drq1 5 port0 0x220 port1 0x330 port2 0x388 config> pnp 1 1 os enable port0 0x200 config> pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20 config> ls Device port irq drq iomem iosize unit flags enab confl fdc0 0x3f0 6 2 0 0 0 0 Yes No wdc0 0x1f0 14 -1 0 0 0 0xa0ffa0ff Yes No wdc1 0x170 15 -1 0 0 1 0xa0ffa0ff Yes No atkbdc0 0x60 -1 -1 0 0 0 0 Yes No atkbd0 0xffffffff 1 -1 0 0 0 0 Yes No psm0 0xffffffff 12 -1 0 0 0 0 Yes No sc0 0xffffffff -1 -1 0 0 0 0 Yes No sio0 0x3f8 4 -1 0 0 0 0x10 Yes No sio1 0x2f8 3 -1 0 0 1 0 Yes No ppc0 0xffffffff 7 -1 0 0 0 0 Yes No pca0 0x40 -1 -1 0 0 0 0 Yes No vga0 0xffffffff -1 -1 0 0 0 0 Yes Yes npx0 0xf0 13 -1 0 0 0 0 Yes No apm0 0xffffffff -1 -1 0 0 0 0x31 No No sb0 0x220 5 1 0 0 0 0 Yes No sbxvi0 0xffffffff -1 5 0 0 0 0 Yes No sbmidi0 0x330 -1 -1 0 0 0 0 Yes No awe0 0x620 -1 -1 0 0 0 0 Yes No opl0 0x388 -1 -1 0 0 0 0 Yes No joy0 0x201 -1 -1 0 0 0 0 Yes No CSN LDN conf en irqs drqs others (PnP devices) 1 0 OS Y 5 0 1 5 port 0x220 0x330 0x388 1 1 OS Y 0 0 0 0 port 0x200 1 2 OS Y 0 0 0 0 port 0x620 0xa20 0xe20 config> quit avail memory = 127430656 (124444K bytes) Found BIOS32 Service Directory header at 0xc00f9ce0 Entry = 0xf0550 (0xc00f0550) Rev = 0 Len = 1 PCI BIOS entry at 0x750 DMI header at 0xc00f5880 Version 2.0 Table at 0xf589a, 33 entries, 1079 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fd110 Preloaded elf kernel "kernel" at 0xc0318000. Preloaded userconfig_script "/pnp.setup" at 0xc03180a8. Pentium Pro MTRR support enabled, default memory type is uncacheable GPL Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base e4000000, size 26 chip0: rev 0x02 on pci0.0.0 found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip1: rev 0x02 on pci0.1.0 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip2: rev 0x02 on pci0.4.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000c800, size 4 ide_pci0: rev 0x01 on pci0.4.1 intel_piix_status: primary master sample = 5, master recovery = 4 intel_piix_status: primary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: primary slave sample = 3, slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled ide_pci: busmaster 0 status: 44 from port: 0000c802 ide_pci: ide0:1 has been configured for DMA by BIOS intel_piix_status: secondary master sample = 5, master recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary slave sample = 5, slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000c80a found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[0]: type 4, range 32, base 0000c400, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip3: rev 0x02 on pci0.4.3 found-> vendor=0x9005, dev=0x001f, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000c000, size 8 map[1]: type 1, range 64, base e1000000, size 12 map[2]: type 0, range 0, base 00000000, size 0 ahc0: rev 0x00 int a irq 9 on pci0.6.0 ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom not present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 390 instructions downloaded found-> vendor=0x11d1, dev=0x01f7, revid=0x00 class=04-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 1, range 32, base e0800000, size 20 found-> vendor=0x10b7, dev=0x9055, revid=0x30 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000b800, size 7 map[1]: type 1, range 32, base e0000000, size 7 xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x30 int a irq 10 on pci0.11.0 xl0: Ethernet address: 00:10:5a:12:90:6f xl0: media options word: a xl0: probing for a PHY xl0: checking address: 0 xl0: found PHY at address 0, vendor id: 0 device id: 0 xl0: PHY type: xl0: found 10baseT xl0: found 100baseTX xl0: autoneg complete, link status good (half-duplex, 10Mbps) bpf: xl0 attached Probing for devices on PCI bus 1: found-> vendor=0x1002, dev=0x4742, revid=0x5c class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e2000000, size 24 map[1]: type 4, range 32, base 0000d800, size 8 map[2]: type 1, range 32, base e1800000, size 12 vga0: rev 0x5c int a irq 11 on pci1.0.0 Probing for PnP devices: Trying Read_Port at 203 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x0cb4360c Comp ID: PNPb02f [0x2fb0d041] PnP: override config for CSN 1 LDN 0 vend_id 0xe4008c0e port 0x0000 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 0 PnP: override config for CSN 1 LDN 1 vend_id 0xe4008c0e port 0x0000 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 0 PnP: override config for CSN 1 LDN 2 vend_id 0xe4008c0e Warning: LDN 2 does not exist port 0x0000 0x0000 0x0000 0x0000 irq 0:0 drq 0:0 en 0 Warning: LDN 2 does not exist Called nullpnp_probe with tag 0x00000001, type 0xe4008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 39 03 c8 psm: status 39 03 c8 psm: status 39 03 c8 psm: status 10 00 64 psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3, 3 buttons psm0: config:00000000, flags:00000000, packet size:4 psm0: syncmask:c8, syncbits:08 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppb0: IEEE1284 device found /NIBBLE/NIBBLE_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: HP ENHANCED PCL5,PJL lpt0: on ppbus 0 lpt0: Interrupt-driven port pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 1 (atapi): , removable, accel, dma, iordis wcd0: drive speed 2062 - 4125KB/sec, 256KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA, packet track wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: CD-ROM 120mm data disc loaded, unlocked wdc1 not found at 0x170 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: awe0 at 0x620 on isa awe0: opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick imasks: bio c0084040, tty c003109a, net c0060400 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled bpf: ppp0 attached bpf: ppp1 attached new masks: bio c0084040, tty c003109a, net c007149a bpf: lo0 attached Waiting 8 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:2. 1 SCBs aborted ahc0: Selection Timeout on A:3. 1 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted ahc0: Selection Timeout on A:6. 1 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted ahc0: Selection Timeout on A:9. 1 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted ahc0: Selection Timeout on A:14. 1 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted ahc0: target 4 synchronous at 10.0MHz, offset = 0xf ahc0: target 1 using 16bit transfers ahc0: target 1 synchronous at 40.0MHz, offset = 0xf ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 40.0MHz, offset = 0xf sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: Serial Number sa0: 10.000MB/s transfers (10.000MHz, offset 15) pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number LM243149000018380RZS pass0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number LM192475000018380TAE pass1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 4 lun 0 pass2: Removable Sequential Access SCSI-2 device pass2: Serial Number pass2: 10.000MB/s transfers (10.000MHz, offset 15) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number LM243149000018380RZS da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number LM192475000018380TAE da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Considering FFS root f/s. changing root device to da1s1a da1s1: type 0xa5, start 63, end = 8883944, size 8883882 : OK da1s2: type 0x82, start 8883945, end = 17751824, size 8867880 : OK ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 19:53:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (as1-p1.tfs.net [139.146.210.1]) by hub.freebsd.org (Postfix) with ESMTP id 8D4F314C9C for ; Wed, 28 Apr 1999 19:53:06 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id VAA00959; Wed, 28 Apr 1999 21:51:35 -0500 (CDT) From: Jim Bryant Message-Id: <199904290251.VAA00959@argus.tfs.net> Subject: Re: ep0 *UTP* In-Reply-To: from Leif Neland at "Apr 29, 99 00:27:45 am" To: root@neland.dk (Leif Neland) Date: Wed, 28 Apr 1999 21:51:34 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > Btw, why does boot write [*UTP*] ? > The card is working nicely with bnc. > > ep0 at port 0x300-0x30f irq 11 on isa0 > ep0: utp/bnc[*UTP*] address 00:60:08:09:c8:d9 > ep0: interrupting at irq 11 > > device ep0 at isa? port 0x300 irq 11 > > Leif good question. when were your sources built? i'm running a kernel from Thu Apr 8 10:40:17 CDT 1999. ep0 at 0x210-0x21f irq 10 on isa ep0: aui/bnc[*BNC*] address 00:20:af:d2:e4:ae jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 19:59:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AC98414E99 for ; Wed, 28 Apr 1999 19:59:37 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA11251; Wed, 28 Apr 1999 19:59:35 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 19:59:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199904290259.TAA11251@apollo.backplane.com> To: Luoqi Chen Cc: freebsd-current@FreeBSD.ORG Subject: buildworld failure - 'pcb_fs' field Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is with the latest cvs tree checked out. For -current. At a guess I would say that it's related to Luoqi's recent checkin. /FreeBSD/FreeBSD-4.x/src/gnu/usr.bin/gdb/gdb/freebsd-nat.c: In function `fetch_core_registers': /FreeBSD/FreeBSD-4.x/src/gnu/usr.bin/gdb/gdb/freebsd-nat.c:119: structure has no member named `pcb_fs' ... -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 20: 1:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id C9D0214E5D for ; Wed, 28 Apr 1999 20:01:19 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id WAA21034; Wed, 28 Apr 1999 22:58:35 -0400 (EDT) Date: Wed, 28 Apr 1999 22:58:35 -0400 (EDT) From: Chuck Robey To: Matthew Dillon Cc: Jim Shankland , current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: <199904281909.MAA08470@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Matthew Dillon wrote: > > :couldn't possibly be more open than RIP. > : > :> > :> OSPF has been around for a long time. > : > :But RIP is older, and was the first routing scheme. > > Which means.... nothing. RIP was designed for a time when networks > were simple. It has no multipath capabilities, it can *barely* > handle subnet masks, and it figures out when a route is dead by > letting packets loop until their TTL runs out. Also, propogation of > state loads the network in a non linear fashion and breaks down when you > have a lot of nodes. It works, but it isn't fun. You misunderstand. I wasn't saying it was good, I said it was first, which it was. According to my reading (reading only, I haven't looked at code) the split horizon with poisoned reverse idea is supposed to let it learn about dead routes far quicker ... pure distance vector would do that. I don't know what's actually in routed yet, and academic books are often completely out to lunch, I'm finding. > > -Matt > Matthew Dillon > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 20: 5:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id A5A4714C9C for ; Wed, 28 Apr 1999 20:05:29 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id XAA21056; Wed, 28 Apr 1999 23:01:44 -0400 (EDT) Date: Wed, 28 Apr 1999 23:01:44 -0400 (EDT) From: Chuck Robey To: Chris Dillon Cc: sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Chris Dillon wrote: > On Wed, 28 Apr 1999 sthaug@nethelp.no wrote: > > > > I can't quite figure why they stuck the word "open" in there, because it > > > couldn't possibly be more open than RIP. > > > > Probably because it was (at the time) in heavy "competition" with the OSI > > IS-IS routing protocol. Those standards were *not* openly available. (I > > believe they are now.) > > Someone correct me if I'm wrong, but OSPF stands for Open Shortest > Path First, and thus "Open" in this context would have nothing to do > with how "free" it is. I don't quite get that. It's a Djikstra calculation, using flooding to pass connection data ... does the SPF mean that it uses hop count only to figure path? Not any delay or traffic loading? > > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > FreeBSD: The fastest and most stable server OS on the planet. > For Intel x86 and Alpha architectures (SPARC under development). > ( http://www.freebsd.org ) > > "One should admire Windows users. It takes a great deal of > courage to trust Windows with your data." > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 20:12:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id CFD1014C9C for ; Wed, 28 Apr 1999 20:12:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA11447; Wed, 28 Apr 1999 20:12:15 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Apr 1999 20:12:15 -0700 (PDT) From: Matthew Dillon Message-Id: <199904290312.UAA11447@apollo.backplane.com> To: Luoqi Chen , freebsd-current@FreeBSD.ORG Subject: I take it back --- Re: buildworld failure - 'pcb_fs' field References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops. I take it back. It worked just fine. I was looking at the wrong xterm! -Matt Matthew Dillon : : This is with the latest cvs tree checked out. For -current. At a guess : I would say that it's related to Luoqi's recent checkin. : :/FreeBSD/FreeBSD-4.x/src/gnu/usr.bin/gdb/gdb/freebsd-nat.c: In function `fetch_core_registers': :/FreeBSD/FreeBSD-4.x/src/gnu/usr.bin/gdb/gdb/freebsd-nat.c:119: structure has no member named `pcb_fs' : ... : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 20:54:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-40.ppp.wenet.net [206.15.85.40]) by hub.freebsd.org (Postfix) with ESMTP id C866814CF8 for ; Wed, 28 Apr 1999 20:54:09 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id UAA03130; Wed, 28 Apr 1999 20:52:06 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Wed, 28 Apr 1999 20:52:06 -0700 (PDT) From: Alex Zepeda To: Jim Bryant Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: ep0 *UTP* In-Reply-To: <199904290251.VAA00959@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Jim Bryant wrote: > good question. when were your sources built? i'm running a kernel > from Thu Apr 8 10:40:17 CDT 1999. > > ep0 at 0x210-0x21f irq 10 on isa > ep0: aui/bnc[*BNC*] address 00:20:af:d2:e4:ae Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting: ep0 XXX: driver didn't set ifq_maxlen - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 20:59:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortis.futuresouth.com (mortis.futuresouth.com [209.45.228.14]) by hub.freebsd.org (Postfix) with ESMTP id 2F40414BF7 for ; Wed, 28 Apr 1999 20:59:16 -0700 (PDT) (envelope-from fullermd@over-yonder.net) Received: by mortis.futuresouth.com (Postfix, from userid 100) id 580B91E5D; Wed, 28 Apr 1999 22:59:12 -0500 (CDT) Date: Wed, 28 Apr 1999 22:59:11 -0500 From: "Matthew D. Fuller" To: current@freebsd.org Subject: -CURRENT told me to panic when it booted, so I did Message-ID: <19990428225911.A24796@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Editor: vi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get a thoroughtly reproducible (in fact, utterly non-un-reproducible) panic on boot of recent -CURRENTs. It did this on a cvsup from maybe 2, 3 days ago, and again with one done ~4pm CDT today. Note: all these messages are hand-copied, this machine isn't in a situation where it's easy to put a serial console on it :( Bootup gets as far as: isab0: at device 15.0 on pci0 which immediately suceeds probing xl0. -v doesn't show anything more revealing. Panic reads as: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x24000208 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01456f5 stack pointer = 0x10:0xc02d5ef8 frame pointer = 0x10:0xc02d5f04 code segment = base 0x0, limit 0xfffff, type 0x1b = DRL 0, pres 1, def32 1, gran 1 processor eflags = interrupts enabled, resume, IOPL=0 current process = 0 ( ) interrupt mask = net tty bio cam kernel: type 12 trap, code:0 DDB reveals Stopped at device_probe_and_attach+0x9 movl 0x8(%ebx),%edi The first few nuggets of creamy goodness 'trace' reveals are: device_probe_and_attach(24000200) at device_probe_and_attach+0x9 bus_generic_attach(c09e1880, c02d5f38, c0145737, c09e1880, c09e1880) at bus_generic_attach+0x16 DEVICE_ATTACH(c09e1880, c09e1880, 0, c061cb40, c02d5f48) at DEVICE_ATTACH+0x25 If previous items in the trace (I think there were around 6 of them) would be helpful, I can grab them; it's just a pain copying the !&$ things down ;) Ideas? Trashing it isn't really an option, I use it too much. It's not a critical server, so I can experiment with patches/etc on it, but it's my main workstation here, so I'd rather not trash it utterly in the process. It's presently up running this 3-day old -CURRENT world and a kernel from... early March, I think, working fine. System is a Compaq Deskpro 575, P120 processor, 80 megs RAM, 1 floppy, 1 IDE drive, built-in lnc1 (which doesn't get along with the lnc driver), xl0 used as net card, parallel port ZIP drive. Kernel config follows: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.166 1999/04/24 21:45:44 peter Exp $ machine i386 cpu I586_CPU ident NEWTAURUS maxusers 64 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=2000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options DDB options MAXMEM=(80*1024) config kernel root on wd0 controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 controller wdc1 at isa? disable port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 controller scbus0 device da0 #Only need one of these, the code dynamically grows device sa0 device pass0 # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? controller vpo0 at ppbus? device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') device lnc0 pseudo-device loop pseudo-device ether pseudo-device sl 4 pseudo-device tun 2 pseudo-device pty 32 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller MF4839 http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 21:18:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (as1-p1.tfs.net [139.146.210.1]) by hub.freebsd.org (Postfix) with ESMTP id BD1FA14FAE for ; Wed, 28 Apr 1999 21:18:51 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id XAA01135; Wed, 28 Apr 1999 23:18:44 -0500 (CDT) From: Jim Bryant Message-Id: <199904290418.XAA01135@argus.tfs.net> Subject: Re: ep0 *UTP* In-Reply-To: from Alex Zepeda at "Apr 28, 99 08:52:06 pm" To: garbanzo@hooked.net (Alex Zepeda) Date: Wed, 28 Apr 1999 23:18:43 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > On Wed, 28 Apr 1999, Jim Bryant wrote: > > > good question. when were your sources built? i'm running a kernel > > from Thu Apr 8 10:40:17 CDT 1999. > > > > ep0 at 0x210-0x21f irq 10 on isa > > ep0: aui/bnc[*BNC*] address 00:20:af:d2:e4:ae > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting: > > ep0 XXX: driver didn't set ifq_maxlen I still get that one too. Driver problem? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 22:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id B9C0B154E6 for ; Wed, 28 Apr 1999 22:34:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id HAA01789; Thu, 29 Apr 1999 07:34:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id HAA26217; Thu, 29 Apr 1999 07:34:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: jbryant@unix.tfs.net Cc: mauri@krabi.mbp.ee (Lauri Laupmaa), freebsd-current@FreeBSD.ORG Subject: Re: new clock good for unix (FreeBSD) In-reply-to: Your message of "Wed, 28 Apr 1999 16:34:56 CDT." <199904282134.QAA37205@argus.tfs.net> Date: Thu, 29 Apr 1999 07:34:44 +0200 Message-ID: <26215.925364084@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199904282134.QAA37205@argus.tfs.net>, Jim Bryant writes: >In reply: >> Hi >> >> Just wondering if the new swatch clock has its way into the date command... > >I'd rather that it wouldn't. Swatch is pulling a marketing stunt, >plain and simple. Something to toss in the closet with the pet rock a >year from now. Indeed, it has absolutely no redeeming features, whatsoever, pure marketing. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 23:11:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 0E56714D60; Wed, 28 Apr 1999 23:11:50 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA24891; Thu, 29 Apr 1999 08:11:44 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id IAA53498; Thu, 29 Apr 1999 08:11:43 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199904290611.IAA53498@greenpeace.grondar.za> To: obrien@NUXI.com Cc: Jean-Marc Zucconi , current@FreeBSD.ORG Subject: Re: make world failure In-Reply-To: Your message of " Wed, 28 Apr 1999 18:46:42 MST." <19990428184642.A77865@nuxi.com> References: <199904290119.DAA77398@qix.jmz.org> <19990428184642.A77865@nuxi.com> Date: Thu, 29 Apr 1999 08:11:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > On Thu, Apr 29, 1999 at 03:19:37AM +0200, Jean-Marc Zucconi wrote: > > I just encountered this: > > > > ===> gnu/usr.bin/cc/doc > > makeinfo -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc -I /u3/ src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/cp --no-split -I /u3/src/gn u/usr.bin/cc/doc -I /u3/src/gnu/usr.bin/cc/doc /u3/src/gnu/usr.bin/cc/doc/../.. /../../contrib/egcs/gcc/gcc.texi -o gcc.info > > As latest egcs committer, info docs are out of my forte. Hopefully > someone knowledgeable about them can help you out. Best chance is a total resup followed by a source-tree de-turd. I find that _two_ "make cleandir"'s followed by "cd /usr/obj;" does a good job even if it is a bit of overkill. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 28 23:45:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A163014CA2 for ; Wed, 28 Apr 1999 23:45:16 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA04951; Thu, 29 Apr 1999 08:45:06 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904290645.IAA04951@freebsd.dk> Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: from Brian Feldman at "Apr 28, 1999 9:58:48 pm" To: green@unixhelp.org (Brian Feldman) Date: Thu, 29 Apr 1999 08:45:06 +0200 (CEST) Cc: tseidmann@SIMULTAN.CH, current@FreeBSD.ORG, shocking@prth.pgs.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Feldman wrote: >Ever going to help with my atapi-fd problems? I found examples of the >corruptions, including lots of NULLs... Well, so long as I cannot get my hands on the problem, its real hard to solve it. I'm trying to get ahold of the same LS120 drive here but so far I havn't found any, in fact LS120 drives are extremely rare over here... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 0:56:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 005FC14C07 for ; Thu, 29 Apr 1999 00:56:27 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id QAA22922; Thu, 29 Apr 1999 16:56:25 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: freebsd-current@freebsd.org Cc: newconfig@jp.freebsd.org Reply-To: newconfig@jp.freebsd.org Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Newconfig snapshot From: Tomoaki NISHIYAMA X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990429165623F.tomoaki@moss.nibb.ac.jp> Date: Thu, 29 Apr 1999 16:56:23 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 33 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newconfig is now based on 4.0-CURRENT-990410, and the snapshot is available at ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/newconfig/snapshot/ snap_sys4c990410_19990429.diff.gz The CardBus and PCMCIA support patch is included in the patch. To test this patch you will do the following, 1. prepare the sys source of 4.0-CURRENT(990410) % cd /home/work % cvs -d /home/ncvs co -D '990410 00:00:00 JST' src/sys (provided that you have a copy of the CVS repository at /home/ncvs) 2. patch % gunzip snap_sys4c990410_19990429.diff.gz % cd src % patch -p1 < ../snap_sys4c990410_19990429.diff % find . -name '*.rej' -print # check that there is no reject file 3. make config.new % cd usr.sbin/config.new % make depend;make 4. configure and make kernel with the newconfig % cd ../../sys/i386/conf % ../../../usr.sbin/config.new/config.new NEWCONF % cd ../../compile/NEWCONF % make depend;make % cp kernel /tmp/kernel 5. test Boot with /tmp/kernel and test the behavior. Note /boot may have to be replaced. -- Tomoaki Nishiyama // Newconfig web page is at http://www.jp.freebsd.org/newconfig/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 3:14: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from qix.jmz.org (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id D27ED1516A for ; Thu, 29 Apr 1999 03:13:55 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.2) id MAA38799; Thu, 29 Apr 1999 12:13:56 +0200 (MET DST) (envelope-from jmz@FreeBSD.ORG) Date: Thu, 29 Apr 1999 12:13:56 +0200 (MET DST) Message-Id: <199904291013.MAA38799@qix.jmz.org> X-Authentication-Warning: qix.jmz.org: jmz set sender to jmz@FreeBSD.ORG using -f From: Jean-Marc Zucconi To: mark@grondar.za Cc: obrien@NUXI.com, current@FreeBSD.ORG In-reply-to: <199904290611.IAA53498@greenpeace.grondar.za> (message from Mark Murray on Thu, 29 Apr 1999 08:11:42 +0200) Subject: Re: make world failure X-Mailer: Emacs References: <199904290119.DAA77398@qix.jmz.org> <19990428184642.A77865@nuxi.com> <199904290611.IAA53498@greenpeace.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Mark Murray writes: > "David O'Brien" wrote: >> On Thu, Apr 29, 1999 at 03:19:37AM +0200, Jean-Marc Zucconi wrote: >> > I just encountered this: >> > >> > ===> gnu/usr.bin/cc/doc >> > makeinfo -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc -I /u3/ > src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/cp --no-split -I /u3/src/gn > u/usr.bin/cc/doc -I /u3/src/gnu/usr.bin/cc/doc /u3/src/gnu/usr.bin/cc/doc/../.. > /../../contrib/egcs/gcc/gcc.texi -o gcc.info >> >> As latest egcs committer, info docs are out of my forte. Hopefully >> someone knowledgeable about them can help you out. > Best chance is a total resup followed by a source-tree de-turd. I find > that _two_ "make cleandir"'s followed by "cd /usr/obj;" > does a good job even if it is a bit of overkill. It appears that this was a cvs problem: my update log showed: ... cvs update: Updating contrib/egcs/gcc cvs update: move away contrib/egcs/gcc/invoke.texi; it is in the way C contrib/egcs/gcc/invoke.texi I removed the file and did a 'cvs update -PdA' again and this solved the problem. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 3:39:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id AAC3014EC8 for ; Thu, 29 Apr 1999 03:39:01 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id OAA00439 for ; Thu, 29 Apr 1999 14:38:54 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@freebsd.org Subject: some bug reports... Date: Thu, 29 Apr 1999 14:01:05 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99042914385400.00520@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG running FreeBSD 4.0-CURRENT last 4 days i have encountered the following problems: 1. something is wrong with psm0 driver. my Genius NewScroll PS/2 mouse works well, but in random moment when i touch the mouse kernel begins to write to the systemn log the following. Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c8 != 0008). Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c0 != 0008). when it happens, mouse cursor moves, but buttons do not work. only reboot solves this problem. this bug doesn't appear with Microsoft and Hewlett-Packard mice. my string in my kernel config related to mouse is device psm0 at atkbdc? irq 12 and kernel detects the mouse as psm0: on atkbdc0 psm0: model NetMouse, device ID 0 psm0: interrupting at irq 12 2. i cannot run MySQL daemon since yesterday's "make world". here is a piece of MySQL's error log: mysqld started on ÞÔ 29 ÁÐÒ 1999 13:59:16 MSD /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "__vt_7filebuf" mysqld ended on ÞÔ 29 ÁÐÒ 1999 13:59:16 MSD 3. my ESS1868-based sound card (Luigi's pcm driver) do not work since one of kernel snapshots. the kernel says the follofing: Probing for PnP devices: CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] This is an ESS1868, but LDN 1 is disabled .. .. pcm0: not probed (disabled) the strings for pcm driver in kernel config are controller pnp0 device pcm0 at isa? disable port 0x220 irq 10 drq 1 flags 0x0 4. i don't think that it is really a bug, but it's just interesting for me. during bootup process my kernel writes the following message: Bad SMBIOS table checksum! so, what is SMBIOS table and why its checksum is bad? :) -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 3:44:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from columba.eur.3com.com (columba.eur.3com.com [161.71.169.13]) by hub.freebsd.org (Postfix) with ESMTP id 9914F1511C for ; Thu, 29 Apr 1999 03:44:41 -0700 (PDT) (envelope-from Florian_Uhl@eur.3com.com) Received: from toucana.eur.3com.com (toucana.eur.3com.com [140.204.220.50]) by columba.eur.3com.com (8.9.3/8.9.3) with ESMTP id LAA10726; Thu, 29 Apr 1999 11:44:15 +0100 (BST) Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com (8.9.3/8.9.3) with SMTP id LAA14345; Thu, 29 Apr 1999 11:43:41 +0100 (BST) Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256762.003BA6B3 ; Thu, 29 Apr 1999 11:51:32 +0100 X-Lotus-FromDomain: 3COM From: "Florian Uhl" To: camel@avias.com Cc: current@freebsd.org Message-ID: <80256762.003BA4ED.00@notesmta.eur.3com.com> Date: Thu, 29 Apr 1999 12:51:30 +0200 Subject: Re: some bug reports... Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please respond to camel@avias.com Sent by: Ilya Naumov To: current@FreeBSD.ORG Subject: some bug reports... >3. my ESS1868-based sound card (Luigi's pcm driver) do not work since one of >kernel snapshots. the kernel says the follofing: >Probing for PnP devices: >CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] >This is an ESS1868, but LDN 1 is disabled >pcm0: not probed (disabled) >the strings for pcm driver in kernel config are >controller pnp0 >device pcm0 at isa? disable port 0x220 irq 10 drq 1 flags 0x0 Delete "disable" or change it in "boot -c" mode. Cheers ... -- florian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 4:13:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 2AABA14E62 for ; Thu, 29 Apr 1999 04:13:29 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id PAA00824; Thu, 29 Apr 1999 15:13:27 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@FreeBSD.ORG Subject: Re: some bug reports... Date: Thu, 29 Apr 1999 15:07:32 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <80256762.003BA4ED.00@notesmta.eur.3com.com> Cc: Florian_Uhl@eur.3com.com MIME-Version: 1.0 Message-Id: <99042915132600.00457@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG th, 29 apr 1999, Florian Uhl wrote: > >3. my ESS1868-based sound card (Luigi's pcm driver) do not work since one of > >kernel snapshots. the kernel says the follofing: > > >CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: PNPb02f > [0x2fb0d041] > >This is an ESS1868, but LDN 1 is disabled > >pcm0: not probed (disabled) > Delete "disable" or change it in "boot -c" mode. thanks for good idea :) the last string don't appear anymore and... that's all. ESS still can't be detected. :( -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 5:25:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 96D5315803 for ; Thu, 29 Apr 1999 05:24:59 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id HAA84238; Thu, 29 Apr 1999 07:23:17 -0500 (CDT) (envelope-from bob) Date: Thu, 29 Apr 1999 07:23:17 -0500 From: Bob Willcox To: Wilko Bulte Cc: "Christopher T. Johnson" , shocking@prth.pgs.com, current@FreeBSD.ORG Subject: Re: Further on tape & CAM problems Message-ID: <19990429072317.A84044@luke.pmr.com> Reply-To: Bob Willcox References: <199904281654.MAA37459@neunacht.netgsi.com> <199904281845.UAA01026@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199904281845.UAA01026@yedi.iaf.nl>; from Wilko Bulte on Wed, Apr 28, 1999 at 08:45:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > Exabyte is not particularly famous for stable firmware. I have quite a number of 8200's here (though I don't really use them much anymore since I now have a Mammoth) that I have installed new firmware in. From an email discussion with an Exabyte tech support person back in '93 (I believe it was), the latest level of firmware in shipping 8200's (this was right at their end-of-life) was: MX: 2680 SV: C034 This is for generic models. OEM models may have different versions due to customizations. At the time he sent me the newest (but not ever installed in shipping products) MX firmware rev 2687 (SV C034 was still the newest) . I have, as a matter of course, upgraded the firmware in all of my 8200's to this 2687/C034 combination with good success. I have both of these ERPOM files handy and would gladly email them to anyone that wants them (you'll need access to an EPROM burner). Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 6:54:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from phobos.walker.dom (pmd-32.ior.com [206.107.145.224]) by hub.freebsd.org (Postfix) with ESMTP id D3C1C1583E for ; Thu, 29 Apr 1999 06:53:54 -0700 (PDT) (envelope-from kew@timesink.spk.wa.us) Received: from timesink.spk.wa.us (localhost.walker.dom [127.0.0.1]) by phobos.walker.dom (8.9.3/8.9.3) with ESMTP id GAA03321; Thu, 29 Apr 1999 06:53:08 -0700 (PDT) (envelope-from kew@timesink.spk.wa.us) Message-ID: <37286442.31514CBA@timesink.spk.wa.us> Date: Thu, 29 Apr 1999 06:53:07 -0700 From: Keith Walker X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@NUXI.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Progs linked against libstdc++ dead... References: <37272C41.6F889B3E@timesink.spk.wa.us> <19990428153908.A76974@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > Aagh! As of last-night's current (Tuesday), *NO* C++ program that > > links against libstdc++ works now. All of them come up with this > > error, and recompilation doesn't help :-( > > You have done a *FULL* CVSup and `make world'? You have then recopiled > any C++ libs from ports or private sources? > Yeah, I've been around long enough to know that that's the first thing you look for: parallax errors with cvsup :-) I've done quite a few *full* cvsup's (src-all) and four 'make worlds'. Nothing helped, although I'm trying Steve Price's idea now. -- Keith Walker, Spokane, WA FreeBSD 4.0-CURRENT (ASUS) #38: Wed Apr 28 13:45:37 PDT 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 7: 0:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 8565B15863 for ; Thu, 29 Apr 1999 07:00:13 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id QAA23742; Thu, 29 Apr 1999 16:00:08 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id PAA24971; Thu, 29 Apr 1999 15:55:43 +0200 (CEST) (envelope-from andreas) Date: Thu, 29 Apr 1999 15:55:42 +0200 From: Andreas Klemm To: "Alok K. Dhir" Cc: Tamiji Homma , phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: worldstone improvement... Message-ID: <19990429155542.A24950@titan.klemm.gtn.com> References: <19990428101628C.thomma@baynetworks.com> <003001be91a4$a8095300$5438b5d8@net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <003001be91a4$a8095300$5438b5d8@net>; from Alok K. Dhir on Wed, Apr 28, 1999 at 02:26:39PM -0400 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 02:26:39PM -0400, Alok K. Dhir wrote: > Are these changes going to be committed to -stable? Am running these changes (the diffs from his homepage) on 3.1-STABLE for a week or so without trouble. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 7:10:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from phobos.walker.dom (pmd-32.ior.com [206.107.145.224]) by hub.freebsd.org (Postfix) with ESMTP id 8188415841 for ; Thu, 29 Apr 1999 07:10:21 -0700 (PDT) (envelope-from kew@timesink.spk.wa.us) Received: from timesink.spk.wa.us (localhost.walker.dom [127.0.0.1]) by phobos.walker.dom (8.9.3/8.9.3) with ESMTP id HAA06218; Thu, 29 Apr 1999 07:10:03 -0700 (PDT) (envelope-from kew@timesink.spk.wa.us) Message-ID: <3728683A.F8D3411@timesink.spk.wa.us> Date: Thu, 29 Apr 1999 07:10:03 -0700 From: Keith Walker X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Steve Price Cc: obrien@NUXI.com, freebsd-current@FreeBSD.ORG Subject: Re: Progs linked against libstdc++ dead... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Price wrote: > On Wed, 28 Apr 1999, David O'Brien wrote: > > # > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined > # > symbol "__vt_7filebuf" > # > # I'm rather tied up until Sunday. So it will be few days unti I can > # really take a look at this. Until then, patches gladly accepted. > > Remember you asked. :-) > > [ patch elided ... ] Thank you sir! I recompiled cc and friends, then the libstdc++, and Shazam! everything works again. Haven't done an extensive test, but KDE works and my X10 daemon :-) Thank you, thank you, thank you! -- Keith Walker, Spokane, WA FreeBSD 4.0-CURRENT (NEW-ASUS) #1: Wed Apr 28 13:45:37 PDT 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 8:10:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40]) by hub.freebsd.org (Postfix) with ESMTP id 1F9CE14D17 for ; Thu, 29 Apr 1999 08:10:45 -0700 (PDT) (envelope-from gjohnson@nola.srrc.usda.gov) Received: (from glenn@localhost) by symbion.srrc.usda.gov (8.9.3/8.9.3) id KAA08311 for current@freebsd.org; Thu, 29 Apr 1999 10:10:44 -0500 (CDT) (envelope-from glenn) Date: Thu, 29 Apr 1999 10:10:43 -0500 From: Glenn Johnson To: current@freebsd.org Subject: Kernel won't boot from IDE disk Message-ID: <19990429101043.A7734@symbion.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am doing a fresh installation. I installed the April 23, 1999 snapshot of STABLE and then cvsupped the CURRENT source (4.0 CURRENT). I did a 'make world' and that went fine. I copied the GENERIC kernel config to a new file and edited the copied file. I deleted whatever drivers I did not need. I also deleted, perhaps mistakenly, but out of habit, the line: "options FAILSAFE" I set the flags to wdc0 and wdc1 to 'a0ffa0ff' I then added the following: options SOFTUPDATES options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options CPU_WT_ALLOC controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 Upon reboot, the system would hang after doing all of the probes. Below is some of the output that I got from a boot -v. I wrote this down on paper, so the formatting may be a little off. isa_compat: didn't get drq for wdc1 ... changing root device to wd0s1a At this point it hangs. But if I press a key on the keyboard I then get: wd0s1: type 0xa5, start 0, end = 3173183, size 3173184 wd0s1: C/H/S end 197/132/63 (1659041) != end 3173183: invalid start_init: trying /sbin/init wd0: interrupt timeout (status 50 error 0) wd0: wdtimeout() DMA status 4 This last two lines above are repeated 5x, then I get: wd0: Last time I say: interrupt timeout. Probably a portable PC. It is a desktop PC. I am not at the system now, so the following is from memory. It is an AMI BIOS, a Western Digital 1.6 GB IDE drive on the primary IDE and a Mitsumi 4x CD-ROM drive on the secondary IDE. I can't boot an old kernel because the only old kernel I have is a 3.1 kernel and it lacks 'curproc()'. I don't remember the exact message for that. If there is any more info that is needed I will see if I can get it but I guess I will have to reinstall 3.1 for now. I hope this information is of value. Thanks. -- Glenn Johnson gljohns@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 9:23:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B263C14F6F for ; Thu, 29 Apr 1999 09:23:42 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA85233 for current@freebsd.org; Thu, 29 Apr 1999 09:23:27 -0700 (PDT) (envelope-from obrien) Message-ID: <19990429092327.A85225@nuxi.com> Date: Thu, 29 Apr 1999 09:23:27 -0700 From: "David O'Brien" To: current@freebsd.org Subject: (FWD) Re: Progs linked against libstdc++ dead... Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Forwarded message from Steve Price ----- #> Remember you asked. :-) #> #> [ patch elided ... ] # # Thank you sir! I recompiled cc and friends, then the libstdc++, and # Shazam! everything works again. Haven't done an extensive test, but KDE # works and my X10 daemon :-) # # Thank you, thank you, thank you! Note the :-) above, this was said in jest. The patch reverts a change that David made to go back to the old, less efficient C++ vtable support. I have no doubt David will figure out what is wrong and fix it. However, this does bring up a problem that should probably be discussed a little bit more. Since the vtable thunks are more efficient and will eventually be the default, we might ought to stick with them. David mentioned that there might be problems with them, but with enough developers using -current to beat out the kinks we should be able to resolve them in short order. -steve ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 9:36:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A44D414FF0 for ; Thu, 29 Apr 1999 09:36:28 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA08156 for ; Thu, 29 Apr 1999 09:36:27 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA77727 for current@freebsd.org; Thu, 29 Apr 1999 09:36:26 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 29 Apr 1999 09:36:26 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: "newbus" CVSup collection is going away Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that the newbus code is in -current, the developers don't need (and aren't using) the separate repository any more. I am going to remove the "newbus" CVSup collection that was available from freefall and cvsup2. If you have been fetching that collection with CVSup, please remove it from your supfiles. Thanks, John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 9:57:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 5F9FE14FC6 for ; Thu, 29 Apr 1999 09:57:08 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id SAA01082 for current@freebsd.org; Thu, 29 Apr 1999 18:57:04 +0200 (SAT) (envelope-from reg) Date: Thu, 29 Apr 1999 18:57:04 +0200 From: Jeremy Lea To: current@freebsd.org Subject: Panic: Fatal trap 12, -CURRENT as of 8 days ago. Message-ID: <19990429185704.A410@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've been having a few problems recently, since the move to EGCS, and I finally caught my box in the act, with a core dump... My system is running -CURRENT (version detail below), with no changes other the Richard Seaman's LinuxThreads patches. It's a UP P5-233, which is an overclocked 166. dmesg, mount and kernel config attached. Yes I know, no overclocking, but the system has been stable for 19 months. I'll clock it back and try again if people suspect hardware, but first read The Whole Story: 1. The first kernel which I built with ECGS, no frills, on 5 Apr 02:30 (GMT+2) after the EGCS import (once the world seemed to be building again), I did the usual make buildworld, make installworld, config, make depend, make and then make install. The system paniced within a few seconds of the new kernel being installed. Major adrenalin rush since the new kernel was not there because of softupdates... 2. Apr 5 23:00, rebooted on new world and kernel with "-O -pipe -mpentium". Full ports rebuild with these flags. 3. Spontaneous reboot on 9 Apr 02:38, with some 'calru: negative time' messages (from Apache) in /var/log/messages and some 'clientReadRequest: FD ?? Invalid Request' messages from squid, neither of which I have seen before, over the previous 24 hours. System idle. 4. Apr 12 00:55, rebooted on new world and kernel with "-O -pipe -march=pentium", following tips from freebsd-current. 5. Apr 19 13:45, spontaneous reboot, system idle, following one "clientReadRequest" error plus the following (note the block number?): Apr 19 02:12:22 shale /kernel: wd0s1f: soft error reading fsbn 7414628 of 7414626-7414627 (wd0s1 bn 8375972; cn 14772 tn 3 sn 59) (status 58 error 2) 6. Apr 21 20:00, rebooted on new world and kernel following new_bus. 7. Apr 29 17:30, paniced to debugger, following a large number of "clientReadRequest" errors from squid. Finally got a core dump. Fatal trap 12: page fault while in kernel mode fault virtual address = 0xb0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01462b7 stack pointer = 0x10:0xc5021d3c frame pointer = 0x10:0xc5021d50 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 = Idle interrupt mask = net bio cam #0 0xc01441b5 in boot () #1 0xc01443f9 in panic () #2 0xc01233a5 in db_panic () #3 0xc0123343 in db_command () #4 0xc012340a in db_command_loop () #5 0xc01255e7 in db_trap () #6 0xc01be17c in kdb_trap () #7 0xc01c9db0 in trap_fatal () #8 0xc01c9a79 in trap_pfault () #9 0xc01c96b3 in trap () #10 0xc01462b7 in tsleep () #11 0xc01a2d96 in swap_pager_getpages () #12 0xc01a4012 in vm_fault () #13 0xc01c9a26 in trap_pfault () #14 0xc01c96b3 in trap () #15 0xc01c8c85 in swtch_com () #16 0xc013e4f4 in owait () #17 0xc013e035 in exit () #18 0xc01ca02a in syscall () #19 0xc01beaac in Xint0x80_syscall () Written down from kernel debugger: tsleep+0x1b. I have the core and kernel if anyone is interested. I can't put them up for FTP, but maybe John Hay can let me put them on internat.freebsd.org? Options: 1. Processor finally suffering from effects of overclocking. 2. UDMA IDE drive dying (squid cache is on the IDE). 3. Something doesn't like EGCS. 4. Something doesn't like -mpentium/-march=pentium. 5. I'm a moron. Like I said, I'll clock the machine back if needed, but these problems have only been around since the switch to EGCS, so I don't suspect that overclocking is the problem. I do have my suspicions about the IDE drive. (5) is always a option... :-) Regards, -Jeremy -- | "Come home my prodigal son, come home and lets be one, --+-- don't want to see you cry, don't make me tell you why, | you've lived in a house with me, my blood has set you free, | in the world you'll surely die, nothing else will satisfy." -MIC dmesg: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed Apr 21 19:54:36 SAT 1999 root@shale.csir.co.za:/usr/src/sys/compile/SHALE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 233864934 Hz CPU: Pentium/P55C (233.86-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62603264 (61136K bytes) Preloaded elf kernel "kernel" at 0xc0284000. Probing for PnP devices: CSN 1 Vendor ID: CTL0070 [0x70008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 isab0: at device 1.0 on pci0 ide_pci0: at device 1.1 on pci0 chip1: at device 1.3 on pci0 ahc0: at device 9.0 on pci0 ahc0: interrupting at irq 12 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs isa0: on motherboard wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 0 (atapi): , removable, accel, dma, iordy wcd0: drive speed 0 - 5843KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA, packet track wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc1: interrupting at irq 15 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 1 3C5x9 board(s) on ISA found at 0x300 ep0 at port 0x300-0x30f irq 10 on isa0 ep0: aui/utp[*UTP*] address 00:60:8c:90:af:c5 ep0: interrupting at irq 10 Intel Pentium detected, installing workaround for F00F bug ep0 XXX: driver didn't set ifq_maxlen ds0 XXX: driver didn't set ifq_maxlen Waiting 2 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) changing root device to da0s4a changing root device to da0a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates mount: /dev/da0a on / (local, soft-updates, writes: sync 3 async 465) /dev/da0f on /usr (local, noatime, soft-updates, writes: sync 9 async 375) /dev/da0e on /var (local, noatime, soft-updates, writes: sync 247 async 918) /dev/wd0s1a on /olddisk/root (local, noatime, soft-updates, writes: sync 2 async 0) /dev/wd0s1f on /olddisk/usr (local, noatime, soft-updates, writes: sync 2 async 77) /dev/wd0s1e on /olddisk/var (local, noatime, soft-updates, writes: sync 2 async 0) procfs on /proc (local) mfs:40 on /tmp (asynchronous, local, nodev, nosuid, writes: sync 2 async 263) swapinfo: Device 1K-blocks Used Avail Capacity Type /dev/da0b 262016 0 262016 0% Interleaved /dev/wd0s1b 140576 0 140576 0% Interleaved Total 402592 0 402592 0% config: machine "i386" cpu "I586_CPU" ident SHALE maxusers 50 options INET #InterNETworking #options IPX #IPX/SPX communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #Want one of these options MFS #Memory File System #options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SOFTUPDATES options UCONSOLE #Allow users to grab the console #options FAILSAFE #Be conservative #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options XSERVER # include code for XFree86 options SYSVSHM options SYSVSEM options SYSVMSG options USER_LDT #allow user-level control of i386 ldt options "VM86" options "AUTO_EOI_1" options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" options "MD5" config kernel root on da0 dumps on da0 controller isa0 controller pnp0 controller pci0 #controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 #disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff device wcd0 controller scbus0 #base SCSI code controller ahc0 device da0 #SCSI disks device pass0 #CAM passthrough driver device pt0 at scbus? # SCSI processor type device sctarg0 at scbus? # SCSI target options AHC_ALLOW_MEMIO # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? tty irq 1 #device psm0 at atkbdc? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port "IO_COM1" tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 controller ppbus0 #controller vpo0 at ppbus? device lpt0 at ppbus? device plip0 at ppbus? #device ppi0 at ppbus? #device pps0 at ppbus? #device lpbb0 at ppbus? #device ed0 at isa? port 0x240 net irq 15 iomem 0xd0000 #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 device ep0 at isa? port 0x300 net irq 10 pseudo-device loop pseudo-device ether #pseudo-device log #pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device #pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 4 #Vnode driver (turns a file into a device) # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing options DDB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 10:12:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DFA2B15846 for ; Thu, 29 Apr 1999 10:12:08 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id KAA08286; Thu, 29 Apr 1999 10:12:07 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA19544; Thu, 29 Apr 1999 10:12:07 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 29 Apr 1999 10:12:07 -0700 (PDT) Message-Id: <199904291712.KAA19544@vashon.polstra.com> To: sprice@hiwaay.net Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... In-Reply-To: <19990429092327.A85225@nuxi.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ----- Forwarded message from Steve Price ----- > > Since the vtable thunks are more efficient and will eventually > be the default, we might ought to stick with them. David mentioned > that there might be problems with them, but with enough developers > using -current to beat out the kinks we should be able to resolve > them in short order. I doubt it. The problems, according to the egcs team, are compiler bugs. It's unlikely any of us could fix them without going into a trance, smoking the g++ pipe three times a day, and abstaining from sexual relations for a year. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 10:16:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles545.castles.com [208.214.165.109]) by hub.freebsd.org (Postfix) with ESMTP id 178B514CD3 for ; Thu, 29 Apr 1999 10:16:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA02964; Thu, 29 Apr 1999 10:15:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904291715.KAA02964@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: camel@avias.com Cc: current@FreeBSD.ORG, Florian_Uhl@eur.3com.com Subject: Re: some bug reports... In-reply-to: Your message of "Thu, 29 Apr 1999 15:07:32 +0400." <99042915132600.00457@camel.avias.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Apr 1999 10:15:49 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > th, 29 apr 1999, Florian Uhl wrote: > > > >3. my ESS1868-based sound card (Luigi's pcm driver) do not work since one of > > >kernel snapshots. the kernel says the follofing: > > > > >CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: PNPb02f > > [0x2fb0d041] > > >This is an ESS1868, but LDN 1 is disabled > > >pcm0: not probed (disabled) > > > Delete "disable" or change it in "boot -c" mode. > > thanks for good idea :) the last string don't appear anymore and... that's > all. ESS still can't be detected. :( You need to set 'PnP OS' in your BIOS to _off_, and may possibly need to explicitly enable the device using userconfig. This is a FAQ, and does not belong on this list. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 10:45:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 3A37114BFC for ; Thu, 29 Apr 1999 10:45:12 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.187]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA381A; Thu, 29 Apr 1999 19:45:10 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id TAA00445; Thu, 29 Apr 1999 19:45:39 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 29 Apr 1999 19:45:39 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Kris Kennaway Subject: Re: Our routed - Vern says it's old and buggy. Cc: current@FreeBSD.ORG, sthaug@nethelp.no, Garrett Wollman , Kunihiro Ishiguro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Apr-99 Kris Kennaway wrote: > On Tue, 27 Apr 1999, Garrett Wollman wrote: > >> Most importantly: >> >> - Recent values of GateD are distributed under a very unfriendly >> license. > > There's also zebra, in ports (as someone pointed out on -net the other > day),which seems to be GPL'ed. I haven't tried either of the two except > to poke around briefly in the code.. Well, I can tell you this: the source code last time I was able to check it (which was about a week, week and a half ago) compiles cleanly under 2.2.8-4.x (where else did ye think those mentions on the site came from? ;) and also works as far as I have been able to test it. (People with better test environments than mine are MORE THAN WELCOME to test the routing code!) Thankfully I got Andreas Klemm on the list as well to test the source and we have been very active in reporting back bugs and submitting patches and Kunihiro-san has been very flexible with releasing snapshots for the ports as well as maintaining a ports directory within the total package for ease of use within FreeBSD. So for a Linux dude he has a very strong sympathy for FreeBSD =) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 11:26:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 1F95A14EB5 for ; Thu, 29 Apr 1999 11:26:40 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id NAA18982; Thu, 29 Apr 1999 13:26:36 -0500 (CDT) Date: Thu, 29 Apr 1999 13:26:36 -0500 (CDT) From: Steve Price To: John Polstra Cc: current@freebsd.org Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... In-Reply-To: <199904291712.KAA19544@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Apr 1999, John Polstra wrote: #> ----- Forwarded message from Steve Price ----- #> #> Since the vtable thunks are more efficient and will eventually #> be the default, we might ought to stick with them. David mentioned #> that there might be problems with them, but with enough developers #> using -current to beat out the kinks we should be able to resolve #> them in short order. # # I doubt it. The problems, according to the egcs team, are compiler # bugs. It's unlikely any of us could fix them without going into a # trance, smoking the g++ pipe three times a day, and abstaining from # sexual relations for a year. Fair enough, but the problem that really concerns me is that all the C++ libraries (and the programs that use them) will have to be recompiled when we make the switch. Is there a programatic way to tell which vtable implementation a library was compiled with? The compile-time error message doesn't count. Turning the new vtable implementation on at any time now or in the future is going to cause confusion. I guess the real question is will turning it on by default now make for less problems than waiting a month or two and then flipping the switch? -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 11:31: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id BA2C114EB5 for ; Thu, 29 Apr 1999 11:31:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA13926; Thu, 29 Apr 1999 11:30:55 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 29 Apr 1999 11:30:54 -0700 (PDT) From: Doug White To: Chuck Robey Cc: Matthew Dillon , Jim Shankland , current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Chuck Robey wrote: > On Wed, 28 Apr 1999, Matthew Dillon wrote: > > > > > :Matthew Dillon writes: > > : > > :> Given the choice between OSPF and RIP1/2, OSPF is far superior > > :> even on 'simple' networks. It is effectively an open protocol, > > :> like BGP. > > : > > :Matt, can you clarify what you mean by "open" here? I know it's > > :what the "O" in OSPF stands for, but in what way are OSPF and > > :BGP more open than RIP? > > : > > :Jim Shankland > > :NLynx Systems, Inc. > > > > You can download the protocol spec without putting forth cash. > > I haven't looked at it for a long time so I don't have a URL handy. > > And you didn't know that the RIP spec is even older, and was publicly > available via an RFC (the same as OSPF?) > > I can't quite figure why they stuck the word "open" in there, because it > couldn't possibly be more open than RIP. Because OSPF stands for 'Open Shortest Path First.' It has nothing to do with licensing. :-) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 11:37:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 647A215294 for ; Thu, 29 Apr 1999 11:37:18 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA14542; Thu, 29 Apr 1999 11:35:44 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 29 Apr 1999 11:35:44 -0700 (PDT) From: Doug White To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: /usr/share/examples/atapi scripts wrong In-Reply-To: <199904281855.UAA03456@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Soren Schmidt wrote: > It seems Doug White wrote: > > Hello ... > > > > The burn* scripts in /usr/share/examples/atapi try to use wormcontrol for > > some reason, which obviously doesn't work. Should we just dump them, or > > does someone have one that uses mkisofs/cdrecord that would be > > appropriate? > > What planet are you from ?? They work for ATAPI drives, and have > been since they were introduced, all the time using wormcontrol.. > > Our SCSI system (CAM) dont support wormdevices (the old did), but that > is something totally unrelated to /usr/share/examples/atapi. > ^^^^^ > Or you where just kidding ?? :) No. Someone on -questions complained that they didn't work. cdrecord seems the future of burning anyway, so why are we will mucking with worm*? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 11:38:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 0352F151F9 for ; Thu, 29 Apr 1999 11:38:21 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA15344; Thu, 29 Apr 1999 11:37:57 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 29 Apr 1999 11:37:57 -0700 (PDT) From: Doug White To: vortexia Cc: current@FreeBSD.ORG Subject: Re: PCM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, vortexia wrote: > I cvsupped from 3.1-RELEASE today to 4.0-CURRENT and since then PCM sound > has been screwed. Im using a crystal sound card, anyone having similar > problems? Someone's not reading -current, obviously. Yes, we know that audio is broken; it's been broken since April 20th. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 11:51:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (Postfix) with ESMTP id 637661509A for ; Thu, 29 Apr 1999 11:51:33 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from amber (pm3a-35.cybcon.com [205.147.75.164]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id LAA17735 for ; Thu, 29 Apr 1999 11:51:32 -0700 (PDT) Message-Id: <199904291851.LAA17735@mail.cybcon.com> From: "William" To: Subject: Re: PCM Date: Thu, 29 Apr 1999 11:50:29 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a question.....I am subscribed to -current, but am wondering how much of -current applies to the Alpha port? I am also subscribed to freebsd-alpha too.....FYI, I am running -current of a few days ago and it is running great on my alpha. William To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 11:56:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E4367151AF for ; Thu, 29 Apr 1999 11:56:07 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA30837; Thu, 29 Apr 1999 11:55:44 -0700 Date: Thu, 29 Apr 1999 11:55:43 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Christopher T. Johnson" Cc: freebsd-current@freebsd.org Subject: Re: Further on tape & CAM problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > and/or CAM issues. > > > > > > Has anyone tried a CAMDEBUG kernel and camcontrol tracing on? > > > > I'll be glad to turn it on if you tell me how to do it on only that > > tape drive. I'm getting ready for another mt erase test and that > > will take about an hour and a half. > > > > > > I'm rebuilding the kernel now with camdebug turned on. I'll do the > > mt erase with -I -T -S -c 0:4 and see what happens. > > > Please. This is what I meant. This is a -current system, right? I > actually have an ancient 8200 so I should be able to replicate the problem > if we figure out the deal on this. Let me know... I've hooked back up my 8200 for some testing again. There's a new variant to the 'mt stat' command in -current (it made it to 3.1-STABLE too): quarm.feral.com > mt -f /dev/rsa3.ctl stat Mode Density Blocksize bpi Compression Current: default variable 0 unsupported ---------available modes--------- 0: default variable 0 unsupported 1: default variable 0 unsupported 2: default variable 0 unsupported 3: default variable 0 unsupported --------------------------------- Current Driver State: Writing. --------------------------------- File Number: 0 Record Number: 7 so you can print out the driver's notion of what it is doing if things are mysteriously hung. That could give a clue where the breakage is (like, if the driver says it's state is 'at rest' the problem is possibly outside the sa driver). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 12:41:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id B7B4B15231 for ; Thu, 29 Apr 1999 12:41:19 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id MAA00919; Thu, 29 Apr 1999 12:41:13 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <3728B5D8.921896F@MexComUSA.net> Date: Thu, 29 Apr 1999 12:41:13 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: camel@avias.com Cc: current@FreeBSD.ORG Subject: MYSQL Re: some bug reports... References: <99042914385400.00520@camel.avias.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ilya Naumov wrote: > > 2. i cannot run MySQL daemon since yesterday's "make world". here is a piece of > MySQL's error log: > > mysqld started on ÞÔ 29 ÁÐÒ 1999 13:59:16 MSD > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "__vt_7filebuf" > mysqld ended on ÞÔ 29 ÁÐÒ 1999 13:59:16 MSD I am having the same problem with mysql3.22.21, does anyone have an idea for a solution. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 12:43:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 9CD2D14E77 for ; Thu, 29 Apr 1999 12:43:37 -0700 (PDT) (envelope-from erik@habatech.no) Received: from freebsd.habatech.no ([62.92.133.2]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id VAA07018; Thu, 29 Apr 1999 21:42:51 +0200 (CEST) (envelope-from erik@habatech.no) From: erik@habatech.no Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904282152.OAA01594@dingo.cdrom.com> Date: Thu, 29 Apr 1999 21:49:12 +0200 (CEST) Reply-To: erik@habatech.no Organization: Habatech AS To: Mike Smith Subject: Re: Problems with ahc (2940U2W) and USB Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Apr-99 Mike Smith wrote: > Check your BIOS settings related to USB; make sure you have it properly > turned on and have an interrupt allocated to the USB port. Try turning > it off, etc. > > Can we have some more verbose boot messages? Specifically, interrupt > details for the USB port as well as the 2940. This will come as soon as I recompile a problematic kernel... -- --------------------------------+---------------------------------------+ Erik H. Bakke, Habatech AS | To be or not to be... | E-Mail: erik@habatech.no | Is simply a question of binary logic. | This message was sent by XFMail | | --------------------------------+---------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 13:10:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from neunacht.netgsi.com (neunacht.netgsi.com [192.55.203.174]) by hub.freebsd.org (Postfix) with ESMTP id CEEFC15068 for ; Thu, 29 Apr 1999 13:10:11 -0700 (PDT) (envelope-from cjohnson@neunacht.netgsi.com) Received: (from cjohnson@localhost) by neunacht.netgsi.com (8.9.2/8.9.2) id QAA45479; Thu, 29 Apr 1999 16:09:48 -0400 (EDT) (envelope-from cjohnson) From: "Christopher T. Johnson" Message-Id: <199904292009.QAA45479@neunacht.netgsi.com> Subject: Re: Further on tape & CAM problems In-Reply-To: <19990429072317.A84044@luke.pmr.com> from Bob Willcox at "Apr 29, 99 07:23:17 am" To: bob@pmr.com Date: Thu, 29 Apr 1999 16:09:47 -0400 (EDT) Cc: wilko@yedi.iaf.nl, shocking@prth.pgs.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > Exabyte is not particularly famous for stable firmware. > > I have quite a number of 8200's here (though I don't really use them > much anymore since I now have a Mammoth) that I have installed new > firmware in. From an email discussion with an Exabyte tech support > person back in '93 (I believe it was), the latest level of firmware in > shipping 8200's (this was right at their end-of-life) was: > > MX: 2680 > SV: C034 > Unfortunately I don't have a eprom burner.... :-( Thanks for the info. I've still not found the problem and I'm still working on it. Today is make world and I'll test again. Already tried the new kernel and that failed to help. With the camcontrol debug with all flags on, this is what I got. (xpt0:ncr0:0:4:-1): debugging flags now f (xpt0:ncr0:0:4:-1): xpt_free_path (xpt0:ncr0:0:4:-1): xpt_release_path cam_debug: queuing for immediate ccb .... cam_debug: queuing for immediate ccb After which I have the same error again. After this world is installed, I'll test again, then build and test with a UP kernel. Chris PS Thanks for all the help I've been getting from people willing to try and replicate the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 13:45: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 67DA814D68; Thu, 29 Apr 1999 13:45:01 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id QAA07776; Thu, 29 Apr 1999 16:45:00 -0400 (EDT) Message-Id: <3.0.5.32.19990429164427.00b69730@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 29 Apr 1999 16:44:27 -0400 To: stable@freebsd.org From: Mike Tancsa Subject: Any action on PR 10570 ? getting closer to 65K :-( Cc: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am currently using a couple of FreeBSD boxes for my border routers, and it seems that the global routing table is getting closer and closer to 65K+ routes (i.e. sooner than later I am going to bump into PR 10570). I am not a systems programmer by any stretch of the imagination, so I would not know how to go about debugging anything and everything that would be effected by changing the size from a short to a long. I guess this PR only effects very few people, so I can understand it not being a priority. But are there any plans to look at it soon ? wat-border# netstat -nr | wc 59118 355941 4200959 ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 14:20:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 4355F14F35 for ; Thu, 29 Apr 1999 14:20:16 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA19776; Thu, 29 Apr 1999 22:53:49 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id WAA12290; Thu, 29 Apr 1999 22:26:36 +0200 (CEST) From: Wilko Bulte Message-Id: <199904292026.WAA12290@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <19990429072317.A84044@luke.pmr.com> from Bob Willcox at "Apr 29, 1999 7:23:17 am" To: bob@pmr.com Date: Thu, 29 Apr 1999 22:26:36 +0200 (CEST) Cc: cjohnson@neunacht.netgsi.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Bob Willcox wrote ... > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > Exabyte is not particularly famous for stable firmware. > > I have quite a number of 8200's here (though I don't really use them > much anymore since I now have a Mammoth) that I have installed new > firmware in. From an email discussion with an Exabyte tech support > person back in '93 (I believe it was), the latest level of firmware in Well, you sent it to me in March 1995 (just found the original email ;-) > shipping 8200's (this was right at their end-of-life) was: > > MX: 2680 > SV: C034 > > This is for generic models. OEM models may have different versions > due to customizations. And these are not recommended for general use. I have a second Exaybyte drive here, I could try to see what firmware that one has and if I can get it to fail. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 14:26: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 0522114C09 for ; Thu, 29 Apr 1999 14:25:58 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 12575 invoked by uid 1008); 29 Apr 1999 21:25:55 -0000 Message-ID: <19990429212555.12573.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Mike Tancsa Cc: freebsd-current@freebsd.org Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-reply-to: Your message of "Thu, 29 Apr 1999 16:44:27 -0400." <3.0.5.32.19990429164427.00b69730@staff.sentex.ca> Date: Fri, 30 Apr 1999 05:25:55 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa writes: > >I am currently using a couple of FreeBSD boxes for my border routers, and >it seems that the global routing table is getting closer and closer to 65K+ >routes (i.e. sooner than later I am going to bump into PR 10570). I am not >a systems programmer by any stretch of the imagination, so I would not know >how to go about debugging anything and everything that would be effected by >changing the size from a short to a long. I guess this PR only effects >very few people, so I can understand it not being a priority. But are >there any plans to look at it soon ? > >wat-border# netstat -nr | wc > 59118 355941 4200959 > > Hey, that is an interesting pr. I'd like to tackle this one if noone minds, I have a similar environment to debug this one in, but it might take a little time. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 14:42: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 80B3F15332 for ; Thu, 29 Apr 1999 14:41:58 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id QAA89343; Thu, 29 Apr 1999 16:41:38 -0500 (CDT) (envelope-from bob) Date: Thu, 29 Apr 1999 16:41:38 -0500 From: Bob Willcox To: Wilko Bulte Cc: bob@pmr.com, cjohnson@neunacht.netgsi.com, shocking@prth.pgs.com, current@FreeBSD.ORG Subject: Re: Further on tape & CAM problems Message-ID: <19990429164138.A89144@luke.pmr.com> Reply-To: Bob Willcox References: <19990429072317.A84044@luke.pmr.com> <199904292026.WAA12290@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199904292026.WAA12290@yedi.iaf.nl>; from Wilko Bulte on Thu, Apr 29, 1999 at 10:26:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote: > As Bob Willcox wrote ... > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > > > Exabyte is not particularly famous for stable firmware. > > > > I have quite a number of 8200's here (though I don't really use them > > much anymore since I now have a Mammoth) that I have installed new > > firmware in. From an email discussion with an Exabyte tech support > > person back in '93 (I believe it was), the latest level of firmware in > > Well, you sent it to me in March 1995 (just found the original > email ;-) > > > shipping 8200's (this was right at their end-of-life) was: > > > > MX: 2680 > > SV: C034 > > > > This is for generic models. OEM models may have different versions > > due to customizations. > > And these are not recommended for general use. Hmm, why is that? The newest of the IBM branded Exabyte 8200's that I have have precisely these firmware levels in them (2680 & C034). Also, I have here about 12 or so 8200's that I have changed to the 2687/C034 (most of them were already at C034 for the SV PROM) without problems. Have you checked the switch settings on the MX board? The IBM drives that I have all came with sw8 set to on which, according to the service manual, is for PI Cartridge Type (International). The off position is for P6 Cartridge type (Domestic, I assume means USA). My drives don't work (hang, as I recall) with this switch set to On. For those out there without the benefit of the service manual, here is the description of these switches: ------------------------------------------------------------------------------- Switch Off Position(0) On Position(1) ------------------------------------------------------------------------------- 1 Run Memory Test On Bypass Memory Test On Power-on reset (65 sec) Power-on reset (8 sec) 2 Parity checking Disabled Parity checking enabled 3 Odd or Even byte disconnect Even byte disconnect 4 Report busy status No busy enable 5 Fixed block mode on Variable block mode on power up power up 6 Normal data operations No disconnect during data transfer 7 Reserved for future use Reserved for future use 8 P6 Cartridge Type PI Cartridge Type (Domestic) (International) I have been setting my switches like so: 1 On 2 On 3 On 4 Off 5 On 6 Off 7 Off 8 Off Notes: Switch 1 is on the left-most side (looking at the card with the edge connector down) and the up position (closest to the top edge of the card) is to On position. Also, all of this applies to level 2 MX cards only. This is all I have ever seen, but I'm sure there are some level 1 cards out there somewhere. According to the service manual the level 1 cards use jumpers rather than switches and though the same functions seem to be there, there not in the same positions. If you happen to have one of these and want to know what their settings are email me. Hope this helps someone, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 15:36: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 83BBC153B4 for ; Thu, 29 Apr 1999 15:36:01 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA24824; Fri, 30 Apr 1999 00:20:51 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id AAA13703; Fri, 30 Apr 1999 00:26:02 +0200 (CEST) From: Wilko Bulte Message-Id: <199904292226.AAA13703@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904292009.QAA45479@neunacht.netgsi.com> from "Christopher T. Johnson" at "Apr 29, 1999 4: 9:47 pm" To: cjohnson@neunacht.netgsi.com (Christopher T. Johnson) Date: Fri, 30 Apr 1999 00:26:02 +0200 (CEST) Cc: bob@pmr.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Christopher T. Johnson wrote ... > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > > > Exabyte is not particularly famous for stable firmware. > > > > I have quite a number of 8200's here (though I don't really use them > > much anymore since I now have a Mammoth) that I have installed new > > firmware in. From an email discussion with an Exabyte tech support > > person back in '93 (I believe it was), the latest level of firmware in > > shipping 8200's (this was right at their end-of-life) was: > > > > MX: 2680 > > SV: C034 > > > Unfortunately I don't have a eprom burner.... :-( > ... > cam_debug: queuing for immediate ccb > .... > cam_debug: queuing for immediate ccb > > After which I have the same error again. > > After this world is installed, I'll test again, then build and test with > a UP kernel. > > Chris > > PS Thanks for all the help I've been getting from people willing to try > and replicate the problem. To get another datapoint I ran the 1.3Gb dump on another Exabyte drive. This one is a: sa0: Removable Sequential Access SCSI-CCS device No problems found. I'll do a resup and bring the testbox to the latest -current to see if that makes any difference. Will take time.. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 16: 7:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id F13DE14C95 for ; Thu, 29 Apr 1999 16:07:42 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA25569; Fri, 30 Apr 1999 00:39:42 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id AAA14008; Fri, 30 Apr 1999 00:36:25 +0200 (CEST) From: Wilko Bulte Message-Id: <199904292236.AAA14008@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <19990429164138.A89144@luke.pmr.com> from Bob Willcox at "Apr 29, 1999 4:41:38 pm" To: bob@pmr.com Date: Fri, 30 Apr 1999 00:36:25 +0200 (CEST) Cc: bob@pmr.com, cjohnson@neunacht.netgsi.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Bob Willcox wrote ... > On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote: > > As Bob Willcox wrote ... > > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > > shipping 8200's (this was right at their end-of-life) was: > > > > > > MX: 2680 > > > SV: C034 > > > > > > This is for generic models. OEM models may have different versions > > > due to customizations. > > > > And these are not recommended for general use. > > Hmm, why is that? The newest of the IBM branded Exabyte 8200's that I That is what I've been told by an Exabyte engineer years back. I can only guess that some OEMs need adaptations to the firmware behaviour that are incompatible with what the rest of the world needs (or has standardised on, e.g. in the ANSI SCSI standard). Again, guessing. > have have precisely these firmware levels in them (2680 & C034). Also, Mine works OK with that f/w. Not that I use the 8200 often anymore, I like my DLT4000 much better than the 8200. ;-) Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 16:49:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8F5D515155 for ; Thu, 29 Apr 1999 16:49:34 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id TAA12485; Thu, 29 Apr 1999 19:47:59 -0400 (EDT) Date: Thu, 29 Apr 1999 19:47:59 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: tseidmann@SIMULTAN.CH, current@FreeBSD.ORG, shocking@prth.pgs.com Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: <199904290645.IAA04951@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: >=20 > >Ever going to help with my atapi-fd problems? I found examples of the > >corruptions, including lots of NULLs... >=20 > Well, so long as I cannot get my hands on the problem, its real hard > to solve it. I'm trying to get ahold of the same LS120 drive here > but so far I havn't found any, in fact LS120 drives are extremely > rare over here... Basically, this drive is a Digital Research brand; it (its firmware?) is made by Motorola, and supposedly this is all the same as an off-the-shelf Imation drive. >=20 > -S=F8ren >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman _ __ ___ ____ ___ ___ ___ =20 green@unixhelp.org _ __ ___ | _ ) __| \=20 FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 16:49:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 7DC3315311 for ; Thu, 29 Apr 1999 16:49:35 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from transit.hanse.de (transit-a.Hanse.DE [193.174.9.161]) by kogge.Hanse.DE (8.9.1/8.9.1) with ESMTP id BAA75432 for ; Fri, 30 Apr 1999 01:49:21 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Received: from monster.transit-a.hanse.de (monster [193.174.9.163]) by transit.hanse.de (8.8.8/8.8.8) with ESMTP id BAA11314 for ; Fri, 30 Apr 1999 01:49:19 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Date: Fri, 30 Apr 1999 01:48:57 +0200 From: Stefan Bethke To: freebsd-current@freebsd.org Subject: make world fails when updating from older -current Message-ID: <59687.3134425737@monster.transit-a.hanse.de> Originator-Info: login-id=stb; server=transit.transit-a.hanse.de X-Mailer: Mulberry (MacOS) [1.4.0, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was trying to go to -current from RELENG_3. Realising that doing both egcs and newbus in one step might be one too much, I started off with a -current from about 3 weeks ago. make wold wnet fine mostly. However, building the modules faild at some point with the problem described below. I was able to finish the build by manually (cd /usr/src/sys/modules; make). Also, the kernel build failed on that source base (yeah, I should provide more info, but I'll still have to try the build on PRE_NEWBUS, and if that still fails, I will post appropriate information). Now, with a successful world from about three weeks ago, when trying to make buildworld from about 3 days ago, I get: ===> sys/modules/fxp @ -> /src/4/src/sys machine -> /src/4/src/sys/i386/include echo "#define NFXP 1" > fxp.h echo "#define NBPFILTER 0" > bpfilter.h touch opt_bdg.h perl5 /src/4/src/sys/modules/fxp/../../kern/makedevops.pl -h /src/4/src/sys/modules/fxp/../../kern/device_if.m perl5: not found *** Error code 1 Stop. Again, (cd /usr/src/sys/modules; make) seems to works fine. I haven't investigated this any further; but having perl5 not available despite being in the base system and having it in the path (/usr/bin/perl5) makes me somewhat suspicious... Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 18:41:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-17.ppp.wenet.net [206.15.85.17]) by hub.freebsd.org (Postfix) with ESMTP id 818BC14DFD for ; Thu, 29 Apr 1999 18:41:23 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id SAA05321; Thu, 29 Apr 1999 18:41:13 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Thu, 29 Apr 1999 18:41:13 -0700 (PDT) From: Alex Zepeda To: Jim Bryant Cc: freebsd-current@freebsd.org Subject: Re: ep0 *UTP* In-Reply-To: <199904290418.XAA01135@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Jim Bryant wrote: > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting: > > > > ep0 XXX: driver didn't set ifq_maxlen > > I still get that one too. Driver problem? I'm guessing so. I wonder if this is the cause of some odd network behavior I'm getting.. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 19:36: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mermaid.shore.net (mermaid.shore.net [207.244.124.6]) by hub.freebsd.org (Postfix) with ESMTP id 4A30714DFD for ; Thu, 29 Apr 1999 19:36:00 -0700 (PDT) (envelope-from ejon@colltech.com) Received: from tcgbstn-s01-22.port.shore.net (colltech.com) [207.244.110.22] by mermaid.shore.net with esmtp (Exim) for current@freebsd.org id 10d39i-0004jv-00; Thu, 29 Apr 1999 22:35:58 -0400 Message-ID: <372915AB.26D40EB3@colltech.com> Date: Thu, 29 Apr 1999 22:30:03 -0400 From: Eric@FreeBSD.ORG, \@FreeBSD.ORG, "Two Cats\" Jones "@FreeBSD.ORG X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: ppbus causes hangs? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I searched the mailing list archives and didn't find anything that looks like this, so maybe it's just me, but adding ppbus and lpt0 to my kernel config (sources cvsupped on 4/17) causes my machine to hang hard during boot. The freeze occurs shortly after probing my network card and is accompanied (sometimes) with an error like RTC BIOS diagnostic error ff My config looks like (if I comment out the ppc,ppbus, and lpt lines, the kernel works fine): machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident GENERIC maxusers 64 #makeoptions DEBUG="-g" #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS " req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on da0 # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 at nexus? #controller pnp0 # PnP support for ISA #controller eisa0 controller pci0 at nexus? controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd device wcd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller ncr0 controller ahc0 controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? tty irq 1 device psm0 at atkbdc? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver #pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #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 device npx0 at nexus? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # #device apm0 at nexus? disable flags 0x31 # Advanced Power Management device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? tty irq 7 controller ppbus0 device lpt0 at ppbus? #device plip0 at ppbus? #device ppi0 at ppbus? #controller vpo0 at ppbus? # # The following Ethernet NICs are all PCI devices. # device de0 # DEC/Intel DC21x4x (``Tulip'') pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. #pseudo-device bpfilter 4 #Berkeley packet filter # USB support #controller uhci0 #controller ohci0 #controller usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # #device ums0 #device ukbd0 #device ulpt0 #device uhid0 #device ugen0 Anyone have any advice? Eric Jones To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 19:42:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles557.castles.com [208.214.165.121]) by hub.freebsd.org (Postfix) with ESMTP id 1F2BC14EE4; Thu, 29 Apr 1999 19:42:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA00363; Thu, 29 Apr 1999 19:41:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904300241.TAA00363@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Eric@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: ppbus causes hangs? In-reply-to: Your message of "Thu, 29 Apr 1999 22:30:03 EDT." <372915AB.26D40EB3@colltech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Apr 1999 19:41:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try setting the flags on the 'ppc' device to 0x40 and _please_ report the results. > I searched the mailing list archives and didn't find anything that > looks like this, so maybe it's just me, but adding ppbus and lpt0 > to my kernel config (sources cvsupped on 4/17) causes my machine to > hang hard during boot. The freeze occurs shortly after probing > my network card and is accompanied (sometimes) with an error like > > RTC BIOS diagnostic error > ff > > My config looks like (if I comment out the ppc,ppbus, and lpt lines, > the kernel works fine): > > machine "i386" > cpu "I586_CPU" > cpu "I686_CPU" > ident GENERIC > maxusers 64 > > #makeoptions DEBUG="-g" #Build kernel with gdb(1) debug > symbols > options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep > this!] > options MFS #Memory Filesystem > options MFS_ROOT #MFS usable as root device, > "MFS" req'ed > #options NFS #Network Filesystem > #options NFS_ROOT #NFS usable as root > device, "NFS > " req'ed > options MSDOSFS #MSDOS Filesystem > options "CD9660" #ISO 9660 Filesystem > options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" > req'ed > options PROCFS #Process filesystem > options "COMPAT_43" #Compatible with BSD 4.3 [KEEP > THIS!] > options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device > options UCONSOLE #Allow users to grab the console > options FAILSAFE #Be conservative > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > > config kernel root on da0 > > # To make an SMP kernel, the next two are needed > #options SMP # Symmetric MultiProcessor > Kernel > #options APIC_IO # Symmetric (APIC) I/O > # Optionally these may need tweaked, (defaults shown): > #options NCPU=2 # number of CPUs > #options NBUS=4 # number of busses > #options NAPIC=1 # number of IO APICs > #options NINTR=24 # number of INTs > > controller isa0 at nexus? > #controller pnp0 # PnP support for ISA > #controller eisa0 > controller pci0 at nexus? > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 > disk fd0 at fdc0 drive 0 > > controller wdc0 at isa? port "IO_WD1" bio irq 14 > disk wd0 at wdc0 drive 0 > disk wd1 at wdc0 drive 1 > > controller wdc1 at isa? port "IO_WD2" bio irq 15 > disk wd > device wcd0 #IDE CD-ROM > device wfd0 #IDE Floppy (e.g. LS-120) > > # A single entry for any of these controllers (ncr, ahb, ahc) is > # sufficient for any number of installed devices. > controller ncr0 > controller ahc0 > > controller scbus0 > > device da0 > > device sa0 > > device pass0 > > device cd0 #Only need one of these, the code dynamically > grows > > # atkbdc0 controlls both the keyboard and the PS/2 mouse > controller atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? tty irq 1 > device psm0 at atkbdc? tty irq 12 > > device vga0 at isa? port ? conflicts > > # splash screen/screen saver > #pseudo-device splash > > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? tty > # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver > #device vt0 at isa? tty > #options XSERVER # support for X server > #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 > > device npx0 at nexus? port IO_NPX irq 13 > > # > # Laptop support (see LINT for more options) > # > #device apm0 at nexus? disable flags 0x31 # Advanced Power > Management > > device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 > device sio1 at isa? port "IO_COM2" tty irq 3 > device sio2 at isa? disable port "IO_COM3" tty irq 5 > device sio3 at isa? disable port "IO_COM4" tty irq 9 > > # Parallel port > device ppc0 at isa? port? tty irq 7 > controller ppbus0 > device lpt0 at ppbus? > #device plip0 at ppbus? > #device ppi0 at ppbus? > #controller vpo0 at ppbus? > > # > # The following Ethernet NICs are all PCI devices. > # > device de0 # DEC/Intel DC21x4x (``Tulip'') > > pseudo-device loop > pseudo-device ether > pseudo-device sl 1 > pseudo-device ppp 1 > pseudo-device tun 1 > pseudo-device pty 16 > pseudo-device gzip # Exec gzipped a.out's > > # KTRACE enables the system-call tracing facility ktrace(2). > # This adds 4 KB bloat to your kernel, and slightly increases > # the costs of each syscall. > options KTRACE #kernel tracing > > # This provides support for System V shared memory and message queues. > # > options SYSVSHM > options SYSVMSG > options SYSVSEM > > > # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be > # aware of the legal and administrative consequences of enabling this > # option. The number of devices determines the maximum number of > # simultaneous BPF clients programs runnable. > #pseudo-device bpfilter 4 #Berkeley packet filter > > > # USB support > #controller uhci0 > #controller ohci0 > #controller usb0 > # > # for the moment we have to specify the priorities of the device > # drivers explicitly by the ordering in the list below. This will > # be changed in the future. > # > #device ums0 > #device ukbd0 > #device ulpt0 > #device uhid0 > #device ugen0 > > Anyone have any advice? > > Eric Jones > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 19:50:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-53.ix.netcom.com [207.93.148.53]) by hub.freebsd.org (Postfix) with ESMTP id E232E14D66 for ; Thu, 29 Apr 1999 19:50:51 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id TAA02360; Thu, 29 Apr 1999 19:50:28 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Thu, 29 Apr 1999 19:50:28 -0700 (PDT) Message-Id: <199904300250.TAA02360@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: current@FreeBSD.ORG Subject: libstdc++ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I lost the thread for this problem and it is not in the archives. I am running 4.0-current SMP, as of a couple hours ago, cvsup this morning. What was the solution to: /usr/lib/libstdc++.so.3: Undefined symbol "__vt_7filebuf" /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' etc. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 20:16:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-53.ix.netcom.com [207.93.148.53]) by hub.freebsd.org (Postfix) with ESMTP id C994414F5D for ; Thu, 29 Apr 1999 20:16:38 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id UAA02510; Thu, 29 Apr 1999 20:16:35 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Thu, 29 Apr 1999 20:16:35 -0700 (PDT) Message-Id: <199904300316.UAA02510@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: current@FreeBSD.ORG In-reply-to: <199904300250.TAA02360@ix.netcom.com> (message from Thomas Dean on Thu, 29 Apr 1999 19:50:28 -0700 (PDT)) Subject: Re: libstdc++ References: <199904300250.TAA02360@ix.netcom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some more information. c++ worked on Apr 12 and Apr 20. I did cvsup/make world/make kernel on: Apr 12 Apr 21 Apr 28 Apr 29 I believe the Apr 29 make world broke it. I used xpdf last night, after the make world. today, it complains of 'undefined symbol __vt_7filebuf' tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 21:35:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E95D614E58 for ; Thu, 29 Apr 1999 21:35:04 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA16000; Fri, 30 Apr 1999 14:05:01 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA81339; Fri, 30 Apr 1999 14:05:00 +0930 (CST) Date: Fri, 30 Apr 1999 14:05:00 +0930 From: Greg Lehey To: Glenn Johnson Cc: current@FreeBSD.ORG Subject: IDE DMA timeouts (was: Kernel won't boot from IDE disk) Message-ID: <19990430140500.E80561@freebie.lemis.com> References: <19990429101043.A7734@symbion.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990429101043.A7734@symbion.srrc.usda.gov>; from Glenn Johnson on Thu, Apr 29, 1999 at 10:10:43AM -0500 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 29 April 1999 at 10:10:43 -0500, Glenn Johnson wrote: > I am doing a fresh installation. I installed the April 23, 1999 snapshot > of STABLE and then cvsupped the CURRENT source (4.0 CURRENT). I did a > 'make world' and that went fine. I copied the GENERIC kernel config to > a new file and edited the copied file. I deleted whatever drivers I did > not need. I also deleted, perhaps mistakenly, but out of habit, the > line: > > "options FAILSAFE" I don't think this is your problem. > I set the flags to wdc0 and wdc1 to 'a0ffa0ff' This might be. > I then added the following: > > options SOFTUPDATES > options P1003_1B > options _KPOSIX_PRIORITY_SCHEDULING > options _KPOSIX_VERSION=199309L > options CPU_WT_ALLOC > > controller snd0 > device sb0 at isa? port 0x220 irq 5 drq 1 > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > device opl0 at isa? port 0x388 > > Upon reboot, the system would hang after doing all of the probes. Below is some > of the output that I got from a boot -v. I wrote this down on paper, so the > formatting may be a little off. > > isa_compat: didn't get drq for wdc1 > ... > changing root device to wd0s1a > > At this point it hangs. But if I press a key on the keyboard I then get: > wd0s1: type 0xa5, start 0, end = 3173183, size 3173184 > wd0s1: C/H/S end 197/132/63 (1659041) != end 3173183: invalid > start_init: trying /sbin/init > wd0: interrupt timeout (status 50 error 0) > wd0: wdtimeout() DMA status 4 > > This last two lines above are repeated 5x, then I get: > > wd0: Last time I say: interrupt timeout. Probably a portable PC. > > It is a desktop PC. I am not at the system now, so the following is from > memory. It is an AMI BIOS, a Western Digital 1.6 GB IDE drive on the > primary IDE and a Mitsumi 4x CD-ROM drive on the secondary IDE. What's your chipset? If it's an SiS 5591, I'd be interested in seeing your complete dmesg output (preferably with a -v output). You'll also be able to get it to work by changing the wdc0 flags to eliminate DMA. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 22:21:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1D6D3152D7 for ; Thu, 29 Apr 1999 22:21:45 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA11057; Thu, 29 Apr 1999 22:21:43 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA03402; Thu, 29 Apr 1999 22:21:43 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 29 Apr 1999 22:21:43 -0700 (PDT) Message-Id: <199904300521.WAA03402@vashon.polstra.com> To: peter@netplex.com.au Subject: Re: Heads up! config(8) changes.. In-Reply-To: <19990424190901.D3A791F58@spinner.netplex.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990424190901.D3A791F58@spinner.netplex.com.au>, Peter Wemm wrote: > This shouldn't cause much in the way of trouble, but it will complain > about old lint in your config files. That includes 'net/tty/bio/cam' > mask indicators, and 'vector xxxintr' as well as some of the wierder > workarounds for the poor 'options' parsing. > > So: things like: > device sio1 at isa? tty port "IO_COM2" tty irq 3 > become: > device sio1 at isa? port IO_COM2 irq3 What do you do about the "ppc" device? Formerly, it needed to be "net irq ..." if the "plip" device was going to be used, but "tty irq ..." otherwise. Which one did you pick? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 22:28: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles557.castles.com [208.214.165.121]) by hub.freebsd.org (Postfix) with ESMTP id 0F74E15098 for ; Thu, 29 Apr 1999 22:27:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA01120; Thu, 29 Apr 1999 22:26:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904300526.WAA01120@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: peter@netplex.com.au, current@freebsd.org Subject: Re: Heads up! config(8) changes.. In-reply-to: Your message of "Thu, 29 Apr 1999 22:21:43 PDT." <199904300521.WAA03402@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Apr 1999 22:26:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <19990424190901.D3A791F58@spinner.netplex.com.au>, > Peter Wemm wrote: > > This shouldn't cause much in the way of trouble, but it will complain > > about old lint in your config files. That includes 'net/tty/bio/cam' > > mask indicators, and 'vector xxxintr' as well as some of the wierder > > workarounds for the poor 'options' parsing. > > > > So: things like: > > device sio1 at isa? tty port "IO_COM2" tty irq 3 > > become: > > device sio1 at isa? port IO_COM2 irq3 > > What do you do about the "ppc" device? Formerly, it needed to be "net > irq ..." if the "plip" device was going to be used, but "tty irq ..." > otherwise. Which one did you pick? It needs to flip between one or both, but I can't raise Nicolas lately, so I'm starting to fear that we're going to need a new maintainer. That bites, given how well things were going. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 22:34:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B811E152D7; Thu, 29 Apr 1999 22:33:55 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA30838; Thu, 29 Apr 1999 22:33:41 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Apr 1999 22:33:41 -0700 (PDT) From: Matthew Dillon Message-Id: <199904300533.WAA30838@apollo.backplane.com> To: Mike Smith Cc: Eric@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ppbus causes hangs? References: <199904300241.TAA00363@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Try setting the flags on the 'ppc' device to 0x40 and _please_ report :the results. Yes, this fixes the problem for me. But, it has to be the *DEFAULT*. The flag should be used to enable the more sophisticated operation that might freeze the machine up, not disable it. :-( -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 22:40: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 28E3614C1E for ; Thu, 29 Apr 1999 22:39:58 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA11140; Thu, 29 Apr 1999 22:39:57 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA14785; Thu, 29 Apr 1999 22:39:56 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 29 Apr 1999 22:39:56 -0700 (PDT) Message-Id: <199904300539.WAA14785@vashon.polstra.com> To: steve@khoral.com Subject: Re: XFree86 and egcs In-Reply-To: <199904282026.OAA13313@zen.alb.khoral.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904282026.OAA13313@zen.alb.khoral.com>, Steve Jorgensen wrote: > > In article <199904271932.NAA01643@zen.alb.khoral.com>, > > Steve Jorgensen wrote: > > > I cvsup'ed and installed yesterday morning it's the third > > > cvsup I've done since egcs went in, so I know it's working > > > ok. Anyway, I decided to update my XFree86 installation, > > > and found that the port no longer works. As it compiles > > > all binaries created report tons of missing symbols > > > from the various X library. The wierd thing is that it > > > still installs most of the X binaries anyway, and they work > > > fine, but it dies when it gets to installing the X server > > > itself. [...] > Ok, well in the interest of not sending large compile > output to the news group, I've put an error log on > my webserver with all the info in it: > > http://www.haunt.com/~steve/error.html I took a look at it. All those undefined symbols are supposed to be in the "-lX11" library. I don't really know why you're getting them. Maybe you have an older version of the library lying around that is stripped? Try a "locate libX11.so" and see what's there. Then do "file libX11.so" on each one and see if it's stripped. Maybe your LD_LIBRARY_PATH environment variable is set, screwing up the build? Maybe you've got something funny in /etc/make.conf? Sorry, these are just guesses. I've never encountered the problem you're reporting. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 22:52:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7B1EE14E93 for ; Thu, 29 Apr 1999 22:52:51 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA11193; Thu, 29 Apr 1999 22:52:50 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA14825; Thu, 29 Apr 1999 22:52:50 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 29 Apr 1999 22:52:50 -0700 (PDT) Message-Id: <199904300552.WAA14825@vashon.polstra.com> To: sprice@hiwaay.net Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Steve Price wrote: > Fair enough, but the problem that really concerns me is that > all the C++ libraries (and the programs that use them) will have > to be recompiled when we make the switch. Is there a programatic > way to tell which vtable implementation a library was compiled > with? The compile-time error message doesn't count. Turning > the new vtable implementation on at any time now or in the future > is going to cause confusion. I guess the real question is will > turning it on by default now make for less problems than waiting > a month or two and then flipping the switch? These are good questions, and I don't know enough yet about the issues surrounding vtable thunks to answer them. We'll of course try to avoid the need to recompile libraries, but if that turns out to be impossible ... well, this is -current, after all. :-} John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 29 22:55:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D7ADF1521F; Thu, 29 Apr 1999 22:55:44 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA11216; Thu, 29 Apr 1999 22:55:44 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA14843; Thu, 29 Apr 1999 22:55:43 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 29 Apr 1999 22:55:43 -0700 (PDT) Message-Id: <199904300555.WAA14843@vashon.polstra.com> To: adrian@freebsd.org Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-Reply-To: <19990429212555.12573.qmail@ewok.creative.net.au> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990429212555.12573.qmail@ewok.creative.net.au>, wrote: > Mike Tancsa writes: > > > >I am currently using a couple of FreeBSD boxes for my border routers, and > >it seems that the global routing table is getting closer and closer to 65K+ > >routes (i.e. sooner than later I am going to bump into PR 10570). I am not > >a systems programmer by any stretch of the imagination, so I would not know > >how to go about debugging anything and everything that would be effected by > >changing the size from a short to a long. I guess this PR only effects > >very few people, so I can understand it not being a priority. But are > >there any plans to look at it soon ? > > > >wat-border# netstat -nr | wc > > 59118 355941 4200959 > > > > > > Hey, that is an interesting pr. > > I'd like to tackle this one if noone minds, I have a similar environment > to debug this one in, but it might take a little time. Of course nobody minds! :-) I posted a follow-up, but it went into the black hole of cvs-all. Briefly, I grepped the source tree and I believe that if you change the field to an "int" and then do a full make world and kernel build, it should work just fine. I recommend using an int rather than a long because on the Alpha, a long is 64 bits. (int32_t would be OK, too.) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 1:29: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id F3EB0158EA for ; Fri, 30 Apr 1999 01:28:59 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 14596 invoked by uid 1008); 30 Apr 1999 08:28:56 -0000 Message-ID: <19990430082856.14594.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: John Polstra Cc: freebsd-current@freebsd.org, mike@sentex.net, andrewb@demon.net Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-reply-to: Your message of "Thu, 29 Apr 1999 22:55:43 MST." <199904300555.WAA14843@vashon.polstra.com> Date: Fri, 30 Apr 1999 16:28:55 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: >In article <19990429212555.12573.qmail@ewok.creative.net.au>, > wrote: >> Mike Tancsa writes: >> > >> >I am currently using a couple of FreeBSD boxes for my border routers, and >> >it seems that the global routing table is getting closer and closer to 65K+ >> >routes (i.e. sooner than later I am going to bump into PR 10570). I am not >> >a systems programmer by any stretch of the imagination, so I would not know >> >how to go about debugging anything and everything that would be effected by >> >changing the size from a short to a long. I guess this PR only effects >> >very few people, so I can understand it not being a priority. But are >> >there any plans to look at it soon ? >> > >> >wat-border# netstat -nr | wc >> > 59118 355941 4200959 >> > >> > >> >> Hey, that is an interesting pr. >> >> I'd like to tackle this one if noone minds, I have a similar environment >> to debug this one in, but it might take a little time. > >Of course nobody minds! :-) > >I posted a follow-up, but it went into the black hole of cvs-all. >Briefly, I grepped the source tree and I believe that if you change >the field to an "int" and then do a full make world and kernel >build, it should work just fine. I recommend using an int rather >than a long because on the Alpha, a long is 64 bits. (int32_t would >be OK, too.) Yup. I checked the source tree for ifa_refcnt and IFAFREE, and including a couple of man page references, all the code plays with ifa_refcnt directly without assigning it to variables and vice versa. I'll submit a followup to the pr, and a patch after I've verified it doesn't panic the system, but that will be sometime early next week (I can't setup a BGP connection to flood routes in and out before then..) (I've CC:ed the original pr poster, although I'm not entirely sure if the same holds for OpenBSDs source tree..) Adrian Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 2:10:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 880C915843 for ; Fri, 30 Apr 1999 02:10:32 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 7590 invoked from network); 30 Apr 1999 09:10:28 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 30 Apr 1999 09:10:28 -0000 Date: Fri, 30 Apr 1999 02:08:52 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Mike Tancsa Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-Reply-To: <3.0.5.32.19990429164427.00b69730@staff.sentex.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting, I was considering trying this with a new UUNET connection with gated, but they're sending me 69,000+ routes. Glad I didn't try it yet. :) On Thu, 29 Apr 1999, Mike Tancsa wrote: > > I am currently using a couple of FreeBSD boxes for my border routers, and > it seems that the global routing table is getting closer and closer to 65K+ > routes (i.e. sooner than later I am going to bump into PR 10570). I am not > a systems programmer by any stretch of the imagination, so I would not know > how to go about debugging anything and everything that would be effected by > changing the size from a short to a long. I guess this PR only effects > very few people, so I can understand it not being a priority. But are > there any plans to look at it soon ? > > wat-border# netstat -nr | wc > 59118 355941 4200959 > > > ---Mike > ------------------------------------------------------------------------ > Mike Tancsa, tel 01.519.651.3400 > Network Administrator, mike@sentex.net > Sentex Communications www.sentex.net > Cambridge, Ontario Canada > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 2:38:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from lists.skynet.be (lists.skynet.be [195.238.1.42]) by hub.freebsd.org (Postfix) with ESMTP id 95D7F1530B; Fri, 30 Apr 1999 02:38:25 -0700 (PDT) (envelope-from brad@mail.his.com) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by lists.skynet.be (8.9.1/8.9.1) with SMTP id LAA12507; Fri, 30 Apr 1999 11:43:18 +0200 (CEST) (envelope-from brad@mail.his.com) X-Mailer: CTM PowerMail 2.4 x-sender: brad@mail.his.com Date: Fri, 30 Apr 1999 11:38:32 +0200 To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org From: Brad Knowles Subject: Porting Greg Lehey's rawio.c from FreeBSD to Linux... Message-Id: <19990430113832.005448@lists.skynet.be> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I don't want to get into any OS wars here, but I'd like to do some low-level disk benchmarking of a Linux system using the same tool I used for that under FreeBSD, namely Greg Lehey's "rawio" (see ). This program was originally written to test his "vinum" software mirroring/striping/RAID device driver for FreeBSD (see ), but I believe that it would be generally useful to do low-level disk testing under most any *nix OS. Anyway, if there's anyone out there with any experience in porting programs that do low-level disk I/O, I'd appreciate it if you could take a look at this program and give me some pointers on what it would take to get it to compile and run under Linux (specifically, Debian Linux with kernel 2.2.6). Also, since I'm not subscribed to either of these mailing lists and I can't keep up with the newsgroup gateway for them, I would appreciate it if you would also e-mail me any responses you might have on this subject. TIA! -- Brad Knowles Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 3:27: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id A56381552F; Fri, 30 Apr 1999 03:27:03 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr ([137.194.24.253]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id MAA26380; Fri, 30 Apr 1999 12:26:54 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 88815D21B; Fri, 30 Apr 1999 12:26:51 +0200 (CEST) Message-ID: <19990430122651.A11742@enst.fr> Date: Fri, 30 Apr 1999 12:26:51 +0200 From: Pierre Beyssac To: adrian@FreeBSD.ORG, John Polstra Cc: freebsd-current@FreeBSD.ORG, mike@sentex.net, andrewb@demon.net Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: <199904300555.WAA14843@vashon.polstra.com> <19990430082856.14594.qmail@ewok.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990430082856.14594.qmail@ewok.creative.net.au>; from adrian@FreeBSD.ORG on Fri, Apr 30, 1999 at 04:28:55PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 30, 1999 at 04:28:55PM +0800, adrian@FreeBSD.ORG wrote: > I'll submit a followup to the pr, and a patch after I've verified it > doesn't panic the system, but that will be sometime early next week > (I can't setup a BGP connection to flood routes in and out before then..) Uh, from reading the PR it looks like it can be triggered by creating a little more than 2^16 routes to the same destination, and then deleting some of them to fall back under 2^16. I'm going to give it a try now and I'll send you the script if that works. I'm also making a world with "short" changed to "int" to see if it works. Wouldn't it be sensible to issue a warning (or panic) when increasing the reference count reaches 0, rather than causing a later kernel segfault? It would involve some overhead though, and I'm not sure having 2^32 routes is currently realistic since most machines don't even have that many bytes of RAM, but it might be true one day... -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 3:53:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 0D0E914DCC for ; Fri, 30 Apr 1999 03:53:39 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 48E9218D0; Fri, 30 Apr 1999 12:54:01 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 45D0C49C2; Fri, 30 Apr 1999 12:54:01 +0200 (CEST) Date: Fri, 30 Apr 1999 12:54:01 +0200 (CEST) From: Andrzej Bialecki To: Soren Schmidt Cc: Brian Feldman , tseidmann@SIMULTAN.CH, current@FreeBSD.ORG, shocking@prth.pgs.com Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: <199904290645.IAA04951@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > > >Ever going to help with my atapi-fd problems? I found examples of the > >corruptions, including lots of NULLs... > > Well, so long as I cannot get my hands on the problem, its real hard > to solve it. I'm trying to get ahold of the same LS120 drive here > but so far I havn't found any, in fact LS120 drives are extremely > rare over here... As I said before, I can make some tests, but unfortunately my machine doesn't want to mount disks at all with the new ATA code... Please take a look at the message I sent about a week ago. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 4: 5:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 10A5A14FB0 for ; Fri, 30 Apr 1999 04:05:14 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA08369; Fri, 30 Apr 1999 13:04:52 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904301104.NAA08369@freebsd.dk> Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: from Andrzej Bialecki at "Apr 30, 1999 12:54: 1 pm" To: abial@webgiro.com (Andrzej Bialecki) Date: Fri, 30 Apr 1999 13:04:52 +0200 (CEST) Cc: green@unixhelp.org, tseidmann@SIMULTAN.CH, current@FreeBSD.ORG, shocking@prth.pgs.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Andrzej Bialecki wrote: > > >Ever going to help with my atapi-fd problems? I found examples of the > > >corruptions, including lots of NULLs... > > > > Well, so long as I cannot get my hands on the problem, its real hard > > to solve it. I'm trying to get ahold of the same LS120 drive here > > but so far I havn't found any, in fact LS120 drives are extremely > > rare over here... > > As I said before, I can make some tests, but unfortunately my machine > doesn't want to mount disks at all with the new ATA code... Please take a > look at the message I sent about a week ago. Unfortunately they dont tell me much :( I'll have to rearrange some disks here and try to make some new installs see if I can get the problem to appear then.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 4: 8:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 2701814FB0 for ; Fri, 30 Apr 1999 04:08:24 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 14904 invoked by uid 1008); 30 Apr 1999 11:08:19 -0000 Message-ID: <19990430110819.14902.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Pierre Beyssac Cc: freebsd-current@freebsd.org Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-reply-to: Your message of "Fri, 30 Apr 1999 12:26:51 +0200." <19990430122651.A11742@enst.fr> Date: Fri, 30 Apr 1999 19:08:18 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac writes: >On Fri, Apr 30, 1999 at 04:28:55PM +0800, adrian@FreeBSD.ORG wrote: >> I'll submit a followup to the pr, and a patch after I've verified it >> doesn't panic the system, but that will be sometime early next week >> (I can't setup a BGP connection to flood routes in and out before then..) > >Uh, from reading the PR it looks like it can be triggered by creating >a little more than 2^16 routes to the same destination, and then >deleting some of them to fall back under 2^16. I'm going to give >it a try now and I'll send you the script if that works. I'm also >making a world with "short" changed to "int" to see if it works. > >Wouldn't it be sensible to issue a warning (or panic) when increasing >the reference count reaches 0, rather than causing a later kernel >segfault? It would involve some overhead though, and I'm not sure >having 2^32 routes is currently realistic since most machines don't >even have that many bytes of RAM, but it might be true one day... >-- There isn't a reference to either IFAFREE or ifa_refcnt outside of /usr/src/sys on my tree. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 4:15:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id F40CF15057; Fri, 30 Apr 1999 04:15:22 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr ([137.194.24.253]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id NAA28431; Fri, 30 Apr 1999 13:15:18 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id C76B7D21B; Fri, 30 Apr 1999 13:15:16 +0200 (CEST) Message-ID: <19990430131516.E10021@enst.fr> Date: Fri, 30 Apr 1999 13:15:16 +0200 From: Pierre Beyssac To: adrian@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: <19990430122651.A11742@enst.fr> <19990430110819.14902.qmail@ewok.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990430110819.14902.qmail@ewok.creative.net.au>; from adrian@freebsd.org on Fri, Apr 30, 1999 at 07:08:18PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 30, 1999 at 07:08:18PM +0800, adrian@freebsd.org wrote: > There isn't a reference to either IFAFREE or ifa_refcnt outside of > /usr/src/sys on my tree. But changing its size changes the offsets of ifa_metric and ifa_rt which are after it in the structure. Also, netstat, route and ifconfig, at least, more or less depend on offsets in that structures, though I don't know exactly how (some of it has been rewritten to use ioctl() or the routing socket, I believe). -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 4:26:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 023FE14FB0 for ; Fri, 30 Apr 1999 04:26:41 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA08416; Fri, 30 Apr 1999 13:26:35 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199904301126.NAA08416@freebsd.dk> Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: <199904301104.NAA08369@freebsd.dk> from Soren Schmidt at "Apr 30, 1999 1: 4:52 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Fri, 30 Apr 1999 13:26:35 +0200 (CEST) Cc: abial@webgiro.com, green@unixhelp.org, tseidmann@SIMULTAN.CH, current@FreeBSD.ORG, shocking@prth.pgs.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Soren Schmidt wrote: > > > > As I said before, I can make some tests, but unfortunately my machine > > doesn't want to mount disks at all with the new ATA code... Please take a > > look at the message I sent about a week ago. > > Unfortunately they dont tell me much :( > > I'll have to rearrange some disks here and try to make some new installs > see if I can get the problem to appear then.. Meanwhile, could you try this patch to boot2.c and ata-disk.c and install the new bootblocks created by this and see if it works with a genuine "ad" device set. You should then use ad?? in fstab of cause. Boot directly ie like 0:ad(0,a)/kernel from the boot promt, as the /boot/loader doesn't know about "ad" devices... Another thing to try is to dump down ata-disk.c so it doesn't use either multi-sector mode or DMA, as that might confuse some disks, notably WD but also Quantum has had some marginal disks... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 4:28:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 73132158F0 for ; Fri, 30 Apr 1999 04:28:28 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 15005 invoked by uid 1008); 30 Apr 1999 11:28:26 -0000 Message-ID: <19990430112826.15003.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Pierre Beyssac Cc: freebsd-current@freebsd.org Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-reply-to: Your message of "Fri, 30 Apr 1999 13:15:16 +0200." <19990430131516.E10021@enst.fr> Date: Fri, 30 Apr 1999 19:28:26 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac writes: >On Fri, Apr 30, 1999 at 07:08:18PM +0800, adrian@freebsd.org wrote: >> There isn't a reference to either IFAFREE or ifa_refcnt outside of >> /usr/src/sys on my tree. > >But changing its size changes the offsets of ifa_metric and ifa_rt >which are after it in the structure. > >Also, netstat, route and ifconfig, at least, more or less depend >on offsets in that structures, though I don't know exactly how >(some of it has been rewritten to use ioctl() or the routing socket, I didn't say you shouldn't make world again, I was just pointing out that there shouldn't be a need to modify anything else in userland. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 4:57:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 5C86814BFA for ; Fri, 30 Apr 1999 04:57:20 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 1845318D0; Fri, 30 Apr 1999 13:57:43 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 1742449BD; Fri, 30 Apr 1999 13:57:43 +0200 (CEST) Date: Fri, 30 Apr 1999 13:57:43 +0200 (CEST) From: Andrzej Bialecki To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: <199904301104.NAA08369@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (trimmed spaghetti CC: list...) On Fri, 30 Apr 1999, Soren Schmidt wrote: > Unfortunately they dont tell me much :( > > I'll have to rearrange some disks here and try to make some new installs > see if I can get the problem to appear then.. Is there any info I can dig out for you? Some useful printfs here and there? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 5: 5:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 5CB1814BFA for ; Fri, 30 Apr 1999 05:05:07 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (postfix@myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id PAA05414; Fri, 30 Apr 1999 15:05:05 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 701D11F44; Fri, 30 Apr 1999 15:05:05 +0300 (EEST) Date: Fri, 30 Apr 1999 15:05:05 +0300 From: Vallo Kallaste To: Thomas Dean Cc: current@FreeBSD.ORG Subject: Re: libstdc++ Message-ID: <19990430150505.C3511@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <199904300250.TAA02360@ix.netcom.com> <199904300316.UAA02510@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199904300316.UAA02510@ix.netcom.com>; from Thomas Dean on Thu, Apr 29, 1999 at 08:16:35PM -0700 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 29, 1999 at 08:16:35PM -0700, Thomas Dean wrote: > c++ worked on Apr 12 and Apr 20. > > I did cvsup/make world/make kernel on: > Apr 12 > Apr 21 > Apr 28 > Apr 29 > > I believe the Apr 29 make world broke it. I used xpdf last night, > after the make world. today, it complains of 'undefined symbol > __vt_7filebuf' Also the sound broke between Apr.21 and 22. My onboard Vibra16X doesn't work with later than Apr.21 sources. It gets probed and seems to work but emits silence. Voxware doesn't work also, complains about incorrect DMA channel, BTW I know that hardware and configuration is ok. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 6: 7:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 1AFC715187 for ; Fri, 30 Apr 1999 06:07:54 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA08855 for ; Fri, 30 Apr 1999 15:07:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA15637 for ; Fri, 30 Apr 1999 15:07:52 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: int_64t support in kernel printf(), anyone ? From: Poul-Henning Kamp Date: Fri, 30 Apr 1999 15:07:52 +0200 Message-ID: <15635.925477672@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, since my last request went so well, lets try again: Adrians patch for the rlimit file in procfs revealed that the kernel printf doesn't support 64 bit integers on i386. Anyone care to try their hands on that little detail ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 7: 8:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id DE99714CB5; Fri, 30 Apr 1999 07:08:39 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id QAA06715; Fri, 30 Apr 1999 16:08:38 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 6DC00D21B; Fri, 30 Apr 1999 16:08:35 +0200 (CEST) Message-ID: <19990430160835.A5581@enst.fr> Date: Fri, 30 Apr 1999 16:08:35 +0200 From: Pierre Beyssac To: adrian@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: <19990430131516.E10021@enst.fr> <19990430112826.15003.qmail@ewok.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990430112826.15003.qmail@ewok.creative.net.au>; from adrian@FreeBSD.ORG on Fri, Apr 30, 1999 at 07:28:26PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a (-CURRENT) system with the short->int patch applied and it seems to run ok so far. Here's a script to exercise the panic, you just need to define "default" as the IP for your default gateway. On Fri, Apr 30, 1999 at 07:28:26PM +0800, adrian@FreeBSD.ORG wrote: > I didn't say you shouldn't make world again, I was just pointing out that > there shouldn't be a need to modify anything else in userland. Uh, not directly anyway, but it seems that at least "netstat" displays the reference count as a signed short. Hence it displays a negative integer if you happen to have more than 2^15 references to the route. I suppose this will have to be given a closer look, as whatever interface it uses to get the count from the kernel might have to be changed. OTOH, the good news is that the old netstat executable still works as before. #!/bin/sh default=xxx.xxx.xxx.xxx count=65537 start=167772161 # 10.0.0.1 end=`expr $start + $count` echo "Adding $count routes" i=$start while [ $i -lt $end ]; do #route add $i $default #i=`expr $i + 1` done i=$start while [ $i -lt $end ]; do # echo -n 'Press RETURN to delete one route: ' # read a route delete $i $default i=`expr $i + 1` done -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 7:19:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 664E914DFD; Fri, 30 Apr 1999 07:19:50 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id QAA07302; Fri, 30 Apr 1999 16:19:49 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 74342D21B; Fri, 30 Apr 1999 16:19:49 +0200 (CEST) Message-ID: <19990430161949.A94714@enst.fr> Date: Fri, 30 Apr 1999 16:19:49 +0200 From: Pierre Beyssac To: adrian@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: <19990430131516.E10021@enst.fr> <19990430112826.15003.qmail@ewok.creative.net.au> <19990430160835.A5581@enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990430160835.A5581@enst.fr>; from Pierre Beyssac on Fri, Apr 30, 1999 at 04:08:35PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 30, 1999 at 04:08:35PM +0200, Pierre Beyssac wrote: > and it seems to run ok so far. Here's a script to exercise the > panic, you just need to define "default" as the IP for your default > while [ $i -lt $end ]; do > #route add $i $default > #i=`expr $i + 1` Ooops, sorry, you need to uncomment the above 2 lines, too :-) -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 7:29:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A8B0814DD7 for ; Fri, 30 Apr 1999 07:29:16 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id HAA13708; Fri, 30 Apr 1999 07:29:15 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id HAA15462; Fri, 30 Apr 1999 07:29:14 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990430122651.A11742@enst.fr> Date: Fri, 30 Apr 1999 07:29:14 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Pierre Beyssac Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac wrote: > Wouldn't it be sensible to issue a warning (or panic) when > increasing the reference count reaches 0, rather than causing a > later kernel segfault? It would involve some overhead though, and > I'm not sure having 2^32 routes is currently realistic since most > machines don't even have that many bytes of RAM, but it might be > true one day... It would be pretty hard to create 2^32 routes, given that IPv4 only has 32-bit addresses. :-) Also, if you time it I suspect you'll find that it would take a geological lifetime on a fast machine to add that many routes. I think it makes more sense to increase the size of the reference count as discussed, rather than adding checks that add more complexity and overhead. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 8: 4:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id A423414CD1 for ; Fri, 30 Apr 1999 08:04:26 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id RAA09420; Fri, 30 Apr 1999 17:04:25 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id A87CED21B; Fri, 30 Apr 1999 17:04:23 +0200 (CEST) Message-ID: <19990430170423.C7295@enst.fr> Date: Fri, 30 Apr 1999 17:04:23 +0200 From: Pierre Beyssac To: John Polstra Cc: freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: <19990430122651.A11742@enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from John Polstra on Fri, Apr 30, 1999 at 07:29:14AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 30, 1999 at 07:29:14AM -0700, John Polstra wrote: > It would be pretty hard to create 2^32 routes, given that IPv4 only > has 32-bit addresses. :-) And here comes... IPv6 :-) > Also, if you time it I suspect you'll find > that it would take a geological lifetime on a fast machine to add that > many routes. Some people crack 40-bit DES in no time nowadays, so who knows what to expect... > I think it makes more sense to increase the size of the reference > count as discussed, rather than adding checks that add more complexity > and overhead. I agree. Let's count on an "int" being extended to 64 bits within the next few decades :-) -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 8:17: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 23F8B150B1 for ; Fri, 30 Apr 1999 08:16:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA09336 for ; Fri, 30 Apr 1999 17:16:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA15923 for ; Fri, 30 Apr 1999 17:16:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: DUMMYNET broken in -current ? From: Poul-Henning Kamp Date: Fri, 30 Apr 1999 17:16:57 +0200 Message-ID: <15921.925485417@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have two machines, the target being a -current SMP box. On the source machine I do ping target On the target machine, SMP kernel with IPFW+DUMMYNET: ipfw pipe config 1 delay 200ms ipfw add pipe 1 icmp from any to any and get a panic in ether_output because "dst" is 0x14. Anybody who can try this ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 8:50: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40]) by hub.freebsd.org (Postfix) with ESMTP id 3EE7D14F96 for ; Fri, 30 Apr 1999 08:49:52 -0700 (PDT) (envelope-from gjohnson@nola.srrc.usda.gov) Received: (from glenn@localhost) by symbion.srrc.usda.gov (8.9.3/8.9.3) id KAA89521; Fri, 30 Apr 1999 10:49:40 -0500 (CDT) (envelope-from glenn) From: Glenn Johnson Date: Fri, 30 Apr 1999 10:49:39 -0500 To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: IDE DMA timeouts (was: Kernel won't boot from IDE disk) Message-ID: <19990430104939.A89475@symbion.srrc.usda.gov> References: <19990429101043.A7734@symbion.srrc.usda.gov> <19990430140500.E80561@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990430140500.E80561@freebie.lemis.com>; from Greg Lehey on Fri, Apr 30, 1999 at 02:05:00PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 30, 1999 at 02:05:00PM +0930, Greg Lehey wrote: > On Thursday, 29 April 1999 at 10:10:43 -0500, Glenn Johnson wrote: > > I am doing a fresh installation. I installed the April 23, 1999 snapshot > > of STABLE and then cvsupped the CURRENT source (4.0 CURRENT). I did a > > 'make world' and that went fine. I copied the GENERIC kernel config to > > a new file and edited the copied file. I deleted whatever drivers I did > > not need. I also deleted, perhaps mistakenly, but out of habit, the > > line: > > > > "options FAILSAFE" > > I don't think this is your problem. > > > I set the flags to wdc0 and wdc1 to 'a0ffa0ff' > > This might be. > > > I then added the following: > > > > options SOFTUPDATES > > options P1003_1B > > options _KPOSIX_PRIORITY_SCHEDULING > > options _KPOSIX_VERSION=199309L > > options CPU_WT_ALLOC > > > > controller snd0 > > device sb0 at isa? port 0x220 irq 5 drq 1 > > device sbxvi0 at isa? drq 5 > > device sbmidi0 at isa? port 0x330 > > device opl0 at isa? port 0x388 > > > > Upon reboot, the system would hang after doing all of the probes. Below is some > > of the output that I got from a boot -v. I wrote this down on paper, so the > > formatting may be a little off. > > > > isa_compat: didn't get drq for wdc1 > > ... > > changing root device to wd0s1a > > > > At this point it hangs. But if I press a key on the keyboard I then get: > > wd0s1: type 0xa5, start 0, end = 3173183, size 3173184 > > wd0s1: C/H/S end 197/132/63 (1659041) != end 3173183: invalid > > start_init: trying /sbin/init > > wd0: interrupt timeout (status 50 error 0) > > wd0: wdtimeout() DMA status 4 > > > > This last two lines above are repeated 5x, then I get: > > > > wd0: Last time I say: interrupt timeout. Probably a portable PC. > > > > It is a desktop PC. I am not at the system now, so the following is from > > memory. It is an AMI BIOS, a Western Digital 1.6 GB IDE drive on the > > primary IDE and a Mitsumi 4x CD-ROM drive on the secondary IDE. > > What's your chipset? If it's an SiS 5591, I'd be interested in seeing > your complete dmesg output (preferably with a -v output). You'll also > be able to get it to work by changing the wdc0 flags to eliminate DMA. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key The IDE controller chip is an Intel PIIX3 Bus Master IDE controller. I did turn off all flags, via boot -c, then deleting the flags. That did not help. I have reinstalled 3.1 so the dmesg output below is from that. Not all of the messages from boot -v are there but I hope the relevant information is. Isn't there a way to expand the message buffer size via a kernel config option? Thanks. dmesg output from 3.1 which works: disabled, B: IRQ12, C: IRQ9, D: disabled MB0: IRQ15, MB1: found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000ffa0, size 4 ide_pci0: rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: 0000ffa2 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 3 intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 3 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000ffaa found-> vendor=0x1013, dev=0x00d0, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base ffafc000, size 14 map[1]: type 1, range 32, base fc000000, size 25 vga0: rev 0x01 on pci0.8.0 found-> vendor=0x1011, dev=0x0014, revid=0x21 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[0]: type 4, range 32, base 00007880, size 7 map[1]: type 1, range 32, base ffafbe80, size 7 de0: rev 0x21 int a irq 12 on pci0.9.0 de0: 21041 [10Mb/s] pass 2.1 de0: address 00:c0:f0:37:d0:2d found-> vendor=0x10cd, dev=0x1300, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 00007c00, size 8 map[1]: type 1, range 32, base ffafbf00, size 8 adv0: rev 0x03 int a irq 9 on pci0.10.0 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 16 Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 psm0: disabled, not probed. sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: irq maps: 0x1 0x801 0x1 0x1 sio2 at 0x3e8-0x3ef irq 11 on isa sio2: type 16550A sio3: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa intel_piix_dmainit: setting multiword DMA mode 2 wd0: wdsetmode() setting transfer mode to 22 intel_piix_status: primary master sample = 3, master recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1 at 0x170-0x177 irq 15 flags 0xa0ff on isa wdc1: unit 0 (atapi): , removable, intr, iordis acd0: drive speed 689KB/sec, 256KB cache acd0: supported read types: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked ppc: parallel port found at 0x378 ppc0: ECP SPP SPP ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip: irq 7 plip0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: imasks: bio c008c040, tty c007189a, net c007189a BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. new masks: bio c008c040, tty c007189a, net c007189a Waiting 2 seconds for SCSI devices to settle (probe2:adv0:0:2:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:adv0:0:2:0): ILLEGAL REQUEST asc:24,0 (probe2:adv0:0:2:0): Invalid field in CDB pass0 at adv0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number U800HS4 pass0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled pass1 at adv0 bus 0 target 2 lun 0 pass1: Removable Direct Access SCSI-2 device pass1: 5.000MB/s transfers (5.000MHz, offset 15) da1 at adv0 bus 0 target 2 lun 0 da1: Removable Direct Access SCSI-2 device da1: 5.000MB/s transfers (5.000MHz, offset 15) da1: 128MB (262144 512 byte sectors: 64H 32S/T 128C) da0 at adv0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number U800HS4 da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4100MB (8398600 512 byte sectors: 255H 63S/T 522C) Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to wd0s1a wd0s1: type 0xa5, start 0, end = 3173183, size 3173184 wd0s1: C/H/S end 197/132/63 (1659041) != end 3173183: invalid vinum: loaded da0s1: type 0xa5, start 0, end = 8398599, size 8398600 da0s1: C/H/S end 522/201/7 (739521) != end 8398599: invalid da0s1: type 0xa5, start 0, end = 8398599, size 8398600 da0s1: C/H/S end 522/201/7 (739521) != end 8398599: invalid da0s1: type 0xa5, start 0, end = 8398599, size 8398600 da0s1: C/H/S end 522/201/7 (739521) != end 8398599: invalid da0s1: type 0xa5, start 0, end = 8398599, size 8398600 da0s1: C/H/S end 522/201/7 (739521) != end 8398599: invalid vinum: reading configuration from /dev/da0e vinum: updating configuration from /dev/wd0e ffs_mountfs: superblock updated for soft updates Linux-ELF exec handler installed splash: image decoder found: green_saver -- Glenn Johnson Technician USDA, ARS, SRRC New Orleans, LA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 9:18:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from car (unknown [193.15.1.16]) by hub.freebsd.org (Postfix) with ESMTP id 8765E150EA for ; Fri, 30 Apr 1999 09:18:31 -0700 (PDT) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o62p36.telia.com [195.198.198.36]) by car (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id SAA01815; Fri, 30 Apr 1999 18:18:37 +0200 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.3/8.9.3) with ESMTP id RAA17882; Fri, 30 Apr 1999 17:52:43 +0200 (CEST) (envelope-from johan@granlund.nu) Date: Fri, 30 Apr 1999 17:52:43 +0200 (CEST) From: Johan Granlund To: Chuck Robey Cc: Matthew Dillon , Jim Shankland , current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, Chuck Robey wrote: > On Wed, 28 Apr 1999, Matthew Dillon wrote: > > > > > :Matthew Dillon writes: > > I can't quite figure why they stuck the word "open" in there, because it > couldn't possibly be more open than RIP. Probably beqause they stuck "OPEN" on _everything_ for a while. It drowe me nuts:) /Johan > > > > > OSPF has been around for a long time. > > But RIP is older, and was the first routing scheme. > > > > > -Matt > > Matthew Dillon > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (Solaris7). > ----------------------------+----------------------------------------------- > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 9:39:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 27F891597E for ; Fri, 30 Apr 1999 09:39:05 -0700 (PDT) (envelope-from fanf@demon.net) Received: by noc.demon.net; id RAA27787; Fri, 30 Apr 1999 17:39:03 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma027760; Fri, 30 Apr 99 17:38:55 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10dGJS-0001d0-00; Fri, 30 Apr 1999 17:38:54 +0100 To: current@freebsd.org From: Tony Finch Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-Reply-To: <19990430160835.A5581@enst.fr> References: <19990430131516.E10021@enst.fr> <19990430112826.15003.qmail@ewok.creative.net.au> <19990430112826.15003.qmail@ewok.creative.net.au> Message-Id: Date: Fri, 30 Apr 1999 17:38:54 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac wrote: >On Fri, Apr 30, 1999 at 07:28:26PM +0800, adrian@FreeBSD.ORG wrote: >> I didn't say you shouldn't make world again, I was just pointing out that >> there shouldn't be a need to modify anything else in userland. > >Uh, not directly anyway, but it seems that at least "netstat" >displays the reference count as a signed short. It actually does printf("%6d %8ld ", rt->rt_refcnt, rt->rt_use); so changing rt_refcnt to an int doesn't cause problems here, at least. Only two other things do need to be changed: src/share/doc/smm/18.net/a.t src/share/man/man9/rtentry.9 (they contain copies of the declaration) Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Arthur: "Oh, that sounds better, have you worked out the controls?" Ford: "No, we just stopped playing with them." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 9:54:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 22BB914D18 for ; Fri, 30 Apr 1999 09:53:49 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id LAA12492 for current@freebsd.org; Fri, 30 Apr 1999 11:53:30 -0500 (CDT) From: Kevin Day Message-Id: <199904301653.LAA12492@home.dragondata.com> Subject: buildworld breaks in doscmd if no X installed? To: current@freebsd.org Date: Fri, 30 Apr 1999 11:53:29 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsupped last night, and I don't have X installed. Is this a matter of "If you want to buildworld, install X"? I'm certain i've done this before though. :) Kevin cc -nostdinc -O -pipe -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/usr/src/tmp/usr/include -o doscmd AsyncIO.o ParseBuffer.o bios.o callback.o cpu.o dos.o cmos.o config.o cwd.o debug.o disktab.o doscmd.o ems.o emuint.o exe.o i386-pinsn.o int.o int10.o int13.o int14.o int16.o int17.o int1a.o int2f.o intff.o mem.o mouse.o net.o port.o setver.o signal.o timer.o trace.o trap.o tty.o xms.o -L/usr/X11R6/lib -lX11 tty.o: In function `video_setborder': tty.o(.text+0x22b): undefined reference to `XSetWindowBackground' tty.o: In function `setgc': tty.o(.text+0x2c1): undefined reference to `XChangeGC' tty.o: In function `video_update': tty.o(.text+0x4ca): undefined reference to `XDrawImageString' tty.o(.text+0x550): undefined reference to `XDrawImageString' tty.o(.text+0x64a): undefined reference to `XChangeGC' tty.o(.text+0x6d2): undefined reference to `XFillRectangle' tty.o(.text+0x77e): undefined reference to `XChangeGC' tty.o(.text+0x7bb): undefined reference to `XFillRectangle' tty.o(.text+0x7c9): undefined reference to `XFlush' tty.o: In function `debug_event': tty.o(.text+0xbf8): undefined reference to `XBell' tty.o(.text+0xc03): undefined reference to `XFlush' tty.o: In function `video_async_event': tty.o(.text+0x11c3): undefined reference to `XFlush' tty.o(.text+0x11e3): undefined reference to `XNextEvent' tty.o(.text+0x1257): undefined reference to `XFlush' tty.o(.text+0x1298): undefined reference to `XNextEvent' tty.o: In function `video_event': tty.o(.text+0x1774): undefined reference to `XLookupString' tty.o(.text+0x18f8): undefined reference to `XLookupString' tty.o: In function `tty_write': tty.o(.text+0x1f82): undefined reference to `XBell' tty.o: In function `KbdWrite': tty.o(.text+0x27da): undefined reference to `XBell' tty.o: In function `video_init': tty.o(.text+0x2b35): undefined reference to `XOpenDisplay' tty.o(.text+0x2b5c): undefined reference to `XDisplayName' tty.o(.text+0x2c39): undefined reference to `XAllocNamedColor' tty.o(.text+0x2c92): undefined reference to `XLoadQueryFont' tty.o(.text+0x2cae): undefined reference to `XLoadQueryFont' tty.o(.text+0x2d81): undefined reference to `XCreateSimpleWindow' tty.o(.text+0x2de4): undefined reference to `XCreateGC' tty.o(.text+0x2e1b): undefined reference to `XCreateGC' tty.o(.text+0x2e38): undefined reference to `XSetNormalHints' tty.o(.text+0x2e62): undefined reference to `XSelectInput' tty.o(.text+0x2e76): undefined reference to `XMapWindow' tty.o(.text+0x2e81): undefined reference to `XFlush' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 9:55:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 9824414D3D; Fri, 30 Apr 1999 09:55:13 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA27556; Fri, 30 Apr 1999 12:14:23 -0500 (EST) Date: Fri, 30 Apr 1999 12:14:21 -0500 (EST) From: Alfred Perlstein To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: DUMMYNET broken in -current ? In-Reply-To: <15921.925485417@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, Poul-Henning Kamp wrote: > > I have two machines, the target being a -current SMP box. > > On the source machine I do > ping target > > On the target machine, SMP kernel with IPFW+DUMMYNET: > > ipfw pipe config 1 delay 200ms > ipfw add pipe 1 icmp from any to any > > and get a panic in ether_output because "dst" is 0x14. > > Anybody who can try this ? perchance related: My gateway configured with BRIDGE panics when doing a sysctl -A/-a it's -current from 2 days ago with Matt Dillon's patches for NFS. ? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 9:58:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DA1E514D18 for ; Fri, 30 Apr 1999 09:58:44 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA14291; Fri, 30 Apr 1999 09:58:42 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA15748; Fri, 30 Apr 1999 09:58:41 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 30 Apr 1999 09:58:41 -0700 (PDT) Message-Id: <199904301658.JAA15748@vashon.polstra.com> To: dwhite@resnet.uoregon.edu Subject: Re: PCM In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Doug White wrote: > Yes, we know that audio is broken; it's been broken since April 20th. Well, it's worse than broken. Merely including pcm0 in the kernel config file causes instant panic on boot-up with my machine (new kernel built last night from fresh sources): BIOS basemem (639K) != RTC basemem (640K), setting to BIOS value Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc015983c stack pointer = 0x10:0xc0303f68 frame pointer = 0x10:0xc0303f70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio cam kernel: type 12 trap, code=0 Stopped at 0xc015983c: movl 0(%ecx),%ebx KGDB says there's a NULL item in sysctl_set: (kgdb) where #0 sysctl_register_oid (oidp=0x0) at ../../kern/kern_sysctl.c:79 #1 0xc01598f1 in sysctl_register_set (lsp=0xc02885b8) at ../../kern/kern_sysctl.c:127 #2 0xc0159941 in sysctl_register_all (arg=0x0) at ../../kern/kern_sysctl.c:145 #3 0xc014954a in main (framep=0xc0303fb4) at ../../kern/init_main.c:231 (kgdb) up #1 0xc01598f1 in sysctl_register_set (lsp=0xc02885b8) at ../../kern/kern_sysctl.c:127 127 sysctl_register_oid((struct sysctl_oid *) lsp->ls_items[i]); (kgdb) p *lsp $1 = {ls_length = 414, ls_items = {0xc026e3e0}} (kgdb) p i $2 = 412 (kgdb) p lsp->ls_items[411] $4 = (void *) 0xc0285bc0 (kgdb) p lsp->ls_items[412] $5 = (void *) 0x0 (kgdb) p lsp->ls_items[413] $6 = (void *) 0x4 (kgdb) up #2 0xc0159941 in sysctl_register_all (arg=0x0) at ../../kern/kern_sysctl.c:145 145 sysctl_register_set(&sysctl_set); (kgdb) up #3 0xc014954a in main (framep=0xc0303fb4) at ../../kern/init_main.c:231 231 (*((*sipp)->func))((*sipp)->udata); I can gather more information if anybody wants it. The kernel works fine if I take pcm0 out of the config file. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 10: 4:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D134F14E9E for ; Fri, 30 Apr 1999 10:04:33 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id NAA21231 for ; Fri, 30 Apr 1999 13:04:32 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Fri, 30 Apr 1999 13:04:32 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: current@freebsd.org Subject: dummynet: weird icmp behavior Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a -current install from just before egcs and am using DummyNet to experiment with network protocols. I've been applying the rules to the loopback device so as to prevent other interference. It seems to work well, except that ICMP seems not to be working for me. At one point in the past, I am certain that it did work. Here is the ruleset: sleipnir:/homea/robert# ipfw list 00001 pipe 5 ip from 127.0.0.1 to 127.0.0.1 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 65000 allow ip from any to any 65535 deny ip from any to any The pipe is configured: sleipnir:/homea/robert# ipfw pipe 5 config bw 10Mbit/s delay 150ms And ping localhost simply doesn't get any response, except once in a blue moon when a 600ms packet turns up. Tcpdump indicates that packets are going out but not being responded to: tcpdump: listening on lo0 13:02:09.201061 127.0.0.1 > 127.0.0.1: icmp: echo request 13:02:10.211104 127.0.0.1 > 127.0.0.1: icmp: echo request 13:02:11.221089 127.0.0.1 > 127.0.0.1: icmp: echo request 13:02:12.231110 127.0.0.1 > 127.0.0.1: icmp: echo request 13:02:13.241125 127.0.0.1 > 127.0.0.1: icmp: echo request When I load up tcpdump, I see: Apr 30 13:02:28 sleipnir last message repeated 19 times Apr 30 13:02:29 sleipnir /kernel: lo0: promiscuous mode enabled Apr 30 13:02:29 sleipnir /kernel: looutput: af=0 unexpected Normal UDP/TCP/etc all seem to get there fine, just not any ICMP (or at least not pings). For example, the ICMP port unreachable packet for telneting to an invalid port also disappears. Any advice here would be quite welcome :) Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 10:12:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 87EC6159DC for ; Fri, 30 Apr 1999 10:12:24 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id TAA29249; Fri, 30 Apr 1999 19:12:22 +0200 (CEST) (envelope-from des) To: Alexander Leidinger Cc: vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Sound doesn't work after recent upgrade References: <199904271430.QAA22904@wurzelausix.cs.uni-sb.de> From: Dag-Erling Smorgrav Date: 30 Apr 1999 19:12:21 +0200 In-Reply-To: Alexander Leidinger's message of "Tue, 27 Apr 1999 16:30:52 +0200 (CEST)" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger writes: > On 27 Apr, Vallo Kallaste wrote: > > Something changed between Apr.21 and Apr.27 so that my onboard > > Vibra16X get probed but I doesn't get sound. No error messages, > > nothing, different players show that all is okay and play > > "silently". Catting something to /dev/audio or /dev/dsp(W) causes > > noise for about 1 second then silence. My soundcard worked well > "Me too" for my Vibra16?-Card. But only for pcm. The in-kernel Voxware > driver works. Me three, with a Soundblaster 32. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 10:19:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 55D6014BF6 for ; Fri, 30 Apr 1999 10:19:34 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id KAA03659; Fri, 30 Apr 1999 10:17:28 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904301717.KAA03659@troutmask.apl.washington.edu> Subject: Re: PCM In-Reply-To: <199904301658.JAA15748@vashon.polstra.com> from John Polstra at "Apr 30, 1999 09:58:41 am" To: jdp@polstra.com (John Polstra) Date: Fri, 30 Apr 1999 10:17:28 -0700 (PDT) Cc: dwhite@resnet.uoregon.edu, current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article , > Doug White wrote: > > > Yes, we know that audio is broken; it's been broken since April 20th. > > Well, it's worse than broken. Merely including pcm0 in the kernel > config file causes instant panic on boot-up with my machine (new > kernel built last night from fresh sources): > It must be something that entered the tree late yesterday afternoon or an interaction between devices. FreeBSD 4.0-CURRENT #1: Thu Apr 29 15:41:29 PDT 1999 root@troutmask.apl.washington.edu:/usr/src/sys/compile/TROUTMASK Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 268435456 (262144K bytes) avail memory = 258375680 (252320K bytes) Programming 24 pins in IOAPIC #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 0xc02f9000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL00a5 [0xa5008c0e] Serial 0x00009df7 Comp ID: @@@0000 \ [0x00000000] SoundBlaster: DSP Command(0xe1) timeout. IRQ conflict ? pcm1 (SB16pnp sn 0x00009df7) at 0x640-0x64f irq 0 drq 4 flags 0x10 \ on isa CSN 2 Vendor ID: CTL0080 [0x80008c0e] Serial 0xffffffff Comp ID: @@@0000 \ [0x00000000] pcm2 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x15\ on isa -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 10:24: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 898BE14BD2 for ; Fri, 30 Apr 1999 10:24:01 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id TAA29334; Fri, 30 Apr 1999 19:23:52 +0200 (CEST) (envelope-from des) To: Alex Zepeda Cc: Jim Bryant , freebsd-current@FreeBSD.ORG Subject: Re: ep0 *UTP* References: From: Dag-Erling Smorgrav Date: 30 Apr 1999 19:23:51 +0200 In-Reply-To: Alex Zepeda's message of "Thu, 29 Apr 1999 18:41:13 -0700 (PDT)" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda writes: > On Wed, 28 Apr 1999, Jim Bryant wrote: > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting: > > > ep0 XXX: driver didn't set ifq_maxlen > > I still get that one too. Driver problem? > I'm guessing so. I wonder if this is the cause of some odd network > behavior I'm getting.. Anybody using a 3c509 and expecting it to work reliably should be taken out and shot in the back of the head. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 10:29:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 1190E14E56 for ; Fri, 30 Apr 1999 10:29:26 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id TAA29366; Fri, 30 Apr 1999 19:28:10 +0200 (CEST) (envelope-from des) To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: ep0 *UTP* References: From: Dag-Erling Smorgrav Date: 30 Apr 1999 19:28:09 +0200 In-Reply-To: Leif Neland's message of "Thu, 29 Apr 1999 00:27:45 +0200 (CEST)" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland writes: > Btw, why does boot write [*UTP*] ? > The card is working nicely with bnc. Your card is configured to use the UTP tranceiver. You probably have -link1 in your ifconfig_ep0, which forces the card to switch to the BNC tranceiver but does not actually reconfigure the card. 3Com are not particularly forthcoming with details on how do this, so if you want it to say [*BNC*] at boot time, boot with a DOS disk and run 3c5x9cfg. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 10:30:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id BADD914BD2 for ; Fri, 30 Apr 1999 10:30:42 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id NAA26434 for current@freebsd.org; Fri, 30 Apr 1999 13:30:41 -0400 (EDT) (envelope-from mi) Message-Id: <199904301730.NAA26434@misha.cisco.com> Subject: Re: ep0 *UTP* In-Reply-To: from Dag-Erling Smorgrav at "Apr 30, 1999 07:23:51 pm" To: current@freebsd.org Date: Fri, 30 Apr 1999 13:30:41 -0400 (EDT) Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav once wrote: > > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still > > > > getting: ep0 XXX: driver didn't set ifq_maxlen > > > I still get that one too. Driver problem? > > I'm guessing so. I wonder if this is the cause of some odd network > > behavior I'm getting.. > > Anybody using a 3c509 and expecting it to work reliably should be > taken out and shot in the back of the head. Is this because the cards are bad, or because the driver is bad? I had my share of problems with them, until I set them to use MTU of 900 -- no problems since, with NFS and X-session traffic flowing through the pair of this cards. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 10:46:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from fgw2.netvalue.fr (cegetel-gw.netvalue.fr [195.115.44.161]) by hub.freebsd.org (Postfix) with ESMTP id 2B54C14C9A for ; Fri, 30 Apr 1999 10:46:39 -0700 (PDT) (envelope-from erwan@netvalue.fr) Received: (from bin@localhost) by fgw2.netvalue.fr (8.9.3/8.8.8) id TAA12574 for ; Fri, 30 Apr 1999 19:46:35 +0200 (CEST) (envelope-from erwan@netvalue.fr) X-Authentication-Warning: fgw2.netvalue.fr: bin set sender to using -f Received: from (etoile.netvalue.fr [192.168.1.11]) by fgw2.netvalue.fr via smap (V2.1) id xma012570; Fri, 30 Apr 99 19:46:27 +0200 Received: from netvalue.fr ([192.168.1.100]) by etoile.netvalue.fr (Netscape Messaging Server 3.6) with ESMTP id AAA2915; Fri, 30 Apr 1999 19:46:25 +0200 Message-ID: <3729EC71.626CCC96@netvalue.fr> Date: Fri, 30 Apr 1999 19:46:25 +0200 From: Erwan Arzur Organization: NetValue S.A. X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en, fr-FR MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: freebsd-current@freebsd.org Subject: Re: ep0 *UTP* References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > Alex Zepeda writes: > > On Wed, 28 Apr 1999, Jim Bryant wrote: > > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting: > > > > ep0 XXX: driver didn't set ifq_maxlen > > > I still get that one too. Driver problem? > > I'm guessing so. I wonder if this is the cause of some odd network > > behavior I'm getting.. > > Anybody using a 3c509 and expecting it to work reliably should be > taken out and shot in the back of the head. > > DES Hi, would you please be more specific about that last sentence ? i've always heard from the FreeBSD community (newsgroups, /sys/i386/conf/GENERIC, ...) that the ep0 driver was buggy. I've got one 3C509 combo NIC in my home box, and it has been running now for 5 (which could turn into much more if was able to remember exactly when i installed it :)) under various releases of FreeBSD without experiencing any problem whatsoever. The board does not get a "real" load, as it is mostly used to connect some other computers to the internet on my home network. I'd like you to tell me why i should expect to get a bullet in the head if we ever meet :-) Which will make you the most unfriendly guy (and for me, the last) around :-) Thanks ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:10: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 21BD014DDF for ; Fri, 30 Apr 1999 11:09:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA14693; Fri, 30 Apr 1999 11:09:58 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA15921; Fri, 30 Apr 1999 11:09:58 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 30 Apr 1999 11:09:58 -0700 (PDT) Message-Id: <199904301809.LAA15921@vashon.polstra.com> To: sgk@troutmask.apl.washington.edu Subject: Re: PCM In-Reply-To: <199904301717.KAA03659@troutmask.apl.washington.edu> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904301717.KAA03659@troutmask.apl.washington.edu>, Steve Kargl wrote: > John Polstra wrote: > > > > Well, it's worse than broken. Merely including pcm0 in the kernel > > config file causes instant panic on boot-up with my machine (new > > kernel built last night from fresh sources): > > > > It must be something that entered the tree late yesterday afternoon or > an interaction between devices. [successful boot transcript omitted] On a hunch, I built the kernel again from the same sources but starting with a clean compile directory. This time it worked. So it appears that the panic I got wasn't something inherent in the kernel, but rather was a build problem. I'm certain that I typed "make depend" before building the bad kernel. So I think there must be a missing dependency somewhere. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:10:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4373114DD6 for ; Fri, 30 Apr 1999 11:10:19 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id LAA25759; Fri, 30 Apr 1999 11:09:03 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199904301809.LAA25759@GndRsh.aac.dev.com> Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-Reply-To: from John Polstra at "Apr 30, 99 07:29:14 am" To: jdp@polstra.com (John Polstra) Date: Fri, 30 Apr 1999 11:09:03 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Pierre Beyssac wrote: > > > Wouldn't it be sensible to issue a warning (or panic) when > > increasing the reference count reaches 0, rather than causing a > > later kernel segfault? It would involve some overhead though, and > > I'm not sure having 2^32 routes is currently realistic since most > > machines don't even have that many bytes of RAM, but it might be > > true one day... > > It would be pretty hard to create 2^32 routes, given that IPv4 only > has 32-bit addresses. :-) Also, if you time it I suspect you'll find > that it would take a geological lifetime on a fast machine to add that > many routes. But some of us are playing with IPv6 and it is easy to create >2^32 routes in that environment. > > I think it makes more sense to increase the size of the reference > count as discussed, rather than adding checks that add more complexity > and overhead. The checks could be added _today_ with very little testing needed, simple return an error if attempting to wrap the route ref count from 65536->0. At least then we don't blow chunks latter and end up segfaulting. This is a real bug fix. Even when the variable is increased in size to an int32_t it _should_ have an overflow test, not doing so is poor programming no matter how you cut it. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:20:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7AAEB14DD6 for ; Fri, 30 Apr 1999 11:20:21 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA14777; Fri, 30 Apr 1999 11:20:20 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA15946; Fri, 30 Apr 1999 11:20:19 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904301809.LAA25759@GndRsh.aac.dev.com> Date: Fri, 30 Apr 1999 11:20:19 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: "Rodney W. Grimes" Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rodney W. Grimes wrote: >> Pierre Beyssac wrote: >> >> > Wouldn't it be sensible to issue a warning (or panic) when >> > increasing the reference count reaches 0, rather than causing a >> > later kernel segfault? It would involve some overhead though, and >> > I'm not sure having 2^32 routes is currently realistic since most >> > machines don't even have that many bytes of RAM, but it might be >> > true one day... >> >> It would be pretty hard to create 2^32 routes, given that IPv4 only >> has 32-bit addresses. :-) Also, if you time it I suspect you'll find >> that it would take a geological lifetime on a fast machine to add that >> many routes. > > But some of us are playing with IPv6 and it is easy to create >2^32 > routes in that environment. You're being totally unrealistic. You can't create >2^32 of _anything_ on an i386 without running out of memory. Even if you could address that much memory, you or your machine would be dead from old age long before it managed to add that many routes. Let's say, _totally_ unrealistically, that you added 100 routes per second continuously. It would still take you 500 days to wrap the 32-bit counter. Regarding IPv6, it would be a surprise if that structure remained the same at all for IPv6. > The checks could be added _today_ with very little testing needed, > simple return an error if attempting to wrap the route ref count > from 65536->0. At least then we don't blow chunks latter and end > up segfaulting. > > This is a real bug fix. No it's not. It doesn't fix anything, because your 16-bit counter has wrapped around and now it's not valid any more. It doesn't matter whether you detect it and warn about it or not. The damage is already done. On the other hand, increasing the size of the variable eliminates the problem entirely. And once you do that, the overflow test is unnecessary. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:24:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id EFE1915029 for ; Fri, 30 Apr 1999 11:24:31 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA10576; Fri, 30 Apr 1999 20:24:29 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA16616; Fri, 30 Apr 1999 20:24:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-reply-to: Your message of "Fri, 30 Apr 1999 11:20:19 PDT." Date: Fri, 30 Apr 1999 20:24:28 +0200 Message-ID: <16614.925496668@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Polstra writes: >Rodney W. Grimes wrote: >>> Pierre Beyssac wrote: >>> >>> > Wouldn't it be sensible to issue a warning (or panic) when >>> > increasing the reference count reaches 0, rather than causing a >>> > later kernel segfault? It would involve some overhead though, and >>> > I'm not sure having 2^32 routes is currently realistic since most >>> > machines don't even have that many bytes of RAM, but it might be >>> > true one day... >>> >>> It would be pretty hard to create 2^32 routes, given that IPv4 only >>> has 32-bit addresses. :-) Also, if you time it I suspect you'll find >>> that it would take a geological lifetime on a fast machine to add that >>> many routes. >> >> But some of us are playing with IPv6 and it is easy to create >2^32 >> routes in that environment. > >You're being totally unrealistic. You can't create >2^32 of >_anything_ on an i386 without running out of memory. Well, John, you can, the newer ones will address 2^36 bytes of memory and even a i386 can address 2^32 bytes or 2^35 bits... But hair splitting aside, you certainly cannot create 2^32 routes without having other significant problems, and while I agree with Rod that the overflow should be checked, I think it should be done with a KASSERT() if not just with a comment. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:26:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id DD50615029 for ; Fri, 30 Apr 1999 11:26:36 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id UAA29561; Fri, 30 Apr 1999 20:26:29 +0200 (CEST) (envelope-from des) To: Erwan Arzur Cc: Dag-Erling Smorgrav , freebsd-current@freebsd.org Subject: Re: ep0 *UTP* References: <3729EC71.626CCC96@netvalue.fr> From: Dag-Erling Smorgrav Date: 30 Apr 1999 20:26:28 +0200 In-Reply-To: Erwan Arzur's message of "Fri, 30 Apr 1999 19:46:25 +0200" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erwan Arzur writes: > Dag-Erling Smorgrav wrote: > > Anybody using a 3c509 and expecting it to work reliably should be > > taken out and shot in the back of the head. > would you please be more specific about that last sentence? 3Com 3c509 NICs are unreliable. Some work, others don't. They are also known to be temperamental, in that the same card may perform well in one computer but poorly in another. Add to that the fact that the driver is buggy (search the mailing list archives!), and what you get is a hardware/software combination I cannot in good faith recommend to anyone. If you need something cheap, go for an SMC or Kingston based NE2000 compatible ISA card. You'll probably get it cheaper than the 3c509, and it will work better (and be pnp-configurable to boot). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:30:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 7669F15187 for ; Fri, 30 Apr 1999 11:30:17 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id LAA04144; Fri, 30 Apr 1999 11:28:03 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199904301828.LAA04144@troutmask.apl.washington.edu> Subject: Re: ep0 *UTP* In-Reply-To: from Dag-Erling Smorgrav at "Apr 30, 1999 07:23:51 pm" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Fri, 30 Apr 1999 11:28:03 -0700 (PDT) Cc: garbanzo@hooked.net (Alex Zepeda), jbryant@unix.tfs.net (Jim Bryant), freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > Alex Zepeda writes: > > On Wed, 28 Apr 1999, Jim Bryant wrote: > > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting: > > > > ep0 XXX: driver didn't set ifq_maxlen > > > I still get that one too. Driver problem? > > I'm guessing so. I wonder if this is the cause of some odd network > > behavior I'm getting.. > > Anybody using a 3c509 and expecting it to work reliably should be > taken out and shot in the back of the head. > I thought I sent this before, but I can't find in the GNAT database. --- if_ep.c.orig Fri Apr 30 11:22:36 1999 +++ if_ep.c Fri Apr 30 11:24:15 1999 @@ -621,6 +621,7 @@ ifp->if_start = epstart; ifp->if_ioctl = epioctl; ifp->if_watchdog = epwatchdog; + ifp->if_snd.ifq_maxlen = IFQ_MAXLEN; if (!attached) { if_attach(ifp); -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:32: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from tsolab.org (dnl.rockefeller.edu [129.85.17.127]) by hub.freebsd.org (Postfix) with ESMTP id 7DD3C1588C for ; Fri, 30 Apr 1999 11:32:01 -0700 (PDT) (envelope-from dan@dna.tsolab.org) Received: from dna.tsolab.org (dna.tsolab.org [129.85.40.125]) by tsolab.org (8.8.8/8.8.8) with ESMTP id OAA01891; Fri, 30 Apr 1999 14:36:10 -0400 (EDT) (envelope-from dan@dna.tsolab.org) Received: by dna.tsolab.org (OAA05657); Fri, 30 Apr 1999 14:30:50 -0400 From: "Dan Ts'o" Message-Id: <199904301830.OAA05657@dna.tsolab.org> Subject: Re: ep0 *UTP* To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Fri, 30 Apr 1999 14:30:48 -0400 (EDT) Cc: erwan@netvalue.fr, des@flood.ping.uio.no, freebsd-current@FreeBSD.ORG In-Reply-To: from "Dag-Erling Smorgrav" at Apr 30, 99 08:26:28 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 3Com 3c509 NICs are unreliable. Some work, others don't. They are also > known to be temperamental, in that the same card may perform well in > one computer but poorly in another. Add to that the fact that the > driver is buggy (search the mailing list archives!), and what you get > is a hardware/software combination I cannot in good faith recommend to > anyone. If you need something cheap, go for an SMC or Kingston based > NE2000 compatible ISA card. You'll probably get it cheaper than the > 3c509, and it will work better (and be pnp-configurable to boot). Hmmmm.... I've deployed well over 3 dozen of the 3c509 in its various versions, with about a third on FreeBSD systems and I haven't seem the problems you are describing. They must work at some level because I know several universities that have used them exclusively, which means probably 100's of units per site. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:36:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 47AF215466 for ; Fri, 30 Apr 1999 11:36:49 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA14877; Fri, 30 Apr 1999 11:36:49 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA15989; Fri, 30 Apr 1999 11:36:48 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <16614.925496668@critter.freebsd.dk> Date: Fri, 30 Apr 1999 11:36:48 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Poul-Henning Kamp Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message , John Polstra writes: >> >>You're being totally unrealistic. You can't create >2^32 of >>_anything_ on an i386 without running out of memory. > > Well, John, you can, the newer ones will address 2^36 bytes of memory > and even a i386 can address 2^32 bytes or 2^35 bits... > > But hair splitting aside, If we're going to split hairs, how about this: To make a reference count exceed 2^32, you need to have >2^32 different pointers pointing to it. A pointer takes 2^2 bytes on the i386. So that's 2^34 bytes of memory you'd need just to store the pointers. You'd better hope you don't get a panic on that mother! It might take quite awhile to write a 16 GByte crash dump. :-) > you certainly cannot create 2^32 routes without having other > significant problems, and while I agree with Rod that the overflow > should be checked, I think it should be done with a KASSERT() if not > just with a comment. A check would be worthwhile to detect bugs in the code (increments without matching decrements). If you want to check for bona-fide overflows, you'd best be prepared to check every counter in the system. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:38:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id F351A15187 for ; Fri, 30 Apr 1999 11:38:32 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA95768; Fri, 30 Apr 1999 11:38:28 -0700 (PDT) (envelope-from obrien) Message-ID: <19990430113828.A95710@nuxi.com> Date: Fri, 30 Apr 1999 11:38:28 -0700 From: "David O'Brien" To: Stefan Bethke , freebsd-current@FreeBSD.ORG Subject: Re: make world fails when updating from older -current Reply-To: obrien@NUXI.com References: <59687.3134425737@monster.transit-a.hanse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <59687.3134425737@monster.transit-a.hanse.de>; from Stefan Bethke on Fri, Apr 30, 1999 at 01:48:57AM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > perl5: not found > *** Error code 1 Do you have NOPERL uncommented in /etc/make.conf? If so, don't do that. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:45:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (Postfix) with ESMTP id B7EF11531A for ; Fri, 30 Apr 1999 11:45:45 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.9.3/8.9.3) with ESMTP id OAA09351; Fri, 30 Apr 1999 14:31:52 -0400 (EDT) Date: Fri, 30 Apr 1999 14:31:52 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Poul-Henning Kamp Cc: John Polstra , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-Reply-To: <16614.925496668@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, Poul-Henning Kamp wrote: > In message , John Polstra writes: > >Rodney W. Grimes wrote: > > > >You're being totally unrealistic. You can't create >2^32 of > >_anything_ on an i386 without running out of memory. > > Well, John, you can, the newer ones will address 2^36 bytes of memory > and even a i386 can address 2^32 bytes or 2^35 bits... Since when does FreeBSD only run on i386? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:46:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 37244154FC for ; Fri, 30 Apr 1999 11:46:20 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA10824; Fri, 30 Apr 1999 20:46:20 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA16713; Fri, 30 Apr 1999 20:46:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-reply-to: Your message of "Fri, 30 Apr 1999 11:36:48 PDT." Date: Fri, 30 Apr 1999 20:46:18 +0200 Message-ID: <16711.925497978@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Polstra writes: >Poul-Henning Kamp wrote: >> In message , John Polstra writes: >>> >>>You're being totally unrealistic. You can't create >2^32 of >>>_anything_ on an i386 without running out of memory. >> >> Well, John, you can, the newer ones will address 2^36 bytes of memory >> and even a i386 can address 2^32 bytes or 2^35 bits... >> >> But hair splitting aside, > >If we're going to split hairs, how about this: To make a reference >count exceed 2^32, you need to have >2^32 different pointers pointing >to it. A pointer takes 2^2 bytes on the i386. So that's 2^34 bytes >of memory you'd need just to store the pointers. > >You'd better hope you don't get a panic on that mother! It might >take quite awhile to write a 16 GByte crash dump. :-) Still only 1/4 the addressable store of P5 and upwards... :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:48:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7141F15A26 for ; Fri, 30 Apr 1999 11:48:33 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA95813; Fri, 30 Apr 1999 11:48:29 -0700 (PDT) (envelope-from obrien) Message-ID: <19990430114829.B95710@nuxi.com> Date: Fri, 30 Apr 1999 11:48:29 -0700 From: "David O'Brien" To: John Polstra , sprice@hiwaay.net Cc: current@FreeBSD.ORG Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... Reply-To: obrien@NUXI.com References: <199904300552.WAA14825@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904300552.WAA14825@vashon.polstra.com>; from John Polstra on Thu, Apr 29, 1999 at 10:52:50PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > These are good questions, and I don't know enough yet about the issues > surrounding vtable thunks to answer them. I haven't had time to really dig into this yet. Hopefully Saturday. I'm about to revert the change until I can see what the problem is and what the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug time frame. Of course I will try to upgrade us to it (well 1.2.1 which I figure will quickly follow). The EGCS maintainers are pushing to get vtable thunks working properly for 1.2. Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has posted a bug report related to them, there is an option to turn them off, and this *is* -CURRENT. I may just leave them turned on by default. Opinions? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:50:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id ADB6E15396 for ; Fri, 30 Apr 1999 11:50:52 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA14977; Fri, 30 Apr 1999 11:50:51 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA16022; Fri, 30 Apr 1999 11:50:51 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 30 Apr 1999 11:50:51 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: ben@rosengart.com Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre wrote: > On Fri, 30 Apr 1999, Poul-Henning Kamp wrote: > >> In message , John Polstra writes: >> >Rodney W. Grimes wrote: >> > >> >You're being totally unrealistic. You can't create >2^32 of >> >_anything_ on an i386 without running out of memory. >> >> Well, John, you can, the newer ones will address 2^36 bytes of memory >> and even a i386 can address 2^32 bytes or 2^35 bits... > > Since when does FreeBSD only run on i386? Sheesh. Make it a bloody long then so you'll get 64 bits on the Alpha. And then go fix all the printf format mismatches. Or, pull you head out of that dark fantasyland and realize that (a) a 32-bit counter is not a problem in any realistic sense, and (b) if it were, we'd have thousands of other equally serious problems throughout the system. I'm done with this absurd thread. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:52:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 106D21531A for ; Fri, 30 Apr 1999 11:52:47 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA14997; Fri, 30 Apr 1999 11:52:38 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA16031; Fri, 30 Apr 1999 11:52:38 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990430114829.B95710@nuxi.com> Date: Fri, 30 Apr 1999 11:52:37 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: obrien@NUXI.com Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... Cc: current@FreeBSD.ORG, sprice@hiwaay.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > I haven't had time to really dig into this yet. Hopefully Saturday. > I'm about to revert the change until I can see what the problem > is and what the upgrade issues will be. EGCS 1.2 *should* be out > in the July/Aug time frame. Of course I will try to upgrade us > to it (well 1.2.1 which I figure will quickly follow). The EGCS > maintainers are pushing to get vtable thunks working properly for > 1.2. Good. I didn't know whether it was something they were actively working on. > Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one > has posted a bug report related to them, there is an option to turn > them off, and this *is* -CURRENT. I may just leave them turned on by > default. > > Opinions? I think that's the best solution for now. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 11:58:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id C8C2315551 for ; Fri, 30 Apr 1999 11:58:45 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA00561 for ; Fri, 30 Apr 1999 14:56:52 -0400 (EDT) Date: Fri, 30 Apr 1999 14:56:51 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: Panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulp!! I just had my first panic in a year, and remembered why I didn't want to use modules too much, because when I tried to revert, the old kernel didn't like the new modules (procfs, it seems). Anyhow, I handcopied the panic message, here it is, I'd extremely appreiciate any help in getting a new kernel to boot. I finally got my old kernel up by not loading procfs.ko ... Oh, yeah, I booted this 3 times with the same message, it's not a random occurrence. Since I handcopied this, and my printing is in block letters, I don't differentiate between upper and lower case, so don't read anything into that. fatal trap 12: page fault while in kernel mode mp_lock = 0000001a; cpuid = 0; lapic.id = 01000000 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8; 0xc01c6663 stack pointer = 0x10; 0xc034ade4 frame pointer = 0x10; 0xc034ae14 code segment = base 0x0, limit 0xfffff, type 0x1b dpl 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, iopl=0 interrupt mask = net tty bio cam <- smp:xxx kernel: type 12 trap, code = 0 stopped at nexus_setup_intr+0x13:pushl 0x14(%edx) This is my first kernel since the nexus stuff was brought in, and I had to edit my config file to get it to stop issuing me errors ... here's my config, I hope this helps: machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident CHUCKRSP maxusers 64 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults: options NCPU=2 # number of CPUs options NBUS=4 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24 # number of INTs options SYSVSHM options SYSVSEM options SYSVMSG #options SCSI_NCR_SYMBIOS_COMPAT options MSGBUF_SIZE=40960 # Lets always enable the kernel debugger for SMP. options DDB # SMP shouldn't need x87 emulation, disable by default. #options MATH_EMULATE #Support for x87 emulation options GPL_MATH_EMULATE #Support for x87 emulation via options INET #InterNETworking options FFS_ROOT options FFS #Berkeley Fast Filesystem #options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem #options "CD9660" #ISO 9660 Filesystem #options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=8000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options "VM86" options "MD5" #options SCSI_NCR_SYMBIOS_COMPAT # for LEDs options SOFTUPDATES #options PERFMON #options VESA # needs VM86 defined too!! # Coda stuff: #options CODA #CODA filesystem. #pseudo-device vcoda 4 #coda minicache <-> venus comm. config kernel root on da0s1a dumps on da0s1b controller isa0 controller eisa0 controller pnp0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 controller scbus0 #device npx0 at isa? port "IO_NPX" irq 13 vector npxintr #device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr # # The Numeric Processing eXtension driver. This should be configured if # your machine has a math co-processor, unless the coprocessor is very # buggy. If it is not configured then you *must* configure math emulation # (see above). If both npx0 and emulation are configured, then only npx0 # is used (provided it works). device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 device da0 device da1 device xpt0 device cd0 #Only need one of these, the code dynamically grows # The keyboard controller; it controlls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at isa? port IO_KBD # new syscons stuff #controller atkbdc0 at isa? port IO_KBD tty #device atkbd0 at isa? tty irq 1 device vga0 at isa? port ? conflicts device sc0 at isa? device sio0 at isa? port IO_COM1 irq 4 device sio1 at isa? port IO_COM2 irq 3 controller ppc0 at isa? port? irq 7 drq 3 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? # sound device pcm0 at isa? port ? irq 15 drq 1 # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 pseudo-device loop pseudo-device vn pseudo-device ether pseudo-device snp 4 #Snoop device - to look at pty/vty/etc.. pseudo-device tun 1 pseudo-device pty 64 pseudo-device streams pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 device pass0 #CAM passthrough driver device pass1 #CAM passthrough driver device pass2 #CAM passthrough driver # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # PS/2 mouse device psm0 at atkbdc? irq 12 ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 12: 3:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id E988A1590E for ; Fri, 30 Apr 1999 12:03:53 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id OAA10956; Fri, 30 Apr 1999 14:03:42 -0500 (CDT) Date: Fri, 30 Apr 1999 14:03:42 -0500 (CDT) From: Steve Price To: obrien@NUXI.com Cc: John Polstra , current@FreeBSD.ORG Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... In-Reply-To: <19990430114829.B95710@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, David O'Brien wrote: # > These are good questions, and I don't know enough yet about the issues # > surrounding vtable thunks to answer them. # # I haven't had time to really dig into this yet. Hopefully Saturday. I'm # about to revert the change until I can see what the problem is and what # the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug # time frame. Of course I will try to upgrade us to it (well 1.2.1 which I # figure will quickly follow). The EGCS maintainers are pushing to get # vtable thunks working properly for 1.2. They seem to work now, but I'll reserve the final judgement for the experts. :-) # Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has # posted a bug report related to them, there is an option to turn them off, # and this *is* -CURRENT. I may just leave them turned on by default. # # Opinions? I'd like to see them left on. # -- # -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 12:15:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2B63714BFA for ; Fri, 30 Apr 1999 12:15:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA59569; Fri, 30 Apr 1999 20:15:56 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 30 Apr 1999 20:15:56 +0100 (BST) From: Doug Rabson To: obrien@NUXI.com Cc: John Polstra , sprice@hiwaay.net, current@freebsd.org Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... In-Reply-To: <19990430114829.B95710@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, David O'Brien wrote: > > These are good questions, and I don't know enough yet about the issues > > surrounding vtable thunks to answer them. > > I haven't had time to really dig into this yet. Hopefully Saturday. I'm > about to revert the change until I can see what the problem is and what > the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug > time frame. Of course I will try to upgrade us to it (well 1.2.1 which I > figure will quickly follow). The EGCS maintainers are pushing to get > vtable thunks working properly for 1.2. > > Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has > posted a bug report related to them, there is an option to turn them off, > and this *is* -CURRENT. I may just leave them turned on by default. > > Opinions? I would prefer to keep vtable thunks turned on. The alternative produces wretched code for multiple inheritance. Personally, I want -fnew-abi too; gcc does some disgusting things with multiple zero-sized base classes without it... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 12:18:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 48E8714CBE for ; Fri, 30 Apr 1999 12:18:14 -0700 (PDT) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id MAA26115; Fri, 30 Apr 1999 12:17:02 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199904301917.MAA26115@GndRsh.aac.dev.com> Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-Reply-To: from John Polstra at "Apr 30, 99 11:20:19 am" To: jdp@polstra.com (John Polstra) Date: Fri, 30 Apr 1999 12:17:02 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Rodney W. Grimes wrote: > >> Pierre Beyssac wrote: > >> > >> > Wouldn't it be sensible to issue a warning (or panic) when > >> > increasing the reference count reaches 0, rather than causing a > >> > later kernel segfault? It would involve some overhead though, and > >> > I'm not sure having 2^32 routes is currently realistic since most > >> > machines don't even have that many bytes of RAM, but it might be > >> > true one day... > >> > >> It would be pretty hard to create 2^32 routes, given that IPv4 only > >> has 32-bit addresses. :-) Also, if you time it I suspect you'll find > >> that it would take a geological lifetime on a fast machine to add that > >> many routes. > > > > But some of us are playing with IPv6 and it is easy to create >2^32 > > routes in that environment. > > You're being totally unrealistic. You can't create >2^32 of > _anything_ on an i386 without running out of memory. You can easily create 2^32 of lots of things on an i386, they just have to take an average of >8 bits each. And this code is _NOT_ restricted to the i386. > > Even if you could address that much memory, you or your machine would > be dead from old age long before it managed to add that many routes. > Let's say, _totally_ unrealistically, that you added 100 routes per > second continuously. It would still take you 500 days to wrap the > 32-bit counter. 100/routes a second is trivial to add, this is a straw man argument, you have no idea what this code might be running on, how fast it can add routes, etc, etc. Your using the same mentality that has created the Y2K issue. > > Regarding IPv6, it would be a surprise if that structure remained > the same at all for IPv6. Routes are still going to reference an interface, reference counts are still there. > > > The checks could be added _today_ with very little testing needed, > > simple return an error if attempting to wrap the route ref count > > from 65536->0. At least then we don't blow chunks latter and end > > up segfaulting. > > > > This is a real bug fix. > > No it's not. It doesn't fix anything, because your 16-bit counter > has wrapped around and now it's not valid any more. It doesn't > matter whether you detect it and warn about it or not. The damage > is already done. And a strange segfalut is a lot easier to track down and figure out what blew up... NOT!! > > On the other hand, increasing the size of the variable eliminates > the problem entirely. And once you do that, the overflow test is > unnecessary. No, it does not ``eliminate'' the problem, it only hides it. Plain and simple not doing bounds checking on reference counts is bad. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 12:53:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id AB3F814F81 for ; Fri, 30 Apr 1999 12:53:22 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Fri, 30 Apr 1999 20:51:16 +0100 Message-ID: From: paul@originative.co.uk To: dfr@nlsystems.com, dillon@apollo.backplane.com Cc: peter@netplex.com.au, mreimer@vpop.net, freebsd-current@freebsd.org Subject: RE: solid NFS patch #6 avail for -current - need testers files) Date: Fri, 30 Apr 1999 20:51:15 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Doug Rabson [mailto:dfr@nlsystems.com] > Sent: 21 April 1999 20:14 > To: Matthew Dillon > Cc: Peter Wemm; Matthew Reimer; freebsd-current@freebsd.org > Subject: Re: solid NFS patch #6 avail for -current - need > testers files) > > > I wonder if it would be too radical to suggest that the > release cycle for > 4.0 be *much* shorter than the 3.0 cycle. Maintaining two > branches gets > worse and worse as time goes on and it just becomes a waste > of programmer > time. If we are reasonably careful with the 4.0 tree, I think a 4.0 > release could be branched off it after 3.2 or maybe 3.3. > > It seems to me that merging a complex set of changes (such as > the VM fixes > or the new-bus work) from 4.0 to the 3.x branch would tend to > produce a > system which was less stable than the 'natural' environment for the > software which is being merged across. > I wonder if it would be too radical to suggest a third branch :-) I know of an increasing number of people who are not tracking -stable anymore because it's losing its reputation of stability. The main reason being that changes are pushed across from -current with little or no testing in -stable. I think -stable should have very conservative commit rules, only bug fixes, no feature creap. For the commercial users this is what they want, they're not interested in the newer features, they want what they already to have to work more reliably. There is however a more vocal group of people who chase features and they adhere to the rules and don't run -current to get them but increasingly their pressure has meant that -current features are hitting -stable very quickly. I think there should be three branches: 1) -current, usual rules apply, may toast your box at any moment, don't use unless you're prepared for such eventualities. 2) -beta, the place where new features migrate from -current when they seem to be working ok. Still potentially flakey but isn't expected to toast your machine. Users need to put up with problems but it should be an useable platform for a lot of people. It gets new features quickly. 3) -stable, only changes made to this branch are bug fixes, no new features added ever. I think -current has largely become -beta with the problem that when it does hit bad spots the "beta users" complain far too loudly than they really have the right to. The user base should be shifted as follows 1) -current has very few (relatively) users, only those developers who work on the OS (i.e. not ports) code. 2) The vast majority of people who run -current at the moment should really be running -beta. 3) -stable is for those who don't "track" FreeBSD. They upgrade only when a release takes place and not even at every release. These are mostly commercial users or home users who really aren't into the OS and just want a working box. In terms of workload I don't think it would have the major impact that people fear. Merges back to -stable should be *very* rare and so should not amount to any significant workload. Most of the merges we do to -stable at the moment should really be done to -beta so the workload there would be the same. Possibly even more radical than a third branch.... Change the -current list into -beta and form a new -current list that requires signing (figuratively not literally) an agreement that you accept -current may seriously hose you. Only allow people who have agreed these terms to post to the list, it would still be open for everyone to follow. This should reduce the number of whining messages on the development list from people who shouldn't really be running the development branch. Paul Richards Originative Solutions Ltd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 12:54:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D453B158F8 for ; Fri, 30 Apr 1999 12:54:09 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA39863; Fri, 30 Apr 1999 12:54:01 -0700 (PDT) (envelope-from dillon) Date: Fri, 30 Apr 1999 12:54:01 -0700 (PDT) From: Matthew Dillon Message-Id: <199904301954.MAA39863@apollo.backplane.com> To: John Polstra Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :If we're going to split hairs, how about this: To make a reference :count exceed 2^32, you need to have >2^32 different pointers pointing :to it. A pointer takes 2^2 bytes on the i386. So that's 2^34 bytes :of memory you'd need just to store the pointers. : :You'd better hope you don't get a panic on that mother! It might :take quite awhile to write a 16 GByte crash dump. :-) : :> you certainly cannot create 2^32 routes without having other :> significant problems, and while I agree with Rod that the overflow :> should be checked, I think it should be done with a KASSERT() if not :> just with a comment. : :A check would be worthwhile to detect bugs in the code (increments :without matching decrements). If you want to check for bona-fide :overflows, you'd best be prepared to check every counter in the :system. : :John :--- : John Polstra jdp@polstra.com We do check some critical reference-count fields for overflow. But it doesn't make sense to check all of them. This particular reference count has no related bugs that we know of apart from legally bumping past 65536, so it would be kinda silly to check it for an overflow. If one insisted, I suppose we could add a check if INVARIANTS is enabled but I don't see any advantage to doing so in this case. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 13:52:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id BCB6915321 for ; Fri, 30 Apr 1999 13:52:05 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id QAA11095; Fri, 30 Apr 1999 16:51:56 -0400 (EDT) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id QAA02111; Fri, 30 Apr 1999 16:51:56 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990430113828.A95710@nuxi.com> Date: Fri, 30 Apr 1999 16:51:57 -0400 (EDT) From: John Baldwin To: obrien@NUXI.com Subject: Re: make world fails when updating from older -current Cc: freebsd-current@FreeBSD.ORG, Stefan Bethke Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Apr-99 David O'Brien wrote: >> perl5: not found >> *** Error code 1 > > Do you have NOPERL uncommented in /etc/make.conf? If so, don't do that. Then why don't we take it out of make.conf for now? If we may still need the functionality, then we can leave the logic in the build mechanism, just don't tell the user about it. Then we can resurrect it in the future as necessary. At least we could add a comment to /etc/make.conf warning a user that buildworlds will fail with that option turned on. > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 14: 4:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from hugin.odin-corporation.com (fredriks-2.pr.mcs.net [205.164.50.242]) by hub.freebsd.org (Postfix) with ESMTP id 285A4155E5 for ; Fri, 30 Apr 1999 14:04:40 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by hugin.odin-corporation.com (8.9.2/8.9.1) with ESMTP id QAA01263 for ; Fri, 30 Apr 1999 16:04:39 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <372A1AE6.4E2738D4@odin-corporation.com> Date: Fri, 30 Apr 1999 16:04:39 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: current@freebsd.org Subject: default route not set up?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I must be missing something.... If you set "defaultrouter" in /etc/rc.conf to an ip address, I expected that rc.network would do a route add default ..., but instead I find that rc.network doesn't do anything with the defaultrouter variable except to pass it on to the route_default variable, which doesn't seem to be used at all. What am I missing here??? Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 14:20:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx4.dynasty.net (mail.dynasty.net [208.200.172.236]) by hub.freebsd.org (Postfix) with ESMTP id 715D31593F for ; Fri, 30 Apr 1999 14:20:12 -0700 (PDT) (envelope-from cpinckard@dynasty.net) Received: from dynasty.net ([12.14.196.220]) by mx4.dynasty.net (Netscape Messaging Server 3.52) with ESMTP id 651 for ; Fri, 30 Apr 1999 16:21:17 -0500 Message-ID: <372A1DAD.A72FD38C@dynasty.net> Date: Fri, 30 Apr 1999 16:16:29 -0500 From: Chas Pinckard X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBsd Current List Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > Rodney W. Grimes wrote: > >> Pierre Beyssac wrote: > >> > >> > Wouldn't it be sensible to issue a warning (or panic) when > >> > increasing the reference count reaches 0, rather than causing a > >> > later kernel segfault? It would involve some overhead though, and > >> > I'm not sure having 2^32 routes is currently realistic since most > >> > machines don't even have that many bytes of RAM, but it might be > >> > true one day... > >> > >> It would be pretty hard to create 2^32 routes, given that IPv4 only > >> has 32-bit addresses. :-) Also, if you time it I suspect you'll find > >> that it would take a geological lifetime on a fast machine to add that > >> many routes. > > > > But some of us are playing with IPv6 and it is easy to create >2^32 > > routes in that environment. > > You're being totally unrealistic. You can't create >2^32 of > _anything_ on an i386 without running out of memory. > > Even if you could address that much memory, you or your machine would > be dead from old age long before it managed to add that many routes. > Let's say, _totally_ unrealistically, that you added 100 routes per > second continuously. It would still take you 500 days to wrap the > 32-bit counter. > > Regarding IPv6, it would be a surprise if that structure remained > the same at all for IPv6. > > > The checks could be added _today_ with very little testing needed, > > simple return an error if attempting to wrap the route ref count > > from 65536->0. At least then we don't blow chunks latter and end > > up segfaulting. > > > > This is a real bug fix. > > No it's not. It doesn't fix anything, because your 16-bit counter > has wrapped around and now it's not valid any more. It doesn't > matter whether you detect it and warn about it or not. The damage > is already done. > > On the other hand, increasing the size of the variable eliminates > the problem entirely. And once you do that, the overflow test is > unnecessary. > > John So what about those i586/pentium machines? Do they have the 32bit counters so you can implement the higher bit counts? Chas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 14:28:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from fwgate1e.conexant.com (fwgate1e.conexant.com [198.62.8.11]) by hub.freebsd.org (Postfix) with SMTP id A6B5015597 for ; Fri, 30 Apr 1999 14:28:27 -0700 (PDT) (envelope-from housel@acm.org) Received: by fwgate1e.conexant.com; id OAA15740; Fri, 30 Apr 1999 14:28:50 -0700 Received: from npbsmtp1.nb.rss.rockwell.com(157.152.161.153) by fwgate1e.conexant.com via smap (V4.2) id xmac15728; Fri, 30 Apr 99 14:28:37 -0700 Received: from snail.nb.conexant.com ([157.152.176.120]) by npbsmtp1.nb.rockwell.com (Lotus SMTP MTA v4.6.3 (778.2 1-4-1999)) with SMTP id 88256763.0075D600; Fri, 30 Apr 1999 14:27:04 -0700 Received: from shrimp.nb.rss.rockwell.com (shrimp.nb.conexant.com [157.152.179.9]) by snail.nb.conexant.com (8.8.8/8.7.3) with ESMTP id OAA16744 for ; Fri, 30 Apr 1999 14:27:55 -0700 (PDT) Received: from housel7352a ([157.152.249.85]) by shrimp.nb.rss.rockwell.com (8.7.5/8.7.3) with SMTP id OAA06809 for ; Fri, 30 Apr 1999 14:27:53 -0700 (PDT) Message-ID: <006b01be9350$51e54800$55f9989d@nb.conexant.com> From: "Peter S. Housel" To: References: <59687.3134425737@monster.transit-a.hanse.de> <19990430113828.A95710@nuxi.com> Subject: Re: make world fails when updating from older -current Date: Fri, 30 Apr 1999 14:27:57 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > perl5: not found > > *** Error code 1 > > Do you have NOPERL uncommented in /etc/make.conf? If so, don't do that. I didn't have NOPERL set, but it happened to me the last time I rebuilt. I tried building again without the -j option to make, and all was well. Without looking into things in detail, it looks like a make dependency problem to me. -Peter- housel@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 14:46:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 67E3F15946 for ; Fri, 30 Apr 1999 14:46:55 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id RAA29258; Fri, 30 Apr 1999 17:05:44 -0500 (EST) Date: Fri, 30 Apr 1999 17:05:42 -0500 (EST) From: Alfred Perlstein To: obrien@NUXI.com Cc: John Polstra , sprice@hiwaay.net, current@FreeBSD.ORG Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... In-Reply-To: <19990430114829.B95710@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, David O'Brien wrote: > > These are good questions, and I don't know enough yet about the issues > > surrounding vtable thunks to answer them. > > I haven't had time to really dig into this yet. Hopefully Saturday. I'm > about to revert the change until I can see what the problem is and what > the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug > time frame. Of course I will try to upgrade us to it (well 1.2.1 which I > figure will quickly follow). The EGCS maintainers are pushing to get > vtable thunks working properly for 1.2. > > Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has > posted a bug report related to them, there is an option to turn them off, > and this *is* -CURRENT. I may just leave them turned on by default. > > Opinions? *gritting teeth* bring it on! :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 14:54:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from web1.aps-services.com (adsl-209-232-134-22.dsl.scrm01.pacbell.net [209.232.134.22]) by hub.freebsd.org (Postfix) with ESMTP id D615914D6C for ; Fri, 30 Apr 1999 14:54:23 -0700 (PDT) (envelope-from david@web1.aps-services.com) Received: from dave ([192.168.0.12]) by web1.aps-services.com (8.9.1/8.8.6) with SMTP id OAA15792; Fri, 30 Apr 1999 14:51:07 -0700 (PDT) Message-Id: <199904302151.OAA15792@web1.aps-services.com> From: david@aps-services.com To: paul@originative.co.uk Date: Fri, 30 Apr 1999 14:54:16 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: RE: solid NFS patch #6 avail for -current - need testers files) Cc: freebsd-current@FreeBSD.ORG In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, My name is David DeTinne and I have been suscribing to FreeBSD Stable for some time now, before 2.2.2 was released. Here is my view regarding your posting: 3.1 is probably the most unstable "stable version" ever to be sent out by Walnut Creek. I have a machine that has 2.2.6 on it, which has been abused, cold booted, etc. When I received 3.1 in the mail I installed it on three seperate machines before giving up. to many system failures. I am waiting for 3.2 to replace my 2.2.6 installation due to the machine's importance. Right now I am using 4.0 current 19990421 on my test box which works fine, go figure? Although I am not a programmer, I do care about the open source movement, and look forward to the day where I can replace all of the desktop OS's in my office with a free version of unix, linux, etc. To sum it all up is there any difference between the branches? Thank You, David DeTinne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 14:58:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 98D5B14D6C for ; Fri, 30 Apr 1999 14:58:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA01083; Fri, 30 Apr 1999 14:57:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904302157.OAA01083@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: david@aps-services.com Cc: paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Fri, 30 Apr 1999 14:54:16 PDT." <199904302151.OAA15792@web1.aps-services.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Apr 1999 14:57:03 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > To sum it all up is there any difference between the branches? Yes. We hope that people like you will help us by participating in the testing of potential releases _before_ they go out as releases, not _afterwards_. Sitting around doing nothing and then complaining after the fact doesn't help anyone, least of all yourself. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 15: 6: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id BC1BA14D6C for ; Fri, 30 Apr 1999 15:05:59 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 1711E173; Fri, 30 Apr 1999 22:05:58 +0000 (GMT) Date: Sat, 1 May 1999 02:05:58 +0400 (MSD) From: oZZ!!! To: david@aps-services.com Cc: paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: RE: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904302151.OAA15792@web1.aps-services.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999 david@aps-services.com wrote: > 3.1 is probably the most unstable "stable version" ever to be sent out > by Walnut Creek. I have a machine that has 2.2.6 on it, which has > been abused, cold booted, etc. When I received 3.1 in the mail I > installed it on three seperate machines before giving up. to many > system failures. I am waiting for 3.2 to replace my 2.2.6 installation > due to the machine's importance. use 3.1-stable from current.freebsd.org last -stable is TODAY-stable :-)) > > Right now I am using 4.0 current 19990421 on my test box which > works fine, go figure? time-to-time -current in some features is MORE stable then last -STABLE, but -current is CURRENT: its a development version. > > Although I am not a programmer, I do care about the open source > movement, and look forward to the day where I can replace all of the > desktop OS's in my office with a free version of unix, linux, etc. > > To sum it all up is there any difference between the branches? plz c handbook at http://www.freebsd.org/handbook Rgdz, Sergey A. Osokin, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 15: 9:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id E92C114E57 for ; Fri, 30 Apr 1999 15:09:35 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id RAA07422; Fri, 30 Apr 1999 17:08:49 -0500 (CDT) From: Kevin Day Message-Id: <199904302208.RAA07422@home.dragondata.com> Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904302157.OAA01083@dingo.cdrom.com> from Mike Smith at "Apr 30, 1999 2:57: 3 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 30 Apr 1999 17:08:48 -0500 (CDT) Cc: david@aps-services.com, paul@originative.co.uk, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > To sum it all up is there any difference between the branches? > > Yes. We hope that people like you will help us by participating in the > testing of potential releases _before_ they go out as releases, not > _afterwards_. > > Sitting around doing nothing and then complaining after the fact > doesn't help anyone, least of all yourself. > This isn't meant in a bad way, but let me share with you my experiences. Before 3.0 was released, I said several times "Hey, NFS got a lot worse on -CURRENT. Is anyone looking at this?" and got several replies of "Duh, this is -CURRENT. Don't whine about it. If you're trying to use this in a production environment, you're crazy." After 3.0 was released, I said "Hey, 3.0 got released, and NFS was still broken", to which I got "Why didn't you bug us about this before the release?" and/or "Why didn't you test this before release?" I understand NFS is a 'special' problem, but for those of us not in the trenches coding, I think the '3-level' system would be better. -CURRENT for those who are coding, -BETA for people like me to test things and bring up what broke, and -RELEASE for everyone else. I honestly don't know when to bring up things like that, now. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 15:15:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 802A414E57 for ; Fri, 30 Apr 1999 15:15:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01178; Fri, 30 Apr 1999 15:13:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199904302213.PAA01178@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kevin Day Cc: mike@smith.net.au (Mike Smith), david@aps-services.com, paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Fri, 30 Apr 1999 17:08:48 CDT." <199904302208.RAA07422@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Apr 1999 15:13:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I honestly don't know when to bring up things like that, now. :) For 3.2, _right_now_. What you're doing with Matt is the first stage; the next involves bringing it back to the 3.2-beta tree and testing it there. Please understand that if "you" (the community) aren't working on this, nobody else is. We don't have enough people manning the trenches because they're all sitting back in the chateau waiting for the afternoon dispatches. This doesn't work. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 15:41:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (Postfix) with ESMTP id 912A214CFA for ; Fri, 30 Apr 1999 15:41:27 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.9.3/8.9.3) with ESMTP id SAA08954; Fri, 30 Apr 1999 18:41:08 -0400 (EDT) Date: Fri, 30 Apr 1999 18:41:08 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Mike Smith Cc: david@aps-services.com, paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904302157.OAA01083@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, Mike Smith wrote: > > To sum it all up is there any difference between the branches? > > Yes. We hope that people like you will help us by participating in the > testing of potential releases _before_ they go out as releases, not > _afterwards_. > > Sitting around doing nothing and then complaining after the fact > doesn't help anyone, least of all yourself. I seem to recall that there was a lot of noise about the instability of 3 before it was released, but that it went out the door because it had been taking too long. Wasn't it Greg Lehey who said that the "beta period" seemed more like "integration testing"? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 16:52:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 56B5114EEE for ; Fri, 30 Apr 1999 16:52:58 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA41119; Fri, 30 Apr 1999 16:52:58 -0700 (PDT) (envelope-from dillon) Date: Fri, 30 Apr 1999 16:52:58 -0700 (PDT) From: Matthew Dillon Message-Id: <199904302352.QAA41119@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: -stable vs -current (was Re: solid NFS patch #6... ) References: <199904302208.RAA07422@home.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, what it comes down to is the number of developers actively developing the codebase. We had some truely unfortunate timing with people leaving and new people coming on, and pieces of the system ( such as NFS ) that simply were left dangling for a long period of time with nobody actively locating or fixing bugs. There have been too many critics and not enough people getting into the guts of the code and fixing things. ( Of course, I'm *very* biased here in my opinion :-) ). What it comes down to is that a whole lot of changes were made between 2.2.x and 3.0 without enough debugging by the authors. This kinda resulted in a partially rotting code base even through the 3.1 release, until a number of us got sick and tired of it and started actively tracking down and fixing the bugs. I expect the 3.2 release to be a really good release. It is true that -current has been, more often then not, more stable then -stable in the last two months. This is because fixes were being made to -current more quickly then they could be backported to -stable. Most of these fixes *have* been backported at this point. There are still a few that have not that are on my hot list ( and still not addressed, even with prodding ). There are also a few bug fixes that simply cannot be backported to stable without some pain ( i.e. require the complete replacement of a number of subsystems ), and pain is not in the cards with the 3.2 release so close. It is hard enough dealing with two branches of the source tree. I will personally take my Super Soaker 5000 to anyone suggesting that we have *three* !!!!. Sqirt sqirt sqirt! I am hoping that we will be able to accomplish a major synchronization after the 3.2 release. I personally believe that -current is stable enough that we should do one big-assed commit to sync -stable up to the current -current and then continue as per normal. I only wish EGCS hadn't been incorporated quite yet. At the very least, I want to sync *my* stuff up ( NFS/VM/VFS/BIO/VN/SWAPPER ). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 17:26:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 1A3AC14F14 for ; Fri, 30 Apr 1999 17:26:08 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA22360; Sat, 1 May 1999 09:56:06 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA90307; Sat, 1 May 1999 09:56:04 +0930 (CST) Date: Sat, 1 May 1999 09:56:04 +0930 From: Greg Lehey To: Brad Knowles Cc: FreeBSD current users Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... Message-ID: <19990501095604.W80561@freebie.lemis.com> References: <19990430113832.005448@lists.skynet.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990430113832.005448@lists.skynet.be>; from Brad Knowles on Fri, Apr 30, 1999 at 11:38:32AM +0200 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 30 April 1999 at 11:38:32 +0200, Brad Knowles wrote: > Folks, > > I don't want to get into any OS wars here, but I'd like to do some > low-level disk benchmarking of a Linux system using the same tool I used > for that under FreeBSD, namely Greg Lehey's "rawio" (see > ). > > This program was originally written to test his "vinum" software > mirroring/striping/RAID device driver for FreeBSD (see > ), but I believe that it would be > generally useful to do low-level disk testing under most any *nix OS. > > > Anyway, if there's anyone out there with any experience in porting > programs that do low-level disk I/O, I'd appreciate it if you could take > a look at this program and give me some pointers on what it would take to > get it to compile and run under Linux (specifically, Debian Linux with > kernel 2.2.6). > > Also, since I'm not subscribed to either of these mailing lists and I > can't keep up with the newsgroup gateway for them, I would appreciate it > if you would also e-mail me any responses you might have on this subject. I don't really understand why you ask a FreeBSD group about it; it's a Linux issue. FWIW, about the only area where you're liable to run into difficulties is in the disk label handling round line 300, which is pretty peripheral to the function: it's just there as one way of finding out the size of the partition. You'll need in-depth Linux information to even find out if Linux has an equivalent function. If you have any other problems, send me the compiler output and I'll guess at what it might be. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 17:50:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id 32D6715927 for ; Fri, 30 Apr 1999 17:50:06 -0700 (PDT) (envelope-from vanderh@ecf.toronto.edu) Received: from localhost.nowhere (ppp6527.on.bellglobal.com [206.172.208.119]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id UAA24289; Fri, 30 Apr 1999 20:52:34 -0400 (EDT) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id UAA94314; Fri, 30 Apr 1999 20:50:31 -0400 (EDT) (envelope-from tim) Date: Fri, 30 Apr 1999 20:50:30 -0400 From: Tim Vanderhoek To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: -stable vs -current (was Re: solid NFS patch #6... ) Message-ID: <19990430205030.A94231@mad> References: <199904302208.RAA07422@home.dragondata.com> <199904302352.QAA41119@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199904302352.QAA41119@apollo.backplane.com>; from Matthew Dillon on Fri, Apr 30, 1999 at 04:52:58PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 30, 1999 at 04:52:58PM -0700, Matthew Dillon wrote: > > I expect the 3.2 release to be a really good release. I seem to recall that 2.2.x wasn't even called "-stable" until 2.2.2. That .2 release is exactly where 3.x is right now... -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 18:24:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mermaid.shore.net (mermaid.shore.net [207.244.124.6]) by hub.freebsd.org (Postfix) with ESMTP id 3056E15571; Fri, 30 Apr 1999 18:24:20 -0700 (PDT) (envelope-from ejon@colltech.com) Received: from tcgbstn-s01-25.port.shore.net (colltech.com) [207.244.110.25] by mermaid.shore.net with esmtp (Exim) id 10dOVS-0002st-00; Fri, 30 Apr 1999 21:23:50 -0400 Message-ID: <372A5642.D10D39DF@colltech.com> Date: Fri, 30 Apr 1999 21:17:54 -0400 From: Eric@FreeBSD.ORG, \@FreeBSD.ORG, "Two Cats\" Jones "@FreeBSD.ORG X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Mike Smith , Eric@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ppbus causes hangs? References: <199904300241.TAA00363@dingo.cdrom.com> <199904300533.WAA30838@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, It's fixed my problem too. Many thanks. I don't know that skipping the probes and defaulting to high functionality wants to be the default, though, Matt. Best would be to figure out how to probe without mucking the chipset...is there something I can do to help, Mike? Eric Matthew Dillon wrote: > > : > :Try setting the flags on the 'ppc' device to 0x40 and _please_ report > :the results. > > Yes, this fixes the problem for me. But, it has to be the *DEFAULT*. > The flag should be used to enable the more sophisticated operation that > might freeze the machine up, not disable it. :-( > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 19:13: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 483CB15A74; Fri, 30 Apr 1999 19:12:55 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id WAA25528; Fri, 30 Apr 1999 22:12:54 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Fri, 30 Apr 1999 22:12:53 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Alfred Perlstein Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: DUMMYNET broken in -current ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suspect not related to the Matt NFS stuff, because I see this same ICMP/Dummynet problem (see my post recently, independent of PHK's post) on code from before egcs. I just noticed this morning while testing some network protocol simulations. On Fri, 30 Apr 1999, Alfred Perlstein wrote: > On Fri, 30 Apr 1999, Poul-Henning Kamp wrote: > > > > > I have two machines, the target being a -current SMP box. > > > > On the source machine I do > > ping target > > > > On the target machine, SMP kernel with IPFW+DUMMYNET: > > > > ipfw pipe config 1 delay 200ms > > ipfw add pipe 1 icmp from any to any > > > > and get a panic in ether_output because "dst" is 0x14. > > > > Anybody who can try this ? > > perchance related: > > My gateway configured with BRIDGE panics when doing a sysctl -A/-a > it's -current from 2 days ago with Matt Dillon's patches for NFS. > > ? > > -Alfred > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 19:14:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 700DA14CB3 for ; Fri, 30 Apr 1999 19:14:36 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA28701; Fri, 30 Apr 1999 19:14:33 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Steve Kargl Cc: jdp@polstra.com (John Polstra), dwhite@resnet.uoregon.edu, current@FreeBSD.ORG Subject: Re: PCM In-reply-to: Your message of "Fri, 30 Apr 1999 10:17:28 PDT." <199904301717.KAA03659@troutmask.apl.washington.edu> Date: Fri, 30 Apr 1999 19:14:33 -0700 Message-ID: <28697.925524873@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It must be something that entered the tree late yesterday afternoon or > an interaction between devices. Same here... FreeBSD 4.0-CURRENT #0: Wed Apr 28 23:21:40 PDT 1999 jkh@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY ... pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0 pcm0: interrupting at irq 5 And I'm using this right now to listen to an mp3 of a Loggins and Messina album, so it must work. :-) One thing I did notice which *is* kinda new, as of this last kernel, is this: smbus0: on bti2c0 smb0: on smbus0 bktr0: interrupting at irq 17 Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner. devclass_alloc_unit: npx0 already exists, using next available unit number I'm pretty sure that npx0 does not "already exist" in this context, leading me to believe that the message is actually being intermingled with another probe's test or something is very odd here. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 19:32:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id D718D15B2C for ; Fri, 30 Apr 1999 19:32:40 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA41012; Fri, 30 Apr 1999 22:32:43 -0400 (EDT) Date: Fri, 30 Apr 1999 22:32:43 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: -stable vs -current (was Re: solid NFS patch #6... ) In-Reply-To: <199904302352.QAA41119@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, Matthew Dillon wrote: > Well, what it comes down to is the number of developers actively > developing the codebase. We had some truely unfortunate timing with > people leaving and new people coming on, and pieces of the system ( such > as NFS ) that simply were left dangling for a long period of time with > nobody actively locating or fixing bugs. There have been too many critics > and not enough people getting into the guts of the code and fixing things. > ( Of course, I'm *very* biased here in my opinion :-) ). > > What it comes down to is that a whole lot of changes were made between > 2.2.x and 3.0 without enough debugging by the authors. This kinda resulted > in a partially rotting code base even through the 3.1 release, until a > number of us got sick and tired of it and started actively tracking down > and fixing the bugs. > > I expect the 3.2 release to be a really good release. > > It is true that -current has been, more often then not, more stable then > -stable in the last two months. This is because fixes were being made > to -current more quickly then they could be backported to -stable. Most > of these fixes *have* been backported at this point. There are still a > few that have not that are on my hot list ( and still not addressed, even > with prodding ). There are also a few bug fixes that simply cannot be > backported to stable without some pain ( i.e. require the complete > replacement of a number of subsystems ), and pain is not in the cards > with the 3.2 release so close. > > It is hard enough dealing with two branches of the source tree. I will > personally take my Super Soaker 5000 to anyone suggesting that we have > *three* !!!!. Sqirt sqirt sqirt! 5000 is out? YES!!! > > I am hoping that we will be able to accomplish a major synchronization > after the 3.2 release. I personally believe that -current is stable > enough that we should do one big-assed commit to sync -stable up to the > current -current and then continue as per normal. I only wish EGCS > hadn't been incorporated quite yet. At the very least, I want to > sync *my* stuff up ( NFS/VM/VFS/BIO/VN/SWAPPER ). I wholeheartedly agree with this idea! > > -Matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 20:51:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 15DFB14DC1 for ; Fri, 30 Apr 1999 20:51:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id UAA10741; Fri, 30 Apr 1999 20:51:06 -0700 Date: Fri, 30 Apr 1999 20:51:06 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Brad Knowles , FreeBSD current users Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... In-Reply-To: <19990501095604.W80561@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I don't really understand why you ask a FreeBSD group about it; it's a > Linux issue. FWIW, about the only area where you're liable to run > into difficulties is in the disk label handling round line 300, which > is pretty peripheral to the function: it's just there as one way of > finding out the size of the partition. You'll need in-depth Linux > information to even find out if Linux has an equivalent function. Open the device, and if (ioctl(fd, BLKGETSIZE, (caddr_t) &seeklim) < 0) { see To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 21:13:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 5F0CA14F6E for ; Fri, 30 Apr 1999 21:13:36 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA23485; Sat, 1 May 1999 13:43:34 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA91824; Sat, 1 May 1999 13:43:34 +0930 (CST) Date: Sat, 1 May 1999 13:43:33 +0930 From: Greg Lehey To: Matthew Jacob Cc: Brad Knowles , FreeBSD current users Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... Message-ID: <19990501134333.G80561@freebie.lemis.com> References: <19990501095604.W80561@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Matt Jacob on Fri, Apr 30, 1999 at 08:51:06PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 30 April 1999 at 20:51:06 -0700, Matt Jacob wrote: >> >> I don't really understand why you ask a FreeBSD group about it; it's a >> Linux issue. FWIW, about the only area where you're liable to run >> into difficulties is in the disk label handling round line 300, which >> is pretty peripheral to the function: it's just there as one way of >> finding out the size of the partition. You'll need in-depth Linux >> information to even find out if Linux has an equivalent function. > > Open the device, and > > if (ioctl(fd, BLKGETSIZE, (caddr_t) &seeklim) < 0) { > > see Thanks for the info. Looking at this, it looks as if this ioctl is for a block device. rawio uses character devices. Does that make a difference? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 21:25:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8368B14E06 for ; Fri, 30 Apr 1999 21:25:40 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id VAA11885; Fri, 30 Apr 1999 21:25:13 -0700 Date: Fri, 30 Apr 1999 21:25:12 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Brad Knowles , FreeBSD current users Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... In-Reply-To: <19990501134333.G80561@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Friday, 30 April 1999 at 20:51:06 -0700, Matt Jacob wrote: > >> > >> I don't really understand why you ask a FreeBSD group about it; it's a > >> Linux issue. FWIW, about the only area where you're liable to run > >> into difficulties is in the disk label handling round line 300, which > >> is pretty peripheral to the function: it's just there as one way of > >> finding out the size of the partition. You'll need in-depth Linux > >> information to even find out if Linux has an equivalent function. > > > > Open the device, and > > > > if (ioctl(fd, BLKGETSIZE, (caddr_t) &seeklim) < 0) { > > > > see > > Thanks for the info. Looking at this, it looks as if this ioctl is > for a block device. rawio uses character devices. Does that make a > difference? > ( everyone... wait for it .... wait for it.... wait for it... NOW! AAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRGGGGGGGGGGGGHHHHHHHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!! ) There are no raw devices in Linux. Linus is totally against them as stupid. Linus has some good points about this, but it's still an, um, interesting stance. Let me qualify that slightly- Steve Tweedie has some patches to provide this finally in the post 2.2 time frame. I helped folks hack an mmap of kernel memory to provide 'raw, direct I/O' functionality years ago (they needed to get video images off of disk, into memory, topped and tailed with UDP info and sent out to the appropriate clients- when they went from one Wide/Fast controller (it was that long ago) to two they only saw a 5% increase in speed (can you spell 'copyin/copyout' boyz && gurlz? Oh, okay,. it's get_fs_long and put_fs_long in linux...)... I just sent this to Brad, but here's a little pattern checker I use for *BSD, solaris && linux, oh yeah, and ConvexOS- much like rawio (which looks a little more clean- I also have a disk exerciser-....Yes, it's GPLd, but basically it's for whomever... I really ought to add the DVH header for IRIX/MIPS.... For raw pattern testing Linux has a special challenge since you right directly into the buffer cache. There *is* a BLKFLSBUF ioctl that can try and force a flush but this probably ought to be written to use O_FSYNC- I think that the ll_rw code might use it or an fsync could be done... -matt #ident "$Id: $ " /* * * Copyright (c) 1998, Matthew Jacob * * This software is free software; you can redistribute it and/or * modify it under the terms of the GNU Library General Public * License as published by the Free Software Foundation; version 2. * * This software is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Library General Public License for more details. * * You should have received a copy of the GNU Library General Public * License along with this software; if not, write to the Free * Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. * * The author may be reached via electronic communications at * * mjacob@feral.com * * or, via United States Postal Address * * Matthew Jacob * 1831 Castro Street * San Francisco, CA, 94131 * *************************************************************************** * * $Log: patchk.c,v $ * Revision 1.2 1999/02/02 17:23:07 mjacob * checkpoint * */ #ifdef convex #include extern int optind; extern int getopt(int, char **, const char *); #define SEEK_T off64_t #define SEEK lseek64 #define FSTAT fstat64 #define STAT_T stat64_t #else #define SEEK_T off_t #define SEEK lseek #define FSTAT fstat #define STAT_T struct stat #endif #include #include #include #include #include #include #include #include #include #include #ifdef sun #define rand lrand48 #define srand srand48 #ifdef __SVR4 #include #else #include extern int gettimeofday(struct timeval *, struct timezone *); extern void bzero(char *, int); extern int strtol(const char *, char **, int); #endif extern int optind; #endif #ifdef __linux__ #include #include #endif #ifdef convex #include #include #endif #if defined(__NetBSD__) || defined(__OpenBSD__) #include #include #endif #ifdef __FreeBSD__ #include #endif #ifdef __ultrix extern int optind; #endif #ifndef O_LARGEFILE #define O_LARGEFILE 0 #endif static int szarg(char *); int main(int a, char **v) { SEEK_T seekbase, seeklim, *buffer, wloc; int blksize; long long sb, sl; STAT_T st; int fd, i, error, create, nowrite; seekbase = (SEEK_T) 0; nowrite = 0; srand((int)(time((time_t *) 0)/getpid())); if (a != 4) { usage: fprintf(stderr, "Usage: %s raw-disk xfersize {c[reate]|u[se]|v[alidate]}\n", *v); return (1); } blksize = szarg(v[2]); buffer = (SEEK_T *) calloc((size_t) blksize, sizeof (SEEK_T)); if (buffer == NULL) { perror("malloc"); return (1); } if (*v[3] == 'c') { create = 1; } else if (*v[3] == 'u') { create = 0; } else if (*v[3] == 'v') { create = 0; nowrite = 1; } else { goto usage; } fd = open(v[1], nowrite? O_RDONLY : O_RDWR, 0666); if (fd < 0) { perror(v[2]); exit(1); } if (FSTAT(fd, &st) < 0) { perror("fstat"); exit(1); } if (S_ISCHR(st.st_mode)) { #if defined(__NetBSD__) || defined(__FreeBSD__) || defined(__OpenBSD__) int part; struct disklabel x; if (ioctl(fd, DIOCGDINFO, (caddr_t) &x) < 0) { perror("DIOCGDINFO"); exit(1); } seekbase = 8192; part = v[1][strlen(v[1]) - 1] - 'a'; seeklim = ((SEEK_T) x.d_partitions[part].p_size) * (SEEK_T) DEV_BSIZE; #elif defined(sun) struct dk_allmap x; int part; if (blksize < DEV_BSIZE) { fprintf(stderr, "%s: block size must be at least %d bytes on " "raw device\n", *v, DEV_BSIZE); exit(1); } #if defined(__svr4__) part = v[1][strlen(v[1]) - 1] - '0'; #else part = v[1][strlen(v[1]) - 1] - 'a'; #endif if (ioctl(fd, DKIOCGAPART, (caddr_t) &x) < 0) { perror("DKIOCGAPART"); exit(1); } seekbase = 8192; seeklim = ((SEEK_T) x.dka_map[part].dkl_nblk) * (SEEK_T) DEV_BSIZE; #elif defined(convex) struct topology top; seeklim = 0; if (ioctl(fd, SIOC_READ_TOPOLOGY, (caddr_t)&top) >= 0) { seeklim = (SEEK_T) top.partition[st.st_rdev & 0xf].size * (SEEK_T) DEV_BSIZE; } #else seeklim = (SEEK_T) 1; #endif } else { #ifdef linux if (ioctl(fd, BLKGETSIZE, (caddr_t) &seeklim) < 0) { perror("BLKGETSIZE"); exit(1); } seeklim <<= 9; #else fprintf(stderr, "%s: is not a raw device\n", v[1]); return (1); #endif } if (seekbase < blksize) seekbase = blksize; /* * Truncate to lower block boundary. */ seeklim &= ~(blksize-1); /* * An back off one. */ seeklim -= blksize; if (seeklim < (SEEK_T) 0) { printf("%s too big for lseek(2) call\n", v[1]); exit(1); } if (seeklim < (seekbase+blksize)) { fprintf(stderr, "%s: botch, seeklim (%ld) < seekbase + blksize (%ld)\n", *v, seeklim, seekbase + blksize); exit(1); } sb = (long long) seekbase; sl = (long long) seeklim; fprintf(stdout, "%s: Seek base %lx%08lx Seek lim %lx%08lx blocksize %d\n", v[1], (long) (sb >> 32LL), (long) (sb & 0xFFFFFFFF), (long) (sl >> 32LL), (long) (sl & 0xFFFFFFFF), blksize); wloc = SEEK(fd, (SEEK_T) seekbase, 0); if (wloc < (SEEK_T) 0) { perror("seek"); exit (1); } if (create) { fprintf(stdout, "Creating Patterns..."); fflush(stdout); for (wloc = seekbase; wloc < seeklim; wloc += blksize) { sb = (long long) wloc; for (i = 0; i < (blksize/sizeof (SEEK_T)); i++) { buffer[i] = wloc; } if ((i = write(fd, (char *)buffer, (int) blksize)) != blksize) { if (errno) perror("write"); fprintf(stderr, "write returned %d at offset 0x%lx0x%08lx\n", i, (long) (sb >> 32LL), (long) (sb & 0xFFFFFFFF)); exit (1); } } wloc = SEEK(fd, (SEEK_T) seekbase, 0); if (wloc < (SEEK_T) 0) { perror("seek"); exit (1); } } fprintf(stdout, "Checking Patterns..."); fflush(stdout); for (wloc = seekbase; wloc < seeklim; wloc += blksize) { sb = (long long) wloc; if ((i = read(fd, (char *)buffer, blksize)) != blksize) { if (errno) perror("read"); fprintf(stderr, "read returned %d at offset 0x%lx%08lx\n", i, (long) (sb >> 32LL), (long) (sb & 0xFFFFFFFF)); exit (1); } for (error = i = 0; i < (blksize/sizeof (SEEK_T)); i++) { if (buffer[i] != wloc) { sb = wloc; sl = (long long) buffer[i]; error++; fprintf(stderr, "compare error at block loc 0x%lx%08lx offset " "%d got %lx%08lx\n", (long) (sb >> 32LL), (long) (sb & 0xFFFFFFFF), i, (long) (sl >> 32LL), (long) (sl & 0xFFFFFFFF)); } } if (error) exit (1); } fprintf(stdout, "Randomly Checking Patterns\n"); while (1) { SEEK_T sloc; wloc = rand(); wloc &= ~(((SEEK_T)blksize) - 1); if (wloc < seekbase) continue; if (wloc >= (seeklim-(SEEK_T) blksize)) continue; sloc = SEEK(fd, wloc, 0); if (sloc < (SEEK_T) 0) { perror("seek"); exit (1); } if (sloc != wloc) { if (errno) perror("seek2"); fprintf(stderr, "wanted to seek to %lx and got to %lx instead\n", wloc, sloc); continue; } sb = (long long) wloc; if (!nowrite && (rand() & 1)) { for (i = 0; i < (blksize/sizeof (SEEK_T)); i++) { buffer[i] = wloc; } if ((i = write(fd, (char *)buffer, blksize)) != blksize) { fprintf(stderr, "\n"); if (errno) perror("write"); fprintf(stderr, "write returned %d at offset 0x%lx%08lx\n", i, (long) (sb >> 32LL), (long) (sb & 0xFFFFFFFF)); printf("wloc %lx sloc %lx\n", wloc, sloc); exit (1); } } else { if ((i = read(fd, (char *)buffer, blksize)) != blksize) { fprintf(stderr, "\n"); if (errno) perror("read"); fprintf(stderr, "read returned %d at offset 0x%lx%08lx\n", i, (long) (sb >> 32LL), (long) (sb & 0xFFFFFFFF)); printf("wloc %lx sloc %lx\n", wloc, sloc); exit (1); } for (error = i = 0; i < (blksize/sizeof (SEEK_T)); i++) { if (buffer[i] != wloc) { sb = wloc; sl = (long long) buffer[i]; if (error++ == 0) fprintf(stderr, "\n"); fprintf(stderr, "compare error at buffer offset %d should " "be 0x%lx%08lx got 0x%lx%08lx\n", i, (long) (sb >> 32LL), (long) (sb & 0xFFFFFFFF), (long) (sl >> 32LL), (long) (sl & 0xFFFFFFFF)); } } if (error) exit (1); } } } static int szarg(char *n) { register int shift = 0; register char *q = n; while (*q != (char) 0) q++; q--; if (*q == 'b' || *q == 'B') q--; if (*q == 'k' || *q == 'K') { shift = 10; *q = 0; } else if (*q == 'm' || *q == 'M') { shift = 20; *q = 0; } else if (*q == 'g' || *q == 'G') { shift = 30; *q = 0; } return ((SEEK_T) strtol((const char *)n, (char **) NULL, 0) << shift); } /* * --------------------------------------------------------------------------- * Local variables: * c-indent-level: 4 * c-brace-imaginary-offset: 0 * c-brace-offset: -4 * c-argdecl-indent: 4 * c-label-offset: -4 * c-continued-statement-offset: 4 * c-continued-brace-offset: 0 * End: */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 21:35:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id CF6A814F63 for ; Fri, 30 Apr 1999 21:35:19 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id VAA66240; Fri, 30 Apr 1999 21:30:44 -0700 (PDT) Date: Fri, 30 Apr 1999 21:30:43 -0700 (PDT) From: Julian Elischer To: Greg Lehey Cc: Matthew Jacob , Brad Knowles , FreeBSD current users Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... In-Reply-To: <19990501134333.G80561@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Linux had no char device last I looked.. everything is always buffered this may have changed, but .... On Sat, 1 May 1999, Greg Lehey wrote: > On Friday, 30 April 1999 at 20:51:06 -0700, Matt Jacob wrote: > >> > >> I don't really understand why you ask a FreeBSD group about it; it's a > >> Linux issue. FWIW, about the only area where you're liable to run > >> into difficulties is in the disk label handling round line 300, which > >> is pretty peripheral to the function: it's just there as one way of > >> finding out the size of the partition. You'll need in-depth Linux > >> information to even find out if Linux has an equivalent function. > > > > Open the device, and > > > > if (ioctl(fd, BLKGETSIZE, (caddr_t) &seeklim) < 0) { > > > > see > > Thanks for the info. Looking at this, it looks as if this ioctl is > for a block device. rawio uses character devices. Does that make a > difference? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 22:38:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from router.gagarinclub.ru (unknown [194.67.182.2]) by hub.freebsd.org (Postfix) with ESMTP id 676B5159F5 for ; Fri, 30 Apr 1999 22:38:11 -0700 (PDT) (envelope-from firma@gagarinclub.ru) Received: from rem.gagarinclub.ru (rem.gagarinclub.ru [194.67.182.5]) by router.gagarinclub.ru (8.9.3/8.9.3) with ESMTP id JAA04703 for ; Sat, 1 May 1999 09:38:09 +0400 (MSD) Date: Sat, 1 May 1999 09:40:37 +0400 (MSD) From: REM Reply-To: REM To: current@freebsd.org Subject: Error while make world (cvsuped 990501) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My system was suped at 990501. -------------------------------------------------------------- >>> elf make world started on Sat May 1 09:36:25 MSD 1999 -------------------------------------------------------------- -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp -------------------------------------------------------------- >>> Making make -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp/usr/bin /usr/obj/usr/src/tmp/make ( cd /usr/src/usr.bin/make; MAKEOBJDIRPREFIX=""; unset MAKEOBJDIRPREFIX; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/libexec MAKEOBJDIR=/usr/obj/usr/src/tmp/make make DESTDIR=/usr/obj/usr/src/tmp -I/usr/src/share/mk -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin BISON_SIMPLE=/usr/obj/usr/src/t! mp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/libexec MAKEOBJDIR=/usr/obj/usr/src/tmp/make make DESTDIR=/usr/obj/usr/src/tmp -I/usr/src/share/mk -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED install; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tm! p/usr/lib:/usr/obj/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/libexec MAKEOBJDIR=/usr/obj/usr/src/tmp/make make DESTDIR=/usr/obj/usr/src/tmp -I/usr/src/share/mk -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED clean ) cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/make/arch.c cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 30 22:55:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id B0A9F14FD7 for ; Fri, 30 Apr 1999 22:55:27 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA23833; Sat, 1 May 1999 15:25:25 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA94582; Sat, 1 May 1999 15:25:24 +0930 (CST) Date: Sat, 1 May 1999 15:25:23 +0930 From: Greg Lehey To: Matthew Jacob Cc: Brad Knowles , FreeBSD current users Subject: Linux char devices (was: Porting Greg Lehey's rawio.c from FreeBSD to Linux...) Message-ID: <19990501152523.H80561@freebie.lemis.com> References: <19990501134333.G80561@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Matt Jacob on Fri, Apr 30, 1999 at 09:25:12PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 30 April 1999 at 21:25:12 -0700, Matt Jacob wrote: > >> On Friday, 30 April 1999 at 20:51:06 -0700, Matt Jacob wrote: >>>> >>>> I don't really understand why you ask a FreeBSD group about it; it's a >>>> Linux issue. FWIW, about the only area where you're liable to run >>>> into difficulties is in the disk label handling round line 300, which >>>> is pretty peripheral to the function: it's just there as one way of >>>> finding out the size of the partition. You'll need in-depth Linux >>>> information to even find out if Linux has an equivalent function. >>> >>> Open the device, and >>> >>> if (ioctl(fd, BLKGETSIZE, (caddr_t) &seeklim) < 0) { >>> >>> see >> >> Thanks for the info. Looking at this, it looks as if this ioctl is >> for a block device. rawio uses character devices. Does that make a >> difference? > > > > There are no raw devices in Linux. Linus is totally against them as > stupid. Linus has some good points about this, but it's still an, um, > interesting stance. It also makes it impossible for rawio to run accurately. rawio measures device throughput, not system throughput. Cache the data and you completely lose this ability (hey! Under Vinum, an array of four floppies has a random read throughput of 50 MB/s!). Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 0: 8:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id AA9FF14E38 for ; Sat, 1 May 1999 00:08:51 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA96409; Sat, 1 May 1999 08:09:03 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 08:09:03 +0100 (BST) From: Doug Rabson To: Kevin Day Cc: Mike Smith , david@aps-services.com, paul@originative.co.uk, freebsd-current@freebsd.org Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904302208.RAA07422@home.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, Kevin Day wrote: > > > > > > To sum it all up is there any difference between the branches? > > > > Yes. We hope that people like you will help us by participating in the > > testing of potential releases _before_ they go out as releases, not > > _afterwards_. > > > > Sitting around doing nothing and then complaining after the fact > > doesn't help anyone, least of all yourself. > > > > This isn't meant in a bad way, but let me share with you my experiences. > > Before 3.0 was released, I said several times "Hey, NFS got a lot worse on > -CURRENT. Is anyone looking at this?" and got several replies of "Duh, this > is -CURRENT. Don't whine about it. If you're trying to use this in a > production environment, you're crazy." > > After 3.0 was released, I said "Hey, 3.0 got released, and NFS was still > broken", to which I got "Why didn't you bug us about this before the > release?" and/or "Why didn't you test this before release?" > > I understand NFS is a 'special' problem, but for those of us not in the > trenches coding, I think the '3-level' system would be better. -CURRENT for > those who are coding, -BETA for people like me to test things and bring up > what broke, and -RELEASE for everyone else. > > I honestly don't know when to bring up things like that, now. :) I don't think a 3 branch system is workable for the simple reason that CVS doesn't handle branches at all well. One possible alternative would be the same structure that we have today with the addition of a 'last known good' tag which is on the head branch and slides forward when a feature is deemed 'good'. People who want features but don't want to fix them can use this tag. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 0:12: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from opi.flirtbox.ch (unknown [62.48.0.50]) by hub.freebsd.org (Postfix) with SMTP id CBD4514E38 for ; Sat, 1 May 1999 00:12:05 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 33963 invoked from network); 1 May 1999 07:12:04 -0000 Received: from unknown (HELO pipeline.ch) (195.134.128.182) by opi.flirtbox.ch with SMTP; 1 May 1999 07:12:04 -0000 Message-ID: <372AA9C1.4ABC9C1B@pipeline.ch> Date: Sat, 01 May 1999 09:14:09 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.07 [en] (Win98; U) MIME-Version: 1.0 To: mjacob@feral.com Cc: Greg Lehey , Brad Knowles , FreeBSD current users Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > For raw pattern testing Linux has a special challenge since you right > directly into the buffer cache. There *is* a BLKFLSBUF ioctl that can try > and force a flush but this probably ought to be written to use O_FSYNC- I > think that the ll_rw code might use it or an fsync could be done... Linux' fsync() works only on directories, not on files. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 0:17:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4883014E38 for ; Sat, 1 May 1999 00:17:07 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA96423; Sat, 1 May 1999 08:17:25 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 08:17:25 +0100 (BST) From: Doug Rabson To: "Jordan K. Hubbard" Cc: Steve Kargl , John Polstra , dwhite@resnet.uoregon.edu, current@freebsd.org Subject: Re: PCM In-Reply-To: <28697.925524873@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, Jordan K. Hubbard wrote: > > It must be something that entered the tree late yesterday afternoon or > > an interaction between devices. > > Same here... > > FreeBSD 4.0-CURRENT #0: Wed Apr 28 23:21:40 PDT 1999 > jkh@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY > ... > pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0 > pcm0: interrupting at irq 5 > > And I'm using this right now to listen to an mp3 of a Loggins and > Messina album, so it must work. :-) > > One thing I did notice which *is* kinda new, as of this last kernel, > is this: > > smbus0: on bti2c0 > smb0: on smbus0 > bktr0: interrupting at irq 17 > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner. > devclass_alloc_unit: npx0 already exists, using next available unit number > > I'm pretty sure that npx0 does not "already exist" in this context, > leading me to believe that the message is actually being intermingled > with another probe's test or something is very odd here. :) Do you have 'npx0 at isa?' in your config file by any chance? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 0:25:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 2118C14E38 for ; Sat, 1 May 1999 00:25:43 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id AAA25403; Sat, 1 May 1999 00:21:48 -0700 (PDT) Message-Id: <199905010721.AAA25403@implode.root.com> To: Andre Oppermann Cc: mjacob@feral.com, Greg Lehey , Brad Knowles , FreeBSD current users Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... In-reply-to: Your message of "Sat, 01 May 1999 09:14:09 +0200." <372AA9C1.4ABC9C1B@pipeline.ch> From: David Greenman Reply-To: dg@root.com Date: Sat, 01 May 1999 00:21:48 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Matthew Jacob wrote: >> For raw pattern testing Linux has a special challenge since you right >> directly into the buffer cache. There *is* a BLKFLSBUF ioctl that can try >> and force a flush but this probably ought to be written to use O_FSYNC- I >> think that the ll_rw code might use it or an fsync could be done... > >Linux' fsync() works only on directories, not on files. Huh? That doesn't make any sense. The "f" in fsync() stands for "file". -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 1:14:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from psycho.h4x0rz.za.org (psycho.h4x0rz.za.org [206.49.228.8]) by hub.freebsd.org (Postfix) with ESMTP id 2DF1014F56 for ; Sat, 1 May 1999 01:14:11 -0700 (PDT) (envelope-from andrew@psycho.h4x0rz.za.org) Received: from localhost (andrew@localhost) by psycho.h4x0rz.za.org (8.9.3/8.9.2) with ESMTP id KAA19671; Sat, 1 May 1999 10:15:29 +0200 (SAST) (envelope-from andrew@psycho.h4x0rz.za.org) Date: Sat, 1 May 1999 10:15:29 +0200 (SAST) From: vortexia To: Doug Rabson Cc: current@FreeBSD.ORG Subject: Re: PCM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heh, the panic problem might be solved, but Ive just cvsupped with the latest 4.0-CURRENT and the problems with pcm are definatly not over, Im getting very jerky sound, its repeating bits of it over and over... and I get messages like this while trying to play mp3s with mpg123: May 1 10:12:16 main /kernel: timeout flushing dbuf_out, chan 3 cnt 0xfff994bc flags 0x00000141 Cheers Andrew On Sat, 1 May 1999, Doug Rabson wrote: > On Fri, 30 Apr 1999, Jordan K. Hubbard wrote: > > > > It must be something that entered the tree late yesterday afternoon or > > > an interaction between devices. > > > > Same here... > > > > FreeBSD 4.0-CURRENT #0: Wed Apr 28 23:21:40 PDT 1999 > > jkh@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY > > ... > > pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0 > > pcm0: interrupting at irq 5 > > > > And I'm using this right now to listen to an mp3 of a Loggins and > > Messina album, so it must work. :-) > > > > One thing I did notice which *is* kinda new, as of this last kernel, > > is this: > > > > smbus0: on bti2c0 > > smb0: on smbus0 > > bktr0: interrupting at irq 17 > > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner. > > devclass_alloc_unit: npx0 already exists, using next available unit number > > > > I'm pretty sure that npx0 does not "already exist" in this context, > > leading me to believe that the message is actually being intermingled > > with another probe's test or something is very odd here. :) > > Do you have 'npx0 at isa?' in your config file by any chance? > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 1:17:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from router.gagarinclub.ru (unknown [194.67.182.2]) by hub.freebsd.org (Postfix) with ESMTP id DFF2114F56 for ; Sat, 1 May 1999 01:17:49 -0700 (PDT) (envelope-from firma@gagarinclub.ru) Received: from rem.gagarinclub.ru (rem.gagarinclub.ru [194.67.182.5]) by router.gagarinclub.ru (8.9.3/8.9.3) with ESMTP id MAA05206 for ; Sat, 1 May 1999 12:17:48 +0400 (MSD) Date: Sat, 1 May 1999 12:20:17 +0400 (MSD) From: REM Reply-To: REM To: current@freebsd.org Subject: Error while make world (cvsuped 990501). Sorry! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My system was suped at 990501. -------------------------------------------------------------- >>> elf make world started on Sat May 1 09:36:25 MSD 1999 -------------------------------------------------------------- [Skip] cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Sorry! My BIOS settings was incorrect! Make world is OK! REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 1:22:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id AAD3715A1B for ; Sat, 1 May 1999 01:22:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 3C75F1F58; Sat, 1 May 1999 16:22:25 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: vortexia Cc: Doug Rabson , current@FreeBSD.ORG Subject: Re: PCM In-reply-to: Your message of "Sat, 01 May 1999 10:15:29 +0200." Date: Sat, 01 May 1999 16:22:25 +0800 From: Peter Wemm Message-Id: <19990501082228.3C75F1F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG vortexia wrote: > Heh, the panic problem might be solved, but Ive just cvsupped with the > latest 4.0-CURRENT and the problems with pcm are definatly not over, Im > getting very jerky sound, its repeating bits of it over and over... and I > get messages like this while trying to play mp3s with mpg123: > > May 1 10:12:16 main /kernel: timeout flushing dbuf_out, chan 3 cnt > 0xfff994bc flags 0x00000141 > > Cheers > Andrew I've run two systems with PCM right since the first newbus commit, and it's worked for me. Admittedly I don't use it all that often, but it's never paniced and I don't recall getting any more sound problems than usual. I checked that the isa_dma.c code is an exact split of the dma code that used to be in the old isa.c, there are zero changes to the isa dma code. > On Sat, 1 May 1999, Doug Rabson wrote: > > > On Fri, 30 Apr 1999, Jordan K. Hubbard wrote: > > > > > > It must be something that entered the tree late yesterday afternoon or > > > > an interaction between devices. > > > > > > Same here... > > > > > > FreeBSD 4.0-CURRENT #0: Wed Apr 28 23:21:40 PDT 1999 > > > jkh@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY > > > ... > > > pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0 > > > pcm0: interrupting at irq 5 > > > > > > And I'm using this right now to listen to an mp3 of a Loggins and > > > Messina album, so it must work. :-) > > > > > > One thing I did notice which *is* kinda new, as of this last kernel, > > > is this: > > > > > > smbus0: on bti2c0 > > > smb0: on smbus0 > > > bktr0: interrupting at irq 17 > > > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner. > > > devclass_alloc_unit: npx0 already exists, using next available unit numbe r > > > > > > I'm pretty sure that npx0 does not "already exist" in this context, > > > leading me to believe that the message is actually being intermingled > > > with another probe's test or something is very odd here. :) > > > > Do you have 'npx0 at isa?' in your config file by any chance? > > > > -- > > Doug Rabson Mail: dfr@nlsystems.com > > Nonlinear Systems Ltd. Phone: +44 181 442 9037 Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 1:31:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CDC5014C36 for ; Sat, 1 May 1999 01:31:31 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA96996; Sat, 1 May 1999 01:31:23 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Doug Rabson Cc: Steve Kargl , John Polstra , dwhite@resnet.uoregon.edu, current@freebsd.org Subject: Re: PCM In-reply-to: Your message of "Sat, 01 May 1999 08:17:25 BST." Date: Sat, 01 May 1999 01:31:23 -0700 Message-ID: <96993.925547483@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do you have 'npx0 at isa?' in your config file by any chance? Whoops! That's the problem; I failed to see that change in GENERIC despite having scrolled past it more than several times. My face is red. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 1:49:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from psycho.h4x0rz.za.org (psycho.h4x0rz.za.org [206.49.228.8]) by hub.freebsd.org (Postfix) with ESMTP id 4EB4914D4E for ; Sat, 1 May 1999 01:49:10 -0700 (PDT) (envelope-from andrew@psycho.h4x0rz.za.org) Received: from localhost (andrew@localhost) by psycho.h4x0rz.za.org (8.9.3/8.9.2) with ESMTP id KAA19717; Sat, 1 May 1999 10:50:09 +0200 (SAST) (envelope-from andrew@psycho.h4x0rz.za.org) Date: Sat, 1 May 1999 10:50:09 +0200 (SAST) From: vortexia To: Peter Wemm Cc: Doug Rabson , current@FreeBSD.ORG Subject: Re: PCM In-Reply-To: <19990501082228.3C75F1F58@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hrmmm strange, I booted this system with a 3.0-STABLE drive just now and I have no problems with the sound, so Im not sure what it is, but its definatly not hardware. Cheers Andrew On Sat, 1 May 1999, Peter Wemm wrote: > vortexia wrote: > > Heh, the panic problem might be solved, but Ive just cvsupped with the > > latest 4.0-CURRENT and the problems with pcm are definatly not over, Im > > getting very jerky sound, its repeating bits of it over and over... and I > > get messages like this while trying to play mp3s with mpg123: > > > > May 1 10:12:16 main /kernel: timeout flushing dbuf_out, chan 3 cnt > > 0xfff994bc flags 0x00000141 > > > > Cheers > > Andrew > > I've run two systems with PCM right since the first newbus commit, and it's > worked for me. Admittedly I don't use it all that often, but it's never > paniced and I don't recall getting any more sound problems than usual. > > I checked that the isa_dma.c code is an exact split of the dma code that > used to be in the old isa.c, there are zero changes to the isa dma code. > > > > On Sat, 1 May 1999, Doug Rabson wrote: > > > > > On Fri, 30 Apr 1999, Jordan K. Hubbard wrote: > > > > > > > > It must be something that entered the tree late yesterday afternoon or > > > > > an interaction between devices. > > > > > > > > Same here... > > > > > > > > FreeBSD 4.0-CURRENT #0: Wed Apr 28 23:21:40 PDT 1999 > > > > jkh@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY > > > > ... > > > > pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0 > > > > pcm0: interrupting at irq 5 > > > > > > > > And I'm using this right now to listen to an mp3 of a Loggins and > > > > Messina album, so it must work. :-) > > > > > > > > One thing I did notice which *is* kinda new, as of this last kernel, > > > > is this: > > > > > > > > smbus0: on bti2c0 > > > > smb0: on smbus0 > > > > bktr0: interrupting at irq 17 > > > > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner. > > > > devclass_alloc_unit: npx0 already exists, using next available unit numbe > r > > > > > > > > I'm pretty sure that npx0 does not "already exist" in this context, > > > > leading me to believe that the message is actually being intermingled > > > > with another probe's test or something is very odd here. :) > > > > > > Do you have 'npx0 at isa?' in your config file by any chance? > > > > > > -- > > > Doug Rabson Mail: dfr@nlsystems.com > > > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > Cheers, > -Peter > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 2:23:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id E08C514F8D for ; Sat, 1 May 1999 02:23:34 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Sat, 1 May 1999 10:21:29 +0100 Message-ID: From: paul@originative.co.uk To: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG Subject: RE: -stable vs -current (was Re: solid NFS patch #6... ) Date: Sat, 1 May 1999 10:21:28 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Matthew Dillon [mailto:dillon@apollo.backplane.com] > Sent: 01 May 1999 00:53 > To: freebsd-current@FreeBSD.ORG > Subject: -stable vs -current (was Re: solid NFS patch #6... ) > > I expect the 3.2 release to be a really good release. > > It is true that -current has been, more often then not, > more stable then > -stable in the last two months. This is because fixes > were being made > to -current more quickly then they could be backported to > -stable. Most > of these fixes *have* been backported at this point. > There are still a > few that have not that are on my hot list ( and still not > addressed, even > with prodding ). There are also a few bug fixes that > simply cannot be > backported to stable without some pain ( i.e. require the complete > replacement of a number of subsystems ), and pain is not > in the cards > with the 3.2 release so close. But no-one is really testing -stable. How many people have a stable machine and a current machine and spend as much time testing stable as they do current? > It is hard enough dealing with two branches of the source > tree. I will > personally take my Super Soaker 5000 to anyone suggesting > that we have > *three* !!!!. Sqirt sqirt sqirt! The -stable branch shouldn't have anything done to it, that's my whole point, we shouldn't be merging stuff back into the -stable branch, only fix specific straightforward problems that don't require complete re-engineering. > I am hoping that we will be able to accomplish a major > synchronization > after the 3.2 release. I personally believe that > -current is stable > enough that we should do one big-assed commit to sync > -stable up to the > current -current and then continue as per normal. I only > wish EGCS > hadn't been incorporated quite yet. At the very least, I want to > sync *my* stuff up ( NFS/VM/VFS/BIO/VN/SWAPPER ). Then what happens to -stable, is it going to get thouroughly tested with all these changes? You're currently treating -stable as a "beta stable" in that users who track it are being used as beta testers to find the bugs caused by merges from current. There's no track for "really stable" users who want to pick up necessary bug fixes. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 3:34:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 593A314CBA for ; Sat, 1 May 1999 03:34:22 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id MAA12959; Sat, 1 May 1999 12:34:14 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905011034.MAA12959@freebsd.dk> Subject: Re: ep0 *UTP* In-Reply-To: from Dag-Erling Smorgrav at "Apr 30, 1999 7:23:51 pm" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Sat, 1 May 1999 12:34:14 +0200 (CEST) Cc: garbanzo@hooked.net, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Dag-Erling Smorgrav wrote: > Alex Zepeda writes: > > On Wed, 28 Apr 1999, Jim Bryant wrote: > > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting: > > > > ep0 XXX: driver didn't set ifq_maxlen > > > I still get that one too. Driver problem? > > I'm guessing so. I wonder if this is the cause of some odd network > > behavior I'm getting.. > > Anybody using a 3c509 and expecting it to work reliably should be > taken out and shot in the back of the head. Would you please take your medication on a daily basis ?? Those mood swings are not fun anymore :) I have lots of machines running with 3c509 cards in them, including all my machines here, I've never had a single problem with them. The ep driver may have some rough edges, but I've never encountered any of them to be a problem. There are lots of better cards out there, but stating that the 3c509 doesn't work, is totally out in the dark... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 3:45: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7C93314CBA for ; Sat, 1 May 1999 03:44:59 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id MAA35034; Sat, 1 May 1999 12:43:25 +0200 (CEST) (envelope-from des) To: Soren Schmidt Cc: garbanzo@hooked.net, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: ep0 *UTP* References: <199905011034.MAA12959@freebsd.dk> From: Dag-Erling Smorgrav Date: 01 May 1999 12:43:25 +0200 In-Reply-To: Soren Schmidt's message of "Sat, 1 May 1999 12:34:14 +0200 (CEST)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt writes: > [...] > There are lots of better cards out there, but stating that the 3c509 > doesn't work, is totally out in the dark... Well, excuse me for breathing. I'll just take your word, and dismiss the problems I've had with flaky 3c509s (about two thirds of those I've encountered have been flaky) as mere hallucinations. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 3:55:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 1A2E514E51 for ; Sat, 1 May 1999 03:55:29 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id FAA14055; Sat, 1 May 1999 05:55:11 -0500 (CDT) From: Kevin Day Message-Id: <199905011055.FAA14055@home.dragondata.com> Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199904302213.PAA01178@dingo.cdrom.com> from Mike Smith at "Apr 30, 1999 3:13:11 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 1 May 1999 05:55:10 -0500 (CDT) Cc: mike@smith.net.au, david@aps-services.com, paul@originative.co.uk, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I honestly don't know when to bring up things like that, now. :) > > For 3.2, _right_now_. What you're doing with Matt is the first stage; > the next involves bringing it back to the 3.2-beta tree and testing it > there. > > Please understand that if "you" (the community) aren't working on this, > nobody else is. We don't have enough people manning the trenches > because they're all sitting back in the chateau waiting for the > afternoon dispatches. This doesn't work. 8) > Can I propose something? I realize gnats does most of this, but... Suppose there's some central list where anyone who is having unresolved problems can post their e-mail address, section of code, and a brief explaination of the symptoms. Other people acn go to this list and tack on their e-mail address to other people's compalaints saying "I'm seeing this too.". Before each release, all of these people are e-mailed saying "Can you test to see if your problem still exists?" This will also be a bonus for developers to find people who are experiencing specific problems, to see if their fixes work. I know this is a lot like gnats, however: I don't think gnats wants a list of 'me too's in it. It's not easy to mail groups of people from gnats. There's no reason for anyone to add their e-mail address to a PR at the moment. I'm not sure if this'll make things more confusing or not, but... It'll stop people with legitimate problems from getting lost in the shuffle, and keeps PR's to more timely issues. Anyone have any comments? Really, i'm just picturing a list of people with specific problems... maybe gnats can be tuned a bit for this... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 4: 0:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id AAE1614FE3 for ; Sat, 1 May 1999 04:00:35 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id NAA35095; Sat, 1 May 1999 13:00:31 +0200 (CEST) (envelope-from des) To: Lars Fredriksen Cc: current@FreeBSD.ORG Subject: Re: default route not set up?? References: <372A1AE6.4E2738D4@odin-corporation.com> From: Dag-Erling Smorgrav Date: 01 May 1999 13:00:30 +0200 In-Reply-To: Lars Fredriksen's message of "Fri, 30 Apr 1999 16:04:39 -0500" Message-ID: Lines: 27 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lars Fredriksen writes: > If you set "defaultrouter" in /etc/rc.conf to an ip address, > I expected that rc.network would > do a route add default ..., but instead I find that rc.network doesn't > do anything with the defaultrouter variable except to pass it on to the > route_default variable, which doesn't seem to be used at all. > > What am I missing here??? # Configure routing if [ "x$defaultrouter" != "xNO" ] ; then static_routes="default ${static_routes}" # look here... route_default="default ${defaultrouter}" fi # Set up any static routes. This should be done before router discovery. if [ "x${static_routes}" != "x" ]; then for i in ${static_routes}; do # ...and here eval route_args=\$route_${i} route add ${route_args} done fi DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 4:19: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 021201500E for ; Sat, 1 May 1999 04:18:58 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id NAA12179 for freebsd-current@freebsd.org; Sat, 1 May 1999 13:18:56 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id 6DF6240; Sat, 1 May 1999 13:14:00 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 623361E19 for ; Sat, 1 May 1999 13:14:00 +0200 (CEST) Date: Sat, 1 May 1999 13:14:00 +0200 (CEST) From: Blaz Zupan To: freebsd-current@freebsd.org Subject: sound and sio problems after newbus changes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I also experience the sound problems. Although sound works, it has problems stopping. For example when I hit stop in x11amp, the sound still loops for a couple of seconds and then I get the following message on the console: timeout flushing dbuf_out, chan 1 cnt 0xfff9e46c flags 0x000001c1 This message is being generated in snd_flush() in /sys/i386/isa/snd/dmabuf.c. Looking at the code, it loops 10 times, each time waiting for a tsleep() to succeed. There are only two places in dmabuf.c that wakeup() this tsleep, one is dsp_wr_dmadone(), the second is in dsp_rd_dmadone(). Both are called from dsp_wrintr(). I put in a printf() at the start of dsp_wrintr(). The interrupt gets called when I start playing music in x11amp. When I stop it, no interrupt is generated, so dsp_wr_dmadone() is never called, so it never wakes up the tsleep() in snd_flush(). I really don't know why the interrupt does not occur (or if it should occur at all), maybe someone more knowledgable can take over from here.... Please. Pretty please with sugar on top :) Also, has anybody problems with sio buffer overflows? My machine is a Pentium 200MMX, which should be able to handle 115.2K on a com port just fine (my old 486 did, when I was running 2.2.x, 3.0 and 4.0 before newbus). But now I'm receiving lots of sio overflows, it is as simple as typing "ATI4" to my Courier, some characters get lost on output. If I am allowed to take a wild guess, this problem could be linked to the sound problem. Maybe some interrupts are generally lost or not correctly handled. Blaz Zupan, blaz@amis.net, http://www.herbie.amis.net Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 4:58:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1C87714FE9 for ; Sat, 1 May 1999 04:58:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id EAA02341 for ; Sat, 1 May 1999 04:58:40 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: Odd message during -current boot Date: Sat, 01 May 1999 04:58:40 -0700 Message-ID: <2337.925559920@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG haveseen_isadev() called - FIXME! (about 10 times) This appears to happen around the bt_isa (Buslogic) probe. Is that of any help? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 5: 5:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5AA3414FB7 for ; Sat, 1 May 1999 05:05:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA51632; Sat, 1 May 1999 13:06:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 13:06:23 +0100 (BST) From: Doug Rabson To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: Odd message during -current boot In-Reply-To: <2337.925559920@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Jordan K. Hubbard wrote: > haveseen_isadev() called - FIXME! > (about 10 times) > > This appears to happen around the bt_isa (Buslogic) probe. Is that of > any help? Its fairly harmless. We don't really support the old haveseen_isadev() api and its a reminder to convert any old drivers which use it. I might deal with it this weekend since I have some time. I'm going to finish importing gdb-4.18 first though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 5:22:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D584F14EF0 for ; Sat, 1 May 1999 05:22:25 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA13123; Sat, 1 May 1999 14:22:18 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905011222.OAA13123@freebsd.dk> Subject: Re: ep0 *UTP* In-Reply-To: from Dag-Erling Smorgrav at "May 1, 1999 12:43:25 pm" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Sat, 1 May 1999 14:22:17 +0200 (CEST) Cc: garbanzo@hooked.net, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Dag-Erling Smorgrav wrote: > Soren Schmidt writes: > > [...] > > There are lots of better cards out there, but stating that the 3c509 > > doesn't work, is totally out in the dark... > > Well, excuse me for breathing. I'll just take your word, and dismiss > the problems I've had with flaky 3c509s (about two thirds of those > I've encountered have been flaky) as mere hallucinations. Yeah, could be, as I hinted in the former email :) Or it could be pilot errors, there are both non-PnP and PnP versions of those cards, and their default behavior can IIRC be changed via a DOS util, so there are lots of room for confusion, but that is not the same as it doesn't work, its just a bit complex. I have used those cards since they showed up, and apart from a few broken ones (they DONT like DC on your BNC cableing) there has been no problems (we are talking hundreds of cards here). To get back to the subject, the default interface type (AUI/BNC/UTP) are store in an EEPROM on board, this default is shown in the probe. The default can be changed with a DOS util from 3COM. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 5:45:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id AD30914BD3 for ; Sat, 1 May 1999 05:45:35 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA07314; Sat, 1 May 1999 21:45:09 +0900 (JST) Message-ID: <372AF60B.E11A6989@newsguy.com> Date: Sat, 01 May 1999 21:39:39 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Lars Fredriksen , current@FreeBSD.ORG Subject: Re: default route not set up?? References: <372A1AE6.4E2738D4@odin-corporation.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Lars Fredriksen writes: > > If you set "defaultrouter" in /etc/rc.conf to an ip address, > > I expected that rc.network would > > do a route add default ..., but instead I find that rc.network doesn't > > do anything with the defaultrouter variable except to pass it on to the > > route_default variable, which doesn't seem to be used at all. > > > > What am I missing here??? > > # Configure routing > > if [ "x$defaultrouter" != "xNO" ] ; then > static_routes="default ${static_routes}" # look here... > route_default="default ${defaultrouter}" > fi > > # Set up any static routes. This should be done before router discovery. > if [ "x${static_routes}" != "x" ]; then > for i in ${static_routes}; do # ...and here > eval route_args=\$route_${i} > route add ${route_args} > done > fi Looking there, it *does* seem that there is a problem. defaultrouter is only used to set route_default, which is *not* used. At least on the code you quoted. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness if that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 5:47:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (Postfix) with SMTP id 482CC14BD3 for ; Sat, 1 May 1999 05:47:17 -0700 (PDT) (envelope-from ejc@bazzle.com) Received: (qmail 21346 invoked from network); 1 May 1999 12:47:11 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 1 May 1999 12:47:11 -0000 Date: Sat, 1 May 1999 08:47:08 -0400 (EDT) From: "Eric J. Chet" To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: DUMMYNET broken in -current ? In-Reply-To: <15921.925485417@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, Poul-Henning Kamp wrote: > > I have two machines, the target being a -current SMP box. > > On the source machine I do > ping target > > On the target machine, SMP kernel with IPFW+DUMMYNET: > > ipfw pipe config 1 delay 200ms > ipfw add pipe 1 icmp from any to any > > and get a panic in ether_output because "dst" is 0x14. > > Anybody who can try this ? Hello It's also broker for UP -current for the last two weeks. Machine locks up or reboots. Later, Eric Chet ejc@kenpo-jujitsu.com ejc@bazzle.com ejc@FreeBSD.ORG ejchet@lucent.com Senior Object Oriented Developer - Specializing in OOA, OOD, C++, Java, CORBA Kenpo JuJitsu the Ultimate in Self Defense, Tai Chi for Life cat man du : where UNIX geeks go when they die To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 5:51:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id AAF8014BD3 for ; Sat, 1 May 1999 05:51:04 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 21177 invoked by uid 1008); 1 May 1999 12:51:01 -0000 Message-ID: <19990501125101.21175.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: freebsd-current@freebsd.org Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-reply-to: Your message of "Fri, 30 Apr 1999 11:50:51 MST." Date: Sat, 01 May 1999 20:51:01 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: >Snob Art Genre wrote: >> On Fri, 30 Apr 1999, Poul-Henning Kamp wrote: >> >>> In message , John Polstra writes: >>> >Rodney W. Grimes wrote: >>> > >>> >You're being totally unrealistic. You can't create >2^32 of >>> >_anything_ on an i386 without running out of memory. >>> >>> Well, John, you can, the newer ones will address 2^36 bytes of memory >>> and even a i386 can address 2^32 bytes or 2^35 bits... >> >> Since when does FreeBSD only run on i386? > >Sheesh. Make it a bloody long then so you'll get 64 bits on the >Alpha. And then go fix all the printf format mismatches. > >Or, pull you head out of that dark fantasyland and realize that (a) a >32-bit counter is not a problem in any realistic sense, and (b) if it >were, we'd have thousands of other equally serious problems throughout >the system. > >I'm done with this absurd thread. I tend to agree here - but I'll submit a patch with an assertion in the next couple of days. adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 6:15:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from opi.flirtbox.ch (unknown [62.48.0.50]) by hub.freebsd.org (Postfix) with SMTP id 06F0614C58 for ; Sat, 1 May 1999 06:15:16 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 35194 invoked from network); 1 May 1999 13:15:14 -0000 Received: from unknown (HELO pipeline.ch) (195.134.128.41) by opi.flirtbox.ch with SMTP; 1 May 1999 13:15:14 -0000 Message-ID: <372AFE5B.AAA231EA@pipeline.ch> Date: Sat, 01 May 1999 15:15:07 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: dg@root.com Cc: mjacob@feral.com, Greg Lehey , Brad Knowles , FreeBSD current users Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... References: <199905010721.AAA25403@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > > >Matthew Jacob wrote: > >> For raw pattern testing Linux has a special challenge since you right > >> directly into the buffer cache. There *is* a BLKFLSBUF ioctl that can try > >> and force a flush but this probably ought to be written to use O_FSYNC- I > >> think that the ll_rw code might use it or an fsync could be done... > > > >Linux' fsync() works only on directories, not on files. > > Huh? That doesn't make any sense. The "f" in fsync() stands for "file". It does write the file to the disk but not the inode. To get the inode on the disk you have to fsync() the directory (which sync'ed the whole FS before 2.0.35). Kinda stupid... If you can't believe it: http://www.ornl.gov/its/archives/mailing-lists/qmail/1998/05/threads.html#00691 Look for Linus' answers. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 6:18:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 03B1614E46 for ; Sat, 1 May 1999 06:18:28 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id PAA35382; Sat, 1 May 1999 15:18:24 +0200 (CEST) (envelope-from des) To: "Daniel C. Sobral" Cc: Dag-Erling Smorgrav , Lars Fredriksen , current@FreeBSD.ORG Subject: Re: default route not set up?? References: <372A1AE6.4E2738D4@odin-corporation.com> <372AF60B.E11A6989@newsguy.com> From: Dag-Erling Smorgrav Date: 01 May 1999 15:18:23 +0200 In-Reply-To: "Daniel C. Sobral"'s message of "Sat, 01 May 1999 21:39:39 +0900" Message-ID: Lines: 27 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: > Dag-Erling Smorgrav wrote: > > # Configure routing > > > > if [ "x$defaultrouter" != "xNO" ] ; then > > static_routes="default ${static_routes}" # look here... > > route_default="default ${defaultrouter}" > > fi > > > > # Set up any static routes. This should be done before router discovery. > > if [ "x${static_routes}" != "x" ]; then > > for i in ${static_routes}; do # ...and here > > eval route_args=\$route_${i} > > route add ${route_args} > > done > > fi > > Looking there, it *does* seem that there is a problem. defaultrouter > is only used to set route_default, which is *not* used. At least on > the code you quoted. This is getting fun :) Look closer at the first line I commented, then at the loop, and especially the eval. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 6:29:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 2917614CBA for ; Sat, 1 May 1999 06:29:29 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA09703; Sat, 1 May 1999 22:59:27 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA16220; Sat, 1 May 1999 23:00:02 +0930 Date: Sat, 1 May 1999 23:00:00 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Blaz Zupan Cc: freebsd-current@freebsd.org Subject: Re: sound and sio problems after newbus changes In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes and yes (I have both the sound problems and the sio overflows) - these started around the time of the newbus commits. Kris On Sat, 1 May 1999, Blaz Zupan wrote: > I also experience the sound problems. Although sound works, it has > problems stopping. For example when I hit stop in x11amp, the sound still > loops for a couple of seconds and then I get the following message on the > console: > > timeout flushing dbuf_out, chan 1 cnt 0xfff9e46c flags 0x000001c1 > > This message is being generated in snd_flush() in > /sys/i386/isa/snd/dmabuf.c. Looking at the code, it loops 10 times, each > time waiting for a tsleep() to succeed. There are only two places in > dmabuf.c that wakeup() this tsleep, one is dsp_wr_dmadone(), the second > is in dsp_rd_dmadone(). Both are called from dsp_wrintr(). > > I put in a printf() at the start of dsp_wrintr(). The interrupt gets > called when I start playing music in x11amp. When I stop it, no interrupt > is generated, so dsp_wr_dmadone() is never called, so it never wakes up > the tsleep() in snd_flush(). I really don't know why the interrupt does > not occur (or if it should occur at all), maybe someone more knowledgable > can take over from here.... Please. Pretty please with sugar on top :) > > Also, has anybody problems with sio buffer overflows? My machine is a > Pentium 200MMX, which should be able to handle 115.2K on a com port just > fine (my old 486 did, when I was running 2.2.x, 3.0 and 4.0 before > newbus). But now I'm receiving lots of sio overflows, it is as simple as > typing "ATI4" to my Courier, some characters get lost on output. > > If I am allowed to take a wild guess, this problem could be linked to the > sound problem. Maybe some interrupts are generally lost or not correctly > handled. > > Blaz Zupan, blaz@amis.net, http://www.herbie.amis.net > Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 7:18: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from oldnews.quick.net (unknown [207.212.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D70D14FDD for ; Sat, 1 May 1999 07:18:00 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id HAA14512; Sat, 1 May 1999 07:17:57 -0700 (PDT) Date: Sat, 1 May 1999 07:17:56 -0700 (PDT) From: "Steven P. Donegan" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Odd message during -current boot In-Reply-To: <2337.925559920@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Jordan K. Hubbard wrote: > haveseen_isadev() called - FIXME! > (about 10 times) > > This appears to happen around the bt_isa (Buslogic) probe. Is that of > any help? > > - Jordan > And, it happens even if the bt device driver is not configured into the kernel... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 7:22: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id B08D914FDD for ; Sat, 1 May 1999 07:21:53 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id JAA13711; Sat, 1 May 1999 09:21:20 -0500 (CDT) (envelope-from bob) Date: Sat, 1 May 1999 09:21:20 -0500 From: Bob Willcox To: Wilko Bulte Cc: bob@pmr.com, cjohnson@neunacht.netgsi.com, shocking@prth.pgs.com, current@FreeBSD.ORG Subject: Re: Further on tape & CAM problems Message-ID: <19990501092120.A13451@luke.pmr.com> Reply-To: Bob Willcox References: <19990429164138.A89144@luke.pmr.com> <199904292236.AAA14008@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199904292236.AAA14008@yedi.iaf.nl>; from Wilko Bulte on Fri, Apr 30, 1999 at 12:36:25AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 30, 1999 at 12:36:25AM +0200, Wilko Bulte wrote: > As Bob Willcox wrote ... > > On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote: > > > As Bob Willcox wrote ... > > > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > > > > shipping 8200's (this was right at their end-of-life) was: > > > > > > > > MX: 2680 > > > > SV: C034 > > > > > > > > This is for generic models. OEM models may have different versions > > > > due to customizations. > > > > > > And these are not recommended for general use. > > > > Hmm, why is that? The newest of the IBM branded Exabyte 8200's that I > > That is what I've been told by an Exabyte engineer years back. I can only > guess that some OEMs need adaptations to the firmware behaviour that are > incompatible with what the rest of the world needs (or has standardised > on, e.g. in the ANSI SCSI standard). Again, guessing. Well, I can only speak for the IBM OEM'd drives that I have (as a retired IBMer, I've been picking them up at their employee surplus store here in Austin, TX). For these drives the generic firmware works just fine. I can see why Exabyte wouldn't openly recommend the change though. Back in the late 80's, when I was still working for IBM on AIX, I do recall that we did have some customizations in the firmware for the RS/6K AIX systems. In addition to changing the Inquiry command Vendor ID data, I believe there were some functional changes (I don't recall the details). I have always suspected that the functional changes are likely what made the IBM OEM'd drives fail on FreeBSD! The upgraded firmware IBM drives work on both (as "Other SCSI Tape Drive"). > > > have have precisely these firmware levels in them (2680 & C034). Also, > > Mine works OK with that f/w. Not that I use the 8200 often anymore, > I like my DLT4000 much better than the 8200. ;-) I much prefer my Exabyte Mammouth drives as well :-) (But I do seem to get some fun out of playing with the 8200's I get for $10 apiece from the surplus store :-) Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 7:46: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id C492014C9E; Sat, 1 May 1999 07:46:00 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS2-p22.hfa.netvision.net.il [62.0.145.150]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id RAA25961; Sat, 1 May 1999 17:45:58 +0300 (IDT) From: Tomer Weller To: FreeBSD Current , FreeBSD Questions Subject: voxware drivers Date: Sat, 1 May 1999 17:22:34 +0300 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99050117280900.00318@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit X-KMail-Mark: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG im trying to use the voxware drivers in FreeBSD 3.1 and CURRENT and the configuration that worked for me in 2.2.7 (worked fine) doesn't work flawless anymore. main problem is that i have problems with mixer. this is a pnp soundcard that emulates SB Pro. when trying to run mixer : mixer: SOUND_MIXER_READ_DEVMASK: Device not configured Kernel config : #sound VOXWARE options SBC_IRQ=5 controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 device mpu0 at isa? port 0x330 irq 9 device opl0 at isa? port 0x388 conflicts dmesg : sb0 at port 0x220 irq 5 drq 1 on isa0 NOTE! SB Pro support required with your soundcard! snd0: sb0: interrupting at irq 5 mpu0 at port 0x330 irq 9 on isa0 snd0: mpu0: interrupting at irq 9 opl0 at port 0x388 on isa0 snd0: how do i ass "SB Pro support" ? never needed that in 2.2.7. i tried pcm0, doesn't work good for me (though mixer works fine) ====================================== Tomer Weller spud@i.am wellers@netvision.net.il "Drugs are good, and if you do'em pepole think that you're cool", NoFX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 7:46:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id A8E4E14E2D; Sat, 1 May 1999 07:46:01 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS2-p22.hfa.netvision.net.il [62.0.145.150]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id RAA07272; Sat, 1 May 1999 17:46:00 +0300 (IDT) From: Tomer Weller To: FreeBSD Current , FreeBSD Questions Subject: voxware sound Date: Sat, 1 May 1999 17:28:33 +0300 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99050117312601.00318@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG im trying to use the voxware drivers in FreeBSD 3.1 and CURRENT and the configuration that worked for me in 2.2.7 (worked fine) doesn't work flawless anymore. main problem is that i have problems with mixer. this is a pnp soundcard that emulates SB Pro. when trying to run mixer : mixer: SOUND_MIXER_READ_DEVMASK: Device not configured Kernel config : #sound VOXWARE options SBC_IRQ=5 controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 device mpu0 at isa? port 0x330 irq 9 device opl0 at isa? port 0x388 conflicts dmesg : sb0 at port 0x220 irq 5 drq 1 on isa0 NOTE! SB Pro support required with your soundcard! snd0: sb0: interrupting at irq 5 mpu0 at port 0x330 irq 9 on isa0 snd0: mpu0: interrupting at irq 9 opl0 at port 0x388 on isa0 snd0: how do i ass "SB Pro support" ? never needed that in 2.2.7. i tried pcm0, doesn't work good for me (though mixer works fine) ====================================== Tomer Weller spud@i.am wellers@netvision.net.il "Drugs are good, and if you do'em pepole think that you're cool", NoFX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 7:50:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 539E014C9E for ; Sat, 1 May 1999 07:50:56 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id KAA01423; Sat, 1 May 1999 10:49:03 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Sat, 1 May 1999 10:49:02 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Dag-Erling Smorgrav Cc: Soren Schmidt , garbanzo@hooked.net, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: ep0 *UTP* In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 May 1999, Dag-Erling Smorgrav wrote: > Soren Schmidt writes: > > [...] > > There are lots of better cards out there, but stating that the 3c509 > > doesn't work, is totally out in the dark... > > Well, excuse me for breathing. I'll just take your word, and dismiss > the problems I've had with flaky 3c509s (about two thirds of those > I've encountered have been flaky) as mere hallucinations. Well, if it's any reassurance at all, a friend of mine recently switched to FreeBSD from Andrew Linux, and the 3c509 was flaky under Linux, but seems to work fine under FreeBSD. Given past experiences, I advised him not to put it under too high a load, but since it's just a crash machine anyway.. They were really amused when the FreeBSD boot sequence announced that the card was known buggy and something should be done about it, and they commented that that was exactly right and they were pretty impressed. Even more so when the card worked for a change. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 7:59:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.36]) by hub.freebsd.org (Postfix) with ESMTP id 64F1614C9E for ; Sat, 1 May 1999 07:58:48 -0700 (PDT) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id OAA05106; Sat, 1 May 1999 14:54:11 GMT (envelope-from zach) Date: Sat, 1 May 1999 09:54:11 -0500 From: Zach Heilig To: Peter Wemm Cc: vortexia , Doug Rabson , current@freebsd.org Subject: Re: PCM Message-ID: <19990501095411.A5012@k6n1.znh.org> References: <19990501082228.3C75F1F58@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990501082228.3C75F1F58@spinner.netplex.com.au>; from Peter Wemm on Sat, May 01, 1999 at 04:22:25PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 01, 1999 at 04:22:25PM +0800, Peter Wemm wrote: > vortexia wrote: > > Heh, the panic problem might be solved, but Ive just cvsupped with the > > latest 4.0-CURRENT and the problems with pcm are definatly not over, Im > > getting very jerky sound, its repeating bits of it over and over... and I > > get messages like this while trying to play mp3s with mpg123: > > > > May 1 10:12:16 main /kernel: timeout flushing dbuf_out, chan 3 cnt > > 0xfff994bc flags 0x00000141 > > > > Cheers > > Andrew > > I've run two systems with PCM right since the first newbus commit, and it's > worked for me. Admittedly I don't use it all that often, but it's never > paniced and I don't recall getting any more sound problems than usual. > > I checked that the isa_dma.c code is an exact split of the dma code that > used to be in the old isa.c, there are zero changes to the isa dma code. Ok, the discussion seems to be here, I posted a debugging log in -multimedia last night. (It basically shows a bunch of data being queued up, one interrupt, and some buffer being filled). One more thing to add to that is: pcm1 (SB16pnp sn 0x12b9118f) at 0x220-0x22f irq 9 drq 0 flags 0x17 on isa and vmstat -i: interrupt total rate old irq9 1 0 mux irq10 47898 1 fdc0 irq6 2 0 wdc0 irq14 24700 0 wdc1 irq15 207 0 atkbd0 irq1 36361 0 psm0 irq12 1215 0 sio1 irq3 3379354 90 ppc0 irq7 1 0 ed0 irq5 238 0 clk irq0 3752093 99 rtc irq8 4802629 127 Total 12044699 320 The sound driver is definately not getting the interrupts it should on my system. Everything worked properly in the first half of April. What I'm about to do is compile a kernel from every day since I last knew it worked and see where it breaks... -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 8:16:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id E1615150C0 for ; Sat, 1 May 1999 08:16:19 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Sat, 1 May 1999 11:15:27 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 1 May 1999 08:15:24 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 1 May 1999 11:15:23 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Kevin Day , Mike Smith , david@aps-services.com, paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Doug Rabson's (dfr@nlsystems.com) message dated Sat, 01 May 1999 08:09:03. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 May 1999 11:15:23 -0400 Message-ID: <18817.925571723@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG BitKeeper should be ready soon. Once it's been proven stable, might it be a better alternative to CVS? H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 8:34:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E873E150BF for ; Sat, 1 May 1999 08:34:29 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA01796; Sun, 2 May 1999 00:34:11 +0900 (JST) Message-ID: <372B1E6B.263A3B19@newsguy.com> Date: Sun, 02 May 1999 00:31:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Lars Fredriksen , current@FreeBSD.ORG Subject: Re: default route not set up?? References: <372A1AE6.4E2738D4@odin-corporation.com> <372AF60B.E11A6989@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > > > # Configure routing > > > > > > if [ "x$defaultrouter" != "xNO" ] ; then > > > static_routes="default ${static_routes}" # look here... > > > route_default="default ${defaultrouter}" > > > fi > > > > > > # Set up any static routes. This should be done before router discovery. > > > if [ "x${static_routes}" != "x" ]; then > > > for i in ${static_routes}; do # ...and here > > > eval route_args=\$route_${i} > > > route add ${route_args} > > > done > > > fi > > > > Looking there, it *does* seem that there is a problem. defaultrouter > > is only used to set route_default, which is *not* used. At least on > > the code you quoted. > > This is getting fun :) Look closer at the first line I commented, then > at the loop, and especially the eval. That's tricky, indeed. You should have commented the line below the second line, not the second line. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness if that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 8:50: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 172C0150BF for ; Sat, 1 May 1999 08:50:01 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id IAA34151 for ; Sat, 1 May 1999 08:50:01 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <372B22A4.495941C@MexComUSA.net> Date: Sat, 01 May 1999 08:49:56 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.org Subject: netatalk (atalkd,papd,afpd) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just realized that I have lost netatalk (atalkd/papd/afpd) seems to have silently died within the last week or so, for no clear reason. Has anyone else, who is running current and netatalk, seen this? (Misery loves company:-) I'm going to start looking for a problem. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 9: 3:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from charon.khoral.com (charon.khoral.com [209.75.155.97]) by hub.freebsd.org (Postfix) with SMTP id 9939C14CCF for ; Sat, 1 May 1999 09:03:45 -0700 (PDT) (envelope-from steve@khoral.com) Received: from zen.alb.khoral.com by charon.khoral.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 1 May 1999 16:03:45 UT Received: from khoral.com Sat, 1 May 1999 10:03:44 -0600 (MDT) Date: Sat, 1 May 1999 10:03:44 -0600 (MDT) From: Steve Jorgensen Message-Id: <199905011603.KAA07075@zen.alb.khoral.com> To: John Polstra , current@freebsd.org Subject: Re: XFree86 and egcs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <199904282026.OAA13313@zen.alb.khoral.com>, > Steve Jorgensen wrote: > > > In article <199904271932.NAA01643@zen.alb.khoral.com>, > > > Steve Jorgensen wrote: > > > > I cvsup'ed and installed yesterday morning it's the third > > > > cvsup I've done since egcs went in, so I know it's working > > > > ok. Anyway, I decided to update my XFree86 installation, > > > > and found that the port no longer works. As it compiles > > > > all binaries created report tons of missing symbols > > > > from the various X library. The wierd thing is that it > > > > still installs most of the X binaries anyway, and they work > > > > fine, but it dies when it gets to installing the X server > > > > itself. > [...] > > Ok, well in the interest of not sending large compile > > output to the news group, I've put an error log on > > my webserver with all the info in it: > > > > http://www.haunt.com/~steve/error.html > I took a look at it. All those undefined symbols are supposed to be > in the "-lX11" library. I don't really know why you're getting > them. Maybe you have an older version of the library lying around > that is stripped? Try a "locate libX11.so" and see what's there. > Then do "file libX11.so" on each one and see if it's stripped. No old versions, I removed the old XF86 installation before installing this one. > Maybe your LD_LIBRARY_PATH environment variable is set, screwing up > the build? Maybe you've got something funny in /etc/make.conf? LD_LIBRARY_PATH is not set, and the only difference in my make.conf is that I set HAVE_MOTIF to yes, because I intend to install lesstif. > Sorry, these are just guesses. I've never encountered the problem > you're reporting. Well, thanks for trying.. I'm going to try cvssuping once more before I dig too deep into the xf86 port. Maybe I updated in the middle of a commit the last time. Steve -- ----------------------------------------------------------- Steven Jorgensen steve@khoral.com steve@haunt.com ------------------------------+---------------------------- Khoral Research Inc. | PHONE: (505) 837-6500 6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842 Albuquerque, NM 87110 | URL: http://www.khoral.com/ ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 10: 0:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprtp (smtprtp.NortelNetworks.com [192.122.117.66]) by hub.freebsd.org (Postfix) with ESMTP id EFC09151C0 for ; Sat, 1 May 1999 10:00:36 -0700 (PDT) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtprtp; Sat, 1 May 1999 13:00:21 -0400 Received: from hcarp00g.ca.nortel.com by zcars01t; Sat, 1 May 1999 12:59:54 -0400 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id NAA00579; Sat, 1 May 1999 13:00:24 -0400 (EDT) Date: Sat, 1 May 1999 13:00:24 -0400 (EDT) From: "Andrew Atrens" Reply-To: "Andrew Atrens" To: "Jordan K. Hubbard" Cc: Steve Kargl , John Polstra , dwhite@resnet.uoregon.edu, current@FreeBSD.ORG Subject: Re: PCM In-Reply-To: <28697.925524873@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a _PnP_ card, and mine comes up as: pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 5 drq 0 flags 0x11 on isa When I use NAS I get an interesting 'riffing' effect (last 2 second sample repeated over and over). The only way to shut it up is to kill the NAS server. Killing nas generates the following kernel message: > timeout flushing dbuf_out, chan 0 cnt 0xfffa3acc flags 0x000040c1 which, originates in /sys/i386/isa/snd/dmabuf.c snd_flush(), which is called by mss_close(). Interestingly other things like xanim and mpg123 are unaffected. Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 10:25:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E152B14C12 for ; Sat, 1 May 1999 10:25:47 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA75931; Sat, 1 May 1999 10:24:13 -0700 (PDT) (envelope-from dillon) Date: Sat, 1 May 1999 10:24:13 -0700 (PDT) From: Matthew Dillon Message-Id: <199905011724.KAA75931@apollo.backplane.com> To: Harlan Stenn Cc: Doug Rabson , Kevin Day , Mike Smith , david@aps-services.com, paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) References: <18817.925571723@brown.pfcs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :BitKeeper should be ready soon. : :Once it's been proven stable, might it be a better alternative to CVS? : :H Maybe, but we wouldn't know for a couple of years. You don't just go trusting 15+ years worth of source history to a program that has just barely been written. I think the Linux people are making a huge mistake by not using CVS. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 10:40:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 8EAAF14FDD for ; Sat, 1 May 1999 10:40:33 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-10-21.camtech.net.au [203.28.1.149]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id DAA14911 for ; Sun, 2 May 1999 03:15:48 +0930 (CST) Message-ID: <372B3CBF.5E524469@camtech.com.au> Date: Sun, 02 May 1999 03:11:19 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: silo overflows in CURRENT ... some info that may help Content-Type: multipart/mixed; boundary="------------ACDDF923C9B1BB571E40AD37" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------ACDDF923C9B1BB571E40AD37 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have been investigating the silo overflow situation for some time. I can trigger them every time by the following action: - Run M.A.M.E. (Multi arcade machine emulator) and then try to download something. (I am using user mode ppp). I believe that the sio driver is its own worst enemy in that once you get one silo overflow, it seems that the driver tries to compensate but it only makes it worse as I continue to get them and the serial port is unusable after that. Exiting MAME doesn't help, I have to reboot or I will be unable to do the smallest thing such as download my mail. I dont think its just MAME but rather anything that thrashes the interrupt system. This is not related to newbus as it occurrred before then in just the same manner. I have seen this effect on my home system no matter what combination of motherboard, modem, serial hardware. I was running a patch to sio.c before newbus came in to improve the speed at which the FIFO buffers were processed but MAME would still trigger the start of the silo overflow storm. With either a patched or unpatched system I can download huge files no problems as long as I dont run MAME at any time. Now dont say "just dont do that" (I know some of you will want to). Kernel config is attached. /etc/ppp/ppp.conf (edited) is attached. dmesg output is also attached. -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------ACDDF923C9B1BB571E40AD37 Content-Type: text/plain; charset=us-ascii; name="KERNEL" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="KERNEL" # Machine with Ultra DMA 32 Bit WD disk, ATAPI CD-ROM, SB16, NE2000 NIC, # NCR PCI SCSI, APM and Intel PIIX power management. # $Id: MATTE,v 11.8 1999/05/02 01:06:00 +09:30 matt Exp $ # based on: $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ # machine i386 ident "MATTE" maxusers 20 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 cpu I686_CPU options CPU_DISABLE_5X86_LSSER # Dont use if you use memory mapped I/O device(s). options CPU_FASTER_5X86_FPU # Faster FPU exception handler options NO_F00F_HACK # Disable Pentium F00F hack # COMPATIBILITY OPTIONS options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT # Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options MD5 # Include a MD5 routine in the kernel options VM86 # Allow processes to switch to vm86 mode (needed for doscmd) # DEBUGGING OPTIONS options DDB # Enable the kernel debugger #options INVARIANTS # Extra sanity checking (slower) #options INVARIANT_SUPPORT # Include sanity checking functions options UCONSOLE # Allow users to grab the console options USERCONFIG # Boot -c editor options VISUAL_USERCONFIG # Visual boot -c editor # NETWORKING OPTIONS options INET # Internet communications protocols # Network interfaces: pseudo-device ether # Generic Ethernet pseudo-device loop # Network loopback device pseudo-device tun 1 # Tunnel driver(user process ppp) pseudo-device streams # SysVR4 STREAMS emulation # FILESYSTEM OPTIONS options FFS # Berkeley Fast Filesystem options FFS_ROOT # FFS usable as root device options NFS # Network Filesystem options CD9660 # ISO 9660 Filesystem options MFS # Memory Filesystem options MSDOSFS # MSDOS Filesystem options PROCFS # Process Filesystem options NSWAPDEV=4 # Allow this many swap-devices options SOFTUPDATES # SoftUpdates aka delayed writes controller pci0 controller ncr0 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # SCSI DEVICE CONFIGURATION (CAM SCSI) controller scbus0 at ncr0 # Base SCSI code disk da0 at scbus0 target 0 disk da1 at scbus0 target 1 disk da2 at scbus0 target 2 disk da3 at scbus0 target 3 disk da4 at scbus0 target 4 disk da5 at scbus0 target 5 disk da6 at scbus0 target 6 options SCSI_DELAY=500 # Only wait 0.5 seconds for SCSI # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 64 # Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 4 # Vnode driver (turns a file into a device) options MSGBUF_SIZE=81920 # Size of the kernel message buffer # HARDWARE DEVICE CONFIGURATION controller isa0 options AUTO_EOI_1 # Save 0.7-1.25 usec for each interrupt controller pnp0 # Enable PnP support in the kernel controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? port ? conflicts pseudo-device splash # Splash screen at start up! device sc0 at isa? options MAXCONS=12 # Number of virtual consoles options SC_HISTORY_SIZE=800 # Number of history buffer lines options VESA # Needs VM86 defined too!! device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives #device wcd0 #controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff #disk wd0 at wdc0 drive 0 #controller wdc1 at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 device psm0 at atkbdc? irq 12 device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device sio0 at isa? port IO_COM1 irq 4 flags 0x10 device sio1 at isa? port IO_COM2 irq 3 options CONSPEED=38400 # Speed for serial console (default 9600) device ed0 at isa? port 0x300 irq 9 iomem 0xd8000 device apm0 at nexus? controller smbus0 controller intpm0 device smb0 at smbus? device joy0 at isa? port IO_GAME #device pcm0 at isa? port? irq 5 drq 1 flags 0x15 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 --------------ACDDF923C9B1BB571E40AD37 Content-Type: text/plain; charset=us-ascii; name="ppp.conf" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ppp.conf" ################################################################# # # PPP Sample Configuration File # # Originally written by Toshiharu OHNO # # $Id: ppp.conf.sample,v 1.28 1997/12/31 03:58:45 brian Exp $ # ################################################################# default: set log chat connect phase set device /dev/cuaa1 set speed 115200 allow users matt deny lqr deny chap set timeout 0 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATX4S95=47 OK-AT-OK \\dATDT\\T TIMEOUT 120 CONNECT" set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 camtechd: set phone 82285100 set login "TIMEOUT 10 sername:--sername: BLAHU assword: BLAHP" dial --------------ACDDF923C9B1BB571E40AD37 Content-Type: text/plain; charset=us-ascii; name="dmegg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmegg" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun May 2 01:10:27 CST 1999 matt@localhost:/usr/src/sys/compile/MATTE Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (463.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping=0 Features=0x183f9ff real memory = 67108864 (65536K bytes) config> pnp 1 0 bios enable avail memory = 62140416 (60684K bytes) Preloaded elf kernel "kernel" at 0xc02ed000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02ed09c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100a1ec0 Comp ID: PNP0600 [0x0006d041] npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 chip2: at device 7.3 on pci0 ncr0: at device 13.0 on pci0 ncr0: interrupting at irq 11 isa0: on motherboard atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model IntelliMouse, device ID 3 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <12 virtual consoles, flags=0x0> fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ed0 at port 0x300-0x31f irq 9 on isa0 ed0: address 00:00:e8:20:33:e8, type NE2000 (16 bit) ed0: interrupting at irq 9 joy0 at port 0x201 on isa0 joy0: joystick sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sb0: interrupting at irq 5 sbxvi0 at drq 5 on isa0 snd0: sbmidi0 at port 0x330 on isa0 snd0: opl0 at port 0x388 on isa0 snd0: ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-3 disk at ata0 as master ad0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s2a ffs_mountfs: superblock updated for soft updates ed0: device timeout --------------ACDDF923C9B1BB571E40AD37-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11: 0:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 28C9514EE5 for ; Sat, 1 May 1999 11:00:21 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-10-21.camtech.net.au [203.28.1.149]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id DAA16265; Sun, 2 May 1999 03:27:48 +0930 (CST) Message-ID: <372B3F93.DE291A83@camtech.com.au> Date: Sun, 02 May 1999 03:23:23 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: abial@webgiro.com, green@unixhelp.org, tseidmann@SIMULTAN.CH, current@FreeBSD.ORG, shocking@prth.pgs.com Subject: New ATA drivers wont boot if second IDE controller enabled References: <199904301126.NAA08416@freebsd.dk> Content-Type: multipart/mixed; boundary="------------2E88C84DE7C443876EFD8FA5" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------2E88C84DE7C443876EFD8FA5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have been unable to use my Ultra DMA ATAPI CD-ROM since version 4 of Soren's ATAPI driver. Version 4 worked fine but since then (since at least version 6 .... I didn't try version 5) The system wont boot if I have my secondary IDE controller enabled. The system never completes its kernel probing, it just sits there after configuring the hard disk. I am running an IBM 6.48 GB (metric GB) hard disk on the first IDE controller as the master. I am running a "Diamond Data 32 speed Ultra DMA CD-ROM" on the second IDE controller and it doesnt matter if its a slave or master (there is nothing else on the controller). The CD-ROM is model number 632A 023 and is made in June 1998. "Diamond Data" is a trade mark of "Mitsubishi Electric Australia". My -CURRENT is only a few hours old (freshly build world and kernel). Kernel config file and dmesg output are attached. -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------2E88C84DE7C443876EFD8FA5 Content-Type: text/plain; charset=us-ascii; name="KERNEL" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="KERNEL" # Machine with Ultra DMA 32 Bit WD disk, ATAPI CD-ROM, SB16, NE2000 NIC, # NCR PCI SCSI, APM and Intel PIIX power management. # $Id: MATTE,v 11.8 1999/05/02 01:06:00 +09:30 matt Exp $ # based on: $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ # machine i386 ident "MATTE" maxusers 20 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 cpu I686_CPU options CPU_DISABLE_5X86_LSSER # Dont use if you use memory mapped I/O device(s). options CPU_FASTER_5X86_FPU # Faster FPU exception handler options NO_F00F_HACK # Disable Pentium F00F hack # COMPATIBILITY OPTIONS options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT # Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options MD5 # Include a MD5 routine in the kernel options VM86 # Allow processes to switch to vm86 mode (needed for doscmd) # DEBUGGING OPTIONS options DDB # Enable the kernel debugger #options INVARIANTS # Extra sanity checking (slower) #options INVARIANT_SUPPORT # Include sanity checking functions options UCONSOLE # Allow users to grab the console options USERCONFIG # Boot -c editor options VISUAL_USERCONFIG # Visual boot -c editor # NETWORKING OPTIONS options INET # Internet communications protocols # Network interfaces: pseudo-device ether # Generic Ethernet pseudo-device loop # Network loopback device pseudo-device tun 1 # Tunnel driver(user process ppp) pseudo-device streams # SysVR4 STREAMS emulation # FILESYSTEM OPTIONS options FFS # Berkeley Fast Filesystem options FFS_ROOT # FFS usable as root device options NFS # Network Filesystem options CD9660 # ISO 9660 Filesystem options MFS # Memory Filesystem options MSDOSFS # MSDOS Filesystem options PROCFS # Process Filesystem options NSWAPDEV=4 # Allow this many swap-devices options SOFTUPDATES # SoftUpdates aka delayed writes controller pci0 controller ncr0 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # SCSI DEVICE CONFIGURATION (CAM SCSI) controller scbus0 at ncr0 # Base SCSI code disk da0 at scbus0 target 0 disk da1 at scbus0 target 1 disk da2 at scbus0 target 2 disk da3 at scbus0 target 3 disk da4 at scbus0 target 4 disk da5 at scbus0 target 5 disk da6 at scbus0 target 6 options SCSI_DELAY=500 # Only wait 0.5 seconds for SCSI # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 64 # Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 4 # Vnode driver (turns a file into a device) options MSGBUF_SIZE=81920 # Size of the kernel message buffer # HARDWARE DEVICE CONFIGURATION controller isa0 options AUTO_EOI_1 # Save 0.7-1.25 usec for each interrupt controller pnp0 # Enable PnP support in the kernel controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? port ? conflicts pseudo-device splash # Splash screen at start up! device sc0 at isa? options MAXCONS=12 # Number of virtual consoles options SC_HISTORY_SIZE=800 # Number of history buffer lines options VESA # Needs VM86 defined too!! device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives #device wcd0 #controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff #disk wd0 at wdc0 drive 0 #controller wdc1 at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 device psm0 at atkbdc? irq 12 device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device sio0 at isa? port IO_COM1 irq 4 flags 0x10 device sio1 at isa? port IO_COM2 irq 3 options CONSPEED=38400 # Speed for serial console (default 9600) device ed0 at isa? port 0x300 irq 9 iomem 0xd8000 device apm0 at nexus? controller smbus0 controller intpm0 device smb0 at smbus? device joy0 at isa? port IO_GAME #device pcm0 at isa? port? irq 5 drq 1 flags 0x15 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 --------------2E88C84DE7C443876EFD8FA5 Content-Type: text/plain; charset=us-ascii; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun May 2 01:10:27 CST 1999 matt@localhost:/usr/src/sys/compile/MATTE Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (463.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping=0 Features=0x183f9ff real memory = 67108864 (65536K bytes) config> pnp 1 0 bios enable avail memory = 62140416 (60684K bytes) Preloaded elf kernel "kernel" at 0xc02ed000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02ed09c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100a1ec0 Comp ID: PNP0600 [0x0006d041] npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 chip2: at device 7.3 on pci0 ncr0: at device 13.0 on pci0 ncr0: interrupting at irq 11 isa0: on motherboard atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model IntelliMouse, device ID 3 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <12 virtual consoles, flags=0x0> fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ed0 at port 0x300-0x31f irq 9 on isa0 ed0: address 00:00:e8:20:33:e8, type NE2000 (16 bit) ed0: interrupting at irq 9 joy0 at port 0x201 on isa0 joy0: joystick sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sb0: interrupting at irq 5 sbxvi0 at drq 5 on isa0 snd0: sbmidi0 at port 0x330 on isa0 snd0: opl0 at port 0x388 on isa0 snd0: ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-3 disk at ata0 as master ad0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s2a ffs_mountfs: superblock updated for soft updates ed0: device timeout --------------2E88C84DE7C443876EFD8FA5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11: 3:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id F17ED14E06 for ; Sat, 1 May 1999 11:03:26 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id NAA00675; Sat, 1 May 1999 13:03:17 -0500 (CDT) Date: Sat, 1 May 1999 13:03:17 -0500 (CDT) From: Steve Price To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199905011724.KAA75931@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Matthew Dillon wrote: # #:BitKeeper should be ready soon. #: #:Once it's been proven stable, might it be a better alternative to CVS? #: #:H # # Maybe, but we wouldn't know for a couple of years. You don't just go # trusting 15+ years worth of source history to a program that has just # barely been written. I think the Linux people are making a huge mistake # by not using CVS. From what I gather (and I could very well be wrong), but I think BitKeeper is somewhat based on SCCS. I'm not advocating that we ditch CVS either, just that BitKeeper may not be as new and fresh as some would like us to believe. Looks like an old friend (or nemisis) dressed in a new set of rags. :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:11:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 3E24714E06 for ; Sat, 1 May 1999 11:11:07 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA04969; Sun, 2 May 1999 04:10:48 +1000 Date: Sun, 2 May 1999 04:10:48 +1000 From: Bruce Evans Message-Id: <199905011810.EAA04969@godzilla.zeta.org.au> To: blaz@gold.amis.net, freebsd-current@FreeBSD.ORG Subject: Re: sound and sio problems after newbus changes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Also, has anybody problems with sio buffer overflows? My machine is a >Pentium 200MMX, which should be able to handle 115.2K on a com port just >fine (my old 486 did, when I was running 2.2.x, 3.0 and 4.0 before >newbus). But now I'm receiving lots of sio overflows, it is as simple as >typing "ATI4" to my Courier, some characters get lost on output. Fast interrupts were broken in early versions of new-bus. Without fast interrupts, sio interrupt latency is limited by the worst spl hog in the system. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:21:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 06A0A1510E for ; Sat, 1 May 1999 11:21:12 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id UAA17726; Sat, 1 May 1999 20:21:04 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id 51AA840; Sat, 1 May 1999 20:19:30 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 3CFCD1E19; Sat, 1 May 1999 20:19:30 +0200 (CEST) Date: Sat, 1 May 1999 20:19:30 +0200 (CEST) From: Blaz Zupan To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: sound and sio problems after newbus changes In-Reply-To: <199905011810.EAA04969@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 May 1999, Bruce Evans wrote: > Fast interrupts were broken in early versions of new-bus. Without > fast interrupts, sio interrupt latency is limited by the worst spl > hog in the system. Yes I know that, but I believe this was later fixed. I'm running a kernel compiled today and the sio overflows still happen. Also adding in the sound problems which seem to be caused by missing interrupts, I think we have a bug in the interrupt code after the newbus changes. Blaz Zupan, blaz@amis.net, http://www.herbie.amis.net Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:23: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id ED8E51510E for ; Sat, 1 May 1999 11:22:56 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA16572; Sat, 1 May 1999 11:22:35 -0700 Date: Sat, 1 May 1999 11:22:33 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Steve Price Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > # > #:BitKeeper should be ready soon. > #: > #:Once it's been proven stable, might it be a better alternative to CVS? > #: > #:H > # > # Maybe, but we wouldn't know for a couple of years. You don't just go > # trusting 15+ years worth of source history to a program that has just > # barely been written. I think the Linux people are making a huge mistake > # by not using CVS. > > >From what I gather (and I could very well be wrong), but I > think BitKeeper is somewhat based on SCCS. I'm not advocating > that we ditch CVS either, just that BitKeeper may not be as new > and fresh as some would like us to believe. Looks like an old > friend (or nemisis) dressed in a new set of rags. :) No, not really. Larry's hostile to RCS because of it's lack of checksum. I've asked him about it a couple of times and he's not really excited about an RCS bottom end. It could be done if you insisted on it (I mean, it's GPL'd code, right?) but it's not something he would support. Bitkeeper is a substantial improvement over CVS and Perforce. It's really a nice piece of work done by somebody who *really* knows his stuff. Remember that Larry saved Sun from complete disaster by inventing NSElite (which Bitkeeper is emphatically a granchild of) in time to keep 1000 engineers from rising up and tearing Eric Schmidt to threads over his insistence that "The Sun/SVR4 merge *SHALL* use NSE and the [ broken ] translucent filesystem if we're here until the year 2000 doing it!". Personally, I'm happy with CVS if you have a model a single main stream of development. It's a disaster when you have to maintain separate development clusters. And very few other packages really do any kind of job of this either. Look- if Linux adopts Bitkeeper, you really should pay attention to that. I doubt you'd find a more difficult set of software engineers to keep code in sync for than the Linux folks- if Bitkeeper works for them and essentially makes a rational release train for Linux, then a major glaring flaw in Linux' strategy that keeps serious businesses from really being able to trust it will be removed. Think about it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:23: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.29]) by hub.freebsd.org (Postfix) with ESMTP id 13F2E15110 for ; Sat, 1 May 1999 11:22:58 -0700 (PDT) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id SAA00597; Sat, 1 May 1999 18:18:53 GMT (envelope-from zach) Date: Sat, 1 May 1999 13:18:53 -0500 From: Zach Heilig To: zach@uffdaonline.net Cc: "Jordan K. Hubbard" , Steve Kargl , John Polstra , dwhite@resnet.uoregon.edu, current@FreeBSD.ORG Subject: Re: PCM Message-ID: <19990501131853.A505@k6n1.znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found the commit that "broke" sound (beyond that, I don't know how to fix it): peter 1999/04/21 00:26:31 PDT Modified files: sys/alpha/isa isa.c sys/alpha/pci pcibus.c sys/cam cam_xpt.c sys/dev/ata ata-all.c sys/i386/i386 nexus.c sys/i386/include types.h sys/i386/isa clock.c intr_machdep.c intr_machdep.h ipl_funcs.c isa_device.h isa_dma.c random_machdep.c sys/isa isavar.h sys/kern kern_intr.c sys/pci intpm.c sys/sys interrupt.h systm.h Log: Stage 1 of a cleanup of the i386 interrupt registration mechanism. Interrupts under the new scheme are managed by the i386 nexus with the awareness of the resource manager. There is further room for optimizing the interfaces still. All the users of register_intr()/intr_create() should be gone, with the exception of pcic and i386/isa/clock.c. Revision Changes Path 1.11 +3 -3 src/sys/alpha/isa/isa.c 1.11 +1 -36 src/sys/alpha/pci/pcibus.c 1.53 +1 -3 src/sys/cam/cam_xpt.c 1.9 +28 -33 src/sys/dev/ata/ata-all.c 1.4 +7 -6 src/sys/i386/i386/nexus.c 1.17 +2 -1 src/sys/i386/include/types.h 1.130 +12 -16 src/sys/i386/isa/clock.c 1.19 +426 -42 src/sys/i386/isa/intr_machdep.c 1.14 +16 -3 src/sys/i386/isa/intr_machdep.h 1.16 +9 -1 src/sys/i386/isa/ipl_funcs.c 1.60 +1 -3 src/sys/i386/isa/isa_device.h 1.2 +1 -2 src/sys/i386/isa/isa_dma.c 1.30 +2 -1 src/sys/i386/isa/random_machdep.c 1.4 +3 -3 src/sys/isa/isavar.h 1.22 +1 -405 src/sys/kern/kern_intr.c 1.5 +4 -8 src/sys/pci/intpm.c 1.8 +4 -19 src/sys/sys/interrupt.h 1.88 +1 -4 src/sys/sys/systm.h A kernel from right before that works for sound, and one from right after it is broken. -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:35:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id D2CB514C05 for ; Sat, 1 May 1999 11:35:33 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Sat, 1 May 1999 19:33:34 +0100 Message-ID: From: paul@originative.co.uk To: dillon@apollo.backplane.com Cc: freebsd-current@FreeBSD.ORG Subject: RE: solid NFS patch #6 avail for -current - need testers files) Date: Sat, 1 May 1999 19:33:33 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Matthew Dillon [mailto:dillon@apollo.backplane.com] > Sent: 01 May 1999 18:24 > To: Harlan Stenn > Cc: Doug Rabson; Kevin Day; Mike Smith; david@aps-services.com; > paul@originative.co.uk; freebsd-current@FreeBSD.ORG > Subject: Re: solid NFS patch #6 avail for -current - need > testers files) > > > > > :BitKeeper should be ready soon. > : > :Once it's been proven stable, might it be a better > alternative to CVS? > : > :H > > Maybe, but we wouldn't know for a couple of years. You > don't just go > trusting 15+ years worth of source history to a program > that has just > barely been written. I think the Linux people are making > a huge mistake > by not using CVS. 15 years? Our cvs repository is only about 5 years old and cvs isn't 15 years old! I agree with the sentiment though :-) Although, if it's widely used I suspect it will stabilise much sooner than a couple of years. If it has the required features it might be worth playing with on the back burner to see how it shaped up. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:37:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DFD50152AA for ; Sat, 1 May 1999 11:37:42 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id OAA03193; Sat, 1 May 1999 14:37:30 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Sat, 1 May 1999 14:37:29 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Matthew Jacob Cc: Steve Price , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So will bitkeeper provide a nice interface for migrating code from an existing and well-established CVS repository to whatever they use? I'm quite happy to allow them to test bitkeeper in a production environment before using it in one myself, needless to say. :) On Sat, 1 May 1999, Matthew Jacob wrote: > > > > > # > > #:BitKeeper should be ready soon. > > #: > > #:Once it's been proven stable, might it be a better alternative to CVS? > > #: > > #:H > > # > > # Maybe, but we wouldn't know for a couple of years. You don't just go > > # trusting 15+ years worth of source history to a program that has just > > # barely been written. I think the Linux people are making a huge mistake > > # by not using CVS. > > > > >From what I gather (and I could very well be wrong), but I > > think BitKeeper is somewhat based on SCCS. I'm not advocating > > that we ditch CVS either, just that BitKeeper may not be as new > > and fresh as some would like us to believe. Looks like an old > > friend (or nemisis) dressed in a new set of rags. :) > > No, not really. Larry's hostile to RCS because of it's lack of checksum. > I've asked him about it a couple of times and he's not really excited > about an RCS bottom end. It could be done if you insisted on it (I mean, > it's GPL'd code, right?) but it's not something he would support. > > Bitkeeper is a substantial improvement over CVS and Perforce. It's really > a nice piece of work done by somebody who *really* knows his stuff. > Remember that Larry saved Sun from complete disaster by inventing NSElite > (which Bitkeeper is emphatically a granchild of) in time to keep 1000 > engineers from rising up and tearing Eric Schmidt to threads over his > insistence that "The Sun/SVR4 merge *SHALL* use NSE and the [ broken ] > translucent filesystem if we're here until the year 2000 doing it!". > > Personally, I'm happy with CVS if you have a model a single main stream of > development. It's a disaster when you have to maintain separate > development clusters. And very few other packages really do any kind of > job of this either. > > Look- if Linux adopts Bitkeeper, you really should pay attention to that. > I doubt you'd find a more difficult set of software engineers to keep code > in sync for than the Linux folks- if Bitkeeper works for them and > essentially makes a rational release train for Linux, then a major > glaring flaw in Linux' strategy that keeps serious businesses from really > being able to trust it will be removed. Think about it. > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:42:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from shattered.disturbed.net (shattered.disturbed.net [192.139.81.180]) by hub.freebsd.org (Postfix) with ESMTP id 8E41C15101 for ; Sat, 1 May 1999 11:42:36 -0700 (PDT) (envelope-from veers@disturbed.net) Received: from shattered.disturbed.net ([192.139.81.180]:62724 "EHLO shattered" ident: "IDENT-NONSENSE") by disturbed.net with ESMTP id <61519-279>; Sat, 1 May 1999 14:47:01 -0400 Date: Sat, 1 May 1999 14:47:00 -0400 (EDT) From: Alex Perel To: paul@originative.co.uk Cc: freebsd-current@FreeBSD.ORG Subject: RE: -stable vs -current (was Re: solid NFS patch #6... ) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999 paul@originative.co.uk wrote: > The -stable branch shouldn't have anything done to it, that's my whole > point, we shouldn't be merging stuff back into the -stable branch, only fix > specific straightforward problems that don't require complete > re-engineering. No new features means stagnation in development. It means that someone coming to FreeBSD and looking for a feature will only find it in -current, which, by virtue of being -current, will have other miscellaneous problems. This person gets annoyed and leaves. This is the _LAST_ thing we need right now. Your idea of -beta is exactly the idea of -stable. If you want something that is only receiving bugfixes, run 2.2.x. It's in maintanance mode now. > Then what happens to -stable, is it going to get thouroughly tested with all > these changes? You're currently treating -stable as a "beta stable" in that > users who track it are being used as beta testers to find the bugs caused by > merges from current. There's no track for "really stable" users who want to > pick up necessary bug fixes. Gosh, I was under the impression that every FreeBSD user was a beta tester... :) It's inevitable that bugs will be found in -stable more quickly than in -current, simply because -stable has a much larger user base. Just think back to the days after 3.0-RELEASE and the myriad of bug reports that suddenly came in because the level of usage for that code skyrocketed. Alex G. Perel -=- AP5081 alexp@iplink.net -=- (work) veers@disturbed.net -=- (play) Disturbed Networks - Powered exclusively by FreeBSD == The Power to Serve -=- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:51:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 982CC14CC3 for ; Sat, 1 May 1999 11:51:48 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id UAA35961; Sat, 1 May 1999 20:51:43 +0200 (CEST) (envelope-from des) To: "Daniel C. Sobral" Cc: Dag-Erling Smorgrav , Lars Fredriksen , current@FreeBSD.ORG Subject: Re: default route not set up?? References: <372A1AE6.4E2738D4@odin-corporation.com> <372AF60B.E11A6989@newsguy.com> <372B1E6B.263A3B19@newsguy.com> From: Dag-Erling Smorgrav Date: 01 May 1999 20:51:42 +0200 In-Reply-To: "Daniel C. Sobral"'s message of "Sun, 02 May 1999 00:31:55 +0900" Message-ID: Lines: 22 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: > Dag-Erling Smorgrav wrote: > > "Daniel C. Sobral" writes: > > > Dag-Erling Smorgrav wrote: > > > > [exerpt from /etc/rc.network] > > > Looking there, it *does* seem that there is a problem. defaultrouter > > > is only used to set route_default, which is *not* used. At least on > > > the code you quoted. > > This is getting fun :) Look closer at the first line I commented, then > > at the loop, and especially the eval. > That's tricky, indeed. You should have commented the line below the > second line, not the second line. :-) Yep. I was similarly miffed the first time I read this code, but I thought 'hey, it works, so it has to be right' and read it over until I was enlightened. I still find it slightly spaghetti. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:54:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 810B714CC3 for ; Sat, 1 May 1999 11:54:29 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup1-2.iptelecom.net.ua [212.42.68.129]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id VAA07322 for ; Sat, 1 May 1999 21:54:35 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <372B4DF4.D30F3756@altavista.net> Date: Sat, 01 May 1999 21:54:44 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Strange figures reported by i586_bzero... Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following is piece of dmesg -v output of my recent kernel (take a look at i586_bzero bandwith figures.... FreeBSD 4.0-CURRENT #1: Sat May 1 21:30:10 EEST 1999 Calibrating clock(s) ... TSC clock: 250536168 Hz, i8254 clock: 1193030 Hz Timecounter "i8254" frequency 1193030 Hz CPU: \^E (250.54-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 64M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable ..... npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = -2111561183 bytes/sec ^^^^^^^^^^^^^^^^^^^^^^- NEGASTIVE BANDWITH? IT'S INTERESTING!!! bzero() bandwidth = 186046511 bytes/sec To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:54:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id 0E97715124 for ; Sat, 1 May 1999 11:54:31 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id for ; Sat, 1 May 1999 14:54:29 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sat, 1 May 1999 11:54:27 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sat, 1 May 1999 14:54:26 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Steve Price's (sprice@hiwaay.net) message dated Sat, 01 May 1999 13:03:17. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 May 1999 14:54:26 -0400 Message-ID: <19432.925584866@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I understand it, BitKeeper is indeed based on SCCS, and is a superset of it. The performance hit of SCCS has been "solved". There are several "significant" commercial users of BitKeeper waiting for the first production release, and Larry McVoy seems to be a bit of a maniac when it comes to things being production stable. He said that a CVS->BitKeeper conversion tool is not far off. I'm mostly interested in the "lines of development" features, the ability to check in various revisions of my *local* work, the ability to apply a patch set as an atomic unit, and several of the GUI tools. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 11:55:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2E723150D7 for ; Sat, 1 May 1999 11:55:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA76437; Sat, 1 May 1999 11:52:51 -0700 (PDT) (envelope-from dillon) Date: Sat, 1 May 1999 11:52:51 -0700 (PDT) From: Matthew Dillon Message-Id: <199905011852.LAA76437@apollo.backplane.com> To: paul@originative.co.uk Cc: freebsd-current@FreeBSD.ORG Subject: Re: RE: solid NFS patch #6 avail for -current - need testers files) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> trusting 15+ years worth of source history to a program :> that has just :> barely been written. I think the Linux people are making :> a huge mistake :> by not using CVS. : :15 years? Our cvs repository is only about 5 years old and cvs isn't 15 :years old! Well, ok, this reposity only goes as far back as 4.4-lite. I was being inclusive :-) -Matt Matthew Dillon :I agree with the sentiment though :-) : :Although, if it's widely used I suspect it will stabilise much sooner than a :couple of years. If it has the required features it might be worth playing :with on the back burner to see how it shaped up. : :Paul. : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 12:17:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1956715239 for ; Sat, 1 May 1999 12:17:26 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA21451; Sat, 1 May 1999 19:50:05 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id RAA00823; Sat, 1 May 1999 17:59:19 +0200 (CEST) From: Wilko Bulte Message-Id: <199905011559.RAA00823@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <19990501092120.A13451@luke.pmr.com> from Bob Willcox at "May 1, 1999 9:21:20 am" To: bob@pmr.com Date: Sat, 1 May 1999 17:59:19 +0200 (CEST) Cc: bob@pmr.com, cjohnson@neunacht.netgsi.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ should we keep this on -current ?? ] As Bob Willcox wrote ... > On Fri, Apr 30, 1999 at 12:36:25AM +0200, Wilko Bulte wrote: > > As Bob Willcox wrote ... > > > On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote: > > > > As Bob Willcox wrote ... > > > > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > Hmm, why is that? The newest of the IBM branded Exabyte 8200's that I > > > > That is what I've been told by an Exabyte engineer years back. I can only > > guess that some OEMs need adaptations to the firmware behaviour that are > > incompatible with what the rest of the world needs (or has standardised > > on, e.g. in the ANSI SCSI standard). Again, guessing. > > Well, I can only speak for the IBM OEM'd drives that I have (as a > retired IBMer, I've been picking them up at their employee surplus > store here in Austin, TX). For these drives the generic firmware works > just fine. I can see why Exabyte wouldn't openly recommend the change > though. The hardware is probably the same, so an EPROM swap brings them to the generic model. > recall that we did have some customizations in the firmware for the > RS/6K AIX systems. In addition to changing the Inquiry command Vendor > ID data, I believe there were some functional changes (I don't recall > the details). I have always suspected that the functional changes are > likely what made the IBM OEM'd drives fail on FreeBSD! The upgraded > firmware IBM drives work on both (as "Other SCSI Tape Drive"). That is quite possible. And it matches the recommendation of the Exabyte engineer. > > Mine works OK with that f/w. Not that I use the 8200 often anymore, > > I like my DLT4000 much better than the 8200. ;-) > > I much prefer my Exabyte Mammouth drives as well :-) > > (But I do seem to get some fun out of playing with the 8200's I get for > $10 apiece from the surplus store :-) Absolutely right. And I got my DLT4000 for US$ 25 so you can guess where I got it from 8-) Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 12:35:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 076FF14BF9 for ; Sat, 1 May 1999 12:35:52 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA08996; Sun, 2 May 1999 05:35:30 +1000 Date: Sun, 2 May 1999 05:35:30 +1000 From: Bruce Evans Message-Id: <199905011935.FAA08996@godzilla.zeta.org.au> To: dg@root.com, oppermann@pipeline.ch Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... Cc: brad@shub-internet.org, FreeBSD-current@FreeBSD.ORG, grog@lemis.com, mjacob@feral.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >Linux' fsync() works only on directories, not on files. >> >> Huh? That doesn't make any sense. The "f" in fsync() stands for "file". > >It does write the file to the disk but not the inode. To get the inode >on the disk you have to fsync() the directory (which sync'ed the whole >FS before 2.0.35). Kinda stupid... fsync() can't reasonably sync everything on filesystems with async metadata. It think it should sync the file's contents and inode, but not directory entries pointing to the inode. fsync() on the directories containing the entries that you care about seems reasonable. >If you can't believe it: >http://www.ornl.gov/its/archives/mailing-lists/qmail/1998/05/threads.html#00691 No one mentioned the POSIX.1b way, perhaps because it has only been standard for 4-5 years. It has: __POSIX_FSYNC feature test macro. If this is defined, then fsync() exists and synchronizes the file to an implementation-defined stage. __POSIX_SYNCHRONIZED_IO feature test macro. If this is defined, then fsync() synchronizes to completion. Also, fdatasync() exists and synchronizes the file's contents, like Linux's fsync() does. Also, there are open flags ODSYNC, O_RSYNC and O_SYNC. O_SYNC and O_DSYNC have similar semantics to fsync() and fdatasync(). O_RSYNC is to synchronise metadata changed by reads (mainly access timestamps). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 12:49:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 8546C15124 for ; Sat, 1 May 1999 12:49:24 -0700 (PDT) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id VAA25645; Sat, 1 May 1999 21:47:30 +0200 (CEST) (envelope-from leif@neland.dk) Message-ID: <007101be940b$7994d260$0e00a8c0@swimsuit.internet.dk> From: "Leif Neland" To: "Soren Schmidt" , "Dag-Erling Smorgrav" Cc: , , References: <199905011222.OAA13123@freebsd.dk> Subject: Sv: ep0 *UTP* Date: Sat, 1 May 1999 21:47:31 +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.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Oprindelig meddelelse ----- Fra: Soren Schmidt Til: Dag-Erling Smorgrav Cc: ; ; Sendt: 1. maj 1999 14:22 Emne: Re: ep0 *UTP* > To get back to the subject, the default interface type (AUI/BNC/UTP) > are store in an EEPROM on board, this default is shown in the probe. > The default can be changed with a DOS util from 3COM. There even exists a linux util which does that. However, it doesn't run 'out of the box', but as long as my card works, I won't bother doing more about it. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 12:56:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id C08C515124 for ; Sat, 1 May 1999 12:56:46 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA26792; Sat, 1 May 1999 12:53:44 -0700 (PDT) Message-Id: <199905011953.MAA26792@implode.root.com> To: Alex Perel Cc: paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: -stable vs -current (was Re: solid NFS patch #6... ) In-reply-to: Your message of "Sat, 01 May 1999 14:47:00 EDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 01 May 1999 12:53:44 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> point, we shouldn't be merging stuff back into the -stable branch, only fix >> specific straightforward problems that don't require complete >> re-engineering. > >No new features means stagnation in development. It means that someone >coming to FreeBSD and looking for a feature will only find it in -current, >which, by virtue of being -current, will have other miscellaneous problems. >This person gets annoyed and leaves. Sorry, but this just isn't how our development model has worked over the past 6 years. -stable means it and we are not going to change that. -current is for new features. The only new features that are added to -stable are those which don't affect existing functionality and architectural changes are to be avoid as much as possible. This has been a winning model for us and we're not going to change it. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 13: 9:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8A59F14E1C for ; Sat, 1 May 1999 13:09:13 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA16891; Sat, 1 May 1999 13:08:46 -0700 Date: Sat, 1 May 1999 13:08:45 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Robert Watson Cc: Steve Price , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So will bitkeeper provide a nice interface for migrating code from an > existing and well-established CVS repository to whatever they use? They have tools for RCS to SCCS- I dunno about CVS tho... > > I'm quite happy to allow them to test bitkeeper in a production > environment before using it in one myself, needless to say. :) fair enuff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 13:10: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4903214BEE for ; Sat, 1 May 1999 13:10:03 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA16902; Sat, 1 May 1999 13:09:39 -0700 Date: Sat, 1 May 1999 13:09:38 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Harlan Stenn Cc: freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <19432.925584866@brown.pfcs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I understand it, BitKeeper is indeed based on SCCS, and is a superset of > it. The performance hit of SCCS has been "solved". > > There are several "significant" commercial users of BitKeeper waiting for > the first production release, and Larry McVoy seems to be a bit of a maniac > when it comes to things being production stable. > > He said that a CVS->BitKeeper conversion tool is not far off. Cool! > > I'm mostly interested in the "lines of development" features, the ability > to check in various revisions of my *local* work, the ability to apply a > patch set as an atomic unit, and several of the GUI tools. > Amen to that.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 13:13:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 8745614BEE for ; Sat, 1 May 1999 13:13:32 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-175.skylink.it [194.185.55.175]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA29341; Sat, 1 May 1999 22:14:32 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id VAA07441; Sat, 1 May 1999 21:18:21 +0200 (CEST) Date: Sat, 1 May 1999 21:18:21 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Jim Bloom Cc: Rick Whitesel , erik@habatech.no, freebsd-current@FreeBSD.ORG Subject: Re: Problems with ahc (2940U2W) and USB In-Reply-To: <3727AFE8.168D7178@acm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did I miss an update on this? Could you guys drop me the output of dmesg (after a boot -v if possible)? Cheers, Nick On Wed, 28 Apr 1999, Jim Bloom wrote: > Add me to the list of people seeing this problem. I have an ASUS P2B-S with > onboard Adaptec 7890. I have been seeing the problem on and off since December > of last year. One time it boots and the next time it doesn't. Once the disk is > hung, the reset switch or power cycling are the only ways to unfreeze it. > > I have seen this problem mentioned on both freebsd-current and freebsd-scsi > several times without a solution. I don't recall a link to USB being mentioned > before. > > I'll try to post my dmesg output later this tonight. > > Jim Bloom > bloom@acm.org > > > Rick Whitesel wrote: > > > > Hi: > > I am seeing the same thing on a ASUS P2B with a Adaptec 2940?? > > controller. > > > > Rick > > > > ----- Original Message ----- > > From: > > To: > > Sent: Wednesday, April 28, 1999 11:38 AM > > Subject: Problems with ahc (2940U2W) and USB > > > > With the current sources, there seems to be a problem with the Adaptec > > 2940U2W driver when using USB. > > > > Whenever I try to boot a kernel with the USB driver, the boot process > > gets to the "Waiting 15 seconds for SCSI devices to settle" and stops. > > If I compile a kernel with an nearly identical config, only the USB > > driver has been commented out, it boots all right. > > > > My computer has a Spacewalker 661 mainboard, which is a 440BX based card. > > The SCSI controller is an Adaptec 2940U2W. > > > > Kernels compiled before the integration of new-bus works fine. > > > > Now, this is not a critical situation for me, as I have no USB devices, > > but I thought someone else would want this information. > > > > Anyone else experiencing this? > > > > -- > > --------------------------------+---------------------------------------+ > > Erik H. Bakke, Habatech AS | To be or not to be... | > > E-Mail: erik@habatech.no | Is simply a question of binary logic. | > > This message was sent by XFMail | | > > --------------------------------+---------------------------------------+ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 13:39:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 76ED6150BF for ; Sat, 1 May 1999 13:39:52 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA58488; Sat, 1 May 1999 21:38:04 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 21:38:04 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: Harlan Stenn , Kevin Day , Mike Smith , david@aps-services.com, paul@originative.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <199905011724.KAA75931@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Matthew Dillon wrote: > > :BitKeeper should be ready soon. > : > :Once it's been proven stable, might it be a better alternative to CVS? > : > :H > > Maybe, but we wouldn't know for a couple of years. You don't just go > trusting 15+ years worth of source history to a program that has just > barely been written. I think the Linux people are making a huge mistake > by not using CVS. My thoughts almost exactly (I think the Linux people have already made a huge mistake and are compounding it). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 13:40:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id 7369B1527C for ; Sat, 1 May 1999 13:40:08 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (dial-35-082.easystreet.com [206.103.35.82]) by mail.easystreet.com (8.9.1/8.9.1) with SMTP id NAA14453 for ; Sat, 1 May 1999 13:40:07 -0700 (PDT) Message-ID: <012c01be9413$13cd3e60$0d787880@apex.tapang> From: "Carlos C. Tapang" To: Subject: FBSDBOOT.EXE Date: Sat, 1 May 1999 13:42:06 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there anybody out there working on upgrading fbsdboot.exe so that it can recognize ELF? Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 13:47:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id DB10814BEC for ; Sat, 1 May 1999 13:47:15 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA66235; Sat, 1 May 1999 21:46:57 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 21:46:57 +0100 (BST) From: Doug Rabson To: Zach Heilig Cc: "Jordan K. Hubbard" , Steve Kargl , John Polstra , dwhite@resnet.uoregon.edu, current@freebsd.org Subject: Re: PCM In-Reply-To: <19990501131853.A505@k6n1.znh.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Zach Heilig wrote: > I found the commit that "broke" sound (beyond that, I don't know how > to fix it): Now this is interesting. You are saying that the previous mega-commit (the new-bus one) didn't break sound? That gives us a bit more to go on. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 13:48:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 16D7C14BEC for ; Sat, 1 May 1999 13:48:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA16994; Sat, 1 May 1999 13:48:33 -0700 Date: Sat, 1 May 1999 13:48:33 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson Cc: freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > :BitKeeper should be ready soon. > > : > > :Once it's been proven stable, might it be a better alternative to CVS? > > : > > :H > > > > Maybe, but we wouldn't know for a couple of years. You don't just go > > trusting 15+ years worth of source history to a program that has just > > barely been written. I think the Linux people are making a huge mistake > > by not using CVS. > > My thoughts almost exactly (I think the Linux people have already made a > huge mistake and are compounding it). > But they are using CVS- sparclinux has been under anon CVS for years. The problem with CVS is that it *just doesn't work* if you try and have truly separate development streams. Branches and corrupted trees and directory renames are as pleasant and easy in CVS as trying to deal with Charles Hannum and Jason Thorpe in NetBSD (crazed weasels on angel dust going for your nether body parts is a comparative tickle). And don't even *begin* to talk about merging... Don't get me wrong- *I* like CVS and how it's used for FreeBSD right now. But if you begin to have separate branch development models and want to really have a flexible source tree that you can repartition and repackage at will, CVS is not your friend. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 14: 3:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id A792A14BEC for ; Sat, 1 May 1999 14:03:21 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA66278; Sat, 1 May 1999 22:02:41 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 22:02:41 +0100 (BST) From: Doug Rabson To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Matthew Jacob wrote: > > > > > > > > :BitKeeper should be ready soon. > > > : > > > :Once it's been proven stable, might it be a better alternative to CVS? > > > : > > > :H > > > > > > Maybe, but we wouldn't know for a couple of years. You don't just go > > > trusting 15+ years worth of source history to a program that has just > > > barely been written. I think the Linux people are making a huge mistake > > > by not using CVS. > > > > My thoughts almost exactly (I think the Linux people have already made a > > huge mistake and are compounding it). > > > > But they are using CVS- sparclinux has been under anon CVS for years. > > The problem with CVS is that it *just doesn't work* if you try and have > truly separate development streams. Branches and corrupted trees and > directory renames are as pleasant and easy in CVS as trying to deal > with Charles Hannum and Jason Thorpe in NetBSD (crazed weasels on > angel dust going for your nether body parts is a comparative tickle). And > don't even *begin* to talk about merging... > > Don't get me wrong- *I* like CVS and how it's used for FreeBSD right now. > But if you begin to have separate branch development models and want to > really have a flexible source tree that you can repartition and repackage > at will, CVS is not your friend. I agree about CVS' limitations completely. I know that a lot of Linux projects are under their own CVS control but what kind of history is available for code once it reaches Linus? Does Linus have a CVS repository which stores file-by-file history for the kernel? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 14: 7:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 16B5114BEC for ; Sat, 1 May 1999 14:07:33 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA17074; Sat, 1 May 1999 14:07:15 -0700 Date: Sat, 1 May 1999 14:07:14 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson Cc: freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I agree about CVS' limitations completely. I know that a lot of Linux > projects are under their own CVS control but what kind of history is > available for code once it reaches Linus? Does Linus have a CVS > repository which stores file-by-file history for the kernel? No. That's what Bitkeeper and some of the retroactive release stream reconstruction that Larry's been doing is about. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 14:13:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 240EA15140 for ; Sat, 1 May 1999 14:13:32 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA66314; Sat, 1 May 1999 22:13:22 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 22:13:21 +0100 (BST) From: Doug Rabson To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Matthew Jacob wrote: > > > I agree about CVS' limitations completely. I know that a lot of Linux > > projects are under their own CVS control but what kind of history is > > available for code once it reaches Linus? Does Linus have a CVS > > repository which stores file-by-file history for the kernel? > > No. That's what Bitkeeper and some of the retroactive release stream > reconstruction that Larry's been doing is about. That sounds like it would be time well spent. I like the sound of Bitkeeper a lot. I just want someone else to test it :-). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 14:16:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id F259F15140 for ; Sat, 1 May 1999 14:16:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA17093; Sat, 1 May 1999 14:16:04 -0700 Date: Sat, 1 May 1999 14:16:03 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson Cc: freebsd-current@FreeBSD.ORG Subject: Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That sounds like it would be time well spent. I like the sound of > Bitkeeper a lot. I just want someone else to test it :-). You and everyone else! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 14:21:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 58A7115140 for ; Sat, 1 May 1999 14:21:19 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA66352; Sat, 1 May 1999 22:20:58 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 22:20:58 +0100 (BST) From: Doug Rabson To: Zach Heilig Cc: "Jordan K. Hubbard" , Steve Kargl , John Polstra , dwhite@resnet.uoregon.edu, current@freebsd.org Subject: Re: PCM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Doug Rabson wrote: > On Sat, 1 May 1999, Zach Heilig wrote: > > > I found the commit that "broke" sound (beyond that, I don't know how > > to fix it): > > Now this is interesting. You are saying that the previous mega-commit (the > new-bus one) didn't break sound? That gives us a bit more to go on. I have managed to reproduce the problem with some old hardware. I have to rearrange things a bit to debug it but I'll see what I can do tomorrow. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 14:50:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 5282014CB0 for ; Sat, 1 May 1999 14:50:47 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id WAA80177 for freebsd.org!current; Sat, 1 May 1999 22:50:46 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 1 May 1999 22:48:32 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 1 May 1999 22:48:29 +0000 To: current@freebsd.org From: Bob Bishop Subject: if_xl.c noise Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Does version 1.34 of if_xl.c really look like the following around line 1886, or is my repository hosed? <<<<<<< if_xl.c /* * Force longword alignment for packet payload for all cpus. This * will optimize NFS ops which have to realign unaligned buffers. */ ======= /* Force longword alignment for packet payload. */ >>>>>>> 1.34 m_new->m_data += 2; <<<<<<< if_xl.c ======= >>>>>>> 1.34 c->xl_mbuf = m_new; c->xl_ptr->xl_status = 0; c->xl_ptr->xl_frag.xl_addr = vtophys(mtod(m_new, caddr_t)); c->xl_ptr->xl_frag.xl_len = MCLBYTES | XL_LAST_FRAG; return(0); -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 14:59: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id A283C14D11 for ; Sat, 1 May 1999 14:59:04 -0700 (PDT) (envelope-from brad@mail.his.com) Received: from [195.238.23.26] (dialup26.brussels2.skynet.be [195.238.23.26]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with SMTP id XAA02240; Sat, 1 May 1999 23:58:21 +0200 (MET DST) In-Reply-To: <19990501152523.H80561@freebie.lemis.com> X-Mailer: CTM PowerMail 2.4 x-sender: brad@mail.his.com Date: Sat, 1 May 1999 22:02:57 +0200 To: Greg Lehey , Matthew Jacob Cc: FreeBSD current users From: Brad Knowles Subject: Re: Linux char devices (was: Porting Greg Lehey's rawio.c from FreeBSD to Linux...) Message-Id: <19990501220257.001997@relay.skynet.be> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 1, 1999, Greg Lehey wrote: >On Friday, 30 April 1999 at 21:25:12 -0700, Matt Jacob wrote: >> There are no raw devices in Linux. Linus is totally against them as >> stupid. Linus has some good points about this, but it's still an, um, >> interesting stance. > >It also makes it impossible for rawio to run accurately. rawio >measures device throughput, not system throughput. Cache the data and >you completely lose this ability (hey! Under Vinum, an array of four >floppies has a random read throughput of 50 MB/s!). It also makes it rather hard for programs like Oracle or Sybase to run and use raw devices for their databases, so you instead wind up polluting your buffer cache no matter what. As I understand it, the Oracle guys finally pounded into his brain the importance of real raw device access, and they are starting to take some steps towards fixing this problem in 2.2.x. Anyway, a friend of mine just yesterday actually got rawio.c to work under Linux. He ended up having to make some changes to rawio, as well as some changes to the way mmap() is implemented. Let me quote his entire message on this subject: >On Fri, Apr 30, 1999 at 03:37:03PM +0200, Brad Knowles wrote: >> Anyway, if there's anyone out there with any experience in porting >> programs that do low-level disk I/O, I'd appreciate it if you could take >> a look at this program and give me some pointers on what it would take to >> get it to compile and run under Linux (specifically, Debian Linux with >> kernel 2.2.6). > > > >Ok, I decided to work on this a bit and I had no idea the trouble I'd run >into.... I ported rawio to Red Hat Linux 5.2 pretty easily--it took about >fifteen minutes. Here's a summary of changes: > >a few more #includes (sys/ioctl.h, among others) >swap out the BSD disklabel.h for linux/genhd.h and rename struct disklabel > to struct bsd_disklabel (from linux/genhd.h) >add srandomdev() from FreeBSD sources >delete MAP_INHERIT from mmap()--no exec's in the program, so not useful-- > good thing, because linux doesn't support it > >This wasn't too bad. Then I tried to run it and got the "Can't mmap shared >memory: Invalid argument" message. Aargh. It works fine under OpenBSD. >After perusing the mmap() man pages, I think that everything's ok. I run >rawio with strace and find this: > >mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = \ > 0x40100000 >... >mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_ANONYMOUS, -1, 0) = -1 \ > EINVAL >_exit(1) > >I think, "Huh. mmap() with the MAP_PRIVATE flag works fine. mmap() with >the MAP_SHARED flag returns EINVAL. That's dumb." I check the man page >again and look at the reasons for EINVAL--nothing different if it's private >or shared. So, I figure it is a kernel bug and check out the kernel source >for mmap. Sure enough, in some function do_mmap(): > >if (file != NULL) { >... >} else if ((flags & MAP_TYPE) != MAP_PRIVATE) > return -EINVAL; > >So (on a development/test/guinea pig/sacrificial lamb machine) I remove this >offensive bit of code, recompile the kernel, reboot, and voila, rawio can >actually communicate between the parent and the child processes, just like >it should have been able to in the first place. > >Of course, now I wonder why this code was there in the first place.... I'm >not so expert a kernel hacker that I can definitively say that this is a >ridiculous bit of of non-logic, but it sure did interfere with rawio.... > > > >Anyway, I half ported it to Linux and half ported Linux to the rest of the >world. You can get the patches at: > >ftp://mvhs1.mbhs.edu/pub/linux/linux-2.2.5-mmap.patch (kernel patch) >ftp://mvhs1.mbhs.edu/pub/linux/rawio-linux.patch (patch to author src) >ftp://mvhs1.mbhs.edu/pub/linux/rawio-linux.tar.gz (patched srcs) >ftp://mvhs1.mbhs.edu/pub/linux/rawio.tar.gz (author src) > >Now you can run your benchmark tests against buffered device files to your >heart's content. :) > >P.S. Keep in mind that you'll have to specify the device size manually. On >BSD, rawio can read the disklabel and get the size from there. I didn't go >to the trouble of reimplementing the device size for ext2fs labels. So, >unless you are running rawio under Linux against a BSD disk, the disklabel >code won't help you much. ;) >-- >Matt Shibla mshibla@mbhs.edu (301) 649-2880 (vox) (301) 649-2830 (fax) > Maryland Virtual High School Montgomery Blair High School > 51 University Boulevard East Silver Spring, MD 20901 >PGP Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x8918CBCD I don't suppose anyone here knows why this piece of do_mmap() is written this particular way, and if there's any harm in removing that code? TIA! -- Brad Knowles Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 14:59:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 048EC152F0 for ; Sat, 1 May 1999 14:59:30 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA07992; Sat, 1 May 1999 17:59:27 -0400 From: Bill Paul Message-Id: <199905012159.RAA07992@skynet.ctr.columbia.edu> Subject: Re: if_xl.c noise To: rb@gid.co.uk (Bob Bishop) Date: Sat, 1 May 1999 17:59:26 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: from "Bob Bishop" at May 1, 99 10:48:29 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1152 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Bob Bishop had to walk into mine and say: > Hi, > > Does version 1.34 of if_xl.c really look like the following around line > 1886, or is my repository hosed? You could have answered this yourself by checking in /pub/FreeBSD/FreeBSD-current/src/sys/pci/if_xl.c on ftp.cdrom.com. Yes, this is only your repository; you must be using some patches from Matt Dillon for NFS. The code in -current has the change that he made already in it (but with a different comment). Grab a fresh copy of if_xl.c and if_xlreg.h from -current and stick with it. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 15:50:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id D995A14D11 for ; Sat, 1 May 1999 15:50:31 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id XAA80645; Sat, 1 May 1999 23:50:30 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 1 May 1999 23:40:34 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199905012159.RAA07992@skynet.ctr.columbia.edu> References: from "Bob Bishop" at May 1, 99 10:48:29 pm Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 1 May 1999 23:40:31 +0000 To: Bill Paul From: Bob Bishop Subject: Re: if_xl.c noise Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 5:59 pm -0400 1/5/99, Bill Paul wrote: >[...]>Yes, this is only your repository; you must be using some patches >from Matt Dillon for NFS. Argh. Pointy hat please - didn't notice "C src/sys/pci/if_xl.c" staring me in the face. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 15:58:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from ftp.dns.ne.jp (ftp.dns.ne.jp [210.155.3.5]) by hub.freebsd.org (Postfix) with ESMTP id 8B95F14E52 for ; Sat, 1 May 1999 15:58:11 -0700 (PDT) (envelope-from tanimura@sakuramail.com) Received: from silver.carrots (yksk5DS01.kng.mesh.ad.jp [210.147.34.139]) by ftp.dns.ne.jp (8.9.2/8.8.5) with ESMTP id HAA23197; Sun, 2 May 1999 07:57:43 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by silver.carrots (8.9.3+3.1W/3.7W) with ESMTP id HAA62892; Sun, 2 May 1999 07:57:51 +0900 (JST) To: freebsd-current@freebsd.org Cc: Seigo TANIMURA Subject: apmconf(8) -e ends to panic in apm_bios_call From: Seigo TANIMURA X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990502075751N.tanimura@sakuramail.com> Date: Sun, 02 May 1999 07:57:51 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 49 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! When I cvsuped, made and installed the new world and kernel on 1st May 1999, the kernel paniced in apm_bios_call called from apmconf(8) -e... [sys/i386/apm/apm_setup.s:_apm_bios_call] movl 8(%ebp),%ecx movl 4(%ebp),%ebx movl 0(%ebp),%eax pushl %ebp lcall _apm_addr <--- paniced here popl %ebp movl %eax,0(%ebp) Strangely, the kernel attaches the APM BIOS without any problem at all. [a part of /var/log/messages with APM_DEBUG] May 1 14:15:20 silver /kernel: apm0: on motherboard May 1 14:15:20 silver /kernel: apm: APM BIOS version 0102 May 1 14:15:20 silver /kernel: apm: Code32 0xc00f0000, Code16 0xc00f0000, Data 0xc00fdbd0 May 1 14:15:20 silver /kernel: apm: Code entry 0x000078a8, Idling CPU disabled, Management enabled May 1 14:15:20 silver /kernel: apm: CS32_limit=0x1e, CS16_limit=0x1e, DS_limit=0x66ae May 1 14:15:20 silver /kernel: apm: Engaged control enabled May 1 14:15:20 silver /kernel: apm: found APM BIOS version 1.2 May 1 14:15:20 silver /kernel: apm: Slow Idling CPU disabled May 1 14:15:20 silver /kernel: Add hook "default suspend" May 1 14:15:20 silver /kernel: Add hook "default resume" May 1 14:15:20 silver /kernel: called apm_event_enable() On attaching, apm_event_enable() calls apm_bios_call successfully. I traced to watch _apm_addr, which pointed the correct entry(0x000078a8) in both situations. The only one difference was CS... Has anyone got a clue? Thanks in advance! Seigo TANIMURA |M2, Nakagawa Lab, Dept of Electronics & CS =========================|Faculty of Engineering, Yokohama National Univ Powered by SIEMENS, |http://www.naklab.dnj.ynu.ac.jp/~tanimura/ FreeBSD 4.0-CURRENT |http://www.sakura.ne.jp/~tcarrot/ (25th Apr 1999) & muesli.|tanimura@naklab.dnj.ynu.ac.jp tcarrot@sakuramail.com VoxWare Midi Driver for Serial Ports on FreeBSD: http://www.naklab.dnj.ynu.ac.jp/~tanimura/freebsd-serialmidi/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 16:46:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B5F8415197 for ; Sat, 1 May 1999 16:46:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA83189; Sat, 1 May 1999 16:46:23 -0700 (PDT) (envelope-from dillon) Date: Sat, 1 May 1999 16:46:23 -0700 (PDT) From: Matthew Dillon Message-Id: <199905012346.QAA83189@apollo.backplane.com> To: Bill Paul Cc: rb@gid.co.uk (Bob Bishop), current@FreeBSD.ORG Subject: Re: if_xl.c noise References: <199905012159.RAA07992@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :You could have answered this yourself by checking in :/pub/FreeBSD/FreeBSD-current/src/sys/pci/if_xl.c on ftp.cdrom.com. :Yes, this is only your repository; you must be using some patches :from Matt Dillon for NFS. The code in -current has the change that :he made already in it (but with a different comment). Grab a fresh :copy of if_xl.c and if_xlreg.h from -current and stick with it. : :-Bill He probably did. I meant to remove those from my NFS stuff... they're gone now. Hopefully the NFS patches ( non-inclusive of the xl stuff ) will be committed soon. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 17:17:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (Postfix) with ESMTP id E5CFE15244 for ; Sat, 1 May 1999 17:17:16 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id SAA20140; Sat, 1 May 1999 18:16:48 -0600 (MDT) (envelope-from drussell@saturn-tech.com) Date: Sat, 1 May 1999 18:16:48 -0600 (MDT) From: Doug Russell To: Matthew Thyer Cc: freebsd-current@FreeBSD.ORG Subject: Re: silo overflows in CURRENT ... some info that may help In-Reply-To: <372B3CBF.5E524469@camtech.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 May 1999, Matthew Thyer wrote: > I have been investigating the silo overflow situation for some time. > > I can trigger them every time by the following action: > > - Run M.A.M.E. (Multi arcade machine emulator) and then try to > download something. (I am using user mode ppp). Can you nice M.A.M.E. slightly? Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 17:31:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 10B6615292 for ; Sat, 1 May 1999 17:31:50 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA21369; Sat, 1 May 1999 17:31:29 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: Steve Price , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Sat, 01 May 1999 11:22:33 PDT." Date: Sat, 01 May 1999 17:31:29 -0700 Message-ID: <21365.925605089@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Look- if Linux adopts Bitkeeper, you really should pay attention to that. > I doubt you'd find a more difficult set of software engineers to keep code > in sync for than the Linux folks- if Bitkeeper works for them and > essentially makes a rational release train for Linux, then a major > glaring flaw in Linux' strategy that keeps serious businesses from really > being able to trust it will be removed. Think about it. I think this all fails to address the distribution problem, however. Let's say we adopt bitkeeper - what becomes of CTM, CVSup and CVSWeb, all interfaces in extremely common use today? It's not just enough to say "something will be worked out" as an answer either, not when contemplating a move which will remove services currently in heavy operational use. Think about it. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 17:46:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4A57815292 for ; Sat, 1 May 1999 17:46:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA19221; Sat, 1 May 1999 17:45:51 -0700 Date: Sat, 1 May 1999 17:45:44 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: Steve Price , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <21365.925605089@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Look- if Linux adopts Bitkeeper, you really should pay attention to that. > > I doubt you'd find a more difficult set of software engineers to keep code > > in sync for than the Linux folks- if Bitkeeper works for them and > > essentially makes a rational release train for Linux, then a major > > glaring flaw in Linux' strategy that keeps serious businesses from really > > being able to trust it will be removed. Think about it. > > I think this all fails to address the distribution problem, however. > Let's say we adopt bitkeeper - what becomes of CTM, CVSup and CVSWeb, > all interfaces in extremely common use today? It's not just enough to > say "something will be worked out" as an answer either, not when > contemplating a move which will remove services currently in heavy > operational use. Think about it. :) I'll try, but it hurts my head ("Why, Ale, man! Ale's the stuff to drink, for them whom it hurts to think!"...) I wasn't suggesting that we jump..I would like to see a plan. I believe BitKeeper and other tools are a good set of tools for the next 5-10 years for *development*. *Distribution* is a separate issue. Again, CVS is a fine tool for distribution and asymmetric (biased toward a higher level of outbound source changes) development. It all depends on what we want. And I'll have to admit that distribution of binaries && source is not something that always is on the top of my list (well, *I'm* not working for a software distribution company...:-)).. My comment about 'think about it' is that if Linux gets it's chaotic source non-management corrected and is able to successfully coordinate all the relatively anarchic and free running clock different groups then the 'predictability and reproducibility' concerns of commercial buyers are closer to being met (which is silly because of how really chaotic internal company release spasms are, SGI being a notorious example- but there it is). If FreeBSD (and NetBSD and OpenBSD) are to continue the way it is now, CVS is probably a good enough tool. However, if you incorporate something like BitKeeper into the picture, then it actually becomes technically more feasible to even begin *considering* a *BSD coordination- you start to have to toolset that can manage large amounts of code that is mostly alike but differs in enough ways to be too hard to just merge this week. But then again you might say, "Pshaw- Matt's been smokin' some serious rope again"..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 17:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7FD0B14CB0 for ; Sat, 1 May 1999 17:54:25 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA21508; Sat, 1 May 1999 17:54:26 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Carlos C. Tapang" Cc: freebsd-current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Sat, 01 May 1999 13:42:06 PDT." <012c01be9413$13cd3e60$0d787880@apex.tapang> Date: Sat, 01 May 1999 17:54:26 -0700 Message-ID: <21504.925606466@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there anybody out there working on upgrading fbsdboot.exe so that it can > recognize ELF? I believe that fbsdboot.exe has, instead, simply been retired. Sorry I don't have better news than this. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 17:56:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from mhub2.tc.umn.edu (mhub2.tc.umn.edu [128.101.131.42]) by hub.freebsd.org (Postfix) with ESMTP id 99DF514CB0 for ; Sat, 1 May 1999 17:56:19 -0700 (PDT) (envelope-from adkin003@tc.umn.edu) Received: from pub56k-22-12.dialup.umn.edu by mhub2.tc.umn.edu for current@freebsd.org; Sat, 1 May 1999 19:56:17 -0500 Date: Sat, 1 May 1999 19:56:14 -0500 (CDT) From: dave adkins To: current@freebsd.org Subject: mem.c v1.57 and mp_machdep.c v1.99 and kernel panic Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kernels built with these panic at mem_range_AP_init() on a dual pentium system. The cvs log entries for mem.c and mp_machdep.c, v1.57 and v1.99 respectively, indicate that the hook (mem_range_softc.mr_op->initAP()) is for the i686 and seems to have NULL entry for a pentium. dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 18: 9:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from phobos.walker.dom (pmd-33.ior.com [206.107.145.225]) by hub.freebsd.org (Postfix) with ESMTP id 6917D1500F for ; Sat, 1 May 1999 18:09:56 -0700 (PDT) (envelope-from kew@timesink.spk.wa.us) Received: from timesink.spk.wa.us (localhost.walker.dom [127.0.0.1]) by phobos.walker.dom (8.9.3/8.9.3) with ESMTP id SAA00599; Sat, 1 May 1999 18:09:34 -0700 (PDT) (envelope-from kew@timesink.spk.wa.us) Message-ID: <372BA5CE.CD669D4E@timesink.spk.wa.us> Date: Sat, 01 May 1999 18:09:34 -0700 From: Keith Walker X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > David O'Brien wrote: > > > Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one > > has posted a bug report related to them, there is an option to turn > > them off, and this *is* -CURRENT. I may just leave them turned on by > > default. > > > > Opinions? > > I think that's the best solution for now. > Especially since the bug that may be caused by vtable thunks is greatly outweighed by the Bug Of Not Working At All :-) -- Keith Walker, Spokane, WA FreeBSD 4.0-CURRENT (ASUS) #39: Sat May 1 17:47:40 PDT 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 18:14:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 5214A14FE3 for ; Sat, 1 May 1999 18:14:08 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id VAA10659; Sat, 1 May 1999 21:13:47 -0400 (EDT) Message-Id: <199905020113.VAA10659@cs.rpi.edu> To: "Jordan K. Hubbard" Cc: "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: FBSDBOOT.EXE In-Reply-To: Message from "Jordan K. Hubbard" of "Sat, 01 May 1999 17:54:26 PDT." <21504.925606466@zippy.cdrom.com> Date: Sat, 01 May 1999 21:13:46 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Won't fbsdboot.exe be able to boot /boot/loader? (maybe I am just naive) (or could it be modified to do so with little effort?) -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 18:57:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6599814CC3 for ; Sat, 1 May 1999 18:57:43 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA21791; Sat, 1 May 1999 18:57:41 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: Steve Price , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-reply-to: Your message of "Sat, 01 May 1999 17:45:44 PDT." Date: Sat, 01 May 1999 18:57:40 -0700 Message-ID: <21787.925610260@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I'm not philosophically opposed to a clearly superior solution, I simply don't want to see us make any moves which involve so many messy trade-offs that we end up wasting more time embroiled in debate than we save with the new tool. My suggestion would be to wait and see how bitkeeper pans out. Enough people in the Linux camp have already looked at CVSup and gone "ooh, sexy!" that I think there will already be significant pressure to develop similar tools for the bitkeeper environment. When that happens, we can start to look at this more seriously. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 19: 8:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9FB3C14CA3 for ; Sat, 1 May 1999 19:08:31 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA01049; Sat, 1 May 1999 19:08:21 -0700 Date: Sat, 1 May 1999 19:08:21 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: Steve Price , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <21787.925610260@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I'm not philosophically opposed to a clearly superior solution, > I simply don't want to see us make any moves which involve so many > messy trade-offs that we end up wasting more time embroiled in debate > than we save with the new tool. > > My suggestion would be to wait and see how bitkeeper pans out. Enough > people in the Linux camp have already looked at CVSup and gone "ooh, > sexy!" that I think there will already be significant pressure to > develop similar tools for the bitkeeper environment. When that > happens, we can start to look at this more seriously. Well, that's fine too, then... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 19: 9:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id AE27E150B0 for ; Sat, 1 May 1999 19:09:07 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA21842; Sat, 1 May 1999 19:09:05 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "David E. Cross" Cc: "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Sat, 01 May 1999 21:13:46 EDT." <199905020113.VAA10659@cs.rpi.edu> Date: Sat, 01 May 1999 19:09:05 -0700 Message-ID: <21838.925610945@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Won't fbsdboot.exe be able to boot /boot/loader? (maybe I am just naive) > (or could it be modified to do so with little effort?) Good question - you tell me. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 19:15:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0CA52151A0 for ; Sat, 1 May 1999 19:15:14 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA15976 for freebsd-current@FreeBSD.ORG; Sun, 2 May 1999 04:15:13 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 23EBC8840; Sun, 2 May 1999 01:52:17 +0200 (CEST) (envelope-from roberto) Date: Sun, 2 May 1999 01:52:16 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) Message-ID: <19990502015216.A915@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: ; from Matthew Jacob on Sat, May 01, 1999 at 11:22:33AM -0700 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Matthew Jacob: > Bitkeeper is a substantial improvement over CVS and Perforce. It's really WHat are the improvements compared to Perforce ? I've begun looking at it and if we forgot the Open Source argument (one that the FreeBSD project can't forget), it is really a very nice SCM. They even give free licenses to people writing/maintaining free software. I know, I just got mine. User name: roberto Client name: dotfiles Client root: /users/staff/roberto Current directory: /tmp Client address: 193.56.58.65:2838 Server address: keltia.freenix.fr:1666 Server root: /work/p4home Server version: P4D/FREEBSD/99.1/10314 (1999/03/31) Server license: Robert Ollivier 10 users on freebsd (support ends 2000/04/26) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 19:15:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 18D141518C for ; Sat, 1 May 1999 19:15:17 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA15978 for freebsd-current@FreeBSD.ORG; Sun, 2 May 1999 04:15:17 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E29F28840; Sun, 2 May 1999 01:52:51 +0200 (CEST) (envelope-from roberto) Date: Sun, 2 May 1999 01:52:51 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) Message-ID: <19990502015251.B915@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19432.925584866@brown.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <19432.925584866@brown.pfcs.com>; from Harlan Stenn on Sat, May 01, 1999 at 02:54:26PM -0400 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Harlan Stenn: > I'm mostly interested in the "lines of development" features, the ability > to check in various revisions of my *local* work, the ability to apply a > patch set as an atomic unit, and several of the GUI tools. Perforce has all that. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 19:29:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E585414CB0 for ; Sat, 1 May 1999 19:29:31 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA27300; Sun, 2 May 1999 11:59:29 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA02010; Sun, 2 May 1999 11:59:24 +0930 (CST) Date: Sun, 2 May 1999 11:59:24 +0930 From: Greg Lehey To: "Jordan K. Hubbard" Cc: "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE Message-ID: <19990502115923.V80561@freebie.lemis.com> References: <012c01be9413$13cd3e60$0d787880@apex.tapang> <21504.925606466@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <21504.925606466@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, May 01, 1999 at 05:54:26PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 1 May 1999 at 17:54:26 -0700, Jordan K. Hubbard wrote: >> Is there anybody out there working on upgrading fbsdboot.exe so that it can >> recognize ELF? > > I believe that fbsdboot.exe has, instead, simply been retired. Sorry > I don't have better news than this. Does this mean that install.bat will disappear as well? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 19:32:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 925D814CB0 for ; Sat, 1 May 1999 19:32:46 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA01132; Sat, 1 May 1999 19:32:42 -0700 Date: Sat, 1 May 1999 19:32:37 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Ollivier Robert Cc: freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <19990502015216.A915@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, very well, I'll have to say Perforce isn't that bad- it's just that it doesn't have a snappy set of tcl/tk GUI tools that allow you look at whole branch and revision histories.. It doesn't have a 3-way filemerge tool (I still fire up teamware (what NSElite became) to do heavy merging and use the automerge feature)... Perforce *does* have the disparate release stream feature, but I have found it somewhat difficult to use. Perhaps if I'd actually had the depot locally I'd feel more at home with it.... > > Bitkeeper is a substantial improvement over CVS and Perforce. It's really > > WHat are the improvements compared to Perforce ? I've begun looking at it and > if we forgot the Open Source argument (one that the FreeBSD project can't > forget), it is really a very nice SCM. > > They even give free licenses to people writing/maintaining free software. I > know, I just got mine. > > User name: roberto > Client name: dotfiles > Client root: /users/staff/roberto > Current directory: /tmp > Client address: 193.56.58.65:2838 > Server address: keltia.freenix.fr:1666 > Server root: /work/p4home > Server version: P4D/FREEBSD/99.1/10314 (1999/03/31) > Server license: Robert Ollivier 10 users on freebsd (support ends 2000/04/26) > > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 19:32:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 883F515331 for ; Sat, 1 May 1999 19:32:50 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA21966; Sat, 1 May 1999 19:32:41 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Greg Lehey Cc: "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Sun, 02 May 1999 11:59:24 +0930." <19990502115923.V80561@freebie.lemis.com> Date: Sat, 01 May 1999 19:32:41 -0700 Message-ID: <21963.925612361@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does this mean that install.bat will disappear as well? It already did. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 20: 6:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles513.castles.com [208.214.165.77]) by hub.freebsd.org (Postfix) with ESMTP id 2833215182 for ; Sat, 1 May 1999 20:06:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA01716; Sat, 1 May 1999 20:05:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905020305.UAA01716@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dave adkins Cc: current@freebsd.org Subject: Re: mem.c v1.57 and mp_machdep.c v1.99 and kernel panic In-reply-to: Your message of "Sat, 01 May 1999 19:56:14 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 May 1999 20:05:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whoops, fixed. Sorry about that. > Kernels built with these panic at mem_range_AP_init() on a dual > pentium system. The cvs log entries for mem.c and mp_machdep.c, > v1.57 and v1.99 respectively, indicate that the hook > (mem_range_softc.mr_op->initAP()) is for the i686 and seems to have > NULL entry for a pentium. > > dave adkins > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 20: 7:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles513.castles.com [208.214.165.77]) by hub.freebsd.org (Postfix) with ESMTP id B2652152FA for ; Sat, 1 May 1999 20:07:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA01733; Sat, 1 May 1999 20:06:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905020306.UAA01733@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" Cc: "Jordan K. Hubbard" , "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Sat, 01 May 1999 21:13:46 EDT." <199905020113.VAA10659@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 May 1999 20:06:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Won't fbsdboot.exe be able to boot /boot/loader? (maybe I am just naive) > (or could it be modified to do so with little effort?) We've had this discussion. No. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 20: 8:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 2F5D815182 for ; Sat, 1 May 1999 20:08:33 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA27464; Sun, 2 May 1999 12:38:32 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA02222; Sun, 2 May 1999 12:38:31 +0930 (CST) Date: Sun, 2 May 1999 12:38:31 +0930 From: Greg Lehey To: Glenn Johnson Cc: current@FreeBSD.ORG Subject: Re: IDE DMA timeouts (was: Kernel won't boot from IDE disk) Message-ID: <19990502123831.Y80561@freebie.lemis.com> References: <19990429101043.A7734@symbion.srrc.usda.gov> <19990430140500.E80561@freebie.lemis.com> <19990430104939.A89475@symbion.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990430104939.A89475@symbion.srrc.usda.gov>; from Glenn Johnson on Fri, Apr 30, 1999 at 10:49:39AM -0500 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 30 April 1999 at 10:49:39 -0500, Glenn Johnson wrote: > On Fri, Apr 30, 1999 at 02:05:00PM +0930, Greg Lehey wrote: >> On Thursday, 29 April 1999 at 10:10:43 -0500, Glenn Johnson wrote: >>> I am doing a fresh installation. I installed the April 23, 1999 snapshot >>> of STABLE and then cvsupped the CURRENT source (4.0 CURRENT). >>> ... >>> Upon reboot, the system would hang after doing all of the probes. Below is some >>> of the output that I got from a boot -v. I wrote this down on paper, so the >>> formatting may be a little off. >>> >>> isa_compat: didn't get drq for wdc1 >>> ... >>> changing root device to wd0s1a >>> >>> At this point it hangs. But if I press a key on the keyboard I then get: >>> wd0s1: type 0xa5, start 0, end = 3173183, size 3173184 >>> wd0s1: C/H/S end 197/132/63 (1659041) != end 3173183: invalid >>> start_init: trying /sbin/init >>> wd0: interrupt timeout (status 50 error 0) >>> wd0: wdtimeout() DMA status 4 >>> >>> This last two lines above are repeated 5x, then I get: >>> >>> wd0: Last time I say: interrupt timeout. Probably a portable PC. >>> >>> It is a desktop PC. I am not at the system now, so the following is from >>> memory. It is an AMI BIOS, a Western Digital 1.6 GB IDE drive on the >>> primary IDE and a Mitsumi 4x CD-ROM drive on the secondary IDE. >> >> What's your chipset? If it's an SiS 5591, I'd be interested in seeing >> your complete dmesg output (preferably with a -v output). You'll also >> be able to get it to work by changing the wdc0 flags to eliminate DMA. > > The IDE controller chip is an Intel PIIX3 Bus Master IDE controller. I > did turn off all flags, via boot -c, then deleting the flags. That did > not help. Ah, OK. Not the problem I was afraid of. Sorry, I can't help on this one. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 21:47:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id 5D75D14E1A for ; Sat, 1 May 1999 21:47:36 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Sun, 2 May 1999 00:47:27 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 1 May 1999 21:47:25 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 2 May 1999 00:47:24 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert Cc: freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Ollivier Robert's (roberto@keltia.freenix.fr) message dated Sun, 02 May 1999 01:52:51. <19990502015251.B915@keltia.freenix.fr> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 May 1999 00:47:24 -0400 Message-ID: <1545.925620444@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The folks who did BitKeeper have a "compare/contrast" section in their web page that talks about BitKeeper vs. CVS and Perforce. I'm running CVS at several places, and I'm going to try BitKeeper for a couple of projects. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 22:58:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ftp.dns.ne.jp (ftp.dns.ne.jp [210.155.3.5]) by hub.freebsd.org (Postfix) with ESMTP id 5451C15330; Sat, 1 May 1999 22:58:49 -0700 (PDT) (envelope-from tanimura@sakuramail.com) Received: from silver.carrots (yksk3DS17.kng.mesh.ad.jp [210.147.34.63]) by ftp.dns.ne.jp (8.9.2/8.8.5) with ESMTP id OAA11689; Sun, 2 May 1999 14:58:15 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by silver.carrots (8.9.3+3.1W/3.7W) with ESMTP id OAA76025; Sun, 2 May 1999 14:58:25 +0900 (JST) To: nox@jelal.kn-bremen.de Cc: tanimura@naklab.dnj.ynu.ac.jp, zinnia@jan.ne.jp, freebsd-current@freebsd.org, freebsd-multimedia@freebsd.org Subject: Re: Call for Review: Voxware midi driver for serial ports From: Seigo TANIMURA In-Reply-To: Your message of "Sun, 2 May 1999 02:15:00 +0200" <19990502021500.A3181@saturn.kn-bremen.de> References: <19990502021500.A3181@saturn.kn-bremen.de> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990502145825Y.tanimura@sakuramail.com> Date: Sun, 02 May 1999 14:58:25 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 75 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Juergen Lock Subject: Re: Call for Review: Voxware midi driver for serial ports Date: Sun, 2 May 1999 02:15:00 +0200 Message-ID: <19990502021500.A3181@saturn.kn-bremen.de> nox> On Tue, Apr 20, 1999 at 10:27:35AM +0900, Seigo TANIMURA wrote: nox> > On Sun, 18 Apr 1999 22:15:05 +0200, nox> > Juergen Lock said: nox> > nox> > >> Another bad news, I tried driving my SC-88 connected directly to a PC using nox> > >> Windows 95 and Portman PC/S driver, to find a miserable result. I saw no midi nox> > >> messages come properly, so Portman PC/S should be cooking the signals in some way... nox> > nox> > nox> Or uses a higher speed than 38k4, can you check that? Hmm, or maybe nox> > nox> i should just take my old Atari MSTe and use that as serial<->midi nox> > nox> interface... nox> > nox> > nox> > Bitrate > 38.4k... I wish I had a looooong serial cable. The PC I had a test nox> > on the Portman driver is not in my room, and it is not a portable one. nox> > nox> > Atari, I have only heard the name. I played with an Acorn when I was a kiwi. nox> nox> Acorn, what CPU did it have again? :) Sorry, it was not mine, so I have no idea. I remember that Acone had a FM synthesizer in it, no midi interfaces. It sounded like a flat harpsichord, which was good at that time(in 1993, six years ago). nox> Anyway I now have restored the m68k-atari crosscompiler from tape and made nox> a little /dev/midi <-> /dev/modem2 connection program. Well, it works! nox> Now, does anyone know a sequencer program that has a tick display and nox> that can record one track while playing back another? rosegarden can only nox> do one thing at a time... Playing and recording simultaneously? I wish I knew one... nox> Oh and i had to patch this to get my kernel to build: nox> nox> Index: i386/conf/files.i386 nox> @@ -225,8 +225,10 @@ nox> i386/isa/sound/uart6850.c optional uart device-driver nox> i386/isa/sound/uart16550.c optional uartsio device-driver nox> i386/isa/sound/midi_synth.c optional uart device-driver nox> +i386/isa/sound/midi_synth.c optional uartsio device-driver nox> i386/isa/sound/midi_synth.c optional css device-driver nox> i386/isa/sound/midibuf.c optional uart device-driver nox> +i386/isa/sound/midibuf.c optional uartsio device-driver nox> i386/isa/sound/midibuf.c optional css device-driver nox> i386/isa/sound/trix.c optional trix device-driver nox> i386/isa/sound/adlib_card.c optional trix device-driver nox> nox> (the box has no sound card so these files were not compiled before.) Fixed the patch, thanks! Seigo TANIMURA |M2, Nakagawa Lab, Dept of Electronics & CS =========================|Faculty of Engineering, Yokohama National Univ Powered by SIEMENS, |http://www.naklab.dnj.ynu.ac.jp/~tanimura/ FreeBSD 4.0-CURRENT |http://www.sakura.ne.jp/~tcarrot/ (25th Apr 1999) & muesli.|tanimura@naklab.dnj.ynu.ac.jp tcarrot@sakuramail.com VoxWare Midi Driver for Serial Ports on FreeBSD: http://www.naklab.dnj.ynu.ac.jp/~tanimura/freebsd-serialmidi/ Seigo TANIMURA |M2, Nakagawa Lab, Dept of Electronics & CS =========================|Faculty of Engineering, Yokohama National Univ Powered by SIEMENS, |http://www.naklab.dnj.ynu.ac.jp/~tanimura/ FreeBSD 4.0-CURRENT |http://www.sakura.ne.jp/~tcarrot/ (25th Apr 1999) & muesli.|tanimura@naklab.dnj.ynu.ac.jp tcarrot@sakuramail.com VoxWare Midi Driver for Serial Ports on FreeBSD: http://www.naklab.dnj.ynu.ac.jp/~tanimura/freebsd-serialmidi/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 1 23:14:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id C2EEA155E4 for ; Sat, 1 May 1999 23:14:02 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id AAA00741; Sun, 2 May 1999 00:14:02 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id AAA27389; Sun, 2 May 1999 00:14:01 -0600 Date: Sun, 2 May 1999 00:14:01 -0600 Message-Id: <199905020614.AAA27389@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Seigo TANIMURA Cc: freebsd-current@FreeBSD.ORG Subject: Re: apmconf(8) -e ends to panic in apm_bios_call In-Reply-To: <19990502075751N.tanimura@sakuramail.com> References: <19990502075751N.tanimura@sakuramail.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When I cvsuped, made and installed the new world and kernel on 1st May 1999, > the kernel paniced in apm_bios_call called from apmconf(8) -e... Does the BIOS of your laptop claim to have less memory than FreeBSD claims? If so, you need to use the 'MAXMEM' option to set the memory to what your BIOS claims. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 0:17:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtualia.combios.es (virtualia.combios.es [195.53.190.48]) by hub.freebsd.org (Postfix) with SMTP id 6ADB114F34; Sun, 2 May 1999 00:17:19 -0700 (PDT) (envelope-from atras@bigfoot.com) Received: from bigfoot.com (195.53.104.11) by virtualia.combios.es (EMWAC SMTPRS 0.81) with SMTP id ; Sun, 02 May 1999 09:15:47 +0200 Date: Sun, 02 May 1999 09:15:47 +0200 Message-ID: From: atras@bigfoot.com To: atras@bigfoot.com Subject: SAVE UNTIL 70 % IN ITS INTERNATIONA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ESTE MENSAJE ES BILINGUE - EAST MESSAGE IS BILINGUE AHORRE HASTA UN 70 % EN SUS LLAMADAS INTERNACIONALES QUIERE ECONOMIZAR EN SUS LLAMADAS INTERNACIONALES ?? Evite los costos elevados de las centrales telefónicas. Llame desde su propio teléfono por la mitad del importe que ahora esta pagando. Sin cuotas de ningún tipo, suscripción gratuita. Si usted gasta en llamadas Internacionales , usted es un gran candidato a ser usuario de nuestro sistema IAS -System CallBack y Tarjetas Virtuales . Usted puede economizar hasta el 70% en sus llamadas para el exterior las 24 Hs. Para mayores informes solicite mas información a call-back@correovirtual.com, indicando el país de origen. Poner en el asunto "más información". o envie un E-mail con su nombre/Pais. e-MAIL; call-back@correo.nu Tambien puede visitarnos en http://red-inter.net/callback Saludos --------------------------------------------------------------------------------------------------------------------------------------------- We strongly believe that this information will be very useful to you. Avoid the high costs of traditional telephone carriers.. Make calls from your own phone at half the cost you are paying now. There are no monthly fees of any type. Sign up today for free! For more information please e-mail call-back@correo.nu. Please indicate your country of origin and write "more info" on the subject line. You can also visit us at http://www.lanzadera.com/callbackin Contact us today and start saving (next week?)! Best regards, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 0:40:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 8B60614E43 for ; Sun, 2 May 1999 00:40:06 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-12-61.camtech.net.au [203.55.242.61]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id RAA17087; Sun, 2 May 1999 17:15:10 +0930 (CST) Message-ID: <372C0180.7F7BEFA@camtech.com.au> Date: Sun, 02 May 1999 17:10:48 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug Russell Cc: freebsd-current@FreeBSD.ORG Subject: Re: silo overflows in CURRENT ... some info that may help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Re-nicing wont help as I have just confirmed that the problem occurs if I run MAME, exit MAME and then get on the net. Very wierd... after running MAME, the serial port is unusable for ppp unless I reboot. Just doing a DNS lookup causes several silo overflows. MAME does something very strange to the system. I will grep the MAME source code for anything related to serial ports. Doug Russell wrote: > > On Sun, 2 May 1999, Matthew Thyer wrote: > > > I have been investigating the silo overflow situation for some time. > > > > I can trigger them every time by the following action: > > > > - Run M.A.M.E. (Multi arcade machine emulator) and then try to > > download something. (I am using user mode ppp). > > Can you nice M.A.M.E. slightly? > > Later...... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 0:41:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (Postfix) with ESMTP id 37A5D14E43 for ; Sun, 2 May 1999 00:41:22 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id RAA15447 for ; Sun, 2 May 1999 17:41:20 +1000 (EST) Date: Sun, 2 May 1999 17:41:19 +1000 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: freebsd-current@FreeBSD.ORG Subject: make world failure mode Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # uname -v FreeBSD 3.1-STABLE #2: Mon Apr 26 22:46:11 EST 1999 I have noticed that if you do not have /usr/share/groff_font directory, a buildworld will fail. I think GROFF_FONT_PATH is missing from a Makefile maybe? The dev* directories are already built in the obj tree... Script started on Sun May 2 15:28:26 1999 # make buildworld ===> share/doc/usd/13.viref sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ex.cmd.roff\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ref.so\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(set.opt.roff\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' /home/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/vi.ref | groff -mtty-char -Tascii -t -s -me -o1- > /dev/null groff: can't find `DESC' file groff:fatal error: invalid device `ascii' *** Error code 3 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # ^Dexit Script done on Sun May 2 17:12:14 1999 -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 0:41:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CA161538C for ; Sun, 2 May 1999 00:41:41 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id BAA16004; Sun, 2 May 1999 01:41:27 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905020741.BAA16004@panzer.plutotech.com> Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: from Matthew Jacob at "May 1, 1999 7:32:37 pm" To: mjacob@feral.com Date: Sun, 2 May 1999 01:41:27 -0600 (MDT) Cc: roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote... > > Oh, very well, I'll have to say Perforce isn't that bad- it's just that it > doesn't have a snappy set of tcl/tk GUI tools that allow you look at whole > branch and revision histories.. I know there's a reasonable web-based tool that lets you look at revision histories for files, trees, whatever. There's also a nice tcl/tk tool that allows you to do merge files from a gui interface. > It doesn't have a 3-way filemerge tool (I > still fire up teamware (what NSElite became) to do heavy merging and use > the automerge feature)... Perforce *does* have the disparate release > stream feature, but I have found it somewhat difficult to use. Perhaps if > I'd actually had the depot locally I'd feel more at home with it.... What do you mean by 3-way merge? I've got one souce tree under perforce that is an amalgamtion of 5 source trees. Right now, I'm actively keeping it in sync with two separate source trees. And this is a non-trivial number of files -- each of the trees in question is at least a full FreeBSD source tree. Perforce's merging tools work pretty well, and have enabled me to do some branching and merging that would probably drive even a seasoned CVS user nuts. Here's how I generally merge things from two branches into a "combined" branch: p4 integrate -b branch1-to-combined-branch [ The -b argument specifies the branch mapping, which basically is the source and destination trees ] p4 resolve -as [ This tells perforce to resolve the merge, and accept "safe" changes. Safe changes are changes to files that have changed in the source or destination branches, but not both. ] p4 resolve [ This picks up the files that weren't automatically merged in the last step. For most files, perforce is able to merge things adequately, but when it can't, you have to go in and edit things manually, or specify whether you want to keep the source or destination branch version of the file. ] p4 submit [ Write a change description, edit the list of files to submit, and then check things in. ] You then repeat the same process for the second branch merge, except that in the first step, you'd use a different branch mapping. It's also pretty easy to merge things in the opposite direction. You can also do nifty things like only merge certain files from one branch to another, or only merge certain changes from one branch to another. It's possible, for instance, to merge revisions 4, 5, 7, and 9 of a file, but not 6 or 8. It's also possible to merge certain changelists from one branch to another, instead of doing a blanket merge. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 0:53:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id E3C2D14C9B for ; Sun, 2 May 1999 00:53:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA97069; Sun, 2 May 1999 08:53:37 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 2 May 1999 08:53:37 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: Bill Paul , Bob Bishop , current@freebsd.org Subject: Re: if_xl.c noise In-Reply-To: <199905012346.QAA83189@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Matthew Dillon wrote: > : > :You could have answered this yourself by checking in > :/pub/FreeBSD/FreeBSD-current/src/sys/pci/if_xl.c on ftp.cdrom.com. > :Yes, this is only your repository; you must be using some patches > :from Matt Dillon for NFS. The code in -current has the change that > :he made already in it (but with a different comment). Grab a fresh > :copy of if_xl.c and if_xlreg.h from -current and stick with it. > : > :-Bill > > He probably did. I meant to remove those from my NFS stuff... they're > gone now. Hopefully the NFS patches ( non-inclusive of the xl stuff ) > will be committed soon. Excellent. If you need another review, just ask me. I have read the patch and can do a proper review if necessary. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 0:54:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from psycho.h4x0rz.za.org (psycho.h4x0rz.za.org [206.49.228.8]) by hub.freebsd.org (Postfix) with ESMTP id 113E714C9B for ; Sun, 2 May 1999 00:54:23 -0700 (PDT) (envelope-from andrew@psycho.h4x0rz.za.org) Received: from localhost (andrew@localhost) by psycho.h4x0rz.za.org (8.9.3/8.9.2) with ESMTP id JAA00451 for ; Sun, 2 May 1999 09:55:46 +0200 (SAST) (envelope-from andrew@psycho.h4x0rz.za.org) Date: Sun, 2 May 1999 09:55:46 +0200 (SAST) From: vortexia To: freebsd-current@freebsd.org Subject: sio overflows of some kind? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hrmmm for some strange reason since I cvsupped a few days ago, Ive been getting strange messages on my consoles every time I move my mouse, something to the effect of: May 2 09:53:04 main /kernel: sio0: 103 more tty-level buffer overflows (total 902) Anyone got any ideas what this is? Cheers Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 2: 9:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0F58615A0D for ; Sun, 2 May 1999 02:09:14 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id LAA01166 for freebsd-current@FreeBSD.ORG; Sun, 2 May 1999 11:09:13 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 3BAAF8840; Sun, 2 May 1999 11:03:12 +0200 (CEST) (envelope-from roberto) Date: Sun, 2 May 1999 11:03:12 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Perforce (Was: Re: BitKeeper) Message-ID: <19990502110312.A3059@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19990502015216.A915@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: ; from Matthew Jacob on Sat, May 01, 1999 at 07:32:37PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Matthew Jacob: > doesn't have a snappy set of tcl/tk GUI tools that allow you look at whole > branch and revision histories.. They're in the contributed section of the WWW site. The Windows client has a GUI too. > It doesn't have a 3-way filemerge tool (I > still fire up teamware (what NSElite became) to do heavy merging and use > the automerge feature)... It does have both an integrated 3-way merge command and a way to invoke an external one. See "p4 resolve". -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 3:23: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 5EF7214E21; Sun, 2 May 1999 03:23:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA22201; Sun, 2 May 1999 12:22:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id MAA02756; Sun, 2 May 1999 12:22:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Date: Sun, 02 May 1999 12:22:59 +0200 Message-ID: <2754.925640579.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: FreeBSD interrupt responsetime... MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: FreeBSD interrupt responsetime... From: Poul-Henning Kamp Date: Sun, 02 May 1999 12:22:59 +0200 Message-ID: <2754.925640579@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Bcc: Blind Distribution List: ; MIME-Version: 1.0 A company asked me for data on interrupt response times in FreeBSD and I've done a setup in my lab to measure it. I have completed the first half of the task: characterising the jitter on the response time, and the data are presented for all to see here. The second half of the task is more tricky: measuring the delay from the external stimuli until we execute the first statement in the interrupt handler, but if I can crack that nut data will be forthcoming on that as well. These data are for the ppsdriver, using a FAST_INTR, running in single user mode with no other programs, and only a tickle of data stored to the disk from the measuring program. The input event rate was 1Hz. Total samples: 86664 Standard Deviation: 250 nsec Average: 0 (dataset centered on mean) Median: -30.1 nsec Min: -763 nsec Max: 2936 nsec first column: the percentage of samples second column: +/- span around the median in nsec third column: +/- span around the mean in nsec In other words, 50 percent of the samples were inside a band of +/- 137 nsec of the mean of all the samples. 10 23 24 20 48 49 30 74 75 40 102 104 50 132 137 60 168 174 70 208 217 75 233 242 80 261 271 90 356 358 95 474 456 97.5 636 606 98 693 663 98.5 763 733 99 864 834 99.25 992 962 99.5 1215 1184 99.75 1215 1436 99.9 1642 1612 99.95 1741 1711 99.99 2040 2009 100 2966 2936 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 3:30:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id 7225415292 for ; Sun, 2 May 1999 03:30:36 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 19659 invoked by uid 1000); 2 May 1999 10:45:00 -0000 Date: Sun, 2 May 1999 12:45:00 +0200 From: Andreas Braukmann To: current@FreeBSD.ORG Subject: Re: default route not set up?? Message-ID: <19990502124500.K6095@paert.tse-online.de> References: <372A1AE6.4E2738D4@odin-corporation.com> <372AF60B.E11A6989@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Dag-Erling Smorgrav on Sat, May 01, 1999 at 03:18:23PM +0200 Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sat, May 01, 1999 at 03:18:23PM +0200, Dag-Erling Smorgrav wrote: > "Daniel C. Sobral" writes: > > Dag-Erling Smorgrav wrote: > > > # Configure routing interesting code deleted ... [..] > > Looking there, it *does* seem that there is a problem. defaultrouter > > is only used to set route_default, which is *not* used. At least on > > the code you quoted. > This is getting fun :) Look closer at the first line I commented, then > at the loop, and especially the eval. since I've stumbled over the same 'what the the hell is going on here?'-piece of shell script once upon a time, I've foreseen the further development of this after having read the first two messages. I had to set a few static routes, saw the empty 'static_routes' configuration variable and just didn't grasped "what to do know" with that variable. I considered, that there has to be some underlying 'magic' similar to the method used for the interface configuration. Despite of this cognition I had to jump head first into the rc.network script to investigate on 'how to use' the core variable (static_routes) and the supplementary variables the right way. It would be very nice, if 'somebody' (TM) would document the various 'dark magic' parts of the rc scripts. But, ... a person priviledged to setup the routing for a system (aka system administrator aka 'root') should really be able to parse 'sh'-code, shouldn't he? -Andreas -- : TSE TeleService GmbH : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 5:28:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id CC1DD14DC6 for ; Sun, 2 May 1999 05:28:22 -0700 (PDT) (envelope-from erik@habatech.no) Received: from freebsd.habatech.no ([62.92.133.2]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id OAA20461; Sun, 2 May 1999 14:28:09 +0200 (CEST) (envelope-from erik@habatech.no) From: erik@habatech.no Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.p0.FreeBSD:990502143436:300=_" In-Reply-To: Date: Sun, 02 May 1999 14:34:36 +0200 (CEST) Reply-To: erik@habatech.no Organization: Habatech AS To: Nick Hibma Subject: Re: Problems with ahc (2940U2W) and USB Cc: freebsd-current@FreeBSD.ORG, Rick Whitesel , Jim Bloom Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990502143436:300=_ Content-Type: text/plain; charset=us-ascii On 01-May-99 Nick Hibma wrote: > > Did I miss an update on this? Could you guys drop me the output of dmesg > (after a boot -v if possible)? > When doing some more research into this problem, I found that the BIOS did not assign any IRQ to the USB controller, even though it was instructed to do so. I upgraded to the newest BIOS version, and suddenly the problematic kernel worked. My problem was solved by this, how about the other people reporting similar problems? Attached is the dmesg output of the kernel. (boot -v) -- --------------------------------+---------------------------------------+ Erik H. Bakke, Habatech AS | To be or not to be... | E-Mail: erik@habatech.no Date: 02-May-99 Time: 14:30:48 | Is simply a question of binary logic. | This message was sent by XFMail | | --------------------------------+---------------------------------------+ --_=XFMail.1.3.p0.FreeBSD:990502143436:300=_ Content-Disposition: attachment; filename="dmesg.works.too" Content-Transfer-Encoding: 7bit Content-Description: dmesg.works.too Content-Type: text/plain; charset=iso-8859-1; name=dmesg.works.too; SizeOnDisk=13219 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Sun May 2 14:10:45 CEST 1999 root@freebsd.habatech.no:/usr/src/sys/compile/HABA.USB Calibrating clock(s) ... TSC clock: 300654953 Hz, i8254 clock: 1193075 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002c5000 - 0x03fd7fff, 64040960 bytes (15635 pages) avail memory = 62316544 (60856K bytes) Found BIOS32 Service Directory header at 0xc00fad80 Entry = 0xfb200 (0xc00fb200) Rev = 0 Len = 1 PCI BIOS entry at 0xb230 DMI header at 0xc00f5c00 Version 2.0 Table at 0xf0800, 29 entries, 747 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fbd90 Preloaded elf kernel "kernel.old" at 0xc02b0000. Pentium Pro MTRR support enabled, default memory type is uncacheable Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 No Plug-n-Play devices were found pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base e0000000, size 26 found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000f000, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 map[0]: type 4, range 32, base 00006400, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1274, dev=0x5000, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 00006800, size 6 found-> vendor=0x9005, dev=0x0010, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[0]: type 4, range 32, base 00006c00, size 8 map[1]: type 1, range 64, base e5100000, size 12 map[2]: type 0, range 0, base 00000000, size 0 found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 3, range 32, base e5101000, size 12 map[1]: type 4, range 32, base 00007000, size 5 map[2]: type 1, range 32, base e5000000, size 20 found-> vendor=0x1002, dev=0x4750, revid=0x5c class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base e4000000, size 24 map[1]: type 4, range 32, base 00007400, size 8 map[2]: type 1, range 32, base e5102000, size 12 pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: at device 7.2 on pci0 uhci0: interrupting at irq 11 uhci0: USB version 1.0, chip rev. 1 usb0: on uhci0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip2: at device 7.3 on pci0 es0: at device 9.0 on pci0 pcm0: using I/O space register mapping at 0x6800 es0: interrupting at irq 10 ahc0: at device 10.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 390 instructions downloaded ahc0: interrupting at irq 5 fxp0: at device 11.0 on pci0 fxp0: interrupting at irq 9 fxp0: Ethernet address 00:08:c7:b2:ec:ef bpf: fxp0 attached isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: interrupting at irq 1 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 36 03 c8 psm: status 36 03 c8 psm: status 36 03 c8 psm: status 10 00 64 psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0: on atkbdc0 psm0: model IntelliMouse, device ID 3, 3 buttons psm0: config:00000000, flags:00000000, packet size:4 psm0: syncmask:c8, syncbits:08 psm0: interrupting at irq 12 vga0: on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc: parallel port found at 0x3bc ppc0: ECP SPP SPP ppc0 at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppb0: IEEE1284 device found /NIBBLE/PS2/ECP/NIBBLE_ID/PS2_ID/ECP_ID/Extensibilit y Link Probing for PnP devices on ppbus0: ppbus0: PCL,MLC,PML plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ppc0: interrupting at irq 7 mss_probe: no address supplied, try default 0x530 mss_detect error, busy still set (0xff) sb_probe: no address supplied, try defaults (0x220,0x240) pca0 at port 0x40 on isa0 pca0: PC speaker audio driver BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. bpf: lo0 attached bpf: ds0 attached ds0 XXX: driver didn't set ifq_maxlen ata0: master: settting up WDMA2 mode on PIIX3/4 chip OK ad0: ATA-? disk at ata0 as master ad0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 8 secs/int, 0 depth queue, DMA mode ata1: master: settting up UDMA2 mode on PIIX4 chip OK ad1: ATA-4 disk at ata1 as master ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode ata1: slave: settting up UDMA2 mode on PIIX4 chip OK ad2: ATA-3 disk at ata1 as slave ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 0 depth queue, DMA mode Waiting 5 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:2. 1 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted ahc0: Selection Timeout on A:6. 1 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted ahc0: Selection Timeout on A:9. 1 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted ahc0: Selection Timeout on A:14. 1 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted (probe3:ahc0:0:3:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe3:ahc0:0:3:0): ILLEGAL REQUEST asc:24,0 (probe3:ahc0:0:3:0): Invalid field in CDB ahc0: target 3 synchronous at 16.0MHz, offset = 0x10 (probe4:ahc0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe4:ahc0:0:4:0): ILLEGAL REQUEST csi:0,0,74,c3 asc:24,0 (probe4:ahc0:0:4:0): Invalid field in CDB ahc0: target 4 synchronous at 10.0MHz, offset = 0xf ahc0: target 1 using 16bit transfers ahc0: target 1 synchronous at 20.0MHz, offset = 0xf ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0xf pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number LN362345000019010TJ0 pass0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabl ed pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number NL00765700001845HWQM pass1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabl ed pass2 at ahc0 bus 0 target 3 lun 0 pass2: Removable CD-ROM SCSI-2 device pass2: 19.230MB/s transfers (19.230MHz, offset 16) pass3 at ahc0 bus 0 target 4 lun 0 pass3: Removable CD-ROM SCSI-2 device pass3: 10.000MB/s transfers (10.000MHz, offset 15) Considering FFS root f/s. changing root device to wd0s1a cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 19.230MB/s transfers (19.230MHz, offset 16) cd0: cd present [284433 x 2048 byte records] da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number NL00765700001845HWQM da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number LN362345000019010TJ0 da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) ad0s1: type 0xa5, start 0, end = 2503871, size 2503872 : OK start_init: trying /sbin/init da0s1: type 0xa5, start 32, end = 8888319, size 8888288 : OK da1s1: type 0xa5, start 32, end = 8888319, size 8888288 : OK ad1: invalid primary partition table: no magic cd1 at ahc0 bus 0 target 4 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: cd present [28879 x 2048 byte records] da0s1: type 0xa5, start 32, end = 8888319, size 8888288 : OK da1s1: type 0xa5, start 32, end = 8888319, size 8888288 : OK ad1s1: type 0xa5, start 63, end = 12594959, size 12594897 : OK Linux-ELF exec handler installed --_=XFMail.1.3.p0.FreeBSD:990502143436:300=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 5:34: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id BE61514DC6 for ; Sun, 2 May 1999 05:33:58 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-12-3.camtech.net.au [203.55.242.3]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id WAA24556; Sun, 2 May 1999 22:08:52 +0930 (CST) Message-ID: <372C4656.4A1464B8@camtech.com.au> Date: Sun, 02 May 1999 22:04:30 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: vortexia Cc: freebsd-current@FreeBSD.ORG Subject: Re: sio overflows of some kind? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have seen silo overflows on my serial port when I am using user mode ppp when using a PS/2 mouse and moused. Whilst downloading a large file I was able to cause multiple sio silo overflows by moving the mouse. I have stopped using moused since then (because of this) and can now download large files without problem but can still cause my serial ports to be unusable (requiring a reboot) if I run MAME first (before getting on the net) or while I am on the net. I can still use a PS/2 mouse, just not with moused, so XFree86 is using the mouse directly now instead of /dev/sysmouse. See my recent messages to freebsd-current entitled "silo overflows in CURRENT ... some info that may help" vortexia wrote: > > Hrmmm for some strange reason since I cvsupped a few days ago, Ive been > getting strange messages on my consoles every time I move my mouse, > something to the effect of: > > May 2 09:53:04 main /kernel: sio0: 103 more tty-level buffer overflows > (total 902) > > Anyone got any ideas what this is? > > Cheers > > Andrew > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 9:21:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 36C64153A3 for ; Sun, 2 May 1999 09:21:15 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA30286; Mon, 3 May 1999 02:21:08 +1000 Date: Mon, 3 May 1999 02:21:08 +1000 From: Bruce Evans Message-Id: <199905021621.CAA30286@godzilla.zeta.org.au> To: andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: make world failure mode Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ># uname -v >FreeBSD 3.1-STABLE #2: Mon Apr 26 22:46:11 EST 1999 > >I have noticed that if you do not have /usr/share/groff_font >directory, a buildworld will fail. I think GROFF_FONT_PATH is >missing from a Makefile maybe? The dev* directories are already >built in the obj tree... Similarly for /usr/share/tmac and GROFF_TMAC_PATH. Not quite similarly for /usr/share/dict/{various}. groff uses these, but there doesn't seem to be any macros for them. Hopefully they aren't used by buildworld. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 10:32:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 9D6E114D9E; Sun, 2 May 1999 10:32:39 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from transit.hanse.de (transit-a.Hanse.DE [193.174.9.161]) by kogge.Hanse.DE (8.9.1/8.9.1) with ESMTP id TAA65743; Sun, 2 May 1999 19:32:20 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Received: from monster.transit-a.hanse.de (monster [193.174.9.163]) by transit.hanse.de (8.8.8/8.8.8) with ESMTP id TAA26605; Sun, 2 May 1999 19:32:18 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Date: Sun, 02 May 1999 19:32:08 +0200 From: Stefan Bethke To: freebsd-current@freebsd.org Cc: sos@freebsd.org Subject: panic in nexus_setup_intr+0x13 with new ata driver Message-ID: <14289515.3134662328@monster.transit-a.hanse.de> Originator-Info: login-id=stb; server=transit.transit-a.hanse.de X-Mailer: Mulberry (MacOS) [1.4.0, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently trying to get a Promise Ultra/33 to work with S=F8rens new = ata drivers. The kernel config is as per LINT: machine "i386" cpu "I486_CPU" ident DEV maxusers 40 options INET #InterNETworking options NETATALK options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MFS options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root device options FFS_ROOT #FFS usable as root device [keep this!] options NFS_ROOT #NFS usable as root device options PROCFS #Process filesystem options SOFTUPDATES options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3D3000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on sa0 dumps on sa0 controller isa0 controller eisa0 controller pci0 controller pnp0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # ATA and ATAPI devices # This is work in progress, use at your own risk. # It currently reuses the majors of wd.c and friends. # It cannot co-exist with the old system in one kernel. # You only need one "controller ata0" for it to find all # PCI devices on modern machines. controller ata0 device atadisk0 # ATA disk drives #device atapicd0 # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives options DDB makeoptions DEBUG=3D-g makeoptions COPTFLAGS=3D"-O -DATA_DEBUG -DAD_DEBUG" controller ncr0 #controller ahc0 controller scbus0 device da0 device sa0 device cd0 device pass0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ed0 at pci? pseudo-device loop pseudo-device ether pseudo-device ppp 4 pseudo-device tun 4 pseudo-device bpfilter 4 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 4 pseudo-device ccd 4 #options KTRACE #kernel tracing options SYSVSHM options SYSVSEM options SYSVMSG options "VM86" options VESA #device pcm0 at isa? disable port ? tty irq 10 drq 1 flags 0x0 I've written down the following: ata-pci0: at device 5.0 on pci0 ata-pci0: type4d33105a class=3D01 subclass=3D04 cmd=3D02000007 ata-pci0: Busmastering DMA supported ata0: iobase=3D0xa000 altiobase=3D0xa100 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: devices =3D 0x1 Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x14 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc02012fb stack pointer =3D 0x10:0xc02dad44 frame pointer =3D 0x10:0xc02dad74 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1 def32 1, gran 1 processor flags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 interrupt mask =3D net tty bio cam kernel: type 12 trap, code=3D0 Stopped at nexus_setup_intr+0x13: pushl 0x14(%edx) db> trace,8 nexus_setup_intr(c0689a40,c06895c0,0,c01e9d44,c068bd00) at next_setup_intr+0x13 BUS_SETUP_INTR(c0689a40,c06895c0,0,c01e9d44,c068bd00) at = BUS_SETUP_INTR+0x34 bus_generic_setup_intr(c0689800,c06895c0,0,c011e9d44,c068bd00) at bus_generic_setup_intr+0x2b BUS_SETUP_INTR(c0689800,c06895c0,0,c01e9d44,c068bd00) at = BUS_SETUP_INTR+0x34 bus_generic_setup_intr(c0689740,c06895c0,0,c01e9d44,c068db00) at bus_generic_setup_intr+0x2b BUS_SETUP_INTR(c0689740,c06895c0,0,c01e9d44,c068bd00) at = BUS_SETUP_INTR+0x34 bus_setup_intr(c06895c0,0,c01e9d44,c068bd00,c02dae88) at = bus_setup_intr+0x21 ata_pciattach(c06895c0,c02daed0,c0148ce3,c06895c0,c06895c0) at ata_pciattach+0x439 db> x/ia nexus_setup_intr,10 nexus_setup_intr: pushl %ebp nexus_setup_intr+0x1: movl %esp,%ebp nexus_setup_intr+0x3: subl $0x24,%esp nexus_setup_intr+0x6: pushl %edi nexus_setup_intr+0x7: pushl %esi nexus_setup_intr+0x8: pushl %ebx nexus_setup_intr+0x9: movl 0xc(%ebp),%ebx nexus_setup_intr+0xc: testl %ebx,%ebx nexus_setup_intr+0xe: jz nexus_setup_intr+0x24 nexus_setup_intr+0x10: movl 0x10(%ebp),%edx nexus_setup_intr+0x13: pushl 0x14(%edx) nexus_setup_intr+0x16: pushl $0xc024bd96 nexus_setup_intr+0x1b: pushl %ebx nexus_setup_intr+0x1c: call device_printf nexus_setup_intr+0x21: addl $0xc,%esp nexus_setup_intr+0x24: movl 0x1c(%ebp),%edx db> x/s $0xc024bd96 __set_sysintit_set_sym_nexus_rootmodule_sys_init+0x11e: interrupting at = irq %d\012 db> show reg cs 0x8 ds 0x10 es 0x10 fs 0x10 ss 0x10 eax 0xc02012e8 nexus_setup_intr ecx 0xc0689a40 edx 0 ebx 0xc06895c0 esp 0xc02dad44 epb 0xc02dad74 esi 0x5 edi 0xc06896c0 eip 0xc02012fb nexus_setup_intr+0x13 efl 0x10286 This is with a -current from about three days ago. Unfortunatly, I don't understand enought about the new bus stuff to really understand where the null pointer gets into the game. Ah, if it matters: the Promise currently has the EPROM removed. Any hints appreciated, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 10:48:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 4914514D9E for ; Sun, 2 May 1999 10:41:32 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (postfix@myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id UAA15545; Sun, 2 May 1999 20:41:15 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id A786A1F44; Sun, 2 May 1999 20:41:13 +0300 (EEST) Date: Sun, 2 May 1999 20:41:13 +0300 From: Vallo Kallaste To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: PCM Message-ID: <19990502204113.A16053@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19990501082228.3C75F1F58@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990501082228.3C75F1F58@spinner.netplex.com.au>; from Peter Wemm on Sat, May 01, 1999 at 04:22:25PM +0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 01, 1999 at 04:22:25PM +0800, Peter Wemm wrote: > I've run two systems with PCM right since the first newbus commit, and it's > worked for me. Admittedly I don't use it all that often, but it's never > paniced and I don't recall getting any more sound problems than usual. > > I checked that the isa_dma.c code is an exact split of the dma code that > used to be in the old isa.c, there are zero changes to the isa dma code. The sound broke for me between Apr.20 and 21. My onboard Vibra16X doesn't work either with pcm or Voxware drivers. Voxware complains about second DMA (1/3) and pcm just simply emits silence. Apr.20 kernel works well. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 10:58:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1322514D9E for ; Sun, 2 May 1999 10:58:30 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA62149; Sun, 2 May 1999 18:58:20 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 2 May 1999 18:58:20 +0100 (BST) From: Doug Rabson To: Vallo Kallaste Cc: Peter Wemm , current@freebsd.org Subject: Re: PCM In-Reply-To: <19990502204113.A16053@myhakas.matti.ee> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 May 1999, Vallo Kallaste wrote: > On Sat, May 01, 1999 at 04:22:25PM +0800, Peter Wemm wrote: > > > I've run two systems with PCM right since the first newbus commit, and it's > > worked for me. Admittedly I don't use it all that often, but it's never > > paniced and I don't recall getting any more sound problems than usual. > > > > I checked that the isa_dma.c code is an exact split of the dma code that > > used to be in the old isa.c, there are zero changes to the isa dma code. > > The sound broke for me between Apr.20 and 21. My onboard Vibra16X > doesn't work either with pcm or Voxware drivers. Voxware complains > about second DMA (1/3) and pcm just simply emits silence. Apr.20 > kernel works well. I will fix this. I just need to find the time to rip the PNP soundcard out of one of my machines and put it into a place where I can debug it. Probably not today. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 11:41:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 6218B15414 for ; Sun, 2 May 1999 11:41:25 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from transit.hanse.de (transit-a.Hanse.DE [193.174.9.161]) by kogge.Hanse.DE (8.9.1/8.9.1) with ESMTP id UAA67282; Sun, 2 May 1999 20:41:07 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Received: from monster.transit-a.hanse.de (monster [193.174.9.163]) by transit.hanse.de (8.8.8/8.8.8) with ESMTP id UAA26761; Sun, 2 May 1999 20:41:04 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Date: Sun, 02 May 1999 20:40:54 +0200 From: Stefan Bethke To: obrien@NUXI.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world fails when updating from older -current Message-ID: <14537697.3134666454@monster.transit-a.hanse.de> In-Reply-To: <19990430113828.A95710@nuxi.com> Originator-Info: login-id=stb; server=transit.transit-a.hanse.de X-Mailer: Mulberry (MacOS) [1.4.0, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fre, 30. Apr 1999 11:38 Uhr -0700 David O'Brien wrote: >> perl5: not found >> *** Error code 1 > > Do you have NOPERL uncommented in /etc/make.conf? If so, don't do that. No, I didn't. And, since I could make the modules manually, why count have that worked? I've since successfully make'd my way to a current -current, and everything seems fine. (but see my other message from today.) Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 12: 8:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 7F6CB14C8D for ; Sun, 2 May 1999 12:08:18 -0700 (PDT) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (mars.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.8.8/8.8.7/8.7.7) with ESMTP id VAA1224814; Sun, 2 May 1999 21:06:40 +0200 (CST) Received: from vodix.cs.uni-sb.de (maxtnt-260.telip.uni-sb.de [134.96.71.131]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id VAA08925; Sun, 2 May 1999 21:06:39 +0200 (CST) Received: from Vodix.CS.Uni-SB.de (localhost.net.local [127.0.0.1]) by vodix.cs.uni-sb.de (8.9.3/8.9.3) with ESMTP id VAA27311; Sun, 2 May 1999 21:06:33 +0200 (CEST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199905021906.VAA27311@vodix.cs.uni-sb.de> Date: Sun, 2 May 1999 21:06:31 +0200 (CEST) From: A.Leidinger@Wurzelausix.CS.Uni-SB.de Subject: Re: PCM To: vallo@matti.ee Cc: peter@netplex.com.au, current@FreeBSD.ORG In-Reply-To: <19990502204113.A16053@myhakas.matti.ee> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 May, Vallo Kallaste wrote: > The sound broke for me between Apr.20 and 21. My onboard Vibra16X > doesn't work either with pcm or Voxware drivers. Voxware complains > about second DMA (1/3) and pcm just simply emits silence. Apr.20 > kernel works well. FreeBSD 4.0-CURRENT #6: Sun Apr 25 20:08:42 CEST 1999 sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sb0: interrupting at irq 5 sbxvi0 at drq 5 on isa0 snd0: It's not onboard. Voxware works for me. pcm is able to produce something I'm not able to recognize, because it's to short in time, even if the audiofile has data for more than one minute (cat something >/dev/dsp{W,}). Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 12:41:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (unknown [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id DC8B9151AA for ; Sun, 2 May 1999 12:41:52 -0700 (PDT) (envelope-from dispatch@blackhelicopters.org) Received: (from dispatch@localhost) by blackhelicopters.org (8.8.8/8.8.8) id PAA22423 for freebsd-current@freebsd.org; Sun, 2 May 1999 15:41:51 -0400 (EDT) (envelope-from dispatch) From: Dispatcher Message-Id: <199905021941.PAA22423@blackhelicopters.org> Subject: Re: -stable vs -current (was Re: solid NFS patch #6... ) To: freebsd-current@freebsd.org Date: Sun, 2 May 1999 15:41:51 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #Tim Vanderhoek wrote: #On Fri, Apr 30, 1999 at 04:52:58PM -0700, Matthew Dillon wrote: #> #> I expect the 3.2 release to be a really good release. # #I seem to recall that 2.2.x wasn't even called "-stable" until 2.2.2. #That .2 release is exactly where 3.x is right now... And it wasn't until 2.2.5 that I saw an official note saying "2.1.7 users should upgrade now." I won't upgrade my mission-critical systems until I see a similar notice from Jordan or someone in his place. For mission-critical systems, I'm still installing 2.2.8-stable. ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 13: 3:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebase.sitaranetworks.com (freebase.sitaranetworks.com [199.103.141.181]) by hub.freebsd.org (Postfix) with SMTP id 532D314C34 for ; Sun, 2 May 1999 13:03:46 -0700 (PDT) (envelope-from john@loverso.southborough.ma.us) Received: from loverso.southborough.ma.us (loverso.sitaranetworks.com [199.103.141.107]) by freebase.sitaranetworks.com (8.8.8/8.8.8) with ESMTP id QAA04527 for ; Sun, 2 May 1999 16:03:44 -0400 (EDT) Received: from loverso.southborough.ma.us (localhost [127.0.0.1]) by loverso.southborough.ma.us (8.8.8/8.6.9) with ESMTP id QAA14116 for ; Sun, 2 May 1999 16:03:43 -0400 (EDT) Message-Id: <199905022003.QAA14116@loverso.southborough.ma.us> To: current@FreeBSD.ORG Subject: Re: Our routed - Vern says it's old and buggy. In-reply-to: Message from Garrett Wollman <199904282103.RAA11123@khavrinen.lcs.mit.edu> . X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO .o>:NlJS1@vO9bVmswRoq3j DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn X-Url: http://surf.to/loverso Date: Sun, 02 May 1999 16:03:43 -0400 From: John Robert LoVerso Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman speaks the truth when he says: > > I can't quite figure why they stuck the word "open" in there, because it > > couldn't possibly be more open than RIP. > > Because a previous link-state (aka shortest-path-first) routing > protocol had been deployed which was not. I can't believe the amount of FUD on this issue. Read what Garrett says above because it is the reason for the "O" in OSPF. OSPF was developed by the IETF 10 years ago in response to the proprietary link-state routing protocol of a large router vender. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 13:54:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 55D611544D; Sun, 2 May 1999 13:54:45 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from transit.hanse.de (transit-a.Hanse.DE [193.174.9.161]) by kogge.Hanse.DE (8.9.1/8.9.1) with ESMTP id WAA70661; Sun, 2 May 1999 22:54:28 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Received: from monster.transit-a.hanse.de (monster [193.174.9.163]) by transit.hanse.de (8.8.8/8.8.8) with ESMTP id WAA27265; Sun, 2 May 1999 22:54:25 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Date: Sun, 02 May 1999 22:54:16 +0200 From: Stefan Bethke To: freebsd-current@FreeBSD.ORG Cc: sos@FreeBSD.ORG Subject: ata and IRQ sharing (was: panic in nexus_setup_intr+0x13 with new ata driver) Message-ID: <15018945.3134674456@monster.transit-a.hanse.de> In-Reply-To: <14289515.3134662328@monster.transit-a.hanse.de> Originator-Info: login-id=stb; server=transit.transit-a.hanse.de X-Mailer: Mulberry (MacOS) [1.4.0, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Son, 2. Mai 1999 19:32 Uhr +0200 Stefan Bethke wrote: > I'm currently trying to get a Promise Ultra/33 to work with S=F8rens new = ata > drivers. I've delved into the code a bit more. The panic results from ata_pciattach() not checking whether an IRQ resource could be allocated. Ths seems to stem from the fact that the IRQ is already taken by an ed PCI card. I've added RF_SHAREABLE to the bus_alloc_resource() flags, and was able to bring up the kernel fine. However, ed0 reported constant device timeouts, and accessing wd0 resulted in an endless wait for an interrupt. Removing the ed card makes the Promise controller work. I'm getting about 7MB/s from an IBM DTTA 350840, which should be normal. The board I'm currently trying this on is an Asus SP3, having the mis-feature of only having a single INTA for all three PCI slots (IRQ 5 = in my case). Now, PCI does support interrupt sharing, but in this case it might be broken: - in the chipset (but it worked with both an ed and ncr card installed) - in the newbus stuff - in the Promise controller - somewhere in promise_intr Would someone care to shed some light on this? I will try to do some tests on an Asus SP3G, which does have seperate = INTAs per PCI slot. Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 14:21:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id E6BDA15A52; Sun, 2 May 1999 14:21:23 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Sun, 2 May 1999 22:19:24 +0100 Message-ID: From: paul@originative.co.uk To: tanimura@naklab.dnj.ynu.ac.jp, nox@jelal.kn-bremen.de Cc: zinnia@jan.ne.jp, freebsd-current@freebsd.org, freebsd-multimedia@freebsd.org Subject: RE: Call for Review: Voxware midi driver for serial ports Date: Sun, 2 May 1999 22:19:23 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Seigo TANIMURA [mailto:tanimura@naklab.dnj.ynu.ac.jp] > Sent: 02 May 1999 06:58 > To: nox@jelal.kn-bremen.de > Cc: tanimura@naklab.dnj.ynu.ac.jp; zinnia@jan.ne.jp; > freebsd-current@freebsd.org; freebsd-multimedia@freebsd.org > Subject: Re: Call for Review: Voxware midi driver for serial ports > > > From: Juergen Lock > Subject: Re: Call for Review: Voxware midi driver for serial ports > Date: Sun, 2 May 1999 02:15:00 +0200 > Message-ID: <19990502021500.A3181@saturn.kn-bremen.de> > > nox> On Tue, Apr 20, 1999 at 10:27:35AM +0900, Seigo TANIMURA wrote: > nox> > On Sun, 18 Apr 1999 22:15:05 +0200, > nox> > Juergen Lock said: > nox> > > nox> > >> Another bad news, I tried driving my SC-88 > connected directly to a PC using > nox> > >> Windows 95 and Portman PC/S driver, to find a > miserable result. I saw no midi > nox> > >> messages come properly, so Portman PC/S should be > cooking the signals in some way... > nox> > > nox> > nox> Or uses a higher speed than 38k4, can you check > that? Hmm, or maybe > nox> > nox> i should just take my old Atari MSTe and use that > as serial<->midi > nox> > nox> interface... > nox> > > nox> > > nox> > Bitrate > 38.4k... I wish I had a looooong serial > cable. The PC I had a test > nox> > on the Portman driver is not in my room, and it is not > a portable one. > nox> > > nox> > Atari, I have only heard the name. I played with an > Acorn when I was a kiwi. > nox> > nox> Acorn, what CPU did it have again? :) > > Sorry, it was not mine, so I have no idea. I remember that > Acone had a FM synthesizer > in it, no midi interfaces. It sounded like a flat > harpsichord, which was good at that > time(in 1993, six years ago). The Acorn used a 6502. They went on to produce a box in the UK called the BBC Computer. It was *way* ahead of it's time, I still have it in the garage. Graphics resolutions that were better than the IBM PC that came later, 3 channel sound capability, the ability to add a second processor, an OS that was really neat. It was one nice piece of kit, ahh nostalgia. Paul Richards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 14:55:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B13F14C8B for ; Sun, 2 May 1999 14:55:02 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-147.skylink.it [194.185.55.147]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA11840; Sun, 2 May 1999 23:55:57 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id XAA02181; Sun, 2 May 1999 23:54:30 +0200 (CEST) Date: Sun, 2 May 1999 23:54:30 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: FreeBSD current Mailing list Cc: MAEKAWA Masahide Subject: driver for Iomega USB Zip 100 drive added Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Added to current today was the driver for the Iomega USB Zip 100 drive. Add controller umass0 in your kernel config file. The driver is probably buggy and might crash your system. The driver currently works properly only on UHCI controllers (Intel and Via chipsets), due to lack of proper support for timeouts on OHCI controllers. Performance is bad (approx 40kb/s) due to bad scheduling in the UHCI driver. The driver was developed together with MAEKAWA Masahide . Thanks! Support for the Ye-Data USB floppy drive will be added as soon as the drive is sent to me by Ye-Data (thanks Ye-Data!). Cheers, Nick Hibma FreeBSD USB project http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 15:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6811114E7A for ; Sun, 2 May 1999 15:54:25 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA25594; Sun, 2 May 1999 15:54:13 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Dispatcher Cc: freebsd-current@FreeBSD.ORG Subject: Re: -stable vs -current (was Re: solid NFS patch #6... ) In-reply-to: Your message of "Sun, 02 May 1999 15:41:51 EDT." <199905021941.PAA22423@blackhelicopters.org> Date: Sun, 02 May 1999 15:54:13 -0700 Message-ID: <25590.925685653@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And it wasn't until 2.2.5 that I saw an official note saying "2.1.7 > users should upgrade now." I won't upgrade my mission-critical > systems until I see a similar notice from Jordan or someone in his > place. > > For mission-critical systems, I'm still installing 2.2.8-stable. And I can only echo these sentiments. I've never made a secret of the fact that ".5" is always the best time to jump on board any branch in this project and it's been that way since practically the beginning. There's even a later snapshot release of the 2.2 branch on the FreeBSD Toolkit for people who continue to subscribe to this philosophy. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 16:34:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from qix.jmz.org (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id DC94114DD2 for ; Sun, 2 May 1999 16:34:41 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.2) id BAA93119; Mon, 3 May 1999 01:35:48 +0200 (MET DST) (envelope-from jmz@FreeBSD.ORG) Date: Mon, 3 May 1999 01:35:48 +0200 (MET DST) Message-Id: <199905022335.BAA93119@qix.jmz.org> X-Authentication-Warning: qix.jmz.org: jmz set sender to jmz@FreeBSD.ORG using -f From: Jean-Marc Zucconi To: freebsd-current@FreeBSD.ORG Subject: ctm-mail cvs-cur.5292.gz 18/82 X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This one did not arrive in my mailbox. Can someone send it to me? I would like to avoid downloading 6Mbytes again. Jean-Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 16:42:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id D8ACD14DD2; Sun, 2 May 1999 16:42:31 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA33852; Sun, 2 May 1999 19:40:28 -0400 (EDT) Date: Sun, 2 May 1999 19:40:28 -0400 (EDT) From: Chuck Robey To: Jean-Marc Zucconi Cc: freebsd-current@FreeBSD.ORG Subject: Re: ctm-mail cvs-cur.5292.gz 18/82 In-Reply-To: <199905022335.BAA93119@qix.jmz.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 May 1999, Jean-Marc Zucconi wrote: > This one did not arrive in my mailbox. Can someone send it to me? I > would like to avoid downloading 6Mbytes again. I'm going to mail it to you separately, but it might not look like it came from me. > > Jean-Marc > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 17: 5:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from hugin.odin-corporation.com (fredriks-2.pr.mcs.net [205.164.50.242]) by hub.freebsd.org (Postfix) with ESMTP id 68E97151CA for ; Sun, 2 May 1999 17:05:05 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by hugin.odin-corporation.com (8.9.2/8.9.1) with ESMTP id MAA15550; Sun, 2 May 1999 12:44:16 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <372C8EF0.DCE3BD49@odin-corporation.com> Date: Sun, 02 May 1999 12:44:16 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: Andreas Braukmann Cc: current@FreeBSD.ORG Subject: Re: default route not set up?? References: <372A1AE6.4E2738D4@odin-corporation.com> <372AF60B.E11A6989@newsguy.com> <19990502124500.K6095@paert.tse-online.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, There are two things going on with the route setup. if [ "x$defaultrouter" != "xNO" ] ; then static_routes="default ${static_routes}" route_default="default ${defaultrouter}" fi 1) since route_default is never used, it should be deleted, ignore that line above. 2) if you set defaultrouter to anything other than "NO", the static_route variable gets a "default" route route label added, and this label will get evaled later on. So rc.conf should read: (example from my setup) defaultrouter="YES" # Set to default gateway (or NO). static_routes="local" # Set to static route list (or leave empty). route_local=" -net " route_default=" default " So, two actions are needed. The route_default line from rc.network should get deleted, and the comment in rc.conf for the defaultrouter variable should be clearer. If others agree, I can go and commit the fixes for that .... Lars Andreas Braukmann wrote: > Hi, > > On Sat, May 01, 1999 at 03:18:23PM +0200, Dag-Erling Smorgrav wrote: > > "Daniel C. Sobral" writes: > > > Dag-Erling Smorgrav wrote: > > > > # Configure routing > interesting code deleted ... [..] > > > Looking there, it *does* seem that there is a problem. defaultrouter > > > is only used to set route_default, which is *not* used. At least on > > > the code you quoted. > > This is getting fun :) Look closer at the first line I commented, then > > at the loop, and especially the eval. > > since I've stumbled over the same 'what the the hell is going on > here?'-piece of shell script once upon a time, I've foreseen the > further development of this after having read the first two > messages. > I had to set a few static routes, saw the empty 'static_routes' > configuration variable and just didn't grasped "what to do know" > with that variable. > I considered, that there has to be some underlying 'magic' similar > to the method used for the interface configuration. > Despite of this cognition I had to jump head first into the > rc.network script to investigate on 'how to use' the core variable > (static_routes) and the supplementary variables the right way. > > It would be very nice, if 'somebody' (TM) would document the > various 'dark magic' parts of the rc scripts. > > But, ... a person priviledged to setup the routing for > a system (aka system administrator aka 'root') should really be > able to parse 'sh'-code, shouldn't he? > > -Andreas > > -- > : TSE TeleService GmbH : Gsf: Arne Reuter : : > : Hovestrasse 14 : Andreas Braukmann : We do it with : > : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : > :--------------------------------------------------------------------: > : Anti-Spam Petition: http://www.politik-digital.de/spam/ : > : PGP-Key: http://www.tse-online.de/~ab/public-key : > : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 17:24:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id B8FE614BD7 for ; Sun, 2 May 1999 17:24:26 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id TAA21375 for ; Sun, 2 May 1999 19:24:25 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id TAA23931 for current@freebsd.org; Sun, 2 May 1999 19:24:25 -0500 (CDT) Date: Sun, 2 May 1999 19:24:25 -0500 From: Alan Cox To: current@freebsd.org Subject: HEADS UP! (NFS) Message-ID: <19990502192425.C23524@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just committed Matt's VFS/BIO/NFS patch. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 17:55: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 6FDAC15224 for ; Sun, 2 May 1999 17:55:01 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from transit.hanse.de (transit-a.Hanse.DE [193.174.9.161]) by kogge.Hanse.DE (8.9.1/8.9.1) with ESMTP id CAA76578; Mon, 3 May 1999 02:54:42 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Received: from monster.transit-a.hanse.de (monster [193.174.9.163]) by transit.hanse.de (8.8.8/8.8.8) with ESMTP id CAA28186; Mon, 3 May 1999 02:54:38 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Date: Mon, 03 May 1999 02:54:29 +0200 From: Stefan Bethke To: Lars Fredriksen Cc: Andreas Braukmann , current@FreeBSD.ORG Subject: Re: default route not set up?? Message-ID: <15885868.3134688869@monster.transit-a.hanse.de> In-Reply-To: <372C8EF0.DCE3BD49@odin-corporation.com> Originator-Info: login-id=stb; server=transit.transit-a.hanse.de X-Mailer: Mulberry (MacOS) [1.4.0, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't! --On Son, 2. Mai 1999 12:44 Uhr -0500 Lars Fredriksen wrote: > So rc.conf should read: (example from my setup) > > > defaultrouter="YES" # Set to default gateway (or NO). > static_routes="local" # Set to static route list (or leave > empty). > route_local=" -net " > route_default=" default " > > So, two actions are needed. The route_default line from rc.network should > get deleted, and the comment > in rc.conf for the defaultrouter variable should be clearer. > > If others agree, I can go and commit the fixes for that .... Don't! Look at rc.network again. If you don't get it, run the code with set -vx, and see what happens. The correct entry still is: defaultrouter="1.2.3.4" For your convenience, I'm posting the complete snipped again: # Configure routing if [ "x$defaultrouter" != "xNO" ] ; then static_routes="default ${static_routes}" route_default="default ${defaultrouter}" fi # Set up any static routes. This should be done before router discovery. if [ "x${static_routes}" != "x" ]; then for i in ${static_routes}; do eval route_args=\$route_${i} route add ${route_args} done fi Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 19:35:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id 6487815374 for ; Sun, 2 May 1999 19:35:38 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id KAA14097; Mon, 3 May 1999 10:27:51 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id KAA24254; Mon, 3 May 1999 10:28:21 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA24613; Mon, 3 May 1999 10:28:20 +0800 Message-Id: <199905030228.KAA24613@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-reply-to: Your message of "Fri, 30 Apr 1999 13:04:52 +0200." <199904301104.NAA08369@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 May 1999 10:28:19 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren, I did a bit of experimenting with my CVS archive and found that version 1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed out errors about unexpected interrupts whilst probing and eventually hung, and 1.10 gave the unable to mount wd0s2a errors we all love. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 19:43:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from hugin.odin-corporation.com (fredriks-2.pr.mcs.net [205.164.50.242]) by hub.freebsd.org (Postfix) with ESMTP id 6718B14CC6 for ; Sun, 2 May 1999 19:42:42 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by hugin.odin-corporation.com (8.9.2/8.9.1) with ESMTP id VAA17811; Sun, 2 May 1999 21:42:32 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <372D0D18.E89B355A@odin-corporation.com> Date: Sun, 02 May 1999 21:42:32 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: Stefan Bethke Cc: Andreas Braukmann , current@FreeBSD.ORG Subject: Re: default route not set up?? References: <15885868.3134688869@monster.transit-a.hanse.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for setting me straight! I am backtracking trying to find out what I did wrong initially when I tried to set it up. I certainly botched the debugging part :-( Lars Stefan Bethke wrote: > Don't! > > --On Son, 2. Mai 1999 12:44 Uhr -0500 Lars Fredriksen > wrote: > > > So rc.conf should read: (example from my setup) > > > > > > defaultrouter="YES" # Set to default gateway (or NO). > > static_routes="local" # Set to static route list (or leave > > empty). > > route_local=" -net " > > route_default=" default " > > > > So, two actions are needed. The route_default line from rc.network should > > get deleted, and the comment > > in rc.conf for the defaultrouter variable should be clearer. > > > > If others agree, I can go and commit the fixes for that .... > > Don't! Look at rc.network again. If you don't get it, run the code with > set -vx, and see what happens. > The correct entry still is: > > defaultrouter="1.2.3.4" > > For your convenience, I'm posting the complete snipped again: > > # Configure routing > > if [ "x$defaultrouter" != "xNO" ] ; then > static_routes="default ${static_routes}" > route_default="default ${defaultrouter}" > fi > > # Set up any static routes. This should be done before router > discovery. > if [ "x${static_routes}" != "x" ]; then > for i in ${static_routes}; do > eval route_args=\$route_${i} > route add ${route_args} > done > fi > > Stefan > > -- > Stefan Bethke > Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 > D-22087 Hamburg > Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 21:55: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id BF50915CAB for ; Sun, 2 May 1999 21:54:40 -0700 (PDT) (envelope-from ck@adsu.bellsouth.com) Received: from oreo (grommit.adsu.bellsouth.com [205.152.173.122]) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) with SMTP id AAA02170 for ; Mon, 3 May 1999 00:54:26 -0400 (EDT) From: "Christian Kuhtz" To: Subject: RE: Our routed - Vern says it's old and buggy. Date: Mon, 3 May 1999 00:51:44 -0400 Message-ID: <000701be9520$a45ccd70$7aad98cd@adsu.bellsouth.com> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199905022003.QAA14116@loverso.southborough.ma.us> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Garrett Wollman speaks the truth when he says: > > > I can't quite figure why they stuck the word "open" in there, > because it > > > couldn't possibly be more open than RIP. > > > > Because a previous link-state (aka shortest-path-first) routing > > protocol had been deployed which was not. If you're referring to IGRP, IGRP (or EIGRP for that matter) is not link-state/SPF/Dijkstra, but rather a distance vector algorithm (DUAL). The only other commonly used SPF algorithm is IS-IS. Cheers, Chris -- BellSouth Corporation, Advanced Data Services, Sr. Network Architect ck@adsu.bellsouth.com -wk, ck@gnu.org -hm "Affiliation given for identification, not representation." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 22:36:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 5B25014F4F; Sun, 2 May 1999 22:36:42 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 10eBPN-000Mpx-00; Mon, 3 May 1999 01:36:49 -0400 To: paul@originative.co.uk Cc: tanimura@naklab.dnj.ynu.ac.jp, nox@jelal.kn-bremen.de, zinnia@jan.ne.jp, freebsd-current@freebsd.org, freebsd-multimedia@freebsd.org From: "Gary Palmer" Subject: Re: Call for Review: Voxware midi driver for serial ports In-reply-to: Your message of "Sun, 02 May 1999 22:19:23 BST." Date: Mon, 03 May 1999 01:36:49 -0400 Message-ID: <87788.925709809@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG paul@originative.co.uk wrote in message ID : > The Acorn used a 6502. They went on to produce a box in the UK called the > BBC Computer. It was *way* ahead of it's time, I still have it in the > garage. Graphics resolutions that were better than the IBM PC that came > later, 3 channel sound capability, the ability to add a second processor, an > OS that was really neat. It was one nice piece of kit, ahh nostalgia. Hrm? If it was '93, it was more likely to be the Archimedes, which came out in '87 or '88. That used the ``ARM'' home-grown processor. In '93, it could have even been an ARM3. The ARM2 ran at a whopping 8MHz! (well, it was 12MHz I think, but after DRAM refresh (which paused the CPU, from memory) it was effectively 8MHz) Gary (who misses well-designed computers like the BBC B and Archimedes. Makes the PC look like a pile of components which fell into a case and somehow managed to work) -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 23:35:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 53B0114C9E for ; Sun, 2 May 1999 23:35:56 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA18409; Mon, 3 May 1999 08:35:39 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905030635.IAA18409@freebsd.dk> Subject: Re: New ATA drivers problem? (Was: New kernels won't boot) In-Reply-To: <199905030228.KAA24613@ariadne.tensor.pgs.com> from Stephen Hocking-Senior Programmer PGS Tensor Perth at "May 3, 1999 10:28:19 am" To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Date: Mon, 3 May 1999 08:35:39 +0200 (CEST) Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > Soren, I did a bit of experimenting with my CVS archive and found that version > 1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed > out errors about unexpected interrupts whilst probing and eventually hung, and > 1.10 gave the unable to mount wd0s2a errors we all love. Hmm, since the only changes are those to support newbus, thats probably where we should find the problem. There has been a fair number of other reports of sound not working etc etc, it might be that we have a problem here with certain HW. COuld you mail me a verbose dmesg when you have the 1.8 and when the 1.10 version ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 2 23:46:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 39A7214CCA for ; Sun, 2 May 1999 23:46:24 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id CAA24080; Mon, 3 May 1999 02:06:18 -0500 (EST) Date: Mon, 3 May 1999 02:06:16 -0500 (EST) From: Alfred Perlstein To: current@freebsd.org Cc: luigi@iet.unipi.it Subject: bridge+dummynet + "sysctl -a" panics in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in, doing a "sysctl -a" will panic the box. (currproc == sysctl) i have both bridging and ipfw enabled on the bridged packets, my de0 card has no ip and my xl0 card does. if you aren't easily able to reproduce it, i'll try harder, i've just been quite busy. This is on -current as of a few days ago, and is still a problem on -current today 5/2/99 Also, could someone consider this patch to the rc system to enable bridging in network_pass1() ? Index: rc.network =================================================================== RCS file: /home/ncvs/src/etc/rc.network,v retrieving revision 1.44 diff -u -r1.44 rc.network --- rc.network 1999/04/12 15:26:41 1.44 +++ rc.network 1999/05/03 10:41:06 @@ -50,6 +50,18 @@ fi done + # Enable bridging. + if [ "x$bridge_enable" = "xYES" ]; then + sysctl -w net.link.ether.bridge=1 >/dev/null 2>&1 + echo -n "Bridging started" + # IPFW the bridged packets. + if [ "x$bridge_enable_ipfw" = "xYES" ]; then + sysctl -w net.link.ether.bridge_ipfw=1 >/dev/null 2>&1 + echo -n ", filtering with ipfw enabled" + fi + echo "." + fi + # Set up all the network interfaces, calling startup scripts if needed for ifn in ${network_interfaces}; do if [ -e /etc/start_if.${ifn} ]; then Index: defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.8 diff -u -r1.8 rc.conf --- rc.conf 1999/04/10 10:56:56 1.8 +++ rc.conf 1999/05/03 10:42:11 @@ -35,6 +35,8 @@ firewall_script="/etc/rc.firewall" # Which script to run to set up the firewall firewall_type="UNKNOWN" # Firewall type (see /etc/rc.firewall) firewall_quiet="NO" # Set to YES to suppress rule display +bridge_enable="NO" # Enable bridging, "YES" == enabled +bridge_enable_ipfw="NO" # Filter bridged packets, "YES" == enabled natd_program="/sbin/natd" # path to natd, if you want a different one. natd_enable="NO" # Enable natd (if firewall_enable == YES). natd_interface="fxp0" # Public interface or IPaddress to use. thanks, -Alfred kernel config file: machine "i386" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident "router" maxusers 128 options INCLUDE_CONFIG_FILE # Include this file in kernel #CPU/Machine Options options "NO_F00F_HACK" options "AUTO_EOI_1" options "AUTO_EOI_2" options VESA options "VM86" options USER_LDT #allow user-level control of i386 ldt options KTRACE #kernel tracing options PERFMON options DDB options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L #File systems options FDESC #File descriptor filesystem options KERNFS #Kernel filesystem options UMAPFS #UID map filesystem options NULLFS #NULL filesystem options MFS #Memory File System options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=6000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console #options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #kernel tracing options SYSVSHM options SYSVSEM options SYSVMSG options MAXDSIZ=(256*1024*1024) options DFLDSIZ=(256*1024*1024) options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options "ICMP_BANDLIM" options DUMMYNET options BRIDGE config kernel root on wd0 #Devices controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 #tape ft0 at fdc0 drive 2 #IDE controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives device atapist0 # ATAPI tape drives #options "CMD640" # work around CMD640 chip deficiency #controller wdc0 at isa? port "IO_WD1" irq 14 flags 0xe0ffe0ff #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" irq 15 flags 0xe0ffe0ff #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device acd0 #IDE CD-ROM #SCSI controller scbus0 controller ahc0 device da0 device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs device od0 #See LINT for possible `od' options. device pass0 #Sound/PnP controller pnp0 device pcm0 at isa? port 0x220 irq 10 drq 3 flags 0x15 #Parrallel Port controller ppbus0 controller vpo0 at ppbus? device nlpt0 at ppbus? device ppi0 at ppbus? controller ppc0 at isa? port ? irq 7 # syscons is the default console driver, resembling an SCO console device sc0 at isa? options SC_HISTORY_SIZE=200 # number of history buffer lines options SC_DISABLE_REBOOT # disable reboot key sequence # The keyboard controller; it controlls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at atkbdc? irq 1 # PS/2 mouse device psm0 at atkbdc? irq 12 # The video card driver. device vga0 at isa? port ? conflicts # Splash screen at start up! Screen savers require this too. pseudo-device splash device npx0 at nexus? port "IO_NPX" irq 13 # Laptop support (see LINT for more options) device apm0 at nexus? disable flags 0x31 # Advanced Power Management device sio0 at isa? port "IO_COM1" irq 4 device sio1 at isa? port "IO_COM2" irq 3 device sio2 at isa? port "IO_COM3" irq 5 device sio3 at isa? port "IO_COM4" irq 9 # USB support # UHCI controller #controller uhci0 # OHCI controller #controller ohci0 # General USB code (mandatory for USB) #controller usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # # USB mouse #device ums0 # USB keyboard #device ukbd0 # USB printer #device ulpt0 # USB hub (kind of mandatory, no other driver is available for the root hub) #device uhub0 # USB communications driver #device ucom0 ## USB modem driver #device umodem0 # Human Interface Device (anything with buttons and dials) #device hid0 # Generic USB device driver #device ugen0 controller smbus0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? device bktr0 # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device fxp0 device xl0 device de0 # DEC/Intel DC21x4x (``Tulip'') device ed0 at pci? #device ed0 at isa? port 0x320 net irq 5 iomem 0xd8000 pseudo-device vn 4 pseudo-device loop pseudo-device ether pseudo-device sl 2 pseudo-device ppp 2 pseudo-device tun 2 pseudo-device pty 256 pseudo-device bpfilter 4 pseudo-device snp 4 pseudo-device gzip # Exec gzipped a.out's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 0: 4: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 0101314F41; Mon, 3 May 1999 00:02:36 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA05278; Mon, 3 May 1999 00:00:05 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA06239; Mon, 3 May 1999 00:00:04 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id XAA00467; Sun, 2 May 1999 23:58:42 -0700 (PDT) From: Don Lewis Message-Id: <199905030658.XAA00467@salsa.gv.tsc.tdk.com> Date: Sun, 2 May 1999 23:58:42 -0700 In-Reply-To: Mike Smith "Re: ppbus causes hangs?" (Apr 29, 7:41pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Mike Smith , Eric@FreeBSD.ORG Subject: Re: ppbus causes hangs? Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 29, 7:41pm, Mike Smith wrote: } Subject: Re: ppbus causes hangs? } } Try setting the flags on the 'ppc' device to 0x40 and _please_ report } the results. I also ran into this problem with a 4/30/1999 version of 3.1-stable on a Dell Dimension XPS R400. The 0x40 flag fixed the problem. BTW, the UPDATING file on the RELENG_3 branch hasn't been updated since the branch point, so there is no info on the ppbus stuff and the post-branch enhancements to the loader. Also, src/sys/boot/README hasn't been added to the RELENG_3 branch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 0:12:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id EE18415453; Mon, 3 May 1999 00:12:19 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA05364; Mon, 3 May 1999 00:12:12 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA06293; Mon, 3 May 1999 00:12:11 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA00521; Mon, 3 May 1999 00:12:10 -0700 (PDT) From: Don Lewis Message-Id: <199905030712.AAA00521@salsa.gv.tsc.tdk.com> Date: Mon, 3 May 1999 00:12:09 -0700 In-Reply-To: Don Lewis "Re: ppbus causes hangs?" (May 2, 11:58pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Don Lewis , Mike Smith , Eric@FreeBSD.ORG Subject: Re: ppbus causes hangs? Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On May 2, 11:58pm, Don Lewis wrote: } Subject: Re: ppbus causes hangs? } On Apr 29, 7:41pm, Mike Smith wrote: } } Subject: Re: ppbus causes hangs? } } } } Try setting the flags on the 'ppc' device to 0x40 and _please_ report } } the results. } } I also ran into this problem with a 4/30/1999 version of 3.1-stable } on a Dell Dimension XPS R400. The 0x40 flag fixed the problem. I forgot to include /var/run/dmesg.boot. Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #1: Fri Apr 30 22:18:51 PDT 1999 gdonl@gvpc85.gv.tsc.tdk.com:/usr/src/sys/compile/TSC_INTERNAL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (398.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 67108864 (65536K bytes) config> di wt0 config> di mcd0 config> di matcdc0 config> di scd0 config> di ie0 config> di aha0 avail memory = 62017536 (60564K bytes) Preloaded elf kernel "kernel" at 0xc031c000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031c09c. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 fxp0: rev 0x02 int a irq 11 on pci0.13.0 fxp0: Ethernet address 00:a0:c9:75:7c:8f fxp1: rev 0x02 int a irq 15 on pci0.15.0 fxp1: Ethernet address 00:a0:c9:75:7b:99 ahc0: rev 0x00 int a irq 9 on pci0.16.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: vga0: rev 0x21 int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 not found at 0x170 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 2 seconds for SCSI devices to settle changing root device to da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8709MB (17836668 512 byte sectors: 255H 63S/T 1110C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 0:36:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 08BF91560F for ; Mon, 3 May 1999 00:36:07 -0700 (PDT) (envelope-from brad@mail.his.com) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with SMTP id JAA16615; Mon, 3 May 1999 09:35:27 +0200 (MET DST) In-Reply-To: <19990501095604.W80561@freebie.lemis.com> X-Mailer: CTM PowerMail 2.4 x-sender: brad@mail.his.com Date: Mon, 3 May 1999 09:31:44 +0200 To: Greg Lehey Cc: FreeBSD current users From: Brad Knowles Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... Message-Id: <19990503093144.009661@relay.skynet.be> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 1, 1999, Greg Lehey wrote: >I don't really understand why you ask a FreeBSD group about it; it's a >Linux issue. BTW, I asked here in addition to many other places, including the linux-kernel mailing list, comp.os.linux.misc, and at least one person who's got some other Linux benchmarking tools and is relatively knowledgable on the subject. This is just the first place I've asked where I've gotten any semi-intelligble answers so far. -- Brad Knowles Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 0:51:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 7F9601517F for ; Mon, 3 May 1999 00:51:40 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id RAA16010; Mon, 3 May 1999 17:59:41 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905030759.RAA16010@cimlogic.com.au> Subject: Re: Porting Greg Lehey's rawio.c from FreeBSD to Linux... In-Reply-To: <19990503093144.009661@relay.skynet.be> from Brad Knowles at "May 3, 1999 9:31:44 am" To: brad@shub-internet.org (Brad Knowles) Date: Mon, 3 May 1999 17:59:38 +1000 (EST) Cc: grog@lemis.com, FreeBSD-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > On Sat, May 1, 1999, Greg Lehey wrote: > > >I don't really understand why you ask a FreeBSD group about it; it's a > >Linux issue. > > BTW, I asked here in addition to many other places, including the > linux-kernel mailing list, comp.os.linux.misc, and at least one person > who's got some other Linux benchmarking tools and is relatively > knowledgable on the subject. This is just the first place I've asked > where I've gotten any semi-intelligble answers so far. There's a moral there somewhere. 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 1: 5:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id E3BC214C36 for ; Mon, 3 May 1999 01:04:59 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA21599; Mon, 3 May 1999 07:52:33 +0200 From: Luigi Rizzo Message-Id: <199905030552.HAA21599@labinfo.iet.unipi.it> Subject: Re: bridge+dummynet + "sysctl -a" panics in -current To: bright@rush.net (Alfred Perlstein) Date: Mon, 3 May 1999 07:52:33 +0200 (MET DST) Cc: current@freebsd.org, luigi@iet.unipi.it In-Reply-To: from "Alfred Perlstein" at May 3, 99 02:05:57 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 802 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in, > doing a "sysctl -a" will panic the box. (currproc == sysctl) if you think the panic is bridge-related, can you try manually the net.link.ether.bridge* sysctl -- if they do not fail, then the problem could be with the sysctl to fetch bridging statistics (and if you have a recent system, "netstat -p bdg" should exercise that. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 1:34:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 0005C14E35; Mon, 3 May 1999 01:34:31 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA66697; Mon, 3 May 1999 09:34:48 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 3 May 1999 09:34:48 +0100 (BST) From: Doug Rabson To: Stefan Bethke Cc: freebsd-current@freebsd.org, sos@freebsd.org Subject: Re: ata and IRQ sharing (was: panic in nexus_setup_intr+0x13 with new ata driver) In-Reply-To: <15018945.3134674456@monster.transit-a.hanse.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 May 1999, Stefan Bethke wrote: > --On Son, 2. Mai 1999 19:32 Uhr +0200 Stefan Bethke > wrote: > > > I'm currently trying to get a Promise Ultra/33 to work with Sørens new ata > > drivers. > > I've delved into the code a bit more. The panic results from > ata_pciattach() not checking whether an IRQ resource could be allocated. > > Ths seems to stem from the fact that the IRQ is already taken by an ed PCI > card. I've added RF_SHAREABLE to the bus_alloc_resource() flags, and was > able to bring up the kernel fine. However, ed0 reported constant device > timeouts, and accessing wd0 resulted in an endless wait for an interrupt. > > Removing the ed card makes the Promise controller work. I'm getting about > 7MB/s from an IBM DTTA 350840, which should be normal. > > The board I'm currently trying this on is an Asus SP3, having the > mis-feature of only having a single INTA for all three PCI slots (IRQ 5 in > my case). > > Now, PCI does support interrupt sharing, but in this case it might be > broken: > - in the chipset (but it worked with both an ed and ncr card installed) > - in the newbus stuff > - in the Promise controller > - somewhere in promise_intr > > Would someone care to shed some light on this? > > I will try to do some tests on an Asus SP3G, which does have seperate INTAs > per PCI slot. Are you saying that the ISA driver for the ed card is sharing an interrupt with the pci IDE card? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 2:33:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id 6AD1814BD7; Mon, 3 May 1999 02:33:13 -0700 (PDT) (envelope-from stefan@promo.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id LAA24802; Mon, 3 May 1999 11:32:30 +0200 (CEST) Date: Mon, 03 May 1999 11:32:00 +0200 From: Stefan Bethke To: Doug Rabson Cc: freebsd-current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ata and IRQ sharing (was: panic in nexus_setup_intr+0x13 with new ata driver) Message-ID: <212535.3134719920@d225.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Sun, 2 May 1999, Stefan Bethke wrote: > >> --On Son, 2. Mai 1999 19:32 Uhr +0200 Stefan Bethke >> wrote: >> >> > I'm currently trying to get a Promise Ultra/33 to work with S=F8rens = new >> > ata drivers. >> >> I've delved into the code a bit more. The panic results from >> ata_pciattach() not checking whether an IRQ resource could be = allocated. >> >> Ths seems to stem from the fact that the IRQ is already taken by an ed >> PCI card. > > Are you saying that the ISA driver for the ed card is sharing an = interrupt > with the pci IDE card? No, it's a generic NE2000-clone PCI card. The combination NE2000 + NCR810 card works fine with the sahred IRQ5 (I've just checked again). (Well, "fine" is a bit optimistic. If I really beat both of them [cvs update from an NFS repo to a fast disk on the NCR], I = get device timeouts, but generally it works.) -- Stefan Bethke Promo Datentechnik | Tel. +49-40-851744-18 + Systemberatung GmbH | Fax. +49-40-851744-44 Eduardstrasse 46-48 | e-mail: stefan@Promo.DE D-20257 Hamburg | http://www.Promo.DE/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 2:41:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id D261014EF9 for ; Mon, 3 May 1999 02:41:49 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.3/8.9.0.Beta6) with ESMTP id FAA05817 for ; Mon, 3 May 1999 05:41:46 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.0.Beta6) with SMTP id FAA19625 for ; Mon, 3 May 1999 05:41:42 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.0.Beta6) with SMTP id FAA19619 for ; Mon, 3 May 1999 05:41:41 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Mon, 3 May 1999 05:41:41 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: Q3 test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As we probably all know, Q3 test is out for Linux. I tested it on FreeBSD, with great results. I just downloaded the correct glide libraries from the site suggested by Carmac (Q3 programmer) and installed those, and then I added the appropriate resoulutions to my configuration. Kenneth Culver Computer Science Major at the University of Maryland, College Park. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 2:52:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5BED014A2E; Mon, 3 May 1999 02:52:40 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA18845; Mon, 3 May 1999 11:52:29 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905030952.LAA18845@freebsd.dk> Subject: Re: ata and IRQ sharing (was: panic in nexus_setup_intr+0x13 with new ata driver) In-Reply-To: <212535.3134719920@d225.promo.de> from Stefan Bethke at "May 3, 1999 11:32: 0 am" To: stefan@promo.de (Stefan Bethke) Date: Mon, 3 May 1999 11:52:29 +0200 (CEST) Cc: dfr@nlsystems.com, freebsd-current@FreeBSD.ORG, sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Stefan Bethke wrote: > >> > I'm currently trying to get a Promise Ultra/33 to work with Sørens new > >> > ata drivers. > >> > >> I've delved into the code a bit more. The panic results from > >> ata_pciattach() not checking whether an IRQ resource could be allocated. > >> > >> Ths seems to stem from the fact that the IRQ is already taken by an ed > >> PCI card. > > > > Are you saying that the ISA driver for the ed card is sharing an interrupt > > with the pci IDE card? > > No, it's a generic NE2000-clone PCI card. > > The combination NE2000 + NCR810 card works fine with the sahred IRQ5 (I've > just checked again). (Well, "fine" is a bit optimistic. If I really beat > both of them [cvs update from an NFS repo to a fast disk on the NCR], I get > device timeouts, but generally it works.) Does the NCR driver still support the "poll" mode ?? if so that might be why it works, the NCR driver doesn't use the intr after it timed out sufficently many times, this tricked me once under the old SCSI system... The ata driver should check for getting a "real" interrupt though... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 3:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id B766A15589; Mon, 3 May 1999 03:20:26 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id MAA26238; Mon, 3 May 1999 12:17:59 +0200 (CEST) Date: Mon, 03 May 1999 12:17:28 +0200 From: Stefan Bethke To: Soren Schmidt Cc: dfr@nlsystems.com, freebsd-current@FreeBSD.ORG, sos@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: ata and IRQ sharing (was: panic in nexus_setup_intr+0x13 with new ata driver) Message-ID: <376758.3134722648@d225.promo.de> In-Reply-To: <199905030952.LAA18845@freebsd.dk> Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Stefan Bethke wrote: >> >> > I'm currently trying to get a Promise Ultra/33 to work with = S=F8rens >> >> > new ata drivers. >> >> >> >> I've delved into the code a bit more. The panic results from >> >> ata_pciattach() not checking whether an IRQ resource could be >> >> allocated. >> >> >> >> Ths seems to stem from the fact that the IRQ is already taken by an = ed >> >> PCI card. >> > >> > Are you saying that the ISA driver for the ed card is sharing an >> > interrupt with the pci IDE card? >> >> No, it's a generic NE2000-clone PCI card. >> >> The combination NE2000 + NCR810 card works fine with the sahred IRQ5 >> (I've just checked again). (Well, "fine" is a bit optimistic. If I >> really beat both of them [cvs update from an NFS repo to a fast disk on >> the NCR], I get device timeouts, but generally it works.) > > Does the NCR driver still support the "poll" mode ?? if so that might > be why it works, the NCR driver doesn't use the intr after it timed out > sufficently many times, this tricked me once under the old SCSI = system... Wouldn't that mean that the performance would be greatly reduced? Anyway, I'll try tonite with debugging enabled for pci/ncr.c. > The ata driver should check for getting a "real" interrupt though... That would be nice to have, but as interrupt sharing is legal, and my crappy m/b doesn't have seperate INTAs per slot, it would be even nicer if the ata driver would support it, if at all possible... Stefan -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 4:28:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id CE099150AC for ; Mon, 3 May 1999 04:28:53 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id MAA67218; Mon, 3 May 1999 12:29:01 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 3 May 1999 12:29:00 +0100 (BST) From: Doug Rabson To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: Q3 test In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 May 1999, Kenneth Wayne Culver wrote: > As we probably all know, Q3 test is out for Linux. I tested it on FreeBSD, > with great results. I just downloaded the correct glide libraries from the > site suggested by Carmac (Q3 programmer) and installed those, and then I > added the appropriate resoulutions to my configuration. How about a port :-) -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 6:39:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 75AA814F6A for ; Mon, 3 May 1999 06:39:42 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id PAA10660 for ; Mon, 3 May 1999 15:39:33 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.2/8.9.2) id PAA20535 for freebsd-current@freebsd.org; Mon, 3 May 1999 15:39:32 +0200 (CEST) From: Rudolf Cejka Message-Id: <199905031339.PAA20535@kazi.dcse.fee.vutbr.cz> Subject: Jail - any success? To: freebsd-current@freebsd.org (freebsd-current@freebsd.org) Date: Mon, 3 May 1999 15:39:32 +0200 (CEST) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to test the new jail feature. It looks it works. But I can't find, how to setup the network communication. Is there anybody who successfully took a run of jail virtual serverrs with networking? Thanks for any suggestions. --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--= Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 6:52:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id A299E15262 for ; Mon, 3 May 1999 06:52:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA29437; Mon, 3 May 1999 15:52:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA08000; Mon, 3 May 1999 15:52:34 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Rudolf Cejka Cc: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) Subject: Re: Jail - any success? In-reply-to: Your message of "Mon, 03 May 1999 15:39:32 +0200." <199905031339.PAA20535@kazi.dcse.fee.vutbr.cz> Date: Mon, 03 May 1999 15:52:34 +0200 Message-ID: <7998.925739554@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905031339.PAA20535@kazi.dcse.fee.vutbr.cz>, Rudolf Cejka writes: > >I'm trying to test the new jail feature. It looks it works. But I can't >find, how to setup the network communication. Is there anybody who >successfully took a run of jail virtual serverrs with networking? You need to put ip aliases on your loopback interface, forinstance: ifconfig lo0 10.0.0.1 netmask 255.255.255.255 alias ifconfig lo0 10.0.0.2 netmask 255.255.255.255 alias ifconfig lo0 10.0.0.3 netmask 255.255.255.255 alias ifconfig lo0 10.0.0.4 netmask 255.255.255.255 alias ifconfig lo0 10.0.0.5 netmask 255.255.255.255 alias Then you give each jail one of these ipnumbers and start whatever daemons you want in the jail (inetd, sshd, apache...) Of course your routing needs to work such that these ip numbers end up on your machine, you can also do this by adding multiple IP# to the ethernet of the machine. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 7:16: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id 5AF4315408 for ; Mon, 3 May 1999 07:15:59 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id HAA10579; Mon, 3 May 1999 07:15:15 -0700 (PDT) Message-ID: <372DAF3B.44D44B9C@seattleu.edu> Date: Mon, 03 May 1999 07:14:19 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: Q3 test References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > > As we probably all know, Q3 test is out for Linux. I tested it on FreeBSD, > with great results. I just downloaded the correct glide libraries from the > site suggested by Carmac (Q3 programmer) and installed those, and then I > added the appropriate resoulutions to my configuration. Or a link to the correct libraries. -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 7:50:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 290D115091 for ; Mon, 3 May 1999 07:50:17 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-12-99.camtech.net.au [203.55.242.99]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id AAA08725 for ; Tue, 4 May 1999 00:25:36 +0930 (CST) Message-ID: <372DB7E6.8D66DCDF@camtech.com.au> Date: Tue, 04 May 1999 00:21:18 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Silo overflows and MAME can someone else reproduce this problem ?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This problem is easily reproducible. However to do so, you need a ROM image for an arcade game that the Multi Arcade Machine Emulator emulates as it wont do it without any roms in the directory "/usr/local/lib/mame/roms". I am using xmame installed from the ports collection (/usr/ports/emulators/xmame) on a very recent -CURRENT machine. If I run xmame *before* I get online with user mode ppp (or while I am on the net), the serial ports get hosed and I have to reboot or I continually get silo overflows. This is not right as it happens AFTER I exit xmame !!! Please can someone else reproduce this problem as I'd hate to think its only on the systems I have owned (Pentium 166 and Celeron 300). -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 7:53:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 473A014E0F for ; Mon, 3 May 1999 07:53:25 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-12-99.camtech.net.au [203.55.242.99]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id AAA09013 for ; Tue, 4 May 1999 00:28:44 +0930 (CST) Message-ID: <372DB8A1.89159C49@camtech.com.au> Date: Tue, 04 May 1999 00:24:25 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Silo overflows and MAME can someone else reproduce this problem ?? References: <372DB7E6.8D66DCDF@camtech.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My usermode ppp works fine normally as I can quite happily download 4 things at once without a single silo overflow (as I did last night) even when there is lots of disk activity or X11 activity. Note this problem is unrelated to newbus as it occurs both before and after those commits. Matthew Thyer wrote: > > This problem is easily reproducible. > > However to do so, you need a ROM image for an arcade game that the > Multi Arcade Machine Emulator emulates as it wont do it without any > roms in the directory "/usr/local/lib/mame/roms". > > I am using xmame installed from the ports collection > (/usr/ports/emulators/xmame) on a very recent -CURRENT machine. > > If I run xmame *before* I get online with user mode ppp (or while > I am on the net), the serial ports get hosed and I have to reboot > or I continually get silo overflows. > > This is not right as it happens AFTER I exit xmame !!! > > Please can someone else reproduce this problem as I'd hate to think > its only on the systems I have owned (Pentium 166 and Celeron 300). > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 8:38:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from psycho.h4x0rz.za.org (psycho.h4x0rz.za.org [206.49.228.8]) by hub.freebsd.org (Postfix) with ESMTP id A8E30152A3 for ; Mon, 3 May 1999 08:38:29 -0700 (PDT) (envelope-from andrew@psycho.h4x0rz.za.org) Received: from localhost (andrew@localhost) by psycho.h4x0rz.za.org (8.9.3/8.9.2) with ESMTP id RAA00647; Mon, 3 May 1999 17:39:17 +0200 (SAST) (envelope-from andrew@psycho.h4x0rz.za.org) Date: Mon, 3 May 1999 17:39:17 +0200 (SAST) From: vortexia To: Matthew Thyer Cc: freebsd-current@FreeBSD.ORG Subject: Re: Silo overflows and MAME can someone else reproduce this problem ?? In-Reply-To: <372DB8A1.89159C49@camtech.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Im getting continous overflows on sio0 after I shutdown X no matter what I do, even when there is NOTHING else running, the moment I shutdown X and I move my mouse I get tons of overflows. I have no pppd running at all and no moused, any ideas? Cheers Andrew On Tue, 4 May 1999, Matthew Thyer wrote: > My usermode ppp works fine normally as I can quite happily download > 4 things at once without a single silo overflow (as I did last night) > even when there is lots of disk activity or X11 activity. > > Note this problem is unrelated to newbus as it occurs both before and > after those commits. > > Matthew Thyer wrote: > > > > This problem is easily reproducible. > > > > However to do so, you need a ROM image for an arcade game that the > > Multi Arcade Machine Emulator emulates as it wont do it without any > > roms in the directory "/usr/local/lib/mame/roms". > > > > I am using xmame installed from the ports collection > > (/usr/ports/emulators/xmame) on a very recent -CURRENT machine. > > > > If I run xmame *before* I get online with user mode ppp (or while > > I am on the net), the serial ports get hosed and I have to reboot > > or I continually get silo overflows. > > > > This is not right as it happens AFTER I exit xmame !!! > > > > Please can someone else reproduce this problem as I'd hate to think > > its only on the systems I have owned (Pentium 166 and Celeron 300). > > > -- > /=======================================================================\ > | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | > \=======================================================================/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 8:42:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (Postfix) with ESMTP id 7DC451513C for ; Mon, 3 May 1999 08:42:26 -0700 (PDT) (envelope-from joe@monk.via.net) Received: (from joe@localhost) by monk.via.net (8.8.8/8.8.8) id IAA24356; Mon, 3 May 1999 08:42:12 -0700 (PDT) (envelope-from joe) From: Joe McGuckin Message-Id: <199905031542.IAA24356@monk.via.net> Date: Mon, 3 May 1999 08:42:11 -0700 (PDT) To: johan@granlund.nu Cc: current@FreeBSD.ORG Subject: Re[2]: Our routed - Vern says it's old and buggy. In-Reply-To: X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's 'open' as in an "open specifiaction". The algorithm was openly published - unlike some other competing routing protocols. Joe Johan Granlund wrote: > > > On Wed, 28 Apr 1999, Chuck Robey wrote: > > > On Wed, 28 Apr 1999, Matthew Dillon wrote: > > > > > > > > :Matthew Dillon writes: > > > > I can't quite figure why they stuck the word "open" in there, because it > > couldn't possibly be more open than RIP. > > Probably beqause they stuck "OPEN" on _everything_ for a while. It drowe > me nuts:) > > /Johan > > > > > > > > > OSPF has been around for a long time. > > > > But RIP is older, and was the first routing scheme. > > > > > > > > -Matt > > > Matthew Dillon > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run picnic (FreeBSD-current) > > (301) 220-2114 | and jaunt (Solaris7). > > ----------------------------+----------------------------------------------- > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Joe McGuckin ViaNet Communications 1235 Pear Ave, Suite 107 Mountain View, CA 90403 Phone: 650-969-2203 Cell: 415-710-4894 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 9:36:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 7F69F154A2 for ; Mon, 3 May 1999 09:36:35 -0700 (PDT) (envelope-from rgrimes@gndrsh.dnsmgr.net) Received: (from rgrimes@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA00473; Mon, 3 May 1999 09:35:31 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199905031635.JAA00473@gndrsh.dnsmgr.net> Subject: Re: default route not set up?? In-Reply-To: <372C8EF0.DCE3BD49@odin-corporation.com> from Lars Fredriksen at "May 2, 1999 12:44:16 pm" To: lars@odin-corporation.com (Lars Fredriksen) Date: Mon, 3 May 1999 09:35:31 -0700 (PDT) Cc: braukmann@tse-online.de (Andreas Braukmann), current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > There are two things going on with the route setup. > > if [ "x$defaultrouter" != "xNO" ] ; then > static_routes="default ${static_routes}" > route_default="default ${defaultrouter}" > fi > > > 1) since route_default is never used, it should be deleted, ignore that > line above. Wrong, it is evaluated when this line is executed: eval route_args=\$route_${i} I wrote this code 4 years ago, it works, has been working and will continue to work. Please, just leave the static/default route stuff alone. > > 2) if you set defaultrouter to anything other than "NO", the > static_route variable gets a "default" route > route label added, and this label will get evaled later on. > > So rc.conf should read: (example from my setup) > > > defaultrouter="YES" # Set to default gateway (or NO). No, the comment is correct as it stands, set it to ``NO'' or set it to the IP address of the defaultroute + any funky route flags you may want on it. > static_routes="local" # Set to static route list (or leave > empty). > route_local=" -net " > route_default=" default " Boo bad, your value of route_default will be smashed by rc.network when it does ``route_default="default ${defaultrouter}"''. You'll end up with the command ``route add default YES'' being executed, not something you really want :-) > > So, two actions are needed. The route_default line from rc.network should > get deleted, and the comment > in rc.conf for the defaultrouter variable should be clearer. > > If others agree, I can go and commit the fixes for that .... NO! Do not agree, read and understand what the trick above is, ``eval route_args=\${route_${i}'' when $i="default'' grabs the route_default for you. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 10: 7:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 394C5153CB for ; Mon, 3 May 1999 10:07:25 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id NAA09929 for ; Mon, 3 May 1999 13:07:25 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA06682; Mon, 3 May 1999 13:06:55 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id NAA67736 for freebsd-current@freebsd.org; Mon, 3 May 1999 13:06:55 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905031706.NAA67736@bb01f39.unx.sas.com> Subject: make release & perl version failure To: freebsd-current@freebsd.org Date: Mon, 3 May 1999 13:06:55 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I don't know if anyone has seen this yet, but from last nights 'make release' I get the following failure .... touch release.2 Making docs... ===> Extracting for docproj-1.0 >> No MD5 checksum file. ===> Patching for docproj-1.0 ===> Configuring for docproj-1.0 ===> Installing for docproj-1.0 ===> docproj-1.0 depends on executable: instant - not found ===> Verifying install for instant in /usr/ports/textproc/sgmlformat Error: you don't have the right version of perl in /usr/bin. *** Error code 1 It looks like the perl updates that went in have some side effects... Later, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 10:36:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id BE7D315447 for ; Mon, 3 May 1999 10:36:29 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA10201 for freebsd-current@freebsd.org; Mon, 3 May 1999 10:36:28 -0700 (PDT) From: Archie Cobbs Message-Id: <199905031736.KAA10201@bubba.whistle.com> Subject: traceroute patch To: freebsd-current@freebsd.org Date: Mon, 3 May 1999 10:36:28 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have this patch for traceroute that adds the ability to send packets with an arbitrary IP protocol number, instead of just TCP and UDP. This is mainly useful to see if some router between points A and B is blocking packets based on IP protocol number. I sent it to "traceroute@ee.lbl.gov" but got no response. Is this something people might be interested in? Is it worth committing? We've found it useful on occasion. ftp://ftp.whistle.com/pub/archie/misc/traceroute.patch -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 10:57:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [206.154.101.226]) by hub.freebsd.org (Postfix) with ESMTP id C56DB14F13 for ; Mon, 3 May 1999 10:57:48 -0700 (PDT) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id KAA40870 for freebsd-current@freebsd.org; Mon, 3 May 1999 10:57:52 -0700 (PDT) (envelope-from freebsd) Posted-Date: Mon, 3 May 1999 10:57:52 -0700 (PDT) Message-Id: <199905031757.KAA40870@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Mon, 3 May 1999 10:57:51 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: Make world failing in perl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to a failed world build which rendered sendmail unable to bind to a socket, which resulted in my being apparently unsubscribed, and the fact that the mailing list indexes aren't updated for a period of days, I'm unable to to check the archives regarding this problem. Perl is failing due to some kind of conflict in library versions: miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' lib/*.pm lib/*/*.pm Perl lib version (5.00502) doesn't match executable version (5.00503) at /usr/libdata/perl/5.00503/mach/Config.pm line 7. BEGIN failed--compilation aborted at /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/AutoSplit.pm line 4. BEGIN failed--compilation aborted at -e line 1. *** Error code 255 A number of cvsup's have been performed during the last two days, and this problem has persisted, as well as clearing the source tree and cvsup'ing anew, as well as the usual obj removal and clean build. Any help is, of course, appreciated ;) staylor@mrynet.com (aka freebsd@mrynet.com) >From freebsd Mon May 3 10:56:51 1999 From: freebsd To: freebsd-current Subject: perl failure in make world Date: Mon, 3 May 1999 10:56:51 +0000 Due to a failed world build which rendered sendmail unable to bind to a socket, which resulted in my being apparently unsubscribed, and the fact that the mailing list indexes aren't updated for a period of days, I'm unable to to check the archives regarding this problem. Perl is failing due to some kind of conflict in library versions: miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' lib/*.pm lib/*/*.pm Perl lib version (5.00502) doesn't match executable version (5.00503) at /usr/libdata/perl/5.00503/mach/Config.pm line 7. BEGIN failed--compilation aborted at /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/AutoSplit.pm line 4. BEGIN failed--compilation aborted at -e line 1. *** Error code 255 A number of cvsup's have been performed during the last two days, and this problem has persisted, as well as clearing the source tree and cvsup'ing anew, as well as the usual obj removal and clean build. Any help is, of course, appreciated ;) staylor@mrynet.com (aka freebsd@mrynet.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 11: 0:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 16BF2156FD for ; Mon, 3 May 1999 11:00:42 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id NAA13712; Mon, 3 May 1999 13:20:32 -0500 (EST) Date: Mon, 3 May 1999 13:20:30 -0500 (EST) From: Alfred Perlstein To: Luigi Rizzo Cc: current@freebsd.org Subject: Re: bridge+dummynet + "sysctl -a" panics in -current In-Reply-To: <199905030552.HAA21599@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 May 1999, Luigi Rizzo wrote: > > a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in, > > doing a "sysctl -a" will panic the box. (currproc == sysctl) > > if you think the panic is bridge-related, can you try manually the > net.link.ether.bridge* sysctl -- if they do not fail, then the problem > could be with the sysctl to fetch bridging statistics (and if you have > a recent system, "netstat -p bdg" should exercise that. > ok, egg in my face, that's not it i guess. What about patching rc.network to allow early setup of bridge though? I'll try to track this down a bit better... I was experianceing it the panic earlier when i had applied matt's NFS patches, however ,my other boxes don't panic when i sysctl -a. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 11:34:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from car (unknown [193.15.1.16]) by hub.freebsd.org (Postfix) with ESMTP id 5647514E24 for ; Mon, 3 May 1999 11:34:08 -0700 (PDT) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t2o62p11.telia.com [195.198.198.71]) by car (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id UAA02656; Mon, 03 May 1999 20:34:15 +0200 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.3/8.9.3) with ESMTP id UAA07927; Mon, 3 May 1999 20:31:32 +0200 (CEST) (envelope-from johan@granlund.nu) Date: Mon, 3 May 1999 20:31:32 +0200 (CEST) From: Johan Granlund To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Netgraph Was:(Re: traceroute patch) In-Reply-To: <199905031736.KAA10201@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 May 1999, Archie Cobbs wrote: > I have this patch for traceroute that adds the ability to send [snip] How is it going with netgraph? I have looked at the -net archives on and off and it's very quit. Is it still going to be committed? /Johan > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 11:36:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 4000F14D71 for ; Mon, 3 May 1999 11:36:25 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA93103 for ; Mon, 3 May 1999 14:34:13 -0400 (EDT) Date: Mon, 3 May 1999 14:34:12 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: Protocol analyzer Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you've EVER used tcpdump, go take a look at this site, I guarantee it's worth your time: http://www.capmedia.fr/mgall/xip/ What a GREAT idea! A full graphical tcpdump! ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 11:44:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id E433215010 for ; Mon, 3 May 1999 11:44:28 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id LAA11668; Mon, 3 May 1999 11:44:14 -0700 (PDT) From: Archie Cobbs Message-Id: <199905031844.LAA11668@bubba.whistle.com> Subject: Re: Netgraph Was:(Re: traceroute patch) In-Reply-To: from Johan Granlund at "May 3, 99 08:31:32 pm" To: johan@granlund.nu (Johan Granlund) Date: Mon, 3 May 1999 11:44:14 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Granlund writes: > How is it going with netgraph? > I have looked at the -net archives on and off and it's very quit. > Is it still going to be committed? Netgraph is doing well.. several people have tried it and/or are using it. One guy in Finland has reimplemented the whole concept in Java for an industrial process automation system :-) We (Julian and myself) have been too busy with other stuff lately to do much new development. However, we have a list of things to do... hopefully we can get back to doing more development on it soon. I'm particularly interested in revamping the PPP node and making corresponding changes in mpd to support it, so that mpd+netgraph can do full kernel-only routing over any link type. Also, I'd like to netgraphify the i4b code. As for committing it, more demand/interest is needed before doing that. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 12:13:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from car (unknown [193.15.1.16]) by hub.freebsd.org (Postfix) with ESMTP id 6A639155EA for ; Mon, 3 May 1999 12:12:54 -0700 (PDT) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t6o62p22.telia.com [195.198.199.82]) by car (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id VAA02666; Mon, 03 May 1999 21:12:56 +0200 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.3/8.9.3) with ESMTP id VAA07993; Mon, 3 May 1999 21:12:04 +0200 (CEST) (envelope-from johan@granlund.nu) Date: Mon, 3 May 1999 21:12:04 +0200 (CEST) From: Johan Granlund To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: Netgraph Was:(Re: traceroute patch) In-Reply-To: <199905031844.LAA11668@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 May 1999, Archie Cobbs wrote: > Johan Granlund writes: > > How is it going with netgraph? > > I have looked at the -net archives on and off and it's very quit. > > Is it still going to be committed? > > Netgraph is doing well.. several people have tried it and/or are using it. > One guy in Finland has reimplemented the whole concept in Java for an > industrial process automation system :-) > Sounds like what i'm proposing at work only it's access control in my case. I'we got another programmer that's into alarm systems to reschool himself from windows to Unix programming. Hopefully something will become of this.... /Johan > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 12:22:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 68A6914C22; Mon, 3 May 1999 12:22:06 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA40502; Mon, 3 May 1999 21:22:05 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id VAA07443; Mon, 3 May 1999 21:22:04 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905031922.VAA07443@greenpeace.grondar.za> To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG, asami@FreeBSD.ORG Subject: Re: make release & perl version failure In-Reply-To: Your message of " Mon, 03 May 1999 13:06:55 -0400." <199905031706.NAA67736@bb01f39.unx.sas.com> References: <199905031706.NAA67736@bb01f39.unx.sas.com> Date: Mon, 03 May 1999 21:22:03 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John W. DeBoskey" wrote: > I don't know if anyone has seen this yet, but from last nights > 'make release' I get the following failure .... > > touch release.2 > Making docs... > ===> Extracting for docproj-1.0 > >> No MD5 checksum file. > ===> Patching for docproj-1.0 > ===> Configuring for docproj-1.0 > ===> Installing for docproj-1.0 > ===> docproj-1.0 depends on executable: instant - not found > ===> Verifying install for instant in /usr/ports/textproc/sgmlformat > Error: you don't have the right version of perl in /usr/bin. > *** Error code 1 > > > It looks like the perl updates that went in have some side > effects... Here's a workaround (Satoshi - your comments, please?): Index: bsd.port.mk =================================================================== RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v retrieving revision 1.311 diff -u -d -r1.311 bsd.port.mk --- bsd.port.mk 1999/04/28 06:20:12 1.311 +++ bsd.port.mk 1999/05/03 19:18:03 @@ -592,7 +592,12 @@ PKG_IGNORE_DEPENDS?= '(XFree86-3\.3\.3\.1|Motif-2\.1\.10)' +.if exists(/usr/bin/perl5.00502) PERL_VERSION= 5.00502 +.endif +.if exists(/usr/bin/perl5.00503) +PERL_VERSION= 5.00503 +.endif PERL_VER= 5.005 PERL_ARCH= ${ARCH}-freebsd PLIST_SUB+= PERL_VERSION=${PERL_VERSION} \ M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 12:45:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id BABD715674 for ; Mon, 3 May 1999 12:45:08 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca14-103.ix.netcom.com [205.186.215.103]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id MAA23887; Mon, 3 May 1999 12:45:20 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id MAA27567; Mon, 3 May 1999 12:43:21 -0700 (PDT) Date: Mon, 3 May 1999 12:43:21 -0700 (PDT) Message-Id: <199905031943.MAA27567@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: mark@grondar.za Cc: jwd@unx.sas.com, freebsd-current@FreeBSD.ORG In-reply-to: <199905031922.VAA07443@greenpeace.grondar.za> (message from Mark Murray on Mon, 03 May 1999 21:22:03 +0200) Subject: Re: make release & perl version failure From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) References: <199905031706.NAA67736@bb01f39.unx.sas.com> <199905031922.VAA07443@greenpeace.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Mark Murray * Here's a workaround (Satoshi - your comments, please?): * * Index: bsd.port.mk * =================================================================== * RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v * retrieving revision 1.311 * diff -u -d -r1.311 bsd.port.mk * --- bsd.port.mk 1999/04/28 06:20:12 1.311 * +++ bsd.port.mk 1999/05/03 19:18:03 * @@ -592,7 +592,12 @@ * * PKG_IGNORE_DEPENDS?= '(XFree86-3\.3\.3\.1|Motif-2\.1\.10)' * * +.if exists(/usr/bin/perl5.00502) * PERL_VERSION= 5.00502 * +.endif * +.if exists(/usr/bin/perl5.00503) * +PERL_VERSION= 5.00503 * +.endif * PERL_VER= 5.005 * PERL_ARCH= ${ARCH}-freebsd * PLIST_SUB+= PERL_VERSION=${PERL_VERSION} \ Eeek. I tought we were not going to do this. ;) When are you planning to merge 5.00503 to -stable? We can just bump the version and be done with it. -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 12:48:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id D7C001546E for ; Mon, 3 May 1999 12:48:53 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id MAA04807 for ; Mon, 3 May 1999 12:48:52 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199905031948.MAA04807@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: IBM's Via Voice Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 May 1999 12:48:52 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I managed to spent a few more minutes with IBM's Via Voice for linux and it appears to work on my system. The draw back is that I don't have a high quality mic right now with me (will have to dig around in my boxes for one). Pertinent information about my system: 1 FreeBSD 4.0 current as of a couple of weeks old 2 GUS PnP with Voxware sound driver (full duplex mode) 3 downloaded the following linux rpms: 4. installed the latest linux_lib port 5 installed rpm2cpio port 6. downloaded the following rpm pacakges location what ftp.redhat.com libstdc++-2.9.0-12.i386.rpm www.lesstiff.org lesstif-0.86.9-linux.tar.gz cd /compat/linux rpmcpio | cpio --extract --make-directories --verbose 7. and of course download ViaVoice from : http://www.software.ibm.com/is/voicetype/dev_linux.html To install follow the instructions above for linux rpm packages 8. Run the audio setup program: /compat/linux/usr/bin/audiog Caveat : you may have to play with "mixer" to properly adjust your microphone input. Enjoy -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 12:54:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id AF78315740; Mon, 3 May 1999 12:54:04 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA40617; Mon, 3 May 1999 21:54:02 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id VAA07901; Mon, 3 May 1999 21:54:01 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905031954.VAA07901@greenpeace.grondar.za> To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: freebsd-current@FreeBSD.ORG Subject: Re: make release & perl version failure In-Reply-To: Your message of " Mon, 03 May 1999 12:43:21 MST." <199905031943.MAA27567@silvia.hip.berkeley.edu> References: <199905031706.NAA67736@bb01f39.unx.sas.com> <199905031922.VAA07443@greenpeace.grondar.za> <199905031943.MAA27567@silvia.hip.berkeley.edu> Date: Mon, 03 May 1999 21:53:59 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * +.if exists(/usr/bin/perl5.00502) > * PERL_VERSION= 5.00502 > * +.endif > * +.if exists(/usr/bin/perl5.00503) > * +PERL_VERSION= 5.00503 > * +.endif : > Eeek. I tought we were not going to do this. ;) Erm, that was before you made life so easy :-) > When are you planning to merge 5.00503 to -stable? We can just bump > the version and be done with it. I'll do it tomorrow if I have half a clue that the rest of core will buy it... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 13:24:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 7727814EA6 for ; Mon, 3 May 1999 13:24:02 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.144]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2C85; Mon, 3 May 1999 22:24:01 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id WAA00663; Mon, 3 May 1999 22:24:52 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 03 May 1999 22:24:51 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Chuck Robey Subject: RE: Protocol analyzer Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-May-99 Chuck Robey wrote: > If you've EVER used tcpdump, go take a look at this site, I guarantee > it's worth your time: > > http://www.capmedia.fr/mgall/xip/ > > What a GREAT idea! A full graphical tcpdump! Damn, another project down the wastebasket =P --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 13:32:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id EEBB114A2E for ; Mon, 3 May 1999 13:32:47 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.144]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA32DB; Mon, 3 May 1999 22:32:46 +0200 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id WAA02043; Mon, 3 May 1999 22:33:37 +0200 (CEST) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 03 May 1999 22:33:36 +0200 (CEST) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Chuck Robey Subject: RE: Protocol analyzer Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-May-99 Chuck Robey wrote: > If you've EVER used tcpdump, go take a look at this site, I guarantee > it's worth your time: > > http://www.capmedia.fr/mgall/xip/ > > What a GREAT idea! A full graphical tcpdump! Also has some probs compiling... Looking at it... Might be nice to have in the ports *chuckle* --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 15: 4:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from sakaki.communique.net (sakaki.communique.net [204.27.64.202]) by hub.freebsd.org (Postfix) with ESMTP id E747E151A8 for ; Mon, 3 May 1999 15:04:36 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by sakaki.communique.net (8.8.8/8.8.8) with ESMTP id RAA19368; Mon, 3 May 1999 17:04:35 -0500 (CDT) Received: from spawn.nectar.com (spawn.nectar.com [10.0.0.101]) by cerebus.nectar.com (Postfix) with ESMTP id 6F71B38; Mon, 3 May 1999 17:04:31 -0500 (CDT) Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (Postfix) with ESMTP id 0C4341F37; Mon, 3 May 1999 17:04:25 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine To: Jeroen Ruigrok/Asmodai Cc: Chuck Robey , freebsd-current@FreeBSD.ORG In-reply-to: References: Subject: Re: Protocol analyzer Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 May 1999 17:04:25 -0500 Message-Id: <19990503220426.0C4341F37@spawn.nectar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made a port, which I will commit as soon as I figure out how/if this thing works. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 3 May 1999 at 22:33, Jeroen Ruigrok/Asmodai wrote: > On 03-May-99 Chuck Robey wrote: > > If you've EVER used tcpdump, go take a look at this site, I guarantee > > it's worth your time: > > > > http://www.capmedia.fr/mgall/xip/ > > > > What a GREAT idea! A full graphical tcpdump! > > Also has some probs compiling... > > Looking at it... Might be nice to have in the ports *chuckle* > > --- > Jeroen Ruigrok van der Werven asmodai(at)wxs.nl > The FreeBSD Programmer's Documentation Project > Network/Security Specialist > *BSD: Powered by Knowledge & Know-how > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 15:51:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id D919A14F10 for ; Mon, 3 May 1999 15:51:23 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id PAA06563 for ; Mon, 3 May 1999 15:51:21 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199905032251.PAA06563@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: IBM's Via Voice In-reply-to: Your message of "Mon, 03 May 1999 12:48:52 PDT." <199905031948.MAA04807@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 May 1999 15:51:21 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After playing a little more with ViaVoice, I can't seem to load the sample binaries the come back with : ./hello ./hello: error in loading shared libraries /usr/lib/libsmapi.so: undefined symbol: __bzero objdump --dynamic-syms /compat/linux/usr/lib/libsmapi.so | grep bzero DYNAMIC SYMBOL TABLE: 00000000 DF *UND* 00000035 __bzero 00000000 w DF *UND* 00000035 bzero Does anyone know what the difference is between symbol type "" and "w"? -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 16: 4: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id A6BED154E1 for ; Mon, 3 May 1999 16:03:54 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id TAA13574; Mon, 3 May 1999 19:03:54 -0400 (EDT) Message-ID: <19990503190353.A9814@netmonger.net> Date: Mon, 3 May 1999 19:03:53 -0400 From: Christopher Masto To: freebsd-current@FreeBSD.ORG Subject: Re: IBM's Via Voice Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199905031948.MAA04807@rah.star-gate.com> <199905032251.PAA06563@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199905032251.PAA06563@rah.star-gate.com>; from Amancio Hasty on Mon, May 03, 1999 at 03:51:21PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 03, 1999 at 03:51:21PM -0700, Amancio Hasty wrote: > After playing a little more with ViaVoice, I can't seem to load the sample > binaries the come back with : > > ./hello > ./hello: error in loading shared libraries > /usr/lib/libsmapi.so: undefined symbol: __bzero > > > objdump --dynamic-syms /compat/linux/usr/lib/libsmapi.so | grep bzero > DYNAMIC SYMBOL TABLE: > 00000000 DF *UND* 00000035 __bzero > 00000000 w DF *UND* 00000035 bzero > > Does anyone know what the difference is between symbol > type "" and "w"? No, but I have the same problem. But for anyone else who can't even get this far.. I needed to install the "ldconfig-1.9.5-15.i386.rpm" RPM. Annoyingly, the "Audio Setup Guru" works. So close.. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 17:46:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id CB2D8156FF; Mon, 3 May 1999 17:46:31 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id UAA65218; Mon, 3 May 1999 20:45:54 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199905040045.UAA65218@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: Eric@FreeBSD.ORG, Don Lewis , current@FreeBSD.ORG, stable@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: ppbus causes hangs? References: <199905030658.XAA00467@salsa.gv.tsc.tdk.com> In-reply-to: Your message of "Sun, 02 May 1999 23:58:42 PDT." <199905030658.XAA00467@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 May 1999 20:45:54 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Apr 29, 7:41pm, Mike Smith wrote: > } Subject: Re: ppbus causes hangs? > } > } Try setting the flags on the 'ppc' device to 0x40 and _please_ report > } the results. > > I also ran into this problem with a 4/30/1999 version of 3.1-stable > on a Dell Dimension XPS R400. The 0x40 flag fixed the problem. I had the same problem on a Motorola CPV5000 Compact-PCI system board. I had to disable the parallel port in the BIOS setup to be able to install FreeBSD on it, or boot kernels with the 'ppc' device configured. SInce adding the flag, this all seems to be better now. This is with a 4.0-current based system as of early March. Petium MMX at 233MHz with an 'HX' chipset. More details upon request. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 17:57:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 5E28B14C20 for ; Mon, 3 May 1999 17:57:32 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id UAA08377; Mon, 3 May 1999 20:57:14 -0400 (EDT) Date: Mon, 3 May 1999 20:57:14 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Thyer Cc: freebsd-current@FreeBSD.ORG Subject: Re: Silo overflows and MAME can someone else reproduce this problem ?? In-Reply-To: <372DB8A1.89159C49@camtech.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 May 1999, Matthew Thyer wrote: > My usermode ppp works fine normally as I can quite happily download > 4 things at once without a single silo overflow (as I did last night) > even when there is lots of disk activity or X11 activity. > > Note this problem is unrelated to newbus as it occurs both before and > after those commits. Doesn't X turn off interrupts? A lot? ESPECIALLY in things like the DGA code (which you're probably using with xmame, aren't you?)? Hope I'm thinking on the right track... ;) > > Matthew Thyer wrote: > > > > This problem is easily reproducible. > > > > However to do so, you need a ROM image for an arcade game that the > > Multi Arcade Machine Emulator emulates as it wont do it without any > > roms in the directory "/usr/local/lib/mame/roms". > > > > I am using xmame installed from the ports collection > > (/usr/ports/emulators/xmame) on a very recent -CURRENT machine. > > > > If I run xmame *before* I get online with user mode ppp (or while > > I am on the net), the serial ports get hosed and I have to reboot > > or I continually get silo overflows. > > > > This is not right as it happens AFTER I exit xmame !!! > > > > Please can someone else reproduce this problem as I'd hate to think > > its only on the systems I have owned (Pentium 166 and Celeron 300). > > > -- > /=======================================================================\ > | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | > \=======================================================================/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 18:14:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 67C1515367 for ; Mon, 3 May 1999 18:14:36 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id SAA07832; Mon, 3 May 1999 18:14:32 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199905040114.SAA07832@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Masto Cc: freebsd-current@FreeBSD.ORG Subject: Re: IBM's Via Voice In-reply-to: Your message of "Mon, 03 May 1999 19:03:53 EDT." <19990503190353.A9814@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 May 1999 18:14:31 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apparently , some linux folks are having the same problem and I think that the issue is that ViaVoice was compiled with RedHat 6.0 so after trying out different linux libraries and having no success over here with ViaVoice sample applications except for audiog I am going to wait till IBM sorts the linking problem out. If anyone is interested on the current linux discussion highlighting the linking problems feel free to visit: http://viavoice.sparklist.com/ > On Mon, May 03, 1999 at 03:51:21PM -0700, Amancio Hasty wrote: > > After playing a little more with ViaVoice, I can't seem to load the sample > > binaries the come back with : > > > > ./hello > > ./hello: error in loading shared libraries > > /usr/lib/libsmapi.so: undefined symbol: __bzero > > > > > > objdump --dynamic-syms /compat/linux/usr/lib/libsmapi.so | grep bzero > > DYNAMIC SYMBOL TABLE: > > 00000000 DF *UND* 00000035 __bzero > > 00000000 w DF *UND* 00000035 bzero > > > > Does anyone know what the difference is between symbol > > type "" and "w"? > > No, but I have the same problem. But for anyone else who can't even > get this far.. I needed to install the "ldconfig-1.9.5-15.i386.rpm" > RPM. > > Annoyingly, the "Audio Setup Guru" works. So close.. > -- > Christopher Masto Senior Network Monkey NetMonger Communications > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 18:59: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 91F23153AD; Mon, 3 May 1999 18:58:58 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id VAA07086; Mon, 3 May 1999 21:58:47 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15177; Mon, 3 May 1999 21:58:17 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id VAA70928; Mon, 3 May 1999 21:58:15 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905040158.VAA70928@bb01f39.unx.sas.com> Subject: Re: make release & perl version failure In-Reply-To: <199905031922.VAA07443@greenpeace.grondar.za> from Mark Murray at "May 3, 1999 9:22: 3 pm" To: mark@grondar.za (Mark Murray) Date: Mon, 3 May 1999 21:58:15 -0400 (EDT) Cc: jwd@unx.sas.com, freebsd-current@FreeBSD.ORG, asami@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I modified /snap/release/usr/ports/Mk/bsd.port.mk after it was checked out during 'make release' processing. It worked like a champ and the release completed. Setting up FTP distribution area 0 blocks 0 blocks Release done + echo make release Finished make release Finished ---> Mon May 3 20:05:57 EDT 1999 - Creating /pub/FreeBSD/4.0-19990503-SNAP ---> Mon May 3 20:18:21 EDT 1999 - build of 4.0-19990503-SNAP was a success. ---> make world/release ran 365 min 1 sec To keep the releases building this seems like a reasonable fix until a better solution is found. Thanks! John > "John W. DeBoskey" wrote: > > I don't know if anyone has seen this yet, but from last nights > > 'make release' I get the following failure .... > > > > touch release.2 > > Making docs... > > ===> Extracting for docproj-1.0 > > >> No MD5 checksum file. > > ===> Patching for docproj-1.0 > > ===> Configuring for docproj-1.0 > > ===> Installing for docproj-1.0 > > ===> docproj-1.0 depends on executable: instant - not found > > ===> Verifying install for instant in /usr/ports/textproc/sgmlformat > > Error: you don't have the right version of perl in /usr/bin. > > *** Error code 1 > > > > > > It looks like the perl updates that went in have some side > > effects... > > Here's a workaround (Satoshi - your comments, please?): > > Index: bsd.port.mk > =================================================================== > RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v > retrieving revision 1.311 > diff -u -d -r1.311 bsd.port.mk > --- bsd.port.mk 1999/04/28 06:20:12 1.311 > +++ bsd.port.mk 1999/05/03 19:18:03 > @@ -592,7 +592,12 @@ > > PKG_IGNORE_DEPENDS?= '(XFree86-3\.3\.3\.1|Motif-2\.1\.10)' > > +.if exists(/usr/bin/perl5.00502) > PERL_VERSION= 5.00502 > +.endif > +.if exists(/usr/bin/perl5.00503) > +PERL_VERSION= 5.00503 > +.endif > PERL_VER= 5.005 > PERL_ARCH= ${ARCH}-freebsd > PLIST_SUB+= PERL_VERSION=${PERL_VERSION} \ > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 19:14:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id 3A77C1571D for ; Mon, 3 May 1999 19:14:02 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id LAA07681 for ; Tue, 4 May 1999 11:43:18 +0930 (CST) Received: from exchsa1.dsto.defence.gov.au (unverified [131.185.2.94]) by dsto-ms2.dsto.defence.gov.au (Integralis SMTPRS 2.0.15) with ESMTP id ; Tue, 04 May 1999 11:43:35 +0930 Received: from fuzz.dsto.defence.gov.au ([131.185.75.229]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id KHN5P9HG; Tue, 4 May 1999 11:43:55 +0930 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.3/8.9.3) with ESMTP id LAA01317; Tue, 4 May 1999 11:43:48 +0930 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-Id: <372E57DB.D7128EA7@dsto.defence.gov.au> Date: Tue, 04 May 1999 11:43:47 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: vortexia Cc: Matthew Thyer , freebsd-current@freebsd.org Subject: Re: Silo overflows and MAME can someone else reproduce this problem?? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The sio driver seems to get into some kind of state where once it starts overflowing there is nothing you can do other than reboot. If you can determine exactly what triggers this on your system and give the list something they can reproduce that would be helpfull. vortexia wrote: > > Im getting continous overflows on sio0 after I shutdown X no matter what I > do, even when there is NOTHING else running, the moment I shutdown X and I > move my mouse I get tons of overflows. > > I have no pppd running at all and no moused, any ideas? > > Cheers > > Andrew > > On Tue, 4 May 1999, Matthew Thyer wrote: > > > My usermode ppp works fine normally as I can quite happily download > > 4 things at once without a single silo overflow (as I did last night) > > even when there is lots of disk activity or X11 activity. > > > > Note this problem is unrelated to newbus as it occurs both before and > > after those commits. > > > > Matthew Thyer wrote: > > > > > > This problem is easily reproducible. > > > > > > However to do so, you need a ROM image for an arcade game that the > > > Multi Arcade Machine Emulator emulates as it wont do it without any > > > roms in the directory "/usr/local/lib/mame/roms". > > > > > > I am using xmame installed from the ports collection > > > (/usr/ports/emulators/xmame) on a very recent -CURRENT machine. > > > > > > If I run xmame *before* I get online with user mode ppp (or while > > > I am on the net), the serial ports get hosed and I have to reboot > > > or I continually get silo overflows. > > > > > > This is not right as it happens AFTER I exit xmame !!! > > > > > > Please can someone else reproduce this problem as I'd hate to think > > > its only on the systems I have owned (Pentium 166 and Celeron 300). > > > -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 20: 6: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 6A11D14DC4 for ; Mon, 3 May 1999 20:01:11 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id CAA23772; Tue, 4 May 1999 02:46:53 +0200 From: Luigi Rizzo Message-Id: <199905040046.CAA23772@labinfo.iet.unipi.it> Subject: Re: bridge+dummynet + "sysctl -a" panics in -current To: bright@rush.net (Alfred Perlstein) Date: Tue, 4 May 1999 02:46:53 +0200 (MET DST) Cc: current@freebsd.org In-Reply-To: from "Alfred Perlstein" at May 3, 99 01:20:11 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 390 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ok, egg in my face, that's not it i guess. What about patching rc.network > to allow early setup of bridge though? i have no objections, the thing is i dont run current or even stable so i can't completely check changes if i do the patch myself, and i'd rather not break things so close to a release. furthermore i think very few people run bridging on full systems... cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 23: 9:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.41]) by hub.freebsd.org (Postfix) with ESMTP id A9BA614E70 for ; Mon, 3 May 1999 23:09:28 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id BAA00470; Tue, 4 May 1999 01:09:24 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 4 May 1999 01:09:24 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@freebsd.org Subject: pcm sound X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14126.36332.612699.745659@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I poked at the pcm sound driver a bit, and it appears that sys/i386/isa/isa_dma.c:isa_dmastatus is returning 65280 (== snd_dmabuf bufsize == 0xff00) when there is no dma pending, which kinda blows the mind of sys/i386/isa/snd/dmabuf.c:dsp_wr_dmaupdate (which is easily confused). This breaks pcm audio. isa_dma.c seems to be new with newbus? I just thought the author(s) might be interested the know that this routine seems not to be returning what it claims in the comments. I don't suppose anyone has a document describing the ISA DMA hardware interface? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 23:30:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CE32A1508E for ; Mon, 3 May 1999 23:30:33 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA08521; Tue, 4 May 1999 00:29:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA55316; Tue, 4 May 1999 00:31:09 -0600 (MDT) Message-Id: <199905040631.AAA55316@harmony.village.org> To: Dag-Erling Smorgrav Subject: Re: ep0 *UTP* Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "30 Apr 1999 19:23:51 +0200." References: Date: Tue, 04 May 1999 00:31:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Dag-Erling Smorgrav writes: : Anybody using a 3c509 and expecting it to work reliably should be : taken out and shot in the back of the head. But what about a 3C589D? The ep driver supports them as well :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 23:37:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 89A4214BC9 for ; Mon, 3 May 1999 23:37:13 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA08543; Tue, 4 May 1999 00:36:32 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA55353; Tue, 4 May 1999 00:37:49 -0600 (MDT) Message-Id: <199905040637.AAA55353@harmony.village.org> To: John Polstra Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( Cc: ben@rosengart.com, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 30 Apr 1999 11:50:51 PDT." References: Date: Tue, 04 May 1999 00:37:48 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message John Polstra writes: : Sheesh. Make it a bloody long then so you'll get 64 bits on the : Alpha. And then go fix all the printf format mismatches. : : Or, pull you head out of that dark fantasyland and realize that (a) a : 32-bit counter is not a problem in any realistic sense, and (b) if it : were, we'd have thousands of other equally serious problems throughout : the system. : : I'm done with this absurd thread. I can understand that. It has taken more time arguing about it than the s/short/int/ ; make world :-) It is completely impossible to have 2^32 routes in IPv4. Period. Your machine must be on a network, and therefore it must have a broadcast address for that network, and therefore there must be at least 4 addresses that are reachable with one route. Since the domain of IPv4 is 2^32, you can have at most 2^32 - 3 routes. An int is fine, no overflow check needed here. IPv6 may change this, but as John keeps pointing out, that is apples and oranges... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 23:42: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 6672E14D3B for ; Mon, 3 May 1999 23:42:00 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA42180; Tue, 4 May 1999 08:41:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id IAA11002; Tue, 4 May 1999 08:41:58 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905040641.IAA11002@greenpeace.grondar.za> To: Warner Losh Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: ep0 *UTP* In-Reply-To: Your message of " Tue, 04 May 1999 00:31:09 CST." <199905040631.AAA55316@harmony.village.org> References: <199905040631.AAA55316@harmony.village.org> Date: Tue, 04 May 1999 08:41:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message Dag-Erling Smorgrav writes: > : Anybody using a 3c509 and expecting it to work reliably should be > : taken out and shot in the back of the head. > > But what about a 3C589D? The ep driver supports them as well :-) Or a 3C589E (AKA a 3CCE589ET)? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 23:54:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6B8E914EFE for ; Mon, 3 May 1999 23:54:08 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA08582; Tue, 4 May 1999 00:53:25 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA55476; Tue, 4 May 1999 00:54:43 -0600 (MDT) Message-Id: <199905040654.AAA55476@harmony.village.org> To: Doug Rabson Subject: Re: Odd message during -current boot Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 01 May 1999 13:06:23 BST." References: Date: Tue, 04 May 1999 00:54:43 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : Its fairly harmless. We don't really support the old haveseen_isadev() api : and its a reminder to convert any old drivers which use it. I might deal : with it this weekend since I have some time. I'm going to finish importing : gdb-4.18 first though. There are 3 that I know of: adv, bt and aha. bt has already been converted, I'm in the middle of converting aha right now, which leaves adv. It is basically trying to make sure that it doesn't probe an address ranage that has previously been claimed by a card. For 99% of the cases, it really isn't needed, but that 1% can cause hangs.. The other one which is needed reconfig_isadev, which is used by the zp and ze drivers. It is only called after a resume and its lack is what causes these devices to not work after a resume. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 3 23:56: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C942C151BC for ; Mon, 3 May 1999 23:56:05 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA08589; Tue, 4 May 1999 00:55:23 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA55492; Tue, 4 May 1999 00:56:41 -0600 (MDT) Message-Id: <199905040656.AAA55492@harmony.village.org> To: "Steven P. Donegan" Subject: Re: Odd message during -current boot Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 01 May 1999 07:17:56 PDT." References: Date: Tue, 04 May 1999 00:56:41 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Steven P. Donegan" writes: : And, it happens even if the bt device driver is not configured into the : kernel... Do you have the aha or adv driver in the kernel, or configured into the kernel? The last time I did a grep on sys for haveseen_isadev, it only showed up in adv. My tree has an uncommitted converted aha driver in it, and bt was converted not too long ago. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 0: 4: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A844614E8A for ; Tue, 4 May 1999 00:03:59 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA08612; Tue, 4 May 1999 01:03:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA55538; Tue, 4 May 1999 01:04:35 -0600 (MDT) Message-Id: <199905040704.BAA55538@harmony.village.org> To: Ollivier Robert Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 May 1999 01:52:16 +0200." <19990502015216.A915@keltia.freenix.fr> References: <19990502015216.A915@keltia.freenix.fr> Date: Tue, 04 May 1999 01:04:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990502015216.A915@keltia.freenix.fr> Ollivier Robert writes: : WHat are the improvements compared to Perforce ? After working with Perforce for 9 month at Pluto, I'd have to say it is head and shoulders above CVS. It is a different style of source management, where you have to explicitly open things, but its ability to deal with branches has made it possible to have an extensive set of changes from FreeBSD for pluto boxes and still stay sane. And deal with multiple branches, and deal well with merging. CVSup is still faster at updates that perforce, however... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 0: 8: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A272B15361 for ; Tue, 4 May 1999 00:08:02 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA08629; Tue, 4 May 1999 01:07:20 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA55573; Tue, 4 May 1999 01:08:39 -0600 (MDT) Message-Id: <199905040708.BAA55573@harmony.village.org> To: mjacob@feral.com Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 01 May 1999 19:32:37 PDT." References: Date: Tue, 04 May 1999 01:08:39 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : Oh, very well, I'll have to say Perforce isn't that bad- it's just that it : doesn't have a snappy set of tcl/tk GUI tools that allow you look at whole : branch and revision histories.. I've seen many Tk tools that do this. There is also a web interface as well. : It doesn't have a 3-way filemerge tool (I : still fire up teamware (what NSElite became) to do heavy merging and use : the automerge feature)... That is true. : Perforce *does* have the disparate release : stream feature, but I have found it somewhat difficult to use. Perhaps if : I'd actually had the depot locally I'd feel more at home with it.... Once you get use to it, it is much easier to use than CVS. I have my own branch for kernel changes that I'm in the middle of, and merging them is as simple as p4 integrate newsrc/sys/... src/sys/... p4 resolve And I can also merge the changes to my src/sys/... tree back into newsrc/sys/... at any time with p4 integrate src/sys/... newsrc/sys/... p4 resolve I'd go insane without it. Or more likely people at work would be more upset with my tendancy to checkin early and often to make sure all the places I work on stuff are in sync. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 0:23:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2C2F814F9A for ; Tue, 4 May 1999 00:23:13 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA08671; Tue, 4 May 1999 01:22:31 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA55644; Tue, 4 May 1999 01:23:50 -0600 (MDT) Message-Id: <199905040723.BAA55644@harmony.village.org> To: Dispatcher Subject: Re: -stable vs -current (was Re: solid NFS patch #6... ) Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 May 1999 15:41:51 EDT." <199905021941.PAA22423@blackhelicopters.org> References: <199905021941.PAA22423@blackhelicopters.org> Date: Tue, 04 May 1999 01:23:50 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905021941.PAA22423@blackhelicopters.org> Dispatcher writes: : For mission-critical systems, I'm still installing 2.2.8-stable. And the security officer still back ports relevant patches to 2.2.8-stale. The 2.2.8 -> 3.x transition lost support for several devices (aic being the mostly loudly complained about). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 0:25:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4CEDB154D8 for ; Tue, 4 May 1999 00:25:09 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA08689; Tue, 4 May 1999 01:24:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA55672; Tue, 4 May 1999 01:25:46 -0600 (MDT) Message-Id: <199905040725.BAA55672@harmony.village.org> To: Chuck Robey Subject: Re: Protocol analyzer Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 May 1999 14:34:12 EDT." References: Date: Tue, 04 May 1999 01:25:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : If you've EVER used tcpdump, go take a look at this site, I guarantee : it's worth your time: : : http://www.capmedia.fr/mgall/xip/ : : What a GREAT idea! A full graphical tcpdump! Looks like a fully animated version of a Poster that FTP software gave out years ago... :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 0:41:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7BC2A14E00 for ; Tue, 4 May 1999 00:41:39 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA43886; Tue, 4 May 1999 08:41:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 4 May 1999 08:41:35 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Odd message during -current boot In-Reply-To: <199905040654.AAA55476@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 May 1999, Warner Losh wrote: > In message Doug Rabson writes: > : Its fairly harmless. We don't really support the old haveseen_isadev() api > : and its a reminder to convert any old drivers which use it. I might deal > : with it this weekend since I have some time. I'm going to finish importing > : gdb-4.18 first though. > > There are 3 that I know of: > adv, bt and aha. > bt has already been converted, I'm in the middle of converting aha > right now, which leaves adv. It is basically trying to make sure that > it doesn't probe an address ranage that has previously been claimed by > a card. For 99% of the cases, it really isn't needed, but that 1% can > cause hangs.. In that case, the driver will detect it when it allocates the resource. It will after conversion anyway :-). > > The other one which is needed reconfig_isadev, which is used by the zp > and ze drivers. It is only called after a resume and its lack is what > causes these devices to not work after a resume. Nasty. Is it worth trying to fix this or will you be changing the zp driver anyway with the pccard work? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 0:47: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 943DB15274 for ; Tue, 4 May 1999 00:47:04 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA08807; Tue, 4 May 1999 01:46:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA55988; Tue, 4 May 1999 01:47:41 -0600 (MDT) Message-Id: <199905040747.BAA55988@harmony.village.org> To: Doug Rabson Subject: Re: Odd message during -current boot Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 May 1999 08:41:35 BST." References: Date: Tue, 04 May 1999 01:47:41 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : In that case, the driver will detect it when it allocates the resource. It : will after conversion anyway :-). :-) : > The other one which is needed reconfig_isadev, which is used by the zp : > and ze drivers. It is only called after a resume and its lack is what : > causes these devices to not work after a resume. : : Nasty. Is it worth trying to fix this or will you be changing the zp : driver anyway with the pccard work? No. Come to think of it the zp and ze drivers should die when ep and whatever ed (or whatever ze replaces) are converted to the new new scheme. That may be a while yet, since I'm still working on the new old scheme. The new new scheme lacks pccardd for anything but dynamic command running after a device has been added to the system, and maybe some configuration stuff. The pccards will probe on insertion, and attach w/o the need for pccardd. This should help the many configuration problems people have had with pccard. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 0:59:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id F051C15B65 for ; Tue, 4 May 1999 00:59:14 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-22.iptelecom.net.ua [212.42.68.149]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id KAA10608 for ; Tue, 4 May 1999 10:59:36 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA13388 for ; Tue, 4 May 1999 10:59:07 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <372EA8C8.158803E5@altavista.net> Date: Tue, 04 May 1999 10:59:04 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: PCCARD driver still sucks Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that as of today -current pccard driver still isn't usable. Kernel paniced after pccardd trying ifconfig ed0. Following is my dmesg, interesting that pccardd complain about "slot 0,1,2,3", while I only have two. May  4 10:46:33 notebook /kernel: Timecounter "i8254"  frequency 1193123 Hz May  4 10:46:33 notebook /kernel: CPU: Pentium/P55C (132.63-MHz 586-class CPU) May  4 10:46:33 notebook /kernel: Origin = "GenuineIntel"  Id = 0x543  Stepping=3 May  4 10:46:33 notebook /kernel: Features=0x8001bf May  4 10:46:33 notebook /kernel: real memory  = 33685504 (32896K bytes) May  4 10:46:33 notebook /kernel: avail memory = 30363648 (29652K bytes) May  4 10:46:33 notebook /kernel: Preloaded elf kernel "kernel" at 0xc0287000. May  4 10:46:33 notebook /kernel: Probing for PnP devices: May  4 10:46:33 notebook /kernel: npx0: on motherboard May  4 10:46:33 notebook /kernel: npx0: INT 16 interface May  4 10:46:33 notebook /kernel: apm0: on motherboard May  4 10:46:33 notebook /kernel: apm: found APM BIOS version 1.2 May  4 10:46:33 notebook /kernel: pcib0: on motherboard May  4 10:46:33 notebook /kernel: pci0: on pcib0 May  4 10:46:33 notebook /kernel: chip0: at device 0.0 on pci0 May  4 10:46:33 notebook /kernel: isa0: on motherboard May  4 10:46:33 notebook /kernel: fdc0: interrupting at irq 6 May  4 10:46:33 notebook /kernel: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 May  4 10:46:33 notebook /kernel: fd0: <1440-KB 3.5" drive> at May  4 10:46:33 notebook /kernel: fdc0 drive 0 May  4 10:46:33 notebook /kernel: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 May  4 10:46:33 notebook /kernel: wdc0: unit 0 (wd0): May  4 10:46:33 notebook /kernel: wd0: 1376MB (2818368 sectors), 2796 cyls, 16 heads, 63 S/T, 512 B/S May  4 10:46:33 notebook /kernel: wdc0: interrupting at irq 14 May  4 10:46:34 notebook /kernel: atkbdc0: at port 0x60 on isa0 May  4 10:46:34 notebook /kernel: atkbd0: on atkbdc0 May  4 10:46:34 notebook /kernel: atkbd0: interrupting at irq 1 May  4 10:46:34 notebook /kernel: psm0: on atkbdc0 May  4 10:46:34 notebook /kernel: psm0: model Generic PS/2 mouse, device ID 0 May  4 10:46:34 notebook /kernel: psm0: interrupting at irq 12 May  4 10:46:34 notebook /kernel: vga0: on isa0 May  4 10:46:34 notebook /kernel: sc0: on isa0 May  4 10:46:34 notebook /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> May  4 10:46:34 notebook /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 May  4 10:46:34 notebook /kernel: sio0: type 16550A May  4 10:46:34 notebook /kernel: sio0: interrupting at irq 4 May  4 10:46:34 notebook /kernel: sio1: configured irq 11 not in bitmap of probed irqs 0 May  4 10:46:34 notebook /kernel: sio2: configured irq 9 not in bitmap of probed irqs 0 May  4 10:46:34 notebook /kernel: ppc0 at port 0x378-0x37f irq 7 on isa0 May  4 10:46:34 notebook /kernel: ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode May  4 10:46:34 notebook /kernel: ppc0: FIFO with 16/16/16 bytes threshold May  4 10:46:34 notebook /kernel: plip0: on ppbus 0 May  4 10:46:34 notebook /kernel: ppc0: interrupting at irq 7 May  4 10:46:34 notebook /kernel: PC-Card Intel 82365 (5 mem & 2 I/O windows) May  4 10:46:34 notebook /kernel: pcic: controller irq 3 May  4 10:46:34 notebook /kernel: Initializing PC- May  4 10:46:34 notebook /kernel: card drivers: ed May  4 10:46:34 notebook /kernel: Intel Pentium detected, installing workaround for F00F bug May  4 10:46:35 notebook /kernel: changing root device to wd0s1a May  4 10:46:35 notebook /kernel: Card inserted, slot 0 May  4 10:46:35 notebook /kernel: Card inserted, slot 1 May  4 10:46:35 notebook /kernel: PC-Card Intel 82365 (5 mem & 2 I/O windows) May  4 10:46:35 notebook /kernel: pcic: controller irq 5 May  4 10:46:35 notebook /kernel: Card inserted, slot 2 May  4 10:46:35 notebook /kernel: Card inserted, slot 3 May  4 10:46:42 notebook /kernel: ed0: address 00:80:c8:88:86:b1, type NE2000 (16 bit) PANICED HERE!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 1:17:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id B541F14C33 for ; Tue, 4 May 1999 01:17:01 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-37.iptelecom.net.ua [212.42.68.228]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id LAA12014 for ; Tue, 4 May 1999 11:16:53 +0300 (EEST) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id LAA13437 for ; Tue, 4 May 1999 11:14:47 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <372EAC74.2428D62E@altavista.net> Date: Tue, 04 May 1999 11:14:44 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: New ATA driver still can't find my hardware Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Soren, As of today -current ata driver isn't probed at all (I don't see ad0 messages when booting kernel and of course it can't mount root), while wd0 driver works well. Following is dmesg from my earlier bootable kernel with ata driver. FreeBSD 4.0-CURRENT #0: Sat Apr 17 02:47:42 EEST 1999 ad0: ATA-? disk at ata0 as master ad0: 1376MB (2818368 sectors), 2796 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, PIO mode My kernel config: #controller      wdc0    at isa? port IO_WD1 irq 14 #disk            wd0     at wdc0 drive 0 controller      ata0 controller      ata1    at isa? port IO_WD1 irq 14 device          atadisk0   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 1:44:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9E96A15156 for ; Tue, 4 May 1999 01:44:34 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA21839; Tue, 4 May 1999 10:44:31 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905040844.KAA21839@freebsd.dk> Subject: Re: New ATA driver still can't find my hardware In-Reply-To: <372EAC74.2428D62E@altavista.net> from Maxim Sobolev at "May 4, 1999 11:14:44 am" To: sobomax@altavista.net Date: Tue, 4 May 1999 10:44:31 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: >Dear Soren, > >As of today -current ata driver isn't probed at all (I don't see ad0 >messages when booting kernel and of course it can't mount root), while >wd0 driver works well. >Following is dmesg from my earlier bootable kernel with ata driver. > >FreeBSD 4.0-CURRENT #0: Sat Apr 17 02:47:42 EEST 1999 >ad0: ATA-? disk at ata0 as master >ad0: 1376MB (2818368 sectors), 2796 cyls, 16 heads, 63 S/T, 512 B/S >ad0: piomode=4, dmamode=2, udmamode=-1 >ad0: 16 secs/int, 0 depth queue, PIO mode > >My kernel config: > >#controller      wdc0    at isa? port IO_WD1 irq 14 >#disk            wd0     at wdc0 drive 0 >controller      ata0 >controller      ata1    at isa? port IO_WD1 irq 14 >device          atadisk0 Is this an ISA only system ?? The introduction of the new-bus code broke pure ISA system, I have some patches lying around, but havn't gotten to commit them yet... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 3:55:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailin.hkstar.com (cygnus.hkstar.com [202.82.3.13]) by hub.freebsd.org (Postfix) with ESMTP id 1B5FA14C40 for ; Tue, 4 May 1999 03:55:07 -0700 (PDT) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by mailin.hkstar.com (8.8.8/8.8.5) with ESMTP id SAA22788 for ; Tue, 4 May 1999 18:55:06 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id SAA10689 for freebsd-current@freebsd.org; Tue, 4 May 1999 18:55:04 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199905041055.SAA10689@b1.hkstar.com> Subject: any clue to compile cc To: freebsd-current@freebsd.org Date: Tue, 4 May 1999 18:55:02 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have problem in compile the whole system. The error is as followings;- Any clue ? Thanks. Clarence ======= Error ======= ===> cpp cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/sr c/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE _CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"\ " -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cp p/../cc_tools -DPREFIX=\"/usr\" -c /usr/src/gnu/usr.bin/cc/cpp/../../../../con trib/egcs/gcc/cccp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: `GPLUSPLUS_ INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: initializer element for `include_defaults_array[0].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: `OLD_GPLUSP LUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: initializer element for `include_defaults_array[1].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: `GCC_INCLUD E_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: initializer element for `include_defaults_array[2].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c: In function `ma log: unmodified: line 1 in': /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: `GCC_INCLU DE_DIR' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: (Each unde clared identifier is reported only once /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: for each f unction it appears in.) *** Error code 1 Stop. ======= Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 4:44:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from plexus.nu (cm2081634025.ponderosa.ispchannel.com [208.163.40.25]) by hub.freebsd.org (Postfix) with ESMTP id CAA9E1507B for ; Tue, 4 May 1999 04:44:09 -0700 (PDT) (envelope-from tas@stephens.org) Received: from plexus.nu (localhost [127.0.0.1]) by plexus.nu (8.9.2/8.9.2) with ESMTP id MAA28916; Tue, 4 May 1999 12:44:06 +0100 (BST) (envelope-from tas@plexus.nu) Message-Id: <199905041144.MAA28916@plexus.nu> To: sobomax@altavista.net Cc: current@FreeBSD.ORG, Thomas Stephens From: Thomas Stephens Subject: Re: PCCARD driver still sucks In-reply-to: Your message of "Tue, 04 May 1999 10:59:04 +0300." <372EA8C8.158803E5@altavista.net> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-ID: <28912.925818245.1@plexus.nu> Content-Transfer-Encoding: quoted-printable Date: Tue, 04 May 1999 04:44:05 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: >It seems that as of today -current pccard driver still isn't usable. >Kernel paniced after pccardd trying ifconfig ed0. Following is my dmesg, >interesting that pccardd complain about "slot 0,1,2,3", while I only >have two. This slot problem is usually caused by loading the pcic KLD into a kernel which already contains pcic support. Is your /etc/rc.pccard loading the pcic module (the default behaviour)? Is pcic support already built into your kernel? If the answer to both of these is `yes', you've got to change one or the other. As to the panic, have you tried the patch S=F8ren posted to current a short time ago? Thomas Stephens tas@stephens.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 5: 2:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 3AD6215213; Tue, 4 May 1999 05:02:32 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id WAA25884; Tue, 4 May 1999 22:02:04 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma025850; Tue, 4 May 99 22:01:38 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA12653; Tue, 4 May 1999 22:01:33 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id WAA16559; Tue, 4 May 1999 22:01:29 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA07094; Tue, 4 May 1999 22:01:28 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199905041201.WAA07094@nymph.detir.qld.gov.au> To: Chuck Robey Cc: Jean-Marc Zucconi , freebsd-current@freebsd.org, syssgm@detir.qld.gov.au Subject: Re: ctm-mail cvs-cur.5292.gz 18/82 References: In-Reply-To: from Chuck Robey at "Sun, 02 May 1999 19:40:28 -0400" Date: Tue, 04 May 1999 22:01:28 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 2nd May 1999, Chuck Robey wrote: >On Mon, 3 May 1999, Jean-Marc Zucconi wrote: > >> This one did not arrive in my mailbox. Can someone send it to me? I >> would like to avoid downloading 6Mbytes again. > >I'm going to mail it to you separately, but it might not look like it >came from me. I also did not receive part 18. Are the individual parts kept anywhere for anonymous ftp access? Failures are rare, but they hit the big updates disproportionately and have a bigger effect on bigger updates, so it's a double lose. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 5:21:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 4164615509; Tue, 4 May 1999 05:21:08 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id IAA13940; Tue, 4 May 1999 08:18:47 -0400 (EDT) Date: Tue, 4 May 1999 08:18:46 -0400 (EDT) From: Chuck Robey To: Stephen McKay Cc: Jean-Marc Zucconi , freebsd-current@FreeBSD.ORG Subject: Re: ctm-mail cvs-cur.5292.gz 18/82 In-Reply-To: <199905041201.WAA07094@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 May 1999, Stephen McKay wrote: > On Sunday, 2nd May 1999, Chuck Robey wrote: > > >On Mon, 3 May 1999, Jean-Marc Zucconi wrote: > > > >> This one did not arrive in my mailbox. Can someone send it to me? I > >> would like to avoid downloading 6Mbytes again. > > > >I'm going to mail it to you separately, but it might not look like it > >came from me. > > I also did not receive part 18. Are the individual parts kept anywhere > for anonymous ftp access? They are kept in a spool directory, which erases them shortly after they become unimportant. The first transmission request, for #18, came while they were there back to #8, so I sent him what he asked for. The second request came at a point that only those after #30 were there, so I couldn't fill it. Can't do it for you either. > > Failures are rare, but they hit the big updates disproportionately and > have a bigger effect on bigger updates, so it's a double lose. I'll have to see about getting another strategy for spool emptying. Maybe we keep around the last two deltas? > > Stephen. > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 5:29:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id F192415830 for ; Tue, 4 May 1999 05:29:00 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id WAA26962; Tue, 4 May 1999 22:27:57 +1000 (EST) Message-ID: <19990504222757.G27888@rf900.physics.usyd.edu.au> Date: Tue, 4 May 1999 22:27:57 +1000 From: David Dawes To: Brian Feldman , Matthew Thyer Cc: freebsd-current@FreeBSD.ORG Subject: Re: Silo overflows and MAME can someone else reproduce this problem ?? References: <372DB8A1.89159C49@camtech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brian Feldman on Mon, May 03, 1999 at 08:57:14PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 03, 1999 at 08:57:14PM -0400, Brian Feldman wrote: >On Tue, 4 May 1999, Matthew Thyer wrote: > >> My usermode ppp works fine normally as I can quite happily download >> 4 things at once without a single silo overflow (as I did last night) >> even when there is lots of disk activity or X11 activity. >> >> Note this problem is unrelated to newbus as it occurs both before and >> after those commits. > >Doesn't X turn off interrupts? A lot? ESPECIALLY in things like the DGA The answers in order are: rarely (never for most modern cards), no, and no. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 6: 1:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from qix.jmz.org (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (Postfix) with ESMTP id 4D29614DD8 for ; Tue, 4 May 1999 06:01:23 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.2) id PAA48854; Tue, 4 May 1999 15:01:59 +0200 (MET DST) (envelope-from jmz@FreeBSD.ORG) Date: Tue, 4 May 1999 15:01:59 +0200 (MET DST) Message-Id: <199905041301.PAA48854@qix.jmz.org> X-Authentication-Warning: qix.jmz.org: jmz set sender to jmz@FreeBSD.ORG using -f From: Jean-Marc Zucconi To: syssgm@detir.qld.gov.au Cc: chuckr@picnic.mat.net, freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au In-reply-to: <199905041201.WAA07094@nymph.detir.qld.gov.au> (message from Stephen McKay on Tue, 04 May 1999 22:01:28 +1000) Subject: Re: ctm-mail cvs-cur.5292.gz 18/82 X-Mailer: Emacs References: <199905041201.WAA07094@nymph.detir.qld.gov.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Stephen McKay writes: > I also did not receive part 18. Are the individual parts kept anywhere > for anonymous ftp access? I will put it on http://www.freebsd.org/~jmz/part18 in a few minutes. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 6:44: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 6CD72154C4 for ; Tue, 4 May 1999 06:43:50 -0700 (PDT) (envelope-from fanf@demon.net) Received: by noc.demon.net; id OAA00580; Tue, 4 May 1999 14:43:49 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma000538; Tue, 4 May 99 14:43:45 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10efU7-0004Iv-00; Tue, 4 May 1999 14:43:43 +0100 To: current@freebsd.org From: Tony Finch Subject: Re: NFS Patch #8 for current available - new TCP fixes In-Reply-To: Message-Id: Date: Tue, 4 May 1999 14:43:43 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > (fanfair!) :-) > NFS attempts to realign packet buffers and trods all over the underlying > mbufs. For TCP connections, several RPC's may be present in an mbuf > chain. The realignment of one of them may destroy the others. This does > not occur with UDP because each UDP packet contains only a single rpc. > > Packet buffers may be unaligned for a number of reasons. The main reason > is due to the 14 byte MAC header on the ethernet frame. This causes the > remainder of the packet - the ip payload - to NOT be 4-byte aligned. We're planning to try replacing some Solaris web servers with FreeBSD machines in the near future. The documents are on a read-only NFS filestore connected to the web servers with CDDI. (Updates will stay on a Sun box.) Are we going to have nfs_realign problems if we use TCP in this situation or should we stick with UDP? Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Arthur: "Oh, that sounds better, have you worked out the controls?" Ford: "No, we just stopped playing with them." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 7:23:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 92EE215747 for ; Tue, 4 May 1999 07:23:25 -0700 (PDT) (envelope-from geoffb@geoffb.noc.demon.net) Received: by noc.demon.net; id PAA06715; Tue, 4 May 1999 15:23:24 +0100 (BST) Received: from geoffb.noc.demon.net(195.11.55.49) by inside.noc.demon.net via smap (3.2) id xma006696; Tue, 4 May 99 15:23:24 +0100 Received: (from geoffb@localhost) by geoffb.noc.demon.net (8.9.3/8.9.1) id QAA07655; Tue, 4 May 1999 16:25:23 +0100 (BST) (envelope-from geoffb) Date: Tue, 4 May 1999 16:25:23 +0100 (BST) Message-Id: <199905041525.QAA07655@geoffb.noc.demon.net> Mime-Version: 1.0 X-Newsreader: knews 1.0b.0 References: In-Reply-To: From: geoffb@demon.net (Geoff Buckingham) Subject: Re: Q3 test X-Original-Newsgroups: mpc.lists.freebsd.current,muc.lists.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Kenneth Wayne Culver writes: > As we probably all know, Q3 test is out for Linux. I tested it on FreeBSD, > with great results. I just downloaded the correct glide libraries from the > site suggested by Carmac (Q3 programmer) and installed those, and then I > added the appropriate resoulutions to my configuration. > Does your sound work? I had problems with the $front driver havn't tried the other two yet. People wanting to run servers can do without glide libaries using the command line switch '+set dedicated 1' most of the other quake2 configuration options seem to work too. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 7:24:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from satty.npi.msu.su (satty.npi.msu.su [158.250.20.4]) by hub.freebsd.org (Postfix) with ESMTP id B227A14D81 for ; Tue, 4 May 1999 07:23:10 -0700 (PDT) (envelope-from dima@zippy.machaon.ru) Received: from zippy.machaon.ru (ws-134.machaon.ru [195.230.75.134] (may be forged)) by satty.npi.msu.su (8.9.1a/8.9.1) with ESMTP id RAA25529; Tue, 4 May 1999 17:49:31 +0400 (MSD) Date: Tue, 4 May 1999 17:49:31 +0400 (MSD) From: Dmitry Khrustalev To: Warner Losh Cc: John Polstra , ben@rosengart.com, freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-Reply-To: <199905040637.AAA55353@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is completely impossible to have 2^32 routes in IPv4. Period. Of course not. It is impossible to have 2^32 *host* routes in IPv4. -Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 8:23: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 4640114DC4 for ; Tue, 4 May 1999 08:22:30 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id RAA73677; Tue, 4 May 1999 17:22:24 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.2/8.9.2) id RAA26168; Tue, 4 May 1999 17:22:23 +0200 (CEST) Date: Tue, 4 May 1999 17:22:22 +0200 From: Rudolf Cejka To: Poul-Henning Kamp Cc: Rudolf Cejka , "freebsd-current@freebsd.org" Subject: Re: Jail - any success? Message-ID: <19990504172222.A25275@kazi.dcse.fee.vutbr.cz> References: <199905031339.PAA20535@kazi.dcse.fee.vutbr.cz> <7998.925739554@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <7998.925739554@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, May 03, 1999 at 03:52:34PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote (1999/05/03): > You need to put ip aliases on your loopback interface, forinstance: > > ifconfig lo0 10.0.0.1 netmask 255.255.255.255 alias > ... > ifconfig lo0 10.0.0.5 netmask 255.255.255.255 alias > > Then you give each jail one of these ipnumbers and start whatever > daemons you want in the jail (inetd, sshd, apache...) > > Of course your routing needs to work such that these ip numbers > end up on your machine, you can also do this by adding multiple > IP# to the ethernet of the machine. Thanks. Now I know where was the problem - if I create ip alias ifconfig lo0 A.B.C.D netmask 255.255.255.255 alias I must write jail command as jail /path domain.name D.C.B.A /command so on my PC ip-address isn't converted to a network format. Here are my suggestions: *) Aplly this patch to jail.c: (Or bug is in system call? What format should be there?) --- jail.c.orig Tue May 4 14:00:36 1999 +++ jail.c Tue May 4 14:00:47 1999 @@ -21,7 +21,7 @@ i = inet_aton(argv[3], &in); if (!i) errx(1, "Couldn't make sense if ip number\n"); - j.ip_number = in.s_addr; + j.ip_number = htonl(in.s_addr); i = jail(&j); if (i) err(1, "Imprisonment failed"); *) There should be "$Id" in all Makefile, jail.8, and jail.c I think. *) In jail(8) there is synopsis "jail path hostname ip-number". It should be "jail path hostname ip command ..." as is usage of jail command. (I you want I can fill PRs :-) Is it possible to call ping in prison session? # ping some.host ping: socket: Operation not permitted --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--= Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 8:35: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from logatome.micronet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id D7F0F14F6D for ; Tue, 4 May 1999 08:35:02 -0700 (PDT) (envelope-from Sebastien.Gioria@FranceNet.fr) Received: from gioria.dialup.FranceNet.fr (eku28.francenet.fr [193.149.97.60]) by logatome.micronet.fr (8.8.8/8.8.8) with ESMTP id RAA11942 for ; Tue, 4 May 1999 17:33:51 +0200 (CEST) Received: by gioria.dialup.FranceNet.fr (Postfix, from userid 42) id 9ECC61FFF6; Tue, 4 May 1999 17:30:40 +0200 (CEST) Message-ID: <19990504173040.C19137@FranceNet.fr> Date: Tue, 4 May 1999 17:30:40 +0200 From: Sebastien GIORIA To: freebsd-current@freebsd.org Subject: Jail ? Reply-To: Sebastien GIORIA Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Operating-System: Definitely FreeBSD Function: Unix and Security Administrator Organization: FranceNet Postal-Address: 28 Rue Desaix , 75015 PARIS, FRANCE Phone: +33 1 43 92 12 34 Fax: +33 1 43 92 14 45 X-Operating-System: FreeBSD-2.2.8-RELEASE (PAO enabled) on Dell Inspiron 3200 X-URL: http://www.FranceNet.fr -- http://www.freebsd-fr.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any chance to have jail include in the 3.x-STABLE before the summer ? Thanks S. -- --> Backbone Scoliosis <-- Sebastien Gioria - FranceNet gioria@francenet.fr Unix && Security Administrator security@francenet.fr Tout FreeBSD en Francais =========> http://www.freebsd-fr.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 8:53:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7BE8214E9D for ; Tue, 4 May 1999 08:53:17 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id IAA10036; Tue, 4 May 1999 08:53:12 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA24559; Tue, 4 May 1999 08:53:11 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 04 May 1999 08:53:11 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Dmitry Khrustalev Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( Cc: freebsd-current@FreeBSD.ORG, Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Khrustalev wrote: >> It is completely impossible to have 2^32 routes in IPv4. Period. > > Of course not. It is impossible to have 2^32 *host* routes in IPv4. Independent of IPv4, IPv6, or IPvAnything, I make the following claim. Let: P = number of bits in a pointer I = number of bits in the integer type used for a reference counter U = size of addressable unit in bits (8 on most machines). If: U <= P <= I then there is no way in theory or in practice to overflow the reference count. The proof is left as an exercise for the reader. Hint: where will you store that many pointers, and how will you address them? And please don't raise the red herring of code bugs in maintaining the reference counts, because that has never been what this thread is about. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 8:54: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 82C5914F7B for ; Tue, 4 May 1999 08:54:00 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA27958; Tue, 4 May 1999 09:53:50 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA09700; Tue, 4 May 1999 09:53:49 -0600 Date: Tue, 4 May 1999 09:53:49 -0600 Message-Id: <199905041553.JAA09700@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: ep0 *UTP* In-Reply-To: <199905040631.AAA55316@harmony.village.org> References: <199905040631.AAA55316@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message Dag-Erling Smorgrav writes: > : Anybody using a 3c509 and expecting it to work reliably should be > : taken out and shot in the back of the head. > > But what about a 3C589D? The ep driver supports them as well :-) The 589D also has problems under heavy load, but I doubt many people are running heavily loaded applications on their laptops. (I did it once, and it tended to timeout and require a lot of ifconfig ep0 up/down about every 3-4 minutes). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 9:39:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9AA4515005 for ; Tue, 4 May 1999 09:39:21 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA90900; Tue, 4 May 1999 09:38:36 -0700 (PDT) (envelope-from obrien) Message-ID: <19990504093836.A90851@nuxi.com> Date: Tue, 4 May 1999 09:38:36 -0700 From: "David O'Brien" To: Chan Yiu Wah , freebsd-current@FreeBSD.ORG Subject: Re: any clue to compile cc Reply-To: obrien@NUXI.com References: <199905041055.SAA10689@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905041055.SAA10689@b1.hkstar.com>; from Chan Yiu Wah on Tue, May 04, 1999 at 06:55:02PM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have problem in compile the whole system. The error is as followings;- > Any clue ? Thanks. Looks like you might want to do: cd /usr/src make cleandir make cleandir to clean up old cruft in your /usr/src/..... directories. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 10:37:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 43BC514E00; Tue, 4 May 1999 10:37:41 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id TAA43451; Tue, 4 May 1999 19:37:39 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id TAA13606; Tue, 4 May 1999 19:37:38 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905041737.TAA13606@greenpeace.grondar.za> To: Jean-Marc Zucconi Cc: syssgm@detir.qld.gov.au, chuckr@picnic.mat.net, freebsd-current@FreeBSD.ORG Subject: Re: ctm-mail cvs-cur.5292.gz 18/82 In-Reply-To: Your message of " Tue, 04 May 1999 15:01:59 +0200." <199905041301.PAA48854@qix.jmz.org> References: <199905041201.WAA07094@nymph.detir.qld.gov.au> <199905041301.PAA48854@qix.jmz.org> Date: Tue, 04 May 1999 19:37:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jean-Marc Zucconi wrote: > >>>>> Stephen McKay writes: > > > I also did not receive part 18. Are the individual parts kept anywhere > > for anonymous ftp access? > > I will put it on http://www.freebsd.org/~jmz/part18 in a few minutes. The ctms are in ftp://ftp.freebsd.org/pub/FreeBSD/CTM/* M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 11:20:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 520F714D63 for ; Tue, 4 May 1999 11:20:23 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA14749; Tue, 4 May 1999 11:19:40 -0700 (PDT) (envelope-from dillon) Date: Tue, 4 May 1999 11:19:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199905041819.LAA14749@apollo.backplane.com> To: Dmitry Khrustalev Cc: Warner Losh , John Polstra , ben@rosengart.com, freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the worst case you might see is on the order of 50,000 or so route entries. If we give FreeBSD the capability to handle multipath routes, it would depend on the size of the mesh but I can't imagine there would be more then a few hundred thousand route entries in the route table. It take a phenominally stupid network setup to create more then that. The number would not be effected much (if at all) IPV4 verses IPV6. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 11:23:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 45348157B3 for ; Tue, 4 May 1999 11:22:46 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA07193; Tue, 4 May 1999 20:22:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA13447; Tue, 4 May 1999 20:22:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Rudolf Cejka Cc: "freebsd-current@freebsd.org" Subject: Re: Jail - any success? In-reply-to: Your message of "Tue, 04 May 1999 17:22:22 +0200." <19990504172222.A25275@kazi.dcse.fee.vutbr.cz> Date: Tue, 04 May 1999 20:22:38 +0200 Message-ID: <13445.925842158@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990504172222.A25275@kazi.dcse.fee.vutbr.cz>, Rudolf Cejka writes: >Is it possible to call ping in prison session? > > # ping some.host > ping: socket: Operation not permitted I have not bothered with it yet, I would have to peek into the ICMP packets to make sure they were OK. Much time, little payback. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 11:27:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 03FE2154E6 for ; Tue, 4 May 1999 11:27:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA14894; Tue, 4 May 1999 11:27:26 -0700 (PDT) (envelope-from dillon) Date: Tue, 4 May 1999 11:27:26 -0700 (PDT) From: Matthew Dillon Message-Id: <199905041827.LAA14894@apollo.backplane.com> To: Tony Finch Cc: current@FreeBSD.ORG Subject: Re: NFS Patch #8 for current available - new TCP fixes References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> remainder of the packet - the ip payload - to NOT be 4-byte aligned. : :We're planning to try replacing some Solaris web servers with FreeBSD :machines in the near future. The documents are on a read-only NFS :filestore connected to the web servers with CDDI. (Updates will stay :on a Sun box.) Are we going to have nfs_realign problems if we use TCP :in this situation or should we stick with UDP? : :Tony. TCP should be very close to UDP now on current. I hope to get a patch for the TCP fixes into -stable for the 3.2 release. There are still bugs in NFS, but they are considerably less serious then before. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 11:43:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id E166E14EB5 for ; Tue, 4 May 1999 11:43:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA00377; Tue, 4 May 1999 11:41:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905041841.LAA00377@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sobomax@altavista.net Cc: current@freebsd.org Subject: Re: PCCARD driver still sucks In-reply-to: Your message of "Tue, 04 May 1999 10:59:04 +0300." <372EA8C8.158803E5@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 04 May 1999 11:41:30 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems that as of today -current pccard driver still isn't usable. > Kernel paniced after pccardd trying ifconfig ed0. Following is my dmesg= , > interesting that pccardd complain about "slot 0,1,2,3", while I only > have two. You're still loading the pcic module. Don't do that. -- = \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 11:56:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id C9FBA152CB for ; Tue, 4 May 1999 11:56:20 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 7777 invoked from network); 4 May 1999 18:56:19 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 4 May 1999 18:56:19 -0000 Date: Tue, 4 May 1999 11:54:36 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Sebastien GIORIA Cc: freebsd-current@FreeBSD.ORG Subject: Re: Jail ? In-Reply-To: <19990504173040.C19137@FranceNet.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree, this would be way cool, and a valuable feature. On Tue, 4 May 1999, Sebastien GIORIA wrote: > Any chance to have jail include in the 3.x-STABLE before > the summer ? > > Thanks > > S. > > -- > --> Backbone Scoliosis <-- > Sebastien Gioria - FranceNet gioria@francenet.fr > Unix && Security Administrator security@francenet.fr > Tout FreeBSD en Francais =========> http://www.freebsd-fr.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 12:14:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 958C714E09 for ; Tue, 4 May 1999 12:14:10 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA53747; Tue, 4 May 1999 20:14:00 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 4 May 1999 20:14:00 +0100 (BST) From: Doug Rabson To: Tony Finch Cc: current@freebsd.org Subject: Re: NFS Patch #8 for current available - new TCP fixes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 May 1999, Tony Finch wrote: > Matthew Dillon wrote: > > > > (fanfair!) > > :-) > > > NFS attempts to realign packet buffers and trods all over the underlying > > mbufs. For TCP connections, several RPC's may be present in an mbuf > > chain. The realignment of one of them may destroy the others. This does > > not occur with UDP because each UDP packet contains only a single rpc. > > > > Packet buffers may be unaligned for a number of reasons. The main reason > > is due to the 14 byte MAC header on the ethernet frame. This causes the > > remainder of the packet - the ip payload - to NOT be 4-byte aligned. > > We're planning to try replacing some Solaris web servers with FreeBSD > machines in the near future. The documents are on a read-only NFS > filestore connected to the web servers with CDDI. (Updates will stay > on a Sun box.) Are we going to have nfs_realign problems if we use TCP > in this situation or should we stick with UDP? I think UDP will probably work better. There won't be any problem with frames being re-ordered and the protocol overhead should be less. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 12:29: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id C797815490 for ; Tue, 4 May 1999 12:28:50 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id VAA18393 for ; Tue, 4 May 1999 21:28:46 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma018391; Tue, 4 May 99 21:28:46 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id VAA03742 for ; Tue, 4 May 1999 21:28:45 +0200 (MET DST) Received: (qmail 12698 invoked by uid 666); 4 May 1999 19:29:07 -0000 Date: Tue, 4 May 1999 21:29:07 +0200 From: Jos Backus To: current@freebsd.org Subject: sys/modules/procfs/Makefile buglet Message-ID: <19990504212907.A12665@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Makefile.orig Tue May 4 21:26:56 1999 +++ Makefile Tue May 4 21:27:25 1999 @@ -3,7 +3,8 @@ .PATH: ${.CURDIR}/../../miscfs/procfs KMOD= procfs SRCS= opt_vmpage.h procfs_ctl.c procfs_map.c procfs_note.c procfs_status.c \ - procfs_subr.c procfs_type.c procfs_vfsops.c procfs_vnops.c + procfs_subr.c procfs_type.c procfs_vfsops.c procfs_vnops.c \ + procfs_rlimit.c NOMAN= VFS_KLD= CFLAGS+= -DPROCFS (Probably.) -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 12:55:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 3B8C614EFC for ; Tue, 4 May 1999 12:55:47 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id VAA18845 for freebsd-current@FreeBSD.ORG; Tue, 4 May 1999 21:55:44 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id AE9C4884E; Tue, 4 May 1999 20:49:14 +0200 (CEST) (envelope-from roberto) Date: Tue, 4 May 1999 20:49:14 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: ctm-mail cvs-cur.5292.gz 18/82 Message-ID: <19990504204914.A23480@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199905022335.BAA93119@qix.jmz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <199905022335.BAA93119@qix.jmz.org>; from Jean-Marc Zucconi on Mon, May 03, 1999 at 01:35:48AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5244 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jean-Marc Zucconi: > This one did not arrive in my mailbox. Can someone send it to me? I > would like to avoid downloading 6Mbytes again. It seems that it got here right: -rw------- 1 nobody wheel 73872 May 3 19:10 cvs-cur.5292.gz+017-082 -rw------- 1 nobody wheel 73872 May 3 19:10 cvs-cur.5292.gz+018-082 -rw------- 1 nobody wheel 73872 May 3 19:10 cvs-cur.5292.gz+019-082 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 13: 5:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CAEF914EFC for ; Tue, 4 May 1999 13:05:11 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA11017; Tue, 4 May 1999 14:04:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA04248; Tue, 4 May 1999 14:04:23 -0600 (MDT) Message-Id: <199905042004.OAA04248@harmony.village.org> To: sobomax@altavista.net Subject: Re: PCCARD driver still sucks Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 May 1999 10:59:04 +0300." <372EA8C8.158803E5@altavista.net> References: <372EA8C8.158803E5@altavista.net> Date: Tue, 04 May 1999 14:04:23 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <372EA8C8.158803E5@altavista.net> Maxim Sobolev writes: : It seems that as of today -current pccard driver still isn't usable. : Kernel paniced after pccardd trying ifconfig ed0. Following is my dmesg, : interesting that pccardd complain about "slot 0,1,2,3", while I only : have two. Bummer. Don't load the pcic module. The PCCARD code really sucks, but it basically kinda sorta works. I'm working to reduce the suckage factor, but it will be some time before the suckage is completely eliminated. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 13:33: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from tardis.perspectives.net (unknown [63.66.225.69]) by hub.freebsd.org (Postfix) with ESMTP id D66DC14E84 for ; Tue, 4 May 1999 13:32:56 -0700 (PDT) (envelope-from jerry.alexandratos@perspectives.net) Received: from localhost ([127.0.0.1] helo=tardis.perspectives.net) by tardis.perspectives.net with esmtp (Exim 2.12 #1) id 10elr1-00098P-00; Tue, 4 May 1999 16:31:47 -0400 To: Warner Losh Cc: sobomax@altavista.net, current@FreeBSD.ORG Subject: Re: PCCARD driver still sucks In-Reply-To: Message from Warner Losh of "Tue, 04 May 1999 14:04:23 MDT." <199905042004.OAA04248@harmony.village.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <35109.925849907.1@tardis.perspectives.net> Date: Tue, 04 May 1999 16:31:47 -0400 From: Jerry Alexandratos Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh says: : In message <372EA8C8.158803E5@altavista.net> Maxim Sobolev writes: : : It seems that as of today -current pccard driver still isn't usable. : : Kernel paniced after pccardd trying ifconfig ed0. Following is my dmesg, : : interesting that pccardd complain about "slot 0,1,2,3", while I only : : have two. : : Bummer. Don't load the pcic module. : : The PCCARD code really sucks, but it basically kinda sorta works. I'm : working to reduce the suckage factor, but it will be some time before : the suckage is completely eliminated. Quick question. Will the work you're doing also solve the problems with the detection and driver assignment on modem/serial cards or is that another problem all-together? --Jerry name: Jerry Alexandratos || Open-Source software isn't a phone: 302.521.1018 || matter of life or death... email: jalexand@perspectives.net || ...It's much more important || than that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 13:39: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 84E8314E84 for ; Tue, 4 May 1999 13:39:00 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA11126; Tue, 4 May 1999 14:38:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA04453; Tue, 4 May 1999 14:38:12 -0600 (MDT) Message-Id: <199905042038.OAA04453@harmony.village.org> To: Jerry Alexandratos Subject: Re: PCCARD driver still sucks Cc: sobomax@altavista.net, current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 May 1999 16:31:47 EDT." References: Date: Tue, 04 May 1999 14:38:12 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jerry Alexandratos writes: : Quick question. Will the work you're doing also solve the problems with : the detection and driver assignment on modem/serial cards or is that : another problem all-together? That is a related problem. The drivers that have been converted to newbus need to be fixed for pccard support. Fortunately, that will be very easy to do, at least it looks easy to do. I'll be doing that for those devices I can test: sio, ata and fdc. I might not commit right away, but I do want both old and new drivers working when I commit the changes. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 15:33:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.30]) by hub.freebsd.org (Postfix) with ESMTP id 618EE152B5 for ; Tue, 4 May 1999 15:32:24 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id RAA00451; Tue, 4 May 1999 17:32:20 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 4 May 1999 17:32:17 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@freebsd.org Subject: VESA/SMP problems again X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14127.29964.319475.838650@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An alert: VESA/SMP seems to be problematic again. For example, this sequence reliably brings me down to the bios: startx ctl-alt-bksp vidcontrol 132x42 startx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 15:56:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from outloud.bellatlantic.net (adsl-151-202-16-56.bellatlantic.net [151.202.16.56]) by hub.freebsd.org (Postfix) with ESMTP id A80D81524E for ; Tue, 4 May 1999 15:56:35 -0700 (PDT) (envelope-from yacine@bellatlantic.net) Received: from bellatlantic.net (sigma@adsl-151-202-16-56.bellatlantic.net [151.202.16.56]) by outloud.bellatlantic.net (8.9.1/8.9.1) with ESMTP id TAA00497 for ; Tue, 4 May 1999 19:05:49 -0500 (EST) (envelope-from yacine@bellatlantic.net) Message-ID: <372F8B5D.EFA79FCA@bellatlantic.net> Date: Tue, 04 May 1999 19:05:49 -0500 From: yacine Reply-To: yacine@bellatlantic.net X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Q3 test References: <199905041525.QAA07655@geoffb.noc.demon.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Geoff Buckingham wrote: > > In article , > Kenneth Wayne Culver writes: > > As we probably all know, Q3 test is out for Linux. I tested it on FreeBSD, > > with great results. I just downloaded the correct glide libraries from the > > site suggested by Carmac (Q3 programmer) and installed those, and then I > > added the appropriate resoulutions to my configuration. > > > Does your sound work? I had problems with the $front driver havn't tried > the other two yet. > > People wanting to run servers can do without glide libaries using the > command line switch '+set dedicated 1' most of the other quake2 configuration > options seem to work too. > > -- > GeoffB > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I have problems with sound myself. I get an error message in the Q3A console saying "your soundcard can't do this." I have a Crystal CS4237B soundcard. Here is information from my dmesg: Probing for PnP devices: CSN 1 Vendor ID: CSCd937 [0x37d9630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] mss_attach 1 at 0x530 irq 9 dma 1:3 flags 0x13 pcm1 (CS423x/Yamaha sn 0xffffffff) at 0x530-0x537 irq 9 drq 1 flags 0x13 on isa Probing for devices on the ISA bus: (...) pcm0 not probed due to drq conflict with pcm1 at 1 The soundcard part of my kernel: #Soundcard info #Crystal 4237 B controller pnp0 # this is required for PnP support device pcm0 at isa? port ? tty irq 9 drq 1 vector pcmintr Other than that, everything works fine. I get sound normally from other programs, from cd playing software to mp3 decoders. The game runs smoothly, but it's a tad annoying without sound :( I apologize if the answer is obvious to some of you (as I am sure it is), but I am rather new to FreeBSD (as if that wasn't obvious ;) (I am using FreeBSD 3.0-RELEASE...) Thank you, Yacine Benzine (yacine@bellatlantic.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 16:26:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (Postfix) with ESMTP id D80F8152D3 for ; Tue, 4 May 1999 16:26:27 -0700 (PDT) (envelope-from plm@smtp3.xs4all.nl) Received: from localhost. (dc2-isdn21.dial.xs4all.nl [194.109.148.21]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id BAA07935 for ; Wed, 5 May 1999 01:26:20 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id BAA00668; Wed, 5 May 1999 01:26:14 +0200 (MET DST) (envelope-from plm) To: freebsd-current@freebsd.org Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) References: <87n1znnyu2.fsf@totally-fudged-out-message-id> From: Peter Mutsaers Date: 04 May 1999 23:29:49 +0200 In-Reply-To: Robert Watson's message of "Sat, 1 May 1999 14:37:29 -0400 (EDT)" Message-ID: <87n1zka5gy.fsf@muon.xs4all.nl> X-Mailer: Gnus v5.6.45/Emacs 20.3 Lines: 31 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "RW" == Robert Watson writes: RW> So will bitkeeper provide a nice interface for migrating code RW> from an existing and well-established CVS repository to RW> whatever they use? I've looked at bitkeeper and wonder what exactly are it's advantages over CVS. It's model looks very much geared towards the fragmented way Linux is developed, offering no advantages for more centralized models such as FreeBSD or most commercial internal environments. In the Linux environment the 'patch' is everything, and the kernel looks like a big pile of 'patches' to me. Thus in bitkeeper generating these patch sets (containing history & log messages) to submit from one repository to another is important, because people exchange patches all the time. The other thing is some graphic tools (written in tcl/tk) but there are also some of such GUI layers for CVS, though they've never become very popular because the command line (combined with UNIX pipes & std. commands, filters) cannot be beaten for this type of work IMO. I'd suggest to at least wait a (long) while to see how it is developing. At the moment I see absolutely no advantage for more centralized development models. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+------------------ Running FreeBSD-current UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 16:32:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id 8C6E915263 for ; Tue, 4 May 1999 16:32:43 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id QAA05708; Tue, 4 May 1999 16:29:09 -0700 (PDT) Message-ID: <372F828F.15673432@seattleu.edu> Date: Tue, 04 May 1999 16:28:15 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: yacine@bellatlantic.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Q3 test References: <199905041525.QAA07655@geoffb.noc.demon.net> <372F8B5D.EFA79FCA@bellatlantic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yacine wrote: > I have problems with sound myself. I get an error message in the Q3A > console saying "your soundcard can't do this." I have a Crystal CS4237B > soundcard. snip... > controller pnp0 # this is required for PnP support > device pcm0 at isa? port ? tty irq 9 drq 1 vector pcmintr > > Other than that, everything works fine. I get sound normally from other > programs, from cd playing software to mp3 decoders. The game runs > smoothly, but it's a tad annoying without sound :( > I apologize if the answer is obvious to some of you (as I am sure it > is), but I am rather new to FreeBSD (as if that wasn't obvious ;) > > (I am using FreeBSD 3.0-RELEASE...) I think it is because the pcm driver don't support mmap()ing. Are we going to get mmap()ing? (If this is the case.) -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 18: 3:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 56C9014FB3 for ; Tue, 4 May 1999 18:03:34 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from transit.hanse.de (transit-a.Hanse.DE [193.174.9.161]) by kogge.Hanse.DE (8.9.1/8.9.1) with ESMTP id DAA52481; Wed, 5 May 1999 03:03:12 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Received: from monster.transit-a.hanse.de (monster [193.174.9.163]) by transit.hanse.de (8.8.8/8.8.8) with ESMTP id DAA08111; Wed, 5 May 1999 03:03:06 +0200 (CEST) (envelope-from stefan.bethke@hanse.de) Date: Wed, 05 May 1999 03:03:04 +0200 From: Stefan Bethke To: Edwin Culp Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: netatalk (atalkd,papd,afpd) Message-ID: <26309987.3134862184@monster.transit-a.hanse.de> In-Reply-To: <372B22A4.495941C@MexComUSA.net> Originator-Info: login-id=stb; server=transit.transit-a.hanse.de X-Mailer: Mulberry (MacOS) [1.4.0, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > I just realized that I have lost netatalk (atalkd/papd/afpd) seems to > have silently died within the last week or so, for no clear reason. Has > anyone else, who is running current and netatalk, seen this? (Misery > loves company:-) I'm going to start looking for a problem. I've just compiled and installed netatalk-asun, and everything seems fine on my -current from about two day ago... I'll try with netatalk sometime soon. Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 18: 6: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from psycho.h4x0rz.za.org (psycho.h4x0rz.za.org [206.49.228.8]) by hub.freebsd.org (Postfix) with ESMTP id BD90514DD3 for ; Tue, 4 May 1999 18:05:42 -0700 (PDT) (envelope-from andrew@psycho.h4x0rz.za.org) Received: from localhost (andrew@localhost) by psycho.h4x0rz.za.org (8.9.3/8.9.2) with ESMTP id DAA01785 for ; Wed, 5 May 1999 03:07:07 +0200 (SAST) (envelope-from andrew@psycho.h4x0rz.za.org) Date: Wed, 5 May 1999 03:07:06 +0200 (SAST) From: vortexia To: freebsd-current@freebsd.org Subject: Make world faliure Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried to make world on a cvsup from about 2 hours, (1am GMT+2 Wed May 5th), and Im getting a make world faliure... it does this... Writing Makefile for DynaLoader ===> Your Makefile has been rebuilt. <=== ===> Please rerun the make command <=== false false: not found *** Error code 1 Stop. Any ideas? Thanx Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 18:22: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id A069A14DD3 for ; Tue, 4 May 1999 18:21:59 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id VAA16735; Tue, 4 May 1999 21:19:29 -0400 (EDT) Date: Tue, 4 May 1999 21:19:29 -0400 (EDT) From: Chuck Robey To: Sebastien GIORIA Cc: freebsd-current@FreeBSD.ORG Subject: Re: Jail ? In-Reply-To: <19990504173040.C19137@FranceNet.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 May 1999, Sebastien GIORIA wrote: > Any chance to have jail include in the 3.x-STABLE before > the summer ? What I'd like to see is a writeup on how to actually make use of these new features. > > Thanks > > S. > > -- > --> Backbone Scoliosis <-- > Sebastien Gioria - FranceNet gioria@francenet.fr > Unix && Security Administrator security@francenet.fr > Tout FreeBSD en Francais =========> http://www.freebsd-fr.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 19: 0: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 990B715076 for ; Tue, 4 May 1999 18:59:59 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA09321; Wed, 5 May 1999 11:28:28 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <372F8B5D.EFA79FCA@bellatlantic.net> Date: Wed, 05 May 1999 11:28:28 +0930 (CST) From: "Daniel O'Connor" To: yacine Subject: Re: Q3 test Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-May-99 yacine wrote: > I have problems with sound myself. I get an error message in the Q3A > console saying "your soundcard can't do this." I have a Crystal CS4237B > soundcard. Here is information from my dmesg: This probably happens because pcm doesn't support mmap'ing the DMA buffers of your sound card.. You could hack the pcm driver, apparently its quite easy to do 8-) --- 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-current" in the body of the message From owner-freebsd-current Tue May 4 19:33:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 83B4315088 for ; Tue, 4 May 1999 19:33:05 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id WAA06458; Tue, 4 May 1999 22:31:54 -0400 (EDT) From: Mikhail Teterin Message-Id: <199905050231.WAA06458@kot.ne.mediaone.net> Subject: Re: ep0 *UTP* In-Reply-To: <199905041553.JAA09700@mt.sri.com> from Nate Williams at "May 4, 1999 09:53:49 am" To: nate@mt.sri.com (Nate Williams) Date: Tue, 4 May 1999 22:31:53 -0400 (EDT) Cc: current@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Tue, 4 May 1999 19:51:27 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA10064; Wed, 5 May 1999 12:20:29 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <372F828F.15673432@seattleu.edu> Date: Wed, 05 May 1999 12:20:29 +0930 (CST) From: "Daniel O'Connor" To: Eric Hodel Subject: Re: Q3 test Cc: freebsd-current@FreeBSD.ORG, yacine@bellatlantic.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-May-99 Eric Hodel wrote: > I think it is because the pcm driver don't support mmap()ing. Are we > going to get mmap()ing? (If this is the case.) Actually.. I wouldn't mind a library you can LD_PRELOAD which replaces open/read/write/mmap/ioctl for audio devices and then mangles it to an appropriate back end.. I was going toward this end but had difficulty getting even a base library to work :( This sort of approach means you don't have to worry about wether you have Esound, NAS, Voxware, OSS or pcm.. Of course it might be a bit slower than normal, but heck, CPU is cheap! ;) --- 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-current" in the body of the message From owner-freebsd-current Tue May 4 20:24:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id C574E1501A for ; Tue, 4 May 1999 20:24:06 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40393>; Wed, 5 May 1999 13:09:37 +1000 Date: Wed, 5 May 1999 13:23:58 +1000 From: Peter Jeremy Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( To: dillon@apollo.backplane.com Cc: freebsd-current@FreeBSD.ORG Message-Id: <99May5.130937est.40393@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > I think the worst case you might see is on the order of 50,000 or so > route entries. ... > It take a phenominally stupid network setup to create more > then that. With Path MTU Discovery (which is on by default), you effectively create a distict route for every host. Currently, routes appear to take ~20 minutes to expire. It seems perfectly reasonable for a big FTP or WWW server to see 50,000 different hosts in this period. This is getting fairly close to the 64K possible entries. > The number would not be effected much (if at all) IPV4 verses IPV6. IPV6 gives you a bigger worst case, but shouldn't affect the typical behaviour. Why is there such resistance to moving from a short to an int? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 21: 6:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 7C77C1528C for ; Tue, 4 May 1999 21:06:09 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id VAA50386; Tue, 4 May 1999 21:05:57 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <372FC3B0.A0587884@MexComUSA.net> Date: Tue, 04 May 1999 21:06:08 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Stefan Bethke Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: netatalk (atalkd,papd,afpd) References: <26309987.3134862184@monster.transit-a.hanse.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Bethke wrote: > Edwin Culp wrote: > > > I just realized that I have lost netatalk (atalkd/papd/afpd) seems to > > have silently died within the last week or so, for no clear reason. Has > > anyone else, who is running current and netatalk, seen this? (Misery > > loves company:-) I'm going to start looking for a problem. > > I've just compiled and installed netatalk-asun, and everything seems fine > on my -current from about two day ago... > > I'll try with netatalk sometime soon. > > Stefan > Good news, maybe it's fixed. I'll give it another try. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 21:15:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id A9F55157D3 for ; Tue, 4 May 1999 21:15:32 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (sj-dsl-9-161-066.dspeed.net [209.249.161.66]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id VAA50425; Tue, 4 May 1999 21:14:41 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <372FC5BB.8E323F75@MexComUSA.net> Date: Tue, 04 May 1999 21:14:51 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Jerry Alexandratos , sobomax@altavista.net, current@FreeBSD.ORG Subject: Re: PCCARD driver still sucks References: <199905042038.OAA04453@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message Jerry Alexandratos writes: > : Quick question. Will the work you're doing also solve the problems with > : the detection and driver assignment on modem/serial cards or is that > : another problem all-together? > > That is a related problem. The drivers that have been converted to > newbus need to be fixed for pccard support. Fortunately, that will be > very easy to do, at least it looks easy to do. I'll be doing that for > those devices I can test: sio, ata and fdc. I might not commit right > away, but I do want both old and new drivers working when I commit the > changes. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I tried my ethernet DE660 again with today's world and after the panic recompiled the kernel with Soren's patch that keeps the suckage factor lower here. It works :-) Thanks, ed P.S. If you need a tester, let me know. The factor can't get much lower that a panic. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 22:24:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id EC05B1553A for ; Tue, 4 May 1999 22:24:14 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id WAA67013 for freebsd-current@FreeBSD.ORG; Tue, 4 May 1999 22:24:14 -0700 (PDT) From: Archie Cobbs Message-Id: <199905050524.WAA67013@bubba.whistle.com> Subject: Re: traceroute patch In-Reply-To: <199905031736.KAA10201@bubba.whistle.com> from Archie Cobbs at "May 3, 99 10:36:28 am" To: freebsd-current@FreeBSD.ORG Date: Tue, 4 May 1999 22:24:14 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: > I have this patch for traceroute that adds the ability to send > packets with an arbitrary IP protocol number, instead of just TCP > and UDP. This is mainly useful to see if some router between points > A and B is blocking packets based on IP protocol number. > > I sent it to "traceroute@ee.lbl.gov" but got no response. > > Is this something people might be interested in? Is it worth committing? > We've found it useful on occasion. > > ftp://ftp.whistle.com/pub/archie/misc/traceroute.patch Hmm.. since nobody replied, I'll try a more provocative question.. :-) Does anyone object to me committing this patch? Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 22:43:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 90C5515813; Tue, 4 May 1999 22:43:17 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA15793; Wed, 5 May 1999 15:13:16 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA49491; Wed, 5 May 1999 15:13:12 +0930 (CST) Date: Wed, 5 May 1999 15:13:11 +0930 From: Greg Lehey To: FreeBSD Stable Users , FreeBSD current users Subject: HEADS UP: Big changes in Vinum Message-ID: <19990505151311.G40359@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just MFCd a lot of changes to the -STABLE revision of Vinum. These have been running in -CURRENT for some weeks, but in view of the impending release of 3.2, I'd be grateful if anybody planning to do something with Vinum were to do it now and let me know immediately if you have any problems. Thanks Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 4 23:48:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 2BD9F14FD0 for ; Tue, 4 May 1999 23:48:15 -0700 (PDT) (envelope-from erik@habatech.no) Received: from intranett (post.lyssand.com [194.54.98.163]) by post.bgnett.no (8.8.8/8.8.8) with SMTP id IAA03189 for ; Wed, 5 May 1999 08:48:09 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: <009b01be96c3$90063e70$589a4cc0@intranett.lyssand.com> From: "Erik H. Bakke" To: Subject: PCM problem solved (?) Date: Wed, 5 May 1999 08:49:53 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In what may have seemed a desperate move to try to find out where the sound drivers decided to stop, I took a look at my config file. I tried to change the attachment of the pcm device from isa? to nexus?, trying to move it closer to the source of the interrupts. (This is with = an SB PCI 128) When I had rebuilt the kernel and rebooted, the error messages seemed a bit different. It was actually suggested that I should try to use pcm0 instead of pcm1. A quick remake of the devices, and suddenly, the sound was back. Will this approach solve the problems for you other people with the same problem? Regards. -- Erik H. Bakke Habatech AS erik@habatech.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 0:25:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 6CD6214E4A for ; Wed, 5 May 1999 00:25:02 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup3-45.iptelecom.net.ua [212.42.69.236]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA28891; Wed, 5 May 1999 10:25:18 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA19394; Wed, 5 May 1999 10:21:36 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <372FF180.72524D82@altavista.net> Date: Wed, 05 May 1999 10:21:36 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Edwin Culp , current@FreeBSD.ORG Cc: Warner Losh Subject: PCCARD today works but sysinstall and PicoBSD broken. (was PCCARD driver still sucks) References: <199905042038.OAA04453@harmony.village.org> <372FC5BB.8E323F75@MexComUSA.net> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank to all for replies. It seems that today current finaly have fixed (pccard works without patches). Hovewer, sysinstall (and PicoBSD) broken with following symptoms: cc -O2 -march=pentium -mpentium -pipe -Wall -I/usr/src/release/sysinstall/../../ gnu/lib/libdialog -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/.. /../sys -DUC_PRIVATE -DKERN_NO_SYMBOLS   -c kget.c In file included from kget.c:31: /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:66: parse error befo re `ointhand2_t' /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:66: warning: no semi colon at end of struct or union /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:66: warning: no semi colon at end of struct or union /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:67: warning: type de faults to `int' in declaration of `id_iu' /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:67: warning: data de finition has no type or storage class /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:80: parse error befo re `}' kget.c: In function `kget': kget.c:69: sizeof applied to an incomplete type kget.c:71: dereferencing pointer to incomplete type kget.c:72: dereferencing pointer to incomplete type kget.c:74: dereferencing pointer to incomplete type kget.c:75: dereferencing pointer to incomplete type kget.c:77: dereferencing pointer to incomplete type etc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 0:26:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 66AF414E4A for ; Wed, 5 May 1999 00:26:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA22417; Wed, 5 May 1999 00:25:23 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 May 1999 00:25:23 -0700 (PDT) From: Matthew Dillon Message-Id: <199905050725.AAA22417@apollo.backplane.com> To: Peter Jeremy Cc: freebsd-current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: <99May5.130937est.40393@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon wrote: :> I think the worst case you might see is on the order of 50,000 or so :> route entries. ... :> It take a phenominally stupid network setup to create more :> then that. :With Path MTU Discovery (which is on by default), you effectively :create a distict route for every host. Currently, routes appear to :take ~20 minutes to expire. It seems perfectly reasonable for a big :FTP or WWW server to see 50,000 different hosts in this period. This :is getting fairly close to the 64K possible entries. The expiration is dynamically tuned based on the creation rate. If you bump up the number of tcp connections being made, the route timeout will drop until it hits the net.inet.ip.rtminexpire sysctl value, which defaults to 10 seconds. You should never see more then a few thousand such routes. In extreme cases, you might have to reduce net.inet.ip.rtexpire from 10 seconds to something smaller, such as 2 seconds. For example, a web server getting 100 hits/sec will, with default sysctl values, maintain approximately 1000 temporary routes in the route table. In fact, I had to commit a fix to the dynamic control of the rtexpire variable last year to prevent sudden ramp-ups from blowing away the kernel memory pool because it wasn't reducing net.inet.ip.rtexpire quickly enough. Otherwise IP spoofing attacks that randomized the source address could take down the machine by overloading the route table and running the kernel out of memory. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 3:21:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 952C31582C for ; Wed, 5 May 1999 03:21:53 -0700 (PDT) (envelope-from fanf@demon.net) Received: by noc.demon.net; id LAA05690; Wed, 5 May 1999 11:21:51 +0100 (BST) Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma005637; Wed, 5 May 99 11:21:48 +0100 Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10eyoE-00055Q-00; Wed, 5 May 1999 11:21:46 +0100 To: current@freebsd.org From: Tony Finch Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( In-Reply-To: <199905041819.LAA14749@apollo.backplane.com> References: Message-Id: Date: Wed, 5 May 1999 11:21:46 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > I think the worst case you might see is on the order of 50,000 or so > route entries. If you read the PR you'll see that we have over 70,000 routes on some interfaces in our network, and we aren't doing multipath routeing. (We have c. 20,000 modems and our customers have static IP addresses.) > It take a phenominally stupid network setup to create more then that. :-) Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net Arthur: "Oh, that sounds better, have you worked out the controls?" Ford: "No, we just stopped playing with them." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 4:40: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 24EAA152B0 for ; Wed, 5 May 1999 04:39:50 -0700 (PDT) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id VAA04718 for ; Wed, 5 May 1999 21:09:48 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.p0.FreeBSD:990505210947:369=_" Date: Wed, 05 May 1999 21:09:47 +0930 (CST) From: "Daniel J. O'Connor" To: current@freebsd.org Subject: SMP & APM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990505210947:369=_ Content-Type: text/plain; charset=us-ascii Hi, Has anyone tried having APM and SMP in the same kernel? It panic()'s mine :) Basically the machine panics a few seconds after I do 'apmconf -e'. apm seems to return normal values though. I've attached a sample output from APM, dmesg and my kernel config. I get a trap 12: page fault in kernel mode mp_lock = 01000009; cpuid = 1; lapic.id = 01000000 fault virtual address = 0x75f0 fault code = supervisor read, page not present interrupt pointer = 0x8:0xc0208a4c stack pointer = 0x10:0xff80dd78 frame pointer = 0x10:0xff80dd7c 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 = Idle interrupt mask = <- SMP: XXX Also, nm kernel.debug | sort shows that 0xc0208a4c is in Xbpt --- 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 --_=XFMail.1.3.p0.FreeBSD:990505210947:369=_ Content-Disposition: attachment; filename="dmesg_out.txt" Content-Transfer-Encoding: 7bit Content-Description: dmesg_out.txt Content-Type: text/plain; charset=us-ascii; name=dmesg_out.txt; SizeOnDisk=3762 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Wed May 5 20:41:20 CST 1999 root@guppy.dons.net.au:/usr/src/sys/compile/GUPPY.nosmp Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x653 Stepping=3 Features=0x183fbff real memory = 134217728 (131072K bytes) avail memory = 127442944 (124456K bytes) Preloaded elf kernel "kernel.nosmp" at 0xc0308000. Pentium Pro MTRR support enabled, default memory type is uncacheable ccd0-3: Concatenated disk drivers Probing for PnP devices: CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x12939604 Comp ID: PNPb02f [0x2fb0 d041] npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 chip2: at device 7.3 on pci0 de0: at device 11.0 on pci0 de0: interrupting at irq 11 de0: 21140 [10-100Mb/s] pass 1.1 de0: address 00:80:ad:16:77:3e de0: enabling 100baseTX port devclass_alloc_unit: npx0 already exists, using next available unit number devclass_alloc_unit: apm0 already exists, using next available unit number isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 12416MB (25429824 sectors), 25228 cyls, 16 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 0 (atapi): , removable, dma, ior dis wcd0: drive speed 5512KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc1: interrupting at irq 15 atkbdc0: at port 0x60 on isa0 psm0: on atkbdc0 psm0: model MouseMan+, device ID 0 psm0: interrupting at irq 12 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0: not probed (disabled) sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sb0: interrupting at irq 5 sbxvi0 at drq 5 on isa0 snd0: sbmidi0 at port 0x330 on isa0 snd0: opl0 at port 0x388 on isa0 snd0: awe0 at port 0x620 on isa0 AWE32: not detected joy0 at port 0x201 on isa0 joy0: joystick changing root device to wd0s3a ffs_mountfs: superblock updated for soft updates DEVICE_SUSPEND error 6, ignored resumed from suspended mode (slept 00:00:03) DEVICE_SUSPEND error 6, ignored resumed from suspended mode (slept 00:00:12) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates de0: enabling 10baseT port --_=XFMail.1.3.p0.FreeBSD:990505210947:369=_ Content-Disposition: attachment; filename="apm_out.txt" Content-Transfer-Encoding: 7bit Content-Description: apm_out.txt Content-Type: text/plain; charset=us-ascii; name=apm_out.txt; SizeOnDisk=346 APM version: 1.2 APM Managment: Enabled AC Line status: on-line Battery status: unknown Remaining battery life: unknown Remaining battery time: unknown Number of batteries: 0 Resume timer: disabled Resume on ring indicator: enabled APM Capacities: global standby state global suspend state resume timer from standby resume timer from suspend --_=XFMail.1.3.p0.FreeBSD:990505210947:369=_ Content-Disposition: attachment; filename="GUPPY" Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=us-ascii; name=GUPPY; SizeOnDisk=3390 bWFjaGluZQkJImkzODYiCmNwdQkJIkk2ODZfQ1BVIgppZGVudAkJVEVTVAptYXh1c2VycwkzMgoK b3B0aW9ucyAgICAgICAgIElOQ0xVREVfQ09ORklHX0ZJTEUgICAgICMgSW5jbHVkZSB0aGlzIGZp bGUgaW4ga2VybmVsCgpvcHRpb25zICAgICAgICAgVVNFUkNPTkZJRyAgICAgICAgICAgICAgI2Jv b3QgLWMgZWRpdG9yCm9wdGlvbnMgICAgICAgICBWSVNVQUxfVVNFUkNPTkZJRyAgICAgICAjdmlz dWFsIGJvb3QgLWMgZWRpdG9yCgpvcHRpb25zCQlJTkVUCQkJI0ludGVyTkVUd29ya2luZwpvcHRp b25zCQlGRlMJCQkjQmVya2VsZXkgRmFzdCBGaWxlc3lzdGVtCm9wdGlvbnMJCU5GUwkJCSNOZXR3 b3JrIEZpbGVzeXN0ZW0KI29wdGlvbnMJCSJDRDk2NjAiCQkjSVNPIDk2NjAgRmlsZXN5c3RlbQpv cHRpb25zCQlQUk9DRlMJCQkjUHJvY2VzcyBmaWxlc3lzdGVtCm9wdGlvbnMJCSJDT01QQVRfNDMi CQkjQ29tcGF0aWJsZSB3aXRoIEJTRCA0LjMgW0tFRVAgVEhJUyFdCm9wdGlvbnMJCVVDT05TT0xF CQkjQWxsb3cgdXNlcnMgdG8gZ3JhYiB0aGUgY29uc29sZQpvcHRpb25zCQlLVFJBQ0UJCQkja2Vy bmVsIHRyYWNpbmcKCm9wdGlvbnMJCVNZU1ZTSE0Kb3B0aW9ucwkJU1lTVlNFTQpvcHRpb25zCQlT WVNWTVNHCgpvcHRpb25zCQlEREIKI29wdGlvbnMgICAgICAgICBEREJfVU5BVFRFTkRFRAoKI29w dGlvbnMJCUJPVU5DRV9CVUZGRVJTCQkjRm9yIEFEViBjb250cm9sbGVyCm9wdGlvbnMJCUNPTlNQ RUVEPTExNTIwMAkJI2RlZmF1bHQgc3BlZWQgZm9yIHNlcmlhbCBjb25zb2xlCm9wdGlvbnMJCU1T R0JVRl9TSVpFPTMyNzY4CgpvcHRpb25zCQlTT0ZUVVBEQVRFUwoKb3B0aW9ucyAgICAgICAgIFNN UCAgICAgICAgICAgICAgICAgICAgICMgU3ltbWV0cmljIE11bHRpUHJvY2Vzc29yIEtlcm5lbApv cHRpb25zICAgICAgICAgQVBJQ19JTyAgICAgICAgICAgICAgICAgIyBTeW1tZXRyaWMgKEFQSUMp IEkvTwoKY29uZmlnCQlrZXJuZWwJcm9vdCBvbiB3ZDAgZHVtcHMgb24gd2QwCgpjb250cm9sbGVy CWlzYTAKY29udHJvbGxlcglwY2kwCgpjb250cm9sbGVyCWZkYzAJYXQgaXNhPyBwb3J0ICJJT19G RDEiIGlycSA2IGRycSAyCmRpc2sJCWZkMAlhdCBmZGMwIGRyaXZlIDAKZGlzawkJZmQxCWF0IGZk YzAgZHJpdmUgMQoKY29udHJvbGxlcgl3ZGMwCWF0IGlzYT8gcG9ydCAiSU9fV0QxIiBpcnEgMTQg ZmxhZ3MgMHhhMGZmYTBmZgpkaXNrCQl3ZDAJYXQgd2RjMCBkcml2ZSAwCmRpc2sJCXdkMQlhdCB3 ZGMwIGRyaXZlIDEKY29udHJvbGxlcgl3ZGMxCWF0IGlzYT8gcG9ydCAiSU9fV0QyIiBpcnEgMTUg ZmxhZ3MgMHhhMGZmYTBmZgpkaXNrCQl3ZDIJYXQgd2RjMSBkcml2ZSAwCmRpc2sJCXdkMwlhdCB3 ZGMxIGRyaXZlIDEKCmRldmljZQkJd2NkMAoKb3B0aW9ucyAgICAgICAgIElERV9ERUxBWT0yMDAw ICAjIEJlIG9wdGltaXN0aWMgYWJvdXQgSm9lIElERSBkZXZpY2UKCm9wdGlvbnMJCSJWTTg2Igpv cHRpb25zCQlWRVNBCgojIGF0a2JkYzAgY29udHJvbGxzIGJvdGggdGhlIGtleWJvYXJkIGFuZCB0 aGUgUFMvMiBtb3VzZQpjb250cm9sbGVyICAgICAgYXRrYmRjMCBhdCBpc2E/IHBvcnQgSU9fS0JE CmRldmljZSAgICAgICAgICBwc20wICAgIGF0IGF0a2JkYz8gaXJxIDEyCmRldmljZSAgICAgICAg ICBhdGtiZDAgIGF0IGF0a2JkYz8gaXJxIDEKCmRldmljZSAgICAgICAgICB2Z2EwICAgIGF0IGlz YT8gcG9ydCA/IGNvbmZsaWN0cwoKIyBzcGxhc2ggc2NyZWVuL3NjcmVlbiBzYXZlcgpwc2V1ZG8t ZGV2aWNlICAgc3BsYXNoCgojIHN5c2NvbnMgaXMgdGhlIGRlZmF1bHQgY29uc29sZSBkcml2ZXIs IHJlc2VtYmxpbmcgYW4gU0NPIGNvbnNvbGUKZGV2aWNlICAgICAgICAgIHNjMCAgICAgYXQgaXNh PwoKIyBNYW5kYXRvcnksIGRvbid0IHJlbW92ZQpkZXZpY2UJCW5weDAJYXQgaXNhPyBwb3J0ICJJ T19OUFgiIGlycSAxMwoKZGV2aWNlCQlzaW8wCWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIgaXJxIDQK ZGV2aWNlCQlzaW8xCWF0IGlzYT8gcG9ydCAiSU9fQ09NMiIgaXJxIDMKCmRldmljZQkJZWQwCWF0 IGlzYT8gcG9ydCAweDI4MCBpcnEgNSBpb21lbSAweGQ4MDAwCgpjb250cm9sbGVyICAgICAgcHBi dXMwCmRldmljZSAgICAgICAgICBubHB0MCAgIGF0IHBwYnVzPwpkZXZpY2UgICAgICAgICAgcGxp cDAgICBhdCBwcGJ1cz8KZGV2aWNlICAgICAgICAgIHBwaTAgICAgYXQgcHBidXM/CmRldmljZSAg ICAgICAgICBwcHMwICAgIGF0IHBwYnVzPwpkZXZpY2UgICAgICAgICAgbHBiYjAgICBhdCBwcGJ1 cz8KCmNvbnRyb2xsZXIgICAgICBwcGMwICAgIGF0IGlzYT8gZGlzYWJsZSBwb3J0ID8gaXJxIDcK CmRldmljZQkJZGUwCmRldmljZQkJZnhwMAoKY29udHJvbGxlcglwbnAwCgpjb250cm9sbGVyICAg ICAgc25kMApkZXZpY2Ugc2IwICAgICAgYXQgaXNhPyBwb3J0IDB4MjIwIGlycSA1IGRycSAxCmRl dmljZSBzYnh2aTAgICBhdCBpc2E/IGRycSA1CmRldmljZSBzYm1pZGkwICBhdCBpc2E/IHBvcnQg MHgzMzAKZGV2aWNlIG9wbDAgICAgIGF0IGlzYT8gcG9ydCAweDM4OApkZXZpY2UgYXdlMCAgICAg YXQgaXNhPyBwb3J0IDB4NjIwCmRldmljZSAgICAgICAgICBqb3kwICAgIGF0IGlzYT8gcG9ydCAi SU9fR0FNRSIKCmRldmljZSAgICAgICAgICBhcG0wICAgIGF0IGlzYT8gY29uZmxpY3RzCgpjb250 cm9sbGVyIHNtYnVzMAoKY29udHJvbGxlciBpbnRwbTAKCmRldmljZSBzbWIwICAgICBhdCBzbWJ1 cz8KCmNvbnRyb2xsZXIgaWljYnVzMApjb250cm9sbGVyIGlpY2JiMAoKZGV2aWNlIGljMCAgICAg IGF0IGlpY2J1cz8KZGV2aWNlIGlpYzAgICAgIGF0IGlpY2J1cz8KZGV2aWNlIGlpY3NtYjAgIGF0 IGlpY2J1cz8KCmNvbnRyb2xsZXIgICAgICBhaGMwCmNvbnRyb2xsZXIgICAgICBzY2J1czAgICNi YXNlIFNDU0kgY29kZQpkZXZpY2UgICAgICAgICAgY2gwICAgICAjU0NTSSBtZWRpYSBjaGFuZ2Vy cwpkZXZpY2UgICAgICAgICAgZGEwICAgICAjU0NTSSBkaXJlY3QgYWNjZXNzIGRldmljZXMgKGFr YSBkaXNrcykKZGV2aWNlICAgICAgICAgIHNhMCAgICAgI1NDU0kgdGFwZXMKZGV2aWNlICAgICAg ICAgIGNkMCAgICAgI1NDU0kgQ0QtUk9NcwpkZXZpY2UgICAgICAgICBvZDAgICAgICNTQ1NJIG9w dGljYWwgZGlzawpkZXZpY2UgICAgICAgICAgcGFzczAgICAjQ0FNIHBhc3N0aHJvdWdoIGRyaXZl cgoKCnBzZXVkby1kZXZpY2UJbG9vcApwc2V1ZG8tZGV2aWNlCWV0aGVyCnBzZXVkby1kZXZpY2UJ cHR5CQkxNgpwc2V1ZG8tZGV2aWNlCWJwZmlsdGVyCTQKcHNldWRvLWRldmljZQlnemlwCQkjIEV4 ZWMgZ3ppcHBlZCBhLm91dCdzCnBzZXVkby1kZXZpY2UJY2NkCTQJI0NvbmNhdGVuYXRlZCBkaXNr IGRyaXZlcgpwc2V1ZG8tZGV2aWNlCXZuCgoK --_=XFMail.1.3.p0.FreeBSD:990505210947:369=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 5:23:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.36]) by hub.freebsd.org (Postfix) with ESMTP id 08E9F15151 for ; Wed, 5 May 1999 05:23:20 -0700 (PDT) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id MAA88758; Wed, 5 May 1999 12:22:42 GMT (envelope-from zach) Date: Wed, 5 May 1999 07:22:41 -0500 From: Zach Heilig To: "Erik H. Bakke" Cc: freebsd-current@freebsd.org Subject: Re: PCM problem solved (?) Message-ID: <19990505072241.A88738@k6n1.znh.org> References: <009b01be96c3$90063e70$589a4cc0@intranett.lyssand.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <009b01be96c3$90063e70$589a4cc0@intranett.lyssand.com>; from Erik H. Bakke on Wed, May 05, 1999 at 08:49:53AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 05, 1999 at 08:49:53AM +0200, Erik H. Bakke wrote: > In what may have seemed a desperate move to try to find out where > the sound drivers decided to stop, I took a look at my config file. > I tried to change the attachment of the pcm device from isa? to nexus?, > trying to move it closer to the source of the interrupts. (This is with an > SB PCI 128) > When I had rebuilt the kernel and rebooted, the error messages seemed > a bit different. > It was actually suggested that I should try to use pcm0 instead of pcm1. > A quick remake of the devices, and suddenly, the sound was back. > > Will this approach solve the problems for you other people with > the same problem? I haven't had a chance to test it out yet to be sure, but: dfr 1999/05/04 14:18:23 PDT Modified files: sys/i386/isa intr_machdep.c Log: Use unit, not device_id as an argument to an old-style ISA interrupt handler. This fixes pnp interrupts and would have fixed pccard interrupts but a workaround has been applied there. This the sound driver problems which people have reported with new-bus. Revision Changes Path 1.21 +3 -3 src/sys/i386/isa/intr_machdep.c was appearantly the problem... -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 5:25:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.36]) by hub.freebsd.org (Postfix) with ESMTP id 2DAAD1589F for ; Wed, 5 May 1999 05:25:11 -0700 (PDT) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id MAA88779 for current@freebsd.org; Wed, 5 May 1999 12:24:38 GMT (envelope-from zach) Date: Wed, 5 May 1999 07:24:38 -0500 From: Zach Heilig To: current@freebsd.org Subject: make world breakage (easy fix).. Message-ID: <19990505072437.B88738@k6n1.znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (someone added: 'wi.' instead of 'wi.4') Index: Makefile =================================================================== RCS file: /home/ncvs/src/share/man/man4/man4.i386/Makefile,v retrieving revision 1.104 diff -u -r1.104 Makefile --- Makefile 1999/05/05 07:36:57 1.104 +++ Makefile 1999/05/05 12:17:27 @@ -9,7 +9,7 @@ rdp.4 rl.4 sb.4 scd.4 screen.4 si.4 sio.4 \ spkr.4 splash.4 sr.4 syscons.4 sysmouse.4 ti.4 tl.4 tw.4 tx.4 uhci.4 \ ukbd.4 ums.4 usb.4 vga.4 vr.4 vx.4 \ - wb.4 wd.4 wfd.4 wi. wl.4 wt.4 xl.4 ze.4 zp.4 + wb.4 wd.4 wfd.4 wi.4 wl.4 wt.4 xl.4 ze.4 zp.4 MLINKS= adv.4 ../adv.4 MLINKS+= adw.4 ../adw.4 -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 6: 9:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 4AB7B14C36 for ; Wed, 5 May 1999 06:09:27 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id XAA27105 for current@freeBSD.org; Wed, 5 May 1999 23:18:29 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905051318.XAA27105@cimlogic.com.au> Subject: Math emulation is broken in sys/i386/isa/npx.c To: current@freeBSD.org Date: Wed, 5 May 1999 23:18:29 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rev 1.67 of npx.c changed a #ifdef SMP to #ifdef 1, preventing the test for the hardware coprocessor. This breaks support for 386 processors without math coprocessors. Grrr. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 6:28: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 507C615191 for ; Wed, 5 May 1999 06:27:53 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-43.iptelecom.net.ua [212.42.68.234]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA00919 for ; Wed, 5 May 1999 16:28:24 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id QAA20877 for ; Wed, 5 May 1999 16:27:46 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37304751.59601766@altavista.net> Date: Wed, 05 May 1999 16:27:45 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Today word breakage Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Word broken with the following message: ===> usr.bin/gensetdefs make: don't know how to make gensetdefs.1. Stop š To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 7:41:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 3E69014BEE for ; Wed, 5 May 1999 07:41:32 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA09586; Wed, 5 May 1999 10:41:31 -0400 (EDT) (envelope-from luoqi) Date: Wed, 5 May 1999 10:41:31 -0400 (EDT) From: Luoqi Chen Message-Id: <199905051441.KAA09586@lor.watermarkgroup.com> To: current@FreeBSD.ORG, darius@dons.net.au Subject: Re: SMP & APM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > Has anyone tried having APM and SMP in the same kernel? It panic()'s mine :) > > Basically the machine panics a few seconds after I do 'apmconf -e'. apm seems > to return normal values though. > > I've attached a sample output from APM, dmesg and my kernel config. > > I get a trap 12: page fault in kernel mode > mp_lock = 01000009; cpuid = 1; lapic.id = 01000000 > fault virtual address = 0x75f0 > fault code = supervisor read, page not present > interrupt pointer = 0x8:0xc0208a4c > stack pointer = 0x10:0xff80dd78 > frame pointer = 0x10:0xff80dd7c > 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 = Idle > interrupt mask = <- SMP: XXX > > Also, nm kernel.debug | sort shows that 0xc0208a4c is in Xbpt > Are you sure it's in Xbpt? Xbpt has only 6 lines of code and none of them is likely to generate a page fault. What's the address of symbol Xbpt? > --- > 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 > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 7:47:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id D767614DCC for ; Wed, 5 May 1999 07:47:27 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id AAA04946; Thu, 6 May 1999 00:17:14 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905051441.KAA09586@lor.watermarkgroup.com> Date: Thu, 06 May 1999 00:17:14 +0930 (CST) From: "Daniel J. O'Connor" To: Luoqi Chen Subject: Re: SMP & APM Cc: darius@dons.net.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-May-99 Luoqi Chen wrote: > > Also, nm kernel.debug | sort shows that 0xc0208a4c is in Xbpt > Are you sure it's in Xbpt? Xbpt has only 6 lines of code and none of them is > likely to generate a page fault. What's the address of symbol Xbpt? Yeah, well, it didn't look likely to me either but.. :-/ Here is part of nm kernel.debug | sort ... c0208a30 T Xnmi c0208a3c T Xbpt c0208a50 T Xofl ... I'll give it another bash and see how goes.. Unfortunatly I can't get crash dumps. I should be able to get a null modem cable tomorrow, so I can try a serial console and remote gdb. --- 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-current" in the body of the message From owner-freebsd-current Wed May 5 8: 1: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id A60C615090 for ; Wed, 5 May 1999 08:00:54 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA09856; Wed, 5 May 1999 11:00:48 -0400 (EDT) (envelope-from luoqi) Date: Wed, 5 May 1999 11:00:48 -0400 (EDT) From: Luoqi Chen Message-Id: <199905051500.LAA09856@lor.watermarkgroup.com> To: doconnor@gsoft.com.au, luoqi@watermarkgroup.com Subject: Re: SMP & APM Cc: current@FreeBSD.ORG, darius@dons.net.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yeah, well, it didn't look likely to me either but.. :-/ > > Here is part of nm kernel.debug | sort > ... > c0208a30 T Xnmi > c0208a3c T Xbpt > c0208a50 T Xofl > ... > Did you actually boot from kernel.debug? If not, use the kernel you booted from, the symbols should still be there. > I'll give it another bash and see how goes.. Unfortunatly I can't get crash > dumps. I should be able to get a null modem cable tomorrow, so I can try a > serial console and remote gdb. > > --- > 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 -lq PS: `nm -n' sorts the output by address. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 8: 2:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 68F3715006 for ; Wed, 5 May 1999 08:02:31 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id QAA04529; Wed, 5 May 1999 16:02:20 +0100 (BST) (envelope-from rb) Message-Id: <3.0.6.32.19990505160215.007cca10@192.168.255.1> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 05 May 1999 16:02:15 +0100 To: current@FreeBSD.ORG From: Bob Bishop Subject: Re: Math emulation is broken in sys/i386/isa/npx.c Cc: John Birrell In-Reply-To: <199905051318.XAA27105@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 23:18 05/05/99 +1000, John Birrell wrote: > >Rev 1.67 of npx.c changed a #ifdef SMP to #ifdef 1, preventing the >test for the hardware coprocessor. This breaks support for 386 processors >without math coprocessors. Grrr. ... and for 486SXs. More Grrr. -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 8:22:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 4A9ED15332 for ; Wed, 5 May 1999 08:22:04 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 4BCE113F for ; Wed, 5 May 1999 15:21:57 +0000 (GMT) Date: Wed, 5 May 1999 19:21:57 +0400 (MSD) From: oZZ!!! To: current@FreeBSD.org Subject: little patch for pkg_info ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Here is a little patch for /usr/src/usr.sbin/pkg_install/info/perform.c --- perform.c.orig Wed May 5 18:37:07 1999 +++ perform.c Wed May 5 19:16:36 1999 @@ -134,6 +134,9 @@ warnx("can't find package `%s' installed or in a file!", pkg); return 1; } + if (!strcmp (log_dir, "/var/db/pkg/.mkversion")) { + return 1; + } if (chdir(log_dir) == FAIL) { warnx("can't change directory to '%s'!", log_dir); return 1; What do think about? Rgdz, Sergey Osokin aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 8:32:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id 3D59515757 for ; Wed, 5 May 1999 08:32:38 -0700 (PDT) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.F05182E0@mailer.syr.edu>; Wed, 5 May 1999 11:32:21 -0400 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with SMTP id LAA22804 for ; Wed, 5 May 1999 11:32:09 -0400 (EDT) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Wed, 5 May 1999 11:32:08 -0400 (EDT) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: current@freebsd.org Subject: questions on modifications to the aio code Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to finish my modifications to the aio code, and have a few questions I'm hoping someone would be willing to take time to answer. First, I have modified the code to queue aio requests for sockets differently. If the socket is soreadable/writeable, the operation happens as before. If not, the aio op is queued seperately. This is where the complexity begins. When sowakeup is called, it checks to see if the socket is waiting on async operations and upcalls into a new routine to move the queued operations back to the main job queue. This means that all the manipulations of that queue (a TAILQ) must be protected at by splnet()/splx() blocks. There are some number of these manipulations. My question is: should I create an alternate queue to hold aio operations for now-ready sockets, so that I don't have to splnet()/splx() every manipulation of the main queue? How expensive is splnet? Note that there's already a separate queue for block io routines, but that makes more sense because they're handled in a completely different way. Second, I ended up having to back out some code written to do reads in the upcall because I was generating a panic every time that an upcall happened when my process wasn't curproc (uio_move was generating a trap because curpcb? wasn't pointing where/describing what it thought it should). I'm wondering if I can do i/o on a socket descriptor (using a struct uio) during an upcall for a socket that I know to be readable when I don't know that that process is curproc. Doing the read in the upcall offers a significant increase in performance, so its a nontrivial win. Finally, a stylistic question. I'm unsure what accepted/able practice for including headers across kernel source files. I modified the socket structure (socketvar.h) to include a TAILQ_HEAD for aio operations waiting on that socket. This TAILQ_HEAD points to struct aiocblist. I moved that structure from vfs_aio.c to sys/aio.h and then included sys/aio.h in uipc_socket.c. Is this the correct thing to do? Sorry for the basic questions, but I'd like to see this work get committed, and I understand that means that it needs to be done "right" for that to happen. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 8:49: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 5ACC615392 for ; Wed, 5 May 1999 08:48:59 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by majordomo2.umd.edu (8.9.3/8.9.0.Beta6) with ESMTP id LAA19544 for ; Wed, 5 May 1999 11:48:54 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.0.Beta6) with SMTP id LAA21107 for ; Wed, 5 May 1999 11:48:53 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.0.Beta6) with SMTP id LAA21101 for ; Wed, 5 May 1999 11:48:53 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Wed, 5 May 1999 11:48:52 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: c++ broken?? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG c++ -Wall -o p5.x flight.o name.o passenger.o passengerlist.o plane.o main.o /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' *** Error code 1 Stop. That is the error I got when I tried to compile a program for my C++ class. It compiles fine on a DEC Alpha. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 8:52: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id B47F014F4C for ; Wed, 5 May 1999 08:51:58 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA10321; Wed, 5 May 1999 11:51:57 -0400 (EDT) (envelope-from luoqi) Date: Wed, 5 May 1999 11:51:57 -0400 (EDT) From: Luoqi Chen Message-Id: <199905051551.LAA10321@lor.watermarkgroup.com> To: current@FreeBSD.ORG, darius@dons.net.au Subject: Re: SMP & APM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > Has anyone tried having APM and SMP in the same kernel? It panic()'s mine :) > > Basically the machine panics a few seconds after I do 'apmconf -e'. apm seems > to return normal values though. > > I've attached a sample output from APM, dmesg and my kernel config. > > I get a trap 12: page fault in kernel mode > mp_lock = 01000009; cpuid = 1; lapic.id = 01000000 > fault virtual address = 0x75f0 > fault code = supervisor read, page not present > interrupt pointer = 0x8:0xc0208a4c > stack pointer = 0x10:0xff80dd78 > frame pointer = 0x10:0xff80dd7c > 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 = Idle > interrupt mask = <- SMP: XXX > > Also, nm kernel.debug | sort shows that 0xc0208a4c is in Xbpt > > --- > 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 > My SMP vm sharing commit broke APM. Please try out this patch, Index: apm.c =================================================================== RCS file: /home/ncvs/src/sys/i386/apm/apm.c,v retrieving revision 1.80 diff -u -r1.80 apm.c --- apm.c 1999/04/21 07:57:55 1.80 +++ apm.c 1999/05/05 15:44:48 @@ -20,6 +20,7 @@ #include "opt_devfs.h" #include "opt_vm86.h" +#include "opt_smp.h" #include #include @@ -45,6 +46,10 @@ #include #endif +#ifdef SMP +#include +#endif + static int apm_display __P((int newstate)); static int apm_int __P((u_long *eax, u_long *ebx, u_long *ecx, u_long *edx)); static void apm_resume __P((void)); @@ -92,6 +97,10 @@ static void setup_apm_gdt(u_int code32_base, u_int code16_base, u_int data_base, u_int code32_limit, u_int code16_limit, u_int data_limit) { +#ifdef SMP + int x; +#endif + /* setup 32bit code segment */ gdt_segs[GAPMCODE32_SEL].ssd_base = code32_base; gdt_segs[GAPMCODE32_SEL].ssd_limit = code32_limit; @@ -108,6 +117,14 @@ ssdtosd(gdt_segs + GAPMCODE32_SEL, &gdt[GAPMCODE32_SEL].sd); ssdtosd(gdt_segs + GAPMCODE16_SEL, &gdt[GAPMCODE16_SEL].sd); ssdtosd(gdt_segs + GAPMDATA_SEL , &gdt[GAPMDATA_SEL ].sd); + +#ifdef SMP + for (x = 1; x < mp_ncpus; x++) { + gdt[x * NGDT + GAPMCODE32_SEL].sd = gdt[GAPMCODE32_SEL].sd; + gdt[x * NGDT + GAPMCODE16_SEL].sd = gdt[GAPMCODE16_SEL].sd; + gdt[x * NGDT + GAPMDATA_SEL ].sd = gdt[GAPMDATA_SEL ].sd; + } +#endif } /* 48bit far pointer. Do not staticize - used from apm_setup.s */ -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 10: 3:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AECF9154A9 for ; Wed, 5 May 1999 10:03:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA27003; Wed, 5 May 1999 10:03:06 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 May 1999 10:03:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199905051703.KAA27003@apollo.backplane.com> To: Tony Finch Cc: current@FreeBSD.ORG Subject: Re: Any action on PR 10570 ? getting closer to 65K :-( References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon wrote: :> :> I think the worst case you might see is on the order of 50,000 or so :> route entries. : :If you read the PR you'll see that we have over 70,000 routes on some :interfaces in our network, and we aren't doing multipath routeing. :(We have c. 20,000 modems and our customers have static IP addresses.) : :> It take a phenominally stupid network setup to create more then that. : ::-) : :Tony. We had a similar situation at BEST, but we realized fairly quickly that static IP's would be disaster to route as our network grew. So we stopped handing them out to 'normal' dialup customers and went w/ dynamic IP assignment. -Matt Matthew Dillon :f.a.n.finch dot@dotat.at fanf@demon.net :Arthur: "Oh, that sounds better, have you worked out the controls?" :Ford: "No, we just stopped playing with them." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 11:15:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 71F40151D7 for ; Wed, 5 May 1999 11:15:13 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id VAA24679 for ; Wed, 5 May 1999 21:15:10 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 27F041F2D; Wed, 5 May 1999 21:15:11 +0300 (EEST) Date: Wed, 5 May 1999 21:15:11 +0300 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: Thanks, sound is fixed Message-ID: <19990505211510.A536@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just want to let know that sound works again for my workstation. Thanks Doug, it was quite annoying to have icecast running but not to hear anything I broadcast :-) -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 11:19:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id DC5FC15350 for ; Wed, 5 May 1999 11:19:18 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA23864; Thu, 6 May 1999 04:19:16 +1000 Date: Thu, 6 May 1999 04:19:16 +1000 From: Bruce Evans Message-Id: <199905051819.EAA23864@godzilla.zeta.org.au> To: current@FreeBSD.ORG, jb@cimlogic.com.au Subject: Re: Math emulation is broken in sys/i386/isa/npx.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Rev 1.67 of npx.c changed a #ifdef SMP to #ifdef 1, preventing the >test for the hardware coprocessor. This breaks support for 386 processors >without math coprocessors. Grrr. It was also broken a month ago by changing TARGET_DEFAULT from (MASK_NO_FANCY_MATH_387 | 0301) for gcc to 0301 for egcs. This mainly permits egcs to emit fsqrt instructions. This can be worked around by using the GPL'ed math emulator or rebuilding everything affected with CFLAGS+=-fno-fancy-math-387. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 11:43:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 073AE14CFF for ; Wed, 5 May 1999 11:43:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA01236; Wed, 5 May 1999 11:42:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905051842.LAA01236@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: alk@pobox.com Cc: current@freebsd.org Subject: Re: VESA/SMP problems again In-reply-to: Your message of "Tue, 04 May 1999 17:32:17 CDT." <14127.29964.319475.838650@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 May 1999 11:42:20 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Insufficient content. Please add more and try again. > An alert: VESA/SMP seems to be problematic again. For example, this > sequence reliably brings me down to the bios: > > startx > ctl-alt-bksp > vidcontrol 132x42 > startx > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 11:47:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id A089D14CC5 for ; Wed, 5 May 1999 11:47:06 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA01612; Wed, 5 May 1999 19:47:07 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 5 May 1999 19:47:07 +0100 (BST) From: Doug Rabson To: Vallo Kallaste Cc: freebsd-current@freebsd.org Subject: Re: Thanks, sound is fixed In-Reply-To: <19990505211510.A536@myhakas.matti.ee> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 May 1999, Vallo Kallaste wrote: > I just want to let know that sound works again for my workstation. > Thanks Doug, it was quite annoying to have icecast running but not to > hear anything I broadcast :-) Sorry the fix took so long :-). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 12:22:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 0897814ECA for ; Wed, 5 May 1999 12:22:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01536; Wed, 5 May 1999 12:19:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905051919.MAA01536@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel J. O'Connor" Cc: Luoqi Chen , darius@dons.net.au, current@FreeBSD.ORG Subject: Re: SMP & APM In-reply-to: Your message of "Thu, 06 May 1999 00:17:14 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 May 1999 12:19:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 05-May-99 Luoqi Chen wrote: > > > Also, nm kernel.debug | sort shows that 0xc0208a4c is in Xbpt > > Are you sure it's in Xbpt? Xbpt has only 6 lines of code and none of them is > > likely to generate a page fault. What's the address of symbol Xbpt? > > Yeah, well, it didn't look likely to me either but.. :-/ > > Here is part of nm kernel.debug | sort > ... > c0208a30 T Xnmi > c0208a3c T Xbpt > c0208a50 T Xofl > ... > > I'll give it another bash and see how goes.. Unfortunatly I can't get crash > dumps. I should be able to get a null modem cable tomorrow, so I can try a > serial console and remote gdb. I wonder if there are problems running the APM requests on an AP? Daniel, are you running with the most recent MTRR/SMP fixes? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 12:43: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (mail.kdsamerica.com [208.149.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 623C31553F for ; Wed, 5 May 1999 12:43:01 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id OAA46009; Wed, 5 May 1999 14:42:52 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 5 May 1999 14:42:51 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: mike@smith.net.au Cc: current@freebsd.org Subject: Re: VESA/SMP problems again References: <14127.29964.319475.838650@avalon.east> <199905051842.LAA01236@dingo.cdrom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14128.40466.876158.143162@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Mike Smith on Wed, 5 May: : : Insufficient content. Please add more and try again. Insufficient for what purpose? (Trying to understand what additional information you would like...) I've got a PR440FX dual running current (99.05.03) with an S3V (Trio64) and XFree96 3.3.something (XF86_S3V), with options SMP options APIC_IO options NCPU=2 options NBUS=4 options NAPIC=1 options NINTR=24 options VESA options VM86 I'm going to be crashing the system later today anyhow, so I'll try DDB to get an backtrace at that time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 12:50:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 92A8515542 for ; Wed, 5 May 1999 12:50:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01759; Wed, 5 May 1999 12:48:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905051948.MAA01759@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: alk@pobox.com Cc: mike@smith.net.au, current@freebsd.org Subject: Re: VESA/SMP problems again In-reply-to: Your message of "Wed, 05 May 1999 14:42:51 CDT." <14128.40466.876158.143162@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 May 1999 12:48:41 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Quoth Mike Smith on Wed, 5 May: > : > : Insufficient content. Please add more and try again. > > Insufficient for what purpose? (Trying to understand what > additional information you would like...) In one place (one message), you need: - what hardware - what firmware - instructions to repeat the problem - accurate and exact descriptions of the symptoms, including transcripts of actual error messages Do not use vague phrases like "it dies", "down to the BIOS", "smoke comes out the back". Do as much investigative work of your own as you can; understand that there's a good chance that we're not going to be able to reproduce your problem here. In your case, you're going to want to bring the XFree86 folks in, as it's the act of starting the server that actually kills your system; the VESA call just puts the card into a particular mode, it doesn't do anything after that. > I've got a PR440FX dual running current (99.05.03) with an S3V > (Trio64) and XFree96 3.3.something (XF86_S3V), with > options SMP > options APIC_IO > options NCPU=2 > options NBUS=4 > options NAPIC=1 > options NINTR=24 > options VESA > options VM86 > > I'm going to be crashing the system later today anyhow, so I'll try > DDB to get an backtrace at that time. That'd definitely help too. You may end up having to single-step through the X server to find out where it kills your system. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 13:33:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id D56FD152F8 for ; Wed, 5 May 1999 13:33:47 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id GAA28793; Thu, 6 May 1999 06:42:51 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905052042.GAA28793@cimlogic.com.au> Subject: Re: Math emulation is broken in sys/i386/isa/npx.c In-Reply-To: <199905051819.EAA23864@godzilla.zeta.org.au> from Bruce Evans at "May 6, 1999 4:19:16 am" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 6 May 1999 06:42:51 +1000 (EST) Cc: current@FreeBSD.ORG, jb@cimlogic.com.au X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >Rev 1.67 of npx.c changed a #ifdef SMP to #ifdef 1, preventing the > >test for the hardware coprocessor. This breaks support for 386 processors > >without math coprocessors. Grrr. > > It was also broken a month ago by changing TARGET_DEFAULT from > (MASK_NO_FANCY_MATH_387 | 0301) for gcc to 0301 for egcs. This mainly > permits egcs to emit fsqrt instructions. This can be worked around > by using the GPL'ed math emulator or rebuilding everything affected > with CFLAGS+=-fno-fancy-math-387. Well at least at that time I could _boot_ the kernel. Now it just hangs. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 13:48:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 480911555D for ; Wed, 5 May 1999 13:48:39 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA13568; Wed, 5 May 1999 13:48:36 -0700 (PDT) (envelope-from obrien) Message-ID: <19990505134836.A13540@nuxi.com> Date: Wed, 5 May 1999 13:48:36 -0700 From: "David O'Brien" To: Kenneth Wayne Culver Cc: current@freebsd.org Subject: Re: c++ broken?? Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kenneth Wayne Culver on Wed, May 05, 1999 at 11:48:52AM -0400 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /usr/lib/libstdc++.so: undefined reference to `filebuf virtual table' > /usr/lib/libstdc++.so: undefined reference to `stdiobuf virtual table' > *** Error code 1 > > That is the error I got when I tried to compile a program for my C++ > class. You need to update your source. This was fixed last week. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 14:41:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id DDAD214ED4 for ; Wed, 5 May 1999 14:41:39 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA37847; Wed, 5 May 1999 14:41:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: oZZ!!! Cc: current@FreeBSD.ORG Subject: Re: little patch for pkg_info ? In-reply-to: Your message of "Wed, 05 May 1999 19:21:57 +0400." Date: Wed, 05 May 1999 14:41:53 -0700 Message-ID: <37844.925940513@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > + if (!strcmp (log_dir, "/var/db/pkg/.mkversion")) { > + return 1; > + } I have a better patch for affected systems: rm /var/db/pkg/.mkversion :-) That file should no longer exist. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 15: 5:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from pez.hyperreal.org (pez.hyperreal.org [207.181.224.6]) by hub.freebsd.org (Postfix) with SMTP id 50FD51535A for ; Wed, 5 May 1999 15:05:15 -0700 (PDT) (envelope-from brian@hyperreal.org) Received: (qmail 19362 invoked by uid 4000); 5 May 1999 22:06:55 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 May 1999 22:06:55 -0000 Date: Wed, 5 May 1999 15:06:55 -0700 (PDT) From: Brian Behlendorf To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: <21787.925610260@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 May 1999, Jordan K. Hubbard wrote: > My suggestion would be to wait and see how bitkeeper pans out. Enough > people in the Linux camp have already looked at CVSup and gone "ooh, > sexy!" that I think there will already be significant pressure to > develop similar tools for the bitkeeper environment. When that > happens, we can start to look at this more seriously. I think that's wise. I'd also recommend people check out Bitkeeper's license before making any final decisions. It's not GPL, BSD, or any other Open Source license. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 15:40:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from cepheus.hkstar.com (cepheus.hkstar.com [202.82.3.12]) by hub.freebsd.org (Postfix) with ESMTP id A1E5D15561 for ; Wed, 5 May 1999 15:40:52 -0700 (PDT) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cepheus.hkstar.com (8.9.0/8.9.0) with ESMTP id GAA13088 for ; Thu, 6 May 1999 06:40:51 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id GAA21762 for freebsd-current@freebsd.org; Thu, 6 May 1999 06:40:49 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199905052240.GAA21762@b1.hkstar.com> Subject: make world failure To: freebsd-current@freebsd.org Date: Thu, 6 May 1999 06:40:48 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I had posted this message for a couple of weeks as I still didn't solve the problem. The error was reported when I tried to make world. My system is freebsd-current with ctm source upto src-cur.3858. The compiler is egcs-1.1.2. I had tried cd /usr/src and make cleandir and make cleandir. It didn't help. Any idea ? Thanks. Clarence ======= Error ======= ===> cpp cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: `GPLUSPLUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: initializer element for `include_defaults_array[0].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: `OLD_GPLUSPLUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: initializer element for `include_defaults_array[1].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: `GCC_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: initializer element for `include_defaults_array[2].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c: In function `main': /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: `GCC_INCLUDE_DIR' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: for each function it appears in.) *** Error code 1 Stop. ======= Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 15:43:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DDC5414CDF for ; Wed, 5 May 1999 15:43:17 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id SAA03332; Wed, 5 May 1999 18:40:29 -0400 (EDT) Date: Wed, 5 May 1999 18:40:28 -0400 (EDT) From: Chuck Robey To: Brian Behlendorf Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 May 1999, Brian Behlendorf wrote: > On Sat, 1 May 1999, Jordan K. Hubbard wrote: > > My suggestion would be to wait and see how bitkeeper pans out. Enough > > people in the Linux camp have already looked at CVSup and gone "ooh, > > sexy!" that I think there will already be significant pressure to > > develop similar tools for the bitkeeper environment. When that > > happens, we can start to look at this more seriously. > > I think that's wise. > > I'd also recommend people check out Bitkeeper's license before making any > final decisions. It's not GPL, BSD, or any other Open Source license. This entire BitKeeper discussion is totally worthless. We're not gonna change. Anyone here want to give up cvsup? Or kick away from a terminal addiction to ctm (and believe me, those ctm'ers are real happily addicted). The answer is no. Face it, it's *possible* that there are better management tools than cvs, but it's for darn sure we can't do better than cvsup/ctm. This discussion merits dropping, at least until someone rewrites cvsup & ctm. Don't hold your breath. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 15:55:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 02AE514E60 for ; Wed, 5 May 1999 15:55:48 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id IAA05602; Thu, 6 May 1999 08:25:37 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905051551.LAA10321@lor.watermarkgroup.com> Date: Thu, 06 May 1999 08:25:35 +0930 (CST) From: "Daniel J. O'Connor" To: Luoqi Chen Subject: Re: SMP & APM Cc: darius@dons.net.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-May-99 Luoqi Chen wrote: > My SMP vm sharing commit broke APM. Please try out this patch, That patch seems to have fixed it! Great stuff :) --- 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-current" in the body of the message From owner-freebsd-current Wed May 5 18: 5:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (Postfix) with SMTP id 5421114CF8 for ; Wed, 5 May 1999 18:05:19 -0700 (PDT) (envelope-from john@nlc.net.au) Received: (qmail 2483 invoked from network); 6 May 1999 11:05:16 +1000 Received: from nhj.nlc.net.au (HELO saruman) (203.24.133.1) by nhj.nlc.net.au with SMTP; 6 May 1999 11:05:16 +1000 Message-ID: <05b301be975c$806d8880$6cb611cb@scitec.com.au> From: "John Saunders" To: "FreeBSD current" Subject: Newconfig has silenced smb support Date: Thu, 6 May 1999 11:05:13 +1000 Organization: NORTHLINK COMMUNICATIONS MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In a recent cvsup I got the newconfig updates. These are generally working well and have solved a number of "inelegancies" in my setup. However since this update the kernel isn't recognising the SMB device. I have tried things like adding "at pci?" to the end of the controller config lines to no available. I've got an Intel chipset MB so I'm using the Intel SMB controller. Can somebody point me to the correct config to make it come back? P.S. My old config used to have an "device ed0 at isa? disable port blah blah" config line so my PCI ethernet card would work. I've now changed this to "device ed0 at pci?" and it works like a charm. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NORTHLINK COMMUNICATIONS P/L - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 18:43:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D228F158DC for ; Wed, 5 May 1999 18:43:09 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA20305 for ; Wed, 5 May 1999 18:43:09 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA28758; Wed, 5 May 1999 18:43:08 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 5 May 1999 18:43:08 -0700 (PDT) Message-Id: <199905060143.SAA28758@vashon.polstra.com> To: current@freebsd.org Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) In-Reply-To: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Chuck Robey wrote: > This discussion merits dropping, at least until someone rewrites > cvsup & ctm. Don't hold your breath. I haven't looked at bitkeeper, but I doubt anybody would have to _rewrite_ CVSup. It would just require that a new update method be added to handle whatever their files look like in an intelligent way. Until that was done, it's likely that CVSup's rsync method could handle them reasonbly well. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 18:55:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id C50921593D for ; Wed, 5 May 1999 18:55:09 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA20370 for ; Wed, 5 May 1999 18:55:08 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA28786; Wed, 5 May 1999 18:55:08 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 5 May 1999 18:55:08 -0700 (PDT) Message-Id: <199905060155.SAA28786@vashon.polstra.com> To: current@freebsd.org Subject: Re: PCCARD driver still sucks In-Reply-To: <199905041841.LAA00377@dingo.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199905041841.LAA00377@dingo.cdrom.com>, Mike Smith wrote: > > It seems that as of today -current pccard driver still isn't usable. > > Kernel paniced after pccardd trying ifconfig ed0. Following is my dmesg, > > interesting that pccardd complain about "slot 0,1,2,3", while I only > > have two. > > You're still loading the pcic module. Don't do that. Having been through this recently myself, I'd bet that his /etc/rc* files are out of date. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 20:31:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 5B7EF15017 for ; Wed, 5 May 1999 20:31:09 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id MAA00344; Thu, 6 May 1999 12:21:28 +0900 (JST) Message-Id: <199905060321.MAA00344@shidahara1.planet.sci.kobe-u.ac.jp> To: "John Saunders" Cc: newconfig@jp.freebsd.org, current@freebsd.org Subject: Re: Newconfig has silenced smb support In-reply-to: Your message of "Thu, 06 May 1999 11:05:13 +1000" References: <05b301be975c$806d8880$6cb611cb@scitec.com.au> Date: Thu, 06 May 1999 12:21:27 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <05b301be975c$806d8880$6cb611cb@scitec.com.au>, "John Saunders" wrote: >However since this update the kernel isn't recognising the SMB device. >I have tried things like adding "at pci?" to the end of the controller >config lines to no available. I've got an Intel chipset MB so I'm >using the Intel SMB controller. Sorry, I'm not familiar with newconfig bus rewriting,though I subscribe newconfig list.(;_;) Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 20:43:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from bulls.mei.co.jp (bulls.mei.co.jp [202.224.189.102]) by hub.freebsd.org (Postfix) with ESMTP id 064FD14C33 for ; Wed, 5 May 1999 20:43:06 -0700 (PDT) (envelope-from kana@saijo.mke.mei.co.jp) Received: by bulls.mei.co.jp (8.9.1/3.7W) with ESMTP id MAA18030; Thu, 6 May 1999 12:42:51 +0900 (JST) Received: by dodgers.mei.co.jp (8.9.1/3.7W) with SMTP id MAA09211; Thu, 6 May 1999 12:42:50 +0900 (JST) Received: from mkegate0.mke.mei.co.jp by mkews1.ho.mke.mei.co.jp (SMI-8.6/3.5Wpl7) id MAA08697; Thu, 6 May 1999 12:42:48 +0900 Received: from soft.saijo.mke.mei.co.jp by mkegate0.mke.mei.co.jp (8.8.8/3.6W-981218) id MAA12018; Thu, 6 May 1999 12:42:47 +0900 (JST) Received: from vepc03.saijo.mke.mei.co.jp by soft.saijo.mke.mei.co.jp (8.8.8/3.6W-980803) id MAA11879; Thu, 6 May 1999 12:43:32 +0900 (JST) Received: from localhost by vepc03.saijo.mke.mei.co.jp (8.8.8/3.7W) id MAA00767; Thu, 6 May 1999 12:45:01 +0900 (JST) To: takawata@shidahara1.planet.sci.kobe-u.ac.jp Cc: john@nlc.net.au, newconfig@jp.freebsd.org, current@freebsd.org Subject: Re: Newconfig has silenced smb support In-Reply-To: <199905060321.MAA00344@shidahara1.planet.sci.kobe-u.ac.jp> References: <05b301be975c$806d8880$6cb611cb@scitec.com.au> <199905060321.MAA00344@shidahara1.planet.sci.kobe-u.ac.jp> X-Mailer: Mew version 1.94b13 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990506124500B.kana@saijo.mke.mei.co.jp> Date: Thu, 06 May 1999 12:45:00 +0900 From: Masanori Kanaoka X-Dispatcher: imput version 990310(IM110) Lines: 13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Takanori Watanabe Subject: Re: Newconfig has silenced smb support Date: Thu, 06 May 1999 12:21:27 +0900 $ Sorry, I'm not familiar with newconfig bus rewriting,though I subscribe $ newconfig list.(;_;) see --- Masanori Kanaoka kana@saijo.mke.mei.co.jp kanaoka@ann.hi-ho.ne.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 21:24:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 4DDCC14E3A for ; Wed, 5 May 1999 21:24:32 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id AAA09663 for current@freebsd.org; Thu, 6 May 1999 00:23:29 -0400 (EDT) From: Mikhail Teterin Message-Id: <199905060423.AAA09663@kot.ne.mediaone.net> Subject: ide_pci.c without pci To: current@freebsd.org Date: Thu, 6 May 1999 00:23:29 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Wed, 5 May 1999 22:10:16 -0700 (PDT) (envelope-from myke@ees.com) Received: from localhost (myke@localhost) by phluffy.fks.bt (8.8.8/8.8.8) with ESMTP id WAA22355 for ; Wed, 5 May 1999 22:10:11 -0700 (PDT) (envelope-from myke@ees.com) Date: Wed, 5 May 1999 22:10:11 -0700 (PDT) From: Mike Holling X-Sender: myke@phluffy.fks.bt To: current@freebsd.org Subject: RTP and RTSP support in libalias? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apple's QuickTime 4 uses these protocols for streaming QuickTime, and I've got users asking me if the FreeBSD NAT box can be made to handle it. Looks like these protocols are new internet standards, has anyone integrated them into libalias yet? If not I might give it a shot, but I'm probably in over my head... - Mike PS. Apple provides links to the RFCs: http://www.apple.com/quicktime/resources/qt4/us/proxy/proxy.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 22:26:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9A789158FD for ; Wed, 5 May 1999 22:26:17 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA16264; Wed, 5 May 1999 23:25:32 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA15252; Wed, 5 May 1999 23:25:46 -0600 (MDT) Message-Id: <199905060525.XAA15252@harmony.village.org> To: Seigo TANIMURA Subject: Re: apmconf(8) -e ends to panic in apm_bios_call Cc: Luoqi Chen , freebsd-current@freebsd.org In-reply-to: Your message of "Thu, 06 May 1999 14:20:29 +0900." <199905060520.OAA83968@rina.naklab.dnj.ynu.ac.jp> References: <199905060520.OAA83968@rina.naklab.dnj.ynu.ac.jp> <199905040732.BAA55716@harmony.village.org> Date: Wed, 05 May 1999 23:25:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905060520.OAA83968@rina.naklab.dnj.ynu.ac.jp> Seigo TANIMURA writes: : My box has got two PII-266's, the RAM of 256MB on ASUS P2L97-DS(BIOS ver is 1005). : I used to apmconf(8) successfully on the kernel in 25th Apr. I have attached : the config at the end of this mail. MAXMEM=(256*1024) did not help... : : Daniel O'Connor has posted a problem similar to my one, followed by the fix : patch by Luoqi Chen. I will try that patch tonight at home... I strongly suspect that the Luoqi Chen fix will solve your problem. It certainly does fix a problem in the hardware configuration (SMP) that you are having. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 22:34:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.naklab.dnj.ynu.ac.jp (rina.naklab.dnj.ynu.ac.jp [133.34.17.16]) by hub.freebsd.org (Postfix) with ESMTP id A837514E2C for ; Wed, 5 May 1999 22:33:53 -0700 (PDT) (envelope-from tanimura@naklab.dnj.ynu.ac.jp) Received: from rina.naklab.dnj.ynu.ac.jp (localhost [127.0.0.1]) by rina.naklab.dnj.ynu.ac.jp (8.9.3/3.7W-Naklab-2.1-19981120) with ESMTP id OAA83968; Thu, 6 May 1999 14:20:29 +0900 (JST) Message-Id: <199905060520.OAA83968@rina.naklab.dnj.ynu.ac.jp> To: imp@harmony.village.org Cc: Nate Williams , Seigo TANIMURA , "Daniel J. O'Connor" , Luoqi Chen , freebsd-current@freebsd.org Subject: Re: apmconf(8) -e ends to panic in apm_bios_call From: Seigo TANIMURA In-Reply-To: Your message of "Tue, 04 May 1999 01:32:01 -0600" References: <199905040732.BAA55716@harmony.village.org> X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 06 May 1999 14:20:29 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Tue, 04 May 1999 01:32:01 -0600, Warner Losh said: imp> In message <19990502075751N.tanimura@sakuramail.com> Seigo TANIMURA writes: imp> : I traced to watch _apm_addr, which pointed the correct entry(0x000078a8) imp> : in both situations. The only one difference was CS... Has anyone got a clue? imp> I seem to recall seeing something similar a while ago. I think that imp> the problem was traced down to using 1.2 apm stuff on a 1.1 system. imp> What I seem to recall is that it was with apm(8), however. imp> What machine are you seeing this on? What does your config line look imp> like? Do you have VM86 in your kernel config file? My box has got two PII-266's, the RAM of 256MB on ASUS P2L97-DS(BIOS ver is 1005). I used to apmconf(8) successfully on the kernel in 25th Apr. I have attached the config at the end of this mail. MAXMEM=(256*1024) did not help... Daniel O'Connor has posted a problem similar to my one, followed by the fix patch by Luoqi Chen. I will try that patch tonight at home... --- v --- my config --- v --- # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.166 1999/04/24 21:45:44 peter Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU #ident GENERIC ident SILVER #maxusers 32 maxusers 512 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed #options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options DDB #options DDB_UNATTENDED options PQ_LARGECACHE #config kernel root on wd0 config kernel root on da0 dumps on da0 # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 controller pnp0 # PnP support for ISA #controller eisa0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 #controller wdc0 at isa? port IO_WD1 irq 14 #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port IO_WD2 irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 # ATAPI devices on wdc? #device wcd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) #device wst0 #IDE Tape (e.g. Travan) # New ATA driver by Soeren Schmidt # for a PCI only system (most modern machines) controller ata0 device atadisk0 # ATA disks device atapicd0 # ATAPI CDROM's #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tapes # You should add the following on ISA systems: #controller ata1 at isa? port "IO_WD1" irq 14 #controller ata2 at isa? port "IO_WD2" irq 15 # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 #controller ahb0 controller ahc0 #controller isp0 options AHC_ALLOW_MEMIO # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. #controller dpt0 #controller adv0 at isa? port ? irq ? #controller adw0 #controller bt0 at isa? port ? irq ? #controller aha0 at isa? port ? irq ? controller scbus0 device da0 #Only need one of these, the code dynamically grows device sa0 device pass0 device cd0 #device wt0 at isa? port 0x300 irq 5 drq 1 #device mcd0 at isa? port 0x300 irq 10 #controller matcd0 at isa? port 0x230 #device scd0 at isa? port 0x230 # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #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 device npx0 at nexus? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # #device apm0 at nexus? disable flags 0x31 # Advanced Power Management device apm0 at nexus? # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? #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 device rp0 # Parallel port device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? #controller vpo0 at ppbus? # # The following Ethernet NICs are all PCI devices. # #device ax0 # ASIX AX88140A device de0 # DEC/Intel DC21x4x (``Tulip'') #device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device rl0 # RealTek 8129/8139 #device tl0 # Texas Instruments ThunderLAN #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vr0 # VIA Rhine, Rhine II #device vx0 # 3Com 3c590, 3c595 (``Vortex'') #device wb0 # Winbond W89C840F #device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 irq 10 #device ex0 at isa? port? irq? #device fe0 at isa? port 0x300 irq ? #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 ##device ze0 at isa? port 0x300 irq 10 iomem 0xd8000 ##device zp0 at isa? port 0x300 irq 10 iomem 0xd8000 #device cs0 at isa? port 0x300 irq ? pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 #pseudo-device tun 1 pseudo-device tun 16 #pseudo-device pty 16 pseudo-device pty 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 4 pseudo-device vn 4 # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. #options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SHMMAXPGS=32768 options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter # USB support controller uhci0 controller ohci0 controller usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # device ums0 device ukbd0 device ulpt0 device uhid0 device ugen0 # Sound stuff #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 5 #device sbmidi0 at isa? port 0x330 #device awe0 at isa? port 0x620 #device opl0 at isa? port 0x388 #device uartsio0 at isa? port 0x3f8 irq 4 device pcm0 at isa? port 0x220 irq 5 drq 1 device midi0 at isa? port 0x3f8 irq 4 pseudo-device seq 1 # vinum #pseudo-device vinum # hack on mbuf options NMBCLUSTERS=(2048+MAXUSERS*64) # could this help? options MAXMEM=(256*1024) --- ^ --- my config --- ^ --- Seigo TANIMURA |M2, Nakagawa Lab, Dept of Electronics & CS =========================|Faculty of Engineering, Yokohama National Univ Powered by SIEMENS, |http://www.naklab.dnj.ynu.ac.jp/~tanimura/ FreeBSD 4.0-CURRENT |http://www.sakura.ne.jp/~tcarrot/ (25th Apr 1999) & muesli.|tanimura@naklab.dnj.ynu.ac.jp tcarrot@sakuramail.com VoxWare Midi Driver for Serial Ports on FreeBSD: http://www.naklab.dnj.ynu.ac.jp/~tanimura/freebsd-serialmidi/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 22:44:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7441E1512C for ; Wed, 5 May 1999 22:44:22 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id WAA25125; Wed, 5 May 1999 22:44:15 -0700 (PDT) (envelope-from obrien) Message-ID: <19990505224415.A25116@nuxi.com> Date: Wed, 5 May 1999 22:44:15 -0700 From: "David O'Brien" To: Chan Yiu Wah , freebsd-current@FreeBSD.ORG Subject: Re: make world failure Reply-To: obrien@NUXI.com References: <199905052240.GAA21762@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905052240.GAA21762@b1.hkstar.com>; from Chan Yiu Wah on Thu, May 06, 1999 at 06:40:48AM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had tried cd /usr/src and make cleandir and make cleandir. It didn't > help. Any idea ? Thanks. rm -rf /usr/src cd /usr cvs co src Something is wrong with your tree. This output is very simular to what you get when contrib/egcs/gcc/config/freebsd-native.h isn't being picked up properly. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 23:46:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt057n14.san.rr.com (dt051nc7.san.rr.com [204.210.32.199]) by hub.freebsd.org (Postfix) with ESMTP id 536F71593E for ; Wed, 5 May 1999 23:46:41 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt057n14.san.rr.com (8.8.8/8.8.8) with ESMTP id XAA27698 for ; Wed, 5 May 1999 23:46:41 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <37313AD0.F5EE0B1C@gorean.org> Date: Wed, 05 May 1999 23:46:40 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Question on 2.2.8 -> -current upgrade procedure Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been doing some reading and I think I have a grip on what I need to do to go from 2.2.8-Release to -current on my scratch box. Please check me and let me know if I've got it right: 1. Install 3.1-Stable sources 2. make upgrade 3. make world 4. make new kernel 5. reboot 6. Install -current sources 7. make world 8. make new kernel 9. reboot Now, the main question I have is, at what points do I want to upgrade /etc? I ask both for my own edification, and for the purpose of testing the new version of mergemaster. I generally upgrade /etc/ before I make world (after backing up of course) so I'm guessing I want to do it between #2 and #3, and again between #6 and #7. TIA, Doug -- *** Chief Operations Officer, DALnet IRC network *** Nominated for quote of the year is the statement made by Representative Dick Armey (Texas), who when asked if he were in the President's place, would he resign, responded: "If I were in the President's place I would not get a chance to resign. I would be lying in a pool of my own blood hearing Mrs. Armey standing over me saying, 'How do I reload this damn thing?'" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 23:54: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from pez.hyperreal.org (pez.hyperreal.org [207.181.224.6]) by hub.freebsd.org (Postfix) with SMTP id 4545814DE5 for ; Wed, 5 May 1999 23:53:58 -0700 (PDT) (envelope-from brian@hyperreal.org) Received: (qmail 26393 invoked by uid 4000); 6 May 1999 06:55:39 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 May 1999 06:55:39 -0000 Date: Wed, 5 May 1999 23:55:39 -0700 (PDT) From: Brian Behlendorf To: current@freebsd.org Subject: problem bootstrapping egcs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm doing a make world for the first time since the egcs cutover (yeah yeah, keep the flames to yourselves) and I encountered a rough spot with the build of egcs. My understanding was that to bootstrap over the change I should first (before the make world) do: # cd /usr/src; make -DCLOBBER includes [worked fine] # cd /usr/src/gnu/usr.bin/cc; make clean; make obj [worked fine] # make ===> cc_tools ===> cc_int ===> cc_drv ===> cpp ===> cc1 ===> cc cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc/../cc_tools -o cc gcc.o /usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a /usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x284): undefined reference to `mkstemps' *** Error code 1 Stop. *** Error code 1 Stop. Hmm. Any ideas? Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 5 23:59:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt057n14.san.rr.com (dt051nc7.san.rr.com [204.210.32.199]) by hub.freebsd.org (Postfix) with ESMTP id A019114C01 for ; Wed, 5 May 1999 23:59:23 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt057n14.san.rr.com (8.8.8/8.8.8) with ESMTP id XAA27835 for ; Wed, 5 May 1999 23:59:22 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <37313DC9.FCAE4D71@gorean.org> Date: Wed, 05 May 1999 23:59:21 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: How stable is -current? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First off, let's assume that I'm aware of all the traditional caveats re -current being bleeding edge, read the lists, etc. and am willing to deal with that. Now let's assume that I am trying to convince the powers that be at work to use freebsd for an upcoming CGI server project. Here is a relatively precise quote from the boss, "I think what we're going to do is set up a box with dual 500's and put linux on it because says that their stuff runs best on linux, I think because of the disk access or something like that." So the most important things I need to know (in no particular order): 1. In general how stable is -current? I know it goes through periods of instability, but assuming that I'm following the lists and know when not to build, could I put a 4.x box up and not be embarrassed? 2. Our architecture is *highly* dependent on NFS. I know that the good work on NFS is happening in -current, which is why I'm considering it. How well does -current NFS mix with an almost all-Sun network? Any plans on MFC'ing the NFS fixes to -stable? 3. How good and how stable is SMP currently, and does -current offer any big advantages over -stable in SMP? 4. How about other "new" features, like soft updates and vinum? Any other words of advice would be greatly appreciated. My experience says that a linux box won't handle the load that we're going to put on it, so if I can come up with something that works and outshines linux I earn points for me, and the project at the same time. If on the other hand, it chokes, errr... that'd be bad. :) I have a scratch box at home that is completely blow-up-able, so putting in the time to make it work is not a problem, I just need to know where to start. TIA, Doug -- *** Chief Operations Officer, DALnet IRC network *** Nominated for quote of the year is the statement made by Representative Dick Armey (Texas), who when asked if he were in the President's place, would he resign, responded: "If I were in the President's place I would not get a chance to resign. I would be lying in a pool of my own blood hearing Mrs. Armey standing over me saying, 'How do I reload this damn thing?'" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 0: 5:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id DC1221509F for ; Thu, 6 May 1999 00:05:05 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA48658; Thu, 6 May 1999 09:05:01 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id JAA17323; Thu, 6 May 1999 09:04:59 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905060704.JAA17323@greenpeace.grondar.za> To: Studded Cc: freebsd-current@FreeBSD.ORG Subject: Re: Question on 2.2.8 -> -current upgrade procedure In-Reply-To: Your message of " Wed, 05 May 1999 23:46:40 MST." <37313AD0.F5EE0B1C@gorean.org> References: <37313AD0.F5EE0B1C@gorean.org> Date: Thu, 06 May 1999 09:04:58 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Studded wrote: > Now, the main question I have is, at what points do I want to upgrade > /etc? I ask both for my own edification, and for the purpose of testing > the new version of mergemaster. I generally upgrade /etc/ before I make > world (after backing up of course) so I'm guessing I want to do it > between #2 and #3, and again between #6 and #7. I generally do it after making a new kernel and before rebooting. I have had no problems doing it that way with the possible exception of changes to /etc/make.conf. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 0: 9:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 4390B1509F for ; Thu, 6 May 1999 00:09:07 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA22467; Thu, 6 May 1999 16:39:05 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA79994; Thu, 6 May 1999 16:39:04 +0930 (CST) Date: Thu, 6 May 1999 16:39:03 +0930 From: Greg Lehey To: Studded Cc: freebsd-current@FreeBSD.ORG Subject: Re: How stable is -current? Message-ID: <19990506163903.J40359@freebie.lemis.com> References: <37313DC9.FCAE4D71@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37313DC9.FCAE4D71@gorean.org>; from Doug Barton on Wed, May 05, 1999 at 11:59:21PM -0700 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 5 May 1999 at 23:59:21 -0700, Doug Barton wrote: > First off, let's assume that I'm aware of all the traditional caveats > re -current being bleeding edge, read the lists, etc. and am willing to > deal with that. Now let's assume that I am trying to convince the powers > that be at work to use freebsd for an upcoming CGI server project. Here > is a relatively precise quote from the boss, "I think what we're going > to do is set up a box with dual 500's and put linux on it because > says that their stuff > runs best on linux, I think because of the disk access or something like > that." > > So the most important things I need to know (in no particular order): > > 1. In general how stable is -current? Parts of it are excellent. > I know it goes through periods of instability, but assuming that I'm > following the lists and know when not to build, could I put a 4.x > box up and not be embarrassed? Yes, but that's a big assumption: "assuming everything went OK". How do you known in advance whether you're not going to find a bug which eats its way, termitelike, through your file systems, and one day you look at the machine and it just falls into a heap of dust on the floor. > 4. How about other "new" features, like soft updates and vinum? Vinum is available in -STABLE as well. It's the same code. I thought that soft updates were also pretty stable. > Any other words of advice would be greatly appreciated. My > experience says that a linux box won't handle the load that we're > going to put on it, so if I can come up with something that works > and outshines linux I earn points for me, and the project at the > same time. If on the other hand, it chokes, errr... that'd be > bad. :) I have a scratch box at home that is completely > blow-up-able, so putting in the time to make it work is not a > problem, I just need to know where to start. What I'm hearing here is that you want to go to -CURRENT because of NFS. That's almost a valid reason, but I'll let other ones fight it out. Or you've been scared off by Doug White badmouthing 3.1. Note that just about everything he mentioned relates to upgrading, not to the stability of the system itself. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 0:11:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 604131594E; Thu, 6 May 1999 00:11:22 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-16.iptelecom.net.ua [212.42.68.143]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA24951; Thu, 6 May 1999 10:11:55 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA23501; Thu, 6 May 1999 10:09:42 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37314034.49123C43@altavista.net> Date: Thu, 06 May 1999 10:09:41 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Cc: jkh@freebsd.org Subject: Sysinstall still broken Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of today -CURRENT (cvsup'ed several minutes ago) sysinstall still broken: sh-2.03# cd /usr/src/release/sysinstall/ sh-2.03# make depend cc -o rtermcap /usr/src/release/sysinstall/rtermcap.c -ltermcap rm -f keymap.tmp for map in be.iso br275.iso danish.iso finnish.iso fr.iso  german.iso hr.iso hu.iso2.101keys it.iso icelandic.iso jp.106  norwegian.iso pl_PL.ISO_8859-2 pt.iso ru.koi8-r si.iso  spanish.iso swedish.iso swissfrench.iso swissgerman.iso uk.iso  us.dvorak us.iso ; do  kbdcontrol -L $map |  sed -e '/^static accentmap_t/,$d' >> keymap.tmp ;  done echo "static struct keymapInfo keymapInfos[] = {" >> keymap.tmp for map in be.iso br275.iso danish.iso finnish.iso fr.iso  german.iso hr.iso hu.iso2.101keys it.iso icelandic.iso jp.106  norwegian.iso pl_PL.ISO_8859-2 pt.iso ru.koi8-r si.iso  spanish.iso swedish.iso swissfrench.iso swissgerman.iso uk.iso  us.dvorak us.iso ; do  echo -n ' { "'$map'", ' >> keymap.tmp ;  echo "&keymap_$map }," | tr '[-.]' '_' >> keymap.tmp ;  done ( echo " { 0 }"; echo "};" ; echo "" ) >> keymap.tmp mv keymap.tmp keymap.h rm -f makedevs.tmp echo '#include ' > makedevs.tmp ./rtermcap ansi |  file2c 'const char termcap_ansi[] = {' ',0};'  >> makedevs.tmp ./rtermcap cons25 |  file2c 'const char termcap_cons25[] = {' ',0};'  >> makedevs.tmp ./rtermcap cons25-m |  file2c 'const char termcap_cons25_m[] = {' ',0};'  >> makedevs.tmp ./rtermcap cons25r |  file2c 'const char termcap_cons25r[] = {' ',0};'  >> makedevs.tmp ./rtermcap cons25r-m |  file2c 'const char termcap_cons25r_m[] = {' ',0};'  >> makedevs.tmp ./rtermcap cons25l1 |  file2c 'const char termcap_cons25l1[] = {' ',0};'  >> makedevs.tmp ./rtermcap cons25l1-m |  file2c 'const char termcap_cons25l1_m[] = {' ',0};'  >> makedevs.tmp ./rtermcap vt100 |  file2c 'const char termcap_vt100[] = {' ',0};'  >> makedevs.tmp file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp mv makedevs.tmp makedevs.c rm -f .depend mkdep -f .depend -a    -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys -DUC_PRIVATE -DKERN_NO_SYMBOLS  anonFTP.c cdrom.c command.c config.c devices.c kget.c disks.c dispatch.c dist.c dmenu.c doc.c dos.c floppy.c ftp.c globals.c index.c install.c installUpgrade.c keymap.c label.c lndir.c main.c makedevs.c media.c menus.c misc.c mouse.c msg.c network.c nfs.c options.c package.c system.c tape.c tcpip.c termcap.c ufs.c user.c variable.c wizard.c kget.c:31: isa/isa_device.h: No such file or directory kget.c:32: isa/pnp.h: No such file or directory mkdep: compile failed *** Error code 1   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 1:12: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 16896158BF for ; Thu, 6 May 1999 01:12:01 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id BAA25681; Thu, 6 May 1999 01:11:42 -0700 (PDT) (envelope-from obrien) Message-ID: <19990506011142.A25660@nuxi.com> Date: Thu, 6 May 1999 01:11:42 -0700 From: "David O'Brien" To: Brian Behlendorf , current@FreeBSD.ORG Subject: Re: problem bootstrapping egcs Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brian Behlendorf on Wed, May 05, 1999 at 11:55:39PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the build of egcs. My understanding was that to bootstrap over the change > I should first (before the make world) do: VERY wrong. All you want to do is a normal ``make world'' (or ``make buildworld'') > # cd /usr/src/gnu/usr.bin/cc; make clean; make obj > # make ... > ===> cc ... > /usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-temp.o): > In function `make_temp_file': > choose-temp.o(.text+0x284): undefined reference to `mkstemps' > *** Error code 1 There are bootstraping issues that are dealt with in ``make world'' that you are not handling in your manually doing it. In this case egcs depends on new libc functionality and you haven't manually built a new libc first. Of course ``make world'' builds the important librarires 1st and then uses those when compiling the commands and other binaries. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 1:55:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id EF15915887 for ; Thu, 6 May 1999 01:55:43 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id JAA28669; Thu, 6 May 1999 09:55:38 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00779; Thu, 6 May 1999 08:09:14 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905060709.IAA00779@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Holling Cc: current@FreeBSD.ORG Subject: Re: RTP and RTSP support in libalias? In-reply-to: Your message of "Wed, 05 May 1999 22:10:11 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 May 1999 08:09:14 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apple's QuickTime 4 uses these protocols for streaming QuickTime, and I've > got users asking me if the FreeBSD NAT box can be made to handle it. > Looks like these protocols are new internet standards, has anyone > integrated them into libalias yet? If not I might give it a shot, but I'm > probably in over my head... Charles Mott is the person to talk to about libalias changes. > - Mike > > PS. Apple provides links to the RFCs: > > http://www.apple.com/quicktime/resources/qt4/us/proxy/proxy.html -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 2:14:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B38E6158AD for ; Thu, 6 May 1999 02:14:56 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA56229; Thu, 6 May 1999 02:15:16 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Studded Cc: freebsd-current@FreeBSD.ORG Subject: Re: How stable is -current? In-reply-to: Your message of "Wed, 05 May 1999 23:59:21 PDT." <37313DC9.FCAE4D71@gorean.org> Date: Thu, 06 May 1999 02:15:16 -0700 Message-ID: <56224.925982116@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. In general how stable is -current? I know it goes through periods of > instability, but assuming that I'm following the lists and know when not > to build, could I put a 4.x box up and not be embarrassed? I run my own machine off -current, have been doing so for months now, and it's hardly an idle machine given the number of release builds and other crap I run on it. It's been a less painful -current than many a -current I could think of in the past, that's for sure. :) > 2. Our architecture is *highly* dependent on NFS. I know that the good > work on NFS is happening in -current, which is why I'm considering it. > How well does -current NFS mix with an almost all-Sun network? Any > plans on MFC'ing the NFS fixes to -stable? Matt's submitted some patches for this which I've asked the core team to review. Anyone else looking for -stable relative NFS patches to test should send Matt Dillon or I some email and we'll provide you with the diffs if you'll provide us with the testing. :) > 3. How good and how stable is SMP currently, and does -current offer any > big advantages over -stable in SMP? I think SMP is pretty good in either branch, though Luoqi and Alan have been working to improve it in -current lately. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 2:17:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6696315982; Thu, 6 May 1999 02:17:21 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA56592; Thu, 6 May 1999 02:17:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: sobomax@altavista.net Cc: current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Sysinstall still broken In-reply-to: Your message of "Thu, 06 May 1999 10:09:41 +0300." <37314034.49123C43@altavista.net> Date: Thu, 06 May 1999 02:17:34 -0700 Message-ID: <56588.925982254@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As of today -CURRENT (cvsup'ed several minutes ago) sysinstall still > broken: Current as of 10 minutes ago: cc -O -pipe -mpentium -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys -I/usr/src/release/sysinstall/../../sys/i386 -DUC_PRIVATE -DKERN_NO_SYMBOLS -c kget.c kget.c: In function `kget': kget.c:42: warning: `fout' might be used uninitialized in this function cc -O -pipe -mpentium -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys -I/usr/src/release/sysinstall/../../sys/i386 -DUC_PRIVATE -DKERN_NO_SYMBOLS -c disks.c .. I don't see the problem? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 2:35:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id A50B215954; Thu, 6 May 1999 02:34:57 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-46.iptelecom.net.ua [212.42.68.237]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id MAA07339; Thu, 6 May 1999 12:35:27 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id MAA24033; Thu, 6 May 1999 12:34:44 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37316232.C92A520D@altavista.net> Date: Thu, 06 May 1999 12:34:43 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Sysinstall still broken References: <56588.925982254@zippy.cdrom.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > As of today -CURRENT (cvsup'ed several minutes ago) sysinstall still > > broken: > > Current as of 10 minutes ago: > > cc -O -pipe -mpentium -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys -I/usr/src/release/sysinstall/../../sys/i386 -DUC_PRIVATE -DKERN_NO_SYMBOLS   -c kget.c > kget.c: In function `kget': > kget.c:42: warning: `fout' might be used uninitialized in this function > cc -O -pipe -mpentium -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys -I/usr/src/release/sysinstall/../../sys/i386 -DUC_PRIVATE -DKERN_NO_SYMBOLS   -c disks.c > .. Instead of #include should be #include and pnp.h also Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 4:55:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id C758C159DC for ; Thu, 6 May 1999 04:55:22 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id HAA14905 for ; Thu, 6 May 1999 07:55:21 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA17800; Thu, 6 May 1999 07:54:51 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id HAA29705 for freebsd-current@freebsd.org; Thu, 6 May 1999 07:54:51 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905061154.HAA29705@bb01f39.unx.sas.com> Subject: make release failure (mkdep & kget.c) To: freebsd-current@freebsd.org Date: Thu, 6 May 1999 07:54:51 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I don't know if anyone else has seen this yet. I'm current as of 5 1/2 hours ago... (2am EST, 11pm PST). Thanks! John file2c 'u_char boot0[] =3D {' '};' < /boot/boot0 >> makedevs.tmp mv makedevs.tmp makedevs.c rm -f .depend mkdep -f .depend -a -I/usr/src/release/sysinstall/../../gnu/lib/libdialo= g -I/usr/obj/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../..= /sys -DUC_PRIVATE -DKERN_NO_SYMBOLS /usr/src/release/sysinstall/anonFTP.c = /usr/src/release/sysinstall/c= drom.c /usr/src/release/sysinstall/command.c /usr/src/release/sysinstall/co= nfig.c /usr/src/release/sysinstall/devices.c /usr/src/release/sysinstall/kg= et.c /usr/src/release/sysinstall/disks.c /usr/src/release/sysinstall/dispat= ch.c /usr/src/release/sysinst= all/dist.c /usr/src/release/sysinstall/dmenu.c /usr/src/release/sysinstall/= doc.c /usr/src/release/sysinstall/dos.c /usr/src/release/sysinstall/floppy.= c /usr/src/release/sysinstall/ftp.c /usr/src/release/sysinstall/globals.c /= usr/src/release/sysinstall/in= dex.c /usr/src/release/sysinstall/install.c /usr/src/release/sysinstall/ins= tallUpgrade.c /usr/src/release/sysinstall/keymap.c /usr/src/release/sysinst= all/label.c /usr/src/release/sysinstall/lndir.c /usr/src/release/sysinstall= /main.c makedevs.c /usr/src/r= elease/sysinstall/media.c /usr/src/release/sysinstall/menus.c /usr/src/rele= ase/sysinstall/misc.c /usr/src/release/sysinstall/mouse.c /usr/src/release/= sysinstall/msg.c /usr/src/release/sysinstall/network.c /usr/src/release/sys= install/nfs.c /usr/src/releas= e/sysinstall/options.c /usr/src/release/sysinstall/package.c /usr/src/relea= se/sysinstall/system.c /usr/src/release/sysinstall/tape.c /usr/src/release/= sysinstall/tcpip.c /usr/src/release/sysinstall/termcap.c /usr/src/release/s= ysinstall/ufs.c /usr/src/rele= ase/sysinstall/user.c /usr/src/release/sysinstall/variable.c /usr/src/relea= se/sysinstall/wizard.c /usr/src/release/sysinstall/kget.c:31: isa/isa_device.h: No such file or di= rectory /usr/src/release/sysinstall/kget.c:32: isa/pnp.h: No such file or directory mkdep: compile failed *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 5: 2:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 326771599D for ; Thu, 6 May 1999 05:02:13 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id FAA79781; Thu, 6 May 1999 05:02:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: make release failure (mkdep & kget.c) In-reply-to: Your message of "Thu, 06 May 1999 07:54:51 EDT." <199905061154.HAA29705@bb01f39.unx.sas.com> Date: Thu, 06 May 1999 05:02:23 -0700 Message-ID: <79773.925992143@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know if anyone else has seen this yet. I'm current as of > 5 1/2 hours ago... (2am EST, 11pm PST). I had a non-standard Makefile, my bad. Fixed an hour or so ago. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 7: 6:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 30781159E4 for ; Thu, 6 May 1999 07:06:36 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA27924; Thu, 6 May 1999 23:05:59 +0900 (JST) Message-ID: <37316B48.6140F3FE@newsguy.com> Date: Thu, 06 May 1999 19:13:28 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Studded , freebsd-current@FreeBSD.ORG Subject: Re: How stable is -current? References: <56224.925982116@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > 3. How good and how stable is SMP currently, and does -current offer any > > big advantages over -stable in SMP? > > I think SMP is pretty good in either branch, though Luoqi and Alan > have been working to improve it in -current lately. 5% gain on worldstone for a recent commit. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness if that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 7:28:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 09E5414F8B; Thu, 6 May 1999 07:28:40 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS3-p84.hfa.netvision.net.il [62.0.146.84]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id RAA18113; Thu, 6 May 1999 17:28:37 +0300 (IDT) From: Tomer Weller To: FreeBSD Current , FreeBSD Ports Date: Thu, 6 May 1999 17:09:28 +0300 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99050617135200.58638@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit Subject: X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG whenever i try to compile KDE software (ports also) i get this error, though packages install fine. i installed KDE from packages, i suspect that's the problem. this is from the kmp3 port, but happens with every piece of kde software : checking for KDE... libraries /usr/local/lib, headers /usr/local/include checking for extra includes... no checking for extra libs... no checking for kde headers installed... yes checking for kde libraries installed... configure: error: your system fails at linking a small KDE application! Check, if your compiler is installed correctly and if you have used the same compiler to compile qt and kdelibs as you did use now *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ====================================== Tomer Weller spud@i.am wellers@netvision.net.il "Drugs are good, and if you do'em pepole think that you're cool", NoFX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 7:36: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 1560714D67; Thu, 6 May 1999 07:35:59 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id JAA13121; Thu, 6 May 1999 09:35:59 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id JAA13115; Thu, 6 May 1999 09:35:53 -0500 (CDT) Message-ID: <009301be97cd$c1747fc0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Tomer Weller" , "FreeBSD Current" , "FreeBSD Ports" Subject: Re: Date: Thu, 6 May 1999 09:35:51 -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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had this problem on a Linux box a little while back. It also used egcs-1.1.2. I suspect there is a problem with the compiler or the configure script of the kde tarball. Tom Veldhouse veldy@visi.com -----Original Message----- From: Tomer Weller To: FreeBSD Current ; FreeBSD Ports Date: Thursday, May 06, 1999 9:31 AM > >whenever i try to compile KDE software (ports also) i get this error, though >packages install fine. >i installed KDE from packages, i suspect that's the problem. > >this is from the kmp3 port, but happens with every piece of kde software : > > >checking for KDE... libraries /usr/local/lib, headers /usr/local/include >checking for extra includes... no >checking for extra libs... no >checking for kde headers installed... yes >checking for kde libraries installed... configure: error: your system fails at linking a small KDE application! >Check, if your compiler is installed correctly and if you have used the >same compiler to compile qt and kdelibs as you did use now >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. > > > >====================================== > Tomer Weller > spud@i.am > wellers@netvision.net.il > "Drugs are good, and if you do'em > pepole think that you're cool", NoFX > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 7:56:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 109EC157FB for ; Thu, 6 May 1999 07:56:19 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id QAA14769 for ; Thu, 6 May 1999 16:56:18 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma014767; Thu, 6 May 99 16:56:18 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id QAA04037 for ; Thu, 6 May 1999 16:56:01 +0200 (MET DST) Received: (qmail 94094 invoked by uid 666); 6 May 1999 14:56:21 -0000 Date: Thu, 6 May 1999 16:56:21 +0200 From: Jos Backus To: FreeBSD Current Subject: Re: Building the kmp3 port Message-ID: <19990506165621.C91167@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <009301be97cd$c1747fc0$236319ac@w142844.carlson.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <009301be97cd$c1747fc0$236319ac@w142844.carlson.com>; from Thomas T. Veldhouse on Thu, May 06, 1999 at 09:35:51AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 06, 1999 at 09:35:51AM -0500, Thomas T. Veldhouse wrote: > >checking for kde libraries installed... configure: error: your system fails > at linking a small KDE application! > >Check, if your compiler is installed correctly and if you have used the > >same compiler to compile qt and kdelibs as you did use now > >*** Error code 1 This smells like the /usr/lib/libstdc++.so.{2,3} issue. You may want to look at the tail of config.log to check; libqt.so possibly needs to be rebuilt. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 8:14:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id A34D71538F for ; Thu, 6 May 1999 08:14:46 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id LAA10523; Thu, 6 May 1999 11:14:38 -0400 (EDT) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id LAA26721; Thu, 6 May 1999 11:14:34 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <56224.925982116@zippy.cdrom.com> Date: Thu, 06 May 1999 11:14:39 -0400 (EDT) From: John Baldwin To: "Jordan K. Hubbard" Subject: Re: How stable is -current? Cc: freebsd-current@FreeBSD.ORG, Studded Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-May-99 Jordan K. Hubbard wrote: >> 2. Our architecture is *highly* dependent on NFS. I know that the good >> work on NFS is happening in -current, which is why I'm considering it. >> How well does -current NFS mix with an almost all-Sun network? Any >> plans on MFC'ing the NFS fixes to -stable? > > Matt's submitted some patches for this which I've asked the core team > to review. Anyone else looking for -stable relative NFS patches to > test should send Matt Dillon or I some email and we'll provide you with > the diffs if you'll provide us with the testing. :) I'll gladly test them. I'm in the process of upgrading the lab I run to 3.1 and it depends heavily on NFS. Since the lab is closed during finals I won't be losing massive amounts of data if they go wrong. Send 'em on. :) NFS is a big deal to a lot of us, and we'd like to see the changes MFC'd to -stable if possible. >> 3. How good and how stable is SMP currently, and does -current offer any >> big advantages over -stable in SMP? > > I think SMP is pretty good in either branch, though Luoqi and Alan > have been working to improve it in -current lately. Do you know if they have test patches for -stable as well? Thanks. > - Jordan --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 8:32: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from pez.hyperreal.org (pez.hyperreal.org [207.181.224.6]) by hub.freebsd.org (Postfix) with SMTP id 1215B1512C for ; Thu, 6 May 1999 08:32:03 -0700 (PDT) (envelope-from brian@hyperreal.org) Received: (qmail 47116 invoked by uid 4000); 6 May 1999 15:33:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 May 1999 15:33:43 -0000 Date: Thu, 6 May 1999 08:33:43 -0700 (PDT) From: Brian Behlendorf To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: problem bootstrapping egcs In-Reply-To: <19990506011142.A25660@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 May 1999, David O'Brien wrote: > > the build of egcs. My understanding was that to bootstrap over the change > > I should first (before the make world) do: > > VERY wrong. All you want to do is a normal ``make world'' (or ``make > buildworld'') Hup, you're right, sorry about the false alarm. It all builds great. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 8:36:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt057n14.san.rr.com (dt051nc7.san.rr.com [204.210.32.199]) by hub.freebsd.org (Postfix) with ESMTP id 809611512C for ; Thu, 6 May 1999 08:36:42 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt057n14.san.rr.com (8.8.8/8.8.8) with ESMTP id IAA02986; Thu, 6 May 1999 08:36:25 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <3731B6F8.19C2074B@gorean.org> Date: Thu, 06 May 1999 08:36:24 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: freebsd-current@FreeBSD.ORG Subject: Re: How stable is -current? References: <37313DC9.FCAE4D71@gorean.org> <19990506163903.J40359@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > I know it goes through periods of instability, but assuming that I'm > > following the lists and know when not to build, could I put a 4.x > > box up and not be embarrassed? > > Yes, but that's a big assumption: "assuming everything went OK". How > do you known in advance whether you're not going to find a bug which > eats its way, termitelike, through your file systems, and one day you > look at the machine and it just falls into a heap of dust on the > floor. *Chuckle* Great visual. Of course, "odd" surprises are not completely unexpected in any freebsd branch, and of course I do plan to take appropriate measures to protect our customer's stuff. The system I'm planning to design will require read-only access from the CGI box to the rest of the world, and almost everything on the box itself will be redundant data anyway. This will be true regardless of what platform we use, so I think this is a unique opportunity to test -current in a relatively pain-free, high load environment. At the same time, I would prefer that it's not crashing regularly because it's my potatoes in the sling, so to speak if I convince them to use freebsd. > > 4. How about other "new" features, like soft updates and vinum? > > Vinum is available in -STABLE as well. It's the same code. I thought > that soft updates were also pretty stable. Ok, thanks for the info on vinum. If I'm going to make this work I need to show disk access as good or better than linux, so I'm looking for every edge. > What I'm hearing here is that you want to go to -CURRENT because of > NFS. Yes, exactly. The other factors you mentioned aren't significant to me, I'm quite familiar with traditional freebsd development cycle instability. :) INRE Jordan's comments about moving the -current NFS improvements to -stable, obviously I'd rather run -stable in a production environment, so assuming we can get a patchset together I could do some testing of that at home since I have two boxes now. My understanding from what I've read was that the changes depended on some architectural improvements in -current that couldn't (easily) be ported back, but I'm still way behind on mail, so I am probably not all up to date on that. However I can't emphasize strongly enough how much our system depends on NFS. Whether that's a good thing or not isn't for me to decide, I just work there. :) I must say though, working in an all-Sun environment it's easy to get used to how easy NFS makes things. I'm starting to feel the same way about samba since I set it up on my home network. Thanks very much to everyone for the responses, they were very helpful. If anyone else has comments or suggestions I welcome them of course. Doug -- *** Chief Operations Officer, DALnet IRC network *** Nominated for quote of the year is the statement made by Representative Dick Armey (Texas), who when asked if he were in the President's place, would he resign, responded: "If I were in the President's place I would not get a chance to resign. I would be lying in a pool of my own blood hearing Mrs. Armey standing over me saying, 'How do I reload this damn thing?'" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 8:51:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mgate03.so-net.ne.jp (mgate03.so-net.ne.jp [210.132.247.33]) by hub.freebsd.org (Postfix) with ESMTP id EE24314F8D for ; Thu, 6 May 1999 08:50:45 -0700 (PDT) (envelope-from sanewo@ba2.so-net.ne.jp) Received: from mail.ba2.so-net.ne.jp (mail.ba2.so-net.ne.jp [210.132.247.97]) by mgate03.so-net.ne.jp (8.8.8+3.0Wbeta9/3.6W99042816) with ESMTP id AAA09303 for ; Fri, 7 May 1999 00:50:30 +0900 (JST) Received: from ba2.so-net.ne.jp (sanewo@p84b573.sng2.ap.so-net.ne.jp [210.132.181.115]) by mail.ba2.so-net.ne.jp (8.8.8+3.0Wbeta9/3.7W99040113) with ESMTP id AAA19548 for ; Fri, 7 May 1999 00:50:29 +0900 (JST) Received: (from sanewo@localhost) by ba2.so-net.ne.jp (8.9.3/8.9.3) id AAA10006; Fri, 7 May 1999 00:50:28 +0900 (JST) (envelope-from sanewo) To: current@FreeBSD.ORG Subject: Re: sys/modules/procfs/Makefile buglet References: <19990504212907.A12665@hal.mpn.cp.philips.com> From: Takanori Saneto In-Reply-To: <19990504212907.A12665@hal.mpn.cp.philips.com> (Jos Backus's message of "Tue, 4 May 1999 21:29:07 +0200") MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=ISO-2022-JP Date: 07 May 1999 00:50:27 +0900 Message-ID: <87hfpqfb98.fsf@ba2.so-net.ne.jp> Lines: 13 User-Agent: Semi-gnus/6.10.11 SEMI/1.13.4 (Terai) FLIM/1.12.6 (=?ISO-8859-4?Q?Family-K=F2enmae?=) Emacs/20.3.92 (i686-pc-freebsd3.0) MULE/4.0 (HANANOEN) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Besides procfs_rlimit(), there are several undefined symbols in procfs.ko: % nm /modules/procfs.ko | egrep ' U procfs_' U procfs_read_fpregs U procfs_read_regs U procfs_sstep U procfs_write_fpregs U procfs_write_regs Is this OK? -- $B$5$M$r(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 9:19:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mgate03.so-net.ne.jp (mgate03.so-net.ne.jp [210.132.247.33]) by hub.freebsd.org (Postfix) with ESMTP id DE627159B2 for ; Thu, 6 May 1999 09:19:28 -0700 (PDT) (envelope-from sanewo@ba2.so-net.ne.jp) Received: from mail.ba2.so-net.ne.jp (mail.ba2.so-net.ne.jp [210.132.247.97]) by mgate03.so-net.ne.jp (8.8.8+3.0Wbeta9/3.6W99042816) with ESMTP id BAA00469 for ; Fri, 7 May 1999 01:19:27 +0900 (JST) Received: from ba2.so-net.ne.jp (sanewo@p84b573.sng2.ap.so-net.ne.jp [210.132.181.115]) by mail.ba2.so-net.ne.jp (8.8.8+3.0Wbeta9/3.7W99040113) with ESMTP id BAA28857 for ; Fri, 7 May 1999 01:19:26 +0900 (JST) Message-Id: <199905061619.BAA28857@mail.ba2.so-net.ne.jp> To: current@FreeBSD.ORG Subject: Re: sys/modules/procfs/Makefile buglet In-reply-to: sanewo's message of 07 May 1999 00:50:27 +0900. <87hfpqfb98.fsf@ba2.so-net.ne.jp> User-Agent: EMH/1.10.0 SEMI/1.13.4 (Terai) FLIM/1.12.6 (=?ISO-8859-4?Q?Fam?= =?ISO-8859-4?Q?ily-K=F2enmae?=) Emacs/20.3.92 (i686-pc-freebsd3.0) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=ISO-2022-JP Date: Fri, 07 May 1999 01:19:25 +0900 From: SANETO Takanori Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, those symbols are in /kernel, of course. Sorry for bothering you with my noisy message. In article <87hfpqfb98.fsf@ba2.so-net.ne.jp> Takanori Saneto said: >% nm /modules/procfs.ko | egrep ' U procfs_' > U procfs_read_fpregs > U procfs_read_regs > U procfs_sstep > U procfs_write_fpregs > U procfs_write_regs -- $B$5$M$r(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 10:34:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 0CC7C1515E for ; Thu, 6 May 1999 10:34:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA37651; Thu, 6 May 1999 10:34:12 -0700 (PDT) (envelope-from dillon) Date: Thu, 6 May 1999 10:34:12 -0700 (PDT) From: Matthew Dillon Message-Id: <199905061734.KAA37651@apollo.backplane.com> To: John Baldwin Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG, Studded Subject: Re: How stable is -current? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'll gladly test them. I'm in the process of upgrading the lab I run to 3.1 :and it depends heavily on NFS. Since the lab is closed during finals I won't :be losing massive amounts of data if they go wrong. Send 'em on. :) NFS is a :big deal to a lot of us, and we'd like to see the changes MFC'd to -stable if :possible. The only major bugfixes that have not been backported from -current to -stable in regards to NFS are the NFS/TCP fix, which is being backported now, and a number of fixes to the VM system when dealing with mmap(), which cannot be backported until we backport the entire -current VM system. Also, NFS-stable will break if directories are VMIO'd due to breakage in the reconstitution of the valid range ( but directories are not VMIO'd in either -stable or -current yet so this will not effect us yet ). The mmap() breakage is unavoidable in -stable but hopefully will not cause serious problems for people. The breakage is related to garbarge showing up in the mmap()'d pages *after* the logical file EOF. That is, if you have a 500 byte file and mmap() it into a 4K page, data occuring after offset 500 may or may not be 0. There are still various other bugs relating to deadlock situations that haven't been fixed in either release that are still being tracked down. Fewer then in prior releases, but still present. :Do you know if they have test patches for -stable as well? Thanks. I would wait until we get the NFS/TCP fix committed to -stable. It should be committed very soon now. :John Baldwin -- http://members.freedomnet.com/~jbaldwin/ -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 10:47:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 3607614D67 for ; Thu, 6 May 1999 10:47:14 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA10605; Thu, 6 May 1999 10:47:12 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 6 May 1999 10:47:11 -0700 (PDT) From: Doug White To: Mike Holling Cc: current@FreeBSD.ORG Subject: Re: RTP and RTSP support in libalias? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 May 1999, Mike Holling wrote: > Apple's QuickTime 4 uses these protocols for streaming QuickTime, and I've > got users asking me if the FreeBSD NAT box can be made to handle it. > Looks like these protocols are new internet standards, has anyone > integrated them into libalias yet? If not I might give it a shot, but I'm > probably in over my head... QT4S supports Socks5, btw. I just dropped a socks server on my gateway, pointed QT4 at it, and all is peachy. Kudos to Apple for looking ahead :) From what I can tell, this runs much like PPTP does. You have a TCP control connection, but the data comes through UDP (PPTP uses GRE). You'd have to dive into the TCP packets to figure out what ports the UDP data was coming back on in order to establish the mapping. And you may have to hack the TCP data so the client doesn't try to tell the server its (invalid) IP address. (The stupid LiveUpdate programs do this and it's a pain.) The current natd PPTP support forces the data to be mapped to/from a static IP. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 11: 7:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt057n14.san.rr.com (dt051nc7.san.rr.com [204.210.32.199]) by hub.freebsd.org (Postfix) with ESMTP id AA65814DDC for ; Thu, 6 May 1999 11:07:37 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt057n14.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA03686; Thu, 6 May 1999 11:06:58 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <3731DA42.302CE829@gorean.org> Date: Thu, 06 May 1999 11:06:58 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: How stable is -current? References: <199905061734.KAA37651@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > The only major bugfixes that have not been backported from -current to > -stable in regards to NFS are the NFS/TCP fix, which is being backported > now, and a number of fixes to the VM system when dealing with mmap(), > which cannot be backported until we backport the entire -current VM system. Ok, that's good news. I'd like to stick with -stable if I can. No pressure, but do you have an ETA on the VM backport? I'm assuming that something like that is "down the road," probably after 3.2? > The mmap() breakage is unavoidable in -stable but hopefully will not cause > serious problems for people. The breakage is related to garbarge showing > up in the mmap()'d pages *after* the logical file EOF. That is, if you > have a 500 byte file and mmap() it into a 4K page, data occuring after > offset 500 may or may not be 0. Hrrrmm... ok. So what could happen due to this bug, and how would I spot it? Meanwhile I'll keep an eye on the commits for that NFS backport. Thanks muchly for the update. :) Doug -- *** Chief Operations Officer, DALnet IRC network *** Nominated for quote of the year is the statement made by Representative Dick Armey (Texas), who when asked if he were in the President's place, would he resign, responded: "If I were in the President's place I would not get a chance to resign. I would be lying in a pool of my own blood hearing Mrs. Armey standing over me saying, 'How do I reload this damn thing?'" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 11:12:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 96C7715A79 for ; Thu, 6 May 1999 11:12:27 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA37958; Thu, 6 May 1999 11:12:23 -0700 (PDT) (envelope-from dillon) Date: Thu, 6 May 1999 11:12:23 -0700 (PDT) From: Matthew Dillon Message-Id: <199905061812.LAA37958@apollo.backplane.com> To: Studded Cc: freebsd-current@FreeBSD.ORG Subject: Re: How stable is -current? References: <199905061734.KAA37651@apollo.backplane.com> <3731DA42.302CE829@gorean.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Ok, that's good news. I'd like to stick with -stable if I can. No :pressure, but do you have an ETA on the VM backport? I'm assuming that :something like that is "down the road," probably after 3.2? There's no ETA at the moment. I'm hoping that modifications to -current's VM system will settle down in the next couple of months and then we'll see. : Hrrrmm... ok. So what could happen due to this bug, and how would I :spot it? Meanwhile I'll keep an eye on the commits for that NFS :backport. Thanks muchly for the update. :) : :Doug Programs which expect the space in the mmap after the logical file EOF to be filled with zero will break. Very few programs make this assumption, because space in an mmap after the logical EOF is supposed to generate a segfault if accessed ( but, obviously, cannot for space past the EOF in the 'last page' that contains the last fragment of file data ). It is more a security issue then anything else. For example, if you are mapping a file fragment you may wind up being able to access (read only) fragmentary data from other files that you would normally not have access to. -Matt Matthew Dillon :-- :*** Chief Operations Officer, DALnet IRC network *** : :Nominated for quote of the year is the statement made by Representative :Dick Armey (Texas), who when asked if he were in the President's place, :would he resign, responded: : :"If I were in the President's place I would not get a chance to resign. :I would be lying in a pool of my own blood hearing Mrs. Armey standing :over me saying, 'How do I reload this damn thing?'" : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 11:25:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (Postfix) with ESMTP id AE81B14DDC for ; Thu, 6 May 1999 11:25:48 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from fermion (crb@fermion.ChrisBowman.com [10.0.1.2]) by quark.ChrisBowman.com (8.9.2/8.8.8) with SMTP id OAA07183; Thu, 6 May 1999 14:25:02 -0400 (EDT) (envelope-from crb@ChrisBowman.com) Message-Id: <199905061825.OAA07183@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Thu, 06 May 1999 14:24:01 -0400 To: Matthew Dillon From: "Christopher R. Bowman" Subject: Re: How stable is -current? Cc: John Baldwin , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG, Studded In-Reply-To: <199905061734.KAA37651@apollo.backplane.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:34 AM 5/6/99 -0700, Matthew Dillon wrote: >:I'll gladly test them. I'm in the process of upgrading the lab I run to 3.1 >:and it depends heavily on NFS. Since the lab is closed during finals I won't >:be losing massive amounts of data if they go wrong. Send 'em on. :) NFS is a >:big deal to a lot of us, and we'd like to see the changes MFC'd to -stable if >:possible. > > The only major bugfixes that have not been backported from -current to > -stable in regards to NFS are the NFS/TCP fix, which is being backported > now, and a number of fixes to the VM system when dealing with mmap(), > which cannot be backported until we backport the entire -current VM system. > Also, NFS-stable will break if directories are VMIO'd due to breakage > in the reconstitution of the valid range ( but directories are not VMIO'd > in either -stable or -current yet so this will not effect us yet ). > > The mmap() breakage is unavoidable in -stable but hopefully will not cause > serious problems for people. The breakage is related to garbarge showing > up in the mmap()'d pages *after* the logical file EOF. That is, if you > have a 500 byte file and mmap() it into a 4K page, data occuring after > offset 500 may or may not be 0. This sounds like the page is not being zeroed before being reassigned for other uses. Does this present a possible security problem? Might I get a page from a terminated process that wasn't zeroed? Say perhaps a page from a vipw process or something similar? If so, this really should be addressed at least in so far as to prevent any possible exploitation (ie putting out software with bugs is one thing, but putting out software with security holes is just bad, not that we are doing this, that's what I am asking) -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 12:28:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 7E17014C42; Thu, 6 May 1999 12:28:12 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-178.skylink.it [194.185.55.178]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id VAA28218; Thu, 6 May 1999 21:29:16 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id VAA00572; Thu, 6 May 1999 21:27:55 +0200 (CEST) Date: Thu, 6 May 1999 21:27:55 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Jamie Bowden Cc: FreeBSD current Mailing list , FreeBSD hackers mailing list , USB BSD list Subject: info on USB, URL's and Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you want some information on USB: FreeBSD USB homepage: http://www.etla.net/~n_hibma/usb/usb.pl USB homepage: http://www.usb.org Mailing list: usb-bsd@egroups.com subscribe: http://www.egroups.com Specs on chips: http://www.intel.com/ (UHCI) http://www.via.com.tw/ (UHCI) http://www.opti.com.tw/ (OHCI) (and other chipset manufacturers I can't remember the name of) UDI (info on USBDI you can find on USB homepage, I think): http://www.sco.com/UDI A reasonable list of devices for USB: http://www.usbstuff.com/ URL's on devices that have supported/will be supported soon: http://www.cherry.com/ 3504 keyboard http://www.yedata.co.jp/ Flashbuster-U (soon) http://www.3com.com/ ISDN-TA (not available yet, I have Sample 73 :-) (soon) 56K0 Voice Faxmodem Pro, aka 5605 (soon) (the above companies: thanks for sending me samples!) http://www.iomega.com/ USB Zip drive Linux: http://peloncho.fis.ucm.es/~inaky/USB.html If you just want to talk lots about USB related things and what one _could_ do :-): linux-usb@peloncho.fis.ucm.es subscribe: majordomo@peloncho.fis.ucm.es Hope this is of any use to anyone. Nick FreeBSD USB project. n_hibma@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 13:21: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B45D1517B; Thu, 6 May 1999 13:20:55 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id OAA46687; Thu, 6 May 1999 14:20:54 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905062020.OAA46687@panzer.plutotech.com> Subject: HEADS UP: CAM changes To: current@FreeBSD.ORG Date: Thu, 6 May 1999 14:20:54 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just committed a number of CAM changes that will require recompilation of any userland programs you have that access the CAM passthrough driver. So things like cdrecord, xmcd, etc., should be recompiled. The best way to update your system is via make world. NOTE: I would really like to hear from NCR owners about these changes. Justin and I made a small negotiation change in the NCR driver that should mean that people with 875's and the like should get Ultra speeds without putting options in their kernel. To summarize, these changes: - add new 'tags' and 'negotiate' commands to camcontrol. The tags command allows setting and viewing the number of tagged openings, and the negotiate command allows viewing and setting negotiation parameters for devices. - add code to make the transport layer's sink devices invisible to camcontrol devlist by default. (they reappear with -v) - The CD and DA drivers now attach regardless of what errors they get back from a read capacity. (with one exception -- "logical unit not supported") - Fixed a negotiation bug in the NCR driver. Note that the ahc, adv, and ncr drivers are the only drivers that fully support the 'camcontrol negotiate' command at this point. Other drivers, like the adw driver, may let you turn sync negotiation on and off but won't let you set the sync rate. In the case of the adw boards, I think it's a hardware limitation. Other drivers, like the bt driver, don't support the XPT_SET_TRAN_SETTINGS CCB at all, so you can't set any negotiation parameters. The 'tags' command should work on any device, because tagged queueing is handled by the transport layer, and not individual peripheral drivers. I plan on checking all of this code into -stable as well, hopefully later on today. Many thanks to Justin for helping with these changes and reviewing everything. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 15:13:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 02EEA14D93 for ; Thu, 6 May 1999 15:13:45 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id SAA21676 for ; Thu, 6 May 1999 18:13:43 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA22948; Thu, 6 May 1999 18:13:13 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id SAA41174 for freebsd-current@freebsd.org; Thu, 6 May 1999 18:13:13 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905062213.SAA41174@bb01f39.unx.sas.com> Subject: 4.0-19990506-SNAP install problem To: freebsd-current@freebsd.org Date: Thu, 6 May 1999 18:13:13 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When I attempt to install the 0506 snap, things work correctly until I get the following on the debug screen: DEBUG: MakeDev: Unknown major/minor for devtype 0s1b DEBUG: MakeDev: Unknown major/minor for devtype 0s1e DEBUG: MakeDev: Unknown major/minor for devtype 0s1a DEBUG: MakeDev: Unknown major/minor for devtype 0s1f DEBUG: MakeDev: Unknown major/minor for devtype 0s1g If anyone has any ideas about this please let me know. I'll start looking at this later this evenning/tomorrow... Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 15:16:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from axle.cs.ucla.edu (Axle.CS.UCLA.EDU [131.179.192.135]) by hub.freebsd.org (Postfix) with ESMTP id 5182E1523E for ; Thu, 6 May 1999 15:16:35 -0700 (PDT) (envelope-from scottm@axle.cs.ucla.edu) Received: from axle.cs.ucla.edu (localhost [127.0.0.1]) by axle.cs.ucla.edu (8.9.3/8.9.3) with ESMTP id PAA00552 for ; Thu, 6 May 1999 15:16:30 -0700 (PDT) (envelope-from scottm@axle.cs.ucla.edu) Message-Id: <199905062216.PAA00552@axle.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org Subject: Problems with -current gdb Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 May 1999 15:16:30 -0700 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current's gdb cannot read core files today (cvsup'd on Monday and installed Monday). It reports: % gdb foobar foobar.core Register %s not found in core file. % The error emanates in gdb/gdb/core-aout.c. I was going to try to diagnose the problem this weekend but unfortunately I have USNR duty. Any pointers, suggestions, etc., when I get back to real life next week? -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 15:31: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from axle.cs.ucla.edu (Axle.CS.UCLA.EDU [131.179.192.135]) by hub.freebsd.org (Postfix) with ESMTP id 9116A15D74 for ; Thu, 6 May 1999 15:30:57 -0700 (PDT) (envelope-from scottm@axle.cs.ucla.edu) Received: from axle.cs.ucla.edu (localhost [127.0.0.1]) by axle.cs.ucla.edu (8.9.3/8.9.3) with ESMTP id PAA00730 for ; Thu, 6 May 1999 15:30:55 -0700 (PDT) (envelope-from scottm@axle.cs.ucla.edu) Message-Id: <199905062230.PAA00730@axle.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org Subject: Re: Problems with -current gdb In-Reply-To: Your message of "Thu, 06 May 1999 15:16:30 PDT." <199905062216.PAA00552@axle.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 May 1999 15:30:54 -0700 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > % gdb foobar foobar.core > Register %s not found in core file. ^^ Should read: "Register eax not found in core file." Silly me... :-) -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 17:49:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiwi.datasys.net (kiwi.hefty.org [209.119.145.2]) by hub.freebsd.org (Postfix) with ESMTP id 3325E151BD for ; Thu, 6 May 1999 17:49:50 -0700 (PDT) (envelope-from ayan@kiwi.datasys.net) Received: (from ayan@localhost) by kiwi.datasys.net (8.9.3/8.9.3) id UAA51174 for freebsd-current@freebsd.org; Thu, 6 May 1999 20:49:43 -0400 (EDT) (envelope-from ayan) Date: Thu, 6 May 1999 20:49:43 -0400 (EDT) From: Ayan George Message-Id: <199905070049.UAA51174@kiwi.datasys.net> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: freebsd-current@freebsd.org Subject: make world woes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, After cvsuping the latest source, I cd'ed to the /usr/src directory and tried to ``make world''. It failed with the following message: ===> cpp cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: `GPLUSPLUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:423: initializer element for `include_defaults_array[0].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: `OLD_GPLUSPLUS_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:424: initializer element for `include_defaults_array[1].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: `GCC_INCLUDE_DIR' undeclared here (not in a function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:449: initializer element for `include_defaults_array[2].fname' is not constant /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c: In function `main': /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: `GCC_INCLUDE_DIR' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c:1376: for each function it appears in.) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 18:44:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay04.netaddress.usa.net (relay04.netaddress.usa.net [204.68.24.184]) by hub.freebsd.org (Postfix) with SMTP id 51B8015A97 for ; Thu, 6 May 1999 18:44:09 -0700 (PDT) (envelope-from jesus.monroy@usa.net) Received: (qmail 9284 invoked from network); 7 May 1999 01:44:08 -0000 Received: from nw175.netaddress.usa.net (204.68.24.75) by outbound.netaddress.usa.net with SMTP; 7 May 1999 01:44:08 -0000 Received: (qmail 13927 invoked by uid 60001); 7 May 1999 01:44:07 -0000 Message-ID: <19990507014407.13926.qmail@nw175.netaddress.usa.net> Received: from 204.68.24.75 by nw175 via web-mailer(M3.0.0.118) on Fri May 7 01:44:07 GMT 1999 Date: 6 May 99 18:44:07 PDT From: Jesus Monroy To: Daniel C.Sobral , Nick Hibma Subject: Re: [Re: ATA driver for alpha (fwd)] Cc: freebsd-current@FreeBSD.ORG X-Mailer: USANET web-mailer (M3.0.0.118) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm condisering such an animal for PicoBSD. = I'm willing to do it for current and other branches, if and only if I can get three solid alpha testers. "Daniel C. Sobral" wrote: > Nick Hibma wrote: > > = > > Jordan, you said nowadays one can simply compile a kernel < 1.44Mb an= d > > stick it on the disk kern.flp? > = > It is possible. Even more, you can add kld modules to that disk, and > then edit loader.rc to load them too, so you don't even need to > compile a kernel. > = > > People could appreciate this. I for one would like to make demo flopp= ies > > to send to companies having supplied devices for USB support to show > > their devices at work. > = > So, anyone up for creating a web page generating custom kern.klp > disks, with features not found in GENERIC, using a cgi script? :-) > = > If you limit this to adding kld modules, it would be surprisingly > easy to do it. > = > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > = > "Well, Windows works, using a loose definition of 'works'..." > = > = > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-advocacy" in the body of the message --- I am not a bot. ____________________________________________________________________ Get free e-mail and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 18:45:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.naklab.dnj.ynu.ac.jp (rina.naklab.dnj.ynu.ac.jp [133.34.17.16]) by hub.freebsd.org (Postfix) with ESMTP id 18A4A15280 for ; Thu, 6 May 1999 18:45:34 -0700 (PDT) (envelope-from tanimura@naklab.dnj.ynu.ac.jp) Received: from rina.naklab.dnj.ynu.ac.jp (localhost [127.0.0.1]) by rina.naklab.dnj.ynu.ac.jp (8.9.1a/3.7W-Naklab-2.1-19981120) with ESMTP id KAA01026; Fri, 7 May 1999 10:45:17 +0900 (JST) Message-Id: <199905070145.KAA01026@rina.naklab.dnj.ynu.ac.jp> To: imp@harmony.village.org Cc: luoqi@watermarkgroup.com, freebsd-current@freebsd.org Cc: Seigo TANIMURA Subject: Re: apmconf(8) -e ends to panic in apm_bios_call From: Seigo TANIMURA In-Reply-To: Your message of "Wed, 05 May 1999 23:25:46 -0600" References: <199905060525.XAA15252@harmony.village.org> X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 07 May 1999 10:45:16 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 05 May 1999 23:25:46 -0600, Warner Losh said: imp> : Daniel O'Connor has posted a problem similar to my one, followed by the fix imp> : patch by Luoqi Chen. I will try that patch tonight at home... imp> I strongly suspect that the Luoqi Chen fix will solve your problem. imp> It certainly does fix a problem in the hardware configuration (SMP) imp> that you are having. Yes, that patch did solve my problem as well! Thanks a lot. Seigo TANIMURA |M2, Nakagawa Lab, Dept of Electronics & CS =========================|Faculty of Engineering, Yokohama National Univ Powered by SIEMENS, |http://www.naklab.dnj.ynu.ac.jp/~tanimura/ FreeBSD 4.0-CURRENT |http://www.sakura.ne.jp/~tcarrot/ (25th Apr 1999) & muesli.|tanimura@naklab.dnj.ynu.ac.jp tcarrot@sakuramail.com VoxWare Midi Driver for Serial Ports on FreeBSD: http://www.naklab.dnj.ynu.ac.jp/~tanimura/freebsd-serialmidi/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 19: 4:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 5C14914CFD for ; Thu, 6 May 1999 19:04:13 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA77883 for ; Thu, 6 May 1999 22:04:20 -0400 (EDT) Date: Thu, 6 May 1999 22:04:19 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: IDE strangeness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having two problems with IDE nowadays. 1. ATA doesn't work with LS-120. That's not new. But ATA does seem to crash on me, and there's no dump() so I can't figure out why. 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my new Seagate, which does UDMA2 fine with ATA Any ideas? ide_pci0: at device 15.0 on pci0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-32 wd3: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 0 (atapi): , removable, iordy wfd0: medium type unknown (no disk) wdc1: interrupting at irq 15 Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 19:39:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from lcremeans.erols.com (lcremeans.erols.com [216.164.87.29]) by hub.freebsd.org (Postfix) with ESMTP id 4B9DF15084 for ; Thu, 6 May 1999 19:39:07 -0700 (PDT) (envelope-from lee@lcremeans.erols.com) Received: (from lee@localhost) by lcremeans.erols.com (8.9.2/8.9.2) id WAA00439; Thu, 6 May 1999 22:39:02 -0400 (EDT) (envelope-from lee) Message-ID: <19990506223902.A428@erols.com> Date: Thu, 6 May 1999 22:39:02 -0400 From: Lee Cremeans To: Brian Feldman , current@FreeBSD.ORG Subject: Re: IDE strangeness References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brian Feldman on Thu, May 06, 1999 at 10:04:19PM -0400 X-OS: FreeBSD 3.0-STABLE Organization: My room? Are you crazy? :) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 06, 1999 at 10:04:19PM -0400, Brian Feldman wrote: > 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my > new Seagate, which does UDMA2 fine with ATA > Can you boot -v and give the output of the ATA_INQUIRY line? That should say which modes are available on the drive. -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-current" in the body of the message From owner-freebsd-current Thu May 6 19:46:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 33AA015128; Thu, 6 May 1999 19:46:17 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id TAA08962; Thu, 6 May 1999 19:46:06 -0700 (PDT) Date: Thu, 6 May 1999 19:46:03 -0700 (PDT) From: Alex Zepeda To: "Thomas T. Veldhouse" Cc: Tomer Weller , FreeBSD Current , FreeBSD Ports Subject: Re: In-Reply-To: <009301be97cd$c1747fc0$236319ac@w142844.carlson.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 May 1999, Thomas T. Veldhouse wrote: > I had this problem on a Linux box a little while back. It also used > egcs-1.1.2. I suspect there is a problem with the compiler or the configure > script of the kde tarball. > > Tom Veldhouse > veldy@visi.com > > -----Original Message----- > From: Tomer Weller > To: FreeBSD Current ; FreeBSD Ports > > Date: Thursday, May 06, 1999 9:31 AM > > > > > >whenever i try to compile KDE software (ports also) i get this error, > though > >packages install fine. > >i installed KDE from packages, i suspect that's the problem. > > > >this is from the kmp3 port, but happens with every piece of kde software : > > > > > >checking for KDE... libraries /usr/local/lib, headers /usr/local/include > >checking for extra includes... no > >checking for extra libs... no > >checking for kde headers installed... yes > >checking for kde libraries installed... configure: error: your system fails > at linking a small KDE application! > >Check, if your compiler is installed correctly and if you have used the > >same compiler to compile qt and kdelibs as you did use now > >*** Error code 1 > > > >Stop. > >*** Error code 1 > > > >Stop. > >*** Error code 1 > > > >Stop. > >*** Error code 1 > > > >Stop. Well do the obvious first, follow the advice of the configur script. Was Qt compiled with the same compiler as the kde port you're trying to build? If not, rebuild Qt. If so, check config.log, and start looking at the end for a fatal error. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 19:52:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id 74D6415236 for ; Thu, 6 May 1999 19:52:18 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id KAA26419 for ; Fri, 7 May 1999 10:51:35 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id KAA20968 for ; Fri, 7 May 1999 10:52:14 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA08385; Fri, 7 May 1999 10:52:13 +0800 Message-Id: <199905070252.KAA08385@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Sound still not quite working (Voxware) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 May 1999 10:52:13 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get DMA / interrupt timeouts on programs such as mpg123 or NAS. Those programs that mmap the DMA buffer and set it cycling through (quake & friends) work fine. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 20:11:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.teleway.ne.jp (smtp.teleway.ne.jp [203.140.129.13]) by hub.freebsd.org (Postfix) with ESMTP id 32CA914CAF for ; Thu, 6 May 1999 20:11:03 -0700 (PDT) (envelope-from yasuf@big.or.jp) Received: from post1a.po.teleway.ne.jp (post1a.teleway.ne.jp [203.140.129.22]) by smtp.teleway.ne.jp (8.9.3+3.2W/3.7W) with ESMTP id MAA29358; Fri, 7 May 1999 12:11:00 +0900 (JST) (envelope-from yasuf@big.or.jp) Received: from localhost ([210.234.51.90]) by post1a.po.teleway.ne.jp (Post.Office MTA v3.0 release "turbo_2" ID# 110-55583U50000L50000S0V35) with ESMTP id AAA15995; Fri, 7 May 1999 12:10:57 +0900 To: freebsd-current@freebsd.org Cc: freebsd@mrynet.com Subject: Re: Make world failing in perl In-Reply-To: Your message of "Mon, 3 May 1999 10:57:51 +0000" <199905031757.KAA40870@mrynet.com> References: <199905031757.KAA40870@mrynet.com> X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Fri_May__7_12:10:40_1999_756)--" Content-Transfer-Encoding: 7bit Message-Id: <19990507121057W.yasuf@big.or.jp> Date: Fri, 07 May 1999 12:10:57 +0900 From: Yasuhiro Fukuma X-Dispatcher: imput version 980905(IM100) Lines: 458 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Fri_May__7_12:10:40_1999_756)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, In the article <199905031757.KAA40870@mrynet.com>, freebsd@mrynet.com (FreeBSD mailing list) wrote: > Perl is failing due to some kind of conflict in library versions: > > miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' lib/*.pm lib/*/*.pm > Perl lib version (5.00502) doesn't match executable version (5.00503) at /usr/libdata/perl/5.00503/mach/Config.pm line 7. > BEGIN failed--compilation aborted at /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/AutoSplit.pm line 4. > BEGIN failed--compilation aborted at -e line 1. > *** Error code 255 I'd had the same problem. I solved it by installing new miniperl before building perl itself, but it doesn't seem to be a good idea to use installled (maybe old version of) miniperl at this point. I think the attached patch can be a nice solution. How do you folks feel about that? --- Yasuhiro Fukuma (=?ISO-2022-JP?B?GyRCSiE0VhsoQiAbJEI5LzkwGyhC?=) as Yasu.F @ Kitakyushu.Fukuoka.Japan Web site: http://www8.big.or.jp/~yasuf/ ``InterNIC is NOT NSI!'' ----Next_Part(Fri_May__7_12:10:40_1999_756)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=perl.diffs Index: Makefile.inc =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/Makefile.inc,v retrieving revision 1.7 diff -u -r1.7 Makefile.inc --- Makefile.inc 1998/10/12 06:00:30 1.7 +++ Makefile.inc 1999/05/07 01:01:56 @@ -4,6 +4,8 @@ BINDIR?= /usr/bin +MINIPERL?= ${.OBJDIR}/../miniperl/miniperl + SHLIB_MAJOR?= 3 SHLIB_MINOR?= 0 Index: libperl/config.SH-aout.i386 =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/libperl/config.SH-aout.i386,v retrieving revision 1.12 diff -u -r1.12 config.SH-aout.i386 --- config.SH-aout.i386 1999/05/05 19:09:48 1.12 +++ config.SH-aout.i386 1999/05/06 19:10:43 @@ -418,7 +418,7 @@ libc='undef' libperl='libperl.so.3.0' libpth='/usr/lib/aout' -libs='-lm -lc -lcrypt' +libs='-lxpg4 -lm -lc -lcrypt' libswanted='sfio socket inet nsl nm ndbm gdbm dbm db dl dld ld sun m c cposix posix ndir dir crypt ucb bsd BSD PW x' line='line' lint='' Index: libperl/config.SH-elf.alpha =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/libperl/config.SH-elf.alpha,v retrieving revision 1.13 diff -u -r1.13 config.SH-elf.alpha --- config.SH-elf.alpha 1999/05/05 19:09:48 1.13 +++ config.SH-elf.alpha 1999/05/06 19:10:44 @@ -417,7 +417,7 @@ libc='/usr/lib/libc.so' libperl='libperl.so.3' libpth='/usr/lib' -libs='-lm -lc -lcrypt' +libs='-lxpg4 -lm -lc -lcrypt' libswanted='sfio socket inet nsl nm ndbm gdbm dbm db dl dld ld sun m c cposix posix ndir dir crypt ucb bsd BSD PW x' line='line' lint='' Index: libperl/config.SH-elf.i386 =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/libperl/config.SH-elf.i386,v retrieving revision 1.12 diff -u -r1.12 config.SH-elf.i386 --- config.SH-elf.i386 1999/05/05 19:09:48 1.12 +++ config.SH-elf.i386 1999/05/06 19:10:44 @@ -417,7 +417,7 @@ libc='/usr/lib/libc.so' libperl='libperl.so.3' libpth='/usr/lib' -libs='-lm -lc -lcrypt' +libs='-lxpg4 -lm -lc -lcrypt' libswanted='sfio socket inet nsl nm ndbm gdbm dbm db dl dld ld sun m c cposix posix ndir dir crypt ucb bsd BSD PW x' line='line' lint='' Index: miniperl/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/miniperl/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- Makefile 1998/10/11 18:13:41 1.7 +++ Makefile 1999/03/25 12:20:34 @@ -9,7 +9,7 @@ # Miniperl _must_ be static!! NOSHARED= yes DPADD= ${LIBPERL} ${LIBM} ${LIBCRYPT} -LDADD= -lperl -lm -lcrypt +LDADD= -lperl -lxpg4 -lm -lcrypt # Trick the bootstrap tools into thinking that miniperl is perl. # This gets overwritten. Index: perl/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/perl/Makefile,v retrieving revision 1.17 diff -u -r1.17 Makefile --- Makefile 1999/05/02 15:29:44 1.17 +++ Makefile 1999/05/07 01:01:20 @@ -8,7 +8,7 @@ SRCS= perlmain.c config.h NOSHARED= no DPADD= lib/auto/DynaLoader/DynaLoader.a ${LIBPERL} ${LIBM} ${LIBCRYPT} -LDADD= lib/auto/DynaLoader/DynaLoader.a -lperl -lm -lcrypt +LDADD= lib/auto/DynaLoader/DynaLoader.a -lperl -lxpg4 -lm -lcrypt LINKS= ${BINDIR}/${PROG} ${BINDIR}/perl5 \ ${BINDIR}/${PROG} ${BINDIR}/perl5.00503 @@ -36,7 +36,7 @@ sh cflags.sh Config.pm: linkfarm - miniperl ${PERL5SRC}/configpm \ + ${MINIPERL} ${PERL5SRC}/configpm \ Config.pm Porting/Glossary myconfig config.sh cd lib ; ln -sf ../${.TARGET} @@ -47,7 +47,7 @@ sh writemain.sh autosplit: linkfarm Config.pm lib/*.pm lib/*/*.pm - miniperl -I${.OBJDIR}/lib \ + ${MINIPERL} -I${.OBJDIR}/lib \ -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' \ lib/*.pm lib/*/*.pm touch ${.TARGET} @@ -55,7 +55,7 @@ .for I in ${STATIC_EXT} ext/${I:H}/Makefile: linkfarm ext/${I:H}/Makefile.PL cflags Config.pm cd ext/${I:H}; \ - miniperl -I${.OBJDIR}/lib Makefile.PL \ + ${MINIPERL} -I${.OBJDIR}/lib Makefile.PL \ LINKTYPE=static INSTALLDIRS=perl PERL_SRC=${.OBJDIR} \ LIBS="-lperl" INSTALLMAN3DIR=${DESTDIR}/usr/share/perl/man3; \ make -B config PERL_SRC=${.OBJDIR} @@ -72,7 +72,7 @@ .for I in ${DYNAMIC_EXT} ext/${I:H}/Makefile: linkfarm ext/${I:H}/Makefile.PL cflags Config.pm pod2man cd ext/${I:H}; \ - miniperl -I${.OBJDIR}/lib Makefile.PL \ + ${MINIPERL} -I${.OBJDIR}/lib Makefile.PL \ LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=${.OBJDIR} \ LIBS="-lperl" INSTALLMAN3DIR=${DESTDIR}/usr/share/perl/man3 \ INST_LIB=${.OBJDIR}/build/${I:H} \ @@ -93,7 +93,7 @@ ext/${I:H}/Makefile: linkfarm ext/${I:H}/Makefile.PL cflags lib/Config.pm mkdir -p ${.OBJDIR}/lib/auto/${I:H} ;\ cd ext/${I:H} ;\ - miniperl -I${.OBJDIR}/lib Makefile.PL \ + ${MINIPERL} -I${.OBJDIR}/lib Makefile.PL \ INSTALLDIRS=perl PERL_SRC=${.OBJDIR} \ INSTALLMAN3DIR=/usr/share/perl/man3 \ INST_LIB=${.OBJDIR}/lib/auto/${I:H} \ @@ -109,14 +109,14 @@ pod2man: Config.pm autosplit ${PERL5SRC}/pod/pod2man.PL ln -sf ${PERL5SRC}/pod/pod2man.PL - miniperl -I${.OBJDIR}/lib pod2man.PL + ${MINIPERL} -I${.OBJDIR}/lib pod2man.PL man3pages: pod2man cd ${.OBJDIR}/lib ;\ for i in `find . -name \*.pm | grep -v Functions.pm` ; do \ j=`echo $$i | sed -e 's|./||' -e 's|/|::|g' -e 's|.pm|.3|'` ;\ echo Manifying $$j ;\ - miniperl -I${.OBJDIR}/lib ${.OBJDIR}/pod2man $$i > $$j ;\ + ${MINIPERL} -I${.OBJDIR}/lib ${.OBJDIR}/pod2man $$i > $$j ;\ gzip -fn $$j ;\ done cd ${.OBJDIR}/ext ;\ @@ -127,7 +127,7 @@ -e 's|/|::|g' -e 's|.pm|.3|' -e 's|.pod|.3|'`;\ i=`echo $$i | sed -e 's|./||'` ;\ echo Manifying $$j ;\ - miniperl -I${.OBJDIR}/lib ${.OBJDIR}/pod2man $$i > ../lib/$$j ;\ + ${MINIPERL} -I${.OBJDIR}/lib ${.OBJDIR}/pod2man $$i > ../lib/$$j ;\ gzip -fn ../lib/$$j ;\ done touch ${.TARGET} Index: pod/Makefile.inc =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/pod/Makefile.inc,v retrieving revision 1.1 diff -u -r1.1 Makefile.inc --- Makefile.inc 1998/09/09 07:20:27 1.1 +++ Makefile.inc 1999/05/07 01:01:12 @@ -3,6 +3,7 @@ # PERL5SRC?= ${.CURDIR}/../../../../../contrib/perl5 +MINIPERL?= ${.OBJDIR}/../../miniperl/miniperl MINIPERLOPT?= -I${.OBJDIR}/../../perl/lib -I${.OBJDIR}/../../perl CLEANFILES+= ${PROG}.1 ${PROG}.PL Index: pod/pod/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/pod/pod/Makefile,v retrieving revision 1.3 diff -u -r1.3 Makefile --- Makefile 1999/05/02 15:29:48 1.3 +++ Makefile 1999/05/07 00:59:49 @@ -18,7 +18,7 @@ @ln -sf ${.OODATE} ${.TARGET} ${I}.1: ${I}.pod - miniperl ${MINIPERLOPT} ${.OBJDIR}/../pod2man/pod2man ${.OODATE} \ + ${MINIPERL} ${MINIPERLOPT} ${.OBJDIR}/../pod2man/pod2man ${.OODATE} \ > ${.TARGET} MAN1+= ${I}.1 Index: pod/pod2html/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/pod/pod2html/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- Makefile 1998/09/09 07:20:27 1.1 +++ Makefile 1999/05/07 00:59:57 @@ -5,10 +5,10 @@ PROG= pod2html ${PROG}: ${PROG}.PL - miniperl ${MINIPERLOPT} ${PROG}.PL + ${MINIPERL} ${MINIPERLOPT} ${PROG}.PL ${PROG}.1: ${PROG}.PL - miniperl ${MINIPERLOPT} ${.OBJDIR}/../pod2man/pod2man ${PROG}.PL > ${PROG}.1 + ${MINIPERL} ${MINIPERLOPT} ${.OBJDIR}/../pod2man/pod2man ${PROG}.PL > ${PROG}.1 .include Index: pod/pod2latex/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/pod/pod2latex/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- Makefile 1998/09/09 07:20:27 1.1 +++ Makefile 1999/05/07 01:00:05 @@ -7,7 +7,7 @@ NOMAN= true ${PROG}: ${PROG}.PL - miniperl ${MINIPERLOPT} ${PROG}.PL + ${MINIPERL} ${MINIPERLOPT} ${PROG}.PL .include Index: pod/pod2man/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/pod/pod2man/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- Makefile 1998/09/09 07:20:28 1.1 +++ Makefile 1999/05/07 01:00:22 @@ -5,10 +5,10 @@ PROG= pod2man ${PROG}: ${PROG}.PL - miniperl ${MINIPERLOPT} ${PROG}.PL + ${MINIPERL} ${MINIPERLOPT} ${PROG}.PL ${PROG}.1: ${PROG}.PL - miniperl ${MINIPERLOPT} ${.OBJDIR}/../pod2man/pod2man ${PROG}.PL \ + ${MINIPERL} ${MINIPERLOPT} ${.OBJDIR}/../pod2man/pod2man ${PROG}.PL \ > ${PROG}.1 .include Index: pod/pod2text/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/pod/pod2text/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- Makefile 1998/09/09 07:20:28 1.1 +++ Makefile 1999/05/07 01:00:32 @@ -7,7 +7,7 @@ NOMAN= true ${PROG}: ${PROG}.PL - miniperl ${MINIPERLOPT} ${PROG}.PL + ${MINIPERL} ${MINIPERLOPT} ${PROG}.PL .include Index: suidperl/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/suidperl/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- Makefile 1999/05/02 15:29:52 1.7 +++ Makefile 1999/05/07 01:02:43 @@ -8,7 +8,7 @@ SRCS= perlmain.c sperl.c config.h NOSHARED= no DPADD= lib/auto/DynaLoader/DynaLoader.a ${LIBPERL} ${LIBM} ${LIBCRYPT} -LDADD= lib/auto/DynaLoader/DynaLoader.a -lperl -lm -lcrypt +LDADD= lib/auto/DynaLoader/DynaLoader.a -lperl -lxpg4 -lm -lcrypt BINOWN= root BINMODE=4511 LINKS= ${BINDIR}/${PROG} ${BINDIR}/sperl5.00503 @@ -34,7 +34,7 @@ sh cflags.sh Config.pm: linkfarm - miniperl ${PERL5SRC}/configpm \ + ${MINIPERL} ${PERL5SRC}/configpm \ Config.pm Porting/Glossary myconfig config.sh cd lib ; ln -sf ../${.TARGET} @@ -45,7 +45,7 @@ sh writemain.sh autosplit: linkfarm Config.pm lib/*.pm lib/*/*.pm - miniperl -I${.OBJDIR}/lib \ + ${MINIPERL} -I${.OBJDIR}/lib \ -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' \ lib/*.pm lib/*/*.pm touch ${.TARGET} @@ -53,7 +53,7 @@ .for I in ${STATIC_EXT} ext/${I:H}/Makefile: linkfarm ext/${I:H}/Makefile.PL cflags Config.pm cd ext/${I:H}; \ - miniperl -I${.OBJDIR}/lib Makefile.PL \ + ${MINIPERL} -I${.OBJDIR}/lib Makefile.PL \ LINKTYPE=static INSTALLDIRS=perl PERL_SRC=${.OBJDIR} \ LIBS="-lperl" INSTALLMAN3DIR=${DESTDIR}/usr/share/perl/man3; \ make -B config PERL_SRC=${.OBJDIR} Index: utils/Makefile.inc =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/utils/Makefile.inc,v retrieving revision 1.2 diff -u -r1.2 Makefile.inc --- Makefile.inc 1998/09/10 10:51:10 1.2 +++ Makefile.inc 1999/05/07 01:03:31 @@ -3,13 +3,14 @@ # PERL5SRC= ${.CURDIR}/../../../../../contrib/perl5 +MINIPERL?= ${.OBJDIR}/../../miniperl/miniperl MINIPERLOPT?= -I${.OBJDIR}/../../perl/lib -I${.OBJDIR}/../../perl ${PROG}: ${PROG}.PL - miniperl ${MINIPERLOPT} ${.OODATE} + ${MINIPERL} ${MINIPERLOPT} ${.OODATE} ${PROG}.1: ${PROG}.PL - miniperl ${MINIPERLOPT} ${.OBJDIR}/../../pod/pod2man/pod2man ${.OODATE} > ${.TARGET} + ${MINIPERL} ${MINIPERLOPT} ${.OBJDIR}/../../pod/pod2man/pod2man ${.OODATE} > ${.TARGET} ${PROG}.PL: ${PERL5SRC}/utils/${PROG}.PL @ln -sf ${.OODATE} ${.TARGET} Index: utils/h2ph/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/utils/h2ph/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- Makefile 1999/05/02 15:29:56 1.4 +++ Makefile 1999/05/07 01:03:54 @@ -8,5 +8,5 @@ afterinstall: cd ${DESTDIR}/usr/include; \ - miniperl ${.OBJDIR}/${PROG} -d \ + ${MINIPERL} ${.OBJDIR}/${PROG} -d \ ${DESTDIR}/usr/libdata/perl/5.00503/mach * */* Index: x2p/Makefile.inc =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/x2p/Makefile.inc,v retrieving revision 1.2 diff -u -r1.2 Makefile.inc --- Makefile.inc 1998/09/10 10:51:10 1.2 +++ Makefile.inc 1999/05/07 01:04:19 @@ -3,6 +3,7 @@ # PERL5SRC= ${.CURDIR}/../../../../../contrib/perl5 +MINIPERL?= ${.OBJDIR}/../../miniperl/miniperl MINIPERLOPT?= -I${.OBJDIR}/../../perl/lib -I${.OBJDIR}/../../perl STRIP= Index: x2p/a2pl/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/x2p/a2pl/Makefile,v retrieving revision 1.6 diff -u -r1.6 Makefile --- Makefile 1998/09/22 12:00:59 1.6 +++ Makefile 1999/05/07 01:04:31 @@ -32,4 +32,4 @@ ln -sf ${.OODATE} ${.TARGET} ${PROG}.1: ${PROG}.pod - miniperl ${MINIPERLOPT} ${.OBJDIR}/../../pod/pod2man/pod2man ${.OODATE} > ${.TARGET} + ${MINIPERL} ${MINIPERLOPT} ${.OBJDIR}/../../pod/pod2man/pod2man ${.OODATE} > ${.TARGET} Index: x2p/find2pl/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/x2p/find2pl/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- Makefile 1998/09/10 10:51:11 1.2 +++ Makefile 1999/05/07 01:04:48 @@ -6,10 +6,10 @@ NOMAN= true ${PROG}: ${PROG}.PL - miniperl ${MINIPERLOPT} ${.OODATE} + ${MINIPERL} ${MINIPERLOPT} ${.OODATE} ${PROG}.1: ${PROG}.PL - miniperl ${MINIPERLOPT} ${.OBJDIR}/../../pod/pod2man/pod2man ${.OODATE} > ${.TARGET} + ${MINIPERL} ${MINIPERLOPT} ${.OBJDIR}/../../pod/pod2man/pod2man ${.OODATE} > ${.TARGET} CLEANFILES+= ${PROG}.1 ${PROG}.PL Index: x2p/s2pl/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/perl/x2p/s2pl/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- Makefile 1998/09/10 10:51:11 1.2 +++ Makefile 1999/05/07 01:05:05 @@ -5,10 +5,10 @@ PROG= s2p ${PROG}: ${PROG}.PL - miniperl ${MINIPERLOPT} ${.OODATE} + ${MINIPERL} ${MINIPERLOPT} ${.OODATE} ${PROG}.1: ${PROG}.PL - miniperl ${MINIPERLOPT} ${.OBJDIR}/../../pod/pod2man/pod2man ${.OODATE} > ${.TARGET} + ${MINIPERL} ${MINIPERLOPT} ${.OBJDIR}/../../pod/pod2man/pod2man ${.OODATE} > ${.TARGET} CLEANFILES+= ${PROG}.1 ${PROG}.PL ----Next_Part(Fri_May__7_12:10:40_1999_756)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 22:52:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 48ECD152BA for ; Thu, 6 May 1999 22:52:24 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA11613; Fri, 7 May 1999 15:52:15 +1000 Date: Fri, 7 May 1999 15:52:15 +1000 From: Bruce Evans Message-Id: <199905070552.PAA11613@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, yasuf@big.or.jp Subject: Re: Make world failing in perl Cc: freebsd@mrynet.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I solved it by installing new miniperl before building perl itself, >but it doesn't seem to be a good idea to use installled (maybe old >version of) miniperl at this point. `make world' is supposed to use the new miniperl that it has just installed in ${TOOLROOT}/usr/bin which is at the front of $PATH. There may be a problem with the perl build breaking $PATH so that the wrong miniperl is found. There certainly are problems with it breaking $PATH so that the wrong perl is found (perl is supposed to be a link to miniperl for `make world'). >I think the attached patch can be a nice solution. >How do you folks feel about that? This breaks cross compiling in much the same way as running perl from an obj dir breaks it. The version in the obj might not run on the host machine. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 6 23:52:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0B4DE15D6B; Thu, 6 May 1999 23:52:43 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA20106; Fri, 7 May 1999 00:51:56 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA00870; Fri, 7 May 1999 00:51:46 -0600 (MDT) Message-Id: <199905070651.AAA00870@harmony.village.org> To: sobomax@altavista.net Subject: Re: Sysinstall still broken Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, jkh@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 May 1999 12:34:43 +0300." <37316232.C92A520D@altavista.net> References: <37316232.C92A520D@altavista.net> <56588.925982254@zippy.cdrom.com> Date: Fri, 07 May 1999 00:51:45 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37316232.C92A520D@altavista.net> Maxim Sobolev writes: : Instead of : #include : should be : #include : and pnp.h also i386/isa/isa_device.h is the legecy interface to the isa drivers. Its use should be strongly discouraged... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 0: 9:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep9.mail.ozemail.net (fep9.mail.ozemail.net [203.2.192.103]) by hub.freebsd.org (Postfix) with ESMTP id 1BAD0153D2 for ; Fri, 7 May 1999 00:09:30 -0700 (PDT) (envelope-from c9710216@atlas.newcastle.edu.au) Received: from atlas.newcastle.edu.au (slnew52p09.ozemail.com.au [203.108.150.87]) by fep9.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id RAA23006 for ; Fri, 7 May 1999 17:09:27 +1000 (EST) Message-ID: <373291BD.42BC5B83@atlas.newcastle.edu.au> Date: Fri, 07 May 1999 17:09:49 +1000 From: obituary X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Problem with the new ATA driver. Content-Type: multipart/mixed; boundary="------------85C250E215D8DF47B681CE72" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------85C250E215D8DF47B681CE72 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The new ATA driver (ata0, atadisk0, atapicd0) gives me a *huge* speed boost when accessing the harddisk, but I have to sacrifice the use of my CDROM if I choose to include it. The CDROM appears to be detected correctly by the kernel, but when trying to access the device I get the message: cd9660: Device not configured I've also tried reading from the CDROM without mounting it. I tried the following: dd if=/dev/ of=/tmp/dumpfile bs=1024k where was (in order) wcd0c, wcd0a, acd0c, acd0a, and their raw equivalents. Each time, the message I received was: : Device not configured Everything works fine if I use the old wd driver. I've included my kernel config file and the dmesg file. If there's anything else I can supply that would help, let me know. -jake -- --------------85C250E215D8DF47B681CE72 Content-Type: text/plain; charset=us-ascii; name="CARCASS" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="CARCASS" # # LINT -- config file for checking all the sources, tries to pull in # as much of the source tree as it can. # # $Id: LINT,v 1.593 1999/05/05 12:22:31 jb Exp $ # machine i386 ident CARCASS maxusers 32 # When this is set, be extra conservative in various parts of the kernel # and choose functionality over speed (on the widest variety of systems). options FAILSAFE # Options for the VM subsystem options PQ_LARGECACHE # color for 512k/16k cache config kernel root on wd0 # CPU OPTIONS cpu I686_CPU # aka Pentium Pro(tm) # Options for CPU features. options CPU_DISABLE_5X86_LSSER options CPU_FASTER_5X86_FPU options NO_F00F_HACK # COMPATIBILITY OPTIONS options COMPAT_43 options COMPAT_LINUX options USER_LDT #allow user-level control of i386 ldt options SYSVSHM options SYSVSEM options SYSVMSG options MD5 options VM86 options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # NETWORKING OPTIONS options INET #Internet communications protocols # Network interfaces: # The `loop' pseudo-device is MANDATORY when networking is enabled. # The `ether' pseudo-device provides code to handle Ethernets. pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device # FILESYSTEM OPTIONS options FFS #Fast filesystem options CD9660 #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options SOFTUPDATES options EXT2FS # POSIX P1003.1B options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 64 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) # HARDWARE DEVICE CONFIGURATION # Mandatory ISA devices: isa, npx controller isa0 # Options for `isa': options AUTO_EOI_1 # ISA PnP Support. controller pnp0 # The keyboard controller; it controls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 # The video card driver. device vga0 at isa? port ? conflicts options VESA # needs VM86 defined too!! pseudo-device splash # The syscons console driver (sco color console compatible). device sc0 at isa? options MAXCONS=16 # number of virtual consoles # The Numeric Processing eXtension driver. device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 # ATA and ATAPI devices controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives # IDE Disk driver #controller wdc0 at isa? port IO_WD1 irq 14 #disk wd0 at wdc0 drive 0 #controller wdc1 at isa? port IO_WD2 irq 15 #options IDE_DELAY=1000 # IDE CD-ROM & CD-R/RW driver - requires wdc controller and ATAPI option #device wcd0 # Standard floppy disk controllers and floppy tapes: `fdc', `fd', and `ft' controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 # sio: serial ports (see sio(4)) device sio0 at isa? port IO_COM1 flags 0x10 irq 4 options CONSPEED=38400 #default speed for serial console # Network interfaces: `cx', `ed', `el', `ep', `ie', `is', `le', `lnc' device ed0 at isa? port 0x340 irq 10 iomem 0xd8000 # Audio drivers: `snd', `sb', `pas', `gus', `pca' controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 #device awe0 at isa? port 0x620 device opl0 at isa? port 0x388 # Not controlled by `snd' device pca0 at isa? port IO_TIMER1 # PCI devices & PCI options: controller pci0 # SMB bus controller smbus0 controller intpm0 device smb0 at smbus? # Parallel-Port Bus controller ppbus0 device lpt0 at ppbus? device ppc0 at isa? port? irq 7 --------------85C250E215D8DF47B681CE72 Content-Type: text/plain; charset=us-ascii; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri May 7 16:36:14 EST 1999 root@carcass.death.net:/usr/src/sys/compile/CARCASS Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 463910653 Hz CPU: Celeron (463.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping=0 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127733760 (124740K bytes) Preloaded elf kernel "kernel" at 0xc02cb000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x0e67b4ee Comp ID: PNPb02f [0x2fb0d041] npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip2: at device 7.3 on pci0 isa0: on motherboard atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model IntelliMouse, device ID 3 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 ed0 at port 0x340-0x35f irq 10 on isa0 ed0: address 00:00:e8:60:97:36, type NE2000 (16 bit) ed0: interrupting at irq 10 sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sb0: interrupting at irq 5 sbxvi0 at drq 5 on isa0 snd0: sbmidi0 at port 0x330 on isa0 snd0: opl0 at port 0x388 on isa0 snd0: pca0 at port 0x40 on isa0 pca0: PC speaker audio driver ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 ata1: unwanted interrupt 1 status = 00 ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 4892MB (10018890 sectors), 10602 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata1 as master acd0: drive speed 0 - 5500KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked changing root device to wd0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates --------------85C250E215D8DF47B681CE72-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 0:23:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7C33E14DC5 for ; Fri, 7 May 1999 00:22:53 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA31392; Fri, 7 May 1999 09:21:43 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905070721.JAA31392@freebsd.dk> Subject: Re: Problem with the new ATA driver. In-Reply-To: <373291BD.42BC5B83@atlas.newcastle.edu.au> from obituary at "May 7, 1999 5: 9:49 pm" To: c9710216@atlas.newcastle.edu.au (obituary) Date: Fri, 7 May 1999 09:21:43 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems obituary wrote: > The new ATA driver (ata0, atadisk0, atapicd0) gives me a *huge* speed > boost when accessing the harddisk, but I have to sacrifice the use of my > CDROM if I choose to include it. > > The CDROM appears to be detected correctly by the kernel, but when > trying to access the device I get the message: > > cd9660: Device not configured > > I've also tried reading from the CDROM without mounting it. I tried the > following: > > dd if=/dev/ of=/tmp/dumpfile bs=1024k > > where was (in order) wcd0c, wcd0a, acd0c, acd0a, and their > raw equivalents. Each time, the message I received was: > > : Device not configured Have you made the acd device nodes with an updated MAKEDEV ?? Sounds like you use the old major number to me... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 0:34:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id A27E214CE0; Fri, 7 May 1999 00:34:36 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-19.iptelecom.net.ua [212.42.68.210]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA27412; Fri, 7 May 1999 10:34:53 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA30000; Fri, 7 May 1999 10:34:02 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37329769.2E50B96E@altavista.net> Date: Fri, 07 May 1999 10:34:01 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Warner Losh Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Sysinstall still broken References: <37316232.C92A520D@altavista.net> <56588.925982254@zippy.cdrom.com> <199905070651.AAA00870@harmony.village.org> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <37316232.C92A520D@altavista.net> Maxim Sobolev writes: > : Instead of > : #include > : should be > : #include > : and pnp.h also > > i386/isa/isa_device.h is the legecy interface to the isa drivers.  Its > use should be strongly discouraged... Tell this to the Jordan... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 0:49:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id 2A3A814F53 for ; Fri, 7 May 1999 00:49:08 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 11583 invoked by uid 1000); 7 May 1999 07:47:31 -0000 Date: Fri, 7 May 1999 09:47:30 +0200 From: Andreas Braukmann To: freebsd-current@freebsd.org Subject: just pulled the egcs-switch Message-ID: <19990507094730.A457@paert.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, ... yesterday I decided, that it might be the right time to actually pull the 'egcs'-switch on my 4.0-current SMP-box. I cvsupped, built and installed the world, tweaked the kernel config (newbus) ... The transition was smooth, so far. The question remained: ... how to easily figure out which ports are in the egcs-caused need for a rebuild? ok. ... all the c++-based ones, but how to find out which ports are c++ ones? Is anybody out there, with hints or experiences to share? TIA, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 1: 4:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 1287314CCF for ; Fri, 7 May 1999 01:04:12 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup3-21.iptelecom.net.ua [212.42.69.212]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA29717; Fri, 7 May 1999 11:04:58 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id LAA30459; Fri, 7 May 1999 11:04:06 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37329D60.924BD5D9@altavista.net> Date: Fri, 07 May 1999 10:59:28 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Andreas Braukmann Cc: freebsd-current@FreeBSD.ORG Subject: Re: just pulled the egcs-switch References: <19990507094730.A457@paert.tse-online.de> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Braukmann wrote: > Hi there, > >  ... yesterday I decided, that it might be the right time to >  actually pull the 'egcs'-switch on my 4.0-current SMP-box. >  I cvsupped, built and installed the world, tweaked the >  kernel config (newbus) ... >  The transition was smooth, so far. > >  The question remained: ... how to easily figure out which ports >  are in  the egcs-caused need for a rebuild? > >  ok. ... all the c++-based ones, but how to find out which ports >  are c++ ones? > >  Is anybody out there, with hints or experiences to share? I can suggest following: sh# find /usr/local/bin -type f -exec ldd {} \;  > /tmp/ldd_list sh# find /usr/X11R6/bin -type f -exec ldd {} \;  >> /tmp/ldd_list sh# less /tmp/ldd_list Then look at the output and find which binaries linked against libstdc++. Howewer problem with third-party c++ libraries (like qt, kde and other will remain). Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 1:10:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 95AA115366 for ; Fri, 7 May 1999 01:10:53 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id BAA26647; Fri, 7 May 1999 01:10:31 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199905070810.BAA26647@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Braukmann Cc: freebsd-current@FreeBSD.ORG Subject: Re: just pulled the egcs-switch In-reply-to: Your message of "Fri, 07 May 1999 09:47:30 +0200." <19990507094730.A457@paert.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 May 1999 01:10:31 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is not a good idea to use the default egcs as it is configured to compile c++ programs which use threads and exceptions for instance Netscape's Eletrical Fire (A Java VM/Compiler) does not work. -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 1:17:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 8AAB315366 for ; Fri, 7 May 1999 01:17:50 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id DAA15632; Fri, 7 May 1999 03:17:47 -0500 (CDT) From: Kevin Day Message-Id: <199905070817.DAA15632@home.dragondata.com> Subject: -current deadlocks within 5 mins, over NFS To: dillon@backplane.com Date: Fri, 7 May 1999 03:17:46 -0500 (CDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt, I told you about this before, but completely forgot about it. After doing considerable testing on my test servers, i thought -current was safe enough to try on our production shell servers. I installed -current on one of my servers, and to my dismay, it hung. :) Within 5 minutes of running, nearly every process is blocked on 'inode', with the exception of a single 'cp' stuck in vmopar. I have a very silly, *very* poorly written script i run out of cron, every 10 mins or so, to update my passwd and group files. #/bin/sh cp /home/private/passwd /etc cp /home/private/master.passwd /etc cp /home/private/group /etc rm /etc/spwd.db.tmp >/dev/null 2>&1 pwd_mkdb /etc/master.passwd This script is the only source of a 'cp' anywhere... If I turn this off, I was able to run for at least 30 mins(more, if i hadn't rebooted) /home is a UDP NFS2 mount. Moving the source of those cp's to a local drive also fixes the problem, but breaks the use for my script. :) What more info do you need for help in debugging this? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 1:31:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D904C15C8B for ; Fri, 7 May 1999 01:31:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA10078; Fri, 7 May 1999 09:31:52 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 7 May 1999 09:31:52 +0100 (BST) From: Doug Rabson To: Scott Michel Cc: freebsd-current@freebsd.org Subject: Re: Problems with -current gdb In-Reply-To: <199905062230.PAA00730@axle.cs.ucla.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 May 1999, Scott Michel wrote: > > % gdb foobar foobar.core > > Register %s not found in core file. > ^^ > Should read: > > "Register eax not found in core file." > > Silly me... :-) I'll look at it today - My head is in gdb mode at the moment after doing the import. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 1:37: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id C407F15D9C for ; Fri, 7 May 1999 01:36:51 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 37860 invoked by uid 1000); 7 May 1999 08:35:15 -0000 Date: Fri, 7 May 1999 10:35:14 +0200 From: Andreas Braukmann To: freebsd-current@FreeBSD.ORG Cc: Amancio Hasty Subject: Re: just pulled the egcs-switch Message-ID: <19990507103514.B457@paert.tse-online.de> References: <19990507094730.A457@paert.tse-online.de> <199905070810.BAA26647@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199905070810.BAA26647@rah.star-gate.com>; from Amancio Hasty on Fri, May 07, 1999 at 01:10:31AM -0700 Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, May 07, 1999 at 01:10:31AM -0700, Amancio Hasty wrote: > Is not a good idea to use the default egcs as it is configured to compile > c++ programs which use threads and exceptions for instance Netscape's > Eletrical Fire (A Java VM/Compiler) does not work. do you suggest to use the egcs from the ports collection as the 'more-or-less' default compiler for the ports? I've used the beast for a few c++ applications (from ports and various other sources), which needed the more advanced c++-compiler than gcc 2.7.x. But then I have '2 different compilers' and '2 different set of libs', again, havn't I? -Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 1:42:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 2595415D5D for ; Fri, 7 May 1999 01:42:18 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id BAA26982; Fri, 7 May 1999 01:42:01 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199905070842.BAA26982@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Braukmann Cc: freebsd-current@FreeBSD.ORG Subject: Re: just pulled the egcs-switch In-reply-to: Your message of "Fri, 07 May 1999 10:35:14 +0200." <19990507103514.B457@paert.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 May 1999 01:42:01 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes I would try out the one on the ports directory first for threaded applications with exceptions. -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 2: 2:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (Postfix) with ESMTP id 9D7D615E52 for ; Fri, 7 May 1999 02:02:28 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id SAA04845 for ; Fri, 7 May 1999 18:59:00 +1000 (EST) Date: Fri, 7 May 1999 18:59:00 +1000 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: freebsd-current@FreeBSD.ORG Subject: Re: make world failure mode In-Reply-To: <199905021621.CAA30286@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 May 1999, Bruce Evans wrote: > >I have noticed that if you do not have /usr/share/groff_font > >directory, a buildworld will fail. I think GROFF_FONT_PATH is > >missing from a Makefile maybe? The dev* directories are already > >built in the obj tree... > > Similarly for /usr/share/tmac and GROFF_TMAC_PATH. > > Not quite similarly for /usr/share/dict/{various}. groff uses these, > but there doesn't seem to be any macros for them. Hopefully they aren't > used by buildworld. A 'make buildworld' completed ok without a /usr/share/dict > > Bruce > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 4:11:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep7.mail.ozemail.net (fep7.mail.ozemail.net [203.2.192.125]) by hub.freebsd.org (Postfix) with ESMTP id 6244114F6C for ; Fri, 7 May 1999 04:11:50 -0700 (PDT) (envelope-from c9710216@atlas.newcastle.edu.au) Received: from atlas.newcastle.edu.au (slnew54p16.ozemail.com.au [203.108.151.32]) by fep7.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id VAA15893; Fri, 7 May 1999 21:09:09 +1000 (EST) Message-ID: <3732C9EB.E30EEBDD@atlas.newcastle.edu.au> Date: Fri, 07 May 1999 21:09:31 +1000 From: obituary X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problem with the new ATA driver. References: <199905070721.JAA31392@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > Have you made the acd device nodes with an updated MAKEDEV ?? > Sounds like you use the old major number to me... That was it. I installed the new MAKEDEV and did a "sh MAKEDEV all" when I upgraded to 4.0-CURRENT. I now know it doesn't create the acd0 devices by default ;-) Thanks for the help. > -Søren -jake c9710216@atlas.newcastle.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 4:37:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 5A24514E49 for ; Fri, 7 May 1999 04:37:45 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id HAA86249; Fri, 7 May 1999 07:37:45 -0400 (EDT) Date: Fri, 7 May 1999 07:37:44 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Lee Cremeans Cc: current@FreeBSD.ORG Subject: Re: IDE strangeness In-Reply-To: <19990506223902.A428@erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 May 1999, Lee Cremeans wrote: > On Thu, May 06, 1999 at 10:04:19PM -0400, Brian Feldman wrote: > > > 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my > > new Seagate, which does UDMA2 fine with ATA > > > > Can you boot -v and give the output of the ATA_INQUIRY line? That should say > which modes are available on the drive. Here's what I've got: ide_pci0: at device 15.0 on pci0 ide_pci: busmaster 0 status: 84 from port: 0000ffa2 ide_pci: busmaster 1 status: 84 from port: 0000ffaa wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wd0: wdsetmode() setting transfer mode to 42 wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wd3: wdsetmode() setting transfer mode to 22 wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-32 wd3: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wd3: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1: unit 0 (atapi): , removable, iordy wfd0: medium type unknown (no disk) wdc1: interrupting at irq 15 > > -lee > > -- > +--------------------------------------------------------------------+ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | > | lcremeans@erols.com | http://wakky.dyndns.org/~lee | > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 5: 7: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (Postfix) with ESMTP id B5F581532D for ; Fri, 7 May 1999 05:06:05 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id GAA06743; Fri, 7 May 1999 06:05:49 -0600 (MDT) (envelope-from drussell@saturn-tech.com) Date: Fri, 7 May 1999 06:05:49 -0600 (MDT) From: Doug Russell To: Brian Feldman Cc: Lee Cremeans , current@FreeBSD.ORG Subject: Re: IDE strangeness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 May 1999, Brian Feldman wrote: > > > 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my > > > new Seagate, which does UDMA2 fine with ATA > > Here's what I've got: > wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 > wd0: wdsetmode() setting transfer mode to 42 > wdc0: unit 0 (wd0): , 32-bit, multi-block-16 > wd0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S > wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 Hmmmm.. I just started playing with 4.0-CURRENT the other day, and I've been using a nice SCSI disk, however, when I connected a couple of Western Digital IDEs, I had a couple strange problems: Same controller in an Asus P5A-A, K6-III 400 MHz @ 100x4... /kernel: ide_pci0: at device 15.0 on pci0 wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 19470MB (39876480 sectors), 39560 cyls, 16 heads, 63 S/T, 512 B/S Note there is no DMA on there either... I couldn't get either the 13 or 20 Gig to do DMA, even though I have done it before on -STABLE. The other oddity with early AM yesterday's world & kernel was: wdc0 at port 0x1f0-0x1f7 irq 1 drq 0 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA,32-bit, multi-block-16 wd0: 19470MB (39876480 sectors), 39560 cyls, 16 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 1 What gives with the irq 1? All sorts of things were showing up on irq 1, even though they were actually configured on 14, 15, 5 (for sio2), etc... I thought this was something funky in the bus changes, and may be gone now, I haven't tried the IDE disks again on anything since, but other things (like sio2) are back to normal on the last 5 or 6 builds. Boy these K6-IIIs are FAST... My worldstone is under 1h WITHOUT turning on softupdates, no async mounting, no noatime, no -j, and src and obj are on the same (/usr) partition of one SCSI disk! Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 5:58:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7DDBF14CC9 for ; Fri, 7 May 1999 05:58:10 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id FAA96664 for ; Fri, 7 May 1999 05:58:42 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: somebody has broken sysctlbyname() in -current Date: Fri, 07 May 1999 05:58:41 -0700 Message-ID: <96660.926081921@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How to repeat symptoms: boot -c kget Watch your system panic when kget does a: sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); where len has been properly fetched in a previous syctlbyname() call (1526 bytes, in my test case) and buf allocated appropriately. System will panic with a supervisor read, page not present. In fact, I've just proven the hard way that trying to read machdep.uc_devlist in any way, including sysctl -a, does the same thing. Wurgh. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 6:23: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailme.wirehub.nl (smtp.wirehub.nl [195.86.25.80]) by hub.freebsd.org (Postfix) with ESMTP id 5AE9714FD4; Fri, 7 May 1999 06:22:56 -0700 (PDT) (envelope-from robertj@wirehub.nl) Received: from default (ip195-86-48-70.dyn.wirehub.net [195.86.48.70]) by mailme.wirehub.nl (8.8.8/8.8.8) with SMTP id PAA26501; Fri, 7 May 1999 15:21:46 +0200 (CEST) Message-Id: <4.1.19990507151648.0459a9f0@mail.wirehub.nl> X-Sender: robertj@mail.wirehub.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 07 May 1999 15:19:01 +0200 To: tech@openbsd.org From: Robert Joosten Subject: [offtopic] proposal nl.comp.os.unix.bsd Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG, netbsd-users@netbsd.org, tech@openbsd.org, bsdi-users@bsdi.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, At first, please accept my apologizes for this off-topic posting. Today, I posted RFD-1 nl.comp.os.unix.bsd in nl.newsgroups. I hope to meet interested participants overthere. Kind regards, Robert Joosten. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 6:49: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BF63514DC6 for ; Fri, 7 May 1999 06:49:00 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id GAA99204 for ; Fri, 7 May 1999 06:49:31 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-reply-to: Your message of "Fri, 07 May 1999 05:58:41 PDT." <96660.926081921@zippy.cdrom.com> Date: Fri, 07 May 1999 06:49:31 -0700 Message-ID: <99200.926084971@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); Sorry for the vague first bug report; I hadn't collected a reasonable crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically where it copies id->id_driver->name into a temporary stack variable. First time through, this thing's NULL and *boom* we're gone. I'm looking into it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 7:20:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id C15FF14F8A for ; Fri, 7 May 1999 07:20:19 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id JAA05761; Fri, 7 May 1999 09:20:11 -0500 (CDT) From: Kevin Day Message-Id: <199905071420.JAA05761@home.dragondata.com> Subject: Re: -current deadlocks within 5 mins, over NFS In-Reply-To: <199905070817.DAA15632@home.dragondata.com> from Kevin Day at "May 7, 1999 3:17:46 am" To: toasty@home.dragondata.com (Kevin Day) Date: Fri, 7 May 1999 09:20:09 -0500 (CDT) Cc: dillon@backplane.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Matt, I told you about this before, but completely forgot about it. After > doing considerable testing on my test servers, i thought -current was safe > enough to try on our production shell servers. I installed -current on one > of my servers, and to my dismay, it hung. :) > > Within 5 minutes of running, nearly every process is blocked on 'inode', > with the exception of a single 'cp' stuck in vmopar. > Just to add more to this, before someone replies. Ran all night, still hasn't crashed. On my test system, if I add that cron job back, it dies very quickly, so this shouldn't be hard to reproduce to someone who needs it. -current sources grabbed last night. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 7:21:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw3adm.rcsntx.swbell.net (mail-gw3.rcsntx.swbell.net [151.164.30.53]) by hub.freebsd.org (Postfix) with ESMTP id C4D5414D86 for ; Fri, 7 May 1999 07:21:09 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-9-69.hstntx.swbell.net [207.193.9.69]) by mail-gw3adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id JAA21710; Fri, 7 May 1999 09:20:40 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id JAA01101; Fri, 7 May 1999 09:21:59 -0500 (CDT) (envelope-from chris) Date: Fri, 7 May 1999 09:21:57 -0500 From: Chris Costello To: Amancio Hasty Cc: Andreas Braukmann , freebsd-current@FreeBSD.ORG Subject: Re: just pulled the egcs-switch Message-ID: <19990507092157.B580@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990507094730.A457@paert.tse-online.de> <199905070810.BAA26647@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i In-Reply-To: <199905070810.BAA26647@rah.star-gate.com>; from Amancio Hasty on Fri, May 07, 1999 at 01:10:31AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 7, 1999, Amancio Hasty wrote: > Is not a good idea to use the default egcs as it is configured to compile > c++ programs which use threads and exceptions for instance Netscape's > Eletrical Fire (A Java VM/Compiler) does not work. Why not? I constantly compile C++ (and lately, objective C) with the default egcs shipped with FreeBSD. > > > -- > > Amancio Hasty > hasty@star-gate.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Chris Costello This time it will surely run. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 7:33:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from work.mzaki.nom (82.pool15.tokyo.att.ne.jp [165.76.220.97]) by hub.freebsd.org (Postfix) with ESMTP id 68C4714D92; Fri, 7 May 1999 07:33:39 -0700 (PDT) (envelope-from mzaki@e-mail.ne.jp) Received: from localhost (localhost [127.0.0.1]) by work.mzaki.nom (8.9.2/8.9.2) with ESMTP id XAA09348; Fri, 7 May 1999 23:33:39 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) To: current@freebsd.org, stable@freebsd.org Subject: Unicode support for Joliet CDs X-Mailer: Mew version 1.94b7 on XEmacs 21.0 (20 minutes to Nikko) X-fingerprint: BD 86 CD D9 66 FD 75 B0 A8 43 4B C4 E2 1B F5 B5 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990507233339A.mzaki@e-mail.ne.jp> Date: Fri, 07 May 1999 23:33:39 +0900 From: Motomichi Matsuzaki X-Dispatcher: imput version 990212(IM106) Lines: 21 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unicode support patch for -current and -stable is now updated. See http://triaez.kaisei.org/~mzaki/joliet/ # It's not intended to merge into the repository. CHANGES: * By default, filenames are encode by UTF-8, not converted to any charset. * Add support for ISO-8859-2 and KOI8-R. * Add kernel config option CHARSET_*. They are to specify the conversion tables you need. -- Motomichi Matsuzaki Dept. of Biological Science, Fuculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 9:11:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt051nc7.san.rr.com (dt051nc7.san.rr.com [204.210.32.199]) by hub.freebsd.org (Postfix) with ESMTP id 09DE314A09 for ; Fri, 7 May 1999 09:11:46 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from localhost (doug@localhost) by dt051nc7.san.rr.com (8.8.8/8.8.8) with ESMTP id JAA29115 for ; Fri, 7 May 1999 09:11:45 -0700 (PDT) (envelope-from Studded@gorean.org) Date: Fri, 7 May 1999 09:11:45 -0700 (PDT) From: Studded X-Sender: doug@dt051nc7.san.rr.com To: freebsd-current@freebsd.org Subject: Version 1.23 of mergemaster available for gamma test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Since several of the people who've asked for changes to mergemaster are on this list I thought I'd give y'all first crack at the new version. I've incorporated the suggestions I've received over the last 6 months, including a fix for the dreaded PAGER problem. You can retrieve a production-ready version by doing: 'fetch http://home.san.rr.com/freebsd/mergemaster-1.23.tgz' I would appreciate it if those of you using freebsd 3.x or -current would give it a go since I don't think I'll get my test system updated before the ports freeze (on the 10th, yes?). Of course, comments and suggestions are welcome. Selected comments from my RCS log are below. Enjoy, Doug -- *** Chief Operations Officer, DALnet IRC network *** Nominated for quote of the year is the statement made by Representative Dick Armey (Texas), who when asked if he were in the President's place, would he resign, responded: "If I were in the President's place I would not get a chance to resign. I would be lying in a pool of my own blood hearing Mrs. Armey standing over me saying, 'How do I reload this damn thing?'" revision 1.23 move mm_install function declaration out of the loop, duh add pwd_mkdb reminder if user installs new master.passwd ---------------------------- revision 1.22 rm the temp versions of /etc/spwd.db /etc/passwd and /etc/pwd.db before the comparison starts since comparing them is bogus anyway ---------------------------- revision 1.21 fix the order of the PAGER tests add listing of files only in /etc to -v option ---------------------------- revision 1.20 skip the umask test if it's an autorun since we won't be installing anything ---------------------------- revision 1.19 Fix some style nits Add fatal error for the case where any part of make'ing /usr/src/etc fails ---------------------------- revision 1.18 Fix problem of PAGER not in PATH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 9:16:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 7226315273 for ; Fri, 7 May 1999 09:15:49 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 3EFE21F72; Sat, 8 May 1999 00:15:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-reply-to: Your message of "Fri, 07 May 1999 06:49:31 MST." <99200.926084971@zippy.cdrom.com> Date: Sat, 08 May 1999 00:15:36 +0800 From: Peter Wemm Message-Id: <19990507161541.3EFE21F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); > > Sorry for the vague first bug report; I hadn't collected a reasonable > crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically > where it copies id->id_driver->name into a temporary stack variable. > First time through, this thing's NULL and *boom* we're gone. I'm > looking into it. Urk. You are right. The problem is that id_driver is a wild pointer. It was pointing to an entry in a malloc'ed array that was built to make isadev->id_driver->name work for userconfig. After the exit of userconfig, these tables are freed up, but the uc_devlist stuff still contains a pointer to the original &isa_drvtab[i]; which is long gone... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 9:49:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AA07814D0F for ; Fri, 7 May 1999 09:49:50 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA45656; Fri, 7 May 1999 09:49:36 -0700 (PDT) (envelope-from dillon) Date: Fri, 7 May 1999 09:49:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199905071649.JAA45656@apollo.backplane.com> To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -current deadlocks within 5 mins, over NFS References: <199905070817.DAA15632@home.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matt, I told you about this before, but completely forgot about it. After :doing considerable testing on my test servers, i thought -current was safe :enough to try on our production shell servers. I installed -current on one :of my servers, and to my dismay, it hung. :) : :Within 5 minutes of running, nearly every process is blocked on 'inode', :with the exception of a single 'cp' stuck in vmopar. : :I have a very silly, *very* poorly written script i run out of cron, every :10 mins or so, to update my passwd and group files. : :#/bin/sh :... : :What more info do you need for help in debugging this? : :Kevin This is great! Just what I've been looking for! I'll try to reproduce the lockup today. If it is stuck in vmopar I already have a good idea about what is going on. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 10:11:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id DB4B614D6D for ; Fri, 7 May 1999 10:11:03 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id DFF581F72; Sat, 8 May 1999 01:11:01 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-reply-to: Your message of "Fri, 07 May 1999 06:49:31 MST." <99200.926084971@zippy.cdrom.com> Date: Sat, 08 May 1999 01:11:01 +0800 From: Peter Wemm Message-Id: <19990507171102.DFF581F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); > > Sorry for the vague first bug report; I hadn't collected a reasonable > crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically > where it copies id->id_driver->name into a temporary stack variable. > First time through, this thing's NULL and *boom* we're gone. I'm > looking into it. Should be fixed as of a few minutes ago in userconfig.c: ---------------------------- revision 1.140 date: 1999/05/07 16:54:50; author: peter; state: Exp; lines: +34 -2 Yet another kludge to maintain the isa_device illusion, this time malloc an isa_driver and name pointer so the uc_devlist sysctl can get to it. ---------------------------- Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 11:32:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CE7F4151A1 for ; Fri, 7 May 1999 11:32:03 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA13362; Sat, 8 May 1999 03:32:00 +0900 (JST) Message-ID: <37332985.4521DB82@newsguy.com> Date: Sat, 08 May 1999 02:57:25 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Motomichi Matsuzaki Cc: current@FreeBSD.ORG Subject: Re: Unicode support for Joliet CDs References: <19990507233339A.mzaki@e-mail.ne.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Motomichi Matsuzaki wrote: > > Unicode support patch for -current and -stable is now updated. > > See http://triaez.kaisei.org/~mzaki/joliet/ > > # It's not intended to merge into the repository. > > CHANGES: > > * By default, filenames are encode by UTF-8, not converted to any charset. BTW, some people mentioned losing case in Joliet names. Is/was this caused by the convertion? Is it fixed in this version? > * Add support for ISO-8859-2 and KOI8-R. > > * Add kernel config option CHARSET_*. > They are to specify the conversion tables you need. And how about selecting the charset to be used? Does this still goes through sysctl, did you get it on a mount option as I suggested, or what? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness if that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 11:49:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 86D4115219 for ; Fri, 7 May 1999 11:49:15 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id OAA15984; Fri, 7 May 1999 14:10:36 -0500 (EST) Date: Fri, 7 May 1999 14:10:34 -0500 (EST) From: Alfred Perlstein To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: bridge+dummynet + "sysctl -a" panics in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 May 1999, Alfred Perlstein wrote: > On Mon, 3 May 1999, Luigi Rizzo wrote: > > > > a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in, > > > doing a "sysctl -a" will panic the box. (currproc == sysctl) > > > > if you think the panic is bridge-related, can you try manually the > > net.link.ether.bridge* sysctl -- if they do not fail, then the problem > > could be with the sysctl to fetch bridging statistics (and if you have > > a recent system, "netstat -p bdg" should exercise that. > > > > ok, egg in my face, that's not it i guess. What about patching rc.network > to allow early setup of bridge though? > > I'll try to track this down a bit better... > > I was experianceing it the panic earlier when i had applied matt's NFS patches, however ,my > other boxes don't panic when i sysctl -a. just a follow-up, Jordan experianced the same bug and tracked it down, I think Peter Wemm fixed it. it was something with isa+sysctl, and not bridge related, sorry. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 11:54:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id D203B14BC9 for ; Fri, 7 May 1999 11:54:19 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id LAA29786; Fri, 7 May 1999 11:53:56 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199905071853.LAA29786@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: chris@calldei.com Cc: Andreas Braukmann , freebsd-current@FreeBSD.ORG Subject: Re: just pulled the egcs-switch In-reply-to: Your message of "Fri, 07 May 1999 09:21:57 CDT." <19990507092157.B580@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 May 1999 11:53:56 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG By all means see if threaded apps with exceptions work with the base installed egcs . I pointed out an application which does not work, care to give an example of a threaded / exception application which works with the base egcs compiler? -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 13: 7:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B9C0414CFB for ; Fri, 7 May 1999 13:07:15 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA14069 for ; Fri, 7 May 1999 21:07:20 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 7 May 1999 21:07:20 +0100 (BST) From: Doug Rabson To: current@freebsd.org Subject: Debugging FreeBSD user threads with gdb Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just implemented a new target for gdb-4.18 which allows programs which use FreeBSD's user threads library to be effectively debugged. The new target automatically detects the presence of user threads when a program is started or attached to and examined using the gdb commands 'info thread' and 'thread'. To allow individual threads to be distinguished from gdb, I had to make the following minor change to uthread. Unless anyone has any objections, I will be committing this change and the new gdb target into -current. Index: pthread_private.h =================================================================== RCS file: /home/ncvs/src/lib/libc_r/uthread/pthread_private.h,v retrieving revision 1.17 diff -u -r1.17 pthread_private.h --- pthread_private.h 1999/03/23 05:07:54 1.17 +++ pthread_private.h 1999/05/06 15:26:53 @@ -420,6 +420,7 @@ #define PTHREAD_MAGIC ((u_int32_t) 0xd09ba115) u_int32_t magic; char *name; + int tid; /* for gdb */ /* * Lock for accesses to this thread structure. Index: uthread_create.c =================================================================== RCS file: /home/ncvs/src/lib/libc_r/uthread/uthread_create.c,v retrieving revision 1.12 diff -u -r1.12 uthread_create.c --- uthread_create.c 1999/03/23 05:07:55 1.12 +++ uthread_create.c 1999/05/06 15:27:33 @@ -42,6 +42,8 @@ #include "pthread_private.h" #include "libc_private.h" +static int next_tid = 1; + int pthread_create(pthread_t * thread, const pthread_attr_t * attr, void *(*start_routine) (void *), void *arg) @@ -87,6 +89,7 @@ } else { /* Initialise the thread structure: */ memset(new_thread, 0, sizeof(struct pthread)); + new_thread->tid = next_tid++; new_thread->slice_usec = -1; new_thread->sig_saved = 0; new_thread->stack = stack; -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 13:11: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1416C154EC for ; Fri, 7 May 1999 13:10:56 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA46817; Fri, 7 May 1999 13:10:47 -0700 (PDT) (envelope-from dillon) Date: Fri, 7 May 1999 13:10:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199905072010.NAA46817@apollo.backplane.com> To: Doug Rabson Cc: current@FreeBSD.ORG Subject: Re: Debugging FreeBSD user threads with gdb References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :--- uthread_create.c 1999/03/23 05:07:55 1.12 :+++ uthread_create.c 1999/05/06 15:27:33 :@@ -42,6 +42,8 @@ : #include "pthread_private.h" : #include "libc_private.h" : :+static int next_tid = 1; :+ : int : pthread_create(pthread_t * thread, const pthread_attr_t * attr, : void *(*start_routine) (void *), void *arg) :@@ -87,6 +89,7 @@ : } else { : /* Initialise the thread structure: */ : memset(new_thread, 0, sizeof(struct pthread)); :+ new_thread->tid = next_tid++; : :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 Hmmm. tid is only an int and some programs which create and destroy threads a lot are almost certainly going to overflow it. 4 billion is not hard to reach. This can result in duplicate tid's. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 13:19:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 3B9E3153DC for ; Fri, 7 May 1999 13:19:35 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id QAA90892 for current@freebsd.org; Fri, 7 May 1999 16:19:35 -0400 (EDT) (envelope-from mi) Message-Id: <199905072019.QAA90892@misha.cisco.com> Subject: Re: Debugging FreeBSD user threads with gdb In-Reply-To: <199905072010.NAA46817@apollo.backplane.com> from Matthew Dillon at "May 7, 1999 01:10:47 pm" To: current@freebsd.org Date: Fri, 7 May 1999 16:19:35 -0400 (EDT) Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon once wrote: > Hmmm. tid is only an int and some programs which create and destroy > threads a lot are almost certainly going to overflow it. 4 billion > is not hard to reach. This can result in duplicate tid's. Unsigned will double that. Not enough either? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 13:21:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 90534155D8 for ; Fri, 7 May 1999 13:21:38 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA00344; Fri, 7 May 1999 13:21:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-reply-to: Your message of "Sat, 08 May 1999 01:11:01 +0800." <19990507171102.DFF581F72@spinner.netplex.com.au> Date: Fri, 07 May 1999 13:21:53 -0700 Message-ID: <340.926108513@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Should be fixed as of a few minutes ago in userconfig.c: > ---------------------------- > revision 1.140 > date: 1999/05/07 16:54:50; author: peter; state: Exp; lines: +34 -2 > Yet another kludge to maintain the isa_device illusion, this time malloc > an isa_driver and name pointer so the uc_devlist sysctl can get to it. > ---------------------------- Yay! Thanks, I fell asleep as it was anyway. :) Man, I spent hours on this one first thinking it was my kget() routine in sysinstall blowing things up. Oh well, at least it made me review the code. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 13:26:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7D511155BA for ; Fri, 7 May 1999 13:26:26 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA15807; Fri, 7 May 1999 21:26:46 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 7 May 1999 21:26:46 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Debugging FreeBSD user threads with gdb In-Reply-To: <199905072010.NAA46817@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 May 1999, Matthew Dillon wrote: > :--- uthread_create.c 1999/03/23 05:07:55 1.12 > :+++ uthread_create.c 1999/05/06 15:27:33 > :@@ -42,6 +42,8 @@ > : #include "pthread_private.h" > : #include "libc_private.h" > : > :+static int next_tid = 1; > :+ > : int > : pthread_create(pthread_t * thread, const pthread_attr_t * attr, > : void *(*start_routine) (void *), void *arg) > :@@ -87,6 +89,7 @@ > : } else { > : /* Initialise the thread structure: */ > : memset(new_thread, 0, sizeof(struct pthread)); > :+ new_thread->tid = next_tid++; > : > :Doug Rabson Mail: dfr@nlsystems.com > :Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > Hmmm. tid is only an int and some programs which create and destroy > threads a lot are almost certainly going to overflow it. 4 billion > is not hard to reach. This can result in duplicate tid's. Didn't think of that. It gets a bit ugly inside gdb since gdb needs a single int to encode the pid and thread id. I'm currently allowing 20 bits for the pid and 11 for the tid. Any ideas? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 13:37: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 43F6514CB9 for ; Fri, 7 May 1999 13:36:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA47016; Fri, 7 May 1999 13:36:51 -0700 (PDT) (envelope-from dillon) Date: Fri, 7 May 1999 13:36:51 -0700 (PDT) From: Matthew Dillon Message-Id: <199905072036.NAA47016@apollo.backplane.com> To: Doug Rabson Cc: current@FreeBSD.ORG Subject: Re: Debugging FreeBSD user threads with gdb References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :--- uthread_create.c 1999/03/23 05:07:55 1.12 :> :+++ uthread_create.c 1999/05/06 15:27:33 :> :@@ -42,6 +42,8 @@ :> : #include "pthread_private.h" :> : #include "libc_private.h" :> : :> :+static int next_tid = 1; :> :+ :> : int :> : pthread_create(pthread_t * thread, const pthread_attr_t * attr, :> : void *(*start_routine) (void *), void *arg) :> :@@ -87,6 +89,7 @@ :> : } else { :> : /* Initialise the thread structure: */ :> : memset(new_thread, 0, sizeof(struct pthread)); :> :+ new_thread->tid = next_tid++; :> : :> :Doug Rabson Mail: dfr@nlsystems.com :> :Nonlinear Systems Ltd. Phone: +44 181 442 9037 :> :> Hmmm. tid is only an int and some programs which create and destroy :> threads a lot are almost certainly going to overflow it. 4 billion :> is not hard to reach. This can result in duplicate tid's. : :Didn't think of that. It gets a bit ugly inside gdb since gdb needs a :single int to encode the pid and thread id. I'm currently allowing 20 :bits for the pid and 11 for the tid. Any ideas? : :-- :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 Hmmm. 11 bits is only 2048 threads. You are going to have problems no matter what. You could have a pool of tid structures. A simple freelist. Pseudo code below. This would fix the unique-tid problem but it would not fix the 2048 thread limit with gdb. #define TIDINCR 32 struct tid { struct tid *t_next; int t_tid; }; int maxtid = 1; struct tid *tidpool; struct tid * alloctid(void) { struct tid *tid; while ((tid = tidpool) == NULL) { int i; tidpool = malloc(sizeof(struct tid) * TIDINCR); if (tidpool == NULL) { ... memory allocation failed ... } for (i = 0; i < TIDINCR; ++i) { tidpool[i].t_tid = maxtid + i; tidpool[i].t_next = &tidpool[i+1]; } tidpool[i-1].t_next = NULL; maxtid += TIDINCR; } tidpool = tid->t_next; return(tid); } freetid(struct tid *tid) { tid->t_next = tidpool; tidpool = tid; } -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 13:53:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (Postfix) with ESMTP id 78F8F155CE for ; Fri, 7 May 1999 13:53:03 -0700 (PDT) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id WAA03738 for ; Fri, 7 May 1999 22:53:01 +0200 (CEST) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.8.5) with ESMTP id WAA18539 for ; Fri, 7 May 1999 22:53:01 +0200 (MET DST) Message-Id: <199905072053.WAA18539@trantor.xs4all.nl> X-Mailer: exmh version 2.0.3 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: sio.c breaks kernel ( even GENERIC) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 May 1999 22:53:00 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't been able to get a kernel built because of some undefined references in sio.o. Even GENERIC is broken. (cvsupped just a few minutes ago ) loading kernel sio.o: In function `siocnprobe': sio.o(.text+0x286e): undefined reference to `gdbdev' sio.o(.text+0x2874): undefined reference to `gdb_getc' sio.o(.text+0x287e): undefined reference to `gdb_putc' sio.o(.text+0x2895): undefined reference to `gdbdev' sio.o(.text+0x28c9): undefined reference to `gdbdev' sio.o(.text+0x28cf): undefined reference to `gdb_getc' sio.o(.text+0x28d9): undefined reference to `gdb_putc' *** Error code 1 Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 13:58:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 05BA314F53 for ; Fri, 7 May 1999 13:58:11 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA17398; Fri, 7 May 1999 21:58:33 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 7 May 1999 21:58:32 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Debugging FreeBSD user threads with gdb In-Reply-To: <199905072036.NAA47016@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 May 1999, Matthew Dillon wrote: > :> :--- uthread_create.c 1999/03/23 05:07:55 1.12 > :> :+++ uthread_create.c 1999/05/06 15:27:33 > :> :@@ -42,6 +42,8 @@ > :> : #include "pthread_private.h" > :> : #include "libc_private.h" > :> : > :> :+static int next_tid = 1; > :> :+ > :> : int > :> : pthread_create(pthread_t * thread, const pthread_attr_t * attr, > :> : void *(*start_routine) (void *), void *arg) > :> :@@ -87,6 +89,7 @@ > :> : } else { > :> : /* Initialise the thread structure: */ > :> : memset(new_thread, 0, sizeof(struct pthread)); > :> :+ new_thread->tid = next_tid++; > :> : > :> :Doug Rabson Mail: dfr@nlsystems.com > :> :Nonlinear Systems Ltd. Phone: +44 181 442 9037 > :> > :> Hmmm. tid is only an int and some programs which create and destroy > :> threads a lot are almost certainly going to overflow it. 4 billion > :> is not hard to reach. This can result in duplicate tid's. > : > :Didn't think of that. It gets a bit ugly inside gdb since gdb needs a > :single int to encode the pid and thread id. I'm currently allowing 20 > :bits for the pid and 11 for the tid. Any ideas? > : > :-- > :Doug Rabson Mail: dfr@nlsystems.com > :Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > Hmmm. 11 bits is only 2048 threads. You are going to have problems > no matter what. > > You could have a pool of tid structures. A simple freelist. Pseudo > code below. This would fix the unique-tid problem but it would not fix > the 2048 thread limit with gdb. I can probably increase the field size of the tid up to about 14 bits (we only have pids going up to 100000 I think). I would rather not do this amount of work inside uthread; perhaps it would be better to make the uthread store a 64bit unique number and then compress it down to a 14 bit tid inside gdb by keeping a hash table or something similar. Its going to be pretty hard to debug a program with 16k active threads so I think this limit should be ok. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 14:22: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id BD0F414D8D for ; Fri, 7 May 1999 14:21:58 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 4A55718D0; Fri, 7 May 1999 23:21:56 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 4724B49D3; Fri, 7 May 1999 23:21:56 +0200 (CEST) Date: Fri, 7 May 1999 23:21:52 +0200 (CEST) From: Andrzej Bialecki To: Peter Wemm Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-Reply-To: <19990507171102.DFF581F72@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 May 1999, Peter Wemm wrote: > "Jordan K. Hubbard" wrote: > > > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); > > > > Sorry for the vague first bug report; I hadn't collected a reasonable > > crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically > > where it copies id->id_driver->name into a temporary stack variable. > > First time through, this thing's NULL and *boom* we're gone. I'm > > looking into it. > > Should be fixed as of a few minutes ago in userconfig.c: > ---------------------------- > revision 1.140 > date: 1999/05/07 16:54:50; author: peter; state: Exp; lines: +34 -2 > Yet another kludge to maintain the isa_device illusion, this time malloc > an isa_driver and name pointer so the uc_devlist sysctl can get to it. > ---------------------------- Neither you nor I seem to be happy with the fix. When I added this sysctl, I only wanted to somehow get to the list of changes from UserConfig without poking around through kmem. Now, when the changes in the way devices are registered are introduced, we can think of something else which could be better suited. For now the only programs that need it are kget and sysinstall. (i.e. it's still easy to change, if we know what we want.. :-) Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 14:33:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.30]) by hub.freebsd.org (Postfix) with ESMTP id ED89F1511D for ; Fri, 7 May 1999 14:33:20 -0700 (PDT) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id VAA02439 for current@freebsd.org; Fri, 7 May 1999 21:32:49 GMT (envelope-from zach) Date: Fri, 7 May 1999 16:32:49 -0500 From: Zach Heilig To: current@freebsd.org Subject: Disappearing/Reappearing Files... Message-ID: <19990507163249.A2406@k6n1.znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an example of what I just noticed: $ ls aaa bbb ccc $ cp aaa bbb $ ls aaa ccc [ !!!, then a couple seconds later: ] $ ls aaa bbb ccc [a few (>5) minutes later in a different vty: ] $ cd problem_dir $ ls aaa ccc [ ugh.. ] $ ls aaa bbb ccc [this is a filesystem with soft-updates on] -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 14:40:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 99D5D151EE for ; Fri, 7 May 1999 14:40:02 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id BFB0E1F72; Sat, 8 May 1999 05:39:58 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-reply-to: Your message of "Fri, 07 May 1999 23:21:52 +0200." Date: Sat, 08 May 1999 05:39:58 +0800 From: Peter Wemm Message-Id: <19990507213959.BFB0E1F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Sat, 8 May 1999, Peter Wemm wrote: > > > "Jordan K. Hubbard" wrote: > > > > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); > > > > > > Sorry for the vague first bug report; I hadn't collected a reasonable > > > crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically > > > where it copies id->id_driver->name into a temporary stack variable. > > > First time through, this thing's NULL and *boom* we're gone. I'm > > > looking into it. > > > > Should be fixed as of a few minutes ago in userconfig.c: > > ---------------------------- > > revision 1.140 > > date: 1999/05/07 16:54:50; author: peter; state: Exp; lines: +34 -2 > > Yet another kludge to maintain the isa_device illusion, this time malloc > > an isa_driver and name pointer so the uc_devlist sysctl can get to it. > > ---------------------------- > > Neither you nor I seem to be happy with the fix. When I added this sysctl, > I only wanted to somehow get to the list of changes from UserConfig > without poking around through kmem. Now, when the changes in the way > devices are registered are introduced, we can think of something else > which could be better suited. For now the only programs that need it are > kget and sysinstall. (i.e. it's still easy to change, if we know what we > want.. :-) > > Andrzej Bialecki Well, `the' fix will be to have a mechanism for passing hints from the loader and letting userconfig update them in the hints database. The hints database isn't up to it yet, it's only just barely dynamic and could probably do with more automatic integration with the bus engine. I'm not too keen to jump in too soon and update userconfig to use an interface (resource_*) that is almost certain to change. As an interim though, it might be better to create a struct that holds the key information that used to be isa_device and use that for the import/ export mechanism for userconfig until we have a clearer idea what userconfig should look like in the end. It's interesting that the ANSI emulation in loader(8) is good enough to do full-screen displays. It still seems to make sense to move userconfig-like functionality into the pre-kernel stages including moving config(8)'s hints to a loaded and parsed file. Forth, bah.. :-] Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 16:31: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (Postfix) with ESMTP id 7B5DD152AA for ; Fri, 7 May 1999 16:30:58 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id RAA00595; Fri, 7 May 1999 17:29:44 -0600 (MDT) (envelope-from drussell@saturn-tech.com) Date: Fri, 7 May 1999 17:29:44 -0600 (MDT) From: Doug Russell To: Paul van der Zwan Cc: freebsd-current@FreeBSD.ORG Subject: Re: sio.c breaks kernel ( even GENERIC) In-Reply-To: <199905072053.WAA18539@trantor.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 May 1999, Paul van der Zwan wrote: > I haven't been able to get a kernel built because of some undefined references > in sio.o. Even GENERIC is broken. > (cvsupped just a few minutes ago ) > > loading kernel > sio.o: In function `siocnprobe': > sio.o(.text+0x286e): undefined reference to `gdbdev' > sio.o(.text+0x2874): undefined reference to `gdb_getc' > sio.o(.text+0x287e): undefined reference to `gdb_putc' > sio.o(.text+0x2895): undefined reference to `gdbdev' > sio.o(.text+0x28c9): undefined reference to `gdbdev' > sio.o(.text+0x28cf): undefined reference to `gdb_getc' > sio.o(.text+0x28d9): undefined reference to `gdb_putc' > *** Error code 1 I've supped many times in the past 18 hours or so and I also get the above error trying to compile a kernel. My world also still fails at: ===> usr.bin/kdump /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c In file included from :47: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition rm -f .depend mkdep -f .depend -a -nostdinc -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include /usr/src/usr.bin/kdump/kdump.c ioctl.c /usr/src/usr.bin/kdump/../ktrace/subr.c ioctl.c:7: sys/disk.h: No such file or directory In file included from ioctl.c:76: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition mkdep: compile failed *** Error code 1 Stop. If I go to /usr/src/usr.bin/kdump and 'make depend', it gives me the same warnings, but it works... Then if I continue my world with a -DNOCLEAN, it fails at usr.bin/truss with a similar error. If I make depend there as well, the world completes.... Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 17:18:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id DE6D014C0A for ; Fri, 7 May 1999 17:18:19 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA03486; Sat, 8 May 1999 10:18:09 +1000 Date: Sat, 8 May 1999 10:18:09 +1000 From: Bruce Evans Message-Id: <199905080018.KAA03486@godzilla.zeta.org.au> To: drussell@saturn-tech.com, paulz@trantor.xs4all.nl Subject: Re: sio.c breaks kernel ( even GENERIC) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> sio.o(.text+0x28cf): undefined reference to `gdb_getc' >> sio.o(.text+0x28d9): undefined reference to `gdb_putc' >> *** Error code 1 > >I've supped many times in the past 18 hours or so and I also get the >above error trying to compile a kernel. My world also still fails at: Quick fix: configure DDB. Correct fix: add ifdefs to sio.c so that debugger support is not compiled unless debugging is configured. >===> usr.bin/kdump >/bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c >In file included from :47: >/usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' >redefined >/usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is >the location of the previous definition memrange.h is broken. >rm -f .depend >mkdep -f .depend -a -nostdinc -I/usr/src/usr.bin/kdump/../ktrace >-I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include >/usr/src/usr.bin/kdump/kdump.c ioctl.c >/usr/src/usr.bin/kdump/../ktrace/subr.c >ioctl.c:7: sys/disk.h: No such file or directory >In file included from ioctl.c:76: >/usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' >redefined >/usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is >the location of the previous definition >mkdep: compile failed >*** Error code 1 The Makefile is not smart enough to know that it should rebuild dependencies when one of the [indirect] source files went away. >If I go to /usr/src/usr.bin/kdump and 'make depend', it gives me the same >warnings, but it works... Then if I continue my world with a -DNOCLEAN, >it fails at usr.bin/truss with a similar error. If I make depend there as >well, the world completes.... Don't use -DNOCLEAN; it gives precisely this type of error when headers go away. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 17:59:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from work.mzaki.nom (17.pool15.tokyo.att.ne.jp [165.76.220.32]) by hub.freebsd.org (Postfix) with ESMTP id 4BE0F14EA7 for ; Fri, 7 May 1999 17:59:42 -0700 (PDT) (envelope-from mzaki@e-mail.ne.jp) Received: from localhost (localhost [127.0.0.1]) by work.mzaki.nom (8.9.2/8.9.2) with ESMTP id JAA13878; Sat, 8 May 1999 09:59:36 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) To: dcs@newsguy.com Cc: current@FreeBSD.ORG Subject: Re: Unicode support for Joliet CDs In-Reply-To: <37332985.4521DB82@newsguy.com> References: <19990507233339A.mzaki@e-mail.ne.jp> <37332985.4521DB82@newsguy.com> X-Mailer: Mew version 1.94b7 on XEmacs 21.0 (20 minutes to Nikko) X-fingerprint: BD 86 CD D9 66 FD 75 B0 A8 43 4B C4 E2 1B F5 B5 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990508095935N.mzaki@e-mail.ne.jp> Date: Sat, 08 May 1999 09:59:35 +0900 From: Motomichi Matsuzaki X-Dispatcher: imput version 990212(IM106) Lines: 50 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Daniel C. Sobral" Subject: Re: Unicode support for Joliet CDs Date: Sat, 08 May 1999 02:57:25 +0900 dcs> > Unicode support patch for -current and -stable is now updated. dcs> BTW, some people mentioned losing case in Joliet names. Is/was this dcs> caused by the convertion? Is it fixed in this version? I have noticed this problem right now. Following is the patch for -current and -stable: --- /usr/src/sys/isofs/cd9660/cd9660_util.c Sun Apr 25 02:53:58 1999 +++ /tmp/cd9660_util.c Sat May 8 09:20:44 1999 @@ -162,7 +162,7 @@ for (; infn != infnend; fnidx++) { infn += isochar(infn, infnend, joliet_level, &c); - if (!original && c >= 'A' && c <= 'Z') + if (!original && !joliet_level && c >= 'A' && c <= 'Z') *outfn++ = c + ('a' - 'A'); else if (!original && c == ';') { fnidx -= (d == '.'); I will change my Unicode patch as the same. dcs> > * Add kernel config option CHARSET_*. dcs> > They are to specify the conversion tables you need. dcs> dcs> And how about selecting the charset to be used? Does this still goes dcs> through sysctl, did you get it on a mount option as I suggested, or dcs> what? Not yet, still 'sysctl'. # I feel that adding conversion tables to kernel is ad hoc way. # The BIG5 encoding is not filesystem-safe so that # some userland supports is neccesary for zh_TW.BIG5. # It is as the same for ja_JP.SJIS. # Then, kernel should pass Unicode to userland as UTF-8 encoded, # and we should make proper I18N on whole FreeBSD. # ... confused. -- Motomichi Matsuzaki Dept. of Biological Science, Fuculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 18:20:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 8962E1545F for ; Fri, 7 May 1999 18:20:08 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id SAA80654; Fri, 7 May 1999 18:18:27 -0700 (PDT) Date: Fri, 7 May 1999 18:18:26 -0700 (PDT) From: Julian Elischer To: Zach Heilig Cc: current@FreeBSD.ORG Subject: Re: Disappearing/Reappearing Files... In-Reply-To: <19990507163249.A2406@k6n1.znh.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG is this reproducible for you? On Fri, 7 May 1999, Zach Heilig wrote: > This is an example of what I just noticed: > > $ ls > aaa bbb ccc > $ cp aaa bbb > $ ls > aaa ccc > [ !!!, then a couple seconds later: ] > $ ls > aaa bbb ccc > > [a few (>5) minutes later in a different vty: ] > $ cd problem_dir > $ ls > aaa ccc > [ ugh.. ] > $ ls > aaa bbb ccc > > [this is a filesystem with soft-updates on] > > -- > Zach Heilig > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 18:33:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 98AE2153A3 for ; Fri, 7 May 1999 18:33:10 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id VAA11585 for ; Fri, 7 May 1999 21:33:09 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA08645; Fri, 7 May 1999 21:32:39 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id VAA80459 for freebsd-current@freebsd.org; Fri, 7 May 1999 21:32:38 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905080132.VAA80459@bb01f39.unx.sas.com> Subject: make world problem (just me?) warning: `MDF_ACTIVE' redefined To: freebsd-current@freebsd.org Date: Fri, 7 May 1999 21:32:38 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've had the following problem for the last 36 hours or so. I haven't seen any fixes related to this. Has anyone else seen the following, or is my tree somehow messed up? Thanks! John ===> usr.bin/kdump cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c In file included from :47: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c ioctl.c:7: sys/disk.h: No such file or directory In file included from ioctl.c:76: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 22:16: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id C71151513F for ; Fri, 7 May 1999 22:15:56 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id WAA23454 for ; Fri, 7 May 1999 22:15:55 -0700 (PDT) Message-ID: <3733C85B.5ACA8F4A@seattleu.edu> Date: Fri, 07 May 1999 22:15:07 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: tosha after CAM changes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having trouble using tosha after the CAM changes, I updated source early this morning (around 7:00 PDT 5/7/1999) including ports, then make deinstall make distclean in /usr/ports/audio/tosha then make && make install and tosha, and now tosha gives me (as root): #tosha -t1 tosha: cam_lookup_pas: CAMGETPASSTHRU ioctl failed cam_lookup_pass: Inappropriate ioctl for device This is using a Teac CD-532S CD-ROM (SCSI2) attached to an onboard AIC-7890 on an ASUS P2B-LS cdrecord's eject, info, pause, play, resume, set, status, stop, and volume work cdrecord's close never worked, and now debug on and reset do not work (don't know if they worked or not before.) kernel config: ident SEVENTH machine i386 cpu I686_CPU maxusers 32 options INET options FFS options FFS_ROOT options MFS options MFS_ROOT options NFS options NFS_ROOT options MSDOSFS options CD9660 options CD9660_ROOT options PROCFS options COMPAT_43 options SCSI_DELAY=2000 options UCONSOLE options FAILSAFE options USERCONFIG options VISUAL_USERCONFIG options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199303L options KBD_INSTALL_CDEV config kernel root on wd0 controller isa0 controller pnp0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 #controller ata0 #device atadisk0 controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port IO_WD2 irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 controller ahc0 controller scbus0 device da0 device cd0 device pass0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x31 # Advanced Power Management #device sio0 at isa? port IO_COM1 flags 0x10 irq 4 #device sio1 at isa? disable port IO_COM2 irq 3 device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device fxp0 device ed0 at isa? disable port 0x2c0 irq 10 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device snp 3 options SYSVSHM options SYSVMSG options SYSVSEM pseudo-device bpfilter 4 #Berkeley packet filter controller uhci0 controller usb0 device umass0 device ums0 device ukbd0 device ulpt0 device uhid0 device ugen0 device pcm0 dmesg: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Thu May 6 21:57:56 PDT 1999 root@erich2.unix.seattleu.edu:/usr/local/src/sys/compile/SEVENTH Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff real memory = 67043328 (65472K bytes) avail memory = 62484480 (61020K bytes) Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 4.0 on pci0 ide_pci0: at device 4.1 on pci0 uhci0: at device 4.2 on pci0 uhci0: interrupting at irq 10 usb0: on uhci0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ukbd0 ukbd0: Microsoft product 0x000b, rev 1.00/1.04, addr 2, iclass 3/1 kbd1 at ukbd0 chip2: at device 4.3 on pci0 ahc0: at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: interrupting at irq 10 fxp0: at device 7.0 on pci0 fxp0: interrupting at irq 11 fxp0: Ethernet address 00:e0:18:90:2d:3e es0: at device 10.0 on pci0 pcm0: using I/O space register mapping at 0xa400 es0: interrupting at irq 11 isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 812MB (1664208 sectors), 1651 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 kbd0 at atkbd0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model MouseMan+, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1: not probed (disabled) 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/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 ed0: not probed (disabled) Waiting 2 seconds for SCSI devices to settle changing root device to wd0s1a cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: cd present [166445 x 2048 byte records] da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 16) da1: 511MB (1046532 512 byte sectors: 64H 32S/T 511C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 7 23:37: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id E259314DDA for ; Fri, 7 May 1999 23:37:02 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id AAA56811; Sat, 8 May 1999 00:36:29 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905080636.AAA56811@panzer.plutotech.com> Subject: Re: tosha after CAM changes In-Reply-To: <3733C85B.5ACA8F4A@seattleu.edu> from Eric Hodel at "May 7, 1999 10:15: 7 pm" To: hodeleri@seattleu.edu (Eric Hodel) Date: Sat, 8 May 1999 00:36:29 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Hodel wrote... > I'm having trouble using tosha after the CAM changes, I updated source > early this morning (around 7:00 PDT 5/7/1999) including ports, then > make deinstall make distclean in /usr/ports/audio/tosha then make && > make install and tosha, and now tosha gives me (as root): > > #tosha -t1 > tosha: cam_lookup_pas: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: Inappropriate ioctl for device > > This is using a Teac CD-532S CD-ROM (SCSI2) attached to an onboard > AIC-7890 on an ASUS P2B-LS > > cdrecord's eject, info, pause, play, resume, set, status, stop, and > volume work > > cdrecord's close never worked, and now debug on and reset do not work > (don't know if they worked or not before.) [ .. ] Did you do a make world? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 0: 0:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8B8EC155F4 for ; Sat, 8 May 1999 00:00:52 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id QAA12608; Sat, 8 May 1999 16:00:23 +0900 (JST) Message-ID: <3733E07D.13078A1C@newsguy.com> Date: Sat, 08 May 1999 15:58:05 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Peter Wemm Cc: Andrzej Bialecki , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current References: <19990507213959.BFB0E1F72@spinner.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > It's interesting that the ANSI emulation in loader(8) is good enough to do > full-screen displays. It still seems to make sense to move userconfig-like > functionality into the pre-kernel stages including moving config(8)'s hints > to a loaded and parsed file. Forth, bah.. :-] I recall saying once I'd do it once people decided they wanted it. The disadvantage of anything written in Forth is that not many people can then maintain the code. But, then again, there is some code around written in C that no one *wants* to maintain (a certain installation program comes to mind... :) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness if that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 0: 5:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 2701D14DDA for ; Sat, 8 May 1999 00:05:29 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA06663; Sat, 8 May 1999 06:56:21 +0200 From: Luigi Rizzo Message-Id: <199905080456.GAA06663@labinfo.iet.unipi.it> Subject: Re: bridge+dummynet + "sysctl -a" panics in -current To: bright@rush.net (Alfred Perlstein) Date: Sat, 8 May 1999 06:56:21 +0200 (MET DST) Cc: current@FreeBSD.ORG In-Reply-To: from "Alfred Perlstein" at May 7, 99 02:10:15 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 319 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > just a follow-up, Jordan experianced the same bug and tracked it down, > I think Peter Wemm fixed it. it was something with isa+sysctl, and not > bridge related, sorry. no problem, you don't know until you find the bug, so i think it is better to receive a false alarm than no alarm for a real bug cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 1:19:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 01E3A1542D for ; Sat, 8 May 1999 01:19:54 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 53BC91F72; Sat, 8 May 1999 16:19:50 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Andrzej Bialecki , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-reply-to: Your message of "Sat, 08 May 1999 15:58:05 +0900." <3733E07D.13078A1C@newsguy.com> Date: Sat, 08 May 1999 16:19:50 +0800 From: Peter Wemm Message-Id: <19990508081953.53BC91F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > Peter Wemm wrote: > > > > It's interesting that the ANSI emulation in loader(8) is good enough to do > > full-screen displays. It still seems to make sense to move userconfig-like > > functionality into the pre-kernel stages including moving config(8)'s hints > > to a loaded and parsed file. Forth, bah.. :-] > > I recall saying once I'd do it once people decided they wanted it. > The disadvantage of anything written in Forth is that not many > people can then maintain the code. But, then again, there is some > code around written in C that no one *wants* to maintain (a certain > installation program comes to mind... :) Well, if you look at userconfig.c, you'll notice that very few people understand/maintain that code either. The most common changes are adding or removing device descriptions in a table, and that should be pretty much the same no matter what language it's written in... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 1:33:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 3AA10155BE for ; Sat, 8 May 1999 01:33:35 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id DAA19171; Sat, 8 May 1999 03:33:35 -0500 (CDT) From: Kevin Day Message-Id: <199905080833.DAA19171@home.dragondata.com> Subject: -current NFS crash (out of mbuf clusters) To: current@freebsd.org Date: Sat, 8 May 1999 03:33:33 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sure by now Matt is gonna kill me. :) -current from 2 days ago. IdlePTD 3096576 initial pcb at 27ea40 panicstr: Out of mbuf clusters panic messages: --- panic: Out of mbuf clusters syncing disks... panic: Out of mbuf clusters dumping to dev 20001, offset 467137 dump 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:288 288 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:288 #1 0xc0145755 in panic () at ../../kern/kern_shutdown.c:450 #2 0xc015c382 in m_retryhdr (i=0, t=1) at ../../kern/uipc_mbuf.c:297 #3 0xc01b3013 in nfsm_rpchead (cr=0xc1096a00, nmflag=35328, procid=21, auth_type=1, auth_len=24, auth_str=0x0, verf_len=-1071591891, verf_str=0x0, mrest=0xc0acb900, mrest_len=44, mbp=0xcad93990, xidp=0xcad93994) at ../../nfs/nfs_subs.c:657 #4 0xc01b0317 in nfs_request (vp=0xca465400, mrest=0xc0acb900, procnum=21, procp=0xc02955a0, cred=0xc1096a00, mrp=0xcad939fc, mdp=0xcad93a00, dposp=0xcad93a04) at ../../nfs/nfs_socket.c:971 #5 0xc01c90d5 in nfs_commit (vp=0xca465400, offset=0, cnt=7463, cred=0xc1096a00, procp=0xc02955a0) at ../../nfs/nfs_vnops.c:2586 #6 0xc01c9620 in nfs_flush (vp=0xca465400, cred=0xc0a5e900, waitfor=2, p=0xc02955a0, commit=1) at ../../nfs/nfs_vnops.c:2846 #7 0xc01c9389 in nfs_fsync (ap=0xcad93b2c) at ../../nfs/nfs_vnops.c:2710 #8 0xc01b9489 in nfs_sync (mp=0xc0ecee00, waitfor=2, cred=0xc0a5e900, p=0xc02955a0) at vnode_if.h:499 #9 0xc016ceaf in sync (p=0xc02955a0, uap=0x0) at ../../kern/vfs_syscalls.c:543 #10 0xc014535a in boot (howto=256) at ../../kern/kern_shutdown.c:205 #11 0xc0145755 in panic () at ../../kern/kern_shutdown.c:450 #12 0xc015c2ca in m_retry (i=0, t=1) at ../../kern/uipc_mbuf.c:269 #13 0xc015c8e7 in m_copym (m=0xc0adf400, off0=0, len=1000000000, wait=0) at ../../kern/uipc_mbuf.c:450 #14 0xc01b047e in nfs_request (vp=0xca346440, mrest=0xc0ded380, procnum=4, procp=0xcac83940, cred=0xc0a5e900, mrp=0xcad93ccc, mdp=0xcad93cd0, dposp=0xcad93cd4) at ../../nfs/nfs_socket.c:1024 #15 0xc01b99a9 in nfs_access (ap=0xcad93d84) at ../../nfs/nfs_vnops.c:357 #16 0xc01bb9cf in nfs_lookup (ap=0xcad93e30) at vnode_if.h:219 #17 0xc016930b in lookup (ndp=0xcad93eb4) at vnode_if.h:31 #18 0xc0168d12 in namei (ndp=0xcad93eb4) at ../../kern/vfs_lookup.c:152 #19 0xc016e878 in lstat (p=0xcac83940, uap=0xcad93f90) at ../../kern/vfs_syscalls.c:1702 #20 0xc020ec26 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1, tf_esi = 0, tf_ebp = -1077947556, tf_isp = -891731996, tf_ebx = 671539952, tf_edx = -1077947508, tf_ecx = 0, tf_eax = 190, tf_trapno = 12, tf_err = 2, tf_eip = 671750724, tf_cs = 31, tf_eflags = 582, tf_esp = -1077947676, tf_ss = 47}) at ../../i386/i386/trap.c:1066 #21 0xc0203f20 in Xint0x80_syscall () #22 0x2806afc7 in ?? () #23 0x2806b24d in ?? () #24 0x2806aa82 in ?? () #25 0x804a56e in ?? () #26 0x804a246 in ?? () #27 0x804acc7 in ?? () #28 0x8049bd1 in ?? () #29 0x80499c1 in ?? () #30 0x80497c9 in ?? () Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri May 7 02:53:27 CDT 1999 toasty@shell3.dragondata.com:/usr/src/sys/compile/SHELL3 Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 268435456 (262144K bytes) sio0: system console avail memory = 258457600 (252400K bytes) Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 ide_pci0: at device 15.0 on pci0 fxp0: at device 16.0 on pci0 fxp0: interrupting at irq 12 fxp0: Ethernet address 00:90:27:34:b9:a7 fxp1: at device 18.0 on pci0 fxp1: interrupting at irq 10 fxp1: Ethernet address 00:90:27:34:c0:12 eisa0: on motherboard isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ppc0: interrupting at irq 7 changing root device to wd0s1a WARNING: / was not properly dismounted Any other info needed? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 1:34:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 06C9715677 for ; Sat, 8 May 1999 01:34:15 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA20830; Sat, 8 May 1999 17:31:32 +0900 (JST) Message-ID: <3733F5D9.C803E70@newsguy.com> Date: Sat, 08 May 1999 17:29:13 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Peter Wemm Cc: Andrzej Bialecki , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current References: <19990508081953.53BC91F72@spinner.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Well, if you look at userconfig.c, you'll notice that very few people > understand/maintain that code either. The most common changes are adding > or removing device descriptions in a table, and that should be pretty > much the same no matter what language it's written in... Give me a hint file and I'll give you a hint file tweaker. I suppose this hint file could be loaded as a special file type, just like userconfig_script is nowadays. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 5:36:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from qix.jmz.org (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (Postfix) with ESMTP id 69EE6154BF for ; Sat, 8 May 1999 05:36:39 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.2) id OAA00383; Sat, 8 May 1999 14:38:00 +0200 (MET DST) (envelope-from jmz@FreeBSD.ORG) Date: Sat, 8 May 1999 14:38:00 +0200 (MET DST) Message-Id: <199905081238.OAA00383@qix.jmz.org> From: Jean-Marc Zucconi To: freebsd-current@FreeBSD.ORG Subject: booting kernel without wd0 X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Today, I can't boot my new kernel. I get: changing device to wd0a can't open /dev/rwdo0: device not configured My system is 100% scsi, and wdc0 is disabled in my config file: config kernel root on da0 dumps on da0 ... controller wdc0 at isa? disable port IO_WD1 irq 14 My previous kernel (april, 29) boots fine. Is there a fix? Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 6:47: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id C301E15166 for ; Sat, 8 May 1999 06:46:59 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-16-24.camtech.net.au [203.55.241.24]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id XAA22595 for ; Sat, 8 May 1999 23:22:13 +0930 (CST) Message-ID: <37344094.620D8ACF@camtech.com.au> Date: Sat, 08 May 1999 23:18:04 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Doesn't anyone care about the broken sio ?? Content-Type: multipart/digest; boundary="------------B4CEB0DE9840F944AC326623" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------B4CEB0DE9840F944AC326623 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I mailed a simple way to reproduce the serious brokeness of the serial port driver on my system and no one responds. What does this mean ? Does core know that sio is seriously broken and doesn't want to admit it ? [dont take that comment too seriously please]. What am I supposed to think ? Here we go again..... Can someone please run M.A.M.E. (/usr/ports/emulators/xmame) and then exit from it and then try to use user mode ppp. [NOTE you will need a M.A.M.E. ROM image from somewhere]. On my system and the previous system I had, this results in serious amounts of silo overflows, so much that the serial port is useless which requires me to reboot before I can use user mode ppp properly. My user mode ppp is fine unless I run MAME at any time before using user mode ppp without a reboot inbetween. All I want is for others to try to reproduce this problem. Previous messages attached giving more information. -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------B4CEB0DE9840F944AC326623 Message-ID: <372B3CBF.5E524469@camtech.com.au> Date: Sun, 02 May 1999 03:11:19 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: silo overflows in CURRENT ... some info that may help Content-Type: multipart/mixed; boundary="------------ACDDF923C9B1BB571E40AD37" This is a multi-part message in MIME format. --------------ACDDF923C9B1BB571E40AD37 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have been investigating the silo overflow situation for some time. I can trigger them every time by the following action: - Run M.A.M.E. (Multi arcade machine emulator) and then try to download something. (I am using user mode ppp). I believe that the sio driver is its own worst enemy in that once you get one silo overflow, it seems that the driver tries to compensate but it only makes it worse as I continue to get them and the serial port is unusable after that. Exiting MAME doesn't help, I have to reboot or I will be unable to do the smallest thing such as download my mail. I dont think its just MAME but rather anything that thrashes the interrupt system. This is not related to newbus as it occurrred before then in just the same manner. I have seen this effect on my home system no matter what combination of motherboard, modem, serial hardware. I was running a patch to sio.c before newbus came in to improve the speed at which the FIFO buffers were processed but MAME would still trigger the start of the silo overflow storm. With either a patched or unpatched system I can download huge files no problems as long as I dont run MAME at any time. Now dont say "just dont do that" (I know some of you will want to). Kernel config is attached. /etc/ppp/ppp.conf (edited) is attached. dmesg output is also attached. -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------ACDDF923C9B1BB571E40AD37 Content-Type: text/plain; charset=us-ascii; name="KERNEL" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="KERNEL" # Machine with Ultra DMA 32 Bit WD disk, ATAPI CD-ROM, SB16, NE2000 NIC, # NCR PCI SCSI, APM and Intel PIIX power management. # $Id: MATTE,v 11.8 1999/05/02 01:06:00 +09:30 matt Exp $ # based on: $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ # machine i386 ident "MATTE" maxusers 20 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 cpu I686_CPU options CPU_DISABLE_5X86_LSSER # Dont use if you use memory mapped I/O device(s). options CPU_FASTER_5X86_FPU # Faster FPU exception handler options NO_F00F_HACK # Disable Pentium F00F hack # COMPATIBILITY OPTIONS options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT # Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options MD5 # Include a MD5 routine in the kernel options VM86 # Allow processes to switch to vm86 mode (needed for doscmd) # DEBUGGING OPTIONS options DDB # Enable the kernel debugger #options INVARIANTS # Extra sanity checking (slower) #options INVARIANT_SUPPORT # Include sanity checking functions options UCONSOLE # Allow users to grab the console options USERCONFIG # Boot -c editor options VISUAL_USERCONFIG # Visual boot -c editor # NETWORKING OPTIONS options INET # Internet communications protocols # Network interfaces: pseudo-device ether # Generic Ethernet pseudo-device loop # Network loopback device pseudo-device tun 1 # Tunnel driver(user process ppp) pseudo-device streams # SysVR4 STREAMS emulation # FILESYSTEM OPTIONS options FFS # Berkeley Fast Filesystem options FFS_ROOT # FFS usable as root device options NFS # Network Filesystem options CD9660 # ISO 9660 Filesystem options MFS # Memory Filesystem options MSDOSFS # MSDOS Filesystem options PROCFS # Process Filesystem options NSWAPDEV=4 # Allow this many swap-devices options SOFTUPDATES # SoftUpdates aka delayed writes controller pci0 controller ncr0 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # SCSI DEVICE CONFIGURATION (CAM SCSI) controller scbus0 at ncr0 # Base SCSI code disk da0 at scbus0 target 0 disk da1 at scbus0 target 1 disk da2 at scbus0 target 2 disk da3 at scbus0 target 3 disk da4 at scbus0 target 4 disk da5 at scbus0 target 5 disk da6 at scbus0 target 6 options SCSI_DELAY=500 # Only wait 0.5 seconds for SCSI # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 64 # Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 4 # Vnode driver (turns a file into a device) options MSGBUF_SIZE=81920 # Size of the kernel message buffer # HARDWARE DEVICE CONFIGURATION controller isa0 options AUTO_EOI_1 # Save 0.7-1.25 usec for each interrupt controller pnp0 # Enable PnP support in the kernel controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? port ? conflicts pseudo-device splash # Splash screen at start up! device sc0 at isa? options MAXCONS=12 # Number of virtual consoles options SC_HISTORY_SIZE=800 # Number of history buffer lines options VESA # Needs VM86 defined too!! device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives #device wcd0 #controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff #disk wd0 at wdc0 drive 0 #controller wdc1 at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 device psm0 at atkbdc? irq 12 device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device sio0 at isa? port IO_COM1 irq 4 flags 0x10 device sio1 at isa? port IO_COM2 irq 3 options CONSPEED=38400 # Speed for serial console (default 9600) device ed0 at isa? port 0x300 irq 9 iomem 0xd8000 device apm0 at nexus? controller smbus0 controller intpm0 device smb0 at smbus? device joy0 at isa? port IO_GAME #device pcm0 at isa? port? irq 5 drq 1 flags 0x15 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 --------------ACDDF923C9B1BB571E40AD37 Content-Type: text/plain; charset=us-ascii; name="ppp.conf" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ppp.conf" ################################################################# # # PPP Sample Configuration File # # Originally written by Toshiharu OHNO # # $Id: ppp.conf.sample,v 1.28 1997/12/31 03:58:45 brian Exp $ # ################################################################# default: set log chat connect phase set device /dev/cuaa1 set speed 115200 allow users matt deny lqr deny chap set timeout 0 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATX4S95=47 OK-AT-OK \\dATDT\\T TIMEOUT 120 CONNECT" set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 camtechd: set phone 82285100 set login "TIMEOUT 10 sername:--sername: BLAHU assword: BLAHP" dial --------------ACDDF923C9B1BB571E40AD37 Content-Type: text/plain; charset=us-ascii; name="dmegg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmegg" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun May 2 01:10:27 CST 1999 matt@localhost:/usr/src/sys/compile/MATTE Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (463.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping=0 Features=0x183f9ff real memory = 67108864 (65536K bytes) config> pnp 1 0 bios enable avail memory = 62140416 (60684K bytes) Preloaded elf kernel "kernel" at 0xc02ed000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02ed09c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100a1ec0 Comp ID: PNP0600 [0x0006d041] npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 chip2: at device 7.3 on pci0 ncr0: at device 13.0 on pci0 ncr0: interrupting at irq 11 isa0: on motherboard atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model IntelliMouse, device ID 3 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <12 virtual consoles, flags=0x0> fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ed0 at port 0x300-0x31f irq 9 on isa0 ed0: address 00:00:e8:20:33:e8, type NE2000 (16 bit) ed0: interrupting at irq 9 joy0 at port 0x201 on isa0 joy0: joystick sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sb0: interrupting at irq 5 sbxvi0 at drq 5 on isa0 snd0: sbmidi0 at port 0x330 on isa0 snd0: opl0 at port 0x388 on isa0 snd0: ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-3 disk at ata0 as master ad0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s2a ffs_mountfs: superblock updated for soft updates ed0: device timeout --------------ACDDF923C9B1BB571E40AD37-- --------------B4CEB0DE9840F944AC326623 Message-ID: <372C0180.7F7BEFA@camtech.com.au> Date: Sun, 02 May 1999 17:10:48 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug Russell CC: freebsd-current@FreeBSD.ORG Subject: Re: silo overflows in CURRENT ... some info that may help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Re-nicing wont help as I have just confirmed that the problem occurs if I run MAME, exit MAME and then get on the net. Very wierd... after running MAME, the serial port is unusable for ppp unless I reboot. Just doing a DNS lookup causes several silo overflows. MAME does something very strange to the system. I will grep the MAME source code for anything related to serial ports. Doug Russell wrote: > > On Sun, 2 May 1999, Matthew Thyer wrote: > > > I have been investigating the silo overflow situation for some time. > > > > I can trigger them every time by the following action: > > > > - Run M.A.M.E. (Multi arcade machine emulator) and then try to > > download something. (I am using user mode ppp). > > Can you nice M.A.M.E. slightly? > > Later...... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------B4CEB0DE9840F944AC326623 Message-ID: <372DB7E6.8D66DCDF@camtech.com.au> Date: Tue, 04 May 1999 00:21:18 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Silo overflows and MAME can someone else reproduce this problem ?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This problem is easily reproducible. However to do so, you need a ROM image for an arcade game that the Multi Arcade Machine Emulator emulates as it wont do it without any roms in the directory "/usr/local/lib/mame/roms". I am using xmame installed from the ports collection (/usr/ports/emulators/xmame) on a very recent -CURRENT machine. If I run xmame *before* I get online with user mode ppp (or while I am on the net), the serial ports get hosed and I have to reboot or I continually get silo overflows. This is not right as it happens AFTER I exit xmame !!! Please can someone else reproduce this problem as I'd hate to think its only on the systems I have owned (Pentium 166 and Celeron 300). -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------B4CEB0DE9840F944AC326623 Message-ID: <372DB8A1.89159C49@camtech.com.au> Date: Tue, 04 May 1999 00:24:25 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Silo overflows and MAME can someone else reproduce this problem ?? References: <372DB7E6.8D66DCDF@camtech.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit My usermode ppp works fine normally as I can quite happily download 4 things at once without a single silo overflow (as I did last night) even when there is lots of disk activity or X11 activity. Note this problem is unrelated to newbus as it occurs both before and after those commits. Matthew Thyer wrote: > > This problem is easily reproducible. > > However to do so, you need a ROM image for an arcade game that the > Multi Arcade Machine Emulator emulates as it wont do it without any > roms in the directory "/usr/local/lib/mame/roms". > > I am using xmame installed from the ports collection > (/usr/ports/emulators/xmame) on a very recent -CURRENT machine. > > If I run xmame *before* I get online with user mode ppp (or while > I am on the net), the serial ports get hosed and I have to reboot > or I continually get silo overflows. > > This is not right as it happens AFTER I exit xmame !!! > > Please can someone else reproduce this problem as I'd hate to think > its only on the systems I have owned (Pentium 166 and Celeron 300). > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------B4CEB0DE9840F944AC326623-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 7:49:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6DECB14CCA for ; Sat, 8 May 1999 07:49:37 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id HAA07974; Sat, 8 May 1999 07:49:36 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id HAA34051; Sat, 8 May 1999 07:49:35 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 8 May 1999 07:49:35 -0700 (PDT) Message-Id: <199905081449.HAA34051@vashon.polstra.com> To: jwd@unx.sas.com Subject: Re: make world problem (just me?) warning: `MDF_ACTIVE' redefined In-Reply-To: <199905080132.VAA80459@bb01f39.unx.sas.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199905080132.VAA80459@bb01f39.unx.sas.com>, John W. DeBoskey wrote: > > I've had the following problem for the last 36 hours or so. I > haven't seen any fixes related to this. Has anyone else seen > the following, or is my tree somehow messed up? ... > ===> usr.bin/kdump > cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c > /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c > In file included from :47: > /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined > /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition > cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c > ioctl.c:7: sys/disk.h: No such file or directory > In file included from ioctl.c:76: > /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined > /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition > *** Error code 1 It's real. I got it too in last night's make world on an alpha machine with a freshly checked-out source tree and an empty obj tree. (I haven't done a make world on i386 this week.) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 7:51:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id 5684214CCA for ; Sat, 8 May 1999 07:51:26 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id HAA16197; Sat, 8 May 1999 07:50:55 -0700 (PDT) Message-ID: <37344F1F.DA8CDBA@seattleu.edu> Date: Sat, 08 May 1999 07:50:07 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: "freebsd-current@FreeBSD.ORG" Subject: Re: tosha after CAM changes References: <199905080636.AAA56811@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > > Eric Hodel wrote... > > I'm having trouble using tosha after the CAM changes, I updated source > > early this morning (around 7:00 PDT 5/7/1999) including ports, then > > make deinstall make distclean in /usr/ports/audio/tosha then make && > > make install and tosha, and now tosha gives me (as root): > > > > #tosha -t1 > > tosha: cam_lookup_pas: CAMGETPASSTHRU ioctl failed > > cam_lookup_pass: Inappropriate ioctl for device > > > > This is using a Teac CD-532S CD-ROM (SCSI2) attached to an onboard > > AIC-7890 on an ASUS P2B-LS > > > > cdrecord's eject, info, pause, play, resume, set, status, stop, and > > volume work > > > > cdrecord's close never worked, and now debug on and reset do not work > > (don't know if they worked or not before.) > > [ .. ] > > Did you do a make world? Yes, sorry about that, forgot the most important part. PS: Accidentally sent a blank message. Serves me right for answering email after getting out of bed. -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 7:53:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 11A1614CCA for ; Sat, 8 May 1999 07:53:32 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id QAA02683; Sat, 8 May 1999 16:53:31 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id QAA16492; Sat, 8 May 1999 16:53:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: jwd@unx.sas.com, current@FreeBSD.ORG Subject: Re: make world problem (just me?) warning: `MDF_ACTIVE' redefined In-reply-to: Your message of "Sat, 08 May 1999 07:49:35 PDT." <199905081449.HAA34051@vashon.polstra.com> Date: Sat, 08 May 1999 16:53:24 +0200 Message-ID: <16490.926175204@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I fixed that this morning (6 hours ago or so...) In message <199905081449.HAA34051@vashon.polstra.com>, John Polstra writes: >In article <199905080132.VAA80459@bb01f39.unx.sas.com>, >John W. DeBoskey wrote: >> >> I've had the following problem for the last 36 hours or so. I >> haven't seen any fixes related to this. Has anyone else seen >> the following, or is my tree somehow messed up? >... >> ===> usr.bin/kdump >> cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c >> /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c >> In file included from :47: >> /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined >> /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition >> cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c >> ioctl.c:7: sys/disk.h: No such file or directory >> In file included from ioctl.c:76: >> /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined >> /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition >> *** Error code 1 > >It's real. I got it too in last night's make world on an alpha >machine with a freshly checked-out source tree and an empty obj tree. >(I haven't done a make world on i386 this week.) > >John >-- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 8:41:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id E38FA14F5E for ; Sat, 8 May 1999 08:41:29 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA07452; Sat, 8 May 1999 15:32:33 +0200 From: Luigi Rizzo Message-Id: <199905081332.PAA07452@labinfo.iet.unipi.it> Subject: m_get(M_WAIT, ...) _can_ return NULL ? To: current@freebsd.org Date: Sat, 8 May 1999 15:32:33 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 567 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, thinking about the supposed "fragility" of FreeBSD when mbufs (or clusters) are not properly dimensioned: i notice that in various places of the code (and this is, i think, 4.4 heritage), there are things like m = m_get(M_WAIT, ...) m->m_len = something. looking at the code, it seems that m_get() _can_ return a NULL pointer even if one specifies M_WAIT. Could this be a potential weakness, and in this case, how shuld we go and fix it -- by making m_get never return if there is no memory, or by hunting all such occurrences of the code ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 9:18:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 63D1B151D8 for ; Sat, 8 May 1999 09:18:35 -0700 (PDT) (envelope-from root@pozo.com) Received: from localhost (root@localhost) by pozo.com (8.9.3/8.9.3) with ESMTP id JAA01061 for ; Sat, 8 May 1999 09:18:34 -0700 (PDT) (envelope-from root@pozo.com) Date: Sat, 8 May 1999 09:18:34 -0700 (PDT) From: Manfred Antar To: current@freebsd.org Subject: missing file fla.h from current sources Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When trying to build a kernel from current sources I get this error when doing make depend In file included from ../../i386/isa/isa_compat.c:46: ../../i386/isa/isa_compat.h:91: fla.h: No such file or directory mkdep: compile failed *** Error code 1 This is from current sources as of Sat 9am pacific time Manfred ============================= || mantar@pacbell.net || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 9:32:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id EFBCD152BF for ; Sat, 8 May 1999 09:32:14 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA25632; Sat, 8 May 1999 11:53:44 -0500 (EST) Date: Sat, 8 May 1999 11:53:43 -0500 (EST) From: Alfred Perlstein To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: m_get(M_WAIT, ...) _can_ return NULL ? In-Reply-To: <199905081332.PAA07452@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 May 1999, Luigi Rizzo wrote: > Hi, > > thinking about the supposed "fragility" of FreeBSD when mbufs (or > clusters) are not properly dimensioned: i notice that > in various places of the code (and this is, i think, 4.4 heritage), > there are things like > > m = m_get(M_WAIT, ...) > m->m_len = something. > > looking at the code, it seems that m_get() _can_ return a NULL pointer > even if one specifies M_WAIT. > > Could this be a potential weakness, and in this case, how shuld we go > and fix it -- by making m_get never return if there is no memory, > or by hunting all such occurrences of the code ? I'm pretty sure there was a discussion about this almost a year ago, the situation with m_get+M_WAIT possibly returning NULL got so man people annoyed that a few sent in patches that REALLY helped FreeBSD remain stable during severe mbuf shortages. Unfortunatly it seems that they didn't catch every place. I think the answer is to figure out how to make these places "back out" instead of making m_get totally blocking, It gives more control. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 9:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8A67E1568A for ; Sat, 8 May 1999 09:34:58 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA26550; Sat, 8 May 1999 10:34:09 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA14466; Sat, 8 May 1999 10:34:18 -0600 (MDT) Message-Id: <199905081634.KAA14466@harmony.village.org> To: Luigi Rizzo Subject: Re: m_get(M_WAIT, ...) _can_ return NULL ? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 08 May 1999 15:32:33 +0200." <199905081332.PAA07452@labinfo.iet.unipi.it> References: <199905081332.PAA07452@labinfo.iet.unipi.it> Date: Sat, 08 May 1999 10:34:18 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905081332.PAA07452@labinfo.iet.unipi.it> Luigi Rizzo writes: : m = m_get(M_WAIT, ...) : looking at the code, it seems that m_get() _can_ return a NULL pointer : even if one specifies M_WAIT. Looking at the man page for malloc: M_WAITOK indicates that it is Ok to wait for resources. It is unconve- niently defined as 0 so care should be taken never to compare against this value directly or try to AND it as a flag. The de- fault operation is to block until the memory allocation succeeds. malloc() can only return NULL if M_NOWAIT is specified. Sounds like a bug to me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 9:37: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3C08B14DDA for ; Sat, 8 May 1999 09:37:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA22233; Sat, 8 May 1999 09:37:28 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Thyer Cc: current@FreeBSD.ORG Subject: Re: Doesn't anyone care about the broken sio ?? In-reply-to: Your message of "Sat, 08 May 1999 23:18:04 +0930." <37344094.620D8ACF@camtech.com.au> Date: Sat, 08 May 1999 09:37:28 -0700 Message-ID: <22229.926181448@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I mailed a simple way to reproduce the serious brokeness of the > serial port driver on my system and no one responds. > > What does this mean ? It means that nobody is probably willing to go bring up a MAME environment just to test this. You need to isolate it to a more minimal test case if you want people to jump on what could be a local problem (some serial hardware is better behaved than others) or a misbehaving X server (which is masking interrupts for too long; see mailing list archives on this topic). The more complex your reproduction case, in other words, the less likely it is that anyone will respond to it. If you can say "here's a small stand-alone C program which hogs things to the extent that the serial driver seriously overruns its buffers" then it's likely that someone will be at least motivated to compile, run and try it. If it involves running some esoteric application which requires downloading data of questionable legality on top of it, it's far less likely that anyone will even bother to look. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 9:51:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3FFB015138 for ; Sat, 8 May 1999 09:51:29 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA22337 for ; Sat, 8 May 1999 09:51:55 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: Latest breakage in -current as reported by current.freebsd.org Date: Sat, 08 May 1999 09:51:55 -0700 Message-ID: <22333.926182315@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> usr.bin/kdump cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdum p/../.. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c In file included from :47: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefi ned /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the loca tion of the previous definition cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdum p/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c ioctl.c:7: sys/disk.h: No such file or directory In file included from ioctl.c:76: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefi ned /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the loca tion of the previous definition To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 9:52:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id CAA9E15138 for ; Sat, 8 May 1999 09:52:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id SAA03161; Sat, 8 May 1999 18:52:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id SAA16825; Sat, 8 May 1999 18:52:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: Matthew Thyer , current@FreeBSD.ORG Subject: Re: Doesn't anyone care about the broken sio ?? In-reply-to: Your message of "Sat, 08 May 1999 09:37:28 PDT." <22229.926181448@zippy.cdrom.com> Date: Sat, 08 May 1999 18:52:44 +0200 Message-ID: <16823.926182364@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce said, in his own quite way, that somebody had broken fast interrupts as part of newbus, and that is the end of that story. Poul-Henning In message <22229.926181448@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> I mailed a simple way to reproduce the serious brokeness of the >> serial port driver on my system and no one responds. >> >> What does this mean ? > >It means that nobody is probably willing to go bring up a MAME >environment just to test this. You need to isolate it to a more >minimal test case if you want people to jump on what could be a local >problem (some serial hardware is better behaved than others) or a >misbehaving X server (which is masking interrupts for too long; see >mailing list archives on this topic). The more complex your >reproduction case, in other words, the less likely it is that anyone >will respond to it. > >If you can say "here's a small stand-alone C program which hogs things >to the extent that the serial driver seriously overruns its buffers" >then it's likely that someone will be at least motivated to compile, >run and try it. If it involves running some esoteric application >which requires downloading data of questionable legality on top of it, >it's far less likely that anyone will even bother to look. > >- Jordan > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 9:54: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 7EF4E15138 for ; Sat, 8 May 1999 09:53:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id SAA03171; Sat, 8 May 1999 18:53:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id SAA16848; Sat, 8 May 1999 18:53:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Latest breakage in -current as reported by current.freebsd.org In-reply-to: Your message of "Sat, 08 May 1999 09:51:55 PDT." <22333.926182315@zippy.cdrom.com> Date: Sat, 08 May 1999 18:53:51 +0200 Message-ID: <16846.926182431@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG already fixed 8 hours ago. In message <22333.926182315@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >===> usr.bin/kdump >cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdum >p/../.. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c >/bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c >In file included from :47: >/usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefi >ned >/usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the loca >tion of the previous definition >cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdum >p/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c >ioctl.c:7: sys/disk.h: No such file or directory >In file included from ioctl.c:76: >/usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefi >ned >/usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the loca >tion of the previous definition > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 9:57: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id CEE4E15138 for ; Sat, 8 May 1999 09:56:58 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id LAA25918; Sat, 8 May 1999 11:56:56 -0500 (CDT) Date: Sat, 8 May 1999 11:56:55 -0500 (CDT) From: Steve Price To: Manfred Antar Cc: current@FreeBSD.ORG Subject: Re: missing file fla.h from current sources In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm (peter@freebsd.org) just committed a fix for this in files.i386. You should be able to grab a copy from your favorite CVSup mirror in less than an hour. -steve On Sat, 8 May 1999, Manfred Antar wrote: # When trying to build a kernel from current sources # I get this error when doing make depend # # In file included from ../../i386/isa/isa_compat.c:46: # ../../i386/isa/isa_compat.h:91: fla.h: No such file or directory # mkdep: compile failed # *** Error code 1 # # This is from current sources as of Sat 9am pacific time # Manfred # ============================= # || mantar@pacbell.net || # || Ph. (415) 681-6235 || # ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 10:24:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 7EF5A14BD6 for ; Sat, 8 May 1999 10:24:42 -0700 (PDT) (envelope-from root@pozo.com) Received: from localhost (root@localhost) by pozo.com (8.9.3/8.9.3) with ESMTP id KAA02988; Sat, 8 May 1999 10:24:40 -0700 (PDT) (envelope-from root@pozo.com) Date: Sat, 8 May 1999 10:24:40 -0700 (PDT) From: Manfred Antar To: Steve Price Cc: current@FreeBSD.ORG Subject: Re: missing file fla.h from current sources In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 May 1999, Steve Price wrote: > Peter Wemm (peter@freebsd.org) just committed a fix for this > in files.i386. You should be able to grab a copy from your > favorite CVSup mirror in less than an hour. > > -steve > > On Sat, 8 May 1999, Manfred Antar wrote: > > # When trying to build a kernel from current sources > # I get this error when doing make depend > # > # In file included from ../../i386/isa/isa_compat.c:46: > # ../../i386/isa/isa_compat.h:91: fla.h: No such file or directory > # mkdep: compile failed > # *** Error code 1 > # > # This is from current sources as of Sat 9am pacific time > # Manfred Thanks Manfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 11:13:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from router.gagarinclub.ru (unknown [194.67.182.2]) by hub.freebsd.org (Postfix) with ESMTP id EC66814BF7 for ; Sat, 8 May 1999 11:13:21 -0700 (PDT) (envelope-from firma@gagarinclub.ru) Received: from rem.gagarinclub.ru (rem.gagarinclub.ru [194.67.182.5]) by router.gagarinclub.ru (8.9.3/8.9.3) with ESMTP id WAA08236; Sat, 8 May 1999 22:10:32 +0400 (MSD) Date: Sat, 8 May 1999 22:13:31 +0400 (MSD) From: REM Reply-To: REM To: John Polstra Cc: jwd@unx.sas.com, current@FreeBSD.ORG Subject: Re: make world problem (just me?) warning: `MDF_ACTIVE' redefined In-Reply-To: <199905081449.HAA34051@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 May 1999, John Polstra wrote: > In article <199905080132.VAA80459@bb01f39.unx.sas.com>, > John W. DeBoskey wrote: > > > > I've had the following problem for the last 36 hours or so. I > > haven't seen any fixes related to this. Has anyone else seen > > the following, or is my tree somehow messed up? > ... > > ===> usr.bin/kdump > > cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c > > /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c > > In file included from :47: > > /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined > > /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition > > cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c > > ioctl.c:7: sys/disk.h: No such file or directory > > In file included from ioctl.c:76: > > /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined > > /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the location of the previous definition > > *** Error code 1 > > It's real. I got it too in last night's make world on an alpha > machine with a freshly checked-out source tree and an empty obj tree. > (I haven't done a make world on i386 this week.) > I have had this problem in the morning of 08.05.99. Then I cvsup my system at the middle of this day and make world. It's OK now. REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 11:25: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles526.castles.com [208.214.165.90]) by hub.freebsd.org (Postfix) with ESMTP id 075A614F6A for ; Sat, 8 May 1999 11:24:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA01001; Sat, 8 May 1999 11:23:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905081823.LAA01001@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo Cc: current@freebsd.org Subject: Re: m_get(M_WAIT, ...) _can_ return NULL ? In-reply-to: Your message of "Sat, 08 May 1999 15:32:33 +0200." <199905081332.PAA07452@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 May 1999 11:23:35 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > thinking about the supposed "fragility" of FreeBSD when mbufs (or > clusters) are not properly dimensioned: i notice that > in various places of the code (and this is, i think, 4.4 heritage), > there are things like > > m = m_get(M_WAIT, ...) > m->m_len = something. > > looking at the code, it seems that m_get() _can_ return a NULL pointer > even if one specifies M_WAIT. > > Could this be a potential weakness, and in this case, how shuld we go > and fix it -- by making m_get never return if there is no memory, > or by hunting all such occurrences of the code ? I engaged in part of a sweep of this sort with Andrzej a while back, but he never committed any of the changes. I'm not quite sure why. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 11:25:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id B4BF2156C5 for ; Sat, 8 May 1999 11:25:17 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id UAA25079 for ; Sat, 8 May 1999 20:25:15 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma025077; Sat, 8 May 99 20:25:15 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id UAA03792 for ; Sat, 8 May 1999 20:25:15 +0200 (MET DST) Received: (qmail 92808 invoked by uid 666); 8 May 1999 18:25:36 -0000 Date: Sat, 8 May 1999 20:25:36 +0200 From: Jos Backus To: current@freebsd.org Subject: mountroot problem Message-ID: <19990508202536.A92612@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fyi: With today's -current I'm unable to remount the root fs during boot. I'm seeing the infamous ``specified device doesn't match mounted device'' as a result of ``mount -u /''. The mounted device is ``root_device'' (as set in sys/kern/vfs_conf.c) according to mount, instead of the usual ``da2s1a'' (which gets changed to ``/dev/da2s1a'' as a result of the mount -u, I've verified). Otoh, a kernel built at the end of May 6th works fine. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 11:26:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A60714F6A for ; Sat, 8 May 1999 11:26:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA55323; Sat, 8 May 1999 11:26:45 -0700 (PDT) (envelope-from dillon) Date: Sat, 8 May 1999 11:26:45 -0700 (PDT) From: Matthew Dillon Message-Id: <199905081826.LAA55323@apollo.backplane.com> To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -current NFS crash (out of mbuf clusters) References: <199905080833.DAA19171@home.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm sure by now Matt is gonna kill me. :) : :-current from 2 days ago. : :IdlePTD 3096576 :initial pcb at 27ea40 :panicstr: Out of mbuf clusters :panic messages: :--- :panic: Out of mbuf clusters This is probably not NFS related unless there is a leak somewhere. You may have to mess with the NMBCLUSTERS kernel config to increase the number of mbuf clusters. FreeBSD tends to not allocate enough by default in more heavily loaded larger-memory configurations. It should be possible to confirm that the problem is not NFS by taking a general look at the state of the system at the time of the crash. You can run 'ps' and 'netstat' on the core dump: cd /var/crash ps -axl -M vmcore.XX -N kernel.XX netstat -tna -M vmcore.XX -N kernel.XX netstat -m -M vmcore.XX -N kernel.XX -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 11:42:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from nfs.dragondata.com (power.dragondata.com [204.137.237.7]) by hub.freebsd.org (Postfix) with ESMTP id 5F77314C31 for ; Sat, 8 May 1999 11:42:36 -0700 (PDT) (envelope-from toasty@nfs.dragondata.com) Received: (from toasty@localhost) by nfs.dragondata.com (8.9.3/8.9.3) id NAA14324; Sat, 8 May 1999 13:42:27 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199905081842.NAA14324@nfs.dragondata.com> Subject: Re: -current NFS crash (out of mbuf clusters) In-Reply-To: <199905081826.LAA55323@apollo.backplane.com> from Matthew Dillon at "May 8, 1999 11:26:45 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 8 May 1999 13:42:27 -0500 (CDT) Cc: toasty@home.dragondata.com (Kevin Day), current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :I'm sure by now Matt is gonna kill me. :) > : > :-current from 2 days ago. > : > :IdlePTD 3096576 > :initial pcb at 27ea40 > :panicstr: Out of mbuf clusters > :panic messages: > :--- > :panic: Out of mbuf clusters > > This is probably not NFS related unless there is a leak somewhere. > > You may have to mess with the NMBCLUSTERS kernel config to increase > the number of mbuf clusters. FreeBSD tends to not allocate enough > by default in more heavily loaded larger-memory configurations. > > It should be possible to confirm that the problem is not NFS by taking > a general look at the state of the system at the time of the crash. You > can run 'ps' and 'netstat' on the core dump: > > cd /var/crash > ps -axl -M vmcore.XX -N kernel.XX UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) 0 1 0 0 10 0 500 0 wait Is ?? 0:00.00 (init) 0 2 0 0 -18 0 0 0 psleep DL ?? 0:00.00 (pagedaemon) 0 3 0 0 18 0 0 0 psleep DL ?? 0:00.00 (vmdaemon) 0 4 0 0 -1 0 0 0 nfsrcv DL ?? 0:00.00 (syncer) 0 39 1 30 18 0 204 0 pause Is ?? 0:00.00 (adjkerntz) 1 233 1 30 2 0 832 0 select Is ?? 0:00.00 (portmap) 0 268 1 7 29 0 1024 0 - Rs ?? 0:00.00 (cron) 10079 384 1 0 -1 0 2092 0 nfsrcv D ?? 0:00.00 (eggdrop) 1200 703 1 0 -1 0 1740 0 nfsrcv D ?? 0:00.00 (eggdrop) 10039 706 1 0 -1 0 1656 0 nfsrcv D ?? 0:00.00 (eggdrop) 10173 711 1 0 2 0 1804 0 select S ?? 0:00.00 (eggdrop) 10336 1075 1 0 -1 0 1916 0 nfsrcv D ?? 0:00.00 (eggdrop) 10051 1245 1 0 -1 0 2356 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 10467 1686 1 0 -1 0 1820 0 nfsrcv D ?? 0:00.00 (eggdrop) 10173 1697 1 0 2 0 1792 0 select S ?? 0:00.00 (eggdrop) 10387 1726 1 0 2 0 1800 0 select S ?? 0:00.00 (eggdrop) 10387 1727 1 0 2 0 1792 0 select S ?? 0:00.00 (eggdrop) 1279 1743 1 0 -1 0 2228 0 nfsrcv D ?? 0:00.00 (eggdrop) 10176 1745 1 6 2 0 2460 0 select S ?? 0:00.00 (eggdrop-1.3.26) 10051 2128 1 0 2 0 1160 0 select Ss ?? 0:00.00 (ezbounce) 0 2200 268 0 -6 0 1056 0 piperd I ?? 0:00.00 (cron) 10002 2206 2200 1 28 0 0 0 - Z ?? 0:00.00 (sh) 0 2548 2200 5 -6 0 1328 0 piperd I ?? 0:00.00 (sendmail) 1292 2602 1 11 10 0 500 0 wait Is ?? 0:00.00 (sh) 10002 2655 1 0 2 0 828 0 select Is ?? 0:00.00 (bnc) 1392 2657 1 0 2 0 860 0 select Is ?? 0:00.00 (bnc) 10218 2658 1 0 2 0 860 0 select Is ?? 0:00.00 (bnc) 10177 2664 1 0 2 0 860 0 select Is ?? 0:00.00 (bnc) 10033 2666 1 0 2 0 860 0 select Is ?? 0:00.00 (bnc) 1294 2667 1 0 2 0 876 0 select Is ?? 0:00.00 (bnc) 10452 2673 1 0 -1 0 956 0 nfsrcv D ?? 0:00.00 (mech) 1292 2688 2602 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10427 2726 1 0 -1 0 1988 0 nfsrcv D ?? 0:00.00 (eggdrop) 1292 2755 2688 0 -6 0 1740 0 piperd I ?? 0:00.00 (eggdrop) 1339 2762 1 0 -1 0 1852 0 nfsrcv D ?? 0:00.00 (BitchX) 1339 2772 1 0 -1 0 1840 0 nfsrcv D ?? 0:00.00 (bnc) 10391 2854 1 0 -1 0 1744 0 nfsrcv D ?? 0:00.00 (eggdrop) 10027 2858 1 0 -1 0 1696 0 nfsrcv D ?? 0:00.00 (eggdrop) 10027 2859 1 0 -1 0 1696 0 nfsrcv D ?? 0:00.00 (eggdrop) 10027 2860 1 0 -1 0 1696 0 nfsrcv D ?? 0:00.00 (eggdrop) 1272 2870 1 0 -1 0 2056 0 nfsrcv D ?? 0:00.00 (eggdrop) 10237 2871 1 0 2 0 1688 0 select S ?? 0:00.00 (eggdrop) 10169 2872 1 0 -1 0 1836 0 nfsrcv D ?? 0:00.00 (eggdrop) 1405 2874 1 0 -1 0 1700 0 nfsrcv D ?? 0:00.00 (eggdrop) 1285 2875 1 0 -1 0 2292 0 nfsrcv D ?? 0:00.00 (eggdrop) 10099 2877 1 0 -1 0 1832 0 nfsrcv D ?? 0:00.00 (eggdrop) 10112 2878 1 0 -1 0 1992 0 nfsrcv D ?? 0:00.00 (eggdrop) 10239 2879 1 0 -1 0 1908 0 nfsrcv D ?? 0:00.00 (eggdrop) 10385 2880 1 0 -1 0 1540 0 nfsrcv D ?? 0:00.00 (eggdrop) 1079 2891 1 0 -1 0 1900 0 nfsrcv D ?? 0:00.00 (eggdrop) 10002 2892 1 0 -1 0 2128 0 nfsrcv D ?? 0:00.00 (eggdrop) 10428 2900 1 0 -1 0 1780 0 nfsrcv D ?? 0:00.00 (eggdrop) 10428 2901 1 0 -1 0 1764 0 nfsrcv D ?? 0:00.00 (eggdrop) 10113 2917 1 0 -1 0 1568 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 10398 2926 1 0 -1 0 1852 0 nfsrcv D ?? 0:00.00 (eggdrop) 10398 2927 1 0 -1 0 1840 0 nfsrcv D ?? 0:00.00 (eggdrop) 10361 2936 1 0 -1 0 1760 0 nfsrcv D ?? 0:00.00 (eggdrop) 1411 2938 1 0 -1 0 1868 0 nfsrcv D ?? 0:00.00 (eggdrop-#indosea) 10412 2957 1 0 -1 0 1792 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 1369 2961 1 0 -1 0 1864 0 nfsrcv D ?? 0:00.00 (eggdrop) 10084 2974 1 0 -1 0 1868 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 10084 2975 1 0 -1 0 1868 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 10137 2985 1 0 -1 0 1868 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 1289 2987 1 0 -1 0 1940 0 nfsrcv D ?? 0:00.00 (eggdrop) 10144 2993 1 0 -1 0 1848 0 nfsrcv D ?? 0:00.00 (eggdrop) 10162 2999 1 0 -1 0 1844 0 nfsrcv D ?? 0:00.00 (eggdrop) 1262 3003 1 0 2 0 1892 0 select S ?? 0:00.00 (eggdrop-1.3.23) 1275 3004 1 0 -1 0 1852 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 10237 3017 1 0 2 0 1688 0 select S ?? 0:00.00 (eggdrop) 1210 3025 1 0 -1 0 2324 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 1335 3031 1 0 -1 0 2088 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.22) 10413 3032 1 0 -1 0 2080 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 10230 3062 1 0 -1 0 2108 0 nfsrcv D ?? 0:00.00 (eggdrop) 10230 3063 1 0 -1 0 2132 0 nfsrcv D ?? 0:00.00 (eggdrop) 1292 3064 2755 0 28 0 0 0 - Z ?? 0:00.00 (uname) 10230 3074 1 0 -1 0 2140 0 nfsrcv D ?? 0:00.00 (eggdrop) 0 3754 1 0 2 0 892 0 select Is ?? 0:00.00 (telnetd) 1275 4073 1 0 -2 0 1852 0 getblk D ?? 0:00.00 (eggdrop-1.3.23) 0 7322 1 1 2 0 872 0 sbwait Is ?? 0:00.00 (telnetd) 10137 7759 1 0 -1 0 1916 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 1292 8958 1 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1399 8972 1 18 10 0 500 0 wait Is ?? 0:00.00 (sh) 1399 9021 8972 0 10 0 508 0 wait I ?? 0:00.00 (sh) 1292 9202 8958 0 10 0 504 0 wait I ?? 0:00.00 (sh) 1399 9341 9021 0 -6 0 1644 0 piperd I ?? 0:00.00 (eggdrop) 1292 9380 9202 1 -6 0 1740 0 piperd I ?? 0:00.00 (eggdrop) 1399 9432 9341 1 28 0 0 0 - Z ?? 0:00.00 (uname) 1411 9465 1 0 -1 0 1852 0 nfsrcv D ?? 0:00.00 (eggdrop-#indosea) 1292 9468 9380 3 28 0 0 0 - Z ?? 0:00.00 (uname) 1360 11048 1 0 -1 0 1880 0 nfsrcv D ?? 0:00.00 (eggdrop) 10461 12605 1 0 -5 0 2248 0 vinvlb D ?? 0:00.00 (eggdrop-1.3.23) 10334 13191 1 0 -1 0 2044 0 nfsrcv D ?? 0:00.00 (eggdrop) 1360 13875 1 0 -1 0 1904 0 nfsrcv D ?? 0:00.00 (eggdrop) 1399 15680 1 0 -1 0 1760 0 nfsrcv D ?? 0:00.00 (eggdrop) 10218 15705 1 0 -1 0 2032 0 nfsrcv D ?? 0:00.00 (eggdrop) 10005 15733 1 0 -1 0 1940 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.23) 1292 21867 1 4 10 0 500 0 wait Is ?? 0:00.00 (sh) 1292 21960 21867 0 10 0 504 0 wait I ?? 0:00.00 (sh) 1292 22149 21960 0 -6 0 1740 0 piperd I ?? 0:00.00 (eggdrop) 1292 22386 22149 1 28 0 0 0 - Z ?? 0:00.00 (uname) 10453 22430 1 0 -1 0 2060 0 nfsrcv D ?? 0:00.00 (eggdrop) 10169 24832 1 0 2 0 1728 0 select S ?? 0:00.00 (eggdrop) 10156 26627 1 0 2 0 752 0 accept Is ?? 0:00.00 (void) 10156 26631 26627 0 2 0 760 0 select I ?? 0:00.00 (void) 1375 28961 1 0 2 0 880 0 select Is ?? 0:00.00 (bnc) 0 30596 1 0 2 0 832 0 select Ss ?? 0:00.00 (syslogd) 0 30688 1 5 2 0 900 0 select Is ?? 0:00.00 (inetd) 0 31951 268 0 10 0 1056 0 wait I ?? 0:00.00 (cron) 0 31952 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 1224 31965 1 1 2 0 860 0 select Is ?? 0:00.00 (bnc) 0 31969 268 0 -6 0 1056 0 piperd I ?? 0:00.00 (cron) 10162 31971 31952 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10478 31974 31969 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 0 31979 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 31995 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 31999 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32001 268 0 -6 0 1056 0 piperd I ?? 0:00.00 (cron) 0 32002 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32003 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32004 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32005 268 0 10 0 1056 0 wait I ?? 0:00.00 (cron) 0 32006 268 0 -6 0 1056 0 piperd I ?? 0:00.00 (cron) 10461 32027 31995 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10144 32031 31999 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10033 32033 32001 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10413 32034 32002 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10413 32035 32003 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10373 32036 32004 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10032 32038 32006 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 0 32042 268 0 -6 0 1056 0 piperd I ?? 0:00.00 (cron) 0 32044 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32048 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32049 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32051 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32054 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32055 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32056 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32059 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32061 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32064 268 0 10 0 1056 0 wait I ?? 0:00.00 (cron) 0 32066 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32071 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32076 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32079 268 0 -6 0 1056 0 piperd I ?? 0:00.00 (cron) 10150 32080 31979 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1345 32083 32042 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10218 32085 32044 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10079 32089 32048 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10391 32090 32049 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1082 32092 32051 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1079 32095 32054 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10237 32096 32055 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10385 32100 32061 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1392 32105 32066 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1294 32110 32071 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1292 32116 32079 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 0 32117 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32118 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32122 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32123 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32124 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32125 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32126 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32132 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 10237 32139 32056 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10173 32140 32059 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1405 32142 32076 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10230 32143 32117 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10230 32144 32118 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1210 32147 32122 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10370 32148 32123 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10216 32149 32124 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10216 32150 32125 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1399 32151 32126 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 1339 32162 32132 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 0 32167 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32168 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 0 32169 268 0 10 0 1056 0 wait I ?? 0:00.00 (cron) 0 32171 268 0 -6 0 1040 0 piperd I ?? 0:00.00 (cron) 10002 32177 32167 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10002 32178 32168 1 10 0 500 0 wait Is ?? 0:00.00 (sh) 1411 32181 32171 0 10 0 500 0 wait Is ?? 0:00.00 (sh) 10478 32193 31974 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10033 32195 32033 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10373 32196 32036 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10162 32200 31971 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10144 32215 32031 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10413 32216 32035 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10032 32217 32038 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10150 32223 32080 0 10 0 504 0 wait I ?? 0:00.00 (sh) 0 32233 31951 0 10 0 1368 0 wait I ?? 0:00.00 (sendmail) 10413 32250 32034 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10237 32255 32096 0 -1 0 492 0 nfsrcv D ?? 0:00.00 (sh) 10218 32258 32085 0 -6 0 500 0 piperd I ?? 0:00.00 (sh) 1392 32262 32105 0 -6 0 500 0 piperd I ?? 0:00.00 (sh) 1272 32265 1 0 -1 0 492 0 nfsrcv D ?? 0:00.00 (sh) 0 32267 32169 0 10 0 1368 0 wait I ?? 0:00.00 (sendmail) 1294 32271 32110 0 -6 0 500 0 piperd I ?? 0:00.00 (sh) 1345 32276 32083 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10237 32278 32139 0 -1 0 492 0 nfsrcv D ?? 0:00.00 (sh) 1292 32279 32116 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10216 32281 32149 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10216 32282 32150 0 10 0 504 0 wait I ?? 0:00.00 (sh) 1399 32283 32151 0 -6 0 504 0 piperd I ?? 0:00.00 (sh) 10385 32289 32100 0 -6 0 504 0 piperd I ?? 0:00.00 (sh) 1339 32291 32162 0 -1 0 500 0 nfsrcv D ?? 0:00.00 (sh) 10370 32292 32148 0 -6 0 504 0 piperd I ?? 0:00.00 (sh) 10002 32293 32177 1 -6 0 500 0 piperd I ?? 0:00.00 (sh) 1210 32296 32147 0 -1 0 492 0 nfsrcv D ?? 0:00.00 (sh) 1079 32297 32095 0 -6 0 504 0 piperd I ?? 0:00.00 (sh) 10002 32298 32178 0 10 0 504 0 wait I ?? 0:00.00 (sh) 1411 32299 32181 0 -6 0 504 0 piperd I ?? 0:00.00 (sh) 10173 32300 32140 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10461 32302 32027 0 -1 0 496 0 nfsrcv D ?? 0:00.00 (sh) 0 32303 32064 0 10 0 1368 0 wait I ?? 0:00.00 (sendmail) 1272 32304 1 0 10 0 500 0 wait I ?? 0:00.00 (sh) 10079 32305 32089 0 -1 0 492 0 nfsrcv D ?? 0:00.00 (sh) 10391 32306 32090 0 -1 0 496 0 nfsrcv D ?? 0:00.00 (sh) 1082 32307 32092 0 -1 0 496 0 nfsrcv D ?? 0:00.00 (sh) 1405 32308 32142 0 -1 0 492 0 nfsrcv D ?? 0:00.00 (sh) 10230 32309 32143 0 10 0 504 0 wait I ?? 0:00.00 (sh) 10230 32310 32144 0 -1 0 500 0 nfsrcv D ?? 0:00.00 (sh) 1200 32311 1 0 -1 0 500 0 nfsrcv D ?? 0:00.00 (sh) 0 32323 32001 6 -6 0 1328 0 piperd I ?? 0:00.00 (sendmail) 0 32328 31969 5 -6 0 1328 0 piperd I ?? 0:00.00 (sendmail) 0 32340 32233 0 2 0 824 0 sbwait Ds ?? 0:00.00 (mail.local) 0 32341 32005 0 10 0 1368 0 wait I ?? 0:00.00 (sendmail) 0 32346 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32348 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32349 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32350 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32351 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32352 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32353 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 1360 32355 32346 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 1360 32356 32348 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 10022 32357 32349 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 10173 32358 32350 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 1272 32359 32351 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 10039 32360 32352 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 1200 32361 32353 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32370 32267 0 -1 0 824 0 nfsrcv Ds ?? 0:00.00 (mail.local) 10373 32393 32196 0 -1 0 1232 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.20) 10033 32398 32195 0 -1 0 1236 0 nfsrcv DL ?? 0:00.00 (eggdrop-1.3.23) 10478 32399 32193 0 -1 0 1236 0 nfsrcv D ?? 0:00.00 (eggdrop) 0 32404 32006 3 -6 0 1328 0 piperd I ?? 0:00.00 (sendmail) 10162 32439 32200 0 -1 0 1232 0 nfsrcv D ?? 0:00.00 (eggdrop) 10144 32452 32215 0 -1 0 1232 0 nfsrcv D ?? 0:00.00 (eggdrop) 10218 32459 32258 0 -1 0 220 0 nfsrcv D ?? 0:00.00 (cat) 1392 32460 32262 0 -1 0 220 0 nfsrcv D ?? 0:00.00 (cat) 1294 32461 32271 0 -1 0 220 0 nfsrcv D ?? 0:00.00 (cat) 10032 32462 32217 0 -1 0 504 0 nfsrcv D ?? 0:00.00 (sh) 0 32463 32042 4 -6 0 1328 0 piperd I ?? 0:00.00 (sendmail) 10413 32464 32250 0 -1 0 504 0 nfsrcv D ?? 0:00.00 (sh) 10150 32472 32223 0 -1 0 1580 0 nfsrcv D ?? 0:00.00 (eggdrop) 10413 32506 32216 0 -1 0 504 0 nfsrcv D ?? 0:00.00 (sh) 0 32509 32079 4 -6 0 1328 0 piperd I ?? 0:00.00 (sendmail) 0 32511 32341 0 -1 0 824 0 nfsrcv Ds ?? 0:00.00 (mail.local) 10216 32513 32282 0 -1 0 504 0 nfsrcv D ?? 0:00.00 (sh) 0 32516 32303 0 -1 0 824 0 nfsrcv Ds ?? 0:00.00 (mail.local) 10370 32522 32292 0 -1 0 220 0 nfsrcv D ?? 0:00.00 (cat) 10385 32523 32289 0 -1 0 220 0 nfsrcv D ?? 0:00.00 (cat) 1079 32525 32297 0 -1 0 220 0 nfsrcv D ?? 0:00.00 (cat) 10216 32528 32281 0 -1 0 180 0 nfsrcv D ?? 0:00.00 (test) 1292 32529 32279 0 -1 0 504 0 nfsrcv D ?? 0:00.00 (sh) 1272 32530 32304 0 -1 0 500 0 nfsrcv D ?? 0:00.00 (sh) 10230 32531 32309 0 -1 0 180 0 nfsrcv D ?? 0:00.00 (test) 1411 32532 32299 0 -1 0 196 0 nfsrcv D ?? 0:00.00 (cat) 10002 32533 32293 0 -1 0 196 0 nfsrcv D ?? 0:00.00 (cat) 10002 32536 32298 0 -1 0 180 0 nfsrcv D ?? 0:00.00 (test) 10173 32537 32300 0 -1 0 180 0 nfsrcv D ?? 0:00.00 (test) 1399 32538 32283 0 -1 0 196 0 nfsrcv D ?? 0:00.00 (cat) 1345 32539 32276 0 -1 0 180 0 nfsrcv D ?? 0:00.00 (test) 0 32540 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32541 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32542 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32543 32540 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32544 32541 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32545 32542 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32546 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32547 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32548 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32549 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32550 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32551 32546 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32552 32547 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32553 32548 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32554 32549 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32555 32550 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32556 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32557 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32558 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32559 32556 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32560 32557 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32561 32558 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32562 551 0 10 0 500 0 wait I ?? 0:00.00 (sh) 0 32564 32562 0 -1 0 204 0 nfsrcv D ?? 0:00.00 (df) 0 32565 32562 0 -6 0 956 0 piperd I ?? 0:00.00 (grep) 0 32566 32562 0 -6 0 956 0 piperd I ?? 0:00.00 (grep) 0 32567 32562 0 -1 0 500 0 nfsrcv D ?? 0:00.00 (sh) 0 32569 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32570 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32571 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32572 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32573 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32574 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32575 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32576 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32577 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32578 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32579 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32580 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32582 32569 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32583 32570 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32584 32571 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32585 32572 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32586 32573 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32587 32574 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32588 32575 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32589 32576 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32590 32577 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32591 32578 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32592 32580 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32593 32579 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32595 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32596 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32597 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32598 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32599 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32600 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32601 32595 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32602 32596 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32603 32597 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32604 32598 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32605 32599 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32606 32600 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32607 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32608 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32609 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32610 32607 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32611 32608 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32612 32609 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32613 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32614 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32615 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32616 32613 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32617 32614 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32618 32615 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32619 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32620 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32621 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32622 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32623 32619 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32624 32620 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32625 32621 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32626 32622 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32627 268 0 -6 0 1040 0 piperd S ?? 0:00.00 (cron) 0 32628 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32629 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32630 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32631 268 0 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32632 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32633 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32634 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32635 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32636 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32637 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32638 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32639 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32640 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32641 268 1 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32642 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32643 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32644 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32645 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32646 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32647 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32648 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32649 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32650 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32651 268 3 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32652 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32653 268 2 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32654 32627 1 28 0 480 0 - Rs ?? 0:00.00 (sh) 0 32655 32628 1 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32656 32629 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32657 32630 0 -1 0 1024 0 nfsrcv DVs ?? 0:00.00 (cron) 0 32658 32631 8 30 0 1024 0 - RVs ?? 0:00.00 (cron) 0 32681 268 3 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32682 268 3 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32683 268 3 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32684 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32685 268 3 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32686 268 3 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32687 268 3 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32688 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32689 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32690 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32691 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32692 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32693 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32694 268 5 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32695 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32696 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32697 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32698 268 4 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32699 268 5 10 0 1024 0 ppwait D ?? 0:00.00 (cron) 0 32700 32681 3 28 0 1024 0 - RV ?? 0:00.00 (cron) 0 32701 32682 3 28 0 1024 0 - RV ?? 0:00.00 (cron) 0 32702 32683 3 28 0 1024 0 - RV ?? 0:00.00 (cron) 0 32703 32684 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32704 32685 3 28 0 1024 0 - RV ?? 0:00.00 (cron) 0 32705 32686 3 28 0 1024 0 - RV ?? 0:00.00 (cron) 0 32706 32687 3 28 0 1024 0 - RV ?? 0:00.00 (cron) 0 32707 32688 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32708 32689 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32709 32690 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32710 32691 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32711 32692 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32712 32693 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32713 32694 5 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32714 32695 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32715 32696 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32716 32697 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32717 32698 4 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32718 32699 5 29 0 1024 0 - RV ?? 0:00.00 (cron) 0 32719 268 5 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32720 268 5 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32721 268 5 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32722 268 5 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32723 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32724 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32725 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32726 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32727 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32728 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32729 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32730 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32731 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32732 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32733 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32734 268 6 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32735 268 7 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32736 268 7 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32737 268 7 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32738 268 7 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32739 268 7 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32740 268 7 29 0 1024 0 - R ?? 0:00.00 (cron) 0 32741 268 7 29 0 1024 0 - R ?? 0:00.00 (cron) 1409 36792 1 0 2 0 1164 0 select Ss ?? 0:00.00 (ez) 10179 45186 1 0 2 0 880 0 select Is ?? 0:00.00 (bnc) 1112 52234 1 0 2 0 888 0 select Is ?? 0:00.00 (bnc) 10433 60820 1 105 2 0 860 0 select Is ?? 0:00.00 (bnc) 10285 75035 1 0 -1 0 1752 0 nfsrcv D ?? 0:00.00 (eggdrop) 10246 75648 1 0 2 0 872 0 select Is ?? 0:00.00 (bnc) 1386 84802 1 0 2 0 904 0 select Is ?? 0:00.00 (bnc) 10027 88359 1 0 -1 0 1696 0 nfsrcv D ?? 0:00.00 (eggdrop) 10456 88871 1 0 2 0 876 0 select Is ?? 0:00.00 (bnc) 1033 88967 1 0 2 0 888 0 select Is ?? 0:00.00 (bnc) 10373 89648 1 0 -1 0 2000 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.20) 10373 92351 1 0 -1 0 2000 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.20) 10373 93684 1 0 -1 0 2000 0 nfsrcv D ?? 0:00.00 (eggdrop-1.3.20) 10334 94888 1 0 -1 0 2060 0 nfsrcv D ?? 0:00.00 (eggdrop) 10334 94891 1 0 -1 0 2028 0 nfsrcv D ?? 0:00.00 (eggdrop) 1224 95244 1 1 2 0 860 0 select Is ?? 0:00.00 (bnc) 10334 96485 1 0 -1 0 2028 0 nfsrcv D ?? 0:00.00 (eggdrop) 10176 3615 1 0 -1 0 2008 0 nfsrcv D p0- 0:00.00 (eggdrop-1.3.26) 1001 3755 3754 216 10 0 1480 0 wait Is p0 0:00.00 (bash) 0 4426 3755 4 3 0 1492 0 ttyin I+ p0 0:00.00 (bash) 10156 7275 1 0 -1 0 1848 0 nfsrcv D p1- 0:00.00 (eggdrop-1.3.23) 1256 8657 1 0 -1 0 1924 0 nfsrcv D p1- 0:00.00 (eggdrop-1.3.23) 10296 14825 1 0 -1 0 1792 0 nfsrcv D p1- 0:00.00 (eggdrop-1.3.22) 1368 20494 1 0 -1 0 1884 0 nfsrcv D p1- 0:00.00 (eggdrop) 1309 33779 1 0 -1 0 3580 0 nfsrcv D p1- 0:00.00 (eggdrop) 1127 34894 1 0 -1 0 1748 0 nfsrcv D p1- 0:00.00 (eggdrop) 1409 36668 1 0 -1 0 1832 0 nfsrcv D p1- 0:00.00 (eggdrop-1.3.23) 10179 45016 1 0 -1 0 1692 0 nfsrcv D p1- 0:00.00 (eggdrop) 10177 79282 1 0 -1 0 2092 0 nfsrcv D p1- 0:00.00 (eggdrop) 10177 79292 1 0 2 0 2128 0 select S p1- 0:00.00 (eggdrop) 10218 79568 1 0 -1 0 2088 0 nfsrcv D p1- 0:00.00 (eggdrop) 10111 80562 1 0 -1 0 1984 0 nfsrcv D p1- 0:00.00 (eggdrop-1.3.20) 10370 82174 1 0 -1 0 1704 0 nfsrcv D p1- 0:00.00 (eggdrop) 10088 8331 1 0 2 0 1728 0 select S p2- 0:00.00 (eggdrop) 10288 18752 1 0 -1 0 1932 0 nfsrcv D p2- 0:00.00 (eggdrop-1.3.23) 10367 21178 1 0 -1 0 1884 0 nfsrcv D p2- 0:00.00 (eggdrop) 10367 21665 1 0 -1 0 1828 0 nfsrcv D p2- 0:00.00 (eggdrop) 10393 28088 1 0 -1 0 1836 0 nfsrcv D p2- 0:00.00 (eggdrop) 10393 28150 1 0 -1 0 1836 0 nfsrcv D p2- 0:00.00 (eggdrop) 10304 41624 1 0 -1 0 1824 0 nfsrcv D p2- 0:00.00 (eggdrop-1.3.23) 10304 41648 1 0 -1 0 1848 0 nfsrcv D p2- 0:00.00 (eggdrop-1.3.23) 10304 41803 1 0 -1 0 2048 0 nfsrcv D p2- 0:00.00 (eggdrop-1.3.23) 10453 44806 1 0 -1 0 2164 0 nfsrcv D p2- 0:00.00 (eggdrop) 10453 45071 1 0 -1 0 2160 0 nfsrcv D p2- 0:00.00 (eggdrop) 10232 49741 1 0 -1 0 1684 0 nfsrcv D p2- 0:00.00 (eggdrop) 10246 80768 1 0 2 0 1980 0 select S p2- 0:00.00 (eggdrop) 10220 86178 1 0 -1 0 2040 0 nfsrcv D p2- 0:00.00 (eggdrop) 10220 86184 1 0 -1 0 2028 0 nfsrcv D p2- 0:00.00 (eggdrop) 10113 91038 1 0 -1 0 2472 0 nfsrcv D p2- 0:00.00 (eggdrop-1.3.23) 10462 4772 1 0 -1 0 1748 0 nfsrcv D p3- 0:00.00 (eggdrop) 10462 4864 1 0 -1 0 1728 0 nfsrcv D p3- 0:00.00 (eggdrop) 10005 8595 1 0 -1 0 1936 0 nfsrcv D p3- 0:00.00 (eggdrop-1.3.23) 1107 12871 1 0 -1 0 1648 0 nfsrcv D p3- 0:00.00 (eggdrop) 1376 24341 1 0 -1 0 1920 0 nfsrcv D p3- 0:00.00 (eggdrop) 1376 24345 1 0 -1 0 1884 0 nfsrcv D p3- 0:00.00 (eggdrop) 1224 25152 1 0 -1 0 2356 0 nfsrcv D p3- 0:00.00 (eggdrop) 1375 29220 1 0 -1 0 1828 0 nfsrcv D p3- 0:00.00 (eggdrop) 10331 32423 1 0 -1 0 1844 0 nfsrcv D p3- 0:00.00 (eggdrop) 10007 37220 1 0 -1 0 2152 0 nfsrcv D p3- 0:00.00 (eggdrop) 10007 37257 1 0 -1 0 1920 0 nfsrcv D p3- 0:00.00 (eggdrop) 1108 38958 1 0 -1 0 1908 0 nfsrcv D p3- 0:00.00 (eggdrop) 10108 40001 1 0 -1 0 1780 0 nfsrcv D p3- 0:00.00 (eggdrop) 10353 86270 1 0 -1 0 1996 0 nfsrcv D p3- 0:00.00 (eggdrop-1.3.23) 10353 86272 1 0 -1 0 1952 0 nfsrcv D p3- 0:00.00 (eggdrop-1.3.23) 1313 92304 1 0 -1 0 1848 0 nfsrcv D p3- 0:00.00 (eggdrop) 1257 92564 1 0 2 0 1796 0 select S p3- 0:00.00 (eggdrop) 10407 95256 1 0 -1 0 1948 0 nfsrcv D p3- 0:00.00 (eggdrop) 10407 95259 1 0 -1 0 1904 0 nfsrcv D p3- 0:00.00 (eggdrop) 10162 26898 1 0 -1 0 1844 0 nfsrcv D p4- 0:00.00 (eggdrop) 10465 43903 1 0 -1 0 1908 0 nfsrcv D p4- 0:00.00 (eggdrop) 1226 62265 1 0 2 0 1296 0 sbwait D p4- 0:00.00 (eggdrop) 10236 66410 1 0 -1 0 1712 0 nfsrcv D p4- 0:00.00 (eggie) 10236 66553 1 0 -1 0 1712 0 nfsrcv D p4- 0:00.00 (eggie) 10236 66597 1 0 -1 0 1716 0 nfsrcv D p4- 0:00.00 (eggie) 1349 77859 1 0 -1 0 1876 0 nfsrcv D p4- 0:00.00 (eggdrop) 10024 95795 1 0 -1 0 1744 0 nfsrcv D p4- 0:00.00 (eggdrop) 10024 96307 1 0 -1 0 1732 0 nfsrcv D p4- 0:00.00 (eggdrop) 10024 96461 1 0 -1 0 1744 0 nfsrcv D p4- 0:00.00 (eggdrop) 1082 16808 1 0 -1 0 1824 0 nfsrcv D p5- 0:00.00 (eggdrop3) 1082 17117 1 0 -1 0 1724 0 nfsrcv D p5- 0:00.00 (eggdrop3) 1336 27506 1 0 -1 0 1728 0 nfsrcv D p5- 0:00.00 (eggdrop) 10169 54544 1 0 2 0 1780 0 select S p5- 0:00.00 (eggdrop) 10021 1148 1 0 -1 0 1964 0 nfsrcv D p6- 0:00.00 (eggdrop-1.3.23) 10019 39399 1 0 -1 0 1720 0 nfsrcv D p6- 0:00.00 (eggdrop) 10019 39410 1 0 -1 0 1708 0 nfsrcv D p6- 0:00.00 (eggdrop) 10130 48190 1 0 -1 0 1884 0 nfsrcv D p6- 0:00.00 (eggdrop-1.3.22) 10039 53701 1 0 -1 0 1684 0 nfsrcv D p6- 0:00.00 (eggdrop) 10400 75063 1 0 2 0 1808 0 select S p9- 0:00.00 (eggdrop-1.3.22) 10298 77032 1 0 -1 0 2284 0 nfsrcv D p9- 0:00.00 (BitchX) 0 1771 1 0 3 0 844 0 ttyin Is+ v0 0:00.00 (getty) 0 628 1 0 3 0 844 0 ttyin Is+ v1 0:00.00 (getty) 0 630 1 0 3 0 844 0 ttyin Is+ v2 0:00.00 (getty) 0 551 1 0 10 0 508 0 wait I con- 0:00.00 (sh) The large number of cron's appeared because it crashed right at 3am. (daily jobs ran, plus nearly every user has */10 for their cron jobs.) I haven't moved my high-load cron patches on this server yet, but i will soon. > netstat -tna -M vmcore.XX -N kernel.XX Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 205.253.12.174.6001 208.240.218.223.28502 TIME_WAIT tcp 0 1606 205.253.12.5.23 206.98.59.154.1356 ESTABLISHED tcp 0 0 205.253.12.166.4444 204.137.237.69.3563 ESTABLISHED tcp 17376 0 205.253.12.182.1035 209.180.211.153.16982 ESTABLISHED tcp 0 0 205.253.12.182.1034 212.41.33.220.1215 CLOSE_WAIT tcp 17376 0 205.253.12.182.1032 207.7.4.10.7000 ESTABLISHED tcp 0 0 *.10509 *.* LISTEN tcp 0 0 *.32222 *.* LISTEN tcp 0 0 205.253.12.164.1031 209.180.211.153.16982 ESTABLISHED tcp 0 0 205.253.12.164.1030 207.152.95.10.6668 ESTABLISHED tcp 0 0 *.34567 *.* LISTEN tcp 0 0 *.23456 *.* LISTEN tcp 0 0 205.253.12.160.4952 209.127.0.53.6669 ESTABLISHED tcp 0 0 205.253.12.160.5050 *.* LISTEN tcp 0 0 205.253.12.160.6500 *.* LISTEN tcp 0 0 205.253.12.176.4785 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.176.4609 24.218.61.130.2600 ESTABLISHED tcp 0 0 205.253.12.163.4605 24.218.61.130.2600 ESTABLISHED tcp 0 0 205.253.12.164.4384 207.173.16.33.6667 ESTABLISHED tcp 0 0 205.253.12.189.28596 209.47.225.4.7396 ESTABLISHED tcp 0 0 205.253.12.165.4219 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.164.4006 205.134.175.92.1562 ESTABLISHED tcp 0 0 205.253.12.164.3938 209.162.144.11.6667 ESTABLISHED tcp 0 0 205.253.12.161.3905 209.127.0.53.6669 ESTABLISHED tcp 0 0 205.253.12.161.5060 *.* LISTEN tcp 0 0 205.253.12.161.6500 *.* LISTEN tcp 0 0 205.253.12.5.23 195.95.41.193.1096 ESTABLISHED tcp 0 0 205.253.12.163.3666 209.162.144.11.6667 ESTABLISHED tcp 0 0 205.253.12.176.3632 209.162.144.11.6667 ESTABLISHED tcp 0 0 204.137.237.5.3544 207.178.128.109.6667 ESTABLISHED tcp 0 0 205.253.12.172.3254 151.198.193.195.32069 ESTABLISHED tcp 0 0 205.253.12.182.3175 199.8.156.8.2987 ESTABLISHED tcp 0 0 205.253.12.182.3162 216.24.134.10.6667 ESTABLISHED tcp 0 0 205.253.12.164.3150 199.8.156.8.2987 ESTABLISHED tcp 0 0 205.253.12.182.16999 *.* LISTEN tcp 9 0 205.253.12.182.3102 195.36.145.7.61432 CLOSE_WAIT tcp 9 0 205.253.12.185.3101 195.36.145.7.61431 CLOSE_WAIT tcp 0 0 205.253.12.164.4749 *.* LISTEN tcp 0 0 205.253.12.169.2824 208.218.89.7.6667 ESTABLISHED tcp 0 0 205.253.12.169.4025 *.* LISTEN tcp 0 0 205.253.12.169.4024 *.* LISTEN tcp 0 0 205.253.12.166.4187 209.224.97.21.14521 ESTABLISHED tcp 0 0 205.253.12.166.4187 209.224.97.19.16264 ESTABLISHED tcp 0 0 205.253.12.205.2597 209.83.197.69.2000 ESTABLISHED tcp 0 0 205.253.12.160.2390 206.252.192.20.5555 ESTABLISHED tcp 0 0 205.253.12.5.1226 209.96.3.88.1343 ESTABLISHED tcp 0 0 *.1226 *.* LISTEN tcp 0 0 205.253.12.166.2320 207.69.200.131.6667 ESTABLISHED tcp 0 0 205.253.12.165.5555 24.112.126.47.3265 ESTABLISHED tcp 0 0 205.253.12.165.5555 24.112.126.47.3207 ESTABLISHED tcp 0 0 205.253.12.165.5555 138.74.72.71.21230 ESTABLISHED tcp 0 0 205.253.12.166.2091 209.186.61.5.12666 ESTABLISHED tcp 0 0 205.253.12.185.2029 24.200.14.149.4668 CLOSE_WAIT tcp 17376 0 205.253.12.185.2001 206.252.192.20.5555 ESTABLISHED tcp 0 0 205.253.12.164.1971 207.46.185.15.6667 ESTABLISHED tcp 0 0 205.253.12.166.1803 207.46.185.15.6667 ESTABLISHED tcp 0 0 204.137.237.5.1798 207.46.185.15.6667 ESTABLISHED tcp 4629 0 205.253.12.182.1763 194.98.81.69.25252 CLOSE_WAIT tcp 0 0 205.253.12.182.1718 24.200.14.149.2891 CLOSE_WAIT tcp 0 0 205.253.12.182.1685 195.200.170.192.61410 ESTABLISHED tcp 3899 0 205.253.12.182.1669 206.252.192.20.5555 CLOSE_WAIT tcp 0 0 205.253.12.169.1558 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.169.50000 *.* LISTEN tcp 0 0 205.253.12.174.1530 206.86.182.38.10001 ESTABLISHED tcp 0 0 205.253.12.171.1478 203.58.57.156.2591 ESTABLISHED tcp 0 0 205.253.12.171.1467 209.198.8.200.6667 ESTABLISHED tcp 0 0 205.253.12.171.41720 *.* LISTEN tcp 0 0 205.253.12.164.4858 204.137.237.87.4100 ESTABLISHED tcp 0 0 205.253.12.164.4800 209.162.144.11.6667 ESTABLISHED tcp 0 0 205.253.12.164.4150 *.* LISTEN tcp 0 0 205.253.12.164.4689 207.154.210.5.6667 ESTABLISHED tcp 0 0 205.253.12.182.4649 206.252.192.20.5555 ESTABLISHED tcp 0 0 *.37011 *.* LISTEN tcp 0 0 205.253.12.174.4365 209.68.218.99.1028 ESTABLISHED tcp 0 0 205.253.12.165.4062 209.198.8.200.6667 ESTABLISHED tcp 0 0 205.253.12.170.4061 206.66.12.230.7002 ESTABLISHED tcp 0 0 205.253.12.160.3332 206.252.192.20.5556 ESTABLISHED tcp 0 0 205.253.12.171.3310 206.252.192.20.6667 ESTABLISHED tcp 0 0 205.253.12.173.3244 206.252.192.20.6667 ESTABLISHED tcp 0 0 205.253.12.200.3156 206.252.192.20.6667 ESTABLISHED tcp 0 0 205.253.12.185.3155 206.252.192.20.6667 ESTABLISHED tcp 0 0 205.253.12.182.3142 207.7.4.10.7000 ESTABLISHED tcp 0 0 205.253.12.162.3107 209.162.144.11.6662 ESTABLISHED tcp 0 0 205.253.12.173.3343 204.137.237.69.4443 ESTABLISHED tcp 0 0 205.253.12.173.2414 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.173.3343 *.* LISTEN tcp 0 0 *.4010 *.* LISTEN tcp 0 0 205.253.12.189.1061 209.127.0.51.6667 ESTABLISHED tcp 0 0 *.56614 *.* LISTEN tcp 0 0 *.46614 *.* LISTEN tcp 0 0 *.36614 *.* LISTEN tcp 0 0 *.26614 *.* LISTEN tcp 0 0 *.16615 *.* LISTEN tcp 0 0 204.137.237.5.2992 204.137.237.88.1122 ESTABLISHED tcp 0 0 205.253.12.172.4183 207.154.210.5.6666 ESTABLISHED tcp 0 0 205.253.12.173.4039 207.142.185.250.15866 ESTABLISHED tcp 0 0 *.9789 *.* LISTEN tcp 0 0 *.58305 *.* LISTEN tcp 0 0 205.253.12.173.3392 207.142.185.250.2357 ESTABLISHED tcp 0 0 205.253.12.182.3386 194.249.251.20.15000 ESTABLISHED tcp 0 0 *.26599 *.* LISTEN tcp 0 0 205.253.12.161.3349 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.161.3297 209.224.62.191.10123 ESTABLISHED tcp 0 0 205.253.12.161.26868 *.* LISTEN tcp 0 0 204.137.237.5.2992 198.175.15.229.40768 ESTABLISHED tcp 0 0 205.253.12.204.2633 205.253.12.76.25555 ESTABLISHED tcp 0 0 205.253.12.204.2629 207.221.83.119.1047 ESTABLISHED tcp 0 0 205.253.12.172.2494 209.123.12.32.6667 ESTABLISHED tcp 0 0 205.253.12.172.2444 207.90.208.103.44141 ESTABLISHED tcp 0 0 205.253.12.172.41721 *.* LISTEN tcp 0 0 205.253.12.173.2343 208.206.78.231.4517 ESTABLISHED tcp 0 0 205.253.12.163.2285 207.154.210.5.6667 ESTABLISHED tcp 0 0 205.253.12.165.5555 150.254.5.89.4418 ESTABLISHED tcp 0 0 205.253.12.200.1661 209.127.0.53.6666 ESTABLISHED tcp 0 0 205.253.12.169.1617 207.154.210.5.6666 ESTABLISHED tcp 0 0 205.253.12.200.1607 209.100.125.34.25001 ESTABLISHED tcp 0 0 205.253.12.200.10555 *.* LISTEN tcp 0 0 205.253.12.185.1602 128.138.129.31.6666 ESTABLISHED tcp 0 0 205.253.12.185.1601 209.100.125.34.25001 ESTABLISHED tcp 0 0 205.253.12.185.19005 *.* LISTEN tcp 0 0 205.253.12.169.1556 209.100.125.34.25001 ESTABLISHED tcp 0 0 205.253.12.169.18000 *.* LISTEN tcp 0 0 205.253.12.177.1506 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.167.2800 205.253.12.174.1483 ESTABLISHED tcp 0 0 205.253.12.174.1483 205.253.12.167.2800 ESTABLISHED tcp 0 0 205.253.12.167.2800 195.148.66.242.2257 ESTABLISHED tcp 0 0 205.253.12.168.1449 209.127.0.53.6667 ESTABLISHED tcp 0 0 205.253.12.167.2800 212.71.70.101.1676 ESTABLISHED tcp 0 0 205.253.12.167.1441 209.127.0.53.6667 ESTABLISHED tcp 0 0 205.253.12.177.3800 205.253.12.167.1439 ESTABLISHED tcp 0 0 205.253.12.167.1439 205.253.12.177.3800 ESTABLISHED tcp 0 0 205.253.12.167.2800 *.* LISTEN tcp 0 0 205.253.12.177.3800 *.* LISTEN tcp 0 0 205.253.12.174.1389 209.127.0.53.6667 ESTABLISHED tcp 0 0 205.253.12.174.4800 *.* LISTEN tcp 0 0 205.253.12.168.3333 *.* LISTEN tcp 0 0 *.4711 *.* LISTEN tcp 0 0 204.137.237.5.2992 208.245.174.68.1491 ESTABLISHED tcp 0 0 205.253.12.166.3500 *.* LISTEN tcp 0 0 205.253.12.175.4328 207.96.122.240.6668 ESTABLISHED tcp 0 0 205.253.12.202.4323 207.96.122.240.6668 ESTABLISHED tcp 0 0 205.253.12.174.3667 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.166.4187 205.253.12.162.3482 ESTABLISHED tcp 0 0 205.253.12.162.3482 205.253.12.166.4187 ESTABLISHED tcp 0 0 205.253.12.169.3459 204.137.237.139.61110 ESTABLISHED tcp 0 0 205.253.12.174.1661 *.* LISTEN tcp 0 0 205.253.12.167.3090 209.100.44.242.6285 ESTABLISHED tcp 0 0 205.253.12.167.3074 209.123.12.32.6663 ESTABLISHED tcp 0 0 205.253.12.167.5275 *.* LISTEN tcp 0 0 205.253.12.5.2488 24.128.200.96.3739 ESTABLISHED tcp 0 0 205.253.12.189.5726 *.* LISTEN tcp 0 0 205.253.12.5.2399 209.127.0.53.6667 ESTABLISHED tcp 0 0 *.9119 *.* LISTEN tcp 0 0 205.253.12.166.1731 209.127.0.53.6667 ESTABLISHED tcp 0 0 205.253.12.173.1729 209.123.12.32.6667 ESTABLISHED tcp 0 0 205.253.12.173.1726 207.19.136.93.10000 ESTABLISHED tcp 0 0 205.253.12.173.15357 *.* LISTEN tcp 0 0 205.253.12.172.20322 216.65.27.109.3929 ESTABLISHED tcp 0 0 205.253.12.169.1555 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.169.16140 *.* LISTEN tcp 0 0 205.253.12.169.15140 *.* LISTEN tcp 0 0 205.253.12.171.1224 195.61.112.181.55666 ESTABLISHED tcp 0 0 205.253.12.173.4911 206.31.232.17.20000 ESTABLISHED tcp 0 0 204.137.237.5.3728 204.137.237.8.8751 ESTABLISHED tcp 0 0 205.253.12.163.3100 204.137.237.60.24720 ESTABLISHED tcp 0 0 205.253.12.163.33229 *.* LISTEN tcp 0 0 205.253.12.174.6001 208.196.56.163.1171 ESTABLISHED tcp 0 0 205.253.12.189.28596 24.200.25.97.2649 ESTABLISHED tcp 0 0 205.253.12.189.28596 24.200.90.45.9282 ESTABLISHED tcp 0 0 205.253.12.161.2616 202.184.151.7.21211 ESTABLISHED tcp 0 0 205.253.12.161.2615 194.159.80.20.6667 ESTABLISHED tcp 0 0 *.17889 *.* LISTEN tcp 0 0 *.8751 *.* LISTEN tcp 0 0 *.3290 *.* LISTEN tcp 0 0 205.253.12.161.29873 195.0.100.253.22673 ESTABLISHED tcp 0 0 205.253.12.161.2411 194.159.80.20.6666 ESTABLISHED tcp 0 0 *.29873 *.* LISTEN tcp 0 0 205.253.12.163.2022 209.123.12.32.8000 ESTABLISHED tcp 0 0 205.253.12.163.9393 *.* LISTEN tcp 0 0 205.253.12.163.3939 *.* LISTEN tcp 0 0 205.253.12.177.1379 209.96.2.134.6666 ESTABLISHED tcp 0 0 205.253.12.177.1377 209.180.140.18.45000 ESTABLISHED tcp 0 0 205.253.12.177.7090 *.* LISTEN tcp 0 0 *.9786 *.* LISTEN tcp 0 0 205.253.12.171.4487 209.207.230.1.6667 ESTABLISHED tcp 0 0 205.253.12.171.3369 *.* LISTEN tcp 0 0 205.253.12.185.4876 216.65.50.160.1054 ESTABLISHED tcp 0 0 205.253.12.185.4876 216.65.50.134.1048 ESTABLISHED tcp 0 0 205.253.12.185.4876 216.65.50.133.1045 ESTABLISHED tcp 0 0 205.253.12.185.3717 207.154.210.5.6667 ESTABLISHED tcp 0 0 205.253.12.172.3653 209.127.0.51.6666 ESTABLISHED tcp 0 0 205.253.12.173.3609 209.180.211.153.16982 ESTABLISHED tcp 0 0 205.253.12.174.6001 208.240.218.223.25675 ESTABLISHED tcp 0 0 205.253.12.200.3353 193.215.253.230.48900 ESTABLISHED tcp 0 0 205.253.12.172.20322 216.65.27.47.1420 ESTABLISHED tcp 0 0 205.253.12.172.3189 198.175.15.229.20322 ESTABLISHED tcp 0 0 *.20322 *.* LISTEN tcp 0 0 205.253.12.174.2921 208.240.218.227.16050 ESTABLISHED tcp 0 0 205.253.12.165.2792 209.100.44.242.9339 ESTABLISHED tcp 0 0 205.253.12.174.6001 205.253.12.88.2547 ESTABLISHED tcp 0 0 204.137.237.5.2720 207.154.210.5.6667 ESTABLISHED tcp 0 0 205.253.12.166.8980 199.166.24.163.2236 ESTABLISHED tcp 0 0 205.253.12.166.8980 63.67.171.175.8491 ESTABLISHED tcp 0 0 205.253.12.166.8980 207.88.31.116.8345 ESTABLISHED tcp 0 0 205.253.12.166.8980 209.54.43.135.4548 ESTABLISHED tcp 0 0 205.253.12.166.8980 209.54.43.146.4546 ESTABLISHED tcp 0 0 205.253.12.185.4876 207.7.5.216.4704 ESTABLISHED tcp 0 0 205.253.12.166.8980 199.166.24.162.2199 FIN_WAIT_2 tcp 0 0 205.253.12.166.23 24.65.158.219.2746 ESTABLISHED tcp 0 0 205.253.12.185.4876 208.220.151.211.1799 ESTABLISHED tcp 0 0 205.253.12.185.1921 207.7.5.218.4876 ESTABLISHED tcp 0 0 205.253.12.166.1919 207.96.122.250.6667 ESTABLISHED tcp 0 0 205.253.12.175.1918 209.127.0.51.6660 ESTABLISHED tcp 0 0 205.253.12.175.3333 *.* LISTEN tcp 0 0 204.137.237.5.1911 204.127.145.17.6661 ESTABLISHED tcp 0 0 205.253.12.185.4876 *.* LISTEN tcp 0 0 205.253.12.166.8980 *.* LISTEN tcp 0 0 205.253.12.163.1720 209.127.0.51.6667 ESTABLISHED tcp 0 0 204.137.237.5.1653 209.207.230.1.6667 ESTABLISHED tcp 0 0 205.253.12.162.1609 12.13.22.35.32520 ESTABLISHED tcp 0 0 205.253.12.165.5555 207.51.47.2.4813 ESTABLISHED tcp 0 0 205.253.12.204.1598 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.165.52782 208.247.113.155.4398 ESTABLISHED tcp 0 0 205.253.12.165.5555 207.51.47.2.4794 ESTABLISHED tcp 0 0 205.253.12.165.5555 207.51.47.2.4793 ESTABLISHED tcp 0 0 205.253.12.165.5555 138.74.72.71.14729 ESTABLISHED tcp 0 0 205.253.12.168.1525 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.168.1523 207.76.224.137.30000 ESTABLISHED tcp 0 0 205.253.12.174.6001 208.240.218.222.22576 ESTABLISHED tcp 0 0 205.253.12.168.50500 *.* LISTEN tcp 0 0 205.253.12.174.6001 205.253.12.178.1489 ESTABLISHED tcp 0 0 205.253.12.178.1489 205.253.12.174.6001 ESTABLISHED tcp 0 0 205.253.12.176.1488 209.118.222.148.10544 ESTABLISHED tcp 0 0 205.253.12.165.52782 205.253.12.167.1480 ESTABLISHED tcp 0 0 205.253.12.167.1480 205.253.12.165.52782 ESTABLISHED tcp 0 0 205.253.12.174.6001 205.253.12.86.2340 ESTABLISHED tcp 0 0 205.253.12.178.1470 207.96.122.240.6666 ESTABLISHED tcp 0 0 205.253.12.164.1466 209.207.230.1.6667 ESTABLISHED tcp 0 0 204.137.237.5.2992 63.67.171.62.3438 ESTABLISHED tcp 0 0 204.137.237.5.2992 63.67.171.43.2964 ESTABLISHED tcp 0 0 204.137.237.5.2992 63.67.171.50.2018 ESTABLISHED tcp 0 0 205.253.12.163.41380 207.233.124.187.16410 ESTABLISHED tcp 0 0 205.253.12.165.5555 205.253.12.166.1452 ESTABLISHED tcp 0 0 205.253.12.166.1452 205.253.12.165.5555 ESTABLISHED tcp 0 0 204.137.237.5.1448 204.127.145.17.6661 ESTABLISHED tcp 0 0 205.253.12.160.1445 128.138.129.31.6667 ESTABLISHED tcp 0 0 205.253.12.174.1442 207.154.210.5.6667 ESTABLISHED tcp 0 0 205.253.12.182.1436 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.178.1432 192.160.127.97.6667 ESTABLISHED tcp 0 0 205.253.12.166.1425 207.154.210.5.6673 ESTABLISHED tcp 0 0 205.253.12.171.1421 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.173.1410 204.137.237.3.6667 ESTABLISHED tcp 0 0 205.253.12.165.1407 204.137.237.3.6667 ESTABLISHED tcp 0 0 205.253.12.173.1404 151.198.193.205.65530 ESTABLISHED tcp 0 0 205.253.12.173.1403 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.165.1401 151.198.193.205.65530 ESTABLISHED tcp 0 0 205.253.12.175.1398 216.65.27.98.3399 ESTABLISHED tcp 0 0 205.253.12.166.1392 216.65.27.98.3399 ESTABLISHED tcp 0 0 205.253.12.202.1391 216.65.27.98.3399 ESTABLISHED tcp 0 0 205.253.12.167.1375 209.123.12.32.6667 ESTABLISHED tcp 0 0 205.253.12.170.1374 209.127.0.53.6667 ESTABLISHED tcp 0 0 205.253.12.166.1372 209.127.0.51.6667 ESTABLISHED tcp 0 0 204.137.237.5.1368 216.111.35.36.9000 ESTABLISHED tcp 3966 0 205.253.12.185.1362 194.98.81.69.25252 CLOSE_WAIT tcp 0 0 205.253.12.165.52782 208.247.113.151.4370 ESTABLISHED tcp 0 0 205.253.12.204.38432 206.58.217.17.22755 ESTABLISHED tcp 0 0 205.253.12.164.5735 204.137.237.88.2250 ESTABLISHED tcp 0 0 205.253.12.164.5735 204.137.237.81.2243 ESTABLISHED tcp 0 0 205.253.12.167.1329 209.127.0.51.6660 ESTABLISHED tcp 0 0 205.253.12.165.1328 209.127.0.51.6660 ESTABLISHED tcp 0 0 205.253.12.162.1325 209.127.0.53.6667 ESTABLISHED tcp 0 0 205.253.12.166.1324 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.165.1323 204.137.237.60.24720 ESTABLISHED tcp 0 0 205.253.12.167.1322 209.100.44.223.22650 ESTABLISHED tcp 0 0 205.253.12.164.1321 204.137.237.60.24720 ESTABLISHED tcp 0 0 205.253.12.166.1320 209.127.0.53.6667 ESTABLISHED tcp 0 0 204.137.237.5.1316 63.67.171.50.4001 ESTABLISHED tcp 0 0 205.253.12.204.38432 209.181.45.214.2027 ESTABLISHED tcp 0 0 205.253.12.166.1307 209.132.113.22.37302 ESTABLISHED tcp 0 0 205.253.12.162.1292 195.0.100.253.32157 ESTABLISHED tcp 0 0 205.253.12.162.1291 207.7.4.10.6667 ESTABLISHED tcp 0 0 205.253.12.164.1287 159.138.5.1.1984 ESTABLISHED tcp 0 0 205.253.12.166.1286 159.138.5.1.1984 ESTABLISHED tcp 0 0 205.253.12.163.41380 205.253.12.204.1280 ESTABLISHED tcp 0 0 205.253.12.204.1280 205.253.12.163.41380 ESTABLISHED tcp 0 0 204.137.237.5.2992 24.112.248.130.8466 ESTABLISHED tcp 0 0 204.137.237.5.2992 24.112.248.130.8329 ESTABLISHED tcp 0 0 205.253.12.165.65530 *.* LISTEN tcp 0 0 205.253.12.173.65520 *.* LISTEN tcp 0 0 *.39541 *.* LISTEN tcp 0 0 205.253.12.166.1270 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.170.1267 205.232.47.15.8989 ESTABLISHED tcp 0 0 205.253.12.204.1259 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.160.1258 206.144.143.15.35158 ESTABLISHED tcp 0 0 205.253.12.183.1253 209.127.0.53.6667 ESTABLISHED tcp 0 0 205.253.12.183.1252 216.140.170.50.25010 ESTABLISHED tcp 0 0 205.253.12.182.1251 216.32.4.15.6464 ESTABLISHED tcp 0 0 205.253.12.205.1244 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.185.1243 193.215.253.230.48900 ESTABLISHED tcp 0 0 205.253.12.164.1242 216.115.72.253.5829 ESTABLISHED tcp 0 0 205.253.12.161.1237 195.18.249.231.6667 ESTABLISHED tcp 0 0 205.253.12.163.1234 216.115.72.253.5829 ESTABLISHED tcp 0 0 205.253.12.166.1230 207.152.95.10.6667 ESTABLISHED tcp 0 0 205.253.12.166.1229 216.65.27.45.7071 ESTABLISHED tcp 0 0 *.5555 *.* LISTEN tcp 0 0 *.7777 *.* LISTEN tcp 0 0 205.253.12.161.1224 206.144.143.15.35158 ESTABLISHED tcp 0 0 205.253.12.163.1222 207.154.210.5.6667 ESTABLISHED tcp 0 0 205.253.12.171.1219 204.137.237.74.64824 ESTABLISHED tcp 0 0 205.253.12.174.6899 *.* LISTEN tcp 0 0 *.13787 *.* LISTEN tcp 0 0 205.253.12.183.25010 *.* LISTEN tcp 0 0 *.13786 *.* LISTEN tcp 0 0 205.253.12.163.1201 207.96.122.240.6667 ESTABLISHED tcp 0 0 205.253.12.164.1198 207.154.210.5.6667 ESTABLISHED tcp 0 0 205.253.12.185.50200 *.* LISTEN tcp 0 0 205.253.12.185.50100 *.* LISTEN tcp 0 0 205.253.12.182.50200 *.* LISTEN tcp 0 0 205.253.12.182.50101 *.* LISTEN tcp 0 0 205.253.12.166.3366 *.* LISTEN tcp 0 0 205.253.12.166.3399 *.* LISTEN tcp 0 0 205.253.12.175.3366 *.* LISTEN tcp 0 0 205.253.12.175.3399 *.* LISTEN tcp 0 0 204.137.237.5.2992 *.* LISTEN tcp 0 0 205.253.12.164.5735 *.* LISTEN tcp 0 0 205.253.12.171.45017 *.* LISTEN tcp 0 0 205.253.12.202.3366 *.* LISTEN tcp 0 0 205.253.12.202.3399 *.* LISTEN tcp 0 0 *.48987 *.* LISTEN tcp 0 0 205.253.12.166.37202 *.* LISTEN tcp 0 0 205.253.12.166.3333 *.* LISTEN tcp 0 0 205.253.12.166.4444 *.* LISTEN tcp 0 0 205.253.12.204.38432 *.* LISTEN tcp 0 0 205.253.12.167.22350 *.* LISTEN tcp 0 0 205.253.12.163.41380 *.* LISTEN tcp 0 0 205.253.12.167.42782 *.* LISTEN tcp 0 0 205.253.12.165.52782 *.* LISTEN tcp 0 0 205.253.12.163.2217 *.* LISTEN tcp 0 0 205.253.12.176.10544 *.* LISTEN tcp 0 0 *.26666 *.* LISTEN tcp 0 0 *.24432 *.* LISTEN tcp 0 0 *.24444 *.* LISTEN tcp 0 0 205.253.12.165.23691 *.* LISTEN tcp 0 0 205.253.12.171.15705 *.* LISTEN tcp 0 0 *.5656 *.* LISTEN tcp 0 0 *.7753 *.* LISTEN tcp 0 0 205.253.12.164.8065 *.* LISTEN tcp 0 0 205.253.12.178.11099 *.* LISTEN tcp 0 0 *.31351 *.* LISTEN tcp 0 0 *.6030 *.* LISTEN tcp 0 0 *.31350 *.* LISTEN tcp 0 0 205.253.12.162.3187 *.* LISTEN tcp 0 0 205.253.12.166.4187 *.* LISTEN tcp 0 0 *.10352 *.* LISTEN tcp 0 0 *.15070 *.* LISTEN tcp 0 0 *.20009 *.* LISTEN tcp 0 0 *.22222 *.* LISTEN tcp 0 0 205.253.12.174.6001 *.* LISTEN tcp 0 0 205.253.12.178.5152 *.* LISTEN tcp 0 0 205.253.12.164.2204 *.* LISTEN tcp 0 0 205.253.12.164.23840 *.* LISTEN tcp 0 0 205.253.12.166.1884 *.* LISTEN tcp 0 0 *.22000 *.* LISTEN tcp 0 0 *.9936 *.* LISTEN tcp 0 0 204.137.237.5.4501 *.* LISTEN tcp 0 0 *.1536 *.* LISTEN tcp 0 0 *.2988 *.* LISTEN tcp 0 0 *.7000 *.* LISTEN tcp 0 0 205.253.12.182.11111 205.253.12.77.1705 ESTABLISHED tcp 0 0 205.253.12.168.21680 198.236.98.156.4179 ESTABLISHED tcp 0 0 205.253.12.182.1139 194.119.240.245.3434 ESTABLISHED tcp 0 0 205.253.12.182.11111 *.* LISTEN tcp 0 0 205.253.12.185.1137 199.184.119.1.4444 ESTABLISHED tcp 0 0 205.253.12.168.21680 205.253.12.166.1127 ESTABLISHED tcp 0 0 205.253.12.166.1127 205.253.12.168.21680 ESTABLISHED tcp 0 0 205.253.12.172.1125 209.74.172.23.9993 ESTABLISHED tcp 0 0 205.253.12.172.1124 209.123.12.32.6667 ESTABLISHED tcp 0 0 *.9993 *.* LISTEN tcp 0 0 205.253.12.168.21680 198.236.98.156.4178 ESTABLISHED tcp 0 0 205.253.12.168.21680 198.236.98.96.4428 ESTABLISHED tcp 0 0 205.253.12.205.1107 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.189.28596 209.133.62.252.2165 ESTABLISHED tcp 0 0 205.253.12.178.1089 207.114.0.144.6667 ESTABLISHED tcp 0 0 205.253.12.189.28596 212.208.227.187.30894 ESTABLISHED tcp 0 0 205.253.12.168.1083 207.114.0.144.6667 ESTABLISHED tcp 0 0 205.253.12.168.21680 205.253.12.178.1079 ESTABLISHED tcp 0 0 205.253.12.178.1079 205.253.12.168.21680 ESTABLISHED tcp 0 0 205.253.12.178.3530 *.* LISTEN tcp 0 0 205.253.12.166.1072 207.114.0.144.6667 ESTABLISHED tcp 0 0 205.253.12.173.1070 207.114.0.144.6667 ESTABLISHED tcp 0 0 205.253.12.168.21680 198.236.98.200.4405 ESTABLISHED tcp 0 0 205.253.12.189.28596 209.133.62.232.9355 ESTABLISHED tcp 0 0 205.253.12.189.1057 204.137.237.3.6667 ESTABLISHED tcp 0 0 205.253.12.182.1051 209.127.0.51.6667 ESTABLISHED tcp 0 0 205.253.12.182.1050 199.120.223.4.28610 ESTABLISHED tcp 0 0 205.253.12.189.9870 *.* LISTEN tcp 0 0 205.253.12.168.21680 205.253.12.173.1037 ESTABLISHED tcp 0 0 205.253.12.162.1045 209.123.12.33.6667 ESTABLISHED tcp 0 0 205.253.12.162.1043 207.127.234.151.11000 ESTABLISHED tcp 0 0 205.253.12.173.1037 205.253.12.168.21680 ESTABLISHED tcp 0 0 205.253.12.185.1034 209.127.0.53.6667 ESTABLISHED tcp 0 0 205.253.12.182.46777 *.* LISTEN tcp 0 0 *.28554 *.* LISTEN tcp 0 0 205.253.12.205.1029 208.2.166.220.9902 ESTABLISHED tcp 0 0 205.253.12.189.25874 *.* LISTEN tcp 0 0 205.253.12.189.28596 *.* LISTEN tcp 0 0 205.253.12.168.21680 *.* LISTEN tcp 0 0 205.253.12.166.3730 *.* LISTEN tcp 0 0 205.253.12.173.3720 *.* LISTEN tcp 0 0 205.253.12.162.12000 *.* LISTEN tcp 0 0 205.253.12.185.1912 *.* LISTEN tcp 0 2 204.137.237.5.23 204.137.237.2.3507 ESTABLISHED tcp 0 0 *.113 *.* LISTEN tcp 0 0 *.23 *.* LISTEN tcp 0 0 *.111 *.* LISTEN udp 0 0 *.111 *.* udp 0 0 *.514 *.* udp 0 0 10.0.0.5.1022 10.0.0.7.2049 udp 0 0 10.0.0.5.1023 10.0.0.7.2049 > netstat -m -M vmcore.XX -N kernel.XX > 1014/2144 mbufs in use: 714 mbufs allocated to data 300 mbufs allocated to packet headers 638/1324/1536 mbuf clusters in use (current/peak/max) 2916 Kbytes allocated to network (48% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines What does this tell you? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 11:48:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from nfs.dragondata.com (power.dragondata.com [204.137.237.7]) by hub.freebsd.org (Postfix) with ESMTP id F1D1015BB4 for ; Sat, 8 May 1999 11:48:08 -0700 (PDT) (envelope-from toasty@nfs.dragondata.com) Received: (from toasty@localhost) by nfs.dragondata.com (8.9.3/8.9.3) id NAA14356; Sat, 8 May 1999 13:48:08 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199905081848.NAA14356@nfs.dragondata.com> Subject: Re: -current NFS crash (out of mbuf clusters) In-Reply-To: <199905081842.NAA14324@nfs.dragondata.com> from Kevin Day at "May 8, 1999 01:42:27 pm" To: toasty@nfs.dragondata.com (Kevin Day) Date: Sat, 8 May 1999 13:48:08 -0500 (CDT) Cc: dillon@apollo.backplane.com (Matthew Dillon), toasty@home.dragondata.com (Kevin Day), current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erm, sorry guys, that huge message wasn't intended to go back to -current, just Matt. My apologies. :) Kevin > > :I'm sure by now Matt is gonna kill me. :) > > : > > :-current from 2 days ago. > > : > > :IdlePTD 3096576 > > :initial pcb at 27ea40 > > :panicstr: Out of mbuf clusters > > :panic messages: > > :--- > > :panic: Out of mbuf clusters > > > > This is probably not NFS related unless there is a leak somewhere. > > > > You may have to mess with the NMBCLUSTERS kernel config to increase > > the number of mbuf clusters. FreeBSD tends to not allocate enough > > by default in more heavily loaded larger-memory configurations. > > > > It should be possible to confirm that the problem is not NFS by taking > > a general look at the state of the system at the time of the crash. You > > can run 'ps' and 'netstat' on the core dump: > > > > cd /var/crash > > ps -axl -M vmcore.XX -N kernel.XX > > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) > 0 1 0 0 10 0 500 0 wait Is ?? 0:00.00 (init) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 12: 1:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id EF1C014C31 for ; Sat, 8 May 1999 12:01:10 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id NAA64562; Sat, 8 May 1999 13:00:34 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905081900.NAA64562@panzer.plutotech.com> Subject: Re: tosha after CAM changes In-Reply-To: <37344F1F.DA8CDBA@seattleu.edu> from Eric Hodel at "May 8, 1999 7:50: 7 am" To: hodeleri@seattleu.edu (Eric Hodel) Date: Sat, 8 May 1999 13:00:34 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Hodel wrote... > "Kenneth D. Merry" wrote: > > > > Eric Hodel wrote... > > > I'm having trouble using tosha after the CAM changes, I updated source > > > early this morning (around 7:00 PDT 5/7/1999) including ports, then > > > make deinstall make distclean in /usr/ports/audio/tosha then make && > > > make install and tosha, and now tosha gives me (as root): > > > > > > #tosha -t1 > > > tosha: cam_lookup_pas: CAMGETPASSTHRU ioctl failed > > > cam_lookup_pass: Inappropriate ioctl for device > > > > > > This is using a Teac CD-532S CD-ROM (SCSI2) attached to an onboard > > > AIC-7890 on an ASUS P2B-LS > > > > > > cdrecord's eject, info, pause, play, resume, set, status, stop, and > > > volume work > > > > > > cdrecord's close never worked, and now debug on and reset do not work > > > (don't know if they worked or not before.) > > > > [ .. ] > > > > Did you do a make world? > > Yes, sorry about that, forgot the most important part. Hmm, so you did a make world? I assume you mean "cdcontrol" above, and not "cdrecord". You can't pause, play, etc., cds with cdrecord. cdcontrol uses the ioctl interface to the cd driver, and so it shouldn't be affected. Well, can you send me the output of the following commands: find /usr/include/cam -print |xargs ident ls -la /usr/lib/libcam* Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 12: 4: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 508A914C31 for ; Sat, 8 May 1999 12:04:02 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA07931; Sat, 8 May 1999 18:55:04 +0200 From: Luigi Rizzo Message-Id: <199905081655.SAA07931@labinfo.iet.unipi.it> Subject: Re: m_get(M_WAIT, ...) _can_ return NULL ? To: imp@harmony.village.org (Warner Losh) Date: Sat, 8 May 1999 18:55:04 +0200 (MET DST) Cc: current@FreeBSD.ORG In-Reply-To: <199905081634.KAA14466@harmony.village.org> from "Warner Losh" at May 8, 99 10:33:59 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1680 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199905081332.PAA07452@labinfo.iet.unipi.it> Luigi Rizzo writes: > : m = m_get(M_WAIT, ...) > : looking at the code, it seems that m_get() _can_ return a NULL pointer > : even if one specifies M_WAIT. > > Looking at the man page for malloc: > M_WAITOK > indicates that it is Ok to wait for resources. It is unconve- > niently defined as 0 so care should be taken never to compare > against this value directly or try to AND it as a flag. The de- > fault operation is to block until the memory allocation succeeds. > malloc() can only return NULL if M_NOWAIT is specified. > > Sounds like a bug to me. i have 2.2.6 online here, and i see that m_get() calls MGET which in turn calls m_retry(), which in turn calls m_reclaim() , which can try to recover memory but it is not guaranteed to succeed. And at the end of the chain there is a check for failure: if (m != NULL) mbstat.m_wait++; else mbstat.m_drops++; return (m); the comment in m_retry says * Must only do the reclaim if not in an interrupt context. but i don't know how this can be identified. cheers luigi > -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ ==== First International Workshop on Networked Group Communication ==== -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 12:12:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id F1B9115356 for ; Sat, 8 May 1999 12:12:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA55730; Sat, 8 May 1999 12:11:14 -0700 (PDT) (envelope-from dillon) Date: Sat, 8 May 1999 12:11:14 -0700 (PDT) From: Matthew Dillon Message-Id: <199905081911.MAA55730@apollo.backplane.com> To: Kevin Day Cc: toasty@home.dragondata.com (Kevin Day), current@FreeBSD.ORG Subject: Re: -current NFS crash (out of mbuf clusters) References: <199905081842.NAA14324@nfs.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :I'm sure by now Matt is gonna kill me. :) :> : :> :-current from 2 days ago. :... : :> netstat -m -M vmcore.XX -N kernel.XX :> : :1014/2144 mbufs in use: : 714 mbufs allocated to data : 300 mbufs allocated to packet headers :638/1324/1536 mbuf clusters in use (current/peak/max) :2916 Kbytes allocated to network (48% in use) :0 requests for memory denied :0 requests for memory delayed :0 calls to protocol drain routines : :What does this tell you? : :Kevin It tells me your userbase is out of control :-) From the looks of it, hundreds of cron jobs are starting up simultaniously and overloading some system resource. I would also recommend: vmstat -m -M vmcore.XX -N kernel.XX It is possible that the machine was attacked from the outside since you are allowing eggdrops to be run. An IP spoofing attack can eat a considerable amount of KVM due to temporary routes and, in fact, run it out, leaving no memory left for mbufs. If so, this will show up in the vmstat. A quick side note on eggdrops: We allowed them at BEST.COM, but after four years our machines and networks were getting attacked virtually every day by IRC bozos. Also, the users who tend to run eggdrops also tend to be stupid - often logging in from compromised machines, so we also had a huge problem with these user's accounts being compromised. We eventually gave up and banned bots entirely. Things have been a whole lot quieter since. Another thing you can do in regards to the cron jobs is go through all your user's crons, many of which are probably running bot check scripts every 10 minutes, and adjust them to run only once an hour, plus scramble the 'minute' so they do not all run simultaniously. I've seen IRC bozos setup cron jobs that run botcheck once a minute. We gave them one warning, and if they did not heed it we kicked them off. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 12:19:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with ESMTP id 318DB156BF for ; Sat, 8 May 1999 12:18:56 -0700 (PDT) (envelope-from gjvc@extremis.demon.co.uk) Received: (from gjvc@localhost) by extremis.demon.co.uk (8.9.3/8.9.1) id TAA00308 for freebsd-current@freebsd.org; Sat, 8 May 1999 19:44:22 GMT (envelope-from gjvc) Date: Sat, 8 May 1999 19:44:22 +0000 From: George Cox To: freebsd-current@freebsd.org Subject: raw disk devices (IDE) Message-ID: <19990508194421.B264@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=f2QGlHpHGjS2mn6Y X-Mailer: Mutt 0.95.5i X-Operating-System: FreeBSD extremis.demon.co.uk 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --f2QGlHpHGjS2mn6Y Content-Type: text/plain; charset=us-ascii Just cvsupped now with the attached slightly alarming boot messages. The kernel booted successfully however, and I am able to send this mail. :-) -- [gjvc] http://www.freebsd.org Dumb terminal, smart user. Smart terminal, [ THE POWER TO SERVE ] --f2QGlHpHGjS2mn6Y Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.err" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat May 8 19:34:41 GMT 1999 root@extremis.demon.co.uk:/usr/src/sys/compile/EXTREMIS-SMP Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400910842 Hz CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x653 Stepping=3 Features=0x183fbff real memory = 134217728 (131072K bytes) avail memory = 127356928 (124372K bytes) Preloaded elf kernel "kernel" at 0xc0327000. DEVFS: ready for devices Pentium Pro MTRR support enabled, default memory type is uncacheable npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 4.0 on pci0 ide_pci0: at device 4.1 on pci0 chip2: at device 4.3 on pci0 ahc0: at device 9.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: interrupting at irq 5 isa0: on motherboard wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa0 wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 1027 cyls, 255 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , LBA, DMA, 32-bit, multi-block-16 wd1: 2441MB (4999680 sectors), 620 cyls, 128 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0 pcm0: interrupting at irq 5 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model IntelliMouse, device ID 3 psm0: interrupting at irq 12 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A sio1: interrupting at irq 3 DEVFS: ready to run IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry IP Filter: initialized. Default = pass all, Logging = enabled Waiting 15 seconds for SCSI devices to settle changing root device to wd0s2a cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: cd present [302958 x 2048 byte records] Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) Device rwd0s1: name slot allocation failed (Errno=17) Device rwd0s3: name slot allocation failed (Errno=17) Device rwd0s4: name slot allocation failed (Errno=17) kernfs_get_rrootdev: no raw root device --f2QGlHpHGjS2mn6Y-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 12:24: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from nfs.dragondata.com (power.dragondata.com [204.137.237.7]) by hub.freebsd.org (Postfix) with ESMTP id BE1AB156A8 for ; Sat, 8 May 1999 12:24:01 -0700 (PDT) (envelope-from toasty@nfs.dragondata.com) Received: (from toasty@localhost) by nfs.dragondata.com (8.9.3/8.9.3) id OAA14425; Sat, 8 May 1999 14:23:57 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199905081923.OAA14425@nfs.dragondata.com> Subject: Re: -current NFS crash (out of mbuf clusters) In-Reply-To: <199905081911.MAA55730@apollo.backplane.com> from Matthew Dillon at "May 8, 1999 12:11:14 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 8 May 1999 14:23:56 -0500 (CDT) Cc: toasty@home.dragondata.com (Kevin Day), current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> netstat -m -M vmcore.XX -N kernel.XX > :> > : > :1014/2144 mbufs in use: > : 714 mbufs allocated to data > : 300 mbufs allocated to packet headers > :638/1324/1536 mbuf clusters in use (current/peak/max) > :2916 Kbytes allocated to network (48% in use) > :0 requests for memory denied > :0 requests for memory delayed > :0 calls to protocol drain routines > : > :What does this tell you? > : > :Kevin > > It tells me your userbase is out of control :-) From the looks > of it, hundreds of cron jobs are starting up simultaniously > and overloading some system resource. > Yeah, I wrote a patch to cron for a while that wouldn't allow that to happen, but it didn't apply cleanly to 4.0's cron, so I'm going to go check why. :) (It staggered the requests, only allow x to run per quantum) > I would also recommend: > > vmstat -m -M vmcore.XX -N kernel.XX > Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 883 141 82052816 1280 0 32 7569 9711 561955 640 253 64 27568 1744 87910913 320 253 128 1526 202 80132397 160 1021415 256 20096 3616 244895 80 151 512 78 2 1911 40 0 1K 277 135 13673 20 314 2K 32 12 173 10 67 4K 6 1 4585 5 0 8K 0 1 2 5 0 16K 3 0 3 5 0 32K 4 0 4 5 0 64K 5 0 5 5 0 128K 1 0 1 5 0 256K 1 0 1 5 0 512K 0 0 2 5 0 Memory usage type by bucket size Size Type(s) 16 devbuf, temp, proc, sysctl, rman, soname, pcb, vnodes, ether_multi, routetbl, isa_devlist, atkbddev, devbuf, temp, proc, sysctl, rman, soname, pcb, vnodes, ether_multi, routetbl, isa_devlist, atkbddev, devbuf, temp, proc, sysctl, rman, soname, pcb, vnodes, ether_multi, routetbl 32 kld, sigio, devbuf, temp, pgrp, subproc, sysctl, SWAP, soname, pcb, cluster_save buffer, vnodes, ifaddr, ether_multi, routetbl, in_multi, NFS req, kld, sigio, devbuf, temp, pgrp, subproc, sysctl, SWAP, soname, pcb, cluster_save buffer, vnodes, ifaddr, ether_multi, routetbl, in_multi, NFS req, kld, sigio, devbuf, temp, pgrp, subproc, sysctl, SWAP, soname, pcb, cluster_save buffer, vnodes, ifaddr, ether_multi, routetbl, in_multi, NFS req 64 file, lockf, namecache, devbuf, temp, session, rman, soname, pcb, cluster_save buffer, vnodes, ifaddr, ether_multi, routetbl, NFS req, file, lockf, namecache, devbuf, temp, session, rman, soname, pcb, cluster_save buffer, vnodes, ifaddr, ether_multi, routetbl, NFS req, file, lockf, namecache, devbuf, temp, session, rman, soname, pcb, cluster_save buffer, vnodes, ifaddr, ether_multi, routetbl, NFS req 128 isadev, kld, timecounter, file desc, zombie, namecache, devbuf, temp, cred, ttys, soname, vnodes, ifaddr, routetbl, ZONE, isadev, kld, timecounter, file desc, zombie, namecache, devbuf, temp, cred, ttys, soname, vnodes, ifaddr, routetbl, ZONE, isadev, kld, timecounter, file desc, zombie, namecache, devbuf, temp, cred, ttys, soname, vnodes, ifaddr, routetbl, ZONE 256 file desc, devbuf, temp, proc, subproc, vnodes, ifaddr, routetbl, NFS srvsock, NFS daemon, FFS node, file desc, devbuf, temp, proc, subproc, vnodes, ifaddr, routetbl, NFS srvsock, NFS daemon, FFS node, file desc, devbuf, temp, proc, subproc, vnodes, ifaddr, routetbl, NFS srvsock, NFS daemon, FFS node 512 file desc, devbuf, temp, ioctlops, BIO buffer, mount, NFSV3 diroff, UFS mount, isa_devlist, file desc, devbuf, temp, ioctlops, BIO buffer, mount, NFSV3 diroff, UFS mount, isa_devlist, file desc, devbuf, temp, ioctlops, BIO buffer, mount, NFSV3 diroff, UFS mount 1K devbuf, temp, proc, BIO buffer, NQNFS Lease, devbuf, temp, proc, BIO buffer, NQNFS Lease, devbuf, temp, proc, BIO buffer, NQNFS Lease 2K devbuf, temp, pcb, BIO buffer, UFS mount, mbuf, isa_devlist, devbuf, temp, pcb, BIO buffer, UFS mount, mbuf, isa_devlist, devbuf, temp, pcb, BIO buffer, UFS mount 4K devbuf, temp, UFS mount, devbuf, temp, UFS mount, devbuf, temp, UFS mount 8K temp, temp, temp 16K devbuf, devbuf, devbuf 32K devbuf, temp, MSDOSFS mount, devbuf, temp, MSDOSFS mount, devbuf, temp, MSDOSFS mount 64K ISOFS mount, NFS hash, UFS ihash, UFS quota, VM pgdata, ISOFS mount, NFS hash, UFS ihash, UFS quota, VM pgdata, ISOFS mount, NFS hash, UFS ihash, UFS quota, VM pgdata 128K namecache, namecache, namecache 256K SWAP, SWAP, SWAP 512K temp, temp, temp Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) isadev 16 2K 2K 40960K 16 0 0 128 ISOFS mount 1 64K 64K 40960K 1 0 0 64K kld 4 1K 1K 40960K 4 0 0 32,128 timecounter 5 1K 1K 40960K 5 0 0 128 file desc 570 74K 74K 40960K 234498 0 0 128,256,512 file 2444 153K 154K 40960K 82740308 0 0 64 sigio 2 1K 1K 40960K 5 0 0 32 zombie 5 1K 14K 40960K 231587 0 0 128 lockf 17 2K 4K 40960K 27419 0 0 64 namecache 24510 1665K 1809K 40960K 279237 0 0 64,128,128K devbuf 332 156K 156K 40960K 384 0 0 16,32,64,128,256,512,1K,2K,4K,16K,32K temp 953 94K 994K 40960K 212165 0 0 16,32,64,128,256,512,1K,2K,4K,8K,32K,512K pgrp 276 9K 10K 40960K 28030 0 0 32 session 259 17K 18K 40960K 26357 0 0 64 proc 118 5K 5K 40960K 5113 0 0 16,256,1K subproc 1336 88K 100K 40960K 492804 0 0 32,256 cred 356 45K 53K 40960K 79650970 0 0 128 sysctl 0 0K 1K 40960K 1614 0 0 16,32 SWAP 2 141K 141K 40960K 2 0 0 32,256K ioctlops 0 0K 1K 40960K 1 0 0 512 rman 33 2K 2K 40960K 50 0 0 16,64 ttys 245 31K 85K 40960K 7850 0 0 128 soname 4 1K 1K 40960K 1778822 0 0 16,32,64,128 pcb 459 12K 12K 40960K 665954 0 0 16,32,64,2K BIO buffer 294 320K 403K 40960K 13047 0 0 512,1K,2K cluster_save buffer 0 0K 1K 40960K 2828 0 0 32,64 mount 4 2K 2K 40960K 4 0 0 512 vnodes 5214 168K 475K 40960K 79653054 0 0 16,32,64,128,256 MSDOSFS mount 1 32K 32K 40960K 1 0 0 32K ifaddr 58 8K 8K 40960K 58 0 0 32,64,128,256 ether_multi 12 1K 1K 40960K 12 0 0 16,32,64 routetbl 521 76K 107K 40960K 3024 0 0 16,32,64,128,256 in_multi 3 1K 1K 40960K 3 0 0 32 NFS srvsock 2 1K 1K 40960K 2 0 0 256 NFS req 347 18K 20K 40960K 4694818 0 0 32,64 NFS daemon 1 1K 1K 40960K 1 0 0 256 NFSV3 diroff 11 6K 6K 40960K 11 0 0 512 NQNFS Lease 1 1K 1K 40960K 1 0 0 1K NFS hash 1 64K 64K 40960K 1 0 0 64K FFS node 19577 4895K 5811K 40960K 173220 0 0 256 UFS ihash 1 64K 64K 40960K 1 0 0 64K UFS quota 1 64K 64K 40960K 1 0 0 64K UFS mount 3 7K 7K 40960K 3 0 0 512,2K,4K VM pgdata 1 64K 64K 40960K 1 0 0 64K ZONE 18 3K 3K 40960K 18 0 0 128 mbuf 1 2K 2K 40960K 1 0 0 2K isa_devlist 29 3K 3K 40960K 29 0 0 16,512,2K atkbddev 1 1K 1K 40960K 1 0 0 16 isadev 16 2K 2K 40960K 16 0 0 128 ISOFS mount 1 64K 64K 40960K 1 0 0 64K kld 4 1K 1K 40960K 4 0 0 32,128 timecounter 5 1K 1K 40960K 5 0 0 128 file desc 570 74K 74K 40960K 234498 0 0 128,256,512 file 2444 153K 154K 40960K 82740308 0 0 64 sigio 2 1K 1K 40960K 5 0 0 32 zombie 5 1K 14K 40960K 231587 0 0 128 lockf 17 2K 4K 40960K 27419 0 0 64 namecache 24510 1665K 1809K 40960K 279237 0 0 64,128,128K devbuf 332 156K 156K 40960K 384 0 0 16,32,64,128,256,512,1K,2K,4K,16K,32K temp 953 94K 994K 40960K 212165 0 0 16,32,64,128,256,512,1K,2K,4K,8K,32K,512K pgrp 276 9K 10K 40960K 28030 0 0 32 session 259 17K 18K 40960K 26357 0 0 64 proc 118 5K 5K 40960K 5113 0 0 16,256,1K subproc 1336 88K 100K 40960K 492804 0 0 32,256 cred 356 45K 53K 40960K 79650970 0 0 128 sysctl 0 0K 1K 40960K 1614 0 0 16,32 SWAP 2 141K 141K 40960K 2 0 0 32,256K ioctlops 0 0K 1K 40960K 1 0 0 512 rman 33 2K 2K 40960K 50 0 0 16,64 ttys 245 31K 85K 40960K 7850 0 0 128 soname 4 1K 1K 40960K 1778822 0 0 16,32,64,128 pcb 459 12K 12K 40960K 665954 0 0 16,32,64,2K BIO buffer 294 320K 403K 40960K 13047 0 0 512,1K,2K cluster_save buffer 0 0K 1K 40960K 2828 0 0 32,64 mount 4 2K 2K 40960K 4 0 0 512 vnodes 5214 168K 475K 40960K 79653054 0 0 16,32,64,128,256 MSDOSFS mount 1 32K 32K 40960K 1 0 0 32K ifaddr 58 8K 8K 40960K 58 0 0 32,64,128,256 ether_multi 12 1K 1K 40960K 12 0 0 16,32,64 routetbl 521 76K 107K 40960K 3024 0 0 16,32,64,128,256 in_multi 3 1K 1K 40960K 3 0 0 32 NFS srvsock 2 1K 1K 40960K 2 0 0 256 NFS req 347 18K 20K 40960K 4694818 0 0 32,64 NFS daemon 1 1K 1K 40960K 1 0 0 256 NFSV3 diroff 11 6K 6K 40960K 11 0 0 512 NQNFS Lease 1 1K 1K 40960K 1 0 0 1K NFS hash 1 64K 64K 40960K 1 0 0 64K FFS node 19577 4895K 5811K 40960K 173220 0 0 256 UFS ihash 1 64K 64K 40960K 1 0 0 64K UFS quota 1 64K 64K 40960K 1 0 0 64K UFS mount 3 7K 7K 40960K 3 0 0 512,2K,4K VM pgdata 1 64K 64K 40960K 1 0 0 64K ZONE 18 3K 3K 40960K 18 0 0 128 mbuf 1 2K 2K 40960K 1 0 0 2K isa_devlist 29 3K 3K 40960K 29 0 0 16,512,2K atkbddev 1 1K 1K 40960K 1 0 0 16 isadev 16 2K 2K 40960K 16 0 0 128 ISOFS mount 1 64K 64K 40960K 1 0 0 64K kld 4 1K 1K 40960K 4 0 0 32,128 timecounter 5 1K 1K 40960K 5 0 0 128 file desc 570 74K 74K 40960K 234498 0 0 128,256,512 file 2444 153K 154K 40960K 82740308 0 0 64 sigio 2 1K 1K 40960K 5 0 0 32 zombie 5 1K 14K 40960K 231587 0 0 128 lockf 17 2K 4K 40960K 27419 0 0 64 namecache 24510 1665K 1809K 40960K 279237 0 0 64,128,128K devbuf 332 156K 156K 40960K 384 0 0 16,32,64,128,256,512,1K,2K,4K,16K,32K temp 953 94K 994K 40960K 212165 0 0 16,32,64,128,256,512,1K,2K,4K,8K,32K,512K pgrp 276 9K 10K 40960K 28030 0 0 32 session 259 17K 18K 40960K 26357 0 0 64 proc 118 5K 5K 40960K 5113 0 0 16,256,1K subproc 1336 88K 100K 40960K 492804 0 0 32,256 cred 356 45K 53K 40960K 79650970 0 0 128 sysctl 0 0K 1K 40960K 1614 0 0 16,32 SWAP 2 141K 141K 40960K 2 0 0 32,256K ioctlops 0 0K 1K 40960K 1 0 0 512 rman 33 2K 2K 40960K 50 0 0 16,64 ttys 245 31K 85K 40960K 7850 0 0 128 soname 4 1K 1K 40960K 1778822 0 0 16,32,64,128 pcb 459 12K 12K 40960K 665954 0 0 16,32,64,2K BIO buffer 294 320K 403K 40960K 13047 0 0 512,1K,2K cluster_save buffer 0 0K 1K 40960K 2828 0 0 32,64 mount 4 2K 2K 40960K 4 0 0 512 vnodes 5214 168K 475K 40960K 79653054 0 0 16,32,64,128,256 MSDOSFS mount 1 32K 32K 40960K 1 0 0 32K ifaddr 58 8K 8K 40960K 58 0 0 32,64,128,256 ether_multi 12 1K 1K 40960K 12 0 0 16,32,64 routetbl 521 76K 107K 40960K 3024 0 0 16,32,64,128,256 in_multi 3 1K 1K 40960K 3 0 0 32 NFS srvsock 2 1K 1K 40960K 2 0 0 256 NFS req 347 18K 20K 40960K 4694818 0 0 32,64 NFS daemon 1 1K 1K 40960K 1 0 0 256 NFSV3 diroff 11 6K 6K 40960K 11 0 0 512 NQNFS Lease 1 1K 1K 40960K 1 0 0 1K NFS hash 1 64K 64K 40960K 1 0 0 64K FFS node 19577 4895K 5811K 40960K 173220 0 0 256 UFS ihash 1 64K 64K 40960K 1 0 0 64K UFS quota 1 64K 64K 40960K 1 0 0 64K UFS mount 3 7K 7K 40960K 3 0 0 512,2K,4K VM pgdata 1 64K 64K 40960K 1 0 0 64K ZONE 18 3K 3K 40960K 18 0 0 128 Memory Totals: In Use Free Requests 25040K 1516K 752769977 > It is possible that the machine was attacked from the outside since you > are allowing eggdrops to be run. An IP spoofing attack can eat a > considerable amount of KVM due to temporary routes and, in fact, run > it out, leaving no memory left for mbufs. If so, this will show up > in the vmstat. Yeah, I've run into this a few times, which usually ended in "panic: kern_kmem_map too small". > > A quick side note on eggdrops: We allowed them at BEST.COM, but > after four years our machines and networks were getting attacked > virtually every day by IRC bozos. Also, the users who tend to run > eggdrops also tend to be stupid - often logging in from compromised > machines, so we also had a huge problem with these user's accounts being > compromised. We eventually gave up and banned bots entirely. Things have > been a whole lot quieter since. > Yeah, we see our problems, but I'm heavy handed with my cluebat, when it's intentional misdoings. In eggdrop user's defense, the instructions for eggdrop tells them to do */10 for the minutes, so they're only doing what they're told. I had a few discussions with Paul Vixie about possible solutions within cron to prevent the forkbombing every 10 mins/hour. We couldn't come up with a great solution, but what I wrote seems to work well. (If you want a diff, i'd be happy to provide it) > Another thing you can do in regards to the cron jobs is go through > all your user's crons, many of which are probably running bot check > scripts every 10 minutes, and adjust them to run only once an hour, > plus scramble the 'minute' so they do not all run simultaniously. > I've seen IRC bozos setup cron jobs that run botcheck once a minute. > We gave them one warning, and if they did not heed it we kicked them off. > Another cron patch was to make the minimum interval 10 minutes for user jobs. :) However, this exact same server, with the exact same cron jobs and eggdrops ran fine on 2.2.8 like this. The only reason I was motivated to fix cron, was that it caused the nfs server to nearly lock up every 10 minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message