From owner-freebsd-current Sun Mar 7 9: 9: 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 50EC714D62 for ; Sun, 7 Mar 1999 09:09:04 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id SAA28320; Sun, 7 Mar 1999 18:08:11 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.3/8.8.5/pb-19970302) id SAA01398; Sun, 7 Mar 1999 18:05:11 +0100 (CET) Message-ID: <19990307180510.A1220@fasterix.frmug.fr.net> Date: Sun, 7 Mar 1999 18:05:10 +0100 From: Pierre Beyssac To: Ollivier Robert , current@FreeBSD.ORG Subject: Re: NTP nanokernel support (experimental) References: <19990306164238.A29897@keltia.freenix.fr> <14112.920744164@critter.freebsd.dk> <19990306200053.B30895@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <19990306200053.B30895@keltia.freenix.fr>; from Ollivier Robert on Sat, Mar 06, 1999 at 08:00:53PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 06, 1999 at 08:00:53PM +0100, Ollivier Robert wrote: > The two outputs I sent were with 4.0.90f. When I run 4.0.92c, ntpd is not > able to get any accurate data from the device whereas 4.0.90f does. > > I get lots of these in /var/log/messages and it doesn't sync at all. > -=-=- > Mar 6 14:02:25 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 3 bits > Mar 6 14:02:29 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits It's typical from bad parity setting on your serial port. Try a stty on that port; I bet it will show that PARENB is set. Unset it and things should go back to normal. > Maybe it is a problem with 4.0.92c... Yes, it's a problem with most of the ntpd 4.0.9x series. There's absolutely no reason why you should enable PARENB for a raw DCF77 driver; yet that's what ntpd's configure does, at least under FreeBSD. I sent a bug report to the ntpd team a while ago but haven't heard from them. -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 7 9:15: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 56FE614D40 for ; Sun, 7 Mar 1999 09:15:23 -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 RAA17932; Sun, 7 Mar 1999 17:12:40 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 7 Mar 1999 17:12:40 +0000 (GMT) From: Doug Rabson To: Sren Schmidt Cc: Steve Price , current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: <199903061542.QAA96195@freebsd.dk> 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 Sat, 6 Mar 1999, Sren Schmidt wrote: > It seems Steve Price wrote: > > [debug output omitted] > > I think I know what is failing now, I just have to find a fix for it.. > > -Søren This seems to be happening to me too on my laptop. The kernel hangs in ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying to probe the slave device on my second ide controller. Specifically, it is the first ata_command() in ata_get_param() which hangs. The laptop in question has a single IDE driver attached to the first controller as a master and a DVD driver attached to the second as a master. The older working probe looked like this: ad0: ATA-3 disk at ata0 as master ad0: 7815MB (16007040 sectors), 15880 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue acd0: CDROM drive at ata1 as master acd0: drive speed 3445KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked The probe which hangs looks the same but stops at this point. -- 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 Mar 7 10:23:25 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 5ED8914BEB for ; Sun, 7 Mar 1999 10:22:47 -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 TAA00727; Sun, 7 Mar 1999 19:22:25 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 07B72883B; Sun, 7 Mar 1999 19:21:58 +0100 (CET) Date: Sun, 7 Mar 1999 19:21:58 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Cc: Harlan Stenn , "David L . Mills" Subject: Re: NTP nanokernel support (experimental) Message-ID: <19990307192158.A57399@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG, Harlan Stenn , "David L . Mills" References: <19990306164238.A29897@keltia.freenix.fr> <14112.920744164@critter.freebsd.dk> <19990306200053.B30895@keltia.freenix.fr> <19990307180510.A1220@fasterix.frmug.fr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990307180510.A1220@fasterix.frmug.fr.net>; from Pierre Beyssac on Sun, Mar 07, 1999 at 06:05:10PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5120 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Pierre Beyssac: > absolutely no reason why you should enable PARENB for a raw DCF77 > driver; yet that's what ntpd's configure does, at least under > FreeBSD. Yes, it seems to be that again. I thought I had fixed it in config.cache but it seems not. It is working now. remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 127.127.1.0 10 - 12 64 1 0.000 0.000 0.000 *127.127.8.0 .DCFa. 0 - 11 64 3 0.000 32.068 0.514 224.0.1.1 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00 A few more peerstats for you Poul-Henning, now with both your diffs and 4.0.92c. 51244 65536.259 127.127.8.0 96c4 0.032788333 0.000000000 0.000000000 0.002593271 51244 65537.261 127.127.8.0 96c4 0.032699250 0.000000000 0.000000000 0.002148683 51244 65538.259 127.127.8.0 96c4 0.032702500 0.000000000 0.000000000 0.001667484 51244 65539.253 127.127.8.0 96c4 0.032702500 0.000000000 0.000000000 0.000871368 51244 65540.259 127.127.8.0 96c4 0.032678083 0.000000000 0.000000000 0.000525512 51244 65541.259 127.127.8.0 96c4 0.032167917 0.000000000 0.000000000 0.000432877 51244 65542.639 127.127.8.0 96c4 0.032068250 0.000000000 0.000000000 0.000513906 The following diff should fix the ignpar/parenb problem. --- configure.in.old Sun Mar 7 19:11:41 1999 +++ configure.in Sun Mar 7 19:11:55 1999 @@ -1055,6 +1055,9 @@ i?86-*-linux*) ans=yes ;; + *-*-freebsd*) + ans=yes + ;; mips-sgi-irix*) ans=yes ;; -- 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 Mar 7 10:25:32 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 91294152ED for ; Sun, 7 Mar 1999 10:25:28 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id TAA98643; Sun, 7 Mar 1999 19:24:57 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903071824.TAA98643@freebsd.dk> Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: from Doug Rabson at "Mar 7, 1999 5:12:40 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 7 Mar 1999 19:24:57 +0100 (CET) Cc: sprice@hiwaay.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 Doug Rabson wrote: >This seems to be happening to me too on my laptop. The kernel hangs in >ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying >to probe the slave device on my second ide controller. Specifically, it >is the first ata_command() in ata_get_param() which hangs. Are you sure it tries to probe the slave ?? Could please try to have it printout scp->devices in ata_probe ?? -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 7 10:55:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from huey.udel.edu (huey.ee.udel.edu [128.175.2.18]) by hub.freebsd.org (Postfix) with SMTP id D8D2F14BF5 for ; Sun, 7 Mar 1999 10:55:09 -0800 (PST) (envelope-from mills@huey.udel.edu) Date: Sun, 7 Mar 1999 13:51:41 EST From: Dave Mills To: Ollivier Robert Cc: current@freebsd.org, Harlan Stenn , "David L . Mills" Subject: Re: NTP nanokernel support (experimental) Message-ID: <199903071351.aa20073@huey.udel.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier, For performance monitoring with the nanokernel and PPS source, see the peerstats and grope for "127.0.0.1" with grep. When the daemon has handed off PPS to the kernel, the radio timecode is used only to mean the transmitter is still on the air. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 7 11:11:55 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 52D7214D88 for ; Sun, 7 Mar 1999 11:11:41 -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 UAA03297; Sun, 7 Mar 1999 20:09:58 +0100 (CET) (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 UAA17046; Sun, 7 Mar 1999 20:09:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dave Mills Cc: Ollivier Robert , current@FreeBSD.ORG, Harlan Stenn , "David L . Mills" Subject: Re: NTP nanokernel support (experimental) In-reply-to: Your message of "Sun, 07 Mar 1999 13:51:41 EST." <199903071351.aa20073@huey.udel.edu> Date: Sun, 07 Mar 1999 20:09:50 +0100 Message-ID: <17044.920833790@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903071351.aa20073@huey.udel.edu>, Dave Mills writes: >Ollivier, > >For performance monitoring with the nanokernel and PPS source, see the >peerstats and grope for "127.0.0.1" with grep. When the daemon has >handed off PPS to the kernel, the radio timecode is used only to >mean the transmitter is still on the air. I don't think Ollivier is doing PPP/hardpps() yet, at least I have not given him the semi-magic code needed for it :-) I wouldn't recommend trying it either, he is bound to have a >1 msec jitter on the DCF77 waves at his place, and that is a lousy diet for hardpps(). Poul-Henning PS: I have updated my rover page, you can see the performance of my machine with the nanokernel-PLL patch, 4.92c and a UT+ Oncore on http://phk.freebsd.dk/rover.html (This isn't using hardpps() either!) -- 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 Mar 7 11:43: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 74E9A14D96 for ; Sun, 7 Mar 1999 11:43:40 -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 TAA18701; Sun, 7 Mar 1999 19:42:17 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 7 Mar 1999 19:42:17 +0000 (GMT) From: Doug Rabson To: Sren Schmidt Cc: sprice@hiwaay.net, current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: <199903071824.TAA98643@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 Sun, 7 Mar 1999, Sren Schmidt wrote: > It seems Doug Rabson wrote: > > >This seems to be happening to me too on my laptop. The kernel hangs in > >ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying > >to probe the slave device on my second ide controller. Specifically, it > >is the first ata_command() in ata_get_param() which hangs. > > Are you sure it tries to probe the slave ?? > Could please try to have it printout scp->devices in ata_probe ?? I'll do that later on today and report back. -- 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 Mar 7 11:57: 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 12ECE14D60 for ; Sun, 7 Mar 1999 11:56:50 -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 TAA18801; Sun, 7 Mar 1999 19:55:26 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 7 Mar 1999 19:55:26 +0000 (GMT) From: Doug Rabson To: Sren Schmidt Cc: sprice@hiwaay.net, current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: <199903071824.TAA98643@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 Sun, 7 Mar 1999, Sren Schmidt wrote: > It seems Doug Rabson wrote: > > >This seems to be happening to me too on my laptop. The kernel hangs in > >ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying > >to probe the slave device on my second ide controller. Specifically, it > >is the first ata_command() in ata_get_param() which hangs. > > Are you sure it tries to probe the slave ?? > Could please try to have it printout scp->devices in ata_probe ?? Here is a log of an attempted boot with ATA_DEBUG defined. It looks like ata_probe() detected a slave where there isn't one. ata-pci0: rev 0x01 on pci0.5.1 ata: type=71118086 class=01018001 cmd=02800005 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=50 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc ata1 at 0x0170 irq 15 on ata-pci0 ... ataintr: entered unit=0 ataintr: entered unit=0 ad0: ATA-3 disk at ata0 as master ad0: 7815MB (16007040 sectors), 15880 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ataintr: entered unit=1 ata_start: entered ataintr: entered unit=1 ataintr: entered unit=1 ata_start: entered acd0: CDROM drive at ata1 as master acd0: drive speed 3445KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked -- 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 Mar 7 12:56:10 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 E3E3F14D2C for ; Sun, 7 Mar 1999 12:56:04 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id VAA06928; Sun, 7 Mar 1999 21:52:22 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.3/8.8.5/pb-19970302) id VAA03562; Sun, 7 Mar 1999 21:50:53 +0100 (CET) Message-ID: <19990307215053.A3517@fasterix.frmug.fr.net> Date: Sun, 7 Mar 1999 21:50:53 +0100 From: Pierre Beyssac To: Poul-Henning Kamp , Dave Mills Cc: Ollivier Robert , current@FreeBSD.ORG, Harlan Stenn , "David L . Mills" Subject: Re: NTP nanokernel support (experimental) References: <199903071351.aa20073@huey.udel.edu> <17044.920833790@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <17044.920833790@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Mar 07, 1999 at 08:09:50PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 07, 1999 at 08:09:50PM +0100, Poul-Henning Kamp wrote: > I don't think Ollivier is doing PPP/hardpps() yet, at least I have not > given him the semi-magic code needed for it :-) > > I wouldn't recommend trying it either, he is bound to have a >1 > msec jitter on the DCF77 waves at his place, and that is a lousy > diet for hardpps(). I agree; jitter with a low-cost DCF77 receiver is even more than that (5 to 10 ms). I tend to believe it's partly due to how the AM signal is demodulated and not that much from the location (Paris is not that far from Frankfurt after all). Maybe a lower jitter could be obtained by averaging 10 or 100 samples, I suppose that's how high-quality receivers work. This might be done in the ntpd driver. -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 7 13: 4: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 ED04014D98 for ; Sun, 7 Mar 1999 13:04:37 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA98922; Sun, 7 Mar 1999 22:04:06 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903072104.WAA98922@freebsd.dk> Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: from Doug Rabson at "Mar 7, 1999 7:55:26 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 7 Mar 1999 22:04:05 +0100 (CET) Cc: sprice@hiwaay.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 Doug Rabson wrote: > > > > Are you sure it tries to probe the slave ?? > > Could please try to have it printout scp->devices in ata_probe ?? > > Here is a log of an attempted boot with ATA_DEBUG defined. It looks like > ata_probe() detected a slave where there isn't one. > > ata1: devices = 0xc Hmm, if it says it found a slave ATAPI device, it found the ATAPI signature in the regs addressed as a slave... Sounds to me like icky hardware, sigh... I'll see what I can do... -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 7 13: 8:21 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 5324F14D5A for ; Sun, 7 Mar 1999 13:08:02 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id PAA15126; Sun, 7 Mar 1999 15:05:04 -0600 (CST) Date: Sun, 7 Mar 1999 15:05:04 -0600 (CST) From: Steve Price To: Doug Rabson Cc: Sren Schmidt , current@freebsd.org Subject: Re: UPDATE2: 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, 7 Mar 1999, Doug Rabson wrote: # > Are you sure it tries to probe the slave ?? # > Could please try to have it printout scp->devices in ata_probe ?? # # Here is a log of an attempted boot with ATA_DEBUG defined. It looks like # ata_probe() detected a slave where there isn't one. # # ata-pci0: rev 0x01 on pci0.5.1 # ata: type=71118086 class=01018001 cmd=02800005 [...] # ata0: devices = 0x1 [...] # ata1: devices = 0xc [snip] For what it's worth I get the same two lines: ata0: devices = 0x1 ata1: devices = 0xc So it found the master (the HD) on the first controller, but it appears to find both a master and a slave on the second controller. The problem is that the DVD-ROM doesn't appear to repsond correctly to either of the attempts to determine which one it wants to be. Just for grins I changed the ata_probe to ignore all but the first controller and it is back to the ufs_dirbad panic. :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 7 13:43:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id 6407714BFC for ; Sun, 7 Mar 1999 13:43:37 -0800 (PST) (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 QAA07085 for ; Sun, 7 Mar 1999 16:43:19 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Sun, 7 Mar 1999 16:43:19 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: current@freebsd.org Subject: zpx in latest snap (4.0-19990307-SNAP) Message-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 the following message from the zp0 driver on boot: zp0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen I assume they should be setting it? :-) 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 Mar 7 13:50: 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 9C09215348 for ; Sun, 7 Mar 1999 13:49:57 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA99025 for current@freebsd.org; Sun, 7 Mar 1999 22:49:39 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903072149.WAA99025@freebsd.dk> Subject: UPDATE3: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Sun, 7 Mar 1999 22:49:39 +0100 (CET) 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 Third update to the new ATA/ATAPI driver: ZIP drives should now be working, I'm not sure about LS120 drives, reports on those most welcome! Fixed problems: Hang on probe on "fantom" devices. The probe now use a timeout to avoid hangs if no interrupt is received. There has also been more general code clenaups, and some reorgs. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. 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 7 15: 9: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 9A95314CB8 for ; Sun, 7 Mar 1999 15:08:48 -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 XAA19618; Sun, 7 Mar 1999 23:06:29 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 7 Mar 1999 23:06:29 +0000 (GMT) From: Doug Rabson To: Steve Price Cc: Sren Schmidt , current@freebsd.org Subject: Re: UPDATE2: 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, 7 Mar 1999, Steve Price wrote: > On Sun, 7 Mar 1999, Doug Rabson wrote: > > # > Are you sure it tries to probe the slave ?? > # > Could please try to have it printout scp->devices in ata_probe ?? > # > # Here is a log of an attempted boot with ATA_DEBUG defined. It looks like > # ata_probe() detected a slave where there isn't one. > # > # ata-pci0: rev 0x01 on pci0.5.1 > # ata: type=71118086 class=01018001 cmd=02800005 > [...] > # ata0: devices = 0x1 > [...] > # ata1: devices = 0xc > [snip] > > For what it's worth I get the same two lines: > > ata0: devices = 0x1 > ata1: devices = 0xc > > So it found the master (the HD) on the first controller, but it > appears to find both a master and a slave on the second controller. > The problem is that the DVD-ROM doesn't appear to repsond correctly > to either of the attempts to determine which one it wants to be. > > Just for grins I changed the ata_probe to ignore all but the first > controller and it is back to the ufs_dirbad panic. :( I never had the ufs_dirbad panic. With the 4 March driver, my system works very well and probes all the ATA devices. Very odd. -- 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 Mar 7 15:58:29 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 CC0D314C3F for ; Sun, 7 Mar 1999 15:58:21 -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 TAA11513 for current@freebsd.org; Sun, 7 Mar 1999 19:04:54 -0500 From: Bill Paul Message-Id: <199903080004.TAA11513@skynet.ctr.columbia.edu> Subject: 2nd request for review for vlan changes To: current@freebsd.org Date: Sun, 7 Mar 1999 19:04:52 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4199 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a second request for review for my proposed if_vlan updates. Since I tweaked a couple of different things, I placed a tarball with the sources at http://www.freebsd.org/~wpaul/VLAN/vlan.tar.gz (or, for those of you with freebsd.org accounts, ~wpaul/public_html/VLAN/vlan.tag.gz). This contains updated sources if_vlan.c, if_vlan_var.h and ifconfig. The changes are as follows: - If the IFF_LINK0 flag is set on a vlan pseudo-interface, it does not peform any header mangling to create the 802.1Q encapsulation, instead allowing the underlying parent driver to do it. (Again, this is mainly for the Tigon driver that I'm working on, which can do its own vlan tag insertion and extraction in firmware.) (I know I used LINK1 before; that's because I forgot that the flag values were zero-based and that LINK0 was really the first one. :) Note: vlan_start() will set rcvif on the outbound mbuf so that the parent driver can find the vlan interface where it originated and find the vlan tag. In order to avoid having the driver possibly follow an uninitialized rcvif pointer, vlan_start() will also set the M_PROTO1 flag in the mbuf to signal to the parent driver that the rcvif is valid. - Implemented vlan_input_tag(), for use with interfaces that know how to do vlan tag extraction and de-capsulation on their own. Works like vlan_input(), except it accepts a third argument, t, which is the extracted vlan tag; given the tag, it tracks down the appropriate vlan interface and sends it the frame. - Added support for multicast. The vlan pseudo interface adds entries to the parent's multicast filter using if_addmulti() and keeps a private list of those groups which it has added. If an update is done, the private list is removed with if_delmulti(), and the parent is programmed again (which again updates the private list). This is a little messy in principle, but the code is fairly simple. - Implemented vlan_unconfig(), the opposite of vlan_config(). When setting up a vlan/parent association with SIOCSETVLAN, the parent's ethernet address and other info are copied to the vlan pseudo interface. This should be removed when the association is broken. - Changed vlan_input()/vlan_input_tag() and vlan_start() to update ifp->if_ipackets and ifp->if_opackets respecively. - If the output queue of the parent interface is full in vlan_start(), increment ifp->if_oerrors, free the mbuf, and continue, instead of just falling through and trying to queue the mbuf even though we know the output queue is full. - Modified ifconfig(8) to allow setting the vlan tag and parent interface of a vlan interface, and to display the interface settings. Three new commands have been added: vlan, vlandev and -vlandev. To set up a vlan interface, you can do this: # ifconfig vlan0 vlan 12345 vlandev foo0 To break the association, you can do this: # ifconfig vlan0 -vlandev foo0 You have to set vlan and vlandev at the same time, since that's how the SIOCSETVLAN ioctl works. Also updated the ifconfig.8 man page. - Fixed a bug in ifconfig. The setifflags() function does a SIOCGIFFLAGS on the ifreq structure that gets passed to it, however this clobbers part of it (namely sa_family) because everything after ifr_name is just one big union. This causes later portions of ifconfig that check the sa_family value to get confused. In my case, the effect was that when I did 'ifconfig vlan0 link0,' ifconfig printed out a line of appletalk status information because sa_family had gotten mangled to 16 (AF_APPLETALK). I still need to write a vlan(4) man page. -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 7 16:41:23 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 402A414CE9 for ; Sun, 7 Mar 1999 16:40:54 -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 QAA04775; Sun, 7 Mar 1999 16:40:23 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903080040.QAA04775@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: 2nd request for review for vlan changes In-reply-to: Your message of "Sun, 07 Mar 1999 19:04:52 EST." <199903080004.TAA11513@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 16:40:23 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is vlan? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 7 18: 4: 6 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 0C39214D9D for ; Sun, 7 Mar 1999 18:04:03 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA05912; Sun, 7 Mar 1999 21:01:16 -0500 (EST) Date: Sun, 7 Mar 1999 21:01:15 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: UPDATE3: ATA/ATAPI driver new version available. In-Reply-To: <199903072149.WAA99025@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 Sun, 7 Mar 1999, S=F8ren Schmidt wrote: >=20 > Third update to the new ATA/ATAPI driver: >=20 > ZIP drives should now be working, I'm not sure about LS120 drives, > reports on those most welcome! It doesn't lock up like before, but on my LS-120 wdc1: unit 0 (atapi): , = removable, iordy it seems to have "corrupt" reads. In addition, much of the time the ATA cod= e now will not boot my system, failing at atapi_transfer: bad command phase. >=20 > Fixed problems: >=20 > Hang on probe on "fantom" devices. > =09The probe now use a timeout to avoid hangs if no interrupt > =09is received. >=20 > There has also been more general code clenaups, and some reorgs. >=20 > As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. >=20 > But please tell me how it works for you! >=20 > Enjoy! >=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=09=09=09=09=09 _ __ ___ ___ ___ =20 green@unixhelp.org=09=09=09 _ __ ___ | _ ) __| \=20 =09 http://www.freebsd.org/=09 _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve!=09 _ __ ___ ____ _____ |___/___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 7 18:19:26 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 AE53614C0E for ; Sun, 7 Mar 1999 18:19:24 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id UAA23505; Sun, 7 Mar 1999 20:16:33 -0600 (CST) Date: Sun, 7 Mar 1999 20:16:32 -0600 (CST) From: Steve Price To: Doug Rabson Cc: Sren Schmidt , current@freebsd.org Subject: Re: UPDATE2: 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, 7 Mar 1999, Doug Rabson wrote: # > Just for grins I changed the ata_probe to ignore all but the first # > controller and it is back to the ufs_dirbad panic. :( # # I never had the ufs_dirbad panic. With the 4 March driver, my system # works very well and probes all the ATA devices. Very odd. Yep, this one has me baffled. The disklabels are there. Well at least 'disklabel ' shows something besides gibberish. This may sound stupid but if they are required and indeed not there why would the old driver not barf at the same spot? If I had to fathom a guess I'd say it had to do with using incorrect drive geometry. Got any ideas on where I might start looking to fix this one? # -- # 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 Mar 7 18:29:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles178.castles.com [208.214.165.178]) by hub.freebsd.org (Postfix) with ESMTP id 5A8D214DBA for ; Sun, 7 Mar 1999 18:29:47 -0800 (PST) (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 SAA04576; Sun, 7 Mar 1999 18:22:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903080222.SAA04576@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Price Cc: Doug Rabson , Sren Schmidt , current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-reply-to: Your message of "Sun, 07 Mar 1999 20:16:32 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 18:22:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the context I've seen, the 'ufs_dirbad' panic is almost certainly due to corrupted disk input. > On Sun, 7 Mar 1999, Doug Rabson wrote: > > # > Just for grins I changed the ata_probe to ignore all but the first > # > controller and it is back to the ufs_dirbad panic. :( > # > # I never had the ufs_dirbad panic. With the 4 March driver, my system > # works very well and probes all the ATA devices. Very odd. > > Yep, this one has me baffled. The disklabels are there. Well at > least 'disklabel ' shows something besides gibberish. > This may sound stupid but if they are required and indeed not there > why would the old driver not barf at the same spot? If I had to > fathom a guess I'd say it had to do with using incorrect drive > geometry. > > Got any ideas on where I might start looking to fix this one? > > # -- > # 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 > -- \\ 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 Sun Mar 7 19: 4: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 8BCBA14CFB for ; Sun, 7 Mar 1999 19:03:45 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id VAA22054; Sun, 7 Mar 1999 21:00:43 -0600 (CST) Date: Sun, 7 Mar 1999 21:00:42 -0600 (CST) From: Steve Price To: Mike Smith Cc: Doug Rabson , Sren Schmidt , current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: <199903080222.SAA04576@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 Sun, 7 Mar 1999, Mike Smith wrote: # # >From the context I've seen, the 'ufs_dirbad' panic is almost certainly # due to corrupted disk input. I definitely can't rule that out as a possibility, but it does make it difficult to explain how the old driver works on this machine. I'm typing this message from the machine in question. Among other things it is building in the neighborhood of twenty ports, recompiling the JDK for the fifteen millionth time :/, CVSup'ing, running a bunch of rxvt's, and generally working its rump off without even the slightest hint of corrupted or flaky disk. All that aside I'm willing to look closer into the possibility of this being the problem. How does one go about obtaining a copy of the raw disklabels? And once I have them how do I verify them for correctness? Thanks. # -- # \\ 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 Sun Mar 7 21:42: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles178.castles.com [208.214.165.178]) by hub.freebsd.org (Postfix) with ESMTP id 31BE914D86 for ; Sun, 7 Mar 1999 21:39:53 -0800 (PST) (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 VAA05029; Sun, 7 Mar 1999 21:32:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903080532.VAA05029@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Price Cc: Doug Rabson , Sren Schmidt , current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-reply-to: Your message of "Sun, 07 Mar 1999 21:00:42 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 21:32:43 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 7 Mar 1999, Mike Smith wrote: > > # > # >From the context I've seen, the 'ufs_dirbad' panic is almost certainly > # due to corrupted disk input. > > I definitely can't rule that out as a possibility, but it does make > it difficult to explain how the old driver works on this machine. The way I read it, the old driver works fine, but the new driver is reading the wrong disk sectors or failing to transfer them correctly. You might want to try instrumenting the panic and see if you can work out what is actually being read. -- \\ 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 Sun Mar 7 23:28: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 1742214D80 for ; Sun, 7 Mar 1999 23:28:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA00174; Mon, 8 Mar 1999 08:27:27 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903080727.IAA00174@freebsd.dk> Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: from Steve Price at "Mar 7, 1999 9: 0:42 pm" To: sprice@hiwaay.net (Steve Price) Date: Mon, 8 Mar 1999 08:27:27 +0100 (CET) Cc: mike@smith.net.au, dfr@nlsystems.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 Steve Price wrote: > On Sun, 7 Mar 1999, Mike Smith wrote: > > # > # >From the context I've seen, the 'ufs_dirbad' panic is almost certainly > # due to corrupted disk input. > > I definitely can't rule that out as a possibility, but it does make > it difficult to explain how the old driver works on this machine. > I'm typing this message from the machine in question. Among other > things it is building in the neighborhood of twenty ports, recompiling > the JDK for the fifteen millionth time :/, CVSup'ing, running a bunch > of rxvt's, and generally working its rump off without even the > slightest hint of corrupted or flaky disk. > > All that aside I'm willing to look closer into the possibility of > this being the problem. How does one go about obtaining a copy of > the raw disklabels? And once I have them how do I verify them for > correctness? Hmm, the only thing I can come up with is that either your disk doesn't support multible sectors, or fails to do 32bit transfers. There is an if 0 around the 32/16 bit transfers try reversing it, and then try to comment out the lines that does the multisector setup. -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 7 23:35:20 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 AD36C14E56 for ; Sun, 7 Mar 1999 23:33:51 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA00203; Mon, 8 Mar 1999 08:33:26 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903080733.IAA00203@freebsd.dk> Subject: Re: UPDATE3: ATA/ATAPI driver new version available. In-Reply-To: from Brian Feldman at "Mar 7, 1999 9: 1:15 pm" To: green@unixhelp.org (Brian Feldman) Date: Mon, 8 Mar 1999 08:33:26 +0100 (CET) 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: >> Third update to the new ATA/ATAPI driver: >> >> ZIP drives should now be working, I'm not sure about LS120 drives, >> reports on those most welcome! > >It doesn't lock up like before, but on my LS-120 >wdc1: unit 0 (atapi): , >removable, iordy >it seems to have "corrupt" reads. In addition, much of the time the ATA >code now will not boot my system, failing at atapi_transfer: bad command phase. Hmm, you could try to increase the timeout at line 230 in atapi-all.c, se if that helps. -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 8 2: 4:48 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 B38F814D0C for ; Mon, 8 Mar 1999 02:04:29 -0800 (PST) (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 LAA07394; Mon, 8 Mar 1999 11:04:11 +0100 (MET) Received: (from beyssac@localhost) by bofh.enst.fr (8.9.3/8.8.8) id LAA00495; Mon, 8 Mar 1999 11:04:10 +0100 (CET) Message-ID: <19990308110410.A379@enst.fr> Date: Mon, 8 Mar 1999 11:04:10 +0100 From: Pierre Beyssac To: =?iso-8859-1?Q?S=F8ren_Schmidt?= , current@FreeBSD.ORG Subject: Re: UPDATE3: ATA/ATAPI driver new version available. References: <199903072149.WAA99025@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: =?iso-8859-1?Q?=3C199903072149=2EWAA99025=40freebsd=2Edk=3E=3B_from_S=F8?= =?iso-8859-1?Q?ren_Schmidt_on_Sun=2C_Mar_07=2C_1999_at_10:49:39PM_+0100?= Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 07, 1999 at 10:49:39PM +0100, Søren Schmidt wrote: > Third update to the new ATA/ATAPI driver: I tried your driver (update 2), and I solves all my CDROM problems (hanged after mount). I keep it. Great work, thanks! ata-pci0: rev 0x01 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 acd0: CDROM drive at ata1 as master acd0: drive speed 2412KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 80mm data disc loaded, unlocked -- 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 Mon Mar 8 3:30: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id C4B5914EE2 for ; Mon, 8 Mar 1999 03:29:59 -0800 (PST) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id MAA05545 for freebsd-current@freebsd.org; Mon, 8 Mar 1999 12:29:41 +0100 (CET) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m10JxJy-000WydC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Mon, 8 Mar 1999 11:31:38 +0100 (CET) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: buildworld failure as of 1999-03-08 Date: 8 Mar 1999 11:31:35 +0100 Message-ID: <7c08u7$dk0$1@mips.rhein-neckar.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'ed the latest source yesterday evening/this morning and started a "make buildworld". ===> gnu/usr.bin/perl/perl ... Writing Makefile for Fcntl mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/Fcntl mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto/Fcntl cd ext/Fcntl; make -B all PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl cp Fcntl.pm /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/Fcntl.pm /usr/obj/usr/src/gnu/usr.bin/perl/perl/perl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -noprototypes -typemap /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/typemap Fcntl.xs >Fcntl.tc && mv Fcntl.tc Fcntl.c cc -c -DVERSION=\"1.03\" -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/usr/src/gnu/usr.bin/perl/perl Fcntl.c In file included from /usr/obj/usr/src/gnu/usr.bin/perl/perl/perl.h:1268, from Fcntl.xs:2: /usr/obj/usr/src/gnu/usr.bin/perl/perl/scope.h:165: unterminated string or character constant /usr/obj/usr/src/gnu/usr.bin/perl/perl/scope.h:49: possible real start of unterminated constant /usr/obj/usr/src/gnu/usr.bin/perl/perl/scope.h:45: unterminated `#if' conditional *** Error code 1 I guess the immediate culprit is this: /usr/obj/usr/src/gnu/usr.bin/perl/perl/scope.h: | #ifdef DEBUGGING | #define ENTER \ | STMT_START { \ | push_scope(); \ | DEBUG_l(WITH_THR(deb("ENTER"scope %ld at %s:%d\n", \ ^ | PL_scopestack_ix, __FILE__, __LINE__))); \ | } STMT_END | #define LEAVE \ | STMT_START { \ | DEBUG_l(WITH_THR(deb("LEAVE scope %ld at %s:%d\n", \ | PL_scopestack_ix, __FILE__, __LINE__))); \ | pop_scope(); \ | } STMT_END | #else | #define ENTER push_scope() | #define LEAVE pop_scope() | #endif -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de See another pointless homepage 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 8 6:18:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from bart.esiee.fr (bart.esiee.fr [147.215.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 9BDEE14EEE for ; Mon, 8 Mar 1999 06:18:32 -0800 (PST) (envelope-from bonnetf@bart.esiee.fr) Received: (from bonnetf@localhost) by bart.esiee.fr (8.9.1a/8.9.1) id PAA26744 for freebsd-current@freebsd.org; Mon, 8 Mar 1999 15:18:10 +0100 (MET) From: Frank Bonnet Message-Id: <199903081418.PAA26744@bart.esiee.fr> Subject: rpc.lockd and HPUX mail To: freebsd-current@freebsd.org Date: Mon, 08 Mar 1999 15:18:10 MET X-Mailer: Elm [revision: 112.7] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'm in trouble with the rpc.lockd daemon we have ~120 HPUX workstations running HPUX 10.20 that use NFS client mounted /var/mail directory to our FreeBSD 3.1 mailhub. The problem is some /var/mail/login.lock files stays in the directory after the user has sent his email and are not removed by the rpc.lockd daemon. actually I run a cron process that stop the MTA then clean the mailspool of the *.lock files then restart the MTA , I am not satisfied by this procedure of course. Is there a solution , patch , trick , infos ? TIA -- Frank Bonnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 8 7:18:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from huey.udel.edu (huey.ee.udel.edu [128.175.2.18]) by hub.freebsd.org (Postfix) with SMTP id 53FCE14BE3 for ; Mon, 8 Mar 1999 07:18:38 -0800 (PST) (envelope-from mills@huey.udel.edu) Date: Mon, 8 Mar 1999 10:12:23 EST From: Dave Mills To: Pierre Beyssac Cc: Poul-Henning Kamp , Dave Mills , Ollivier Robert , current@freebsd.org, Harlan Stenn , "David L . Mills" Subject: Re: NTP nanokernel support (experimental) Message-ID: <199903081012.aa20781@huey.udel.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre, The NTPv4 driver interface already implements a trimmed-mean filter, which cleans up a good deal of jitter as it is. The IRIG and CHU drivers do a lot more signal processing, yielding generally low jitter in the tens of microseconds. Deglitching and filtering noisy time sampls is somewhat an art form, but the methods are not hard to implement. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 8 7:32:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 77DDB14BE3 for ; Mon, 8 Mar 1999 07:32:07 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA11738; Mon, 8 Mar 1999 16:31:43 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA58826; Mon, 8 Mar 1999 16:31:37 +0100 (MET) Date: Mon, 8 Mar 1999 16:31:37 +0100 From: Eivind Eklund To: HighWind Software Information , current@FreeBSD.ORG Subject: Re: Killed Myself Message-ID: <19990308163137.Q41771@bitbox.follo.net> References: <199811180249.VAA03471@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199811180249.VAA03471@highwind.com>; from HighWind Software Information on Tue, Nov 17, 1998 at 09:49:31PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 17, 1998 at 09:49:31PM -0500, HighWind Software Information wrote: > > After installing the recent libc_r and libc, I'm getting: > > ld.so failed: Undefined symbol "SYS_kldsym" in make:/usr/lib/aout/libc.so.3.1 > > I also get it sometimes when I link against libc_r. > > "SYS_kldsym" is always the thing I don't seem to have a definition for. > > This just started happening. UGH! If you do not know how FreeBSD works to a detailed enough level to NOT HAVE TO ASK THIS, then you should MAKE WORLD. You should NOT try to do incremental recompiles. That is reserved for those people that know exactly what they are doing. Sorry, but this is like taking a nail-gun and shooting from the hip towards the floor instead of actually bedning your knees, and then coming shouting 'My foot hurts! My foot hurts! What should I do?' Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 8 8:50:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.on.home.com (ha1.rdc1.on.wave.home.com [24.2.9.66]) by hub.freebsd.org (Postfix) with ESMTP id A8D8714F22 for ; Mon, 8 Mar 1999 08:50:25 -0800 (PST) (envelope-from street@iname.com) Received: from mired.eh.local ([24.64.150.8]) by mail.rdc1.on.home.com (InterMail v4.00.03 201-229-104) with ESMTP id <19990308165007.WXFJ18874.mail.rdc1.on.home.com@mired.eh.local> for ; Mon, 8 Mar 1999 08:50:07 -0800 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id LAA21087; Mon, 8 Mar 1999 11:50:07 -0500 (EST) (envelope-from kws) To: current@FreeBSD.org Subject: ATA/ATAPI speed test From: Kevin Street Date: 08 Mar 1999 11:50:06 -0500 Message-ID: <87r9r09b9d.fsf@mired.eh.local> Lines: 37 X-Mailer: Gnus v5.6.45/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried the ata drivers on the weekend and they work fine, but seem a bit slow. I ran my usual buildworld script with the old and new drivers with these elapsed time results: With the wd drivers 2:05:32 With the ata drivers 2:54:21 So that's nearly 40% longer for the ata case - is this all likely due to dma? /usr/obj is on drive 0, /usr/src is on drive 1 and they are mounted with soft-updates and noatime. The tests were not entirely pure as there was some other minor activity running on the machine as well. The ata dmesg output is: ata-pci0: rev 0x01 on pci0.4.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: ATA-3 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ad1: ATA-4 disk at ata1 as master ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue Waiting 2 seconds for SCSI devices to settle acd0: CDROM drive at ata0 as slave acd0: drive speed 5515KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked -- Kevin Street street@iname.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 8 8:53:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id 18F3114DDB for ; Mon, 8 Mar 1999 08:53:18 -0800 (PST) (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 LAA12081; Mon, 8 Mar 1999 11:52:37 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Mon, 8 Mar 1999 11:52:37 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Eivind Eklund Cc: HighWind Software Information , current@FreeBSD.ORG Subject: Re: Killed Myself In-Reply-To: <19990308163137.Q41771@bitbox.follo.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 So actually, I have a question about this. How is the syscall glue generated, and when. Pretty much all the userland libraries call syscalls using symbols of the same name rather than the syscall() wrapper, presumably for performance and feasiability reasons (especially with pipe()). When is this glue generated? Two possibilities come to mind: a) When a buildworld is done, the compiler includes the /usr/include/sys/syscall* files, and as such has access to the necessary arguments to compile the glue straight into the libraries/applications when they require the symbol to be available, or at link time. b) When gcc compiles an application, it dynamically reads in the syscall data in /usr/include/sys And an unlikely third: c) It munges the kernel Which of these is the case, or what other event is happening? Previously when adding syscalls, I've always rebuilt the kernel and the world. As a result, I've never run into the problem I ran into today where my test machine whines that it cannot link against my shared libraries making use of new syscalls in its kernel, even though the include files are available and correct. I assume this is because my compiler needs to be updated, but as I'm not actually familiar with the glue making process, I figured I would ask. Thanks in advance, On Mon, 8 Mar 1999, Eivind Eklund wrote: > On Tue, Nov 17, 1998 at 09:49:31PM -0500, HighWind Software Information wrote: > > > > After installing the recent libc_r and libc, I'm getting: > > > > ld.so failed: Undefined symbol "SYS_kldsym" in make:/usr/lib/aout/libc.so.3.1 > > > > I also get it sometimes when I link against libc_r. > > > > "SYS_kldsym" is always the thing I don't seem to have a definition for. > > > > This just started happening. UGH! > > If you do not know how FreeBSD works to a detailed enough level to NOT > HAVE TO ASK THIS, then you should MAKE WORLD. You should NOT try to > do incremental recompiles. That is reserved for those people that > know exactly what they are doing. > > Sorry, but this is like taking a nail-gun and shooting from the hip > towards the floor instead of actually bedning your knees, and then > coming shouting 'My foot hurts! My foot hurts! What should I do?' > > Eivind. > > > > 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: 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 Mar 8 8:58:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from marte.bbsiga.com.br (marte.bbsiga.com.br [200.246.184.252]) by hub.freebsd.org (Postfix) with ESMTP id 9CF8114F3F for ; Mon, 8 Mar 1999 08:57:42 -0800 (PST) (envelope-from mezzanet@iname.com) Received: from marte.bbsiga.com.br (mezzanet@marte.bbsiga.com.br [200.246.184.252]) by marte.bbsiga.com.br (8.8.7/8.8.7) with SMTP id NAA00640 for ; Mon, 8 Mar 1999 13:57:16 -0300 Date: Mon, 8 Mar 1999 13:57:16 -0300 (EST) From: Marcello Mezzanotti X-Sender: mezzanet@marte.bbsiga.com.br To: freebsd-current@FreeBSD.ORG Subject: new fetch? where i get? In-Reply-To: <7c08u7$dk0$1@mips.rhein-neckar.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 im using freebsd rel 3.1 and i cvsup ports-all everyday, now when i try any make fetch, it complains about -A NEW OPTION, whats the probs?? i instaled 31upgrade from misc, but nothing happens!!! :/ i edited bsd.port.mk and put off -A option from fetch where i can find new fetch?? tahnx anyway marcello +-----------------------------------------------+---------------------+ | Marcello Mezzanotti | Amiga 1200/18Mb | | ICQ UIN #1845241 | AmigaOS 3.1 | | C, Pascal, PHP, Arexx Programmer | Linux 2.0.33pl1 | | Star Trek, UNIX, Amiga Computers | NetBSD 1.3.3 | | IRC Nick: MezzaNET | | +-----------------------------------------------+ K6 233 32Mb | | Amiga: The Computer For Creative Minds | FreeBSD 3.1 | | Linux: The Choice of The Next Generation | Linux 2.0.36 | +-----------------------------------------------+---------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 8 9:22: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 54B2F14E78 for ; Mon, 8 Mar 1999 09:22:47 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id JAA00875; Mon, 8 Mar 1999 09:22:20 -0800 (PST) (envelope-from obrien) Date: Mon, 8 Mar 1999 09:22:19 -0800 From: "David O'Brien" To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: Killed Myself Message-ID: <19990308092219.A819@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990308163137.Q41771@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Robert Watson on Mon, Mar 08, 1999 at 11:52:37AM -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 > When is this glue generated? 1. syscalls.h and syscall.mk is built from syscalls.master makesyscalls.sh by when you compile a kernel 2. these files are used when you build libc, so make knows all the syscalls so it can build the stubs. Ex. getpgrp.S: #include "SYS.h" RSYSCALL(getpgrp) -- -- 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 8 9:54:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from holly.dyndns.org (ip161.houston3.tx.pub-ip.psi.net [38.12.169.161]) by hub.freebsd.org (Postfix) with ESMTP id 3045814F04 for ; Mon, 8 Mar 1999 09:53:54 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id LAA96937; Mon, 8 Mar 1999 11:48:18 -0600 (CST) (envelope-from chris) Date: Mon, 8 Mar 1999 11:48:17 -0600 From: Chris Costello To: Marcello Mezzanotti Cc: freebsd-current@FreeBSD.ORG Subject: Re: new fetch? where i get? Message-ID: <19990308114817.E93344@holly.dyndns.org> Reply-To: chris@calldei.com References: <7c08u7$dk0$1@mips.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: ; from Marcello Mezzanotti on Mon, Mar 08, 1999 at 01:57:16PM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 8, 1999, Marcello Mezzanotti put this into my mailbox: > im using freebsd rel 3.1 and i cvsup ports-all everyday, now when i try > any make fetch, it complains about -A NEW OPTION, whats the probs?? > i instaled 31upgrade from misc, but nothing happens!!! :/ > > i edited bsd.port.mk and put off -A option from fetch > > where i can find new fetch?? CVSup to your latest -CURRENT or -STABLE tree. From the fetch man page: -A Do not automatically follow ``temporary'' (302) redirects. Some broken Web sites will return a redirect instead of a not-found error when the requested object does not exist. -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" Every program in development at MIT expands until it can read 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 8 15: 0:18 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 6A30E1505C for ; Mon, 8 Mar 1999 15:00:09 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 5087 invoked from network); 8 Mar 1999 22:59:12 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 8 Mar 1999 22:59:12 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.3/8.9.1) id RAA00540; Mon, 8 Mar 1999 17:59:05 -0500 (EST) Message-Id: <199903082259.RAA00540@y.dyson.net> Subject: Re: Killed Myself In-Reply-To: <19990308163137.Q41771@bitbox.follo.net> from Eivind Eklund at "Mar 8, 99 04:31:37 pm" To: eivind@yes.no (Eivind Eklund) Date: Mon, 8 Mar 1999 17:59:05 -0500 (EST) Cc: info@highwind.com, 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 Eivind Eklund said: > On Tue, Nov 17, 1998 at 09:49:31PM -0500, HighWind Software Information wrote: > > > > After installing the recent libc_r and libc, I'm getting: > > > > ld.so failed: Undefined symbol "SYS_kldsym" in make:/usr/lib/aout/libc.so.3.1 > > > > I also get it sometimes when I link against libc_r. > > > > "SYS_kldsym" is always the thing I don't seem to have a definition for. > > > > This just started happening. UGH! > > If you do not know how FreeBSD works to a detailed enough level to NOT > HAVE TO ASK THIS, then you should MAKE WORLD. You should NOT try to > do incremental recompiles. That is reserved for those people that > know exactly what they are doing. > And those who know exactly what they are doing still get zapped. -- 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 8 17:15:24 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 11C8715008 for ; Mon, 8 Mar 1999 17:15:21 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id TAA32174; Mon, 8 Mar 1999 19:12:13 -0600 (CST) Date: Mon, 8 Mar 1999 19:12:13 -0600 (CST) From: Steve Price To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: mike@smith.net.au, dfr@nlsystems.com, current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: <199903080727.IAA00174@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 Mon, 8 Mar 1999, S=F8ren Schmidt wrote: # > All that aside I'm willing to look closer into the possibility of # > this being the problem. How does one go about obtaining a copy of # > the raw disklabels? And once I have them how do I verify them for # > correctness? #=20 # Hmm, the only thing I can come up with is that either your disk # doesn't support multible sectors, or fails to do 32bit transfers. # There is an if 0 around the 32/16 bit transfers try reversing # it, and then try to comment out the lines that does the multisector # setup. I just tried this and it still panics at the same spot. I tried it with all four combinations of the two '#if 0' blocks in ata-disk.c. I'm going to play around with Mike's suggestion of instrumenting ad_interrupt with a bunch of debug prints and see if I can see what is happening. I'll do this right after I determine for sure that both the old and new driver are at least trying to read the same blocks from the disk for the disklabels. Sounds stupid I know, but I can cut the problem space in half if I can prove that they are least trying to go to the same spot on the disk. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 8 17:25: 6 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 47BCE15317 for ; Mon, 8 Mar 1999 17:25:03 -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 RAA01839; Mon, 8 Mar 1999 17:15:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903090115.RAA01839@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Price Cc: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= , mike@smith.net.au, dfr@nlsystems.com, current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-reply-to: Your message of "Mon, 08 Mar 1999 19:12:13 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 08 Mar 1999 17:15:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm going to play around with Mike's suggestion of instrumenting > ad_interrupt with a bunch of debug prints and see if I can see > what is happening. I'll do this right after I determine for > sure that both the old and new driver are at least trying to > read the same blocks from the disk for the disklabels. Sounds > stupid I know, but I can cut the problem space in half if I > can prove that they are least trying to go to the same spot on > the disk. I'd be more worried that they're going to different places _after_ = they've read the disklabel. If they couldn't read the disklabel, you = wouldn't be mounting the disk in the first place. Is your disk dedicated in some way? -- = \\ 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 8 17:39:49 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 2CBF014D2D for ; Mon, 8 Mar 1999 17:39:38 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id TAA16492; Mon, 8 Mar 1999 19:36:35 -0600 (CST) Date: Mon, 8 Mar 1999 19:36:35 -0600 (CST) From: Steve Price To: Mike Smith Cc: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= , dfr@nlsystems.com, current@freebsd.org Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: <199903090115.RAA01839@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 Mon, 8 Mar 1999, Mike Smith wrote: # I'd be more worried that they're going to different places _after_ # they've read the disklabel. If they couldn't read the disklabel, you # wouldn't be mounting the disk in the first place. # # Is your disk dedicated in some way? Nope not knowingly. I started out with 3.1-RELEASE on this box and I'm pretty sure I answered no to the dangerously-dedicated question in sysinstall if that's what you mean. # -- # \\ 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 8 18:23:23 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 9204414DFB for ; Mon, 8 Mar 1999 18:23:19 -0800 (PST) (envelope-from august70@mediaone.net) Received: from mediaone.net (augustsevenzero.ne.mediaone.net [24.128.249.13]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA27364 for ; Mon, 8 Mar 1999 21:23:00 -0500 (EST) Message-ID: <36E485E5.80B03044@mediaone.net> Date: Mon, 08 Mar 1999 21:22:29 -0500 From: Paul Fournier X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: subscribe freebsd-current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Mon Mar 8 22:49:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 5991015006 for ; Mon, 8 Mar 1999 22:49:23 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id HAA23100; Tue, 9 Mar 1999 07:49:04 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id HAA62427; Tue, 9 Mar 1999 07:49:03 +0100 (MET) Date: Tue, 9 Mar 1999 07:49:02 +0100 From: Eivind Eklund To: "John S. Dyson" Cc: info@highwind.com, current@FreeBSD.ORG Subject: Re: Killed Myself Message-ID: <19990309074902.T41771@bitbox.follo.net> References: <19990308163137.Q41771@bitbox.follo.net> <199903082259.RAA00540@y.dyson.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199903082259.RAA00540@y.dyson.net>; from John S. Dyson on Mon, Mar 08, 1999 at 05:59:05PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 08, 1999 at 05:59:05PM -0500, John S. Dyson wrote: > Eivind Eklund said: > > If you do not know how FreeBSD works to a detailed enough level to NOT > > HAVE TO ASK THIS, then you should MAKE WORLD. You should NOT try to > > do incremental recompiles. That is reserved for those people that > > know exactly what they are doing. > > And those who know exactly what they are doing still get zapped. Of course - but we know not to ask :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 8 23:34:18 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 313B114C21 for ; Mon, 8 Mar 1999 23:34:16 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 22151 invoked from network); 9 Mar 1999 07:33:56 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 9 Mar 1999 07:33:56 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.3/8.9.1) id CAA32299; Tue, 9 Mar 1999 02:33:55 -0500 (EST) Message-Id: <199903090733.CAA32299@y.dyson.net> Subject: Re: Killed Myself In-Reply-To: <19990309074902.T41771@bitbox.follo.net> from Eivind Eklund at "Mar 9, 99 07:49:02 am" To: eivind@FreeBSD.ORG (Eivind Eklund) Date: Tue, 9 Mar 1999 02:33:55 -0500 (EST) Cc: dyson@iquest.net, info@highwind.com, 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 Eivind Eklund said: > On Mon, Mar 08, 1999 at 05:59:05PM -0500, John S. Dyson wrote: > > Eivind Eklund said: > > > If you do not know how FreeBSD works to a detailed enough level to NOT > > > HAVE TO ASK THIS, then you should MAKE WORLD. You should NOT try to > > > do incremental recompiles. That is reserved for those people that > > > know exactly what they are doing. > > > > And those who know exactly what they are doing still get zapped. > > Of course - but we know not to ask :-) > I agree... This is a deal where people need to know the limits of their experience. Of course, it is good when people try to push themselves. When people delve deeper and deeper into the system, it seems that there are more and more ways of burning oneself. Anything like new system calls, changing kernel data structures and (even worse) on disk formats is more or less tricky for anyone. With experience, ones is surprised less and less, but still mistakes do happen :-(. Is this clearly noted somewhere? I know that it is common knowledge, but as new people use the system (and get adventureous) some of 'em will get burnt with mistakes. Back in the late '70's, I started investigating C as a programming language. It took a week to get a "hello world" to compile and link. I was an island, without any support from anyone. Such experiences do teach one to be somewhat tolerant. My mistake: I came from a DEC programming world, and I wrote the program like this: Main() { Printf("Hello world\n"); } My brain wasn't trained to be case sensitive (of course, it is now), but that was a most irritating experience. -- 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 Tue Mar 9 0:40: 1 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 18B7B1505F for ; Tue, 9 Mar 1999 00:39:56 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. ([212.42.68.185]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id KAA04768; Tue, 9 Mar 1999 10:40:02 +0200 (EET) (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 KAA03035; Tue, 9 Mar 1999 10:39:28 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <36E4DE33.C7D04A42@altavista.net> Date: Tue, 09 Mar 1999 10:39:15 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: =?x-user-defined?Q?S=F8ren?= Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE3: ATA/ATAPI driver new version available. References: <199903072149.WAA99025@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 Driver works fine, but on my notebook, when HDD awake from sleep I see "at0: unvanted interrupt" message. Maybe we need flag similar to "SLEEP_HACK" on wd driver? Sincerely, Maxim "Søren Schmidt" wrote: > Third update to the new ATA/ATAPI driver: > > ZIP drives should now be working, I'm not sure about LS120 drives, > reports on those most welcome! > > Fixed problems: > >     Hang on probe on "fantom" devices. >         The probe now use a timeout to avoid hangs if no interrupt >         is received. > > There has also been more general code clenaups, and some reorgs. > > As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 9 0:59:46 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 CD8A114BEF for ; Tue, 9 Mar 1999 00:59:43 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA03119; Tue, 9 Mar 1999 09:56:08 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903090856.JAA03119@freebsd.dk> Subject: Re: UPDATE3: ATA/ATAPI driver new version available. In-Reply-To: <36E4DE33.C7D04A42@altavista.net> from Maxim Sobolev at "Mar 9, 1999 10:39:15 am" To: sobomax@altavista.net Date: Tue, 9 Mar 1999 09:56:08 +0100 (CET) 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: >Driver works fine, but on my notebook, when HDD awake from sleep I see >"at0: unvanted interrupt" message. Maybe we need flag similar to >"SLEEP_HACK" on wd driver? I'm not sure how I'm going to handle this yet, but it is on my TODO list... -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 9 3:30:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id B23E414C2F for ; Tue, 9 Mar 1999 03:30:04 -0800 (PST) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id MAA12663 for freebsd-current@freebsd.org; Tue, 9 Mar 1999 12:29:36 +0100 (CET) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m10KKV4-000WyYC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Tue, 9 Mar 1999 12:16:38 +0100 (CET) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: buildworld failure as of 1999-03-08 Date: 9 Mar 1999 12:16:35 +0100 Message-ID: <7c2vuj$pni$1@mips.rhein-neckar.de> References: <7c08u7$dk0$1@mips.rhein-neckar.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, must have been a gremlin. cvsup'ed again yesterday (didn't look like anything related to the problem had changed), did another buildworld, and this time it worked. Oh, well. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de >H Deutsche Transhumanismus-Mailingliste echo 'subscribe trans-de' | mail majordomo@lists.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 9 4:58:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id BEF1614E70 for ; Tue, 9 Mar 1999 04:58:21 -0800 (PST) (envelope-from arno@heho.snv.jussieu.fr) Received: from hall.snv.jussieu.fr (hall.snv.jussieu.fr [134.157.37.2]) by shiva.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id NAA15602 for ; Tue, 9 Mar 1999 13:58:02 +0100 (CET) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.37.22]) by hall.snv.jussieu.fr (8.8.8/jtpda-5.2) with SMTP id NAA23072 for ; Tue, 9 Mar 1999 13:58:29 +0100 (CET) Received: by heho.snv.jussieu.fr (4.1/jf930126) at Tue, 9 Mar 99 13:58:01 +0100 To: freebsd-current@freebsd.org Subject: egcs-snap-world From: arno@heho.snv.jussieu.fr (Arno J. Klaassen) Date: 09 Mar 1999 13:57:59 +0100 Message-Id: Lines: 324 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just in case someone is interested (i'm not a particular advocat of the need of the world and kernel being able to be compiled with something else than the system-compiler; just to show that the current sources apparently do not depend a lot on FreeBSD-specific features of gcc/binutils): applying some minor changes, I compiled the world with an arbitrary mix of a recent egcs-cvs-snapshot and binutils-2.9.1.0.19 (haifa-scheduling enabled) I regularly use for userland compilations, using the following script: #! /bin/bash export CC='/usr/vol/opt/freebsd3/egcs-snap/bin/gcc -B/usr/vol/opt/freebsd3/egcs-snap/bin/ -B/usr/vol/opt/freebsd3/egcs-snap/lib/gcc-lib/i686-pc-freebsdelf/egcs-2.92.32/ -v -MD ' export CXX='/usr/vol/opt/freebsd3/egcs-snap/bin/c++ -B/usr/vol/opt/freebsd3/egcs-snap/bin/ -B/usr/vol/opt/freebsd3/egcs-snap/lib/gcc-lib/i686-pc-freebsdelf/egcs-2.92.32/ -v -I/usr/vol/opt/freebsd3/egcs-snap/include/g++-2 -MD ' make -DNOGAMES -DNOAOUT $* I compiled buildworld on an Intel Madrona: FreeBSD siamese-twins 3.1-STABLE FreeBSD 3.1-STABLE #1: Fri Feb 19 21:16:03 MET 1999 toor@siamese-twins:/usr/src_RELENG_3/sys/compile/SIAM i386 Further, I did an installworld on my current-machine, an Intergraph TD4 (dual-P90): CPU: Pentium/P54C (90.00-MHz 586-class CPU) eisa0: ncr0: rev 0x01 int a irq 11 on pci0.7.0 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), Tagged Queueing Enabled da0: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) and then re-compiled the kernel with CC='/usr/bin/cc -pipe -fformat-extensions ' This is not a really good test since this system is very slow and rather unreliable under cc-compiled world as well; anyway, for basic ``workstation-use'' (xntpd, nfs, xterm, compiling ports etc.) so far I did not notice any difference with the cc-compiled world (when I've time, I'll install a Dual-PPro as alternative current-machine). For completeness, this is kldstat-output: (I recompiled nfs into the kernel; no notable difference with using nfs.ko) Id Refs Address Size Name 1 4 0xf0100000 189ef0 kernel 2 1 0xf08f4000 6000 procfs.ko 3 1 0xf090d000 e000 linux.ko 4 1 0xf0922000 2000 green_saver.ko Voila the cvs-diff on the source tree: (especially for the vinum-mods, I was not concerned at all for semantic correctness; if someone is interested, I put a cvs-context-diff as well as my log-file and dependency-output on ftp://heho.snv.jussieu.fr/pub/FreeBSD_egcs/ ) Index: bin/sh/Makefile =================================================================== RCS file: /home/ncvs/src/bin/sh/Makefile,v retrieving revision 1.28 diff -r1.28 Makefile 41a42,43 > ${BRANDELF} ${.TARGET} > Index: gnu/lib/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/lib/Makefile,v retrieving revision 1.19 diff -r1.19 Makefile 3c3 < SUBDIR= libdialog libg++ libgmp libmp libobjc libregex libreadline libstdc++ --- > SUBDIR= libdialog libgmp libmp libregex libreadline Index: gnu/usr.bin/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/Makefile,v retrieving revision 1.44 diff -r1.44 Makefile 3c3 < SUBDIR= awk bc binutils bison cc cpio cvs dc dialog diff diff3 genclass gperf \ --- > SUBDIR= awk bc binutils bison cpio cvs dc dialog diff diff3 genclass gperf \ Index: gnu/usr.bin/cc/cc_tools/Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/cc/cc_tools/Makefile,v retrieving revision 1.14 diff -r1.14 Makefile 30a31 > ${BRANDELF} ${.TARGET} 62a64 > ${BRANDELF} ${.TARGET} 72a75 > ${BRANDELF} ${.TARGET} Index: lib/libmytinfo/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libmytinfo/Makefile,v retrieving revision 1.16 diff -r1.16 Makefile 35a36,37 > ${BRANDELF} ${.TARGET} > 39a42,43 > ${BRANDELF} ${.TARGET} > 46a51,52 > ${BRANDELF} ${.TARGET} > 52a59,60 > ${BRANDELF} ${.TARGET} > 61a70,71 > ${BRANDELF} ${.TARGET} > 64a75,76 > ${BRANDELF} ${.TARGET} > Index: share/mk/bsd.kern.mk =================================================================== RCS file: /home/ncvs/src/share/mk/bsd.kern.mk,v retrieving revision 1.15 diff -r1.15 bsd.kern.mk 12c12 < -fformat-extensions -ansi --- > -ansi Index: share/mk/bsd.prog.mk =================================================================== RCS file: /home/ncvs/src/share/mk/bsd.prog.mk,v retrieving revision 1.81 diff -r1.81 bsd.prog.mk 39a40 > ${BRANDELF} ${.TARGET} 54a56 > ${BRANDELF} ${.TARGET} Index: share/mk/sys.mk =================================================================== RCS file: /home/ncvs/src/share/mk/sys.mk,v retrieving revision 1.43 diff -r1.43 sys.mk 46a47,49 > # _Arno_ two line sadded > BRANDELF ?= /usr/bin/brandelf -f -t FreeBSD > CC_FOR_AS ?= /usr/bin/cc Index: share/syscons/scrnmaps/Makefile =================================================================== RCS file: /home/ncvs/src/share/syscons/scrnmaps/Makefile,v retrieving revision 1.12 diff -r1.12 Makefile 26a27 > ${BRANDELF} ${.TARGET} Index: sys/boot/ficl/ficl.c =================================================================== RCS file: /home/ncvs/src/sys/boot/ficl/ficl.c,v retrieving revision 1.11 diff -r1.11 ficl.c 233c233 < c = *(pVM->ip); --- > c.p = (*(pVM->ip)); 250c250 < c = *pVM->ip; --- > c.p = *pVM->ip; 258c258 < c = *pVM->ip; --- > c.p = *pVM->ip; 266c266 < c = *pVM->ip; --- > c.p = *pVM->ip; 271c271 < c = *pVM->ip; --- > c.p = *pVM->ip; 276c276 < c = *pVM->ip; --- > c.p = *pVM->ip; 281c281 < c = *pVM->ip; --- > c.p = *pVM->ip; Index: sys/boot/i386/btx/btxldr/Makefile =================================================================== RCS file: /home/ncvs/src/sys/boot/i386/btx/btxldr/Makefile,v retrieving revision 1.6 diff -r1.6 Makefile 18c18 < ${CC} ${AFLAGS} -c -o ${.TARGET} ${.CURDIR}/btxldr.s --- > ${CC_FOR_AS} ${AFLAGS} -c -o ${.TARGET} ${.CURDIR}/btxldr.s Index: sys/boot/i386/loader/Makefile =================================================================== RCS file: /home/ncvs/src/sys/boot/i386/loader/Makefile,v retrieving revision 1.29 diff -r1.29 Makefile 100c100 < ${CC} ${LDFLAGS} -o ${.TARGET} ${BTXCRT} ${OBJS} vers.o \ --- > ${CC_FOR_AS} ${LDFLAGS} -o ${.TARGET} ${BTXCRT} ${OBJS} vers.o \ Index: sys/dev/vinum/vinum.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinum.c,v retrieving revision 1.9 diff -r1.9 vinum.c 180a181,183 > union daemoninfo null_di; > > null_di.rq = NULL; 194c197 < queue_daemon_request(daemonrq_return, NULL); /* stop the daemon */ --- > queue_daemon_request(daemonrq_return, null_di); /* stop the daemon */ Index: sys/dev/vinum/vinumdaemon.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumdaemon.c,v retrieving revision 1.5 diff -r1.5 vinumdaemon.c 208a209,211 > union daemoninfo null_di; > > null_di.rq = NULL; 211c214 < queue_daemon_request(daemonrq_ping, NULL); /* queue a ping */ --- > queue_daemon_request(daemonrq_ping, null_di); /* queue a ping */ Index: sys/dev/vinum/vinuminterrupt.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinuminterrupt.c,v retrieving revision 1.9 diff -r1.9 vinuminterrupt.c 76,77c76,80 < if (debug & DEBUG_LASTREQS) < logrq(loginfo_iodone, rqe, ubp); --- > if (debug & DEBUG_LASTREQS) { > union rqinfou urqe; > urqe.rqe = rqe; > logrq(loginfo_iodone, urqe, ubp); > } 145,146c148,152 < } else /* try to recover */ < queue_daemon_request(daemonrq_ioerror, rq); /* let the daemon complete */ --- > } else { /* try to recover */ > union daemoninfo urq; > urq.rq = rq; > queue_daemon_request(daemonrq_ioerror, urq); /* let the daemon complete */ > } Index: sys/dev/vinum/vinumio.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumio.c,v retrieving revision 1.13 diff -r1.13 vinumio.c 699c699,702 < queue_daemon_request(daemonrq_saveconfig, NULL); --- > union daemoninfo null_di; > > null_di.rq = NULL; > queue_daemon_request(daemonrq_saveconfig, null_di); Index: sys/dev/vinum/vinumrequest.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumrequest.c,v retrieving revision 1.12 diff -r1.12 vinumrequest.c 175a176,177 > union rqinfou ubp; > ubp.bp = bp; 177c179 < logrq(loginfo_user_bp, bp, bp); --- > logrq(loginfo_user_bp, ubp, bp); 367,368c369,373 < if (debug & DEBUG_LASTREQS) < logrq(loginfo_user_bpl, rq->bp, rq->bp); --- > if (debug & DEBUG_LASTREQS) { > union rqinfou ubp; > ubp.bp = rq->bp; > logrq(loginfo_user_bpl, ubp, rq->bp); > } 396,397c401,405 < if (debug & DEBUG_LASTREQS) < logrq(loginfo_rqe, rqe, rq->bp); --- > if (debug & DEBUG_LASTREQS) { > union rqinfou urqe; > urqe.bp = rqe; > logrq(loginfo_rqe, urqe, rq->bp); > } Index: sys/dev/vinum/vinumutil.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinumutil.c,v retrieving revision 1.7 diff -r1.7 vinumutil.c 165c165 < return (enum volstate) i; --- > return (enum volumestate) i; Index: sys/modules/linux/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/linux/Makefile,v retrieving revision 1.25 diff -r1.25 Makefile 30a31 > ${BRANDELF} ${.TARGET} Index: sys/modules/svr4/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/svr4/Makefile,v retrieving revision 1.2 diff -r1.2 Makefile 37a38 > ${BRANDELF} ${.TARGET} Amicalement, -- Arno J. Klaassen INSERM U483, University Pierre et Marie Curie, Boite 23 9, quai Saint Bernard 75 252 Paris Cedex 5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 9 6:45:58 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 6147C152D0 for ; Tue, 9 Mar 1999 06:45:55 -0800 (PST) (envelope-from mike@sentex.net) Received: from leaverite (leaverite.sentex.ca [209.112.4.36]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id JAA15267; Tue, 9 Mar 1999 09:44:41 -0500 (EST) Message-Id: <3.0.5.32.19990309094839.042b93e0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 09 Mar 1999 09:48:39 -0500 To: Matthew Dillon , Chris Costello , current@FreeBSD.ORG From: Mike Tancsa Subject: Re: Simple DOS against 3.x locks box solid In-Reply-To: <199903050035.QAA33521@apollo.backplane.com> References: <4.1.19990304073656.084804e0@granite.sentex.ca> <19990304155401.A5710@holly.dyndns.org> <199903050022.QAA32802@apollo.backplane.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 04:35 PM 3/4/99 -0800, Matthew Dillon wrote: > Well, this was easy to duplicate. I'll try to track it down. It seems > to occur under -4.x as well as -3.x. Definitely an inode deadlock of some > kind. > > -Matt > >: Try changing the 'find' to 'find -x'. If this still locks up the machine >: we will have to then determine whether it occurs under 4.x as well, or >: if it only occurs under 3.x. >: -Matt >: >::> As posted by yk@dgtu.donetsk.ua >::> > >::> >This script freeze my 3.1-RELEASE box. >::> >I can't make any connection with my box, also from console. >::> > >::> >-------- cut here --- >::> >#! /bin/sh >::> > >::> >for j in 1 2 3 4 5 6 7 8 9 10 >::> >do >::> >echo -n $j >::> >nohup sh -c 'while :; do find / -type file |xargs fgrep fticom; done' >::> >/dev/null 2>&1 & >::> >echo >::> >done >::> >--------- cut here ---- >::> > >::> >-- >::> >Yury V. Yaroshevsky | Donetsk State Technical University >::> >YY18-RIPE | (380 622) 356455 yk@dgtu.donetsk.ua > > ------------------------------------------------------------------------ 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 Tue Mar 9 8:30: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 507E514E63 for ; Tue, 9 Mar 1999 08:30:33 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA19125; Tue, 9 Mar 1999 11:30:09 -0500 (EST) Date: Tue, 9 Mar 1999 11:30:08 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Thomas Dean Cc: current@FreeBSD.ORG Subject: Re: fd broken [!!!] In-Reply-To: <199903062039.MAA05063@ix.netcom.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, 6 Mar 1999, Thomas Dean wrote: So Does anyone have an idea why the hell fd(4) broke?! > I have the same problem on 4.0-current SMP of Mon Feb 15 03:34:29 PST > 1999. > > tomdean > > > 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 Tue Mar 9 13:45:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.kellogg.nwu.edu (orthanc.kellogg.nwu.edu [129.105.197.36]) by hub.freebsd.org (Postfix) with ESMTP id 7179B15019 for ; Tue, 9 Mar 1999 13:45:10 -0800 (PST) (envelope-from pcox@orthanc.kellogg.nwu.edu) Received: (from pcox@localhost) by orthanc.kellogg.nwu.edu (8.9.3/8.9.1) id PAA00606 for current@freebsd.org; Tue, 9 Mar 1999 15:44:53 -0600 (CST) (envelope-from pcox) Date: Tue, 9 Mar 1999 15:44:52 -0600 From: Peter Cox To: current@freebsd.org Subject: Secondary IDE woes Message-ID: <19990309154452.A519@orthanc.kellogg.nwu.edu> 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 Hi all, I recompiled -current last week, and have been having intermittent problems with my secondary IDE controller not being detected since. Sometimes when I boot, it sees the controller with no problems. Most often though, it doesn't detect it at all. I recompiled again with today's sources and the problem persists. Here's the dmesg output, any help would be appreciated. Cheers, Peter Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #19: Tue Mar 9 15:21:37 CST 1999 pcox@orthanc.kellogg.nwu.edu:/usr/src/sys/compile/ORTHANC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 297998769 Hz CPU: Pentium II (298.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 134217728 (131072K bytes) avail memory = 127864832 (124868K bytes) Preloaded elf kernel "kernel" at 0xf02ad000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 on pci0.7.3 ahc0: rev 0x01 int a irq 10 on pci0.13.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x00 int a irq 9 on pci0.14.0 chip4: rev 0x03 on pci0.15.0 xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.17.0 xl0: Ethernet address: 00:c0:4f:8c:c1:c1 xl0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for devices on PCI bus 1: vga1: rev 0x5c on pci1.0.0 Probing for devices on PCI bus 2: 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 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A psm0 irq 12 on isa psm0: model MouseMan+, device ID 0 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: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 npx0 on motherboard npx0: INT 16 interface vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 11) da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8363MB (17127880 512 byte sectors: 255H 63S/T 1066C) changing root device to wd0s1a OSS/FreeBSD loading, address = f0bc1d58 -- ----------------------------------------------------------------------------- Peter Cox - Systems Administrator, Phone: (847) 467 1842 Kellogg Graduate School of Management, Fax: (847) 467 3500 Northwestern University. Email: p-cox@nwu.edu ----------------------------------------------------------------------------- It is impossible to travel faster than light, and certainly not desirable, as one's hat keeps blowing off. -- Woody Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 9 19:48: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 1EDF414D17 for ; Tue, 9 Mar 1999 19:48:27 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id MAA23787; Wed, 10 Mar 1999 12:48:21 +0900 (JST) Message-ID: <36E5EB27.2E44F17D@newsguy.com> Date: Wed, 10 Mar 1999 12:46:47 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@freebsd.org Subject: HEADS UP: new loader.rc stuff 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 A new loader.rc mechanism has been introduced. Nothing has changed with loader, mind you, and you can continue to use your current loader.rc (if any) unchanged, but Jordan thinks it might be better to install a loader.rc using the new mechanism by default, to keep support easy, so things might change in the future... Meanwhile, the new loader.rc stuff, for those who want it. It is modeled after rc.conf files. We now have a /boot/defaults/loader.conf, with all defaults (meaning it hardly does anything, serving more as a template), which will also load /boot/loader.conf and /boot/loader.conf.local, in that order, if present. The idea is to leave /boot/loader.conf for sysinstall, /boot/loader.conf.local for the user, and /boot/defaults/loader.conf to installworld. To use this, put the following lines in your /boot/loader.rc: include /boot/loader.4th start Then you can create a /boot/loader.conf.local with whatever other stuff you'd like, such as using a splash screen. Feedback, comments, musings and flames are welcome. (I'd particularly like a better name than "start" :) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 9 20:29: 1 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 8DD5314FF0 for ; Tue, 9 Mar 1999 20:28:59 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id UAA38031 for freebsd-current@freebsd.org; Tue, 9 Mar 1999 20:28:41 -0800 (PST) From: Archie Cobbs Message-Id: <199903100428.UAA38031@bubba.whistle.com> Subject: wchar.h? To: freebsd-current@freebsd.org Date: Tue, 9 Mar 1999 20:28:41 -0800 (PST) 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 The jikes Java compiler relies on an include file "whcar.h" being on the system. However, even if it's not, it includes routines to do what it needs... only about 40 lines or so for these functions: wcslen() wcscpy() wcsncpy() wcscat() wcscmp() wcsncmp() How come FreeBSD doesn't have these? Is there a complicated problem preventing us from adding them? 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 Mar 9 21:52:47 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 5AB3114F81 for ; Tue, 9 Mar 1999 21:52:44 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id IAA01909; Wed, 10 Mar 1999 08:52:25 +0300 (MSK) (envelope-from ache) Date: Wed, 10 Mar 1999 08:52:25 +0300 From: "Andrey A. Chernov" To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: wchar.h? Message-ID: <19990310085224.B98291@nagual.pp.ru> References: <199903100428.UAA38031@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903100428.UAA38031@bubba.whistle.com>; from archie@whistle.com on Tue, Mar 09, 1999 at 08:28:41PM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 09, 1999 at 08:28:41PM -0800, Archie Cobbs wrote: > The jikes Java compiler relies on an include file "whcar.h" being > wcsncmp() > > How come FreeBSD doesn't have these? Is there a complicated problem > preventing us from adding them? Wide chars manipulations simple not implemented, if you plan to write some implementation please take a look to some standards first like Single UNIX Specs: http://www.opengroup.org/onlinepubs/7908799/xsh/wchar.h.html -- 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 Tue Mar 9 22:16: 7 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 713C214E3B for ; Tue, 9 Mar 1999 22:16:03 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id BAA00333; Wed, 10 Mar 1999 01:18:32 -0500 (EST) Date: Wed, 10 Mar 1999 01:18:30 -0500 (EST) From: Alfred Perlstein To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff In-Reply-To: <36E5EB27.2E44F17D@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 Wed, 10 Mar 1999, Daniel C. Sobral wrote: > A new loader.rc mechanism has been introduced. Nothing has changed > with loader, mind you, and you can continue to use your current > loader.rc (if any) unchanged, but Jordan thinks it might be better > to install a loader.rc using the new mechanism by default, to keep > support easy, so things might change in the future... > > Meanwhile, the new loader.rc stuff, for those who want it. It is > modeled after rc.conf files. We now have a > /boot/defaults/loader.conf, with all defaults (meaning it hardly > does anything, serving more as a template), which will also load > /boot/loader.conf and /boot/loader.conf.local, in that order, if > present. > > The idea is to leave /boot/loader.conf for sysinstall, > /boot/loader.conf.local for the user, and /boot/defaults/loader.conf > to installworld. > > To use this, put the following lines in your /boot/loader.rc: > > include /boot/loader.4th > start > > Then you can create a /boot/loader.conf.local with whatever other > stuff you'd like, such as using a splash screen. > > Feedback, comments, musings and flames are welcome. (I'd > particularly like a better name than "start" :) As long as the man page makes it clear what's going on. All this including of files is going to get damn confusing for newbies. It's also unlike anything i've ever seen before... -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 9 22:48: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 5A94614F56 for ; Tue, 9 Mar 1999 22:48:18 -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 WAA30462; Tue, 9 Mar 1999 22:49:24 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199903100649.WAA30462@troutmask.apl.washington.edu> Subject: Re: wchar.h? In-Reply-To: <199903100428.UAA38031@bubba.whistle.com> from Archie Cobbs at "Mar 9, 1999 8:28:41 pm" To: archie@whistle.com (Archie Cobbs) Date: Tue, 9 Mar 1999 22:49:24 -0800 (PST) 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 Archie Cobbs wrote: > The jikes Java compiler relies on an include file "whcar.h" being > on the system. However, even if it's not, it includes routines > to do what it needs... only about 40 lines or so for these functions: > > wcslen() > wcscpy() > wcsncpy() > wcscat() > wcscmp() > wcsncmp() > > How come FreeBSD doesn't have these? Is there a complicated problem > preventing us from adding them? > Look at /usr/include/machine/ansi.h. It has a brief statement about wchar_t. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 9 23: 2: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 8E6161501B for ; Tue, 9 Mar 1999 23:02:38 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id QAA15766; Wed, 10 Mar 1999 16:02:27 +0900 (JST) Message-ID: <36E616B1.FC899131@newsguy.com> Date: Wed, 10 Mar 1999 15:52:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff 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 Alfred Perlstein wrote: > > All this including of files is going to get damn confusing > for newbies. Hopefully, they won't have to touch them directly, and just use sysinstall. > It's also unlike anything i've ever seen before... Actually, it reminds me of the Linux boot loader a little tiny bit... :-) And you could certainly make comparisons with OpenBoot. But, aside from that, you are on the mark here. The new loader gave us a lot of power, and we are not exactly sure how to put that to good use. Up to now, it meant putting actual code inside loader.rc, which results in all sorts of trouble. Using a configuration files is a natural solution for that, and the similarities with rc.conf will, hopefully, make using it easier. Also hopefully, we'll get feedback to correct any mistakes before we get this back to -stable. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 1:48:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 72367150A6 for ; Wed, 10 Mar 1999 01:48:17 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Wed, 10 Mar 1999 09:46:14 -0000 Message-ID: From: paul@originative.co.uk To: dcs@newsguy.com, current@freebsd.org Subject: RE: HEADS UP: new loader.rc stuff Date: Wed, 10 Mar 1999 09:46:14 -0000 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: Daniel C. Sobral [mailto:dcs@newsguy.com] > Sent: 10 March 1999 03:47 > To: current@freebsd.org > Subject: HEADS UP: new loader.rc stuff > > Meanwhile, the new loader.rc stuff, for those who want it. It is > modeled after rc.conf files. We now have a > /boot/defaults/loader.conf, with all defaults (meaning it hardly > does anything, serving more as a template), which will also load > /boot/loader.conf and /boot/loader.conf.local, in that order, if > present. > > The idea is to leave /boot/loader.conf for sysinstall, > /boot/loader.conf.local for the user, and /boot/defaults/loader.conf > to installworld. > Hmm, feeling of deja-vu here :-) Why do we need three levels of config files? Can't we make do with two? Configuration of the system is becoming more and more of a horrible mess of spaghetti. I think /boot/defaults/loader.conf and /boot/loader.conf should be enough. It's just confusing otherwise, if I change something with sysinstall I may, or may not, cause an effect depending on whether I've twiddled the same knob in loader.conf.local. I see sysinstall as just an alternative user interface to vi or emacs for editing options. Is there something awkward about the way sysinstall works that requires it to have its own config file? Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 2:28:46 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 C5E6115074 for ; Wed, 10 Mar 1999 02:28:38 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA13960; Wed, 10 Mar 1999 19:28:26 +0900 (JST) Message-ID: <36E6451C.67B16009@newsguy.com> Date: Wed, 10 Mar 1999 19:10:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: paul@originative.co.uk Cc: current@freebsd.org Subject: Re: HEADS UP: new loader.rc stuff 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 paul@originative.co.uk wrote: > > Hmm, feeling of deja-vu here :-) It was on purpose. :-) > Why do we need three levels of config files? Can't we make do with two? Yes, two are enough. > Configuration of the system is becoming more and more of a horrible mess of > spaghetti. That's an unavoidable trade off of flexibility. > I think /boot/defaults/loader.conf and /boot/loader.conf should be enough. > It's just confusing otherwise, if I change something with sysinstall I may, > or may not, cause an effect depending on whether I've twiddled the same knob > in loader.conf.local. Then don't use loader.conf.local. > I see sysinstall as just an alternative user interface to vi or emacs for > editing options. Is there something awkward about the way sysinstall works > that requires it to have its own config file? No. Well, sysinstall doesn't even touch these files yet, but I don't expect it to do anything strange. You can safely use just two files. If you don't want a third (or fourth, fifth, whatever) file, just do not create/use them. There are people who *really* prefer not to have their stuff touched by anything. That's why the support exists. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 7:54:27 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 C837414C98 for ; Wed, 10 Mar 1999 07:54:17 -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 QAA67278; Wed, 10 Mar 1999 16:53:36 +0100 (CET) (envelope-from des) To: Matthew Dillon Cc: "Daniel C. Sobral" , Jos Backus , Dmitrij Tejblum , perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> <19990223105939.D97001@hal.mpn.cp.philips.com> <36D329D1.73146EEF@newsguy.com> <199902250803.AAA01163@apollo.backplane.com> From: Dag-Erling Smorgrav Date: 10 Mar 1999 16:53:34 +0100 In-Reply-To: Matthew Dillon's message of "Thu, 25 Feb 1999 00:03:15 -0800 (PST)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > I would disagree with that. Invariants are for people who want > their data to be as safe as possible and don't mind eating a little > cpu doing extra sanity checks in the kernel. It is something I would > almost certainly enable in a production kernel. Uh, no. Invariants are for developers who want to make sure their code is correct. There is no reason why an end user would want to build a kernel with invariants enabled. Invariants will *not* increase data safety. If they have any effect at all (i.e. if they actually catch a bug), the result is a panic (whereas with a kernel without invariants, the bug might actually go unnoticed). You must be thinking of the FAILSAFE option. 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 Mar 10 8: 2:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from postal.metaip.checkpoint.com (metaip.checkpoint.com [204.29.28.25]) by hub.freebsd.org (Postfix) with ESMTP id 7849514C58 for ; Wed, 10 Mar 1999 08:02:57 -0800 (PST) (envelope-from marka@metaip.checkpoint.com) Received: from cartman.metainfo.com (cartman.metainfo.com [204.29.28.145]) by postal.metaip.checkpoint.com (8.8.7/8.8.7) with ESMTP id HAA02913; Wed, 10 Mar 1999 07:27:24 -0800 Received: from moby.dev.metainfo.com (sneakers.metainfo.com [204.29.28.213]) by cartman.metainfo.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id GT68WF2R; Wed, 10 Mar 1999 07:47:31 -0800 Date: Wed, 10 Mar 1999 08:02:00 -0800 (PST) From: Mark Atkinson X-Sender: marka@moby.dev.metainfo.com Reply-To: marka@metaip.checkpoint.com To: Archie Cobbs Cc: freebsd-current@freebsd.org Subject: Re: wchar.h? In-Reply-To: <199903100428.UAA38031@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 Tue, 9 Mar 1999, Archie Cobbs wrote: > The jikes Java compiler relies on an include file "whcar.h" being > on the system. However, even if it's not, it includes routines > to do what it needs... only about 40 lines or so for these functions: I was bitten by this one recently too, and there are quite a few messages in the mailing-list archives on the subject. If I remember right (without looking right now) the reason it hasn't been included was some sort of issue of 16bit vs 32bit. The short answer is you need write your own functions and header file that you need, or use the Xwchar library that came in the original X11R5/contrib distributions (with slight modifications to the header file to use FreeBSD's wchar_t type and specific includes). It looks like jikes does the 'right thing' just because there's not that much consistancy across platforms. Just FYI HP, linux, and solaris all include a wchar.h, but different systems are missing different wcs* type functions. --- Mark Atkinson Checkpoint Technologies' Metaip Group marka@metaip.checkpoint.com !(wired)?(coffee++):(wired) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 8:27:55 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 7C752151F1 for ; Wed, 10 Mar 1999 08:27:18 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 28894 invoked by uid 1001); 10 Mar 1999 16:26:59 +0000 (GMT) To: des@flood.ping.uio.no Cc: dillon@apollo.backplane.com, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free From: sthaug@nethelp.no In-Reply-To: Your message of "10 Mar 1999 16:53:34 +0100" 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, 10 Mar 1999 17:26:59 +0100 Message-ID: <28892.921083219@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Uh, no. Invariants are for developers who want to make sure their code > is correct. There is no reason why an end user would want to build a > kernel with invariants enabled. Invariants will *not* increase data > safety. If they have any effect at all (i.e. if they actually catch a > bug), the result is a panic (whereas with a kernel without invariants, > the bug might actually go unnoticed). So for the end user it's better to have the bug go unnoticed than to get a kernel panic and notice the bug? Please tell me I'm misunder- standing something here. 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 Mar 10 8:46: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (Postfix) with ESMTP id B07C7152A0 for ; Wed, 10 Mar 1999 08:46:01 -0800 (PST) (envelope-from druber@mail.kersur.net) Received: from localhost (druber@localhost) by mail.kersur.net (8.9.1/8.9.1) with SMTP id LAA27322; Wed, 10 Mar 1999 11:48:57 -0500 (EST) Date: Wed, 10 Mar 1999 11:48:57 -0500 (EST) From: Dan Swartzendruber To: sthaug@nethelp.no Cc: des@flood.ping.uio.no, dillon@apollo.backplane.com, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: <28892.921083219@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, 10 Mar 1999 sthaug@nethelp.no wrote: > > Uh, no. Invariants are for developers who want to make sure their code > > is correct. There is no reason why an end user would want to build a > > kernel with invariants enabled. Invariants will *not* increase data > > safety. If they have any effect at all (i.e. if they actually catch a > > bug), the result is a panic (whereas with a kernel without invariants, > > the bug might actually go unnoticed). > > So for the end user it's better to have the bug go unnoticed than to > get a kernel panic and notice the bug? Please tell me I'm misunder- > standing something here. I have to concur. I've never understood the "don't worry be happy" point of view on this issue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 8:50: 5 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 9F5FF15407 for ; Wed, 10 Mar 1999 08:50:02 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA26851; Wed, 10 Mar 1999 11:49:43 -0500 (EST) (envelope-from wollman) Date: Wed, 10 Mar 1999 11:49:43 -0500 (EST) From: Garrett Wollman Message-Id: <199903101649.LAA26851@khavrinen.lcs.mit.edu> To: Dan Swartzendruber Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: References: <28892.921083219@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I have to concur. I've never understood the "don't worry be happy" > point of view on this issue. Do you always compile and install all your programs with debugging symbols? -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 Mar 10 8:58: 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 D5BDA150F8 for ; Wed, 10 Mar 1999 08:58: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 RAA93661; Wed, 10 Mar 1999 17:57:43 +0100 (CET) (envelope-from des) To: sthaug@nethelp.no Cc: dillon@apollo.backplane.com, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <28892.921083219@verdi.nethelp.no> From: Dag-Erling Smorgrav Date: 10 Mar 1999 17:57:43 +0100 In-Reply-To: sthaug@nethelp.no's message of "Wed, 10 Mar 1999 17:26:59 +0100" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no writes: > > Uh, no. Invariants are for developers who want to make sure their code > > is correct. There is no reason why an end user would want to build a > > kernel with invariants enabled. Invariants will *not* increase data > > safety. If they have any effect at all (i.e. if they actually catch a > > bug), the result is a panic (whereas with a kernel without invariants, > > the bug might actually go unnoticed). > So for the end user it's better to have the bug go unnoticed than to > get a kernel panic and notice the bug? Please tell me I'm misunder- > standing something here. No, it is not - not in the general case, and not in the long term. I was trying to point out that there may be extreme cases where an otherwise harmless bug would cause a panic with invariants enabled. Matt claimed that invariants increase data safety, which I find difficult to understand. The only possible value an end user could derive from a kernel with invariants is a backtrace to attach to a send-pr. 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 Mar 10 8:58:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (Postfix) with ESMTP id 447FF152FE for ; Wed, 10 Mar 1999 08:58:18 -0800 (PST) (envelope-from druber@mail.kersur.net) Received: from localhost (druber@localhost) by mail.kersur.net (8.9.1/8.9.1) with SMTP id MAA28077; Wed, 10 Mar 1999 12:03:00 -0500 (EST) Date: Wed, 10 Mar 1999 12:03:00 -0500 (EST) From: Dan Swartzendruber To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: <199903101649.LAA26851@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, 10 Mar 1999, Garrett Wollman wrote: > < said: > > > I have to concur. I've never understood the "don't worry be happy" > > point of view on this issue. > > Do you always compile and install all your programs with debugging > symbols? No, but I didn't think that was what we were talking about. I thought we were talking about assertions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 8:58:38 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 7A2F515378 for ; Wed, 10 Mar 1999 08:58:33 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA14506; Wed, 10 Mar 1999 11:58:07 -0500 (EST) Date: Wed, 10 Mar 1999 11:58:07 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Garrett Wollman Cc: Dan Swartzendruber , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: <199903101649.LAA26851@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, 10 Mar 1999, Garrett Wollman wrote: > < said: > > > I have to concur. I've never understood the "don't worry be happy" > > point of view on this issue. > > Do you always compile and install all your programs with debugging > symbols? This is the DEVELOPMENT branch of the FreeBSD project, and you know that. > > -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 > 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 Wed Mar 10 9:22:38 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 5908D1517D for ; Wed, 10 Mar 1999 09:22:35 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA27037; Wed, 10 Mar 1999 12:22:17 -0500 (EST) (envelope-from wollman) Date: Wed, 10 Mar 1999 12:22:17 -0500 (EST) From: Garrett Wollman Message-Id: <199903101722.MAA27037@khavrinen.lcs.mit.edu> To: Dan Swartzendruber Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: References: <199903101649.LAA26851@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > No, but I didn't think that was what we were talking about. I thought > we were talking about assertions. We were talking about invariants, which document the conditions which nearby code expect and/or cause. To actually check these conditions in a production system is a waste of CPU power; their function is to define for the developers precisely what the expected outcome of a particular operation is, so that new bugs are not introduced when code is modified. -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 Mar 10 11: 0: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 1896D1537A for ; Wed, 10 Mar 1999 11:00:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA57042; Wed, 10 Mar 1999 10:59:55 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 10:59:55 -0800 (PST) From: Matthew Dillon Message-Id: <199903101859.KAA57042@apollo.backplane.com> To: Garrett Wollman Cc: Dan Swartzendruber , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <199903101649.LAA26851@khavrinen.lcs.mit.edu> <199903101722.MAA27037@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :We were talking about invariants, which document the conditions which :nearby code expect and/or cause. To actually check these conditions :in a production system is a waste of CPU power; their function is to :define for the developers precisely what the expected outcome of a :particular operation is, so that new bugs are not introduced when code :is modified. : :-GAWollman : :-- :Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same I would not characterize the use of invariants in production kernels as being a waste of cpu power... I'm sure there are many people who are more interested in data integrity then in performance. The use of inviariants can conceivably catch a problem early that might otherwise corrupt the system later. On the otherhand, the speeddaemons might not want either the invariants or the standard sanity checks, in which case they do not turn on invariant support and they do turn on MAX_PERF ( which gets rid of most of the standard sanity checks ). -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 Mar 10 11: 5: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 4E3B4151DD for ; Wed, 10 Mar 1999 11:05:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA57081; Wed, 10 Mar 1999 11:05:11 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 11:05:11 -0800 (PST) From: Matthew Dillon Message-Id: <199903101905.LAA57081@apollo.backplane.com> To: Dag-Erling Smorgrav Cc: sthaug@nethelp.no, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <28892.921083219@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :No, it is not - not in the general case, and not in the long term. I :was trying to point out that there may be extreme cases where an :otherwise harmless bug would cause a panic with invariants enabled. : :Matt claimed that invariants increase data safety, which I find :difficult to understand. : :DES There is no such thing as a harmless bug. If it's a bug, it needs to be fixed. Many 'harmless bugs' which are noted in source code come back to bite you later when some other programmer adds new code that uses a function in a legal but never-before-tested way. It is my considered opinion that one of the reasons why it has taken FreeBSD years to work out and fix serious bugs in the kernel is that there are simply not enough sanity checks being made in the kernel. The VM system is especially fragile in this regard, but most of the rest of the system has the same problem. For example, trying to block on a lockmgr lock inside an interrupt should result in an instantanious panic. But it doesn't. I can recall at least a dozen bugs that took months to locate because that sort of sanity check is not being made. It is *NOT* 'harmless', even if the occassional hit doesn't fry the system. -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 Mar 10 11:21:19 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 B8FFD153FA for ; Wed, 10 Mar 1999 11:20:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA57256; Wed, 10 Mar 1999 11:20:38 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 11:20:38 -0800 (PST) From: Matthew Dillon Message-Id: <199903101920.LAA57256@apollo.backplane.com> To: Dag-Erling Smorgrav Cc: "Daniel C. Sobral" , Jos Backus , Dmitrij Tejblum , perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> <19990223105939.D97001@hal.mpn.cp.philips.com> <36D329D1.73146EEF@newsguy.com> <199902250803.AAA01163@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Uh, no. Invariants are for developers who want to make sure their code :is correct. There is no reason why an end user would want to build a :kernel with invariants enabled. Invariants will *not* increase data :safety. If they have any effect at all (i.e. if they actually catch a :bug), the result is a panic (whereas with a kernel without invariants, :the bug might actually go unnoticed). : :You must be thinking of the FAILSAFE option. : :DES :-- :Dag-Erling Smorgrav - des@flood.ping.uio.no I would rather the system panic then corrupt a filesystem. Invariants are most useful to developers, but just because a developer's testing doesn't hit any invariants doesn't mean that the invariant won't get hit after the developer commits his code. I think what you are missing here is the fact that allowing bugs to go unnoticed draws out the debugging process. If we had more KASSERT's in the kernel 3 years ago, we would not still have a buggy kernel today. Sweeping bugs under the rug this way does not help anyone. It goes without saying that users catch almost as many bugs as developers, they simply can't fix them. When the a production kernel does not perform extra sanity checks, a bug can remain undetected for years. Therefore, my preference is to turn invariants on on all my production kernels as well as my development kernels. -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 Mar 10 11:35:32 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 8CCB3153F0 for ; Wed, 10 Mar 1999 11:35:22 -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 UAA21323; Wed, 10 Mar 1999 20:35:03 +0100 (CET) (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 UAA32859; Wed, 10 Mar 1999 20:34:52 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Dag-Erling Smorgrav , sthaug@nethelp.no, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.org Subject: Re: panic: zone: entry not free In-reply-to: Your message of "Wed, 10 Mar 1999 11:05:11 PST." <199903101905.LAA57081@apollo.backplane.com> Date: Wed, 10 Mar 1999 20:34:52 +0100 Message-ID: <32857.921094492@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You two are basically discussing "overspecifying source code" vs "normal source code". It doesn't really matter much if the overspecifying consists of merging the TeX sources for a book or by adding invariants as part of design verification. The discussion itself has about as much merit as our recent style(9) discussions, split infinitives included or not: It is pointless. We already have one option in the kernel for "increased sanity checks", it's called "DIAGNOSTIC" and it is legal to add (even substantial) amounts of extra code under that option, as long as there is a sensible reason. Several of my kernels run with DIAGNOSTIC defined, and debug symbols and basic-block profiling to boot. And yes, I do find bugs that way. And no, I would hate to spend 50% of my performance on those options in production. Considering that I think a sensible approach here would be to define a global macro called "INVARIANT(condition, text)" as follows: #ifdef DIAGNOSTIC #define INVARIANT(condition, text) if (condition) ; else panic(text) #else #define INVARIANT(condition, text) do ; while (0) #endif In a suitably global kernel include file. Can everybody live with that as a compromise ? -- 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 10 11:48: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 C7D0E151EA for ; Wed, 10 Mar 1999 11:48:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA57482; Wed, 10 Mar 1999 11:44:20 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 11:44:20 -0800 (PST) From: Matthew Dillon Message-Id: <199903101944.LAA57482@apollo.backplane.com> To: Poul-Henning Kamp Cc: Dag-Erling Smorgrav , sthaug@nethelp.no, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.org Subject: Re: panic: zone: entry not free References: <32857.921094492@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't use DIAGNOSTIC because it's overly intrusive and cause cause panics or create bugs where none exist. At least that was true in 2.2.x. I remember trying to use it at BEST. The result was continually crashing machines due to bugs in the diagnostic code ( such as diagnostics that were using a blocking malloc() inside an interrupt ). Personally, I would be happier if DIAGNOSTIC were ripped out entirely and replaced with something less intrusive. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 12: 2: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 C1C28151B2 for ; Wed, 10 Mar 1999 12:02:53 -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 VAA21465; Wed, 10 Mar 1999 21:02:35 +0100 (CET) (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 VAA33050; Wed, 10 Mar 1999 21:02:25 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Dag-Erling Smorgrav , sthaug@nethelp.no, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.org Subject: Re: panic: zone: entry not free In-reply-to: Your message of "Wed, 10 Mar 1999 11:44:20 PST." <199903101944.LAA57482@apollo.backplane.com> Date: Wed, 10 Mar 1999 21:02:25 +0100 Message-ID: <33048.921096145@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903101944.LAA57482@apollo.backplane.com>, Matthew Dillon writes: > I don't use DIAGNOSTIC because it's overly intrusive and cause cause > panics or create bugs where none exist. Then it should be fixed. > Personally, I would be happier if DIAGNOSTIC were ripped out entirely > and replaced with something less intrusive. I wouldn't. -- 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 10 12:52:53 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 4D247151E9 for ; Wed, 10 Mar 1999 12:52:50 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA01438; Thu, 11 Mar 1999 05:52:28 +0900 (JST) Message-ID: <36E6D191.5AD6B575@newsguy.com> Date: Thu, 11 Mar 1999 05:09:53 +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 Feldman Cc: Garrett Wollman , Dan Swartzendruber , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free 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: > > On Wed, 10 Mar 1999, Garrett Wollman wrote: > > > < said: > > > > > I have to concur. I've never understood the "don't worry be happy" > > > point of view on this issue. > > > > Do you always compile and install all your programs with debugging > > symbols? > > This is the DEVELOPMENT branch of the FreeBSD project, and you know that. Which would get back to my original (contested) statement: you shouldn't use INVARIANTS unless you are running blah, blah, blah, say, for example, -current. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 13: 2:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from landsraad.net (caladan.arrakis.es [195.5.65.34]) by hub.freebsd.org (Postfix) with ESMTP id 81D7A15405 for ; Wed, 10 Mar 1999 13:02:30 -0800 (PST) (envelope-from magickey@arrakis.es) Received: from 10.0.1.1.inf (if-40.arrakis.es [195.5.75.40]) by landsraad.net (8.9.3/8.9.3) with SMTP id WAA22239 for freebsd-current@freebsd.org; Wed, 10 Mar 1999 22:04:19 +0100 (MET) Date: Wed, 10 Mar 1999 22:04:19 +0100 (MET) From: magickey To: freebsd-current@freebsd.org Subject: MAGIC LINK EXCHANGE Message-Id: Content-Type: TEXT/PLAIN charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Friend in the magic: My name is Eduardo Hernando, and I am devoted to maker of electronic effects for magicians, I would like if it is possible you to insert my link in your web. I would be pleased if you would agree to add my page to your website.  If you would like to, let me know, and I will add your page to my website. My link: ELECTRONIC ILLUSIONS MAKER OF ELECTRONIC ILLUSIONS FOR MAGICIANS http://www.arrakis.es/~eduher/export.htm e. mail magickey@arrakis.es To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 13:20:35 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 EDC9814C44 for ; Wed, 10 Mar 1999 13:20:25 -0800 (PST) (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 QAA46177; Wed, 10 Mar 1999 16:19:45 -0500 (EST) Date: Wed, 10 Mar 1999 16:19:45 -0500 (EST) From: John Fieber To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: wchar.h? In-Reply-To: <199903100428.UAA38031@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 Tue, 9 Mar 1999, Archie Cobbs wrote: > wcslen() > wcscpy() > wcsncpy() > wcscat() > wcscmp() > wcsncmp() > > How come FreeBSD doesn't have these? Is there a complicated problem > preventing us from adding them? I have a start at all the wc functions in the NA1 of ANSI C which includes these and wide versions of most of the stdio functions (fgetwc, fputwc and the like) as well as wide iswxxx() ctype functions. Anybody who would like to finish the job is most welcome to what I have so far. (I've also got a Unicode UTF-8 local I'd like to bring in at some point...) -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 13:57:48 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 1EB1E14F7E for ; Wed, 10 Mar 1999 13:57:46 -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 NAA71468; Wed, 10 Mar 1999 13:53:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: Poul-Henning Kamp , Dag-Erling Smorgrav , sthaug@nethelp.no, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-reply-to: Your message of "Wed, 10 Mar 1999 11:44:20 PST." <199903101944.LAA57482@apollo.backplane.com> Date: Wed, 10 Mar 1999 13:53:06 -0800 Message-ID: <71464.921102786@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't use DIAGNOSTIC because it's overly intrusive and cause cause > panics or create bugs where none exist. Then it should be fixed. I think DIAGNOSTIC is *supposed* to do everything you're arguing for and to scream for its removal in one breath and then call for a mechanism which does exactly what it was *supposed* to do in the next doesn't exactly advance the credibility of the argument, knowwhutahmean? - 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 10 16:34:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id 9E0E5150E4 for ; Wed, 10 Mar 1999 16:34:37 -0800 (PST) (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 TAA27981; Wed, 10 Mar 1999 19:34:12 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Wed, 10 Mar 1999 19:34:12 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: "Daniel C. Sobral" Cc: paul@originative.co.uk, current@freebsd.org Subject: Re: HEADS UP: new loader.rc stuff In-Reply-To: <36E6451C.67B16009@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 So this is actually just a general response to the whole thing--one of the things I actually dislike about rc.conf is its flexibility: the user can put anything script-wise they like into it. My temptation would be to reduce the flexibility: to have a simple name:value configuration file (with appropriate extensions for lists, quoted strings, etc) that is guaranteed to be readable by any third-party (or even first-party :) automated configuration programs. Depending on your mood, the name field could even be MIB-like (boot.runaway: yes). It just seems like sometimes scripts give too much flexibility :-); rather than providing useful increased functionality, they improve the chances that the user will screw themselves by taking advantage of it in ways that confuse automated utilities such as configuration checkers, managers, etc. 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 Wed Mar 10 16:40:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id E2E85150FF for ; Wed, 10 Mar 1999 16:40:51 -0800 (PST) (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 TAA28039; Wed, 10 Mar 1999 19:39:24 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Wed, 10 Mar 1999 19:39:23 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: sthaug@nethelp.no Cc: des@flood.ping.uio.no, dillon@apollo.backplane.com, dcs@newsguy.com, Jos.Backus@nl.origin-it.com, dima@tejblum.dnttm.rssi.ru, perhaps@yes.no, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: <28892.921083219@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, 10 Mar 1999 sthaug@nethelp.no wrote: > > Uh, no. Invariants are for developers who want to make sure their code > > is correct. There is no reason why an end user would want to build a > > kernel with invariants enabled. Invariants will *not* increase data > > safety. If they have any effect at all (i.e. if they actually catch a > > bug), the result is a panic (whereas with a kernel without invariants, > > the bug might actually go unnoticed). > > So for the end user it's better to have the bug go unnoticed than to > get a kernel panic and notice the bug? Please tell me I'm misunder- > standing something here. # Halt the system (panic) on discovering an unexpected kernel # inconsistency, in an attempt to prevent data corruption. Disabled # by default on production releases because of increased CPU load and that # these states "should never happen". Good on -CURRENT. # # Bugs: Does not stop on other kinds of failures (hardware, etc) # # options FAILSTOP 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 Wed Mar 10 17:17:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id 5EFA414C3B; Wed, 10 Mar 1999 17:17:32 -0800 (PST) (envelope-from girgen@partitur.se) Received: from d1o29.telia.com (root@d1o29.telia.com [194.236.214.241]) by maile.telia.com (8.8.5/8.8.8) with ESMTP id CAA11869; Thu, 11 Mar 1999 02:17:00 +0100 (CET) Received: from stordatan.telia.com (t4o29p64.telia.com [194.236.215.184]) by d1o29.telia.com (8.8.8/8.8.5) with ESMTP id CAA25538; Thu, 11 Mar 1999 02:16:56 +0100 (MET) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.telia.com (8.9.2/8.9.1) with ESMTP id CAA53738; Thu, 11 Mar 1999 02:16:35 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <36E71973.341EA98D@partitur.se> Date: Thu, 11 Mar 1999 02:16:35 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: panic: aha0 Invalid CCB or SG list References: <36D4B092.8B076D55@partitur.se> <199902252308.QAA04402@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 Hi Warner! Sorry to intrude, but I just want to check that I didn't miss any messages in this thread. Have you found anything that might be causing this problem? I think it's related to the 100% CPU utilization while writing full speed to both the ahc2940uw on pci and the 1542CP on isa. I realize this is not the easiest thing to debug; I had to sit and watch the screen for 90 minutes before it happened... Drop me a mail if you find anything. Thanks! /Palle Warner Losh wrote: > > In message <36D4B092.8B076D55@partitur.se> Palle Girgensohn writes: > : I've seen three crashes in the last couple of weeks, with a server > : box that's been running stable as a rock for two years, at least. It > : has an adaptec 2940UW with six disks, and an adaptec 1542CP that's > : connected to a seagate travan tape driver. > > OK. This card is known to be good. At least I've not had any > problems with it. > > : It's running STABLE-3.1 from Feb 19 1999, and since the last > : upgrade, I've seen three crashes, all related to dumping to > : tape. Since I got no info on what happened, I decided to sit down > : with the machine, run a backup sequence to tape, and wait for it to > : possibly crash. After 90 minutes, I was about to give up when > : suddenly, poof: > : panic: aha0 Invalid CCB or SG list. > : > : So, it's probably the 1540 driver (or hardware)? > > Ah. OK. I'm not doing tape stuff on my machine. How fast is that > seagate tr-4 that you are doing? > > : Can anybody shed some light on what to do? Is it software? That's my > : guess, since the machine never ONCE has crashed until the upgrade to > : 3.x. I had one crash when running current form beginning of January > : (soon after moving to 3.x), and now theese three in a week. The 1540 > : has been in the machine for about six months. > > Chances are really good that this is software. The invalid ccb or sg > list is due to either a race condition or something taht corrupts > these things. > > : If there's anything I can do to help debug I'll do it, but device > : drivers are a little above my level of expertise. > > If you can wait a day or three, I might be able to find something that > will help. However, I don't have a tape drive right now to test it > with. I'll see what I can beg, borrow or steal. > > 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 10 17:48:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from WWW.meridianksi.com (meridianksi.com [207.86.113.200]) by hub.freebsd.org (Postfix) with ESMTP id 795CE151E5 for ; Wed, 10 Mar 1999 17:48:15 -0800 (PST) (envelope-from rdewalt@meridianksi.com) Received: from rdewalt.meridianksi.com ([207.86.113.194]) by WWW.meridianksi.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-57398U100L2S100V35) with SMTP id AAA66 for ; Wed, 10 Mar 1999 21:00:48 -0500 Message-Id: <3.0.3.32.19990310204716.006ffc7c@207.86.113.200> X-Sender: rdewalt@207.86.113.200 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 10 Mar 1999 20:47:16 -0500 To: freebsd-current@FreeBSD.ORG From: rdewalt@meridianksi.com (Ryan Dewalt) Subject: problem with pccard.c cvsup'ed 3-10-99 15:00:54 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After running cvsup today, and running my weekly make world (with no problems) re-compiling the kernel, I recieved this error. (after the original make all failed, I re-ran this to regenerate the error) porta# make all loading kernel pccard.o: In function `unregister_device_interrupt': pccard.o(.text+0x31c): undefined reference to `unregister_pcic_intr' pccard.o: In function `pccard_alloc_intr': pccard.o(.text+0x691): undefined reference to `register_pcic_intr' *** Error code 1 porta# current $Id in pccard.c is: * $Id: pccard.c,v 1.73 1999/03/10 15:00:54 roger Exp $ Running FreeBSD 4.0-CURRENT on a CTX 700E laptop (32 M ram) Until today, I've had no problems at all with the PCMCIA subsystem. (relevant line from the last successfull dmesg) pcic0: rev 0x01 int a irq 255... pcic1: (same as above), but "int b" Any suggestions? -Thanks Ryan Dewalt rdewalt@meridianksi.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 10 18:11:35 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 BADD815167 for ; Wed, 10 Mar 1999 18:11:28 -0800 (PST) (envelope-from peter.jeremy@AUSS2.ALCATEL.COM.AU) Received: by border.alcanet.com.au id <40401>; Thu, 11 Mar 1999 11:59:08 +1000 Date: Thu, 11 Mar 1999 12:11:03 +1000 From: Peter Jeremy Subject: Re: panic: zone: entry not free To: current@FreeBSD.ORG Message-Id: <99Mar11.115908est.40401@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > there are simply not enough sanity checks being made in the kernel. There is a trade off between the amount of sanity checking and performance. We need to make sure that any sanity checking we add doesn't make the system unusably slow or adversely impact interrupt response. It's up the the relevant developers to make sure that a `reasonable' level of sanity checking is done. And later > It goes without saying that users catch almost as many bugs as developers, Possibly more - there are more of them and they are likely to be stressing the system in unexpected (to the developer) ways. > Therefore, my preference is to turn invariants on on all my production > kernels as well as my development kernels. This means that invariants need to add relatively little overhead. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 18:17: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 79987151C6 for ; Wed, 10 Mar 1999 18:17:45 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA59257; Wed, 10 Mar 1999 18:16:23 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 18:16:23 -0800 (PST) From: Matthew Dillon Message-Id: <199903110216.SAA59257@apollo.backplane.com> To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <99Mar11.115908est.40401@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Therefore, my preference is to turn invariants on on all my production :> kernels as well as my development kernels. : :This means that invariants need to add relatively little overhead. : :Peter .... which they do. -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 Mar 10 18:59:13 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 4E25C15064 for ; Wed, 10 Mar 1999 18:59:05 -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 VAA68892; Wed, 10 Mar 1999 21:56:34 -0500 (EST) Date: Wed, 10 Mar 1999 21:56:34 -0500 (EST) From: Chuck Robey To: Matthew Dillon Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: <199903110216.SAA59257@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, 10 Mar 1999, Matthew Dillon wrote: > : > :> Therefore, my preference is to turn invariants on on all my production > :> kernels as well as my development kernels. > : > :This means that invariants need to add relatively little overhead. > : > :Peter > > .... which they do. You know, guys, for programmers, wanting immediate panics on stuff like this is great, but there isn't one user in a thousand that wants this. If you make this kinda stuff default on a version *other than* current (current being by definition, for programmers/developers only) then you're going to hear bloody murder, and you guys will be doing vast damage to FreeBSD's reputation. Users don't want panics, and they don't care why, they just want things to work. Your reasons are great, and totally irrelevant, unless I misunderstood you and you meant to restrict it to current only. ----------------------------+----------------------------------------------- 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 10 19:10: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id E40C615207 for ; Wed, 10 Mar 1999 19:09:58 -0800 (PST) (envelope-from shigeru@iij.ad.jp) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id MAA10257 for ; Thu, 11 Mar 1999 12:09:40 +0900 (JST) Received: from iij.ad.jp (shigeru@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id MAA26576 for ; Thu, 11 Mar 1999 12:09:40 +0900 (JST) Message-Id: <199903110309.MAA26576@ns.iij.ad.jp> To: freebsd-current@freebsd.org Subject: Re: problem with pccard.c cvsup'ed 3-10-99 15:00:54 In-Reply-To: Your message of "Wed, 10 Mar 1999 20:47:16 -0500" References: <3.0.3.32.19990310204716.006ffc7c@207.86.113.200> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 11 Mar 1999 12:09:39 +0900 From: =?ISO-2022-JP?B?GyRCOzNLXBsoQg==?= =?ISO-2022-JP?B?GyRCTFAbKEI=?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Ryan" == Ryan Dewalt writes: Ryan> re-compiling the kernel, I recieved this error. (after the Ryan> original make all failed, I re-ran this to regenerate the error) Ryan> porta# make all Ryan> loading kernel Ryan> pccard.o: In function `unregister_device_interrupt': Ryan> pccard.o(.text+0x31c): undefined reference to `unregister_pcic_intr' Ryan> pccard.o: In function `pccard_alloc_intr': Ryan> pccard.o(.text+0x691): undefined reference to `register_pcic_intr' Ryan> *** Error code 1 Ryan> porta# unregister_pcic_intr() and register_pcic_intr() are described in @sys/pccard/pcic.c but they are described as 'static' functions when APIC_IO is not defined ;-( I think it is better to delete 'static' at line 189 and line 194 in @sys/pccard/pcic.c than to chnage unregister_pcic_intr()/register_pcic_intr() to unregister_intr()/register_intr() in @sys/pccard/pccard.c. I fixed @sys/pccard/pcic.c and recompiled. and now I'm using new kernel on a VAIO 818. Thanks, ------- YAMAMOTO Shigeru Internet Initiative Japan Inc. Network Engineering Div. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 20:36: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 2005D14D9A for ; Wed, 10 Mar 1999 20:36:24 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id NAA17444; Thu, 11 Mar 1999 13:36:03 +0900 (JST) Message-ID: <36E747EB.A6CFA403@newsguy.com> Date: Thu, 11 Mar 1999 13:34:51 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Robert Watson Cc: paul@originative.co.uk, current@freebsd.org Subject: Re: HEADS UP: new loader.rc stuff 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 Robert Watson wrote: > > So this is actually just a general response to the whole thing--one of the > things I actually dislike about rc.conf is its flexibility: the user can > put anything script-wise they like into it. My temptation would be to > reduce the flexibility: to have a simple name:value configuration file > (with appropriate extensions for lists, quoted strings, etc) that is > guaranteed to be readable by any third-party (or even first-party :) > automated configuration programs. Depending on your mood, the name field > could even be MIB-like (boot.runaway: yes). > > It just seems like sometimes scripts give too much flexibility :-); rather > than providing useful increased functionality, they improve the chances > that the user will screw themselves by taking advantage of it in ways that > confuse automated utilities such as configuration checkers, managers, etc. Well, the idea behind loader.conf is *reducing* flexibility, in a way... :-) There are features in it that make it that still gives a lot of flexibility, to be able to deal with unexpected situations. But loader.conf syntax is ="", with # treated like bourne shell do. The loader.rc file contains commands in a very flexible language, making it virtually impossible for automated tools to modify it. So, loader.conf. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 21:18: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from WWW.meridianksi.com (meridianksi.com [207.86.113.200]) by hub.freebsd.org (Postfix) with ESMTP id 875CA15171 for ; Wed, 10 Mar 1999 21:17:34 -0800 (PST) (envelope-from tet@nova.org) Received: from mg-20425420-73.ricochet.net ([204.254.20.73]) by WWW.meridianksi.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-57398U100L2S100V35) with ESMTP id AAA199; Thu, 11 Mar 1999 00:30:05 -0500 Date: Thu, 11 Mar 1999 00:17:26 +0000 (GMT) From: "Tet \"PansyAss\" Solfire" X-Sender: tet@localhost To: =?ISO-2022-JP?B?GyRCOzNLXBsoQg==?= =?ISO-2022-JP?B?GyRCTFAbKEI=?= Cc: freebsd-current@FreeBSD.ORG Subject: Re: problem with pccard.c cvsup'ed 3-10-99 15:00:54 In-Reply-To: <199903110309.MAA26576@ns.iij.ad.jp> 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 Well, I went and removed "static" from both lines in pcic.c as noted below, did a make clean, make depend all, and recieved the same error. Unfortunately, I'm running out of ideas. I've tried commenting out the whole sections, replacing the register_pcic.init with "return(10);" (what my pcmcia was using for IRQ before) it compiles clean, however, my NIC does not work.. (which I assumed) Running out of ideas, coffee, and sleep... I'd rather not have to downgrade my source tree if necessary... -Ryan On Thu, 11 Mar 1999, [ISO-2022-JP] $B;3K\(B[ISO-2022-JP] $BLP(B wrote: > > >>>>> "Ryan" == Ryan Dewalt writes: > Ryan> re-compiling the kernel, I recieved this error. (after the > Ryan> original make all failed, I re-ran this to regenerate the error) > Ryan> porta# make all > Ryan> loading kernel > Ryan> pccard.o: In function `unregister_device_interrupt': > Ryan> pccard.o(.text+0x31c): undefined reference to `unregister_pcic_intr' > Ryan> pccard.o: In function `pccard_alloc_intr': > Ryan> pccard.o(.text+0x691): undefined reference to `register_pcic_intr' > Ryan> *** Error code 1 > Ryan> porta# > > unregister_pcic_intr() and register_pcic_intr() are described in > @sys/pccard/pcic.c > but they are described as 'static' functions when APIC_IO is not > defined ;-( > > I think it is better to delete 'static' at line 189 and line 194 in > @sys/pccard/pcic.c than to chnage > unregister_pcic_intr()/register_pcic_intr() to > unregister_intr()/register_intr() in @sys/pccard/pccard.c. > > I fixed @sys/pccard/pcic.c and recompiled. > and now I'm using new kernel on a VAIO 818. > > Thanks, > ------- > YAMAMOTO Shigeru Internet Initiative Japan Inc. > Network Engineering Div. > > > 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 10 21:20: 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 BCCAD14E51 for ; Wed, 10 Mar 1999 21:20:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA61078; Wed, 10 Mar 1999 21:19:29 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 21:19:29 -0800 (PST) From: Matthew Dillon Message-Id: <199903110519.VAA61078@apollo.backplane.com> To: Chuck Robey Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> : :> :This means that invariants need to add relatively little overhead. :> : :> :Peter :> :> .... which they do. : :You know, guys, for programmers, wanting immediate panics on stuff like :this is great, but there isn't one user in a thousand that wants this. :If you make this kinda stuff default on a version *other than* current :(current being by definition, for programmers/developers only) then :you're going to hear bloody murder, and you guys will be doing vast :damage to FreeBSD's reputation. : :Users don't want panics, and they don't care why, they just want things No no no... you are missing the whole point. *IF* we put these kinds of checks in by default, the result is a few more panics in the near term, but *NO* panics in the medium and long term. In otherwords, by putting the checks in now, the kernel gets debugged much more quickly --- to the point where a year down the line we no longer get kernel panics at all. If you are worried about FreeBSD's reputation, just think where we would be now if we had done this 3 years ago! When you push something under the rug, all you do is draw out the complaints into multiple years. This can't be ( and hasn't been ) good for our reputation. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 10 23:48:38 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 7E77D14DFE for ; Wed, 10 Mar 1999 23:48:36 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id BAA28636; Thu, 11 Mar 1999 01:47:51 -0600 (CST) From: Kevin Day Message-Id: <199903110747.BAA28636@home.dragondata.com> Subject: Re: panic: zone: entry not free In-Reply-To: <199903110519.VAA61078@apollo.backplane.com> from Matthew Dillon at "Mar 10, 1999 9:19:29 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 11 Mar 1999 01:47:50 -0600 (CST) Cc: chuckr@mat.net, peter.jeremy@AUSS2.ALCATEL.COM.AU, 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 > :> : > :> :This means that invariants need to add relatively little overhead. > :> : > :> :Peter > :> > :> .... which they do. > : > :You know, guys, for programmers, wanting immediate panics on stuff like > :this is great, but there isn't one user in a thousand that wants this. > :If you make this kinda stuff default on a version *other than* current > :(current being by definition, for programmers/developers only) then > :you're going to hear bloody murder, and you guys will be doing vast > :damage to FreeBSD's reputation. > : > :Users don't want panics, and they don't care why, they just want things > > No no no... you are missing the whole point. > > *IF* we put these kinds of checks in by default, the result is a > few more panics in the near term, but *NO* panics in the medium and > long term. > > In otherwords, by putting the checks in now, the kernel gets debugged > much more quickly --- to the point where a year down the line we no > longer get kernel panics at all. > Also, try commenting out a panic line in a known bug, and watch how quickly the kernel crashes anyway, in the same situation. Most of the time, the panic is dumping out (some) debugging information before crashing all over itself. Just taking out the diagnostic message is really just making crashes more obscure. If the error were recoverable, normally the system recovers from it. If it's not, it panic's and dies. Take out the panic, and all you've got left is a 'die', which probably will lead people on a wild goose chase as to where that section of memory really got trashed. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 11 0: 5:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-28.ppp.wenet.net [206.15.85.28]) by hub.freebsd.org (Postfix) with ESMTP id 151A314CF9 for ; Thu, 11 Mar 1999 00:05:22 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id AAA41750; Thu, 11 Mar 1999 00:04:40 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Thu, 11 Mar 1999 00:04:40 -0800 (PST) From: Alex Zepeda To: Chuck Robey Cc: Matthew Dillon , Peter Jeremy , current@FreeBSD.ORG Subject: Re: panic: zone: entry not free 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, 10 Mar 1999, Chuck Robey wrote: > You know, guys, for programmers, wanting immediate panics on stuff like > this is great, but there isn't one user in a thousand that wants this. > If you make this kinda stuff default on a version *other than* current > (current being by definition, for programmers/developers only) then > you're going to hear bloody murder, and you guys will be doing vast > damage to FreeBSD's reputation. Hmm. Well think of it this way. What happens when the kernel doesn't panic but manages to accidentally wipe out your file system without warning? or perhaps just loose some of the more important data on the HDD? What kind of reaction do you expect then? > Users don't want panics, and they don't care why, they just want > things to work. True enough, but at what cost? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 11 1:18: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 4FCBA14BCF for ; Thu, 11 Mar 1999 01:18: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 EAA69738; Thu, 11 Mar 1999 04:16:01 -0500 (EST) Date: Thu, 11 Mar 1999 04:16:01 -0500 (EST) From: Chuck Robey To: Matthew Dillon Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: <199903110519.VAA61078@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, 10 Mar 1999, Matthew Dillon wrote: > :> : > :> :This means that invariants need to add relatively little overhead. > :> : > :> :Peter > :> > :> .... which they do. > : > :You know, guys, for programmers, wanting immediate panics on stuff like > :this is great, but there isn't one user in a thousand that wants this. > :If you make this kinda stuff default on a version *other than* current > :(current being by definition, for programmers/developers only) then > :you're going to hear bloody murder, and you guys will be doing vast > :damage to FreeBSD's reputation. > : > :Users don't want panics, and they don't care why, they just want things > > No no no... you are missing the whole point. > > *IF* we put these kinds of checks in by default, the result is a > few more panics in the near term, but *NO* panics in the medium and > long term. That's completely true, but nearly all users simply couldn't care less. They don't see the long view, they only see what's happening right now. It's the reason that your attitude is totally correct & healthy for a developer ... but the only thing that most users will see is the fact that FreeBSD panics more often. They won't even bother to make of note of why a panic occurred, all they will ever note is that a panic *did* occur. A developer will be helped hugely by your attitude, which is why it would be *very* healthy for current to do what you want. All the folks running current would serve as a better set of guinea pigs ... we're all developers, I don't think any of us would complain ... but never get the idea that a user is going to be happy to get a panic; no matter how much time you spend explaining why it's a good thing, they'll only remember that FreeBSD paniced on them. Alex Zepeda wrote: > Hmm. Well think of it this way. What happens when the kernel doesn't > panic but manages to accidentally wipe out your file system without > warning? or perhaps just loose some of the more important data on the > HDD? What kind of reaction do you expect then? Seeing as we're talking about failures that, most of the time, the user never sees the results of, users won't say a single thing ... if they're box *doesn't* panic, they'll be happy. If it panics more often, they'll notice that, and they won't bother asking why, they'll just switch to Linux (and quickly). They aren't signing on to be FreeBSD beta-testers, you know ... at least, believe me, THEY know that. On top of all that, the ordinary user won't even bother to report the fact that your panic happened (or why), while they're removing FreeBSD. ----------------------------+----------------------------------------------- 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 Mar 11 1:53:52 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 3286815231 for ; Thu, 11 Mar 1999 01:53:48 -0800 (PST) (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 JAA85125 for ; Thu, 11 Mar 1999 09:53:29 GMT Message-ID: <36E79298.444D3E70@tdx.co.uk> Date: Thu, 11 Mar 1999 09:53:28 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: panic: zone: entry not free - Default of state of Invariants References: 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: > That's completely true, but nearly all users simply couldn't care less. > They don't see the long view, they only see what's happening right now. With that I will agree... :) > It's the reason that your attitude is totally correct & healthy for a > developer ... but the only thing that most users will see is the fact > that FreeBSD panics more often. They won't even bother to make of note > of why a panic occurred, all they will ever note is that a panic *did* > occur. Why not make the default 'OFF' for non -current, and just tell the users it's there? I know quite a few FreeBSD users, and out of the bunch I reckon ~3 of them would turn it on, and be happy - the other 9 or so would leave it off, and still be happy... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 11 2: 6: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 332EF15243 for ; Thu, 11 Mar 1999 02:04:27 -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 KAA30247 for ; Thu, 11 Mar 1999 10:05:10 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 11 Mar 1999 10:05:10 +0000 (GMT) From: Doug Rabson To: current@freebsd.org Subject: Proposed change to printf Message-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 want to make this change to printf so that it treats format codes like '%llx' as 64bit formats (i.e. the same as '%qx'). This convention is the same as that used by glibc. I needed this change to make an i386->alpha cross debugger which worked properly but I think that it is a good idea to be compatible with glibc in this respect. Index: vfprintf.c =================================================================== RCS file: /home/ncvs/src/lib/libc/stdio/vfprintf.c,v retrieving revision 1.20 diff -u -r1.20 vfprintf.c --- vfprintf.c 1998/09/16 04:17:44 1.20 +++ vfprintf.c 1999/02/20 10:20:08 @@ -545,7 +545,10 @@ flags |= SHORTINT; goto rflag; case 'l': - flags |= LONGINT; + if (flags & LONGINT) + flags |= QUADINT; + else + flags |= LONGINT; goto rflag; case 'q': flags |= QUADINT; @@ -1016,7 +1019,10 @@ flags |= SHORTINT; goto rflag; case 'l': - flags |= LONGINT; + if (flags & LONGINT) + flags |= QUADINT; + else + flags |= LONGINT; goto rflag; case 'q': flags |= QUADINT; -- 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 Thu Mar 11 2:12:45 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 56FF81527C for ; Thu, 11 Mar 1999 02:12:28 -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 CAA60046; Thu, 11 Mar 1999 02:12:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs In-reply-to: Your message of "Tue, 02 Mar 1999 02:56:00 PST." <19990302025600.F13655@relay.nuxi.com> Date: Thu, 11 Mar 1999 02:12:16 -0800 Message-ID: <60043.921147136@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've put the bmake & contrib framework for EGCS at > ftp://ftp.nuxi.com/pub/FreeBSD/egcs > (ftp://ftp.nuxi.com/pub/FreeBSD/egcs/cvs is all you really need) > This is very rough work, but should help us towards our goal. > > In there you will find a CVS tree under ``cvs''. This CVS tree > corresponds to /usr/src in that you will find "src/gnu/usr.bin/cc", > "src/gnu/lib/libstdc++", and "src/contrib/egcs". How's this going? I didn't quite get the same results when I tried overlapping cvs checkouts of the base bits and your own repository, but then LinuxWorld came up and I never got back to trying this again. What's the preferred method for tracking your egcs work, given one completely spammable box, a CVS repository (the project's), a network connection and plenty of disk space? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 11 3:16:31 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 9EBBC15106 for ; Thu, 11 Mar 1999 03:16:26 -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 WAA12554; Thu, 11 Mar 1999 22:16:07 +1100 Date: Thu, 11 Mar 1999 22:16:07 +1100 From: Bruce Evans Message-Id: <199903111116.WAA12554@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dfr@nlsystems.com Subject: Re: Proposed change to printf Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I want to make this change to printf so that it treats format codes like >'%llx' as 64bit formats (i.e. the same as '%qx'). This convention is the >same as that used by glibc. %llx is actually for unsigned long longs, and %qx is actually for u_quad_t's. These types are different for FreeBSD on alphas. Printing quad_t's using %llx should cause warnings from gcc -Wformat on alphas, but printing them using %qx should work. I think gcc -Wformat doesn't actually understand %q formats, so printing quad_t's using %qx gives bogus warnings on alphas. However, %llx is more standard. It is in the C9x draft. %qx should go away. >Index: vfprintf.c >=================================================================== >RCS file: /home/ncvs/src/lib/libc/stdio/vfprintf.c,v >retrieving revision 1.20 >diff -u -r1.20 vfprintf.c >--- vfprintf.c 1998/09/16 04:17:44 1.20 >+++ vfprintf.c 1999/02/20 10:20:08 >@@ -545,7 +545,10 @@ > flags |= SHORTINT; > goto rflag; > case 'l': >- flags |= LONGINT; >+ if (flags & LONGINT) >+ flags |= QUADINT; >+ else >+ flags |= LONGINT; > goto rflag; > case 'q': > flags |= QUADINT; >@@ -1016,7 +1019,10 @@ > flags |= SHORTINT; > goto rflag; > case 'l': >- flags |= LONGINT; >+ if (flags & LONGINT) >+ flags |= QUADINT; >+ else >+ flags |= LONGINT; > goto rflag; > case 'q': > flags |= QUADINT; This assumes that long longs have the same representation as quad_t's. I suppose not doing a global change from quad_t to long long is best, because the change should actually be to C9x's intmax_t to support C9x's %m formats. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 11 8: 2:53 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 926E815398 for ; Thu, 11 Mar 1999 08:02:51 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA05472; Fri, 12 Mar 1999 01:02:34 +0900 (JST) Message-ID: <36E7E6F3.FD3F7D3D@newsguy.com> Date: Fri, 12 Mar 1999 00:53: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: Karl Pielorz Cc: current@FreeBSD.ORG Subject: Re: panic: zone: entry not free - Default of state of Invariants References: <36E79298.444D3E70@tdx.co.uk> 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 Karl Pielorz wrote: > > > It's the reason that your attitude is totally correct & healthy for a > > developer ... but the only thing that most users will see is the fact > > that FreeBSD panics more often. They won't even bother to make of note > > of why a panic occurred, all they will ever note is that a panic *did* > > occur. > > Why not make the default 'OFF' for non -current, and just tell the users it's > there? I know quite a few FreeBSD users, and out of the bunch I reckon ~3 of > them would turn it on, and be happy - the other 9 or so would leave it off, > and still be happy... Like it has been done since... middle january? This thread is entering the twilight zone... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 11 8:35: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 008BA15226 for ; Thu, 11 Mar 1999 08:35:19 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id IAA82767; Thu, 11 Mar 1999 08:34:52 -0800 (PST) (envelope-from obrien) Date: Thu, 11 Mar 1999 08:34:52 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs Message-ID: <19990311083452.N79145@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990302025600.F13655@relay.nuxi.com> <60043.921147136@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <60043.921147136@zippy.cdrom.com>; from Jordan K. Hubbard on Thu, Mar 11, 1999 at 02:12:16AM -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 > How's this going? Everything now builds, and I can pass the C++ STL tests supplied with EGCS. There is at least one case w/in gnu/usr.bin/cc that ``make cleandir && make cleandir && make obj && make depend && make && make clean && make'' will file to build. But I haven't worried too much about that yet. The biggest problem is that ``cpp'' will get a sig11 when executed by c++. If I use ``c++ -v'' and manually execute what c++ is, I don't get the sig11. I got tired of trying to track this down, so to get around this (so I could work on libstdc++), I copy ``cpp'' into /usr/libexec from a copy of an installed EGCS port. The version in my repository is EGCS 1.1.2-pre3. Rumors have it that 1.1.2 will released on Friday, and by Monday at the latest. > What's the preferred method for tracking your egcs work, given one On a test box, one should CVSup using: *default host=relay.nuxi.com *default base=. *default release=cvs *default delete use-rel-suffix egcs I create a directory separate from our repository to sup into. Then checkout (``cvs -d co src/gnu src/contrib/egcs'') into a directory separate from /usr/src. I've been compiling things w/in /usr/src/ , but haven't done a ``make world'' with EGCS in-place in /usr/src due to the `cpp w/c++'' problem. -- -- 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 Mar 11 11: 7: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 B556014C37 for ; Thu, 11 Mar 1999 11:07:09 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id OAA24582; Thu, 11 Mar 1999 14:08:59 -0500 (EST) Date: Thu, 11 Mar 1999 14:08:57 -0500 (EST) From: Alfred Perlstein To: Chuck Robey Cc: Matthew Dillon , Peter Jeremy , current@FreeBSD.ORG Subject: Re: panic: zone: entry not free 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, 11 Mar 1999, Chuck Robey wrote: > On Wed, 10 Mar 1999, Matthew Dillon wrote: > > > :> : > > :> :This means that invariants need to add relatively little overhead. > > :> : > > :> :Peter > > :> > > :> .... which they do. > > : > > :You know, guys, for programmers, wanting immediate panics on stuff like > > :this is great, but there isn't one user in a thousand that wants this. > > :If you make this kinda stuff default on a version *other than* current > > :(current being by definition, for programmers/developers only) then > > :you're going to hear bloody murder, and you guys will be doing vast > > :damage to FreeBSD's reputation. > > : > > :Users don't want panics, and they don't care why, they just want things > > > > No no no... you are missing the whole point. > > > > *IF* we put these kinds of checks in by default, the result is a > > few more panics in the near term, but *NO* panics in the medium and > > long term. > > That's completely true, but nearly all users simply couldn't care less. > They don't see the long view, they only see what's happening right now. > It's the reason that your attitude is totally correct & healthy for a > developer ... but the only thing that most users will see is the fact > that FreeBSD panics more often. They won't even bother to make of note > of why a panic occurred, all they will ever note is that a panic *did* > occur. it most likely will crash anyway. > > A developer will be helped hugely by your attitude, which is why it > would be *very* healthy for current to do what you want. All the folks > running current would serve as a better set of guinea pigs ... we're all > developers, I don't think any of us would complain ... but never get the > idea that a user is going to be happy to get a panic; no matter how much > time you spend explaining why it's a good thing, they'll only remember > that FreeBSD paniced on them. it most likely will crash/reboot/freeze anyway. > > Alex Zepeda wrote: > > > Hmm. Well think of it this way. What happens when the kernel doesn't > > panic but manages to accidentally wipe out your file system without > > warning? or perhaps just loose some of the more important data on the > > HDD? What kind of reaction do you expect then? > > Seeing as we're talking about failures that, most of the time, the user > never sees the results of, users won't say a single thing ... if they're > box *doesn't* panic, they'll be happy. If it panics more often, they'll > notice that, and they won't bother asking why, they'll just switch to > Linux (and quickly). They aren't signing on to be FreeBSD beta-testers, > you know ... at least, believe me, THEY know that. > > On top of all that, the ordinary user won't even bother to report the > fact that your panic happened (or why), while they're removing FreeBSD. Perhaps if a panic printed a small line on how to report the problem that could be considered an improvement, if that could then also be disabled with 'options NO_CONTACT_INFO_ON_PANIC'. 'Please Transcribe this down and email it to bugs@freebsd.org someone will get back to you as soon as possible, don't bother if you are overclocking' :) or perhaps a url to explain what not to report... It actually sounds like a good idea, this isn't NT, FreeBSD shouldn't 'just go boom' I want to see where the hell it did, so i can look at it and contact someone who can look at it. Someone at work asked me what's so awesome about freebsd, I babbled on for about half an hour then i showed him something he didn't belive at first: http://www.freebsd.org/cgi/query-pr.cgi?pr=8732 'dude, yeah i found a bug, they got back to within the hour and fixed it' 'really? how much was the tech support call?' 'oh, i just emailed them.' 'wow.' :) Happy users? Happy core team? yes, it's possible even when you get a panic. thanks, you guys make computers usable. -Alfred > > ----------------------------+----------------------------------------------- > 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 Mar 11 12:32: 6 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 0599F151B7 for ; Thu, 11 Mar 1999 12:31:56 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a34 ([207.164.233.103]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id QAA01177 for ; Thu, 11 Mar 1999 16:46:51 -0500 Message-ID: <005901be6bfd$b05dfc80$2200000a@a34.my.intranet> From: "RT" To: Subject: acd drivers Date: Thu, 11 Mar 1999 15:28:02 -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 I've run into a small snag with the acd drivers. Normal (store bought) CDs appear to function fine. Recordables have some troubles. First off, 50% of the disks mount properly. 50% complain with the error "Invalid Argument" when doing a: 'mount -t cd9660 /dev/acd0a /mnt/cdrom' I can cat /dev/racd0a and receive data, but still not mount those particular disks. As for the 50% that do mount. Only some detect the (I believe it's Joliet) extensions. The rest end up with 8.3 filenames (not that big of a pain). I've got 2 4x4 changers, and 2 32x CD-ROM drives in 2 freebsd machines now (both 4-current updated about 2 days ago). I took them out of a OS/2 Warp 4 box (which could mount / read all CDs properly). Any assistance would be nice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 11 12:47: 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 DAC56151E5 for ; Thu, 11 Mar 1999 12:47:04 -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 UAA31228; Thu, 11 Mar 1999 20:47:48 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 11 Mar 1999 20:47:48 +0000 (GMT) From: Doug Rabson To: Bruce Evans Cc: current@freebsd.org Subject: Re: Proposed change to printf In-Reply-To: <199903111116.WAA12554@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, 11 Mar 1999, Bruce Evans wrote: > >I want to make this change to printf so that it treats format codes like > >'%llx' as 64bit formats (i.e. the same as '%qx'). This convention is the > >same as that used by glibc. > > %llx is actually for unsigned long longs, and %qx is actually for > u_quad_t's. These types are different for FreeBSD on alphas. Printing > quad_t's using %llx should cause warnings from gcc -Wformat on alphas, > but printing them using %qx should work. I think gcc -Wformat doesn't > actually understand %q formats, so printing quad_t's using %qx gives > bogus warnings on alphas. > > However, %llx is more standard. It is in the C9x draft. %qx should go > away. Ok. > > >Index: vfprintf.c > >=================================================================== > >RCS file: /home/ncvs/src/lib/libc/stdio/vfprintf.c,v > >retrieving revision 1.20 > >diff -u -r1.20 vfprintf.c > >--- vfprintf.c 1998/09/16 04:17:44 1.20 > >+++ vfprintf.c 1999/02/20 10:20:08 > >@@ -545,7 +545,10 @@ > > flags |= SHORTINT; > > goto rflag; > > case 'l': > >- flags |= LONGINT; > >+ if (flags & LONGINT) > >+ flags |= QUADINT; > >+ else > >+ flags |= LONGINT; > > goto rflag; > > case 'q': > > flags |= QUADINT; > >@@ -1016,7 +1019,10 @@ > > flags |= SHORTINT; > > goto rflag; > > case 'l': > >- flags |= LONGINT; > >+ if (flags & LONGINT) > >+ flags |= QUADINT; > >+ else > >+ flags |= LONGINT; > > goto rflag; > > case 'q': > > flags |= QUADINT; > > This assumes that long longs have the same representation as quad_t's. > I suppose not doing a global change from quad_t to long long is best, > because the change should actually be to C9x's intmax_t to support C9x's > %m formats. So is the patch correct enough to commit then? -- 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 Thu Mar 11 13: 8:39 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 69FB11513B for ; Thu, 11 Mar 1999 13:08:34 -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 IAA19103; Fri, 12 Mar 1999 08:08:15 +1100 Date: Fri, 12 Mar 1999 08:08:15 +1100 From: Bruce Evans Message-Id: <199903112108.IAA19103@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: Proposed change to printf Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >@@ -1016,7 +1019,10 @@ >> > flags |= SHORTINT; >> > goto rflag; >> > case 'l': >> >- flags |= LONGINT; >> >+ if (flags & LONGINT) >> >+ flags |= QUADINT; >> >+ else >> >+ flags |= LONGINT; >> > goto rflag; >> > case 'q': >> > flags |= QUADINT; >> >> This assumes that long longs have the same representation as quad_t's. >> I suppose not doing a global change from quad_t to long long is best, >> because the change should actually be to C9x's intmax_t to support C9x's >> %m formats. > >So is the patch correct enough to commit then? Yes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 11 14:46: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 2DC7615248 for ; Thu, 11 Mar 1999 14:44:33 -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 WAA31423; Thu, 11 Mar 1999 22:45:23 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 11 Mar 1999 22:45:23 +0000 (GMT) From: Doug Rabson To: Bruce Evans Cc: current@freebsd.org Subject: Re: Proposed change to printf In-Reply-To: <199903112108.IAA19103@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, 12 Mar 1999, Bruce Evans wrote: > >> >@@ -1016,7 +1019,10 @@ > >> > flags |= SHORTINT; > >> > goto rflag; > >> > case 'l': > >> >- flags |= LONGINT; > >> >+ if (flags & LONGINT) > >> >+ flags |= QUADINT; > >> >+ else > >> >+ flags |= LONGINT; > >> > goto rflag; > >> > case 'q': > >> > flags |= QUADINT; > >> > >> This assumes that long longs have the same representation as quad_t's. > >> I suppose not doing a global change from quad_t to long long is best, > >> because the change should actually be to C9x's intmax_t to support C9x's > >> %m formats. > > > >So is the patch correct enough to commit then? > > Yes. Thanks. -- 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 Thu Mar 11 14:52: 2 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 9C9181529C for ; Thu, 11 Mar 1999 14:51:55 -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 WAA31445; Thu, 11 Mar 1999 22:52:26 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 11 Mar 1999 22:52:26 +0000 (GMT) From: Doug Rabson To: Bruce Evans Cc: current@freebsd.org Subject: Re: Proposed change to printf In-Reply-To: <199903112108.IAA19103@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, 12 Mar 1999, Bruce Evans wrote: > >> >@@ -1016,7 +1019,10 @@ > >> > flags |= SHORTINT; > >> > goto rflag; > >> > case 'l': > >> >- flags |= LONGINT; > >> >+ if (flags & LONGINT) > >> >+ flags |= QUADINT; > >> >+ else > >> >+ flags |= LONGINT; > >> > goto rflag; > >> > case 'q': > >> > flags |= QUADINT; > >> > >> This assumes that long longs have the same representation as quad_t's. > >> I suppose not doing a global change from quad_t to long long is best, > >> because the change should actually be to C9x's intmax_t to support C9x's > >> %m formats. > > > >So is the patch correct enough to commit then? > > Yes. Thanks for the review. -- 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 Thu Mar 11 21:19: 5 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 F13FF1519F for ; Thu, 11 Mar 1999 21:18: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 AAA08168 for ; Fri, 12 Mar 1999 00:18:37 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA23068; Fri, 12 Mar 1999 00:18:37 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id AAA84687 for freebsd-current@freebsd.org; Fri, 12 Mar 1999 00:18:36 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199903120518.AAA84687@bb01f39.unx.sas.com> Subject: 4.0-19990311-SNAP bootblock install weirdness To: freebsd-current@freebsd.org Date: Fri, 12 Mar 1999 00:18:36 -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, Just an install report from the field.... I did a new install of 4.0-19990311-SNAP onto a system that was previously running 3.0-19991105-SNAP. The 3.0 system was using the old boot blocks. The 4.0 install was via ftp, and worked without a problem. However, upon rebooting the machine, it would not boot. The 2nd stage boot loader had not been installed. The only way to boot was to type in /boot/loader and it would then boot up. Upon determining this was the problem, I then ran: fdisk -b to rewrite the sector 0 boot code. This had no effect. I then ran: boot0cfg -B this had no effect. Finally, I tried: disklabel -B da0 which also had no effect. I re-installed the 4.0 system from scratch again thinking I must have really messed something up. No effect, still no normal boot. Out of frustration I ran the following: dd if=/dev/zero of=/dev/da0 bs=512 count=2048 to wipe out the front-end of the boot disk. I then re-installed the 4.0 system a 3rd time and it now boots normally. I am unable to explain why this happened, but hope that someone with more experience with the sysinstall/boot code can shed some light on it. An additional item with respect to sysinstall. I select [All] of the distributions to install, which includes compat22. Well, compat22 is not built by the 4.0 system. Looking at the last snap on ftp.freebsd.org (4.0-19990211-SNAP) shows that compat22 is: lrwxrwxrwx 1 2035 207 19 Feb 12 04:09 compat22 -> ../current/compat22 Could someone explain why this isn't built at 4.0, or what is going on with it? (I build my own -SNAP releases daily, and the latest 4.0 builds are looking really stable, at least of uniprocessor systems). Comments, critiques, and helpful hints appreciated! Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 1:26: 8 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 7B05415305 for ; Fri, 12 Mar 1999 01:24:24 -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 BAA06749; Fri, 12 Mar 1999 01:24:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19990311-SNAP bootblock install weirdness In-reply-to: Your message of "Fri, 12 Mar 1999 00:18:36 EST." <199903120518.AAA84687@bb01f39.unx.sas.com> Date: Fri, 12 Mar 1999 01:24:44 -0800 Message-ID: <6747.921230684@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > to wipe out the front-end of the boot disk. I then re-installed > the 4.0 system a 3rd time and it now boots normally. I am unable to > explain why this happened, but hope that someone with more experience > with the sysinstall/boot code can shed some light on it. No, that's just pretty weird. :-) I wonder if the geometry was calculated differently in the two cases, did you manage to compare numbers in the fdisk screen in the before-and-after case? Now that you've zero'd it, it makes analysis of the original condition a little more difficult. :) > lrwxrwxrwx 1 2035 207 19 Feb 12 04:09 compat22 -> ../current/compat22 Yep, if you're mirroring these bits, you need to fetch "through" that link and populate compat22. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 2: 8: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 E08E6152EB for ; Fri, 12 Mar 1999 02:08:28 -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 CAA07106; Fri, 12 Mar 1999 02:08:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs In-reply-to: Your message of "Thu, 11 Mar 1999 08:34:52 PST." <19990311083452.N79145@relay.nuxi.com> Date: Fri, 12 Mar 1999 02:08:50 -0800 Message-ID: <7104.921233330@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been compiling things w/in /usr/src/ , but haven't done a ``make > world'' with EGCS in-place in /usr/src due to the `cpp w/c++'' problem. Where exactly does it die? We should at least make it easily possible to get the build environment configured the way it's "supposed" to look so that others can stumble over the exact same problem and hopefully fix it. I'm going to be away for a few days but will pick this thread up again when I return on wednesday - I'd like to help with this. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 2:26:29 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 443B015305 for ; Fri, 12 Mar 1999 02:26:28 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id CAA88144; Fri, 12 Mar 1999 02:26:08 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Mar 1999 02:26:08 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs Message-ID: <19990312022608.H85451@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990311083452.N79145@relay.nuxi.com> <7104.921233330@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <7104.921233330@zippy.cdrom.com>; from Jordan K. Hubbard on Fri, Mar 12, 1999 at 02:08:50AM -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've been compiling things w/in /usr/src/ , but haven't done a ``make > > world'' with EGCS in-place in /usr/src due to the `cpp w/c++'' problem. > > Where exactly does it die? Lets assume one is not trying to hook EGCS into /usr/src yet. cd /foo/src/gnu/usr.bin/cc make obj make depend make -k make -k install # the above will fail in libgcc since we are not using the freshly # built c++ because we aren't doing this as a ``build world'' which # would do the appropriate bootstrapping. Same issues as the previous # gcc 2.6.x to 2.7.x upgrade. make cleandir make obj make depend make make install cd /foo/src/gnu/usr.bin/lib/libstdc++ make obj make depend CC="cc" CXX="c++" CONFIG_NM="nm" CPP="cc -E -nostdinc -idirafter /usr/include" sh /foo/src/gnu/lib/libstdc++/../../../contrib/egcs/libio/gen-params LIB_VERSION=3.0.0 >_G_config.h c++: Internal compiler error: program cpp got fatal signal 11 gen-params: could not compile dummy.C with c++ *** Error code 1 It is at this point, that I'm coping ``cpp'' from an installed copy of the Egcs port into /usr/libexec so I can keep working on `build world' 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 Fri Mar 12 2:29: 6 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 AB30E14A0B for ; Fri, 12 Mar 1999 02:29:04 -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 CAA22208; Fri, 12 Mar 1999 02:29:27 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs In-reply-to: Your message of "Fri, 12 Mar 1999 02:26:08 PST." <19990312022608.H85451@relay.nuxi.com> Date: Fri, 12 Mar 1999 02:29:27 -0800 Message-ID: <22206.921234567@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /foo/src/gnu/lib/libstdc++/../../../contrib/egcs/libio/gen-params I'd be very curious to see how gen-params is calling c++ and/or cpp in this case. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 3: 2: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 3D66B15360 for ; Fri, 12 Mar 1999 03:02:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id DAA89112; Fri, 12 Mar 1999 03:02:34 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Mar 1999 03:02:34 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs Message-ID: <19990312030234.A88193@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990312022608.H85451@relay.nuxi.com> <22206.921234567@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <22206.921234567@zippy.cdrom.com>; from Jordan K. Hubbard on Fri, Mar 12, 1999 at 02:29:27AM -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 On Fri, Mar 12, 1999 at 02:29:27AM -0800, Jordan K. Hubbard wrote: > > /foo/src/gnu/lib/libstdc++/../../../contrib/egcs/libio/gen-params > > I'd be very curious to see how gen-params is calling c++ and/or cpp in > this case. + c++ -v -O -c dummy.C Using builtin specs. gcc version egcs-2.91.63 19990224 (egcs-1.1.2 pre-release-3) /usr/libexec/cpp -lang-c++ -v -undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus -D__GNUC_MINOR__=91 -Di386 -Dunix -D__ELF__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=300001 -D__i386__ -D__unix__ -D__ELF__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=300001 -D__i386 -D__unix -Asystem(unix) -Asystem(FreeBSD) -Acpu(i386) -Amachine(i386) -D__EXCEPTIONS -D__OPTIMIZE__ -D__ELF__ dummy.C /var/tmp/ccO39xXH.ii GNU CPP version egcs-2.91.63 19990224 (egcs-1.1.2 pre-release-3) (i386 FreeBSD/ELF) c++: Internal compiler error: program cpp got fatal signal 11 + echo gen-params: could not compile dummy.C with c++ -v gen-params: could not compile dummy.C with c++ -v + exit 1 *** Error code 1 gdb on the resulting core file isn't leading me anywhere. If I use a little X-cut-n-paste and run the `cpp' command manually, it works fine and I get the expected output from `cpp'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 5:10: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 5913B153C9 for ; Fri, 12 Mar 1999 05:10:27 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id IAA22683; Fri, 12 Mar 1999 08:10:02 -0500 (EST) Date: Fri, 12 Mar 1999 08:08:59 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "David O'Brien" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs In-Reply-To: <19990312030234.A88193@relay.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, 12 Mar 1999, David O'Brien wrote: > On Fri, Mar 12, 1999 at 02:29:27AM -0800, Jordan K. Hubbard wrote: > > > /foo/src/gnu/lib/libstdc++/../../../contrib/egcs/libio/gen-params > > > > I'd be very curious to see how gen-params is calling c++ and/or cpp in > > this case. > > + c++ -v -O -c dummy.C > Using builtin specs. > gcc version egcs-2.91.63 19990224 (egcs-1.1.2 pre-release-3) > /usr/libexec/cpp -lang-c++ -v -undef -D__GNUC__=2 -D__GNUG__=2 > -D__cplusplus -D__GNUC_MINOR__=91 -Di386 -Dunix -D__ELF__ -D__FreeBSD__=4 > -D__FreeBSD_cc_version=300001 -D__i386__ -D__unix__ -D__ELF__ > -D__FreeBSD__=4 -D__FreeBSD_cc_version=300001 -D__i386 -D__unix > -Asystem(unix) -Asystem(FreeBSD) -Acpu(i386) -Amachine(i386) > -D__EXCEPTIONS -D__OPTIMIZE__ -D__ELF__ dummy.C /var/tmp/ccO39xXH.ii > GNU CPP version egcs-2.91.63 19990224 (egcs-1.1.2 pre-release-3) (i386 > FreeBSD/ELF) > c++: Internal compiler error: program cpp got fatal signal 11 > + echo gen-params: could not compile dummy.C with c++ -v > gen-params: could not compile dummy.C with c++ -v > + exit 1 > *** Error code 1 > > > gdb on the resulting core file isn't leading me anywhere. > If I use a little X-cut-n-paste and run the `cpp' command manually, it > works fine and I get the expected output from `cpp'. Hmm.... environment variables? > > > 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 Fri Mar 12 7:30:42 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 0C285153C3 for ; Fri, 12 Mar 1999 07:29:21 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id KAA07489 for current@freebsd.org; Fri, 12 Mar 1999 10:29:02 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199903121529.KAA07489@misha.cisco.com> Subject: cryptfs and friends To: current@freebsd.org Date: Fri, 12 Mar 1999 10:29:02 -0500 (EST) 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 Can somebody comment on http://www.cs.columbia.edu/~ezk/research/cryptfs/node3.html#SECTION00036000000000000000 and on bringing the other goodies from http://www.cs.columbia.edu/~ezk/research/index.html into -current and, perhaps, -stable? Right now, we only have am-utils... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 9:48:58 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 D8E1114CAC for ; Fri, 12 Mar 1999 09:48:52 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA06088; Fri, 12 Mar 1999 09:44:34 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdMF6081; Fri Mar 12 17:44:30 1999 Date: Fri, 12 Mar 1999 09:44:27 -0800 (PST) From: Julian Elischer To: "Jordan K. Hubbard" Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19990311-SNAP bootblock install weirdness In-Reply-To: <6747.921230684@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 had the same problem.. I had to reinstal the old booteazy off a backup before my system would boot again. I have booteasy on dsk0, and used fdisk -b on dsk1 after installing hte new bootblocks (3stage). It stopped booting and nothing I could do woul dmake it boot till I manufactured a new booteasy block by concattinating the booteasy code from dsk0 and the MBR table from dsk1 (by hand). root is on da1sd1a and it all worked fine (and now again) with the old booteasy code on both disks. ( replace the booteasy code on da1 because there si no choice there and wanted silent bootblock.. julian On Fri, 12 Mar 1999, Jordan K. Hubbard wrote: > > to wipe out the front-end of the boot disk. I then re-installed > > the 4.0 system a 3rd time and it now boots normally. I am unable to > > explain why this happened, but hope that someone with more experience > > with the sysinstall/boot code can shed some light on it. > > No, that's just pretty weird. :-) I wonder if the geometry was > calculated differently in the two cases, did you manage to compare > numbers in the fdisk screen in the before-and-after case? Now that > you've zero'd it, it makes analysis of the original condition a little > more difficult. :) > > > lrwxrwxrwx 1 2035 207 19 Feb 12 04:09 compat22 -> ../current/compat22 > > Yep, if you're mirroring these bits, you need to fetch "through" that > link and populate compat22. > > - Jordan > > > 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 Mar 12 9:50:43 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 BE58C14F95 for ; Fri, 12 Mar 1999 09:50:32 -0800 (PST) (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 SAA09970 for ; Fri, 12 Mar 1999 18:50:13 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id SAA22067 for current@freebsd.org; Fri, 12 Mar 1999 18:50:13 +0100 (MET) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.2/8.8.8) with ESMTP id SAA31884 for ; Fri, 12 Mar 1999 18:49:55 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Fri, 12 Mar 1999 18:49:55 +0100 (CET) From: Michael Reifenberger To: FreeBSD-Current Subject: -current kernel compile and 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 Hi, under -current I get during kernel compile: ... cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DCOMPAT_LINUX_THREADS -DKERNEL -DVM_STACK -include opt_global.h -elf ../../pccard/pcic.c ../../pccard/pcic.c:190: warning: static declaration for `register_pcic_intr' follows non-static ../../pccard/pcic.c:194: warning: static declaration for `unregister_pcic_intr' follows non-static ... loading kernel pccard.o: In function `unregister_device_interrupt': pccard.o(.text+0x31c): undefined reference to `unregister_pcic_intr' pccard.o: In function `pccard_alloc_intr': pccard.o(.text+0x691): undefined reference to `register_pcic_intr' *** Error code 1 Stop. I can't find the reason in pcic.c Anyone else? 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 Mar 12 11: 8: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 9E187154BA for ; Fri, 12 Mar 1999 11:08:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA78534; Fri, 12 Mar 1999 11:08:37 -0800 (PST) (envelope-from dillon) Date: Fri, 12 Mar 1999 11:08:37 -0800 (PST) From: Matthew Dillon Message-Id: <199903121908.LAA78534@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Major VFS/BIO patch has been committed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heads up! 4.x developers / testers. A bunch of bug fixes have been committed, including a big involved one that solves problems related in the getnewbuf() thread by basically rewriting getnewbuf(). At least a half dozen bug fixes by various authors have been committed in recent days covering over a dozen files in the VM system. While these are supposed to be bug fixes, care should be taken when running an updated -current system. Please review the commit logs. Here is an overview: * VFS/BIO fixes getnewbuf() has been fixed to (A) not recurse 5 levels, which can run the supervisor stack out when the system has long VFS call chains, and (B) handle extreme low-memory situations without deadlocking. * VM fixes A read()/mmap()/open() deadlock has been fixed. DG has upped reserved KVM space to 1G, solving large-memory and large-maxusers configuration problems. Note: you must have the latest bootblocks and /boot directory for new kernels to boot properly. * NFS fixes NFS was not properly clearing B_DONE in some cases, leading to process lockups due to code in biodone() which would not wakeup the bp if it was already marked B_DONE. biodone() now (properly) panics if the bp is already marked B_DONE, and the NFS code now properly clears B_DONE prior to initiating a new I/O operation. * CCD fixes An overflow in CCD that disallowing large stripe sizes ( > 2GB ) has been fixed. * MFS fixes An earlier commit that fixes a low-swap/kill problem created a 'syncing filesystems...giving up' problem. This has been fixed. The more trivial bug fixes have been backported to -3.x. The others are under review. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 11:57:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from send101.yahoomail.com (send101.yahoomail.com [205.180.60.87]) by hub.freebsd.org (Postfix) with SMTP id B804A153EC for ; Fri, 12 Mar 1999 11:57:28 -0800 (PST) (envelope-from valsho@yahoo.com) Message-ID: <19990312195615.26156.rocketmail@send101.yahoomail.com> Received: from [147.226.106.179] by send101.yahoomail.com; Fri, 12 Mar 1999 11:56:15 PST Date: Fri, 12 Mar 1999 11:56:15 -0800 (PST) From: Valentin Shopov Subject: pcic.c & {,un}register_pcic_intr declarations 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 w/o device pcic into kernel config (using kldload pcic) still: loading kernel pccard.o: In function `unregister_device_interrupt': pccard.o(.text+0x362): undefined reference to `unregister_pcic_intr' pccard.o: In function `pccard_alloc_intr': pccard.o(.text+0x718): undefined reference to `register_pcic_intr' *** Error code 1 Stop. 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 Fri Mar 12 12:52: 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 E26BB14C35 for ; Fri, 12 Mar 1999 12:51:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id UAA65776; Fri, 12 Mar 1999 20:51:38 GMT 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 NAA21704; Fri, 12 Mar 1999 13:51:53 -0700 (MST) Message-Id: <199903122051.NAA21704@harmony.village.org> To: Valentin Shopov Subject: Re: pcic.c & {,un}register_pcic_intr declarations Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 12 Mar 1999 11:56:15 PST." <19990312195615.26156.rocketmail@send101.yahoomail.com> References: <19990312195615.26156.rocketmail@send101.yahoomail.com> Date: Fri, 12 Mar 1999 13:51:53 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990312195615.26156.rocketmail@send101.yahoomail.com> Valentin Shopov writes: : w/o device pcic into kernel config (using kldload pcic) still: : : loading kernel : pccard.o: In function `unregister_device_interrupt': : pccard.o(.text+0x362): undefined reference to `unregister_pcic_intr' : pccard.o: In function `pccard_alloc_intr': : pccard.o(.text+0x718): undefined reference to `register_pcic_intr' : *** Error code 1 I just committed a fix for this about two or three hours ago. It should be on the cvsup servers by now. I removed the 'static' declarations from these functions in the non-apic case (they were already gone from the apic case). I've not had time to test it heavily, but at least things link now. Give it a spin. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 13:12: 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 6F9FB14E3B for ; Fri, 12 Mar 1999 13:11:54 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA90989; Fri, 12 Mar 1999 13:11:24 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Mar 1999 13:11:24 -0800 From: "David O'Brien" To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs Message-ID: <19990312131124.C90936@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990312030234.A88193@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brian Feldman on Fri, Mar 12, 1999 at 08:08:59AM -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 > Hmm.... environment variables? That is my guess.. but I don't know an easy way to printout the entire environtment a program sees. -- -- 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 Mar 12 13:36: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 3667D14D2C for ; Fri, 12 Mar 1999 13:36:19 -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 VAA36157; Fri, 12 Mar 1999 21:37:17 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 12 Mar 1999 21:37:17 +0000 (GMT) From: Doug Rabson To: "David O'Brien" Cc: Brian Feldman , current@freebsd.org Subject: Re: bmake/contrib framework for egcs In-Reply-To: <19990312131124.C90936@relay.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, 12 Mar 1999, David O'Brien wrote: > > Hmm.... environment variables? > > That is my guess.. but I don't know an easy way to printout the entire > environtment a program sees. How about hacking cpp so that it does 'system("env > /tmp/somefile")' as the first thing. -- 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 Mar 12 14: 8:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from tick.ssec.wisc.edu (tick.ssec.wisc.edu [144.92.108.121]) by hub.freebsd.org (Postfix) with ESMTP id 1550F14CCA for ; Fri, 12 Mar 1999 14:08:22 -0800 (PST) (envelope-from dglo@tick.ssec.wisc.edu) Received: from tick.ssec.wisc.edu (localhost [127.0.0.1]) by tick.ssec.wisc.edu (8.8.7/8.8.7) with ESMTP id QAA18006; Fri, 12 Mar 1999 16:07:54 -0600 (CST) From: Dave Glowacki Message-Id: <199903122207.QAA18006@tick.ssec.wisc.edu> To: Doug Rabson Cc: "David O'Brien" , Brian Feldman , current@freebsd.org Subject: Re: bmake/contrib framework for egcs In-reply-to: Your message of "Fri, 12 Mar 1999 21:37:17 GMT." Date: Fri, 12 Mar 1999 16:07:53 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Fri, 12 Mar 1999, David O'Brien wrote: > > > > Hmm.... environment variables? > > > > That is my guess.. but I don't know an easy way to printout the entire > > environtment a program sees. > > How about hacking cpp so that it does 'system("env > /tmp/somefile")' as > the first thing. I like to move the executable to 'cpp.bin' then create a shell script name 'cpp' that does something like: env > /tmp/cpp-env.$$ exec cpp.bin "$@" You can even have it start 'gdb' from within the script, if you really want to... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 14:22:17 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 4F03214DB1 for ; Fri, 12 Mar 1999 14:22:11 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id WAA00882 for current@freebsd.org; Fri, 12 Mar 1999 22:21:06 GMT (envelope-from nik) Date: Fri, 12 Mar 1999 22:21:06 +0000 From: Nik Clayton To: current@freebsd.org Subject: Move doc. install to /usr/share/doc/en? Message-ID: <19990312222106.K1309@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, Currently, the English versions of the FAQ and Handbook install in to /usr/doc/FAQ and /usr/doc/handbook respectively. The language specific versions install into /usr/doc/{language code}/FAQ and /usr/doc/{language code}/handbook respectively. If no one has any objections, I'd like to change this, and have the English ones install in to /usr/doc/en/* as well. Symlinks could be used so that /usr/doc/FAQ and /usr/doc/handbook point to whichever version is most appropriate for the host it's installed on? Any objections? Would this break anything? 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 Fri Mar 12 14:22:33 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 D0079152C4; Fri, 12 Mar 1999 14:22:11 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id WAA00327; Fri, 12 Mar 1999 22:16:40 GMT (envelope-from nik) Date: Fri, 12 Mar 1999 22:16:40 +0000 From: Nik Clayton To: current@freebsd.org, doc@freebsd.org Subject: "make release" testers wanted for Doc. Proj. Message-ID: <19990312221640.J1309@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, If you're used to running "make release" I'd appreciate you trying the following and letting me know what happens. This is so that I can check that the DocBook version of the Handbook is being installed correctly. After checking out the most recent version of doc-all, please do the following; 1. Install the textproc/docproj port. This is a meta port which pulls in a few others. You do *not* need the TeX installation with this (not including it is the default, so you don't need to do anything out of the ordinary). 2. Make sure /usr/doc/ is up to date (or wherever you store a checked out copy of the doc-all repository). Specifically, the doc/Makefile should contain a LANGSUBDIR variable which *includes* the "en" directory. doc/en/handbook/Makefile should include a DISTRIBUTION variable. If either of these is missing then you're not up to date. 3. Edit doc/Makefile, and change the SUBDIR line from SUBDIR= FAQ handbook to SUBDIR= FAQ 4. Edit the doc.1 target in /usr/src/release/Makefile. Add "DOC_LANG=en" to the "make all distribute" call. 5. Run "make release" as normal. 6. Check that ..../trees/doc/usr/share/doc/handbook/ is populated by HTML files. 7. If you want to generate a plain text version of the Handbook as well, at step 4 above add "FORMATS= html-split txt" to the "make" line too. If that works flawlessly then great, I'm a step closer to the cut-over. If it doesn't, please let me know what went wrong. Thanks, 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 Fri Mar 12 15:16: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 7EE5615020 for ; Fri, 12 Mar 1999 15:16:50 -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 PAA25040; Fri, 12 Mar 1999 15:17:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Nik Clayton Cc: current@FreeBSD.ORG Subject: Re: "make release" testers wanted for Doc. Proj. In-reply-to: Your message of "Fri, 12 Mar 1999 22:16:40 GMT." <19990312221640.J1309@catkin.nothing-going-on.org> Date: Fri, 12 Mar 1999 15:17:10 -0800 Message-ID: <25038.921280630@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. Install the textproc/docproj port. This is a meta port which pulls > in a few others. You do *not* need the TeX installation with this > (not including it is the default, so you don't need to do anything > out of the ordinary). This is done by make release in the chroot area. > 2. Make sure /usr/doc/ is up to date (or wherever you store a This will have no effect on the chroot area - it's checked out by make release. :) > 3. Edit doc/Makefile, and change the SUBDIR line from Ditto. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 15:42: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles321.castles.com [208.214.167.21]) by hub.freebsd.org (Postfix) with ESMTP id D086E14D56 for ; Fri, 12 Mar 1999 15:42:03 -0800 (PST) (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 PAA01552; Fri, 12 Mar 1999 15:36:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903122336.PAA01552@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Valentin Shopov Cc: current@freebsd.org Subject: Re: pcic.c & {,un}register_pcic_intr declarations In-reply-to: Your message of "Fri, 12 Mar 1999 11:56:15 PST." <19990312195615.26156.rocketmail@send101.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Mar 1999 15:36:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The only configuration which currently works correctly is to remove the kldload of the pcic module from /etc/rc.pccard and compile everything else statically into the kernel. Every other variation is *broken*. > w/o device pcic into kernel config (using kldload pcic) still: > > loading kernel > pccard.o: In function `unregister_device_interrupt': > pccard.o(.text+0x362): undefined reference to `unregister_pcic_intr' > pccard.o: In function `pccard_alloc_intr': > pccard.o(.text+0x718): undefined reference to `register_pcic_intr' > *** Error code 1 > > Stop. > > > > 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 > -- \\ 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 Mar 12 17: 7:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m1-30-dbn.dial-up.net [196.34.155.30]) by hub.freebsd.org (Postfix) with ESMTP id 3E3DE15413 for ; Fri, 12 Mar 1999 17:07:27 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id DAA00868; Sat, 13 Mar 1999 03:05:01 +0200 (SAT) From: Robert Nordier Message-Id: <199903130105.DAA00868@ceia.nordier.com> Subject: Re: 4.0-19990311-SNAP bootblock install weirdness In-Reply-To: from Julian Elischer at "Mar 12, 99 09:44:27 am" To: julian@whistle.com (Julian Elischer) Date: Sat, 13 Mar 1999 03:04:59 +0200 (SAT) Cc: jkh@zippy.cdrom.com, jwd@unx.sas.com, 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 Julian Elischer wrote: > I had the same problem.. I had to reinstal the old booteazy off a backup > before my system would boot again. > > I have booteasy on dsk0, and used fdisk -b on dsk1 after installing hte > new bootblocks (3stage). It stopped booting and nothing I could do woul > dmake it boot till I manufactured a new booteasy block by concattinating > the booteasy code from dsk0 and the MBR table from dsk1 (by hand). > > root is on da1sd1a and it all worked fine (and now again) with the old > booteasy code on both disks. ( replace the booteasy code on da1 because > there si no choice there and wanted silent bootblock.. If anyone else runs into the same problem, it would probably be a help if they could save the output from the following script before proceeding: #!/bin/sh DRIVE=da0 SLICE=s1 fdisk ${DRIVE} disklabel ${DRIVE} dd if=/dev/r${DRIVE} count=1 dd if=/dev/r${DRIVE}${SLICE} count=17 However, the problem in Julian's case is most likely that fdisk -b writes a completely standard MBR which effectively assumes that the drive being booted from is BIOS drive 0x80 (drive 0). You have to have a boot manager (or some kind of non-standard MBR) on higher-numbered drives in order to boot from them. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 12 23:20:41 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 665DE14C24 for ; Fri, 12 Mar 1999 23:20:33 -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 JAA13065; Sat, 13 Mar 1999 09:19: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 JAA20951; Sat, 13 Mar 1999 09:19:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903130719.JAA20951@greenpeace.grondar.za> To: Mike Smith Cc: Valentin Shopov , current@freebsd.org Subject: Re: pcic.c & {,un}register_pcic_intr declarations In-Reply-To: Your message of " Fri, 12 Mar 1999 15:36:25 PST." <199903122336.PAA01552@dingo.cdrom.com> References: <199903122336.PAA01552@dingo.cdrom.com> Date: Sat, 13 Mar 1999 09:19:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > The only configuration which currently works correctly is to remove the > kldload of the pcic module from /etc/rc.pccard and compile everything > else statically into the kernel. > > Every other variation is *broken*. Nope. I am kldloading pcic on my Libretto with no problems at all. I have no private hacks on that machine _at_all_. The only brokenness is when users compile pcic into the kernel, and rc.pccard kldloads pcic (Which is my stuffup). Two solutions; 1) don't compile pcic into your kernel; 2) remove the kldload pcic from rc.pccard; 3) fix kldload to not load modules when their functionality is already compiled in (_Three_ Solutions!!). 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 Mar 12 23:28:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles218.castles.com [208.214.165.218]) by hub.freebsd.org (Postfix) with ESMTP id 232E314D60 for ; Fri, 12 Mar 1999 23:28:13 -0800 (PST) (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 XAA00672; Fri, 12 Mar 1999 23:21:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903130721.XAA00672@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray Cc: Mike Smith , Valentin Shopov , current@freebsd.org Subject: Re: pcic.c & {,un}register_pcic_intr declarations In-reply-to: Your message of "Sat, 13 Mar 1999 09:19:56 +0200." <199903130719.JAA20951@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Mar 1999 23:21:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > The only configuration which currently works correctly is to remove the > > kldload of the pcic module from /etc/rc.pccard and compile everything > > else statically into the kernel. > > > > Every other variation is *broken*. > > Nope. I am kldloading pcic on my Libretto with no problems at all. > I have no private hacks on that machine _at_all_. The only brokenness > is when users compile pcic into the kernel, and rc.pccard kldloads > pcic (Which is my stuffup). Unfortunately, no, that's not correct. The pcic module contains a reference to a symbol that's only present in the kernel when the card* devices are statically compiled in. Ie. if you remove pcic* and card* you can't load the pcic module. This makes the pcic module useless, and, as I said, renders any combination other than 100% static *broken*. > Two solutions; 1) don't compile pcic into your kernel; 2) remove the > kldload pcic from rc.pccard; 3) fix kldload to not load modules when > their functionality is already compiled in (_Three_ Solutions!!). 1) is a non-solutuion. 3) is where the correct answer lies, but until the file/module dichotomy is resolved, it's not possible to 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 Fri Mar 12 23:39:14 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 9F4AF156F6 for ; Fri, 12 Mar 1999 23:39:06 -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 JAA13106; Sat, 13 Mar 1999 09:38: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 JAA21046; Sat, 13 Mar 1999 09:38:45 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903130738.JAA21046@greenpeace.grondar.za> To: Mike Smith Cc: Valentin Shopov , current@freebsd.org Subject: Re: pcic.c & {,un}register_pcic_intr declarations In-Reply-To: Your message of " Fri, 12 Mar 1999 23:21:58 PST." <199903130721.XAA00672@dingo.cdrom.com> References: <199903130721.XAA00672@dingo.cdrom.com> Date: Sat, 13 Mar 1999 09:38:43 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Mike Smith wrote: > > > > > > The only configuration which currently works correctly is to remove the > > > kldload of the pcic module from /etc/rc.pccard and compile everything > > > else statically into the kernel. > > > > > > Every other variation is *broken*. > > > > Nope. I am kldloading pcic on my Libretto with no problems at all. > > I have no private hacks on that machine _at_all_. The only brokenness > > is when users compile pcic into the kernel, and rc.pccard kldloads > > pcic (Which is my stuffup). > > Unfortunately, no, that's not correct. > > The pcic module contains a reference to a symbol that's only present in > the kernel when the card* devices are statically compiled in. Ie. if > you remove pcic* and card* you can't load the pcic module. I have card* compiled in (perhaps I should have mentioned that?), and pcic* kldloaded. > This makes the pcic module useless, and, as I said, renders any > combination other than 100% static *broken*. Rubbish! Why is my system working? > > Two solutions; 1) don't compile pcic into your kernel; 2) remove the > > kldload pcic from rc.pccard; 3) fix kldload to not load modules when > > their functionality is already compiled in (_Three_ Solutions!!). > > 1) is a non-solutuion. 3) is where the correct answer lies, but until > the file/module dichotomy is resolved, it's not possible to do that. 1) works (and needs tidying up). Any suggestions for a kernel neophyte on how to get stuck into 3)? 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 Mar 12 23:51:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles218.castles.com [208.214.165.218]) by hub.freebsd.org (Postfix) with ESMTP id 3EBD114E8D for ; Fri, 12 Mar 1999 23:51:37 -0800 (PST) (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 XAA00785; Fri, 12 Mar 1999 23:45:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903130745.XAA00785@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray Cc: Mike Smith , Valentin Shopov , current@freebsd.org Subject: Re: pcic.c & {,un}register_pcic_intr declarations In-reply-to: Your message of "Sat, 13 Mar 1999 09:38:43 +0200." <199903130738.JAA21046@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Mar 1999 23:45:19 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The pcic module contains a reference to a symbol that's only present in > > the kernel when the card* devices are statically compiled in. Ie. if > > you remove pcic* and card* you can't load the pcic module. > > I have card* compiled in (perhaps I should have mentioned that?), and > pcic* kldloaded. > > > This makes the pcic module useless, and, as I said, renders any > > combination other than 100% static *broken*. > > Rubbish! Why is my system working? Because you have an horrific mishmash of bits; it's not meant to be broken up as you have. > > > Two solutions; 1) don't compile pcic into your kernel; 2) remove the > > > kldload pcic from rc.pccard; 3) fix kldload to not load modules when > > > their functionality is already compiled in (_Three_ Solutions!!). > > > > 1) is a non-solutuion. 3) is where the correct answer lies, but until > > the file/module dichotomy is resolved, it's not possible to do that. > > 1) works (and needs tidying up). > > Any suggestions for a kernel neophyte on how to get stuck into 3)? Not really; you'd need to study how KLD currently works, then go back over the discussions that Peter, Doug, I and others have had about how we might identify modules within a file, and implement it. I fear that it will result in binary incompatability (again). -- \\ 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 Mar 13 2:21:40 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 9D03614BDA for ; Sat, 13 Mar 1999 02:21:29 -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 MAA13346; Sat, 13 Mar 1999 12:21: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 MAA25837; Sat, 13 Mar 1999 12:21:06 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903131021.MAA25837@greenpeace.grondar.za> To: Mike Smith Cc: Valentin Shopov , current@freebsd.org Subject: Re: pcic.c & {,un}register_pcic_intr declarations In-Reply-To: Your message of " Fri, 12 Mar 1999 23:45:19 PST." <199903130745.XAA00785@dingo.cdrom.com> References: <199903130745.XAA00785@dingo.cdrom.com> Date: Sat, 13 Mar 1999 12:21:05 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I have card* compiled in (perhaps I should have mentioned that?), and > > pcic* kldloaded. > > > > > This makes the pcic module useless, and, as I said, renders any > > > combination other than 100% static *broken*. > > > > Rubbish! Why is my system working? > > Because you have an horrific mishmash of bits; it's not meant to be > broken up as you have. If that is the case, then the documentation and people's ideas differ dramatically from reality. As I said, I have a nicely working Libretto here. The configs could be tidier, and more of the kernel could be KLD, but it works almost as well as PAO did 7 months ago, and this is -CURRENT :-). > > Any suggestions for a kernel neophyte on how to get stuck into 3)? > > Not really; you'd need to study how KLD currently works, then go back > over the discussions that Peter, Doug, I and others have had about how > we might identify modules within a file, and implement it. I fear that > it will result in binary incompatability (again). Fooey :-(. Smells like a kernel registry-of-loaded-bits is needed? 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 Mar 13 5: 0:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (Postfix) with ESMTP id 6708714DB5 for ; Sat, 13 Mar 1999 05:00:51 -0800 (PST) (envelope-from root@ice.cold.org) Received: (from root@localhost) by ice.cold.org (8.8.8/8.8.5) id GAA26447; Sat, 13 Mar 1999 06:00:32 -0700 (MST) Date: Sat, 13 Mar 1999 06:00:32 -0700 (MST) Message-Id: <199903131300.GAA26447@ice.cold.org> Subject: ERRATA NOTICE: FreeBSD 3.1-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.1-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/3.1-RELEASE/ERRATA.TXT The last update was sent: Mon Feb 15 17:42:32 1999 This update is sent: Sat Mar 13 06:00:32 1999 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: o Kernel change information is not saved in the new kernel, even though this is claimed to work in the docs. Fix: The change information is being written out, in fact, but to the wrong location. move /kernel.config to /boot/kernel.conf (if it exists, otherwise there were no changes to save) and add the following lines to /boot/loader.rc: load /kernel load -t userconfig_script /boot/kernel.conf autoboot 5 This will cause the kernel change information to be read in and used properly (and you just learned a little about the new 3-stage loader in the process, so the exercise wasn't a total loss). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 13 6:22:14 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 50C2914C0F for ; Sat, 13 Mar 1999 06:22:03 -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 JAA00370; Sat, 13 Mar 1999 09:20:26 -0500 (EST) Date: Sat, 13 Mar 1999 09:20:26 -0500 (EST) From: Chuck Robey To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff In-Reply-To: <36E5EB27.2E44F17D@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 Wed, 10 Mar 1999, Daniel C. Sobral wrote: > A new loader.rc mechanism has been introduced. Nothing has changed > with loader, mind you, and you can continue to use your current > loader.rc (if any) unchanged, but Jordan thinks it might be better > to install a loader.rc using the new mechanism by default, to keep > support easy, so things might change in the future... > > Meanwhile, the new loader.rc stuff, for those who want it. It is > modeled after rc.conf files. We now have a > /boot/defaults/loader.conf, with all defaults (meaning it hardly > does anything, serving more as a template), which will also load > /boot/loader.conf and /boot/loader.conf.local, in that order, if > present. > > The idea is to leave /boot/loader.conf for sysinstall, > /boot/loader.conf.local for the user, and /boot/defaults/loader.conf > to installworld. Daniel, I'm having a little trouble getting this to work. I don't see any kind of example loader.conf, or loader.conf.local, I made the file you asked, below (/boot/loader.rc) ... I didn't have a loader.conf, so on boot, it issues me an error on that. I have a new pnp sound card I have working manually, by donig a boot -c, and issuing the command pnp 1 0 os enable port0 0x534 port2 0x220 irq0 15 drq0 1 drq1 0 This very helpfully shows up in my dmesg, and I get sound, but I want to have this done automatically on boot (no boot -c). My kernel already is correct, so I stuck that line into the otherwise empty loader.conf.local, but it told me that I had a syntax error (on encountering the first "1") and didn't get the configuration done. I checked very carefully, the loader.conf.local does have that exact pnp line I showed. It would help me if you had an example loader.conf and loader.conf.local file hanging around ... and maybe an ls -lR /boot, so I'd know I had a complete set of files. Thanks. > > To use this, put the following lines in your /boot/loader.rc: > > include /boot/loader.4th > start > > Then you can create a /boot/loader.conf.local with whatever other > stuff you'd like, such as using a splash screen. > > Feedback, comments, musings and flames are welcome. (I'd > particularly like a better name than "start" :) > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "FreeBSD is Yoda, Linux is Luke Skywalker." > > > > 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 Mar 13 13:34:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kar.net (n186.cdialup.kar.net [195.178.130.186]) by hub.freebsd.org (Postfix) with ESMTP id 0AECA14D69 for ; Sat, 13 Mar 1999 13:34:36 -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 XAA07659; Sat, 13 Mar 1999 23:33:24 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Sat, 13 Mar 1999 23:33:23 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: "David O'Brien" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs In-Reply-To: <19990311083452.N79145@relay.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1769575940-921360803=:6938" 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-1769575940-921360803=:6938 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, here's where cpp died. There's a small error in freebsd.h: INCLUDE_DEFAULTS array defined in a wrong way (patch attached). Now cpp doesn't die anymore. There's an another problem, though. For somereason libgcc doesn't want to compile with base c++ (conflict in "new", it seems). It does compile if COMPILER_PATH is set to uitilize a newly compiled c++ and cc1plus, but it takes addition CFLAGS+= -I${GCCDIR}/cp/inc to gnu/usr.bin/cc/Makefile.inc. Then everything builds indeed. BTW, binaries compiled with egcc are still larger than with stock gcc. Is there a way to shrink them (beyond what's possible with -O optimisation)? On Thu, 11 Mar 1999, David O'Brien wrote: > > How's this going? > > Everything now builds, and I can pass the C++ STL tests supplied with > EGCS. > > There is at least one case w/in gnu/usr.bin/cc that ``make cleandir && > make cleandir && make obj && make depend && make && make clean && make'' > will file to build. But I haven't worried too much about that yet. > > The biggest problem is that ``cpp'' will get a sig11 when executed by > c++. If I use ``c++ -v'' and manually execute what c++ is, I don't get > the sig11. I got tired of trying to track this down, so to get around > this (so I could work on libstdc++), I copy ``cpp'' into /usr/libexec > from a copy of an installed EGCS port. > > The version in my repository is EGCS 1.1.2-pre3. Rumors have it that > 1.1.2 will released on Friday, and by Monday at the latest. Regards, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | --0-1769575940-921360803=:6938 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="freebsd.h.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="freebsd.h.diff" KioqIGZyZWVic2QuaC5vcmlnCVNhdCBNYXIgMTMgMjM6MjA6MjcgMTk5OQ0K LS0tIGZyZWVic2QuaAlXZWQgTWFyIDEwIDIzOjIyOjMyIDE5OTkNCioqKioq KioqKioqKioqKg0KKioqIDI1OSwyNjcgKioqKg0KICAjaWZkZWYgRlJFRUJT RF9OQVRJVkUNCiAgDQogICNkZWZpbmUgSU5DTFVERV9ERUZBVUxUUyB7IFwN CiEgCXsgIi91c3IvaW5jbHVkZSIsIDAsIDAgfSwgXA0KISAJeyAiL3Vzci9p bmNsdWRlL2crKyIsIDEsIDEgfSwgXA0KISAJeyAwLCAwLCAwfSBcDQogIAl9 DQogIA0KICAjdW5kZWYgTURfRVhFQ19QUkVGSVgNCi0tLSAyNTksMjY3IC0t LS0NCiAgI2lmZGVmIEZSRUVCU0RfTkFUSVZFDQogIA0KICAjZGVmaW5lIElO Q0xVREVfREVGQVVMVFMgeyBcDQohIAl7ICIvdXNyL2luY2x1ZGUiLCAwLCAw LCAwIH0sIFwNCiEgCXsgIi91c3IvaW5jbHVkZS9nKysiLCAiRysrIiwgMSwg MSB9LCBcDQohIAl7IDAsIDAsIDAsIDB9IFwNCiAgCX0NCiAgDQogICN1bmRl ZiBNRF9FWEVDX1BSRUZJWA0K --0-1769575940-921360803=:6938-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 13 14: 8:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-20.ppp.wenet.net [206.15.85.20]) by hub.freebsd.org (Postfix) with ESMTP id A133614BFF for ; Sat, 13 Mar 1999 14:08:54 -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 OAA80750; Sat, 13 Mar 1999 14:07:27 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 13 Mar 1999 14:07:27 -0800 (PST) From: Alex Zepeda To: Vladimir Kushnir Cc: "David O'Brien" , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs 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, 13 Mar 1999, Vladimir Kushnir wrote: > BTW, binaries compiled with egcc are still larger than with stock gcc. Is > there a way to shrink them (beyond what's possible with -O optimisation)? Try -Os, -fno-exceptions* -fno-rtti* or any combo of the above. * Don't do this with libraries, just in case you've got any programs that use exceptions or rtti. Obviously this won't work with programs that use rtti and/or exceptions. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 13 14:47:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kar.net (n186.cdialup.kar.net [195.178.130.186]) by hub.freebsd.org (Postfix) with ESMTP id 9A3D21543F for ; Sat, 13 Mar 1999 14:45:35 -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 AAA18386; Sun, 14 Mar 1999 00:40:09 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Sun, 14 Mar 1999 00:39:15 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: Alex Zepeda Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs 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 Thanks, I'll try, but what I mean is egcs compiled binaries are bigger even for C, not C++, and as if memory serves -Os is -O2 subset. So probably I'll just have to accept this increase in binaries size :-(. Ah well, it ain't all that much, anyway. Oh, incidentally, I forgot to add that (when compiling libstdc++ with new c++ for the first time, it can't find file exception. So perhaps in gnu/lib/libstdc++/Makefile this part of CFLAGS shoild be -I${EGCSDIR}/gcc/cp/inc rather than -I${EGCSDIR}/gcc/cp/inc/exception (after all, ${EGCSDIR}/gcc/cp/inc/exception is a file). On Sat, 13 Mar 1999, Alex Zepeda wrote: > On Sat, 13 Mar 1999, Vladimir Kushnir wrote: > > > BTW, binaries compiled with egcc are still larger than with stock gcc. Is > > there a way to shrink them (beyond what's possible with -O optimisation)? > > Try -Os, -fno-exceptions* -fno-rtti* or any combo of the above. > > * Don't do this with libraries, just in case you've got any programs that > use exceptions or rtti. Obviously this won't work with programs that use > rtti and/or exceptions. > > - alex > 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 Sat Mar 13 15: 9:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-6.ppp.wenet.net [206.15.85.6]) by hub.freebsd.org (Postfix) with ESMTP id 6FB5214F4D for ; Sat, 13 Mar 1999 15:08:40 -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 PAA80943; Sat, 13 Mar 1999 15:07:29 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 13 Mar 1999 15:07:29 -0800 (PST) From: Alex Zepeda To: Vladimir Kushnir Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs 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, 14 Mar 1999, Vladimir Kushnir wrote: > Thanks, I'll try, but what I mean is egcs compiled binaries are bigger > even for C, not C++, and as if memory serves -Os is -O2 subset. So > probably I'll just have to accept this increase in binaries size :-(. Ah > well, it ain't all that much, anyway. -Os is a subset of -O2, which enables everything that won't increase the size of a binary. However, I don't know about rtti, but IIRC exception handling code (or perhaps stubs thereof) are included even in C code, just incase. Perhaps jdp can shed some more light on this (he's been a very useful resource to me in the past). > Oh, incidentally, I forgot to add that (when compiling libstdc++ with new > c++ for the first time, it can't find file exception. So perhaps in > gnu/lib/libstdc++/Makefile this part of CFLAGS shoild be > -I${EGCSDIR}/gcc/cp/inc rather than -I${EGCSDIR}/gcc/cp/inc/exception > (after all, ${EGCSDIR}/gcc/cp/inc/exception is a file). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 13 16:33:33 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 CE69214EE2 for ; Sat, 13 Mar 1999 16:33:29 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id JAA27045; Sun, 14 Mar 1999 09:33:14 +0900 (JST) Message-ID: <36EB037C.B0D9C7BC@newsguy.com> Date: Sun, 14 Mar 1999 09:31:56 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Chuck Robey Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff 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 Chuck Robey wrote: > > Daniel, I'm having a little trouble getting this to work. I don't see > any kind of example loader.conf, or loader.conf.local, I made the file > you asked, below (/boot/loader.rc) ... I didn't have a loader.conf, so > on boot, it issues me an error on that. I have a new pnp sound card I ... > It would help me if you had an example loader.conf and loader.conf.local > file hanging around ... and maybe an ls -lR /boot, so I'd know I had a > complete set of files. Well, first, this has been introduced only on -current at the present time. I am in no hurry to mfc, because this thing has just been introduced. I want the freedom to make drastic changes, and I'll loose that once it gets on the stable three. If you are running -stable, you'll be able to use it if you import -current's sys/boot and sys/sys/linker.h, cd /sys/boot ; make depend && make all install. OTOH, you might solve your problem just by adding the following two lines to /boot/loader.rc load kernel load -t userconfig_script /kernel.config and then putting your pnp configuration line on /kernel.config (if it is not there already). This will work on both current and stable, so I think I ought to mention it. :-) Now, back to the loader.rc stuff, in case you _are_ running -current... it should have installed the following files: /boot/loader.4th /boot/support.4th /boot/defaults/loader.conf The last file is all you really need as example. A man page is in the works. It is queued right after the loader man page, which has been a real drag to write, but I think I might be committing it today. But the loader.conf man page won't really add anything for you that is not in /boot/defaults/loader.conf. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "My theory is that his ignorance clouded his poor judgment." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 13 17:41: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 8F58214F3C for ; Sat, 13 Mar 1999 17:41: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 UAA16382; Sat, 13 Mar 1999 20:39:40 -0500 (EST) Date: Sat, 13 Mar 1999 20:39:39 -0500 (EST) From: Chuck Robey To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff In-Reply-To: <36EB037C.B0D9C7BC@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, 14 Mar 1999, Daniel C. Sobral wrote: > If you are running -stable This is the -current list, and I'm running current. I don't have the file "userconfig_script" nor /kernel.config. , you'll be able to use it if you import > -current's sys/boot and sys/sys/linker.h, cd /sys/boot ; make depend > && make all install. > > OTOH, you might solve your problem just by adding the following two > lines to /boot/loader.rc > > load kernel > load -t userconfig_script /kernel.config > > and then putting your pnp configuration line on /kernel.config (if > it is not there already). This is good info for current, right? And I don't need to worry about "userconfig_script"? What's load -t do (I don't need a man page, but at least a few words on the -t, please). The pnp line will be the only thing in /kernel.config, that's normal? > > This will work on both current and stable, so I think I ought to > mention it. :-) I am not running stable, it doesn't track all the new config stuff, but I have all the files listed below, it seems. > > Now, back to the loader.rc stuff, in case you _are_ running > -current... it should have installed the following files: > > /boot/loader.4th > /boot/support.4th > /boot/defaults/loader.conf > > The last file is all you really need as example. I was asking about where to stick in the pnp line, and an example of that. I guess it's not loader.conf (I just tested that, it didn't work there). I'm a little leery yet of the load -t because I don't have that userconfig_script file, and I don't know what the load -t does. > > A man page is in the works. It is queued right after the loader man > page, which has been a real drag to write, but I think I might be > committing it today. But the loader.conf man page won't really add > anything for you that is not in /boot/defaults/loader.conf. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "My theory is that his ignorance clouded his poor judgment." > > ----------------------------+----------------------------------------------- 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 Mar 13 18:23:24 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 1683014F69 for ; Sat, 13 Mar 1999 18:23:21 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 5F12618C2; Sun, 14 Mar 1999 03:23:14 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 5836849CB; Sun, 14 Mar 1999 03:23:14 +0100 (CET) Date: Sun, 14 Mar 1999 03:23:14 +0100 (CET) From: Andrzej Bialecki To: Chuck Robey Cc: "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc 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 Sat, 13 Mar 1999, Chuck Robey wrote: > > load kernel > > load -t userconfig_script /kernel.config > > > > and then putting your pnp configuration line on /kernel.config (if > > it is not there already). > > This is good info for current, right? And I don't need to worry about > "userconfig_script"? What's load -t do (I don't need a man page, but at > least a few words on the -t, please). '-t' does basically two things. First of all, it selects right loading procedure, e.g. just suck it in instead of interpreting it as an ELF binary. The other thing is that it attaches a magic label to this piece of code, so that later from within the kernel you can do preload_search_by_type("my_lovely_magic_string") and it will return a pointer to the right data, be it an executable code or a text or a graphics image. > > The pnp line will be the only thing in /kernel.config, that's normal? Yes. Since you're running -current, you should be able to use kget(8) as a dset replacement to generate /kernel.config for you, based on the changes in UserConfig. 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 Mar 13 18:23: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 437C014E2F for ; Sat, 13 Mar 1999 18:23:45 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA07987; Sat, 13 Mar 1999 18:06:15 -0800 (PST) (envelope-from obrien) Date: Sat, 13 Mar 1999 18:06:15 -0800 From: "David O'Brien" To: Vladimir Kushnir Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs Message-ID: <19990313180615.A7861@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990311083452.N79145@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Vladimir Kushnir on Sat, Mar 13, 1999 at 11:33:23PM +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 Sat, Mar 13, 1999 at 11:33:23PM +0200, Vladimir Kushnir wrote: > Hello, here's where cpp died. There's a small error in freebsd.h: ^^^^^^^^^ freebsd-elf.h > INCLUDE_DEFAULTS array defined in a wrong way (patch attached). Now cpp Crud! I had freebsd.h right, but didn't get the changes to "INCLUDE_DEFAULTS" into freebsd-elf.h. Thanks! -- -- 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 Mar 13 18:37:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from carbon.marathon.org (carbon.marathon.org [209.180.116.41]) by hub.freebsd.org (Postfix) with ESMTP id 0E17814F66; Sat, 13 Mar 1999 18:37:00 -0800 (PST) (envelope-from nje@carbon.marathon.org) Received: from localhost (nje@localhost) by carbon.marathon.org (8.9.2/8.9.2) with ESMTP id TAA49856; Sat, 13 Mar 1999 19:36:41 -0700 (MST) (envelope-from nje@carbon.marathon.org) Date: Sat, 13 Mar 1999 19:36:40 -0700 (MST) From: Nicholas Esborn To: current@FreeBSD.org, stable@FreeBSD.org Subject: Diskless boot stopping at "NFS ROOT:..." Message-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 a problem I have had on two seperate systems, running 3.0-RELEASE and now 3.1-STABLE built about a week ago. The systems were brought up seperately. Unfortunately since this machine never comes up to any usable state, I don't have detailed logs of its boot output. I'll try to summarize: I compiled the 3.1-S kernel with KERNFORMAT=aout and placed it in /usr/local/netboot/fs/, my NFS rootfs. The following dirs were cpio'd from the host system: drwxr-xr-x 2 root wheel 512 Mar 13 17:51 bin drwxr-xr-x 2 root wheel 1024 Mar 13 17:52 lkm drwxr-xr-x 2 root wheel 1536 Mar 13 17:52 sbin drwxr-xr-x 4 root wheel 512 Mar 13 17:52 stand I made usr and cpio'd the following dirs into it: drwxr-xr-x 2 root wheel 6144 Mar 13 18:03 bin drwxr-xr-x 3 root wheel 512 Mar 13 18:03 compat drwxr-xr-x 4 root wheel 3584 Mar 13 18:05 lib drwxr-xr-x 9 root wheel 512 Mar 13 18:05 libdata drwxr-xr-x 7 root wheel 1024 Mar 13 18:07 libexec drwxr-xr-x 2 root wheel 3584 Mar 13 18:07 sbin drwxr-xr-x 26 root wheel 512 Mar 13 18:15 share I made etc and copied ttys into it. I made the following rc: #!/bin/sh echo 'STARTING UP' PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin export PATH ifconfig lo0 inet 127.0.0.1 netmask 0xffffffff mount -t nfs -u 10.0.0.1:/export/boot/fs / mount -a /sbin/ldconfig -elf /usr/lib /usr/lib/compat /usr/X11R6/lib while [ 1 -eq 1 ]; do /usr/X11R6/bin/XF86_S3 -bpp 16 -query deimos done The mounting stuff may be problematic, but it doesn't look like rc is even running... The clients find the kernel and start booting, goes through its bootpc configuration obtaining all the right numbers, prints: NFS ROOT: 10.0.0.1:/usr/local/netboot/fs and stops. I have to hard power cycle the client. The kernel is GENERIC with BOOTP, BOOTP_NFSROOT, "BOOTP_NFSV3", and BOOTP_COMPAT. I can't tell if the nfs flags are getting set in the kernel, as the machine never comes up to a shell. Here's the irony: I can currently get 2.2.x booting through almost the same procedures and setups (only differing where 2.2.x and 3.x features differ). Any ideas? Thank you for your time either way. Please respond to me by email as I'm not on the mailing lists. Nick Esborn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 13 18:39: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 C340414E30 for ; Sat, 13 Mar 1999 18:39:39 -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 VAA16489; Sat, 13 Mar 1999 21:37:47 -0500 (EST) Date: Sat, 13 Mar 1999 21:37:47 -0500 (EST) From: Chuck Robey To: Andrzej Bialecki Cc: "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc 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 Sun, 14 Mar 1999, Andrzej Bialecki wrote: > On Sat, 13 Mar 1999, Chuck Robey wrote: > > > > load kernel > > > load -t userconfig_script /kernel.config > > > > > > and then putting your pnp configuration line on /kernel.config (if > > > it is not there already). > > > > This is good info for current, right? And I don't need to worry about > > "userconfig_script"? What's load -t do (I don't need a man page, but at > > least a few words on the -t, please). > > '-t' does basically two things. First of all, it selects right loading > procedure, e.g. just suck it in instead of interpreting it as an ELF > binary. The other thing is that it attaches a magic label to this piece of > code, so that later from within the kernel you can do > preload_search_by_type("my_lovely_magic_string") and it will return a > pointer to the right data, be it an executable code or a text or a > graphics image. > > > > > The pnp line will be the only thing in /kernel.config, that's normal? > > Yes. Since you're running -current, you should be able to use kget(8) as a > dset replacement to generate /kernel.config for you, based on the changes > in UserConfig. Wonderful, between you, Don Maddox and Dan Sobral, you guys have explained that pretty darned well. Glad it's in the mail archives now. My new $30 sound card is also surprising heck out of me by sounding fine, too. I'll stick info on that in snd/CARDS when I'm finished getting more info on it. This stuff oughta be somewhere, soonest. If it's not man page, at least a temporary distillation of it in a file in sys/boot, to be tossed once there's a man page. ----------------------------+----------------------------------------------- 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 Mar 13 20: 4: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 988B914DFB for ; Sat, 13 Mar 1999 20:04:33 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id UAA08502; Sat, 13 Mar 1999 20:02:55 -0800 (PST) (envelope-from obrien) Date: Sat, 13 Mar 1999 20:02:55 -0800 From: "David O'Brien" To: Vladimir Kushnir Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs Message-ID: <19990313200255.C8213@relay.nuxi.com> Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Vladimir Kushnir on Sun, Mar 14, 1999 at 12:39:15AM +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 > gnu/lib/libstdc++/Makefile this part of CFLAGS shoild be > -I${EGCSDIR}/gcc/cp/inc rather than -I${EGCSDIR}/gcc/cp/inc/exception > (after all, ${EGCSDIR}/gcc/cp/inc/exception is a file). Yes. What I was working on is newer than the CVS repository. I'm chasing several issues & moving things around. I haven't been keeping the CVSup'able totally bits upto date in the past few days. Tonight or Sunday, I hope to have the same thing I'm working on available to all. -- -- 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 Mar 13 20: 8:14 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 072661553D for ; Sat, 13 Mar 1999 20:08:12 -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 UAA06069; Sat, 13 Mar 1999 20:08:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Chuck Robey Cc: Andrzej Bialecki , "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff In-reply-to: Your message of "Sat, 13 Mar 1999 21:37:47 EST." Date: Sat, 13 Mar 1999 20:08:25 -0800 Message-ID: <6067.921384505@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This stuff oughta be somewhere, soonest. If it's not man page, at least > a temporary distillation of it in a file in sys/boot, to be tossed once > there's a man page. *chuckle* It's like taking candy from a baby, I tell you! I can't help but notice that Chuck is a committer, and under the rules of "he who last touched it, gets it" in -committers, I'd say we're all in unanimous agreement (with him) that he should now commit something to start this process along, right folks? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 13 21:31:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kar.net (n186.cdialup.kar.net [195.178.130.186]) by hub.freebsd.org (Postfix) with ESMTP id AB37D14EE2 for ; Sat, 13 Mar 1999 21:31:21 -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 HAA27370; Sun, 14 Mar 1999 07:31:00 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Sun, 14 Mar 1999 07:30:59 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: "David O'Brien" Cc: Vladimir Kushnir , current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs In-Reply-To: <19990313200255.C8213@relay.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 Excellent, I'll have a free weekend then :-) BTW, do you plan to include egcs' g77 as well? On Sat, 13 Mar 1999, David O'Brien wrote: > Yes. What I was working on is newer than the CVS repository. I'm > chasing several issues & moving things around. I haven't been keeping > the CVSup'able totally bits upto date in the past few days. > > Tonight or Sunday, I hope to have the same thing I'm working on available > to all. > > -- > -- 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